Oracle archive log move

Dear All,
Please help me at the time of Netvault RMAN backup how i move the archive log file another location.
Normal case if i moved the archive log file Netvault RMAN backup fail, so please suggest.
Thanks,
Manas

Hi;
You have to login https://support.oracle.com/CSP/ui/flash.html and you have to CSI account.
This site is oracle site for tech. documents for can rise SR etc.. for more details please check Re: Installing Oracle Database 10.2.0.4
you need to customer support identifier which is called CSI for can login metalink(https://support.oracle.com/CSP/ui/flash.html)
If you dont have metalink account there is no way to see doc or download patch.
Pretty simple process:
1) You purchase a perpetual or term license from Oracle;
2) At the beginning of the period, during the valid term you purchase
Support for the period (1 year);
3) Oracle sends you the CSI.
Easy to do at http://store.oracle.com armed with a credit card.
You can also see:
http://repettas.wordpress.com/2008/11/01/restore-archive-logs-to-new-location-using-rman/
http://oracledisect.blogspot.com/2008/06/when-your-archive-log-destination-is.html
Regard
Helios

Similar Messages

Oracle archive log compression

Dear All,
Please help me how I compress oracle archive log in 10g.
Thanks,
Manas

manas wrote:
Dear All,
Please help me how I compress oracle archive log in 10g.
Thanks,
ManasUse RMAN by Compressed option (or) with Compressed and delete input option
RMAN> backup as compressed backupset archivelog all;
Starting backup at 23-FEB-12
current log archived
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=72 device type=DISK
channel ORA_DISK_1: starting compressed archived log backup set
channel ORA_DISK_1: specifying archived log(s) in backup set
input archived log thread=1 sequence=16 RECID=11 STAMP=775778430
input archived log thread=1 sequence=17 RECID=12 STAMP=775819218
input archived log thread=1 sequence=18 RECID=13 STAMP=775835555
input archived log thread=1 sequence=19 RECID=14 STAMP=775835555
channel ORA_DISK_1: starting piece 1 at 23-FEB-12
channel ORA_DISK_1: finished piece 1 at 23-FEB-12
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2012_02_23\O1_MF_ANNNN_TAG20120223T115447_7NCPXJBF_.BKP tag=TAG20120223T115447 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:07
channel ORA_DISK_1: starting compressed archived log backup set
channel ORA_DISK_1: specifying archived log(s) in backup set
input archived log thread=1 sequence=1 RECID=15 STAMP=775847193
input archived log thread=1 sequence=2 RECID=16 STAMP=775847245
input archived log thread=1 sequence=3 RECID=17 STAMP=775847246
input archived log thread=1 sequence=4 RECID=18 STAMP=775864847
input archived log thread=1 sequence=5 RECID=19 STAMP=775906825
input archived log thread=1 sequence=6 RECID=20 STAMP=775906906
input archived log thread=1 sequence=7 RECID=21 STAMP=776001285
channel ORA_DISK_1: starting piece 1 at 23-FEB-12
channel ORA_DISK_1: finished piece 1 at 23-FEB-12
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2012_02_23\O1_MF_ANNNN_TAG20120223T115447_7NCPXQS2_.BKP tag=TAG20120223T115447 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:07
Finished backup at 23-FEB-12
Starting Control File and SPFILE Autobackup at 23-FEB-12
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORCL\AUTOBACKUP\2012_02_23\O1_MF_S_776001303_7NCPY044_.BKP comment=NONE
Finished Control File and SPFILE Autobackup at 23-FEB-12
RMAN>
=====================
RMAN> backup as compressed backupset archivelog all delete input;
Starting backup at 23-FEB-12
current log archived
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=9 device type=DISK
channel ORA_DISK_1: starting compressed archived log backup set
channel ORA_DISK_1: specifying archived log(s) in backup set
input archived log thread=1 sequence=16 RECID=11 STAMP=775778430
input archived log thread=1 sequence=17 RECID=12 STAMP=775819218
input archived log thread=1 sequence=18 RECID=13 STAMP=775835555
input archived log thread=1 sequence=19 RECID=14 STAMP=775835555
channel ORA_DISK_1: starting piece 1 at 23-FEB-12
channel ORA_DISK_1: finished piece 1 at 23-FEB-12
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2012_02_23\O1_MF_ANNNN_TAG20120223T115645_7NCQ15OV_.BKP tag=TAG20120223T115645 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:08
channel ORA_DISK_1: deleting archived log(s)
archived log file name=C:\ORACLE\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2012_02_20\O1_MF_1_16_7N4X928H_.ARC RECID=11 STAMP=775778430
archived log file name=C:\ORACLE\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2012_02_21\O1_MF_1_17_7N653S9L_.ARC RECID=12 STAMP=775819218
archived log file name=C:\ORACLE\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2012_02_21\O1_MF_1_18_7N6MQBWS_.ARC RECID=13 STAMP=775835555
archived log file name=C:\ORACLE\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2012_02_21\O1_MF_1_19_7N6NXV4M_.ARC RECID=14 STAMP=775835555
channel ORA_DISK_1: starting compressed archived log backup set
channel ORA_DISK_1: specifying archived log(s) in backup set
input archived log thread=1 sequence=1 RECID=15 STAMP=775847193
input archived log thread=1 sequence=2 RECID=16 STAMP=775847245
input archived log thread=1 sequence=3 RECID=17 STAMP=775847246
input archived log thread=1 sequence=4 RECID=18 STAMP=775864847
input archived log thread=1 sequence=5 RECID=19 STAMP=775906825
input archived log thread=1 sequence=6 RECID=20 STAMP=775906906
input archived log thread=1 sequence=7 RECID=21 STAMP=776001285
input archived log thread=1 sequence=8 RECID=22 STAMP=776001403
channel ORA_DISK_1: starting piece 1 at 23-FEB-12
channel ORA_DISK_1: finished piece 1 at 23-FEB-12
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2012_02_23\O1_MF_ANNNN_TAG20120223T115645_7NCQ1GLP_.BKP tag=TAG20120223T115645 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:08
channel ORA_DISK_1: deleting archived log(s)
archived log file name=C:\ORACLE\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2012_02_21\O1_MF_1_1_7N70G0F6_.ARC RECID=15 STAMP=775847193
archived log file name=C:\ORACLE\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2012_02_21\O1_MF_1_2_7N70HOHF_.ARC RECID=16 STAMP=775847245
archived log file name=C:\ORACLE\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2012_02_21\O1_MF_1_3_7N70HP3O_.ARC RECID=17 STAMP=775847246
archived log file name=C:\ORACLE\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2012_02_21\O1_MF_1_4_7N7KONB8_.ARC RECID=18 STAMP=775864847
archived log file name=C:\ORACLE\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2012_02_22\O1_MF_1_5_7N8TOK3Q_.ARC RECID=19 STAMP=775906825
archived log file name=C:\ORACLE\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2012_02_22\O1_MF_1_6_7N8TR2S1_.ARC RECID=20 STAMP=775906906
archived log file name=C:\ORACLE\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2012_02_23\O1_MF_1_7_7NCPXCKL_.ARC RECID=21 STAMP=776001285
archived log file name=C:\ORACLE\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2012_02_23\O1_MF_1_8_7NCQ13VV_.ARC RECID=22 STAMP=776001403
Finished backup at 23-FEB-12
Starting Control File and SPFILE Autobackup at 23-FEB-12
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORCL\AUTOBACKUP\2012_02_23\O1_MF_S_776001423_7NCQ1RFZ_.BKP comment=NONE
Finished Control File and SPFILE Autobackup at 23-FEB-12
RMAN>Edited by: CKPT on Feb 23, 2012 11:57 AM

Skipping archive logs

Hi All,
I have a question regarding oracle archive log configuration .
My DB is : Ora10gR2
Unix : HPUX
To support Data guard functionality DBA has put DB in ARCHIVE LOG mode with forced logging mode =YES.
1* select LOG_MODE,FORCE_LOGGING from v$database
SQL> /
LOG_MODE FORCE_LOGGING
ARCHIVELOG YES
Now i have a table called PARAMETER where i need to load aroung 700 Million records . Since DB is in forced logging mode this will create lot of log information and that will take long time to load as well.
Is thr any option to keep a table in nologging mode , even if the DB is in forced logging mode ??
Thanks

am_73798 wrote:
Hi All,
I have a question regarding oracle archive log configuration .
My DB is : Ora10gR2
Unix : HPUX
To support Data guard functionality DBA has put DB in ARCHIVE LOG mode with forced logging mode =YES.
1* select LOG_MODE,FORCE_LOGGING from v$database
SQL> /
LOG_MODE FORCE_LOGGING
ARCHIVELOG YES
Now i have a table called PARAMETER where i need to load aroung 700 Million records . Since DB is in forced logging mode this will create lot of log information and that will take long time to load as well.
Is thr any option to keep a table in nologging mode , even if the DB is in forced logging mode ??
ThanksHi,
No there is no option to keep a table in nologging mode if DB is in force logging.
Regards
Anurag

No clarity on location of archive logs in Oracle 11g database

I have this query which I am not able to resolve. There is one location of archive log mentioned as /oraarch/app/oracle/oradata/snlprod/archive_logs/ in the parameter log_archive_dest_1. But the archive logs are showing in another location /orabackup/rman/snlprod/archive_logs. I am wondering how the archive logs are showing in this location, /orabackup/rman/snlprod/archive_logs.
I guess there is only one way in which location can be given which is seen from Availability->Recovery Settings->Media Recovery.
I hope, my question is clear.
Please revert with the reply to my query.
Regards

Must be
show parameter db_recovery_file_dest
If you want archived redo log send to /oraarch/app/oracle/oradata/snlprod/archive_logs
then you must set log_archive_dest_1 ='LOCATION= /oraarch/app/oracle/oradata/snlprod/archive_logs'
log_archive_dest_1 is same before then it means your all archvied redo log file will create in this directory
Regards
Mahir M. Quluzade

Deletion of archive log using RMAN Target in Oracle 10g

Hi All,
I recently have noticed that the archive logs have occupied 102 GBs out of the drive and I need to free up some space. When I tried to connect RMAN Catalog using
connect catalog user@dbI got error message as
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-06445: cannot connect to recovery catalog after NOCATALOG has been usedBut I was able to get through using
connect target user@dbMy Query is can I use
RMAN> delete noprompt expired archivelog all;as given in [how to delete archive log file |https://forums.oracle.com/forums/thread.jspa?threadID=2321257&start=0&tstart=0]
Or shall I take any other approach to delete the obsolete archive logs?
Regards,
*009*

Hello;
I recently have noticed that the archive logs have occupied 102 GBs out of the drive and I need to free up some space. When I tried to connect RMAN Catalog using
connect catalog user@dbI got error message as
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-06445: cannot connect to recovery catalog after NOCATALOG has been usedBut I was able to get through using
connect target user@db
Are you trying to connect it through Grid control ? If connecting through a script, then please post its contents.
Make sure you are not connecting to the target database using "nocatalog".
rman target sys/<pwd_of_target>@<target_db> catalog <catalog_schema>/<catalog_schema_pwd>@<catalog_db>
My Query is can I use
RMAN> delete noprompt expired archivelog all;
as given in [how to delete archive log file |https://forums.oracle.com/forums/thread.jspa?threadID=2321257&start=0&tstart=0]
Or shall I take any other approach to delete the obsolete archive logs?
Regards,
*009*Are these archives backed up ? The above command only updates the RMAN repository if in case the archives were delete manually at OS level.
I would recommend you to backup these archives and then delete them.
RMAN>backup archivelog all not backedup 1 times delete input;If these archives are already backed up and have not been deleted from the disk, then you can use the below command
RMAN>delete force noprompt archivelog all completed before 'SYSDATE-n';where "n" is the number of days behind the current date. Make sure to verify if these archives have been backed up before deleting.
Regards,
Shivananda

Oracle recommended location for archive logs in oracle 10g rac

Hello All,
We would like to know the oracle recommended location for the archive logs in oracle10g RAC .we are using ASM.
Thanks...

user4487322 wrote:
thanks. Is it the recommended setting ,if we go for a DR setup?I mean archive logs in ASM.If you can use dataguard, the archivelog copy to the standby system would be handled by Oracle and it supports ASM.
Just remember, what ever your strategy, the archivelogs must be in a SHARED location (where all nodes can read/write to this location.)

Archive log folders in Oracle 10g

Hi everybody,
I have installed Oracle 10g on my Windows XP Pro SP3 in archivelog mode.
The archived log are saved in different folders according to the save date; for example I have a folder called 2008_06_06 which contains all the archives saved on that day and so on
I'd like to have all archive log saved by Oracle in only one folder, how can I specify this in the installation process or in the parametrs settings?
Thanks, Valerio

user640800 wrote:
Hi everybody,
I have installed Oracle 10g on my Windows XP Pro SP3 in archivelog mode.
The archived log are saved in different folders according to the save date; for example I have a folder called 2008_06_06 which contains all the archives saved on that day and so on
I'd like to have all archive log saved by Oracle in only one folder, Why? What problem does it solve? Oracle knows where those files are, how to back them up, how to restore them from backup, how to delete them when they are no longer needed. Rman will take care of all the housekeeping just fine, thank you very much.
Yes, oracle provides mechanisms for writing the archivelogs to a different directory structure and with a different file name convention. But again, to what end? What problem does it solve by doing so?
how can I specify this in the installation process or in the parametrs settings?Go to tahiti.oracle.com. Drill down to your product and version. Locate the Reference Manual. Open it and scan the table of contents. You will find a section on initialization parms. Use your browser's search function to find parms that deal with "archive".
>
Thanks, Valerio

Archive log mode in oracle 10g

Hi,
I would like to know the archive log mode in oracle 10g and I use this code in SQLPlus
select log_mode from v$database
But it displayed: "2" not : NOARCHIVELOG or ARCHIVELOG
It displayed a number, not a String.
How could I know this?
Thanks

Hi Paul
Because I am a newbie in DBA Oracle so I got many difficulties.
You are very kind to help me.
So I have some more questions:
1. when I executed this code, it always reported error:
$ tmp=`${ORACLE_HOME}/bin/sqlplus -s / as sysdba << EOF
set heading off feedback off;
exit
EOF`
tmp='ERROR:
ORA-01031: insufficient privileges
SP2-0306: Invalid option.
Usage: CONN[ECT] [logon] [AS {SYSDBA|SYSOPER}]
where <logon> ::= <username>[<password>][@<connect_identifier>] | /
SP2-0306: Invalid option.
Usage: CONN[ECT] [logon] [AS {SYSDBA|SYSOPER}]
where <logon> ::= <username>[<password>][@<connect_identifier>] | /
SP2-0157: unable to CONNECT to ORACLE after 3 attempts, exiting SQL*Plus'
so when I updated like this:
tmp=`${ORACLE_HOME}/bin/sqlplus -s sys/syspass@db02 as sysdba <<EOF
               set heading off feedback off;
               exit
               EOF`
It run correctly.
2. With Paul's guide:
Do not execute Oracle commands from root, execute them as oracle user. This works to me :
$ tmp=`${ORACLE_HOME}/bin/sqlplus -s / as sysdba << EOF
set heading off feedback off
alter database backup controlfile to '${CONTROLFILE_DIR}/<file name>';
alter database backup controlfile to trace;
exit
EOF`
Of course CONTROLFILE_DIR must be set to a directory with write permission for oracle user.
For ex: I have an Unix account: unix/unix
and a Sys Oracle account: oracle/oracle
I login with Unix acount (unix/unix) and call script file that contains above code.
tmp=`${ORACLE_HOME}/bin/sqlplus -s oracle/oracle@db02 as sysdba <<EOF
               set heading off feedback off
               alter database backup controlfile to '${CONTROLFILE_DIR}/backup_control.ctl';
               alter database backup controlfile to trace;
               exit
               EOF`
Unix report as following: Linux error: 13: Permission denied.
CONTROLFILE_DIR directory is read,write,execute for account unix/unix.
Of course CONTROLFILE_DIR must be set to a directory with write permission for oracle user. You mean I have to create a Unix user is the same to Oracle user so that Oracle user can have permission to write.
Please guilde more detail.
Thanks for your attention.
Message was edited by:
user481034

Oracle write archive log files continuosly

Hi all,
I don't know why my Oracle Database has this problem. Online log are writen to archive log file continuously(3 minutes period). My archive logfile is 300M. I have startup force my database. It work, but archive log files are writen so much. This is alert log:
>
Sat Jan 1 14:23:19 2011
Successfully onlined Undo Tablespace 5.
Sat Jan 1 14:23:19 2011
SMON: enabling tx recovery
Sat Jan 1 14:23:19 2011
Database Characterset is AL32UTF8
Opening with internal Resource Manager plan
where NUMA PG = 1, CPUs = 16
replication_dependency_tracking turned off (no async multimaster replication found)
Sat Jan 1 14:23:40 2011
WARNING: AQ_TM_PROCESSES is set to 0. System operation might be adversely affected.
Sat Jan 1 14:24:32 2011
db_recovery_file_dest_size of 204800 MB is 28.64% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Sat Jan 1 14:24:40 2011
Completed: ALTER DATABASE OPEN
Sat Jan 1 14:27:05 2011
Warning: PROCESSES may be too low for current load
shared servers=360, want 7 more but starting only 3 more
Warning: PROCESSES may be too low for current load
shared servers=363, want 9 more but starting only 0 more
Sat Jan 1 14:27:39 2011
Warning: PROCESSES may be too low for current load
shared servers=363, want 9 more but starting only 1 more
Warning: PROCESSES may be too low for current load
shared servers=364, want 9 more but starting only 0 more
Sat Jan 1 14:28:58 2011
Thread 1 advanced to log sequence 9463 (LGWR switch)
Current log# 3 seq# 9463 mem# 0: /u01/oradata/TNORA3/redo03a.log
Current log# 3 seq# 9463 mem# 1: /u02/oradata/TNORA3/redo03b.log
Sat Jan 1 14:30:20 2011
Errors in file /opt/app/oracle/admin/TNORA3/bdump/tnora_j000_17762.trc:
ORA-00604: error occurred at recursive SQL level 1
ORA-00018: maximum number of sessions exceeded
Sat Jan 1 14:39:47 2011
Thread 1 advanced to log sequence 9464 (LGWR switch)
Current log# 1 seq# 9464 mem# 0: /u01/oradata/TNORA3/redo01a.log
Current log# 1 seq# 9464 mem# 1: /u02/oradata/TNORA3/redo01b.log
Sat Jan 1 14:42:51 2011
Errors in file /opt/app/oracle/admin/TNORA3/bdump/tnora_s008_17165.trc:
ORA-07445: exception encountered: core dump [_intel_fast_memcpy.J()+80] [SIGSEGV] [Address not mapped to object] [0x2B8988CE2018] [] []
Sat Jan 1 14:42:57 2011
Thread 1 advanced to log sequence 9465 (LGWR switch)
Current log# 2 seq# 9465 mem# 0: /u01/oradata/TNORA3/redo02a.log
Current log# 2 seq# 9465 mem# 1: /u02/oradata/TNORA3/redo02b.log
Sat Jan 1 14:43:11 2011
found dead shared server 'S008', pid = (42, 1)
Sat Jan 1 14:45:39 2011
Thread 1 advanced to log sequence 9466 (LGWR switch)
Current log# 3 seq# 9466 mem# 0: /u01/oradata/TNORA3/redo03a.log
Current log# 3 seq# 9466 mem# 1: /u02/oradata/TNORA3/redo03b.log
Sat Jan 1 14:48:47 2011
Thread 1 cannot allocate new log, sequence 9467
Checkpoint not complete
Current log# 3 seq# 9466 mem# 0: /u01/oradata/TNORA3/redo03a.log
Current log# 3 seq# 9466 mem# 1: /u02/oradata/TNORA3/redo03b.log
Sat Jan 1 14:48:50 2011
Thread 1 advanced to log sequence 9467 (LGWR switch)
Current log# 1 seq# 9467 mem# 0: /u01/oradata/TNORA3/redo01a.log
Current log# 1 seq# 9467 mem# 1: /u02/oradata/TNORA3/redo01b.log
Sat Jan 1 14:52:11 2011
Thread 1 advanced to log sequence 9468 (LGWR switch)
Current log# 2 seq# 9468 mem# 0: /u01/oradata/TNORA3/redo02a.log
Current log# 2 seq# 9468 mem# 1: /u02/oradata/TNORA3/redo02b.log
Sat Jan 1 14:55:12 2011
Thread 1 advanced to log sequence 9469 (LGWR switch)
Current log# 3 seq# 9469 mem# 0: /u01/oradata/TNORA3/redo03a.log
Current log# 3 seq# 9469 mem# 1: /u02/oradata/TNORA3/redo03b.log
Sat Jan 1 14:58:12 2011
Thread 1 advanced to log sequence 9470 (LGWR switch)
Current log# 1 seq# 9470 mem# 0: /u01/oradata/TNORA3/redo01a.log
Current log# 1 seq# 9470 mem# 1: /u02/oradata/TNORA3/redo01b.log
Sat Jan 1 15:02:00 2011
Thread 1 advanced to log sequence 9471 (LGWR switch)
Current log# 2 seq# 9471 mem# 0: /u01/oradata/TNORA3/redo02a.log
Current log# 2 seq# 9471 mem# 1: /u02/oradata/TNORA3/redo02b.log
Sat Jan 1 15:05:16 2011
Thread 1 advanced to log sequence 9472 (LGWR switch)
Current log# 3 seq# 9472 mem# 0: /u01/oradata/TNORA3/redo03a.log
Current log# 3 seq# 9472 mem# 1: /u02/oradata/TNORA3/redo03b.log
Sat Jan 1 15:08:30 2011
Thread 1 advanced to log sequence 9473 (LGWR switch)
Current log# 1 seq# 9473 mem# 0: /u01/oradata/TNORA3/redo01a.log
Current log# 1 seq# 9473 mem# 1: /u02/oradata/TNORA3/redo01b.log
Sat Jan 1 15:11:12 2011
Thread 1 cannot allocate new log, sequence 9474
Checkpoint not complete
Current log# 1 seq# 9473 mem# 0: /u01/oradata/TNORA3/redo01a.log
Current log# 1 seq# 9473 mem# 1: /u02/oradata/TNORA3/redo01b.log
Sat Jan 1 15:11:14 2011
Thread 1 advanced to log sequence 9474 (LGWR switch)
Current log# 2 seq# 9474 mem# 0: /u01/oradata/TNORA3/redo02a.log
Current log# 2 seq# 9474 mem# 1: /u02/oradata/TNORA3/redo02b.log
Sat Jan 1 15:14:15 2011
Thread 1 advanced to log sequence 9475 (LGWR switch)
Current log# 3 seq# 9475 mem# 0: /u01/oradata/TNORA3/redo03a.log
Current log# 3 seq# 9475 mem# 1: /u02/oradata/TNORA3/redo03b.log
>
PLs, help me.

This is the contait of tail -100 /opt/app/oracle/admin/TNORA3/bdump/tnora_s008_17165.trc | more
KCBS: Tot bufs in set segwise
KCBS: nbseg[0] is 1568
KCBS: nbseg[1] is 1568
KCBS: nbseg[2] is 1569
KCBS: nbseg[3] is 1568
KCBS: nbseg[4] is 1568
KCBS: nbseg[5] is 1568
KCBS: nbseg[6] is 1569
KCBS: nbseg[7] is 1568
KCBS: nbseg[8] is 1568
KCBS: nbseg[9] is 1568
KCBS: nbseg[10] is 1569
KCBS: nbseg[11] is 1568
KCBS: nbseg[12] is 1568
KCBS: nbseg[13] is 1568
KCBS: nbseg[14] is 1569
KCBS: nbseg[15] is 1568
KCBS: nbseg[16] is 1568
KCBS: nbseg[17] is 1568
KCBS: nbseg[18] is 1569
KCBS: nbseg[19] is 1568
KCBS: Act cnt = 15713
KCBS: bufcnt = 31365, nb_kcbsds = 31365
KCBS: fbufcnt = 445
KCBS: Tot bufs in set segwise
KCBS: nbseg[0] is 1568
KCBS: nbseg[1] is 1568
KCBS: nbseg[2] is 1569
KCBS: nbseg[3] is 1568
KCBS: nbseg[4] is 1568
KCBS: nbseg[5] is 1568
KCBS: nbseg[6] is 1569
KCBS: nbseg[7] is 1568
KCBS: nbseg[8] is 1568
KCBS: nbseg[9] is 1568
KCBS: nbseg[10] is 1569
KCBS: nbseg[11] is 1568
KCBS: nbseg[12] is 1568
KCBS: nbseg[13] is 1568
KCBS: nbseg[14] is 1569
KCBS: nbseg[15] is 1568
KCBS: nbseg[16] is 1568
KCBS: nbseg[17] is 1568
KCBS: nbseg[18] is 1569
KCBS: nbseg[19] is 1568
KCBS: Act cnt = 15713
KCBS: bufcnt = 31365, nb_kcbsds = 31365
KCBS: fbufcnt = 445
KCBS: Tot bufs in set segwise
KCBS: nbseg[0] is 1568
KCBS: nbseg[1] is 1568
KCBS: nbseg[2] is 1568
KCBS: nbseg[3] is 1569
KCBS: nbseg[4] is 1568
KCBS: nbseg[5] is 1568
KCBS: nbseg[6] is 1568
KCBS: nbseg[7] is 1569
KCBS: nbseg[8] is 1568
KCBS: nbseg[9] is 1568
KCBS: nbseg[10] is 1568
KCBS: nbseg[11] is 1569
KCBS: nbseg[12] is 1568
KCBS: nbseg[13] is 1568
KCBS: nbseg[14] is 1568
KCBS: nbseg[15] is 1569
KCBS: nbseg[16] is 1568
KCBS: nbseg[17] is 1568
KCBS: nbseg[18] is 1568
KCBS: nbseg[19] is 1569
KCBS: Act cnt = 15713
KCBS: bufcnt = 31365, nb_kcbsds = 31365
KCBS: fbufcnt = 444
KCBS: Tot bufs in set segwise
KCBS: nbseg[0] is 1568
KCBS: nbseg[1] is 1568
KCBS: nbseg[2] is 1568
KCBS: nbseg[3] is 1569
KCBS: nbseg[4] is 1568
KCBS: nbseg[5] is 1568
KCBS: nbseg[6] is 1568
KCBS: nbseg[7] is 1569
KCBS: nbseg[8] is 1568
KCBS: nbseg[9] is 1568
KCBS: nbseg[10] is 1568
KCBS: nbseg[11] is 1569
KCBS: nbseg[12] is 1568
KCBS: nbseg[13] is 1568
KCBS: nbseg[14] is 1568
KCBS: nbseg[15] is 1569
KCBS: nbseg[16] is 1568
KCBS: nbseg[17] is 1568
KCBS: nbseg[18] is 1568
KCBS: nbseg[19] is 1569
KCBS: Act cnt = 15713
KSOLS: Begin dumping all object level stats elements
KSOLS: Done dumping all elements. Exiting.
Dump event group for SESSION
Unable to dump event group - no SESSION state objectDump event group for SYSTEM
ssexhd: crashing the process...
Shadow_Core_Dump = partial

Managing ARCHIVE Logs in Oracle 10.2.0.3

I am working with a customer who seems to think there is a way of controling the database other than a custom JOB, script or RMAN in how it creates, manages and deletes its archive logs while running in archivelog mode. He wants the database to automatically delete obsolete archive logs. He also wants to control the duration in time between each time an archive log is written in order to stop the growth of archive logs and filling up disk space.
I am saying this is not possible. You either configure RMAN to delete the obsolete or expired archive logs based on your retention policy or do it manually in the Enterprise Manager or Grid Control Console by deletenig obsolete or expired logs.
Am I correct or am I off base here?

4.1.3 Sizing Redo Log Files
The size of the redo log files can influence performance, because the behavior of the database writer and archiver processes depend on the redo log sizes. Generally, larger redo log files provide better performance. Undersized log files increase checkpoint activity and reduce performance.
Although the size of the redo log files does not affect LGWR performance, it can affect DBWR and checkpoint behavior. Checkpoint frequency is affected by several factors, including log file size and the setting of the FAST_START_MTTR_TARGET initialization parameter. If the FAST_START_MTTR_TARGET parameter is set to limit the instance recovery time, Oracle automatically tries to checkpoint as frequently as necessary. Under this condition, the size of the log files should be large enough to avoid additional checkpointing due to under sized log files. The optimal size can be obtained by querying the OPTIMAL_LOGFILE_SIZE column from the V$INSTANCE_RECOVERY view. You can also obtain sizing advice on the Redo Log Groups page of Oracle Enterprise Manager Database Control.
It may not always be possible to provide a specific size recommendation for redo log files, but redo log files in the range of a hundred megabytes to a few gigabytes are considered reasonable. Size your online redo log files according to the amount of redo your system generates. A rough guide is to switch logs at most once every twenty minutes.
http://download.oracle.com/docs/cd/B19306_01/server.102/b14211/build_db.htm#sthref237
If you are talking about data guard then:
4.1.3 Sizing Redo Log Files
The size of the redo log files can influence performance, because the behavior of the database writer and archiver processes depend on the redo log sizes. Generally, larger redo log files provide better performance. Undersized log files increase checkpoint activity and reduce performance.
Although the size of the redo log files does not affect LGWR performance, it can affect DBWR and checkpoint behavior. Checkpoint frequency is affected by several factors, including log file size and the setting of the FAST_START_MTTR_TARGET initialization parameter. If the FAST_START_MTTR_TARGET parameter is set to limit the instance recovery time, Oracle automatically tries to checkpoint as frequently as necessary. Under this condition, the size of the log files should be large enough to avoid additional checkpointing due to under sized log files. The optimal size can be obtained by querying the OPTIMAL_LOGFILE_SIZE column from the V$INSTANCE_RECOVERY view. You can also obtain sizing advice on the Redo Log Groups page of Oracle Enterprise Manager Database Control.
It may not always be possible to provide a specific size recommendation for redo log files, but redo log files in the range of a hundred megabytes to a few gigabytes are considered reasonable. Size your online redo log files according to the amount of redo your system generates. A rough guide is to switch logs at most once every twenty minutes.
Automatic Deletion of Applied Archive Logs
Archived logs, once they are applied on the logical standby database, will be automatically deleted by SQL Apply.
This feature reduces storage consumption on the logical standby database and improves Data Guard manageability.
See also:
Oracle Data Guard Concepts and Administration for details
http://download.oracle.com/docs/cd/B19306_01/server.102/b14214/chapter1.htm#sthref269

Putting a Oracle RAC in to archive log mode??

Our RAC is a 10gR2 Three(3) node RAC with a SAN as the shared storage. cluster is installed on linux. at the moment the RAC is in noarchieve log mode.
SQL> archive log list;
Database log mode No Archive Mode
Automatic archival Disabled
Archive destination /u01/app/oracle/product/10.2.
0/db_1/dbs/arch
Oldest online log sequence 665
Current log sequence 666
we created raw partitions in SAN and use ASM to manage shared storage.
when running DBCA at "specify locations for the database files to be created" step we selected "use oracle managed files" and gave database area = +DATA/
then at choose the recovery options for the database" step we ticked specify flash recovery area and gave Flash Recovery AREA = +BACKUP/ and flash recovery area = 10240 MB. we didnt click "enable archiving" option. hence the RAC DB is in NOARCHIEVELOG mode.
i found some guide to put RAC in archive log mode which i have given below....
ALTER SYSTEM SET log_archive_start=TRUE SCOPE=spfile;
ALTER SYSTEM SET log_archive_dest_1='location=/u01/oradata/MYSID/archive/' SCOPE=spfile;
ALTER SYSTEM SET log_archive_format='arch_%t_%s.arc' SCOPE=spfile;
Since we need to mount the database in exclusive mode we must also alter the following parameter:
ALTER SYSTEM SET cluster_database=FALSE SCOPE=spfile;
From the command line we can stop the entire cluster using:
srvctl stop database -d MYSID
With the cluster down we can connect to a single node and issue the following commands:
STARTUP MOUNT;
ARCHIVE LOG START;
ALTER DATABASE ARCHIVELOG;
ALTER SYSTEM SET cluster_database=TRUE SCOPE=spfile;
SHUTDOWN IMMEDIATE;
Notice that the CLUSTER_DATABASE parameter has been reset to it's original value. Since the datafiles and spfile are shared between all instances this operation only has to be done from a single node.
From the command line we can now start the cluster again using:
srvctl start database -d MYSID
my main question is about the setting of
ALTER SYSTEM SET log_archive_dest_1='location= ????? ' SCOPE=spfile;
since i have set +BACKUP/ as the FRA during installation how should i define the location of log_archive_dest_1???
many thanks in advance.
regards
Dilan

many thanks for the replies
will the command you posted send the archive logs to the "+BACKUP/" location in my SAN.
if yes how does oracle know that USE_DB_RECOVERY_FILE_DEST = BACKUP/ in my SAN. or how do i set oracle to use BACKUP/ as the USE_DB_RECOVERY_FILE_DEST??
im a newbie to RAC so pls bear with me. also at the moment i get the following outputs from my database.... pls note the bold part below, is the archive destination pointing to a location in my local server?
SQL> archive log list;
Database log mode No Archive Mode
Automatic archival Disabled
Archive destination /u01/app/oracle/product/10.2.0/db_1/dbs/arch
Oldest online log sequence 665
Current log sequence 666
SQL> show parameter db_recovery;
NAME TYPE VALUE
db_recovery_file_dest string
db_recovery_file_dest_size big integer 0
SQL> show parameter archive
NAME TYPE VALUE
archive_lag_target integer 0
log_archive_config string
log_archive_dest string
log_archive_dest_1 string
log_archive_dest_10 string
log_archive_dest_2 string
log_archive_dest_3 string
log_archive_dest_4 string
log_archive_dest_5 string
log_archive_dest_6 string
log_archive_dest_7 string
NAME TYPE VALUE
log_archive_dest_8 string
log_archive_dest_9 string
log_archive_dest_state_1 string enable
log_archive_dest_state_10 string enable
log_archive_dest_state_2 string enable
log_archive_dest_state_3 string enable
log_archive_dest_state_4 string enable
log_archive_dest_state_5 string enable
log_archive_dest_state_6 string enable
log_archive_dest_state_7 string enable
log_archive_dest_state_8 string enable
NAME TYPE VALUE
log_archive_dest_state_9 string enable
log_archive_duplex_dest string
log_archive_format string %t_%s_%r.dbf
log_archive_local_first boolean TRUE
log_archive_max_processes integer 2
log_archive_min_succeed_dest integer 1
log_archive_start boolean FALSE
log_archive_trace integer 0
remote_archive_enable string true
standby_archive_dest string ?/dbs/arch

Oracle 10g - switch off archive logs

Hi,
I understand in oracle 10g, the following parameter is not longer available:
LOG_ARCHIVE_START=FALSE
Can i confirm that for now, only way to disable archive log is to execute the following command when in mount stage:
alter database noarchivelog;
There's not other parameter we can specify in pfile to disable it permantely?
thanks

You are correct. No other parameters.

Oracle Restore from Online backup without any archive logs

Hi,
May be a dumb question. If I have a good online backup (say it took 2 hours to do that. And there is database activity while backup is going on), and lost all the archive logs happened after the online backup, is it possible at all to do the restore using that backup? complete or incomplete? and bring back the database to normal operation mode? Some details on this.
Thanks.

Let us see the reasoning behind this.
Database:WORLDDB
WORLDDB configuration:-
TBSP_WDB
->TBSP_WDB_01.dbf
->TBSP_WDB_02.dbf
SYSTEM
->SYSTEM.dbf
USERS
and so on for the tablespaces.
CASE 1:-
User managed backup.
You issue
ALTER TABLESPACE TBSP_WDB BEGIN BACKUP;
DB keeps working all transactions are recorded in the redo stream, the scn information is not updated in the file header.
Also note that the other tablespaces were been continuously worked on hence their scn numbers are a moving target.
http://download-east.oracle.com/docs/cd/B10501_01/server.920/a96572/osbackups.htm#10012
So if you begin tablespace TBSP_WDB backup at time t1 and by the time you are done with your backups you are at time t2, you will need all of the archive log's between time t1 and t2.
CASE 2:-
If we do with rman, rman takes care of the file header update information and goes on its merry way, those details are hidden from the end user. If one of the tablespace is fractured, updated while backups are going on , rman knows about it and will re-read the affected blocks in question.
My thinking would be that you might need archive logs, unless it is a cold backup, with switch logfiles in between.
If you do hot backups you need archivelogs is my thought. The number of archivelogs required will be decreased considerably through rman.
http://download-east.oracle.com/docs/cd/B10501_01/server.920/a96566/rcmconc1.htm#458821
Summary:-
Either way archivelogs are needed.

Oracle 9i request wrong archive log name during recovery

Hello all,
I am facing a problem with a database 9i Enterprise Edition running on Windows 2003 Enterprise Edition environment. According to the customer, when he takes the database offline using MSCS to take an offline backup, the database crashes when he tries to put it back online... But here a strange thing happens... when the command RECOVER DATABASE is issued, it asks for the wrong archive log... for example:
The actual sequence is 14322, but Oracle asks for the archive log SID_4322... (in this case we have to rename the original file SID_14322 to SID_4322). I don't understand why it asks for the archive incorrectly... I issued the command ARCHIVE LOG LIST and it says that the current thread is 14322 (which is correct)... every new archive is created with the correct name (SID_143XX)... why is it asking for an archive without the number 1 in this case? Rename all the files to recover a database is not very pleasent job... creating an script to do so is not a solution in my opinion, hehe. Thanks for your help in advance.
Best regards,
Bruno Carvalho
Edited by: Bruno Carvalho on Jul 5, 2010 10:08 AM

Hello Damorgan,
MSCS = Microsoft Cluster Services (it's an MMC console). The backup strategy is very old, and they use BR*Tools script to create a job on ArcServe Brigstor, and then the backup is performed via backint. (It's an SAP ERP system, which should be backed up using BR*Tools). I checked the alert log and I think that the problem is the length of the archive log name (in the alert log it gives me the error below):
ARCH: Warning. Log sequence in archive filename wrapped
to fix length as indicated by %S in LOG_ARCHIVE_FORMAT.
Old log archive with same name might be overwritten.
Media Recovery Log E:\ORACLE\SID\SAPARCH\SIDARCH\SIDARCH_43454.DBF <- this should be SIDARCH_143454.DBF
Now I'm looking for a parameter where I can set the length of the archives, your help would be very appreciated (and please let me know if I'm not going the right way).
Best regards,
Bruno Carvalho

Tidying the list of archive logs in Oracle

We have been using Archive Logging for a while but manually handle the purging of them. Since we restart our 9.2 Oracle DBs daily and perform backups (cold) daily, the archive logs are currently suitable for a day.
However, in Oracle Enterprise Manager > Storage > Archive Logs, we see the entire list (history) of archive logs.
Can this be tidied and how?
Thanks

my mistake
Problem Description:
====================
When querying "v$loghist," the number of rows displayed is less than the total
number of Redo Logs created by the database.
Solution Description:
=====================
The quantity of Log History is driven by the internal parameter "maxloghistory".
When creating a database you have the option to specify the "maxloghistory"
parameter. The default value is OS dependent.
In order to alter this parameter you need to re-create the controlfile and
specify the "maxloghistory" parameter.
Explanation:
============
The setting for log history in the control file is set very low.
The Log history is stored in the controlfile. When a database is created we
specify how much Log history to store. Often, this setting is ignored or made
small so the controlfile is not too large.
References:
===========
Oracle Server SQL Reference
Note: there are some bugs about maxloghistory being ignored if you try to recreate your database.

Oracle archive log move

Similar Messages

Maybe you are looking for