Create an Oracle physical backup server

All databases of the Oracle physical backup server, whether physical or logical, must be created as physical backup databases first. Tools used to create backup databases include RMAN, data guard proxy, and Oracle grid control. The operation must be performed on both the master server and slave server. However, no matter how many backup servers you plan to create, the steps on the master database only need to be performed once. Oracle 11g RMAN provides a simple command to create a backup database and back up the database at the same time. To create a physical backup server, perform the following steps on the master server:

Select FORCE_LOGGING from v $ database; IT training institution alter database force logging;

 

Logs are recorded for all modifications, even if some objects that may be set to not record logs are recorded. Configure redo transfer authentication; use the remote login password file. Add the backup server log file to the master server. To enable the redo logs applied to the master server to be applied to the slave server, the logs on the slave server must be as large as the logs on the master server or larger than those on the master server.

alter database add standby logfile '/u...' size 50M;

 

Set initialization parameters on the master server:

DB_NAME = DB_UNIQUE_NAME (this parameter does not change even if the backup server is changed to the master server .) CONTROL_FILES # control file. LOG_ARCHIVE_CONFIG = 'dg _ config = (DG01, DG02) 'LOG_ARCHIVE_DEST_1 = 'location =/u01/oraarch/dg0' ## local archive directory. LOG_ARCHIVE_DEST_2 = 'service = DG01 ASYNC VALID_FOR = (ONLINE_LOGFILE, PRIMARY_ROLE) db_unique_name = DG01 '# sets the transmission type for physical backup servers. REMOTE_LOGIN_PASSWORDFILE = Exclusive LOG_ARCHIVE_DEST_STATE_n success

 

Set the master server to archive logs. The network configuration of the slave database must be configured on the master server and the slave server. Using the Oracle Network Manager on two servers helps with this configuration. (The related content is discussed in chapter 3 ). When configuring the service name, use the "unique_db" name for the backup server. After configuring listeners and services on both servers, verify that the copied password files and directories such as adump, bdump, and flashback have been created. Create a backup database through the network and start the backup database in NOMOUNT mode. On the master server, run the RMAN command and connect with sysdba:

RMAN> connect auxiliary sys/password @ DG02 RMAN> run {allocate channel disk1 type disk; allocate auxiliary channel stby type disk; duplicate target database for standby from active database spfile parameter_value_convert 'dg01 ', 'dg02' set db_unique_name = 'dg02' set db_file_name_convert = '/dg01/', '/DG02/'set log_file_name_convert ='/dg01 /', '/dg02/'set control_files ='/u01/app/oradata/controlfiles/dg02 . Ctl 'set log_archive_max_processes = '5' set fal_client = 'dg02' # FAL (extract archiving logs) client. If the role is switched, it will be used. Set fal_server = 'dg01' set standby_file_management = 'auto' set log_archive_config = 'dg _ config = (dg01, dg02) 'set region = 'service = dg01 ASYNC valid_for = (ONLINE_LOGFILE, PRIMARY_ROLE) db_unique_name = DG01 ';}

 

Go to the master server and switch log files: Start the recovery process on the slave server:

　　SQLPLUS> alter database recover managed standby database using current logfile disconnect;

 

The master server and slave server have been created and should be verified now.