CLM database connection string question

Greg Leff (11●2●4) | asked Dec 18 '19, 12:04 p.m.
edited Dec 23 '19, 11:40 p.m. by Muralidhar Rajagopal (101●1●4)

We use a set of active/passive mirrored Oracle RAC environments to support our CLM suite of tools. For each application, we currently have defined a JDBC connection string like this:

thin:APP/{password}@//database1.company.com:1521/database1_srv.company.com

saved to a file, but not defined until needed:

thin:APP/{password}@//database2.company.com:1521/database2_srv.company.com

However, we would like to use a connection string like this - which would allow the application to automatically connect to whatever the active database is.

thin:APP/{password}@//database.world=
(DESCRIPTION_LIST=
    (FAILOVER=on)
    (LOAD_BALANCE=off)
    (DESCRIPTION=
      (CONNECT_TIMEOUT=5)
      (TRANSPORT_CONNECT_TIMEOUT=3)
      (ADDRESS_LIST=
        (LOAD_BALANCE=on)
        (ADDRESS=
          (PROTOCOL=TCP)
          (HOST=database1.company.com)
          (PORT=1521)
        )
      )
      (CONNECT_DATA=
        (SERVICE_NAME=database_srv.company.com)
      )
    )
    (DESCRIPTION=
      (CONNECT_TIMEOUT=5)
      (TRANSPORT_CONNECT_TIMEOUT=3)
      (ADDRESS_LIST=
        (LOAD_BALANCE=on)
        (ADDRESS=
          (PROTOCOL=TCP)
          (HOST=database2.company.com)
          (PORT=1521)
        )
      )
      (CONNECT_DATA=
        (SERVICE_NAME=database_srv.company.com)
      )
    )
)

Is it possible for the CLM suite to failover without needing a connection string change (with or without a stop/start)? Currently we have to stop the application, change the database connection string, and start the application.

Be the first one to answer this question!

It's all about the answers!

Related questions

CLM database connection string question

Be the first one to answer this question!