R12.1 upgrade patch is failing on JDBC connections - RAC
Problem Summary---------------------------------------------------
R12.1 upgrade patch is failing on JDBC connections - RAC
Problem Description
---------------------------------------------------
This is and upgrade from 11.5.10.2 to R12.1.1
Exadata RAC database 2 node. Fully functioning as RAC
R12.1 ugprade script attempts jdbc connections that are in an incorrect format using SID instead of service name AND the sid is pointing to the database name rather than the SID name
Error Codes
---------------------------------------------------
ORA-12505
### Impact on Business ###
The E-Business suite R12.1.1 upgrade patch is failing when it uses jdbc connections. The jdbc connection is defaulting to a SID rather than to a service_name. The RAC database does NOT accept a SID name for the database name. In other words, the database name is l2dv, sid of node 1 is l2dv1 and sid of node 2 is l2dv2. sid is NOT and should NOT be l2dv. Here is the error. This is a severe disruption to the go-live schedule:
R12.1 upgrade patch is failing on JDBC connections - RAC
Problem Description
---------------------------------------------------
This is and upgrade from 11.5.10.2 to R12.1.1
Exadata RAC database 2 node. Fully functioning as RAC
R12.1 ugprade script attempts jdbc connections that are in an incorrect format using SID instead of service name AND the sid is pointing to the database name rather than the SID name
Error Codes
---------------------------------------------------
ORA-12505
### Impact on Business ###
The E-Business suite R12.1.1 upgrade patch is failing when it uses jdbc connections. The jdbc connection is defaulting to a SID rather than to a service_name. The RAC database does NOT accept a SID name for the database name. In other words, the database name is l2dv, sid of node 1 is l2dv1 and sid of node 2 is l2dv2. sid is NOT and should NOT be l2dv. Here is the error. This is a severe disruption to the go-live schedule:
Tagged:
0