3 Replies Latest reply: Sep 17, 2008 8:31 AM by 516019 RSS

    Content Service goes down when one DB instance in RAC goes down

    539731
      Hi all,

      When one of the content DB in 2 node RAC goes down our content service application also goes down, can anyone help me in configuring our OCS application to work in RAC mode, so that even when if one instance goes DOWN the applications should work fine with the other available DB instance

      -Vinil
        • 1. Re: Content Service goes down when one DB instance in RAC goes down
          516019
          Hi,

          We are having the same problem where Content Services stops working if a node in the RAC database is shut down. Please could you inform us whether you found a solution for this problem and what configuration changes needed to be made?

          Thanks
          • 2. Re: Content Service goes down when one DB instance in RAC goes down
            Hareesh-Oracle
            For the database connections to be failed over to the next available instance, you would have to configure TAF(Transparent application failover).

            For a very basic example - here is how you would change your tns connect descriptor to

            sales.us.acme.com=
            (description= (load_balance=on) (failover=on) (address= (protocol=tcp) (host=sales1-server)
            (port=1521))
            (address= (protocol=tcp) (host=sales2-server) (port=1521)) (connect_data=
            (service_name=sales.us.acme.com)
            (failover_mode= (type=select) (method=basic))))

            This connect descriptor needs to be changed in OiD where content services picks up the database connection url from.

            Hope that helps
            • 3. Re: Content Service goes down when one DB instance in RAC goes down
              516019
              Hi Hareesh,

              Thanks for the reply. We have been using a database connection string like this but still had problems. We have since discovered that the problem seems to be with the S2S servlet that allows trusted authentication. If a RAC node is shutdown then the S2S servlet will log exceptions and return errors when trying to create a session for a user until the servlet has used up all of it's invalid cached connections to the database. After this point it appears to start authenticating users correctly again. Our system cannot have this kind of period of authentication failures, so hopefully there is a resolution somewhere for this issue!

              Thanks