DBIF_DSQL2_CONNECTSTR_ERROR<br>
Exception CX_SY_NATIVE_SQL_ERROR<br>
Short text<br>
Connection ID unknown<br><br>
What happened?<br>
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".<br><br>
Error analysis<br>
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.<br>
The reason for the exception is:
Triggering ABAP/4 statement: Connect to "CONNECTION"<br><br>
System environment<br>
SAP-Release 701<br>
Application server... "sapps2ci"<br>
Network address...... "10.10.61.58"<br>
Operating system..... "SunOS"<br>
Release.............. "5.10"<br>
Hardware type........ "sun4u"<br>
Character length.... 16 Bits<br>
Pointer length....... 64 Bits<br>
Work process number.. 1<br>
Shortdump setting.... "full"<br>
Database server... "chr7c012"<br>
Database type..... "ORACLE"<br>
Database name..... "PS2"<br>
Database user ID.. "SAPSR3"
<br>
Terminal.......... "chr7c012"<br>
Char.set.... "C"<br>
SAP kernel....... 701<br>
created (date)... "Aug 10 2009 22:14:37"<br>
create on........ "SunOS 5.9 Generic_117171-13 sun4u"<br>
Database version. "OCI_102 (10.2.0.2.0) "<br>
Patch level. 55<br>
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."<br>
SAP database version. 701
Operating system..... "SunOS 5.9, SunOS 5.10"<br>
Memory consumption<br>
Roll.... 16192
EM...... 4189848
Heap.... 0
Page.... 16384
MM Used. 2042024
MM Free. 2145224
User and Transaction<br>
Client.............. 100<br>
User................ "SAP_BC_BTC"<br>
Language Key........ "E"<br>
Transaction......... " "<br>
Transactions ID..... "4B945D205B8E2A25E10000000A0A3D24"<br>
Program............. "/SDF/SAPLRI_ORACLE"<br>
Screen.............. "SAPMSSY1 3004"<br>
Screen Line......... 2<br>
Information on caller of Remote Function Call (RFC):<br>
System.............. "PS2"<br>
Database Release.... 701<br>
Kernel Release...... 701<br>
Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)<br>
Call Type........... "synchron and non-transactional (emode 0, imode 0)"<br>
Inbound TID.........." "<br>
Inbound Queue Name..." "<br>
Outbound TID........." "<br>
Outbound Queue Name.." <br>"
<br>
Client.............. 100<br>
User................ "SAP_BC_BTC"<br>
Transaction......... " "<br>
Call Program........."SAPLBDL5"<br>
Function Module..... "/BDL/_EXECUTE_FUNCTION"<br>
Call Destination.... "NONE"<br>
Source Server....... "sapps2ci_PS2_20"<br>
Source IP Address... "10.10.61.58"<br>
<br>
Additional information on RFC logon:<br>
Trusted Relationship " "<br>
Logon Return Code... 0<br>
Trusted Return Code. 0<br>
Note: For releases < 4.0, information on the RFC caller are often<br>
only partially available.
Information on where terminated<br>
Termination occurred in the ABAP program "/SDF/SAPLRI_ORACLE" - in
"CONNECT_REMOTEDB".
The main program was "SAPMSSY1 ".<br>
In the source code you have the termination point in line 211
of the (Include) program "/SDF/LRI_ORACLETOP".<br>
The termination is caused because exception "CX_SY_NATIVE_SQL_ERROR" occurred
in<br>
procedure "CONNECT_REMOTEDB" "(FORM)", but it was neither handled locally nor
declared<br>
in the RAISING clause of its signature.<br>
The procedure is in program "/SDF/SAPLRI_ORACLE "; its source code begins in<br>
line
200 of the (Include program "/SDF/LRI_ORACLETOP ".
Edited by: Dipankar@igate(SAP) on Mar 12, 2010 7:58 AM
Bluesky
