rsync from EMCC standby OMS nodes

From the OMS secondary 1:

export LVMSOURCE=<IP>

echo "Synching /u01"
rsync -vat --stats --checksum --delete --delete-excluded --exclude '*.log' --exclude '*.trc' --log-file=$HOME/admin/rsync.log --progress ${LVMSOURCE}:/u01/ /u01

echo "Synching /library"
rsync -vat --stats --delete --checksum --delete ${LVMSOURCE}:/library/ /library

echo "Synching /bip"
rsync -vat --stats --delete --checksum --delete ${LVMSOURCE}:/bip/ /bip

 

From the OMS secondary 2:

export LVMSOURCE=<IP>

echo "Synching /u01"
rsync -vat --stats --checksum --delete --delete-excluded --exclude '*.log' --exclude '*.trc' --log-file=$HOME/admin/rsync.log --progress ${LVMSOURCE}:/u01/ /u01

 

Advertisements

TNS-12541 TNS-560 TNS-00511 While starting listener

Under some circumstances, a listener may fail to start with the following error.

TNS-12541: TNS:no listener
TNS-12560: TNS:protocol adapter error
TNS-00511: No listener
Linux Error: 111: Connection refused

Solution may be to set the LD_BIND_NOW variable to 1.

Then optionally to restart the EMCC agent with that parameter set, if the error occured during an agent-base software deployment. Preferably undo this change once the EMCC  job has completed, as this parameter may have side effects on other EMCC jobs.

 

EM13c: Resuming from error during a management server plugin deployment

To recover from a plugin deployment that failed on either of the Management Servers, for example in the latest step ‘Starting Management Server’, leaving the deployment unfinished and leaving the status as ‘deploying’ in the OMS UI, a possible solution is to start a dummy pluginca session on this OMS server where the session could not complete.

To example, to recover from an issue deploying the ZFS plugin agent, that occured on the second OMS:

On the second OMS server:

$ORACLE_HOME/bin/pluginca -plugins oracle.sun.oss7=13.2.4.0.0 -action all -isfirstoms false

This session would display in success status, on the deployment activity page for this plugin. The old session stuck in status ‘deploying’ will then be ignored.