SP2-0642: SQL*Plus internal error state 2130, context 0:0:0

..experience, Working case

SP2-0642: SQL*Plus internal error state 2130, context 0:0:0

2016-10-09

没有评论

今天一个10g的客户端,连接12c的数据库,报错:

sqlplus user/passwd@10.11.22.33:1525/mysrv

SQL*Plus: Release 11.1.0.6.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

1

2

3

4

5

6

7

8

sqlplus user/passwd@10.11.22.33:1525/mysrv

SQL*Plus: Release 11.1.0.6.0 - Production on Thu Jun 11 10:05:29 2009

Copyright (c) 1982, 2007, Oracle.  All rights reserved.

Unsafe to proceed

而这个客户端连接其他12c的数据库是没有问题的。

这是因为建立的service已经是非标准的service,包含了failover type等参数。见下面的Test Case:

Test Case:
----------
1.Create a service

srvctl add service -d <database-name> -s <service-name> -r "instance-name,instance-name" -P BASIC

2. Start the service

srvctl start service -d rac -s <service-name>
Below was service called test_srv

3.Make a connection using ezconnnect >>

sqlplus scott/tiger@jcrac1-vip:1521/test_srv

This will work.

4.Now modify the service

SQL> select name,service_id from dba_services where name = ‘test_srv‘;

NAME SERVICE_ID
---------------------------------------------------------------- ----------
server_taf 12

SQL> execute dbms_service.modify_service (service_name => ‘test_srv‘ -
, aq_ha_notifications => true -
, failover_method => dbms_service.failover_method_basic -
, failover_type => dbms_service.failover_type_select -
, failover_retries => 180 -
, failover_delay => 5 -
, clb_goal => dbms_service.clb_goal_long);

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

NAME METHOD TYPE RETRIES GOAL CLB_GOAL AQNOT
--------------- ----------- ---------- -------- ---------- -------- -----
test_srv BASIC SELECT 180 NONE LONG YES

5.Connection now fails

sqlplus scott/tiger@jcrac1-vip:1521/test_srv

SQL*Plus: Release 11.1.0.6.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
Enter user-name:

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

Test Case:

----------

1.Create a service

srvctl add service -d <database-name> -s <service-name> -r "instance-name,instance-name" -P BASIC

2. Start the service

srvctl start service -d rac -s <service-name>

Below was service called test_srv

3.Make a connection using ezconnnect >>

sqlplus scott/tiger@jcrac1-vip:1521/test_srv

This will work.

4.Now modify the service

SQL> select name,service_id from dba_services where name = ‘test_srv‘;

NAME                                                             SERVICE_ID

---------------------------------------------------------------- ----------

server_taf                                                               12

SQL> execute dbms_service.modify_service (service_name => ‘test_srv‘ -

, aq_ha_notifications => true -

, failover_method => dbms_service.failover_method_basic -

, failover_type => dbms_service.failover_type_select -

, failover_retries => 180 -

, failover_delay => 5 -

, clb_goal => dbms_service.clb_goal_long);

SQL>select name, failover_method, failover_type, failover_retries,goal,

clb_goal,aq_ha_notifications from dba_services where service_id = 12

NAME            METHOD      TYPE        RETRIES GOAL       CLB_GOAL AQNOT

--------------- ----------- ---------- -------- ---------- -------- -----

test_srv        BASIC       SELECT          180 NONE       LONG     YES

5.Connection now fails

sqlplus scott/tiger@jcrac1-vip:1521/test_srv

SQL*Plus: Release 11.1.0.6.0 - Production on Thu Jun 11 10:05:29 2009

Copyright (c) 1982, 2007, Oracle.  All rights reserved.

Unsafe to proceed

Enter user-name:

该问题是Bug 8599395 : EZCONNECT ERRORS WITH SP2-0642: SQL*PLUS INTERNAL ERROR STATE 2130, CONTEXT 0:0:

解决方法:

建议升级客户端到11.2以上,或者按照bug文档中的workaround也可以:

Workaround:
-----------
LOCAL naming resolution works -- 使用tnsnames.ora文件连接
Use standard service works -- 使用标准的service,去掉failover type的参数设置
Do not put port number in the command -- 使用1521默认端口,ezconnect的时候,不写端口号

1

2

3

4

5

Workaround:

-----------

LOCAL naming resolution works -- 使用tnsnames.ora文件连接

Use standard service works -- 使用标准的service,去掉failover type的参数设置

Do not put port number in the command -- 使用1521默认端口,ezconnect的时候,不写端口号

12cbug

Previous Post
Next Post

相关文章

发表评论 取消回复

电子邮件地址不会被公开。 必填项已用*标注

评论

姓名 *

电子邮件 *

站点

此站点使用Akismet来减少垃圾评论。了解我们如何处理您的评论数据

原文地址:https://oracleblog.org/working-case/sp2-0642-sqlplus-internal-error-state-2130-context-000/

原文地址:https://www.cnblogs.com/jpfss/p/11167838.html

时间: 2024-10-12 14:49:23

SP2-0642: SQL*Plus internal error state 2130, context 0:0:0的相关文章

sqlplus连接数据库报错SP2-0642: SQL*Plus internal error state 2130, context 0:0:0解决

sqlplus连接数据库报错SP2-0642: SQL*Plus internal error state 2130, context 0:0:0解决 sqlplus 连接数据库报错SP2-0642: SQL*Plus internal error state 2130, context 0:0:0 问题描述: 使用sqlplus客户端登录数据库,报错SP2-0642,而使用其它方式plsql或者tnsnames等方式连接数据库均没有问题 [plain] [[email protected] ~

SQL调用存储过程错误Internal error when parsing callable statement metadata (missing parameter type)

[6 Apr 2005 15:29] Chadwick Baatz Description: When calling a stored procedure with datatype Decimal(m,d) (i.e. Decimal(18,0)) the Connector/J library throws the exception below. After looking into the code it appears that the getCallStmtParameterTyp

Eclipse启动时出现错误 An internal error occurred during: “Updating indexes”

在Eclipse的workspace下有个.metadata文件夹,Eclipse出现异常的log文件就在这个目录下. 最近出现了这样的错误: 查看日志文件发现:     !ENTRY org.eclipse.core.jobs 4 2 2011-08-03 09:33:32.843     !MESSAGE An internal error occurred during: "Updating indexes".     !STACK 0     java.lang.OutOfMe

Eclipse启动时出现错误 An internal error occurred during: &quot;Updating indexes&quot;

在Eclipse的workspace下有个.metadata文件夹,Eclipse出现异常的log文件就在这个目录下. 最近出现了这样的错误: 查看日志文件发现:     !ENTRY org.eclipse.core.jobs 4 2 2011-08-03 09:33:32.843     !MESSAGE An internal error occurred during: "Updating indexes".     !STACK 0     Java.lang.OutOfMe

An internal error occurred during: &quot;Setup check&quot;. java.lang.NullPointerException

在Eclipse的workspace下有个.metadata文件夹,Eclipse出现异常的log文件就在这个目录下. 最近出现了这样的错误: 查看日志文件发现:     !ENTRY org.eclipse.core.jobs 4 2 2011-08-03 09:33:32.843!MESSAGE An internal error occurred during: "Updating indexes".     !STACK 0Java.lang.OutOfMemoryError:

Eclipse启动报错:An internal error occurred during: &quot;Updating indexes&quot;.org/eclipse/core/runtime/internal/adaptor/BasicLocation解决方法

Eclipse一直用的好好的,突然这两天每次启动都会出现如下的错误:An internal error occurred during: "Updating indexes".org/eclipse/core/runtime/internal/adaptor/BasicLocation,刚开始没有在意,以为是机器的内存不够导致,但后来发现不是怎么回事,刚开机,打开Eclipse也报这个错误.找到Eclipse的日志文件,workspace/.metadata/.log,查询"

SQL Server 2005 sp_send_dbmail出现Internal error at FormatRowset (Reason: Not enough storage is available to complete this operation)

案例环境: 操作系统: Windows 2003 SE 32bit(SP2) 数据库版本:Microsoft SQL Server 2005 - 9.00.5069.00 (Intel X86) Aug 22 2012 16:01:52 Copyright (c) 1988-2005 Microsoft Corporation Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2) 案例分析: 如下所示,使用下面SQL语句发

SQL Tuning Advisor报错ORA-00600: internal error code, arguments: [kesqsMakeBindValue:obj]

执行SELECT dbms_sqltune.report_tuning_task(:tuning_task) FROM dual;  报错信息如下: ORA-00600: internal error code, arguments: [kesqsMakeBindValue:obj], [], [], [], [], [], [], [] ORA-06512: at "SYS.PRVT_ADVISOR", line 1624 ORA-06512: at "SYS.DBMS_A

Start Failed, Internal error: recovering IDE to the working state after the critical startup error

Start Failed, Internal error: recovering IDE to the working state after the critical startup error FOLLOW Serge Baranov Updated Yesterday at 06:05 Symptoms IDE shows the Start Failed dialog with the exception stacktrace and the following text: Intern