Automatic failover

Dear all,
10.2.0.3 on windows 2003.
One of our clients wants to have a DR site of their primary rac database and insist to have automatic failover to DR site ?.
Please suggest me what are all the options available to implement DR site with automatic failover enabled ?
Kai

Dear KaiS,
If you are talking about a "Disaster Recovery" than you need to configure Oracle Data Guard.
If you are talking about a "replication of the primary database" than you can use Oracle Streams.
Both technologies are well structed and documented.
The Data Guard configuration allows you to automatically failover or switchover to the standby site. This configuration is called the "observer". You can setup the observer to another location rather than the primary and standby database and it constantly monitors both sites in terms of availability.
Please refer to the Oracle's Online documentation --> http://tahiti.oracle.com/
Regards.
Ogan

Similar Messages

  • Automatic failover doesn't failback to the first server if the second server is lost.

    Hi Everybody,
       We use the database mirroring a lot in our product solutions and we have recently experienced a strange behaviour in our failover tests with SQL2008R2.
    We have 2 servers running Windows 2008 R2 standard and SQL 2008 R2 standard SP2. (let's call them DB1 and DB2)
    We also have a Witness workstation running SQL 2008 Express on a Windows 7
    A database from DB1 is mirrored to DB2 in "safety full" mode, with witness. At this stage, the database is principal on DB1 and mirror on DB2
    To test the automatic failover, we first restart the DB1 server which has the database in principal mode
    After a few seconds, the database on DB2 becomes principal, which is normal , that's exactly what we want.
    After a few minutes, DB1 comes back online and its database takes the mirror role (still OK). At this stage then, the database is principal on DB2 and mirror on DB1
    when the monitoring application shows that the mirror is synchronized and that both servers are connected to the witness, we restart DB2 to trigger an automatic failover to DB1.
    What we see is that DB1 never takes the principal role and the database stays in mirror.
    In the DB1 Errorlog, I only see these 2 lines when DB2 disappears, no other message related to the mirroring session.
    2014-01-22 08:57:26.91 spid43s     Starting up database 'Test123'.
    2014-01-22 08:57:26.95 spid43s     Bypassing recovery for database 'Test123' because it is marked as a mirror database, which cannot be recovered. This is an informational message only. No user action is required.
    When DB2 comes back online, the database on DB2 keeps its principal status and the database on DB1 stays mirror.
    And what is really really strange is that, if I restart DB2 once again, directly after that, DB1 failover normally and the database on DB1 takes the principal role after a few seconds. without any configuration changes between the 2 restarts.
    DB1 errorlog shows then :
    2014-01-22 09:00:37.53 spid29s     Error: 1474, Severity: 16, State: 1.
    2014-01-22 09:00:37.53 spid29s     Database mirroring connection error 4 'An error occurred while receiving data: '64(The specified network name is no longer available.)'.' for 'TCP://DB2:5022'.
    2014-01-22 09:00:37.53 spid18s     Database mirroring is inactive for database 'Test123'. This is an informational message only. No user action is required.
    2014-01-22 09:00:42.37 spid32s     The mirrored database "Test123" is changing roles from "MIRROR" to "PRINCIPAL" due to Auto Failover.
    2014-01-22 09:00:42.39 spid32s     Recovery is writing a checkpoint in database 'Test123' (7). This is an informational message only. No user action is required.
    2014-01-22 09:00:42.39 spid32s     Recovery completed for database Test123 (database ID 7) in 78 second(s) (analysis 0 ms, redo 0 ms, undo 7 ms.) This is an informational message only. No user action is required.
    So, if I summarize, 
    - a first failover from DB1 to DB2 always work
    - then, a restart of DB2 never failover to DB1
    - a second restart of DB2 always failover to DB1
    This is pretty much systematic on one our server couple.
    Any explanation for this or any idea where I can search to find the reason of this strange behavior ?
    Thanks a lot for your help
    Seb

    Thank you Tom
    But I have already checked that and reported the Errorlog abstracts in my original post.
    When DB01 disapears for the first time, nothing in the DB01 ERRORLOG (it is restarting :-) )
    AND no particular error message in the DB02 ERRORLOG (nothing related to the fact that DB01 is not reachable anymore !!! )
    Only these two lines
    2014-01-22 08:57:26.91 spid43s     Starting
    up database 'Test123'.
    2014-01-22 08:57:26.95 spid43s     Bypassing recovery
    for database 'Test123' because it is marked as a mirror database, which cannot be recovered. This is an informational message only. No user action is required.
    So my main question remains Why DB02 doesn't detect that DB01 disapears (and the first time only) and why the failover mechanism doesn't trigger the failover ?
    Thank you
    Seb

  • SQL 2005 mirroring : Abrupt Automatic failover

    hi All, 
    We have a SQL 2005 SP4 mirroring  setup of 15 DBs with Principal(P), Mirror(M) & Witness (W).
    We have now seen abrupt DB failovers for some of the databases (yest it was 4 out of 15) from P to M.
    Errors were seen on Witness server as follows for all Dbs that failed over:
    Date 07/01/2015 11:07:48 PM
    Log SQL Server (Current - 08/01/2015 12:00:00 AM)
    Source spid19s
    Message
    The mirroring connection to "TCP://<server.domain.com>:5022" has timed out for database "<DBName>" after 10 seconds without a response.  Check the service and network connections.
    Actions taken:
    1. Network and Firewall team reverted that no error detected and no network traffic between the witness server and db server during the db auto failover period.
    2. On the system side, we have verified that no hardware error found on either VM or SAN storage, and no Symantec SQL backup jobs running nor anti virus scanning during the db auto failover period too.
    3. We did see some high amount of IO activity on P server around failover time. Some IO errors similar to below were seen, however point to note is these errors were not only for the DBs that failed over, but for others including TEMPDB:
    Date 07/01/2015 11:07:38 PM
    Log SQL Server (Current - 08/01/2015 4:06:00 AM)
    Source spid2s
    Message
    SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [R:\SQLDATA\MSSQL.1\MSSQL\Data\<DBName>.mdf] in database [DBName] (5).  The OS file handle is 0x000000000000095C.  The offset of the
    latest long I/O is: 0x0000054ff22000
    Questions:
    1. I assumed that the Witness keeps polling P & M on DB mirroring endpoints (in our case 5022) to check that the DBs are online, but Network team says there is no activity on that port, is my understanding correct?
    2. Is there any other reason for DB failover ? 
    Link referred:  
    http://dba.stackexchange.com/questions/22402/what-can-cause-a-mirroring-session-to-timeout-then-failover-sql-server-2005
    http://msdn.microsoft.com/en-us/library/ms179344(v=sql.90).aspx
    Any help is highly appreciated!!!
    Regards,
    Mandar

    This is common with Mirroring server it is not as resilient to changes as log shipping. Are you aware about
    below fact although not directly related to your question
    If you plan to use high-safety mode with automatic failover, the normal load on each failover partner should be less than 50 percent of the CPU. If your work load overloads the CPU, a failover partner might be unable to ping the other server instances in
    the mirroring session. This causes a unnecessary failover. If you cannot keep the CPU usage under 50 percent, we recommend that you use either high-safety mode without automatic failover or high-performance mode.
    Now to your problem
    The mirroring connection to "TCP://<server.domain.com>:5022" has timed out for database "<DBName>" after 10 seconds without a response.  Check the service and network connections.
    I would say there was network dip for more than 10 seconds and since default failover time is 10 seconds and for few databases witness thought principal cannot be reached it initiated failover.
    Network team is incorrect to say there was no dip (its common with NOC team not to take responsibility)
    This Support Article is worth reading specially the network part
    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
    My Technet Wiki Article
    MVP

  • SQL 2012 Database Availability Group - Force Automatic Failover

    Hi All,
    I'd appreciate some help in understanding the following scenario in my test environment.
    I have created a DAG with 2 replica servers (both of which are HyperV VM's running W2012 Std).
    From a client PC in my test lab, I can connect to the virtual listener of my DAG and confirm via the "select @@servername" command that I am connecting to the primary replica server.
    Using the Failover Wizard, I can easily move to primary instance between my 2 nodes and the command above confirms that the primary replica server has changed. So far so good.
    What I wanted to test, was what would happen to my DAG in the event of a complete loss of power to the server that was acting as the primary replica server. At first, I thought I would stop the SQL Server service on the primary server, but this did not result
    in my DAG failing over to the secondary replica. I have found out that the only way I can do this is by effectively shutting down the primary server in a controlled manner.
    Is there any reason why either stopping the SQL Server service on the primary replica, or indeed forcing a power off of the primary replica does not result in the DAG failing over to the secondary replica?
    Thanks,
    Bob

    Hi,
    I would verify if Database Availability Group means AlwaysOn Availability Group.
    How did you set the FailureConditionLevel?
    Whether the diagnostic data and health information returned by sp_server_diagnostics warrants an automatic failover depends on the failure-condition level of the availability group. The failure-condition level specifies what failure conditions
    trigger an automatic failover. There are five failure-condition levels, which range from the least restrictive (level one) to the most restrictive (level five). For details about failure-conditions level, see:
    http://msdn.microsoft.com/en-us/library/hh710061.aspx#FClevel
    There are two useful articles may be helpful:
    SQL 2012 AlwaysOn Availability groups Automatic Failover doesn’t occur or does it – A look at the logs
    http://blogs.msdn.com/b/sql_pfe_blog/archive/2013/04/08/sql-2012-alwayson-availability-groups-automatic-failover-doesn-t-occur-or-does-it-a-look-at-the-logs.aspx
    SQL Server 2012 AlwaysOn – Part 7 – Details behind an AlwaysOn Availability Group
    http://blogs.msdn.com/b/saponsqlserver/archive/2012/04/24/sql-server-2012-alwayson-part-7-details-behind-an-alwayson-availability-group.aspx
    Thanks.
    Tracy Cai
    TechNet Community Support
    Hi,
    Thanks for the reply.
    It's an AlwaysOn Availability Group.
    In my test lab, I have changed the quorum configuration to a file share witness and that has allowed an automatic failover when I turn the primary replica server off (rather than power it off).
    I'll take a look at the links you provided.
    Regards,
    Bob

  • Unplanned automatic failover using Hyper-v Replica , why don't the VMs start up automatically on the replica server?

    Hi,
    We have cluster with two hosts (Host01 , host02) replicated to another server (Replica01)
    in order to test automatic failover to the replica server  (Replica01) We unplugged the power cables from Host01 and Host 02 
    now the VMs on the replica server is still off  , why don't the VMs start up  automatically on the replica server?
    Ramy Shaker

    overall there is no automatic failover in Hyper-V
    Of course there is. It's enabled by Failover Clustering. This is a totally separate technology from Hyper-V Replica.
    There is no automatic start up in Hyper-V Replica because it is not designed to detect a split-brain condition where the same virtual machine is running in multiple locations simultaneously. The replica site has no way to know why it can't reach the primary
    system anymore. It might just be because someone unplugged a network cable. If the primary's virtual machines are still running and the replica decides to spin up its copies, you will have many troubles.
    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."

  • HACMP Clustering Script for SAP ECC 6.0 (SR1) - Automatic Failover

    Hello,
    I have installed the SAP ECC 6.0 (SR1) under AIX 5.3 / DB2 V8 FP12 with HACMP Clustering environment. Manual Failover is working fine. Central System has been installed in share drive with Virtual IP and Virtual name inNode A. Dialog Instance is loaded locally in Node B. I want to get HACMP Clustering script(automatic failover script) for Automation. Please help me if you have. It is single package clustering. If Node A fails, Node B will take care ( Central System and Dialog instance will run in Node B)
    Thanks
    Gautam Poddar

    this post is duplicated at Upgrade to ERP 2005/ECC 6.0 from  R/3 4.72/Basis 640 on Z/OS 1.4 DB2 8.1

  • HACMP Clustering Script for SAP ECC 6.0 (SR1) - Automatic Failover-Oracle10

    Hello,
    I have installed the SAP ECC 6.0 (SR1) under AIX 5.3 / Oracle 10g with HACMP Clustering environment. Manual Failover is working fine. ASCS and Database instances are loaded in share drive with Virtual IP and Virtual name. Central Instance and Dialog Instance are loaded locally in Node A and Node B. I want to get HACMP Clustering script(automatic failover script) for Automation. Please help me if you have.
    Thanks
    Gautam Poddar

    Here are HA stop & start scripts that you should be able adapt for your particular circumstances. Based on earlier versions of SAP / Oracle but assume should be a reasonable guide
    Script to start SAP is start_sap_prd
    #!/bin/ksh
    Script:         /usr/local/bin/cluster/start_sap_prd
    Comments:       HACMP Application START script for PRD
    Show me obvious information in hacmp.out
    banner "Starting"
    banner "PRD SAP"
    Set the oracle and sap owner.
    ORASID="PRD"
    SAPADM="prdadm"
    ORAUSR="oraprd"
    VIRTUALHOST="vhost"
    DEVHOST="vhostdev"
    Get the volume groups for this resource group
    RG=$( /usr/es/sbin/cluster/utilities/cllsgrp | grep -i $ )
    VG_LIST=$( /usr/es/sbin/cluster/utilities/cllsres -g $ | \
            grep "VOLUME_GROUP=" | \
            awk -F\" '{ print $2 }' )
    Check the transport directory is mounted.
    if mount | grep -w "/usr/sap/trans"
      then
            print "Transport directory is already mounted."
      else
            cd /tmp
            print "Attempting a background mount of the transport directory."
            nohup mount -o intr,bg,soft :/usr/sap/trans1 /usr/sap/trans &
    fi
    #Start SAP and Oracle
    #Start listener
    su - $ -c /rprd/oracle/PRD/920_64/bin/lsnrctl start
    rc=$?
    if [ $? != 0 ]
      then
            echo "ERROR: Listener failed to start\n"
    fi
    #Start Database
    su - $ -c "/rprd/oracle/PRD/bin/start_database_PRD.sh"
    sleep 20
    Standard sapstart script
    su - $ -c startsap $
    Script:       /usr/local/bin/cluster/stop_sap_prd
    Dated:        01/11/06
    Application:  Oracle/SAP
    Comments:     HACMP Application STOP script for SAP / Oracle PRD
    Show me obvious information in hacmp.out
    Set the oracle and sap owner.
    rc=$?
    if [ $? != 0 ]
    then
            echo "ERROR: Failed to start SAP\n"
    fi
    exit 0
    Script to stop SAP is stop_sap_prd
    #!/bin/ksh
    set -x
    banner "stopping"
    banner "PRD SAP"
    ORASID="PRD"
    SAPADM="prdadm"
    ORAUSR="oraprd"
    VIRTUALHOST="vhost"
    #Stop SAP/Oracle
    su - $ -c stopsap $
    rc=$?
    if [ $? != 0 ]
    then
            echo "ERROR: Failed to stop SAP and Oracle\n"
            break
    fi
    Stop SAP collector and Oracle listener.
    su - $ -c /usr/sap/PRD/SYS/exe/run/saposcol -k
    rc=$?
    if [ $? != 0 ]
    then
            echo "ERROR: Failed to stop SAPOSCOL \n"
    fi
    su - $ -c /rprd/oracle/PRD/920_64/bin/lsnrctl stop
    rc=$?
    if [ $? != 0 ]
    then
            echo "ERROR: Listener failed to stop\n"
    fi
    if mount | grep -w "/usr/sap/trans"
      then
            print "Transport directory is mounted."
            /usr/es/sbin/cluster/events/utils/cl_nfskill -k -u /usr/sap/trans
            sleep 1
            /usr/es/sbin/cluster/events/utils/cl_nfskill -k -u /usr/sap/trans
            sleep 1
            umount -f /usr/sap/trans &
      else
            print "Transport directory is not mounted."
    fi
    exit 0

  • Manual or Automatic failover?

    For SQL Server (2005/2008/R2) cluster, after failover happened from one node to another, how do I tell whether it was an automatic failover or somebody failed it over manually. This would help further troubleshoot what caused the failover. Please
    consider both Windows Server 2003 and Windows Server 2008 scenario. Thanks.

    Hi yarkandstar,
    Based on your description, you can check the SQL Server Error logs to find if it is an automatic failover or a manual failover in  SQL Server cluster. In the Error logs, if SQL Server restart multiple times in the same node and then come online in the
    other node, it should ideally be an automatic failover. If SQL Server is running on a different node after the first restart, it is a manual failover.
    Also, as Balmukund’s post, you can check the cluster log  to know whether SQL Server has an automatic failover or a manual failover.
    For more details about checking cluster log in Windows server 2003 cluster, please review this blog:
    How to find whether SQL Server had an Automatic Failover or a Manually initiated Failover in cluster.
    For more details about checking cluster log in Windows server 2008 cluster, please review this similar thread:
    Need to know if it was a manual or an automatic failover - WIndows server 2008 R2.
    Thanks,
    Lydia Zhang

  • Availability group Automatic failover

    Hi
    setup a simple 2 node AG, sync. (SQL 2014 enterprise on windows 2012R2 standard)
    if I set it as manual failover everything works as expected. however when I switch to automatic failover and stop SQL service on the primary node the AG resource in cluster does offline and doesn't failover to secondary node.
    both nodes are available to the cluster resourse.
    would appreciate your feedback as to what might be the reason
    Regards
    Shaunt

    Hi,
    I would verify if Database Availability Group means AlwaysOn Availability Group.
    How did you set the FailureConditionLevel?
    Whether the diagnostic data and health information returned by sp_server_diagnostics warrants an automatic failover depends on the failure-condition level of the availability group. The failure-condition level specifies what failure conditions
    trigger an automatic failover. There are five failure-condition levels, which range from the least restrictive (level one) to the most restrictive (level five). For details about failure-conditions level, see:
    http://msdn.microsoft.com/en-us/library/hh710061.aspx#FClevel
    There are two useful articles may be helpful:
    SQL 2012 AlwaysOn Availability groups Automatic Failover doesn’t occur or does it – A look at the logs
    http://blogs.msdn.com/b/sql_pfe_blog/archive/2013/04/08/sql-2012-alwayson-availability-groups-automatic-failover-doesn-t-occur-or-does-it-a-look-at-the-logs.aspx
    SQL Server 2012 AlwaysOn – Part 7 – Details behind an AlwaysOn Availability Group
    http://blogs.msdn.com/b/saponsqlserver/archive/2012/04/24/sql-server-2012-alwayson-part-7-details-behind-an-alwayson-availability-group.aspx
    Thanks.
    Tracy Cai
    TechNet Community Support
    Hi,
    Thanks for the reply.
    It's an AlwaysOn Availability Group.
    In my test lab, I have changed the quorum configuration to a file share witness and that has allowed an automatic failover when I turn the primary replica server off (rather than power it off).
    I'll take a look at the links you provided.
    Regards,
    Bob

  • Oracle 9i Dataguard automatic failover

    Hi Gurus,
    I wanted to setup automatic failover from primary to physical standby database in oracle 9i . Could you please advice me what are necessary things required for this setup. Right now we are manually doing the activity.
    thanks in advance
    regards,
    Shaan

    Hi,
    there is thread with the same question and I put there one link.
    Re: DGMGRL switchover automatically without manual intervention
    Regards,
    Tom
    http://oracledba.cz

  • DataGuard automatic failover

    Say an automatic failover has happened.
    The former primary DB is down.
    The former standby DB is now the primary DB and is up and running.
    I assume the clients have to reconnect to the second DB.
    Now, how can we make the automatic failover for the clients?
    (At least that you do not have to manually change the clients' tnsnames.ora to the new DB.)

    Take a look into the NET8 manual. The simple way is to define multiple addresses in the address list. That way you get a connect time failover: if the first instance isn't reachable the scond one will be used and so on.
    DB =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.1.1)(PORT = 1521))
    (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.1.2)(PORT = 1521))
    (CONNECT_DATA =
    (SERVICE_NAME = ORCL)
    )

  • Weblogic7/examples/clustering/ejb Automatic failover for idempotent methods ?

    This one should be easy since it is from the examples folder of bea 7 about
              clustering.
              Ref : \bea7\weblogic007\samples\server\src\examples\cluster\ejb
              I am referring to the cluster example provided with the weblogic server 7.0
              on windows 2000.
              I deployed Admin server and 2 managed server as described in document.
              Everything works fine as shown by the example. I get load balancing and
              failover both. Too Good.
              Client.java is using the while loop to manage the failover. So on exception
              it will go thru the loop again.
              I understand from the documentation that the stateless session EJB will
              provide the automatic failover for Idempotent stateless bean
              Case Failover Idempotent : ( Automatic )
              If methods are written in such a way that repeated calls to the same method
              do not cause duplicate updates, the method is said to be "idempotent." For
              idempotent methods, WebLogic Server provides the
              stateless-bean-methods-are-idempotent deployment property. If you set this
              property to "true" in weblogic-ejb-jar.xml, WebLogic Server assumes that the
              method is idempotent and will provide failover services for the EJB method,
              even if a failure occurs during a method call.
              Now I made 2 changes to the code.
              1 . I added as follows to the weblogic-ejb-jar.xml of teller stateless EJB
              <stateless-clustering>
              <stateless-bean-is-clusterable>true</stateless-bean-is-clusterable>
              <stateless-bean-load-algorithm>random</stateless-bean-load-algorithm>
              <stateless-bean-methods-are-idempotent>true</stateless-bean-methods-are-idem
              potent>
              </stateless-clustering>
              So I should get the automatic failover .............
              2. Also I added the break statement in the catch on line around 230 in
              Client .java
              catch (RemoteException re) {
              System.out.println(" Error: " + re);
              // Replace teller, in case that's the problem
              teller = null;
              invoke = false;
              break;
              So that the client program does not loop again and again.
              Now I compile and restart all my three servers and redeploy application (
              just to be sure )
              I start my client and I get a automatic load balancing between the server
              which makes me happy.
              But Failover ....?
              I kill one of the managed application server in cluster at any particular
              test fail point.
              I expect the exception to be taken care automatically by error/failover
              handler in the home/remote stub
              But the client program fails and terminates.
              1. What is wrong with the code ?
              2. Does the automatic failover with the indempotent methods also has to be
              taken care by coding the similar while loop for stateless ejb ?
              Your help will be appreciated ASAP.
              Let me know if you need any thing more from my system. But I am sure this
              will be very easy as it is from the sample code.........
              Thanks
              

    Sorry I meant to send this to the ejb newsgroup.
              dan
              dan benanav wrote:
              > Do any vendors provide for clustering with automatic failover of entity
              > beans? I know that WLS does not. How about Gemstone? If not is there
              > a reason why it is not possible?
              >
              > It seems to me that EJB servers should be capable of automatic failover
              > of entity beans.
              >
              > dan
              

  • Replicating simple Java objects for automatic failover

    Is there a way to replicate a simple java object that is bound from JNDI
              across all servers so that if the primary server fails, it will
              automatically failover?
              We have a java client that uses JNDI to access EJBs on WLS5.1 SP8. In order
              to determine client information, the client currently binds a simple java
              class in the JNDI tree. The Entity and Session beans use the caller
              principal to locate the object in order to access client-information for
              such things as record locking, logging, etc..
              We have to move this architecture to a cluster environment and we are
              wondering how we can replicate this object across cluster servers so that
              failover is handled automatically, and that it is still accessible through
              JNDI.
              An RMI replicated stub is not enough, since it only works as long as the
              server hosting the RMI object is alive.
              I'd like to add that the object is created and bound at client start-up and
              destroyed at client exit.
              Thank you for any advice or information,
              Dania Kodeih.
              

    A: Replicating simple Java objects for automatic failover

    That's what I figured. I guess the only solution in this case is to persist
              the object during client sessions. I was hoping for something simpler, but I
              guess I'll have to create an Entity Bean and everything else that comes with
              it.
              Thanks,
              Dania.
              Cameron Purdy wrote in message <[email protected]>...
              >Unfortunately, when the originating server goes down, the replicated object
              >disappears.
              >
              >Peace,
              >
              >--
              >Cameron Purdy
              >Tangosol, Inc.
              >http://www.tangosol.com
              >+1.617.623.5782
              >WebLogic Consulting Available
              >
              >
              >"Don Ferguson" <[email protected]> wrote in message
              >news:[email protected]..
              >> If I am not mistaken, any serializable object will automatically be
              >replicated
              >> across the tree.
              >>
              >> Dania Kodeih wrote:
              >>
              >> > Is there a way to replicate a simple java object that is bound from
              JNDI
              >> > across all servers so that if the primary server fails, it will
              >> > automatically failover?
              >> >
              >> > We have a java client that uses JNDI to access EJBs on WLS5.1 SP8. In
              >order
              >> > to determine client information, the client currently binds a simple
              >java
              >> > class in the JNDI tree. The Entity and Session beans use the caller
              >> > principal to locate the object in order to access client-information
        �... [Show more]

    Read other 4 answers

  • Configuring Automatic Failover for EPM Planning Cluster

    We are trying to test automatic failover using a Planning(11.1.2.2)/weblogic cluster containing 2 physical servers and a Weblogic proxy plug-in for OHS.
    I understand that to enable this we must configure in-memory replication of HTTP session states and to do this, (according to various sources including ID 779350.1) the weblogic.xml file must include a descriptor set up as follows:
    <session-descriptor>
       <session-param>
        <param-name>PersistentStoreType</param-name>
        <param-value>replicated</param-value>
    </session-param>
    </session-descriptio>
    Where should weblogic.xml be created or amended (if it already exists) for a Planning cluster in a standard scaled out EPM deployment in order to effect failover between the two servers.
    Thanks

    yes, it can be load balanced in hyperion registry i believe, seen it once only drawback is ,if a JVM goes down while processing a request it needs to be manually started, however the url will switch automatically   

  • Problem setting up JMS Automatic Failover in WebLogic 9.1

    I received the following error when trying to configure server migration using Sybase DB to store leasing tables information:
              <java.sql.SQLException:JZ0S3:> The inherited method executdUpdate(String) cannot be used in this subclass.
              at com.sybase.jdbc2.jdbc.ErrorMessage.raiseError(ErrorMessage.556)
              at com.sybase.jdbc2.jdbc.SybPreparedStatement.executedUpdate(SybPreparedStatement.java:122)
              at weblogic.jdbc.wrapper.Statement.executedUpdate(Statement.java:433)
              at weblogic.cluster.singleton.DatabaseLeasingBasis.renewAllLeases(DatabaseLeasingBasis.java:118)
              at weblogic.cluster.singleton.DatabaseLeasingBasis.sendHeartbeat(DatabaseLeasingBasis.java:94)
              I'm using Sybase driver type 4, version 5.X. I also experimented with Sybase driver type 4, version 6.X but got the same error. I tried to use WebLogic Sybase Driver and got different error (SQLException: SQLState(HY000)).
              I have used Sybase driver version 5.X successfully with our application in WL9.1. It seems the calls to renew all leases in WL9.1 need to change to from PreparedStatement to Statement since Sybase PreparedStatement does not support executeUpdate(String).
              I need to resolve this problem ASAP. We are upgrading to WL9.1 from 8.1 so that we could take advantage of the automatic failover but so far, it is not working. Please help.
              Thanks.

    I'd contact [email protected] I believe this is a known bug when using sybase.
              -- Rob
              WLS Blog http://dev2dev.bea.com/blog/rwoollen/

  • Automatic failover not currently supported by WebLogic JMS?

              Hi,
              does this apply to Weblogic 8.1 as well? When will automatic failover be implemented?
              Thanks,
              A.
              

    Hi,
              You can setup a "node manager" process to automatically
              restart a failing server, but there is no automatic
              fail-over to a new machine.
              To achieve automatic failover use
              third party HA framework software and disk replication
              software such as is supplied by Veritas. I'm not aware
              of any plans to add automated fail-over to the next release.
              Tom
              Iggy wrote:
              > Hi,
              >
              > does this apply to Weblogic 8.1 as well? When will automatic failover be implemented?
              >
              > Thanks,
              >
              > A.
              >
              >
              

Maybe you are looking for