Installing First cluster node cluster service offline

Hi ,
While i'm trying to install the first cluster node on Node1 cluster disk shows online but the cluster service shows offline .
as shown below in the screenshot .
I have  run the prerequisite checker on both the nodes but  it was successful kindly give your input to resolve this issue 

you are performing this actions as a domain administrator?
If not repeat the stuff you want to perform as domain administrator.
kind regards
Peter

Similar Messages

  • Error while installing Oracle Cluster Ready Services – Release 1 (10.1.0.2)

    Hi all,
    I am trying for RAC – 10gR1 (10.1.0.2) using two machines with Windows 2000 Server. For this I need to install Oracle Cluster Ready Services – Release 1 (10.1.0.2).
    Machine details are as follows:-
    Node 1:
    Computer Name:     RAC1
    Windows 2000 IP Configuration
    Ethernet adapter Local Area Connection 2: (Used for Public Interface)
    Connection-specific DNS Suffix . :
    IP Address. . . . . . . . . . . . : 192.168.1.65
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Default Gateway . . . . . . . . . :
    Ethernet adapter Local Area Connection: (Used for Private Interface between the two nodes)
    Connection-specific DNS Suffix . :
    IP Address. . . . . . . . . . . . : 10.10.10.11
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Default Gateway . . . . . . . . . :
    Node 2:
         Computer Name:     RAC2
    Windows 2000 IP Configuration
    Ethernet adapter Local Area Connection 2: (Used for Public Interface)
    Connection-specific DNS Suffix . :
    IP Address. . . . . . . . . . . . : 192.168.1.181
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Default Gateway . . . . . . . . . :
    Ethernet adapter Local Area Connection: (Used for Private Interface between the two nodes)
    Connection-specific DNS Suffix . :
    IP Address. . . . . . . . . . . . : 10.10.10.12
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Default Gateway . . . . . . . . . :
    I have made following entries in Hosts file of both the machines:-
    192.168.1.65     RAC1
    192.168.1.181     RAC2
    10.10.10.11     RAC01-PRIV
    10.10.10.12     RAC02-PRIV
    192.168.1.201     RAC01-VIP
    192.168.1.202     RAC02-VIP
    I have completed all the pre-installation steps, i.e. configuring the disk for storage, and both the machine are communicating each other through there Private and Public interfaces. Now the problem appears when I am installing Oracle Cluster Ready Services, at the end of Installation following message appears and the auto configuration steps fails.
    ================================================================================================================
    Output generated from configuration assistant "Oracle Cluster Ready Services Configuration Assistant":
    Successfully accumulated necessary OCR keys.
    Using ports: CSS=49895 CRS=49896 EVMC=49898 and EVMR=49897.
    node <nodenumber>: <nodename> <private interconnect name> <hostname>
    node 1: rac1 rac01-priv rac1
    node 2: rac2 rac02-priv rac2
    Creating OCR keys for user 'administrator', privgrp ''..
    Operation successful.
    Now formatting voting device: \\.\votedsk
    Successful in setting block0 for voting disk.
    Format complete.
    Step 1: checking status of CRS cluster
    Step 2: configuring OCR repository
    Step 3: configuring safe mode for CRS stack
    Step 4: Starting up CRS stack on all nodes
    RAC1 service OracleCSService in improper PENDING state, err(997)
    RAC2 service OracleCSService in improper PENDING state, err(997)
    Configuration assistant "Oracle Cluster Ready Services Configuration Assistant" failed
    ================================================================================================================
    Output generated from configuration assistant "Oracle Notification Server Configuration Assistant":
    Configuration assistant "Oracle Notification Server Configuration Assistant" failed
    ================================================================================================================
    Output generated from configuration assistant "Oracle Private Interconnect Configuration Assistant":
    PRIF-10: failed to initialize the cluster registry
    Configuration assistant "Oracle Private Interconnect Configuration Assistant" failed
    ===============================================================
    I would be highly obliged if any one tell me why it is happing like this and what could be the possible remedy.
    Waiting for the respone.
    With Regards
    Dinesh
    [email protected]

    Hi user478171,
    I have the same problem with two nodes in Windows 2003 with RAC 10g R2, but I don't have idea to solve.
    Please advice me
    Thanks advances
    regards,
    IvanR

  • Pre-check for cluster services setup was unsuccessful on all the nodes.

    hi
    when i am running the fixup script getting:
    if i run cluvfy again i am getting another fixup script.what exactly to do?
    [root@rac-1 grid1]# sh /tmp/CVU_11.2.0.1.0_grid1/runfixup.sh
    Response file being used is :/tmp/CVU_11.2.0.1.0_grid1/fixup.response
    Enable file being used is :/tmp/CVU_11.2.0.1.0_grid1/fixup.enable
    Log file location: /tmp/CVU_11.2.0.1.0_grid1/orarun.log
    uid=1100(grid1) gid=1000(oinstall) groups=1000(oinstall),1100(dba),1200(asmdba),1300(asmadmin),1202(asmoper)
    grid1     hard    nproc    16384
    Value of MAX PROCESSES HARDLIMIT in response file is not greater than value in/etc/security/limits.conf. Hence not changing it.
    grid1     hard    nofile   65536
    Value of FILE OPEN MAX HARDLIMIT in response file is not greater than value in /etc/security/limits.conf.Hence not changing it.
    uid=1100(grid1) gid=1000(oinstall) groups=1000(oinstall),1100(dba),1200(asmdba),1300(asmadmin),1202(asmoper)
    [root@rac-1 grid1]#
    Performing pre-checks for cluster services setup
    Checking node reachability...
    Check: Node reachability from node "rac-1"
      Destination Node                      Reachable?             
      rac-2                                 yes                    
      rac-1                                 yes                    
    Result: Node reachability check passed from node "rac-1"
    Checking user equivalence...
    Check: User equivalence for user "grid1"
      Node Name                             Comment                
      rac-2                                 passed                 
      rac-1                                 passed                 
    Result: User equivalence check passed for user "grid1"
    Checking node connectivity...
    Checking hosts config file...
      Node Name     Status                    Comment                
      rac-2         passed                                           
      rac-1         passed                                           
    Verification of the hosts config file successful
    Interface information for node "rac-2"
    Name   IP Address      Subnet          Gateway         Def. Gateway    HW Address        MTU  
    eth0   192.168.1.3     192.168.1.0     0.0.0.0         192.168.1.1     00:1D:72:39:3A:E4 1500 
    virbr0 192.168.122.1   192.168.122.0   0.0.0.0         192.168.1.1     00:00:00:00:00:00 1500 
    eth1   192.168.181.20  192.168.181.0   0.0.0.0         192.168.1.1     00:00:00:00:00:00 1500 
    Interface information for node "rac-1"
    Name   IP Address      Subnet          Gateway         Def. Gateway    HW Address        MTU  
    eth0   192.168.1.2     192.168.1.0     0.0.0.0         192.168.1.1     00:00:E8:F7:02:B0 1500 
    eth1   192.168.181.10  192.168.181.0   0.0.0.0         192.168.1.1     00:26:18:59:EE:49 1500 
    virbr0 192.168.122.1   192.168.122.0   0.0.0.0         192.168.1.1     00:00:00:00:00:00 1500 
    Check: Node connectivity of subnet "192.168.1.0"
      Source                          Destination                     Connected?     
      rac-2:eth0                      rac-1:eth0                      yes            
    Result: Node connectivity passed for subnet "192.168.1.0" with node(s) rac-2,rac-1
    Check: TCP connectivity of subnet "192.168.1.0"
      Source                          Destination                     Connected?     
      rac-1:192.168.1.2               rac-2:192.168.1.3               passed         
    Result: TCP connectivity check passed for subnet "192.168.1.0"
    Check: Node connectivity of subnet "192.168.122.0"
      Source                          Destination                     Connected?     
      rac-2:virbr0                    rac-1:virbr0                    yes            
    Result: Node connectivity passed for subnet "192.168.122.0" with node(s) rac-2,rac-1
    Check: TCP connectivity of subnet "192.168.122.0"
    Result: TCP connectivity check failed for subnet "192.168.122.0"
    Check: Node connectivity of subnet "192.168.181.0"
      Source                          Destination                     Connected?     
      rac-2:eth1                      rac-1:eth1                      yes            
    Result: Node connectivity passed for subnet "192.168.181.0" with node(s) rac-2,rac-1
    Check: TCP connectivity of subnet "192.168.181.0"
      Source                          Destination                     Connected?     
      rac-1:192.168.181.10            rac-2:192.168.181.20            passed         
    Result: TCP connectivity check passed for subnet "192.168.181.0"
    Interfaces found on subnet "192.168.1.0" that are likely candidates for VIP are:
    rac-2 eth0:192.168.1.3
    rac-1 eth0:192.168.1.2
    Interfaces found on subnet "192.168.122.0" that are likely candidates for a private interconnect are:
    rac-2 virbr0:192.168.122.1
    rac-1 virbr0:192.168.122.1
    Interfaces found on subnet "192.168.181.0" that are likely candidates for a private interconnect are:
    rac-2 eth1:192.168.181.20
    rac-1 eth1:192.168.181.10
    Result: Node connectivity check passed
    Check: Total memory
      Node Name     Available                 Required                  Comment  
      rac-2         1.96GB (2050416.0KB)      1.5GB (1572864.0KB)       passed   
      rac-1         1.96GB (2058984.0KB)      1.5GB (1572864.0KB)       passed   
    Result: Total memory check passed
    Check: Available memory
      Node Name     Available                 Required                  Comment  
      rac-2         1.7GB (1780600.0KB)       50MB (51200.0KB)          passed   
      rac-1         1.56GB (1636896.0KB)      50MB (51200.0KB)          passed   
    Result: Available memory check passed
    Check: Swap space
      Node Name     Available                 Required                  Comment  
      rac-2         4GB (4194296.0KB)         2.93GB (3075624.0KB)      passed   
      rac-1         4GB (4192956.0KB)         2.95GB (3088476.0KB)      passed   
    Result: Swap space check passed
    Check: Free disk space for "rac-2:/tmp"
      Path              Node Name     Mount point   Available     Required      Comment    
      /tmp              rac-2         /             24.03GB       1GB           passed     
    Result: Free disk space check passed for "rac-2:/tmp"
    Check: Free disk space for "rac-1:/tmp"
      Path              Node Name     Mount point   Available     Required      Comment    
      /tmp              rac-1         /             16.54GB       1GB           passed     
    Result: Free disk space check passed for "rac-1:/tmp"
    Check: User existence for "grid1"
      Node Name     Status                    Comment                
      rac-2         exists                    passed                 
      rac-1         exists                    passed                 
    Result: User existence check passed for "grid1"
    Check: Group existence for "oinstall"
      Node Name     Status                    Comment                
      rac-2         exists                    passed                 
      rac-1         exists                    passed                 
    Result: Group existence check passed for "oinstall"
    Check: Group existence for "dba"
      Node Name     Status                    Comment                
      rac-2         exists                    passed                 
      rac-1         exists                    passed                 
    Result: Group existence check passed for "dba"
    Check: Membership of user "grid1" in group "oinstall" [as Primary]
      Node Name         User Exists   Group Exists  User in Group  Primary       Comment    
      rac-2             yes           yes           yes           yes           passed     
      rac-1             yes           yes           yes           yes           passed     
    Result: Membership check for user "grid1" in group "oinstall" [as Primary] passed
    Check: Membership of user "grid1" in group "dba"
      Node Name         User Exists   Group Exists  User in Group  Comment        
      rac-2             yes           yes           no            failed         
      rac-1             yes           yes           yes           passed         
    Result: Membership check for user "grid1" in group "dba" failed
    Check: Run level
      Node Name     run level                 Required                  Comment  
      rac-2         5                         3,5                       passed   
      rac-1         5                         3,5                       passed   
    Result: Run level check passed
    Check: Hard limits for "maximum open file descriptors"
      Node Name         Type          Available     Required      Comment        
      rac-2             hard          65536         65536         passed         
      rac-1             hard          65536         65536         passed         
    Result: Hard limits check passed for "maximum open file descriptors"
    Check: Soft limits for "maximum open file descriptors"
      Node Name         Type          Available     Required      Comment        
      rac-2             soft          1024          1024          passed         
      rac-1             soft          65536         1024          passed         
    Result: Soft limits check passed for "maximum open file descriptors"
    Check: Hard limits for "maximum user processes"
      Node Name         Type          Available     Required      Comment        
      rac-2             hard          16384         16384         passed         
      rac-1             hard          16384         16384         passed         
    Result: Hard limits check passed for "maximum user processes"
    Check: Soft limits for "maximum user processes"
      Node Name         Type          Available     Required      Comment        
      rac-2             soft          2047          2047          passed         
      rac-1             soft          16384         2047          passed         
    Result: Soft limits check passed for "maximum user processes"
    Check: System architecture
      Node Name     Available                 Required                  Comment  
      rac-2         x86_64                    x86_64                    passed   
      rac-1         x86_64                    x86_64                    passed   
    Result: System architecture check passed
    Check: Kernel version
      Node Name     Available                 Required                  Comment  
      rac-2         2.6.18-92.el5             2.6.18                    passed   
      rac-1         2.6.18-164.el5            2.6.18                    passed   
    WARNING:
    PRVF-7524 : Kernel version is not consistent across all the nodes.
    Kernel version = "2.6.18-164.el5" found on nodes: rac-1.
    Kernel version = "2.6.18-92.el5" found on nodes: rac-2.
    Result: Kernel version check passed
    Check: Kernel parameter for "semmsl"
      Node Name     Configured                Required                  Comment  
      rac-2         250                       250                       passed   
      rac-1         250                       250                       passed   
    Result: Kernel parameter check passed for "semmsl"
    Check: Kernel parameter for "semmns"
      Node Name     Configured                Required                  Comment  
      rac-2         32000                     32000                     passed   
      rac-1         32000                     32000                     passed   
    Result: Kernel parameter check passed for "semmns"
    Check: Kernel parameter for "semopm"
      Node Name     Configured                Required                  Comment  
      rac-2         100                       100                       passed   
      rac-1         100                       100                       passed   
    Result: Kernel parameter check passed for "semopm"
    Check: Kernel parameter for "semmni"
      Node Name     Configured                Required                  Comment  
      rac-2         142                       128                       passed   
      rac-1         142                       128                       passed   
    Result: Kernel parameter check passed for "semmni"
    Check: Kernel parameter for "shmmax"
      Node Name     Configured                Required                  Comment  
      rac-2         1049812992                536870912                 passed   
      rac-1         4398046511104             536870912                 passed   
    Result: Kernel parameter check passed for "shmmax"
    Check: Kernel parameter for "shmmni"
      Node Name     Configured                Required                  Comment  
      rac-2         4096                      4096                      passed   
      rac-1         4096                      4096                      passed   
    Result: Kernel parameter check passed for "shmmni"
    Check: Kernel parameter for "shmall"
      Node Name     Configured                Required                  Comment  
      rac-2         3279547                   2097152                   passed   
      rac-1         1073741824                2097152                   passed   
    Result: Kernel parameter check passed for "shmall"
    Check: Kernel parameter for "file-max"
      Node Name     Configured                Required                  Comment  
      rac-2         6815744                   6815744                   passed   
      rac-1         6815744                   6815744                   passed   
    Result: Kernel parameter check passed for "file-max"
    Check: Kernel parameter for "ip_local_port_range"
      Node Name     Configured                Required                  Comment  
      rac-2         between 9000 & 65500      between 9000 & 65500      passed   
      rac-1         between 9000 & 65500      between 9000 & 65500      passed   
    Result: Kernel parameter check passed for "ip_local_port_range"
    Check: Kernel parameter for "rmem_default"
      Node Name     Configured                Required                  Comment  
      rac-2         262144                    262144                    passed   
      rac-1         4194304                   262144                    passed   
    Result: Kernel parameter check passed for "rmem_default"
    Check: Kernel parameter for "rmem_max"
      Node Name     Configured                Required                  Comment  
      rac-2         4194304                   4194304                   passed   
      rac-1         4194304                   4194304                   passed   
    Result: Kernel parameter check passed for "rmem_max"
    Check: Kernel parameter for "wmem_default"
      Node Name     Configured                Required                  Comment  
      rac-2         262144                    262144                    passed   
      rac-1         262144                    262144                    passed   
    Result: Kernel parameter check passed for "wmem_default"
    Check: Kernel parameter for "wmem_max"
      Node Name     Configured                Required                  Comment  
      rac-2         1048576                   1048576                   passed   
      rac-1         1048576                   1048576                   passed   
    Result: Kernel parameter check passed for "wmem_max"
    Check: Kernel parameter for "aio-max-nr"
      Node Name     Configured                Required                  Comment  
      rac-2         3145728                   1048576                   passed   
      rac-1         3145728                   1048576                   passed   
    Result: Kernel parameter check passed for "aio-max-nr"
    Check: Package existence for "ocfs2-tools-1.2.7"
      Node Name     Available                 Required                  Comment  
      rac-2         ocfs2-tools-1.2.7-1.el5   ocfs2-tools-1.2.7         passed   
      rac-1         ocfs2-tools-1.4.2-1.el5   ocfs2-tools-1.2.7         passed   
    Result: Package existence check passed for "ocfs2-tools-1.2.7"
    Check: Package existence for "make-3.81"
      Node Name     Available                 Required                  Comment  
      rac-2         make-3.81-3.el5           make-3.81                 passed   
      rac-1         make-3.81-3.el5           make-3.81                 passed   
    Result: Package existence check passed for "make-3.81"
    Check: Package existence for "binutils-2.17.50.0.6"
      Node Name     Available                 Required                  Comment  
      rac-2         binutils-2.17.50.0.6-6.el5  binutils-2.17.50.0.6      passed   
      rac-1         binutils-2.17.50.0.6-12.el5  binutils-2.17.50.0.6      passed   
    Result: Package existence check passed for "binutils-2.17.50.0.6"
    Check: Package existence for "gcc-4.1.2"
      Node Name     Available                 Required                  Comment  
      rac-2         gcc-4.1.2-42.el5          gcc-4.1.2                 passed   
      rac-1         gcc-4.1.2-46.el5          gcc-4.1.2                 passed   
    Result: Package existence check passed for "gcc-4.1.2"
    Check: Package existence for "libaio-0.3.106 (i386)"
      Node Name     Available                 Required                  Comment  
      rac-2         libaio-0.3.106-3.2 (i386)  libaio-0.3.106 (i386)     passed   
      rac-1         libaio-0.3.106-3.2 (i386)  libaio-0.3.106 (i386)     passed   
    Result: Package existence check passed for "libaio-0.3.106 (i386)"
    Check: Package existence for "libaio-0.3.106 (x86_64)"
      Node Name     Available                 Required                  Comment  
      rac-2         libaio-0.3.106-3.2 (x86_64)  libaio-0.3.106 (x86_64)   passed   
      rac-1         libaio-0.3.106-3.2 (x86_64)  libaio-0.3.106 (x86_64)   passed   
    Result: Package existence check passed for "libaio-0.3.106 (x86_64)"
    Check: Package existence for "glibc-2.5-24 (i686)"
      Node Name     Available                 Required                  Comment  
      rac-2         glibc-2.5-24 (i686)       glibc-2.5-24 (i686)       passed   
      rac-1         glibc-2.5-42 (i686)       glibc-2.5-24 (i686)       passed   
    Result: Package existence check passed for "glibc-2.5-24 (i686)"
    Check: Package existence for "glibc-2.5-24 (x86_64)"
      Node Name     Available                 Required                  Comment  
      rac-2         glibc-2.5-24 (x86_64)     glibc-2.5-24 (x86_64)     passed   
      rac-1         glibc-2.5-42 (x86_64)     glibc-2.5-24 (x86_64)     passed   
    Result: Package existence check passed for "glibc-2.5-24 (x86_64)"
    Check: Package existence for "compat-libstdc++-33-3.2.3 (i386)"
      Node Name     Available                 Required                  Comment  
      rac-2         compat-libstdc++-33-3.2.3-61 (i386)  compat-libstdc++-33-3.2.3 (i386)  passed   
      rac-1         compat-libstdc++-33-3.2.3-61 (i386)  compat-libstdc++-33-3.2.3 (i386)  passed   
    Result: Package existence check passed for "compat-libstdc++-33-3.2.3 (i386)"
    Check: Package existence for "compat-libstdc++-33-3.2.3 (x86_64)"
      Node Name     Available                 Required                  Comment  
      rac-2         compat-libstdc++-33-3.2.3-61 (x86_64)  compat-libstdc++-33-3.2.3 (x86_64)  passed   
      rac-1         compat-libstdc++-33-3.2.3-61 (x86_64)  compat-libstdc++-33-3.2.3 (x86_64)  passed   
    Result: Package existence check passed for "compat-libstdc++-33-3.2.3 (x86_64)"
    Check: Package existence for "elfutils-libelf-0.125 (x86_64)"
      Node Name     Available                 Required                  Comment  
      rac-2         elfutils-libelf-0.125-3.el5 (x86_64)  elfutils-libelf-0.125 (x86_64)  passed   
      rac-1         elfutils-libelf-0.137-3.el5 (x86_64)  elfutils-libelf-0.125 (x86_64)  passed   
    Result: Package existence check passed for "elfutils-libelf-0.125 (x86_64)"
    Check: Package existence for "elfutils-libelf-devel-0.125"
      Node Name     Available                 Required                  Comment  
      rac-2         elfutils-libelf-devel-0.125-3.el5  elfutils-libelf-devel-0.125  passed   
      rac-1         elfutils-libelf-devel-0.137-3.el5  elfutils-libelf-devel-0.125  passed   
    Result: Package existence check passed for "elfutils-libelf-devel-0.125"
    Check: Package existence for "glibc-common-2.5"
      Node Name     Available                 Required                  Comment  
      rac-2         glibc-common-2.5-24       glibc-common-2.5          passed   
      rac-1         glibc-common-2.5-42       glibc-common-2.5          passed   
    Result: Package existence check passed for "glibc-common-2.5"
    Check: Package existence for "glibc-devel-2.5 (i386)"
      Node Name     Available                 Required                  Comment  
      rac-2         glibc-devel-2.5-24 (i386)  glibc-devel-2.5 (i386)    passed   
      rac-1         glibc-devel-2.5-42 (i386)  glibc-devel-2.5 (i386)    passed   
    Result: Package existence check passed for "glibc-devel-2.5 (i386)"
    Check: Package existence for "glibc-devel-2.5 (x86_64)"
      Node Name     Available                 Required                  Comment  
      rac-2         glibc-devel-2.5-24 (x86_64)  glibc-devel-2.5 (x86_64)  passed   
      rac-1         glibc-devel-2.5-42 (x86_64)  glibc-devel-2.5 (x86_64)  passed   
    Result: Package existence check passed for "glibc-devel-2.5 (x86_64)"
    Check: Package existence for "glibc-headers-2.5"
      Node Name     Available                 Required                  Comment  
      rac-2         glibc-headers-2.5-24      glibc-headers-2.5         passed   
      rac-1         glibc-headers-2.5-42      glibc-headers-2.5         passed   
    Result: Package existence check passed for "glibc-headers-2.5"
    Check: Package existence for "gcc-c++-4.1.2"
      Node Name     Available                 Required                  Comment  
      rac-2         gcc-c++-4.1.2-42.el5      gcc-c++-4.1.2             passed   
      rac-1         gcc-c++-4.1.2-46.el5      gcc-c++-4.1.2             passed   
    Result: Package existence check passed for "gcc-c++-4.1.2"
    Check: Package existence for "libaio-devel-0.3.106 (i386)"
      Node Name     Available                 Required                  Comment  
      rac-2         libaio-devel-0.3.106-3.2 (i386)  libaio-devel-0.3.106 (i386)  passed   
      rac-1         libaio-devel-0.3.106-3.2 (i386)  libaio-devel-0.3.106 (i386)  passed   
    Result: Package existence check passed for "libaio-devel-0.3.106 (i386)"
    Check: Package existence for "libaio-devel-0.3.106 (x86_64)"
      Node Name     Available                 Required                  Comment  
      rac-2         libaio-devel-0.3.106-3.2 (x86_64)  libaio-devel-0.3.106 (x86_64)  passed   
      rac-1         libaio-devel-0.3.106-3.2 (x86_64)  libaio-devel-0.3.106 (x86_64)  passed   
    Result: Package existence check passed for "libaio-devel-0.3.106 (x86_64)"
    Check: Package existence for "libgcc-4.1.2 (i386)"
      Node Name     Available                 Required                  Comment  
      rac-2         libgcc-4.1.2-42.el5 (i386)  libgcc-4.1.2 (i386)       passed   
      rac-1         libgcc-4.1.2-46.el5 (i386)  libgcc-4.1.2 (i386)       passed   
    Result: Package existence check passed for "libgcc-4.1.2 (i386)"
    Check: Package existence for "libgcc-4.1.2 (x86_64)"
      Node Name     Available                 Required                  Comment  
      rac-2         libgcc-4.1.2-42.el5 (x86_64)  libgcc-4.1.2 (x86_64)     passed   
      rac-1         libgcc-4.1.2-46.el5 (x86_64)  libgcc-4.1.2 (x86_64)     passed   
    Result: Package existence check passed for "libgcc-4.1.2 (x86_64)"
    Check: Package existence for "libstdc++-4.1.2 (i386)"
      Node Name     Available                 Required                  Comment  
      rac-2         libstdc++-4.1.2-42.el5 (i386)  libstdc++-4.1.2 (i386)    passed   
      rac-1         libstdc++-4.1.2-46.el5 (i386)  libstdc++-4.1.2 (i386)    passed   
    Result: Package existence check passed for "libstdc++-4.1.2 (i386)"
    Check: Package existence for "libstdc++-4.1.2 (x86_64)"
      Node Name     Available                 Required                  Comment  
      rac-2         libstdc++-4.1.2-42.el5 (x86_64)  libstdc++-4.1.2 (x86_64)  passed   
      rac-1         libstdc++-4.1.2-46.el5 (x86_64)  libstdc++-4.1.2 (x86_64)  passed   
    Result: Package existence check passed for "libstdc++-4.1.2 (x86_64)"
    Check: Package existence for "libstdc++-devel-4.1.2 (x86_64)"
      Node Name     Available                 Required                  Comment  
      rac-2         libstdc++-devel-4.1.2-42.el5 (x86_64)  libstdc++-devel-4.1.2 (x86_64)  passed   
      rac-1         libstdc++-devel-4.1.2-46.el5 (x86_64)  libstdc++-devel-4.1.2 (x86_64)  passed   
    Result: Package existence check passed for "libstdc++-devel-4.1.2 (x86_64)"
    Check: Package existence for "sysstat-7.0.2"
      Node Name     Available                 Required                  Comment  
      rac-2         sysstat-7.0.2-1.el5       sysstat-7.0.2

    In both node oracle user & group should be same but in your case looks different.
    Once again check your user & group.
    Babu

  • Cluster service is requested to stop on all nodes when DNS is unavailable

    Our 6 node coherence cluster has been running fine for few days. All coherence nodes were requested to stop the cluster service when the DNS server was not available for few mins due to a scheduled maintenance activity. Cluster services didn’t come back up until the DNS server is available. Why would it need a DNS server when the cluster is already started and running fine for few days?
    Here’s the error message and thread dump from the logs:
    2010-12-18 18:07:18.819/3464791.277 Oracle Coherence GE 3.6.0.3 <Error> (thread=IpMonitor, member=7): Detected hard timeout) of {WrapperGuardable Guard{Daemon=Cluster} Service=ClusterService{Name=Cluster, State=(SERVICE_STARTED, STATE_JOINED), Id=0, Version=3.6, OldestMemberId=5}}
    2010-12-18 18:07:18.823/3464791.281 Oracle Coherence GE 3.6.0.3 <Error> (thread=Termination Thread, member=7): Full Thread Dump
    Thread[Invocation:Management:EventDispatcher,5,Cluster]
    java.lang.Object.wait(Native Method)
    com.tangosol.coherence.component.util.Daemon.onWait(Daemon.CDB:18)
    com.tangosol.coherence.component.util.daemon.queueProcessor.Service$EventDispatcher.onWait(Service.CDB:7)
    com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:39)
    java.lang.Thread.run(Thread.java:619)
    Thread[Logger@9250962 3.6.0.3,3,main]
    java.lang.Object.wait(Native Method)
    com.tangosol.coherence.component.util.Daemon.onWait(Daemon.CDB:18)
    com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:39)
    java.lang.Thread.run(Thread.java:619)
    Thread[Signal Dispatcher,9,system]
    Thread[Finalizer,8,system]
    java.lang.Object.wait(Native Method)
    java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:118)
    java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:134)
    java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159)
    Thread[Invocation:Management,5,Cluster]
    java.lang.Object.wait(Native Method)
    com.tangosol.coherence.component.util.Daemon.onWait(Daemon.CDB:18)
    com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.onWait(Grid.CDB:6)
    com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:39)
    java.lang.Thread.run(Thread.java:619)
    ThreadCluster
    java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method)
    java.net.InetAddress$1.lookupAllHostAddr(InetAddress.java:850)
    java.net.InetAddress.getAddressFromNameService(InetAddress.java:1201)
    java.net.InetAddress.getAllByName0(InetAddress.java:1154)
    java.net.InetAddress.getAllByName(InetAddress.java:1084)
    java.net.InetAddress.getAllByName(InetAddress.java:1020)
    java.net.InetAddress.getByName(InetAddress.java:970)
    java.net.InetSocketAddress.<init>(InetSocketAddress.java:124)
    com.tangosol.net.ConfigurableAddressProvider$AddressHolder.getAddress(ConfigurableAddressProvider.java:426)
    com.tangosol.net.ConfigurableAddressProvider$1.next(ConfigurableAddressProvider.java:167)
    java.util.AbstractCollection.contains(AbstractCollection.java:89)
    com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.ClusterService.isWellKnown(ClusterService.CDB:5)
    com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.ClusterService.compareImportance(ClusterService.CDB:7)
    com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.ClusterService.getWitnessMemberSet(ClusterService.CDB:49)
    com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.ClusterService.verifyMemberLeft(ClusterService.CDB:91)
    com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.ClusterService.onNotifyTcmpTimeout(ClusterService.CDB:11)
    com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.ClusterService$NotifyTcmpTimeout.onReceived(ClusterService.CDB:1)
    com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.onMessage(Grid.CDB:11)
    com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.onNotify(Grid.CDB:33)
    com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.ClusterService.onNotify(ClusterService.CDB:3)
    com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:42)
    java.lang.Thread.run(Thread.java:619)
    Thread[main,5,main]
    java.lang.Object.wait(Native Method)
    com.tangosol.net.DefaultCacheServer.monitorServices(DefaultCacheServer.java:270)
    com.tangosol.net.DefaultCacheServer.startAndMonitor(DefaultCacheServer.java:56)
    com.tangosol.net.DefaultCacheServer.main(DefaultCacheServer.java:197)
    Thread[PacketReceiver,7,Cluster]
    java.lang.Object.wait(Native Method)
    com.tangosol.coherence.component.util.Daemon.onWait(Daemon.CDB:18)
    com.tangosol.coherence.component.util.daemon.queueProcessor.packetProcessor.PacketReceiver.onWait(PacketReceiver.CDB:2)
    com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:39)
    java.lang.Thread.run(Thread.java:619)
    Thread[PacketSpeaker,8,Cluster]
    java.lang.Object.wait(Native Method)
    com.tangosol.coherence.component.util.queue.ConcurrentQueue.waitForEntry(ConcurrentQueue.CDB:16)
    com.tangosol.coherence.component.util.queue.ConcurrentQueue.remove(ConcurrentQueue.CDB:7)
    com.tangosol.coherence.component.util.Queue.remove(Queue.CDB:1)
    com.tangosol.coherence.component.util.daemon.queueProcessor.packetProcessor.PacketSpeaker.onNotify(PacketSpeaker.CDB:21)
    com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:42)
    java.lang.Thread.run(Thread.java:619)
    Thread[Termination Thread,6,Cluster]
    java.lang.Thread.dumpThreads(Native Method)
    java.lang.Thread.getAllStackTraces(Thread.java:1487)
    com.tangosol.net.GuardSupport.logStackTraces(GuardSupport.java:810)
    com.tangosol.coherence.component.net.Cluster$DefaultFailurePolicy.onGuardableTerminate(Cluster.CDB:4)
    com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid$WrapperGuardable.terminate(Grid.CDB:1)
    com.tangosol.net.GuardSupport$Context$2.run(GuardSupport.java:677)
    java.lang.Thread.run(Thread.java:619)
    Thread[Reference Handler,10,system]
    java.lang.Object.wait(Native Method)
    java.lang.Object.wait(Object.java:485)
    java.lang.ref.Reference$ReferenceHandler.run(Reference.java:116)
    Thread[PacketPublisher,6,Cluster]
    java.lang.Object.wait(Native Method)
    com.tangosol.coherence.component.util.Daemon.onWait(Daemon.CDB:18)
    com.tangosol.coherence.component.util.daemon.queueProcessor.packetProcessor.PacketPublisher.onWait(PacketPublisher.CDB:2)
    com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:39)
    java.lang.Thread.run(Thread.java:619)
    Thread[DistributedCache,5,Cluster]
    java.lang.Object.wait(Native Method)
    com.tangosol.coherence.component.util.Daemon.onWait(Daemon.CDB:18)
    com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.onWait(Grid.CDB:6)
    com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:39)
    java.lang.Thread.run(Thread.java:619)
    Thread[IpMonitor,6,Cluster]
    java.lang.Object.wait(Native Method)
    com.tangosol.coherence.component.util.Daemon.onWait(Daemon.CDB:18)
    com.tangosol.coherence.component.util.daemon.IpMonitor.onWait(IpMonitor.CDB:4)
    com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:39)
    java.lang.Thread.run(Thread.java:619)
    Thread[PacketListener1P,8,Cluster]
    java.net.PlainDatagramSocketImpl.receive0(Native Method)
    java.net.PlainDatagramSocketImpl.receive(PlainDatagramSocketImpl.java:136)
    java.net.DatagramSocket.receive(DatagramSocket.java:725)
    com.tangosol.coherence.component.net.socket.UdpSocket.receive(UdpSocket.CDB:22)
    com.tangosol.coherence.component.net.UdpPacket.receive(UdpPacket.CDB:1)
    com.tangosol.coherence.component.util.daemon.queueProcessor.packetProcessor.PacketListener.onNotify(PacketListener.CDB:20)
    com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:42)
    java.lang.Thread.run(Thread.java:619)
    Thread[PacketListener1,8,Cluster]
    java.net.PlainDatagramSocketImpl.receive0(Native Method)
    java.net.PlainDatagramSocketImpl.receive(PlainDatagramSocketImpl.java:136)
    java.net.DatagramSocket.receive(DatagramSocket.java:725)
    com.tangosol.coherence.component.net.socket.UdpSocket.receive(UdpSocket.CDB:22)
    com.tangosol.coherence.component.net.UdpPacket.receive(UdpPacket.CDB:1)
    com.tangosol.coherence.component.util.daemon.queueProcessor.packetProcessor.PacketListener.onNotify(PacketListener.CDB:20)
    com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:42)
    java.lang.Thread.run(Thread.java:619)
    2010-12-18 18:07:18.823/3464791.281 Oracle Coherence GE 3.6.0.3 <Warning> (thread=Termination Thread, member=7): Terminating Guard{Daemon=Cluster}
    2010-12-18 18:07:18.823/3464791.281 Oracle Coherence GE 3.6.0.3 <Error> (thread=StopService, member=7): Requested to stop cluster service.
    2010-12-18 18:07:18.826/3464791.284 Oracle Coherence GE 3.6.0.3 <D5> (thread=DistributedCache, member=7): Service DistributedCache left the cluster
    2010-12-18 18:07:18.826/3464791.284 Oracle Coherence GE 3.6.0.3 <D5> (thread=Invocation:Management, member=7): Service Management left the cluster
    2010-12-18 18:07:24.904/3464797.362 Oracle Coherence GE 3.6.0.3 <Error> (thread=main, member=7): Failed to restart services: com.tangosol.net.RequestTimeoutException: Timeout while waiting for cluster to stop.
    2010-12-18 18:07:33.915/3464806.373 Oracle Coherence GE 3.6.0.3 <Error> (thread=main, member=7): Failed to restart services: com.tangosol.net.RequestTimeoutException: Timeout while waiting for cluster to stop.
    2010-12-18 18:07:42.924/3464815.382 Oracle Coherence GE 3.6.0.3 <Error> (thread=main, member=7): Failed to restart services: com.tangosol.net.RequestTimeoutException: Timeout while waiting for cluster to stop.
    2010-12-18 18:07:51.936/3464824.394 Oracle Coherence GE 3.6.0.3 <Error> (thread=main, member=7): Failed to restart services: com.tangosol.net.RequestTimeoutException: Timeout while waiting for cluster to stop.

    The log file shows that list of the addresses are formed by IP, but they are configured by using hostname in override file.
    Here's the log entry:
    WellKnownAddressList(Size=2,
    WKA{Address=165.X.X.XX7, Port=8088}
    WKA{Address=165.X.X.XX8, Port=8088}
    Here's the configuration from tangosol-coherence-override-prod.xml:
    <well-known-addresses>
    <socket-address id="1">
    <address system-property="tangosol.coherence.wka">serverA</address>
    <port system-property="tangosol.coherence.wka.port">8088</port>
    </socket-address>
    <socket-address id="2">
    <address system-property="tangosol.coherence.wka">serverB</address>
    <port system-property="tangosol.coherence.wka.port">8088</port>
    </socket-address>
    </well-known-addresses>
    Thanks,
    Ramesh

  • SQL Cluster services is not start in secound node.

    SQL Cluster services is not start in secound node.

    Start or Stop the Cluster Service on a Cluster Node
    https://technet.microsoft.com/en-us/library/cc771742.aspx
    Ahsan Kabir Please remember to click Mark as Answer and Vote as Helpful on posts that help you. This can be beneficial to other community members reading the thread. http://www.aktechforum.blogspot.com/

  • Install Java Add-In for existing ABAP == 'First MSCS Node' step fails

    I am in the process of installing the Java Add-In for an existing ABAP System.
    I am doing the High-Availability Installation Services.
    There are seven (7) steps:
    1. Central Services Instance (CSC) Java Add-In
    2. First MSCS Node
    3. Database Instance Java Add-In
    4. Additional MSCS Node
    5. Enqueue Replication Server
    6. Central Instance Java Add-In
    7. Dialog Instance
    Step #1 was completed successfully.
    Step #2 (First MSCS Node) keeps failing with the following warnings/error:
    <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
    WARNING 2011-11-02 07:38:04.928
    Execution of the command "cluster.exe RESOURCE "SAP BWP 00 Service"" finished with return code 5007. Output:
    Listing status for resource 'SAP BWP 00 Service':
    Resource             Group                Node            Status
    System error 5007 has occurred (0x0000138f).
    The cluster resource could not be found.
    <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
    WARNING 2011-11-02 07:40:29.085
    Execution of the command "M:\usr\sap\BWP\ASCS00\exe\sapstartsrv.exe -u -q -s BWP -n 00" finished with return code 128. Output:
    <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
    ERROR 2011-11-02 07:40:29.210
    FCO-00011  The step dCreateSecondNewSCSServiceWithVirtualHostName with step key |MSCS_A|windows|ind|ind|ind|0|0|SAPServices|windows|ind|ind|ind|9|0|dCreateSecondNewSCSServiceWithVirtualHostName was executed with status ERROR .

    This seems to be an issue with the clustering solution. Please, refer to the following article link:
    http://support.microsoft.com/default.aspx?scid=kb;en-us;281796
    See if that helps
    Edited by: David Fitzgibbon on Nov 2, 2011 2:18 PM

  • Howto take SQL Server 2005 Cluster AND Cluster Group Offline

    I need to update firmware on the backend storage used by our Active/Passive SQL Server 2005 Cluster.  The first step in the process states that all I/O to the disks should be stopped.  Per that, I need to take the the SQL Server cluster offline AND the cluster group; however, I then need to use one of the servers that participates in the cluster to perform the upgrade on the storage array.  Using the process (which doesn't account for having to use one of clustered servers to perform updates) outlined at http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1550288&SiteID=1 as a basis, below is my best guess regarding what I will need to do: 
    Shutdown:
    1. Backup all of your databases prior to the outage and ensure they are in a safe place (NOT on the disk drives in the cluster)
    2. Take the SQL Server group OFFLINE.  This will cleanly shutdown the SQL Server and it will remain offline when you power the machine back on.
    3. Once SQL Server is offline, power off the node which does NOT have the cluster resource currently running on it
    4. Save the node which is running the cluster group for last - make a note of this machine as it will be the first one you power back on.  MY ADDITION: Before powering it down, set the cluster service to manual so that when you restart the server to perform the storage array maintenance, the cluster will not be running - and likewise not generating I/O against the disk array.
    MY ADDITION: 5. Restart the server from step 4.  Takes the cluster offline "cleanly" and brings the server back on line so that the storage array maintenance can be performed.
    6. Update the firmware on the storage array.  After that is complete, set the cluster service back to "Automatic".
    Start up:
    1. Restart the server.  Per the previous steps, the server to be restarted will be the server that last hosted the cluster group and the one used to update the firmware on the storage array.
    2. RDP into the node, open cluster administrator, and verify that the cluster came back online successfully and everything looks clean
    3. Power on the second node.
    4. Failover the cluster group across each node in the cluster and validate that everything looks OK
    5. Bring your SQL Server groups back online
    6. Validate that everything is operational
    Is there a better way to do this or official documentation for the process? 
    Thanks.

    FYI: I did use the process outlined above to briing the cluster offline, perform updates, and bring it back online.  It worked as I had hoped.  As a test, I had also done the same on a test [non-SQL] cluster prior to making the updates to our SQL cluster.  Is it the best way to do it?  Who knows. Did it work?  Yes.

  • SAP Cluster service issue

    Here is the description of the PRD cluster scenario. ( windows 2008 + oracle)
    We have 2 nodes .
    1. host-erpn01 ( Have ASCS , Database instance, Enqueue and Dialog
    Instance installed)
    2. host-erp02 ( Have Central Instance, Dialog Instance and Enqueue installed)
    When we move "SAP SID" service using "failover cluster management tool" from one node to another its fails and we have to manually select the  "SAP SID cluster service" and "SAP SID cluster instance" to online.
    These both service and instance were coming online after manual selection, however after some time in the mmc console of node 2 the sap instances hosted on node1 are in red cross and are giving " cannot connect to sap service dcom interface error 800706BA"
    We replaced the sapstartsrv.exe from working directory of ASCS instance to CI executable directory.
    Now the disp+work is stopped for CI instance. Also in the CI instance executable directory we can see five files with name of sapstartsrv i.e
    sapstartsrv.exe.new , sapstartsrv.exe.tmp, sapstartsrv.new, sapstartsrv.pdb and actual sapstartsrv.exe file.
    Here is the log of sapstartsrv.log  CI work directory from node2.
    trc file: "sapstartsrv.log", trc level: 0, release: "701"
    pid        1968
    Mon Oct 11 15:55:33 2010
    SAP HA Trace: Build in SAP Microsoft Cluster library '701, patch 32, changelist 1046543' initialized
    Initializing SAPControl Webservice
    SapSSLInit failed => https support disabled
    Starting WebService Named Pipe thread
    Starting WebService thread
    Webservice named pipe thread started, listening on port
    .\pipe\sapcontrol_01
    Webservice thread started, listening on port 50113
    GCCIA\csrvadmin is starting SAP System at 2010/10/11 16:09:07
    SAP HA Trace: FindClusterResource: SAP resource not found [sapwinha.cpp, line 334]
    SAP HA Trace: SAP_HA_FindSAPInstance returns: SAP_HA_NOT_CLUSTERED [sapwinha.cpp, line 907]"
    or you can view other logs from the work directory dump at
    http://s000.tinyupload.com/index.php?file_id=45384422007535688902
    Now when we try to start the SAPSID_00 service manually its giving error "The SAPSID_00 service failed to start due to the following error: The system cannot find the path specified.
    Please advice.
    Regards
    Edited by: Tech GCCIA on Oct 11, 2010 3:27 PM
    Edited by: Tech GCCIA on Oct 11, 2010 3:28 PM

    Hi Sunil ,
                       On node 1 there is no  listener.trc at /oracle_home/network/trace folder , here is the log of listener.log file in case if it is helpful.
    TNSLSNR for 64-bit Windows: Version 10.2.0.4.0 - Production on 10-OCT-2010 10:37:37
    Copyright (c) 1991, 2007, Oracle.  All rights reserved.
    System parameter file is D:\oracle\GCP\102\network\admin\listener.ora
    Log messages written to D:\oracle\GCP\102\network\log\listener.log
    Trace information written to D:\oracle\GCP\102\network\trace\listener.trc
    Trace level is currently 0
    Started with pid=3116
    Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=
    .\pipe\GCP.WORLDipc)))
    Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=
    .\pipe\GCPipc)))
    Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=gccia-erpn01.gccia.com.sa)(PORT=1527)))
    Listener completed notification to CRS on start
    TIMESTAMP * CONNECT DATA [* PROTOCOL INFO] * EVENT [* SID] * RETURN CODE
    TNSLSNR for 64-bit Windows: Version 10.2.0.4.0 - Production on 10-OCT-2010 11:59:37
    Copyright (c) 1991, 2007, Oracle.  All rights reserved.
    System parameter file is D:\oracle\GCP\102\network\admin\listener.ora
    Log messages written to D:\oracle\GCP\102\network\log\listener.log
    Trace information written to D:\oracle\GCP\102\network\trace\listener.trc
    Trace level is currently 0
    Started with pid=5036
    Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=
    .\pipe\GCP.WORLDipc)))
    Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=
    .\pipe\GCPipc)))
    Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=192.168.11.13)(PORT=1527)))
    Listener completed notification to CRS on start
    TIMESTAMP * CONNECT DATA [* PROTOCOL INFO] * EVENT [* SID] * RETURN CODE
    10-OCT-2010 12:00:31 * (CONNECT_DATA=(SID=GCP)(GLOBAL_NAME=GCP.WORLD)(CID=(PROGRAM=D:\oracle\OFS\SRV\fs\fssvr\bin\FsSurrogate.exe)(HOST=GCCIA-ERPN01)(USER=csrvadmin))) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.11.13)(PORT=60592)) * establish * GCP * 0
    10-OCT-2010 12:00:31 * (CONNECT_DATA=(SID=GCP)(GLOBAL_NAME=GCP.WORLD)(CID=(PROGRAM=D:\oracle\OFS\SRV\fs\fssvr\bin\FsSurrogate.exe)(HOST=GCCIA-ERPN01)(USER=csrvadmin))) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.11.13)(PORT=60593)) * establish * GCP * 0
    10-OCT-2010 12:00:31 * (CONNECT_DATA=(SID=GCP)(GLOBAL_NAME=GCP.WORLD)(CID=(PROGRAM=D:\oracle\OFS\SRV\fs\fssvr\bin\FsSurrogate.exe)(HOST=GCCIA-ERPN01)(USER=csrvadmin))) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.11.13)(PORT=60594)) * establish * GCP * 0
    10-OCT-2010 12:00:31 * (CONNECT_DATA=(SID=GCP)(GLOBAL_NAME=GCP.WORLD)(CID=(PROGRAM=D:\oracle\OFS\SRV\fs\fssvr\bin\FsSurrogate.exe)(HOST=GCCIA-ERPN01)(USER=csrvadmin))) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.11.13)(PORT=60595)) * establish * GCP * 0
    10-OCT-2010 12:00:31 * (CONNECT_DATA=(SID=GCP)(GLOBAL_NAME=GCP.WORLD)(CID=(PROGRAM=D:\oracle\OFS\SRV\fs\fssvr\bin\FsSurrogate.exe)(HOST=GCCIA-ERPN01)(USER=csrvadmin))) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.11.13)(PORT=60596)) * establish * GCP * 0
    10-OCT-2010 13:01:19 * (CONNECT_DATA=(SID=GCP)(GLOBAL_NAME=GCP.WORLD)(CID=(PROGRAM=D:\oracle\OFS\SRV\fs\fssvr\bin\FsSurrogate.exe)(HOST=GCCIA-ERPN01)(USER=csrvadmin))) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.11.13)(PORT=61336)) * establish * GCP * 0
    10-OCT-2010 13:01:37 * (CONNECT_DATA=(SID=GCP)(GLOBAL_NAME=GCP.WORLD)(CID=(PROGRAM=D:\oracle\OFS\SRV\fs\fssvr\bin\FsSurrogate.exe)(HOST=GCCIA-ERPN01)(USER=csrvadmin))) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.11.13)(PORT=61340)) * establish * GCP * 0
    10-OCT-2010 13:01:37 * (CONNECT_DATA=(SID=GCP)(GLOBAL_NAME=GCP.WORLD)(CID=(PROGRAM=D:\oracle\OFS\SRV\fs\fssvr\bin\FsSurrogate.exe)(HOST=GCCIA-ERPN01)(USER=csrvadmin))) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.11.13)(PORT=61341)) * establish * GCP * 0
    10-OCT-2010 13:01:37 * (CONNECT_DATA=(SID=GCP)(GLOBAL_NAME=GCP.WORLD)(CID=(PROGRAM=D:\oracle\OFS\SRV\fs\fssvr\bin\FsSurrogate.exe)(HOST=GCCIA-ERPN01)(USER=csrvadmin))) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.11.13)(PORT=61342)) * establish * GCP * 0
    10-OCT-2010 13:01:37 * (CONNECT_DATA=(SID=GCP)(GLOBAL_NAME=GCP.WORLD)(CID=(PROGRAM=D:\oracle\OFS\SRV\fs\fssvr\bin\FsSurrogate.exe)(HOST=GCCIA-ERPN01)(USER=csrvadmin))) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.11.13)(PORT=61343)) * establish * GCP * 0
    10-OCT-2010 13:01:37 * (CONNECT_DATA=(SID=GCP)(GLOBAL_NAME=GCP.WORLD)(CID=(PROGRAM=D:\oracle\OFS\SRV\fs\fssvr\bin\FsSurrogate.exe)(HOST=GCCIA-ERPN01)(USER=csrvadmin))) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.11.13)(PORT=61344)) * establish * GCP * 0
    10-OCT-2010 13:08:27 * (CONNECT_DATA=(SID=GCP)(GLOBAL_NAME=GCP.WORLD)(CID=(PROGRAM=D:\oracle\OFS\SRV\fs\fssvr\bin\FsSurrogate.exe)(HOST=GCCIA-ERPN01)(USER=csrvadmin))) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.11.13)(PORT=61485)) * establish * GCP * 0
    10-OCT-2010 13:08:42 * (CONNECT_DATA=(SID=GCP)(GLOBAL_NAME=GCP.WORLD)(CID=(PROGRAM=D:\oracle\OFS\SRV\fs\fssvr\bin\FsSurrogate.exe)(HOST=GCCIA-ERPN01)(USER=csrvadmin))) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.11.13)(PORT=61489)) * establish * GCP * 0
    10-OCT-2010 13:08:42 * (CONNECT_DATA=(SID=GCP)(GLOBAL_NAME=GCP.WORLD)(CID=(PROGRAM=D:\oracle\OFS\SRV\fs\fssvr\bin\FsSurrogate.exe)(HOST=GCCIA-ERPN01)(USER=csrvadmin))) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.11.13)(PORT=61490)) * establish * GCP * 0
    10-OCT-2010 13:08:42 * (CONNECT_DATA=(SID=GCP)(GLOBAL_NAME=GCP.WORLD)(CID=(PROGRAM=D:\oracle\OFS\SRV\fs\fssvr\bin\FsSurrogate.exe)(HOST=GCCIA-ERPN01)(USER=csrvadmin))) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.11.13)(PORT=61491)) * establish * GCP * 0
    10-OCT-2010 13:08:42 * (CONNECT_DATA=(SID=GCP)(GLOBAL_NAME=GCP.WORLD)(CID=(PROGRAM=D:\oracle\OFS\SRV\fs\fssvr\bin\FsSurrogate.exe)(HOST=GCCIA-ERPN01)(USER=csrvadmin))) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.11.13)(PORT=61492)) * establish * GCP * 0
    10-OCT-2010 13:08:42 * (CONNECT_DATA=(SID=GCP)(GLOBAL_NAME=GCP.WORLD)(CID=(PROGRAM=D:\oracle\OFS\SRV\fs\fssvr\bin\FsSurrogate.exe)(HOST=GCCIA-ERPN01)(USER=csrvadmin))) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.11.13)(PORT=61493)) * establish * GCP * 0
    TNSLSNR for 64-bit Windows: Version 10.2.0.4.0 - Production on 10-OCT-2010 13:09:57
    Copyright (c) 1991, 2007, Oracle.  All rights reserved.
    System parameter file is D:\oracle\GCP\102\network\admin\listener.ora
    Log messages written to D:\oracle\GCP\102\network\log\listener.log
    Trace information written to D:\oracle\GCP\102\network\trace\listener.trc
    Trace level is currently 0
    Started with pid=2336
    Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=
    .\pipe\GCP.WORLDipc)))
    Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=
    .\pipe\GCPipc)))
    Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=192.168.11.13)(PORT=1527)))
    Listener completed notification to CRS on start
    TIMESTAMP * CONNECT DATA [* PROTOCOL INFO] * EVENT [* SID] * RETURN CODE
    TNSLSNR for 64-bit Windows: Version 10.2.0.4.0 - Production on 10-OCT-2010 13:14:34
    Copyright (c) 1991, 2007, Oracle.  All rights reserved.
    System parameter file is D:\oracle\GCP\102\network\admin\listener.ora
    Log messages written to D:\oracle\GCP\102\network\log\listener.log
    Trace information written to D:\oracle\GCP\102\network\trace\listener.trc
    Trace level is currently 0
    Started with pid=4948
    Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=
    .\pipe\GCP.WORLDipc)))
    Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=
    .\pipe\GCPipc)))
    Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=192.168.11.13)(PORT=1527)))
    Listener completed notification to CRS on start
    TIMESTAMP * CONNECT DATA [* PROTOCOL INFO] * EVENT [* SID] * RETURN CODE
    TNSLSNR for 64-bit Windows: Version 10.2.0.4.0 - Production on 10-OCT-2010 13:38:12
    Copyright (c) 1991, 2007, Oracle.  All rights reserved.
    System parameter file is D:\oracle\GCP\102\network\admin\listener.ora
    Log messages written to D:\oracle\GCP\102\network\log\listener.log
    Trace information written to D:\oracle\GCP\102\network\trace\listener.trc
    Trace level is currently 0
    Started with pid=2456
    Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=
    .\pipe\GCP.WORLDipc)))
    Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=
    .\pipe\GCPipc)))
    Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=192.168.11.13)(PORT=1527)))
    Listener completed notification to CRS on start
    TIMESTAMP * CONNECT DATA [* PROTOCOL INFO] * EVENT [* SID] * RETURN CODE
    TNSLSNR for 64-bit Windows: Version 10.2.0.4.0 - Production on 10-OCT-2010 14:03:35
    Copyright (c) 1991, 2007, Oracle.  All rights reserved.
    System parameter file is D:\oracle\GCP\102\network\admin\listener.ora
    Log messages written to D:\oracle\GCP\102\network\log\listener.log
    Trace information written to D:\oracle\GCP\102\network\trace\listener.trc
    Trace level is currently 0
    Started with pid=2756
    Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=
    .\pipe\GCP.WORLDipc)))
    Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=
    .\pipe\GCPipc)))
    Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=192.168.11.13)(PORT=1527)))
    Listener completed notification to CRS on start
    TIMESTAMP * CONNECT DATA [* PROTOCOL INFO] * EVENT [* SID] * RETURN CODE
    TNSLSNR for 64-bit Windows: Version 10.2.0.4.0 - Production on 10-OCT-2010 14:10:42
    Copyright (c) 1991, 2007, Oracle.  All rights reserved.
    System parameter file is D:\oracle\GCP\102\network\admin\listener.ora
    Log messages written to D:\oracle\GCP\102\network\log\listener.log
    Trace information written to D:\oracle\GCP\102\network\trace\listener.trc
    Trace level is currently 0
    Started with pid=4812
    Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=
    .\pipe\GCP.WORLDipc)))
    Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=
    .\pipe\GCPipc)))
    Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=192.168.11.13)(PORT=1527)))
    Listener completed notification to CRS on start
    TIMESTAMP * CONNECT DATA [* PROTOCOL INFO] * EVENT [* SID] * RETURN CODE
    TNSLSNR for 64-bit Windows: Version 10.2.0.4.0 - Production on 11-OCT-2010 09:34:05
    Copyright (c) 1991, 2007, Oracle.  All rights reserved.
    System parameter file is D:\oracle\GCP\102\network\admin\listener.ora
    Log messages written to D:\oracle\GCP\102\network\log\listener.log
    Trace information written to D:\oracle\GCP\102\network\trace\listener.trc
    Trace level is currently 0
    Started with pid=1920
    Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=192.168.11.13)(PORT=1527)))
    Listener completed notification to CRS on start
    TIMESTAMP * CONNECT DATA [* PROTOCOL INFO] * EVENT [* SID] * RETURN CODE
    TNSLSNR for 64-bit Windows: Version 10.2.0.4.0 - Production on 11-OCT-2010 21:12:29
    Copyright (c) 1991, 2007, Oracle.  All rights reserved.
    System parameter file is D:\oracle\GCP\102\network\admin\listener.ora
    Log messages written to D:\oracle\GCP\102\network\log\listener.log
    Trace information written to D:\oracle\GCP\102\network\trace\listener.trc
    Trace level is currently 0
    Started with pid=1952
    Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=192.168.11.13)(PORT=1527)))
    Listener completed notification to CRS on start
    TIMESTAMP * CONNECT DATA [* PROTOCOL INFO] * EVENT [* SID] * RETURN CODE

  • The Cluster service is shutting down because quorum was lost

    Hi, we recently experienced the above issue and after looking for explanations I haven't been able to find any satisfying answers when other people have posted this issue.
    Our problem is as follows:
    2 node 2008R2 cluster running SQL 2012
    Each node is a HP BL460c running in a HP C7000 Blade Chassis.
    We were updating the flexfabric cards on one of the chassis.  The other chassis had been patched the previous week with no problems. 
    During the update process the flexfabric cards, which hold the Ethernet and FC connections, reboot so before work had begun all active cluster services had been failed over to the node in the chassis not being worked on.  However despite this the cluster
    service shut down on this one particular cluster.  All other clusters running across these 2 chassis continued to run as expected.
    As other people have posted before we saw the following errors in the system log.
    1564: File share witness resource 'File Share Witness' failed to arbitrate for the file share
    1069: Cluster resource 'File Share Witness' in clustered service or application 'Cluster Group' failed.
    1172: The Cluster service is shutting down because quorum was lost. This could be due to the loss of network connectivity between some or all nodes in the cluster, or a failover of the witness disk.
    Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapter. Also check for failures in any other network components to which the node is connected
    such as hubs, switches, or bridges.
    However we cant understand what could cause this to happen when the service is running on the node in the chassis not being updated, especially when the same update was performed the week before with no issues.  How can both nodes lose connectivity
    to the File Share Witness at the same time?
    Cluster Validation tests run fine and don't highlight any issues.  The file share witness is accessible from both servers.

    Hi,
    Please confirm you have install the Recommended hotfixes and updates for Windows Server 2008 R2 SP1 Failover Clusters update, especially the following hotfix.
    The network location profile changes from "Domain" to "Public" in Windows 7 or in Windows Server 2008 R2
    http://support.microsoft.com/kb/2524478/EN-US
    A hotfix is available that adds two new cluster control codes to help you determine which cluster node is blocking a GUM update in Windows Server 2008 R2 and Windows Server
    2012
    http://support.microsoft.com/kb/2779069/EN-US
    Hope this helps.
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Taking cluster disk offline made all other resources in the group to go offline.

    Hi,
    We have three node windows 2008 R2 failover cluster. When we tried to take one of the cluster disk offline from a application and services, it made all other resources in that application and services to go offline even though there was no dependency on
    this disk. I want to know why it made all other resources to go offline. Can some one clarify please? Is it a default behavior?
    Umesh

    "When we tried to take one of the cluster disk offline from a application and services, it made all other resources in that application and services to go offline even though there was no dependency on this disk."
    I'm a little unclear on your problem description.  You state you are taking a "disk offline from a application and services".  That implies the disk is necessary for the application and/or service, otherwise there is no way to take it
    offline from that application and/or service.  Then you state "there was no dependency on this disk".  If there was no dependency on the disk, how you could take it "offline from a application and services"?
    Using the Failover Cluster Manager consolde, select one of the resources that is going offline.  Click on the Resources tab at the bottom of the center window.  That resource does not show any dependency on the disk being taken offline? 
    Does it show dependency on any other resource that is dependent upon the disk you are taking offline?
    . : | : . : | : . tim

  • Cluster services UNKNOWN state

    Hi,
    I am having two node cluster database. I have some doubt
    If cluster services will go UNKNOWN state in first node existing connection will failover to second node?
    New connections will try to connect first node?

    user2017273 wrote:
    Hi,
    I am having two node cluster database. I have some doubtQuit doubting and TEST it for yourself. Also actually reading the documentation will help
    >
    If cluster services will go UNKNOWN state in first node existing connection will failover to second node?
    Maybe...
    New connections will try to connect first node?If nodex is down any connection attempt should go to the remaining nodes.

  • Why virtual interfaces added to ManagementOS not visible to Cluster service?

    Hello All, 
    I"m starting this new thread since the one before is answered by our friend Udo. My problem in short is following. Diagram will be enough to explain what I'm trying to achieve. I've setup this lab to learn Hyper-V clustering with 2 nodes. It is Hyper-V
    server 2012. Both nodes have 3x physical NIcs, 1 in each node is dedicated to managing the Node. Rest of the two are used to create a NIC team. Atop of that NIC team, a virtual switch is created with -AllowManagementOS
    $False. Next I created and added following virtual interfaces to host partition, and plugged them into virtual switch created atop of teamed interface. These virtual interfaces should serve the purpose of various networks available. 
    For SAN i'm running a Linux VM which has iSCSI target server and clustering service has no problem with that. All tests pass ok.
    The problem is......when those virtual interfaces added to hosts; do not appear as available networks
    to cluster service; instead it only shows the management NIC as the available network to leverage. 
    This is making it difficult to understand how to setup a cluster of 2x Hyper-V Server nodes. Can someone help please?
    Regards,
    Shahzad.

    Shahzad,
    I've read this thread a couple of times and I don't think I'm clear on the exact question you're asking.
    When the clustering service goes out to look for "Networks", what it does is scan the IP addresses on each node. Every time it finds an IP in a unique subnet, that subnet is listed as a network. It can't see virtual switches and doesn't care about
    virtual vs. teamed vs. physical adapters or anything like that. It's just looking at IP addresses. This is why I'm confused when you say, "it won't show virtual interfaces available as networks". "Networks" in this context are IP subnets.
    I'm not aware of any context where a singular interface would be treated like a network.
    If you've got virtual adapters attached to the management operating system
    and have assigned IPs to them, the cluster should have discovered those networks. If you have multiple adapters on the same node using IPs in the same subnet, that network will only appear once and the cluster service will only use
    one adapter from that subnet on that node. The one it picked will be visible on the "Network Connections" tab at the bottom of Failover Cluster Manager when you're on the Networks section.
    Eric Siron Altaro Hyper-V Blog
    I am an independent blog contributor, not an Altaro employee. I am solely responsible for the content of my posts.
    "Every relationship you have is in worse shape than you think."
    Hello Eric and friends, 
    Eric, much appreciated about your interest about the issue and yes I agree with you when you said... "When the clustering service goes out to look for "Networks",
    what it does is scan the IP addresses on each node. Every time it finds an IP in a unique subnet, that subnet is listed as a network. It can't see virtual switches and doesn't care about virtual vs. teamed vs. physical adapters or anything like that. It's
    just looking at IP addresses. This is why I'm confused when you say, "it won't show virtual interfaces available as networks". "Networks" in this context are IP subnets. I'm not aware of any context where a singular interface would be treated
    like a network."
    By networks I meant to say subnets. Let me explain what I've configured so far:
    Node 1 & Node 2 installed with 3x NICs. All 3 NICs/node plugged into same switch. 
    Node1:  131.107.0.50/24
    Node2:  131.107l.0.150/24
    A Core Domain controller VM running on Node 1:   131.107.0.200/24 
    A JUMPBOX (WS 2012 R2 Std.) VM running on Node 1: 131.107.0.100/24
    A Linux SAN VM running on Node 2: 10.1.1.100/8 
    I planed to configured following networks:
    (1) Cluster traffic:  10.0.0.50/24     (IP given to virtual interface for Cluster traffic in Node1)
         Cluster traffic:  10.0.0.150/24   (IP given to virtual interface for Cluster traffic in Node2)
    (2) SAN traffic:      10.1.1.50/8      (IP given to virtual interfce for SAN traffic in Node1)  
         SAN traffic:      10.1.1.150/8    (IP given to virtual interfce for SAN traffic in Node2)
    Note: Cluster service has no problem accessing the SAN VM (10.1.1.100) over this network, it validates SAN settings and comes back OK. This is an indication that virtual interface is
    working fine. 
    (3) Migration traffic:   172.168.0.50/8     (IP given to virtual interfce for
    Migration traffic in Node1) 
         Migration traffic:   172.168.0.150/8    (IP given to virtual interfce for
    Migration  traffic in Node2)
    All these networks (virtual interfaces) are made available through two virtual switches which are configured EXACTLY identical on both Node1/Node2.
    Now after finishing the cluster validation steps (which comes all OK), when create cluster wizard starts, it only shows one network; i.e. network of physical Layer 2 switch i.e. 131.107.0.0/24.
    I wonder why it won't show IPs of other networks (10.0.0.0/8, 10.1.1.0/8 and  172.168.0.0/8)
    Regards,
    Shahzad

  • Timefinder mirror  BCV issues after installing Solaris Cluster 3.2

    I just installed Solaris Cluster 3.2, and since then, my BVC's will no longer mount. I have a case open with EMC already, just thought I check and see if anyone here has ever ran into the same issues and found a fix. The BCV job runs just fine until it comes to the time to mount it under an alternate location. This fails which I initially assumed was because SC needs the diskgroup to be registered. However, I have BCV's running on other servers that use SC3.2 as well, and they work just fine. If anyone has any past experience with this, please let me know how you overcame the problem.
    TIA...

    Did a rebuild with current patches, did not run JASS or an in-house hardening script on the nodes and I get the same result.
    I think I might have a bug issue with the bge driver or something.
    On the first node before running scinstall all nic lights are lit.
    After that first node reboots from scinstall the nic lights stay lit until right before the CMM messages begin appearing on the console. At that point the interconnect lights go out and stay out physically.
    No errors were detected with sccheck or in the install logs for the cluster.
    I tried a rebuild of the cluster nodes using a switch (ProCurve 2626) for the interconnects rather than an ethernet cable or cross-over cable.
    I have a hme interface in my V210 and V240 and I am going to use that for one of the interconnects to see if it matters.
    Basically at this point it is definitely not something physical (bad cable, bad switch port, etc) but something in the cluster configuration from scinstall that is not digging the interconnects and keeping the cluster nodes from conversing.
    Since the cluster isn't working anyway I can do a clintr enable node:port,switch@port and see that the ports and switch ports show as enabled by clintr status does not show an interconnect active and the physical ports are not lit.
    I do see references to bgeX/0 unregistered in /var/adm/messages but I haven't found information as to what this means or what to do about it exactly yet.
    Closest thing so far is this:
    http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6453203

  • Unix Cluster Services provided with 10G

    The information that I have read with regards to Oracle 10G (for Unix customers) suggests that 10G now includes volume management, file systems and the cluster services.
    Within earlier release of Oracle DB and Apps, the above components would have been provided by software vendors (e.g. Veritas) or the hardware vendors themselves (Sun, IBM etc..).
    The provision of an Oracle 10G architecture to customers without the requirement to procure additional "clusterware" services will clearly appeal to customers on tight budgets or who or currently focused on ROI. However, what about customers who are focused on performance and the highest levels of availability?
    Looking at the file system provided by Oracle (OSFS?), does this file system include journaling capabilities (i.e. improve fsck performance under unplanned system crash conditions). In addition, does the ORacle file system allow storage check points to be taken at a file system level? Finally, is there any performance data available comparing the Oracle file system directly with say Vxfs (either vanila product or with direct I/O) or Sun's UFS?
    Thanks in advance.
    Nathan

    In Oracle 10g there are two features that provide files system type functions. The first is Oracle Clustered File System (OCFS). It has been built to support clustered files for RAC deployments on NT and Linux. As I am not an expert on OCFS, I will not attempt to address your specific OCFS questions at this time.
    The second feature is Automatic Storage Management (ASM) which is an integrated file system and volume manager purpose built for the Oracle data files. It is a tool for the DBA to manage database storage and to increase their productivity. It speeds up the process of database layout and greatly simplifies the process of extending the storage configuration for a database. However, it is not a general purpose file system nor a general purpose clustered file system as it does not support flat files, trace files or binaries at present. ASM supports both single instance databases on a single node as well as on a clustered set of nodes. It also supports RAC.
    As for performance and availability, ASM has been doing very well in stress testing and beta testing. It performs as well as other file system and volume manager environments and in most cases ASM does better than those other environments. As a non ASM database will typically becomes fragmented and needs to have storage capacity added to it, the performance of that database will either decline or will require vast amounts of DBA and SA time to keep its performance optimal. With the database running on ASM managed disks, the performance will stay optimal with minimal maintenance from DBA and SA. ASM will rebalance the data across new storage and by way of its distribution of the data across the entire storage pool, there will be no fragmentation or imbalance of the workload. With ASM the manual task of I/O performance tuning will not be required.
    We do not yet have any published benchmarks at this time but hope to be able to publish a number which compares ASM to other volume mgmt and file systems environments at two points in time; one is the set up of a new config (best case) and the other is 6 months later when both environments have had the same fragmentation and storage configuration changes. That benchmark will need to track the time spent managing those two databases over that 6 months of as well. The challenge is that no such benchmark exists today.

  • CFMX7 - Linux - Novell Cluster Services

    I have a 2 node cluster set up with Suse Linux and Novell
    Cluster Services. There is a cluster resource of apache that is set
    up in the cluster, as well as a shared volume as a cluster
    resource. THe apache running as the cluster resource is using the
    shared volume for the web root home. Furthermore, apache is running
    individually on each node. Can anyone offer any opinions on setting
    up CFMX7 in this environment. We are not worried about load
    balancing, this is strictly needed for failover. My concerns are
    which install config I could be using, Individual Server,
    MultiServer, or J2EE? Can we use 1 CFADMIN for both nodes to
    minimize the overhead of keeping the configs in sync? During the
    install, can we use the cluster resource instance of apache to
    install to? My concern here is when we install it on the second
    node and point to the shared volume for the web root home, it's
    going to have a problem since it already exists? Any input is
    appreciated. Thanks.

    On 11.03.2011 14:06, laurabuckley wrote:
    >
    > Now I've been tasked with investigating the possibility of virtualizing
    > the nodes using VMWare (and making use of VMotion).
    >
    > This will give us the ability to have 6 virtual nodes rather than 3
    > physical nodes.
    >
    > What is the general feeling of the community with regards to:
    >
    > 1. Virtualizing cluster nodes
    > 2. How complex is the setup on VMWare
    > 3. Could I do a rolling migration from physical to virtual
    lot of talks about this, many things to consider.. here are few atleast;
    If you have (or buy) VMware HA and vMotion, do you even need Novell
    Cluster Services anymore?
    if you want vMotion, you need to use vmdk for storage, which might be an
    issue for large volumes.. or not?
    For large storage you could use RDM LUNs directly from SAN. But then you
    cannot use vMotion or run many nodes (of the same cluster) on one
    physical server.
    We are running multiple three node OES2 NCS clusters on three VMware
    servers, using RDM LUNs from EMC SAN. Did a rolling migration from
    physical Netware clusters using the same LUNs.
    -sk

Maybe you are looking for

  • Can I install Mac OS X Tiger 10.4 on a dell Optiplex Gx280?

    Hi! I have a couple of questions which I can't seem to find the answers too. 1) Can I install Mac OS X Tiger 10.4 on a Dell Optiplex GX280? 2) Can I take the HDD from the aforementioned Dell and place it in my Power Mac G4 Digital Audio? If so, will

  • Indexing Word document in UTF8 database

    Hello, have anybody experience with database created with character set UTF8 (Unicode) and indexing formatted documents like MS Word, Powerpoint, Adobe Acrobat etc.? When I'm indexing Word document in non UTF8 database it's OK, in UTF8 database index

  • Installer error

    Hello, I have Labview 8.0 and want to use the installer. My instrument uses serial comunication that's why i select at "additional installers" the "ni-serial". My installer is building without any problems when I do not select "ni-serial". When I sel

  • ROP Planning

    Hi all There is a requirement on which I'm currently working Material A - ROH MRP type VB we are maintaining reorder point,safety stock,Maximum stock level Lot size as HB and Ind/collective ind set as "1" And in configuration of MRP type VB under "Ad

  • How can I play Yahoo! Pool on my Mac?

    I updated Java, I let Java and Safari accept incoming connections, I disabled pop-up blocker, and still nothing.