Rman Backup time error

Today i saw this error in our production backup time .
Please let me know how to leave out from this.
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup plus archivelog command at 05/27/2011 01:13:47
RMAN-03009: failure of backup command on ORA_DISK_2 channel at 05/27/2011 01:10:52
ORA-19566: exceeded limit of 0 corrupt blocks for file
N:\USERS01.DBF
Regs,
Brij

Also, be aware that rman: backup validate (check logical) command could not show the corrupted blocks if that block are newer used(or used before, but freed later for example). In this case, rman validate does not populate V$database_block_corruption but it also does not allows you to continue with your backup.
So the solution will be, as previous posters said, either set the limit for the sustained number of corrupted blocks or format/repair the corrupted block.
For checking the corrupted blocks you could also use db verify utility(dbv). This will definitely show you the details about corrupted blocks, even they are not used ever.

Similar Messages

RMAN Backup Script Error

Hi ,
I am getting the following error when i am executing manbackup shell script.
Message file RMAN<lang>.msb not found
Verify that ORACLE_HOME is set properly
RMAN Script
DATE=`date +%Y%m%d.%H%M`
#su - oracle
#<<EOF
export ORACLE_HOME=/home/app/oracle/product/10.2.0/db_1
echo $ORACLE_HOME
export PATH=$PATH:$ORACLE_HOME/bin
#export PATH=$ORACLE_HOME/bin:$PATH
export ORACLE_SID=ACILOC
echo $ORACLE_SID
rman cmdfile=/oraclebkp/rmanbackupscripts/rmanlevel0bkp.bck log=/oraclebkp/rmanbackupscripts/rmanACILOClev0$DATE.log
export ORACLE_SID=ACIDC
echo $ORACLE_SID
rman cmdfile=/oraclebkp/rmanbackupscripts/rmanlevel0bkp.bck log=/oraclebkp/rmanbackupscripts/rmanACIDClev0$DATE.log
#EOF
level0bkp.bck
connect target `/'
run
backup incremental level 0 database;
but I am able to take RMAN backups by connecting as RMAN TARGET /
Thanks in advance
Priya

connect target `/'Dont give / in quotations just connect as
connect target /
backup incremental level 0 database;
}Thanks
Close the threads as answered if helpful/correct.
user11342455
Handle: user11342455
Status Level: Newbie
Registered: Feb 18, 2010
Total Posts: 22
Total Questions: 10 (8 unresolved)
Edited by: CKPT on Jan 5, 2011 12:17 PM

REDUCE RMAN BACKUP TIME

Hi,
We have are 800GB database and we take daily backup through RMAN.
Backup policy is LEVEL 0 on week end and LEVEL1 AND LEVEL2 on other days.
When we take the backup our system utilization become high and which is effecting our 24X7 service.
How can I reduce the load on the database during backup.
Thanks in advance.

if you have a physical standby in place , or if you can create one, use that to backup. Using standby will completely off load your backup time & performance impact
other wise use RATE in channel
CONFIGURE CHANNEL DEVICE TYPE DISK MAXPIECESIZE <piecesize> K FORMAT '/backups/DBSID/DBSID.bkup.%U' RATE 2000000;

RMAN backup time increased

Hi All,
I need details about some diagnostic test regarding RMAN backup on my instance.
The following are the current configuration of details:
SQL> select release_name from fnd_product_groups;
RELEASE_NAME
11.5.8
SQL> select * from v$version;
BANNER
Oracle9i Enterprise Edition Release 9.2.0.8.0 - 64bit Production
PL/SQL Release 9.2.0.8.0 - Production
CORE 9.2.0.8.0 Production
TNS for Solaris: Version 9.2.0.8.0 - Production
NLSRTL Version 9.2.0.8.0 - Production
===============================================
Database Size
1.5 TB
Earlier the RMAN backup used to take 20 -23 hours, now for the last 2 months, it has started taking 40 hours.
We want to identify the reason behind the increase in time.
Please let us know methods that we can use to diagnose the root cause.
Thanks
Peeks

Hi Talip,
Thanks for you suggestions.
I tried the three queries suggested by you, please find below the output:
SQL> select set_stamp from v$backup_async_io where to_date(open_time,'dd.mon.rr')='05.mar.12';
SET_STAMP
777154038
777154038
777154038
777154038
777154038
777154038
777154038
777154038
777154038
777154038
777167658
SET_STAMP
777167658
777167658
777167673
777167673
777167673
16 rows selected.The we checked the effective_bytes_per_second "mb/sec" column for the 777154038 and 777167658 Set_stamps.
SQL> select device_type "Device",
type,
open_time,close_time,
elapsed_time/100 "Ela",
effective_bytes_per_second/1024/1024 "mb/sec",
filename
from v$backup_async_io
where set_stamp = &a
order by close_time desc; 2    3    4    5    6    7    8    9
Enter value for a: 777154038
old   8: where set_stamp = &a
new   8: where set_stamp = 777154038
Device          TYPE      OPEN_TIME       CLOSE_TIME             Ela     mb/sec FILENAME
SBT_TAPE        OUTPUT    05-MAR-12       05-MAR-12            13498 3.03509712 bk_87606_1_777154038
SBT_TAPE        OUTPUT    05-MAR-12       05-MAR-12            13475 3.03425884 bk_87605_1_777154038
DISK            AGGREGATE 05-MAR-12       05-MAR-12            13476   3.041852
DISK            INPUT     05-MAR-12       05-MAR-12             2832 2.90395451 /u1141/oradata/PRD1/rbs03.dbf
DISK            AGGREGATE 05-MAR-12       05-MAR-12            13446 3.0486393
DISK            INPUT     05-MAR-12       05-MAR-12             2829 2.90703392 /u1141/oradata/PRD1/rbs01.dbf
DISK            INPUT     05-MAR-12       05-MAR-12             5332 3.07276821 /u1140/oradata/PRD1/ard01.dbf
DISK            INPUT     05-MAR-12       05-MAR-12             5314 3.08317661 /u1140/oradata/PRD1/applsysx01.dbf
DISK            INPUT     05-MAR-12       05-MAR-12             5309 3.08608055 /u1140/oradata/PRD1/gld01.dbf
DISK            INPUT     05-MAR-12       05-MAR-12             5300 3.09132099 /u1140/oradata/PRD1/applsysd01.dbf
10 rows selected.
SQL> /
Enter value for a: 777167658
old   8: where set_stamp = &a
new   8: where set_stamp = 777167658
Device          TYPE      OPEN_TIME       CLOSE_TIME             Ela     mb/sec FILENAME
SBT_TAPE        OUTPUT    05-MAR-12       06-MAR-12            13323 3.07180786 bk_87607_1_777167658
DISK            AGGREGATE 05-MAR-12       06-MAR-12            13289 3.08224869
DISK            INPUT     06-MAR-12       06-MAR-12             2652 3.08898926 /u1141/oradata/PRD1/rbs02.dbf
DISK            INPUT     06-MAR-12       06-MAR-12             5330 3.0739212 /u1140/oradata/PRD1/invd01.dbf
DISK            INPUT     05-MAR-12       06-MAR-12             5305 3.08840752 /u1140/oradata/PRD1/arx01.dbf
SQL>The above output looks fine, but when i checked the long wait uery, it showed high percentage usage for OUTPUT streams. The below is the output:
TYPE        IO_COUNT      READY SHORT_WAITS LONG_WAITS    LIO_PCT FILENAME
INPUT          16385      15361           0       1024 6.24961855 /u1140/oradata/PRD1/applsysd01.dbf
INPUT          16385      15361           0       1024 6.24961855 /u1140/oradata/PRD1/applsysx01.dbf
INPUT          16385      15361           0       1024 6.24961855 /u1140/oradata/PRD1/ard01.dbf
INPUT          16385      15361           0       1024 6.24961855 /u1140/oradata/PRD1/gld01.dbf
INPUT           8225       7711           0        514 6.24924012 /u1141/oradata/PRD1/rbs01.dbf
INPUT           8225       7711           0        514 6.24924012 /u1141/oradata/PRD1/rbs03.dbf
OUTPUT         10222       7662           0       2560 25.0440227 bk_87605_1_777154038
OUTPUT         10242       7678           0       2564 25.034173 bk_87606_1_777154038
AGGREGATE      40995      38433           0       2562 6.24954263
AGGREGATE      40995      38433           0       2562 6.24954263
10 rows selected.
TYPE        IO_COUNT      READY SHORT_WAITS LONG_WAITS    LIO_PCT FILENAME
INPUT          16385      15361           0       1024 6.24961855 /u1140/oradata/PRD1/arx01.dbf
INPUT          16385      15361           0       1024 6.24961855 /u1140/oradata/PRD1/invd01.dbf
INPUT           8193       7681           0        512 6.24923715 /u1141/oradata/PRD1/rbs02.dbf
OUTPUT         10232       7669           0       2563 25.0488663 bk_87607_1_777167658
AGGREGATE      40963      38403           0       2560 6.24954227So, as per the output please suggest possible solutions to decrease the backup time, if not possible any other option.
Is there any problem with the tape device or is it an oracle issue.
Thanks
Peeks

Rman backup validate error

DBGSQL: RCVCAT> begin dbms_rcvman.findSpfileBackup( allCopies => TRUE, rmanCmd => dbms_rcvman.restoreCmd_t); end; [10:37:16.635]
DBGSQL: sqlcode = 6550 [10:37:16.635]
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 [9302] [6550] [begin dbms_rcvman.findSpfileBackup( allCopies => TRUE, rmanCmd => dbms_rcvman.restoreCmd_t); end; ] [] []
RMAN-06004: ORACLE error from recovery catalog database: ORA-06550: line 1, column 7:
PLS-00306: wrong number or types of arguments in call to 'FINDSPFILEBACKUP'
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored
pls any one help me out
Thanks!

Since you say nothing about your OS and database version and we also don't know,which command produces this error, only a vague guess is possible, COULD be
Bug 7633694: RESTORE SPFILE LS-00306: WRONG NUMBER OR TYPES OF ARGUMENTS 'FINDSPFILEBACKUP' .
IF this bug is hit possible workarounds are:
1) Don't use a 11gR1 catalog
2) don't use spfile,keep a text based pfile
3) upgrade to 11gR2 (IF your OS is Linux or Solaris)
Werner

Rman backup time

Hi,
can any one please provide me the query to find how much time takes to take the backup of the database.
backup is by rman, that may be any thing like level 0 or 1 or 2
thanks

Hi,
can any one please provide me the query to find how much time takes to take the backup of the database.Pleaserun this and post the result.
alter session set nls_date_format = 'yyyy-MON-dd hh24:mi:ss';
select backup_type,
incremental_level,
round(sum(original_input_bytes)/1024/1024,2) "MB in",
round(sum(output_bytes)/1024/1024,2) "MB out",
status,
min(start_time),
max(completion_time),
round((sum(output_bytes)/1024/1024)/((max(completion_time)-min(start_time))*86400), 1) "MB/s"
from v$backup_set_details
group by backup_type, incremental_level, status, session_key, session_recid, session_stamp
order by 6
Regards,
Tycho

How to speed up rman backup?

Hi,
we are taking backup using rman. my database size is increasing.so rman backup time is increasing. so i want to spped up rman bakup performance. how to speed up rman bakup?
Thnaks,

My general request whenever you post the question in forum please start your question something like this:
Oracle Version : <4 digit version> select * from v$version;
OS Information with complete version and/or patch whatsoever.
1. http://www.oracle-base.com/articles/10g/RMANEnhancements10g.php
2. Re: RMAN Backup Script
and read the reply of Adith
You can also use set
CONFIGURE BACKUP OPTIMIZATION ON
Additionally review
Restarting and Optimizing RMAN Backups
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmbackp007.htm#i1006318
Best Regards
Girish Sharma

RMAN backup to SAN takes 13 hours

Hi All,
I have configured my RMAN to run through Recovery Catalog, and take daily full backup (limitation of Standard Edition) to a shared location on Test Server (\\testdb), which takes around 35 minutes to complete successfully.
The same full database backup takes 13 hours to complete on shared location to SAN storage mounted on blade server (\\blade5). To investigate further I opened an SR with Oracle Support and ran a series of test to take backup of a single tablespace (using target controlfile) on following 3 locations:
1. Local Hard disk of Production Server
2. Shared location on Test Server
3. Shared location to SAN storage mounted on blade server
Following were the results of the test:
1. The backup tablespace size is 1.36 GB with one datafile.
2. The backup piece size in all 3 test cases is 1.1 GB each.
3. RMAN Backup Time at 3 location:
3a. Local Backup Duration (D:\backup): 04:55 minutes
3b. Shared Backup Duration (\\testdbl): 02:25 minutes
3c. Shared SAN Duration (\\blade5): 26:25 minutes
Based on the above finding Oracle Support concluded that Oracle RMAN is perfectly fine and It is at the SAN that the problem resides, whereas the IT Admins state the problem is at the RMAN side.
My query is, how do we determine that Oracle RMAN is underperforming due to issues with SAN or blade server or network?
Regard,
Z.K.

ebrian wrote:
When the backup is running to the SAN, you may want to see what RMAN may be waiting for from V$SESSION/V$SESSION_WAIT. In addition, you may want to enable tracing during the backup to the SAN and see if anything stands out from the trace file:
rman target / log rman.log trace rman.trc debug
As per your suggestion, I carried out the test again with tracing enabled.
1 Tablespace [with 1 datafile] size 1.36 GB used for RMAN backup.
Backup piece size: 1.1 GB
Please find below output of V$SESSION/V$SESSION_WAIT for all 3 cases:
*1. LOCAL DISK*
--v$session
SADDR     SID     SERIAL#     AUDSID     PADDR     USER#     USERNAME     COMMAND     OWNERID     TADDR     LOCKWAIT     STATUS     SERVER     SCHEMA#     SCHEMANAME     OSUSER     PROCESS     MACHINE     TERMINAL     PROGRAM     TYPE     SQL_ADDRESS     SQL_HASH_VALUE     PREV_SQL_ADDR     PREV_HASH_VALUE     MODULE     MODULE_HASH     ACTION     ACTION_HASH     CLIENT_INFO     FIXED_TABLE_SEQUENCE     ROW_WAIT_OBJ#     ROW_WAIT_FILE#     ROW_WAIT_BLOCK#     ROW_WAIT_ROW#     LOGON_TIME     LAST_CALL_ET     PDML_ENABLED     FAILOVER_TYPE     FAILOVER_METHOD     FAILED_OVER     RESOURCE_CONSUMER_GROUP     PDML_STATUS     PDDL_STATUS     PQ_STATUS     CURRENT_QUEUE_DURATION     CLIENT_IDENTIFIER
5428E7D8     30     14290     0     5425FD54     0     SYS     0     2147483644               INACTIVE     DEDICATED     0     SYS     ISCO\zafferk     6200:5792     ISCO\DBSERVER     DBSERVER     RMAN.EXE     USER     00     0     0D779F90     888448358     RMAN.EXE     0     0000001 FINISHED     2940145100          2466540     -1     0     0     0     3/9/2009 10:31:32 AM     6     NO     NONE     NONE     NO     SYS_GROUP     DISABLED     ENABLED     ENABLED     0
542B01C8     87     3021     0     54263FBC     0     SYS     0     2147483644               INACTIVE     DEDICATED     0     SYS     ISCO\zafferk     6200:5792     ISCO\DBSERVER     DBSERVER     RMAN.EXE     USER     00     0     0AA8F068     1819975476     RMAN.EXE     0          0          2466515     -1     0     0     0     3/9/2009 10:31:51 AM     12     NO     NONE     NONE     NO     SYS_GROUP     DISABLED     ENABLED     ENABLED     0
542C84B8     128     3620     0     542643A4     0     SYS     0     2147483644               INACTIVE     DEDICATED     0     SYS     ISCO\zafferk     6200:5792     ISCO\DBSERVER     DBSERVER     RMAN.EXE     USER     05B36878     1141676395     05B36878     1141676395     backup full datafile: ORA_DISK_1     3173805813     0000014 FINISHED     4058944949     rman channel=ORA_DISK_1     2466514     -1     0     0     0     3/9/2009 10:32:13 AM     12     NO     NONE     NONE     NO     SYS_GROUP     DISABLED     ENABLED     ENABLED     0
--v$session_wait
SID     SEQ#     EVENT     P1TEXT     P1     P1RAW     P2TEXT     P2     P2RAW     P3TEXT     P3     P3RAW     WAIT_TIME     SECONDS_IN_WAIT     STATE
128     751     async disk IO     count     1     00000001     intr     32     00000020     timeout     2147483647     7FFFFFFF     -1     0     WAITED KNOWN TIME
30     655     SQL*Net message from client     driver id     1111838976     42455100     #bytes     1     00000001          0     00     0     264     WAITING
87     135     SQL*Net message from client     driver id     1111838976     42455100     #bytes     1     00000001          0     00     0     9     WAITING*2. TESTDB*
--v$session
SADDR     SID     SERIAL#     AUDSID     PADDR     USER#     USERNAME     COMMAND     OWNERID     TADDR     LOCKWAIT     STATUS     SERVER     SCHEMA#     SCHEMANAME     OSUSER     PROCESS     MACHINE     TERMINAL     PROGRAM     TYPE     SQL_ADDRESS     SQL_HASH_VALUE     PREV_SQL_ADDR     PREV_HASH_VALUE     MODULE     MODULE_HASH     ACTION     ACTION_HASH     CLIENT_INFO     FIXED_TABLE_SEQUENCE     ROW_WAIT_OBJ#     ROW_WAIT_FILE#     ROW_WAIT_BLOCK#     ROW_WAIT_ROW#     LOGON_TIME     LAST_CALL_ET     PDML_ENABLED     FAILOVER_TYPE     FAILOVER_METHOD     FAILED_OVER     RESOURCE_CONSUMER_GROUP     PDML_STATUS     PDDL_STATUS     PQ_STATUS     CURRENT_QUEUE_DURATION     CLIENT_IDENTIFIER
54290D98     34     11745     0     542643A4     0     SYS     0     2147483644               ACTIVE     DEDICATED     0     SYS     ISCO\zafferk     5156:5620     ISCO\DBSERVER     DBSERVER     RMAN.EXE     USER     05B36878     1141676395     00     0     backup full datafile: ORA_DISK_1     3173805813     0000012 STARTED     2679454996     rman channel=ORA_DISK_1     2467508     -1     0     0     0     3/9/2009 10:50:26 AM     12     NO     NONE     NONE     NO     SYS_GROUP     DISABLED     ENABLED     ENABLED     0
54294FA8     41     13232     0     54263FBC     0     SYS     0     2147483644               INACTIVE     DEDICATED     0     SYS     ISCO\zafferk     5156:5620     ISCO\DBSERVER     DBSERVER     RMAN.EXE     USER     00     0     0AA8F068     1819975476     RMAN.EXE     0          0          2467521     -1     0     0     0     3/9/2009 10:50:03 AM     3     NO     NONE     NONE     NO     SYS_GROUP     DISABLED     ENABLED     ENABLED     0
5429D3C8     55     4581     0     5425FD54     0     SYS     0     2147483644               INACTIVE     DEDICATED     0     SYS     ISCO\zafferk     5156:5620     ISCO\DBSERVER     DBSERVER     RMAN.EXE     USER     00     0     58565384     2746682842     RMAN.EXE     0     0000001 FINISHED     2940145100          2467505     -1     0     0     0     3/9/2009 10:48:48 AM     15     NO     NONE     NONE     NO     SYS_GROUP     DISABLED     ENABLED     ENABLED     0
--v$session_wait
SID     SEQ#     EVENT     P1TEXT     P1     P1RAW     P2TEXT     P2     P2RAW     P3TEXT     P3     P3RAW     WAIT_TIME     SECONDS_IN_WAIT     STATE
34     788     async disk IO     count     1     00000001     intr     32     00000020     timeout     2147483647     7FFFFFFF     -1     0     WAITED KNOWN TIME
41     95     SQL*Net message from client     driver id     1111838976     42455100     #bytes     1     00000001          0     00     0     3     WAITING
55     655     SQL*Net message from client     driver id     1111838976     42455100     #bytes     1     00000001          0     00     0     132     WAITING*3. SAN blade5*
--v$session
SADDR     SID     SERIAL#     AUDSID     PADDR     USER#     USERNAME     COMMAND     OWNERID     TADDR     LOCKWAIT     STATUS     SERVER     SCHEMA#     SCHEMANAME     OSUSER     PROCESS     MACHINE     TERMINAL     PROGRAM     TYPE     SQL_ADDRESS     SQL_HASH_VALUE     PREV_SQL_ADDR     PREV_HASH_VALUE     MODULE     MODULE_HASH     ACTION     ACTION_HASH     CLIENT_INFO     FIXED_TABLE_SEQUENCE     ROW_WAIT_OBJ#     ROW_WAIT_FILE#     ROW_WAIT_BLOCK#     ROW_WAIT_ROW#     LOGON_TIME     LAST_CALL_ET     PDML_ENABLED     FAILOVER_TYPE     FAILOVER_METHOD     FAILED_OVER     RESOURCE_CONSUMER_GROUP     PDML_STATUS     PDDL_STATUS     PQ_STATUS     CURRENT_QUEUE_DURATION     CLIENT_IDENTIFIER
54294FA8     41     13257     0     5425FD54     0     SYS     0     2147483644               INACTIVE     DEDICATED     0     SYS     ISCO\zafferk     5804:5620     ISCO\DBSERVER     DBSERVER     RMAN.EXE     USER     00     0     58565384     2746682842     RMAN.EXE     0     0000001 FINISHED     2940145100          2468381     -1     0     0     0     3/9/2009 10:55:08 AM     169     NO     NONE     NONE     NO     SYS_GROUP     DISABLED     ENABLED     ENABLED     0
5429D3C8     55     4725     0     542643A4     0     SYS     0     2147483644               ACTIVE     DEDICATED     0     SYS     ISCO\zafferk     5804:5620     ISCO\DBSERVER     DBSERVER     RMAN.EXE     USER     05B36878     1141676395     00     0     backup full datafile: ORA_DISK_1     3173805813     0000012 STARTED     2679454996     rman channel=ORA_DISK_1     2468384     -1     0     0     0     3/9/2009 10:56:16 AM     166     NO     NONE     NONE     NO     SYS_GROUP     DISABLED     ENABLED     ENABLED     0
542C2FC8     119     14058     0     54263FBC     0     SYS     0     2147483644               INACTIVE     DEDICATED     0     SYS     ISCO\zafferk     5804:5620     ISCO\DBSERVER     DBSERVER     RMAN.EXE     USER     00     0     0AA8F068     1819975476     RMAN.EXE     0          0          2468834     -1     0     0     0     3/9/2009 10:55:52 AM     8     NO     NONE     NONE     NO     SYS_GROUP     DISABLED     ENABLED     ENABLED     0
--v$session_wait
SID     SEQ#     EVENT     P1TEXT     P1     P1RAW     P2TEXT     P2     P2RAW     P3TEXT     P3     P3RAW     WAIT_TIME     SECONDS_IN_WAIT     STATE
55     833     async disk IO     count     0     00     intr     32     00000020     timeout     2147483647     7FFFFFFF     -1     4     WAITED KNOWN TIME
41     656     SQL*Net message from client     driver id     1111838976     42455100     #bytes     1     00000001          0     00     0     1354     WAITING
119     495     SQL*Net message from client     driver id     1111838976     42455100     #bytes     1     00000001          0     00     0     10     WAITINGIf you'd like, I can post trace file output of backup to \\blade5.
Regards,
Z.K.

Restore spfile from rman backup ---- error.

Hi,
I am trying to execute recovery on new machine ...
I have done the following steps..
I have one database as ora10g2 as peroduction database on one machine as hosta
I have created a catalog on another machine cora10g2 (hostb)
I have taken a full backup from hosta as per following ...
the following command execute from hosta machine.
$ rman target sys/<passwd>@ora10g2 catalog rman/rman@cora10g2 ...
Backup completed ...
Now I am trying to restore this backup on hostb machine where i have already rman catlog database ..
I have done the following setting ...on host b
set oracle_sid=DUP
and execute following command ...
rman target / catalog rman/rman@cora10g2
RMAN> set dbid 2760732370
executing command: SET DBID
database name is "BAAN10G2" and DBID is 2760732370
RMAN>
RMAN>
RMAN> startup force nomount ;
startup failed: ORA-01078: failure in processing system parameters
LRM-00109: could not open parameter file '/oracle/dbs/baan10g2/dbs/initbaan10g2.ora'
starting Oracle instance without parameter file for retrival of spfile
Oracle instance started
Total System Global Area 159383552 bytes
Fixed Size 1977112 bytes
Variable Size 67114216 bytes
Database Buffers 83886080 bytes
Redo Buffers 6406144 bytes
RMAN>
RMAN>
RMAN>
RMAN> show all ;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/rman/backup/control/cntrl_%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 4 BACKUP TYPE TO BACKUPSET;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/baanora3/rman/ora10g2/bkup_db_%d_s%s_P%p_t%t' MAXPIECESIZE 1024;
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
RMAN>
RMAN>
RMAN> list backup of spfile ;
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
2420 Full 7.33M DISK 00:00:01 14-JUN-07
BP Key: 2426 Status: AVAILABLE Compressed: NO Tag: TAG20070614T182935
Piece Name: /rman/backup/control/cntrl_c-2760732370-20070614-00
SPFILE Included: Modification time: 14-JUN-07
BS Key Type LV Size Device Type Elapsed Time Completion Time
2509 Full 7.33M DISK 00:00:01 15-JUN-07
BP Key: 2515 Status: AVAILABLE Compressed: NO Tag: TAG20070615T130416
Piece Name: /rman/backup/control/cntrl_c-2760732370-20070615-00
SPFILE Included: Modification time: 15-JUN-07
BS Key Type LV Size Device Type Elapsed Time Completion Time
2694 Full 7.33M DISK 00:00:01 15-JUN-07
BP Key: 2739 Status: AVAILABLE Compressed: NO Tag: TAG20070615T131703
Piece Name: /rman/backup/control/cntrl_c-2760732370-20070615-01
SPFILE Included: Modification time: 15-JUN-07
BS Key Type LV Size Device Type Elapsed Time Completion Time
2760 Full 80.00K DISK 00:00:01 15-JUN-07
BP Key: 2763 Status: AVAILABLE Compressed: NO Tag: TAG20070615T163437
Piece Name: /rman/spfile/spfile.ora
SPFILE Included: Modification time: 15-JUN-07
BS Key Type LV Size Device Type Elapsed Time Completion Time
2769 Full 7.33M DISK 00:00:02 15-JUN-07
BP Key: 2771 Status: AVAILABLE Compressed: NO Tag: TAG20070615T163441
Piece Name: /rman/backup/control/cntrl_c-2760732370-20070615-02
SPFILE Included: Modification time: 15-JUN-07
RMAN>
RMAN>
RMAN> restore spfile from autobackup ;
Starting restore at 19-JUN-07
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=36 devtype=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: sid=35 devtype=DISK
allocated channel: ORA_DISK_3
channel ORA_DISK_3: sid=34 devtype=DISK
allocated channel: ORA_DISK_4
channel ORA_DISK_4: sid=33 devtype=DISK
channel ORA_DISK_1: looking for autobackup on day: 20070619
channel ORA_DISK_1: looking for autobackup on day: 20070618
channel ORA_DISK_1: looking for autobackup on day: 20070617
channel ORA_DISK_1: looking for autobackup on day: 20070616
channel ORA_DISK_1: looking for autobackup on day: 20070615
channel ORA_DISK_1: looking for autobackup on day: 20070614
channel ORA_DISK_1: looking for autobackup on day: 20070613
channel ORA_DISK_1: no autobackup in 7 days found
channel ORA_DISK_2: looking for autobackup on day: 20070619
channel ORA_DISK_2: looking for autobackup on day: 20070618
channel ORA_DISK_2: looking for autobackup on day: 20070617
channel ORA_DISK_2: looking for autobackup on day: 20070616
channel ORA_DISK_2: looking for autobackup on day: 20070615
channel ORA_DISK_2: looking for autobackup on day: 20070614
channel ORA_DISK_2: looking for autobackup on day: 20070613
channel ORA_DISK_2: no autobackup in 7 days found
channel ORA_DISK_3: looking for autobackup on day: 20070619
channel ORA_DISK_3: looking for autobackup on day: 20070618
channel ORA_DISK_3: looking for autobackup on day: 20070617
channel ORA_DISK_3: looking for autobackup on day: 20070616
channel ORA_DISK_3: looking for autobackup on day: 20070615
channel ORA_DISK_3: looking for autobackup on day: 20070614
channel ORA_DISK_3: looking for autobackup on day: 20070613
channel ORA_DISK_3: no autobackup in 7 days found
channel ORA_DISK_4: looking for autobackup on day: 20070619
channel ORA_DISK_4: looking for autobackup on day: 20070618
channel ORA_DISK_4: looking for autobackup on day: 20070617
channel ORA_DISK_4: looking for autobackup on day: 20070616
channel ORA_DISK_4: looking for autobackup on day: 20070615
channel ORA_DISK_4: looking for autobackup on day: 20070614
channel ORA_DISK_4: looking for autobackup on day: 20070613
channel ORA_DISK_4: no autobackup in 7 days found
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 06/19/2007 18:00:13
RMAN-06172: no autobackup found or specified handle is not a valid copy or piece
RMAN>
I am not able to restore spfile from rman backup ;;;

Hi,
I would like to know few things
1. How are you setting the db_name ? you can set db_id at RMAN, how are you setting the db_name ?
2. Do you have any default init file at default location ? if yes, is the db_name parameter set correctly in that file ?
Since spfile is yet to be restored, you must set the db_name parameter correctly before you start spfile restore.This can be done with init file at default location which can even contain just one paremeter i.e db_name.

RMAN backup fails using OEM with no output error

I am trying to do a weekly automatic full backup of a database in noarchivelog mode using RMAN in Enterprise Manager. Every time I submit the backup job (even if I try to do an immediate backup) the job fails almost immediately. When I Iook at the job output for the failed attempt, it says that there is no output for the job. I believe I have all of the preferred credentials and priveleges correct. Does anyone have any ideas as to what the problem could be or maybe where I can find an error log for rman to get a better explanation of the error?
Thanks

please check in metalink.....
you find useful informations here:
RMAN backup using Oracle Secure Backup fails with ORA-19511 (sbt__rpc_connect)
Doc ID: Note:396046.1
Best Regards,
Shishir Tekade.
My Blog: http://shishirtekade.blogspot.com

RMAN backup in RAC failing with error ORA-19566

Hi all, i have 2 node RAC and i am trying to take rman backup of the database which is in ASM filesystem.
There is a corruption in SYSAUX file and rman is failing to take backup of the sysaux datafile and error thrown at the end like
piece handle=/home/oracle/orabackup/BLOOM_LVL0_20120627_1qnejueh_s58_p1 tag=TAG20120627T185538 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:56
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 06/27/2012 18:56:17
*ORA-19566: exceeded limit of 0 corrupt blocks for file +DATA/bloom/datafile/sysaux.257.775475317*
Then i tried to validate the backup in rman of the datafile sysaux nad fired the following query
SQL> SELECT * FROM v$database_block_corruption;
FILE# BLOCK# BLOCKS CORRUPTION_CHANGE# CORRUPTIO
3 32011 1 0 ALL ZERO
3 32049 40 0 ALL ZERO
3 32034 1 0 ALL ZERO
3 28964 1 1399837 LOGICAL
3 32015 2 0 ALL ZERO
and found all the blocks in the table WRH$_SQL_PLAN.
Then dropped the table, and tried to take backup of the database and it is failing again with the same error..
ANY SOLUTION TO TAKE BACKUP OF THE DATABASE.
anyhow we can SET MAXCORRUPT FOR DATAFILE 3 to value, but does this works all time...
Thanks in advance,
TEJAS

Both are good suggestions, but
Osama-mustafa wrote:
RMAN> blockrecover datafile 5 block 2684; -- Fix Eror That ship has already sailed:
TEJAS_DBA wrote:
And Yes this is the first time i am taking backup on the database.And:
Osama-mustafa wrote:
Or Skip Option
Like
RMAN> RUN{
2> SET MAXCORRUPT FOR DATAFILE 1,3 to 1;
3> BACKUP DATABASE;
4> }The OP was aware of this option and hopefully was able to get at least some sort of a backup eventually. But as for the dropped WRH$_SQL_PLAN, TEJAS is, I will use the word "braver" than most. And as often is the case, Dan Morgan offered the only bit of sensible advise.
Open an SR.
Good luck.

RMAN BACKUPS TAKING A LONG TIME IN 11.1.0.6

Its almost 4 days since the RMAN Full Backup is running and it has completed almost 91% and is stuck at this point since last 2 days, so now we killed the RMAN backup Process and started the RMAN Full Backup on Disk. We need to take the RMAN Backups on Tapes.
When we take the RMAN Full Backup to Tape manually with the same script attached, the Backup runs successfully withing Hours. While if the RMAN Full Backup is running through Cronjobs , then it takes days and it gets hung.
Initially it happened with Full backup , now Incremental Backup is also not working.
Log File of Current RMAN Incremental Backup Running and in Hung state
Recovery Manager: Release 11.1.0.6.0 - Production on Mon Nov 5 20:00:02 2012
Copyright (c) 1982, 2007, Oracle. All rights reserved.
connected to target database: ZSBO (DBID=4052190355)
RMAN>
2>
3>
4> run{
5> allocate channel t1 type 'SBT_TAPE'
6> parms 'ENV=(NSR_SERVER=sa-backup01,NSR_CLIENT=sa-dm03b)';
7> allocate channel t2 type 'SBT_TAPE'
8> parms 'ENV=(NSR_SERVER=sa-backup01,NSR_CLIENT=sa-dm03b)';
9> allocate channel t3 type 'SBT_TAPE'
10> parms 'ENV=(NSR_SERVER=sa-backup01,NSR_CLIENT=sa-dm03b)';
11> allocate channel t4 type 'SBT_TAPE'
12> parms 'ENV=(NSR_SERVER=sa-backup01,NSR_CLIENT=sa-dm03b)';
13> backup
14> incremental level 2
15> format 'Incremental_zsbo_%U_%t'
16> (database);
17> sql "alter system archive log current";
18> backup
19> format 'arch_zsbo_%d_%s_%p_%t'
20> (archivelog from time 'sysdate-1' all delete input);
21> release channel t1;
22> release channel t2;
23> release channel t3;
24> release channel t4;
25> }
26>
using target database control file instead of recovery catalog
allocated channel: t1
channel t1: SID=2086 device type=SBT_TAPE
channel t1: NMO v4.5.0.0
allocated channel: t2
channel t2: SID=2075 device type=SBT_TAPE
channel t2: NMO v4.5.0.0
allocated channel: t3
channel t3: SID=2069 device type=SBT_TAPE
channel t3: NMO v4.5.0.0
allocated channel: t4
channel t4: SID=2061 device type=SBT_TAPE
channel t4: NMO v4.5.0.0
Starting backup at 05-NOV-12
channel t1: starting incremental level 2 datafile backup set
channel t1: specifying datafile(s) in backup set
input datafile file number=00096 name=/data13/oradata/zsbo/A0186LA2591_00_CURR_12.dbf
input datafile file number=00058 name=/data17/oradata/zsbo/A0436IL2022_00_PREV_01.DBF
input datafile file number=00014 name=/data7/oradata/zsbo/A1225NY2502_00_TEMP_01.dbf
input datafile file number=00087 name=/data7/oradata/zsbo/A1086IL2502_00_PREV_01.dbf
input datafile file number=00045 name=/data7/oradata/zsbo/A1143BO2515_00_CURR_IDX_01.dbf
input datafile file number=00130 name=/data7/oradata/zsbo/A0171LA2034_01_DEMO_IDX_01.dbf
input datafile file number=00080 name=/data7/oradata/zsbo/A0436IL2022_00_CURR_IDX_02.DBF
input datafile file number=00119 name=/data10/oradata/zsbo/A0136NJ2533_00_CURR_05.dbf
input datafile file number=00136 name=/data5/oradata/zsbo/A1225NY2502_00_TEMP_11.dbf
channel t1: starting piece 1 at 05-NOV-12
channel t2: starting incremental level 2 datafile backup set
channel t2: specifying datafile(s) in backup set
input datafile file number=00095 name=/data12/oradata/zsbo/A0186LA2591_00_CURR_11.dbf
input datafile file number=00075 name=/data17/oradata/zsbo/A0186LA2591_00_CURR_IDX_02.dbf
input datafile file number=00094 name=/data6/oradata/zsbo/A0186LA2591_00_CURR_10.dbf
input datafile file number=00151 name=/data10/oradata/zsbo/A0136NJ2533_00_CURR_06.dbf
input datafile file number=00148 name=/data8/oradata/zsbo/A1143BO2515_00_PREV_02.dbf
channel t2: starting piece 1 at 05-NOV-12
channel t3: starting incremental level 2 datafile backup set
channel t3: specifying datafile(s) in backup set
input datafile file number=00127 name=/data8/oradata/zsbo/A1143BO2515_00_PREV_01.dbf
input datafile file number=00018 name=/data15/oradata/zsbo/A1225NY2502_00_TEMP_05.dbf
input datafile file number=00062 name=/data15/oradata/zsbo/A0436IL2022_00_TEMP_02.dbf
input datafile file number=00081 name=/data15/oradata/zsbo/A1110CH2505_00_PREV_01.dbf
input datafile file number=00137 name=/data7/oradata/zsbo/A1225NY2502_00_TEMP_12.dbf
input datafile file number=00065 name=/data18/oradata/zsbo/A1086IL2003_00_CURR_01.dbf
input datafile file number=00103 name=/data2/oradata/zsbo/A0186LA2591_00_PREV_05.dbf
channel t3: starting piece 1 at 05-NOV-12
channel t4: starting incremental level 2 datafile backup set
channel t4: specifying datafile(s) in backup set
input datafile file number=00059 name=/data6/oradata/zsbo/A0436IL2022_00_PREV_02.DBF
input datafile file number=00068 name=/data5/oradata/zsbo/A0186LA2591_00_CURR_01.dbf
input datafile file number=00071 name=/data9/oradata/zsbo/A0186LA2591_00_CURR_04.dbf
input datafile file number=00078 name=/data10/oradata/zsbo/A0136NJ2533_00_CURR_01.dbf
channel t4: starting piece 1 at 05-NOV-12 ----> No Progress since last 10 hours
Any help will be appreciated.
Regards,
Mohit
Edited by: 969777 on Nov 6, 2012 4:29 AM

Hi,
We have upgraded our database from 10.2.0.3 to 11.1.0.6.
The Script runs fine when we take command line backup on disk which we took 6 days backup, but when we schedule the same on cronjob RMAN Full Backup completes till 91% and it hangs forever. Everything was running fine with Incremental backup which we took 2 days before and it ran successfully but the above log is of Incremental Backup which is still in Hang state from the last 10 Hours , but still showing no Errors.
Please let me know if anything you want to confirm.
Thanks for ur prompt response,
Mohit

RMAN backup restore leads to the error "ORA-00600: internal error code, arguments: [kccsbck_first], [2], [2349545192]" on DB startup

Hi All,
DB:11.2.0.3.0
OS: Sun Solaris SPARC 64 bits
I am facing an issue - RMAN backup restore leads to the error "ORA-00600: internal error code, arguments: , , " on DB startup. Restored from RMAN backup DB test2 to DB test1.
 $ sqlplus / as sysdba
 SQL*Plus: Release 11.2.0.3.0 Production on Sun Oct 6 09:31:28 2013
 Copyright (c) 1982, 2011, Oracle. All rights reserved.
 Connected to an idle instance.

SQL> startup
ORACLE instance started.
Total System Global Area 4277059584 bytes
Fixed Size 2166160 bytes
Variable Size 1493176944 bytes
Database Buffers 2768240640 bytes
Redo Buffers 13475840 bytes
ORA-00600: internal error code, arguments: , , ,
SQL> exit
DB test2 database validated:
RMAN> validate Database;
No issues reported.
Could anyone please let me the what's the cause of this error
Thanks for your time
Regards,
user10088255

HI,
CASE : I
C:\>set ORACLE_SID=xxxx
C:\>sqlplus sys/XXXXX@rosen as sysdba
SQL*Plus: Release 11.2.0.1.0 Production on Sat Jan 29 12:28:00 2011
Copyright (c) 1982, 2010, Oracle. All rights reserved.
Connected to an idle instance.
SQL> startup
ORACLE instance started.
Total System Global Area 3423965184 bytes
Fixed Size 2180544 bytes
Variable Size 2080377408 bytes
Database Buffers 1325400064 bytes
Redo Buffers 16007168 bytes
ORA-00600: internal error code, arguments: [kccsbck_first], [1], [3978145973],
Solution: AFTER GETTING ORA-00600, SHUT THE DATABASE AND STARTUP IT INTO MOUNT STAGE AND THEN ALTER DATABASE TO OPEN STAGE .
SQL> shut immediate
ORA-01507: database not mounted
ORACLE instance shut down.
SQL> startup mount
ORACLE instance started.
Total System Global Area 3423965184 bytes
Fixed Size 2180544 bytes
Variable Size 2080377408 bytes
Database Buffers 1325400064 bytes
Redo Buffers 16007168 bytes
Database mounted.
SQL> alter database open;
Database altered.
SQL> select name,open_mode from v$database;
NAME OPEN_MODE
ROSEN READ WRITE
CASE :: II
C:\>sqlplus sys/XXXX@royalton as sysdba
SQL*Plus: Release 11.2.0.1.0 Production on Sat Jan 29 12:37:37 2011
Copyright (c) 1982, 2010, Oracle. All rights reserved.
Connected to an idle instance.
SQL> startup
ORACLE instance started.
Total System Global Area 3423965184 bytes
Fixed Size 2180544 bytes
Variable Size 1979714112 bytes
Database Buffers 1426063360 bytes
Redo Buffers 16007168 bytes
ORA-00600: internal error code, arguments: [kccsbck_first], [1], [73515151],[], [], [], [], [], [], [], [], []
Solution : As in above case, I have started the database in mount and then alter it to the open mode but it doesnot work out. After some analysis ,troubleshooting and googling, we have decided to flush the shared pool component of the SGA . So, we have started the database in mount stage and then flush the shared pool and further alter it to open stage . Below are the steps performed to solve this issue .
SQL> shut immediate
ORA-01507: database not mounted
ORACLE instance shut down.
C:\>set ORACLE_SID= royalton
C:\>sqlplus sys/xxxxxxxx@royalton as sysdba
SQL*Plus: Release 11.2.0.1.0 Production on Sat Jan 29 12:28:00 2011
Copyright (c) 1982, 2010, Oracle. All rights reserved.
Connected to an idle instance.
SQL> startup mount
ORACLE instance started.
Total System Global Area 3423965184 bytes
Fixed Size 2180544 bytes
Variable Size 2080377408 bytes
Database Buffers 1325400064 bytes
Redo Buffers 16007168 bytes
Database mounted.
SQL> alter system flush shared_pool;
SQL> alter database open
Database altered.
SQL> select name,open_mode from v$database;
NAME OPEN_MODE
ROYALTON READ WRITE
Conclusion : Though this is not the solution but a workaround to solve ORA-00600 which is having same argument as above, then you may follow the above steps.
Please chek this link : One Can Succeed at Almost Anything For Which He Has Enthusiasm...: ORA-00600: internal error code, arguments: [kccsbck_f…

Rman backup error: ORA-19502

I am running a rman backup script with incremental 1 level as
backup as backupset incremental level 1 cumulative device type disk tag 'Baan_bkup$LEVEL_0' database;
recover copy of database;
backup device type disk tag 'Baan_bkup$LEVEL_0' archivelog all not backed up;
backup archivelog until time 'sysdate-6' delete all input;
delete noprompt obsolete device type disk;
It has run almost two weeks and last night it showed this error and failed
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 11/08/2006 03:02:14
ORA-19502: write error on file "/dbrecovery/flashback/goi1rkdm_1_1", blockno 164865 (blocksize=8192)
ORA-27072: File I/O error
Additional information: 4
Additional information: 164865
Additional information: 782336
Linux Error: 2: No such file or directory
I checked the df -k and I still have about 6% space in my /dbrecovery disk, a separated space, and I did not find the file indicated either. So was still possible the space is full? or others reason?
I used the "delete obsolete"command in rman but nothing can be deleted.

It seems your filesystem cannot handle large files (> 2G). Use 'maxpiecesize' option of 'allocate channel' command to limit the filesize.
Werner

Intermittent OCFS2 Heartbeat Errors During RMAN Backup

Hello all. If this is better suited to an OCFS2 list, please let me know.
I have an Oracle 10g RAC (10.2.0.2), on which one node runs an RMAN backup nightly around 10:45 PM. The node is running on RHEL4 x64 with 8 GB of RAM.
About every other night these errors turn up in the messages log in the server:
Apr 19 23:48:23 servername kernel: (4059,2):o2hb_setup_one_bio:371 ERROR: Could not alloc slots BIO!
Apr 19 23:48:23 servername kernel: (4059,2):o2hb_read_slots:507 ERROR: status = -12
Apr 19 23:48:23 servername kernel: (4059,2):o2hb_do_disk_heartbeat:973 ERROR: status = -12
This only seems to happen when the RMAN backup is in progress, and I get these at no other time of the day.
Can anyone point me to a reference for what these error codes mean, and if you've encountered these before can you tell me what impact this has and how it can be resolved? I'm assuming that the read/write load on the block device for the OCFS2 mount is causing issues, but this all conjecture without an explanation of the error code.
Thanks in advance,
Dan

Thanks for the response!
Kernel is: 2.6.9-34.0.2.ELsmp
ocfs2 is: ocfs2-2.6.9-34.0.2.ELsmp-1.2.4-2
To my knowledge it's never lead to a fence, and these are the only ocfs2 messages logged in the system log. When these messages occur, there doesn't seem to be any other symptom and the backup completes.
To be honest, we've never had issues with ocfs2 since we set this RAC node up, so I'm sad to say I don't even know what messages a fencing event would create.

Rman Backup time error

Similar Messages

Maybe you are looking for