Application Intent Parameter for Hard Coded Connection Strings in RPD

EAddams

Organization Name (Required - If you are an Oracle Partner, please provide the organization you are logging the idea on behalf of):

DAS, OCIO, State Of Nebraska

Description (Required):

We've been instructed by Oracle Support and Oracle Dev to submit this request to attempt to resolve an immediate issue. Updating Oracle SQL Server Wire Protocol driver from version 7.1 to version 8.0 for OAC

Use Case and Business Need (Required):

Due to some specifics of our setup, we are required to have hard coded connections strings in our RPD that utilize version 7.1 of the driver specified above. For some reason the parameter for applicationintent=1 causes the connections to be refused and never reach our internal network. Without the parameter for applicationintent=1 all connections are directed to our primary node instead of the secondary node, causing global resource usage issues that threaten to bring down dozens of applications on the enterprise. We currently have outages that stem from this issue reportedly affecting thousands of users state wide.

Enhancement Request / Service Request:

original request we submitted reporting this issue: SR 3-32302412821 : RPD Connection String Pointing to Primary Database Node - caused internal fail over

Alan Lee - Oracle-Oracle

Update of SQL Server driver from 7.1 to 8.0 is planned.