Filter
Top Products
446 U41117-J-Z125-7-76
Message lines Explanation of console messages
Case 3:
If the value 0 seconds is specified as the period, no usable data is contained in
/etc/mirrord/ms.db. Notify 3rd-Level Support!
SXCF014 CMF(#14): ALERT: failed to become PRIMARY, stale data
Meaning
When switching from SVLP to VLP a mirror backup server switches to become the mirror
server (from the viewpoint of the CMF). During the change to multi-user mode in the VLP’s
boot phase, the /etc/rc2.d/S70mirrorstart script determines that the data resources
are not up-to-date when it checks the cache mirror data (/etc/mirrord/ms.db).
This can occur when the failed VLP was not able to replicate the data (see message
SXCF012).
The switchover to multi-user mode is stopped and the data resources are updated manually.
Response
Access to the VLP via LAN is possible because the LAN services (inetd) are already
activated.
The most recent valid data resources of the “ex-VLP” must be restored manually on the new
VLP. When activated the ex-VLP automatically becomes the SVLP. When you switch to
multi-user mode this will probably be halted in the /etc/rc2.d/S70mirrorstart script
because the database (/etc/mirrord/ms.db) which the VLP has not yet been able to
replicate is obsolete. However, access via LAN is possible.
The following steps are required to update the data resources:
1. Terminate the mirror server on the VLP:
myps -K mirror.s
2. Copy the last version of the data resources but one from the ex-VLP to the VLP using
rcp:
rcp <Name-des-Ex-VLPs>:/etc/mirrord/ms.dbak /etc/mirrord/ms.db
3. Start the mirror server on the VLP:
/etc/mirrord/mirror.spray