~ORA-16038: log 2 sequence# 140 cannot be archived~ORA-19809: limit exceede
~ORA-16038: log 2 sequence# 140 cannot be archived~ORA-19809: limit exceeded for recovery files~ORA-00312: online log 2 thread 1: '/u02/oradata/PROD/redo02.log'
but my /u02/oradata/PROD/ is empty, mod is set to 777
What possible happened?
Thanks.
09:37:29 SQL> startup
ORA-32004: obsolete and/or deprecated parameter(s) specified
ORACLE instance started.
see my init.ora, last three line is added by me,
is it obsolete and/or deprecated parameter(s)?
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=838860800
*.undo_management='AUTO'
*.undo_tablespace='UNDOTBS1'
*.user_dump_dest='/u01/app/oracle/admin/PROD/udump'
LOG_ARCHIVE_START=TRUE
LOG_ARCHIVE_DEST=/u02/archive/PROD
LOG_ARCHIVE_FORMAT=arc%s.arc
Similar Messages
-
ORA-16038: log 1 sequence# 1292 cannot be archived ORA-19809: limit exceede
I am getting this error when starting the database 10g
ORA-16038: log 1 sequence# 1292 cannot be archived
ORA-19809: limit exceeded for recovery files
ORA-00312: online log 1 thread 1:
'/usr/lib/oracle/xe/app/oracle/flash_recovery_area/XE/onlinelog/o1_mf_1_45ngtrx0_.log'
Can someone help me, it is very urgent.
ZulqarnainIt is resolved when I tried
ALTER SYSTEM SET DB_RECOVERY_FILE_DEST_SIZE = 15G SCOPE=BOTH -
ORA-16038: log 1 sequence# 607 cannot be archived Error..
hi I Have a Problem to Start my Database.
My Database is Not in Archive Mode..
to know the detail error message is Given..
SQL> alter database open;
alter database open
ERROR at line 1:
ORA-16038: log 1 sequence# 607 cannot be archived
ORA-19809: limit exceeded for recovery files
ORA-00312: online log 1 thread 1:
'C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL\REDO01.LOG'
I cam not recover My Database..
SQL> recover database;
ORA-00283: recovery session canceled due to errors
ORA-00264: no recovery required
I think recovery nolonger needed..
pls any one help me..Hi
ORA-19809: limit exceeded for recovery filesYou have two options now. First is to set the db_recovery_file_dest_size to a bigger size (if you have disk space available ie) and second to use RMAN to delete the archivelogs.
Rgds
Adnan -
ORA 16038 log 1 sequence# 158249 cannot be archived
hi im getting this error on my database when opening
ORA-16038: log 1 sequence# 158249 cannot be archived
ORA-19809: limit exceeded for recovery files
ORA-00312: online log 1 thread 1: '/bill01/app/oracle/oradata/billing/redo01.log
i have tried to free the space but still getting the same error
this are the setting on the init file
*.db_recovery_file_dest='/bill01/oracle/archive/BILLING'
*.db_recovery_file_dest_size=21021851648
on /bill01 ...... i have 131 GB free
any ideaSQL> alter system set db_recovery_file_dest_size=30G;
System altered.
SQL> alter database open;
alter database open
ERROR at line 1:
ORA-16014: log 1 sequence# 158249 not archived, no available destinations
ORA-00312: online log 1 thread 1:
'/bill01/app/oracle/oradata/billing/redo01.log'
======================
*.db_recovery_file_dest='/bill01/oracle/archive/BILLING'
set on init -
Database is not opening due to ORA-16038: log 1 sequence# 16 cannot be arch
Dear All,
I am using oracle database 10g release2 on linux platform............
I am just moving logsegment type object from one tablespace to another tablespace.
But due to low space for redo log file my alter query was hanged on and not completed sucessfully. and the directory is showing full.
then i abort the query by shutdown database by using shutdown immediate command.
After that when i m trying to startup my databse in normal mode i am getting following error....
ERROR at line 1:
ORA-16038: log 1 sequence# 16 cannot be archived
ORA-19502: write error on file "", blockno (blocksize=)
ORA-00312: online log 1 thread 1:
'/var/oracle/oradata/clone/redofiles/REDO_RLOG_01a.dbf'
ORA-00312: online log 1 thread 1:
'/var/oracle/oradata/clone/redofiles/REDO_RLOG_03b.dbf'
so pls suggest me the solution to resolve this problem.Check your Archive log location capacity , used & free.
If archive mount point/FRA is full , then either take backup archive with delete option into another mount point'
or
as part of emergency you can move those archives into different mount point.
Once there is enough free space, bring database back again. Post if any errors again -
Log 1 sequence# 638 cannot be archived
Hello,
I've this error when i start my OAS script and i found nothing about these error.
Could you help me to correct this error please ?
ORA-16038: log 1 sequence# 638 cannot be archived
ORA-19809: limit exceeded for recovery files
ORA-00312: online log 1 thread 1: '/home/oracle/oradata/orcl/redo01.log'
Then, after that:
opmnctl: starting opmn and all managed processes...
and after a long time to wait opmnctl...I obtain that :
opmnctl: starting opmn and all managed processes...
================================================================================
opmn id=rd-srv-oas:6200
1 of 2 processes started.
ias-instance id=infra.rd-srv-oas
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
ias-component/process-type/process-set:
OC4J/OC4J_SECURITY/default_island
Error
--> Process (pid=1522)
time out while waiting for a managed process to start
Log:
/home/oracle/infra/opmn/logs/OC4J~OC4J_SECURITY~default_island~1
TZ set to Europe/Paris
Oracle Enterprise Manager 10g Application Server Control Release 10.1.2.0.0
Copyright (c) 1996, 2004 Oracle Corporation. All rights reserved.
http://rd-srv-oas:1810/emd/console/aboutApplication
Starting Oracle Enterprise Manager 10g Application Server Control ...... started successfully.
opmnctl: starting opmn and all managed processes...
================================================================================
opmn id=rd-srv-oas:6201
3 of 6 processes started.
ias-instance id=portal.rd-srv-oas
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
ias-component/process-type/process-set:
OC4J/home/default_island
Error
--> Process (pid=3334)
time out while waiting for a managed process to start
Log:
/home/oracle/portal/opmn/logs/OC4J~home~default_island~1
ias-component/process-type/process-set:
OC4J/OC4J_Portal/default_island
Error
--> Process (pid=3335)
time out while waiting for a managed process to start
Log:
/home/oracle/portal/opmn/logs/OC4J~OC4J_Portal~default_island~1
ias-component/process-type/process-set:
OC4J/TestWeb/default_island
Error
--> Process (pid=3336)
time out while waiting for a managed process to start
Log:
/home/oracle/portal/opmn/logs/OC4J~TestWeb~default_island~1
TZ set to Europe/Paris
Oracle Enterprise Manager 10g Application Server Control Release 10.1.2.0.0
Copyright (c) 1996, 2004 Oracle Corporation. All rights reserved.
http://rd-srv-oas:1814/emd/console/aboutApplication
Starting Oracle Enterprise Manager 10g Application Server Control ...... started successfully.
Thanks a lot !!!
M.
Message was edited by:
Manu[demo oracle test10]$ oerr ora 19809
19809, 00000, "limit exceeded for recovery files"
//*Cause: The limit for recovery files specified by the
// DB_RECOVERY_FILE_DEST_SIZE was exceeded.
//*Action:The error is accompanied by 19804. See message 19804 for further
// details.
[demo oracle test10]$ oerr ora 19804
19804, 00000, "cannot reclaim %s bytes disk space from %s limit"
// *Cause: Oracle cannot reclaim disk space of specified bytes from the
// DB_RECOVERY_FILE_DEST_SIZE limit.
// *Action: There are five possible solutions:
// 1) Take frequent backup of recovery area using RMAN.
// 2) Consider changing RMAN retention policy.
// 3) Consider changing RMAN archivelog deletion policy.
// 4) Add disk space and increase DB_RECOVERY_FILE_DEST_SIZE.
// 5) Delete files from recovery area using RMAN.
[demo oracle test10]$Your DB is not able to archive a logfile, because of no more space in FLASHBACK area. If you have enough space on disk you can increase the value of DB_RECOVERY_FILE_DEST_SIZE parameter, if not you should take one of other actions above to reduce occupied space in directory identified by DB_RECOVERY_FILE_DEST parameter.
Anyway, you should periodically clean up the flashback area in some way.
Paul -
Please HELP with ORA-19809: limit exceeded for recovery files
Hi Gurus,
I am not a DBA but a developer. Today my Oracle database 11g on my PC will not open and I am getting the errors,
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
I checked my alert logs and found these errors,
Errors in file c:\oracle\diag\rdbms\orcl\orcl\trace\orcl_ora_2144.trc:
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 41072128 bytes disk space from 4039114752 limit
ARCH: Error 19809 Creating archive log file to 'C:\ORACLE\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2011_04_08\O1_MF_1_120_%U_.ARC'
Errors in file c:\oracle\diag\rdbms\orcl\orcl\trace\orcl_ora_2144.trc:
ORA-16038: log 3 sequence# 120 cannot be archived
ORA-19809: limit exceeded for recovery files
ORA-00312: online log 3 thread 1: 'C:\ORACLE\ORADATA\ORCL\REDO03.LOG'
USER (ospid: 2144): terminating the instance due to error 16038
Instance terminated by USER, pid = 2144
So I started searching for answers on this forum and found a suggestion using RMAN to delete all the archive logs,
RMAN> connect target sys/*******
RMAN> delete archivelog all;
RMAN>crosscheck archivelog all;
But I get these errors in RMAN,
using target database control file instead of recovery catalog
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of delete command at 04/08/2011 11:20:58
RMAN-06403: could not obtain a fully authorized session
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
So, please help me: How do I fix this problem since I can't start the instance?
Thank you.
BenYou need to increase the FRA by changing the parameter DB_RECOVERY_FILE_DEST_SIZE. Create a parameter file while being connected as Sys user and issue,
sql>create pfile from spfile;It would create the pfile in the Oracle_Home/database folder. Edit that file and increase the parameter to a larger size-like double of it's current value. Save the file and issue,
sql>startup pfile=<your location of the file>HTH
Aman.... -
ORA-19809: limit exceeded for recovery files and flash_recovery_area
Hi.
I am getting the below errors (at the end) when trying to backup the database using RMAN.
The directory structure is
E:\oracle\TEST
E:\oracle\TEST\flash_recovery_area
E:\oracle\TEST\flash_recovery_area\arch --> HAS ARCHIVE FILES
E:\oracle\TEST\flash_recovery_area\TEST
E:\oracle\ATEST\flash_recovery_area\TEST\BACKUPSET --> RMAN backup sets
E:\oracle\TEST\flash_recovery_area\TEST\ONLINELOG --> This is empty.
D:\oracle\product\10.2.0\ is oracle home
It has:
D:\oracle\product\10.2.0\admin
D:\oracle\product\10.2.0\db1
D:\oracle\product\10.2.0\oradata
D:\oracle\product\10.2.0\oradata\test has data files.
1) I created this database using OUI and DBCA and I have a feeling that this structure is somewhat convoluted. Could you let me know if this needs to be changed?
2) Secondly, the RMAN error. The entire size of E:\oracle\TEST\flash_recovery_area is now only 1.74 GB yet I am getting this error.
I deleted old archive logs from E:\oracle\TEST\flash_recovery_area\arch . Currently it has only arch logs for seven days. Next I issued delete expired archivelog all command. Right now crosscheck archivelog all finds only 40 archive logs..
and increased db_recovery_file_dest_size to 10GB. alter system set db_recovery_file_dest_size=10000M scope=both;
select name
, floor(space_limit / 1024 / 1024) "Size MB"
, ceil(space_used / 1024 / 1024) "Used MB"
from v$recovery_file_dest
order by name
This query is returning the use space as 6GB. However physically only 1.74 GB is currenly used. Please let me know the way forward. Appreciate in advance.
channel ORA_DISK_1: starting piece 1 at 09-JUN-09
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 06/09/2009 17:56:
15
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 52428800 bytes disk space from 10485760000 limit
continuing other job steps, job failed will not be re-run
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
including current control file in backupset
including current SPFILE in backupset
channel ORA_DISK_1: starting piece 1 at 09-JUN-09
channel ORA_DISK_1: finished piece 1 at 09-JUN-09
piece handle=E:\ORACLE\TEST\FLASH_RECOVERY_AREA\TEST\BACKUPSET\2009_06_09\
O1_MF_NCSNF_TAG20090609T175224_52XPN0Y9_.BKP tag=TAG20090609T175224 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:02
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 06/09/2009 17:56:
15
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 52428800 bytes disk space from 10485760000 limit
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 06/09/2009 17:54:
19
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 52428800 bytes disk space from 10485760000 limit
RMAN>Hi,
Thanks for looking into my problem... Here are the answers..
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination E:\oracle\TEST\flash_recovery_area\arch
Oldest online log sequence 1011
Next log sequence to archive 1013
Current log sequence 1013
SQL>
select * from v$flash_recovery_area_usage;
FILE_TYPE PERCENT_SPACE_USED PERCENT_SPACE_RECLAIMABLE NUMBER_OF_FILES
CONTROLFILE 0.00 0.00 0
ONLINELOG 0.00 0.00 0
ARCHIVELOG 0.00 0.00 0
BACKUPPIECE 66.57 0.20 5
IMAGECOPY 0.00 0.00 0
FLASHBACKLOG 0.00 0.00 0
SQL> show parameter log_archive_dest
NAME TYPE VALUE
log_archive_dest string
log_archive_dest_1 string LOCATION=E:\oracle\TEST\flash_recovery_area\arch
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
log_archive_dest_8 string
NAME TYPE VALUE
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
log_archive_dest_state_9 string enable
SQL> -
Oracle Not Starting : error ORA-19809
Hello All,
I was trying to start the 11gr2 database and getting the following error. Please can any one give some advise ? I manually deleted all archive logs using OS command but still i get the
same error when i try to start the database.
ORA-19815: WARNING: db_recovery_file_dest_size of 4039114752 bytes is 100.00% used, a nd has 0 remaining bytes available.
You have following choices to free up space from recovery area:
1. Consider changing RMAN RETENTION POLICY. If you are using Data Guard,
then consider changing RMAN ARCHIVELOG DELETION POLICY.
2. Back up files to tertiary device such as tape using RMAN
BACKUP RECOVERY AREA command.
3. Add disk space and increase db_recovery_file_dest_size parameter to
reflect the new space.
4. Delete unnecessary files using RMAN DELETE command. If an operating
system command was used to delete files, then use RMAN CROSSCHECK and
DELETE EXPIRED commands.
Errors in file /u01/app/oracle/diag/rdbms/orcl/DB11G/trace/DB11G_ora_2921.trc:
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 50629632 bytes disk space from 4039114752 limit
ARCH: Error 19809 Creating archive log file to '/u01/app/oracle/flash_recovery_area/O RCL/archivelog/2012_02_18/o1_mf_1_95_%u_.arc'
2012-02-18 15:58:55.099000 -05:00
ARC3: Archival started
ARC0: STARTING ARCH PROCESSES COMPLETE
ARCH: Archival stopped, error occurred. Will continue retrying
ORACLE Instance DB11G - Archival Error
ORA-16038: log 3 sequence# 96 cannot be archived
ORA-19809: limit exceeded for recovery files
ORA-00312: online log 3 thread 1: '/u01/app/oracle/oradata/ORCL/onlinelog/o1_mf_3_7kp sygwt_.log'
ORA-00312: online log 3 thread 1: '/u01/app/oracle/flash_recovery_area/ORCL/onlinelog /o1_mf_3_7kpsyj6n_.log'
Errors in file /u01/app/oracle/diag/rdbms/orcl/DB11G/trace/DB11G_arc2_2927.trc:
ORA-16038: log 3 sequence# 96 cannot be archived
ORA-19809: limit exceeded for recovery files
ORA-00312: online log 3 thread 1: '/u01/app/oracle/oradata/ORCL/onlinelog/o1_mf_3_7kp sygwt_.log'
ORA-00312: online log 3 thread 1: '/u01/app/oracle/flash_recovery_area/ORCL/onlinelog /o1_mf_3_7kpsyj6n_.log'
Errors in file /u01/app/oracle/diag/rdbms/orcl/DB11G/trace/DB11G_ora_2921.trc:
ORA-16038: log 2 sequence# 95 cannot be archived
ORA-19809: limit exceeded for recovery files
ORA-00312: online log 2 thread 1: '/u01/app/oracle/oradata/ORCL/onlinelog/o1_mf_2_7kp sydnm_.log'
ORA-00312: online log 2 thread 1: '/u01/app/oracle/flash_recovery_area/ORCL/onlinelog /o1_mf_2_7kpsyfp7_.log'
USER (ospid: 2921): terminating the instance due to error 16038
2012-02-18 15:58:56.976000 -05:00
Instance terminated by USER, pid = 2921Rama Krishna wrote:
I think database need to be started before you do any thing with RMAN my problem is database not even starting!You told SB that you had done "option 4":
4. Delete unnecessary files using RMAN DELETE command. If an operating
system command was used to delete files, then use RMAN CROSSCHECK and
DELETE EXPIRED commands.
Oh well. So you " *think* database need to be started before you do any thing with RMAN"
Did you try?
We don't need the database to be open for this, just have the control file mounted:
SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
[oracle@vmlnxsrv01 ~]$ rman target /
Recovery Manager: Release 11.2.0.1.0 - Production on Sat Feb 18 16:21:25 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database (not started)
RMAN> startup mount;
Oracle instance started
database mounted
Total System Global Area 849530880 bytes
Fixed Size 1339824 bytes
Variable Size 578817616 bytes
Database Buffers 264241152 bytes
Redo Buffers 5132288 bytes
RMAN> crosscheck archivelog all;
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=18 device type=DISK
validation succeeded for archived log
archived log file name=/orafra/ORCL/archivelog/2012_01_15/o1_mf_1_66_7k6t71k9_.arc RECID=3 STAMP=772653704
<snip>
archived log file name=/orafra/ORCL/archivelog/2012_02_18/o1_mf_1_80_7n06cfq0_.arc RECID=17 STAMP=775582480
Crosschecked 15 objects
RMAN> exit
Recovery Manager complete.
[oracle@vmlnxsrv01 ~]$ exit
logoutEdited by: EdStevens on Feb 18, 2012 4:32 PM -
Error , ORA-19809 & ORA-19804 While restoring RMAN backup .
Hi Experts,
I am restoring production RMAN backup to UAT . Using below steps
1)rman target=/
2)RMAN> startup nomount;
3) RMAN> restore controlfile from '/orabkdump/Rman_Bak/ACME/bkup_CTLFL_2206101206.ctl';
Starting restore at 05-AUG-10
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=3 device type=DISK
channel ORA_DISK_1: copied control file copy
output file name=+DATA_ACME/acme/controlfile/current.256.724845209
output file name=+DATA_ACME/acme/controlfile/current.257.724845209
Finished restore at 05-AUG-10
4) RMAN> alter database mount;
database mounted
released channel: ORA_DISK_1
5) RMAN> CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/orabkdump/Rman_Bak/ACME/%F';
old RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/orabkdump/Rman_Bak/ACME1/current/%F';
new RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/orabkdump/Rman_Bak/ACME/%F';
new RMAN configuration parameters are successfully stored
6) RMAN> CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/orabkdump/Rman_Bak/ACME/%U';
old RMAN configuration parameters:
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/orabkdump/Rman_Bak/ACME/%U';
new RMAN configuration parameters:
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/orabkdump/Rman_Bak/ACME/%U';
new RMAN configuration parameters are successfully stored
released channel: ORA_DISK_1
7) RMAN> CATALOG START WITH '/orabkdump/Rman_Bak/ACME';
searching for all files that match the pattern /orabkdump/Rman_Bak/ACME
List of Files Unknown to the Database
=====================================
File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722347594_1_1
File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722347939_2_1
File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722348365_3_1
File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722348681_4_1
File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722349076_5_1
File Name: /orabkdump/Rman_Bak/ACME/bkup_CTLFL_2206101206.ctl
File Name: /orabkdump/Rman_Bak/ACME/c-1904932673-20100622-00
File Name: /orabkdump/Rman_Bak/ACME/dbsnap.log
File Name: /orabkdump/Rman_Bak/ACME/rman_Tuesday_LVL_0.log
File Name: /orabkdump/Rman_Bak/ACME/rman_Tuesday_LVL_0.trc
Do you really want to catalog the above files (enter YES or NO)? YES
cataloging files...
cataloging done
List of Cataloged Files
=======================
File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722347594_1_1
File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722347939_2_1
File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722348365_3_1
File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722348681_4_1
File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722349076_5_1
File Name: /orabkdump/Rman_Bak/ACME/bkup_CTLFL_2206101206.ctl
File Name: /orabkdump/Rman_Bak/ACME/c-1904932673-20100622-00
List of Files Which Where Not Cataloged
=======================================
File Name: /orabkdump/Rman_Bak/ACME/dbsnap.log
RMAN-07517: Reason: The file header is corrupted
File Name: /orabkdump/Rman_Bak/ACME/rman_Tuesday_LVL_0.log
RMAN-07517: Reason: The file header is corrupted
File Name: /orabkdump/Rman_Bak/ACME/rman_Tuesday_LVL_0.trc
RMAN-07517: Reason: The file header is corrupted
8) RMAN> run {
2> set until sequence 1789 thread 2;
3> restore database;
4> recover database;
5> sql 'alter database open resetlogs';
6> }
executing command: SET until clause
Starting restore at 06-AUG-10
using channel ORA_DISK_1
Finished restore at 06-AUG-10
Starting recover at 06-AUG-10
using channel ORA_DISK_1
starting media recovery
channel ORA_DISK_1: starting archived log restore to default destination
channel ORA_DISK_1: restoring archived log
archived log thread=1 sequence=2803
channel ORA_DISK_1: restoring archived log
archived log thread=2 sequence=6051
channel ORA_DISK_1: restoring archived log
archived log thread=1 sequence=2804
channel ORA_DISK_1: reading from backup piece /orabkdump/Rman_Bak/ACME/ACME_AL_726286927_57_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 08/06/2010 23:10:38
ORA-19870: error while restoring backup piece /orabkdump/Rman_Bak/ACME/ACME_AL_726286927_57_1
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 49283072 bytes disk space from 5218762752 limit
** My UAT database should be in noarchival mode . Generally such errors have been observed during backup , but have no clue why they occurred during recovery .Please advice .
Thanks
Edited by: user11981514 on Aug 6, 2010 9:46 AMHi,
Since the error ORA-19809 indicates the lack of space in flash recovery area during the media recovery, I suggested increasing the value of the parameter DB_RECOVERY_FILE_DEST_SIZE.
Yes, during the media recovery the RMAN will restore the archived log to the default destination (only if the required archived logs are not already on the disks).You can confirm the restore location of the archived log in RMAN restore log/destination specified by parameters log_archive_dest_1/db_recovery_file_dest.
Regards,
Vaibhav -
Physical Standby with ORA-19809 and ORA-19804
My 10.2.0.3 physical standby produced the below errors, although it remained up. I am wondering if I ran into Bug 6432837, except “select FLASHBACK_ON from V$DATABASE” returns “NO”. I was able to increase the size of DB_RECOVERY_FILE_DEST_SIZE to get around it. However, I fear I have only prolonged the problem, since I have not a viable work around. I’m using the Grid Control to administer both Primary and Standby. It doesn’t seem to allow me to back up the standby, nor do I know how to crosscheck archive logs.
Ideas? Suggestions?
You have following choices to free up space from flash recovery area:
1. Consider changing RMAN RETENTION POLICY. If you are using Data Guard,
then consider changing RMAN ARCHIVELOG DELETION POLICY.
2. Back up files to tertiary device such as tape using RMAN
BACKUP RECOVERY AREA command.
3. Add disk space and increase db_recovery_file_dest_size parameter to
reflect the new space.
4. Delete unnecessary files using RMAN DELETE command. If an operating
system command was used to delete files, then use RMAN CROSSCHECK and
DELETE EXPIRED commands.
****Creating archive destination file : /u06/archive/PROD/PROD1/archivelog/2008_12_05/o1_mf_1_110223_1_.arc (10244 blocks)
Fri Dec 5 17:49:04 2008
Errors in file /u01/app/oracle/product/10.2.0/admin/PROD/udump/prod_rfs_21541.trc:
ORA-00270: error creating archive log /u06/archive/PROD/PROD1/archivelog/2008_12_05/o1_mf_1_110223_%u_.arc
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 5244928 bytes disk space from 40531656704 limit
Fri Dec 5 17:49:04 2008
Errors in file /u01/app/oracle/product/10.2.0/admin/PROD/udump/prod_rfs_21541.trc:
ORA-00270: error creating archive log /u06/archive/PROD/PROD1/archivelog/2008_12_05/o1_mf_1_110223_%u_.arc
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 5244928 bytes disk space from 40531656704 limit
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[253|http://forums.oracle.com/forums/]: Assigned to RFS process 21543
RFS[253|http://forums.oracle.com/forums/]: Identified database type as 'physical standby'
Fri Dec 5 17:49:07 2008
Errors in file /u01/appORA-19815: WARNING: db_recovery_file_dest_size of 40531656704 bytes is 99.99% used, and has 5241344 remaining bytes available.
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 100 0 7340
BACKUPPIECE 0 0 0
IMAGECOPY 0 0 0
FLASHBACKLOG 0 0 0
6 rows selected.
SQL> select * from v$recovery_file_dest;
NAME
SPACE_LIMIT SPACE_USED SPACE_RECLAIMABLE NUMBER_OF_FILES
/u06/archive/PROD
4.0532E+10 4.0531E+10 5241344 7340ARCHIVELOG 100 0 7340Your FRA on the standby side is full - with archivelogs. Archivelogs transferred to the standby are not removed automatically,yourself have to take care of this. As soon as the archives are applied to the standby you can delete them (assuming you do appropriate backups on the primary side). Nevertheless you may take an additional backup on the standby:
backup archivelog all delete all input;
delete obsolete noprompt;
If retention policy is set to redundancy 1 (the default), a backup of the archivelogs is made,the backed up archivelogs are deleted and then the previous backup of older archivelogs is also deleted.
So you should no longer run out of space.
Werner -
ORA-00308: cannot open archived log, ORA-27041
hi All,
here I am making DR server and I copied SAP Data file1,2,3,4 from PRD to DR server and created control file. when I try to run following command for applied archives which i copy from PRD then getting below error.
SQL>Startup
Database mounted.
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
SQL> recover database using backup controlfile;
ORA-00279: change 1209554452 generated at 02/09/2012 17:02:57 needed for thre
1
ORA-00289: suggestion : F:\ORACLE\PRD\ORAARCH\PRDARCH1_59501_657865393.DBF
ORA-00280: change 1209554452 for thread 1 is in sequence #59501
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
auto
ORA-00308: cannot open archived log
'F:\ORACLE\PRD\ORAARCH\PRDARCH1_59501_657865393.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
ORA-00308: cannot open archived log
'F:\ORACLE\PRD\ORAARCH\PRDARCH1_59501_657865393.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
here required PRDARCH1_59501_657865393.DBF while PRD server have PRDARCHARC59501_0657865393.001
I did change the LOG_ARCHIVE_DEST parameter in initSID.ora of DR server and not in PRD.
please tell that, how can i apply PRD's archive (.001 extension) on DR.
Regards,hi all,
after recommendation , now parameter values on DR server is :
*.log_archive_dest_1='LOCATION=F:\oracle\PRD\oraarch\PRDarch'
*.log_archive_format='%t_%s_%r.001'
when i try to apply
SQL> recover database using backup controlfile;
ORA-00279: change 1211443555 generated at 02/10/2012 23:36:05 needed for thread
1
ORA-00289: suggestion : F:\ORACLE\PRD\ORAARCH\PRDARCH\1_59557_657865393.001
ORA-00280: change 1211443555 for thread 1 is in sequence #59557
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
auto
ORA-00308: cannot open archived log
'F:\ORACLE\PRD\ORAARCH\PRDARCH\1_59557_657865393.001'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
if you see that the required archive is: 1_59557_657865393.001
while copied archive exist with this name: PRDARCHARC59557_0657865393.001
I tried to change in Format parameter to make required format but
Exp:
%t_%s_%r.001
1_59557_657865393.001
ARC%s%r%t.001
ARC595576578653931.001'
ARC%s_%r%t.001
ARC59557_6578653931.001
ARC%s_%r.%t
ARC59557_657865393.1
PRDARCHARC%s_%r.%t
PRDARCHARC59557_657865393.1
Required Format: PRDARCHARC59540_0657865393.001
how can i resolve this different name issue? please suggest me required format.
Regards, -
ORA-00308: cannot open archived log '+DATA'
Hello all,
I created new physical standby but I facing problem with shipping archived file between primary and standby.
Primary : RAC (4 nodes)
Standby : single node with ASM
when I run :
alter database recover managed standby database disconnect from session;
in alert log file :
Managed Standby Recovery not using Real Time Apply
Parallel Media Recovery started with 24 slaves
Waiting for all non-current ORLs to be archived...
All non-current ORLs have been archived.
Media Recovery Waiting for thread 1 sequence 25738
Tue Mar 03 12:21:13 2015
Completed: alter database recover managed standby database disconnect from session
and when i checked archived files by
select max(sequence#) from v$archivanded_log;
It was null.
I understand thatno shipping between primary and standby till this point i deiced to use manual recovery by :
alter database recover automatic standby database;
But i get this error in alert log file :
alter database recover automatic standby database
Media Recovery Start
started logmerger process
Tue Mar 03 12:38:38 2015
Managed Standby Recovery not using Real Time Apply
Parallel Media Recovery started with 24 slaves
Media Recovery Log +DATA
Errors with log +DATA
Errors in file /u01/app/oracle/diag/rdbms/oracledrs/oracledrs/trace/oracledrs_pr00_4989.trc:
ORA-00308: cannot open archived log '+DATA'
ORA-17503: ksfdopn:2 Failed to open file +DATA
ORA-15045: ASM file name '+DATA' is not in reference form
ORA-279 signalled during: alter database recover automatic standby database..
when i opened oracledrs_pr00_4989.trc: file i find :
*** 2015-03-03 12:38:39.478
Media Recovery add redo thread 4
ORA-00308: cannot open archived log '+DATA'
ORA-17503: ksfdopn:2 Failed to open file +DATA
ORA-15045: ASM file name '+DATA' is not in reference form
When I created i set these parameter in duplicate command:
set db_file_name_convert='+ASM_ORADATA/oracle','+DATA/oracledrs'
set log_file_name_convert='+ASM_ARCHIVE/oracle','+DATA/oracledrs','+ASM_ORADATA/oracle','+DATA/oracledrs'
set control_files='+DATA'
set db_create_file_dest='+DATA'
set db_recovery_file_dest='+DATA'
What please the mistake here
Thanks in advance,Yes I have datafiles under +DATA
ASMCMD> cd +DATA/ORACLEDRS/DATAFILE
ASMCMD> ls
ASD.282.873258045
CATALOG.288.873258217
DEVTS.283.873258091
EXAMPLE.281.873258043
FEED.260.873227069
FEED.279.873257713
INDX.272.873251345
INDX.273.873252239
INDX.278.873257337
SYSAUX.262.873227071
SYSTEM.277.873256531
SYSTEM_2.280.873257849
TB_WEBSITE.284.873258135
TB_WEBSITE.285.873258135
TB_WEBSITE.286.873258181
TB_WEBSITE.287.873258183
UNDOTBS1.275.873253421
UNDOTBS2.276.873255247
UNDOTBS3.261.873227069
UNDOTBS4.271.873245967
USERS.263.873227071
USERS.264.873235507
USERS.265.873235893
USERS.266.873237079
USERS.267.873238225
USERS.268.873243661
USERS.269.873244307
USERS.270.873244931
USERS.274.873252585
asd01.dbf
catalog01
dev01.dbf
example.dbf
feed01.dbf
feed02.dbf
indx01.dbf
indx02.dbf
indx03.dbf
sysaux01.dbf
system01.dbf
system02.dbf
undotbs01.dbf
undotbs02.dbf
undotbs03.dbf
undotbs04.dbf
user1.dbf
users01.dbf
users02.dbf
users03.dbf
users04.dbf
users05.dbf
users06.dbf
users07.dbf
users08.dbf
website01.dbf
website02.dbf
website03.dbf
website04.dbf
ASMCMD>
Standby :
[root@oracledrs ~]# id oracle
uid=54321(oracle) gid=54321(oinstall) groups=54321(oinstall),54322(dba)
Primary :
[root@dbn-prod-1 disks]# id oracle
uid=54321(oracle) gid=54321(oinstall) groups=54321(oinstall),54322(dba)
1- yes i have needed archived files at my primary
2- select inst_id,thread#,group# from gv$log;
Primary :
INST_ID,THREAD#,GROUP#
1,1,1
1,1,2
1,2,3
1,2,4
1,3,5
1,3,6
1,4,7
1,4,8
1,1,9
1,2,10
1,3,11
1,4,12
3,1,1
3,1,2
3,2,3
3,2,4
3,3,5
3,3,6
3,4,7
3,4,8
3,1,9
3,2,10
3,3,11
3,4,12
2,1,1
2,1,2
2,2,3
2,2,4
2,3,5
2,3,6
2,4,7
2,4,8
2,1,9
2,2,10
2,3,11
2,4,12
4,1,1
4,1,2
4,2,3
4,2,4
4,3,5
4,3,6
4,4,7
4,4,8
4,1,9
4,2,10
4,3,11
4,4,12
Standby :
INST_ID,THREAD#,GROUP#
1,1,9
1,1,2
1,1,1
1,2,3
1,2,4
1,2,10
1,3,5
1,3,6
1,3,11
1,4,12
1,4,7
1,4,8
3- That's sample from alert log since i started the standby (for standby and primary)
Standby :
alter database mount standby database
NOTE: Loaded library: /opt/oracle/extapi/64/asm/orcl/1/libasm.so
NOTE: Loaded library: System
SUCCESS: diskgroup DATA was mounted
ERROR: failed to establish dependency between database oracledrs and diskgroup resource ora.DATA.dg
ARCH: STARTING ARCH PROCESSES
Tue Mar 03 18:38:16 2015
ARC0 started with pid=128, OS id=4461
ARC0: Archival started
ARCH: STARTING ARCH PROCESSES COMPLETE
ARC0: STARTING ARCH PROCESSES
Tue Mar 03 18:38:17 2015
Successful mount of redo thread 1, with mount id 1746490068
Physical Standby Database mounted.
Lost write protection disabled
Tue Mar 03 18:38:17 2015
ARC1 started with pid=129, OS id=4464
Tue Mar 03 18:38:17 2015
ARC2 started with pid=130, OS id=4466
Tue Mar 03 18:38:17 2015
ARC3 started with pid=131, OS id=4468
Tue Mar 03 18:38:17 2015
ARC4 started with pid=132, OS id=4470
Tue Mar 03 18:38:17 2015
ARC5 started with pid=133, OS id=4472
Tue Mar 03 18:38:17 2015
ARC6 started with pid=134, OS id=4474
Tue Mar 03 18:38:17 2015
ARC7 started with pid=135, OS id=4476
Completed: alter database mount standby database
Tue Mar 03 18:38:17 2015
ARC8 started with pid=136, OS id=4478
Tue Mar 03 18:38:17 2015
ARC9 started with pid=137, OS id=4480
ARC1: Archival started
ARC2: Archival started
ARC3: Archival started
ARC4: Archival started
ARC5: Archival started
ARC6: Archival started
ARC7: Archival started
ARC8: Archival started
ARC8: Becoming the 'no FAL' ARCH
ARC2: Becoming the heartbeat ARCH
ARC2: Becoming the active heartbeat ARCH
Tue Mar 03 18:38:18 2015
Starting Data Guard Broker (DMON)
ARC9: Archival started
ARC0: STARTING ARCH PROCESSES COMPLETE
Tue Mar 03 18:38:23 2015
INSV started with pid=141, OS id=4494
Tue Mar 03 18:39:11 2015
alter database recover managed standby database disconnect from session
Attempt to start background Managed Standby Recovery process (oracledrs)
Tue Mar 03 18:39:11 2015
MRP0 started with pid=142, OS id=4498
MRP0: Background Managed Standby Recovery process started (oracledrs)
started logmerger process
Tue Mar 03 18:39:16 2015
Managed Standby Recovery not using Real Time Apply
Parallel Media Recovery started with 24 slaves
Waiting for all non-current ORLs to be archived...
All non-current ORLs have been archived.
Media Recovery Waiting for thread 1 sequence 25738
Completed: alter database recover managed standby database disconnect from session
Tue Mar 03 18:41:17 2015
WARN: ARCH: Terminating pid 4476 hung on an I/O operation
Killing 1 processes with pids 4476 (Process by index) in order to remove hung processes. Requested by OS process 4224
ARCH: Detected ARCH process failure
Tue Mar 03 18:45:17 2015
ARC2: STARTING ARCH PROCESSES
Tue Mar 03 18:45:17 2015
ARC7 started with pid=127, OS id=4586
Tue Mar 03 18:45:18 2015
Fatal NI connect error 12170.
VERSION INFORMATION:
TNS for Linux: Version 11.2.0.4.0 - Production
Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.4.0 - Production
TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.4.0 - Production
Time: 03-MAR-2015 18:45:18
Tracing not turned on.
Tns error struct:
ns main err code: 12535
TNS-12535: TNS:operation timed out
ns secondary err code: 12560
nt main err code: 505
TNS-00505: Operation timed out
nt secondary err code: 0
nt OS err code: 0
Client address: <unknown>
ARC7: Archival started
ARC2: STARTING ARCH PROCESSES COMPLETE
Tue Mar 03 18:47:14 2015
alter database recover managed standby database cancel
Tue Mar 03 18:48:18 2015
Fatal NI connect error 12170.
VERSION INFORMATION:
TNS for Linux: Version 11.2.0.4.0 - Production
Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.4.0 - Production
TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.4.0 - Production
Time: 03-MAR-2015 18:48:18
Tracing not turned on.
Tns error struct:
ns main err code: 12535
TNS-12535: TNS:operation timed out
ns secondary err code: 12560
nt main err code: 505
TNS-00505: Operation timed out
nt secondary err code: 0
nt OS err code: 0
Client address: <unknown>
Tue Mar 03 18:51:18 2015
Fatal NI connect error 12170.
VERSION INFORMATION:
TNS for Linux: Version 11.2.0.4.0 - Production
Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.4.0 - Production
TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.4.0 - Production
Time: 03-MAR-2015 18:51:18
Tracing not turned on.
Tns error struct:
ns main err code: 12535
TNS-12535: TNS:operation timed out
ns secondary err code: 12560
nt main err code: 505
TNS-00505: Operation timed out
nt secondary err code: 0
nt OS err code: 0
Client address: <unknown>
Error 12170 received logging on to the standby
FAL[client, USER]: Error 12170 connecting to oracle for fetching gap sequence
MRP0: Background Media Recovery cancelled with status 16037
Errors in file /u01/app/oracle/diag/rdbms/oracledrs/oracledrs/trace/oracledrs_pr00_4500.trc:
ORA-16037: user requested cancel of managed recovery operation
Recovery interrupted!
Tue Mar 03 18:51:18 2015
MRP0: Background Media Recovery process shutdown (oracledrs)
Tue Mar 03 18:51:19 2015
Managed Standby Recovery Canceled (oracledrs)
Completed: alter database recover managed standby database cancel
Tue Mar 03 18:51:56 2015
alter database recover automatic standby database
Media Recovery Start
started logmerger process
Tue Mar 03 18:51:56 2015
Managed Standby Recovery not using Real Time Apply
Parallel Media Recovery started with 24 slaves
Media Recovery Log +DATA
Errors with log +DATA
Errors in file /u01/app/oracle/diag/rdbms/oracledrs/oracledrs/trace/oracledrs_pr00_4617.trc:
ORA-00308: cannot open archived log '+DATA'
ORA-17503: ksfdopn:2 Failed to open file +DATA
ORA-15045: ASM file name '+DATA' is not in reference form
ORA-279 signalled during: alter database recover automatic standby database...
Tue Mar 03 18:53:06 2015
db_recovery_file_dest_size of 512000 MB is 0.13% 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.
Primary :
Tue Mar 03 17:13:43 2015
Thread 1 advanced to log sequence 26005 (LGWR switch)
Current log# 1 seq# 26005 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_1.271.849356883
Tue Mar 03 17:13:44 2015
Archived Log entry 87387 added for thread 1 sequence 26004 ID 0x66aa5a0d dest 1:
Tue Mar 03 18:00:18 2015
Thread 1 advanced to log sequence 26006 (LGWR switch)
Current log# 2 seq# 26006 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_2.270.849356883
Tue Mar 03 18:00:18 2015
Archived Log entry 87392 added for thread 1 sequence 26005 ID 0x66aa5a0d dest 1:
Tue Mar 03 18:55:33 2015
Thread 1 advanced to log sequence 26007 (LGWR switch)
Current log# 9 seq# 26007 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_9.295.853755983
Current log# 9 seq# 26007 mem# 1: +ASM_ARCHIVE/oracle/onlinelog/group_9.10902.853755985
Tue Mar 03 18:55:33 2015
Archived Log entry 87395 added for thread 1 sequence 26006 ID 0x66aa5a0d dest 1:
Tue Mar 03 19:14:22 2015
Dumping diagnostic data in directory=[cdmp_20150303191422], requested by (instance=4, osid=10234), summary=[incident=1692472].
Dumping diagnostic data in directory=[cdmp_20150303191425], requested by (instance=4, osid=10234), summary=[incident=1692473].
Tue Mar 03 20:00:06 2015
Thread 1 advanced to log sequence 26008 (LGWR switch)
Current log# 1 seq# 26008 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_1.271.849356883
Tue Mar 03 20:00:07 2015
Archived Log entry 87401 added for thread 1 sequence 26007 ID 0x66aa5a0d dest 1:
Tue Mar 03 21:00:02 2015
Thread 1 advanced to log sequence 26009 (LGWR switch)
Current log# 2 seq# 26009 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_2.270.849356883
Tue Mar 03 21:00:03 2015
Archived Log entry 87403 added for thread 1 sequence 26008 ID 0x66aa5a0d dest 1:
Thread 1 advanced to log sequence 26010 (LGWR switch)
Current log# 9 seq# 26010 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_9.295.853755983
Current log# 9 seq# 26010 mem# 1: +ASM_ARCHIVE/oracle/onlinelog/group_9.10902.853755985
Tue Mar 03 21:00:06 2015
Archived Log entry 87404 added for thread 1 sequence 26009 ID 0x66aa5a0d dest 1:
Tue Mar 03 22:00:00 2015
Setting Resource Manager plan SCHEDULER[0x32DA]:DEFAULT_MAINTENANCE_PLAN via scheduler window
Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter
Tue Mar 03 22:00:00 2015
Starting background process VKRM
Tue Mar 03 22:00:00 2015
VKRM started with pid=184, OS id=4838
Tue Mar 03 22:00:07 2015
Begin automatic SQL Tuning Advisor run for special tuning task "SYS_AUTO_SQL_TUNING_TASK"
Tue Mar 03 22:00:25 2015
Thread 1 advanced to log sequence 26011 (LGWR switch)
Current log# 1 seq# 26011 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_1.271.849356883
Tue Mar 03 22:00:26 2015
Archived Log entry 87408 added for thread 1 sequence 26010 ID 0x66aa5a0d dest 1:
Tue Mar 03 22:00:58 2015
Thread 1 advanced to log sequence 26012 (LGWR switch)
Current log# 2 seq# 26012 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_2.270.849356883
Tue Mar 03 22:01:00 2015
Archived Log entry 87412 added for thread 1 sequence 26011 ID 0x66aa5a0d dest 1:
Tue Mar 03 22:02:37 2015
Thread 1 cannot allocate new log, sequence 26013
Checkpoint not complete
Current log# 2 seq# 26012 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_2.270.849356883
Thread 1 advanced to log sequence 26013 (LGWR switch)
Current log# 9 seq# 26013 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_9.295.853755983
Current log# 9 seq# 26013 mem# 1: +ASM_ARCHIVE/oracle/onlinelog/group_9.10902.853755985
Tue Mar 03 22:02:41 2015
Archived Log entry 87415 added for thread 1 sequence 26012 ID 0x66aa5a0d dest 1:
Tue Mar 03 22:03:26 2015
Thread 1 cannot allocate new log, sequence 26014
Checkpoint not complete
Current log# 9 seq# 26013 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_9.295.853755983
Current log# 9 seq# 26013 mem# 1: +ASM_ARCHIVE/oracle/onlinelog/group_9.10902.853755985
Thread 1 advanced to log sequence 26014 (LGWR switch)
Current log# 1 seq# 26014 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_1.271.849356883
Tue Mar 03 22:03:29 2015
Archived Log entry 87416 added for thread 1 sequence 26013 ID 0x66aa5a0d dest 1:
Tue Mar 03 22:05:50 2015
Thread 1 cannot allocate new log, sequence 26015
Checkpoint not complete
Current log# 1 seq# 26014 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_1.271.849356883
Tue Mar 03 22:05:52 2015
End automatic SQL Tuning Advisor run for special tuning task "SYS_AUTO_SQL_TUNING_TASK"
Thread 1 advanced to log sequence 26015 (LGWR switch)
Current log# 2 seq# 26015 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_2.270.849356883
Tue Mar 03 22:05:54 2015
Archived Log entry 87418 added for thread 1 sequence 26014 ID 0x66aa5a0d dest 1:
Tue Mar 03 22:07:29 2015
Thread 1 cannot allocate new log, sequence 26016
Checkpoint not complete
Current log# 2 seq# 26015 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_2.270.849356883
Thread 1 advanced to log sequence 26016 (LGWR switch)
Current log# 9 seq# 26016 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_9.295.853755983
Current log# 9 seq# 26016 mem# 1: +ASM_ARCHIVE/oracle/onlinelog/group_9.10902.853755985
Tue Mar 03 22:07:33 2015
Archived Log entry 87421 added for thread 1 sequence 26015 ID 0x66aa5a0d dest 1:
Thread 1 cannot allocate new log, sequence 26017
Checkpoint not complete
Current log# 9 seq# 26016 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_9.295.853755983
Current log# 9 seq# 26016 mem# 1: +ASM_ARCHIVE/oracle/onlinelog/group_9.10902.853755985
Thread 1 advanced to log sequence 26017 (LGWR switch)
Current log# 1 seq# 26017 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_1.271.849356883
Tue Mar 03 22:07:39 2015
Archived Log entry 87422 added for thread 1 sequence 26016 ID 0x66aa5a0d dest 1:
Tue Mar 03 22:16:36 2015
Thread 1 advanced to log sequence 26018 (LGWR switch)
Current log# 2 seq# 26018 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_2.270.849356883
Tue Mar 03 22:16:37 2015
Archived Log entry 87424 added for thread 1 sequence 26017 ID 0x66aa5a0d dest 1:
Tue Mar 03 22:30:06 2015
Thread 1 advanced to log sequence 26019 (LGWR switch)
Current log# 9 seq# 26019 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_9.295.853755983
Current log# 9 seq# 26019 mem# 1: +ASM_ARCHIVE/oracle/onlinelog/group_9.10902.853755985
Tue Mar 03 22:30:07 2015
Archived Log entry 87427 added for thread 1 sequence 26018 ID 0x66aa5a0d dest 1:
Tue Mar 03 22:30:18 2015
Thread 1 advanced to log sequence 26020 (LGWR switch)
Current log# 1 seq# 26020 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_1.271.849356883
Tue Mar 03 22:30:19 2015
Archived Log entry 87428 added for thread 1 sequence 26019 ID 0x66aa5a0d dest 1:
Tue Mar 03 23:07:27 2015
Dumping diagnostic data in directory=[cdmp_20150303230727], requested by (instance=4, osid=25140), summary=[incident=1692496].
Dumping diagnostic data in directory=[cdmp_20150303230730], requested by (instance=4, osid=25140), summary=[incident=1692497].
Thanks in advance sir , -
ORA-16014: log 2 sequence# 283 not archived, no available destinations
When trying to start my database my alert log is showing
ORA-16014: log 2 sequence# 283 not archived, no available destinations
ORA-00312: online log 2 thread 1: '/home/app/oracle/oradata/PRIMARYP/redo02.log'
I can mount the instance ok but not actually open the database
my db_recovery_file_dest_size is 22 Gb and and the mount point defined by db_recovery_file_dest has pleanty of free space
Also
select *
from v$recovery_file_dest;
shows plenty of free FRA space -
NAME
SPACE_LIMIT SPACE_USED SPACE_RECLAIMABLE NUMBER_OF_FILES
/home/app/oracle/fast_recovery_area
2.3622E+10 5506131968 3297617408 159
select error
from v$archive_dest;
shows no errors
Can anyone help !
thanks, Jimok here's the wierd thing. When I set up the primary, physical standby and logical standby, I set the following Log Archive Destinations on my primary database ( into the SPFILE )
ALTER SYSTEM SET log_archive_dest_1='LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ONLINE_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=PRIMARYP' SCOPE=BOTH;
ALTER SYSTEM SET log_archive_dest_2='SERVICE=STANDBYP ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=STANDBYP' SCOPE=BOTH;
ALTER SYSTEM SET log_archive_dest_3='SERVICE=STANDBYL ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=STANDBYL'
SCOPE=BOTH;
ALTER SYSTEM SET log_archive_dest_4='LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(STANDBY_LOGFILES,STANDBY_ROLE) DB_UNIQUE_NAME=PRIMARYP' SCOPE=BOTH;
Then I converted to using DGMGRL instead od SqlPlus to manage my Data Guard Environment. I then did a switchover to my Physical Standby and then a switchbach to my primary. Today when I check the log_archive_dests on my primary, they are completely different from how I set them up originally !
*.log_archive_dest_1='service="STANDBYL"','LGWR ASYNC NOAFFIRM delay=0 optional compression=disable max_failure=0 max_connections=1 reopen=300 db_unique_name="STANDBYL" net_timeout=30','valid_for=(all_logfiles,primary_role)'
*.log_archive_dest_2='service="STANDBYP"','LGWR ASYNC NOAFFIRM delay=0 optional compression=disable max_failure=0 max_connections=1 reopen=300 db_unique_name="STANDBYP" net_timeout=30','valid_for=(all_logfiles,primary_role)'
*.log_archive_dest_3=''
*.log_archive_dest_4='LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(STANDBY_LOGFILES,STANDBY_ROLE) DB_UNIQUE_NAME=PRIMARYP'
As you can see there is no setting place for the standard archive logs for PRIMARYP !
When I set log_archive_dest_3 to
'LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(STANDBY_LOGFILES,STANDBY_ROLE) DB_UNIQUE_NAME=PRIMARYP' SCOPE=BOTH;
Then I am able to open the PRIMARYP database again.
Q. what cause the entire resetting of the 4 log_archive_dest_n settings ? I am presuming it is something the broker has done ( presumably on the switchover or switch back ) ? However it seems to have completely mucked itself up, not even provising a standard archive log destination for PRIMARYP and in the process causing the instance not to be able to start
Has anyone ever seen this before ?
Also now I am getting ORA-16783: cannot resolve gap for database STANDBYP, STANDBYL
In my Broker Config for the PRIMARYP database. I am worried because during the investigation of this problem I issues the following on PRIMARYP
alter database clear unarchived logfile group 1;
Have I created a Gap which I cannot resolve ?
thanks,
Jim -
ORA-16014: log 1 sequence# 40845 not archived, no available destinations
Hi,
My RMAN archive script gives the following error. I'm not sure why - there is still about 16 GB diskspace and an archivelog is not more than 50 MB. Does anyone know what could be the cause of this error? Thanks.
Recovery Manager: Release 8.1.7.4.1 - Production
RMAN-06005: connected to target database: PROD (DBID=1412471481)
RMAN-06009: using target database controlfile instead of recovery catalog
RMAN> sql 'alter system archive log current';
2> change archivelog all validate;
3> run{
4> allocate channel c1 type DISK;
5> allocate channel c2 type DISK;
6> backup filesperset 10
7> format 'C:\backup\rman\PROD\%d_ARCHIVES_%u_%s.bak'
8> archivelog all delete input;
9> release channel c1;
10> release channel c2;
11> }
12>
RMAN-03022: compiling command: sql
RMAN-06162: sql statement: alter system archive log current
RMAN-03023: executing command: sql
RMAN-03026: error recovery releasing channel resources
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03006: non-retryable error occurred during execution of command: sql
RMAN-07004: unhandled exception during command execution on channel default
RMAN-20000: abnormal termination of job step
RMAN-11003: failure during parse/execution of SQL statement: alter system archive log current
RMAN-11001: Oracle Error: ORA-16014: log 1 sequence# 40845 not archived, no available destinations
ORA-00312: online log 1 thread 1: 'C:\ORACLE\ORADATA\PROD\REDO01.LOG'
Recovery Manager complete.NAME TYPE VALUE
log_archive_dest string
log_archive_dest_1 string LOCATION=/ora MANDATORY R
EOPEN=300
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
log_archive_dest_8 string
NAME TYPE VALUE
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
log_archive_dest_state_9 string enable
Maybe you are looking for
-
Choosefromlist with Form in FIND_MODE
Hi all, - I've a user table @TBL with two fields: Code and Name - I've created in my .NET application a SAP FORM with a button a two EditText: on bind with Code, the other with Name - I've put my form in FIND_MODE When I click on button "Find" I have
-
Different Between KT4V ver1.0 and KT4V v10A
Hi guys, when i just bought a new MSI KT4V from a shop, it was version 1.0, but 3 month later i send for warrantty claim, they return the board to me (I think they replace the board, but i dun think it was a new board, it was a used board), but it w
-
Enterprise services for create employee
hi all, I need to know if there are any Enterprise Services to create an Employee? thanks!
-
Hi, I would like to learn more about the queue directory structure for a given channel. For example, why do we have 20 directories named 000 to 019; when are they created and what is the condition for a given message to be inserted in this or that di
-
Hi Everyone I have installed EP 2004s over Windows 2003 Server and SQL Server 2005, when I try to access to the Room directory or to any room after create it I'm getting the next error message: java.lang.NoSuchMethodError: com.sap.ip.collaboration.ro