- level 1 for datafile not backed up since 'sysdate-1' then another policy makes:
- level 0 when the datafiles become read only
The recovery windows is set to 1 day.
In the following situation:
RMAN> list backup of datafile 394;
List of Backup Sets =================== BS Key Type LV Size Device Type Elapsed Time Completion Time ------- ---- -- ---------- ----------- ------------ --------------- 12721 Incr 0 13.25M SBT_TAPE 00:01:13 25-MAY-11 BP Key: 12777 Status: AVAILABLE Compressed: NO Tag: ST_TRONLINE_FB20110525 Handle: bk_13201_1_752082473 Media: A00003
[code]....
I expect that the first L0 backup is going to become obsolete, but even if I run crosscheck, it never become obsolete.
While starting up my database i am getting this error.by mistake i had moved log files, and after some time again i inserted those log files again into same directory i am getting this error.
During a duplicate process to a new database name, rman crashed after the restore but before the switch datafile all.So now, we have under ASM the data files under the correct (new) diskgroup but v$datafile contains the previous names (and so diskgroup) and v$datafile_header is empty. RMAN is completly lost, our solution is to manually rename each file under SQL*Plus using ALTER DATABASE RENAME FILE. Unfortunately, we are using or migrating to OMF, so file names are meaningless and we are unable to associate ASM files with database files.
Any way (query or anything else) to associate the ASM files to the database files. Here's an abstract of what we have for one (small) tablespace:
ASMCMD [+ORAXQG1_L136_DG1/ORAXPG1/DATAFILE] > ls -l N47CAW* Type Redund Striped Time Sys Name DATAFILE UNPROT COARSE NOV. 12 10:00:00 Y N47CAW1.276.799152039 DATAFILE UNPROT COARSE NOV. 12 10:00:00 Y N47CAW1.318.799151641 SQL> select file#, name from v$datafile where ts#=17 2 / [code]...
How one should know whether RMAN is using target database control file or using separate catalog database. Also what one should do if he dont have catalog users credentials.
I have a RUN file within a script to duplicate a database. As part of this RUN file I also run the command configure controlfile autobackup off; as part of this RUN file. However, this command has turned off backup of the control file on the AUXILLARY database (i.e. production) as well as the TARGET database (test). Is this supposed to happen?
My run file is:
rman TARGET sys/XXXX@${DB}-SOURCE AUXILIARY / RUN { allocate AUXILIARY channel a1 type disk; allocate AUXILIARY channel a2 type disk; allocate AUXILIARY channel a3 type disk; allocate AUXILIARY channel a4 type disk;
UPDATE event_request SET REQ_EVENT_DATE = TO_CHAR(REQ_EVENT_DATE - INTERVAL '1' HOUR, 'yyyy-mm-dd hh24:mi') WHERE eventID=123
Oracle returns this error:
ERROR at line 4:ORA-01861: literal does not match format string
where line 4 is REQ_EVENT_DATE = TO_CHAR(REQ_EVENT_DATE - INTERVAL '1' HOUR, 'yyyy-mm-dd hh24:mi').The REQ_EVENT_DATE field was originally populated with this stripped down query:
When i open the primary database in my dataguard env,it raise error?
SQL> alter database open; alter database open * ERROR at line 1: ORA-00314: log 1 of thread 1, expected sequence# 77 doesn't match 0 ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/oracl/redo01.log'
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?
I am tryign to run a split onlike full backup from the os useign the sap command which is linked to rman..Command that i am useing is ...
brbackup -u / -c force -t online_split -m full -p initBR1_onlinefull.sap
The backup goes thru but i get this erro on the end...
BR0522I 57 of 57 files/save sets processed by RMAN BR0280I BRBACKUP time stamp: 2011-01-26 12.23.26 BR0505I Full database backup (level 0) using RMAN successful BR0280I BRBACKUP time stamp: 2011-01-26 12.23.28
[code]...
Copyright (c) 1982, 2007, Oracle. All rights reserved.
I want to ask if I restore a control file from backup of say day2 and I recover till day1 using RMAN script, then what will be the state of my database? I mean day2 control file may be having SCN-Day2, and I am instructing RMAN to recover till past point in time that is SCN-Day1.
I am trying to setup incremental backup on my windows OS based server using RMAN command in batch file. When I use batch file in OS scheduler it is working fine, when I am calling same batch file from my LOCAL desktop PC it throws errors as below.
D:> \3.193.211.19sgdba mankp_acressit.bat D:>rman catalog rman/******@acressit target / cmd file=E:sgdba mankp_arch.rcv log E:sgdba mansit_arch_rman_backup.log RMAN-00557: could not open MSGLOG "E:sgdba
[code]....
Both single and double quotes (' or ") are accepted for a quoted-string.
Quotes are not required unless the string contains embedded white-space.
RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-00556: could not open CMDFILE "E:sgdba mankp_arch.rcv"
[code]....
* on my DB server I am login using my administrator account, on my PC I dont have admin account.
* I have checked remote execution using local user as well as admin user.
* I have checked the permission and my local ID & EVERYONE has all permission in that folder.
run { CONFIGURE CONTROLFILE AUTOBACKUP ON; CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/dd_oraback/tkprod/%F'; CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 22 DAYS; sql 'alter system archive log current';
[code]...
So /dd_oraback is a Data Domain mount. Not sure if that makes any difference or not.
I am trying to open the database bur gettinf following errors
ERROR at line 1: ORA-01194: file 1 needs more recovery to be consistent ORA-01110: data file 1: 'C:ORACLEPRODUCT10.2.0ORADATAORCLSYSTEM01.DBF'
SQL> shutdown ORA-01109: database not open Database dismounted. ORACLE instance shut down. SQL> startup mount; ORACLE instance started. Total System Global Area 289406976 bytes
I am trying to move my data files from one location to other as i ran out of space.
SQL> alter database rename file 'C:oracleproduct10.2.0oradataSPF433SPF433ADW_DATA.DBF' to 'D:OracleDatafilesSPF433SPF433ADW_DATA.DBF'; Database Altered
SQL> alter database rename file 'C:oracleproduct10.2.0oradataSPF433SPF433ADW_DATATEMP.DBF' to 'D:OracleDatafilesSPF433SPF433ADW_DATATEMP.DBF' Database Altered
Now when i am trying to run Alter Database open I get ORA-01113: file 5 needs media recovery error
I have an oracle autoback of controlfile and spfile. I am trying to restore the production database using this backup, into a new server with a different directory structure.
I have completed the following steps in the restore process.
1. Creating a pfile from spfile
2. Changing the the location of cdump, udump, bdump and the control files ( there are three )
3. Then creating a spfile from this pfile
I am stuck on the next step where to rename all the datafiles and tempfile and restore the database. Following is what I did.
After mounting the database in RMAN, tried to run the following.
RMAN> run 2> { 3> allocate channel c1 device type disk 4> ; 5> @/home/oracle/rman_scripts/newloc.rman 6> SET NEWNAME FOR DATAFILE 1 TO '/u02/oradata/dorian/system01.dbf'; 7> SET NEWNAME FOR DATAFILE 2 TO '/u02/oradata/dorian/undotbs01.dbf'; 8> SET NEWNAME FOR DATAFILE 3 TO '/u02/oradata/dorian/sysaux01.dbf'; 9> SET NEWNAME FOR DATAFILE 4 TO '/u02/oradata/dorian/users01.dbf';
[code]....
I am getting the following error message.
Starting restore at 25-JAN-2012 21:26:48 released channel: c1 RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of restore command at 01/25/2012 21:26:49 RMAN-06026: some targets not found - aborting restore RMAN-06100: no channel to restore a backup or copy of datafile 30 RMAN-06100: no channel to restore a backup or copy of datafile 29 RMAN-06100: no channel to restore a backup or copy of datafile 28
I am trying to backup my control on a STBBY DB(RAC) and I am getting the ollowing error.
ORA-00245: control file backup failed; target is likely on a local file system
what the issue is? Note the FS is ACFS and can see on all my nodes
show all; using target database control file instead of recovery catalog RMAN configuration parameters for database with db_unique_name PA01INS_IM3L059B are: CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default CONFIGURE BACKUP OPTIMIZATION OFF; # default
[code]...
ACFS file system
df -h /share/dbbkup/oracle/PA01INS/rman Filesystem Size Used Avail Use% Mounted on /dev/asm/pa01ins-33 75G 2.6G 73G 4% /share/dbbkup/oracle/PA01INS rman cmdfile=control.rman
how i can change backup datafile name into its original file name,bcoz at time backup datafile name is different and how i can change that name into its original datafile name so i apply recovery command in user managaed recovery..
SQL> alter database open resetlogs; alter database open resetlogs * ERROR at line 1: ORA-01152: file 1 was not restored from a sufficiently old backup ORA-01110: data file 1: 'F:APPADMINISTRATORORADATATHIRDBSYSTEM01.DBF'
To get rid of this , I tried following,
SQL> recover database using backup controlfile until cancel; ORA-00279: change 1004739 generated at 09/26/2011 10:31:34 needed for thre ORA-00289: suggestion : F:APPADMINISTRATORFLASH_RECOVERY_AREATHIRDBARCHIVELOG2011_09_27O1_M
I take hot backup of database at 10:00 am.After taking the hot backup 50 archived logs are created.Out of 50 i have backed up first 25 of them and at 5:00pm i lose complete database including control,data and the last 25 archived log files that were not backed up.So I am using latest hot backup to recover
I restore the control file backup and datafile backup taken during ho tbackup(10 am) and i issue the command
.......startup mount >>>>>>>Recover database until cancel !!!!!!! Apply the available 25 archive logs
then i give "cancel" since I dont have the next redo log .Now in which mode will the database open(Reset logs or no reset logs)
I want to restore control file from backup set,just as the flowing command,where location does the control file be restored to? how can i specify the location when restore control file?
restore controlfile from '/u01/rman_backup/mybak/df_768589733_7_1.bak';
taking the backup of a control file, as i am taking online backup, archive mode.
At first i have executed the statement
sql> alter database backup control file to trace;
then i have removed the control files and enterd some data in a table and committed it.As my oracle is not shutting down, so i shut aborted it. Now after saving the last file from the udump as obkp.sql i am unable to edit this file and use.
how to edit and use this file, so that i can startup my database normally.
Oracle10g to Sybase12.5 Migration:- How a Oracle dump file can be converted to any text file/xls file which will be loaded in sybase database later through BCP.
means 1.Exporting objects as dump file from Oracle. 2.Is there any tool/process available that can convert this into csv/txt/xls file. 3.This files can be loaded in sybase.
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
