Possible Owner Node, Fail Safe

Hello,
I'm testing Fail Safe with MS Failover Cluster.
There are three nodes in the cluster and "Oracle Service for MSCS" is Online. On each node is also installed oracle 11g and Fail Safe v3.4.2
* Successfully connected to MS Failover Cluster
* Successfully verified Cluster, clusterwide...
* Successfully created a group.
* Successfully added virtual ip to group.
* Successfully verified group, clusterwide...
* Successfully created standalone database
* Successfully verified standalone database, clusterwide...
now...when i try to add this standalone database to the group, in the second step of the wizard, there are NO possible owner nodes.
All three nodes are listed as: Not a possible owner.
where did wrong? Thanx
Saimo

The name of this Oracle Corp. forum is "RAC, ASM & Clusterware" installation
If you have issues around Microsoft technology I recommend you contact them. If you have issues with Oracle Fail Safe please look for a forum that addresses that product or open a ticket with MyOracleSupport.

Similar Messages

  • Not all of the host cluster nodes are marked as possible owners for the vms on this cluster

    I get this message in a cluster's properties after having replaced nodes' hardware (but keeping the same names). I noticed that some of the VMs in their settings have all the nodes but one checked as Possible Owners.
    What is a quick (PowerShell) way to find these VMs and check all the nodes as Possible Owners?  I see this page (http://technet.microsoft.com/en-us/library/jj628161.aspx) as how
    to do it in the GUI, but I want to do it with a script.  I haven't yet found a VMM cmdlet that sets the Possible Owners of a VM.

    Something like
    Get-SCVirtualMachine | `
    Where-Object{ ( $_.VirtualizationPlatform -eq "HyperV" ) -and $_.IsHighlyAvailable -and ( $_.ClusterNonPossibleOwner.count -gt 0 ) } `
    | Foreach-object{ Set-SCVirtualMachine -VM $_ -ClusterNonPossibleOwner ( @() ) | Out-Null }
    Gleb.

  • Database control in a two node oracle fail safe cluster

    os windows server 2003 r2
    db 10.2.0.4
    ofs 3.4.1
    i've configured db control in the following
    D:\oracle\product\10.2.0\db_1\BIN>emca -config dbcontrol db -repos recreate -cluster_name name_of_the_cluster
    is this right?
    next question
    the -cluster flag and the -EM_NODE / -EM_SID_LIST parameters in the emca are only for rac?
    with my configuration i can't login to my database over dbcontrol
    Listener refused the connection with the following error: ORA-12514, TNS:listener does not currently know of service requested in connect descriptor The Connection descriptor used by the client was: (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=node1.blah)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=ABBA)))

    How to Configure the 10.2 DB Control in a Failsafe Environment
    ID: 452305.1
    HOWTO: PUBLISHED 17-OCT-2008
    In this Document
       Goal
       Solution
       References
    Applies to:
    Enterprise Manager Grid Control - Version: 10.2.0.1 to 10.2.0.3
    Information in this document applies to any platform.
    Goal
    The goal of the document is to provide the steps to configure the DB Console in an Oracle Failsafe environment.
    Please note that the solution offered in this document is not certified by Oracle. It's only provided as a workaround for customers who wish to use this setup for the Database Control Console in a failsafe environment. Support for the procedure outlined in this document will be provided on a 'best efforts' approach.
    As an alternative to this approach you can use Grid Control Agents to monitor a database in a failsafe environment. For more details please see:
    Note 396659.1  How To Setup Grid Control Central Agent Manually in Oracle Failsafe Environment
    We assume the following:
    - the database binaries are installed on each node on the local disk
    - you already have a failsafe group with the database, the listener, disk resource, and virtual
    ip/hostname
    Note: This is specific for Windows environments using Oracle Failsafe. For setting up the DB Console in Active/Passive clusters on UNIX please use the following note instead:
    Note 362524.1 Configure DB Control 10.2 for use in Active/Passive High Availability Environments
    Solution
    1. Drop the DB Control repository and configuration files on the active node:
    <ORACLE_HOME>/bin/emca -deconfig dbcontrol db -repos drop
    2. Recreate the DB Control using the virtual hostname:
    - in a command window do the following:
    set oracle_sid=<your_sid>
    set oracle_home=<your_oracle_home>
    set oracle_hostname=<virtual_hostname>
    cd %oracle_home%\bin
    emca -config dbcontrol db -repos create
    -- make sure that the virtual host name was picked up by emca (it will display a summary screen
    before continuing)
    3. Verify that the DB Console works fine and can be accessed using the virtual host name in the URL
    4. Stop the DB Console
    5. Create a directory path on the group disk resource similar to your oracle home path on the local disk.
    For example:
    If the oracle home on the local disk is C:\oracle\product\10.2.0\db_1 and the shared disk is D:
    then create the following path: D:\oracle\product\10.2.0\db_1
    Copy C:\oracle\product\10.2.0\db_1\<hostname_sid> and
    C:\oracle\product\10.2.0\db_1\oc4j\j2ee\OC4J_DBConsole_<hostname_sid>
    to D:\oracle\product\10.2.0\db_1\<hostname_sid> and respectively
    D:\oracle\product\10.2.0\db_1\oc4j\j2ee\OC4J_DBConsole_<hostname_sid>
    Remember to change the values enclosed in <> with those in your environment.
    6. Delete the following directories from the local disk
    C:\oracle\product\10.2.0\db_1\<hostname_sid>
    C:\oracle\product\10.2.0\db_1\oc4j\j2ee\OC4J_DBConsole_<hostname_sid>
    7. Create NTFS junction points from the local disk to the shared disk (these work like symbolic
    links on UNIX) . It is your responsibility to create these.
    You can find a brief guide as well as some tools that will help you create them at:
    http://en.wikipedia.org/wiki/NTFS_junction_point
    http://www.microsoft.com/technet ... dDisk/Junction.mspx
    Important: Please note that this functionality is not certified nor supported by Oracle. Make sure you understand the
    implications. Especially don't delete the junction points from Windows Explorer !!
    In the end you should have the junction points on the local disk (with the same names as the
    original directories) that would point to the directories you copied on the shared disk.
    8. Start the DB Console service and verify that everything is still working fine.
    9. Stop the DB Console service.
    10. Move the Fail Safe group to the 2nd node.
    11. Once the database is started, create the DB Console configuration files on the 2nd node:
    <ORACLE_HOME>/bin/emca -config dbcontrol db
    12. Stop the DB Console
    13. Delete the created configuration files from the local disk:
    C:\oracle\product\10.2.0\db_1\<hostname_sid>
    C:\oracle\product\10.2.0\db_1\oc4j\j2ee\OC4J_DBConsole_<hostname_sid>
    14. Create junction points from the local disk to the directories already located on the shared
    disk.
    15. Start the DB Console service and verify that is working fine.
    16. Add the DB Console service as a resource to the fail safe group and put dependencies on the
    database and listener services.
    17. Perform a fail over and see if everything works fine.
    References
    Note 298238.1 - Oracle10g Grid Control with Oracle Fail Safe
    Note 362524.1 - Configure DB Control 10.2, 11g for use in Active/Passive High Availability Environments
    Note 396659.1 - How To Setup Grid Control Central Agent Manually in Oracle Failsafe Environment
    Keywords
    EMCA ; DB~CONTROL ; FAILSAFE ; DBCONTROL ; ENTERPRISE~MANAGER ;

  • Ora Fail Safe - under cluster ctl on one node but gives FS:10413  on other

    Hi,
    Trying to set up a single Fail Safe (3.3.3) instance (9.2) on a set of Windows 2003 servers running MSCS.
    After creating the standalone DB on the first node, I was able to get it verified and added to the cluster control (while the second server was down - had to this as the error I'm about to mention kept rolling back the changes on both nodes, otherwise). Now that the first node is configured and the FS listener service and FS DB service are created, I tried setting the second node to match the first one (viz. getting listener.ora, sqlnet.ora and even tnsnames.ora).
    The "verify group" operation kept failing on creation of the Windows FS service for the DB and listener.
    Found out that there was an issue with picking up the Oracle_Home when even trying to invoke sqlplus manually from the command line (though the registry entries seemed to be right and match the ones set on the first node). Eventually on adding the ORACLE_HOME variable to the list of env variables, it started picking up the OH correctly and the next "verify group" operation successfully added the WIndows FS service for the DB (OracleService{SID}) on the second node. (The first node didn't have to encounter these problems as during the standalone DB install (using DBCA), this service was created).
    Next, started the Windows FS DB service (on the second node with the problem) and tried starting the DB manually (out of cluster controll) and it worked fine.
    However when trying to "verify group" again, I keep getting the error FS-10413 (and the subsequent FS:10046, FS:10111 and FS:10890) while trying to add the Windows FS listener service (OracleORA_HOMETNSListenerFsl{oradb_virtual_name}).
    Could really do with extra eyes (and heads) helping to get to the bottom of this. Thanks.
    <<< The gist of the output from the "verify group" action is below >>>
    13 18:29:18 > FS-10300: Verifying Oracle Net listener resource OracleORA_HOME1TNSListenerFsloradbl
    14 18:29:19 Oracle Net listener Fsloradbl for the group is not found
    FS-10413: Error found in Oracle Net on node PANTHER; the group listener needs to be taken offline. Do you want it to be fixed? > Yes
    15 18:29:19 >> FS-10600: Oracle Net configuration file updated: C:\ORACLE\PRODUCT\9.2\NETWORK\ADMIN\LISTENER.ORA
    16 18:29:20 ** ERROR : FS-10066: Failed to start Windows service OracleORA_HOME1TNSListenerFsloradbl for the Oracle Net listener
    <<<< >>>>>>>
    Further to typing the above, read the section 7.10.8.2 in "Oracle Fail Safe Concepts and Admin guide" (http://download-uk.oracle.com/docs/html/B12070_01/ofs_db.htm#sthref985) and checked the output log. Bizarrely, the output file has a few "msg not found" errors (akin to when it doesn't find the correct OH).
    Wonder where this has to be set in the registry!?!
    The TNS-01151 (missing listener name in listener.ora) error is also a bit odd as this is the new listener OFS is trying to create and add to the new listener.ora file. Isn't it!?!?!
    <<<< Fsloradbl.out >>>>>
    LSNRCTL for 32-bit Windows: Version 9.2.0.7.0 - Production on 07-FEB-2007 21:50:46
    Copyright (c) 1991, 2002, Oracle Corporation. All rights reserved.
    Starting tnslsnr: please wait...
    TNSLSNR for 32-bit Windows: Version 9.2.0.7.0 - Production
    Message 279 not found; No message file for product=NETWORK, facility=NL
    TNS-01151: Message 1151 not found; No message file for product=NETWORK, facility=TNS     [Fsloradbl]
    Listener failed to start. See the error message(s) above...
    <<<< >>>>
    Thanks for your time (reading and hopefully responding to this) and any comments or suggestions.
    Regards,
    Ranjit

    yes i did. i mean, the db starts corretly using the Enteprise Manager and listener.ora and tnsnames.ora are the ones created during db creation. they seem alright.
    i'm trying to execute those commands from the node of the cluster where the db resides.
    but... i have one big question: do i have to create the db instance on BOTH cluster nodes (both pointing to the same oradata in the shared disk) or is it enough to create my standalone db only on the nodeA and then let everything to the FailSafe management (adding the standalone db to the cluster group FailSafe creates all the services needed)???
    thanks

  • Oracle fail safe error "FS-10784" failed to register database with group

    Hi,
    I'm getting following error while registering database to FS manager group.
    Version is -
    1) Fail safe 3.4.2
    2) Database 11.2
    3) 64 bit windows
    I executed following steps in order to create FS.
    1)     Install 11.2 software on node 1
    2)     Install 11.2 software on node 2
    3)     Install OFS 3.4.2 on node 1
    4)     Install OFS 3.4.2 on node 2
    5)     Create cluster tree from FS manager
    Below is the complete error..
    Versions: client = 3.4.1 server = 3.4.2 OS =
    Operation: Adding resource "COMPACTOR" to group "dbclusterdtc"
    Starting Time: Dec 01, 2011 18:25:31
    Elapsed Time: 0 minutes, 3 seconds
    1 18:25:31 Starting clusterwide operation
    2 18:25:32 FS-10370: Adding the resource COMPACTOR to group dbclusterdtc
    3 18:25:32 FS-10371: CSIPLAPP1DB2 : Performing initialization processing
    4 18:25:32 FS-10371: CSIPLDB1APP2 : Performing initialization processing
    5 18:25:32 FS-10372: CSIPLAPP1DB2 : Gathering resource owner information
    6 18:25:32 FS-10372: CSIPLDB1APP2 : Gathering resource owner information
    7 18:25:32 FS-10373: CSIPLAPP1DB2 : Determining owner node of resource COMPACTOR
    8 18:25:33 FS-10374: CSIPLAPP1DB2 : Gathering cluster information needed to perform the specified operation
    9 18:25:33 FS-10374: CSIPLDB1APP2 : Gathering cluster information needed to perform the specified operation
    10 18:25:33 FS-10375: CSIPLAPP1DB2 : Analyzing cluster information needed to perform the specified operation
    11 18:25:33 >>> FS-10652: CSIPLAPP1DB2 has Oracle Database version 11.2.0.1 installed in OraDb11g_home2
    12 18:25:33 >>> FS-10652: CSIPLDB1APP2 has Oracle Database version 11.2.0.1 installed in OraDb11g_home2
    13 18:25:33 FS-10376: CSIPLAPP1DB2 : Starting configuration of resource COMPACTOR
    14 18:25:33 FS-10378: CSIPLAPP1DB2 : Preparing for configuration of resource COMPACTOR
    15 18:25:33 FS-10380: CSIPLAPP1DB2 : Configuring virtual server information for resource COMPACTOR
    16 18:25:33 ** ERROR : 0xEA: More data is available.
    17 18:25:33 > FS-10496: Generating the Oracle Net migration plan for COMPACTOR
    18 18:25:33 ** ERROR : FS-10990: The error 0x800400EA was reported as a system error, but the error message cannot be found
    19 18:25:33 ** ERROR : FS-10757: A COM error was returned when trying to send a work item to the worker
    20 18:25:33 ** ERROR : FS-10784: The Oracle Database resource provider failed to configure the virtual server for resource COMPACTOR
    21 18:25:33 ** ERROR : FS-10890: Oracle Services for MSCS failed during the add operation
    22 18:25:33 ** ERROR : FS-10497: Starting clusterwide rollback of the operation
    23 18:25:34 FS-10488: CSIPLAPP1DB2 : Starting rollback of operation
    24 18:25:34 FS-10489: CSIPLAPP1DB2 : Completed rollback of operation
    25 18:25:34 ** ERROR : FS-10495: Clusterwide rollback of the operation has been completed
    26 18:25:34 Please check your Windows Application log using the Event Viewer for any additional errors
    27 18:25:34 The clusterwide operation failed !
    Inputs are appreciable.
    Regards

    After applying patch of 3.4.2.3, still i'm facing this problem. But however there are very less errors....I think the problem is with Listener.
    1 20:34:03 Starting clusterwide operation
    2 20:34:04 FS-10370: Adding the resource COMPACTOR to group dbclusterdtc
    3 20:34:04 FS-10371: CSIPLAPP1DB2 : Performing initialization processing
    4 20:34:04 FS-10371: CSIPLDB1APP2 : Performing initialization processing
    5 20:34:05 FS-10372: CSIPLAPP1DB2 : Gathering resource owner information
    6 20:34:05 FS-10372: CSIPLDB1APP2 : Gathering resource owner information
    7 20:34:05 FS-10373: CSIPLAPP1DB2 : Determining owner node of resource COMPACTOR
    8 20:34:05 FS-10374: CSIPLAPP1DB2 : Gathering cluster information needed to perform the specified operation
    9 20:34:05 FS-10374: CSIPLDB1APP2 : Gathering cluster information needed to perform the specified operation
    10 20:34:05 FS-10375: CSIPLAPP1DB2 : Analyzing cluster information needed to perform the specified operation
    11 20:34:05 >>> FS-10652: CSIPLAPP1DB2 has Oracle Database version 11.2.0.1 installed in OraDb11g_home2
    12 20:34:05 >>> FS-10652: CSIPLDB1APP2 has Oracle Database version 11.2.0.1 installed in OraDb11g_home2
    13 20:34:05 FS-10376: CSIPLAPP1DB2 : Starting configuration of resource COMPACTOR
    14 20:34:05 FS-10378: CSIPLAPP1DB2 : Preparing for configuration of resource COMPACTOR
    15 20:34:05 FS-10380: CSIPLAPP1DB2 : Configuring virtual server information for resource COMPACTOR
    16 20:34:06 > FS-10496: Generating the Oracle Net migration plan for COMPACTOR
    17 20:34:06 > FS-10490: Configuring the Oracle Net listener for COMPACTOR
    18 20:34:06 >> FS-10600: Oracle Net configuration file updated: D:\APP\ORACLE\PRODUCT\11.2.0\DBHOME_2\NETWORK\ADMIN\LISTENER.ORA
    19 20:34:06 >> FS-10606: Listener configuration updated in database parameter file: M:\Datafiles\compactor\spfilecompactor.ora
    20 20:34:13 >> FS-10605: Oracle Net listener Fsldbclusterdtc created
    21 20:34:14 ** ERROR : 0x426: The service has not been started.
    22 20:34:14 ** ERROR : FS-10066: Failed to start Windows service OracleOraDb11g_home2TNSListener for the Oracle Net listener
    23 20:34:14 ** ERROR : FS-10065: Error trying to configure the Oracle Net listener
    24 20:34:14 > FS-10090: Rolling back Oracle Net changes on node CSIPLAPP1DB2
    25 20:34:17 ** ERROR : FS-10784: The Oracle Database resource provider failed to configure the virtual server for resource COMPACTOR
    26 20:34:17 ** ERROR : FS-10890: Oracle Services for MSCS failed during the add operation
    27 20:34:17 ** ERROR : FS-10497: Starting clusterwide rollback of the operation
    28 20:34:17 FS-10488: CSIPLAPP1DB2 : Starting rollback of operation
    29 20:34:17 FS-10489: CSIPLAPP1DB2 : Completed rollback of operation
    30 20:34:17 ** ERROR : FS-10495: Clusterwide rollback of the operation has been completed
    31 20:34:17 Please check your Windows Application log using the Event Viewer for any additional errors
    32 20:34:17 The clusterwide operation failed !

  • SQL AlwaysOn Availability Group modifies preferred owner node on move/failover

    I have a two node Windows Server 2012 R2 failover cluster with two SQL Server 2012 Enterprise AlwaysOn Availability groups configured. Within the cluster I have configured a preference order on which node a AlwaysOn Availability Group should run.
    Get-ClusterGroup -Name "AlwaysOn1" | Set-ClusterOwnerNode -Owners "node1","node2";
    Get-ClusterGroup -Name "AlwaysOn2" | Set-ClusterOwnerNode -Owners "node2","node1";
    After configuring the preference and retrieving the preference order it is configured as it should be. When I do a failover the preference order is adjusted to first the node it currently runs on and second the other node instead of leaving the preference
    order as it was. It doesn't matter if I use the PowerShell "Move-ClusterGroup" or the "ALTER AVAILABILITY GROUP [AlwaysOn1] FAILOVER" T-SQL command. From the cluster log it is shown that the preference is modified after the resource
    has been moved.
    INFO  [GUM] Node 2: executing request locally, gumId:15859, my action: /rcm/gum/SetGroupPreferredOwners, # of updates: 1
    INFO  [RCM] rcm::RcmGum::SetGroupPreferredOwners(AlwaysOn1,<vector len='2'>
    The default groups within the cluster "Available Storage" and "Cluster Group" keep their preference setting when configured (only configured for testing to verify it has to do with the SQL Server Availability Group resource type).
    The Windows Server 2012 R2 servers are updated using the latest Windows Updates and SQL 2012 has build number 11.0.5556.
    For other cluster groups which I have configured in the past like file, Hyper-V (used for affinity to get VM's which have a lot of traffic between them within the same virtual switch to reduce latency and additional hops. it would be nice if vNext will have
    a affinity option for cluster groups besides the anti-affinity within the current version)
    I would like to know if someone could explain why the SQL Server Availability Group resource always modifies the group preference. I might understand this with a three node cluster where the first two are running in Synchronous commit mode and the third
    one in Asynchronous commit mode.
    Thanks in advance,
    Dennis van den Akker

    Hi Dennis van den Akker,
    Do not use the Failover Cluster Manager to manipulate availability groups, for example:
    Do not add or remove resources in the clustered service (resource group) for the availability group.
    Do not change any availability group properties, such as the possible owners and preferred owners. These properties are set automatically by the availability group.
    Do not use the Failover Cluster Manager to move availability groups to different nodes or to fail over availability groups. The Failover Cluster Manager is not aware of the synchronization status of the availability replicas, and doing so can lead to extended
    downtime. You must use Transact-SQL or SQL Server Management Studio.
    The related KB:
    Failover Clustering and AlwaysOn Availability Groups (SQL Server)
    https://msdn.microsoft.com/en-us/library/ff929171.aspx
    The similar thread:
    SQL Server Clustering 2008 (Multi Node)
    https://social.msdn.microsoft.com/Forums/sqlserver/zh-CN/c35fe863-3fed-4a6e-830b-b79aa032c198/sql-server-clustering-2008-multi-node?forum=sqldisasterrecovery
    Best Regards,
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • RMAN Automatic backup/recovery with oracle fail safe, windows cluster

    Hello,
    I have question,
    1) Whether it is possible to do "RMAN Automatic Backup and recovery" in environment as ?
    Environment: -
    a. Windows clustering with windows server 2003 Enterprise Edition R2 (Two Node Clustering)
    b. Shared disk ( RAID )
    c. Oracle 10g standard edition one
    d. Oracle fail safe v3.3.3 (for redundancy)
    Here we have single oracle instance operating on single database whose files are located on shared disk.
    2) If answer to above question is yes please specify if there is some good documentation to it.
    Any help regarding this will be greatly appreciated.
    Thanks in advance,
    Rahul

    You just need to make sure that the RMAN scripts are always able to connect to the target database instance whether instance runs on cluster node 1 or cluster node 2
    here, If oracle services(resources) will shift from Node1 to Node2 (due to media or any failure) during RMAN Backup then there will be break in connection, will it destroy my backup or will it get started automatically without any harm?
    and also I want to know,
    Do we need to setup another server which will have RMAN backup script running?

  • Fail Safe adding database to group gives error "FS-10006: Unable to open.."

    Environment:
    Fail Safe 3.4.2
    Oracle 11.2.0.1 64bit
    Windows 2008 Server 64bit
    Two nodes in an active/passive cluster using windows clustering and oracle fail safe.
    Problem:
    We have created the windows cluster, installed fail safe on both clustered nodes, installed the database software, verified the cluster, created a group and added a virtual address to the group. We also managed to verify the stand alone database instance without any issues. However, when we try to add the database to the group we get the following errors:
    Versions:  client = 3.4.1    server = 3.4.2    OS = 
    Operation:   Adding resource "THORD" to group "EO_THORD_GRP" 
    Starting Time:   Jul 26, 2010   16:23:04
    Elapsed Time:   0 minutes, 2 seconds
    1   16:23:04  Starting clusterwide operation
    2   16:23:05  FS-10370: Adding the resource THORD to group EO_THORD_GRP
    3   16:23:05  FS-10371: ClusterNode1 : Performing initialization processing
    4   16:23:05  FS-10371: ClusterNode2 : Performing initialization processing
    5   16:23:05  FS-10372: ClusterNode1 : Gathering resource owner information
    6   16:23:05  FS-10372: ClusterNode2 : Gathering resource owner information
    7   16:23:05  FS-10373: ClusterNode1 : Determining owner node of resource THORD
    8   16:23:05  FS-10374: ClusterNode1 : Gathering cluster information needed to perform the specified operation
    9   16:23:05  FS-10374: ClusterNode2 : Gathering cluster information needed to perform the specified operation
    10  16:23:05  FS-10375: ClusterNode1 : Analyzing cluster information needed to perform the specified operation
    11  16:23:05   >>> FS-10652: ClusterNode1 has Oracle Database version 11.2.0.1 installed in OraDb11g_home1
    12  16:23:05   >>> FS-10652: ClusterNode2 has Oracle Database version 11.2.0.1 installed in OraDb11g_home1
    13  16:23:05  FS-10376: ClusterNode1 : Starting configuration of resource THORD
    14  16:23:05  FS-10378: ClusterNode1 : Preparing for configuration of resource THORD
    15  16:23:05  FS-10380: ClusterNode1 : Configuring virtual server information for resource THORD
    16  16:23:05    ** ERROR : 0x138F: The cluster resource could not be found.
    17  16:23:06    ** ERROR : FS-10006: Unable to open the resource
    18  16:23:06    ** ERROR : FS-10012: Failed to bring the cluster resource  online. Check the Windows event log for messages
    19  16:23:06    ** ERROR : FS-10784: The Oracle Database resource provider failed to configure the virtual server for resource THORD
    20  16:23:06    ** ERROR : FS-10890: Oracle Services for MSCS failed during the add operation
    21  16:23:06    ** ERROR : FS-10497: Starting clusterwide rollback of the operation
    22  16:23:06  FS-10488: ClusterNode1 : Starting rollback of operation
    23  16:23:06  FS-10489: ClusterNode1 : Completed rollback of operation
    24  16:23:06    ** ERROR : FS-10495: Clusterwide rollback of the operation has been completed
    25  16:23:06  Please check your Windows Application log using the Event Viewer for any additional errors
    26  16:23:06  The clusterwide operation failed !
    FS-10006: Unable to open the resourceAll the cluster resources seem to be online. We're all out of ideas here, can someone please shead some light on this or have any ideas how we can go on about this.
    Your help is highly appreciated.
    Thanks

    I am getting into the issue (step-6) when I run standalone resource verify after successful step-5 and need your advice.
    I will give you information about the infrastructure -
    NODE1-2K8-ORADBND1
    NODE2-2K8-ORADBND2
    Cluster IP-
    Virtual IP on NODE1 and NODE2 host file -
    OS - Windows 2008 R2 64 bit
    Oracle Database - 11gR2
    Oracle FailSafe - 3.4.1.6
    Oracle SID- ORA11
    (ORA11 is up and running on NODE1 active node while running add to group option from - Groups/Standalone Resources to verify the instance and it gets error)
    Here is the error log -
    Versions: client = 3.3.3 ; server = 3.4.1 ; OS =
    Operation: Adding resource "ORA11" to group "Available Storage"
    Starting Time: Sep 02, 2010 12:50:06
    Elapsed Time: 0 minutes, 1 seconds
    1 12:50:06 Starting clusterwide operation
    2 12:50:06 FS-10370: Adding the resource ORA11 to group Available Storage
    3 12:50:06 FS-10371: 2K8-ORADBND1 : Performing initialization processing
    4 12:50:06 FS-10371: 2K8-ORADBND2 : Performing initialization processing
    5 12:50:07 FS-10372: 2K8-ORADBND1 : Gathering resource owner information
    6 12:50:07 FS-10372: 2K8-ORADBND2 : Gathering resource owner information
    7 12:50:07 FS-10373: 2K8-ORADBND1 : Determining owner node of resource ORA11
    8 12:50:07 FS-10374: 2K8-ORADBND1 : Gathering cluster information needed to perform the specified operation
    9 12:50:07 ** ERROR : FS-10791: The Oracle Database resource provider failed while gathering cluster information for resource ORA11
    10 12:50:07 ** ERROR : FS-10890: Oracle Services for MSCS failed during the add operation
    11 12:50:07 Please check your Windows Application log using the Event Viewer for any additional errors
    12 12:50:07 The clusterwide operation failed !
    Thanks for your help!

  • Upgrade a database from 10.2.0.1 to 10.2.0.4 in a fail safe cluster

    Hi,
    I need to upgrade from oracle 10.2.0.1 (base) to 10.4.0.4 in a fail-safe cluster.
    Questions:
    1.If I upgrade each node as a alone server, ¿fail-safe cluster can run with 2 nodes in diferent versions? (for example one week,for rollback )
    2. I have read how to upgrade a fail-safe cluster metalink document. Please, can somebody tell me the best form (or logical) to upgrade from 10.2.0.1 to 10.2.0.4 in this cluster?
    for example:
    1. Backup database
    2. Upgrade node 1 to 10.2.0.1 to 10.2.0.4 (following metalink document)
    3. Test database and applications
    4. One week later the same in node 2 (only if it is possibly run oracle in different versions in failsafe, if not, install node 2 after node 1 works fine)
    It´s my first failsafe environment, and i´m not sure how to do it.
    Thanks a lot for your help!!!

    Welcome to the forums !
    Pl see if MOS Doc 223709.1 (How to upgrade or apply a patch to the RDBMS in an Oracle Fail Safe environment) can help. I have no personal experience with Fail Safe.
    HTH
    Srini

  • Error in Creating the Oracle Fail Safe Group during installation on MSCS

    Hi All,
    I am installing ECC 6 dual stack on MSCS.
    I have done steps till CI installation as per installation guide.
    I am gettig the following error in the step "Creating the Oracle fail safe group" while changing physical hostname into the virtual databse hostname using configtool in secure store parameter jdbc/pool/<SAPSID>Url as per the installation guide.
    "Error occurred while working with configuration(scanning)
    MSG:Error while connecting to the database"
    I think it is not accepting the virtual hostname.
    In our scenario CI is running CI node and DB instance is running on DB node.
    I have followed the steps as per the installation guide.
    Please let me know how to resolve this issue.
    Database - Oracle 10g,OS is Windows server 2008 enterprse edition.
    Regards,
    Dinakar
    Edited by: mutnuru dinakar on Jun 1, 2011 1:39 PM
    Edited by: mutnuru dinakar on Jun 1, 2011 1:40 PM

    Hi,
    Thanks for your reply.
    1) did you stop the CI before making the modifications as stated in the installation guide?
         Yes
    2) is your database currently running on the same physical cluster node as your CI?
        No.Database instance is running on DB node and CI is on CI node.
    3) is your database online?
         Yes,it is up and running
    Please let me know if there is anyway to resolve this issue.
    Regards,
    Dinakar

  • Error while adding oracle database resource to the fail safe group

    Hi,
    we are installaing ERP 6.0 EHP4 , oracle10.2.04  in MSCS
    During the step, Adding the oracle Database Resource to the fail safe
    group , I am getting the error.
    28  13:21:57    ** WARNING : FS-10288: Parameter file C:\oracle\BCP\102\database\init<SID>_OFS.ora is not located on a cluster disk
    29  13:21:57    ** WARNING : FS-10404: The database uses a nonclustered disk in one of the system parameters.  Value of parameter is C:\ORACLE\<SID>\102\RDBMS\AUDIT
    30  13:21:58    ** ERROR : FS-10036: The resource uses disk SAP HDD, which is also used by cluster resource SAP VIP in another group
    31  13:21:58    ** ERROR : FS-10778: The Oracle Database resource provider failed to configure the cluster resource <SID>.WORLD
    32  13:21:58    ** ERROR : FS-10890: Oracle Services for MSCS failed during the add operation
    33  13:21:58    ** ERROR : FS-10497: Starting clusterwide rollback of the operation
    34  13:21:58  FS-10488:<primary node name> : Starting rollback of operation
    35  13:21:58   > FS-10090: Rolling back Oracle Net changes on node <primary node name>
    I am having one local disk C: one shared disk Z: and quorum disk Q:
    Shared disk Z: is already used for SAP<sid> group.
    Regards,
    Joel

    Joeldhanaraj wrote:>
    > Hi,
    >
    > we are installaing ERP 6.0 EHP4 , oracle10.2.04  in MSCS
    >
    > During the step, Adding the oracle Database Resource to the fail safe
    > group , I am getting the error.
    >
    > 28  13:21:57    ** WARNING : FS-10288: Parameter file C:\oracle\BCP\102\database\init<SID>_OFS.ora is not located on a cluster disk
    > 29  13:21:57    ** WARNING : FS-10404: The database uses a nonclustered disk in one of the system parameters.  Value of parameter is C:\ORACLE\<SID>\102\RDBMS\AUDIT
    > 30  13:21:58    ** ERROR : FS-10036: The resource uses disk SAP HDD, which is also used by cluster resource SAP VIP in another group
    > 31  13:21:58    ** ERROR : FS-10778: The Oracle Database resource provider failed to configure the cluster resource <SID>.WORLD
    > 32  13:21:58    ** ERROR : FS-10890: Oracle Services for MSCS failed during the add operation
    > 33  13:21:58    ** ERROR : FS-10497: Starting clusterwide rollback of the operation
    > 34  13:21:58  FS-10488:<primary node name> : Starting rollback of operation
    > 35  13:21:58   > FS-10090: Rolling back Oracle Net changes on node <primary node name>
    >
    > I am having one local disk C: one shared disk Z: and quorum disk Q:
    >
    > Shared disk Z: is already used for SAP<sid> group.
    Hi Joel,
    how about following the advice given by the error message and moving the mentioned files/folder (init<sid>_OFS.ora, AUDIT folder) to a clustered resource disk?
    just my 2 pence...

  • Issue while adding DB resources to the fail safe group

    Hi,
    we are installaing ERP 6.0 EHP4 , oracle10.2.04 in MSCS
    During the step, Adding the oracle Database Resource to the fail safe
    group , I am getting the error.
    28 13:21:57 ** WARNING : FS-10288: Parameter file C:\oracle\BCP\102\database\init<SID>_OFS.ora is not located on a cluster disk
    29 13:21:57 ** WARNING : FS-10404: The database uses a nonclustered disk in one of the system parameters. Value of parameter is C:\ORACLE\<SID>\102\RDBMS\AUDIT
    30 13:21:58 ** ERROR : FS-10036: The resource uses disk SAP HDD, which is also used by cluster resource SAP VIP in another group
    31 13:21:58 ** ERROR : FS-10778: The Oracle Database resource provider failed to configure the cluster resource <SID>.WORLD
    32 13:21:58 ** ERROR : FS-10890: Oracle Services for MSCS failed during the add operation
    33 13:21:58 ** ERROR : FS-10497: Starting clusterwide rollback of the operation
    34 13:21:58 FS-10488:<primary node name> : Starting rollback of operation
    35 13:21:58 > FS-10090: Rolling back Oracle Net changes on node <primary node name>
    I am having one local disk C: one shared disk Z: and quorum disk Q:
    Shared disk Z: is already used for SAP<sid> group.
    Regards
    Joel

    No crossposting please!
    Error while adding oracle database resource to the fail safe group

  • Installation of oracle fail safe on windows cluster - plz very urgent

    hi everybody,
    this is the first time i am going to install oracle failsafe on windows clusters.
    i am going to install oracle 9i release 2 software.
    so i have to install the patches.
    plz tell me with oracle cmds how to do the following.
    1. after installing oracle 9i rel 2 how to install the patches to it in windows environment?
    2. how to create oracle database on one node using shared disk for storage.
    3. how to install oracle fail safe on each cluster?
    4. how to configure cluster using fail safemanager?
    plz provide me soln asap very urgent.
    and don't forget to give me the soln with commands aqnd step by step.
    plz plz plz
    thanks in advance
    suresh

    For 9i , this is better:
    http://download-uk.oracle.com/docs/cd/B10501_01/rac.920/a96600/toc.htm

  • Fail Safe Virtual IP Problems

    I have a Windows 2008 R2 SP1 2 node active/passive cluster with fail safe 3.4.2 installed. I also have 11G database software installed. My problem is I am unable to successsfully add an oracle virtual IP to the oracle group within fail safe. I receive the below error when I try. Can anyone please help me in the right direction with this? I need to get this resolved so that I can add my databases to the cluster. Thank you.
    Oracle Fail Safe Manager
    FS-10890: Oracle Services for MSCS failed during the create operation
    FS-11220: Failed to create the virtual address
    FS-10012: Failed to bring the cluster resource Network Name HHVHAVELP01 online. Check the Windows event log for messages.
    FS-10726: Resource Network Name HHVHAVELP01 is in a failed state
    I don't see any message in the event log when I check...

    Hi,
    Your problem looks-like this metalink note 416339.1
    Check it on oracle support.

  • Fail safe cannot move Group

    Hello, i have installed Windows 2003 with Microsoft Cluster and 4 Nodes, Oracle fail Safe 3.3.2.
    The Problem is i can move the Groups using MCSC but when i try to move a group with FS-Manager nothing is done.
    I press the button move group nothing happens.
    can you help me ?
    Helmut

    Here is the error, in more details:
    Mon Sep 19 22:49:59 [srvr1] <DB_RES> ORCL.WORLD starting
    Mon Sep 19 22:49:59 [srvr1] <DB_RES> ORCL.WORLD connect as user "SYS", password is supplied, SYSDBA, PRELIM_AUTH
    Mon Sep 19 22:49:59 [srvr1] <DB_RES>  using bequeath
    Mon Sep 19 22:49:59 [srvr1] <DB_RES> ORCL.WORLD OCIServerAttach attach string "(DESCRIPTION=(ADDRESS=(PROTOCOL=BEQ)(PROGRAM=oracle)(ARGV0=oracleORCL)(ARGS='(DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))'))(CONNECT_DATA=(SID=ORCL)(CID=(PROGRAM=C:\WINDOWS\cluster\resrcmon.exe)(HOST=srvr1)(USER=DOMAIN\userservice))))"
    Mon Sep 19 22:49:59 [srvr1] <DB_RES> ORCL.WORLD ***** OCI routine OCIServerAttach Bequeath returned error -1 - OCI_ERROR
    Mon Sep 19 22:49:59 [srvr1] <COMMON> ORA-12631: Username retrieval failed
    Mon Sep 19 22:49:59 [srvr1] <DB_RES> ORCL.WORLD disconnect
    Mon Sep 19 22:49:59 [srvr1] <DB_RES> Event start
    Oracle Fail Safe resource ORCL.WORLD failed to start.
    ORA-12631: Username retrieval failed

Maybe you are looking for