REBUILD Utility Cannot be run on a non-AMP vproc

[JJayUK]

Hello,

Using the local demo version which we use to develop with we lost one of the AMPS (AMP 1) which went to FATAL. Using vprocmanager I executed a BOOT command and the status of the AMP is now UTILITY.

When trying to execute the REBUILD command, though, I'm getting the error:

REBUILD Utility cannot be run on a non-AMP vproc (VprocId = 16384) . The results from the STATUS command are below. If anyone can help that would fantastic as I'd hate to have to reinstall it again!

SYSTEM NAME: localhost 05/08/25 12:54:30

DBS LOGICAL CONFIGURATION
-------------------------

Vproc Rel. Node Crash Vproc Config Config Cluster/ RcvJrnl/
Number Vproc# ID Movable Count State Status Type Host No. Host Type
------ ------ ------ ------- ----- ------- -------- ------ -------- ---------
0* 1 1-01 Yes 0 ONLINE Online AMP 0 On
1 2 1-01 Yes 0 UTILITY Down AMP 0 On
8192 4 1-01 No 0 ONLINE N/A GTW 1 COP
16383 3 1-01 No 0 ONLINE Online PE 1 COP
--------------------------------------------------------------------------------
* DBS Control AMP

DBS State: Logons are enabled - The system is quiescent

DBS RestartKind: COLDWAIT

PDE PHYSICAL CONFIGURATION
--------------------------

Node Node Clique # Memory # #
ID State Number CPUs (MB) CHANs LANs Node Name
------- ------- ------ ---- ------ ----- ---- --------------------------------
1-01@ ONLINE 0 1 255 0 1 localhost
------------------------------------------------------------------------------
@ PDE Distribution Node

PDE State: RUN/STARTED



Regards,
JJayUK

 

[BillDHS]

I don't know if I can help much. Instead of creating an AMP VPROC, you created a PE VPROC. The documnetation might give you a clue on dropping it and creating an AMP

 

[tdatgod]

Hi,
you must run REBUILD from DBW/cnstool. It doesn't run from the cmd prompt.

Its a DEMO.... Unistall it and Reinstall it. Make sure to answer Yes to do you want to remove the TDCONFIG dirrectory.

Its not like there is any DATA out there that you can't get back from simply re running the installation.