DBIF_DSQL2_CONNECTSTR_ERROR

Former Member — Fri, 12 Mar 2010 06:58:23 GMT

Exception CX_SY_NATIVE_SQL_ERROR

Short text

Connection ID unknown

What happened?

The connection identifier points to the data in the table DBCON

needed to establish a connection to the database system in the

context of the multi-connect. However, there is no entry

with the key "CONNECTION".

Error analysis

An exception occurred that is explained in detail below.

The exception, which is assigned to class 'CX_SY_NATIVE_SQL_ERROR', was not

caught in

procedure "CONNECT_REMOTEDB" "(FORM)", nor was it propagated by a RAISING

clause.

Since the caller of the procedure could not have anticipated that the

exception would occur, the current program is terminated.

The reason for the exception is:

Triggering ABAP/4 statement: Connect to "CONNECTION"

System environment

SAP-Release 701

Application server... "sapps2ci"

Network address...... "10.10.61.58"

Operating system..... "SunOS"

Release.............. "5.10"

Hardware type........ "sun4u"

Character length.... 16 Bits

Pointer length....... 64 Bits

Work process number.. 1

Shortdump setting.... "full"

Database server... "chr7c012"

Database type..... "ORACLE"

Database name..... "PS2"

Database user ID.. "SAPSR3"

Terminal.......... "chr7c012"

Char.set.... "C"

SAP kernel....... 701

created (date)... "Aug 10 2009 22:14:37"

create on........ "SunOS 5.9 Generic_117171-13 sun4u"

Database version. "OCI_102 (10.2.0.2.0) "

Patch level. 55

Patch text.. " "

Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."

SAP database version. 701

Operating system..... "SunOS 5.9, SunOS 5.10"

Memory consumption

Roll.... 16192

EM...... 4189848

Heap.... 0

Page.... 16384

MM Used. 2042024

MM Free. 2145224

User and Transaction

Client.............. 100

User................ "SAP_BC_BTC"

Language Key........ "E"

Transaction......... " "

Transactions ID..... "4B945D205B8E2A25E10000000A0A3D24"

Program............. "/SDF/SAPLRI_ORACLE"

Screen.............. "SAPMSSY1 3004"

Screen Line......... 2

Information on caller of Remote Function Call (RFC):

System.............. "PS2"

Database Release.... 701

Kernel Release...... 701

Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)

Call Type........... "synchron and non-transactional (emode 0, imode 0)"

Inbound TID.........." "

Inbound Queue Name..." "

Outbound TID........." "

Outbound Queue Name.." "

Client.............. 100

User................ "SAP_BC_BTC"

Transaction......... " "

Call Program........."SAPLBDL5"

Function Module..... "/BDL/_EXECUTE_FUNCTION"

Call Destination.... "NONE"

Source Server....... "sapps2ci_PS2_20"

Source IP Address... "10.10.61.58"

Additional information on RFC logon:

Trusted Relationship " "

Logon Return Code... 0

Trusted Return Code. 0

Note: For releases < 4.0, information on the RFC caller are often

only partially available.

Information on where terminated

Termination occurred in the ABAP program "/SDF/SAPLRI_ORACLE" - in

"CONNECT_REMOTEDB".

The main program was "SAPMSSY1 ".

In the source code you have the termination point in line 211

of the (Include) program "/SDF/LRI_ORACLETOP".

The termination is caused because exception "CX_SY_NATIVE_SQL_ERROR" occurred

in

procedure "CONNECT_REMOTEDB" "(FORM)", but it was neither handled locally nor

declared

in the RAISING clause of its signature.

The procedure is in program "/SDF/SAPLRI_ORACLE "; its source code begins in

line

200 of the (Include program "/SDF/LRI_ORACLETOP ".

Edited by: Dipankar@igate(SAP) on Mar 12, 2010 7:58 AM

Re: DBIF_DSQL2_CONNECTSTR_ERROR

Former Member — Fri, 12 Mar 2010 07:12:20 GMT

Hi Dipankar,

Please check the entry created for the Database connection in Transaction DBCO.

The database name, type, connection information etc must be valid/accurate w.r.t the database you wish to connect.

Regards

Raj

Re: DBIF_DSQL2_CONNECTSTR_ERROR

Former Member — Fri, 12 Mar 2010 08:16:07 GMT

Thanks Raj for your valuable input regarding this.....

I came to know that it is a catchable exception but now it is telling <h3>specified secondary database connection is not registered in table DBCON.</h3> but i am not understanding how does the secondary database come here?

topic Re: DBIF_DSQL2_CONNECTSTR_ERROR in Application Development and Automation Discussions

DBIF_DSQL2_CONNECTSTR_ERROR

Re: DBIF_DSQL2_CONNECTSTR_ERROR

Re: DBIF_DSQL2_CONNECTSTR_ERROR