As this is by desing no ‘solution’ is required.
However there are instances where a customer’s Primary server has failed and it is required to export the database from the Secondary without reinstalling the Primary and Synchronizing.
Further ‘migrate export/upgrade_export’ requires that all SmartConsoles be disconnected before running it. therefore if the ‘Primary’ is up and is ‘Active’ it might be useful if the export could be run on a ‘Standby’.
The Primary is the Security Management Server installed first in an environment and the rest will all be Secondary. Further the Primary can be Standby while a Secondary is Active. Please read sk65370 for further details.
To verify the Primary/Secondary state of the server, run
# cpprod_util FwIsPrimary
This should return ‘1’ if the server is the Primary
or ‘0’ if the server is Secondary.
So the workaround is to trick the migration script into believing that its running on the Primary and not on a Secondary.
To do this you should run this command.
# cpprod_util FwSetPrimary 1
Verify this change by running the « cpprod_utill FwIsPrimary » command again. Once this parameter is set to ‘1’, you should be able to run ‘migrate export’ or ‘upgrade_export’ (depending on the version) without it causing an issue.
Once the export is complete change the setting back to ‘0’ by running the following command.
# cpprod_util FwSetPrimary 0