RMAN-11003 ORA-32001 Errors When Duplicate Database

Last day I was performing a duplicate from production enviroment to developmente enviroment, when I received the next error;

 
channel: aux3 released channel: aux4 released channel: aux5 released channel: aux6 released channel: aux7 released channel: aux8
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 09/11/2017 17:09:24
RMAN-05501: aborting duplication of target database
RMAN-03015: error occurred in stored script Memory Script
RMAN-03009: failure of sql command on clone_default channel at 09/11/2017 17:09:24
RMAN-11003: failure during parse/execution of SQL statement: alter system set  db_name =  'SAPP' comment= 'Modified by RMAN duplicate' scope=spfile
ORA-32001: write to SPFILE requested but no SPFILE is in use

In this case the problem was the SPFILE, like the error show. I remove the previus clone of database before to duplicate again, but when I removed the previous image it not remove the service,
It is a RAC and I need remove from CRS. Remove the service and repeat the duplicate command again solve the problem.

HTH – Antonio NAVARRO

 

Advertisements

RMAN-06136 ORA-17627 ORA-01017 ORA-17629 Errors When Duplicating DB

Last morning I was improving a duplicate script, from production environment to development, when I get the next error;Last morning I was improving a duplicate script, from production environment to development, when I get the next error;

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 08/31/2017 08:41:54
RMAN-05501: aborting duplication of target database
RMAN-03015: error occurred in stored script Memory Script
RMAN-06136: ORACLE error from auxiliary database: ORA-17629: Cannot connect to the remote database server
ORA-17627: ORA-01017: invalid username/password; logon denied
ORA-17629: Cannot connect to the remote database server

After many probes I have discovered that password file is wrong. I performed a scp from prod to dev. When I send the file again it works fine.

 
HTH – Antonio NAVARRO

ORA-12720, RMAN-06136 And RMAN-05501 Errors When Duplicating Database

Today I was performa a duplicate database when I got the next error.

 
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 08/30/2017 10:32:22
RMAN-05501: aborting duplication of target database
RMAN-06136: ORACLE error from auxiliary database: ORA-01503: CREATE CONTROLFILE failed
ORA-12720: operation requires database is in EXCLUSIVE mode

Okay, it is my fault, I forgot set the cluster_databsae to FALSE. It came from a RAC and have value of TRUE. It is so easy as change this parameter.

HTH – Antonio NAVARRO

Restore Don’t Need DBID If You Use A Tag

The last day a coworker asked me to take a look at a rman script that I had to launch to start recovering a database. He specified the DBID and a TAG to restore the control file. Since the database is not mounted and we are recovering from a backup catalog, at some point we have to tell RMAN which database we want to recover (this catalog has hundreds of databases). Usually the “set dbid” clause is used to tell you which database we are interested in. But he previously made a backup of the database using the TAG clause in the backup database. In this case if you use the TAG you will not have to specify the BDID, since Oracle associates it with said tag.

The script would be as follows

 

connect target /
connect rcvcat backup/xxxxx@catalog;

#### set dbid 325364398  -- Don't neccesary

spool log to '/exp/home/ora12c/util/LOG/restore_cf.log';

run {

         allocate channel t1 type 'SBT_TAPE' MAXPIECESIZE 700G
         parms 'ENV=(NSR_DATA_VOLUME_POOL=Prod_Pool,
                                     NSR_CLIENT=bckcli.domain.one,
                                     NSR_SERVER=bckser.domain.one)';

         restore controlfile from tag backup_migra12c_v2_290617 ;

}

HTH – Antonio NAVARRO

 

ORA-19870 ORA-19504 ORA-17502 ORA-15041 When Restoring Backup

I was restoring a backup to Flex ASM instance when I get the next errorstack;

 
channel t4: restoring datafile 00069 to +CLOUD_PROD_DATA_DISKG
channel t4: restoring datafile 00075 to +CLOUD_PROD_DATA_DISKG
channel t4: restoring datafile 00077 to +CLOUD_PROD_DATA_DISKG
channel t4: reading from backup piece dbwebdb_c0s464nj_1_1
channel t1: ORA-19870: error while restoring backup piece dbclout_c1f432tc_1_1
ORA-19504: failed to create file "+CLOUD_PROD_DATA_DISKG"
ORA-17502: ksfdcre:4 Failed to create file +CLOUD_PROD_DATA_DISKG
ORA-15041: diskgroup "CLOUD_PROD_DATA_DISKG" space exhausted

I checked the space. Usually before start the restore look at the filesystem or ASM to check free space. From asmcmp (I like with -p parameter);

ASMCMD [+] > lsdg
State    Type    Rebal  Sector  Block       AU  Total_MB  Free_MB  Req_mir_free_MB  Usable_file_MB  Offline_disks  Voting_files  Name
MOUNTED  EXTERN  N         512   4096  4194304      5116       52                0              52              0             N  ACFS_CLOUD_PROD_TRZ_DG/
MOUNTED  EXTERN  N         512   4096  4194304      1020       52                0              52              0             N  ACFS_CLOUD_PROD_UDD_DG/
MOUNTED  NORMAL  N         512   4096  1048576     30717    21271            10239            5516              0             Y  OCRVTD_DG/
MOUNTED  EXTERN  N         512   4096  4194304     71676    71544                0           71544              0             N  CLOUD_PROD_ARCCLD1_DG/
MOUNTED  EXTERN  N         512   4096  4194304     71676    71548                0           71548              0             N  CLOUD_PROD_ARCCLD2_DG/
MOUNTED  EXTERN  Y         512   4096  4194304    747476   425468                0          425468              0             N  CLOUD_PROD_DATA_DISKG/
MOUNTED  EXTERN  N         512   4096  4194304      5116     4372                0            4372              0             N  CLOUD_PROD_RC1_DG/
MOUNTED  EXTERN  N         512   4096  4194304      5116     4372                0            4372              0             N  CLOUD_PROD_RC2_DG/

Of course, the column Rebal(ance) has value Y, ummm I suppose a new disk was added to the diskgroup but no rebalanced. With the nexts commands you can rebalance all the DG.

Execute the rebalance of my diskgroup;

rebal CLOUD_PROD_DATA_DISKG

To monitoring rebalancing;

lsop

I tryed the restores again with a happy end.

HTH – Antonio NAVARRO

RMAN-00550 And RMAN-02000 When Execute Rman

Today I have discoverd the next error when I was executing rman;

 
C:\>rman 
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
 wrong message file version (msg 19 not found)

Search for the error at ML/MOS I have seen that the problem can be the NLS_LANG variable. This database is on Windows 2003 Server and Oracle 9.2, of course it is out of all support and logic but it is a requeriment from the application. I have been perform some testcases with the NLS_LANG but without results.

Executing rman command from oracle_home binary files, it works fine;

 
C:\oracle\ora92\bin>rman

Recovery Manager: Release 9.2.0.8.0 - Production

Copyright (c) 1995, 2002, Oracle Corporation.  All rights reserved.

RMAN>

I don’t know where is the problem yet, I Think it is relative to PATH variable but looks good.

HTH – Antonio NAVARRO

RMAN-00554 RMAN-04005 ORA-01031 Errors

Today a coworker ask about the next error when He was configuring a Rman backup;

 
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-04005: error from target database:
ORA-01031: insufficient privileges

The core problem is the ORA-01031: insufficient privileges to perform the backup. Check the next items, it must solve the problem in the majority of cases;

 

i) Verify the password file exits. You can query the password file contain by the next query;

 
   SELECT * FROM V$PWFILE_USERS;
   

 

ii) check if remote_login_passworfile is set to EXCLUSIVE if not you can set by the next command;

 alter system set remote_login_passwordfile = EXCLUSIVE scope=both;

 

HTH – Antonio NAVARRO