ORA-00600: [kcratr_nab_less_than_odr]處理
今天有一個朋友報了一個故障給我,資料庫無法Open,在alert裡面報以下錯誤:
之前意外斷過一次電
Starting up:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options.
Using parameter settings in server-side spfile H:\APP\ADMINISTRATOR\PRODUCT\11.2.0\DBHOME_1\DATABASE\SPFILEONEBYONE.ORA
System parameters with non-default values:
processes = 150
memory_target = 804M
control_files = "H:\APP\ADMINISTRATOR\ORADATA\ONEBYONE\CONTROL01.CTL"
control_files = "H:\APP\ADMINISTRATOR\FLASH_RECOVERY_AREA\ONEBYONE\CONTROL02.CTL"
db_block_size = 8192
compatible = "11.2.0.0.0"
db_recovery_file_dest = "H:\app\Administrator\flash_recovery_area"
db_recovery_file_dest_size= 3912M
undo_tablespace = "UNDOTBS1"
remote_login_passwordfile= "EXCLUSIVE"
db_domain = ""
dispatchers = "(PROTOCOL=TCP) (SERVICE=ONEBYONEXDB)"
job_queue_processes = 0
audit_file_dest = "H:\APP\ADMINISTRATOR\ADMIN\ONEBYONE\ADUMP"
audit_trail = "DB"
db_name = "ONEBYONE"
open_cursors = 300
deferred_segment_creation= FALSE
aq_tm_processes = 0
diagnostic_dest = "H:\APP\ADMINISTRATOR"
Fri Jun 19 13:34:47 2015
PMON started with pid=2, OS id=3192
Fri Jun 19 13:34:47 2015
VKTM started with pid=3, OS id=3196 at elevated priority
VKTM running at (10)millisec precision with DBRM quantum (100)ms
Fri Jun 19 13:34:47 2015
GEN0 started with pid=4, OS id=3200
Fri Jun 19 13:34:47 2015
DIAG started with pid=5, OS id=3204
Fri Jun 19 13:34:47 2015
DBRM started with pid=6, OS id=3208
Fri Jun 19 13:34:47 2015
PSP0 started with pid=7, OS id=3212
Fri Jun 19 13:34:47 2015
DIA0 started with pid=8, OS id=3216
Fri Jun 19 13:34:47 2015
MMAN started with pid=9, OS id=3220
Fri Jun 19 13:34:47 2015
DBW0 started with pid=10, OS id=3224
Fri Jun 19 13:34:47 2015
LGWR started with pid=11, OS id=3228
Fri Jun 19 13:34:47 2015
CKPT started with pid=12, OS id=3232
Fri Jun 19 13:34:47 2015
SMON started with pid=13, OS id=3236
Fri Jun 19 13:34:47 2015
RECO started with pid=14, OS id=3240
Fri Jun 19 13:34:47 2015
MMON started with pid=15, OS id=3244
Fri Jun 19 13:34:47 2015
MMNL started with pid=16, OS id=3248
Fri Jun 19 13:34:47 2015
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
starting up 1 shared server(s) ...
ORACLE_BASE from environment = H:\app\Administrator
Fri Jun 19 13:34:52 2015
alter database mount exclusive
Fri Jun 19 13:34:58 2015
Successful mount of redo thread 1, with mount id 987684157
Database mounted in Exclusive Mode
Lost write protection disabled
Completed: alter database mount exclusive
alter database open
Beginning crash recovery of 1 threads
parallel recovery started with 2 processes
Started redo scan
Completed redo scan
read 7 KB redo, 10 data blocks need recovery
Started redo application at
Thread 1: logseq 162, block 76766
Recovery of Online Redo Log: Thread 1 Group 3 Seq 162 Reading mem 0
Mem# 0: H:\APP\ADMINISTRATOR\ORADATA\ONEBYONE\REDO03.LOG
Completed redo application of 0.00MB
Completed crash recovery at
Thread 1: logseq 162, block 76780, scn 6058453
10 data blocks read, 10 data blocks written, 7 redo k-bytes read
Fri Jun 19 13:37:53 2015
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Using LOG_ARCHIVE_DEST_1 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BR
ILAT =27
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Fri Jun 19 13:38:04 2015
Starting up:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options.
Using parameter settings in server-side spfile H:\APP\ADMINISTRATOR\PRODUCT\11.2.0\DBHOME_1\DATABASE\SPFILEONEBYONE.ORA
System parameters with non-default values:
processes = 150
memory_target = 804M
control_files = "H:\APP\ADMINISTRATOR\ORADATA\ONEBYONE\CONTROL01.CTL"
control_files = "H:\APP\ADMINISTRATOR\FLASH_RECOVERY_AREA\ONEBYONE\CONTROL02.CTL"
db_block_size = 8192
compatible = "11.2.0.0.0"
db_recovery_file_dest = "H:\app\Administrator\flash_recovery_area"
db_recovery_file_dest_size= 3912M
undo_tablespace = "UNDOTBS1"
remote_login_passwordfile= "EXCLUSIVE"
db_domain = ""
dispatchers = "(PROTOCOL=TCP) (SERVICE=ONEBYONEXDB)"
job_queue_processes = 0
audit_file_dest = "H:\APP\ADMINISTRATOR\ADMIN\ONEBYONE\ADUMP"
audit_trail = "DB"
db_name = "ONEBYONE"
open_cursors = 300
deferred_segment_creation= FALSE
aq_tm_processes = 0
diagnostic_dest = "H:\APP\ADMINISTRATOR"
Fri Jun 19 13:38:06 2015
PMON started with pid=2, OS id=3188
Fri Jun 19 13:38:06 2015
VKTM started with pid=3, OS id=3192 at elevated priority
VKTM running at (10)millisec precision with DBRM quantum (100)ms
Fri Jun 19 13:38:06 2015
GEN0 started with pid=4, OS id=3196
Fri Jun 19 13:38:06 2015
DIAG started with pid=5, OS id=3200
Fri Jun 19 13:38:06 2015
DBRM started with pid=6, OS id=3204
Fri Jun 19 13:38:06 2015
PSP0 started with pid=7, OS id=3208
Fri Jun 19 13:38:06 2015
DIA0 started with pid=8, OS id=3212
Fri Jun 19 13:38:06 2015
MMAN started with pid=9, OS id=3216
Fri Jun 19 13:38:06 2015
DBW0 started with pid=10, OS id=3220
Fri Jun 19 13:38:06 2015
LGWR started with pid=11, OS id=3224
Fri Jun 19 13:38:06 2015
CKPT started with pid=12, OS id=3228
Fri Jun 19 13:38:06 2015
SMON started with pid=13, OS id=3232
Fri Jun 19 13:38:06 2015
RECO started with pid=14, OS id=3236
Fri Jun 19 13:38:06 2015
MMON started with pid=15, OS id=3240
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
Fri Jun 19 13:38:06 2015
MMNL started with pid=16, OS id=3244
starting up 1 shared server(s) ...
ORACLE_BASE from environment = H:\app\Administrator
Fri Jun 19 13:38:10 2015
alter database mount exclusive
Successful mount of redo thread 1, with mount id 987671554
Database mounted in Exclusive Mode
Lost write protection disabled
Completed: alter database mount exclusive
alter database open
Beginning crash recovery of 1 threads
parallel recovery started with 2 processes
Started redo scan
Completed redo scan
read 0 KB redo, 0 data blocks need recovery
Errors in file h:\app\administrator\diag\rdbms\onebyone\onebyone\trace\onebyone_ora_3260.trc (incident=42153):
ORA-00600: ??????, ??: [kcratr_nab_less_than_odr], [1], [163], [3], [75], [], [], [], [], [], [], []
Incident details in: h:\app\administrator\diag\rdbms\onebyone\onebyone\incident\incdir_42153\onebyone_ora_3260_i42153.trc
Aborting crash recovery due to error 600
Errors in file h:\app\administrator\diag\rdbms\onebyone\onebyone\trace\onebyone_ora_3260.trc:
ORA-00600: ??????, ??: [kcratr_nab_less_than_odr], [1], [163], [3], [75], [], [], [], [], [], [], []
Fri Jun 19 13:38:20 2015
Trace dumping is performing id=[cdmp_20150619133820]
Errors in file h:\app\administrator\diag\rdbms\onebyone\onebyone\trace\onebyone_ora_3260.trc:
ORA-00600: ??????, ??: [kcratr_nab_less_than_odr], [1], [163], [3], [75], [], [], [], [], [], [], []
ORA-600 signalled during: alter database open...
Fri Jun 19 13:39:13 2015
Sweep [inc][42153]: completed
Sweep [inc2][42153]: completed
Fri Jun 19 13:52:03 2015
db_recovery_file_dest_size of 3912 MB is 0.00% 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.
Sun Jun 21 07:32:58 2015
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Using LOG_ARCHIVE_DEST_1 parameter default value as USE_DB_RECOVERY_FILE_DEST
Sun Jun 21 07:33:09 2015
Autotune of undo retention is turned on.
IMODE=BR
ILAT =27
LICENSE_MAX_USERS = 0
SYS auditing is disabled
資料庫是非歸檔模式,只能進行重建控制檔案,如果資料量較小,建議做一次完整的冷備
alter database backup controlfile
TO
TRACE
AS 'd:\backupcontrol.ctl';
開啟backupcontrol.ctl檔案:
重建控制檔案
資料庫nomount狀態
STARTUP NOMOUNT
開始重建
CREATE CONTROLFILE REUSE DATABASE "ONEBYONE" NORESETLOGS NOARCHIVELOG
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
MAXINSTANCES 8
MAXLOGHISTORY 292
LOGFILE
GROUP 1 'H:\APP\ADMINISTRATOR\ORADATA\ONEBYONE\REDO01.LOG' SIZE 50M BLOCKSIZE 512,
GROUP 2 'H:\APP\ADMINISTRATOR\ORADATA\ONEBYONE\REDO02.LOG' SIZE 50M BLOCKSIZE 512,
GROUP 3 'H:\APP\ADMINISTRATOR\ORADATA\ONEBYONE\REDO03.LOG' SIZE 50M BLOCKSIZE 512
-- STANDBY LOGFILE
DATAFILE
'H:\APP\ADMINISTRATOR\ORADATA\ONEBYONE\SYSTEM01.DBF',
'H:\APP\ADMINISTRATOR\ORADATA\ONEBYONE\SYSAUX01.DBF',
'H:\APP\ADMINISTRATOR\ORADATA\ONEBYONE\UNDOTBS01.DBF',
'H:\APP\ADMINISTRATOR\ORADATA\ONEBYONE\USERS01.DBF',
'H:\APP\ADMINISTRATOR\ORADATA\ONEBYONE\EXAMPLE01.DBF',
'E:\ORADATA\JTYBSBASE_DATA.ORA',
'E:\ORADATA\JTYBSBASE_IDX.ORA',
'F:\ORADATA\JTYBSBUSI_DATA.ORA',
'F:\ORADATA\JTYBSBUSI_IDX.ORA'
CHARACTER SET ZHS16GBK
;
recover資料庫
RECOVER DATABASE;
開啟資料庫
ALTER DATABASE OPEN;
增加臨時檔案
ALTER TABLESPACE TEMP ADD TEMPFILE 'H:\APP\ADMINISTRATOR\ORADATA\ONEBYONE\TEMP01.DBF' REUSE;
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/24486203/viewspace-1707979/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- ORA-00600 kcratr_nab_less_than_odr ORA-00600 [4194]
- 系統crash掉導致ORA-00600的處理
- 多對一處理 和一對多處理的處理
- JSP 異常處理如何處理?JS
- ORA-00600 [925]
- ORA-00600[KZSRGPW]
- ORA-00600: [qksdsInitSample:2]
- 模板處理
- 平滑處理
- 字串處理字串
- 事件處理事件
- Python錯誤處理和異常處理(二)Python
- APM RUEI processor處理程式hang死處理方法
- Python資料處理(二):處理 Excel 資料PythonExcel
- Python影像處理丨5種影像處理特效Python特效
- webgl 影像處理2---影像畫素處理Web
- 【故障處理】ORA-600:[13013],[5001]故障處理
- Apache Beam,批處理和流式處理的融合!Apache
- ORA-00600: [OSDEP_INTERNAL]
- Python 影像處理 OpenCV (6):影像的閾值處理PythonOpenCV
- Python 影像處理 OpenCV (7):影像平滑(濾波)處理PythonOpenCV
- rust學習十、異常處理(錯誤處理)Rust
- C#基礎之前處理器,異常處理C#
- Python處理JSONPythonJSON
- Java處理emojiJava
- React事件處理React事件
- 影像預處理
- VideoView全屏處理IDEView
- golang處理signalGolang
- TOML 配置處理TOML
- Oracle SQL處理OracleSQL
- linux故障處理Linux
- vue事件處理Vue事件
- python切片處理Python
- iframe高度處理
- Freemarket模板處理
- 前端Cookie處理前端Cookie
- 異常處理
- redis雪崩處理Redis