GAX - JDBC DAP with Oracle Dataguard [SOLVED]

Voice & Telephony
1

Hi all,

does anybody have an Oracle DB with Dataguard up and running?

I’m currently setting up a new environment and the customer has an Oracle Database with a Physical Standby (Dataguard).

It’s actually working fine with a regular DAP and DB Server but with GAX a switchover is not working due to the JDBC Connection.

Even by using the custom application Option “jdbc_url” and adding both hosts and activating failover.

It looks like Genesys is not even trying the 2nd host and just returns an ORA-12514 which indicates that only the “old” Primary is tried and the Service is shut down due to the implemented trigger.

Update1:
I’ve checked the GAX logs and it obviously doesn’t use the jdbc_url Parameter at all:

jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=192.168.66.21)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=CORE))(FAILOVER_MODE=(TYPE=SELECT)(METHOD=BASIC)(RETRIES=10)(DELAY=5)))

But the jdbc_url is configured like that:

jdbc:oracle:thin:@(DESCRIPTION=(FAILOVER=on)(ADDRESS=(PROTOCOL=TCP)(HOST=192.168.66.22)(PORT=1521))(ADDRESS=(PROTOCOL=TCP)(HOST=192.168.66.22)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=CORE)))

The configured jdbc_url is working properly when I’m testing it with SQLDeveloper

Update2:
I’ve also tried using “jdbc-url” as there is a missmatch in the Documentation between GIM (jdbc-url) and GAX (jdbc_url).
Unfortunately no positive result.

Update3:
By studying the logs, I’ve found the following:

JDBC URL is not configured in DAP application

But it definitely is.

Hope somebody can help.

Best regards,
Zwerg

2

I’ve resolved the issue.

There is obviously a typo in the documentation:

[GAX]
jdbc_url=....

instead of:

[gax]
jdbc_url=....
3

Hmmm, we never ran into this problem yet.

JDBC URL is not configured in DAP application - usually the issue is improperly labeled section. Have you checked Annex?

4

Hi victor,

according to Genesys Docs it is:

Starting in GAX 8.5.25x, you can create a custom JDBC URL to connect to the GAX Database. This URL is specified in the Database Access Point (DAP), and is an alternative to using a connection based on the DAP object that enables access to the GAX Database.

And they are stating the following:

To configure a custom JDBC URL, use the jdbc_url option in the [GAX] section of the DAP object. If this option is not configured, GAX will use the DAP object values for establishing the connection.

As mentioned above, it’s not [GAX] but [gax]