Release 7.0
A42860-1
 Library |
 Product |
 Contents |
 Index |
| Oracle Rdb7(tm) and Oracle CODASYL DBMS(tm) Guide to Hot Standby(tm) Databases Release 7.0 A42860-1 |
|
This chapter describes how to monitor database replication activities and describes some methodologies to enhance database replication performance.
You can use the database Show and Dump commands to monitor and evaluate all database activity. In many cases, you can display the database state and replication performance information graphically or numerically through these methods:
The Oracle RMU and Oracle CODASYL DBMS Show Users command is a powerful tool you can use to monitor the current status of the master and standby databases. For example, you can use the Show Users command to find out which replication servers are active or if after-image journal backup operations have been suspended.
Example 7-1 shows the output from an RMU Show Users command entered on the master database.
$ RMU /SHOW USERS database DISK1:[USER]MF_PERSONNEL.RDB;1- First opened 24-MAY-1996 08:41:29.71 * database is opened by an operator - current after-image journal file DISK1:[USER.MASTER]AIJ_1.AIJ;1 - Hot standby "Log Catch-Up Server" is active
- Hot standby "Log Shipping Server" is active
- AIJ Log Server is active - 3 active database users - 24404893:1 - RDMLS - non-utility, RDBVMS - active user - image DSA1:[SYS4.SYSCOMMON.][SYSEXE]RDMALS70.EXE;811 - output filename "DISK1:[USER.STANDBY]ALS_25C02918.OUT;"
- 24400F47:1 - HOT4 - utility, ORUSER - active user - image DISK1:[RDMS_X07000.VAX.][RMU]RMU70.EXE;1 - 24404E96:1 - RDM_LCS - non-utility, RDBVMS - active user - image DSA1:[SYS4.SYSCOMMON.][SYSEXE]RDMLCS70.EXE;755 - standby database "REMNOD::DISK1:[USER]STANDBY_PERSONNEL"
- Replication is "active"
- output filename "DISK1:[ORAUSER]LCS.LOG;" - synchronization mode "cold" - checkpoint interval 10 messages - wait interval 1 minute - quiet-point synchronization
The following list describes the callouts shown in Example 7-1:
The name of the master database.
The LCS process is currently bringing the standby database up to date with the master database.
The ALS process on the master database is active. Notice that the "Log Shipping Server" is another name for the ALS process when replication operations are active.
The name of the ALS output file (specified with the BIND_ALS_OUTPUT_FILE logical name).
The name of the standby database.
Indicates that replication operations are active. The lines following this one show the replication parameter settings for the master database.
Example 7-2 shows the output from an RMU Show Users command entered on the standby database.
$ RMU /SHOW USERS database _DISK1:[USER]STANDBY_PERSONNEL.RDB;1- First opened 24-MAY-1996 08:41:07.12 * database is opened by an operator - current after-image journal file is DISK1:[ORAUSER.STANDBY]AIJ_1.AIJ;1 - Hot standby "Log Roll-Forward Server" is active
- 2 active database users
- 24400F48:1 - HOT3 - utility, ORAUSER - active user - image DISK1:[RDMS_X07000.VAX.][RMU]RMU70.EXE;1 - 24404E97:1 - RDM_LRS70 - non-utility, RDBVMS - active user - image DSA1:[SYS4.SYSCOMMON.][SYSEXE]RDMLRS70.EXE;551 - master database "_DISK1:[USER]MF_PERSONNEL.RDB;1"
- Replication is "active" - checkpoint interval 100 messages - timeout interval 5 minutes - access mode "read only" - buffer count 256 - 2PC resolve state "commit" - Replication governor is enabled
The name of the standby database.
The LRS process is active.
There are 2 users active on the standby database. The lines following this one show the users.
The name of the master database.
The Oracle RMU and DBO Dump command displays or writes the contents of the database, storage areas, and snapshot files including database root information.
Database header information is especially useful when you want to display database parameter settings. For example, the header information can indicate when database replication is not possible because of inappropriate database attribute settings.
Because the output from the Dump command is lengthy, you can include the Header qualifier to display only the information that you need. For example, to display only the Hot Standby information, you can specify the Hot_Standby keyword on the Header qualifier.
Examples 7-3 and 7-4 show Hot Standby information in the database headers for the master and standby databases, respectively.
$ RMU/DUMP/HEADER=HOT_STANDBY HOTDISK:[ORAUSER.OE_MASTER]mf_personnel *----------------------------------------------------------------- * Oracle Rdb V7.0-00 24-MAY-1996 08:52:38.64 * * Dump of Database header * Database: DISK1:[USER]MF_PERSONNEL.RDB;1 *------------------------------------------------------------------- Database Parameters: Root filename is "DISK1:[USER]MF_PERSONNEL.RDB;1" Hot Standby... - Database is currently being replicated as "Master" Standby database is "DISK1:[USER]STANDBY_PERSONNEL.RDB;1" Database is local to this node ("ORANOD") Replication commenced on 24-MAY-1996 08:41:53.91 Synchronization obtained via quiet-point Server checkpoint interval is 10 messages Server connection-timeout interval is 1 minute Replication synchronization is "cold"Example 7-4 Dump Header Display for the Standby Database
$ RMU/DUMP/HEADER=HOT_STANDBY DISK1:[USER]standby_personnel.rdb;1 *------------------------------------------------------------------ * Oracle Rdb V7.0-00 24-MAY-1996 08:51:10.97 * * Dump of Database header * Database: DISK1:[USER]STANDBY_PERSONNEL.RDB;1 *------------------------------------------------------------------ Database Parameters: Root filename is "DISK:[ORAUSER.WORK.OE.OE_STANDBY]OE_RDB.RDB;1" Hot Standby... - Database is currently being replicated as "Standby" Master database is "DISK1:[USER]MF_PERSONNEL.RDB;1" Database is local to this node ("REMNOD") Replication commenced on 24-MAY-1996 08:41:52.81 Database replication is "online" Server checkpoint interval is 100 messages Server gap-timeout interval is 5 minutes Server buffer count is 256 Server 2PC transaction resolution is "commit"
Oracle Rdb and Oracle CODASYL DBMS provide Performance Monitor facilities to help you display and diagnose your database statistics, and tune your database performance. To view the current database statistics and performance information, enter the Oracle RMU or DBO Show Statistics command. The following example shows how to use this command for an Oracle CODASYL DBMS database:
$ DBO /SHOW STATISTICS PARTS
The Performance Monitor displays a summary statistics screen. You can enter the letter "M" to display a menu of options. To view information specific to your Hot Standby environment, select the Hot Standby Information submenu or the Database Dashboard submenu from the Oracle RMU or DBO Show Statistics main menu.
The following example shows the menu options you can select. You can highlight the Hot Standby Information submenu by typing the letter "J" or using the arrow keys to move to the Hot Standby selection.
When you select the Hot Standby Information option and press the Return key, the following menu displays from which you can choose to view either Hot Standby statistics or synchronization mode statistics:
Example 7-5 shows an example of the Hot Standby Statistics display.
Node: ORANOD Oracle Rdb V7.0-00 Performance Monitor 3-APR-1996 08:25:21 Rate: 1.00 Second Hot Standby Statistics Elapsed: 00:53:24.21 Page: 1 of 1 DISK1:[USER]MF_PERSONNEL.RDB;1 Mode: Online ----------------------------------------------------------------------------- State: Active UserSync: Cold Current.Msg: 2539 Cl Mstr.AIJ: 22:4487 LagTime: 00:01:53 AutoSync: Warm Stalled.Msg: 1 Stby.AIJ: 22:3447 Stby.DB: DISK01$:[ORAUSER.WORK.OE.OE_STANDBY]OE_RDB.RDB;1 statistic......... rate.per.second............. total....... average...... name.............. max..... cur..... avg....... count....... per.trans.... AIJ network send 9 0 0.8 2822 3.5 AIJ network recv 7 0 0.4 1345 1.6 data 8 0 0.7 2494 3.1 control 2 0 0.1 328 0.4 checkpoints 1 0 0.0 255 0.3 Stall time x100 1801 18 54.7 175432 220.1 blocks shipped 809 91 36.2 116248 145.8 received 7 0 0.4 1345 1.6 Network Reconnect 0 0 0.0 0 0.0 Free Network Xmit 10 0 0.9 2508 2.4 Stalled MSN found 0 0 0.0 0 0.0 -------------------------------------------------------------------------------- Exit Graph Help Menu Options Pause Reset Set_rate Time_plot Unreset Write X_plot
The last line of the display shows the options you can enter to control the display. For example, you can type the letter "H" to obtain online help information about any of the fields displayed. You can also type the letter "G" to obtain the Hot Standby Statistics in a graphical display.
Example 7-6 shows an example of the Synchronization Mode Statistics display.
Node: ORANOD Oracle Rdb V7.0-00 Performance Monitor 3-APR-1996 08:25:29 Rate: 1.00 Second Synchronization Mode Statistics Elapsed: 00:53:31.40 Page: 1 of 1 DISK1:[USER]MF_PERSONNEL.RDB;1 Mode: Online -------------------------------------------------------------------------------- statistic......... rate.per.second............. total....... average...... name.............. max..... cur..... avg....... count....... per.trans.... transactions 3 0 0.2 797 1.0 Cold sync send 8 0 0.4 1467 1.8 Warm sync send 7 3 0.2 961 1.2 Hot sync send 3 0 0.0 70 0.0 Commit sync send 0 0 0.0 0 0.0 Cold stall x100 6 0 0.1 456 0.5 Warm stall x100 1088 463 33.8 108765 136.4 Hot stall x100 1010 0 2.4 7809 9.7 Commit stall x100 0 0 0.0 0 0.0 -------------------------------------------------------------------------------- Exit Graph Help Menu Options Pause Reset Set_rate Time_plot Unreset Write X_plot
The Performance Monitor provides a Database Dashboard facility that displays the actual database parameter and attributes settings being used by the processes attached to the database. To view information specific to your Hot Standby environment, select the Database Dashboard submenu from the Oracle RMU or DBO Show Statistics main menu.
The following example shows the menu options you can select. To choose the Database Dashboard option, highlight it by typing the letter "U" or using the arrow keys to move to that selection.
When you are viewing any of the Database Dashboard displays, you can examine logical name and configuration parameter values and other database attributes settings during run time. You can "drive" the database faster or slower by optionally making changes without having to restart database processes. The changes are in effect on a single node and only during run time.
When you select the Database Dashboard option and press the Return key, the following menu displays from which you can choose from a number of Dashboard options:
You can use the Hot Standby Dashboard display to monitor the amount of time the standby database lags behind the master database. Monitoring the synchronization between the databases can help you decide whether to try to recover the master database after a failure or fail over to the standby database.
The following Hot Standby events are tracked by the Hot Standby Dashboard:
Example 7-7 shows an example of the Hot Standby Dashboard display.
Node: ORANOD Oracle Rdb V7.0-00 Performance Monitor 23-JUL-1996 19:53:29 Rate: 9.00 Seconds Hot Standby Dashboard Elapsed: 00:37:47.21 Page: 1 of 1 DISK1:[USER]MF_PERSONNEL.RDB;1 Mode: Online -------------------------------------------------------------------------------- Database.......... Current... Previous.. Lowest.... Highest... Original.. Chng Attribute.Name.... Value..... Value..... Value..... Value..... Value..... Cnt. Network Timeout120 120 120 120 120 0 Connect Timeout
5 5 5 5 5 0 Data Sync Mode
0 0 0 0 0 0 Server Checkpoint
100 100 100 100 100 0 Gap Timeout
5 5 5 5 5 0 Governor Enabled
1 1 1 1 1 0 Suspend ABS
0 0 0 0 0 0 -------------------------------------------------------------------------------- Config Exit Help Menu Options Set_rate Write !
In Example 7-7, you can use the Set_rate menu option at the bottom of the display to dynamically modify certain database parameter settings to be higher or lower and immediate see the impact of the change. The following list describes the fields in the Hot Standby Dashboard display and how you can change database attribute settings:
Displays the amount of time, in seconds, after which the Hot Standby network times out. The default is 120 seconds. You can override the default with the BIND_HOT_NETWORK_TIMEOUT logical name or configuration parameter.
Displays the amount of time, in minutes, to wait for the connection to be made between the master and the standby database. The default is 5 minutes. You can override the default with the BIND_LCS_CONNECT_TIMEOUT logical name or configuration parameter.
Displays the current database synchronization mode:
You can override the default value with the BIND_HOT_DATA_SYNC_MODE logical name or configuration parameter.
Displays the number of messages per server checkpoint interval. The default is 100 messages. You can override the default with the BIND_HOT_CHECKPOINT logical name or configuration parameter.
Displays the amount of time, in minutes, to wait for stalled MSN (gap) resolution. The default is 5 minutes. You can override the default value with the BIND_LRS_GAP_TIMEOUT logical name or configuration parameter.
Indicates if the replication governor is enabled or disabled.
You can override the default value with the BIND_LRS_GOVERNOR_ENABLED logical name or configuration parameter.
Indicates if ABS backup operations are suspended.
Remember that the purpose of updating attributes is to test and measure the effects of changes on the database so that you can later make persistent changes to the appropriate database attributes.
Reference: Appendix A describes these logical names and configuration parameters in more detail.
The Monitor Dashboard display shows the actual database parameter settings being used by the database. Just like the Hot Standby Dashboard display, most of the database parameter settings on the Monitor Dashboard display can be dynamically modified temporarily and nonpersistently as a means of experimenting with different values to identify their immediate effect on the overall operation of the database.
Example 7-8 shows an example of the Monitor Dashboard display.
Node: ORANOD Oracle Rdb V7.0-00 Performance Monitor 24-JUL-1996 10:11:32 Rate: 1.00 Second Monitor Dashboard Elapsed: 14:00:57.89 Page: 1 of 1 DISK1:[USER]MF_PERSONNEL.RDB;1 Mode: Online -------------------------------------------------------------------------------- Database.......... Current... Previous.. Lowest.... Highest... Original.. Chng Attribute.Name.... Value..... Value..... Value..... Value..... Value..... Cnt. Max DBR Count 50 50 50 50 50 0 ABS Priority 15 15 15 15 15 0 ALS Priority 8 8 8 8 8 0 DBR Priority 15 15 15 15 15 0 LCS Priority 15 15 15 15 15 0 LRS Priority 15 15 15 15 15 0 RCS Priority 4 4 4 4 4 0 -------------------------------------------------------------------------------- Config Exit Help Menu Options Set_rate Write !
Reference: You can obtain help on the Monitor Dashboard display and its fields using the Help menu option at the bottom of the display.
You can modify the database attributes during run time using the logical names and configuration parameters shown in Table 7-1.
Reference: Appendix A describes these logical names and configuration parameters in more detail.
You can have the Hot Standby software record replication activities being performed by the ALS, LRS, and LCS server processes to an operational output file. Then, you can monitor the replication activities of these replication server processes by examining the appropriate log file.
You can make the Hot Standby software record this information by:
Example 7-9 provides an example of an ALS output file.
-------------------------------------------------------------------------------- 15-AUG-1996 09:52:06.20 - Oracle Rdb V7.0-00 database utility started -------------------------------------------------------------------------------- This is a VAX 6000-630 running VMS V6.2 Current time is 15-AUG-1996 09:52:06.25 15-AUG-1996 06:35:35.97: Linked ALS . . . 14-AUG-1996 20:20:55.80: Compiled ALS . . . 14-AUG-1996 20:20:50.08: Compiled KOD$LIBRARY . . . . . . ================================================================================ Defined Product Logicals Information ================================================================================ . . . 15-AUG-1996 09:52:06.50 - AIJ Log Server (ALS) startup 15-AUG-1996 09:52:07.69 - Updating dashboard information 15-AUG-1996 09:52:07.69 - Fast commit = 01 15-AUG-1996 09:52:07.69 - Commit-to-Journal = 00 15-AUG-1996 09:52:07.69 - Optimized Page Transfer = 00 15-AUG-1996 09:52:07.69 - Opening "_DISK1:[USER.MASTER]AIJ_1.AIJ;1" 15-AUG-1996 09:52:14.82 - Received LCS_STARTUP (1:0) 15-AUG-1996 09:52:25.61 - Received LSS_ACTIVE (1:0) 15-AUG-1996 09:52:25.61 - Changing LSS state from "Active" to "Net Bind" 15-AUG-1996 09:52:25.61 - Remote node: "REMNOD" 15-AUG-1996 09:52:25.61 - Standby database: "DISK1:[USER]STANDBY_PERSONNEL" 15-AUG-1996 09:52:25.61 - Server name: "554424313131245F0C000000380675" 15-AUG-1996 09:52:28.09 - Network protocol is "DECnet" 15-AUG-1996 09:52:28.09 - Sending LSS_ACTIVE (1:1) 15-AUG-1996 09:52:28.10 - Changing LSS_REF_COUNT from 0 to 1 15-AUG-1996 09:52:28.10 - AIJ Log Ship Server (ALS) activated on master database 15-AUG-1996 09:52:28.10 - sending "Attach_Req" message to server 15-AUG-1996 09:52:28.10 - Changing LSS state from "Net Bind" to "Connecting" 15-AUG-1996 09:52:28.10 - Sending "Attach_Req" (MSN 0) LRS reply expected 15-AUG-1996 09:53:10.54 - sending "Ckpt_Req" message to server 15-AUG-1996 09:53:10.55 - Checkpoint taken for inactivity 15-AUG-1996 09:53:10.55 - TROOT #3 AIJ VNO:VBN=6:1 15-AUG-1996 09:53:10.55 - Sending "Ckpt_Req" (MSN 0) LRS reply expected 15-AUG-1996 09:53:10.55 - Reading 49152 message 15-AUG-1996 09:53:10.56 - setting BUF_LEN=512 15-AUG-1996 09:53:10.56 - Received "Ckpt_Ack" reply (MSN 0) 15-AUG-1996 09:53:10.56 - LAG_BLK_CNT=0, AVG_BLK_STALL_MS=0 15-AUG-1996 09:53:10.56 - LAG_TAD= 0 00:00:00.00 15-AUG-1996 09:53:10.56 - Checkpointed at AIJ location 6:2 15-AUG-1996 09:53:10.57 - AIJ switch-over detected on another node 15-AUG-1996 09:53:10.57 - sending "Ckpt_Req" message to server 15-AUG-1996 09:53:10.57 - Checkpoint taken for inactivity 15-AUG-1996 09:53:10.57 - Sending "Ckpt_Req" (MSN 0) LRS reply expected 15-AUG-1996 09:53:10.57 - Reading 49152 message 15-AUG-1996 09:53:10.58 - setting BUF_LEN=512 15-AUG-1996 09:53:10.59 - Received "Ckpt_Ack" reply (MSN 0) 15-AUG-1996 09:53:10.59 - LAG_BLK_CNT=0, AVG_BLK_STALL_MS=0 15-AUG-1996 09:53:10.59 - LAG_TAD= 0 00:00:00.00 15-AUG-1996 09:54:57.13 - LAG_TAD= 0 00:00:00.00 15-AUG-1996 09:54:57.13 - Checkpointed at AIJ location 7:2 15-AUG-1996 09:54:57.13 - Starting inactivity timer 15-AUG-1996 09:55:57.13 - sending "Ckpt_Req" message to server 15-AUG-1996 09:55:57.13 - Checkpoint taken for inactivity 15-AUG-1996 09:55:57.13 - Sending "Ckpt_Req" (MSN 0) LRS reply expected 15-AUG-1996 09:55:57.13 - Reading 49152 message 15-AUG-1996 09:55:57.42 - setting BUF_LEN=512 15-AUG-1996 09:55:57.42 - Received "Ckpt_Ack" reply (MSN 0) 15-AUG-1996 09:55:57.42 - LAG_BLK_CNT=0, AVG_BLK_STALL_MS=0 15-AUG-1996 09:55:57.42 - LAG_TAD= 0 00:00:00.00 15-AUG-1996 09:55:57.42 - Checkpointed at AIJ location 7:2 15-AUG-1996 09:55:57.42 - Starting inactivity timer 15-AUG-1996 09:56:57.42 - sending "Ckpt_Req" message to server 15-AUG-1996 09:56:57.42 - Checkpoint taken for inactivity 15-AUG-1996 09:56:57.42 - Sending "Ckpt_Req" (MSN 0) LRS reply expected 15-AUG-1996 09:56:57.42 - Reading 49152 message 15-AUG-1996 09:57:01.31 - setting BUF_LEN=512 15-AUG-1996 09:57:01.31 - Received "Ckpt_Ack" reply (MSN 0) 15-AUG-1996 10:01:25.36 - setting BUF_LEN=512 15-AUG-1996 10:01:25.36 - New AIJSERVER invocation detected 15-AUG-1996 10:01:25.36 - Received "Attach_Ack" reply (MSN 0) 15-AUG-1996 10:01:25.36 - AIJSERVER PID is 2661D013 15-AUG-1996 10:01:25.36 - Changing LSS state from "Connecting" to "Active" 15-AUG-1996 10:01:25.36 - sending "Ckpt_Req" message to server 15-AUG-1996 10:01:25.36 - Checkpoint taken for inactivity 15-AUG-1996 10:01:25.37 - TROOT #3 AIJ VNO:VBN=8:1 15-AUG-1996 10:01:25.37 - Sending "Ckpt_Req" (MSN 0) LRS reply expected 15-AUG-1996 10:01:25.37 - Reading 49152 message 15-AUG-1996 10:01:25.38 - setting BUF_LEN=512 15-AUG-1996 10:01:25.38 - Received "Ckpt_Ack" reply (MSN 0) 15-AUG-1996 10:01:25.38 - LAG_BLK_CNT=0, AVG_BLK_STALL_MS=0 15-AUG-1996 10:01:25.38 - LAG_TAD= 0 00:00:00.00 15-AUG-1996 10:01:25.38 - Checkpointed at AIJ location 8:2 15-AUG-1996 10:01:25.38 - AIJ switch-over detected on another node 15-AUG-1996 10:01:25.38 - sending "Ckpt_Req" message to server 15-AUG-1996 10:01:25.38 - Checkpoint taken for inactivity 15-AUG-1996 10:01:25.38 - Sending "Ckpt_Req" (MSN 0) LRS reply expected 15-AUG-1996 10:03:00.59 - Received "Ckpt_Ack" reply (MSN 0) 15-AUG-1996 10:03:00.59 - LAG_BLK_CNT=0, AVG_BLK_STALL_MS=0 15-AUG-1996 10:03:00.59 - LAG_TAD= 0 00:00:00.00 15-AUG-1996 10:03:00.59 - Checkpointed at AIJ location 9:2 15-AUG-1996 10:03:25.77 - sending "Ckpt_Req" message to server 15-AUG-1996 10:03:25.77 - Checkpoint taken for inactivity 15-AUG-1996 10:03:25.77 - Sending "Ckpt_Req" (MSN 0) LRS reply expected 15-AUG-1996 10:03:25.77 - Reading 49152 message 15-AUG-1996 10:03:25.78 - setting BUF_LEN=512 15-AUG-1996 10:03:25.78 - Received "Ckpt_Ack" reply (MSN 0) 15-AUG-1996 10:03:25.78 - LAG_BLK_CNT=0, AVG_BLK_STALL_MS=0 15-AUG-1996 10:03:25.78 - LAG_TAD= 0 00:00:00.00 15-AUG-1996 10:03:25.78 - Checkpointed at AIJ location 9:2 15-AUG-1996 10:03:25.78 - Starting inactivity timer 15-AUG-1996 10:04:25.78 - sending "Ckpt_Req" message to server 15-AUG-1996 10:04:25.78 - Checkpoint taken for inactivity 15-AUG-1996 10:04:25.78 - Sending "Ckpt_Req" (MSN 0) LRS reply expected 15-AUG-1996 10:04:25.78 - Reading 49152 message 15-AUG-1996 10:04:25.80 - setting BUF_LEN=512 15-AUG-1996 10:04:25.80 - Received "Ckpt_Ack" reply (MSN 0) 15-AUG-1996 10:04:25.80 - LAG_BLK_CNT=0, AVG_BLK_STALL_MS=0 15-AUG-1996 10:04:25.80 - LAG_TAD= 0 00:00:00.00 15-AUG-1996 10:04:25.80 - Checkpointed at AIJ location 9:2 15-AUG-1996 10:04:25.80 - Starting inactivity timer 15-AUG-1996 10:04:53.66 - Received LCS_STARTUP (0:1) 15-AUG-1996 10:04:53.66 - Received LSS_SHUTDOWN (1:0) 15-AUG-1996 10:04:53.66 - sending "Shutdown_Req" message to server 15-AUG-1996 10:04:53.67 - Sending LSS_ACTIVE (1:0) 15-AUG-1996 10:04:53.67 - Changing LSS_REF_COUNT from 1 to 0 15-AUG-1996 10:04:53.67 - AIJ Log Ship Server (ALS) deactivated for master database 15-AUG-1996 10:04:53.69 - Changing LSS state from "Shutdown" to "Inactive
Example 7-10 provides an example of an LCS output file.
-------------------------------------------------------------------------------- 16-AUG-1996 10:10:51.59 - Oracle Rdb V7.0-00 database utility started -------------------------------------------------------------------------------- This is a VAX 6000-630 running VMS V6.2 Current time is 16-AUG-1996 10:10:51.63 16-AUG-1996 09:19:00.81: Linked LCS . . . 16-AUG-1996 08:46:21.06: Compiled LCS . . . 16-AUG-1996 08:46:14.14: Compiled KOD$LIBRARY . . . . . . ================================================================================ Defined Product Logicals Information ================================================================================ . . . 16-AUG-1996 10:10:51.86 - AIJ Log Catch-Up Server (LCS) activated 16-AUG-1996 10:10:51.86 - Remote node: "REMNOD" 16-AUG-1996 10:10:51.86 - Master DB: "_DISK1:[USER]MF_PERSONNEL.RDB; 16-AUG-1996 10:10:51.86 - StandbyDB: "_DISK1:[USER]STANDBY_PERSONNEL.RDB;1" 16-AUG-1996 10:10:51.86 - Server name: "" 16-AUG-1996 10:10:51.91 - Debug information initialized 16-AUG-1996 10:10:51.93 - Updating dashboard information 16-AUG-1996 10:10:51.94 - Changing LSS state from "Inactive" to "DB Bind" 16-AUG-1996 10:10:51.94 - Fast commit = 01 16-AUG-1996 10:10:51.94 - Commit-to-Journal = 00 16-AUG-1996 10:10:51.94 - Optimized Page Transfer = 00 16-AUG-1996 10:10:51.94 - Changing LSS state from "DB Bind" to "Net Bind" 16-AUG-1996 10:10:51.97 - Opening standby database _DISK1:[USER]STANDBY_PERSONNEL 16-AUG-1996 10:10:51.97 - Starting standby database replication 16-AUG-1996 10:10:55.05 - sending "Bind_Req" message to server 16-AUG-1996 10:10:55.05 - setting network timer to 0 00:02:00.00 16-AUG-1996 10:10:55.08 - "Bind_Req" message complete 16-AUG-1996 10:10:55.09 - Changing LSS state from "Net Bind" to "Connecting" 16-AUG-1996 10:10:55.09 - Sending LCS_ACTIVE (0:1) 16-AUG-1996 10:10:55.09 - Sending LRS_SHUTDOWN (0:0) 16-AUG-1996 10:10:55.09 - Automatically suspended AIJ backup operations 16-AUG-1996 10:10:55.12 - sending "Connect_Req" message to server 16-AUG-1996 10:10:55.12 - AIJDSC[0]: VNO=0 AIJID=0 ALLOC=512 16-AUG-1996 10:10:55.12 - AIJDSC[1]: VNO=1 AIJID=1 ALLOC=512 16-AUG-1996 10:10:55.12 - AIJDSC count=2 16-AUG-1996 10:10:55.12 - AIJFB_CNT=9 16-AUG-1996 10:10:55.14 - ALLOCATION=512, PEOF=512 16-AUG-1996 10:10:55.17 - ALLOCATION=512, PEOF=512 16-AUG-1996 10:10:55.23 - AIJ_SIGNATURE=00000624 FILID_SIGNATURE=000E001C 16-AUG-1996 10:10:55.23 - Sending "Connect_Req" (MSN 0) LRS reply expected 16-AUG-1996 10:10:55.23 - setting network timer to 0 00:02:00.00 16-AUG-1996 10:10:55.95 - Received "Connect_Ack" reply 16-AUG-1996 10:10:55.95 - LRS replied 16-AUG-1996 10:10:55.95 - Master database replication restarts at 1:35 16-AUG-1996 10:10:55.95 - AIJSERVER PID is 00000000 16-AUG-1996 10:10:55.95 - Resuming suspended AIJ backup operations 16-AUG-1996 10:10:55.96 - Changing LSS state from "Connecting" to "DB Synch." 16-AUG-1996 10:10:56.06 - After-image journal 1 switch-over in progress (to 2) 16-AUG-1996 10:10:56.07 - No more after-image journals available 16-AUG-1996 10:10:56.10 - Scanning AIJ sequence 1:35-36 16-AUG-1996 10:10:56.10 - Reading AIJ sequence 1:35-36 16-AUG-1996 10:10:56.13 - sending "Sync_Data" message to server 16-AUG-1996 10:10:56.14 - Sending "Sync_Data" (MSN 6) no reply expected 16-AUG-1996 10:10:56.14 - setting network timer to 0 00:00:05.00 16-AUG-1996 10:10:56.15 - sending "Sync_Req" message to server 16-AUG-1996 10:10:56.15 - SYNC_REQ: VNO=1, VBN=35 16-AUG-1996 10:10:56.15 - Sending "Sync_Req" (MSN 0) LRS reply expected 16-AUG-1996 10:10:56.15 - setting network timer to 0 00:00:05.00 16-AUG-1996 10:10:56.16 - Received "Sync_Ack" reply 16-AUG-1996 10:10:56.16 - LRS replied 16-AUG-1996 10:10:56.16 - sending "Info_Req" message to server 16-AUG-1996 10:10:56.16 - Sending "Info_Req" (MSN 0) LRS reply expected 16-AUG-1996 10:10:56.16 - setting network timer to 0 00:00:05.00 16-AUG-1996 10:10:56.24 - Received "Info_Ack" reply 16-AUG-1996 10:10:56.24 - LRS replied 16-AUG-1996 10:10:56.24 - Verified replicated journal commit TSN 0:384 16-AUG-1996 10:10:56.24 - NUM_ACTIVE_AIJ=2 16-AUG-1996 10:10:56.24 - AIJFB_CNT=9 16-AUG-1996 10:10:56.26 - ALLOCATION=512, PEOF=512 16-AUG-1996 10:10:56.28 - ALLOCATION=512, PEOF=512 16-AUG-1996 10:10:56.28 - AIJ_SIGNATURE=00000624 16-AUG-1996 10:10:56.28 - LAG_BLK_CNT=1, AVG_BLK_STALL_MS=0 16-AUG-1996 10:10:56.28 - LAG_TAD= 0 00:00:00.00 16-AUG-1996 10:10:56.28 - Changing LSS state from "DB Synch." to "Active" 16-AUG-1996 10:10:56.28 - Sending LSS_ACTIVE (0:1) 16-AUG-1996 10:10:56.28 - Sending LSS_REF_COUNT (0:0) 16-AUG-1996 10:12:12.95 - Received LCS_STARTUP (0:1) 16-AUG-1996 10:12:12.96 - Received LSS_SHUTDOWN (1:0) 16-AUG-1996 10:12:12.96 - sending "Shutdown_Req" message to server 16-AUG-1996 10:12:12.96 - Sending "Shutdown_Req" (MSN 0) no reply expected 16-AUG-1996 10:12:12.96 - setting network timer to 0 00:00:05.00 16-AUG-1996 10:12:12.96 - Sending LSS_SHUTDOWN (1:1) 16-AUG-1996 10:12:12.97 - Sending LCS_ACTIVE (1:0) 16-AUG-1996 10:12:12.97 - Disconnecting from tincan
Example 7-11 provides an example of an LRS output file.
-------------------------------------------------------------------------------- 27-JUL-1996 16:09:39.31 - Rdb7 V7.0-00 database utility started -------------------------------------------------------------------------------- This is a VAXstation 3600 Series running VMS V6.2 Current time is 27-JUL-1996 16:09:39.60 27-JUL-1996 15:25:31.60: Linked LRS . . . 27-JUL-1996 06:41:23.11: Compiled LRS . . . 27-JUL-1996 06:41:14.95: Compiled KOD$LIBRARY . . . . . (System and configuration information has been omitted from this example.) . -------------------------------------------------------------------------------- 27-JUL-1996 16:09:40.59 - AIJ Log Roll-Forward Server (LRS) activated 27-JUL-1996 16:10:14.00 - Received "Bind_Req" from 66000A9B 27-JUL-1996 16:10:14.13 - Sending "Bind_Ack" to 66000A9B 27-JUL-1996 16:10:14.33 - Received "Connect_Req" from 66000A9B 27-JUL-1996 16:10:15.05 - Received "Sync_Data" from 66000A9B 27-JUL-1996 16:10:17.75 - Received "Sync_Data" from 66000A9B 27-JUL-1996 16:10:17.76 - Received "Sync_Data" from 66000A9B 27-JUL-1996 16:10:47.15 - Received "Sync_Req" from 66000A9B 27-JUL-1996 16:11:01.64 - Received re-submitted "Sync_Req" from 66000A9B
