Unable To Deploy Patches Due To Incorrect Connection String #exadata #unix #ORMB2.5
(Doc ID 2421989.1)
Last updated on FEBRUARY 27, 2019
Applies to:Oracle Financial Services Revenue Management and Billing - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
"ouafDatabasePatch.sh" fails due to issues with connection to the EXADATA database.
During the deployments, receiving error: "Connection string is invalid format should be dbhost:dbport:dbsid".
Note that environments using standalone databases, where USE_SID_AS_SERVICE is in use, the patching ends successfully.
But when we are using EXADATA databases, where USE_SID_AS_SERVICE is forbidden by ORACLE, as it is a global variable, we are experiencing the issue.
This article advises workaround on how to deploy patches against environments using Exadata.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document