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 appendix describes the Hot Standby logical names and configuration parameters available to manage database replication operations.
Except for the facility prefix, the logical names and configuration parameters are the same regardless of the database or operating system that you use.
Table A-1 shows the prefixes that apply to the logical name or configuration parameter for each database and operating system.
The logical names and configuration parameters described in this appendix are completely compatible with other operating system logical names and configuration parameters that you define for standard database operations.
For Oracle Rdb or Oracle CODASYL DBMS databases running on OpenVMS systems, define the logical names in the LNM$SYSTEM_TABLE logical name table.
For Oracle Rdb databases on Digital UNIX systems, define the configuration parameters in the rdb.conf configuration file.
Also, you can define many of the logical names and configuration parameters using the Database Dashboard facility available with the RMU or DBO Show Statistics command.
|
Note: Oracle Corporation recommends that you define all logical names or configuration parameters before opening the master and standby databases. The logical names or configuration parameters are translated when you open each database, and the values are stored in the Database Dashboard facility (described in Chapter 7). Defining logical names and configuration parameters before opening the database is especially useful in a multiple-database configuration; you can customize each database configuration by dynamically assigning, opening, and then deassigning the logical names or configuration parameters before you open another database. |
Reference: See Chapter 7 for more information about the using the Database Dashboard facility.
Table A-2 provides a listing of the logical names and configuration parameters for Hot Standby configurations, and includes a brief description of each.
| Name | Defines | |
|---|---|---|
|
DBM$BIND_ABS_LOG_FILE |
The location and name of the informational output file for the after-image journal backup server (ABS). The default file extension is .log. |
|
|
DBM$BIND_ABS_PRIORITY |
The base priority at which the ABS process is invoked by the database monitor. Define this logical name on OpenVMS systems only. If you do not define this logical name, the current priority of the database monitor is used. |
|
|
DBM$BIND_AIJ_WORK_FILE |
The directory location of the temporary after-image journal rollforward work files. Define this logical name or configuration parameter for the standby database only. If you do not include a file extension, it defaults to .tmp. See Section 2.11 for more information. |
|
|
DBM$BIND_ALS_OUTPUT_FILE |
The location and name of the informational output file for the AIJ log server (ALS). You can include "_PID" in the output file specification to create a unique file name that includes the process identification (PID). For example:
This creates a unique file name that includes the PID, for example, Alternatively, you can define the location of the output file using the Output qualifier on the Replicate After_Journal Start command. The Output qualifier overrides definitions you make with the logical name or configuration parameter. |
|
|
DBM$BIND_ALS_PRIORITY |
The base priority at which the AIJ log server (ALS) process is invoked by the database monitor. This logical name is applicable to OpenVMS systems only. If you do not define this logical name, the Hot Standby software uses the current priority of the database monitor. |
|
|
DBM$BIND_DBR_LOG_FILE |
The location and name of the database recovery process (DBR) log file. The default file extension is .log. |
|
|
DBM$BIND_DBR_PRIORITY |
The base priority at which the database recovery process (DBR) is invoked by the database monitor. This logical name is applicable to OpenVMS systems only. If you do not define this name, the Hot Standby software uses the current priority of the database monitor. |
|
|
DBM$BIND_DBR_WORK_FILE |
The directory location of the temporary DBR redo work file. If you do not define this logical name or configuration parameter, the default location is the recovery-unit journal directory. If you do not include a file extension, it defaults to .tmp. |
|
|
DBM$BIND_HOT_CHECKPOINT |
How frequently, in terms of processed messages, the Hot Standby software performs a checkpoint operation to update information about the database in the root file. Note the following:
Alternatively, you can specify the Checkpoint qualifier on the Replicate After_Journal Start command. |
|
|
DBM$BIND_HOT_DATA_SYNC_MODE |
The degree to which you want to synchronize committed transactions on the standby database with committed transactions on the master database. Define this logical name or configuration parameter on the master database system only. Valid settings include the following values: |
|
|
|
Value
3 |
Synchronization Mode
Commit |
|
|
Alternatively, you can specify the Synchronization qualifier on the Replicate After_Journal Start command. |
|
|
DBM$BIND_HOT_DECNET_OBJECT |
The name of the DECnet network object for the AIJSERVER process on the remote standby database. Define the DECnet object names as follows:
|
|
|
DBM$BIND_HOT_NETWORK_TIMEOUT |
The maximum number of seconds that replication operations wait for a network transmission between the master and standby databases. You can specify a value from 30 to 1800 seconds (30 minutes) on the master and standby databases. The default timeout interval is 120 seconds. If a network transmission does not occur in the time allowed, replication operations shut down. Note: You can specify a value of 0 seconds to disable the network timeout capability. This results in the replication servers waiting indefinitely for a network transmission to occur. However, Oracle Corporation recommends disabling network timeouts only in a well-controlled database environment. |
|
|
DBM$BIND_HOT_NETWORK_TRANSPORT |
The network transport protocol you want to use to ship after-image journal modifications to the remote database.Valid values are DECNET and TCPIP. Do not use the "/" (for example, TCP/IP) when you define this logical name or configuration parameter. |
|
|
DBM$BIND_HOT_OUTPUT_FILE |
The location and name of the output file that records the replication activities of the AIJSERVER process. You can include "_PID" in the output file specification to create a unique file name that includes the process identification (PID). For example:
This creates a unique file name that includes the PID, for example, |
|
|
DBM$BIND_HOT_SNAP_QUIET_POINT |
Enables or disables quiet-point locks for snapshot transactions on the master database. The valid settings are as follows:
|
|
|
|
Value 0 1 |
Description Disables quiet-point locks for snapshot transactions. Enables quiet-point locks for snapshot transactions. This is the default setting. |
|
|
Note: Quiet-point locks must be enabled (the default setting) on the standby database whenever replication operations are occurring. |
|
|
DBM$BIND_LCS_CONNECT_TIMEOUT |
The number of minutes that the LCS process on the master database waits for a network connection to be made so replication operations can start. The default value is 5 minutes. You can set this logical name or configuration parameter from 1 to 4320 minutes on the master database only. Alternatively, you can specify the Connect_Timeout qualifier on the Replicate After_Journal Start command. |
|
|
DBM$BIND_LCS_OUTPUT_FILE |
The location and name of the log catch-up server (LCS) information output files. You can include "_PID" in the output file specification to create a unique file name that includes the process identification (PID). For example:
This creates a unique file name that includes the PID, for example, Alternatively, you can define the location of the output file using the Output qualifier on the Replicate After_Journal Start command. The Output qualifier overrides definitions you make with the logical name or configuration parameter. |
|
|
DBM$BIND_LCS_PRIORITY |
The base priority at which the log catch-up server (LCS) process is invoked by the database monitor. This logical name is applicable to OpenVMS systems only. If you do not define this name, the Hot Standby software uses the current priority of the database monitor. |
|
|
DBM$BIND_LRS_GAP_TIMEOUT |
The maximum number of minutes (from 1 to 4320) that the standby database waits for a gap in the sequence of messages from the master database to be resolved. The default value is 5 minutes. Specify this logical name or configuration parameter on the standby database only. Alternatively, you can specify the Gap_Timeout qualifier on the Replicate After_Journal Start command. |
|
|
DBM$BIND_LRS_GOVERNOR_ENABLED |
Enables the replication governor that automatically and dynamically chooses the synchronization mode that balances performance and database replication synchronization. The valid settings are as follows: |
|
|
|
Value 0 1 |
Description Disables the replication governor. Enables the replication governor (default). |
|
|
Alternatively, you can specify the Governor=Enabled qualifier on the Replicate After_Journal Start command |
|
|
DBM$BIND_LRS_OUTPUT_FILE |
The location and name of the output file that contains information about the replication activities of the log rollforward server (LRS). You can include "_PID" in the output file specification to create a unique file name that includes the process identification (PID). For example:
This creates a unique file name that includes the PID, for example, Typically, you define this name on the standby database only. However, you can define this name on the master database to specify the LRS output file on the standby database only if replication is not already active on the standby database. Alternatively, you can define the location of the output file using the Output qualifier on the Replicate After_Journal Start command. The Output qualifier overrides definitions you make with the logical name or configuration parameter. |
|
|
DBM$BIND_LRS_PRIORITY |
The base priority at which the log rollforward server (LRS) process is invoked by the database monitor. This logical name is applicable to OpenVMS systems only. If you do not define this name, the Hot Standby software uses the current priority of the database monitor. |
|
