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.

Similar Messages

RAC Install fails with "OCR upgrade failed with (-1073741819) on 10.2.0

I am trying to install RAC 10.2.0 with two Server 2003 R2 nodes connected to a fiber channel SAN. I have set up the shared storage, created the extended partitions, and setup the unformatted no drive letter volumes. Both servers see the unformatted volumes (and no others do). The preinstallation checks work fine and the installations works fine until the first configuration assistant runs. That would be the "Oracle Clusterware Configuration Assistant". It tries to run crssetup.config.bat and fails on step 3 (configuring OCR Repository) with
ocr upgrade failed with (-1073741819)
If I uninstall clusterware and try again it will not show the OCR and Voting disks as available disks until I delete the volumes and partitions and recreate them. I have run the precheck batch files and they show everything as good as well. When I define the OCR and Voting drives in the clusterware setup I do not select format or assign drive letter. Every time I try to do the install I get the exact same error.
Is there anything I am missing or some trick or patch I may not have done?

Take a look at this notes!!
Note 341214.1 - How To clean up after a Failed Oracle Clusterware Installation on Windows
Note 388730.1 - Oracle RAC Clusterware Installation on Windows Commonly Missed / Misunderstood Prerequisites
Rgrs,
Paulo.

Creating physical standby using rman fails with ORA-19558: error de-allocat

Dear All,
We are creating physical stadnby database from 2 node RAC ( 2 node RAC to standalone physical standby).
While in the rman duplicate process we are getting below error, we were not able to sorted out..
No third party storage has been used ....
DB version : 11gR2 and the OS is RHEL5
Appreciate if any one hepl us to resolve this issue ...
Thanks in advance ...
RMAN-03009: failure of backup command on prmy1 channel at 10/05/2011 17:59:26
ORA-19558: error de-allocating device
ORA-19557: device error, device type: DISK, device name:
ORA-17627: ORA-01041: internal error. hostdef extension doesn't exist
ORA-17627: ORA-01041: internal error. hostdef extension doesn't exist
ORA-03113: end-of-file on communication channel
Edited by: 889828 on 2011/10/06 2:17 AM

The problem is well decribed in your alert log.....you are using Oracle Managed File names which means you will not be able to duplicate the database as RMAN won't be able to automatically generate new names for the files using the DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT initialization parameters.
Youll have to use the SET NEWNAME command to specify the names of the database files. Done this a few times , and I don't recommend using OMF specifically beacuse of this hassle.
WARNING: OMF is enabled on this database. Creating a physical standby controlfile, when OMF is enabled on the primary database, requires manual RMAN intervention to resolve OMF
datafile pathnames.
NOTE: Please refer to the RMAN documentation for procedures describing how to manually resolve OMF datafile pathnames.
Problem handling is described in
Oracle® Database Backup and Recovery Reference
10g Release 2 (10.2)
Part Number B14194-03

Rman problem with NLS_LANG mismatch b/w catalog and target DB

Hi,
I have target database NLS_LANG set to 'AMERICAN_AMERICA.JA16SJIS' and recovery catalog NLS_LANG set to 'JAPANESE_JAPAN.JA16EUC'. When backup is started the rman fails with the following error.
<----
RMAN-00571:
===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS
===============
RMAN-00571:
===========================================================
RMAN-03002: failure of allocate command at 11/26/2007 11:22:41
RMAN-03014: implicit resync of recovery catalog failed
RMAN-03009: failure of partial resync command on default channel
at
11/26/2007 11:22:41
ORA-06502: PL/SQL: numeric or value error
------>
It works fine if I change the recovery catalog NLS_LANG to 'AMERICAN_AMERICA.JA16SJIS'
Any help could be appreciated.
Thanks,
Prince

Hello Faust,
have already tried that in SQLPlus, SQLWorksheet, MS Access (OffXP). All apps used on the same computer. OS Win XP Prof.
Result in Plus and Worksheet
40 ! â a a î l c ç i Ä . < ( + ! 50 ! & e e e i n k g Ü $ * ) ; ^ 60 ! - / Â A A Î L C Ç I ö , % > ? 70 ! E E E I N K G ` : § ' = " 80 ! a b c d e f g h i [ ] g @ 90 ! ° j k l m n o p q r º ¿ A0 ! µ ß s t u v w x y z G ¿ B0 ! 0 1 2 3 4 5 6 7 8 9 a ß ¿ d e ¿ C0 ! ä A B C D E F G H I � t õ D0 ! ü J K L M N O P Q R · u i s u E0 ! Ö S T U V W X Y Z ² � T Õ F0 ! 0 1 2 3 4 5 6 7 8 9 ³ U I S U
result in Access (via ODBC Con)
40 ! â ą ā î ļ č ç ī Ä . < ( + ! 50 ! & ē ę ė į ņ ķ ģ Ü $ * ) ; ^ 60 ! - / Â Ą Ā Î Ļ Č Ç Ī ö , % > ? 70 ! Ē Ę Ė Į Ņ Ķ Ģ ` : § ' = " 80 ! a b c d e f g h i [ ] ğ @ 90 ! ° j k l m n o p q r º ≙ A0 ! µ ß s t u v w x y z Ğ Δ B0 ! ₀ ₁ ₂ ₃ ₄ ₅ ₆ ₇ ₈ ₉ α β γ δ ε ω C0 ! ä A B C D E F G H I ţ õ D0 ! ü J K L M N O P Q R · ų ı ş ū E0 ! Ö S T U V W X Y Z ² Ţ Õ F0 ! 0 1 2 3 4 5 6 7 8 9 ³ Ų İ Ş Ū

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

Word conversion fails with error -1073741819

How can I convert a Word 2007 .docx file into a fillable .pdf form, without suffering errors? The file contains a Word table with numerous cells, text and legacy controls (checkbox and drop-down list). (Converting a .docx file with nothing but the word "test" is successful.)
When I attempt this with the default settings, LiveCycle ES 8.2.1.4029 fails with the error -1073741819. Repeating the procedure has the same effect. What does this error mean?
Event log:
Faulting application convertword.exe, version 8.2.1.4029, faulting module convertword.exe, version 8.2.1.4029, fault address 0x0004bb84.
Operating system is Windows XP Professional SP3, running as a member of the Users group (no administrative rights).

Hello Venu,
Best of option to run export is from Database host. You have said you cannot get sapinst screens properly when you running from sapinst
can you chek this
1. Make sure you only have acitve profile in /usr/sap/SID/SYS/profile. Remove all other profile including backup profile.
If you still have issues
2. Skip update statistics from sapinst and run them manually using BR tools.
Thank You,
Praveen

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

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.

Backup Fails with Invalid RECID Error

Hi All,
Please help me to understand Caution -section
below text is from
[http://download.oracle.com/docs/cd/B10501_01/server.920/a96566/rcmtroub.htm#447765]
Backup Fails with Invalid RECID Error: Solution 2
This solution is more difficult than solution 1:
To create the control file with SQL*Plus:
   1. Connect to the target database with SQL*Plus. For example, enter:
      % sqlplus 'SYS/oracle@trgt AS SYSDBA'
   2. Mount the database if it is not already mounted:
      SQL> ALTER DATABASE MOUNT;
   3. Back up the control file to a trace file:
      SQL> ALTER DATABASE BACKUP CONTROLFILE TO TRACE;
   4. Edit the trace file as necessary. The relevant section of the trace file looks something like the following:
      # The following commands will create a new control file and use it
      # to open the database.
      # Data used by the recovery manager will be lost. Additional logs may
      # be required for media recovery of offline data files. Use this
      # only if the current version of all online logs are available.
      STARTUP NOMOUNT
      CREATE CONTROLFILE REUSE DATABASE "TRGT" NORESETLOGS ARCHIVELOG
      -- STANDBY DATABASE CLUSTER CONSISTENT AND UNPROTECTED
          MAXLOGFILES 32
          MAXLOGMEMBERS 2
          MAXDATAFILES 32
          MAXINSTANCES 1
          MAXLOGHISTORY 226
      LOGFILE
        GROUP 1 '/oracle/oradata/trgt/redo01.log' SIZE 25M,
        GROUP 2 '/oracle/oradata/trgt/redo02.log' SIZE 25M,
        GROUP 3 '/oracle/oradata/trgt/redo03.log' SIZE 500K
      -- STANDBY LOGFILE
      DATAFILE
        '/oracle/oradata/trgt/system01.dbf',
        '/oracle/oradata/trgt/undotbs01.dbf',
        '/oracle/oradata/trgt/cwmlite01.dbf',
        '/oracle/oradata/trgt/drsys01.dbf',
        '/oracle/oradata/trgt/example01.dbf',
        '/oracle/oradata/trgt/indx01.dbf',
        '/oracle/oradata/trgt/tools01.dbf',
        '/oracle/oradata/trgt/users01.dbf'
      CHARACTER SET WE8DEC
      # Take files offline to match current control file.
      ALTER DATABASE DATAFILE '/oracle/oradata/trgt/tools01.dbf' OFFLINE;
      ALTER DATABASE DATAFILE '/oracle/oradata/trgt/users01.dbf' OFFLINE;
      # Configure RMAN configuration record 1
      VARIABLE RECNO NUMBER;
      EXECUTE :RECNO := SYS.DBMS_BACKUP_RESTORE.SETCONFIG('CHANNEL','DEVICE TYPE DISK
      DEBUG 255');
      # Recovery is required if any of the datafiles are restored backups,
      # or if the last shutdown was not normal or immediate.
      RECOVER DATABASE
      # All logs need archiving and a log switch is needed.
      ALTER SYSTEM ARCHIVE LOG ALL;
      # Database can now be opened normally.
      ALTER DATABASE OPEN;
      # Commands to add tempfiles to temporary tablespaces.
      # Online tempfiles have complete space information.
      # Other tempfiles may require adjustment.
      ALTER TABLESPACE TEMP ADD TEMPFILE '/oracle/oradata/trgt/temp01.dbf' REUSE;
      # End of tempfile additions.
   5. Shut down the database:
      SHUTDOWN IMMEDIATE
   6. Execute the script to create the control file, recover (if necessary), archive the logs, and open the database:
      STARTUP NOMOUNT
      CREATE CONTROLFILE ...;
      EXECUTE ...;
      RECOVER DATABASE
      ALTER SYSTEM ARCHIVE LOG CURRENT;
      ALTER DATABASE OPEN ...;
Caution:
      If you do not open with the RESETLOGS option,
then two copies of an archived redo log for a given log sequence number may
exist--even though these two copies have completely different contents.
For example, one log may have been created on the original host and the other on the new host.
If you accidentally confuse the logs during a media recovery,
then the database will be corrupted but Oracle and RMAN cannot detect the problem.

Please help me to understand Caution -section
Caution:
If you do not open with the RESETLOGS option,
then two copies of an archived redo log for a given log sequence number may
exist--even though these two copies have completely different contents.
For example, one log may have been created on the original host and the other on the new host.
If you accidentally confuse the logs during a media recovery,
then the database will be corrupted but Oracle and RMAN cannot detect the problem.As per my understanding it says. If you don't open database with RESETLOGS option then there may be archived logs with log sequence number which is already archived on the source host. This may happen due to difference in RECIDs. Now when the database needs media recovery for this particular log sequence, you may provide any of them. So in this case, RMAN and Oracle will not be able to differentiate the two files and can accept any of the archived log files during recovery. Since the contents of two archived logs are different, because they are generated at different times and they contains different transactions. So, internally it corrupts your database.
Rgds.

RMAN fails with 1073741819

Similar Messages

Maybe you are looking for