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

Oracle RAC Standby implementation Manual

Catalogue

1 implementation of environmental planning 3

1.1 IP address Planning 3

1.2 Archive configuration related parameters 3

1.3 main library software environment information 4

1.4 prepare database software environment information 4

2 Active DataGuard implementation conditions 6

3 Active DataGuard implementation preparation 8

3.1 configure DG dedicated snooping 8

3.1.1 create LISTENER_DG 8

3.1.2 add snooping to crs resource 10

3.2Configuring TNS aliases 10

3.3 synchronize password files 11

3.4 Test the effectiveness of the TNS configuration 11

4 configure database parameters 13

4.1 main library parameter adjustment 13

4.2 the main library creates STANDBY logs 14

4.3 adjust the parameters of the library 14

4.4 create a directory required for the standby library 15

5 prepare library initialization 16

5.1 set slave ORACLE_SID environment variable 16

5.2 start standby database instance to NOMOUNT status 16

5.3 Test the connection status of the primary / standby database 16

5.4 perform DUPLICATE operation to copy database 16

5.5 create standby library parameter file 17

5.5.1 preparation library node 1 completes parameter file adjustment 17

5.5.2 standby library node 2 completes pfile file creation 18

5.6 add repository to crs resource 18

5.7 start standby 18

5.8 launch Active DataGuard 18

6 prepare for library test 19

1 implement environmental planning

There are three protection modes of DataGuard: maximum protection, maximum effectiveness and maximum performance. To reduce the impact on the primary database, the maximum performance mode is used for DataGuard configuration below.

There are three main types of slave database in DataGuard configuration: logical standby database, physical standby database and snapshot-based standby database. The physical standby database is used for DataGuard configuration below.

Data synchronization between master database and standby database in DataGuard configuration is realized through TCP/IP network communication. In order to minimize the competition of network bandwidth and the performance problems of existing applications, it is suggested to build a network dedicated to DataGuard between the master database host and the standby database host, that is, it is necessary to add new network cards and other hardware resources to build a network dedicated to DataGuard.

In addition, it is recommended to create database listeners dedicated to DataGuard on the master database and slave database, such as listener_dg, whose listening port is 1525. If the master database and slave database are on different network segments and there is a firewall, port 1525 needs to be enabled on the firewall.

1.1 IP address Planning

Hostnam

IP address

Description

Master database environment

Crmdb1

192.168.56.210

Public network IP address

192.168.56.216

DG dedicated IP address

Crmdb2

192.168.56.211

Public network IP address

192.168.56.217

DG dedicated IP address

Standby database environment

Crmdg1

192.168.56.220

Public network IP address

192.168.56.225

DG dedicated IP address

Crmdg2

192.168.56.221

Public network IP address

192.168.56.226

DG dedicated IP address

1.2 Archive configuration related parameters

Database type

Hostnam

DB_UNIQUE_NAME

INSTANCE_NAME

Net Service Name

Main library

Crmdb1

Crmdb

Crmdb1

CRMDB_DG

Crmdb2

Crmdb2

Prepare the library

Crmdg1

Crmdg

Crmdb1

CRMDG_DG

Crmdb2

Crmdb2

1.3 Software environment information of the main library

In order to facilitate the management, the configuration of the software environment information of the main and standby libraries is consistent.

Software environment information of main library

Database sys user password

The password of the primary database and the standby database must be the same, set to oracle

Grid and database version

11.2.0.4

ORACLE_SID environment variable

Crmdb1 and crmdb2

GRID software ORACLE_BASE directory

/ oracle/app/oracle

GRID software ORACLE_HOME directory

/ grid/app/11.2.0.4/grid

DB software ORACLE_BASE directory

/ oracle/app/oracle

DB software ORACLE_HOME directory

/ oracle/app/oracle/product/11.2.0.4/db_1

DG dedicated listener

LISTENER_DG

DG dedicated listener port

1525

Initialization parameter

DB_NAME=crmdb

DB_UNIQUE_NAME=crmdb

COMPATIBLE primary database and standby database must be consistent

Archiving mode

Archiving mode

Archival catalogue

+ CRMDBARCH

1.4 prepare database software environment information

Preparation of software environment information

Database sys user password

The password of the primary database and the standby database must be the same, set to oracle

Grid and database version

11.2.0.4

ORACLE_SID environment variable

Crmdb1 and crmdb2

GRID software ORACLE_BASE directory

/ oracle/app/oracle

GRID software ORACLE_HOME directory

/ grid/app/11.2.0.4/grid

DB software ORACLE_BASE directory

/ oracle/app/oracle

DB software ORACLE_HOME directory

/ oracle/app/oracle/product/11.2.0.4/db_1

DG dedicated listener

LISTENER_DG

DG dedicated listener port

1525

Initialization parameter

DB_NAME=crmdb

DB_UNIQUE_NAME=crmdg

COMPATIBLE primary database and standby database must be consistent

Archiving mode

Archiving mode

Archival catalogue

+ CRMDGARCH

2 Active DataGuard implementation conditions

The prerequisites for implementing Active DataGuard are as follows:

1. The hardware platforms of the master database host and the standby database host are the same, if both are Linux hosts

two。 The software versions of the main database and standby database are the same and both are 11.2.0.4.

3. The storage space of the standby database is not less than that of the primary database.

$asmcmd

ASMCMD > lsdg

4. The master database is running normally and working in archivelog mode

$sqlplus / as sysdba

-1. Modify and check archive parameters

SQL > alter system set log_archive_dest_1='location=+CRMDBARCH'

SQL > show parameter log_archive_dest_1

SQL > show parameter log_archive_format

-- 2. Close the two nodes of the main library

SQL > shutdown immediate

-3. Start a node to enable archiving operation

SQL > startup mount

SQL > alter database ARCHIVELOG

SQL > alter database open

-- 4. Start another node

SQL > startup

-5. Test archive configuration results

SQL > alter system archive log current

5. The main database database needs to start the force logging function

$sqlplus / as sysdba

SQL > select FORCE_LOGGING from v$database

SQL > alter database force logging

6. The password of the primary database and standby database sys user is the same, and the password file must exist and the primary database initialization parameter remote_login_passwordfile must be set to EXCLUSIVE

3 preparation for Active DataGuard implementation

In order to facilitate the switching between master and slave databases, the application can switch quickly, and the instance names of master and slave databases are the same.

3.1 configure DG dedicated snooping 3.1.1 create LISTENER_DG

Log in to each node host of the master / slave database through grid to create a LISTENER_DG listener. For the list of master / slave database hosts, please see: IP address Plan.

Main library configuration file (crmdb1/crmdb2 host):

[grid@crmdb1 ~] $cd $ORACLE_HOME/network/admin

[grid@crmdb1 admin] $cp listener.ora listener.ora.`date +% Y% m% d`

[grid@crmdb1 admin] $vi listener.ora

# ADD FOR DG

LISTENER_DG =

(DESCRIPTION_LIST =

(DESCRIPTION =

(ADDRESS = (PROTOCOL = TCP) (HOST = 192.168.56.216) (PORT = 1525))

)

)

SID_LIST_LISTENER_DG =

(SID_LIST =

(SID_DESC =

(GLOBAL_DBNAME = crmdb)

(ORACLE_HOME = / oracle/app/oracle/product/11.2.0.4/db_1)

(SID_NAME = crmdb1)

)

)

Red part content description:

LISTENER_DG:DG dedicated listener name

192.168.56.216:crmdb1 node DG snooping IP address

1525:DG dedicated listening port

Crmdb:DB_UNIQUE_NAME initialization parameter valu

Crmdb1: current host ORACLE_SID or INSTANCE_NAME

Standby repository configuration file (crmdg1/crmdg2 host):

[grid@crmdg1 ~] $cd $ORACLE_HOME/network/admin

[grid@crmdg1 admin] $cp listener.ora listener.ora.`date +% Y% m% d`

[grid@crmdg1 admin] $vi listener.ora

# ADD FOR DG

LISTENER_DG =

(DESCRIPTION_LIST =

(DESCRIPTION =

(ADDRESS = (PROTOCOL = TCP) (HOST = 192.168.56.225) (PORT = 1525))

)

)

SID_LIST_LISTENER_DG =

(SID_LIST =

(SID_DESC =

(GLOBAL_DBNAME = crmdg)

(ORACLE_HOME = / oracle/app/oracle/product/11.2.0.4/db_1)

(SID_NAME = crmdb1)

)

)

Red part content description:

LISTENER_DG:DG dedicated listener name

192.168.56.225:crmdg1 node DG exclusively listens to the IP address. This parameter varies from host to host.

1525:DG dedicated listening port

Crmdg:DB_UNIQUE_NAME initialization parameter value, which is different from master / slave database.

Crmdb1: current host ORACLE_SID or INSTANCE_NAME. This parameter varies from node to node in the cluster.

3.1.2 add snooping to crs resources

Main library:

[grid@crmdb1] $srvctl add listener-l LISTENER_DG-p TCP:1525

[grid@crmdb1] $srvctl start listener-l LISTENER_DG-n crmdb1

[grid@crmdb2] $srvctl start listener-l LISTENER_DG-n crmdb2

Prepare the library:

[grid@crmdg1] $srvctl add listener-l LISTENER_DG-p TCP:1525

[grid@crmdg1] $srvctl start listener-l LISTENER_DG-n crmdg1

[grid@crmdg2] $srvctl start listener-l LISTENER_DG-n crmdg2

3.2Configuring TNS aliases

The configuration is the same as the primary and standby libraries.

[oracle@crmdb1 ~] $cd $ORACLE_HOME/network/admin

[oracle@crmdb1 admin] $cp tnsnames.ora tnsnames.ora.`date +% Y% m% d`

[oracle@crmdb1 admin] $vi tnsnames.ora

CRMDB_DG =

(DESCRIPTION =

(ADDRESS = (PROTOCOL = TCP) (HOST = 192.168.56.216) (PORT = 1525))

(ADDRESS = (PROTOCOL = TCP) (HOST = 192.168.56.217) (PORT = 1525))

(CONNECT_DATA =

(SERVICE_NAME = CRMDB)

)

)

CRMDG_DG =

(DESCRIPTION =

(ADDRESS = (PROTOCOL = TCP) (HOST = 192.168.56.225) (PORT = 1525))

(ADDRESS = (PROTOCOL = TCP) (HOST = 192.168.56.226) (PORT = 1525))

(CONNECT_DATA =

(SERVICE_NAME = CRMDG)

)

)

Note:

The SERVICE_NAME of the slave library is CRMDG, but it is configured as crmdb1/crmdb2 in ORACLE_SID.

3.3 synchronize password files

If you need to change the password of the sys user, ftp the database password file to other crmdb2, crmdg1, and crmdg2 nodes after the node crmdb1 executes the following command.

[oracle@crmdb1 ~] $cd $ORACLE_HOME/dbs

-1. Ftp to each node. Using the hostname makes it easy to organize the script. The actual operation requires the host ip address.

[oracle@crmdb1 dbs] $scp orapwcrmdb1 crmdb2: `pwd` # copy password file to crmdb2

[oracle@crmdb1 dbs] $scp orapwcrmdb1 crmdg1: `pwd` # copy password file to crmdg1

[oracle@crmdb1 dbs] $scp orapwcrmdb1 crmdg2: `pwd` # copy password file to crmdg2

-- 2. Modify password file name

[oracle@crmdb2 dbs] $mv orapwcrmdb1 orapwcrmdb2 # crmdb2 operation on the node

[oracle@crmdg2 dbs] $mv orapwcrmdb1 orapwcrmdb2 # crmdg2 operation on the node

-3. Modify password file permissions (this operation is not actually required for ftp through oracle users)

[oracle@crmdb2 dbs] $chown oracle:oinstall orapwcrmdb2 # crmdb1 operation on the node

[oracle@crmdg1 dbs] $chown oracle:oinstall orapwcrmdb1 # crmdg1 operation on the node

[oracle@crmdg2 dbs] $chown oracle:oinstall orapwcrmdb2 # crmdg2 operation on the node

3.4 Test the validity of the TNS configuration

All hosts are tested for connectivity.

[oracle@crmdb1 ~] $tnsping CRMDB_DG

[oracle@crmdb1 ~] $tnsping CRMDG_DG

[oracle@crmdb1 ~] $sqlplus sys/oracle@CRMDB_DG as sysdba

[oracle@crmdb1 ~] $sqlplus sys/oracle@CRMDG_DG as sysdba

4 configure database parameters

DB_UNIQUE_NAME,INSTANCE_NAME,Net Service Name related parameters configuration. Refer to Archive configuration related parameters.

4.1 Parameter adjustment of the main library

SQL > show parameter spfile

-1. Back up the main library parameter file

SQL > create pfile='/home/oracle/crmdb.pfile' from spfile

-- 2. Modify the main library parameter file

Alter system set LOG_ARCHIVE_CONFIG='DG_CONFIG= (crmdb,crmdg)'

Alter system set LOG_ARCHIVE_DEST_1='LOCATION=+CRMDBARCH VALID_FOR= (ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=crmdb'

Alter system set LOG_ARCHIVE_DEST_2='SERVICE=CRMDG_DG LGWR ASYNC VALID_FOR= (ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=crmdg'

Alter system set FAL_SERVER=CRMDG_DG

Alter system set STANDBY_FILE_MANAGEMENT=AUTO

Alter system set LOG_ARCHIVE_MAX_PROCESSES=4

Alter system set DB_FILE_NAME_CONVERT='+CRMDGDATA/crmdg/','+CRMDBDATA/crmdb/' scope=spfile

Alter system set LOG_FILE_NAME_CONVERT='+CRMDGDATA/crmdg/','+CRMDBDATA/crmdb/' scope=spfile

-3. Restart the main library for verification

SQL > shutdown immediate

SQL > startup

-- 4. Generate the current main library parameter file, which is used to prepare the template of the library parameter file

SQL > create pfile='/home/oracle/crmdb.primary' from spfile

Parameter file template:

* .audit_file_dest='/oracle/app/oracle/admin/crmdb/adump'

* .audit_trail='db'

* .cluster_database=true

* .compatible='11.2.0.4.0'

* .control_files='+CRMDBDATA/crmdb/controlfile/current.256.960630751'

* .db_block_size=8192

* .db_create_file_dest='+CRMDBDATA'

* .db_domain=''

* .db_name='crmdb'

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

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

* .open_cursors=300

* .pga_aggregate_target=1073741824

* .processes=1500

* .remote_listener='crmdb-scan:1521'

* .remote_login_passwordfile='exclusive'

* .sessions=1655

* .sga_target=4294967296

Crmdb1.instance_number=1

Crmdb2.instance_number=2

Crmdb1.thread=1

Crmdb2.thread=2

Crmdb1.undo_tablespace='UNDOTBS1'

Crmdb2.undo_tablespace='UNDOTBS2'

* .fal_server='CRMDG_DG'

* .log_archive_config='DG_CONFIG= (crmdb,crmdg)'

* .log_archive_dest_1='LOCATION=+CRMDBARCH VALID_FOR= (ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=crmdb'

* .log_archive_dest_2='SERVICE=CRMDG_DG LGWR ASYNC VALID_FOR= (ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=crmdg'

* .db_file_name_convert='+CRMDGDATA/crmdg/','+CRMDBDATA/crmdb/'

* .log_file_name_convert='+CRMDGDATA/crmdg/','+CRMDBDATA/crmdb/'

* .standby_file_management='AUTO'

4.2 the main library creates STANDBY logs

ALTER DATABASE ADD STANDBY LOGFILE thread 1 group 5 ('+ CRMDBDATA') SIZE 52428800

ALTER DATABASE ADD STANDBY LOGFILE thread 1 group 6 ('+ CRMDBDATA') SIZE 52428800

ALTER DATABASE ADD STANDBY LOGFILE thread 1 group 7 ('+ CRMDBDATA') SIZE 52428800

ALTER DATABASE ADD STANDBY LOGFILE thread 2 group 8 ('+ CRMDBDATA') SIZE 52428800

ALTER DATABASE ADD STANDBY LOGFILE thread 2 group 9 ('+ CRMDBDATA') SIZE 52428800

ALTER DATABASE ADD STANDBY LOGFILE thread 2 group 10 ('+ CRMDBDATA') SIZE 52428800

Principles for creating STANDBY log files:

1. The number of STANDBY log filegroups per instance is greater than the number of online log filegroups

two。 Each STANDBY log file size is the same as the online log file size

4.3 adjust the parameters of the library

Copy a copy of the parameter file generated by the main library and modify it as a template for the parameter file of the standby library.

[oracle@crmdb1 ~] $cp crmdb.primary crmdg.standby

-1. DG independent parameters

* .cluster_database=true

* .compatible='11.2.0.4.0'

* .db_block_size=8192

* .db_name='crmdb'

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

* .open_cursors=300

* .pga_aggregate_target=809500672

* .processes=1500

* .sessions=1655

* .sga_target=2428502016

* .log_archive_max_processes=4

* .remote_login_passwordfile='exclusive'

Crmdb1.undo_tablespace='UNDOTBS1'

Crmdb2.undo_tablespace='UNDOTBS2'

Crmdb1.instance_number=1

Crmdb2.instance_number=2

* .standby_file_management='AUTO'

-- 2. Catalog related parameters

* .audit_file_dest='/oracle/app/oracle/admin/crmdg/adump'

* .control_files='+CRMDGDATA/crmdg/controlfile/current.260.958853369'

* .db_create_file_dest='+CRMDGDATA'

-3. Network service related parameters

* .db_unique_name='crmdg'

* .log_archive_config='DG_CONFIG= (crmdg,crmdb)'

* .fal_server='CRMDB_DG'

* .log_archive_dest_1='LOCATION=+CRMDGARCH VALID_FOR= (ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=crmdg'

* .log_archive_dest_2='SERVICE=CRMDB_DG LGWR ASYNC VALID_FOR= (ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=crmdb'

* .remote_listener='crmdg-cluster01-scan:1521'

* .db_file_name_convert='+CRMDBDATA/crmdb/','+CRMDGDATA/crmdg/'

* .log_file_name_convert='+CRMDBDATA/crmdb/','+CRMDGDATA/crmdg/'

Prepare the library parameter file template:

* .audit_file_dest='/oracle/app/oracle/admin/crmdg/adump'

* .cluster_database=true

* .compatible='11.2.0.4.0'

* .db_block_size=8192

* .db_create_file_dest='+CRMDGDATA'

* .db_name='crmdb'

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

* .open_cursors=300

* .pga_aggregate_target=809500672

* .processes=1500

* .remote_login_passwordfile='exclusive'

* .sessions=1655

* .sga_target=4294967296

* .pga_aggregate_target=1073741824

Crmdb1.thread=1

Crmdb2.thread=2

Crmdb1.instance_number=1

Crmdb2.instance_number=2

Crmdb1.undo_tablespace='UNDOTBS1'

Crmdb2.undo_tablespace='UNDOTBS2'

* .db_unique_name='crmdg'

* .control_files='+CRMDGDATA/crmdg/controlfile/current.260.958853369'

* .log_archive_config='DG_CONFIG= (crmdg,crmdb)'

* .log_archive_dest_1='LOCATION=+CRMDGARCH VALID_FOR= (ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=crmdg'

* .log_archive_dest_2='SERVICE=CRMDB_DG LGWR ASYNC VALID_FOR= (ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=crmdb'

* .remote_listener='crmdg-cluster01-scan:1521'

* .fal_server='CRMDB_DG'

* .standby_file_management='AUTO'

* .db_file_name_convert='+CRMDBDATA/crmdb/','+CRMDGDATA/crmdg/'

* .log_file_name_convert='+CRMDBDATA/crmdb/','+CRMDGDATA/crmdg/'

Note:

Problem: control_files will change after the completion of RMAN DUPLICATE, and after the completion of DUPLICATE, the spfile file used by the standby library contains memory information, so it cannot be used as a production spfile file.

Suggestion: replace the control_files parameter after DUPLICATE with the control_files parameter in the pfile file when creating the standby library, and recreate a new spfile file through the pfile file.

4.4 create a directory required for the standby library

When the instance is started, you need to have an audit log directory, which needs to be created manually on the 2 nodes (crmdg1/crmdg2) of the slave database.

[oracle@crmdg1 ~] $mkdir-p/oracle/ app/oracle/admin/crmdg/adump

4.5 DG parameter check script

SET LINESIZE 160

COL NAME FOR A30

COL VALUE FOR A80

SELECT INST_ID, NAME, VALUE

FROM GV$PARAMETER

WHERE (NAME IN ('cluster_database')

'db_name'

'db_unique_name'

'dg_broker_start'

'dg_broker_config_file1'

'dg_broker_config_file2'

'fal_client'

'fal_server'

'archive_lag_target'

'log_archive_max_processes'

'log_archive_config'

'log_archive_trace'

'db_file_name_convert'

'log_file_name_convert'

'remote_login_password_file'

'standby_file_management'

'redo_transport_user'))

OR (NAME LIKE 'log_archive_dest%' AND UPPER (VALUE)! = UPPER (' ENABLE'))

ORDER BY NAME, INST_ID

5 slave initialization 5.1 set standby ORACLE_SID environment variable

Setting the environment variable parameter ORACLE_SID of each node of the standby database is consistent with that of each node of the main library.

[oracle@crmdg1 ~] $cat / home/oracle/.bash_profile | grep ORACLE_SID

5.2 start the slave database instance to NOMOUNT status

Transfer the previously edited crmdg.standby file to each node of the standby library. Start the slave instance to NOMOUNT status.

[oracle@crmdg1 ~] $sqlplus / as sysdba

SQL > startup nomount pfile='/home/oracle/crmdg.standby'

[oracle@crmdg2 ~] $sqlplus / as sysdba

SQL > startup nomount pfile='/home/oracle/crmdg.standby'

5.3 Test the connection status of the primary / standby database

All nodes of the main and standby libraries are tested.

[oracle@crmdb1 ~] $sqlplus sys/oracle@CRMDG_DG as sysdba

[oracle@crmdb1 ~] $sqlplus sys/oracle@CRMDB_DG as sysdba

5.4 perform DUPLICATE operations to copy the database

Rman target sys/oracle@crmdb_dg auxiliary sys/oracle@crmdg_dg show parameter control_files

SQL > shutdown immediate

-- 2. Edit to create a standby library parameter file and replace the old control file information with the new control file

[oracle@crmdg1 ~] $vi crmdg.standby

* .control_files='+CRMDGDATA/crmdg/controlfile/current.256.958853369'

-3. Create a new spfile file

SQL > create spfile='+CRMDGDATA/crmdg/spfilecrmdb.ora' from pfile='/home/oracle/crmdg.standby'

-- 4. Create a pfile file and connect to a new parameter file

[oracle@crmdg1 ~] $cd $ORACLE_HOME/dbs

[oracle@crmdg1 dbs] $rm spfilecrmdb1.ora

[oracle@crmdg1 dbs] $vi initcrmdb1.ora

Spfile='+CRMDGDATA/crmdg/spfilecrmdb.ora'

5.5.2 standby library node 2 completes the creation of pfile files

[oracle@crmdg2 ~] $cd $ORACLE_HOME/dbs

[oracle@crmdg2 dbs] $vi initcrmdb2.ora

Spfile='+CRMDGDATA/crmdg/spfilecrmdb.ora'

Add the repository to the crs resource

[oracle@crmdg1] $srvctl add database-d crmdg-n crmdb-o $ORACLE_HOME

[oracle@crmdg1] $srvctl add instance-d crmdg-I crmdb1-n crmdg1

[oracle@crmdg1] $srvctl add instance-d crmdg-I crmdb2-n crmdg2

5.7 start the reserve library

[oracle@crmdg1] $srvctl start database-d crmdg

5.8 start Active DataGuard

1. User oracle logs in to crmdg1 host to cancel archiving log files and append

SQL > alter database recover managed standby database cancel

two。 User oracle logs in to the crmdg1 host to synchronize the main database in real-time mode

SQL > ALTER DATABASE RECOVER MANAGED STANDBY DATABASE PARALLEL 8 USING CURRENT LOGFILE DISCONNECT FROM SESSION

SQL > SELECT OPEN_MODE FROM GV$DATABASE

3. Observe the status of log append

SQL > SELECT thread#,max (sequence#) from v$archived_log where applied='YES' GROUP BY THREAD#

SQL > select * from v$archive_gap

6 prepare for library test

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.