EZCONNECT Connections Error with SP2-0642: Sql*Plus Internal Error State 2130
Last updated on DECEMBER 07, 2011
Applies to:Oracle Net Services - Version: 10.2.0.1
Information in this document applies to any platform.
Connections using EZCONNECT naming resolution from 10.2.0.1 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,
from dba_services where service_id = orcl
NAME METHOD TYPE RETRIES GOAL CLB_GOAL AQNOT
---------- ------ ------ ------- ---- -------- -----
server_taf BASIC SELECT 180 NONE LONG YES
SQL*plus using local naming resolution (TNSNAMES.ORA) works fine for the modified service.
SQL*Plus: Release 22.214.171.124.0 - 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.
nigtrm: Count in the NL global area is now 4
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms