RMAN :: How To Do Archivelog Dump
Sep 13, 2012how can I do an archivelog dump?
View 3 Replieshow can I do an archivelog dump?
View 3 RepliesI 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.
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
10.2.0
win 7
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.
May I know what is the command for rman to backup and delete single archive log?
View 15 Replies View RelatedOracle 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-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
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.
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 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 ?
View 4 Replies View Relatedi 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?
View 7 Replies View RelatedI wanted to copy some archive log files between 2 DB Server.Steps:
1) Edited the Local and Remote DB's TNSNAMES file and modifyied like below.
bookstore =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 10.80.100.28)(PORT = 1521))
)
(CONNECT_DATA =
(SID = BOOKSTORE)
)
)
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.
initial configuration:
cta: physical standby
ctastd: primary
I cancel my failover at cta half way, from [URL]
Quote:
Step 4 Initiate a failover on the target physical standby database.
Issue the following statement to initiate the failover:
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE FINISH FORCE;
during the above process it took too long so I opened up another session and cancel the above process
SQL>alter database recover managed standby database cancel;
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.
I'm using Oracle 10.2.0.4 and os is windows.
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
View 8 Replies View RelatedJust now my database is hang due to the archivelog full. I try to use RMAN to delete the expired one and free space but encounter the error:
RMAN>crosscheck archivelog all;
archive log filename=/geodata/oraclelog/archive_log/ORAGF45/archivelog/2013_06_04/o1_mf_1_1444_8tsxvwc2_.arc recid=1350 stamp=817182450
validation succeeded for archived log
archive log filename=/geodata/oraclelog/archive_log/ORAGF45/archivelog/2013_06_04/o1_mf_1_1445_8ttx2q6j_.arc recid=1351 stamp=817214416
[code].......
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.
View 5 Replies View RelatedI created a standby database yesterday and everything is working correctly. I need to make some tweaks, however, and one of those is the directory that the standby database expects the archivelogs to be.
I found that the archivelogs were being shipped to $ORACLE_HOME/dbs and named arch*.arc. Interestingly a log switch ships the archivelog minus the "arch" at the front and all archivelogs now do not have that format. I moved the archivelogs to the correct location and renamed them. I have been able to set the correct location using standby_archive_dest and can see that the archivelogs are shipped to there.
Also, v$archived_log shows the correct path and filename. The problem I have is that when I come to apply the archivelogs it still seems to think that they should be in $ORACLE_HOME/dbs and named with "arch" at the front. what parameter I need to change to tell oracle the correct path and filename to use when applying the archivelogs?
We have oracle 10gR2 RAC with ASM running on HP-UX. The archivelogs are located in a NFS filesystem and we want to move this into ASM.
View 1 Replies View RelatedHow to make the automatic deletion of all the archivelogs when it is applied successfully on the standby database? We have 1 primary database and 1 standby database using oracle physical dataguard.
In the primary database, we have daily backup job so that the applied archivelogs are deleted automatically, no problem
But in the standby database ( physical standby) I have to go there and delete manually because I don't issue backup on this database. Is there any solution for this problem.
I have a DR setup with the following configuration
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 30 DAYS;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY
I dont want to backup the STDBY DB but I want the ARC files to be removed when applied so my flash area does not fill up. Is there some command(rman or not) that can fire off this policy?
I am creating physical standby database through Rman duplicate command from 2 node rac cluster. rman do all its work. now am try to start the mrp process on physical standby database. I am getting following errors
------------------------------------------------------------
Check that the primary and standby are using a password file
and remote_login_passwordfile is set to SHARED or EXCLUSIVE,
and that the SYS password is same in the password files.
returning error ORA-16191
------------------------------------------------------------
ORA-16191: Primary log shipping client not logged on standby
------------------------------------------------------------
I copied the same pass file from primary to standby and many times verify the same but i got the same error.
My oracle backup via Netbackup failing with error 6 (Netbackup) and i have checked the logs please find the RMAN log file as well.
Script /opt/rman_script/st72_oracle_full.sh
==== started on Tue May 28 15:27:46 SGT 2013 ====
RMAN: /OraBase/V10203/bin/rman
ORACLE_SID: ST72
ORACLE_USER: oracle
ORACLE_HOME: /OraBase/V10203
NB_ORA_FULL: 1
NB_ORA_INCR: 0
[code]....
Database Version - 10.2.0.4.0
OS - Red Hat Linux
We have configured oracle one way stream between two databases. Source database is capturing the changes (No downstream configured). Configuration was working fine but destination database was lagging behind very much i.e about 15 days behind the source database. We are ok with this but the problem is now that , as per client request we have restored previous backup and open the database with resetlog option in source database. After resetlog , archivelog sequence has been changed and stream is not working.
Can I apply the previous archivelog (before resetlog archivelogs ) in destination database anyway.Source database is a production database.
I need to make my database to ARCHIVELOG mode when i try it it gives below following error
SQL> alter database archivelog;
alter database archivelog
*
ERROR at line 1:
ORA-00265: instance recovery required, cannot set ARCHIVELOG mode
Given facts:
rman is used to backup database A to disk
rman is used to put those disk backups to tape
rman is used to duplicate database A to database B on another host
the duplicate process worked fine before we started testing encryption
the duplicate process worked fine with database A having an encrypted column in one table in a non-encrypted tablespace
Now, database A has an encrypted tablespace with nothing currently in it. The duplicate process now ultimately fails with ORA-19913, unable to decrypt backup.
I am not using encrypted backups, not specifying encrypt or decrypt anywhere in the duplication process. The only thing that is encrypted is the one tablespace in database A. I have the same wallet files on Host A (database A) and Host B (database B). Wallets are open. So why does the duplication process fail because the backup cannot be decrypted?
I want to do the recovery of my database using the archive log files but one of the archive log in between is missing,
View 17 Replies View Related