RMAN :: ORA-01516 With Tablespace Point-in-time Recovery
Jul 29, 2012
Oracle 11.2.0.1.0 on CentOS 5.5
i am now facing Tablespace Point-in-time subject. Doing some tests, the following problem appeared:
sql statement: alter database datafile 1 online
sql statement: alter database datafile 3 online
sql statement: alter database datafile 2 online
sql statement: alter database datafile 10 online
[code]....
ORA-01516: nonexistent log file, data file, or temporary file "10"I am using the following command to restore one of my tablespaces:
RMAN> run {
2> recover tablespace tbs_testes_pitr until time "to_date('25/07/2012 19:50:00','dd/mm/yyyy hh24:mi:ss')"
3> auxiliary destination '+DATA';
4> }The error described at the begin of this thread only appears at the end of the operation. I did some research, and the error ORA-01516 indicates that the datafile is not known by the database. When this error appears, i have to do a media recovery on datafile 10, which in fact exists, and is the datafile atached to the tablespace that i am trying to recover
I need to recover a tablespace called "SBSECD01_MDS" (point-in-time).I need to determine and resolve dependencies.
select obj1_owner, obj1_name, obj1_type, ts1_name, ts2_name from sys.ts_pitr_check where (ts1_name = 'SBSECD01_MDS' and ts2_name != 'SBSECD01_MDS') or (ts1_name != 'SBSECD01_MDS' and ts2_name = 'SBSECD01_MDS');
My dev application team iwant to test their application, and once that is done they want to recover to point in time. In my case they would do that after 9.0Am and once that is done they want the state of the database back to 9.0Am
What i am planning to do is:create a restore point at 9.0Am and once application testing is done recover until restore point. ..But i was suggested not to do that way instead my Lead want me to use just recover until timestampI asked what is the difference in doing in my way,the answer i got is by using recover until restore point, the recover process cannot apply incremental level 1 backups and it just restores to a point of incremental level 0, it looked strange to me.
I am trying to restore 11gr2 database to point in time. using following steps:
Control files are fine, that are not restored.
RMAN> run { set until time "to_time('2012-12-13 12:12:00','YYYY-MM-DD HH24:MI:SS')"; } RMAN> restore database; RMAN> recover database; RMAN> alter database open;
Here my problem is it is restore complete data what ever i was having, but i don't was it, i has to restore up to specified time only.
i have the performed level 0 rman backup on 15th feb 2013, and after that i have incremental 1 and archives and controlfile backup. Before this no backup is the database.
Now i want to restore it to 12th feb 2013.so is there any ways to restore the database to that point time.can we restore controlfile to point in time.
I am getting error when i try to restore one tablespace using RMAN.
RMAN> restore tablespace test;
RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-00558: error encountered while parsing input commands RMAN-01009: syntax error: found "test": expecting one of: "double-quoted-string, identifier, single-quoted-string" RMAN-01007: at line 1 column 20 file: standard input
But it's working for other tablespace
RMAN> restore tablespace users;
Starting restore at 10-OCT-12 using channel ORA_DISK_1 channel ORA_DISK_1: starting datafile backup set restore channel ORA_DISK_1: specifying datafile(s) to restore from backup set channel ORA_DISK_1: restoring datafile 00004 to /u01/app/oracle/product/11.2.0/db_1/dbs/TEST/users01.dbf
I have to perform the TSPITR of a tablespace to recover it to a time 03-apr-2011 5 pm.Now I have done that.
Now I find that I need to actually recover it ti 04-apr-2011.Can I again recover the tablespace to 04-Apr after recovering it to 03-Apr by mistake I am not usng recovery catalog;
We would take backup regulary by RMAN(catalog). Last two days we could not take backup. Backup start but after take backup some datafile then rman does not do anything.
i want to clone the test db to dev db but i dont want default users and tablespaces(SYS,SYSAUX,...) in the test db datapump and exp are not working, then contacted ORACLE support and they concluded that test db sysaux was corrupted.i took RMAN all tablespace bkup except default tablespaces. then created new database using DBCA and now i want to restore and recover all those test db tablesapces but while i'm doing restore its saying
RMAN> restore tablespace MAIN_DATA;
Starting restore at 07-SEP-12 using target database control file instead of recovery catalog allocated channel: ORA_DISK_1 channel ORA_DISK_1: SID=129 device type=DISK creating datafile file number=20 name=/opt/oracle/oradata/DEV71/main_data01.dbf restore not done; all files read only, offline, or already restored Finished restore at 07-SEP-12
we are using dataware house of huge amount of data I want to take backup using rman so that I restore oracle instance and specific tablespace only not full database
We are doing RMAN Duplicate set until time to refresh daily our test database for our developers and it taking long time to finish. We noticed on the restore log that RMAN was using a day old old backup pieces to refresh the test database and don't immediately use the latest backup pieces instead.
For additional details here's the rman duplicate command we are using which we run daily(mon-sat) at 4am once daily full backup on production completed.
RMAN Duplicate commands: run { set until time "to_date(to_char(sysdate,'Mon DD YYYY') || ' 04:00:00', 'Mon DD YYYY HH24:MI:SS')"; allocate auxiliary channel ch1 type disk; duplicate target database to testdb; } exit
Is there a way on how to let RMAN use the latest backup pieces instead?
We want to keep the Guaranteed restore point for week but unfortunately we don't have enough flash space in the server. Is it possible to backup the flashback log(restore point logs) through rman and send bkp file to tape? how to restore the database in new server until Guaranteed restore point.
I run DLY cold backups including controlfile & archivelogs and keep 3 gens of backups and archivelogs to 3 days also. What is the correct procedure to restore back to an old cold backup. Database is backed up Mon,Tue,Wed on Thur we require to bring database back to Tuesday DLY security.
I have tried: startup mount restore database from tag 'DLYTUE' recover database
( this just rolls forward on all archive logs once it restores datafiles, not getting to point to alter database open resetlogs.)
Next tried to :
recover database archivelog tag 'DLYTUE' ( same outcome )
What is the correct rman procedure including should I remove old archive logs from working OS directory ? Also need to know once I restore back and open database to TUE security how do you tidy up the archive logs and dumps which are no longer require i.e. : weds..
I have read about using the set until time option but how to I get absolute time from when cold backup completed if this is the correct procedure.
I am using RMAN with a recovery catalog option on a separate Database. My question is
When we use catalog does RMAN keep the information in Control file of the Target Database as well or only in recovery catalog? I am asking this in case We lost the database which contains the recovery catalog what to do?
While connecting to target database from stand database. I am getting below error.
calhost dbs]$ sqlplus system/oracle@proddb
SQL*Plus: Release 10.2.0.1.0 - Production on Sat Jun 22 00:18:10 2013
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production With the Partitioning, OLAP and Data Mining options
SQL> exit Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production With the Partitioning, OLAP and Data Mining options [standdb@localhost dbs]$ rman target system/oracle@proddb auxiliary system/oracle@standdb
Recovery Manager: Release 10.2.0.1.0 - Production on Sat Jun 22 00:18:22 2013
Copyright (c) 1982, 2005, Oracle. All rights reserved.
i have read from documentation but getting some error.
in last
E:Documents and SettingsAdministrator>rman Recovery Manager: Release 11.2.0.2.0 - Production on Sun Sep 30 03:03:09 2012 Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved. RMAN> connect auxiliary sys/12 connected to auxiliary database: XE (not mounted) RMAN> RMAN> DUPLICATE DATABASE TO xe
[code]...
Backup-Based Duplication Without a Target and a Recovery Catalog Connection?
I have a doubt regarding the process the RMAN follows for restore and recovery of the database.
My Level 0 full backup completes on Saturdays at around 11 am after taking 8 hours (It starts at 3am).On Sunday, I ask RMAN to restore (on a different box) till Saturday 11:30 am.Then, after the restore is successful, I recover it till 11:45 am.
The recovery also goes fine and Iam able to clone to test box.
Till what time is the database restored? I assume its till 11 am since the L0 backup finishes at 11 am though I have asked it to restore till 11:30 am
During the recovery, ONLY the archives generated between Saturday 3 am and till the time i asked for recovery (Saturday 11:45 am ) are required. But, checking the recovery log file, i was surprised to see that RMAN has restored archive files starting from Friday 9:30 pm (Much before the time the Level 0 backup even started).
I am making incremental backups via RMAN, the backups are staying at disk. And the infrastructure team will copy this files backups to tape. And they want delete the files that will staying in disk via RMAN. Until now it's ok.
But and if I need of backups that stay on tape, it's possible make a recovery of deleted files by rman.
I was trying to backup my database via RMAN and I had deleted a datafile from the database while it was still in open mode.Since I can't return back to mount stage again,I tried to bring the tablespace pertaining to that datafile offline and then restore backup of the tablespace but it's falshing error during recovery.
When I try to restore entire database,it is not even able to restore.
