I have been trying to do a once off backup of an oracle database. I have followed instructions to do standard backups and when actually running the RMAN backup I got a ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode.
No problem: I read that you need to execute the following commands in RMAN to ensure a clean shutdown/startup of the database to get past this problem: run {shutdown immediate;startup mount, etc } ...problem is - this code shuts down the database and then I cannot restart it using startup mount as it starts with this TNS listener errors. So I have restart through services but then I get the NOARCHIVELOG error cropping up again.
I'm getting quite frustrated with this. I don't need an archive/redo log - I just need the current state (snapshot) of the database with all the datafiles / procedures/functions in it...a once off - but I can't seem to get this working.
am trying to run rman backup plus archivelog TO tape disk my rman configuration settings are as seen below
RMAN configuration parameters are: CONFIGURE RETENTION POLICY TO REDUNDANCY 2; CONFIGURE BACKUP OPTIMIZATION ON; CONFIGURE DEFAULT DEVICE TYPE TO DISK; CONFIGURE CONTROLFILE AUTOBACKUP ON; [code].....
get the following error when i do this, RMAN-03009: failure of backup command on C3 channel at 01/03/2013 11:33:45 ORA-00600: internal error code, arguments: [ksfdfetch1], [], [], [], [], [], [],
i have changed the log_archive_dest_1 to another drive (suppose D ) than Oracle installed disk
created tables in scott , alter system switch logfile;
so archive log was der in the new destination i delete that archivelog from D and pasted to drive E ( cut paste ) start rman , crosschecked archivelogs Now , i want to tell Rman that recover that archivelog from E and then recover
We have EM (Cloud 12c) initiated scheduled backup jobs that perform (all below are online backups, obviously archivelog mode)
- level 0 Incremental 3AM on Sunday - with options backup all archive logs, delete input, delete obsolete
- level 1 Incremental (non cumulative) 3AM every other day - same options
Recovery window is set to 3 days, other options below:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 3 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 BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 2;
[code]....
Everything appears to be working normally (archive logs are being backed up and once they are the archive logs themselves are being deleted from the FRA), but I'm having some trouble understanding the behavior of the delete obsolete.
With a recovery window of 3 days, on Monday at 11AM my expectation would be that I would find in backups the following:
- level 0s from day before (Sunday) and the previous Sunday (8 days prior)
- all level 1s from previous Sunday on (so Mon-Sat and this morning)
- archivelog backups from Friday until this morning
What I'm not understanding is that I'm seeing archivelog backups from last Monday, Tuesday, etc. - i would have thought these would have gone obsolete based on my recovery window, yet when I run report obsolete in RMAN nothing is showing up.
I have a standby database in which I am backing up my database from. I also backup my archivelogs on my primary site as well as the control file. My issue is that I cannot find the correct RMAN command that will allow me to delete the actual backupsets from disk after say 7 days.
I know how to delete automatically the actual archivelog files, but not how to only have 7 days of archivelog backupsets available at any one given time.
Oracle 10gR2 on 64-bit RHEL.Backup Strategy:There will be a level-0 backup of the database every Sunday and level-1 every weekday.Archivelogs will be backed up up every 30 minutes.
Q: How can I delete ALL the archivelog backups that were taken that day (every 30 minutes) right after successful completion of level-0 or level-1 backup?
I want to delete them because they may not be of any use after the level-0 or level-1 backup (am I right)?
We have two Windows 2008 VMs with Oracle 11G configured as primary and standby.This configuration has been defined by a partner who is no longer working for us.We have broken the correct application of the redo log on the standby when we have not correctly restored some snapshots on those two VMs.I would like to create a new Oracle server that will become the new standby. For that, I need too :
- Display the full dataguard configuration to reproduce it on the new server - Stop (delete ?) the configuration on the primary server.
We also have the current problem that RMAN refuses to delete old archivelog since they have not been applied to the standby.
RMAN-03009: failure of backup command on t1 channel at 12/15/2012 06:15:11 RMAN-10015: error compiling PL/SQL program RMAN-10033: error during compilation of job step 2: ORA-00603: ORACLE server session terminated by fatal error ORA-04030: out of process memory when trying to allocate 400 bytes (PL/SQL DIANA,LISIMA: Add cells)
We received the above error message after the following event:
rman failed to backup because archivelog destination was out of space
We moved SOME of the archivelog file manually using operating system command mv to another location so that our application can run first.When the engineers restarted the rman to backup, we receive the above error.
I'm on a Windows server 2003 R2 64 bit, database is 11.1.0.7. From RMAN connected to the target and the catalog, this is a show all;
RMAN> show all;
RMAN configuration parameters for database with db_unique_name ORCL are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 3 DAYS; CONFIGURE BACKUP OPTIMIZATION OFF; CONFIGURE DEFAULT DEVICE TYPE TO DISK; CONFIGURE CONTROLFILE AUTOBACKUP ON; CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'F:oracleadmin
[code]....
I'm running incremental backups, a level 0 on sunday and a level 1 the other days of the week, this is the ctl file:
LEVEL 0: connect target /@ORCL connect catalog rman/rmanpw@rmancat RUN {
[code]....
The level 0 does delete the archive logs (because of the delete input). Each backupset has two copies of the archive logs (which is what I want), and I expected the logs to be deleted after being backed up 2 days (each day is twice, 2 days = 4 times). But it's not deleting the logs, even after 6 runs.
Microsoft Windows [Version 5.2.3790] � Copyright 1985-2003 Microsoft Corp. C:\>set ORACLE_SID=PRODDB C:\>set ORACLE_HOME=C:\oracle\product\10.2.0 C:\>rman target / Message file RMAN<lang>.msb not found Verify that ORACLE_HOME is set properly C:\>sqlplus / as sysdba Error 6 initializing SQL*Plus Message file sp1<lang>.msb not found SP2-0750: You may need to set ORACLE_HOME to your Oracle software directory
Performing backups on the physical standby via RMAN. We need to restore our test database, and right now it is equivalent to the production. The DUPLICATE command seemed the best bet. We have controlfile and SPFile both on Auto-backup, and the RMAN on a six day retention with weekly 0 level backups and nightly level 1 cumulative backups.
However, when I run the DUPLICATE it chokes being unable to find a current controlfile nor one in backup, even though we have six days worth of supposedly good (validated) backups. We are not using a catalog, rather the DB controlfile.
The solution to this error is reopen the database and try again. however, the physical standby cannot be opened. It is the standby. What if we move the last backup to the primary database, "register" it there, and try this DUPLICATE?
I have seen nothing on this in my searches, and the Oracle documentation does not address this, though it recommends backup from the Physical Standby.
I have troubles when restore FULL BACKUP from server A to Server B . when i Backup Full from server A ,i copy that Backup files to Server B (aa new server),i restore spfile và control file from BK files,then i mount (alter database mount ) to restore database , it show error message ORA-01103:
database name 'ORCL' in control file is not 'DUMMY' ,
I tried to shutdown immediate and then startup mount again , but it show other error message
RMAN-04014: startup failed: ORA-00845: MEMORY_TARGET not supported on this system.
I read the error description. In my case there is only one full backup at a time running, hence it does not make any sense.
RMAN> connected to target database: OTATEST (DBID=3130218754) RMAN-06900: WARNING: unable to generate V$RMAN_STATUS or V$RMAN_OUTPUT row RMAN-06901: WARNING: disabling update of the V$RMAN_STATUS and V$RMAN_OUTPUT row s ORACLE error from target database: ORA-19921: maximum number of 128 rows exceeded
i am trying to restore database using rman backup on same machine using command
RMAN> run { 2> set until sequence 23; 3> restore database; 4> recover database; 5> } but it will give me error. RMAN-00571: ======================================================= RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =========== RMAN-00571: ======================================================= RMAN-03002: failure of restore command at 03/31/2011 19:18:11 [code]....
One of database, while taking backup using RMAN, it failed with the following error:
RMAN-03009: failure of backup command on DISK4 channel at 11/28/2012 09:47:29 ORA-19566: exceeded limit of 0 corrupt blocks for file <faile_name>
I used DBV to identify the number of blocks corrupted.
I referred the Metalink iD 457422.1 & 336133.1. But it did not work since the corrupted blocks have got object in it.
I could able to find the object as well. it is one of the table in the datafile.
I used 'ALTER TABLE ... MOVE..' command to see if that works. But again getting the same error while taking the backup and corrupted blocks still exists.
I turned on ARCHIVELOG in my main database, anticipating GoldenGate replications and standing up a physical standby database. However, during the process I forgot to create a new SPFILE for my database, meaning that the next time the database cycled, the archive log destination would revert to the Oracle default (rather than the mount point I had set up to receive them) $ORACLE_BASE/fast_recovery_area
. I discovered this because my database hung..... In looking at the ALERT LOG, I discovered that the logs were going to fast_recovery_area, and it had run out of room. OK, so I did an alter system set db_recovery_file_dest_size= 5G scope=both; at which point in time I was notified that no active SPFILE existed! I moved out all of the logfiles that were in the fast_recovery_area, but the database seemed to still think that it was full.
I've managed to get everything fixed and put back together, but my remaining question is: After I freed up all sorts of space in the fast_recovery_area, why did/does the database still think that area is full?
11gr2, HP-UX, 64-bit. From last one week, we are seeing tremendous increase in archive-log growth. Its comes almost around 110GB per a day (db size=600g). I don't think its usual.Alertlog is clean and we don't see any alerts. Remedy app is built on this db and its creating tables on fly with LOB columns and indexes on them. As a first step. shall I disable logging for indexes on LOB columns ?
i have one question regarding archivelog and backup if i take just backup excluding archivelogs like = RMAN>backup database; (not plus archivelog ) now when even i recover database using backup , will it also recover changes that was in archives?
2) Created a Source Directory --> DR1 3) Created a Target Directory --> DR2 4) Created a DB Link CREATE DATABASE LINK LINK1 CONNECT TO <username of the Remote DB> IDENTIFIED BY <Password> USING '<Remote DB Name taken in the TNSFILE>. 5) In the Local Server I had written the below command.
create or replace procedure proc1 is cursor c1 is select recid,substr(name,37) "ARCH_FILE" from v$archived_log; var1 c1%rowtype; begin open c1; fetch c1 into var1; [code]...
It is working, but not coping the Files from Local To the Remote.
the data guard configuration is left as it is, i.e.
cta: physical standby ctastd: primary
I discover the following findings in the alertcta.log, i.e. in cta database,
Primary database is in MAXIMUM PERFORMANCE mode RFS[8]: Successfully opened standby log 4: 'D:ORA102CTAREDO04.LOG' Thu Sep 01 10:38:08 2011 Errors in file d:ora102ctaudumpcta_rfs_536.trc: ORA-16401: archivelog rejected by RFS
Quote:
ORA-16401: archivelog rejected by RFS
Cause: An attempt was made to re-archive an existing archivelog. This usually happens because either a multiple primary database or standby database(s) or both are trying to archive to this standby database.
Action: See alert log and trace file for more details. No action is necessary; this is an informational statement provided to record the event for diagnostic purposes.
it seems to be that there are multiple primary database, but it is not based on the information from v$database.Right now the physical standby database cannot received any archive logs from the primary.I've checked the database_role in both servers, they are as they are designated.
from the physical standby database
SYS@cta>select db_unique_name, database_role, switchover_status from v$database; DB_UNIQUE_NAME DATABASE_ROLE SWITCHOVER_STATUS ------------------------------ ---------------- -------------------- CTA PHYSICAL STANDBY NOT ALLOWED SYS@cta>alter database recover managed standby database disconnect from session
[code]....
the standby is always busy, i.e. SESSIONS ACTIVE. i.e make sure the archived logs are shipped and apply over to physical standby.
archive logs to be stored in its own "date formatted" separate folders.I have already configured flashrecovery area and I dont want to change it as backups are stored there.How can I achieve this without changing the flash recovery area location ? db_recovery_file_dest is set to G:log archive dest is set to F
So I try to back it up first by using the below command:
RMAN> backup archivelog all;
Starting backup at 04-JUN-13 using channel ORA_DISK_1 channel ORA_DISK_1: starting archive log backupset channel ORA_DISK_1: specifying archive log(s) in backup set [code]......
I know that I have to extend the db_recovery_file_dest directory for "limit exceed" error but how can I safely delete the archivelog in order to bring up the database?
I have migrated my database to oracle and while migration i have followed all instructions and migrated to oracle.the connection and user having my tables and all object is
con name: orcltestcon user: orcltestuser and password: orcltestuser.
I want to turn on ARCHIVELOG Mode ON.
1) Is it good practice to turn on archivelog. also tel me cases where it is good. 2) to turn on ARCHIVELOG , with which command i should connect.
1) CONNECT SYS/<password> AS SYSDBA; or 2) CONNECT orcltestuser/orcletestuser AS SYSDBA.
I'm new on 11g, due to my limit storage with mounted internal disk, so I think, may I can store archivelog in ASM without FRA? However, I did not find any document to verify.