Skip to Main Content

Oracle Database Discussions

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

What caused our listener handshake to lose AUTH_SC information?

Tom HalladayAug 31 2018 — edited Aug 31 2018

Last week one of our client's Oracle environments was altered, and a cascade of unintended issues ensued. One of which is that the Listener header signature changed during the client handshake. It is now missing AUTH_SC information that the ODP.NET driver apparently requires. What we need to know is how do we change this signature back to provide the full package of AUTH_SC information.

When the environment was altered, the ARCHIVELOG caused the DB_RECOVERY_FILE_DEST to run out of space. That has since been remedied, but that remedy did not resolve this issue, which we believe is or was related, based on 2+ articles that share the same symptoms and causes as ours ( )

Redacted Handshake Diff.png

Environment A is the server that was altered

Environment B is a test server with a copy of Environment A that has not been altered, and still works

Specifically the headers we need back are

AUTH_SC_SERVER_HOST,

AUTH_SC_DBUNIQUE_NAME

AUTH_SC_INSTANCE_NAME

AUTH_SC_SERVICE_NAME

But it would be nice to revert back to the original set including

AUTH_SC_INSTANCE_ID

AUTH_SC_INSTANCE_START_TIME

AUTH_SC_DB_DOMAIN

AUTH_ONS_RLB_SUBSCR_PATTERN

AUTH_ONS_HA_SUBSCR_PATTERN

AUTH_SC_SVC_FLAGS

At this point we're not focused on the fact that the handling of this scenario is a bug in ODP.NET, we simply want to revert the server changes that lead to the bug in the first place.

The Oracle Environment information:

Oracle Client 12c 12.1.0.2.0

Oracle Database 12c 12.1.0.2.0

Interim patches (2) :

Patch 26027162 : applied on Thu Oct 26 09:13:26 PDT 2017

Unique Patch ID: 21319014

Patch 26609783 : applied on Thu Oct 26 09:12:32 PDT 2017

Unique Patch ID: 21481899

Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Sep 28 2018
Added on Aug 31 2018
0 comments
252 views