Home > 主机 > scstat unexpected error问题及解决

scstat unexpected error问题及解决

最近一直很少更新博客,熟悉的朋友都知道,我在忙一个重要的release,Oracle Database 11g的第一个patchset – 11.1.0.7,这个patchset应该很快就要发布的,敬请期待。

今天在测试的时候,Solaris的节点再一次出现问题,最近服务器的问题不断,先是DLM问题,后面是QFS问题,现在居然是服务出现依赖关系,启动异常,SunCluster命令scstat返回异常结果:unexepcted error

根据google搜到的结果,在Sun的官方网站找到一个类似的问题

根据提示,检查一下svcs -x 的输出,
bash-2.05$ svcs -x
svc:/network/nfs/client:default (NFS client)
State: offline since August 25, 2008 10:33:46 PM PDT
Reason: Start method is running.
See: http://sun.com/msg/SMF-8000-C4
See: mount_nfs(1M)
See: /var/svc/log/network-nfs-client:default.log
Impact: 18 dependent services are not running. (Use -v for list.)

svc:/application/print/server:default (LP print server)
State: disabled since August 25, 2008 10:31:10 PM PDT
Reason: Disabled by an administrator.
See: http://sun.com/msg/SMF-8000-05
See: lpsched(1M)
Impact: 2 dependent services are not running. (Use -v for list.)

svc:/system/cluster/cl-svc-cluster-milestone:default (Synchronizing the cluster userland services)
State: disabled since August 25, 2008 10:32:38 PM PDT
Reason: Temporarily disabled by an administrator.
See: http://sun.com/msg/SMF-8000-1S
Impact: 1 dependent service is not running. (Use -v for list.)

svc:/application/stosreg:default (Service Tag OS Registry Inserter)
State: maintenance since August 25, 2008 10:33:39 PM PDT
Reason: Method failed.
See: http://sun.com/msg/SMF-8000-8Q
See: stclient(1M)
See: /var/svc/log/application-stosreg:default.log
Impact: This service is not running.

svc:/network/stdiscover:default (Service Tag discovery probe)
State: maintenance since August 25, 2008 10:33:45 PM PDT
Reason: Restarter svc:/network/inetd:default gave no explanation.
See: http://sun.com/msg/SMF-8000-9C
See: in.stdiscover(1M)
Impact: This service is not running.

svc:/network/stlisten:default (Service Tag Discovery Listener)
State: maintenance since August 25, 2008 10:33:45 PM PDT
Reason: Restarter svc:/network/inetd:default gave no explanation.
See: http://sun.com/msg/SMF-8000-9C
See: in.stlisten(1M)
Impact: This service is not running.
bash-2.05$

发现服务的依赖不对,启动console进入单用户模式,操作了几个服务,重新禁用和启用,重启,居然好了。
记录一下。

Categories: 主机 Tags:

7 Comments

  • At 2008.08.27 17:09, Breeze said:

    Ricky: 我在11.0.6 windows平台下面发现一个非常严重的bug–就是大量未绑定变量sql解析时,经常报ora-600错误,导致sql无法执行。不知11.0.7中解决没有.
    这错误,应存在于任何平台.

    • At 2008.08.27 20:10, ricky.zhu said:

      1. 确认是bug吗?bug number是多少。有没有提交SR
      2. 为绑定变量sql解析可能会有性能问题,但是600错误就不清楚,具体错误信息是什么?
      3. 你说的应用于任何平台,有何依据吗?

    • At 2008.09.01 15:36, Breeze said:

      1.我想应该是bug,正准备使用11g,测试发现这个问题。不敢使用.
      测试也有方式提交SR?
      2.具体的信息:
      ORA-00600: 内部错误代码, 参数: [kcbz_find_bpid_3], [7], [], [], [], [], [], []

      ========= Dump for incident 61317 (ORA 600 [kcbz_find_bpid_3]) ========

      *** 2008-08-30 17:15:04.757
      —– Current SQL Statement for this session (sql_id=372ncv5zpw4kk) —–
      SELECT COUNT(*) FROM TRAY_INFO WHERE TRAY_NO= (SELECT DISTINCT TRAY_NO FROM TRAY_DETAIL WHERE CELL_NAME IN (SELECT CELL_NAME FROM TEST_CELLS1 WHERE FILE_NAME=:B1 ) ) AND TRAY_STATE!=’FINISHED’
      —– PL/SQL Stack —–
      —– PL/SQL Call Stack —–
      object line object
      handle number name
      4336BA60 213 package body FORMAT.EXECUTE_DTS
      4319B650 1 anonymous block

      —– Call Stack Trace —–
      calling call entry argument values in hex
      location type point (? means dubious value)
      ——————– ——– ——————– —————————-
      _skdstdst()+114 CALLrel _kgdsdst()+0 5BCC1BF4 2
      _ksedst1()+91 CALLrel _skdstdst()+0
      _ksedst()+50 CALLrel _ksedst1()+0 0 1
      _dbkedDefDump()+298 CALLrel _ksedst()+0 0
      5
      ……
      不知对你有用否?

      • At 2008.09.01 16:23, ricky.zhu said:

        yes, you are correct, it’s a bug: number is 7019643, which will be fixed in 11.2 and on 11.1.0.6, you can apply patch

      • At 2008.09.03 13:32, Breeze said:

        Ricky,我正在测试,没买license如何得到这个patch呢?

        • At 2009.01.15 14:55, zf_wu said:

          Ricky,11.1.0.7解决了这个问题没有?

          • At 2009.01.15 23:23, ricky.zhu said:

            不知道你说的是哪个问题,上面那个bug?在11.1.0.7已经fix的了

        (Required)
        (Required, will not be published)