Use the show post command to view statistics for the Post process.
Basic show post command
The basic show post command shows global statistics for all sessions a Post process. It shows the status of the Post process and the number of messages posted since it started. To filter the output for a specific post queue or datasource (useful when you have multiple replicating data streams), use the queuequeuename or fordatasourcedatadest option.
Detailed show post command
To view detailed statistics for the Post process, use the show post command with the detail option. That option shows the most recent SQL statement processed, as well as other statistics that can help you assess Post’s performance, decide whether tuning parameters need to be adjusted, and detect problems or bottlenecks.
The following explains the detailed statistics shown with show post. These statistics vary slightly depending on the type of source and target.
Statistic | Description |
---|---|
Host | The name of the local machine (target system). |
Source | The source of the data being processed by Post. |
Queue | The Post queue for this Post process. For a default Post queue, it is the name of the source system. For a named queue, it is the user-defined name. |
Target | The name of the target of this Post process, for example the name of an Oracle instance or Open Target database. |
Status |
The status of the Post process (running or stopped). Possible statuses are:
|
Operations posted Operations processed |
The number of transactional operations and SharePlex internal operations that this Post process processed since it was started. |
Since | The time that Post started. |
Total | The number of messages in the 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 queue to be processed by Post. |
Last operation posted |
Identifying information for the most current operation that is being posted to the target if Post is active, or the last operation posted if it is inactive. This information is specific to the type of datastore that originated the data. An operation can be:
|
Last transaction posted Last transaction processed |
Identifying information for the last transaction that was posted. This information is specific to the type of datastore that originated the data. |
Last file switch | Shown if the target is output to a file. Shows the record identifier for the record after which the active file was switched to a new one. |
Post state |
The state of the Post process, in relation to the replication work it performs. It can be one of the following:
|
Activation ID | The activation ID of the current configuration. |
Number of messages read released |
Shown for an Oracle target. Shows the difference between the number of operations posted and the actual number of operations removed from the queue. This field is used mainly by Technical Support staff when Post is stalled. |
Number of threads | Shown for an Oracle target. Shows the number of processing threads in a multithreaded Post, including the main and timekeeper threads. |
Number of Oracle connections |
Shown for an Oracle target. Shows the number of connections that a multithreaded Post has open. |
Concurrency (Active sessions) | Shown for an Oracle target. Shows the number of concurrent transactions that multithreaded Post is processing. |
Peak number of sessions | Shown for an Oracle target. Shows the highest number of concurrent transactions that multithreaded Post processed since it was started. |
Operations posted Operations processed |
The number of SQL operations that Post applied to the target, whether or not the COMMIT was received. |
Transactions posted Transactions processed |
The number of committed transactions that Post applied to the target since it was started. |
Full rollbacks | Shown for an Oracle target. Shows the number of rolled back transactions processed by Post. |
Full rollback operations posted | Shown for an Oracle target. Shows the number of operations that Post applied before the transcation was rolled back. (Post does not wait for a commit to start applying operations that it has in the queue.) |
Full rollback operations skipped | Shown for an Oracle target. Shows the number of operations that Post skipped because it received an early indication that the transaction was rolled back. |
Transactions <= 2 | Shown for an Oracle target. Shows the number of transactions that contain two or fewer operations. |
Transactions > 10000 | Shown for an Oracle target. Shows the number of transactions that contain more than 10,000 operations. |
Largest transaction | Shown for an Oracle target. Shows the size of the largest transaction processed. |
Insert operations | The number of INSERT operations processed by Post since it was started. |
Update operations | The number of UPDATE operations processed by Post since it was started. |
Delete operations | The number of DELETE operations processed by Post since it was started. |
Insert batch operations / average |
|
Delete batch operations / average | Shown for an Oracle target. Shows the number of DELETE_BATCH statements processed / average number of DELETE operations in one DELETE_BATCH statement. |
Other operations | Shown for an Oracle target. Shows the number of operations, other than INSERT, UPDATE or DELETE, processed by Post since it was started. |
LOB changes | Shown for an Oracle target. Shows the number of LOB change operations. |
Key cache hit count | Shown for an Oracle target. Shows the number of times that the SharePlex internal key cache was used by the Post process to generate UPDATE statements. SharePlex uses the key cache to post data to the target instance quickly. |
SQL cache hit count | Shown for an Oracle target. Shows the ratio of the total number of messages that were executed without parsing and binding divided by the total number of INSERT, UPDATE and DELETE operations. For more information on the SQL Cache feature of SharePlex, see the SharePlex Administration Guide. |
File switches | Shown if the target is output to a file. Shows the total number of file switches performed by Post. |
Usage
Supported sources: | Oracle |
Supported targets: | All |
Authorization level: | Viewer (3) |
Issued for: | target system |
Related commands: | show capture, show read, show export, show import |
Syntax
Basic command | Command options | Remote options |
---|---|---|
show post |
[detail] [queue queuename] [for datasource-datadest] [sessions] [session=n] |
[ on host | on host:portnumber | on login/password@host | on login/password@host:portnumber ] |
Syntax description
Component | Description |
---|---|
show post |
|
detail |
This option displays detailed statistics for the Post process. Example: sp_ctrl(sysB)> show post detail |
queue queuename |
This option filters the show post display for a specific post queue.
If you are unsure what the queue name is, issue the qstatus command. Queue names are case-sensitive on all platforms. This option can appear in any order with other options. Example: sp_ctrl(sysB)> show post queue sysA |
for datasource-datadest |
This option filters the show post display for a specific data stream.
This option can appear in any order with other options. Example: sp_ctrl(sysB)> show post for o.oraA-r.ssB |
sessions |
For Oracle targets, this option displays statistics for all of the threads spawned by the Post process. For Open Target, which is single-threaded, this option can be used to view details for that thread. This option can appear in any order with other options. Example: sp_ctrl(sysB)> show post sessions queue queuename |
session=n |
(Oracle only) This option displays statistics shown in the show post sessions output plus additional details about the state of the thread, the number of messages waiting to be processed by the thread, and the status of the overall transaction. • session= is a required part of the syntax. • n is any session number displayed with the show post sessions command. Leave no space between any of the components. This option can appear in any order with any other option. Example: sp_ctrl(sysB)> show post session=1234 queue queuename |
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.
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 |