Rman duplication fails with RMAN-00600

Hi All,
I'm trying to perform a database duplication from a prod server to a non prod one with ORacle 11gR2.
I'm performing a backup-based duplication without target connection from DEV3 database to DEV1 database. I followed the steps mentionned in the "backup & Recovery Guide" http://download.oracle.com/docs/cd/E11882_01/backup.112/e10642/rcmdupdb.htm
Here are the steps I followed:
1. I configured my spfile of the auxiliary database like the target one. I also added these lines to change the location of the restores:
SQL> alter system set log_file_name_convert='/u04/DEV3/rdo','/u04/DEV1/rdo','/u03/DEV3/rdo','/u03/DE V1/rdo','/u02/DEV3/rdo','/u02/DEV1/rdo' scope=spfile;
SQL> alter system set db_file_name_convert='/u04/DEV3/rdo','/u04/DEV1/rdo','/u03/DEV3/rdo','/u03/DEV1/rdo','/u02/DEV3/rdo','/u02/DEV1/rdo','/u02/DEV3/dbf/DEV3','/u02/DEV1/dbf/DEV1' scope=spfile;
2. I then shutdown the database, and start it in nomount mode.
3. I connect to the auxiliary database, and the recovery catalog
4. I run the following rman duplication command:
RUN{
DUPLICATE DATABASE DEV3 to DEV1;
The restore succeeds but at the end, the recovery ends with the following error:
channel ORA_AUX_DISK_6: reading from backup piece /RMAN/DEV3/DEV3_0_14:27:01-05-31-2011_2_138.rman
channel ORA_AUX_DISK_4: piece handle=/RMAN/DEV3/DEV3_0_14:27:01-05-31-2011_2_136.rman tag=LVL0_DB_BKP
channel ORA_AUX_DISK_4: restored backup piece 2
channel ORA_AUX_DISK_4: restore complete, elapsed time: 02:24:10
channel ORA_AUX_DISK_6: piece handle=/RMAN/DEV3/DEV3_0_14:27:01-05-31-2011_2_138.rman tag=LVL0_DB_BKP
channel ORA_AUX_DISK_6: restored backup piece 2
channel ORA_AUX_DISK_6: restore complete, elapsed time: 02:25:09
Finished restore at 06/06/11 15:22:58
contents of Memory Script:
catalog clone datafilecopy "/u02/DEV1/dbf/DEV1/undotbs01.dbf";
switch clone datafile 3 to datafilecopy
"/u02/DEV1/dbf/DEV1/undotbs01.dbf";
switch clone datafile all;
executing Memory Script
cataloged datafile copy
datafile copy file name=/u02/DEV1/dbf/DEV1/undotbs01.dbf RECID=70 STAMP=753117778
datafile 3 switched to datafile copy
input datafile copy RECID=70 STAMP=753117778 file name=/u02/DEV1/dbf/DEV1/undotbs01.dbf
datafile 1 switched to datafile copy
input datafile copy RECID=71 STAMP=753117780 file name=/u02/DEV1/dbf/DEV1/system01.dbf
datafile 2 switched to datafile copy
input datafile copy RECID=72 STAMP=753117780 file name=/u02/DEV1/dbf/DEV1/sysaux01.dbf
contents of Memory Script:
set until scn 7241504550365;
recover
clone database
delete archivelog
executing Memory Script
executing command: SET until clause
Starting recover at 06/06/11 15:23:15
using channel ORA_AUX_DISK_1
using channel ORA_AUX_DISK_2
using channel ORA_AUX_DISK_3
using channel ORA_AUX_DISK_4
using channel ORA_AUX_DISK_5
using channel ORA_AUX_DISK_6
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00601: fatal error in recovery manager
RMAN-03012: fatal error during compilation of command
RMAN-03028: fatal error code for command recover : 600
RMAN-00600: internal error, arguments [8029] [1] [] [] []
Can someone please help me resolve this issue???it's quite urgent.
Thank you,
Farah

I am facing same error, did any of you find a resolution yet?
contents of Memory Script:
set until scn 7243533883622;
recover
clone database
delete archivelog
executing Memory Script
executing command: SET until clause
Starting recover at 10/12/11 19:33:12
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00601: fatal error in recovery manager
RMAN-03012: fatal error during compilation of command
RMAN-03028: fatal error code for command recover : 600
RMAN-00600: internal error, arguments [8029] [1] [] [] []
Wed Oct 12 19:33:14 CEST 2011 Remove the lock file
ERROR: RMAN FAILUR
I see many kblockd processes, can this be an indication:
applprod@gvaebsdb3:~ $ ps -ef|grep kblockd
root 231 211 0 Oct05 ? 00:00:00 [kblockd/0]
root 232 211 0 Oct05 ? 00:00:00 [kblockd/1]
root 233 211 0 Oct05 ? 00:00:00 [kblockd/2]
root 234 211 0 Oct05 ? 00:00:00 [kblockd/3]
root 235 211 0 Oct05 ? 00:00:00 [kblockd/4]
root 236 211 0 Oct05 ? 00:00:00 [kblockd/5]
root 237 211 0 Oct05 ? 00:00:00 [kblockd/6]
root 238 211 0 Oct05 ? 00:00:00 [kblockd/7]
root 239 211 0 Oct05 ? 00:00:00 [kblockd/8]
root 240 211 0 Oct05 ? 00:00:00 [kblockd/9]
root 241 211 0 Oct05 ? 00:00:00 [kblockd/10]
root 242 211 0 Oct05 ? 00:00:00 [kblockd/11]
root 243 211 0 Oct05 ? 00:00:00 [kblockd/12]
root 244 211 0 Oct05 ? 00:00:00 [kblockd/13]
root 245 211 0 Oct05 ? 00:00:00 [kblockd/14]
root 246 211 0 Oct05 ? 00:00:00 [kblockd/15]
Thanks,
Horia

Similar Messages

Tablespace Point in Time Recovery fails with RMAN-06026:

I have cataloged with RMAN the datafiles from Snapshot backup. Still it fails with the following error.
RMAN> RECOVER TABLESPACE TSPC UNTIL TIME "to_date('03-apr-2013 02:18:00','dd-mon-yyyy hh24:mi:ss')" AUXILIARY DESTINATION '/tmp/auxpran';
Starting recover at 03-APR-13
using channel ORA_DISK_1
RMAN-05026: WARNING: presuming following set of tablespaces applies to specified point-in-time
List of tablespaces expected to have UNDO segments
Tablespace SYSTEM
Tablespace UNDOTBS1
Creating automatic instance, with SID='Ebgt'
initialization parameters used for automatic instance:
db_name=ORCL
db_unique_name=Ebgt_tspitr_ORCL
compatible=11.2.0.0.0
db_block_size=8192
db_files=200
sga_target=280M
processes=50
db_create_file_dest=/tmp/auxpran
log_archive_dest_1='location=/tmp/auxpran'
#No auxiliary parameter file used
starting up automatic instance ORCL
Oracle instance started
Total System Global Area 292933632 bytes
Fixed Size 1336092 bytes
Variable Size 100666596 bytes
Database Buffers 184549376 bytes
Redo Buffers 6381568 bytes
Automatic instance created
Running TRANSPORT_SET_CHECK on recovery set tablespaces
TRANSPORT_SET_CHECK completed successfully
contents of Memory Script:
# set requested point in time
set until time "to_date('03-apr-2013 02:18:00','dd-mon-yyyy hh24:mi:ss')";
# restore the controlfile
restore clone controlfile;
# mount the controlfile
sql clone 'alter database mount clone database';
# archive current online log
sql 'alter system archive log current';
# avoid unnecessary autobackups for structural changes during TSPITR
sql 'begin dbms_backup_restore.AutoBackupFlag(FALSE); end;';
executing Memory Script
executing command: SET until clause
Starting restore at 03-APR-13
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID=19 device type=DISK
channel ORA_AUX_DISK_1: restoring control file
channel ORA_AUX_DISK_1: copied control file copy
input file name=/tmp/auxpran/controlbc.ctl
output file name=/tmp/auxpran/ORCL/controlfile/o1_mf_8opkv8v4_.ctl
Finished restore at 03-APR-13
sql statement: alter database mount clone database
sql statement: alter system archive log current
sql statement: begin dbms_backup_restore.AutoBackupFlag(FALSE); end;
contents of Memory Script:
# set requested point in time
set until time "to_date('03-apr-2013 02:18:00','dd-mon-yyyy hh24:mi:ss')";
# set destinations for recovery set and auxiliary set datafiles
set newname for clone datafile 1 to new;
set newname for clone datafile 3 to new;
set newname for clone datafile 2 to new;
set newname for clone tempfile 1 to new;
set newname for datafile 5 to
"+DG_DATA/orcl/datafile/tspc.268.811733685";
# switch all tempfiles
switch clone tempfile all;
# restore the tablespaces in the recovery set and the auxiliary set
restore clone datafile 1, 3, 2, 5;
switch clone datafile all;
executing Memory Script
executing command: SET until clause
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
renamed tempfile 1 to /tmp/auxpran/ORCL/datafile/o1_mf_temp_%u_.tmp in control file
Starting restore at 03-APR-13
using channel ORA_AUX_DISK_1
One or more auxiliary set datafiles could not be removed
Removing automatic instance
shutting down automatic instance
database dismounted
Oracle instance shut down
Automatic instance removed
auxiliary instance file /tmp/auxpran/ORCL/controlfile/o1_mf_8opkv8v4_.ctl deleted
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 04/03/2013 02:32:55
RMAN-03015: error occurred in stored script Memory Script
RMAN-06026: some targets not found - aborting restore
RMAN-06023: no backup or copy of datafile 2 found to restore
RMAN-06023: no backup or copy of datafile 3 found to restore
RMAN-06023: no backup or copy of datafile 1 found to restore
Could anyone please reply ASAP?
Regards,
Pranam

I had created a snapshot of the database(datafiles and archivelogs) and cataloged them.
CATALOG START WITH "+TBL_DG_DATA/ORCL/DATAFILE/" NOPROMPT;
catalog start with "+DG_ARCH/ORCL/ARCHIVELOG/" NOPROMPT;
The time i gave was after the snapshot was created.
When it failed the first time I created another controlfile using
sql "alter database backup controlfile to ''/tmp/auxpran/controlbc.ctl''";
And ran the recover command after the time after i generated this controlfile. Changed nothing else. TSPITR completed successfully. But it had failed first time. Cannot figure how it ran the second time but failed the first time.
Removing automatic instance
Automatic instance removed
auxiliary instance file /tmp/auxpran/ORCL/datafile/o1_mf_temp_8opndd87_.tmp deleted
auxiliary instance file /tmp/auxpran/ORCL/onlinelog/o1_mf_3_8opnd1o6_.log deleted
auxiliary instance file /tmp/auxpran/ORCL/onlinelog/o1_mf_2_8opncy32_.log deleted
auxiliary instance file /tmp/auxpran/ORCL/onlinelog/o1_mf_1_8opncv7d_.log deleted
auxiliary instance file /tmp/auxpran/ORCL/datafile/o1_mf_sysaux_8opn516p_.dbf deleted
auxiliary instance file /tmp/auxpran/ORCL/datafile/o1_mf_undotbs1_8opn4j14_.dbf deleted
auxiliary instance file /tmp/auxpran/ORCL/datafile/o1_mf_system_8opmyvly_.dbf deleted
auxiliary instance file /tmp/auxpran/ORCL/controlfile/o1_mf_8opmy14q_.ctl deleted
Finished recover at 03-APR-13

Rman command fails with "RMAN-00554: initialization of internal RMAN"

Hi
I am at cross roads with no direction. 2 things and most like cause for the issue is same
1)rman target rman1/rman1@ppmqa
Recovery Manager: Release 11.2.0.1.0 - Production on Thu Dec 16 10:34:46 2010
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
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
2) sqlnet userid/passwd@db1 "/as sysdba" works some times and fails with insufficient privileges" some times
ppmqa1 10:24 AM sqrac202a:/oracle/base/diag/tnslsnr/sqrac202a/listener/trace > sqlplus rman1/rman1@ppmqa1 "as sysdba"
SQL*Plus: Release 11.2.0.1.0 Production on Thu Dec 16 10:24:55 2010
Copyright (c) 1982, 2009, Oracle. All rights reserved.
ERROR:
ORA-01031: insufficient privileges
ppmqa1 10:24 AM sqrac202a:/oracle/base/diag/tnslsnr/sqrac202a/listener/trace > sqlplus rman1/rman1@ppmqa1 "as sysdba"
SQL*Plus: Release 11.2.0.1.0 Production on Thu Dec 16 10:24:57 2010
Copyright (c) 1982, 2009, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
Data Mining and Real Application Testing options
SQL>
Information on environment and let me know if you need or know any more details... thanks in advance.
CRS Version 11201 and so DB
current parameters:
SQL> show parameter remote
NAME TYPE VALUE
remote_dependencies_mode string TIMESTAMP
remote_listener string sqrac202-scan.frxntnyc.frx2.co
m:1521
remote_login_passwordfile string EXCLUSIVE
remote_os_authent boolean FALSE
remote_os_roles boolean FALSE
result_cache_remote_expiration integer 0
SQL> select * from v$pwfile_users
USERNAME SYSDB SYSOP SYSAS
SYS TRUE TRUE FALSE
RMAN1 TRUE TRUE FALSE
sqlnet.ora from GRID Home
NAMES.DIRECTORY_PATH= (TNSNAMES, EZCONNECT)
ADR_BASE = /oracle/base
#################################

I found solution just now, this is very simple i was not aware this but this is how it working
Hope this helps
I granted sysdba from node A but not from node B, thinking that if you grant any privilege at instance level that is applicable to db level but that is not the case with sysdba privs
so i need to grant it from both nodes A and B.
here is the output
test case
initially no entry for instance 2
1) select * from gv$pwfile_users;
INST_ID USERNAME SYSDB SYSOP SYSAS
2 SYS TRUE TRUE FALSE
1 SYS TRUE TRUE FALSE
1 RMAN1 TRUE TRUE FALSE
2) grant sysdba to rman1 -- this I did at NODE B or instance 2
3) SQL> select * from gv$pwfile_users;
INST_ID USERNAME SYSDB SYSOP SYSAS
2 SYS TRUE TRUE FALSE
2 RMAN1 TRUE FALSE FALSE
1 SYS TRUE TRUE FALSE
1 RMAN1 TRUE TRUE FALSE
4) I am able to connect remotely
C:\Documents and Settings\kthoka> sqlplus rman1/rman1@ppmqa "as sysdba"
SQL*Plus: Release 10.2.0.3.0 - Production on Thu Dec 16 13:59:20 2010
Copyright (c) 1982, 2006, Oracle. All Rights Reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, Real Application Clusters, Automatic Storage Management
OLAP,
Data Mining and Real Application Testing options
SQL> select instance_name from v$instance;
INSTANCE_NAME
ppmqa2
5) rman also working fine
ppmqa 03:00 PM sqrac202a:/oracle/NSQ/112_64/dbs > rman target rman1/rman1@ppmqa
Recovery Manager: Release 11.2.0.1.0 - Production on Thu Dec 16 15:00:32 2010
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: PPMQA (DBID=774170541)
RMAN> exit
Recovery Manager complete.

Rman archivelog backup fails with rman-03002,ora-19563

Hi,
D:\ Oracle- -\BIN\RMAN TARGET / NOCATALOG
RMAN> backup archivelog all;
RMAN-03002: Error with backup command on 06-25-2013
ORA-19563: Header-Validation is not successful.
fails with the given errors.
11.2.0.2 PROD DB on Windows Server 2008 R2 Enterpriise.
When I issue BACKUP INCREMENTAL LEVEL 0 DATABASE; it works fine. but with archivelog it is creating problems. Unfortunatly, I have not found exactly the same problem on google and on Oracle support.
The DB is using INIT.ORA and last time when I switched the mode to archive log mode I set the parameter like SCOPE=MEMORY as SPFILE was not in use and ALTER SYSTEM with SCOPE=BOTH FRA destination and size, but after the DB restarting of course that setting is gone and I am having these problems.
Please suggest.
Thanks a lot.
Best Regards,

Hi,
Thanks a lot.
I don't think that archivelogs were relocated, except I changed the location yesterday.
As I wrote at the start that because of INIT.ORA file being in use instead of SPFILE. I set DB_RECOVERY_FILE_DEST, DB_RECOVERY_DEST_SIZE after changing the DB mode to ARCHIVELOG, but DB was restarted by somebody else, and as the parameter changing was NOT PERMANENT, it rollback.
LOG_ARCHIVE_DEST was set to d:\oradata\db with archivelog mode but db_recovery_file_dest and size was set to 0. Now here, I have no idea that whether archivelogs were not being backed up or deleted physically, but I guess that as log_archive_dest parameter is deprecated and mode is set to archivelog with no real ARCHIVELOG DESTINATION. Please correct me if I am wrong or totally wrong :-)
I performed DELETED EXPIRED ARCHIVELOG ALL, and it deleted 49 EXPIRED objects.
Now CROSSCHECK ARCHIVELOG ALL and LIST ARCHIVELOG ALL shows nothing.
LIST BACKUP OF ARCHIVELOG ALL has of course those 49 archivelog gap.
Could you please tell the impacts of those 49 missing archivelogs. Retention policy is set to 14 days. I mean the risk is for 14 days right? As anyhow, the older backups are being DELETED according to retention policy of RMAN.

ORA-27369:job of type EXECUTABLE failed with exit code + rman???

Hi all,
I was trying to execute job from 10G (10.2.01) Enterprise Manager Database Control, and got error below
ORA-27369:job of type EXECUTABLE failed with exit code: Network is down STANDARD_ERROR="/home/oracle/scripts/backup/backupset_full:rman: command not found"
Here is the file contents of backupset_full
#!usr/bin/bash
rman <<EOF
connect catalog rman/rman@catrcv
connect target sys/sys@test
run{
EXECUTE SCRIPT global_backup_full;
quit
EOF
Here is the file content of global_backup_full script
CREATE SCRIPT global_backup_full
shutdown immediate;
startup mount;
allocate channel d1 device type DISK;
backup as compressed backupset database;
release channel d1;
NOTE: I am running on bash shell environment.
THANK YOU VERY MUCH in advance.
Rich,

You need to set ORACLE_HOME inside backupset_full script and possibly change rman to $ORACLE_HOME/bin/rman
#!usr/bin/bash
export ORACLE_HOME=<your_oracle_home _directory>
$ORACLE_HOME/bin/rman <<EOF
connect catalog rman/rman@catrcv
connect target sys/sys@test
run{
EXECUTE SCRIPT global_backup_full;
quit
EOF
Here is the file content of global_backup_full script
CREATE SCRIPT global_backup_full
shutdown immediate;
startup mount;
allocate channel d1 device type DISK;
backup as compressed backupset database;
release channel d1;
}

Command fail with RMAN-02001

Hi everyone.
I have a command that I wish to insert into a RMAN script. It' actually an OS command, renaming a file (the log file generated by the script). Here's the command I'm using:
RMAN> HOST 'mv /oracle/backup/database_backups/BackupLog/rman_backup.log
/oracle/backup/database_backups/BackupLog/"rman_backup"`date '+_%Y%m%d_%H%M%S'`".log"';When executing, it fails with this error:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01006: error signaled during parse
RMAN-02001: unrecognized punctuation symbol "+"I tried different qutations to mark that "+" as a special character, but couldn't find the right way to get rid of the error.
If anyone else already met this problem, please let me know how to solve it.
Thanks.

Razvan Balu wrote:
Hi everyone.
I have a command that I wish to insert into a RMAN script. It' actually an OS command, renaming a file (the log file generated by the script). Here's the command I'm using:
RMAN> HOST 'mv /oracle/backup/database_backups/BackupLog/rman_backup.log
/oracle/backup/database_backups/BackupLog/"rman_backup"`date '+_%Y%m%d_%H%M%S'`".log"';When executing, it fails with this error:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01006: error signaled during parse
RMAN-02001: unrecognized punctuation symbol "+"I tried different qutations to mark that "+" as a special character, but couldn't find the right way to get rid of the error.
If anyone else already met this problem, please let me know how to solve it.
Thanks.Could you try it like this:
HOST 'mv /oracle/backup/database_backups/BackupLog/rman_backup.log /oracle/backup/database_backups/BackupLog/rman_backup `date +_%Y%m%d_%H%M%S`.log';
Best regards
Gokhan Atil
If this question is answered, please mark the thread as closed and assign points where earned. Thanks

RMAN fails with 1073741819

Hi,
Recently one of my database backup failed and i can't seems to find out the problem. Hope somebody can help me. The error comes only on backup to tape, not on backup to disk, so it could be something about TSM
Error message:
Recovery Manager: Release 8.1.7.4.1 - Production
RMAN-06005: connected to target database: CREP (DBID=2011042218)
RMAN-06008: connected to recovery catalog database
RMAN> Run
2> {
3> Allocate Channel T1 Type 'sbt_tape';
4> backup
5> filesperset 5
6> format 'df_%t_%s_%p'
7> database;
8> }
RMAN-03022: compiling command: allocate
RMAN-03023: executing command: allocate
RMAN-03026: error recovery releasing channel resources
Oracle8 RMAN command failed with exit status - 1073741819

Check the TSM logs for errors, the error stack here doesn't show any useful information (only informational messages and an undefined exit code). This is an 8i problem, later releases transfer much better messages from the media management software.

Backup fails with RMAN-08132

Hi
I'm trying to run rman backup on standby db. It seems like the backup completes but i'm getting the following message at the end. I cant issue commands like "list backup;" Fails with the same error. Tried searching metalink without any luck. Anyone seen this before??
Finished backup at 25-APR-07
RMAN-08132: WARNING: cannot update recovery area reclaimable file list
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of REFAF command on default channel at 04/25/2007 12:30:45
ORA-00604: error occurred at recursive SQL level 1
ORA-01219: database not open: queries allowed on fixed tables/views only
Any clues from you sharp-eyed dba's out there would be greatly appricated!!

There's an entry on metalink:
Known RMAN issues in Oracle10g
Doc ID: Note:363409.1
Inside this note search for 'WARNING: cannot update recovery area reclaimable file list'
Werner

RMAN backup got failed with the error ORA-19566

Hi,
One of database, while taking backup using RMAN, it failed with the following error:
RMAN-03009: failure of backup command on DISK4 channel at 11/28/2012 09:47:29
ORA-19566: exceeded limit of 0 corrupt blocks for file <faile_name>
I used DBV to identify the number of blocks corrupted.
I referred the Metalink iD 457422.1 & 336133.1. But it did not help since the corrupted blocks have got object in it.
I could able to find the object as well. it is one of the table in the datafile.
I used 'ALTER TABLE ... MOVE..' command to see if that helps. But again getting the same error while taking the backup and corrupted blocks still exists.
DB Version : 10.2.0.5
OS Version : RHEL 5.6
Please help me out to get this fixed.

Here it is:
SQL> Select * from v$database_block_corruption ;
FILE# BLOCK# BLOCKS CORRUPTION_CHANGE# CORRUPTION_TYPE
13 3988352 128 0 ALL ZERO

RMAN backup failes with ORA-19624 occurred during call to DBMS_BACKUP_RESTO

RMAN backup up failes with following errors. It works some times and then failes. When it failes then if i un install and reinstall Oralec agent and Backup cliet then it start working OK for few days and then again start getting error. See the messages below...
Recovery Manager: Release 8.1.7.0.0 - Production
RMAN-06005: connected to target database: MIMSDEVH (DBID=3525230908)
RMAN-06008: connected to recovery catalog database
RMAN> RUN { 2> execute script tapelevel0; 3> }
RMAN-03021: executing script: tapelevel0
RMAN-03022: compiling command: allocate
RMAN-03023: executing command: allocate
RMAN-03026: error recovery releasing channel resources
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03015: error occurred in stored script tapelevel0
RMAN-03007: retryable error occurred during execution of command: allocate
RMAN-07004: unhandled exception during command execution on channel ch00
RMAN-10035: exception raised in RPC: ORA-19554: error allocating device, device type: SBT_TAPE, device name:
ORA-19557: device error, device type: SBT_TAPE, device name:
ORA-27000: skgfqsbi: failed to initialize storage subsystem (SBT) layer
ORA-19511: SBT error = 4110, errno = 0, BACKUP_DIR environment variable is not set
RMAN-10031: ORA-19624 occurred during call to DBMS_BACKUP_RESTORE.DEVICEALLOCATE
Send me some solution...

hi,
what is your backup script
can you post back the result of the command
show all;
from the rman command prompt
regards
Alan

RMAN-00600 Error during Duplicate

RDBMS Version: 8.1.6
Operating System and Version: NT 4.0
Error Number (if applicable): RMAN-00600
Product: Recovery Manager
Product Version: 8.1.6
RMAN Duplicate Database Error (RMAN-00600)
While running the following command:
run {
allocate auxiliary channel ch1 type disk;
allocate auxiliary channel ch2 type disk;
duplicate target database to db1backup nofilenamecheck;
I get the following errors:
RMAN-03022: compiling command: Duplicate Db
RMAN-00571: =========================================================
RMAN-00569: ================ ERROR MESSAGE STACK FOLLOWS ============
RMAN-00571: =========================================================
RMAN-00601: fatal error in recovery manager
RMAN-03012: fatal error during compilation of command
RMAN-03028: fatal error code: 600
RMAN-03013: command type: Duplicate Db
RMAN-00600: internal error, arguments [14036] [-11] [29] [
CHARACTER SET %s
] [WE8ISO8859P1]
Any ideas as to what may be causing this? I have successfully backed up the target database, the connections to the target and auxiliary databases are fine, and I'm using a controlfile vs. a catalog.
Mike McAndrew
[email protected]
null

Hi
Duplicate databases with RMAN is not as simple as it seems, look at message colled "Duplicate database error with RMAN"
This maybe could help you.
Anyway, I saw the message:
"internal error, arguments [14036] [-11] [29] [CHARACTER SET %s] [WE8ISO8859P1] "
What NLS configuration have you?
A10!
null

RMAN-00600: internal error, arguments [8201]

Hi,
on 10g R2 on a win 2003 server we had follwing error for RMAN backup :
RMAN-00600: internal error, arguments [8201] [] [] [] []we looked at metalink note : 412786.1
that says :
There is mismatch between the information stored in the Controlfile and rman Catalogand did RMAN> resync catalog; that did not resolve the problem.
We created another RMAN schema which means a new catalog. Then it is difficult to believe
that the new catalog was not syncronized with control file. But again exactly the same error :
RMAN-00600: internal error, arguments [8201] [] [] [] []
Why again the same error with a new catalog ?
Thanks.

Thank you Werner. I read the discussion. How about this work arround in Bug No. 5916459 :
Workaround ========== . Modify ?/admin/recover.bsq as follows and upgrade recovery catalog schema .
using UPGRADE CATALOG command.
FROM
SELECT nvl(oldest_flashback_time, MAXDATEVAL) INTO fbUntiltime FROM fb
WHERE dbinc_key = this_dbinc_key; .
TO .
SELECT nvl(oldest_flashback_time, MAXDATEVAL) INTO fbUntiltime FROM fb
WHERE dbinc_key = this_dbinc_key AND db_unique_name = this_db_unique_name; . I need some details to apply it.

[INFORMATIVE] RMAN-00600 8029

In case anybody encounters such an error when restoring with RMAN, from backup to ASM:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00601: fatal error in recovery manager
RMAN-03012: fatal error during compilation of command
RMAN-03028: fatal error code for command restore : 600
RMAN-00600: internal error, arguments [8029] [2] [] [] []It happened to me when I had to cancel a DUPLICATE command because of tape issues.
In order to "resume" the recovery, you must manually use "set newname for datafile xx to yy;"
xx : former file name (or number)
yy : new file name (here including ASM reference)
e.g. :
run {
allocate auxiliary channel ch1 type 'SBT_TAPE' PARMS '...';
allocate auxiliary channel ch2 type 'SBT_TAPE' PARMS '...';
allocate auxiliary channel ch3 type 'SBT_TAPE' PARMS '...';
set newname for datafile 2 to '+DG/dat01.dbf';
set newname for datafile 4 to '+DG/dat07.dbf';
set newname for datafile 16 to '+DG/dat03.dbf';
set newname for datafile 71 to '+DG/dat13.dbf';
restore clone datafile 2,4,16,71;
}Printed here because there's no info about RMAN-00600 [8029] on MetaLink.
Yoann.

Sorry this is a late response.
All ora-600 errors should be logged to Oracle Support.
Thanks Tammy

RMAN-00600: internal error

Hi every-one!
Now I have Oracle RAC 10.2.0.4 on AIX p595.
Normally, about 2 years, I backup by RMAN;
BACKUP DATABASE;
but from Yesterday, when using BACKUP DATABASE, it causes error as bellow:
RMAN> backup database;
Starting backup at 2011-04-11 10:02:59
using target database control file instead of recovery catalog
allocated channel: ORA_SBT_TAPE_1
channel ORA_SBT_TAPE_1: sid=9782 instance=oltpdb2 devtype=SBT_TAPE
channel ORA_SBT_TAPE_1: Data Protection for Oracle: version 5.4.1.0
allocated channel: ORA_SBT_TAPE_2
channel ORA_SBT_TAPE_2: sid=10436 instance=oltpdb2 devtype=SBT_TAPE
channel ORA_SBT_TAPE_2: Data Protection for Oracle: version 5.4.1.0
allocated channel: ORA_SBT_TAPE_3
channel ORA_SBT_TAPE_3: sid=9502 instance=oltpdb2 devtype=SBT_TAPE
channel ORA_SBT_TAPE_3: Data Protection for Oracle: version 5.4.1.0
allocated channel: ORA_SBT_TAPE_4
channel ORA_SBT_TAPE_4: sid=9489 instance=oltpdb2 devtype=SBT_TAPE
channel ORA_SBT_TAPE_4: Data Protection for Oracle: version 5.4.1.0
allocated channel: ORA_SBT_TAPE_5
channel ORA_SBT_TAPE_5: sid=9912 instance=oltpdb2 devtype=SBT_TAPE
channel ORA_SBT_TAPE_5: Data Protection for Oracle: version 5.4.1.0
allocated channel: ORA_SBT_TAPE_6
channel ORA_SBT_TAPE_6: sid=9396 instance=oltpdb2 devtype=SBT_TAPE
channel ORA_SBT_TAPE_6: Data Protection for Oracle: version 5.4.1.0
allocated channel: ORA_SBT_TAPE_7
channel ORA_SBT_TAPE_7: sid=9120 instance=oltpdb2 devtype=SBT_TAPE
channel ORA_SBT_TAPE_7: Data Protection for Oracle: version 5.4.1.0
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 04/11/2011 10:03:29
RMAN-00600: internal error, arguments [13205] [] [] [] []
RMAN>
But when I try to backup
BACKUP TABLESPACE USERS;
Iit is OK.
Pls help me!

Hi,
Probably you have hit Bug 6325947.
You could try to limit your files per set or your piece size.
Regards,
Tycho

Change DB_NAME failed with NID-00133: Database should have only consistent.

I have created two testing database for active data guard with Oracle 11g on Linux. I created standby DB by using rman backup from primary database. Now I want to change DB_NAME of standby database. I used DBNEWID utility
%> nid TARGET=SYS DBNAME=newname SETNAME=YES
It generated the error like this
NID-00133: Database should have only consistent datafiles
Change of database name failed during validation - database is intact
Many datafiles even system datafiles are not consistent. I shutdown DB and startup mount again and tried again. It all failed with the same errors. I searched solutions on Oracle Support web and other twchincal web and couldn't find
answers. Please help me to get the solutions. Thanks.

Thank each of you so much for your inputs.
Yes, based on oracle document, primary and standby shouid use the same name. But they can have different db_unique_name or instance_name. I created standby by using Grid Control. It automatically assign the same DB_NAME.
I modified db_unique_name. However, our PeopleSoft admin needs to connect to two databases to do testing. PeopleSoft version only support the different DB Name and DB Name cannot be over 8 characters. This is why I tried to
change DB_NAME to meet PeopleSoft Admin's requirement. I think, in the real world for data guard configuration, primary and standby should have the same db_name.

Rman duplication fails with RMAN-00600

Similar Messages

Maybe you are looking for