Review the instance-specific system settings for the new primary instance and update any setting as needed.
Note:The new primary instance does not inherit these settings from the original primary instance.
In the Security Console, go to Setup > System Settings, and review the settings that are configured by instance.
For example, you may want to review and update the following instance-specific settings:
Verify your dynamic seed provisioning configuration
In the Security Console, go to Setup > System Settings, and under Authentication Settings, click Tokens.
Review the dynamic seed provisioning settings. If the fully qualified hostname of the demoted primary instance is used, update the setting with the fully qualified hostname of the new primary instance. For further instructions, see Configure Token Settings.
Depending on the outcome of the promotion, additional steps may also display.
If any of the following scenarios apply to the promotion that you completed, you must perform the corresponding task:
You chose to manually copy and transfer log data after promotion
The log backup file is created on the original primary instance. Using methods like FTP, transfer the backup file to a supported backup location. For instructions on restoring from a backup, see Restore from Backup.
Note:SSH must be enabled to access the local file system on the instance. To enable SSH, go to the Operations Console for the instance and click Administration > Operating System Access.
One or more additional replica instances could not be updated to point to new primary instance
Enable communication with replica instances
For each additional replica instance that could not be updated, log on to the Operations Console of the replica instance, click Administration> Network> Update Primary Hostname and update the Primary Hostname field to that of the new primary instance.
The original primary instance cannot be demoted
Reset and configure the original primary instance as a replica