Problem with RMAN.

Hi, i worked with Oracle Database 10g Express Edition, my problem is the execute the Backup utility, display the message error:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: fallo del comando backup en el canal ORA_DISK_1 en 08/17/2008 15:30:
01
ORA-19566: se ha excedido el lÝmite de 0 bloques corruptos para el archivo C:\OR
ACLEXE\ORADATA\XE\SYSTEM.DBF
Recovery Manager terminado.
==================== ERROR =============================
Backup of the database failed.
RMAN Error - See log for details .
Log file is at C:\ORACLEXE\APP\ORACLE\PRODUCT\10.2.0\SERVER\DATABASE\OX
E_BACKUP_CURRENT.LOG.
==================== ERROR =============================
Roberto.

Have you reviewed:
RMAN-03009: failure of backup command; ORA-19566: exceeded limit of ...
HTH,
Scott

Similar Messages

Problem with RMAN incomplete recovery

Oracle Version: 9i
Operating System: Windows 2000
I have a problem with RMAN incomplete recovery until sequence.
According to my database structure ............
SQL> SELECT GROUP#,SEQUENCE#,THREAD# FROM V$LOG;
GROUP# SEQUENCE# THREAD#
1 14 1
2 13 1
3 12 1
I took the backup of backup of full database using RMAN and i am trying to recover like this:
RUN
ALLOCATE CHANNEL C1 TYPE DISK;
SET UNTIL SEQUENCE 7 THREAD 1;
RESTORE DATABASE;
RECOVER DATABASE;
ALTER DATABASE OPEN RESETLOGS;
BUT i am getting a message saying there is no backup of DATAFILE 1,2,......10 to restore although my database is in archivelog mode and i took a backup.
Yachendra

Please consult v$backup_datafile.
It will tell you when the file was backed up.
RMAN will always search for a datafile backup prior to the logsequence or whatever is limiting the incomplete recovery.
Likely when you made your backup Oracle was already past sequence 7.
Sybrand Bakker
Senior Oracle DBA

Problem with RMAN on Oracle8.1.7 on Redhat Linux 6.2

Hi, does anyone who is using Oracle with the configuration listed below having problems running RMAN?
- Redhat 6.2 with kernel upgraded to 2.2.16-3
- Oracle 8.1.7 EE for Linux
I don't seem to be able to start RMAN even though I have enable LARGE_POOL_SIZE in the parameter file.
Whenever I type rman at the prompt, it just hangs!
If I issue rman catalog rman/rmancatdb, it will return with an error saying can't connect to catalog.
I got these messages when creating the recovery catalog for the 1st time.
I suspect its the rman executable that is playing pranks with me. I even issue "relink all" and still can't run rman.
If anyone know a solution to this please reply. Thanks.

Hi there,
Its funny...I found a solution to my problem from oracle metalink.
if anyone face the same problem you can see the solution here.
The solution is....check your PATH in .bash_profile
Make sure the $ORACLE_HOME/bin is specified before the $PATH so that it can call the right Oracle rman executable. This is becoz Linux has a command by the same name rman.
The Oracle metalink explanation is below.
On typing rman at the command prompt, the process goes for a hang. The rman utility
is not invoked nor there is any error message displayed at the prompt.
If the user types rman -h , then the following error message appears on the
screen:
rman
[-f <ASCII|roff|TkMan|Tk|Sections|HTML|SGML|MIME|LaTeX|LaTeX2e|RTF|pod>]
[-S(ource of man page passed in)] [-F(ormatted man page passed in)]
[-r <man reference printf string>] [-l <title printf string>]
[-V(olume) <colon-separated list>] [-U(RLs as hyperlinks)]
[-b (show subsections)] [-k(eep head/foot)]
[-n(ame of man page) <string>] [-s(ection) <string>]
[-p(aragraph mode toggle)] [-t(abstops spacing) <number>]
[-N(ormalize spacing, changebars)] [-y (zap hyphens toggle)]
[-K (declare that page has no breaks)]
[-d(iff) <file> (old version of page source to incorporate)]
[-M(essage) <text> (included verbatim at end of Name section)]
[-R(ebus words for TkMan)] [-C (enable Tcl/Tk formatting)]
[-o (no op)] [-O <arg> (no op with arg)]
[-q(uiet--don't report warnings)] [-h(elp)] [-v(ersion)]
[<filename>]
Solution Description
Find out which rman utility is invoked by typing ,
'which rman' at the command prompt.
Ensure that the correct utility is invoked from $ORACLE_HOME/bin directory.
Explanation
In linux, there is a OS utility called rman. This utility is used for formatting
purposes.This resides in the /usr/bin directory.
If the ORACLE_HOME is not set properly or the PATH variable contains ORACLE_HOME/bin
at the end instead of beginning, then the rman utility provided by oracle is
not invoked.Also, no error message is thrown out, since there is another utility
by the same name.
When the environment variables are properly set, then the correct utility is
invoked from the $ORACLE_HOME/bin
Good Luck to whoever needs this solution.
null

Problem with rman backups

We upgraded, the rman catalog due to the following error:
PL/SQL package RMAN.DBMS_RCVCAT version 11.02.00.01 in RCVCAT database is not current PL/SQL package RMAN.DBMS_RCVMAN version 11.02.00.01 in RCVCAT database is not current
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of sql command at 01/17/2011 21:00:36
ORA-03114: not connected to ORACLEWe registered our database on the catalog again
problem we have now is that our backup fails with the following errors:
RMAN> connect target *
2> connect catalog *
3>
4> run {
5> crosscheck archivelog all;
6> }
7>
connected to target database: MAC (DBID=710471977)
connected to recovery catalog database
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of crosscheck command at 01/20/2011 06:00:29
ORA-03114: not connected to ORACLEany suggestions, as to how we can fix these errors

Must this be done fron the local machine where my backup scripts reside..
or must it be done on the catalog server?????
I ran the crosscheck command from the local machine without connecting to the catalog
here are the eroors I received:
oracle $ rman
Recovery Manager: Release 11.2.0.2.0 - Production on Thu Jan 20 11:42:42 2011
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
RMAN> connect target /
connected to target database: MAC (DBID=710471977)
RMAN> run{
2> crosscheck backup COMPLETED AFTER 'sysdate-1';
3> }
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of crosscheck command at 01/20/2011 11:43:48
RMAN-12010: automatic channel allocation initialization failed
ORA-03114: not connected to ORACLE
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
ORA-03114: not connected to ORACLE
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of crosscheck command at 01/20/2011 11:43:48
RMAN-12010: automatic channel allocation initialization failed
ORA-03114: not connected to ORACLE

Problem with RMAN script

Hi,
I have wriiten RMAN script to report need backup?below the code
#!/bin/ksh
export ORACLE_SID=test1
echo $ORACLE_SID
export ORACLE_HOME=/u01/app/oracle/product/10.2.0/db_1
echo $ORACLE_HOME
export PATH
echo $PATH
RMAN=$ORACLE_HOME/bin/rman
$RMAN target sys/sys@test1 nocatalog
RUN {
report need backup;}
exit;
echo "Completd"The problem is that when i run the script it goes into the RMAN prompt and doesnt run "report need backup". I guess its unable to recognize the run command.below the error
./full_db_hot_backup.sh[14]: RUN: not found [No such file or directory]
./full_db_hot_backup.sh: line 14: syntax error at line 15: `}' unexpected

Write as following
$ORACLE_HOME/bin/rman << EOF
connect target /
run
report need backup;
exit
EOF
Talip Hakan Ozturk
http://taliphakanozturken.wordpress.com/

Problems with RMAN redundancy retention

Edited by: 878226 on Dec 5, 2011 7:05 PM

paste from sql
SQL>show parameter control_file_record_keep_timeAs well paste yours daily backup scripts.

RMAN problem with block corruption

Hi
I have problem with the block corruption in one of the database .
here is the error message .
ora-01578:oracle data block corrupted (file# 10,block # 55309) ora-01110: data file 10:
'/db/gist1/data/gist1_gis_nologging_01.dbf' ora-26040: data block was loaded using the NOLOGGING option .
gisq SQL> select * from v$database_block_corruption;
FILE# BLOCK# BLOCKS CORRUPTION_CHANGE# CORRUPTIO
10 11 126 3754364971 LOGICAL
RMAN> blockrecover datafile 10 block 11;
Starting blockrecover at 14/DEC/2012 16:25:48
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of blockrecover command at 12/14/2012 16:25:48
RMAN-05009: Block Media Recovery requires Enterprise Edition
Could some one help me in providing solution for this . we we have standard addition only .
Thanks in advance ...

It appears that there was a NOLOGGING operation on an object that resides in '/db/gist1/data/gist1_gis_nologging_01.dbf' .
NOLOGGING operations, as the name suggests, do generate limited redo log, which makes the objects affected by them non-recoverable.
RMAN Blockrecover, as far as I understand, uses full and archivelog backup to perform the block recovery. Since the archivelog backup does not store any changes related to the NOLOGGING operation, then Blockrecover would not be able to help you even if you were licensed.
You can try to restore the object as of the most recent full backup…
Iordan Iotzov
http://iiotzov.wordpress.com/

Problem with .cmd/batch file, while scheduling RMAN backup

I am running Oracle 10g on Windows. I Have written RMAN Backup script & saved it as .cmd file. Now i will schedule this via AT utility on windows. While i try to run this .cmd file then after starting RMAN it does nothing, neither RMAN gets connected to target database nor backup gets started. What may be the problem??
Contents of .cmd file are like this:-
RMAN target 'sys/manager@test'
backup database include current controlfile;
backup archive log;
Message was edited by:
user648257
Message was edited by:
user648257

RMAN target 'sys/manager@test'
backup database include current controlfile;
backup archive log;will not work. You are passing 3 different commands to the Windows command interpreter. CMD executes the first command 'RMAN target ...@test" and waits for it to complete before it will proceed to attempt to execute the "backup database".
That is, the "backup database" command isn't being passed to RMAN at all.
You should put the two "backup" commands in a script file (as you would do for an SQLPlus script file) -- eg backup.rmn and execute it with rman
eg
rman target 'sys/manager@test' @backup.rmn

[RMAN] problem with registering database

Hello, we have RAC environment on two nodes. We created rman catalog database and then registered our database with REGISTER DATABASE command. After that we issued command SHOW ALL and encountered an error:
RMAN> show all;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 21 DAYS;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
could not read file header for datafile 74 error reason 4
could not read file header for datafile 74 error reason 4
could not read file header for datafile 74 error reason 4
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/10.2.0/db_1/dbs/snapcf_easy1.f'; # default
this is new catalog database, which is to replace the old one
how to deal with this problem ?

So you are following up on datafile 74 in this other thread :
problem with datafile recovery
Hemant K Chitale

Problem creating physical Standby database with RMAN

Hi All
I am trying to learn oracle dataguard and as part of the process learning creating standby database.
Platform : Sun-Fire-V250 Sparc, Solaris 10
Database Version - Oracle 11R2
I am creating standby database on same server, so directory structure is different.
Following the instructions on Oracle site I managed to create a functional physical standby database. But I am not able to create standby database using RMAN. These are the steps that I followed-
1.Set up all necessary parameters on primary database as done while creating physical standby database manually, eg setting force logging, creating standby logs etc.
2.Edited parameter file on primary database as done while creating manual pysical standby database creation. Some of the changes done are-
On Primary Database:
*.FAL_CLIENT='orcl11020' #Primary database unique name
*.FAL_SERVER='stdby_11' #Standby database unique name
db_file_name_convert='/<dir>/oradata/stdby_11','/<dir>/oradata/orcl11020'
log_file_name_convert='/<dir>/oradata/stdby_11','/<dir>/oradata/orcl11020','/<dir>/oradata/stdby_11/redo_mem','/<dir>/oradata/orcl11020/redo_mem'
standby_file_management=auto
*.log_archive_config='DG_CONFIG=(orcl11020,stdby_11)'
*.log_archive_dest_1='LOCATION=/<dir>/flash_recovery_area/ORCL11020/archivelog
VALID_FOR=(ALL_LOGFILES,ALL_ROLES) db_unique_name=orcl11020'
*.log_archive_dest_2='SERVICE=stdby_11 LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) db_unique_name=stdby_11'
*.LOG_ARCHIVE_DEST_STATE_1='ENABLE'
*.LOG_ARCHIVE_DEST_STATE_2='ENABLE'
*.LOG_ARCHIVE_FORMAT='%t_%s_%r.arc'
*.LOG_ARCHIVE_MAX_PROCESSES=30
Copied same pfile for standby database and modified following-
*.control_files='/<dir>/oradata/stdby_11/stdby_11.ctl','/<dir>/fra_stdby/stdby_11/stdby_11.ctl'
*.db_name='orcl1102'
*.db_unique_name='stdby_11'
*.FAL_CLIENT='stdby_11'
*.FAL_SERVER='orcl11020'
db_file_name_convert='/<dir>/oradata/orcl11020','/<dir>/oradata/stdby_11'
log_file_name_convert='/<dir>/oradata/orcl11020','/<dir>/oradata/stdby_11','/<dir>/oradata/orcl11020/redo_mem','/<dir>/oradata/stdby_11/redo_mem'
standby_file_management=auto
*.log_archive_dest_1='LOCATION=/<dir>/fra_stdby/STDBY_11/archivelog
VALID_FOR=(ALL_LOGFILES,ALL_ROLES) db_unique_name=stdby_11'
*.log_archive_dest_2='SERVICE=orcl11020 LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)
db_unique_name=orcl11020'
3. Add relevant information in tnsnames.ora and listener.ora files and then restart listener.
3. Created password file with same credential as primary database.
4.Up-to-date RMAN backup of primary database available.
5.Create standby controlfile with rman
While primary database s open (I tried with primary database in mount mode as well)-
$>rman catalog rman/paswd@rman target /
RMAN> BACKUP CURRENT CONTROLFILE FOR STANDBY;
6. Open a new terminal and startup standby database in nomount mode using parameter file created -
$>ORACLE_SID=stdby_11
$>export ORACLE_SID
$>sqlplus / as sysdba
SQL>STARTUP NOMOUNT pfile='<location/initfilename.ora'
SQL>quit
$> rman AUXILIARY / target sys/passwd@orcl11020 catalog rman/passwd@rman
RMAN>DUPLICATE TARGET DATABASE FOR STANDBY DORECOVER;
RMAN finishes without error but archive logs are not being tranported. Looking at the log, following caught my eye-
Error 1017 received logging on to the standby
Check that the primary and standby are using a password file
and remote_login_passwordfile is set to SHARED or EXCLUSIVE,
and that the SYS password is same in the password files.
returning error ORA-16191
FAL[client, ARC2]: Error 16191 connecting to orcl11020 for fetching gap sequence
Errors in file /<>dir>/diag/rdbms/stdby_11/stdby_11/trace/stdby_11_arc2_24321.trc:
ORA-16191: Primary log shipping client not logged on standby
Errors in file /<dir>/diag/rdbms/stdby_11/stdby_11/trace/stdby_11_arc2_24321.trc:
ORA-16191: Primary log shipping client not logged on standby
So on both primary and standby I confirmed
SQL> show parameter remote_login_passwordfile
NAME TYPE VALUE
remote_login_passwordfile string EXCLUSIVE
To make double sure that password files are same, I shutdown both databases, delete password files and recreated with same credentials.
Password files are called - orapworcl11020 and orapwstdby_11
Can someone guide me where thisngs are going wrong here please.

Not sure if I understood it clearly.
SELECT * FROM V$ARCHIVE_GAP;
returns no rows so there is no gap.
But could you please explain me the result of the previous query. To catch up again, on standby when I check
SELECT SEQUENCE#,APPLIED FROM V$ARCHIVED_LOG
SEQUENCE# APPLIED
75 NO
74 NO
76 NO
77 NO
I understand that though archive files have been copied across but they are not applied yet.
On primary when I give your query -
SELECT name as STANDBY,SEQUENCE#,applied, completion_time
2 FROM v$archived_log
3 where dest_id=2
4 and sequence# BETWEEN 74 and 80;
I get -
STANDBY SEQUENCE# APPLIED COMPLETIO
stdby_11 74 YES 28-JUN-11
stdby_11 75 YES 28-JUN-11
stdby_11 76 YES 29-JUN-11
stdby_11 77 YES 29-JUN-11
stdby_11 78 YES 29-JUN-11
stdby_11 79 YES 29-JUN-11
stdby_11 80 YES 29-JUN-11
stdby_11 75 NO 07-JUL-11
stdby_11 74 NO 07-JUL-11
stdby_11 76 NO 07-JUL-11
stdby_11 77 NO 07-JUL-11
stdby_11 78 NO 07-JUL-11
I have intentionally given
sequence# BETWEEN 74 and 80
because I know in the current incarnaion of the database, max sequence is 78.
So my understanding is, the rows between 28-29 June are from previous incarnation, correct me if I am wrong
Archive files of the current incarnation, since I successfully created standby database are shipped but yet to be applied - am I right?
Then my final question is, when will these archives be applied to standby database?
I am sorry to ask too many questions but I am just trying to understand how it all works.
Thanks for your help again

[HELP] Problem with restore and recovery to new host

Hi, guys!
I have been trying for two days, but still cannot get it to work.
I have taken a full hot(online) backup with archive logs as well as the control file and SPFILE, and then copied the backup to the new host with the same directory structure and settings. Finally, I have tried to restore & recover the database on the new host but failed during the restore process.
Both the original host and the new host have the same Oracle installed down to the patch level. I couldn't figure out the proper solution to this problem base on my limited knowledge about Oracle DB.
Could anyone help me out here? Any advice would be appreciated!
RMAN> restore database until sequence 10 thread 1;
Starting restore at 08-NOV-11
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to D:\DBDATA\PRODDB\SYSTEM01.DBF
restoring datafile 00002 to D:\DBDATA\PRODDB\UNDOTBS01.DBF
restoring datafile 00003 to D:\DBDATA\PRODDB\SYSAUX01.DBF
restoring datafile 00004 to D:\DBDATA\PRODDB\USERS01.DBF
restoring datafile 00005 to D:\ORA_DATADATA01.DBF
restoring datafile 00006 to D:\ORA_DATA\DATA02.DBF
restoring datafile 00007 to D:\ORA_DATA\INDX01.DBF
restoring datafile 00008 to D:\ORA_DATA\INDX02.DBF
channel ORA_DISK_1: reading from backup piece C:\ORACLE\PRODUCT\10.2.0\FLASH_REC
OVERY_AREA\PRODDB\BACKUPSET\2011_11_07\O1_MF_NNNDF_TAG20111107T175037_7CH6YYVJ_.BK
P
failover to previous backup
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 11/08/2011 11:41:33
RMAN-06026: some targets not found - aborting restore
RMAN-06023: no backup or copy of datafile 4 found to restore
RMAN-06023: no backup or copy of datafile 3 found to restore
RMAN-06023: no backup or copy of datafile 2 found to restore
RMAN-06023: no backup or copy of datafile 1 found to restore
Here is some extra information that you might want to know about:
RMAN> list incarnation;
List of Database Incarnations
DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
1 1 PRODDB 3774691295 PARENT 1 17-APR-07
2 2 PRODDB 3774691295 PARENT 521803 06-OCT-11
3 3 PRODDB 3774691295 PARENT 1595143 20-OCT-11
4 4 PRODDB 3774691295 PARENT 1600974 20-OCT-11
5 5 PRODDB 3774691295 PARENT 1952053 27-OCT-11
6 6 PRODDB 3774691295 CURRENT 2146951 07-NOV-11
RMAN> list backup recoverable;
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
37 Full 822.34M DISK 00:29:47 07-NOV-11
BP Key: 37 Status: AVAILABLE Compressed: NO Tag: TAG20111107T175037
Piece Name: C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\PRODDB\BACKUPSET\
2011_11_07\O1_MF_NNNDF_TAG20111107T175037_7CH6YYVJ_.BKP
List of Datafiles in backup set 37
File LV Type Ckp SCN Ckp Time Name
1 Full 2149673 07-NOV-11 D:\DBDATA\PRODDB\SYSTEM01.DBF
2 Full 2149673 07-NOV-11 D:\DBDATA\PRODDB\UNDOTBS01.DBF
3 Full 2149673 07-NOV-11 D:\DBDATA\PRODDB\SYSAUX01.DBF
4 Full 2149673 07-NOV-11 D:\DBDATA\PRODDB\USERS01.DBF
5 Full 2149673 07-NOV-11 D:\ORA_DATA\DATA01.DBF
6 Full 2149673 07-NOV-11 D:\ORA_DATA\DATA02.DBF
7 Full 2149673 07-NOV-11 D:\ORA_DATA\INDX01.DBF
8 Full 2149673 07-NOV-11 D:\ORA_DATA\INDX02.DBF
BS Key Type LV Size Device Type Elapsed Time Completion Time
38 Full 6.95M DISK 00:00:03 07-NOV-11
BP Key: 38 Status: AVAILABLE Compressed: NO Tag: TAG20111107T182034
Piece Name: C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\PRODDB\AUTOBACKUP
\2011_11_07\O1_MF_S_766606834_7CH8Q439_.BKP
Control File Included: Ckp SCN: 2151141 Ckp time: 07-NOV-11
SPFILE Included: Modification time: 07-NOV-11
BS Key Size Device Type Elapsed Time Completion Time
39 18.46M DISK 00:00:05 08-NOV-11
BP Key: 39 Status: AVAILABLE Compressed: NO Tag: TAG20111108T093359
Piece Name: C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\PRODDB\BACKUPSET\
2011_11_08\O1_MF_ANNNN_TAG20111108T093359_7CJY7TG1_.BKP
List of Archived Logs in backup set 39
Thrd Seq Low SCN Low Time Next SCN Next Time
1 1 2146951 07-NOV-11 2149493 07-NOV-11
1 2 2149493 07-NOV-11 2149519 07-NOV-11
1 3 2149519 07-NOV-11 2149565 07-NOV-11
1 4 2149565 07-NOV-11 2149641 07-NOV-11
1 5 2149641 07-NOV-11 2172859 07-NOV-11
1 6 2172859 07-NOV-11 2197851 07-NOV-11
1 7 2197851 07-NOV-11 2220349 08-NOV-11
1 8 2220349 08-NOV-11 2222621 08-NOV-11
1 9 2222621 08-NOV-11 2222729 08-NOV-11
1 10 2222729 08-NOV-11 2223088 08-NOV-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
40 Full 6.95M DISK 00:00:00 08-NOV-11
BP Key: 40 Status: AVAILABLE Compressed: NO Tag: TAG20111108T093411
Piece Name: C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\PRODDB\AUTOBACKUP
\2011_11_08\O1_MF_S_766661651_7CJY84LK_.BKP
Control File Included: Ckp SCN: 2223097 Ckp time: 08-NOV-11
SPFILE Included: Modification time: 08-NOV-11
Thanks in advance!
Jay

Thank you for your reply,Hemant K Chitale!
>
a) Does the directory structur exist on the new server :
D:\DBDATA\PRODDB\ --- for files 1 to 4
D:\ --- for file 5
D:\ORA_DATA\ --- for files 6 to 8
>
Yep, I have doubled check the directory structure that get in the way, and they are all exist.
Would it be something to do with the folder permissions?
>
b) Apparently a RESETLOGS has been issued on 07-Nov. Which controflile backup do you have restored and mounted on the new server ? It should be the one after the RESETLOGS.
>
I restored the one included with the backup. Should I take another backup of controlfile seperately and restore from it instead?
>
(I assume that you did a RESTORE CONTROLFILE followed by sql "alter database mount" before the attempt to RESTORE DATABASE)
>
Yep, that's exactly what I did.
//executed @ RMAN prompt of the new host
startup nomount; 'the new host has the right SPFILE to start with so i didn''t bother to RESTORE SPFILE first.
restore controlfile from autobackup;
alter database mount;
restore database sequence 10 thread 1;
//get stucked here with RMAN-06026, 06023
//...the following is not executed yet.... :-(
recover database until sequence 10;
alter database open resetlogs;Edited by: HappyJay on 2011/11/08 13:25
I have made several attemps with your advice, but still get the same type of errors.
Here is the output:
RMAN> list backup of controlfile;
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
38 Full 6.95M DISK 00:00:03 07-NOV-11
BP Key: 38 Status: AVAILABLE Compressed: NO Tag: TAG20111107T182034
Piece Name: C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\PRODDB\AUTOBACKUP
\2011_11_07\O1_MF_S_766606834_7CH8Q439_.BKP
Control File Included: Ckp SCN: 2151141 Ckp time: 07-NOV-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
40 Full 6.95M DISK 00:00:00 08-NOV-11
BP Key: 40 Status: AVAILABLE Compressed: NO Tag: TAG20111108T093411
Piece Name: C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\PRODDB\AUTOBACKUP
+\2011_11_08\O1_MF_S_766661651_7CJY84LK_.BKP+
Control File Included: Ckp SCN: 2223097 Ckp time: 08-NOV-11
as you suggested, this backup piece of controlfile should be right one to be restored.
RMAN> shutdown;
database dismounted
Oracle instance shut down
RMAN> startup nomount;
connected to target database (not started)
Oracle instance started
Total System Global Area 490733568 bytes
Fixed Size 1291360 bytes
Variable Size 364907424 bytes
Database Buffers 121634816 bytes
Redo Buffers 2899968 bytes
RMAN> restore controlfile from autobackup;
Starting restore at 08-NOV-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=157 devtype=DISK
recovery area destination: C:\oracle\product\10.2.0\flash_recovery_area
database name (or database unique name) used for search: PRODDB
channel ORA_DISK_1: autobackup found in the recovery area
channel ORA_DISK_1: autobackup found: C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AR
EA\PRODDB\AUTOBACKUP\2011_11_08\O1_MF_S_766661651_7CJY84LK_.BKP
channel ORA_DISK_1: control file restore from autobackup complete
output filename=D:\DBDATA\PRODDB\CONTROL01.CTL
output filename=D:\DBDATA\PRODDB\CONTROL02.CTL
output filename=D:\DBDATA\PRODDB\CONTROL03.CTL
Finished restore at 08-NOV-11
tried shutdown normally and mount again instead.
RMAN> shutdown;
Oracle instance shut down
RMAN> exit
Recovery Manager complete.
C:\>rman target /
Recovery Manager: Release 10.2.0.3.0 - Production on Tue Nov 8 13:49:42 2011
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database (not started)
RMAN> startup mount;
Oracle instance started
database mounted
Total System Global Area 490733568 bytes
Fixed Size 1291360 bytes
Variable Size 369101728 bytes
Database Buffers 117440512 bytes
Redo Buffers 2899968 bytes
RMAN> restore database until sequence 10 thread 1;
Starting restore at 08-NOV-11
Starting implicit crosscheck backup at 08-NOV-11
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK
Crosschecked 3 objects
Finished implicit crosscheck backup at 08-NOV-11
Starting implicit crosscheck copy at 08-NOV-11
using channel ORA_DISK_1
Crosschecked 2 objects
Finished implicit crosscheck copy at 08-NOV-11
searching for all files in the recovery area
cataloging files...
cataloging done
List of Cataloged Files
=======================
File Name: C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\PRODDB\AUTOBACKUP\2011_11_
08\O1_MF_S_766661651_7CJY84LK_.BKP
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to D:\DBDATA\PRODDB\SYSTEM01.DBF
restoring datafile 00002 to D:\DBDATA\PRODDB\UNDOTBS01.DBF
restoring datafile 00003 to D:\DBDATA\PRODDB\SYSAUX01.DBF
restoring datafile 00004 to D:\DBDATA\PRODDB\USERS01.DBF
restoring datafile 00005 to D:\ORA_DATA\DATA01.DBF
restoring datafile 00006 to D:\ORA_DATA\DATA02.DBF
restoring datafile 00007 to D:\ORA_DATA\INDX01.DBF
restoring datafile 00008 to D:\ORA_DATA\INDX02.DBF
channel ORA_DISK_1: reading from backup piece C:\ORACLE\PRODUCT\10.2.0\FLASH_REC
OVERY_AREA\PRODDB\BACKUPSET\2011_11_07\O1_MF_NNNDF_TAG20111107T175037_7CH6YYVJ_.BK
P
failover to previous backup
//however, still get the same results(ended up with errors)
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 11/08/2011 13:50:29
RMAN-06026: some targets not found - aborting restore
RMAN-06023: no backup or copy of datafile 4 found to restore
RMAN-06023: no backup or copy of datafile 3 found to restore
RMAN-06023: no backup or copy of datafile 2 found to restore
RMAN-06023: no backup or copy of datafile 1 found to restore
Edited by: HappyJay on 2011/11/08 13:59

Problem with OEM backing up on windows system.

Hi to all,
I have a problem with backing up with a specific user.
I am currently running various "test" db's and am planning to back them up.
The Setup:
Host OS is windows 2003 server s2
Grid control 10.2.0.1
Database 10.2.0.2
Target Db is running on a windows 2003 server
The Situation:
From grid control I locate the db in question and go to the maintenance page and the backup settings. First of all I want to test the backup using the tab. Before this of course I enter the Host OS credentials into the system, let’s say "jamie", and add the appropriate password. By this point I have made sure that the user "jamie" is in the local security policy setting "log on as batch job" and that is in the group ora_dba (This is on both the machine I am backing up from and the target db machine.). For security reasons I have limited the share folder location to the user "jamie", making sure that sharing and security has the appropriate privileges to access the share.
I run a test backup using the tab within backup settings and await the results. The results come back unsuccessful. Reading through the log I see that the path to backup share is denied.
So to further the test I change the privileges within the share to "everyone" and that is for both sharing and security, just to see whether or not it’s the path itself rather than restrictions to the user. It is then a success. I checked to see who actually owned the file that was used within the test. It belonged to the local system on the target db, not to the user that I had specified within "Host OS Credentials".
Can anyone explain to me why and what is the reason behind putting in Host OS Credentials when the agent that is committing the back up is using the local domain system user account. I am aware that the Agent is part of a service within windows and belongs to the local domain. Ergo, why have host credentials.
And can anyone help me out with getting round this predicament if I still want security within the systems. I can’t just leave access to the share under "everyone", that'd be a really big hole in the system?!
Any help at all will be gratefully received.
If you’ve got any questions to help me solve the problem, please fire away.

You may want to take a look at these metalink notes:
Ref.
Subject:      ERROR in RMAN to Write to Shared Drives on Windows NT/2000
     Doc ID:      Note:246107.1      Type:      PROBLEM
     Last Revision Date:      08-JUL-2004      Status:      PUBLISHED
Subject:      How to Configure RMAN to Write to Shared Drives on Windows NT/2000
     Doc ID:      Note:145843.1      Type:      BULLETIN
     Last Revision Date:      21-OCT-2005      Status:      PUBLISHED
~ Madrid
http://hrivera99.blogspot.com/

Problem with backups on Tape

Could you help me ,I have a problem with backups on tape drive .The error which Windows throws is "BackupTapeFile::UnloadTape: PrepareTape(UNLOCK) failure on backup device '\\.\tape0'. Operating system error 21(failed to retrieve text for this error. Reason: 15105)."
Does anyone of you have the same problem.Thank you!

You cannot perform a regular restore/recovery (up to the latest possible point in time), because at this time dropped tablespace is not known to the controlfiles/recocery catalog and therefore not known to RMAN,too. You have to 2 possibilities:
1. Restore the entire database and recover back in time to before the tablespace is dropped.
This will cause ALL data within the database to go back in time, not just this tablespace.
2. Clone the target database to a new location, perform point in time recovery in order to export
the data of the tablespace for import into the original database. This causes the data of this
tablespace to be brought back into the production database, not effecting existing (current) data
in any other area of the database.
As you can see recovering from a dropped tablespace needs some additional efforts. By the way you also cannot use RMAN's TSPITR functionality.
Werner

Problem with the Agent

Following a problem I had with saving to a shared location on windows nt using RMAN. (see note 145843.1 in metalink, also see bottom of this text)
When I got to the stage of assigning the service to the domain administrator the agent failed. Can anyone shed any light on the situation on to why it is doing whats its doing.
Thanks to all
Note 145843.1
Doc ID: Note:145843.1 Type: BULLETIN
Last Revision Date: 21-OCT-2005 Status: PUBLISHED
PURPOSE
Following are step-by-step instructions for configuring RMAN to write
to mapped (shared/networked) drive(s) on Windows NT, 2000 or 2003.
SCOPE & APPLICATION
RMAN users who are familiar with basic RMAN functionality
as well as database configuration on the Windows Platform.
WRITING FILES TO A MAPPED DRIVE WITH RMAN
The problem of backing up to a mapped network drive using the SYSTEM account
is a security issue. By default, Oracle requires the SYSTEM user to have
privileges to write to the drives. Microsoft considers granting SYSTEM owned
service access to a shared drive a security issue.
However, there is a workaround that allows Oracle to access a shared drive.
The Oracle services are originally configured to log on using the SYSTEM
account. The SYSTEM account should not be granted access to the shared drive,
therefore the Oracle services for the TARGET DB need to be reconfigured to
logon using an Administrator account (preferably a Domain Administrator).
THE STEPS NEEDED TO RESOLVE THIS ISSUE
1. On the machine where you wish to write the files to, create a shared drive
granting the user 'Administrator' FULL Control.
Note: For reference below, this Administrator will use the password 'test',
this will be referred to as the "Destination" machine.
2. On the machine with the TARGET DB, verify the Administrator user has the
same password of the user that shared the drive on the destination machine.
In the example here, the password would be 'test'.
3. Map a network drive on the TARGET machine to the shared drive on the
destination machine. When mapping this drive, use the Administrator
user with the password 'test'.
4. On the TARGET machine, BOTH the OracleTNSListener Service and the
OracleService<SID> services must be configured to start using the
Administrator/test account.
(As discussed above, Oracle uses the Local System account by default.)
a. Go to the Control Panel and then open up the Services panel.
b. Double click on the appropriate service
(TNSListener or OracleService<SID>).
c. Change the "Log on as" user from the "Local System Account" to
ShowDoc https://metalink.oracle.com/metalink/plsql/f?p=130:14:176254058330...
2 of 3 12/06/2008 08:48
"This Account".
d. Specify the service to log on as the Administrator user.
c. Click on "OK".
5. Shutdown the TARGET database and stop and start the services on the Target
machine. Restart the TARGET database.
6. You should now be able to use RMAN from the Catalog machine to copy the
datafiles. In the RMAN script, specify the drive letter that you mapped
in step 3.
Special Windows 2003 Update :
As Windows 2003 has a changed access behavior compared to Windows 2000,
the solution is a little restrict :
Don't use local drive letters for mapping network shares.
Workaround is to use UNC locations directly, e.g. backup to \\B\share
Since this is in fact an absolute location this is always the same for any
node in the network.
So whether accessed from node A or node B, \\B\share is always the shared
location on B.
FINAL NOTES
It is recommended to use the Domain Administrator account to ensure that
passwords are the same across the various machines. If there is no domain,
use the local Administrator account and ensure that the passwords are the same
for this account across all of the machines.
If your backups are to be automated using the AT command, it is best to start
up the SCHEDULE service under the same Administrator account that the
OracleService<SID> and the OracleTNSListener services use.
In the event that you HAVE to use a user account for the Oracle Services,
rather then using the SYSTEM account, you can create a batch file that
reconnects the shared drives at system startup. The batch file runs
automatically as a service when the server starts and would establish the
connection to the shared drives, regardless of which user logs into the
system. This process of creating the batch file is outlined in the Microsoft's
Knowledgebase article Q243486 - "How to Run a Batch File Before Logging on
to Your Computer." The batch file is not supported by Oracle and is only
mentioned here as an alternative way to reconnect the shared drives.
COMMON MISTAKES
If the OracleService<SID> and OracleTNSListener services are not configured
to use the same account as the shared drive, you can expect the following
errors:
RMAN-10035: exception raised in RPC: ORA-19504: failed to create file
"<file name>"
ORA-27040: skgfrcre: create error, unable to create file
OSD-04002: unable to open file
O/S-Error: (OS 5) Access is denied.
ORA-19600: input file is datafile 1(<path and file name of Datafile 1>)
ORA-19601: output file is datafile-copy 0(<path and file name of file
to be created>)
RMAN-10031: ORA-19624 occurred during call to
DBMS_BACKUP_RESTORE.COPYDATAFILE
If the mapped drive is created on the CATALOG machine and NOT on the TARGET
machine, you can expect the following errors.
RMAN-10035: exception raised in RPC: ORA-19504: failed to create file
"<file name>"
ORA-27040: skgfrcre: create error, unable to create file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
ORA-19600: input file is datafile 1 (<path and file name of Datafile 1>)
ORA-19601: output file is datafile-copy 0 (<path and file name of file to
be created>)
RMAN-10031: ORA-19624 occurred during call to
DBMS_BACKUP_RESTORE.COPYDATAFILE

If there's more information required, Please do not hesitate to send a post. I check this post Daily.

Auxiliary channel allocation in TSPITR with RMAN-managed instance

Hi,
I'm trying do perform TSPITR with RMAN-managed auxiliary instance. All backups are stored on tape. I need to send MML environment values while allocating auxiliary channel to connect to correct NetWorker server and send other NetWorker parameters.
Unfortunately I have issues with sending these params - I can't send them from recover RUN block, as auxiliary instance does not exists at the time when I'm starting to execute script. (example from test env using disk channels)
RMAN> RUN
2> {
3> ALLOCATE CHANNEL c1 DEVICE TYPE disk;
4> ALLOCATE AUXILIARY CHANNEL aux1 DEVICE TYPE disk;
5> SET NEWNAME FOR DATAFILE 1 TO '/u01/backup/tspitr/10gdb2/system01.f';
6> SET NEWNAME FOR DATAFILE 2 TO '/u01/backup/tspitr/10gdb2/undo01.f';
7> SET NEWNAME FOR DATAFILE 7 TO '/u01/backup/tspitr/10gdb2/hr_bak01.f';
8> SET AUXILIARY INSTANCE PARAMETER FILE TO '/home/oracle/params_auxinit.ora';
9> RECOVER TABLESPACE hr_test UNTIL TIME "SYSDATE - 1/4"
10> AUXILIARY DESTINATION '/u01/backup/tspitr/10gdb2';
11> RELEASE CHANNEL c1;
12> RELEASE CHANNEL aux1;
13> }
allocated channel: c1
channel c1: sid=141 devtype=DISK
released channel: c1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of allocate command at 04/07/2010 17:21:53
RMAN-06174: not connected to auxiliary databaseI know I can do it using configure, but is there any way to set this on session level?
10.2.0.4, RHEL
Thanks,
Lukasz

What can be done here, is to CONFIGURE AUXILIARY CHANNEL to set appropriate params for auxiliary instance (without allocating channels manually).
I just wanted to know, if I can do it just for this one session (without permanent modification). What I can do, is:
CONFIGURE AUXILIARY CHANNEL DEVICE TYPE sbt_tape PARMS 'mml settings';
CONFIGURE CHANNEL DEVICE TYPE sbt_tape PARMS 'mml settings';
CONFIGURE DEFAULT DEVICE TYPE TO sbt_tape;
RUN
(new names, auxiliary parameter file)
RECOVER TABLESPACE ...
CONFIGURE AUXILIARY CHANNEL DEVICE TYPE sbt_tape CLEAR;
CONFIGURE CHANNEL DEVICE TYPE sbt_tape CLEAR;
CONFIGURE DEFAULT DEVICE TYPE CLEAR;I just wanted more 'elegant' solution.
Update:
Due to bug no. 4768353 there is no possibility to use automatic channel allocation in auxiliary instance. Problem resolved by using own customized auxiliary instance started before recovery process. Channels have been allocated manually using ALLOCATE AUXILIARY CHANNEL c1 DEVICE TYPE sbt... on already running aux.
Thanks,
Lukasz
Edited by: Łukasz Mastalerz on Apr 19, 2010 6:47 PM

Problem with RMAN.

Similar Messages

Maybe you are looking for