lstatus command

Use the lstatus command to view detailed information about the status of replication on a source or target system. This command is the most comprehensive information command in sp_ctrl. To view a brief status of replication, use the status command.

The lstatus command displays:

• The status of the replication processes, including their associated queues.
• The operating system process ID of each process.
• When the process started.
• The machine where the process is running.
• The number of messages (SQL or SharePlex operations) in the queues and their age.
• Whether the machine is a source or target system.
• Events that took place since sp_cop started.
• A list of active configurations.

The lstatus command also provides information about the queues, including:

• Type: The kind of queue that it is (capture queue, export queue, post queue).
• Queue name: The name of the queue, either a default name or the user-assigned name of a named queue.
• # Messages: The number of messages in the queue. A message approximately corresponds to a SQL operation, but there can be multiple messages for one operation on a LONG or LOB column. Conversely, there could be one message for numerous operations in an array insert.
• Size: The current size of the queue. This varies with the amount of data.
• Age: The time difference between when the oldest and newest messages in the queue were written to that queue.
• Oldest Msg Time: The date and time the oldest message entered the queue.
• Newest Msg Time: The date and time the newest message entered the queue.

The lstatus command also provides other information, such as how the system is being used, its configuration activity, and errors that occurred.

Understanding the SharePlex queues

The following will help you understand the statistics for the SharePlex queues.

Queue size

Although SharePlex uses memory for the queues, the data is periodically written to disk as part of the checkpoint recovery system. The default size for SharePlex queue files is 8 MB. However, queue files are sparse files, meaning that from a system standpoint the file size is 8 MB, but the filesystem might only allocate part of the file for data written to the queues.

That is why the qstatus command can show a queue size of less than 8 MB, but what you see with qstatus is NOT the true indication of the actual file size. To predict disk space usage for the queue files, use the information from qstatus and not the filesystem.

Number of queues

It is normal for the capture and export queues to have fewer queue files than the post queue. Data that resides in one queue file on the source system is separated into multiple sub-queue files on the target system, each approximately corresponding to a user session on the source system.

Names of queues

Queue names are case-sensitive on all platforms. The following explains the naming conventions for SharePlex queues.

• Default capture queues are identified by their datasource, which is expressed as o.SourceSID, for example o.ora64.
• Default export queues are identified by the source system's name, for example SysA.
• Default post queues are identified by the name of the source system appended with datasource-datadestination, where datasource is o.sourceSid and datadestination is o.targetSID, for example lajolla (o.ora10a-o.ora10b).
• Named export and post queues are identified by their user-assigned names, not the default name. For more information about named queues, see the SharePlex Administration Guide.

Usage

Supported sources:	Oracle
Supported targets:	All
Authorization level:	Viewer (3)
Issued for:	source or target system
Related commands:	qstatus, show, show statusdb, status

Syntax

Basic command	Remote options
lstatus	[ 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.

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