论坛徽章:: 0

电梯直达

1楼 [收藏(0)] [报告]

发表于 2010-03-09 12:47 |只看该作者 |倒序浏览

数据库版本：Oralce 9I  90111
操作系统：windows 2003
双机软件：rose HA
服务器品牌：惠普

09年9月份安装好的，一直使用的都没问题，前几天突然出现客户端连接不上，看ROSE ha 的服务和操作系统的服务都没问题，出现这种问题后从起服务器或切换ROSE HA的服务可以好用一段时间。
操作系统事件日志在今天9点54分有错误
内容：（事件 ID ( 20 )的描述(在资源( Oracle.orcl )中)无法找到。本地计算机可能没有必要的注册信息或消息 DLL 文件来从远程计算机显示消息。您可能可以使用 /AUXSOURCE= 标识来检索词描述；查看帮助和支持以了解详细信息。下列信息是事件的一部分: ORACLE Instance orcl - Can not allocate log, archival required
.）

oracle 的 alrtlog  在这个时间段的内容：（Wed Mar 03 16:21:33 2010
replication_dependency_tracking turned off (no async multimaster replication found)
Completed: alter database open
Wed Mar 03 17:53:43 2010
Errors in file G:\oracle\admin\orcl\bdump\orclSMON.TRC:
ORA-00604: error occurred at recursive SQL level 1
ORA-01001: invalid cursor
ORA-00601: cleanup lock conflict

Tue Mar 09 09:54:15 2010
Thread 1 cannot allocate new log, sequence 227
All online logs needed archiving
  Current log# 3 seq# 226 mem# 0: G:\ORACLE\ORADATA\ORCL\REDO03.LOG
Tue Mar 09 12:04:21 2010
Restarting dead background process EMN0
EMN0 started with pid=24
Tue Mar 09 12:04:21 2010
Shutting down instance: further logons disabled
Shutting down instance (immediate)
License high water mark = 13
Tue Mar 09 12:04:22 2010
Errors in file G:\oracle\admin\orcl\bdump\ORA00280.TRC:
ORA-01089: immediate shutdown in progress - no operations are permitted
ORA-01089: immediate shutdown in progress - no operations are permitted

Tue Mar 09 12:04:22 2010
Errors in file G:\oracle\admin\orcl\bdump\ORA00976.TRC:
ORA-01089: immediate shutdown in progress - no operations are permitted
ORA-00604: error occurred at recursive SQL level 1
ORA-01089: immediate shutdown in progress - no operations are permitted

Tue Mar 09 12:04:23 2010
Errors in file G:\oracle\admin\orcl\bdump\ORA01620.TRC:
ORA-01089: immediate shutdown in progress - no operations are permitted
ORA-01089: immediate shutdown in progress - no operations are permitted）

请朋友们帮我分析下是什么原因导致的这个问题，谢谢了。

文库|博客

在炸老子就跑

稍有积蓄

论坛徽章:: 0

2楼 [报告]

发表于 2010-03-09 14:43 |只看该作者

查一下你的归档目录是否满了

实战分享：从技术角度谈机器学习入门| 【大话IT】RadonDB低门槛向MySQL集群下战书 | ChinaUnix打赏功能已上线！ | 新一代分布式关系型数据库RadonDB知多少？

dingning239

小富即安

论坛徽章:: 0

3楼 [报告]

发表于 2010-03-09 16:22 |只看该作者

与归档日志没啥关系，以前我碰到过rac环境不能使用taf连接不同节点的问题，oracle官方认为是一个bug

楼主看看是否可以按照文档所说解决问题：

到metalink上找到一篇文档364855.1，上面介绍了9207存在的这种情况：

RAC Connection Redirected To Wrong Host/IP ORA-12545 [ID 364855.1]

--------------------------------------------------------------------------------

  修改时间 01-MAY-2008    类型 PROBLEM    状态 PUBLISHED

In this Document
  Symptoms
  Cause
  Solution
  References

--------------------------------------------------------------------------------

Applies to:
Oracle Net Services - Version: 9.1 to 10.2
This problem can occur on any platform.

Symptoms
When we try to connect to a RAC service name we sometimes get redirected by the first node's listener to the public address/hostname of the second node instead of its VIP address. An ORA-12545 error may be generated if that public hostname is not configured in DNS.

We were expecting the connection to eventually be redirected to the VIP of the other node.

Cause
The Database on one RAC node remote registers with the wrong local IP address to the listener on the other RAC node (e.g. the public IP address instead of the wanted VIP address).

The PMON process handles database registration to the local and remote listeners. For remote listeners registration PMON will have to find out what is the IP address of the local system in order to present it to the remote listener as database contact address.

In the default Oracle configuration, for hosts which have more than one IP address configured on the network interfaces,  it is undefined which IP address will be selected for remote registration.

Solution
Modify the local_listener database parameter to point to the local VIP address. For the parameter value use either an alias name which contains in the DESCRIPTION field only the VIP address or use an explicit connection statement like the following:

alter system set LOCAL_LISTENER="(ADDRESS=(PROTOCOL=TCP)(HOST=<VIP_address>)(PORT=1521))" scope=both sid='instance_name';  Where "instance_name" is the unique instance name. Issue this statement for all instances in the cluster.

The LOCAL_LISTENER database parameter will give PMON a hint in respect of which IP address it should use for remote registration with other nodes' listener(s).

References
NOTE:235562.1 - Issues affecting Automatic Service Registration
NOTE:256275.1 - Dynamic Registration Fails On Multiple Network Interface Server