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.

Similar Messages

Changing the location of archive log from flash recovery area PLZ HELP!!!

Hi All,
My archive log is being stored in flash memory area which got full and the production server went down.
alert log file details.....
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 43432960 bytes disk space from 2147483648 limit
*** 2010-04-25 14:22:49.777 62692 kcrr.c
ARCH: Error 19809 Creating archive log file to
'/oracle/product/10.2.0/flash_rec
overy_area/EDWREP/archivelog/2010_04_25/o1_mf_1_232_%u_.arc'
*** 2010-04-25 14:22:49.777 60970 kcrr.c
kcrrfail: dest:10 err:19809 force:0 blast:1I removed the files and started the database,
Can someone kindly tell me as to how to avoid this problem in future by keeping archive log destination in flash recovery area.
I want to change the location of archive log files, can someone please guide me as to hiow to do that
I changed the size of flash recovery area for the time being, but i am afraid it will be full again!!
SQL> select * from v$flash_recovery_area_usage;
FILE_TYPE    PERCENT_SPACE_USED PERCENT_SPACE_RECLAIMABLE NUMBER_OF_FILES
CONTROLFILE                   0                         0               0
ONLINELOG                     0                         0               0
ARCHIVELOG                99.44                         0              57
BACKUPPIECE                   0                         0               0
IMAGECOPY                     0                         0               0
FLASHBACKLOG                  0                         0               0
6 rows selected.
SQL> alter system set DB_RECOVERY_FILE_DEST_SIZE = 4G ;
System altered.
SQL> select * from v$flash_recovery_area_usage;
FILE_TYPE    PERCENT_SPACE_USED PERCENT_SPACE_RECLAIMABLE NUMBER_OF_FILES
CONTROLFILE                   0                         0               0
ONLINELOG                     0                         0               0
ARCHIVELOG                49.72                         0              57
BACKUPPIECE                   0                         0               0
IMAGECOPY                     0                         0               0
FLASHBACKLOG                  0                         0               0
6 rows selected.regards,
Edited by: user10243788 on Apr 25, 2010 6:12 AM

user10243788 wrote:
Hi All,
My archive log is being stored in flash memory area which got full and the production server went down.
alert log file details.....
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 43432960 bytes disk space from 2147483648 limit
*** 2010-04-25 14:22:49.777 62692 kcrr.c
ARCH: Error 19809 Creating archive log file to
'/oracle/product/10.2.0/flash_rec
overy_area/EDWREP/archivelog/2010_04_25/o1_mf_1_232_%u_.arc'
*** 2010-04-25 14:22:49.777 60970 kcrr.c
kcrrfail: dest:10 err:19809 force:0 blast:1I removed the files and started the database,
Can someone kindly tell me as to how to avoid this problem in future by keeping archive log destination in flash recovery area.
I want to change the location of archive log files, can someone please guide me as to hiow to do that
I changed the size of flash recovery area for the time being, but i am afraid it will be full again!!
SQL> select * from v$flash_recovery_area_usage;
FILE_TYPE    PERCENT_SPACE_USED PERCENT_SPACE_RECLAIMABLE NUMBER_OF_FILES
CONTROLFILE                   0                         0               0
ONLINELOG                     0                         0               0
ARCHIVELOG                99.44                         0              57
BACKUPPIECE                   0                         0               0
IMAGECOPY                     0                         0               0
FLASHBACKLOG                  0                         0               0
6 rows selected.
SQL> alter system set DB_RECOVERY_FILE_DEST_SIZE = 4G ;
System altered.
SQL> select * from v$flash_recovery_area_usage;
FILE_TYPE    PERCENT_SPACE_USED PERCENT_SPACE_RECLAIMABLE NUMBER_OF_FILES
CONTROLFILE                   0                         0               0
ONLINELOG                     0                         0               0
ARCHIVELOG                49.72                         0              57
BACKUPPIECE                   0                         0               0
IMAGECOPY                     0                         0               0
FLASHBACKLOG                  0                         0               0
6 rows selected.regards,
Edited by: user10243788 on Apr 25, 2010 6:12 AMPointing the archive log dest (and/or the FRA) to a new location, or enlarging them, will do no good if you are not performing regular housekeeping on the archivelogs. You will just keep knocking down the same problem over and over.
If you simply delete the archivelogs at the OS level, the database will never know about it and it will continue to think the destination is full, based on records kept in the control file.
For regular housekeeping, you need to be doing something similar to this in rman:
run {
backup archivelog all not backed up 1 times tag='bkup_vlnxora1_arch';
delete noprompt archivelog all backed up 1 times to device type disk;
run {
delete noprompt obsolete;
crosscheck archivelog all;
delete noprompt expired archivelog all;

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

After setting the db to archive log mode what to do?

Hi All,
We have a database which is being used as production database since one week and running in NoArchive Log mode. Now i wanted to change that to Archive Log mode because i want to take hot backup using RMAN daily/weekly. My doubt is..after changing the db to Archive Log mode, can i take backup using RMAN (i got a RMAN script to take a hot backup of db)? which will contain all the backup with control files and spfiles? or do i have to do anything before taking hotbackup.
Thanks,
Praveen.

Yes you are fine. BTW, how many archive destinations did you configure.
Usually it is more than 1 on two different Disks.
TEST CASE:
NOARCHIVELOG Database
Change it ARCHIVELOG
Take a hot backup and try to restore/recover it.
STATUS=SUCCES
Can someone explain this to me please:-
Ensure DB in noarchivelog mode
SQL> archive log list
Database log mode No Archive Mode
SQL> startup mount;
SQL> alter database archivelog;
SQL> alter database open;
-- DID Not take a COLD BACKUP
-- Right after switching the mode I am taking hot backup
RMAN> backup incremental level=0 database ;
RMAN> backup archivelog all delete all input;
Nuke the datafiles
RMAN> SET DBID=1299283748;
RMAN> restore controlfile from autobackup;
run
set until logseq=79 ;
restore database;
recover database;
sql 'alter database open resetlogs';
Database is opened restored / recovered?
I totally agree we should take a cold backup right after switching the mode. Can someone explain the above though.
Message was edited by:
gopalora

How to delete the data in archived log files

hi
how can i delete the enteries in archived log files. and what is the disadvantage of deleting archived log enteries.

There is no documented way to delete data stored in archived log files: you can only remove the archived log files if needed.

Finding the order of archive logs in RAC to NON-RAC manual cloning

Hi,
I am in the process of automating a RAC to NON-RAC clone using traditional method [ not using RMAN ].
Here are the steps:
On Source:
Record the sequence number and thread of the instance
put the database in begin backup mode
copy the files
disable the backup mode
record the sequence number and thread of the instance
prepare the order of the archive logs which will be needed for recovery ==> Here is where I need help
On Target:
Restore the backup
Issue recovery using the order of archive logs identified ==> Failing as order is not correct.
I am finding the archive logs based on FIRST_TIME# and preparing the order which is not correct. I think i should be using SCN but not sure what should be the criteria.
Could you please let me know on what basis we can find the order of the archive logs which will be asked during the recovery ?
Your quick response is appreciated. Thanks in advance for your help.
Thanks
Suneel

Yes, When we execute recover database using backup controlfile until cancel, will prompt for the redo log sequences.
But as i mentioned before, I am trying script everything and cannot manually enter the sequence numbers required. I need to know the archives and thread it is going to ask [ in what order as well ] so that recovery command can be scripted in shell.
Please let me know if there is a away to find the order of archive logs which needs to be applied to recover [ if this is a NON-RAC, we can simply go with the sequence numbers but since it is a RAC, i should know the thread number as well ].
Thanks

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

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.)

How to removed the 300GB old archive logs???

Dear Gurus
Site-A
Our Environment:
Live Production 2-Node RAC Oracle10g r2 10.2.0.4
Data and Archive is stored in Oracle ASM
Operating System: Sun Solaris10 64bit
We have two databases.
==>db-1(Site-A db-1 is Oracle streaming with Site-B db-1,so archive logs should not be deleted which is required for oracle streaming)
==>db-2
Existing Backup and Recovery Strategy:
Daily logical backup of application schema using DATA PUMP.
We have not taken any RMAN Backup still.
Please find the status of Shared Storage.
-bash-3.00$ asmcmd
ASMCMD> lsdg
State Type Rebal Unbal Sector Block AU Total_MB Free_MB Req_mir_free_MB Usable_file_MB Offline_disks Name
MOUNTED EXTERN N N 512 4096 1048576 614256 577801 0 577801 0 DATA/
MOUNTED EXTERN N N 512 4096 1048576 298948 38635 0 38635 0 FLASH/
We want to removed the old archive logs?
Please suggest the best way of removed the old archive logs for db-2 and db-1?
Can you Please suggest that how many time and how many space it's required for completed the backup?
Regards
Hitesh Gondalia
Edited by: hitgon on Oct 1, 2011 9:50 PM
Edited by: hitgon on Oct 1, 2011 10:09 PM
Edited by: hitgon on Oct 1, 2011 10:13 PM

You should consider using RMAN for backup/recovery. Logical exports (Data Pump) are useful for some purposes, but are not the preferred way to go for your backup and recovery needs. RMAN will give you better performance and so much more options.
Long-term, a great way to delete archivelog backups is via RMAN “backup archivelog …. delete input” and/or “delete archivelog … “commands.
Please delete archivelogs only after they are already backed up. RMAN will also take into consideration if the backups are needed for Streams and/or Standby.
About the backup space – a full RMAN backup is typically smaller than the size of your DB. You need to run a test to see the exact size. The frequency and type of backup should be based on your SLE for this DB.
Iordan Iotzov
http://iiotzov.wordpress.com/

How to know the size of archived logs created under ASM

I using Oracle 10g on Linux x86-64.
I need to ship the archived logs(not the entire directory, only a few) from the Live database to the DR site, so I need an estimate of how much time it will take to ship them across the network ?
Is there anyway I can know the size of a specific archived log file stored under ASM ?
We can use du in ASM to know the size of directory but I dont find a command in ASM to get the size of a file ?

No we are also switching logfiles manually , so the maximum size may not
have reached.
What I need is something like ls -l command in the Unix prompt which will
help us to find the size of the file , a similar command to help us determine
a size of file in ASM ?What is the objective?
Anyways, you can get the size of an archived log file by quering V$ARCHIVED_LOG view.
SQL> select sequence#, name, blocks*block_size from v$archived_log where sequence# > 180;
SEQUENCE# NAME                                     BLOCKS*BLOCK_SIZE
       182 C:\MYDB\ARCH\ARC00182_0633314306.001             223053312
       181 C:\MYDB\ARCH\ARC00181_0633314306.001             264281600
       183 C:\MYDB\ARCH\ARC00183_0633314306.001              26209280
       184 C:\MYDB\ARCH\ARC00184_0633314306.001                  4096
       185 C:\MYDB\ARCH\ARC00185_0633314306.001                 16384
SQL>

Change the location of Archive Logs on standby Server

Can somebody tell me the process how to change the archive logs location for the standby by server. e.g. Its going now to location C:\stby\archives and I want to send it to E:\stby\archives
Thx

Hi,
Change the STANDBY SPFILE/PFILE Value of <b>standby_archive_dest=E:\stby\archives</b>
see this
http://download.oracle.com/docs/cd/B10501_01/server.920/a96653/init_params.htm#84366
HTH
Regards!

How to view the List of statements executed in Oracle 11G database

Hi ,
I have this Application which internally updates and writes to the tables in my database. Is there a way that i can make oracle 11g to log all the statements that are executed in it so that ill be able to see the statements?. Plz explain me how to do this ?
Thanks
Kiran

User Auditing on those tables.
http://www.oracle.com/technology/deploy/security/database-security/database-auditing/index.html
http://www.oracle-base.com/articles/10g/Auditing_10gR2.php
Regards
Rajesh

Duplexing the Archive Log - is there a potential performance hit

Good Afternoon Oracle People -
I apologize if this question is silly or out of place.
Basically, we are looking at options for implementing a (cheap) DR solution for our Oracle Database.
Bottom line objective is to have a second copy of our production system (not running, offline) with a usable archive log to recover from at a remote site with a similar set of disk technologies etc.
The sites are linked by 100MBPs link - so any access to secondary site is relatively fast.
What I was thinking of doing is creating an iSCSI target on the destination SAN and adding this as a disk into the production database. Then, I was going to go in and define a duplex archive log destination to this iSCSI target.
My fear is that if the archiver waits for the write to the destination, I would imagine that this would slow down database access. Is this a valid concern? Or does Oracle treat the Duplex as a replicated (slower) copy?
Again, sorry if this question is stupid - i have tried the google machine but couldn't find anything, and it isn't all that clear from the documentation.
Kind Regards,
Aleksei

Or does Oracle treat the Duplex as a replicated (slower) copy?
Oracle treats it in a way you tell Oracle to treat it – please take a look at LOG_ARCHIVE_DEST_n parameters such as MANDATORY and OPTIONAL, MAX_FAILURE, etc
There are two major things to consider:
->Is the throughput of the destination enough to handle max archive log generation?
You need to take a look at the size of archive logs and how frequently they are
generated during peak load.
->What happens when the destination is not available?
HTH,
Iordan Iotzov

Pecification does not match any archive log in the recovery catalog

MAN> list archivelog all;
pecification does not match any archive log in the recovery catalog
RMAN> list backup of archivelog all
BS Key Size Device Type Elapsed Time Completion Time
671197 5.17M DISK 00:00:03 29-MAY-11
BP Key: 671200 Status: AVAILABLE Compressed: YES Tag: TAG20110529T180030
Piece Name: F:\OSSTDBY_BACKUP\ARCH\OSONDEMA_ARC_20110529_FVMDIGPU_S25087_P1
List of Archived Logs in backup set 671197
Thrd Seq Low SCN Low Time Next SCN Next Time
1 44836 503663671 29-MAY-11 503675934 29-MAY-11
2 22517 503663669 29-MAY-11 503675932 29-MAY-11
BS Key Size Device Type Elapsed Time Completion Time
671232 5.12M DISK 00:00:02 29-MAY-11
BP Key: 671235 Status: AVAILABLE Compressed: YES Tag: TAG20110529T200050
Piece Name: F:\OSSTDBY_BACKUP\ARCH\OSONDEMA_ARC_20110529_G1MDINRJ_S25089_P1
List of Archived Logs in backup set 671232
Thrd Seq Low SCN Low Time Next SCN Next Time
1 44837 503675934 29-MAY-11 503688661 29-MAY-11
2 22518 503675932 29-MAY-11 503688659 29-MAY-11
BS Key Size Device Type Elapsed Time Completion Time
671267 5.14M DISK 00:00:03 29-MAY-11
BP Key: 671270 Status: AVAILABLE Compressed: YES Tag: TAG20110529T220036
Piece Name: F:\OSSTDBY_BACKUP\ARCH\OSONDEMA_ARC_20110529_G3MDIUS4_S25091_P1
List of Archived Logs in backup set 671267
Thrd Seq Low SCN Low Time Next SCN Next Time
1 44838 503688661 29-MAY-11 503701009 29-MAY-11
2 22519 503688659 29-MAY-11 503701007 29-MAY-11
BS Key Size Device Type Elapsed Time Completion Time
671302 16.55M DISK 00:00:05 30-MAY-11
BP Key: 671305 Status: AVAILABLE Compressed: YES Tag: TAG20110530T000048
Piece Name: F:\OSSTDBY_BACKUP\ARCH\OSONDEMA_ARC_20110530_G5MDJ5TG_S25093_P1
List of Archived Logs in backup set 671302
Thrd Seq Low SCN Low Time Next SCN Next Time
1 44839 503701009 29-MAY-11 503716961 30-MAY-11
2 22520 503701007 29-MAY-11 503716959 30-MAY-11
BS Key Size Device Type Elapsed Time Completion Time
671337 5.13M DISK 00:00:02 30-MAY-11
BP Key: 671340 Status: AVAILABLE Compressed: YES Tag: TAG20110530T020121
Piece Name: F:\OSSTDBY_BACKUP\ARCH\OSONDEMA_ARC_20110530_G7MDJCVI_S25095_P1
List of Archived Logs in backup set 671337
Thrd Seq Low SCN Low Time Next SCN Next Time
1 44840 503716961 30-MAY-11 503729544 30-MAY-11
2 22521 503716959 30-MAY-11 503729542 30-MAY-11
BS Key Size Device Type Elapsed Time Completion Time
671372 5.25M DISK 00:00:03 30-MAY-11
BP Key: 671375 Status: AVAILABLE Compressed: YES Tag: TAG20110530T040055
Piece Name: F:\OSSTDBY_BACKUP\ARCH\OSONDEMA_ARC_20110530_G9MDJJVN_S25097_P1
the archives are in the location of
F:\OSSTDBY_BACKUP\ARCH\OSONDEMA_ARC_20110529_G1MDINRJ_S25089_P1
when it is not specified in catalog how can i delete archives from f location i.e
F:\OSSTDBY_BACKUP\ARCH\OSONDEMA_ARC_20110529_G1MDINRJ_S25089_P1
please let me know from rman how can i delete archives from f location...........................
do i need to register with catalog?
i have used Delete archivelog all completed before 'SYSDATE-10';
but no use
out put is
MAN> Delete archivelog all completed before 'SYSDATE-10';
eleased channel: ORA_DISK_1
llocated channel: ORA_DISK_1
hannel ORA_DISK_1: sid=311 devtype=DISK
pecification does not match any archive log in the recovery catalog
MAN> crosscheck backup archivelog all;
please send me the query which i can delete ......................thanks
cheers
mahesh

EdStevens wrote:
856483 wrote:
<snip>
can i have you mobile contact phone number if possible?
I have seen some pretty astonishing requests on this board, but this one really raises (or lowers) the bar. Just what is it your boss is paying you to do?
Some listserves have lots of people giving their number. I find it odd that people would, but not astonishing for someone to ask. Outside the norm here, but how would someone know ahead of time? It's a bravely connected new world.

ARCHIVE LOGS CREATED in WRONG FOLDER

Hello,
I'm facing an issue with the Archive logs.
In my Db the parameters for Archive logs are
log_archive_dest_1 string LOCATION=/u03/archive/SIEB MANDATORY REOPEN=30
db_create_file_dest string /u01/oradata/SIEB/dbf
db_create_online_log_dest_1 string /u01/oradata/SIEB/rdo
But the archive logs are created in
/u01/app/oracle/product/9.2.0.6/dbs
Listed Below :
bash-2.05$ ls -lrt *.arc
-rw-r----- 1 oracle dba 9424384 Jan 9 09:30 SIEB_302843.arc
-rw-r----- 1 oracle dba 7678464 Jan 9 10:00 SIEB_302844.arc
-rw-r----- 1 oracle dba 1536 Jan 9 10:00 SIEB_302845.arc
-rw-r----- 1 oracle dba 20480 Jan 9 10:00 SIEB_302846.arc
-rw-r----- 1 oracle dba 10010624 Jan 9 10:30 SIEB_302847.arc
-rw-r----- 1 oracle dba 104858112 Jan 9 10:58 SIEB_302848.arc
bash-2.05$
Does anyone have an Idea why this happens?
Is this a Bug!!!
Thxs

But in another Db I've
log_archive_dest string
log_archive_dest_1 string LOCATION=/u03/archive/SIEB MANDATORY REOPEN=30
and my archivelogs are in
oracle@srvsdbs7p01:/u03/archive/SIEB/ [SIEB] ls -lrt /u03/archive/SIEB
total 297696
-rw-r----- 1 oracle dba 10010624 Jan 9 10:30 SIEB_302847.arc
-rw-r----- 1 oracle dba 21573632 Jan 9 11:00 SIEB_302848.arc
-rw-r----- 1 oracle dba 101450240 Jan 9 11:30 SIEB_302849.arc
-rw-r----- 1 oracle dba 6308864 Jan 9 12:00 SIEB_302850.arc
-rw-r----- 1 oracle dba 12936704 Jan 9 12:30 SIEB_302851.arc
oracle@srvsdbs7p01:/u03/archive/SIEB/ [SIEB]

Tidying the list of archive logs in Oracle

Similar Messages

Maybe you are looking for