Hi Joe,
I've been using Oracle RAC with Applications Manager for a number of years (currently 12c until support for 19c is released). The AM product is poorly designed to work with RAC, so it doesn't act like a normal "RAC enabled" product. Essentially you need to focus the application stack to one node when bringing the product up.
During the install, I reference the Scan Listener address for "Oracle Instance IP or Hostname" and the "Oracle Listener Port"=1533 (in my case)
In the sosite file I export TWO_TASK=
Service Name.In the awenv.ini I set the following:
DB_IP=
scan listener addressDB_PORT=
1533DB_SERVICE=
service nameIn ~/web/classes/Options.properties:
OracleRAC= (DESCRIPTION = (ENABLE=BROKEN)(ADDRESS = (PROTOCOL = TCP) (HOST =
host1) (PORT = 1541)) (ADDRESS = (PROTOCOL = TCP) (HOST =
host2) (PORT = 1541)) (ADDRESS = (PROTOCOL = TCP) (HOST =
host3) (PORT = 1541)) (LOAD_BALANCE = OFF) (FAILOVER = ON) (CONNECT_DATA = (SERVER = DEDICATED)(SERVICE_NAME =
service name) ) )
With these pieces in place, you will start AM in node1, if it fails it will move to node2 , etc.
If you do any AM DB variable queries, etc. it will hit the scan listener for any available node.
HTH,
Scott
Original Message:
Sent: 03-06-2020 06:40 PM
From: Joe DuQuette
Subject: Application Manager v9 with Oracle RAC
Has anyone used an oracle rac database with application manager v9. When we try to point our environment to the rac instance we are getting error when we try to start the Automation Engine.
These are the steps we took to change the database.
Change TNS entry to point to new database.
Run cdinst.sh to change java to database by changing the server and service name, giving it the correct password when prompted.
The upgrade/install steps run correctly.
When we run startso all we get an error.
We've used these steps to move the database on multiple single instance oracle databases in the past.
Thanks,
Joe