ORA-32700: error occurred in DIAG Group Service

哎呀我的天吶發表於2015-07-15

SQL> alter database mount;
alter database mount
*
ERROR at line 1:
ORA-32700: error occurred in DIAG Group Service


SQL> exit
Disconnected from Oracle9i Enterprise Edition Release 9.2.0.6.0 - 64bit Production
With the Partitioning, Real Application Clusters, OLAP and Oracle Data Mining options
JServer Release 9.2.0.6.0 - Production
$ su - 
root's Password: 

# id
uid=0(root) gid=0(system) groups=2(bin),3(sys),7(security),8(cron),10(audit),11(lp)

# lsvg -o
rootvg
# lspv
hdisk0          00c8595263968b53                    rootvg          active
hdisk1          00c859521d9abab1                    rootvg          active
hdisk2          00c85952cb6d6531                    oradatavg       
hdisk3          002357abcb361aea                    oradatavg       
hdisk4          00c85952cb6d7403                    convg           
hdisk5          00c85952cb5e5b42                    oradatavg       
hdisk6          00c85952e05b6896                    oradatavg       
hdisk7          00c859529653674e                    oradatavg       
hdisk8          002357ab9a668d08                    None            
hdisk9          00c859522b37b7c9                    oradatavg       
hdisk10         00c8595261a25746                    oradatavg       
hdisk11         00c85952fbeeaa37                    None            
hdisk12         none                                None                      
# smit clstart


                                                                             Start Cluster Services


Type or select values in entry fields.
Press Enter AFTER making all desired changes.


                                                                 [Entry Fields]
* Start now, on system restart or both                now                                                                                                                     +
  Start Cluster Services on these nodes              [db1]                                                                                                                     +
* Manage Resource Groups                             Automatically                                                                                                           +
  BROADCAST message at startup?                       true                                                                                                                    +
  Startup Cluster Information Daemon?                 true                                                                                                                    +
  Ignore verification errors?                                 false                                                                                                                   +
  Automatically correct errors found during          Interactively                                                                                                           +
  cluster start?


                     
                                                  
F1=Help                                     F2=Refresh      +------------------------------------------------------+                F4=List
Esc+5=Reset                               Esc+6=Command   | Running command...                     |                Esc+8=Image
Esc+9=Shell                                Esc+0=Exit      +------------------------------------------------------+          
                                                                                 COMMAND STATUS


Command: running       stdout: yes           stderr: no


Before command completion, additional instructions may appear below.


clhaver[156]: cannot connect to node db2 rc=-1 errno=0
migcheck[471]: cl_connect() error, nodename=db2, rc=-1


WARNING: A communication error was encountered trying to get the VRMF from remote nodes. Please make sure clcomd is running
migcheck[471]: cl_connect() error, nodename=db2, rc=-1
[MORE...22]
The Disk Heartbeat on the node will not be checked. Make sure the node
is accessible.


rshexec: cannot connect to node db2
WARNING: fgets failed processing data for node db2
the VRM of installed cluster software.


Verifying Cluster Configuration Prior to Starting Cluster Services.
Successfully verified node(s): db1 


Starting Cluster Services on node: db1
This may take a few minutes.  Please wait...
migcheck[471]: cl_connect() error, nodename=db2, rc=-1
db1: start_cluster: Starting HACMP
db1: 0513-029 The portmap Subsystem is already active.
db1: Multiple instances are not supported.
db1: 0513-029 The inetd Subsystem is already active.
db1: Multiple instances are not supported.
db1:   25832      -  0:00 syslogd
db1: Setting routerevalidate to 1
db1: 0513-059 The topsvcs Subsystem has been started. Subsystem PID is 181298.
db1: 0513-059 The grpsvcs Subsystem has been started. Subsystem PID is 192964.
db1: 0513-059 The emsvcs Subsystem has been started. Subsystem PID is 193724.
db1: 0513-059 The emaixos Subsystem has been started. Subsystem PID is 197818.
db1: 0513-059 The gsclvmd Subsystem has been started. Subsystem PID is 177236.
db1: 0513-059 The clinfoES Subsystem has been started. Subsystem PID is 168732.
db1: Jul 14 2015 23:07:00 Starting execution of /usr/es/sbin/cluster/etc/rc.cluster
db1: with parameters: -boot -N -A -b -i -C interactive -P cl_rc_cluster
db1: 
db1: migcheck[471]: cl_connect() error, nodename=db2, rc=-1
db1: migcheck[471]: cl_connect() error, nodename=db2, rc=-1
db1: Jul 14 2015 23:07:20 Checking for srcmstr active...
db1: Jul 14 2015 23:07:20 complete.
db1: Jul 14 2015 23:07:21 
db1: /usr/es/sbin/cluster/utilities/clstart: called with flags -m -G -i -b -P cl_rc_cluster -C interactive -B -A
db1: 
db1:    Jul 14 2015 23:07:43
db1: Completed execution of /usr/es/sbin/cluster/etc/rc.cluster
db1: with parameters: -boot -N -A -b -i -C interactive -P cl_rc_cluster.
db1: Exit status = 0
db1: 


[BOTTOM]


                                                                                 COMMAND STATUS


Command: OK            stdout: yes           stderr: no


Before command completion, additional instructions may appear below.


[TOP]
clhaver[156]: cannot connect to node db2 rc=-1 errno=0
migcheck[471]: cl_connect() error, nodename=db2, rc=-1


WARNING: A communication error was encountered trying to get the VRMF from remote nodes. Please make sure clcomd is running
migcheck[471]: cl_connect() error, nodename=db2, rc=-1
migcheck[471]: cl_connect() error, nodename=db2, rc=-1


WARNING: A communication error was encountered trying to get the VRMF from remote nodes. Please make sure clcomd is running
rshexec: cannot connect to node db2


WARNING: Unable to contact node: db2 while attempting to gather
the VRM of installed cluster software.




Verifying Cluster Configuration Prior to Starting Cluster Services.


Verifying node(s): db1 against the running node db3rshexec: cannot connect to node db2
WARNING: Unable to communicate with the remote node: db2.
Please check that node: db2 has the /usr/es/sbin/cluster/etc/rhosts
file configured and the clcomdES subsystem running.
WARNING: db2 node is part of Disk Heartbeat Network: net_diskhbmulti_01,
however the node's data could not be collected for verification.
The Disk Heartbeat on the node will not be checked. Make sure the node
is accessible.


rshexec: cannot connect to node db2
WARNING: fgets failed processing data for node db2


Successfully verified node(s): db1


Starting Cluster Services on node: db1
This may take a few minutes.  Please wait...
migcheck[471]: cl_connect() error, nodename=db2, rc=-1
db1: start_cluster: Starting HACMP
db1: 0513-029 The portmap Subsystem is already active.
db1: Multiple instances are not supported.
db1: 0513-029 The inetd Subsystem is already active.
[MORE...25]


F1=Help                                     F2=Refresh                                  F3=Cancel                                   Esc+6=Command
Esc+8=Image                                 Esc+9=Shell                                 Esc+0=Exit                                  /=Find
n=Find Next                                                                                                         




# lspv
hdisk0          00c8595263968b53                    rootvg          active
hdisk1          00c859521d9abab1                    rootvg          active
hdisk2          00c85952cb6d6531                    oradatavg       concurrent
hdisk3          002357abcb361aea                    oradatavg       concurrent
hdisk4          00c85952cb6d7403                    convg           concurrent
hdisk5          00c85952cb5e5b42                    oradatavg       concurrent
hdisk6          00c85952e05b6896                    oradatavg       concurrent
hdisk7          00c859529653674e                    oradatavg       concurrent
hdisk8          002357ab9a668d08                    None            
hdisk9          00c859522b37b7c9                    oradatavg       concurrent
hdisk10         00c8595261a25746                    oradatavg       concurrent
hdisk11         00c85952fbeeaa37                    None            
hdisk12         none                                None            

# su - oracle
[YOU HAVE NEW MAIL]
$ sqlplus 


SQL*Plus: Release 9.2.0.6.0 - Production on Tue Jul 14 23:08:18 2015


Copyright (c) 1982, 2002, Oracle Corporation.  All rights reserved.


Enter user-name: / as sysdba


Connected to:
Oracle9i Enterprise Edition Release 9.2.0.6.0 - 64bit Production
With the Partitioning, Real Application Clusters, OLAP and Oracle Data Mining options
JServer Release 9.2.0.6.0 - Production


SQL> alter database mount;
alter database mount
*
ERROR at line 1:
ORA-32700: error occurred in DIAG Group Service




SQL> shutdown immediate;
ORA-01507: database not mounted


ORACLE instance shut down.
SQL> 
SQL> select status from v$instance;
select status from v$instance
*
ERROR at line 1:
ORA-01034: ORACLE not available
 
SQL> 
SQL> exit
Disconnected from Oracle9i Enterprise Edition Release 9.2.0.6.0 - 64bit Production
With the Partitioning, Real Application Clusters, OLAP and Oracle Data Mining options
JServer Release 9.2.0.6.0 - Production

$ sqlplus 


SQL*Plus: Release 9.2.0.6.0 - Production on Tue Jul 14 23:08:51 2015

Copyright (c) 1982, 2002, Oracle Corporation.  All rights reserved.

Enter user-name: / as sysdba
Connected to an idle instance.


SQL> startup;
ORACLE instance started.


Total System Global Area 1.5741E+10 bytes
Fixed Size                   765160 bytes
Variable Size            7348420608 bytes
Database Buffers         8388608000 bytes
Redo Buffers                3420160 bytes
Database mounted.
Database opened.
SQL> 
SQL> 
SQL> exit
Disconnected from Oracle9i Enterprise Edition Release 9.2.0.6.0 - 64bit Production
With the Partitioning, Real Application Clusters, OLAP and Oracle Data Mining options
JServer Release 9.2.0.6.0 - Production

$ lsnrctl


LSNRCTL for IBM/AIX RISC System/6000: Version 9.2.0.6.0 - Production on 14-JUL-2015 23:12:03


Copyright (c) 1991, 2002, Oracle Corporation.  All rights reserved.


Welcome to LSNRCTL, type "help" for information.


LSNRCTL> 
LSNRCTL> status
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=10.48.201.101)(PORT=9521)))
STATUS of the LISTENER
------------------------
Alias                     LISTENER
Version                   TNSLSNR for IBM/AIX RISC System/6000: Version 9.2.0.6.0 - Production
Start Date                14-JUL-2015 22:41:25
Uptime                    0 days 0 hr. 30 min. 39 sec
Trace Level               off
Security                  OFF
SNMP                      OFF
Listener Parameter File   /oracle/app/product/9.2.0.6/network/admin/listener.ora
Listener Log File         /oracle/app/product/9.2.0.6/network/log/listener.log
Listening Endpoints Summary...
  (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=10.48.201.101)(PORT=9521)))
  (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=loopback)(PORT=9521)))
  (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=loopback)(PORT=8080))(Presentation=HTTP)(Session=RAW))
  (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=loopback)(PORT=2100))(Presentation=FTP)(Session=RAW))
Services Summary...
Service "ORA91" has 1 instance(s).
  Instance "ORA91", status UNKNOWN, has 1 handler(s) for this service...
Service "ora9" has 1 instance(s).
  Instance "ora91", status READY, has 1 handler(s) for this service...
Service "ora9XDB" has 1 instance(s).
  Instance "ora91", status READY, has 1 handler(s) for this service...
The command completed successfully
LSNRCTL> 
LSNRCTL> exit

$ ps -ef | grep LOCAL=NO | grep -v grep | wc -l
     194

來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/29990276/viewspace-1734060/,如需轉載,請註明出處,否則將追究法律責任。

相關文章