show statusdb
Use the show statusdb command to view the Status Database. Each machine involved in replication has its own Status Database that contains records of key replication events, including those that did not generate an error message or warning at the user interface. This information can alert you to potential problems and help you resolve existing ones.
The show statusdb display includes the following information:
- Level: whether the entry is there only for information purposes or whether it is the result of an error or warning condition.
- Details: the reason for the event.
When appropriate, the Status Database refers you to the Event Log if there is more information about an entry.
Usage
Supported sources: |
Oracle |
Supported targets: |
All |
Authorization level: |
Viewer (3) |
Issued for: |
source or target system |
Related commands: |
status, lstatus |
Syntax
show statusdb |
detail |
[ on host |
on host:portnumber |
on login/password@host |
on login/password@host:portnumber ] |
Syntax description
detail |
This option displays a higher level of detail for the Status Database.
Example:
sp_ctrl(sysB)> show statusdb detail |
Remote options
These options enable you to issue the command on a remote machine and to script commands that include a login name, password, port number, or combination of those items.
on host |
Execute the command on a remote system (one other than the one where the current sp_ctrl session is running). You are prompted for login credentials for the remote system. If used, must be the last component of the command syntax.
Example: sp_ctrl(sysB)>status on SysA |
on host:portnumber |
Execute the command on a remote system when a remote login and port number must be provided. If used, must be the last component of the command syntax.
Example: sp_ctrl(sysB)>status on SysA:8304 |
on login/password@host |
Execute the command on a remote system when a remote login, password, and host name must be provided. If used, must be the last component of the command syntax.
Example:sp_ctrl(sysB)>status on john/spot5489@SysA |
on login/password@host:portnumber |
Execute the command on a remote system when a remote login, password, host name, and port number must be provided. If used, must be the last component of the command syntax.
Example: sp_ctrl(sysB)>status on john/spot5489@SysA:8304 |
show scn
Show SCN
Use the show scn command to view the Oracle SCN of the last transaction that a Post process applied to the target. The command shows all of the last SCNs when using multiple post queues.
NOTE: This command stops all Post processes in order to obtain the SCN information.
sp_ctrl (sysB)> show scn
For resume replication from ora112
On source activate to scn=4550108289
reconcile queue spdl13 for o.ora112-o.ora112 scn 4550108290
reconcile queue spdl14 for o.ora112-o.ora112 scn 4574108174
reconcile queue spdl15 for o.ora112-o.ora112 scn 5374667318
Usage
Supported sources: |
Oracle |
Supported targets: |
Oracle |
Authorization level: |
Viewer (3) |
Issued for: |
target system |
Related commands: |
activate config |
Syntax
show scn |
[ on host |
on host:portnumber |
on login/password@host |
on login/password@host:portnumber ] |
Remote options
These options enable you to issue the command on a remote machine and to script commands that include a login name, password, port number, or combination of those items.
on host |
Execute the command on a remote system (one other than the one where the current sp_ctrl session is running). You are prompted for login credentials for the remote system. If used, must be the last component of the command syntax.
Example: sp_ctrl(sysB)>status on SysA |
on host:portnumber |
Execute the command on a remote system when a remote login and port number must be provided. If used, must be the last component of the command syntax.
Example: sp_ctrl(sysB)>status on SysA:8304 |
on login/password@host |
Execute the command on a remote system when a remote login, password, and host name must be provided. If used, must be the last component of the command syntax.
Example:sp_ctrl(sysB)>status on john/spot5489@SysA |
on login/password@host:portnumber |
Execute the command on a remote system when a remote login, password, host name, and port number must be provided. If used, must be the last component of the command syntax.
Example: sp_ctrl(sysB)>status on john/spot5489@SysA:8304 |
show sync
The show sync command shows any out-of-sync issues that Post may have encountered. The information is extracted from the Status Database.
For each out-of-sync object, the command displays:
- Count: the number of statements that failed
- Detail: contains the table name, queue name, date and time
To see which SQL statement caused the error, view the SID_errlog.sql log file. The Event Log also will contain a record of the problem.
If nothing is out of synchronization when you issue the show sync command, you will be returned to the sp_crtl prompt.
Issue this command for the target system.
Usage
Supported sources: |
Oracle |
Supported targets: |
All |
Authorization level: |
Viewer (3) |
Issued for: |
target system |
Related commands: |
show statusdb |
Syntax
show sync |
[ on host |
on host:portnumber |
on login/password@host |
on login/password@host:portnumber ] |
Remote options
These options enable you to issue the command on a remote machine and to script commands that include a login name, password, port number, or combination of those items.
on host |
Execute the command on a remote system (one other than the one where the current sp_ctrl session is running). You are prompted for login credentials for the remote system. If used, must be the last component of the command syntax.
Example: sp_ctrl(sysB)>status on SysA |
on host:portnumber |
Execute the command on a remote system when a remote login and port number must be provided. If used, must be the last component of the command syntax.
Example: sp_ctrl(sysB)>status on SysA:8304 |
on login/password@host |
Execute the command on a remote system when a remote login, password, and host name must be provided. If used, must be the last component of the command syntax.
Example:sp_ctrl(sysB)>status on john/spot5489@SysA |
on login/password@host:portnumber |
Execute the command on a remote system when a remote login, password, host name, and port number must be provided. If used, must be the last component of the command syntax.
Example: sp_ctrl(sysB)>status on john/spot5489@SysA:8304 |
shutdown
Use the shutdown command to shut down replication. Upon completion of the shutdown command, SharePlex shuts down sp_ctrl automatically.
Shutting down gracefully
The basic shutdown command shuts down sp_cop (the Sp_Copsrv on Windows systems) and all other SharePlex processes gracefully, saving the state of each process, performing a checkpoint to disk, read-releasing buffered data, and cleaning up child processes. Data in the queues remains safely in place, ready for processing when an authorized user starts sp_cop again.
Shutting down forcefully
The shutdown command with the [force] option kills the SharePlex processes immediately, whether or not the normal shutdown procedures were completed. SharePlex recovers from a forced shutdown when you start sp_cop, but replication processing resumes from a previous save point, which means startup can be slightly longer.
Use the [force] option only if you tried to shut down SharePlex gracefully, but child processes remained running. You can verify whether SharePlex processes are still running by issuing the ps -ef | grep sp_ command in the command shell or by viewing the Processes tab in Windows Task Manager.
Important: If you shut down replication and users continue changing the objects in the active configuration(s), it is possible for the Oracle redo logs to wrap before SharePlex starts again. If the delay is long and the archive logs become unavailable, you will need to re-synchronize the data. The redo logs should be large and numerous enough to accommodate the time SharePlex will be shut down. For more information about the proper sizing of the redo logs for replication, see the SharePlex Installation and Setup Guide.
Usage
Supported sources: |
Oracle |
Supported targets: |
All |
Authorization level: |
Administrator (1) |
Issued for: |
source or target system |
Related commands: |
startup |
Syntax
shutdown |
[force] |
[ on host |
on host:portnumber |
on login/password@host |
on login/password@host:portnumber ] |
Syntax description
force |
This option shuts down all replication processes, including sp_cop, immediately, whether or not they have finished reading from or writing to a queue. Use this option if the default shutdown command fails or you cannot wait for a graceful shutdown.
Example:
sp_ctrl(sysA)> shutdown force |
Remote options
These options enable you to issue the command on a remote machine and to script commands that include a login name, password, port number, or combination of those items.
on host |
Execute the command on a remote system (one other than the one where the current sp_ctrl session is running). You are prompted for login credentials for the remote system. If used, must be the last component of the command syntax.
Example: sp_ctrl(sysB)>status on SysA |
on host:portnumber |
Execute the command on a remote system when a remote login and port number must be provided. If used, must be the last component of the command syntax.
Example: sp_ctrl(sysB)>status on SysA:8304 |
on login/password@host |
Execute the command on a remote system when a remote login, password, and host name must be provided. If used, must be the last component of the command syntax.
Example:sp_ctrl(sysB)>status on john/spot5489@SysA |
on login/password@host:portnumber |
Execute the command on a remote system when a remote login, password, host name, and port number must be provided. If used, must be the last component of the command syntax.
Example: sp_ctrl(sysB)>status on john/spot5489@SysA:8304 |