Use the show read command to view statistics about the Read process.
The basic show read command shows an overview of the process, such as the data source, whether the process is running or stopped, and other basic information.
To view detailed statistics for the Read process, use the show read command with the [detail] option. This option shows detailed statistics that can help you assess the performance of the process, decide whether tuning parameters need to be adjusted, and detect problems or bottlenecks.
|Host||The name of the local machine (source system).|
|Source||The name of the source Oracle instance.|
The status of the Read process (running or stopped).
|Operations forwarded||The number of operations that Read sent to the Export queue.|
|Since||The time that Read started.|
|Total||The number of messages in the capture queue that have yet to be read-released. This number corresponds to the 'Number of messages' returned from running qstatus.|
|Backlog||The number of messages that are waiting in the capture queue to be processed by Read.|
|Last operation forwarded||Identifying information about the most recent operation that Read sent to the export queue, or the last operation it sent if Read is inactive. An operation can be data relating to a DML or DDL operation or an internal SharePlex operation.|
The state of the process, in relation to the replication work it performs: It can be one of the following:
The Read State field is useful if Read appears to be taking too long to process an operation.
|Activation ID||The internal identifying number of the configuration activation, which identifies the associated processes and queues.|
|Operations forwarded||The number of transactional and internal SharePlex operations sent by Read to the export queue since it started.|
|Transactions forwarded||The number of committed transactions sent by Read to the export queue since it started. Comparing this value with the value for the operations forwarded indicates whether the transactions tend to be small or large. You can use that information to determine why Read appears to be falling behind and why the queues are not emptying (large transactions without a COMMIT).|
|Full rollbacks||The number of rolled back transactions processed by Read.|
|Full rollback operations skipped||The number of operations that Read does not forward to the export queue because the transaction was rolled back.|
|Cursor cache hit count||The number of times Read used a cached cursor.|
|Cursor cache miss count||The number of times Read could not use a cached cursor.|
|Number of open cursors||The number of open cursors reserved by Read to access Oracle if necessary.|
|Number of active batches||The number of transactions currently active that are being processed as a batch transaction. If enabled, Read will combine batch operations so that they can be posted more quickly.|
|Batch message total||The number of operations that the Read process combines into batch operations.|
|Authorization level:||Viewer (3)|
|Issued for:||source system|
|Related commands:||show capture, show export, show import, show post|
|Basic command||Command options||Remote options|
[detail] [for datasource]
[ on host |
on host:portnumber |
on login/password@host |
on login/password@host:portnumber ]
This option displays detailed statistics for the Read process.
sp_ctrl(sysA)> show read detail
This option shows Read statistics for a specific datasource.
datasource is expressed as o.SID, where SID is an ORACLE_SID.
sp_ctrl(sysA)> show read for o.oraA
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.
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
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
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
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