有人知道吗,以下是alert文件的部分内容
Using parameter settings in server-side spfile D:\APP\ADMINISTRATOR\PRODUCT\11.1.0\DB_1\DATABASE\SPFILESJZ.ORA
System parameters with non-default values:
processes
= 150
memory_target
= 820M
control_files
= "D:\APP\ADMINISTRATOR\ORADATA\SJZ\CONTROL01.CTL"
db_block_size
= 8192
compatible
= "11.1.0.0.0"
db_recovery_file_dest= "D:\app\Administrator\flash_recovery_area"
db_recovery_file_dest_size= 2G
_allow_resetlogs_corruption= TRUE
undo_tablespace
= "UNDOTBS1"
remote_login_passwordfile= "EXCLUSIVE"
db_domain
= ""
dispatchers
= "(PROTOCOL=TCP) (SERVICE=SJZXDB)"
audit_file_dest
= "D:\APP\ADMINISTRATOR\ADMIN\SJZ\ADUMP"
audit_trail
= "DB"
db_name
= "SJZ"
open_cursors
= 300
diagnostic_dest
= "D:\APP\ADMINISTRATOR"
Thu Feb 02 14:24:22 2012
PMON started with pid=2, OS id=8004
Thu Feb 02 14:24:22 2012
VKTM started with pid=3, OS id=8008 at elevated priority
VKTM running at (20)ms precision
Thu Feb 02 14:24:22 2012
DIAG started with pid=4, OS id=8012
Thu Feb 02 14:24:22 2012
DBRM started with pid=5, OS id=8016
Thu Feb 02 14:24:22 2012
PSP0 started with pid=6, OS id=8020
Thu Feb 02 14:24:22 2012
DSKM started with pid=7, OS id=8024
Thu Feb 02 14:24:22 2012
DIA0 started with pid=8, OS id=8028
Thu Feb 02 14:24:22 2012
MMAN started with pid=7, OS id=8032
Thu Feb 02 14:24:22 2012
DBW0 started with pid=9, OS id=8036
Thu Feb 02 14:24:22 2012
DBW1 started with pid=10, OS id=8040
Thu Feb 02 14:24:22 2012
DBW2 started with pid=11, OS id=8044
Thu Feb 02 14:24:22 2012
DBW3 started with pid=12, OS id=8048
Thu Feb 02 14:24:22 2012
LGWR started with pid=13, OS id=8052
Thu Feb 02 14:24:22 2012
CKPT started with pid=14, OS id=8056
Thu Feb 02 14:24:22 2012
SMON started with pid=15, OS id=8060
Thu Feb 02 14:24:22 2012
RECO started with pid=16, OS id=8064
Thu Feb 02 14:24:22 2012
MMON started with pid=17, OS id=8068
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
Thu Feb 02 14:24:22 2012
MMNL started with pid=18, OS id=8072
starting up 1 shared server(s) ...
ORACLE_BASE from environment = D:\app\Administrator
Thu Feb 02 14:24:22 2012
ALTER DATABASEsjz MOUNT
Setting recovery target incarnation to 2
Successful mount of redo thread 1, with mount id 2975656729
Database mounted in Exclusive Mode
Lost write protection disabled
Completed: ALTER DATABASEsjz MOUNT
Thu Feb 02 14:24:29 2012
ALTER DATABASE OPEN
Beginning crash recovery of 1 threads
parallel recovery started with 16 processes
Started redo scan
Completed redo scan
1 redo blocks read, 0 data blocks need recovery
Started redo application at
Thread 1: logseq 4, block 2, scn 6963035
Recovery of Online Redo Log: Thread 1 Group 1 Seq 4 Reading mem 0
Mem# 0: D:\APP\ADMINISTRATOR\ORADATA\SJZ\REDO01.LOG
Completed redo application
Completed crash recovery at
Thread 1: logseq 4, block 3, scn 6983037
0 data blocks read, 0 data blocks written, 1 redo blocks read
Thread 1 advanced to log sequence 5
Thread 1 opened at log sequence 5
Current log# 2 seq# 5 mem# 0: D:\APP\ADMINISTRATOR\ORADATA\SJZ\REDO02.LOG
Successful open of redo thread 1
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
SMON: enabling cache recovery
ORA-01555 caused by SQL statement below (SQL ID: 04xtrk7uyhknh, Query Duration=0 sec, SCN: 0x0000.006a8e06):
select obj#,type#,ctime,mtime,stime,status,dataobj#,flags,oid$, spare1, spare2 from obj$ where owner#=:1 and name=:2 and namespace=:3 and remoteowner is null and linkname is null and subname is null
Errors in file d:\app\administrator\diag\rdbms\sjz\sjz\trace\sjz_ora_8108.trc:
ORA-00704: 引导程序进程失败
ORA-00604: 递归 SQL 级别 2 出现错误
ORA-01555: 快照过旧: 回退段号 10 (名称为 "_SYSSMU10_1192467665$") 过小
Error 704 happened during db open, shutting down database
USER (ospid: 8108): terminating the instance due to error 704
Thu Feb 02 14:24:31 2012
ORA-704 : opidrv aborting process S000 ospid (4716_8080)
Instance terminated by USER, pid = 8108
ORA-1092 signalled during: ALTER DATABASE OPEN...
ORA-1092 : opiodr aborting process unknown ospid (4716_8108)
Thu Feb 02 14:24:33 2012
ORA-1092 : opitsk aborting process
|