sitemap

RSS地图

收藏本站

设为首页

Oracle研究中心

当前位置:Oracle研究中心 > 故障案例 >

【案例】Oracle数据库在solaris安装11G报错INS-30131 MOS解决办法

时间:2016-10-29 17:12   来源:Oracle研究中心   作者:HTZ   点击:

天萃荷净 Oracle研究中心案例分析:运维DBA反映在Solaris系统上安装Oracle1 11G时遇到报错INS-30131,结合MOS官方的解决办法为系统配置异常导致。
在solaris 10安装oracle 11.2.0.4,在检查一步出现下面的报错

下面是debug时的输出信息
Exectask version couldn’t be fetched from node: solaris
debug
ommand@4532b038
[pool-1-thread-1] [ 2014-08-23 20:01:52.429 CST ] [ClusterException.setErrorMessage:153] ClusterException.setErrorMessage: errString is ‘couldn’t set locale correctly|couldn’t set locale correctly|couldn’t set locale correctly|couldn’t set locale correctly|couldn’t set locale correctly’
[pool-1-thread-1] [ 2014-08-23 20:01:52.429 CST ] [ClusterException.setErrorMessage:163] ClusterException.setErrorMessage: errString is ‘couldn’t set locale correctly
couldn’t set locale correctly
couldn’t set locale correctly
couldn’t set locale correctly
couldn’t set locale correctly’
[pool-1-thread-1] [ 2014-08-23 20:01:52.429 CST ] [ClusterConfig.destroy:452] destroying resources for client thread Thread[pool-1-thread-1,5,main]
[pool-1-thread-1] [ 2014-08-23 20:01:52.430 CST ] [GlobalHandler.submit:172] GlobalHandler::EXCEPTION: ClusterException[Thread:pool-1-thread-1]: couldn’t set locale correctly|couldn’t set locale correctly|couldn’t set locale correctly|couldn’t set locale correctly|couldn’t set locale correctlycouldn’t set locale correctly
couldn’t set locale correctly
Oracleoracleplus.net
couldn’t set locale correctly
couldn’t set locale correctly
couldn’t set locale correctly
[pool-1-thread-1] [ 2014-08-23 20:01:52.430 CST ] [GlobalExecution.dumpTraceInfo:938] —- Execution Trace for getExectaskVer from node: solaris —–
[pool-1-thread-1] [ 2014-08-23 20:01:52.430 CST ] [GlobalExecution.dumpTraceInfo:946] ::Inside execute()
[pool-1-thread-1] [ 2014-08-23 20:01:52.430 CST ] [GlobalExecution.dumpTraceInfo:946] super.execute() failed for GetExectaskVerCommand…
[pool-1-thread-1] [ 2014-08-23 20:01:52.430 CST ] [VerificationUtil.checkDestLoc:4097] VerificationUtil:: getExectaskVer() performed!!
[pool-1-thread-1] [ 2014-08-23 20:01:52.430 CST ] [VerificationUtil.checkGetExectaskVerResults:4844] Exectask version couldn’t be fetched from node: solaris
[pool-1-thread-1] [ 2014-08-23 20:01:52.431 CST ] [ResultSet.traceResultSet:359]

Before return from checkDestLoc with #succNodes=0;#failNodes=1;#nodes=1
Overall Status->OPERATION_FAILED

solaris–>OPERATION_FAILED


[Worker 2] [ 2014-08-23 20:01:52.537 CST ] [ClusterConfig$ExecuteCommand.run:3069] Released Semaphore by worker=Worker 2
[Worker 2] [ 2014-08-23 20:01:52.537 CST ] [Semaphore.acquire:109] SyncBufferFull:Acquire called by thread Worker 2 m_count=0

1,修改temp目录

查看tmp目录的权限是正常的,修改tmp,temp,tmpdir目录到/oracle/temp后故障现象仍然存在。并且也检查了其它的配置信息,无任何错误

2,禁用JAVA桌面

禁用java桌面,启用cde桌面后,验证正常。
本文固定链接: http://www.htz.pw/2014/08/24/ins-30131-solaris-10%e5%ae%89%e8%a3%8511-2-0-4%e6%8a%a5%e9%94%99.html | 认真就输

--------------------------------------ORACLE-DBA----------------------------------------

最权威、专业的Oracle案例资源汇总之【案例】Oracle数据库在solaris安装11G报错INS-30131 MOS解决办法

本文由大师惜分飞原创分享,网址:http://www.oracleplus.net/arch/1103.html

Oracle研究中心

关键词:

INS-30131

solaris 10安装11.2.0.4报错INS-30131原因和解决办法

Oracle 11G在solaris安装时报错INS-30131