早上接到测试的电话，测试数据库起不来，报600的错误，...
库是昨天发现起不来，然后他们自己瞎整，重建了控制文件，还有其他一些不知道的动作。目前数据库只能到Mount状态，open时报错600的错误---------------------------------------以下是告警日志的内容----------------------------------------------
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BR
ILAT =18
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.1.0.
System parameters with non-default values:
processes = 150
__shared_pool_size = 520093696
__large_pool_size = 16777216
__java_pool_size = 16777216
__streams_pool_size = 0
spfile = D:\ORACLE\PRODUCT\10.2.0\DB_1\DBS\SPFILEORCL.ORA
sga_target = 2533359616
control_files = E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\CONTROL01.CTL, E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\CONTROL02.CTL, E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\CONTROL03.CTL
db_block_size = 8192
__db_cache_size = 1962934272
compatible = 10.2.0.1.0
db_file_multiblock_read_count= 16
db_recovery_file_dest = d:\oracle\product\10.2.0/flash_recovery_area
db_recovery_file_dest_size= 2147483648
undo_management = AUTO
undo_tablespace = UNDOTBS1
remote_login_passwordfile= EXCLUSIVE
db_domain =
dispatchers = (PROTOCOL=TCP) (SERVICE=ORCLXDB)
job_queue_processes = 10
audit_file_dest = D:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\ADUMP
background_dump_dest = D:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\BDUMP
user_dump_dest = D:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\UDUMP
core_dump_dest = D:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\CDUMP
db_name = ORCL
open_cursors = 300
pga_aggregate_target = 838860800
PMON started with pid=2, OS id=5752
PSP0 started with pid=3, OS id=1492
MMAN started with pid=4, OS id=4828
DBW0 started with pid=5, OS id=5848
LGWR started with pid=6, OS id=5336
CKPT started with pid=7, OS id=5084
SMON started with pid=8, OS id=1992
RECO started with pid=9, OS id=2624
CJQ0 started with pid=10, OS id=4636
MMON started with pid=11, OS id=1876
Tue Dec 04 17:28:35 2012
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
MMNL started with pid=12, OS id=5348
Tue Dec 04 17:28:35 2012
starting up 1 shared server(s) ...
Tue Dec 04 17:28:35 2012
ALTER DATABASE MOUNT
Tue Dec 04 17:28:39 2012
Setting recovery target incarnation to 3
Tue Dec 04 17:28:39 2012
Successful mount of redo thread 1, with mount id 1328944451
Tue Dec 04 17:28:39 2012
Database mounted in Exclusive Mode
Completed: ALTER DATABASE MOUNT
Tue Dec 04 17:28:39 2012
ALTER DATABASE OPEN
Tue Dec 04 17:28:40 2012
Beginning crash recovery of 1 threads
parallel recovery started with 3 processes
Tue Dec 04 17:28:40 2012
Started redo scan
Tue Dec 04 17:28:42 2012
Completed redo scan
57 redo blocks read, 10 data blocks need recovery
Tue Dec 04 17:28:42 2012
Started redo application at
Thread 1: logseq 8, block 3
Tue Dec 04 17:28:43 2012
Recovery of Online Redo Log: Thread 1 Group 1 Seq 8 Reading mem 0
Mem# 0 errs 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\REDO01.LOG
Tue Dec 04 17:28:43 2012
Completed redo application
Tue Dec 04 17:28:43 2012
Completed crash recovery at
Thread 1: logseq 8, block 60, scn 829323347
10 data blocks read, 10 data blocks written, 57 redo blocks read
Tue Dec 04 17:28:43 2012
Thread 1 advanced to log sequence 9
Thread 1 opened at log sequence 9
Current log# 2 seq# 9 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\REDO02.LOG
Successful open of redo thread 1
Tue Dec 04 17:28:43 2012
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Tue Dec 04 17:28:43 2012
SMON: enabling cache recovery
Tue Dec 04 17:28:44 2012
Successfully onlined Undo Tablespace 1.
Tue Dec 04 17:28:44 2012
SMON: enabling tx recovery
Tue Dec 04 17:28:44 2012
*********************************************************************
WARNING: The following temporary tablespaces contain no files.
This condition can occur when a backup controlfile has
been restored. It may be necessary to add files to these
tablespaces. That can be done using the SQL statement:
ALTER TABLESPACE <tablespace_name> ADD TEMPFILE
Alternatively, if these temporary tablespaces are no longer
needed, then they can be dropped.
Empty temporary tablespace: TEMP
*********************************************************************
Database Characterset is ZHS16GBK
Tue Dec 04 17:28:44 2012
Errors in file d:\oracle\product\10.2.0\admin\orcl\bdump\orcl_smon_1992.trc:
ORA-00600: internal error code, arguments: , , , , , , [], []
replication_dependency_tracking turned off (no async multimaster replication found)
Tue Dec 04 17:28:45 2012
Fatal internal error happened while SMON was doing active transaction recovery.
Tue Dec 04 17:28:45 2012
Errors in file d:\oracle\product\10.2.0\admin\orcl\bdump\orcl_smon_1992.trc:
ORA-00600: internal error code, arguments: , , , , , , [], []
SMON: terminating instance due to error 474
Tue Dec 04 17:28:46 2012
Errors in file d:\oracle\product\10.2.0\admin\orcl\bdump\orcl_pmon_5752.trc:
ORA-00474: SMON process terminated with error
Tue Dec 04 17:28:47 2012
Errors in file d:\oracle\product\10.2.0\admin\orcl\bdump\orcl_psp0_1492.trc:
ORA-00474: SMON process terminated with error
Tue Dec 04 17:28:47 2012
Errors in file d:\oracle\product\10.2.0\admin\orcl\bdump\orcl_lgwr_5336.trc:
ORA-00474: SMON process terminated with error
Tue Dec 04 17:28:47 2012
Errors in file d:\oracle\product\10.2.0\admin\orcl\bdump\orcl_mman_4828.trc:
ORA-00474: SMON process terminated with error
Tue Dec 04 17:28:47 2012
Errors in file d:\oracle\product\10.2.0\admin\orcl\bdump\orcl_dbw0_5848.trc:
ORA-00474: SMON process terminated with error
Tue Dec 04 17:28:47 2012
Errors in file d:\oracle\product\10.2.0\admin\orcl\bdump\orcl_ckpt_5084.trc:
ORA-00474: SMON process terminated with error
Tue Dec 04 17:28:47 2012
Errors in file d:\oracle\product\10.2.0\admin\orcl\bdump\orcl_reco_2624.trc:
ORA-00474: SMON process terminated with error
页:
[1]