Yong Huang 发表于 2012-12-6 01:06
Why do you check adump? The most important logs are in bdump.
Were you able to login database loc ...
谢谢回复,好像11g数据库没有bdump这个目录了吧,日志文件如下:
(一):
alert.log
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 E:\APP\YUEYUE\PRODUCT\11.2.0\DBHOME_2\DATABASE\SPFILEORCL.ORA
System parameters with non-default values:
processes = 5000
sessions = 7522
nls_language = "AMERICAN"
nls_territory = "CHINA"
memory_target = 3216M
control_files = "E:\APP\YUEYUE\ORADATA\ORCL\CONTROL01.CTL"
control_files = "E:\APP\YUEYUE\FLASH_RECOVERY_AREA\ORCL\CONTROL02.CTL"
db_block_size = 8192
compatible = "11.2.0.0.0"
db_recovery_file_dest = "E:\app\yueyue\flash_recovery_area"
db_recovery_file_dest_size= 3912M
undo_tablespace = "UNDOTBS1"
remote_login_passwordfile= "EXCLUSIVE"
db_domain = ""
dispatchers = "(PROTOCOL=TCP)(dispatchers=3)(SERVICE=orclXDB)"
audit_file_dest = "E:\APP\YUEYUE\ADMIN\ORCL\ADUMP"
audit_trail = "DB"
db_name = "orcl"
open_cursors = 300
diagnostic_dest = "E:\APP\YUEYUE"
Wed Dec 05 13:43:54 2012
PMON started with pid=2, OS id=668
Wed Dec 05 13:43:54 2012
VKTM started with pid=3, OS id=1176 at elevated priority
VKTM running at (10)millisec precision with DBRM quantum (100)ms
Wed Dec 05 13:43:54 2012
DIAG started with pid=5, OS id=1264
Wed Dec 05 13:43:54 2012
PSP0 started with pid=7, OS id=1012
Wed Dec 05 13:43:54 2012
DIA0 started with pid=8, OS id=1008
Wed Dec 05 13:43:54 2012
MMAN started with pid=9, OS id=1088
Wed Dec 05 13:43:54 2012
DBW0 started with pid=10, OS id=1384
Wed Dec 05 13:43:54 2012
LGWR started with pid=11, OS id=976
Wed Dec 05 13:43:54 2012
CKPT started with pid=12, OS id=1004
Wed Dec 05 13:43:54 2012
SMON started with pid=13, OS id=1016
Wed Dec 05 13:43:54 2012
RECO started with pid=14, OS id=1080
Wed Dec 05 13:43:54 2012
MMON started with pid=15, OS id=1084
starting up 3 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
starting up 1 shared server(s) ...
Wed Dec 05 13:43:54 2012
GEN0 started with pid=4, OS id=1164
Wed Dec 05 13:43:55 2012
ORACLE_BASE from environment = E:\app\yueyue
Wed Dec 05 13:43:54 2012
DBRM started with pid=6, OS id=1332
Wed Dec 05 13:43:54 2012
MMNL started with pid=16, OS id=960
Wed Dec 05 13:43:57 2012
alter database mount exclusive
Successful mount of redo thread 1, with mount id 1328985885
Database mounted in Exclusive Mode
Lost write protection disabled
Completed: alter database mount exclusive
alter database open
Wed Dec 05 13:44:07 2012
Beginning crash recovery of 1 threads
parallel recovery started with 2 processes
Started redo scan
Completed redo scan
read 110 KB redo, 60 data blocks need recovery
Started redo application at
Thread 1: logseq 2935, block 35688
Recovery of Online Redo Log: Thread 1 Group 1 Seq 2935 Reading mem 0
Mem# 0: E:\APP\YUEYUE\ORADATA\ORCL\REDO01.LOG
Completed redo application of 0.05MB
Completed crash recovery at
Thread 1: logseq 2935, block 35909, scn 27327361
60 data blocks read, 60 data blocks written, 110 redo k-bytes read
Wed Dec 05 13:44:11 2012
Thread 1 advanced to log sequence 2936 (thread open)
Thread 1 opened at log sequence 2936
Current log# 2 seq# 2936 mem# 0: E:\APP\YUEYUE\ORADATA\ORCL\REDO02.LOG
Successful open of redo thread 1
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Wed Dec 05 13:44:12 2012
SMON: enabling cache recovery
Wed Dec 05 13:44:20 2012
Successfully onlined Undo Tablespace 2.
Verifying file header compatibility for 11g tablespace encryption..
Verifying 11g file header compatibility for tablespace encryption completed
SMON: enabling tx recovery
Database Characterset is UTF8
No Resource Manager plan active
replication_dependency_tracking turned off (no async multimaster replication found)
Wed Dec 05 13:44:34 2012
Starting background process QMNC
Wed Dec 05 13:44:34 2012
QMNC started with pid=24, OS id=2364
Wed Dec 05 13:44:46 2012
Completed: alter database open
Wed Dec 05 13:44:59 2012
Starting background process CJQ0
Wed Dec 05 13:44:59 2012
CJQ0 started with pid=29, OS id=2448
Wed Dec 05 13:45:06 2012
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.
Wed Dec 05 13:53:39 2012
Starting background process SMCO
Wed Dec 05 13:53:39 2012
SMCO started with pid=26, OS id=3792
Wed Dec 05 17:28:17 2012
Thread 1 cannot allocate new log, sequence 2937
Private strand flush not complete
Current log# 2 seq# 2936 mem# 0: E:\APP\YUEYUE\ORADATA\ORCL\REDO02.LOG
Thread 1 advanced to log sequence 2937 (LGWR switch)
Current log# 3 seq# 2937 mem# 0: E:\APP\YUEYUE\ORADATA\ORCL\REDO03.LOG
Wed Dec 05 19:38:23 2012
***********************************************************************
Fatal NI connect error 12636, connecting to:
(LOCAL=NO)
VERSION INFORMATION:
TNS for 64-bit Windows: Version 11.2.0.1.0 - Production
Oracle Bequeath NT Protocol Adapter for 64-bit Windows: Version 11.2.0.1.0 - Production
Windows NT TCP/IP NT Protocol Adapter for 64-bit Windows: Version 11.2.0.1.0 - Production
Time: 05-12月-2012 19:38:23
Tracing not turned on.
Tns error struct:
ns main err code: 12636
TNS-12636: 包发送失败
ns secondary err code: 12560
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
opiodr aborting process unknown ospid (4824) as a result of ORA-609
(二)
在数据库所在机器上sqlplus 登录的情况
Microsoft Windows [版本 5.2.3790]
(C) 版权所有 1985-2003 Microsoft Corp.
C:\Documents and Settings\yueyue>sqlplus / as sysdba
SQL*Plus: Release 11.2.0.1.0 Production on 星期四 12月 6 09:24:28 2012
Copyright (c) 1982, 2010, Oracle. All rights reserved.
已连接到空闲例程。
SQL> exit
已断开连接
C:\Documents and Settings\yueyue>sqlplus
SQL*Plus: Release 11.2.0.1.0 Production on 星期四 12月 6 09:24:47 2012
Copyright (c) 1982, 2010, Oracle. All rights reserved.
请输入用户名: root
输入口令:
ERROR:
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
进程 ID: 0
会话 ID: 0 序列号: 0
请输入用户名:
(三)
监听器的log.xml
type='UNKNOWN' level='16' host_id='CN-CAIWUSYS'
host_addr='192.168.1.83'>
06-12月-2012 09:22:23 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=SYSTEM))(SERVICE_NAME=orcl)) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.1.83)
(PORT=2424)) * establish * orcl * 0
type='UNKNOWN' level='16' host_id='CN-CAIWUSYS'
host_addr='192.168.1.83'>
06-12月-2012 09:22:28 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=SYSTEM))(SERVICE_NAME=orcl)) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.1.83)
(PORT=2575)) * establish * orcl * 12571
type='UNKNOWN' level='16' host_id='CN-CAIWUSYS'
host_addr='192.168.1.83'>
TNS-12571: TNS: 包写入程序失败
TNS-12560: TNS: 协议适配器错误
TNS-00502: 参数无效
64-bit Windows Error: 22: Invalid argument
TNS-12518: TNS: 监听程序无法分发客户机连接
TNS-12560: TNS: 协议适配器错误
type='UNKNOWN' level='16' host_id='CN-CAIWUSYS'
host_addr='192.168.1.83'>
06-12月-2012 09:23:50 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=SYSTEM))(SERVICE_NAME=orcl)) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.1.83)
(PORT=2577)) * establish * orcl * 0
type='UNKNOWN' level='16' host_id='CN-CAIWUSYS'
host_addr='192.168.1.83'>
06-12月-2012 09:23:55 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=SYSTEM))(SERVICE_NAME=orcl)) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.1.83)
(PORT=2734)) * establish * orcl * 12571
type='UNKNOWN' level='16' host_id='CN-CAIWUSYS'
host_addr='192.168.1.83'>
TNS-12571: TNS: 包写入程序失败
TNS-12560: TNS: 协议适配器错误
TNS-00502: 参数无效
64-bit Windows Error: 22: Invalid argument
TNS-12518: TNS: 监听程序无法分发客户机连接
TNS-12560: TNS: 协议适配器错误
type='UNKNOWN' level='16' host_id='CN-CAIWUSYS'
host_addr='192.168.1.83'>
06-12月-2012 09:25:17 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=SYSTEM))(SERVICE_NAME=orcl)) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.1.83)
(PORT=2736)) * establish * orcl * 0
type='UNKNOWN' level='16' host_id='CN-CAIWUSYS'
host_addr='192.168.1.83'>
06-12月-2012 09:25:17 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=SYSTEM))(SERVICE_NAME=orcl)) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.1.83)
(PORT=2887)) * establish * orcl * 12518
type='UNKNOWN' level='16' host_id='CN-CAIWUSYS'
host_addr='192.168.1.83'>
TNS-12518: TNS: 监听程序无法分发客户机连接
TNS-12560: TNS: 协议适配器错误
type='UNKNOWN' level='16' host_id='CN-CAIWUSYS'
host_addr='192.168.1.83'>
06-12月-2012 09:26:39 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=SYSTEM))(SERVICE_NAME=orcl)) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.1.83)
(PORT=2889)) * establish * orcl * 12560
type='UNKNOWN' level='16' host_id='CN-CAIWUSYS'
host_addr='192.168.1.83'>
TNS-12560: TNS: 协议适配器错误
TNS-00530: 协议适配器错误
64-bit Windows Error: 53: Unknown error
TNS-12518: TNS: 监听程序无法分发客户机连接
TNS-12571: TNS: 包写入程序失败
TNS-12560: TNS: 协议适配器错误
TNS-00502: 参数无效
64-bit Windows Error: 22: Invalid argument