Rman configuration DataGuard uses the main library to back up with filesystem when not configured 01/18 Update SLTechnology News&Howtos

Rman configuration DataGuard uses the main library to back up with filesystem when not configured

2025-01-18 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Database >

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

I. Environment

Hostnam

Database version

Dbname

Db_unique_name

IP address

System version

Jason1 (Master)

Oracle11204

Jason

Jason1

192.168.1.99

Rhel6.6_x86_64

Jason2 (standby)

Jason2

192.168.1.100

Second, the main library configuration 1. Make sure that the master database turns on the mandatory LOGGING mode

[oracle@jason1 ~] $sqlplus / nolog

SQL*Plus: Release 11.2.0.4.0 Production on Thu Jul 14 20:45:33 2016

SQL > conn / as sysdba

Connected.

SQL > ALTER DATABASE FORCE LOGGING

Database altered.

SQL > select force_logging from v$database

FOR

YES

two。 Open archiving

SQL > archive log list

Database log mode Archive Mode

Automatic archival Enabled

Archive destination USE_DB_RECOVERY_FILE_DEST

Oldest online log sequence 3

Next log sequence to archive 5

Current log sequence 5

SQL > select group#,bytes/1024/1024 from v$log

GROUP# BYTES/1024/1024

1 50

3 50

2 50

3. Back up the main library

Create a backup directory and back up the main library using the following script.

Mkdir / data

Chown oracle:oinstall / data

Run

{

Backup database include current controlfile

Format'/ data/fulldb_%U.bak'

Plus archivelog

Format'/ data/arch_%U.bak'

}

After the backup ends, manually switch to generate archive logs, simulate the amount of archives for a day, and then start to configure the DG parameters of the main database.

4. Create a standby log group

1). The file size of standby redo log is the same as the online redo log file size of primary database

2). The number of standby redo log log filegroups is calculated according to the following principles

Standby redo log group number formula > = (number of instance log groups + 1) * number of instance

For example, in my environment, there is only one node, and this node has three sets of redo, so

Standby redo log group number formula > = (3x 1) * 1 = = 4

So you need to create 4 groups of Standby redo log

3)。 For security reasons, each log group can contain multiple member files.

Check the number and size of log groups in the master database, and create standy log groups, which cannot be smaller than the online log size.

SQL > select member from v$logfile

MEMBER

/ u01/app/oracle/oradata/JASON/redo03.log

/ u01/app/oracle/oradata/JASON/redo02.log

/ u01/app/oracle/oradata/JASON/redo01.log

Create a standby log group in the primary database in the same path as the original log group.

SQL > ALTER DATABASE ADD STANDBY LOGFILE ('/ u01ax SIZE SIZE 50m)

Database altered.

SQL > ALTER DATABASE ADD STANDBY LOGFILE ('/ u01ax SIZE SIZE 50m)

Database altered.

SQL > ALTER DATABASE ADD STANDBY LOGFILE ('/ u01ax SIZE SIZE 50m)

Database altered.

SQL > ALTER DATABASE ADD STANDBY LOGFILE ('/ u01ax SIZE SIZE 50m)

Database altered.

SQL > select group#,status,type,member from v$logfile

GROUP# STATUS TYPE MEMBER

3 ONLINE / u01/app/oracle/oradata/JASON/redo03.log

2 ONLINE / u01/app/oracle/oradata/JASON/redo02.log

1 ONLINE / u01/app/oracle/oradata/JASON/redo01.log

4 STANDBY / u01/app/oracle/oradata/JASON/standby01.log

5 STANDBY/u01/app/oracle/oradata/JASON/standby02.log

6 STANDBY/u01/app/oracle/oradata/JASON/standby03.log

7 STANDBY/u01/app/oracle/oradata/JASON/standby04.log

7 rows selected.

5. Main library parameter file configuration

Modify the parameters related to the dataguard configuration on the main library. The specific meaning of each parameter can be found in the oracle online documentation.

SQL > alter system set LOG_ARCHIVE_CONFIG='DG_CONFIG= (JASON1,JASON2) 'SCOPE=SPFILE

System altered.

SQL > alter system set DB_UNIQUE_NAME='JASON1' SCOPE=SPFILE

System altered.

SQL > alter system set STANDBY_FILE_MANAGEMENT='AUTO' SCOPE=SPFILE

System altered.

SQL > alter system setLOG_ARCHIVE_DEST_1='LOCATION=/u01/app/oracle/archivelog/VALID_FOR= (ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=JASON1' scope=spfile

System altered.

SQL > alter system set LOG_ARCHIVE_DEST_2='SERVICE=JASON2 ASYNCVALID_FOR= (ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=JASON2' scope=spfile

System altered.

SQL > alter system set LOG_ARCHIVE_DEST_STATE_1='ENABLE' scope=spfile

System altered.

SQL > alter system set LOG_ARCHIVE_DEST_STATE_2='ENABLE' scope=spfile

System altered.

SQL > alter system setLOG_FILE_NAME_CONVERT='/ u01 scope=spfile alter system setLOG_FILE_NAME_CONVERT='/ U01 scope=spfile

System altered.

SQL > alter system set FAL_SERVER='JASON2' scope=spfile

System altered.

SQL > shutdown immediate

Database closed.

Database dismounted.

ORACLE instance shut down.

SQL > startup

ORACLE instance started.

Total System Global Area 409194496 bytes

Fixed Size 2253744 bytes

Variable Size 310381648 bytes

Database Buffers 92274688 bytes

Redo Buffers 4284416 bytes

Database mounted.

Database opened.

6. Configure snooping and tnsname

Create listeners and tnsname.ora. You must use static snooping, as follows:

[oracle@jason1 admin] $cat listener.ora

# listener.ora Network Configuration File:/u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora

# Generated by Oracle configuration tools.

SID_LIST_LISTENER =

(SID_LIST =

(SID_DESC =

(GLOBAL_DBNAME = JASON1)

(ORACLE_HOME = / u01/app/oracle/product/11.2.0/dbhome_1)

(SID_NAME = JASON)

)

LISTENER =

(DESCRIPTION =

(ADDRESS = (PROTOCOL = TCP) (HOST = 192.168.1.99) (PORT = 1521))

)

ADR_BASE_LISTENER = / u01/app/oracle

[oracle@jason1 admin] $cat tnsnames.ora

# tnsnames.ora Network Configuration File:/u01/app/oracle/product/11.2.0/dbhome_1/network/admin/tnsnames.ora

# Generated by Oracle configuration tools.

JASON1 =

(DESCRIPTION =

(ADDRESS = (PROTOCOL = TCP) (HOST = 192.168.1.99) (PORT = 1521))

(CONNECT_DATA =

(SERVER = DEDICATED)

(SERVICE_NAME = JASON1)

)

JASON2 =

(DESCRIPTION =

(ADDRESS = (PROTOCOL = TCP) (HOST = 192.168.1.100) (PORT = 1521))

(CONNECT_DATA =

(SERVER = DEDICATED)

(SERVICE_NAME = JASON2)

)

[oracle@jason1 admin] $lsnrctl status

LSNRCTL for Linux: Version 11.2.0.4.0-Production on 20-JUL-201623:06:17

Connecting to (DESCRIPTION= (ADDRESS= (PROTOCOL=TCP) (HOST=jason1) (PORT=1521)

STATUS of the LISTENER

Alias LISTENER

Version TNSLSNRfor Linux: Version 11.2.0.4.0-Production

Start Date 20-JUL-2016 22:50:04

Uptime 0 days 0hr. 16 min. 13 sec

Trace Level off

Security ON:Local OS Authentication

SNMP OFF

Listener Parameter File / u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora

Listener Log File / u01/app/oracle/diag/tnslsnr/jason1/listener/alert/log.xml

Listening Endpoints Summary...

(DESCRIPTION= (ADDRESS= (PROTOCOL=tcp) (HOST=jason1) (PORT=1521))

Services Summary...

Service "JASON1" has 2 instance (s).

Instance "JASON", status UNKNOWN, has 1 handler (s) for this service...

Instance "JASON", status READY, has 1 handler (s) for this service...

Service "JASONXDB" has 1 instance (s).

Instance "JASON", status READY, has 1 handler (s) for this service...

The command completed successfully

[oracle@jason1 admin] $

7. Generate pfile files and synchronize the corresponding files to the standby library

Generate a pfile file in the main database.

SQL > create pfile from spfile

File created.

Synchronize the content under dbs to the standby host

[oracle@jason1 dbs] $pwd

/ u01/app/oracle/product/11.2.0/dbhome_1/dbs

[oracle@jason1 dbs] $scp initJASON.ora orapwJASON192.168.1.100:/u01/app/oracle/product/11.2.0/dbhome_1/dbs/

The authenticity of host '192.168.1.100 (192.168.1.100)' can't beestablished.

RSA key fingerprint is 25:ca:65:90:d3:30:fa:68:ed:11:64:b2:0e:b0:39:a7.

Are you sure you want to continue connecting (yes/no)? Yes

Warning: Permanently added '192.168.1.100' (RSA) to the list of knownhosts.

Oracle@192.168.1.100's password:

InitJASON.ora 100% 1415 1.4KB/s 00:00

OrapwJASON 100% 1536 1.5KB/s 00:00

[oracle@jason1 dbs]

Third, prepare the library configuration 8. Create a corresponding directory

Create a related directory on the standby library

[oracle@jason2 oracle] $mkdir-p / u01/app/oracle/admin/JASON/adump

[oracle@jason2 oracle] $mkdir-p / u01/app/oracle/admin/JASON/dpdump

[oracle@jason2 oracle] $mkdir-p / u01/app/oracle/admin/JASON/pfile

[oracle@jason2 oracle] $mkdir-p / u01/app/oracle/archivelog

[oracle@jason2 oracle] $mkdir-p / u01/app/oracle/oradata/JASON

[oracle@jason2 oracle] $mkdir-p / u01/app/oracle/fast_recovery_area

[oracle@jason2 oracle] $mkdir-p / u01/app/oracle/cfgtoollogs/catbundle

[oracle@jason2 oracle] $mkdir-p / u01/app/oracle/cfgtoollogs/dbca/JASON

[oracle@jason2 oracle] $mkdir-p / u01/app/oracle/cfgtoollogs/emca

[oracle@jason2 oracle] $mkdir-p / u01/app/oracle/cfgtoollogs/netca

[oracle@jason2 oracle] $ll

Total 32

Drwxr-xr-x 3 oracle oinstall 4096Jul 14 22:27 admin

Drwxr-xr-x 2 oracle oinstall 4096Jul 14 22:28 archivelog

Drwxr-xr-x 6 oracle oinstall 4096Jul 14 22:32 cfgtoollogs

Drwxr-xr-x 2 oracle oinstall 4096Jul 13 23:32 checkpoints

Drwxrwxr-x 11 oracle oinstall 4096 Jul 13 23:06 diag

Drwxr-xr-x 2 oracle oinstall 4096Jul 14 22:30 fast_recovery_area

Drwxr-xr-x 3 oracle oinstall 4096Jul 14 22:28 oradata

Drwxr-xr-x 3 oracle oinstall 4096Jul 13 21:37 product

[oracle@jason2 oracle] $

9. Copy database backup

[oracle@jason2 oracle] # mkdir / data

[oracle@jason2 oracle] # chownoracle:oinstall / data

Copy the database backup to the standby on the node jason1.

[oracle@jason1 data] $scp * 192.168.1.100:/data

Oracle@192.168.1.100's password:

Arch_01rbevvh_1_1.bak 100% 96MB 23.9MB/s 00:04

Arch_04rbf01l_1_1.bak 100% 31KB 31.0KB/s 00:00

Fulldb_02rbevvp_1_1.bak 100% 1035MB 16.4MB/s 01:03

Fulldb_03rbf01i_1_1.bak 100%9600KB 9.4MB/s 00:00

[oracle@jason1 data] $

10. Prepare the library parameter file configuration

Modify the initial parameter file on the standby library, and the parameters required to configure DG are as follows.

JASON.__db_cache_size=75497472

JASON.__java_pool_size=4194304

JASON.__large_pool_size=71303168

JASON.__oracle_base='/u01/app/oracle'#ORACLE_BASE set from environment

JASON.__pga_aggregate_target=155189248

JASON.__sga_target=255852544

JASON.__shared_io_pool_size=0

JASON.__shared_pool_size=96468992

JASON.__streams_pool_size=0

* .audit_file_dest='/u01/app/oracle/admin/JASON/adump'

* .audit_trail='db'

* .compatible='11.2.0.4.0'

* .control_files='/u01/app/oracle/oradata/JASON/control01.ctl','/u01/app/oracle/oradata/JASON/control02.ctl','/u01/app/oracle/oradata/JASON/control03.ctl'

* .db_block_size=8192

* .db_domain=''

* .db_name='JASON'

* .db_recovery_file_dest_size=4385144832

* .db_recovery_file_dest='/u01/app/oracle/fast_recovery_area'

* .log_file_name_convert='/u01/app/oracle/oradata/JASON','/u01/app/oracle/oradata/JASON'

* .db_unique_name='JASON2'

* .diagnostic_dest='/u01/app/oracle'

* .dispatchers=' (PROTOCOL=TCP) (SERVICE=JASONXDB)'

* .fal_server='JASON1'

* .log_archive_config='DG_CONFIG= (JASON1,JASON2)'

* .log_archive_dest_1='LOCATION=/u01/app/oracle/archivelog/VALID_FOR= (ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=JASON2'

* .log_archive_dest_2='SERVICE=JASON1 ASYNCVALID_FOR= (ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=JASON1'

* .log_archive_dest_state_1='ENABLE'

* .log_archive_dest_state_2='ENABLE'

* .log_archive_format='%t_%s_%r.dbf'

* .memory_target=411041792

* .open_cursors=300

* .processes=150

* .remote_login_passwordfile='EXCLUSIVE'

* .standby_file_management='AUTO'

* .undo_tablespace='UNDOTBS1

11. Configure snooping

Standby listening must be set to static snooping

[oracle@jason2 admin] $cat listener.ora

# listener.ora Network Configuration File:/u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora

# Generated by Oracle configuration tools.

SID_LIST_LISTENER =

(SID_LIST =

(SID_DESC =

(GLOBAL_DBNAME = JASON2)

(ORACLE_HOME = / u01/app/oracle/product/11.2.0/dbhome_1)

(SID_NAME = JASON)

)

LISTENER =

(DESCRIPTION =

(ADDRESS = (PROTOCOL = TCP) (HOST = 192.168.1.100) (PORT = 1521))

)

ADR_BASE_LISTENER = / u01/app/oracle

[oracle@jason2 admin] $cat tnsnames.ora

# tnsnames.ora Network Configuration File:/u01/app/oracle/product/11.2.0/dbhome_1/network/admin/tnsnames.ora

# Generated by Oracle configuration tools.

JASON1 =

(DESCRIPTION =

(ADDRESS = (PROTOCOL = TCP) (HOST = 192.168.1.99) (PORT = 1521))

(CONNECT_DATA =

(SERVER = DEDICATED)

(SERVICE_NAME = JASON1)

)

JASON2 =

(DESCRIPTION =

(ADDRESS = (PROTOCOL = TCP) (HOST = 192.168.1.100) (PORT = 1521))

(CONNECT_DATA =

(SERVER = DEDICATED)

(SERVICE_NAME = JASON2)

)

twelve。 Create a spfile file

[oracle@jason2 dbs] $sqlplus / nolog

SQL*Plus: Release 11.2.0.4.0 Production on Thu Jul 14 23:07:22 2016

SQL > conn / as sysdba

Connected to an idle instance.

SQL > startup nomount

ORACLE instance started.

Total System Global Area 409194496 bytes

Fixed Size 2253744 bytes

Variable Size 310381648 bytes

Database Buffers 92274688bytes

Redo Buffers 4284416 bytes

SQL > create spfile from pfile

File created.

13. Create a standby library

Start the slave database to the nomount state, and then connect to the master library on the slave for duplicate operation.

SQL > shutdown immediate

ORA-01507: database not mounted

ORACLE instance shut down.

SQL > startup nomount

ORACLE instance started.

Total System Global Area 409194496 bytes

Fixed Size 2253744 bytes

Variable Size 310381648 bytes

Database Buffers 92274688 bytes

Redo Buffers 4284416 bytes

SQL > exit

Disconnected from Oracle Database 11g Enterprise Edition Release11.2.0.4.0-64bit Production

With the Partitioning, OLAP, Data Mining and Real Application Testingoptions

[oracle@jason2 ~] $lsnrctl status

LSNRCTL for Linux: Version 11.2.0.4.0-Production on 20-JUL-2016 23:04:56

Connecting to (DESCRIPTION= (ADDRESS= (PROTOCOL=TCP) (HOST=jason2) (PORT=1521)

STATUS of the LISTENER

Alias LISTENER

Version TNSLSNRfor Linux: Version 11.2.0.4.0-Production

Start Date 20-JUL-2016 22:50:42

Uptime 0 days 0hr. 14 min. 14 sec

Trace Level off

Security ON:Local OS Authentication

SNMP OFF

Listener Parameter File / u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora

Listener Log File / u01/app/oracle/diag/tnslsnr/jason2/listener/alert/log.xml

Listening Endpoints Summary...

(DESCRIPTION= (ADDRESS= (PROTOCOL=tcp) (HOST=jason2) (PORT=1521))

Services Summary...

Service "JASON2" has 2 instance (s).

Instance "JASON", status UNKNOWN, has 1 handler (s) for this service...

Instance "JASON", status BLOCKED, has 1 handler (s) for this service...

The command completed successfully

[oracle@jason2 ~] $rman target sys/system@JASON1 auxiliarysys/system@JASON2

Recovery Manager: Release 11.2.0.4.0-Production on Sat Jul 23 23 Production on Sat Jul 13 purl 192016

Connected to target database: JASON (DBID=2141348976)

Connected to auxiliary database: JASON (not mounted)

RMAN > duplicate target database for standby nofilenamecheck

Starting Duplicate Db at 23-JUL-16

Using target database control file instead of recovery catalog

Allocated channel: ORA_AUX_DISK_1

Channel ORA_AUX_DISK_1: SID=18 device type=DISK

Contents of Memory Script:

{

Restore clone standbycontrolfile

}

Executing Memory Script

Starting restore at 23-JUL-16

Using channel ORA_AUX_DISK_1

Channel ORA_AUX_DISK_1: starting datafile backup set restore

Channel ORA_AUX_DISK_1: restoring control file

Channel ORA_AUX_DISK_1: reading from backup piece/data/fulldb_03rbf01i_1_1.bak

Channel ORA_AUX_DISK_1: piece handle=/data/fulldb_03rbf01i_1_1.baktag=TAG20160723T224513

Channel ORA_AUX_DISK_1: restored backup piece 1

Channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:03

Output file name=/u01/app/oracle/oradata/JASON/control01.ctl

Output file name=/u01/app/oracle/oradata/JASON/control02.ctl

Output file name=/u01/app/oracle/oradata/JASON/control03.ctl

Finished restore at 23-JUL-16

Contents of Memory Script:

{

Sql clone 'alter database mountstandby database'

}

Executing Memory Script

Sql statement: alter database mount standby database

Contents of Memory Script:

{

Set newname for tempfile 1 to

"/ u01/app/oracle/oradata/JASON/temp01.dbf"

Switch clone tempfile all

Set newname for datafile 1 to

"/ u01/app/oracle/oradata/JASON/system01.dbf"

Set newname for datafile 2 to

"/ u01/app/oracle/oradata/JASON/sysaux01.dbf"

Set newname for datafile 3 to

"/ u01/app/oracle/oradata/JASON/undotbs01.dbf"

Set newname for datafile 4 to

"/ u01/app/oracle/oradata/JASON/users01.dbf"

Restore

Clone database

}

Executing Memory Script

Executing command: SET NEWNAME

Renamed tempfile 1 to / u01/app/oracle/oradata/JASON/temp01.dbf incontrol file

Executing command: SET NEWNAME

Starting restore at 23-JUL-16

Using channel ORA_AUX_DISK_1

Channel ORA_AUX_DISK_1: starting datafile backup set restore

Channel ORA_AUX_DISK_1: specifying datafile (s) to restore from backupset

Channel ORA_AUX_DISK_1: restoring datafile 00001 to/u01/app/oracle/oradata/JASON/system01.dbf

Channel ORA_AUX_DISK_1: restoring datafile 00002 to/u01/app/oracle/oradata/JASON/sysaux01.dbf

Channel ORA_AUX_DISK_1: restoring datafile 00003 to/u01/app/oracle/oradata/JASON/undotbs01.dbf

Channel ORA_AUX_DISK_1: restoring datafile 00004 to/u01/app/oracle/oradata/JASON/users01.dbf

Channel ORA_AUX_DISK_1: reading from backup piece/data/fulldb_02rbevvp_1_1.bak

Channel ORA_AUX_DISK_1: piece handle=/data/fulldb_02rbevvp_1_1.baktag=TAG20160723T224513

Channel ORA_AUX_DISK_1: restored backup piece 1

Channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:58

Finished restore at 23-JUL-16

Contents of Memory Script:

{

Switch clone datafile all

}

Executing Memory Script

Datafile 1 switched to datafile copy

Input datafile copy RECID=1 STAMP=917998157 filename=/u01/app/oracle/oradata/JASON/system01.dbf

Datafile 2 switched to datafile copy

Input datafile copy RECID=2 STAMP=917998157 filename=/u01/app/oracle/oradata/JASON/sysaux01.dbf

Datafile 3 switched to datafile copy

Input datafile copy RECID=3 STAMP=917998157 filename=/u01/app/oracle/oradata/JASON/undotbs01.dbf

Datafile 4 switched to datafile copy

Input datafile copy RECID=4 STAMP=917998157 filename=/u01/app/oracle/oradata/JASON/users01.dbf

Finished Duplicate Db at 23-JUL-16

RMAN > exit

Recovery Manager complete.

[oracle@jason2 ~] $

14. Create a standby log group

Check the number and size of log groups in the master database, and create standy log groups, which cannot be smaller than the online log size.

SQL > select member from v$logfile

MEMBER

/ u01/app/oracle/oradata/JASON/redo03.log

/ u01/app/oracle/oradata/JASON/redo02.log

/ u01/app/oracle/oradata/JASON/redo01.log

Create a standby log group in the slave database in the same path as the original log group.

SQL > ALTER DATABASE ADD STANDBY LOGFILE ('/ u01ax SIZE SIZE 50m)

Database altered.

SQL > ALTER DATABASE ADD STANDBY LOGFILE ('/ u01ax SIZE SIZE 50m)

Database altered.

SQL > ALTER DATABASE ADD STANDBY LOGFILE ('/ u01ax SIZE SIZE 50m)

Database altered.

SQL > ALTER DATABASE ADD STANDBY LOGFILE ('/ u01ax SIZE SIZE 50m)

Database altered.

SQL >

Note: after the slave database is created, the database is in mount state. To create a standby database using an unconfigured master database, you need to create a standby log group and open the database. When opened, temporary tablespaces, online logs, standby logs will be initialized, and undelivered logs will be received.

15. Turn on ADG

Put the slave in active dataguard mode, and when the database open, all archive logs generated since backup will be sent to the slave.

[oracle@jason2 ~] $sqlplus / nolog

SQL*Plus: Release 11.2.0.4.0 Production on Thu Jul 14 23:42:40 2016

SQL > conn / as sysdba

Connected.

SQL > alter database open

Database altered.

SQL > alter database recover managed standby database using currentlogfile disconnect from session

Database altered.

SQL > select open_mode,database_role,db_unique_name from v$database

OPEN_MODE DATABASE_ROLE DB_UNIQUE_NAME

READ ONLY WITH APPLY PHYSICAL STANDBY JASON2

SQL > select protection_mode,protection_level from v$database

PROTECTION_MODE PROTECTION_LEVEL

MAXIMUMPERFORMANCE MAXIMUMPERFORMANCE

SQL > select status from v$standby_log

STATUS

ACTIVE

UNASSIGNED

SQL > select group#,status,type,member from v$logfile

GROUP# STATUS TYPE MEMBER

3 ONLINE / u01/app/oracle/oradata/JASON/redo03.log

2 ONLINE / u01/app/oracle/oradata/JASON/redo02.log

1 ONLINE / u01/app/oracle/oradata/JASON/redo01.log

4 STANDBY/u01/app/oracle/oradata/JASON/standby01.log

5 STANDBY/u01/app/oracle/oradata/JASON/standby02.log

6 STANDBY / u01/app/oracle/oradata/JASON/standby03.log

7 STANDBY/u01/app/oracle/oradata/JASON/standby04.log

7 rows selected.

SQL >

View the database data file as follows:

[root@jason2 JASON] # ll

Total 1744852

-rw-r- 1 oracle oinstall 9748480 Jul 21 00:11 control01.ctl

-rw-r- 1 oracle oinstall 9748480 Jul 21 00:11 control02.ctl

-rw-r- 1 oracle oinstall 9748480 Jul 21 00:11 control03.ctl

-rw-r- 1 oracle oinstall 52429312 Jul 21 00:06 redo01.log

-rw-r- 1 oracle oinstall 52429312 Jul 21 00:06 redo02.log

-rw-r- 1 oracle oinstall 52429312 Jul 21 00:06 redo03.log

-rw-r- 1 oracle oinstall 52429312 Jul 21 00:11 standby01.log

-rw-r- 1 oracle oinstall 52429312 Jul 21 00:09 standby02.log

-rw-r- 1 oracle oinstall 52429312 Jul 21 00:07 standby03.log

-rw-r- 1 oracle oinstall 52429312 Jul 21 00:07 standby04.log

-rw-r- 1 oracle oinstall 534781952 Jul 21 00:09 sysaux01.dbf

-rw-r- 1 oracle oinstall 775954432 Jul 21 00:09 system01.dbf

-rw-r- 1 oracle oinstall 30416896 Jul 21 00:09 temp01.dbf

-rw-r- 1 oracle oinstall 73408512 Jul 21 00:09 undotbs01.dbf

-rw-r- 1 oracle oinstall 5251072 Jul 21 00:09 users01.dbf

[root@jason2 JASON] #

Main database view database status

SQL > select open_mode,database_role,db_unique_name from v$database

OPEN_MODE DATABASE_ROLE DB_UNIQUE_NAME

READ WRITE PRIMARY JASON1

SQL > select protection_mode,protection_level from v$database

PROTECTION_MODE PROTECTION_LEVEL

MAXIMUMPERFORMANCE MAXIMUMPERFORMANCE

4. Testing 16.switch_over testing

Main library switch

SQL > SELECT SWITCHOVER_STATUS FROM V$DATABASE

SWITCHOVER_STATUS

TO STANDBY

SQL > ALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL STANDBYWITH SESSION SHUTDOWN

Database altered.

SQL > SELECT SWITCHOVER_STATUS FROM V$DATABASE

SELECT SWITCHOVER_STATUS FROM V$DATABASE

ERROR at line 1:

ORA-01034: ORACLE not available

Process ID: 2849

Session ID: 44 Serial number: 27

SQL > startup

ORACLE instance started.

Total System Global Area 409194496 bytes

Fixed Size 2253744 bytes

Variable Size 322964560 bytes

Database Buffers 79691776 bytes

Redo Buffers 4284416 bytes

Database mounted.

Database opened.

SQL > select open_mode,database_role,db_unique_name fromv$database

OPEN_MODE DATABASE_ROLE DB_UNIQUE_NAME

READ ONLY PHYSICAL STANDBY JASON1

SQL > ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USINGCURRENT LOGFILE DISCONNECT FROM SESSION

Database altered.

SQL >

Reserve database switch

SQL > SELECT SWITCHOVER_STATUS FROM V$DATABASE

SWITCHOVER_STATUS

TO PRIMARY

SQL > ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY WITHSESSION SHUTDOWN

Database altered.

SQL > select open_mode,database_role,db_unique_name fromv$database

OPEN_MODE DATABASE_ROLE DB_UNIQUE_NAME

MOUNTED PRIMARY JASON2

SQL > alter database open

Database altered.

SQL > select open_mode,database_role,db_unique_name fromv$database

OPEN_MODE DATABASE_ROLE DB_UNIQUE_NAME

READ WRITE PRIMARY JASON2

SQL >

Fifth, error processing 17. Error

On the slave server, add static registration information to the $GRID_HOME/network/listener.ora file

This is mainly because when the AUXILIARY instance starts to nomount state, listener cannot register the AUXILIARY instance, and listener will mark the Auxiliary instance as' blocked' status, so the duplicate command cannot connect to the Auxiliary instance through TNS. In order to solve this problem, you need to manually statically register the database instance to the listener. When the Data Guard configuration is complete, you can delete the statically registered configuration information

[oracle@jason2 dbs] $rman target sys/system@JASON_PD auxiliarysys/system@JASON_SD

Recovery Manager: Release 11.2.0.4.0-Production on Thu Jul 14 23 purl 1512016

Connected to target database: JASON (DBID=2141348976)

RMAN-00571: =

RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =

RMAN-00571: =

RMAN-00554: initialization of internal recovery manager package failed

RMAN-04006: error from auxiliary database: ORA-12528: TNS:listener: allappropriate instances are blocking new connections

Set status after static snooping

[oracle@jason2 dbs] $lsnrctl status

LSNRCTL for Linux: Version 11.2.0.4.0-Production on 14-JUL-201623:15:50

Connecting to (DESCRIPTION= (ADDRESS= (PROTOCOL=TCP) (HOST=192.168.1.100) (PORT=1521)

STATUS of the LISTENER

Alias LISTENER

Version TNSLSNRfor Linux: Version 11.2.0.4.0-Production

Start Date 14-JUL-2016 22:41:05

Uptime 0 days 0hr. 34 min. 44 sec

Trace Level off

Security ON:Local OS Authentication

SNMP OFF

Listener Parameter File / u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora

Listener Log File / u01/app/oracle/diag/tnslsnr/jason2/listener/alert/log.xml

Listening Endpoints Summary...

(DESCRIPTION= (ADDRESS= (PROTOCOL=tcp) (HOST=192.168.1.100) (PORT=1521))

(DESCRIPTION= (ADDRESS= (PROTOCOL=ipc) (KEY=EXTPROC1521)

Services Summary...

Service "JASON2" has 1 instance (s).

Instance "JASON", status BLOCKED, has 1 handler (s) for this service...

The command completed successfully

[oracle@jason2 dbs] $

VI. Changes in the primary and secondary libraries when creating a standby library

In this lab, we use the rman backup before the main library is configured to create the DG. The simulated backup is the backup of the previous day. The database backup ends with the log serial number 17. Then manually switch the archive log generated one day after the simulated backup, and the final log sequence number is 54. The following is the query result of the main database log.

SQL > SELECT SEQUENCE#,APPLIED FROM V$ARCHIVED_LOG ORDER BYSEQUENCE#

SEQUENCE# APPLIED

7 NO

8 NO

9 NO

10 NO

11 NO

12 NO

13 NO

14 NO

15 NO

16 NO

17 NO

SEQUENCE# APPLIED

18 NO

19 NO

20 NO

21 NO

22 NO

23 NO

24 NO

25 NO

26 NO

27 NO

28 NO

SEQUENCE# APPLIED

29 NO

30 NO

31 NO

32 NO

33 NO

34 NO

35 NO

36 NO

37 NO

38 NO

39 NO

SEQUENCE# APPLIED

40 NO

41 NO

42 NO

43 NO

44 NO

45 NO

46 NO

47 NO

48 NO

49 NO

50 NO

SEQUENCE# APPLIED

51 NO

52 NO

53 NO

54 NO

48 rows selected.

SQL >

When the primary library sends rman backups to the standby library, the backup location must be the same as the primary library. Then restore the database in the preparation database. After the recovery, create a standby log group in the slave database, and then execute the alter database open command to open the slave database. At this time, it can be found from the slave log that when the slave is opened, all the archive log files generated since the end of the backup (the archive log must be guaranteed to exist) are automatically transferred to the slave. At this point, if you look at the log again in the main library, you will find that the archive log has been delivered, but not applied.

The following is the log change process:

SQL > /

SEQUENCE# APPLIED

7 NO

8 NO

9 NO

10 NO

11 NO

12 NO

13 NO

14 NO

15 NO

16 NO

17 NO

SEQUENCE# APPLIED

17 NO

18 NO

19 NO

20 NO

21 NO

22 NO

SEQUENCE# APPLIED

23 NO

24 NO

25 NO

26 NO

27 NO

28 NO

SEQUENCE# APPLIED

28 NO

29 NO

30 NO

31 NO

32 NO

33 NO

SEQUENCE# APPLIED

34 NO

35 NO

36 NO

37 NO

38 NO

39 NO

SEQUENCE# APPLIED

39 NO

40 NO

41 NO

42 NO

43 NO

44 NO

SEQUENCE# APPLIED

45 NO

46 NO

47 NO

48 NO

49 NO

50 NO

SEQUENCE# APPLIED

50 NO

51 NO

52 NO

53 NO

54 NO

55 NO

SEQUENCE# APPLIED

56 NO

90 rows selected.

SQL >

Then open the real-time log application in the repository and execute alter database recover managed standby database using current logfiledisconnect from session

When this command is executed, it can be found in the repository log that MRP0 begins to apply all archive logs for data recovery until the latest log. For specific changes, you can view the logs of the main database and slave database as follows.

Note: you can also perform log recovery when the database is mounted, equalize and apply the log before opening the database.

ALTERDATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT FROMSESSION

Alterdatabase recover managed standby database cancel

Alterdatabase open

ALTERDATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT FROMSESSION

Main library log

[root@jason1 trace] # tail-f alert_JASON.log

Sat Jul 23 23:27:56 2016

PING [ARC2]: Heartbeat failed to connect to standby 'JASON2'. Error is16058.

Sat Jul 23 23:28:31 2016

Using STANDBY_ARCHIVE_DEST parameter default value as/u01/app/oracle/archivelog/

ALTER SYSTEM SET log_archive_dest_state_2='ENABLE' SCOPE=MEMORY SID='*'

Sat Jul 23 23:28:31 2016

PING [ARC2]: Heartbeat failed to connect to standby 'JASON2'. Error is16058.

Sat Jul 23 23:28:36 2016

Thread 1 advanced to log sequence 56 (LGWR switch)

Current log# 2 seq# 56 mem# 0:/u01/app/oracle/oradata/JASON/redo02.log

Sat Jul 23 23:28:36 2016

Archived Log entry 52 added for thread 1 sequence 55 ID 0x7fa28a70 dest1:

Sat Jul 23 23:31:57 2016

ALTER SYSTEM SET log_archive_dest_state_2='ENABLE' SCOPE=MEMORY SID='*'

Sat Jul 23 23:31:58 2016

ARC3: Archive log rejected (thread 1 sequence 17) at host 'JASON2'

FAL [server, ARC3]: FAL archive failed, see trace file.

ARCH: FAL archive failed. Archiver continuing

ORACLE Instance JASON-Archival Error. Archiver continuing.

Sat Jul 23 23:32:00 2016

Thread 1 advanced to log sequence 57 (LGWR switch)

Current log# 3 seq# 57 mem# 0:/u01/app/oracle/oradata/JASON/redo03.log

Sat Jul 23 23:32:00 2016

LGWR: Setting 'active' archival for destination LOG_ARCHIVE_DEST_2

LNS: Standby redo logfile selected for thread 1 sequence 57 fordestination LOG_ARCHIVE_DEST_2

Sat Jul 23 23:32:01 2016

Expanded controlfile section 11 from 66 to 153 records

Requested to grow by 87 records; added 3 blocks of records

Sat Jul 23 23:32:01 2016

Archived Log entry 73 added for thread 1 sequence 56 ID 0x7fa28a70 dest1:

Prepare database log

[root@jason2 trace] # tail-f alert_JASON.log

Sat Jul 23 23:11:43 2016

Using STANDBY_ARCHIVE_DEST parameter default value as / u01/app/oracle/archivelog/

Sat Jul 23 23:27:44 2016

Destination database instance is' started' not 'mounted'

Sat Jul 23 23:28:08 2016

Conversion to standby controlfile pending for restored file

No controlfile conversion

Sat Jul 23 23:28:11 2016

RFS connections have been disallowed

Alter database mount standby database

Converting controlfile to standby

If db_file_name_convert or log_file_name_convert parameters

Are not used, then RMAN intervention is required to fix the

File names in the converted control file. Refer to RMAN

Documentation for how to fix all file names.

Clearing standby activation ID 2141358704 (0x7fa28a70)

The primary database controlfile was created using the

'MAXLOGFILES 16 'clause.

There is space for up to 13 standby redo logfiles

Use the following SQL commands on the standby database to create

Standby redo logfiles that match the primary database:

ALTER DATABASE ADD STANDBY LOGFILE 'srl1.f' SIZE 52428800

ALTER DATABASE ADD STANDBY LOGFILE 'srl2.f' SIZE 52428800

ALTER DATABASE ADD STANDBY LOGFILE 'srl3.f' SIZE 52428800

ALTER DATABASE ADD STANDBY LOGFILE 'srl4.f' SIZE 52428800

Set as converted control file due to db_unique_name mismatch

Changing di2dbun from JASON1 to JASON2

ARCH: STARTING ARCH PROCESSES

Sat Jul 23 23:28:16 2016

ARC0 started with pid=22, OS id=2774

ARC0: Archival started

ARCH: STARTING ARCH PROCESSES COMPLETE

ARC0: STARTING ARCH PROCESSES

Sat Jul 23 23:28:17 2016

Successful mount of redo thread 1, with mount id 2142218252

Physical Standby Database mounted.

Lost write protection disabled

Sat Jul 23 23:28:17 2016

ARC1 started with pid=23, OS id=2776

Sat Jul 23 23:28:17 2016

ARC2 started with pid=24, OS id=2778

ARC1: Archival started

ARC2: Archival started

ARC1: Becoming the'no FAL' ARCH

ARC2: Becoming the heartbeat ARCH

ARC2: Becoming the active heartbeat ARCH

Sat Jul 23 23:28:17 2016

ARC3 started with pid=25, OS id=2780

Completed: alter database mount standby database

ARC3: Archival started

ARC0: STARTING ARCH PROCESSES COMPLETE

Sat Jul 23 23:28:19 2016

Full restore complete of datafile 4/u01/app/oracle/oradata/JASON/users01.dbf. Elapsed time: 0:00:00

Checkpoint is 1024819

Last deallocation scn is 3

Errors in file/u01/app/oracle/diag/rdbms/jason2/JASON/trace/JASON_lgwr_2557.trc:

ORA-00313: open failed for members of log group 1 of thread 1

ORA-00312: online log 1 thread 1 Vortex Greater U01App Uniplex oracleUniplex oradata Universe JASONGUDO 01.log'

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

Additional information: 3

Errors in file / u01/app/oracle/diag/rdbms/jason2/JASON/trace/JASON_lgwr_2557.trc:

ORA-00313: open failed for members of log group 1 of thread 1

ORA-00312: online log 1 thread 1 Vortex Greater U01App Uniplex oracleUniplex oradata Universe JASONGUDO 01.log'

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

Additional information: 3

Errors in file/u01/app/oracle/diag/rdbms/jason2/JASON/trace/JASON_lgwr_2557.trc:

ORA-00313: open failed for members of log group 2 of thread 1

ORA-00312: online log 2 thread 1:'/ u01 Greater App Universe oradata Universe redo02.log'

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

Additional information: 3

Errors in file/u01/app/oracle/diag/rdbms/jason2/JASON/trace/JASON_lgwr_2557.trc:

ORA-00313: open failed for members of log group 2 of thread 1

ORA-00312: online log 2 thread 1 Flux Grey U01 Grey App Grey oracleGrease oradataUnique JASONUnique redo02.log'

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

Additional information: 3

Errors in file / u01/app/oracle/diag/rdbms/jason2/JASON/trace/JASON_lgwr_2557.trc:

ORA-00313: open failed for members of log group 3 of thread 1

ORA-00312: online log 3 thread 1 Flux Grey U01 Grey App Grey oracleGrease oradataUnique JASONUnique redo03.log'

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

Additional information: 3

Errors in file/u01/app/oracle/diag/rdbms/jason2/JASON/trace/JASON_lgwr_2557.trc:

ORA-00313: open failed for members of log group 3 of thread 1

ORA-00312: online log 3 thread 1:'/ u01 apprenticeship oradata Universe redo03.log'

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

Additional information: 3

Sat Jul 23 23:28:24 2016

Warning: VKTM detected a time drift.

Time drifts can result in an unexpected behavior such as time-outs.Please check trace file for more details.

Full restore complete of datafile 3/u01/app/oracle/oradata/JASON/undotbs01.dbf. Elapsed time: 0:00:02

Checkpoint is 1024819

Last deallocation scn is 968786

Undo Optimization current scn is967371

Sat Jul 23 23:28:59 2016

Full restore complete of datafile 2/u01/app/oracle/oradata/JASON/sysaux01.dbf. Elapsed time: 0:00:38

Checkpoint is 1024819

Last deallocation scn is 964749

Sat Jul 23 23:29:11 2016

Full restore complete of datafile 1/u01/app/oracle/oradata/JASON/system01.dbf. Elapsed time: 0:00:49

Checkpoint is 1024819

Last deallocation scn is 963928

Undo Optimization current scn is967371

Sat Jul 23 23:29:17 2016

Switch of datafile 1 complete to datafile copy

Checkpoint is 1024819

Switch of datafile 2 complete to datafile copy

Checkpoint is 1024819

Switch of datafile 3 complete to datafile copy

Checkpoint is 1024819

Switch of datafile 4 complete to datafile copy

Checkpoint is 1024819

Alter database clear logfile group 1

Clearing online log 1 of thread 1 sequence number 16

Errors in file/u01/app/oracle/diag/rdbms/jason2/JASON/trace/JASON_ora_2710.trc:

ORA-00313: open failed for members of log group 1 of thread 1

ORA-00312: online log 1 thread 1:'/ u01 apprenticeship oradata Universe redo01.log'

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

Additional information: 3

Errors in file/u01/app/oracle/diag/rdbms/jason2/JASON/trace/JASON_ora_2710.trc:

ORA-00313: open failed for members of log group 1 of thread 1

ORA-00312: online log 1 thread 1 Vortex Greater U01App Uniplex oracleUniplex oradata Universe JASONGUDO 01.log'

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

Additional information: 3

Completed: alter database clear logfile group 1

Alter database clear logfile group 2

Clearing online log 2 of thread 1 sequence number 17

Errors in file/u01/app/oracle/diag/rdbms/jason2/JASON/trace/JASON_ora_2710.trc:

ORA-00313: open failed for members of log group 2 of thread 1

ORA-00312: online log 2 thread 1 Flux Grey U01 Grey App Grey oracleGrease oradataUnique JASONUnique redo02.log'

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

Additional information: 3

Errors in file/u01/app/oracle/diag/rdbms/jason2/JASON/trace/JASON_ora_2710.trc:

ORA-00313: open failed for members of log group 2 of thread 1

ORA-00312: online log 2 thread 1 Flux Grey U01 Grey App Grey oracleGrease oradataUnique JASONUnique redo02.log'

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

Additional information: 3

Completed: alter database clear logfile group 2

Alter database clear logfile group 3

Clearing online log 3 of thread 1 sequence number 15

Errors in file/u01/app/oracle/diag/rdbms/jason2/JASON/trace/JASON_ora_2710.trc:

ORA-00313: open failed for members of log group 3 of thread 1

ORA-00312: online log 3 thread 1 Flux Grey U01 Grey App Grey oracleGrease oradataUnique JASONUnique redo03.log'

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

Additional information: 3

Errors in file / u01/app/oracle/diag/rdbms/jason2/JASON/trace/JASON_ora_2710.trc:

ORA-00313: open failed for members of log group 3 of thread 1

ORA-00312: online log 3 thread 1 Flux Grey U01 Grey App Grey oracleGrease oradataUnique JASONUnique redo03.log'

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

Additional information: 3

Completed: alter database clear logfile group 3

RFS connections are allowed

Sat Jul 23 23:30:29 2016

ALTER DATABASE ADD STANDBY LOGFILE ('/ u01 SIZE) SIZE 50m

Completed: ALTER DATABASE ADD STANDBY LOGFILE ('/ u01ax SIZE SIZE 50m)

Sat Jul 23 23:30:48 2016

ALTER DATABASE ADD STANDBY LOGFILE ('/ u01 SIZE) SIZE 50m

Completed: ALTER DATABASE ADD STANDBY LOGFILE ('/ u01ax SIZE SIZE 50m)

Sat Jul 23 23:31:02 2016

ALTER DATABASE ADD STANDBY LOGFILE ('/ u01 SIZE) SIZE 50m

Completed: ALTER DATABASE ADD STANDBY LOGFILE ('/ u01ax SIZE SIZE 50m)

Sat Jul 23 23:31:17 2016

ALTER DATABASE ADD STANDBY LOGFILE ('/ u01 SIZE) SIZE 50m

Completed: ALTER DATABASE ADD STANDBY LOGFILE ('/ u01ax SIZE SIZE 50m)

Sat Jul 23 23:31:45 2016

Alter database open

AUDIT_TRAIL initialization parameter is changed to OS, as DB is NOTcompatible for database opened with read-only access

Signalling error 1152 for datafile 1!

Beginning Standby Crash Recovery.

Serial Media Recovery started

Managed Standby Recovery starting Real Time Apply

Media Recovery Waiting for thread 1 sequence 17

Sat Jul 23 23:31:45 2016

RFS [1]: Assigned to RFS process 2810

RFS [1]: Opened log for thread 1 sequence 17 dbid 2141348976 branch917134706

Archived Log entry 1 added for thread 1 sequence 17 rlc 917134706 ID0x7fa28a70 dest 2:

Media Recovery Log / u01/app/oracle/archivelog/1_17_917134706.dbf

Incomplete Recovery applied until change 1024865 time 07/23/201622:46:10

Completed Standby Crash Recovery.

Sat Jul 23 23:31:46 2016

SMON: enabling cache recovery

Sat Jul 23 23:31:47 2016

RFS [2]: Assigned to RFS process 2808

RFS [2]: Opened log for thread 1 sequence 19 dbid 2141348976 branch917134706

RFS [1]: Opened log for thread 1 sequence 20 dbid 2141348976 branch917134706

Archived Log entry 2 added for thread 1 sequence 19 rlc 917134706 ID0x7fa28a70 dest 2:

Sat Jul 23 23:31:47 2016

RFS [3]: Assigned to RFS process 2812

RFS [3]: Opened log for thread 1 sequence 18 dbid 2141348976 branch917134706

Archived Log entry 3 added for thread 1 sequence 20 rlc 917134706 ID0x7fa28a70 dest 2:

RFS [2]: Opened log for thread 1 sequence 21 dbid 2141348976 branch917134706

RFS [1]: Opened log for thread 1 sequence 22 dbid 2141348976 branch917134706

Archived Log entry 4 added for thread 1 sequence 22 rlc 917134706 ID0x7fa28a70 dest 2:

Archived Log entry 5 added for thread 1 sequence 21 rlc 917134706 ID0x7fa28a70 dest 2:

Archived Log entry 6 added for thread 1 sequence 18 rlc 917134706 ID0x7fa28a70 dest 2:

RFS [1]: Opened log for thread 1 sequence 23 dbid 2141348976 branch917134706

RFS [2]: Opened log for thread 1 sequence 25 dbid 2141348976 branch917134706

Archived Log entry 7 added for thread 1 sequence 23 rlc 917134706 ID0x7fa28a70 dest 2:

RFS [3]: Opened log for thread 1 sequence 24 dbid 2141348976 branch917134706

Archived Log entry 8 added for thread 1 sequence 25 rlc 917134706 ID0x7fa28a70 dest 2:

Archived Log entry 9 added for thread 1 sequence 24 rlc 917134706 ID0x7fa28a70 dest 2:

RFS [1]: Opened log for thread 1 sequence 26 dbid 2141348976 branch917134706

RFS [3]: Opened log for thread 1 sequence 27 dbid 2141348976 branch917134706

Archived Log entry 10 added for thread 1 sequence 26 rlc 917134706 ID0x7fa28a70 dest 2:

RFS [2]: Opened log for thread 1 sequence 28 dbid 2141348976 branch917134706

Archived Log entry 11 added for thread 1 sequence 27 rlc 917134706 ID0x7fa28a70 dest 2:

Archived Log entry 12 added for thread 1 sequence 28 rlc 917134706 ID0x7fa28a70 dest 2:

RFS [1]: Opened log for thread 1 sequence 29 dbid 2141348976 branch917134706

RFS [3]: Opened log for thread 1 sequence 30 dbid 2141348976 branch917134706

Archived Log entry 13 added for thread 1 sequence 29 rlc 917134706 ID0x7fa28a70 dest 2:

RFS [2]: Opened log for thread 1 sequence 31 dbid 2141348976 branch917134706

Archived Log entry 14 added for thread 1 sequence 30 rlc 917134706 ID0x7fa28a70 dest 2:

RFS [1]: Opened log for thread 1 sequence 32 dbid 2141348976 branch917134706

Archived Log entry 15 added for thread 1 sequence 31 rlc 917134706 ID0x7fa28a70 dest 2:

RFS [3]: Opened log for thread 1 sequence 33 dbid 2141348976 branch917134706

Archived Log entry 16 added for thread 1 sequence 32 rlc 917134706 ID0x7fa28a70 dest 2:

Archived Log entry 17 added for thread 1 sequence 33 rlc 917134706 ID0x7fa28a70 dest 2:

RFS [2]: Opened log for thread 1 sequence 34 dbid 2141348976 branch917134706

RFS [1]: Opened log for thread 1 sequence 35 dbid 2141348976 branch917134706

Archived Log entry 18 added for thread 1 sequence 34 rlc 917134706 ID0x7fa28a70 dest 2:

RFS [3]: Opened log for thread 1 sequence 36 dbid 2141348976 branch917134706

Archived Log entry 19 added for thread 1 sequence 35 rlc 917134706 ID0x7fa28a70 dest 2:

Archived Log entry 20 added for thread 1 sequence 36 rlc 917134706 ID0x7fa28a70 dest 2:

Sat Jul 23 23:31:48 2016

Primary database is in MAXIMUM PERFORMANCE mode

RFS [4]: Assigned to RFS process 2814

RFS [4]: Selected log 4 for thread 1 sequence 57 dbid 2141348976 branch917134706

Sat Jul 23 23:31:50 2016

RFS [5]: Assigned to RFS process 2816

RFS [5]: Opened log for thread 1 sequence 38 dbid 2141348976 branch917134706

Sat Jul 23 23:31:50 2016

RFS [6]: Assigned to RFS process 2820

RFS [6]: Opened log for thread 1 sequence 39 dbid 2141348976 branch917134706

Archived Log entry 21 added for thread 1 sequence 38 rlc 917134706 ID0x7fa28a70 dest 2:

Sat Jul 23 23:31:50 2016

RFS [7]: Assigned to RFS process 2818

RFS [7]: Opened log for thread 1 sequence 37 dbid 2141348976 branch917134706

Archived Log entry 22 added for thread 1 sequence 39 rlc 917134706 ID0x7fa28a70 dest 2:

Archived Log entry 23 added for thread 1 sequence 37 rlc 917134706 ID0x7fa28a70 dest 2:

RFS [5]: Opened log for thread 1 sequence 40 dbid 2141348976 branch917134706

Dictionary check beginning

RFS [6]: Opened log for thread 1 sequence 41 dbid 2141348976 branch917134706

Archived Log entry 24 added for thread 1 sequence 40 rlc 917134706 ID0x7fa28a70 dest 2:

RFS [7]: Opened log for thread 1 sequence 42 dbid 2141348976 branch917134706

Archived Log entry 25 added for thread 1 sequence 41 rlc 917134706 ID0x7fa28a70 dest 2:

RFS [5]: Opened log for thread 1 sequence 43 dbid 2141348976 branch917134706

Archived Log entry 26 added for thread 1 sequence 42 rlc 917134706 ID0x7fa28a70 dest 2:

Archived Log entry 27 added for thread 1 sequence 43 rlc 917134706 ID0x7fa28a70 dest 2:

RFS [6]: Opened log for thread 1 sequence 44 dbid 2141348976 branch917134706

RFS [7]: Opened log for thread 1 sequence 45 dbid 2141348976 branch917134706

RFS [5]: Opened log for thread 1 sequence 46 dbid 2141348976 branch917134706

Archived Log entry 28 added for thread 1 sequence 44 rlc 917134706 ID0x7fa28a70 dest 2:

Expanded controlfile section 11 from 28 to 280 records

Requested to grow by 252 records; added 9 blocks of records

Archived Log entry 29 added for thread 1 sequence 45 rlc 917134706 ID0x7fa28a70 dest 2:

Archived Log entry 30 added for thread 1 sequence 46 rlc 917134706 ID0x7fa28a70 dest 2:

RFS [6]: Opened log for thread 1 sequence 47 dbid 2141348976 branch917134706

RFS [7]: Opened log for thread 1 sequence 48 dbid 2141348976 branch917134706

Archived Log entry 31 added for thread 1 sequence 47 rlc 917134706 ID0x7fa28a70 dest 2:

Archived Log entry 32 added for thread 1 sequence 48 rlc 917134706 ID0x7fa28a70 dest 2:

RFS [5]: Opened log for thread 1 sequence 49 dbid 2141348976 branch917134706

Sat Jul 23 23:31:52 2016

Errors in file/u01/app/oracle/diag/rdbms/jason2/JASON/trace/JASON_dbw0_2555.trc:

ORA-01157: cannot identify/lock data file 201-see DBWR trace file

ORA-01110: data file 201:'/ u01Applicable oradataUniple JASONUnip temp01.dbf'

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

Additional information: 3

Errors in file/u01/app/oracle/diag/rdbms/jason2/JASON/trace/JASON_dbw0_2555.trc:

ORA-01186: file 201 failed verification tests

ORA-01157: cannot identify/lock data file 201-see DBWR trace file

ORA-01110: data file 201:'/ u01Applicable oradataUniple JASONUnip temp01.dbf'

File 201 not verified due to error ORA-01157

Archived Log entry 33 added for thread 1 sequence 49 rlc 917134706 ID0x7fa28a70 dest 2:

Dictionary check complete

Re-creating tempfile / u01/app/oracle/oradata/JASON/temp01.dbf

RFS [6]: Opened log for thread 1 sequence 50 dbid 2141348976 branch917134706

Archived Log entry 34 added for thread 1 sequence 50 rlc 917134706 ID0x7fa28a70 dest 2:

Database Characterset is ZHS16GBK

RFS [6]: Opened log for thread 1 sequence 53 dbid 2141348976 branch917134706

Archived Log entry 35 added for thread 1 sequence 53 rlc 917134706 ID0x7fa28a70 dest 2:

RFS [7]: Opened log for thread 1 sequence 51 dbid 2141348976 branch917134706

Archived Log entry 36 added for thread 1 sequence 51 rlc 917134706 ID0x7fa28a70 dest 2:

RFS [6]: Opened log for thread 1 sequence 54 dbid 2141348976 branch917134706

RFS [5]: Opened log for thread 1 sequence 52 dbid 2141348976 branch917134706

Archived Log entry 37 added for thread 1 sequence 54 rlc 917134706 ID0x7fa28a70 dest 2:

RFS [7]: Opened log for thread 1 sequence 55 dbid 2141348976 branch917134706

Archived Log entry 38 added for thread 1 sequence 52 rlc 917134706 ID0x7fa28a70 dest 2:

Archived Log entry 39 added for thread 1 sequence 55 rlc 917134706 ID0x7fa28a70 dest 2:

RFS [6]: Opened log for thread 1 sequence 56 dbid 2141348976 branch917134706

Archived Log entry 40 added for thread 1 sequence 56 rlc 917134706 ID0x7fa28a70 dest 2:

Sat Jul 23 23:31:56 2016

No Resource Manager plan active

* * *

WARNING: Files may exists in db_recovery_file_dest

That are not known to the database. Use the RMAN command

CATALOG RECOVERY AREA to re-catalog any such files.

If files cannot be cataloged, then manually delete them

Using OS command.

One of the following events caused this:

1. A backup controlfile was restored.

2. A standby controlfile was restored.

3. The controlfile was re-created.

4. Db_recovery_file_dest had previously been enabled and

Then disabled.

* * *

Replication_dependency_tracking turned off (no async multimasterreplication found)

Physical standby database opened for read only access.

Sat Jul 23 23:32:01 2016

Db_recovery_file_dest_size of 4182 MB is 0.005% used. This is a

User-specified limit on the amount of space that will be used by this

Database for recovery-related files, and does not reflect the amount of

Space available in the underlying filesystem or ASM diskgroup.

Completed: alter database open

Sat Jul 23 23:32:25 2016

Alter database recover managed standby database using current logfiledisconnect from session

Attempt to start background Managed Standby Recovery process (JASON)

Sat Jul 23 23:32:25 2016

MRP0 started with pid=28, OS id=2824

MRP0: Background Managed Standby Recovery process started (JASON)

Serial Media Recovery started

Managed Standby Recovery starting Real Time Apply

Waiting for all non-current ORLs to be archived...

All non-current ORLs have been archived.

Media Recovery Log / u01/app/oracle/archivelog/1_17_917134706.dbf

Media Recovery Log / u01/app/oracle/archivelog/1_18_917134706.dbf

Media Recovery Log / u01/app/oracle/archivelog/1_19_917134706.dbf

Media Recovery Log / u01/app/oracle/archivelog/1_20_917134706.dbf

Media Recovery Log / u01/app/oracle/archivelog/1_21_917134706.dbf

Media Recovery Log / u01/app/oracle/archivelog/1_22_917134706.dbf

Media Recovery Log / u01/app/oracle/archivelog/1_23_917134706.dbf

Media Recovery Log / u01/app/oracle/archivelog/1_24_917134706.dbf

Media Recovery Log / u01/app/oracle/archivelog/1_25_917134706.dbf

Media Recovery Log / u01/app/oracle/archivelog/1_26_917134706.dbf

Media Recovery Log / u01/app/oracle/archivelog/1_27_917134706.dbf

Media Recovery Log / u01/app/oracle/archivelog/1_28_917134706.dbf

Media Recovery Log / u01/app/oracle/archivelog/1_29_917134706.dbf

Completed: alter database recover managed standby database using currentlogfile disconnect from session

Media Recovery Log / u01/app/oracle/archivelog/1_30_917134706.dbf

Media Recovery Log / u01/app/oracle/archivelog/1_31_917134706.dbf

Media Recovery Log / u01/app/oracle/archivelog/1_32_917134706.dbf

Media Recovery Log / u01/app/oracle/archivelog/1_33_917134706.dbf

Media Recovery Log / u01/app/oracle/archivelog/1_34_917134706.dbf

Media Recovery Log / u01/app/oracle/archivelog/1_35_917134706.dbf

Media Recovery Log / u01/app/oracle/archivelog/1_36_917134706.dbf

Media Recovery Log / u01/app/oracle/archivelog/1_37_917134706.dbf

Media Recovery Log / u01/app/oracle/archivelog/1_38_917134706.dbf

Media Recovery Log / u01/app/oracle/archivelog/1_39_917134706.dbf

Media Recovery Log / u01/app/oracle/archivelog/1_40_917134706.dbf

Media Recovery Log / u01/app/oracle/archivelog/1_41_917134706.dbf

Media Recovery Log / u01/app/oracle/archivelog/1_42_917134706.dbf

Media Recovery Log / u01/app/oracle/archivelog/1_43_917134706.dbf

Media Recovery Log / u01/app/oracle/archivelog/1_44_917134706.dbf

Media Recovery Log / u01/app/oracle/archivelog/1_45_917134706.dbf

Media Recovery Log / u01/app/oracle/archivelog/1_46_917134706.dbf

Media Recovery Log / u01/app/oracle/archivelog/1_47_917134706.dbf

Media Recovery Log / u01/app/oracle/archivelog/1_48_917134706.dbf

Sat Jul 23 23:32:35 2016

Media Recovery Log / u01/app/oracle/archivelog/1_49_917134706.dbf

Media Recovery Log / u01/app/oracle/archivelog/1_50_917134706.dbf

Media Recovery Log / u01/app/oracle/archivelog/1_51_917134706.dbf

Media Recovery Log / u01/app/oracle/archivelog/1_52_917134706.dbf

Media Recovery Log / u01/app/oracle/archivelog/1_53_917134706.dbf

Media Recovery Log / u01/app/oracle/archivelog/1_54_917134706.dbf

Media Recovery Log / u01/app/oracle/archivelog/1_55_917134706.dbf

Media Recovery Log / u01/app/oracle/archivelog/1_56_917134706.dbf

Media Recovery Waiting for thread 1 sequence 57 (in transit)

Recovery of Online Redo Log: Thread 1 Group 4 Seq 57 Reading mem 0

Mem# 0:/u01/app/oracle/oradata/JASON/standby01.log

Note: if ADG is not enabled for 11g database, then when the mount status of the database is ready, when the log real-time application alter database recovermanaged standby database using current logfile disconnect from session is enabled. The undelivered archive log starts to be transferred when the real-time application of the log is opened, and the log is applied after the transfer is finished.

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.

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.