Utilities affecting the primary database

The following table lists Control‑M/Server utilities that affect the primary database and the action required to ensure that the mirror database is in sync.

ctm_menu Option

Database

Utility/Menu

Action

Database Menu

Build Database

  • Oracle
  • MSSQL

internal utility

Initialize Mirroring

Delete Database

Oracle

Troubleshooting Menu

Initialize Mirroring

Erase Database

  • Oracle
  • MSSQL

Troubleshooting Menu

Initialize Mirroring

Restore Database

  • Oracle
  • MSSQL

Database Menu

Initialize Mirroring

Database Maintenance Menu

Extend Database Size

  • Oracle
  • MSSQL

ctm_dbextend

Initialize mirroring

Troubleshooting Menu

Restart New Day Procedure

  • Oracle
  • MSSQL

internal utility

Initialize Mirroring

Reset Control‑M Active Environment

  • Oracle
  • MSSQL

clean_ajf

Initialize Mirroring

Remote Host computers

  • Oracle
  • MSSQL

ctmhostmap or Control-M Configuration Manager

By adding the details of a remote host computer to the Control-M/Server database, you need to run the command ctm_agstat -AGSTAT <remoteHostName> R R on the secondary Control-M/Server.

Replace the <remoteHostName> variable with the name of remote host that was added.

By updating or modifying the the specified remote host computer details in the Control-M/Server database, you need to run the command on the secondary Control-M/Server: ctm_agstat -AGSTAT <remoteHostName> R R

Replace the <remoteHostName> variable with the name of remote host that was updated.

Delete: Delete the details of the specified computer from the Control-M/Server database

Remote Host computer

  • Oracle
  • MSSQL

ctmhostmap or Control-M Configuration Manager

By converting a Control-M/Agent to a remote host run the command on the secondary Control-M/Server: ctm_agstat -AGSTAT <remoteHostName> R R

Replace the <remoteHostName> variable with the node that was updated.

Parent Topic

Control-M/Server mirroring database