In addition to Weibo, there is also WeChat
Please pay attention
WeChat public account
Shulou
2025-02-23 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Database >
Share
Shulou(Shulou.com)06/01 Report--
You will often encounter the following error message
Welcome to join the ORACLE Super Group: 17115662 solve all kinds of ORACLE problems free of charge. BLOG will migrate to http://www.htz.pw in the future.
ARCH: Error 19809 Creating archivelog file to'/ oracle/app/oracle/fast_recovery_area/ORCL1124/archivelog/2014_06_05/o1_mf_1_113_%u_.arc'
ARC1: Error 19809 Creating archivelog file to'/ oracle/app/oracle/fast_recovery_area/ORCL1124/archivelog/2014_06_05/o1_mf_1_114_%u_.arc'
Errors in file / oracle/app/oracle/diag/rdbms/orcl1124/orcl1124/trace/orcl1124_ora_22611.trc:
ORA-16038: log 2 sequence# 113 cannot be archived
ORA-19809: limit exceeded for recovery files
ORA-00312: online log 2 thread 1:'/ oracle/app/oracle/oradata/orcl1124/redo02.log'
ARCH: Archival stopped, error occurred. Will continue retrying
ORACLE Instance orcl1124-Archival Error
ORA-16038: log 3 sequence# 114 cannot be archived
ORA-19809: limit exceeded for recovery files
ORA-00312: online log 3 thread 1:'/ oracle/app/oracle/oradata/orcl1124/redo03.log'
System state dump requested by (instance=1, osid=22611), summary= [abnormal instance termination].
System State dumped to trace file / oracle/app/oracle/diag/rdbms/orcl1124/orcl1124/trace/orcl1124_diag_22544_20140605180150.trc
Dumping diagnostic data in directory= [CDMP _ 20140605180150], requested by (instance=1, osid=22611), summary= [abnormal instance termination].
USER (ospid: 22611): terminating the instance due to error 16038
Instance terminated by USER, pid = 22611
The reason is simple: the archive directory is full, and there are many solutions.
1. If the archive is stored in the FRA area, you can change the size of a FRA area, as long as there is still space left in the FRA directory.
2. Use a separate archive directory, expand the file system or change the archive path to another place.
3. Let's test another method.
1. Start the database to report an error
[oracle@www.htz.pw oradata] $sqlplus / as sysdba
SQL*Plus: Release 11.2.0.4.0 Production on Thu Jun 5 18:01:30 2014
Copyright (c) 1982, 2013, Oracle. All rights reserved.
Connected to an idle instance.
Www.htz.pw > startup
ORACLE instance started.
Total System Global Area 379965440 bytes
Fixed Size 2253464 bytes
Variable Size 171969896 bytes
Database Buffers 201326592 bytes
Redo Buffers 4415488 bytes
Database mounted.
ORA-03113: end-of-file on communication channel
Process ID: 22611
Session ID: 1 Serial number: 5
The following error is reported in 2pr alert
ORA-19815: WARNING: db_recovery_file_dest_size of 4385144832 bytes is 100.005% used, and 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.
*
ARCH: Error 19809 Creating archivelog file to'/ oracle/app/oracle/fast_recovery_area/ORCL1124/archivelog/2014_06_05/o1_mf_1_113_%u_.arc'
ARC1: Error 19809 Creating archivelog file to'/ oracle/app/oracle/fast_recovery_area/ORCL1124/archivelog/2014_06_05/o1_mf_1_114_%u_.arc'
Errors in file / oracle/app/oracle/diag/rdbms/orcl1124/orcl1124/trace/orcl1124_ora_22611.trc:
ORA-16038: log 2 sequence# 113 cannot be archived
ORA-19809: limit exceeded for recovery files
ORA-00312: online log 2 thread 1:'/ oracle/app/oracle/oradata/orcl1124/redo02.log'
ARCH: Archival stopped, error occurred. Will continue retrying
ORACLE Instance orcl1124-Archival Error
ORA-16038: log 3 sequence# 114 cannot be archived
ORA-19809: limit exceeded for recovery files
ORA-00312: online log 3 thread 1:'/ oracle/app/oracle/oradata/orcl1124/redo03.log'
System state dump requested by (instance=1, osid=22611), summary= [abnormal instance termination].
System State dumped to trace file / oracle/app/oracle/diag/rdbms/orcl1124/orcl1124/trace/orcl1124_diag_22544_20140605180150.trc
Dumping diagnostic data in directory= [CDMP _ 20140605180150], requested by (instance=1, osid=22611), summary= [abnormal instance termination].
USER (ospid: 22611): terminating the instance due to error 16038
Instance terminated by USER, pid = 22611
3. Change the archive library to non-archive and start normally.
What I did added the resetlog approach, which is fine with noresetlogs in the production environment, because we're just changing the archiving mode.
CREATE CONTROLFILE REUSE DATABASE "ORCL1124" RESETLOGS NOARCHIVELOG
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
MAXINSTANCES 8
MAXLOGHISTORY 292
LOGFILE
GROUP 1'/ oracle/app/oracle/oradata/orcl1124/redo01.log' SIZE 50m BLOCKSIZE 512
GROUP 2'/ oracle/app/oracle/oradata/orcl1124/redo02.log' SIZE 50m BLOCKSIZE 512
GROUP 3'/ oracle/app/oracle/oradata/orcl1124/redo03.log' SIZE 50m BLOCKSIZE 512
-- STANDBY LOGFILE
DATAFILE
'/ oracle/app/oracle/oradata/orcl1124/system01.dbf'
'/ oracle/app/oracle/oradata/orcl1124/sysaux01.dbf'
'/ oracle/app/oracle/oradata/orcl1124/undotbs01.dbf'
'/ oracle/app/oracle/oradata/orcl1124/users01.dbf'
'/ oracle/app/oracle/oradata/orcl1124/htz01.dbf'
'/ oracle/app/oracle/oradata/orcl1124/undotbs02.dbf'
CHARACTER SET ZHS16GBK
Www.htz.pw > recover database using backup controlfile until cancel
ORA-00279: change 2795841 generated at 06/05/2014 17:52:39 needed for thread 1
ORA-00289: suggestion:
/ oracle/app/oracle/fast_recovery_area/ORCL1124/archivelog/2014_06_05/o1_mf_1_115
_% u_.arc
ORA-00280: change 2795841 for thread 1 is in sequence # 115
Specify log: {= suggested | filename | AUTO | CANCEL}
/ oracle/app/oracle/oradata/orcl1124/redo03.log
ORA-00310: archived log contains sequence 114; sequence 115 required
ORA-00334: archived log:'/ oracle/app/oracle/oradata/orcl1124/redo03.log'
Www.htz.pw > recover database using backup controlfile until cancel
ORA-00279: change 2795841 generated at 06/05/2014 17:52:39 needed for thread 1
ORA-00289: suggestion:
/ oracle/app/oracle/fast_recovery_area/ORCL1124/archivelog/2014_06_05/o1_mf_1_115
_% u_.arc
ORA-00280: change 2795841 for thread 1 is in sequence # 115
Specify log: {= suggested | filename | AUTO | CANCEL}
/ oracle/app/oracle/oradata/orcl1124/redo01.log
Log applied.
Media recovery complete.
Be sure to enter the log path manually here, otherwise you may lose data or encounter other errors.
Www.htz.pw > alter database open resetlogs
Database altered.
Www.htz.pw > archive log list
Database log mode No Archive Mode
Automatic archival Disabled
Archive destination USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence 1
Current log sequence 1
Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.
Views: 0
*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.
Continue with the installation of the previous hadoop.First, install zookooper1. Decompress zookoope
"Every 5-10 years, there's a rare product, a really special, very unusual product that's the most un
© 2024 shulou.com SLNews company. All rights reserved.