High Availability Data Guard, Sharding and Global Data Services (MOSC)

MOSC Banner

Error 12170 received logging on to the standby

edited Oct 25, 2016 5:00AM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 2 commentsAnswered

After Switch over Primary to Standby we have faced below issues every 5 10 min in alert logs

Fatal NI connect error 12170.

VERSION INFORMATION:

TNS for 64-bit Windows: Version 11.2.0.3.0 - Production

Windows NT TCP/IP NT Protocol Adapter for 64-bit Windows: Version 11.2.0.3.0 - Production

Time: 28-SEP-2016 11:03:52

Tracing not turned on.

Tns error struct:

ns main err code: 12535

TNS-12535: TNS:operation timed out

ns secondary err code: 12560

nt main err code: 505

TNS-00505: Operation timed out

nt secondary err code: 60

nt OS err code: 0

Client address: <unknown>

Error 12170 received logging on to the standby

PING[ARC1]: Heartbeat failed to connect to standby 'gscc'. Error is 12170.

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

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