When a new config is activated on the top of the existing active config, the status shows "Config Change" process in the output:
Â
sp_ctrl (servername:2100)> status
Brief Status for servername
Process State PID Running Since
--------------- ------------------------------ -------- --------------------
Cop Running 2580890 25-Mar-10 20:58:30
Cmd & Ctrl Running 2400542 25-Mar-10 21:02:27
Config Change Running 1953830 25-Mar-10 21:02:50
Cmd & Ctrl Running 1888440 25-Mar-10 21:03:08
There are no active configuration files
General information.
It simply tells that there is currently a config being activated. Depending on the number of objects added in the newer config file, the config may take some time to activate. During that period the "status" output will show "Config Change" is running. If the activation process is not able to lock one or more of the tables (say for example, when using "live" activation), then the activation process will wait till it is able to acquire the lock. This may show that "Config Change" is running for a long time. This fact can be confirmed from the event log entries where the ORA-00054 will appear if Shareplex is not able to acquire the lock. There can be other reasons which may cause the config to take a long time to activate or error out eventually. But in case of latter the previously active config file will remain activated.
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center