I am trying to remove archive log file on my standby site but I am getting the following message. There are lots of archive logs are present on the storage but rman is unable to displaying that.
RMAN> list archivelog all;
specification does not match any archived log in the repositoryRMAN>
ora-00257 archiver error. connect internal only until freed
when we tried to remove the unwanted arc files thro ASMCMD,we are getting below error:
ASMCMD> rm -ef 2011_04_05/ Unknown option: e usage: rm [-rf] <name1 name2 . . .> ASMCMD> rm -rf 2011_04_05/ ORA-15032: not all alterations performed ORA-15028: ASM file '+XCOM_BACKUP_DG/TXCOM/ARCHIVELOG/2011_04_05/thread_2_seq_27215.1143.747641143' not dropped; currently being accessed (DBD ERROR: OCIStmtExecute) ORA-15032: not all alterations performed ORA-15028: ASM file '+XCOM_BACKUP_DG/TXCOM/ARCHIVELOG/2011_04_05/thread_3_seq_21762.826.747641143' not dropped; currently being accessed (DBD ERROR: OCIStmtExecute) ORA-15032: not all alterations performed ORA-15177: cannot operate on system aliases (DBD ERROR: OCIStmtExecute)
We have a nightly rman backup that was complete and clean.The backup contains a Data File, Control File and a backup Archive Log file.The database server crashed with all the subsequent archive logs lost.
We are trying to recover from the three backup files.We are bumping into the backup piece missing as all the archive logs are done. how to restore with the exising backup files. the lost archive logs are probably salvageable.
If I want to take Rman archive log backup with delete input command , how the archive logs will be copied to standby database
For eg
I am taking archive backup as
RMAN>backup archivelog all delete input;
here consider few archives are not copied to standby database (due to nw issue) then how standby will receives these missing archives as those are deleted by rman backup at primary side.
I am not getting any document related to above query.
I had a production db with archive logging enabled
SQL> select name,status 2 from v$archived_log;
NAME STATUS ---------------------------------------- - D:ORACLEARCHIVE_ORCL11_13.DBF A D:ORACLEARCHIVE_ORCL11_14.DBF A D:ORACLEARCHIVE_ORCL11_15.DBF A
[code]...
So i need to restore archivelogs by using sequence
RMAN>RESTORE ARCHIVELOG FROM SEQUENCE 20 UNTIL SEQUENCE 28; So the restore is completed successfully So its very hard to monitor archivelog files i feel i should have included all archivelog files while taking RMAN backup
RMAN >backup database plus archivelog all delete input;
but the problem is my RMAN backup is already 360GB in size and it takes 4-5 hrs to complete .so i need to schedule RMAN backup at one time (e.g sunday) ,delete the archivelog files older than sundayand now schedule the archivelog backup at another day (e.g wed &sat)
my question is where i have to change my script to backup all avaialbe archivelog files if old archivelog files are deleted at os level?
RMAN> run { 2> allocate channel c1 type disk; 3> sql 'alter system archive log current'; 4> backup archivelog all format 'D:oracleackuplog_t%t_s%s_p%p' delete input; 5> release channel c1; 6> }
I am running the following command to backup my archive logs and want to keep at least two hours of .arc files on disk.
rman < connect target login/password connect catalog login/password show all; sql "alter system archive log current"; backup filesperset 5 archivelog until time 'sysdate-2/24' format $FILE_DEST_ARCH delete input ; resync catalog; EOT
On some occassions, there will not be any archive logs that meet this criteria and I get the following error:
RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of backup command at 12/01/2010 12:50:58 RMAN-06004: ORACLE error from recovery catalog database: RMAN-20242: specificati on does not match any archive log in the recovery catalog
Is there anything I can do to the rman command above that will prevent this error from happening but yet keeping same functionality?
I am not able to delete one month old archive log file on production database. it already applied on standby database. While deleting the files, it throwing errors as "Another program is using it".
I am using Oracle RAC 11gR2.I am planing to move my old trace files to an archive location.
I have the below questions concerning the users and groups used by Oracle RAC when moving the trace files.It is related to the permissions but it is about oracle behavior.
The trace files of database (oracle user) are created as below:
284 -rw-r----- 1 oracle asmadmin 283571 Aug 20 18:08 PPRD1_mmon_13893716.trc 4 -rw-r----- 1 oracle asmadmin 125 Aug 20 18:10 PPRD1_gcr0_11730998.trm 4 -rw-r----- 1 oracle asmadmin 2833 Aug 20 18:10 PPRD1_gcr0_11730998.trc 580 -rw-r----- 1 oracle asmadmin 588489 Aug 20 18:12 PPRD1_lmhb_15859792.trm
[code]....
when moving the files using the oracle user it will be created as oracle:oinstall and not oracle:asmadmin since asmadmin is not a group of the oracle user.
1. How oracle created my trace and log files with permission oracle:asmadmin?
2. How should I move these files? I moved it using the Oracle user and it was created as oracle:oinstall with Operating system error "unable to duplicate owner and mode after move"
We are planning to setup a data guard (Maximum performance configuration ) between two Oracle 9i databases on two different servers.
The archive logs on the primary servers are deleted via a RMAN job bases on a policy , just wondering how I should delete the archive logs that are shipped to the standby.
Is putting a cron job on the standby to delete archive logs that are say 2 days old the proper approach or is there a built in data guard option that would some how allow archive logs that are no longer needed or are two days old deleted automatically.
I'm facing problem with archive log file size, Archive logs are generated with only of 90m or 92m or 94m(Variable sizes of less than 100m), Although i had set 100m for each of my redo log file. Here i'm providing my create db script for your reference. I want to know why the log switches before it reaches 100m.Is there any connection of intial 10m for my .dbf files.
We have data archive scripts, these scripts move data for a date range to a different table. so the script has two parts first copy data from original table to archive table; and second delete copied rows from the original table. The first part is executing very fast but the deletion is taking too long i.e. around 2-3 hours. The customer analysed the delete query and are saying the script is not using index and is going into full table scan. but the predicate itself is the primary key,More info below
Plan hash value: 2798378986 ------------------------------------------------------------------------------------- | Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time | -------------------------------------------------------------------------------------| 0 | DELETE STATEMENT | | 2520 | 233K| 87 (2)| 00:00:02 || 1 | DELETE | MON_TXNS | | | | ||* 2 | HASH JOIN RIGHT SEMI | | 2520 | 233K| 87 (2)| 00:00:02 || 3 | INDEX FAST FULL SCAN| OTW_ID_TXN | 2520 | 15120 | 3 (0)| 00:00:01 || 4 | TABLE ACCESS FULL | MON_TXNS | 14260 | 1239K| 83 (0)| 00:00:02 |
------------------------------------------------------------------------------------- PLAN_TABLE_OUTPUT -------------------------------------------------------------------------------------------------------------------------------------------- Predicate Information (identified by operation id): ---------------------------------------------------
I can delete the old archives with extension arc. Today, when I consult V$RECOVERY_FILE_DEST, there are files with today date. Can I delete these files, without danger the database?
How after a re-catalog of an archivelog, RMAN knows that the archivelog will be needed and in the right order?
If the re-catalog and subsequent crosscheck has changed the path of the archivelog will RMAN ignore the path and just recognize the archivelog name and format?
We are having an intermittent problem related to failing RMAN archive log backups. Normally everything works fine but once every fortnight or so the archive log backup starts to fail with the below message. We run two Oracle instances on this windows box, so they are using same oracle and TSM client binaries, but it is only of the instances that have this problem - the largest instance though. Restarting the Oracle instance solves the problem and everything is back to normal, until next time ...
This is the error message in the rman log file CODERMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03009: failure of allocate command on c1 channel at 03/27/2013 11:00:29 ORA-03113: end-of-file on communication channel
Trace file CODE Trace file R:\ORA_DATA\SDC002\diag\rdbms\sdc002\sdc002\trace\sdc002_ora_12328.trc Oracle Database 11g Release 11.2.0.3.0 - 64bit Production Windows NT Version V6.1 Service Pack 1 CPU : 40 - type 8664, 20 Physical Cores Process Affinity : 0x0x0000000000000000 Memory (Avail/Total): Ph:85656M/147445M, Ph+PgF:96175M/157683M Instance name: sdc002 Redo thread mounted by this instance: 1 Oracle process number: 57 Windows thread id: 12328, image: ORACLE.EXE (SHAD)
I have the incident file as well if that is of any use.
Could the problem be related to running two backups in parallel?
We run full backups once a week and both this time and last time the archive log backup failed it was in conjunction to when the full backup also was running.
Is there any other solution to the problem than restarting the oracle instance?
Since this is a busy production instance it is a big problem for us to restart it outside of maintenance windows.
Starting backup at 06-MAY-13 channel ch00: starting compressed incremental level 0 datafile backup set channel ch00: specifying datafile(s) in backup set RMAN-03009: failure of backup command on ch00 channel at 05/06/2013 07:09:16
[Code]....
RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03009: failure of backup command on ch00 channel at 05/06/2013 07:09:16 ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
I was having troubles with deleting some files and folders in windows 7, I used a software called SPAM. It works fine. Do I have any other options to do that thing? Or is it ok to be with SPAM? This tool has more options too.
Anyway, I've loaded 5 .csv files through an external table and after doing it I tried to delete them.
But this error comes "Cannot delete 'filename': It is being used by another person or program".
I closed Oracle Developer and tried again deleting them manually, and the result was the same.
Tried restarting and deleting one .csv and it worked, but when I open sql dev and tried deleting the other files couldn't do it.
The question is: files that were used on external tables can't be deleted if developer is working?
The thing is that I've created a Stored Procedure that delete the files and obviously can't work. So, I should delete every time I load a csv file after restarting the computer.
We are going to implement oracle 11g. Now I wanna use rman to take the incremental backup in the follwing way:
Level-0 backup weekly, in the way:
run { allocate channel c1 type disk; allocate channel c2 type disk; BACKUP incremental level 0 DATABASE TAG 'Weekly_full' FORMAT 'E:RMAN_backupweekly_full_%d_%Y%M%D_s%s_p%p.bak'; backup archivelog all not backed up 1 times delete input TAG 'Weekly_full_arc' FORMAT 'E:RMAN_backupweekly_full_arc_%d_%Y%M%D_s%s_p%p.bak';
[code].....
and RETENTION POLICY TO RECOVERY WINDOW is set to 10 days, so that there is no chance that i will delete expired backup before taking backup.
Now my question is,
1) Is the way is correct that there is no wrong configuration. My main concern is about archive log, is it correct?
2) As i am deleting archive log files with the backup and after that the expired archive log backup is also deleted, so is there any chance of failure in recovery.
3) here how archive log backup will work with 10 days retention policy.
I have got oracle 11g release 1, I need recomendation, how can I delete safely content from the folder C:oraclediag dbmsinstancenameinstancenameincident?
I trying to backup archive logs using rman in standby database. I'm able to backup archive logs using simple command it get's successfully completed. rman > BACKUP ARCHIVELOG ALL When i'm trying to do with keep command it's getting failed.I'm trying to do on physical standby databaseBACKUP ARCHIVELOG ALL KEEP UNTIL TIME 'SYSDATE+100' TAG = 'TEST'.
I have Oracle 10gR2 database on a windows server, I have scheduled rman backup for this database from Solaris server
set echo onrun { crosscheck archivelog all; backup check logical database plus archivelog; delete noprompt obsolete device type DISK; } exit;
It is deleting the obsolete backup pieces but it is not deleting old archive logs (obsolete archive logs) and it is not even showing old archives as obsolete when I check thru report obsolete
if I run below rman command lines in 10g and 11g RMAN, it works well, but NOT in RMAN (Release 8.1.7.4.0), so which commandlines I should use to get to the same pursposes in RMAN 8.1.7.4?
run { ALLOCATE CHANNEL c1 TYPE 'sbt_tape'; ALLOCATE CHANNEL c2 TYPE 'sbt_tape'; ALLOCATE CHANNEL c3 TYPE 'sbt_tape';
I use the following script to duplicate a target to an auxiliary instance. This works fine once.
However if I run it a second time it will create a new set of datafiles leaving the original files in place taking up space.
Is there something that I can put in the script that will stop this happening.
I know I could probably put a "set newname for datafile" clause for each datafile in the target database, but this makes the script over complicated and I would like to keep it as generic as possible.
DUPLICATE TARGET DATABASE TO dupdb until time "TO_DATE('07/06/2011 07:25','DD/MM/YYYY HH24:MI')" LOGFILE GROUP 1 ('+DATA') SIZE 50M, GROUP 2 ('+DATA') SIZE 50M, GROUP 3 ('+DATA') SIZE 50M, GROUP 4 ('+DATA') SIZE 50M;