Shulou(Shulou.com)05/31 Report--

This article mainly explains "what is the method to deal with common problems in DG construction". The explanation content in this article is simple and clear, and it is easy to learn and understand. Please follow the ideas of Xiaobian to study and learn "what is the method to deal with common problems in DG construction" together.

1. ORA-09925 error

Error 1:

connected to auxiliary database (not started)released channel: prmy1released channel: prmy2released channel: prmy3released channel: prmy4RMAN-00571: ===========================================================RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============RMAN-00571: ===========================================================RMAN-03002: failure of Duplicate Db command at 07/27/2018 10:48:43RMAN-05501: aborting duplication of target databaseRMAN-03015: error occurred in stored script Memory ScriptRMAN-04014: startup failed: ORA-09925: Unable to create audit trail fileLinux-x86_64 Error: 2: No such file or directoryAdditional information: 9925

Reason: adump file does not exist

Solution:

mkdri -p $ORACLE_HOME/admin/db_unique_name/adump

For example:

mkdir -p $ORACLE_BASE/admin/mssdbdg/adump

2. ERROR IN UNIT-05537

Error 2:

Starting Duplicate Db at 27-JUL-18released channel: prmy1released channel: prmy2released channel: prmy3released channel: prmy4released channel: stbyRMAN-00571: ===========================================================RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============RMAN-00571: ===========================================================RMAN-03002: failure of Duplicate Db command at 07/27/2018 10:57:28RMAN-05501: aborting duplication of target databaseRMAN-05537: DUPLICATE without TARGET connection when auxiliary instance is started with spfile cannot use SPFILE clause

Cause: Backup library runs duplicate script, spfile file is not deleted, restart database to nomount

Solution: Delete spfile file first, restart database to nomount

ORA-17628: Oracle error 19505

contents of Memory Script:{ backup as copy current controlfile for standby auxiliary format '/ORADATA/RESNETDBDG/control01.ctl'; restore clone primary controlfile to '/ORADATA/fast_recovery_area/RESNETDBDG/control02.ctl' from '/ORADATA/RESNETDBDG/control01.ctl';}executing Memory ScriptStarting backup at 26-JUL-2018 18:42:20using channel ORA_DISK_1channel ORA_DISK_1: starting datafile copycopying standby control fileRMAN-00571: ===========================================================RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============RMAN-00571: ===========================================================RMAN-03002: failure of Duplicate Db command at 07/26/2018 18:42:21RMAN-05501: aborting duplication of target databaseRMAN-03015: error occurred in stored script Memory ScriptRMAN-03009: failure of backup command on ORA_DISK_1 channel at 07/26/2018 18:42:21ORA-17628: Oracle error 19505 returned by remote Oracle server

Reason: The destination path does not exist. Either the file system path does not exist or the permissions are insufficient. If ASM is used, please confirm whether the disk group exists and whether the permissions of the disk are correct.

4. ORA-01017 error

This is a password error report. SYS user login uses the password file authentication method, so it is necessary to ensure that the password file can be read and written, and the ORACLE_SID in the password file name corresponds to the ORACLE_SID in the monitoring. Password errors can occur in many ways.

4.1 The first time I set up the Times password was wrong.

4.1.1 Inconsistent password files

Confirm that the Oracle user has write permissions by changing the password at one node in the primary repository and copying the password file for that node to all other nodes, including all nodes in the primary repository and all nodes in the backup repository.

4.1.2 The target end reports password error

4.1.1 has been completed, but the password error is still reported. At this time, it is very likely that the database ORACLE_SID in the static monitoring is inconsistent with the SID in the password file.

5. Log not transmitted to backup database Analysis method

SELECT DESTINATION, STATUS, ERROR FROM V$ARCHIVE_DEST WHERE TARGET='STANDBY';

Check the ERROR code and solve the problem according to the ERROR code.

6. ORA-00845 error report

RMAN-00571: ===========================================================RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============RMAN-00571: ===========================================================RMAN-03002: failure of Duplicate Db command at 07/30/2018 02:22:10RMAN-03015: error occurred in stored script Memory ScriptRMAN-04014: startup failed: ORA-00845: MEMORY_TARGET not supported on this system

Since AMM function is used, but SHM size is not as large as AMM, so SHM needs to be re-specified and the same size as AMM.

mount -o remount,default,size=102G /dev/shm

Modify the values in/etc/fstab

7, monitoring configuration is OK, sqlplus test is OK, tnsping is OK, but still report the following error

RMAN-00571: ===========================================================RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============RMAN-00571: ===========================================================RMAN-03002: failure of Duplicate Db command at 08/05/2018 02:30:01RMAN-05501: aborting duplication of target databaseRMAN-03015: error occurred in stored script Memory ScriptRMAN-03009: failure of backup command on prmy2 channel at 08/05/2018 02:30:01ORA-17629: Cannot connect to the remote database serverORA-17627: ORA-12154: TNS:could not resolve the connect identifier specifiedORA-17629: Cannot connect to the remote database serverRMAN>

Solution: Make a copy of tnsname.ora's contents under grid's network/admin. RMAN Active Duplicate on RAC fails with ORA-17629 and ORA-17627: ORA-12154 (Doc ID 1982003.1)

8. Duplicate error. The reason is that there are two data files in the original library that do not use OMF format and cannot be passed.

RMAN-00571: ===========================================================RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============RMAN-00571: ===========================================================RMAN-03002: failure of Duplicate Db command at 08/05/2018 20:42:25RMAN-05501: aborting duplication of target databaseRMAN-03015: error occurred in stored script Memory ScriptRMAN-03009: failure of backup command on prmy4 channel at 08/05/2018 20:01:35ORA-17628: Oracle error 19505 returned by remote Oracle serverRMAN-03009: failure of backup command on prmy4 channel at 08/05/2018 20:01:20ORA-17628: Oracle error 19505 returned by remote Oracle server

Solution: View Error Code: MOS 1331986.1

Note that before doing this, make sure that it is not an OMF file. If not, first create a directory in the asm sublayer or write the sublayer directory in the script.

Thank you for reading, the above is the content of "DG build common problem handling method is what", after the study of this article, I believe that we have a deeper understanding of DG build common problem handling method is what this problem, the specific use of the situation also needs to be verified by practice. Here is, Xiaobian will push more articles related to knowledge points for everyone, welcome to pay attention!

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.