生产数据库ALERT中发现如下警报:ORA-4063 encountered when generating server alert SMG-4120
ORA-4063 encountered when generating server alert SMG-4121该错误每5分钟生成一次尝试了以下处理办法但未解决问题SQL>alter system enable restricted session
SQL>@$ORACLE_HOME/rdbms/admin/catnoalr.sql
SQL>@$ORACLE_HOME/rdbms/admin/catalog.sql
SQL>@$ORACLE_HOME/rdbms/admin/catproc.sql
SQL>@$ORACLE_HOME/rdbms/admin/catalrt.sql
SQL>@$ORACLE_HOME/rdbms/admin/utlrp.sql
SQL>alter system disable restricted session在网上查了很久,均未解决
http://forums.oracle.com/forums/thread.jspa?messageID=2205766&tstart=0
上说可以使用 metalink 430146.1 解决请有METALINK帐号的朋友帮查一下 430146.1
在下万分感激!
(不好意思,积分不足, 太穷,不知道有分后能否再给分)
ORA-4063 encountered when generating server alert SMG-4121该错误每5分钟生成一次尝试了以下处理办法但未解决问题SQL>alter system enable restricted session
SQL>@$ORACLE_HOME/rdbms/admin/catnoalr.sql
SQL>@$ORACLE_HOME/rdbms/admin/catalog.sql
SQL>@$ORACLE_HOME/rdbms/admin/catproc.sql
SQL>@$ORACLE_HOME/rdbms/admin/catalrt.sql
SQL>@$ORACLE_HOME/rdbms/admin/utlrp.sql
SQL>alter system disable restricted session在网上查了很久,均未解决
http://forums.oracle.com/forums/thread.jspa?messageID=2205766&tstart=0
上说可以使用 metalink 430146.1 解决请有METALINK帐号的朋友帮查一下 430146.1
在下万分感激!
(不好意思,积分不足, 太穷,不知道有分后能否再给分)
解决方案 »
- 启动PLSQL报错: access violation at address 7723FC47 in module 'ntdll.dll' .
- oracle做分区用的日期字段写入内容错误
- 关于oracle视图的建立
- 关于where a.1 = b.1(+)
- oracle 10g 客户端 进入问题
- RMAN备份的数据库保存在哪里?
- ORACLE 如何在数字和字符串混合的字段上按照数字的顺序进行范围查询?
- 如何在存储过程中获取异常信息
- 这段程序哪出了问题?
- 兄弟们:平常大家遇到的数据库开发觉的很简单,但当查询的数据量大时,是怎么解决这些问题的,欢迎大家探讨现实问题,一起提高自己的能力
- sql 行转列问题 急!
- oracle存储过程的问题
Modified 13-AUG-2009 Type PROBLEM Status MODERATED In this Document
Symptoms
Cause
Solution
References--------------------------------------------------------------------------------This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process, and therefore has not been subject to an independent technical review.
Applies to:
Oracle Server - Enterprise Edition - Version: 10.2.0.4 to 10.2.0.4
This problem can occur on any platform.Symptoms
The following messages appears in the alert log file :
ORA-0 encountered when generating server alert SMG-4120
ORA-0 encountered when generating server alert SMG-4121Cause
Messages 4120 and 4121 are used to record instance up/down events, it's just info and not errors :04120, 00000, "Instance %s up on node %s as of time %s; reason code: %s"
04121, 00000, "Instance %s down on node %s as of time %s; reason code: %s"Solution
Probably the SYS.ALERT_QUE is missing or corrupted,.Recreate it as per the following note:
Note 430146.1 'How to recreate the SYS.ALERT_QUE'In some cases you had to force drop the queue before, please do the following :?/rdbms/admin/catnoalr
exec DBMS_AQADM.DROP_QUEUE_TABLE(queue_table => 'sys.alert_qt', FORCE => TRUE);
?/rdbms/admin/dbmsslrt
?/rdbms/admin/catalrt
?/rdbms/admin/utlrpReferences
BUG:6315425 - ORA-0 ENCOUNTERED WHEN GENERATING SERVER ALERT SMG-4120
BUG:7536814 - ORA-0 ENCOUNTERED WHEN GENERATING SERVER ALERT SMG-4120
NOTE:430146.1 - How to recreate the SYS.ALERT_QUE--------------------------------------------------------------------------------
Related--------------------------------------------------------------------------------
Products
--------------------------------------------------------------------------------•Oracle Database Products > Oracle Database > Oracle Database > Oracle Server - Enterprise Edition
Modified 17-AUG-2009 Type HOWTO Status PUBLISHED In this Document
Goal
Solution
References--------------------------------------------------------------------------------Applies to:
Oracle Server - Enterprise Edition - Version: 10.2.0.1 to 10.2.0.4
Information in this document applies to any platform.Goal
The purpose of this article is to outline the steps for recreating the SYS.ALERT_QUE The ALERT_QUE is used by the Grid Control and DB Control Management Agents to monitor server-generated alerts
NOTE: By running the script below, the queue tables will be recreated and the messages in the queue
will be lost Solution
SQL> connect / as sysdbaSQL>alter system enable restricted session;To drop server alert schema.SQL>@$ORACLE_HOME/rdbms/admin/catnoalr.sqlTo re-create tables, sequence, type and queue for server alertSQL>@$ORACLE_HOME/rdbms/admin/dbmsslrt.sql
SQL>@$ORACLE_HOME/rdbms/admin/catalrt.sqlTo recompile the invalid objectsSQL>@$ORACLE_HOME/rdbms/admin/utlrp.sqlSQL> alter system disable restricted session;
Note: This option may leave DBSNMP.MGMT_BSLN_INTERNAL invalid. To validate the same run catsnmp.sqlORSQL> connect / as sysdbaSQL>alter system enable restricted session;To drop server alert schema.SQL>@$ORACLE_HOME/rdbms/admin/catnoalr.sqlRerun catproc.sqlSQL>@$ORACLE_HOME/rdbms/admin/catproc.sqlSQL> alter system disable restricted session; References
NOTE:603289.1 - OBJECTS MGMT_BSLN_INTERNAL and MGMT_BSLN INVALID FOR DBSNMP--------------------------------------------------------------------------------
Related--------------------------------------------------------------------------------
Products
--------------------------------------------------------------------------------•Oracle Database Products > Oracle Database > Oracle Database > Oracle Server - Enterprise Edition
Keywords
--------------------------------------------------------------------------------
INVALID OBJECT; DB CONTROL; GRID CONTROL; OUTLINE; MANAGEMENT AGENT; RESTRICTED; UTLRP.SQL; CATPROC.SQL; INVALID OBJECT