Install, Upgrade, Clone, Patch - EBS (MOSC)

MOSC Banner

Io exception: Connection refused during patch because wrong service_name is used

edited Oct 29, 2014 11:38AM in Install, Upgrade, Clone, Patch - EBS (MOSC) 11 commentsAnswered

Patch 4298372 fails, and the adworker log shows it's trying to connect with the wrong connection string.

Io exception: Connection refused(DESCRIPTION=(TMP=)(VSNNUM=186647296)(ERR=12514)(ERROR_STACK=(ERROR=(CODE=12514)(EMFI=4))))

Connecting to APPS@(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=oradb2.scint.businesswire.com)(PORT=7377))(CONNECT_DATA=(SERVICE_NAME=BILLISC2))) -- UTF8

Unable to connect to (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=oradb2.scint.businesswire.com)(PORT=7377))(CONNECT_DATA=(SERVICE_NAME=BILLISC2)))

The SERVICE_NAME should not be BILLISC2. BILLISC2 is name of an instance in the RAC cluster, not a service.  How do I correct the connection information?


Tagged:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

EBS LCM Tags

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center