Add NA application support for Oracle Dataguard Exacc Platform

Idea ID 1684640

Add NA application support for Oracle Dataguard Exacc Platform

Hi Team,

HP NA 10.x is not able to connect to more than one Oracle Dataguard node.

"JDBCDrivers.properties" file couldn't interpret a connection string with the following format :

oracle.url=jdbc:oracle:thin:@(DESCRIPTION=(LOAD_BALANCE=ON)(ADDRESS=(PROTOCOL=TCP)(HOST= host1.oracledatguard.com) (PORT=1523))(ADDRESS=(PROTOCOL=TCP)(HOST= host2.oracledatguard.com)(PORT=1523))(CONNECT_DATA=(SERVICE_NAME=NAPRD_WEB)))

where : host1.oracledatguard.com is the primary Oracle Dataguard node (Primary site)

host2.oracledatguard.com is the standby Oracle Dataguard node (Secondary site)

It only accepts something like that :

oracle.url=jdbc:oracle:thin:@//host1.oracledatguard.com:1523/NAPRD_WEB

Also, the tc_tools.sh utility is obsolete as it asks for node name (which is one and only one node) and database name (instead of asking for service name). Access to database should be done through service names and not through a direct Database instance connection anymore.

So, is it possible to add NA support for more than one Oracle Dataguard node so when losing a primary site, NA application continues to work with the new Dataguard node (previously the standby node) instead of configuring it manually at each site loss in the "JDBCDrivers.properties" ?

Thank you and best regards,

Aymen.S

 

3 Comments
Micro Focus Expert
Micro Focus Expert
Status changed to: Waiting for Votes

The idea has received an initial review to ensure adherence to our idea submission and community guidelines. More information may be needed at a later stage. We expect the community to help prioritize the idea with comments and community support (votes/kudos)

 

 

 

Micro Focus Expert
Micro Focus Expert

For the same was submitted an ER: QCCR1B172763 "NA - Request NA to be able to handle the long connection string to Oracle DB DataGuard"

Frequent Contributor.
Frequent Contributor.

jdbc:oracle:thin:@(DESCRIPTION=(CONNECT_TIMEOUT=10)(RETRY_COUNT=3)(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=<Primary_host.com>)(PORT=1521))(ADDRESS=(PROTOCOL=TCP)(HOST=<secondary_host.com)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=<service-Name.com>)(SERVER=DEDICATED))) works when running NA (10.30.05, 10.30.04, 2019.05).

We also tested switching the database server without doing anything on the NA Servers (10.40.04) :  it also worked. We felt a short latency on the webUI - but we even did not have to login again. In jboss_wrapper.log we found some messages about the db server being switched. So NA recognized it but handled it without problems.

Installing NA software did not work in all cases. Some worked with the long connection string already in JDBCDrivers.properties. For some installation procedures we temporarily had to shorten the string to one server /no options  in JDBCDrivers.properties within the installation procedure.  You should take the active db server then of course ;-).

In my opinion it is absolutely essential to have full support of long connection strings  if MF / NA  wants to keep pace with developement of oracle db architectures. 

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.