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.
Statistic | Description |
---|---|
Host | The name of the local machine (source system). |
Source | The name of the source Oracle instance. |
Status |
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. |
Read state |
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. |
Supported targets: | All |
Authorization level: | Viewer (3) |
Issued for: | source system |
Related commands: | show capture, show export, show import, show post |
Basic command | Command options | Remote options |
---|---|---|
show read |
[detail] [for datasource] |
[ on host | on host:portnumber | on login/password@host | on login/password@host:portnumber ] |
Component | Description |
---|---|
show read |
|
detail |
This option displays detailed statistics for the Read process. Example: sp_ctrl(sysA)> show read detail |
for datasource |
This option shows Read statistics for a specific datasource. datasource is expressed as o.SID, where SID is an ORACLE_SID. Example: 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.
Option | Description |
---|---|
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 |
Use the show sql command to view the SQL statement being written by the Post process to post data to the target database. If the post queue is empty, or if Post is not processing a statement, the show sql command shows the most recent SQL statement processed.
Use this command when you think replication is taking too long, or when Post stops on an error. Knowing which SQL statement is at fault can help you determine what is wrong and whether or not further action is required.
The following is an example of the show sql display:
sp_ctrl (tustin:8852)> show sql
Last SQL statement of queue tustin and instance o.ora920-0.ora920 on tustin
insert into “KWONG”.”KCWTAB2” (“C1”,”C2”) values (:V001,:V002)
Issue this command for the target system.
Supported targets: | All |
Authorization level: | Viewer (3) |
Issued for: | target system |
Related commands: | none |
Component | Description |
---|---|
show sql | Without options, shows all SQL statements. |
queue queuename |
Use this option to show the SQL statement for a specific named queue.
Queue names are case-sensitive on all platforms. Example: sp_ctrl(sysA)> show sql queue q1 |
for datasource-datadest |
Use this option to show the SQL for a specific replication stream when you are replicating to or from more than one Oracle instance.
Example: sp_ctrl(sysA)> show sql for o.oraA-o.oraB |
thread=n |
Use this option to show the SQL for a post processing thread.
Leave no spaces between the components. This option can appear in any order with other options. Example: sp_ctrl(sysB)> show sql thread=1234 |
session=n |
Use this option to show the SQL for a user session. • session= is a required part of the syntax. • n is a session number displayed with the show post threads command. Leave no space between the components. This option can appear in any order with other options. Example: sp_ctrl(sysB)> show sql session=1234 |
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.
Option | Description |
---|---|
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 |
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:
When appropriate, the Status Database refers you to the Event Log if there is more information about an entry.
Supported targets: | All |
Authorization level: | Viewer (3) |
Issued for: | source or target system |
Related commands: | status, lstatus |
Basic command | Command options | Remote options |
---|---|---|
show statusdb | detail |
[ on host | on host:portnumber | on login/password@host | on login/password@host:portnumber ] |
Component | Description |
---|---|
detail |
This option displays a higher level of detail for the Status Database. Example: sp_ctrl(sysB)> show statusdb detail |
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.
Option | Description |
---|---|
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 |
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
Post processes replicating from o.w111a64f
Queue spxl11, SCN of the last transaction applied: 292767
Queue eq1, SCN of the last transaction applied: 192563
Queue pq1, SCN of the last transaction applied: 232686
Queue pq2, SCN of the last transaction applied: 18995
Queue pq3, SCN of the last transaction applied: 31032
Target o.ora112 is consistent with source o.w111a64f at SCN 18995
Supported targets: | Oracle |
Authorization level: | Viewer (3) |
Issued for: | target system |
Related commands: |
activate config |
Basic command | Remote options |
---|---|
show scn |
[ on host | on host:portnumber | on login/password@host | on login/password@host:portnumber ] |
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.
Option | Description |
---|---|
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 |
© 2021 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy