I am the only DBA in my company and Oracle just crashed on me. The data is corrupted as well as the data on my backup! Is there ANY way I can get the information back?
My scenario is use RMAN to restore and recover database to a new host.The structure of two hosts are same.
In Host A: 1. Take a full backup. 2. Import a schema which has 191 tables in order to generate archivelogs.
In Host B: I put all the folders(backupset, autobackup, archivelog) to the same directory. But after recovered the database, i checked that schema just has 175 tables, the latest few tables are missing.
I take a backup on PROD and want to use that backup on test to duplicate the PROD db.I ran this first on PROD:
catalog rman11cv/password@metarep connect target / RUN { ALLOCATE CHANNEL disk1 DEVICE TYPE DISK FORMAT 'G: estore\%U'; BACKUP DATABASE PLUS ARCHIVELOG;
I runs fine.map the network drive on my TEST machine. I run the script:
connect target sys/password@pdm; connect auxiliary /; run { allocate auxiliary channel 'ch1' type disk; SET NEWNAME FOR DATAFILE 1 TO 'D:oracleoradatadatabasedataSYSTEM01.DBF'; SET NEWNAME FOR DATAFILE 2 TO 'D:oracleoradatadatabasedataUNDOTBS01.DBF'; SET NEWNAME FOR DATAFILE 3 TO 'D:oracleoradatadatabasedataCWMLITE01.DBF';
[code]....
Its trying to read from the right backupset.But Im not sure it can see it:
channel ch1: reading from backup piece G:RESTOREN3MKSOMQ_1_1 ORA-19870: error reading backup piece G:RESTOREN3MKSOMQ_1_1 ORA-19505: failed to identify file "G:RESTOREN3MKSOMQ_1_1" ORA-27041: unable to open file OSD-04002: unable to open file O/S-Error: (OS 3) The system cannot find the path specified.failover to previous backup
Net view of the PROD host gives this:
D:oracleadminduplicatePDMTEST>net view myprod Shared resources at myprod
Share name Type Used as Comment ------------------------------------------------------ restore Disk G: The command completed successfully.
SQL> alter database mount; Database altered. SQL> alter database open resetlogs; alter database open resetlogs * ERROR at line 1: ORA-01139: RESETLOGS option only valid after an incomplete database recovery
My database is in NOARCHIVELOG mode.I took whole DB backup ( cold).Then just after half an hour I ran following script.
RMAN> RUN { RESTORE DATABASE;RECOVER DATABASE;alter database open;}
Starting restore at 24-FEB-12 using target database control file instead of recovery catalog allocated channel: ORA_DISK_1 channel ORA_DISK_1: SID=133 device type=DISK channel ORA_DISK_1: starting datafile backup set restore
[code]...
Starting recover at 24-FEB-12 using channel ORA_DISK_1
starting media recovery archived log for thread 1 with sequence 2 is already on disk as file /u01/app/oracle/oradata/PROD/redo02.log archived log file name=/u01/app/oracle/oradata/PROD/redo02.log thread=1 sequence=2 media recovery complete, elapsed time: 00:00:01
[code]...
Why do I need to specify an option at the first place?As my redo is intact, it is not incomplete recovery and, I do not want to generate new incarnation of my database.Why oracle simply not opening my database?
I've read a lot about the different types of backup available with Oracle (hot and cold backup). However, I was thinking of a different way of performing this task. I'm currently using Windows Server 2008 R2 and Oracle 11g Standard Edition. I'd like to schedule an entire backup of my server via the utility "Windows Server Backup" (available for free).That way, I could recover my entire server with all the programs and files in case the latter crashes.I'm wondering if this solution could be used as a way of backing up (and recovering) the Oracle database. Should I still set up a regular hot backup with the Archivelog mode enabled in case some operations/transactions were being done at the time of the crash (for the data integrity)?
We have a database server running oracle 12G on linux which is the production then we have a DR using the same version of DB and linux, I want to restore from tape into the DR from the production backup. the UNIX admin has restored already from tape the rman backup, i would like to know what are the steps to restore the backup from tape, also the DR database server was created identical like production using the same spfile etc.
were do i copy restored file into on the DR server? also then in RMAN do i just start the DR database and run the command restore database? what else do i need?
I have taken cold back-up of a complete database using below rcv from a server.
RMAN> connect target / run{ set command id to 'bkp_EMCPROD_db'; allocate channel c1 type 'sbt_tape' parms="BLKSIZE=1048576, ENV=(TDPO_OPTFILE=/opt/tivoli/tsm/client/oracle/bin/tdpo.opt)"; backup current controlfile format 'ct_t%t_T%T_d%d_s%s.ctl'; backup database format 'db_t%t_T%T_d%d_s%s_p%p.db'; backup current controlfile format 'ct_t%t_T%T_d%d_s%s.ctl'; release channel c1; }
I need to restore this back-up on another server of the same Database Name. Below is the rcv which my sr. dba asked me to look into for the restore.
/* From the new server to restore the back-up */ RMAN> connect target "rman/xxxxx@emcprod" connect auxiliary / run { set until time "to_date('Nov 03 2011 19:00:00','Mon DD YYYY HH24:MI:SS')"; allocate auxiliary channel c1 type 'sbt_tape' parms="ENV=(TDPO_OPTFILE=/opt/tivoli/tsm/client/oracle/bin64/tdpo.sacsun8.opt)"; restore database; }
I am restoring Oracle rman backup from nodeA to nodeB through RMAN and I was in the middle of the process of rename the redo log files to new location where I suddenly got the below mentioned error:
RMAN> SQL "alter database rename file 'E:oracleproduct10.2.0oradatadbadeepakREDO01.LOG' to 'E: est_rman estrmanREDO01.LOG'"; sql statement: alter database rename file 'E:oracleproduct10.2.0oradatadbadeepakREDO01.LOG' to 'E: est_rman estrmanREDO01.LOG' RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03009: failure of sql command on default channel at 01/31/2011 12:53:04
I have a database ORADB1 running on UNIX server and I took a hot backup using a script and restored it on the same server as ORADB2 and opened the database to verify it comes up and then shut it down.
Now I have a requirement that I need to use the same datafile copy (ORADB2) and bring it up in another server as ORADB1 .
We are trying to restore a database on the different server using RAM incremental level 0 and 1 backups. We have weekly Incremental level 0 backups along with incremental backups on daily basis. During recovery of Incremental level 0 backup, RMAN is expecting/looking for Incremental Level 0 backup of prior week as well. Is this the usual process for RMAN to look for prior level 0 backup though we need to restore from the current level 0 backup and roll forward by a week with subsequent Level 1 backup.?
We intend to restore from the Level 0 of 1/16 and roll forward with daily incrementals till 1/22. RMAN is expecting level 0 backupsets from 1/9 backup as well and keep failing since those backups are not available. quick inputs since we are in middle of recovery and trying to resolve if this is even doable.
I have problem on using "delete obsolete" in RMAN.
First, let describe my backup configuration.
1. Full backup every Monday (17-Oct, 10-Oct, 3-Oct, 26-Sep) 2. Incremental backup for other days 3. Enable autobackup of control file 4. Backup archive log every day 5. RETENTION POLICY TO RECOVERY WINDOW OF 30 DAYS 6. Execute "Delete obsolete" every day 7. control file is used instead of catalog
The results observed: 1. Backup of control files older than 30 days will be deleted 2. Backup of archive log files older than 30 days will be deleted. 3. Backup of datafiles older than ~14 days but before 30 days are also DELETED.
In my example, the backup of datafiles created at 26-Sep is deleted at 16-Oct.
I tried "restore database validate until time "sysdate-22"" at 17-Oct. And RMAN reported "datafile xx will be created automatically during restore operation". It seems that RMAN failed to do restoration up to 22 days ago. The retention policy I set seems not effective on datafile backups.
I checked view v$backup_set and the "Keep" is "No" and "Keep until" is empty.
The only thing I can think of, is the settings of "CONTROL_FILE_RECORD_KEEP_TIME". It is marked "7" in the Oracle, which is less than the retention. But I suppose this only causes the backup not deleted, but NOT be deleted earlier.
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 just switched my STBDY DB to a PRIMARY DB and I am ran the following:
RMAN> CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;
using target database control file instead of recovery catalog old RMAN configuration parameters: CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY; new RMAN configuration parameters: CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; new RMAN configuration parameters are successfully stored ORA-00245: control file backup operation failed
RMAN-08132: WARNING: cannot update recovery area reclaimable file list
RMAN> show all;
RMAN configuration parameters for database with db_unique_name ORARZULB are: CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 30 DAYS; CONFIGURE BACKUP OPTIMIZATION OFF; # default CONFIGURE DEFAULT DEVICE TYPE TO DISK; CONFIGURE CONTROLFILE AUTOBACKUP ON; [code]....
what causes this warning and how to get rid of it?
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).
while opening my database i got this error i already increase my db_recovery_file_dest_size but still i got this error
E:oracleproduct10.2.0db_1BIN>SET ORACLE_SID=LIVEDB E:oracleproduct10.2.0db_1BIN>SQLPLUS SQL*Plus: Release 10.2.0.4.0 - Production on Thu Mar 22 11:14:47 2012 Copyright (c) 1982, 2007, Oracle. All Rights Reserved. Enter user-name: SYS AS SYSDBA Enter password: Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing options
