Shulou(Shulou.com)06/01 Report--

Details of the parameters of the main library:

Keep all DB_NAME in the same Data Guard the same

DB_NAME=ora11g # specifies a unique name for a database. Once specified, this parameter will not be changed unless DBA actively changes, so DB_UNIQUE_NAMEDB_UNIQUE_NAME=ora11g_primary # is introduced into Oracle 10g to define the unique name of the database, because the DB_NAME parameter must be the same for the physical database and different for the logical database. Parameter to determine each database of # in the DataGuard configuration, and if this parameter is not defined, the DB_NAME parameter value is used by default. This parameter must be configured differently in dataguard.

LOG_ARCHIVE_CONFIG is used to control sending archive logs to remote locations, receiving remote archive logs, and specifying a unique database name for the Data Guard configuration, with a default value of SEND,RECEIVE,NODG_CONFIG.

When this parameter is set to SEND, sending archive logs to a remote location is activated

When the energy is set to NOSEND, sending archive logs to a remote location is prohibited.

When this parameter is set to RECEIVE, receiving remote archive logs is activated.

When this parameter is set to NORECEIVE, remote archive logs are prohibited.

When you set this parameter to DG_CONFIG, you can specify up to 9 unique database names

When this parameter is set to NODG_CONFIG, the assignment of a unique database name is prohibited.

LOG_ARCHIVE_CONFIG='DG_CONFIG= (ora11g_primary, ora11g_standby)'# defines a list of valid DB_UNIQUE_NAME parameters for DataGuard configuration. No name order requires LOG_ARCHIVE_DEST_1='LOCATION=/u01/app/oracle/archive VALID_FOR= (ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=ora11g_primary' # to specify the path to the local archive LOG_ARCHIVE_DEST_2='SERVICE=ora11g_standby LGWR ASYNC VALID_FOR= (ONLINE_LOGFILES) PRIMARY_ROLE) DB_UNIQUE_NAME=ora11g_standby'# specifies the archive path of the remote standby library

LOG_ARCHIVE_DEST_n (from 1 to 10) defines the path to the redo file. This parameter must specify the archive file path through location or service. Location represents the local path, and service is usually net service name, the standby database that receives redo data. Net service name refers to the name configured in tnsnames.ora.

Note: each LOG_ARCHIVE_DEST_n has a corresponding LOG_ARCHIVE_DEST_STATE_n parameter, which has the following four attribute values:

ENABLE: default value, which means that the transport service is allowed

DEFER: specify a valid log_archive_dest_n parameter, but do not use it for the time being

ALTERNATE: transmission is disabled, but if all other related destinations fail to connect, it will become enable

RESET: the function is similar to DEFER, but if there is an error before the transfer destination, it clears all error messages

LOG_ARCHIVE_DEST_STATE_1=ENABLELOG_ARCHIVE_DEST_STATE_2=ENABLE

REMOTE_LOGIN_PASSWORDFILE=EXCLUSIVE # set exclusive mode for remote login (make sure that the passwords of master and slave libraries are the same) LOG_ARCHIVE_FORMAT=%t_%s_%r.arc

Archive Gap occurs when some logs of Primary Database are not sent to Standby Database. The missing log is GAP. Data Guard can automatically detect and solve filing cracks without the intervention of DBA. This requires configuring the two parameters FAL_CLIENT,FAL_SERVER (FAL:Fetch Archive Log). As can be seen from the name FAL, this process is initiated by Standby Database to fetch logs. Standby Database is FAL_CLIENT, which fetches these GAP from FAL_SERVER. In 10g, the FAL_SERVER can be Primary Database, or the other Standby Database FAL_CLIENT and FAL_SERVER parameters are both Oracle Net Name FAL_CLIENT to send requests to FAL_SERVER over the network, and FAL_SERVER to send missing logs to FAL_CLIENT over the network, but these two connections are not necessarily a connection. So when FAL_CLIENT sends a request to FAL_SERVER, it carries the parameter value of FAL_CLIENT to tell FAL_SERVER where to send the missing log. This parameter is also an Oracle Net Name, which Name is defined on FAL_SERVER and is used to point to FAL_CLIENT.

Master database settings: FAL_SERVER=ora11g_standbyFAL_CLIENT=ora11g_primary slave database settings FAL_SERVER=ora11g_primaryFAL_CLIENT=ora11g_standby

If the Primary database data file is modified (such as new), then make the corresponding modification in the standby database

Set to AUTO to indicate automatic management. Set it to MANUAL to indicate manual management (note: rename modification

Will not be transferred to the standby database)

STANDBY_FILE_MANAGEMENT=AUTO

Main library parameters

DB_NAME=ora11gDB_UNIQUE_NAME=ora11g_primaryLOG_ARCHIVE_CONFIG='DG_CONFIG= (ora11g_primary, ora11g_standby) 'LOG_ARCHIVE_DEST_1='LOCATION=/u01/app/oracle/archive VALID_FOR= (ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=ora11g_primary'LOG_ARCHIVE_DEST_2='SERVICE=ora11g_standby LGWR ASYNC VALID_FOR= (ONLINE_LOGFILES) PRIMARY_ROLE) DB_UNIQUE_NAME=ora11g_standby'LOG_ARCHIVE_DEST_STATE_1=ENABLELOG_ARCHIVE_DEST_STATE_2=ENABLEREMOTE_LOGIN_PASSWORDFILE=EXCLUSIVELOG_ARCHIVE_FORMAT=%t_%s_%r.arcFAL_SERVER=ora11g_standbyFAL_CLIENT=ora11g_primarySTANDBY_FILE_MANAGEMENT=AUTO

Reserve database parameters

DB_NAME=ora11gDB_UNIQUE_NAME=ora11g_standby LOG_ARCHIVE_CONFIG='DG_CONFIG= (ora11g_primary, ora11g_standby) 'LOG_ARCHIVE_DEST_1='LOCATION=/u01/app/oracle/archive VALID_FOR= (ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=ora11g_standby'LOG_ARCHIVE_DEST_2='SERVICE=ora_primary LGWR ASYNC VALID_FOR= (ONLINE_LOGFILES) PRIMARY_ROLE) DB_UNIQUE_NAME=ora11g_primary'LOG_ARCHIVE_DEST_STATE_1=ENABLELOG_ARCHIVE_DEST_STATE_2=ENABLEREMOTE_LOGIN_PASSWORDFILE=EXCLUSIVELOG_ARCHIVE_FORMAT=%t_%s_%r.arcFAL_SERVER=ora11g_primaryFAL_CLIENT=ora11g_standbySTANDBY_FILE_MANAGEMENT=AUTO

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.