錯誤日志如下：
1.alert_ora11.log
Mon Apr 23 15:25:04 2018
Adjusting the default value of parameter parallel_max_servers
from 1280 to 120 due to the value of parameter processes (150)
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Initial number of CPU is 32
Number of processor cores in the system is 16
Number of processor sockets in the system is 2
Picked latch-free SCN scheme 3
Mon Apr 23 15:25:23 2018
Using LOG_ARCHIVE_DEST_1 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned off.
LICENSE_MAX_USERS = 0
SYS auditing is disabled
NUMA system with 2 nodes detected
Starting up:
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options.
Windows NT Version V6.2
CPU : 32 - type 8664, 16 Physical Cores
Process Affinity : 0x0x0000000000000000
Memory (Avail/Total): Ph:178047M/261741M, Ph+PgF:215729M/300653M
Using parameter settings in server-side spfile D:\APP\PRODUCT\11.2.0\DBHOME_1\DATABASE\SPFILEORA11.ORA
System parameters with non-default values:
processes = 150
sga_target = 78592M
control_files = "D:\APP\ORADATA\ORA11\CONTROL01.CTL"
control_files = "D:\APP\FAST_RECOVERY_AREA\ORA11\CONTROL02.CTL"
db_block_size = 8192
compatible = "11.2.0.4.0"
db_files = 600
db_recovery_file_dest = "D:\app\fast_recovery_area"
db_recovery_file_dest_size= 400G
undo_management = "MANUAL"
undo_tablespace = "UNDOTBS1"
remote_login_passwordfile= "EXCLUSIVE"
db_domain = "unicom.db2"
dispatchers = "(PROTOCOL=TCP) (SERVICE=ora11XDB)"
audit_file_dest = "D:\APP\ADMIN\ORA11\ADUMP"
audit_trail = "DB"
db_name = "ora11"
open_cursors = 300
pga_aggregate_target = 26174M
diagnostic_dest = "D:\APP"
Mon Apr 23 15:25:34 2018
PMON started with pid=2, OS id=4924
Mon Apr 23 15:25:34 2018
PSP0 started with pid=3, OS id=2512
Mon Apr 23 15:25:35 2018
VKTM started with pid=4, OS id=4640 at elevated priority
VKTM running at (10)millisec precision with DBRM quantum (100)ms
Mon Apr 23 15:25:35 2018
GEN0 started with pid=5, OS id=4820
Mon Apr 23 15:25:35 2018
DIAG started with pid=6, OS id=2792
Mon Apr 23 15:25:35 2018
DBRM started with pid=7, OS id=4732
Mon Apr 23 15:25:35 2018
DIA0 started with pid=8, OS id=1564
Mon Apr 23 15:25:35 2018
MMAN started with pid=9, OS id=1688
Mon Apr 23 15:25:35 2018
DBW0 started with pid=10, OS id=4528
Mon Apr 23 15:25:35 2018
DBW1 started with pid=11, OS id=4480
Mon Apr 23 15:25:35 2018
DBW2 started with pid=12, OS id=3588
Mon Apr 23 15:25:35 2018
DBW3 started with pid=13, OS id=624
Mon Apr 23 15:25:35 2018
LGWR started with pid=14, OS id=2208
Mon Apr 23 15:25:35 2018
CKPT started with pid=15, OS id=3608
Mon Apr 23 15:25:35 2018
SMON started with pid=16, OS id=3376
Mon Apr 23 15:25:35 2018
RECO started with pid=17, OS id=4544
Mon Apr 23 15:25:35 2018
MMON started with pid=18, OS id=4288
Mon Apr 23 15:25:35 2018
MMNL started with pid=19, OS id=4740
Mon Apr 23 15:25:35 2018
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
starting up 1 shared server(s) ...
ORACLE_BASE from environment = D:\app
Mon Apr 23 15:25:35 2018
ALTER DATABASE MOUNT
Successful mount of redo thread 1, with mount id 918190256
Database mounted in Exclusive Mode
Lost write protection disabled
Completed: ALTER DATABASE MOUNT
Mon Apr 23 15:25:40 2018
ALTER DATABASE OPEN
Beginning crash recovery of 1 threads
parallel recovery started with 31 processes
Started redo scan
Completed redo scan
read 0 KB redo, 0 data blocks need recovery
Started redo application at
Thread 1: logseq 17, block 3, scn 5833380769
Recovery of Online Redo Log: Thread 1 Group 2 Seq 17 Reading mem 0
Mem# 0: D:\APP\ORADATA\ORA11\REDO02.LOG
Completed redo application of 0.00MB
Completed crash recovery at
Thread 1: logseq 17, block 3, scn 5833400770
0 data blocks read, 0 data blocks written, 0 redo k-bytes read
Mon Apr 23 15:25:48 2018
LGWR: STARTING ARCH PROCESSES
Mon Apr 23 15:25:48 2018
ARC0 started with pid=54, OS id=4336
ARC0: Archival started
LGWR: STARTING ARCH PROCESSES COMPLETE
ARC0: STARTING ARCH PROCESSES
Mon Apr 23 15:25:49 2018
ARC1 started with pid=55, OS id=3684
Mon Apr 23 15:25:49 2018
ARC2 started with pid=56, OS id=4956
Mon Apr 23 15:25:49 2018
ARC3 started with pid=57, OS id=3356
ARC1: Archival started
ARC2: Archival started
ARC1: Becoming the 'no FAL' ARCH
ARC1: Becoming the 'no SRL' ARCH
ARC2: Becoming the heartbeat ARCH
Thread 1 advanced to log sequence 18 (thread open)
ARC3: Archival started
ARC0: STARTING ARCH PROCESSES COMPLETE
Thread 1 opened at log sequence 18
Current log# 3 seq# 18 mem# 0: D:\APP\ORADATA\ORA11\REDO03.LOG
Successful open of redo thread 1
Mon Apr 23 15:25:51 2018
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Mon Apr 23 15:25:51 2018
SMON: enabling cache recovery
Errors in file D:\APP\diag\rdbms\ora11\ora11\trace\ora11_ora_5104.trc (incident=82985):
ORA-00600: 內部錯誤代碼, 引數: [16703], [1403], [20], [], [], [], [], [], [], [], [], []
Incident details in: D:\APP\diag\rdbms\ora11\ora11\incident\incdir_82985\ora11_ora_5104_i82985.trc
Archived Log entry 289791 added for thread 1 sequence 17 ID 0x36b80a19 dest 1:
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Errors in file D:\APP\diag\rdbms\ora11\ora11\trace\ora11_ora_5104.trc:
ORA-00704: 引導程式行程失敗
ORA-00704: 引導程式行程失敗
ORA-00600: 內部錯誤代碼, 引數: [16703], [1403], [20], [], [], [], [], [], [], [], [], []
Errors in file D:\APP\diag\rdbms\ora11\ora11\trace\ora11_ora_5104.trc:
ORA-00704: 引導程式行程失敗
ORA-00704: 引導程式行程失敗
ORA-00600: 內部錯誤代碼, 引數: [16703], [1403], [20], [], [], [], [], [], [], [], [], []
Error 704 happened during db open, shutting down database
USER (ospid: 5104): terminating the instance due to error 704
Mon Apr 23 15:26:02 2018
Instance terminated by USER, pid = 5104
ORA-1092 signalled during: ALTER DATABASE OPEN...
opiodr aborting process unknown ospid (5104) as a result of ORA-1092
Mon Apr 23 15:26:11 2018
ORA-1092 : opitsk aborting process
2.ora11_ora_5104.trc
Trace file D:\APP\diag\rdbms\ora11\ora11\trace\ora11_ora_5104.trc
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Windows NT Version V6.2
CPU : 32 - type 8664, 16 Physical Cores
Process Affinity : 0x0x0000000000000000
Memory (Avail/Total): Ph:177945M/261741M, Ph+PgF:215586M/300653M
Instance name: ora11
Redo thread mounted by this instance: 1
Oracle process number: 22
Windows thread id: 5104, image: ORACLE.EXE (SHAD)
*** 2018-04-23 15:25:47.636
*** SESSION ID:(177.3) 2018-04-23 15:25:47.636
*** CLIENT ID:() 2018-04-23 15:25:47.636
*** SERVICE NAME:() 2018-04-23 15:25:47.636
*** MODULE NAME:(sqlplus.exe) 2018-04-23 15:25:47.636
*** ACTION NAME:() 2018-04-23 15:25:47.636
Successfully allocated 31 recovery slaves
Using 6 overflow buffers per recovery slave
*** 2018-04-23 15:25:47.776
Thread 1 checkpoint: logseq 17, block 2, scn 5833380767
on-disk rba: logseq 17, block 3, scn 5833380769
start recovery at logseq 17, block 3, scn 5833380769
*** 2018-04-23 15:25:47.808
Started writing zeroblks thread 1 seq 17 blocks 3-10
*** 2018-04-23 15:25:47.808
Completed writing zeroblks thread 1 seq 17
==== Redo read statistics for thread 1 ====
Total physical reads (from disk and memory): 4096Kb
-- Redo read_disk statistics --
Read rate (ASYNC): 0Kb in 0.02s => 0.00 Mb/sec
----------------------------------------------
----- Recovery Hash Table Statistics ---------
Hash table buckets = 1048576
Longest hash chain = 0
Average hash chain = 0/0 = 0.0
Max compares per lookup = 0
Avg compares per lookup = 0/0 = 0.0
----------------------------------------------
*** 2018-04-23 15:25:47.808
KCRA: start recovery claims for 0 data blocks
*** 2018-04-23 15:25:47.808
KCRA: blocks processed = 0/0, claimed = 0, eliminated = 0
*** 2018-04-23 15:25:47.808
Recovery of Online Redo Log: Thread 1 Group 2 Seq 17 Reading mem 0
*** 2018-04-23 15:25:47.823
Completed redo application of 0.00MB
*** 2018-04-23 15:25:47.823
Completed recovery checkpoint
----- Recovery Hash Table Statistics ---------
Hash table buckets = 1048576
Longest hash chain = 0
Average hash chain = 0/0 = 0.0
Max compares per lookup = 0
Avg compares per lookup = 0/0 = 0.0
----------------------------------------------
Recovery sets nab of thread 1 seq 17 to 3 with 8 zeroblks
*** 2018-04-23 15:25:51.589
Incident 82985 created, dump file: D:\APP\diag\rdbms\ora11\ora11\incident\incdir_82985\ora11_ora_5104_i82985.trc
ORA-00600: 內部錯誤代碼, 引數: [16703], [1403], [20], [], [], [], [], [], [], [], [], []
ORA-00704: 引導程式行程失敗
ORA-00704: 引導程式行程失敗
ORA-00600: 內部錯誤代碼, 引數: [16703], [1403], [20], [], [], [], [], [], [], [], [], []
ORA-00704: 引導程式行程失敗
ORA-00704: 引導程式行程失敗
ORA-00600: 內部錯誤代碼, 引數: [16703], [1403], [20], [], [], [], [], [], [], [], [], []
*** 2018-04-23 15:25:52.323
USER (ospid: 5104): terminating the instance due to error 704
3.ora11_ora_5104_i82985.trc
Dump continued from file: D:\APP\diag\rdbms\ora11\ora11\trace\ora11_ora_5104.trc
ORA-00600: 內部錯誤代碼, 引數: [16703], [1403], [20], [], [], [], [], [], [], [], [], []
========= Dump for incident 82985 (ORA 600 [16703]) ========
*** 2018-04-23 15:25:51.589
dbkedDefDump(): Starting incident default dumps (flags=0x2, level=3, mask=0x0)
----- Current SQL Statement for this session (sql_id=1h50ks4ncswfn) -----
ALTER DATABASE OPEN
----- Call Stack Trace -----
uj5u.com熱心網友回復：
當時重啟了一下資料庫：shutdown immediate；然后再startup；然后就報錯了
小白求大神幫忙，不甚感激。
uj5u.com熱心網友回復：
http://www.xifenfei.com/2017/07/oracle-software-malicious-injection.html這個我們處理過很多用戶了，使用了注入惡意代碼的oracle 軟體
uj5u.com熱心網友回復：
有備份嗎？邏輯的 或者物理的uj5u.com熱心網友回復：
有歸檔日志。uj5u.com熱心網友回復：
邏輯備份可以恢復，如果是物理備份，還是需要特殊處理，不然open的時候，依舊和現在故障一樣的
轉載請註明出處，本文鏈接：https://www.uj5u.com/shujuku/68210.html
標籤：基礎和管理
下一篇：大神們，幫幫忙，這個有點看不懂呀