In addition to Weibo, there is also WeChat
Please pay attention
WeChat public account
Shulou
2025-04-06 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Database >
Share
Shulou(Shulou.com)06/01 Report--
[phenomenon]
SQL > alter database open resetlogs
Alter database open resetlogs
*
ERROR at line 1:
ORA-00392: log 4 of thread 1 is being cleared, operation not allowed
ORA-00312: online log 4 thread 1:'/ mnt/data/PBF/db/proddata/redo04a.log'
ORA-00312: online log 4 thread 1:'/ mnt/data/PBF/db/proddata/redo04b.log'
[official explanation]
CLEARING_CURRENT-Current log is being cleared of a closed thread. The log can stay in this status if there is some failure in the switch such as an I/O error writing the new log header.
CLEARING-Log is being re-created as an empty log after an ALTER DATABASE CLEAR
[centralized status of redo log files]
1.CURRENT-the group (which is also the ACTIVE status) currently in use by LGWR, which records the changes being made in the database, and deletion will result in data loss during recovery.
2.ACTIVE-the status of the active log file, which may occur when the log completes the switch or waits for the checkpoint event. It is not a CURRENT log but is required for instance recovery. At this time, the log may have been archived and is about to become INACTIVE, or the log file may not be archived while waiting for the Checkpoint event.
3.INACTIVE-inactive log state where the log instance is no longer needed for recovery and may have been archived.
4.UNUSED-A blank log group that has not yet recorded change, usually after add logfile, resetlogs opens the database, or uses the clear logfile command.
5.CLEARING-indicates that the group of redo log files are being rebuilt by ALTER DATABASE CLEAR LOGFILE statements (after reconstruction the state will become unused).
6.CLEARING_CURRENT-indicates that there was an error in redoing log file reconstruction in this group, which is the case when there is an Ibino failure to the log file.
[solution]
SQL > select group#,bytes/1024/1024 | | 'Mitchell status from v$log
GROUP# BYTES/1024/1024 | |'M'
STATUS
1 1000M
CLEARING
2 1000M
CLEARING
5 1000M
CLEARING
GROUP# BYTES/1024/1024 | |'M'
STATUS
4 1000M
CLEARING_CURRENT
3 1000M
CLEARING
SQL >
SQL >
SQL >
SQL > alter database clear logfile group 1
Alter database clear logfile group 2
Alter database clear logfile group 3
Alter database clear logfile group 4
Alter database clear logfile group 5
Database altered.
SQL >
Database altered.
SQL >
Database altered.
SQL >
Database altered.
SQL >
Database altered.
SQL > col group# form 99
SQL > col bytes form 999999999999
SQL > col status form A20
SQL > select group#,bytes/1024/1024 | | 'Mitchell status from v$log
GROUP# BYTES/1024/1024 | |'M' STATUS
1 1000M UNUSED
2 1000M UNUSED
5 1000M UNUSED
4 1000M CURRENT
3 1000M UNUSED
Alter database open resetlogs
OK!
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.