My Oracle Support Banner

EZCONNECT Connections Error with SP2-0642: Sql*Plus Internal Error State 2130 (Doc ID 855965.1)

Last updated on FEBRUARY 03, 2019

Applies to:

Oracle Net Services - Version: and later   [Release: 10.2 and later ]
Information in this document applies to any platform.
Connections using EZCONNECT naming resolution from onwards


Using ezconnect naming resolution fails with error SP2-0642: SQL*Plus internal error state 2130, when the service is not running with default values.

That is dbms_service.modify_service has been used to change a service, for example to configure Server Side Transparent Application Failover (TAF).

SQL>select name, failover_method, failover_type, 
failover_retries,goal, clb_goal,aq_ha_notifications  
from dba_services where service_id = orcl

----------  ------ ------ ------- ---- -------- -----
server_taf  BASIC  SELECT 180     NONE LONG     YES

SQL*plus using local naming resolution (TNSNAMES.ORA) works fine for the modified service.

sqlplus scott/tiger@rac1-vip:1521/orcl
SQL*Plus: Release - Production on Thu Jun 11 10:05:29 2009
Copyright (c) 1982, 2007, Oracle. All rights reserved.
SP2-0642: SQL*Plus internal error state 2130, context 0:0:0
Unsafe to proceed

Using standard default service values, allows the ezconnect connection to work.Oracle Net client traces do not show a SP2-0642 error, but instead shows a connection handshake and end with the following lines.

nttdisc: Closed socket 8
nttdisc: exit
nigtrm: Count in the NL global area is now 4


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

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.