Siebel Remote and Replication Manager Administration Guide > Administering Siebel Remote > Monitoring Siebel Remote Operations >
Monitoring Transaction Logs
Use the Administration - Siebel Remote views to monitor transaction logs. To monitor transaction logs
- From the application-level menu, choose Navigate > Site Map > Administration - Siebel Remote.
- In the link bar, select Transaction Log.
The Transaction Log list displays information about each transaction. The Operation Types for Siebel Remote transactions are as follows:
|
|
D |
Delete single row |
E |
Delete multiple rows |
F |
Delete cascading rows |
I |
Insert single row |
U |
Update single row |
V |
Update multiple rows |
X |
Insert set-based rows |
Y |
Update set-based rows |
Z |
Delete set-based rows |
G |
Merge multiple rows |
The fields in the Transaction Log list are described below.
|
|
Node Number |
ID of the node that generated the transaction |
Operation |
Insert (I), update (U), delete (D), ... |
Item |
Table name of the transaction |
File Flag |
Flag to indicate whether the transaction is on a file attachment-related table |
Transaction ID |
Sequence number of the transaction |
Transaction Row ID |
ROW_ID of the transaction |
Transaction Updated |
Timestamp showing when the transaction was last updated |
The fields in the Detail form are described below, except for fields that are identical to those in the Transaction Log list.
|
|
Transaction Updated by |
ROW_ID of the user who last updated the transaction |
Transaction Conflict ID |
ID of the conflict for the base table record |
Transaction Mod ID |
Version number of the base table record |
Visibility Level |
Visibility event level for the transaction: Enterprise(E), Limited(L) |
Visibility Event |
Whether the transaction is a visibility event |
Related Visibility Event |
Whether the transaction is a related visibility event |
Dock Object Code |
Dock object code of the transaction instance |
Primary Table Row ID |
ROW_ID of Primary table for the dock object instance |
Length (Long Log data) |
Real length of the long column of the transaction data |
Log Data 1, 2, 3, 4, long |
These fields hold transaction data |
- To monitor transaction logs by operation, select Transaction Log By Operation from the link bar.
The fields in the Transaction Log By Operation view provide information about the number of transactions for each operation using the following fields:
|
|
Operation |
Type of the operation |
Number of transactions |
Total number of transaction for the operation type |
- To monitor transaction logs by node, select Transaction Log By Node from the link bar.
The Transaction Log By Node view displays the number of transactions for each node. A node is a Mobile Web Client or Regional server. The following fields appear in the view:
|
|
Node Name |
Mobile client node name |
Number of transactions |
Total number of transactions for the operation type |
NOTE: This view only shows transactions from mobile users and regional nodes. It does not include transactions created by nonmobile users who connect directly to the server.
- To monitor transaction logs by table, select Transaction Log By Table from the link bar.
The Transaction Log By Table view displays the number of transactions for each table in the Siebel database. The following fields appear in the view:
|
|
Item |
Table name |
Number of transactions |
Total number of transactions for the operation type |
|