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

Considerations for DG-duplicate Operation

Log_file_name_convert='+orcl_DATA/orcldb','+orcl_data/orcldb_dg2'

View the details and status of ASM disks

Select group_number,disk_number,header_status,mode_status,state,total_mb,name,failgroup,path from v$asm_disk

Select name,state from v$asm_diskgroup

-- add ASM disk group

Create diskgroup orcl1_DATA external redundancy disk'/ dev/asm_vdd'

Create diskgroup orcl2_DATA external redundancy disk'/ dev/asm_vdb'

Create diskgroup orcl3_DATA external redundancy disk'/ dev/asm_vdi'

Add disks to a disk group

Alter diskgroup data add disk'/ dev/asm_vde'

Alter diskgroup data add disk'/ dev/asm_vdf'

Alter diskgroup data add disk'/ dev/asm_vdg'

Alter diskgroup data add disk'/ dev/asm_vdh'

Alter diskgroup data add disk'/ dev/asm_vdj'

-- load disk groups

ALTER DISKGROUP DATA MOUNT

13. Pay attention to the configuration of / etc/hostsip address orcldb-dg

14. After duplicate, the synchronization log is not successful, and an error occurred in the query of the main database: SQL > select inst_id,dest_name,status,error from gv$archive_dest_status where dest_name='LOG_ARCHIVE_DEST_2'.

INST_ID

-

DEST_NAME

STATUS ERROR

--

one

LOG_ARCHIVE_DEST_2

ERROR ORA-16191:?

two

LOG_ARCHIVE_DEST_2

ERROR ORA-16191:?

Or

two

LOG_ARCHIVE_DEST_2

ERROR ORA-16058:?

one

LOG_ARCHIVE_DEST_2

ERROR ORA-16058:?

At this time, you need to prepare the database and restart the database instance.

Shutdown immediate

Startup

15. Error occurs during duplicate RMAN-00571: =

RMAN-03002: failure of Duplicate Db command at 03/28/2018 19:36:20

RMAN-05501: aborting duplication of target database

RMAN-03015: error occurred in stored script Memory Script

RMAN-03009: failure of backup command on ORA_DISK_1 channel at 03/28/2018 19:36:20

ORA-00245:?

Try to execute the command manually without script

16. After installing the slave single-node ASM, you need to start the CRS service crsctl start resource ora.diskmon manually

Crsctl status resource-t

Crs_stat-p ora.cssd

Crsctl modify resource "ora.cssd"-attr "AUTO_START=1"-- sets automatic startup

Crs_stat-p ora.diskmon

Crsctl modify resource "ora.diskmon"-attr "AUTO_START=1"-- sets automatic startup

Note: the GRID software is installed using the graphical interface here, and the second installation should be selected.

If you choose the last installation software, some CRS services may be missed, making it impossible to use the asmca command to open the graphical interface

17. Remember to stop the backup 18. After duplicate, the synchronization log is not successful and an error occurred in the query of the main database.

SQL > select inst_id,dest_name,status,error from gv$archive_dest_status where dest_name='LOG_ARCHIVE_DEST_2'

INST_ID

-

DEST_NAME

STATUS ERROR

--

two

LOG_ARCHIVE_DEST_2

ERROR ORA-01033: ORACLE initialization or shutdown in progress

one

LOG_ARCHIVE_DEST_2

ERROR ORA-01033: ORACLE initialization or shutdown in progress

INST_ID

-

DEST_NAME

STATUS ERROR

--

Solution:

1. Check whether the password file of the RAC node is synchronized, and you can copy and overwrite it directly.

2. Check whether the password file of the DG node is synchronized. You can copy the password file of RAC directly to DG to overwrite it.

3. Alter system set log_archive_dest_state_2=enable on the primary node

4. The query status becomes normal VALID again.

SQL > select inst_id,dest_name,status,error from gv$archive_dest_status where dest_name='LOG_ARCHIVE_DEST_2'

INST_ID

-

DEST_NAME

STATUS ERROR

--

two

LOG_ARCHIVE_DEST_2

VALID

one

LOG_ARCHIVE_DEST_2

VALID

INST_ID

-

DEST_NAME

STATUS ERROR

--

Note: check whether the DG log is out of sync due to password problems, and you can also look for verification in alter.log (both the main database and slave database)

19. If you encounter the following error, , maybe the path you set is not LOG_ARCHIVE_DEST_2

It could be LOG_ARCHIVE_DEST_3, so take a good look. Select * from V$ARCHIVE_DEST_STATUS

SQL > select inst_id,dest_name,status,error from gv$archive_dest_status where dest_name='LOG_ARCHIVE_DEST_2'

INST_ID

-

DEST_NAME

STATUS ERROR

--

two

LOG_ARCHIVE_DEST_2

BAD PARAM

one

LOG_ARCHIVE_DEST_2

BAD PARAM

INST_ID

-

DEST_NAME

STATUS ERROR

--

20. After setting synchronization on the DG library, it is found that the log is not synchronized.

SQL > select thread#,process,client_process,sequence#,status from v$managed_standby

THREAD# PROCESS CLIENT_P SEQUENCE# STATUS

--

0 ARCH ARCH 0 CONNECTED

0 ARCH ARCH 0 CONNECTED

0 ARCH ARCH 0 CONNECTED

0 ARCH ARCH 0 CONNECTED

2 MRP0 N/A 2880 APPLYING_LOG

At this time, check the status of the main library

SQL > select inst_id,dest_name,status,error from gv$archive_dest_status where dest_name='LOG_ARCHIVE_DEST_2'

INST_ID

-

DEST_NAME

STATUS ERROR

--

one

LOG_ARCHIVE_DEST_2

ERROR ORA-03135: connection lost contact

two

LOG_ARCHIVE_DEST_2

ERROR ORA-03135: connection lost contact

INST_ID

-

DEST_NAME

STATUS ERROR

--

It is useless to re-enable in the main library.

Alter system set log_archive_dest_state_2=ENABLE

Check the DG standby listening and find that the listening has not been started.

Su-oracle

Lsnrctl start

Then check again and find that it is still out of sync.

Check status of main database

SQL > select inst_id,dest_name,status,error from gv$archive_dest_status where dest_name='LOG_ARCHIVE_DEST_2'

INST_ID

-

DEST_NAME

STATUS ERROR

--

one

LOG_ARCHIVE_DEST_2

ERROR ORA-12543: TNS:destination host unreachable

two

LOG_ARCHIVE_DEST_2

ERROR ORA-12543: TNS:destination host unreachable

INST_ID

-

DEST_NAME

STATUS ERROR

--

At this time, check the DG repository and find that iptables-L finds that the firewall is blocked.

Iptables-F clearance

Problem solving

21. After setting synchronization on the DG library, it is found that the log is not synchronized.

SQL > select thread#,process,client_process,sequence#,status from v$managed_standby

THREAD# PROCESS CLIENT_P SEQUENCE# STATUS

--

0 ARCH ARCH 0 CONNECTED

0 ARCH ARCH 0 CONNECTED

0 ARCH ARCH 0 CONNECTED

0 ARCH ARCH 0 CONNECTED

2 MRP0 N/A 2880 APPLYING_LOG

At this time, check the status of the main library

SQL > select inst_id,dest_name,status,error from gv$archive_dest_status where dest_name='LOG_ARCHIVE_DEST_2'

INST_ID

-

DEST_NAME

STATUS ERROR

--

two

LOG_ARCHIVE_DEST_2

DISABLED ORA-16057: server not in Data Guard configuration

one

LOG_ARCHIVE_DEST_2

DISABLED ORA-16057: server not in Data Guard configuration

INST_ID

-

DEST_NAME

STATUS ERROR

--

When I see this error report, I'm going to check log_archive_config.

Both the main and standby libraries should be checked, because they have to be consistent.

Main library view

SQL > show parameter log_archive_config

NAME TYPE VALUE

-

Log_archive_config string DG_CONFIG=orcldb,orcldbdg3)

Prepare the library for viewing

SQL > show parameter log_archive_config

NAME TYPE VALUE

-

Log_archive_config string DG_CONFIG= (orcldbdg3,orcldbdg)

It's really inconsistent. Modify it.

SQL > alter system set log_archive_config='DG_CONFIG= (orcldbdg3,orcldb)'

Go to the main library and re-enable.

Alter system set log_archive_dest_state_2=ENABLE

When I went back to the reserve database, I found that the synchronization log had been enabled.

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.