非常郁闷的问题:oracle服务突然不响应

brightboy 2008-10-09 11:34:31
进行了一些数据量比较大的插入删除操作后,再也无法连接上oracle服务

1.检查了系统的事件记录,未发现异常
2.手动重新启动oracle服务,启动失败
3.ping服务器IP地址正常
4.在oracle服务器的本机上连接也不响应
5.检查了alert*文件,有NI 的信息
6.已经禁用了网卡上的节能
7.出现这个问题后只能重新启动机器才能恢复

请熟悉这些的朋友帮忙~
...全文
277 20 打赏 收藏 转发到动态 举报
写回复
用AI写文章
20 条回复
切换为时间正序
请发表友善的回复…
发表回复
brightboy 2008-10-10
  • 打赏
  • 举报
回复
持续测试了一段时间,未发现死机现象,谢谢大家~
BlueskyWide 2008-10-09
  • 打赏
  • 举报
回复
其实,LZ的服务器偶而出现死机现象也没什么大惊小怪的,操作系统、Oracle也不能解决特殊用户的所有问题。

只是如果经常出现此类问题,必须得多看看书和资料了。
brightboy 2008-10-09
  • 打赏
  • 举报
回复
可能在另外一个文件里,我再发~
Well 2008-10-09
  • 打赏
  • 举报
回复
没看到什么异常啊。。。
brightboy 2008-10-09
  • 打赏
  • 举报
回复
谢谢,我先去试试
king20151111 2008-10-09
  • 打赏
  • 举报
回复
如果没有删除oracle里那些系统表之类的,应该没问题的,再看看日志里有没有问题
brightboy 2008-10-09
  • 打赏
  • 举报
回复
操作系统是win2003server
BlueskyWide 2008-10-09
  • 打赏
  • 举报
回复
一、服务器性能优化也是LZ可能要面临的问题。

二、再出现故障时,不妨检查一下是否有死锁。

SELECT /*+ rule */ s.username,
decode(l.type,'TM','TABLE LOCK',
'TX','ROW LOCK',
NULL) LOCK_LEVEL,
o.owner,o.object_name,o.object_type,
s.sid,s.serial#,s.terminal,s.machine,s.program,s.osuser
FROM v$session s,v$lock l,dba_objects o
WHERE l.sid = s.sid
AND l.id1 = o.object_id(+)
AND s.username is NOT NULL

可以通过alter system kill session ‘sid,serial#’来杀掉会话 。



brightboy 2008-10-09
  • 打赏
  • 举报
回复
用的是IBM机架式服务器
Oralce9
brightboy 2008-10-09
  • 打赏
  • 举报
回复
这是log中的内容

因为是24*7的系统,所以重启是不允许的

brightboy 2008-10-09
  • 打赏
  • 举报
回复
日志:
Wed Oct 08 16:44:42 2008
starting up 1 shared server(s) ...
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
Wed Oct 08 16:44:43 2008
alter database mount exclusive
Wed Oct 08 16:44:51 2008
Successful mount of redo thread 1, with mount id 2325586750.
Wed Oct 08 16:44:51 2008
Database mounted in Exclusive Mode.
Completed: alter database mount exclusive
Wed Oct 08 16:44:51 2008
alter database open
Wed Oct 08 16:44:51 2008
Beginning crash recovery of 1 threads
Wed Oct 08 16:44:51 2008
Started first pass scan
Wed Oct 08 16:44:52 2008
Completed first pass scan
32374 redo blocks read, 606 data blocks need recovery
Wed Oct 08 16:44:52 2008
Started recovery at
Thread 1: logseq 2103, block 21371, scn 0.0
Recovery of Online Redo Log: Thread 1 Group 2 Seq 2103 Reading mem 0
Mem# 0 errs 0: D:\ORACLE\ORADATA\SERVERA\REDO02.LOG
Wed Oct 08 16:44:52 2008
Ended recovery at
Thread 1: logseq 2103, block 53745, scn 0.44955196
606 data blocks read, 606 data blocks written, 32374 redo blocks read
Crash recovery completed successfully
Wed Oct 08 16:44:53 2008
Thread 1 advanced to log sequence 2104
Thread 1 opened at log sequence 2104
Current log# 3 seq# 2104 mem# 0: D:\ORACLE\ORADATA\SERVERA\REDO03.LOG
Successful open of redo thread 1.
Wed Oct 08 16:44:54 2008
SMON: enabling cache recovery
Wed Oct 08 16:44:55 2008
Undo Segment 1 Onlined
Undo Segment 2 Onlined
Undo Segment 3 Onlined
Undo Segment 4 Onlined
Undo Segment 5 Onlined
Undo Segment 6 Onlined
Undo Segment 7 Onlined
Undo Segment 8 Onlined
Undo Segment 9 Onlined
Undo Segment 10 Onlined
Successfully onlined Undo Tablespace 1.
Wed Oct 08 16:44:55 2008
SMON: enabling tx recovery
Wed Oct 08 16:44:55 2008
Database Characterset is ZHS16GBK
replication_dependency_tracking turned off (no async multimaster replication found)
Wed Oct 08 16:45:19 2008
Completed: alter database open
Wed Oct 08 18:00:28 2008
Thread 1 advanced to log sequence 2105
Current log# 1 seq# 2105 mem# 0: D:\ORACLE\ORADATA\SERVERA\REDO01.LOG
Wed Oct 08 20:00:07 2008
Thread 1 advanced to log sequence 2106
Current log# 2 seq# 2106 mem# 0: D:\ORACLE\ORADATA\SERVERA\REDO02.LOG
Wed Oct 08 22:00:11 2008
Thread 1 advanced to log sequence 2107
Current log# 3 seq# 2107 mem# 0: D:\ORACLE\ORADATA\SERVERA\REDO03.LOG
Thu Oct 09 00:00:24 2008
Thread 1 advanced to log sequence 2108
Current log# 1 seq# 2108 mem# 0: D:\ORACLE\ORADATA\SERVERA\REDO01.LOG
Thu Oct 09 02:00:28 2008
Thread 1 advanced to log sequence 2109
Current log# 2 seq# 2109 mem# 0: D:\ORACLE\ORADATA\SERVERA\REDO02.LOG
Thu Oct 09 04:38:22 2008
Thread 1 advanced to log sequence 2110
Current log# 3 seq# 2110 mem# 0: D:\ORACLE\ORADATA\SERVERA\REDO03.LOG
Thu Oct 09 07:00:02 2008
Thread 1 advanced to log sequence 2111
Current log# 1 seq# 2111 mem# 0: D:\ORACLE\ORADATA\SERVERA\REDO01.LOG
Thu Oct 09 09:00:06 2008
Thread 1 advanced to log sequence 2112
Current log# 2 seq# 2112 mem# 0: D:\ORACLE\ORADATA\SERVERA\REDO02.LOG
Dump file c:\oracle\admin\servera\bdump\alert_servera.log
Thu Oct 09 09:25:14 2008
ORACLE V9.2.0.1.0 - Production vsnsta=0
vsnsql=12 vsnxtr=3
Windows 2000 Version 5.2 Service Pack 2, CPU type 586
Thu Oct 09 09:25:14 2008
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
SCN scheme 2
Using log_archive_dest parameter default value
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up ORACLE RDBMS Version: 9.2.0.1.0.
System parameters with non-default values:
processes = 150
timed_statistics = TRUE
shared_pool_size = 50331648
large_pool_size = 8388608
java_pool_size = 33554432
control_files = d:\oracle\oradata\servera\CONTROL01.CTL, d:\oracle\oradata\servera\CONTROL02.CTL, d:\oracle\oradata\servera\CONTROL03.CTL
db_block_size = 8192
db_cache_size = 25165824
compatible = 9.2.0.0.0
db_file_multiblock_read_count= 16
fast_start_mttr_target = 300
undo_management = AUTO
undo_tablespace = UNDOTBS1
undo_retention = 10800
remote_login_passwordfile= EXCLUSIVE
db_domain =
instance_name = servera
dispatchers = (PROTOCOL=TCP) (SERVICE=serveraXDB)
job_queue_processes = 10
hash_join_enabled = TRUE
background_dump_dest = C:\oracle\admin\servera\bdump
user_dump_dest = C:\oracle\admin\servera\udump
core_dump_dest = C:\oracle\admin\servera\cdump
sort_area_size = 524288
db_name = servera
open_cursors = 300
star_transformation_enabled= FALSE
query_rewrite_enabled = FALSE
pga_aggregate_target = 25165824
aq_tm_processes = 1
PMON started with pid=2
DBW0 started with pid=3
LGWR started with pid=4
CKPT started with pid=5
SMON started with pid=6
RECO started with pid=7
CJQ0 started with pid=8
QMN0 started with pid=9
Thu Oct 09 09:25:18 2008
starting up 1 shared server(s) ...
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
Thu Oct 09 09:25:19 2008
alter database mount exclusive
Thu Oct 09 09:25:24 2008
Successful mount of redo thread 1, with mount id 2325709247.
Thu Oct 09 09:25:24 2008
Database mounted in Exclusive Mode.
Completed: alter database mount exclusive
Thu Oct 09 09:25:24 2008
alter database open
Thu Oct 09 09:25:25 2008
Beginning crash recovery of 1 threads
Thu Oct 09 09:25:25 2008
Started first pass scan
Thu Oct 09 09:25:25 2008
Completed first pass scan
80219 redo blocks read, 1560 data blocks need recovery
Thu Oct 09 09:25:26 2008
Started recovery at
Thread 1: logseq 2111, block 189017, scn 0.0
Recovery of Online Redo Log: Thread 1 Group 1 Seq 2111 Reading mem 0
Mem# 0 errs 0: D:\ORACLE\ORADATA\SERVERA\REDO01.LOG
Recovery of Online Redo Log: Thread 1 Group 2 Seq 2112 Reading mem 0
Mem# 0 errs 0: D:\ORACLE\ORADATA\SERVERA\REDO02.LOG
Thu Oct 09 09:25:28 2008
Ended recovery at
Thread 1: logseq 2112, block 64439, scn 0.45199449
1560 data blocks read, 1560 data blocks written, 80219 redo blocks read
Crash recovery completed successfully
Thu Oct 09 09:25:28 2008
Thread 1 advanced to log sequence 2113
Thread 1 opened at log sequence 2113
Current log# 3 seq# 2113 mem# 0: D:\ORACLE\ORADATA\SERVERA\REDO03.LOG
Successful open of redo thread 1.
Thu Oct 09 09:25:29 2008
SMON: enabling cache recovery
Thu Oct 09 09:25:30 2008
Undo Segment 1 Onlined
Undo Segment 2 Onlined
Undo Segment 3 Onlined
Undo Segment 4 Onlined
Undo Segment 5 Onlined
Undo Segment 6 Onlined
Undo Segment 7 Onlined
Undo Segment 8 Onlined
Undo Segment 9 Onlined
Undo Segment 10 Onlined
Successfully onlined Undo Tablespace 1.
Thu Oct 09 09:25:30 2008
SMON: enabling tx recovery
Thu Oct 09 09:25:30 2008
Database Characterset is ZHS16GBK
replication_dependency_tracking turned off (no async multimaster replication found)
Thu Oct 09 09:25:53 2008
Completed: alter database open
Thu Oct 09 10:53:48 2008
Thread 1 advanced to log sequence 2114
Current log# 1 seq# 2114 mem# 0: D:\ORACLE\ORADATA\SERVERA\REDO01.LOG
dlpseeyou 2008-10-09
  • 打赏
  • 举报
回复
重启
oracledbalgtu 2008-10-09
  • 打赏
  • 举报
回复
综上所述,出错的根源估计是网络相关导致(也可能是bug),最好把alert.log的出错信息post出来。


[Quote=引用楼主 brightboy 的帖子:]
进行了一些数据量比较大的插入删除操作后,再也无法连接上oracle服务

1.检查了系统的事件记录,未发现异常
2.手动重新启动oracle服务,启动失败
3.ping服务器IP地址正常
4.在oracle服务器的本机上连接也不响应
5.检查了alert*文件,有NI 的信息
6.已经禁用了网卡上的节能
7.出现这个问题后只能重新启动机器才能恢复

请熟悉这些的朋友帮忙~
[/Quote]
無名VF 2008-10-09
  • 打赏
  • 举报
回复
[Quote=引用 18 楼 ruihuahan 的回复:]
应该是网络问题。

不建议在服务器上安装实时监控的杀毒软件,很影响性能。
[/Quote]
UP
ruihuahan 2008-10-09
  • 打赏
  • 举报
回复
应该是网络问题。

不建议在服务器上安装实时监控的杀毒软件,很影响性能。
brightboy 2008-10-09
  • 打赏
  • 举报
回复
嗯,似乎这种情况的可能性比较大,
服务器上安装了诺顿
我先卸了它~
BlueskyWide 2008-10-09
  • 打赏
  • 举报
回复
TNS-12560: TNS: 协议适配器错误

是网络上的故障,如果net configuration assistant没有错的话,是不是其它故障。

如有好几种病毒反复地向某ip地址发包,阻塞端口的现象。建议使用杀毒软件查一下整个网络。

brightboy 2008-10-09
  • 打赏
  • 举报
回复
sqlnet.log中
Fatal NI connect error 12560, connecting to:
(DESCRIPTION=(ADDRESS=(PROTOCOL=BEQ)(PROGRAM=oracle)(ARGV0=oracleservera)(ARGS='(DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))'))(CONNECT_DATA=(SID=servera)(CID=(PROGRAM=c:\oracle\ora92\bin\ORACLE.EXE)(HOST=SERVERA)(USER=OraUser))))

VERSION INFORMATION:
TNS for 32-bit Windows: Version 9.2.0.1.0 - Production
Oracle Bequeath NT Protocol Adapter for 32-bit Windows: Version 9.2.0.1.0 - Production
Time: 08-10月-2008 16:41:52
Tracing not turned on.
Tns error struct:
nr err code: 0
ns main err code: 12560
TNS-12560: TNS: 协议适配器错误
ns secondary err code: 0
nt main err code: 530
TNS-00530: 协议适配器错误
nt secondary err code: 203
nt OS err code: 0


***********************************************************************
Fatal NI connect error 12560, connecting to:
(DESCRIPTION=(ADDRESS=(PROTOCOL=BEQ)(PROGRAM=oracle)(ARGV0=oracleservera)(ARGS='(DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))'))(CONNECT_DATA=(SID=servera)(CID=(PROGRAM=c:\oracle\ora92\bin\ORACLE.EXE)(HOST=SERVERA)(USER=OraUser))))

VERSION INFORMATION:
TNS for 32-bit Windows: Version 9.2.0.1.0 - Production
Oracle Bequeath NT Protocol Adapter for 32-bit Windows: Version 9.2.0.1.0 - Production
Time: 08-10月-2008 16:42:03
Tracing not turned on.
Tns error struct:
nr err code: 0
ns main err code: 12560
TNS-12560: TNS: 协议适配器错误
ns secondary err code: 0
nt main err code: 530
TNS-00530: 协议适配器错误
nt secondary err code: 203
nt OS err code: 0


***********************************************************************
Fatal NI connect error 12560, connecting to:
(DESCRIPTION=(ADDRESS=(PROTOCOL=BEQ)(PROGRAM=oracle)(ARGV0=oracleservera)(ARGS='(DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))'))(CONNECT_DATA=(SID=servera)(CID=(PROGRAM=c:\oracle\ora92\bin\ORACLE.EXE)(HOST=SERVERA)(USER=OraUser))))

VERSION INFORMATION:
TNS for 32-bit Windows: Version 9.2.0.1.0 - Production
Oracle Bequeath NT Protocol Adapter for 32-bit Windows: Version 9.2.0.1.0 - Production
Time: 09-10月-2008 09:22:26
Tracing not turned on.
Tns error struct:
nr err code: 0
ns main err code: 12560
TNS-12560: TNS: 协议适配器错误
ns secondary err code: 0
nt main err code: 530
TNS-00530: 协议适配器错误
nt secondary err code: 203
nt OS err code: 0


***********************************************************************
Fatal NI connect error 12560, connecting to:
(DESCRIPTION=(ADDRESS=(PROTOCOL=BEQ)(PROGRAM=oracle)(ARGV0=oracleservera)(ARGS='(DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))'))(CONNECT_DATA=(SID=servera)(CID=(PROGRAM=c:\oracle\ora92\bin\ORACLE.EXE)(HOST=SERVERA)(USER=OraUser))))

VERSION INFORMATION:
TNS for 32-bit Windows: Version 9.2.0.1.0 - Production
Oracle Bequeath NT Protocol Adapter for 32-bit Windows: Version 9.2.0.1.0 - Production
Time: 09-10月-2008 09:22:36
Tracing not turned on.
Tns error struct:
nr err code: 0
ns main err code: 12560
TNS-12560: TNS: 协议适配器错误
ns secondary err code: 0
nt main err code: 530
TNS-00530: 协议适配器错误
nt secondary err code: 203
nt OS err code: 0
brightboy 2008-10-09
  • 打赏
  • 举报
回复
oradim.log

Wed Jul 09 14:32:12 2008ORA-12638: 身份证明检索失败

Tue Jul 15 07:53:17 2008ORA-12560: TNS: 协议适配器错误

Thu Aug 07 08:33:12 2008ORA-12560: TNS: 协议适配器错误

Sun Aug 24 17:20:51 2008ORA-12560: TNS: 协议适配器错误

Mon Aug 25 18:54:08 2008ORA-12560: TNS: 协议适配器错误

Mon Sep 01 19:23:59 2008ORA-12638: 身份证明检索失败

Sun Sep 07 15:16:08 2008ORA-12560: TNS: 协议适配器错误

Tue Sep 09 08:52:14 2008ORA-12560: TNS: 协议适配器错误

Wed Sep 17 20:05:30 2008ORA-12638: 身份证明检索失败

Sun Sep 28 15:30:32 2008ORA-12638: 身份证明检索失败

Mon Sep 29 19:04:19 2008ORA-12560: TNS: 协议适配器错误

Tue Sep 30 10:38:45 2008ORA-12560: TNS: 协议适配器错误

Sat Oct 04 08:11:08 2008ORA-12560: TNS: 协议适配器错误

Sun Oct 05 09:02:36 2008ORA-12638: 身份证明检索失败

Sun Oct 05 11:04:32 2008ORA-12560: TNS: 协议适配器错误

Sun Oct 05 11:45:49 2008ORA-12560: TNS: 协议适配器错误

Sun Oct 05 15:05:09 2008ORA-12560: TNS: 协议适配器错误

Sun Oct 05 15:53:23 2008ORA-12560: TNS: 协议适配器错误

Sun Oct 05 17:15:44 2008ORA-12560: TNS: 协议适配器错误

Mon Oct 06 11:30:50 2008ORA-12560: TNS: 协议适配器错误

Mon Oct 06 16:24:47 2008ORA-12638: 身份证明检索失败

Tue Oct 07 18:53:11 2008ORA-12560: TNS: 协议适配器错误

Tue Oct 07 23:22:01 2008ORA-12560: TNS: 协议适配器错误

Wed Oct 08 16:42:03 2008ORA-12560: TNS: 协议适配器错误

Thu Oct 09 09:22:36 2008ORA-12560: TNS: 协议适配器错误
brightboy 2008-10-09
  • 打赏
  • 举报
回复
最近才出的,而且比较频繁
对于一个24*7运行的系统来说,死机是绝对不允许的,所以...

17,377

社区成员

发帖
与我相关
我的任务
社区描述
Oracle 基础和管理
社区管理员
  • 基础和管理社区
加入社区
  • 近7日
  • 近30日
  • 至今
社区公告
暂无公告

试试用AI创作助手写篇文章吧