ASAP Installation with a Second Node In the Cluster (Doc ID 1351799.1)

Last updated on JANUARY 04, 2015

Applies to:

Oracle Communications ASAP - Version 7.0.1 and later
Information in this document applies to any platform.

Goal

What should be changed in the ASAP installation response file when it is performed with the installation of a second node in a cluster, and the DB is staying the same (we have 3 machines, node1, node2, and DB)

The user creation during the first installation the DBA created the users, and everything went fine, creating all the tables/triggers/procedures/views and populating with the default data.

But what is needed is a way to avoid the installation and creating the full DB again, by inserting some rows in a few cases where there were no constraints.






Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms