故障报错如下
Wed Mar 07 16:42:43 GMT+08:00 2012Errors in file /oracle10g/app/oracle/admin/zgscdb/udump/zgscdb1_ora_55247194.trc:
ORA-27300: OS system dependent operation:invalid_process_id failed with status: 0
ORA-27301: OS failure message: Error 0
ORA-27302: failure occurred at: skgpalive1
ORA-27300,ORA-27301,ORA-27302事实上有很多报错原因,主要是数据库和操作系统交互时引起的报错,大部分为bug,上述报错是由于bug 10010310引起的,需要打patch 10010310补丁。metalink上的具体信息如下
Applies to:
Oracle Server - Enterprise Edition - Version: 10.2.0.5 and later [Release: 10.2 and later ]
Information in this document applies to any platform.
Symptoms
Database alert_<ORACLE_SID>.log shows following error and keeps running:
Errors in file /u04/admin/njord/udump/njord_ora_25895.trc:
ORA-27300: OS system dependent operation:invalid_process_id failed with status: 0
ORA-27301: OS failure message: Error 0
ORA-27302: failure occurred at: skgpalive1
Changes
Applied 10.2.0.5 patch set.
Cause
This is caused by bug 10010310
Solution
bug 10010310
is fixed in 11.2.0.3, 12.1 and above. Please check patch 10010310
for existing interim patches.
References
BUG:10010310
- ORA-27300: INVALID_PROCESS_ID FAILED WITH STATUS: 0; ORA-27302: SKGPALIVE1
BUG:10154137
- ORA-27300: OS SYSTEM DEPENDENT OPERATION:INVALID_PROCESS_ID FAILED WITH STATUS 0
BUG:10207340
参考至:https://support.oracle.com/CSP/ui/flash.html#tab=KBHome%28page=KBHome&id=%28%29%29,%28page=KBNavigator&id=%28bmDocTitle=ORA-27300%20ORA-27301%20ORA-27302:%20failure%20occurred%20at:%20skgpalive1&bmDocType=PROBLEM&bmDocID=1252265.1&viewingMode=1143&bmDocDsrc=KB&from=BOOKMARK%29%29
本文原创,转载请注明出处、作者
如有错误,欢迎指正
邮箱:czmcj@163.com
分享到:
相关推荐
ORA-27302: failure occurred at: sskgpbitsper ``` 这里显示了由于系统信号量资源不足导致的错误,即“没有空间可用”。 **原因** 问题的根本原因在于系统信号量集(或信号量数组)的数量耗尽。虽然`kernel.sem`...
ORA-27302: failure occurred at: skgxpvfymmtu ORA-27303: additional information: MTU could not be verified. Did not receive valid message. These errors are caused by more aggressive checking ...
oracle远程连接服务器出现 ORA-12170 TNS:连接超时 解决办法,需要的朋友可以参考一下
在Oracle数据库系统中,"ORA-01036:非法的变量名/编号"是一个常见的错误,通常出现在PL/SQL代码或者SQL查询语句中,当你尝试使用一个不正确或者未定义的变量时,Oracle数据库会抛出这个错误。这个错误可能是由于...
ORA-00604: error occurred at recursive SQL level 1 ORA-14452: attempt to create, alter or drop an index on temporary table already in use ``` 这通常是因为有其他会话正在使用Goldengate用户的临时表。...
#### ORA-00104: Full Divisional Lockout Occurred 发生了完全部门锁定。这可能是由于并发控制机制的问题或锁管理器的问题。 #### ORA-00105: Dispatcher Not Found 未找到调度器。这可能是由于配置错误或服务管理...
报错如下 报错: ORA-12170:TNS connect timeout occurred 第一反应是监听没开: 1. 测试了一下, 连接超时没用ping 通 C:\Users\Administrator>tnsping brorcl TNS Ping Utility for 64-bit Windows: Version 11.2...
用myeclispe来连接oracle数据库时出现了如下错误: ORA-00604: error occurred at recursive SQL level 1 ORA-12705: Cannot access NLS data files or invalid environment specified
12 ORA‐00604: error occurred at recursive SQL level 2 13 ORA‐01555: snapshot too old: rollback segment number 7 with name 14 "_SYSSMU7_4222772309$" too small 15 Process ID: 1730 16 Session ID: 1996 ...
官网中关于ORA-12560的解释: ORA-12560: TNS:protocol adapter error Cause: A generic protocol adapter error occurred. Action: Check addresses used for proper protocol specification. Before reporting ...
在Red Hat Enterprise Linux Server Releae 5.5 成功安装ORACLE 10g 后,在客户端配置TNS后,测试是否可以连接到数据块服务器,结果报错:ORA-12170:TNS:连接超时
本篇文章是对ORA-12170 TNS 连接超时的解决办法进行了详细的分析介绍,需要的朋友参考下
#### ORA-00053: Lock timeout occurred - **解释**: 发生锁超时。 - **解决方案**: 优化锁管理或增加等待时间。 #### ORA-00054: Lock acquisition failed, NOWAIT specified - **解释**: 锁获取失败,指定了`NO...
- **故障现象**: 在安装RAC时,出现`ORA-00603: ORACLE servers session terminated by fatal error` 或 `ORA-29702: error occurred in Cluster Group Service operation`。 - **原因分析**: RAC的节点名出现在了...
ORA-00604: error occurred at recursive SQL level 1 ORA-01116: error in opening database file 1 ORA-01110: data file 1: '/u01/app/oracle/oradata/ora10g/system01.dbf' ORA-27041: unable to open file ...
在安装Real Application Clusters (RAC)时,出现错误提示ORA-00603: ORACLE servers session terminated by fatal error 或 ORA-29702: error occurred in Cluster Group Service operation。 **原因分析:** - RAC...
此错误的出现往往伴随着日志文件中的详细信息,例如:“ORA-1433: error occurred at row number...”。 #### 解决方案一:禁用表压缩 **步骤1:** 在源数据库中,找到引起问题的表,并执行命令以禁用其压缩功能。...
预定义异常是Oracle系统自动引发的,例如违反唯一性约束(ORA-0001)、超时错误(ORA-0051)或事务死锁(ORA-061)。这些异常通常与数据库操作相关,开发者无需显式定义,只需要在异常处理部分捕获并处理它们。 非...