Quantcast
Channel: SCN : Popular Discussions - SAP MaxDB
Viewing all articles
Browse latest Browse all 1545

could not load library for database connection LCA

$
0
0

Hi,

 

I am facing RFC connection prblem while connectiong to database. I have installed SCM5.1 and live cache in single server

 

Please find the logs.

 

Work process log:

 

B Mon Jul 20 11:19:13 2009

B  create_con (con_name=LCA)

B  Loading DB library 'E:\usr\sap\SC7\DVEBMGS03\exe\dbsdbslib.dll' ...

M  *** ERROR => DlLoadLib: LoadLibrary(E:\usr\sap\SC7\DVEBMGS03\exe\dbsdbslib.dll) Error 126 [dlnt.c       241]

M          Error 126 = "The specified module could not be found."

B  *** ERROR => Couldn't load library 'E:\usr\sap\SC7\DVEBMGS03\exe\dbsdbslib.dll'

[dbcon.c      4731]

B  ***LOG BYG=> could not load library for database connection LCA        [dbds#1 @ 1035] [dbds    1035 ]

A

A Mon Jul 20 11:21:58 2009

GENER starting remote generation: /SAPAPO/OM_SYNC_LC_DB (requested by W1).

B

 

 

SM21:

 

No shared library found for the database with ID LCA|

-


 

No shared library found for the database with ID LCA

 

/SAPAPO/OM17|/SAPAPO/OM_SYNC_LC_DB|K |SAP Web AS Problem|SBAC   |

-


 

 

-


Documentation for system log message BY G :

As well as the standard connection, an attempt was made to set up

another database connection, under the specified ID. The Shared Library

for this second database could not be found.

The Shared Library is usually found in the the Executable

directory (profile parameter DIR_LIBRARY) under the name dbs

<dbs>slib<os_ext>. <dbs> stands for the database type and <os_ext>

stands for the operating system-specific extension of the Shared

Libraries.

The database type is determined from the entry that corresponds to the

specified DB ID in the table DBDCON. Check whether the data in this

entry is correct.

-


 

 

 

ST22

 

Runtime Errors         DBIF_DSQL2_CONNECTERR

Exception              CX_SY_NATIVE_SQL_ERROR

Date and Time          20.07.2009 11:22:21

-


 

-


Short text

Error setting up a secondary database connection

-


 

-


What happened?

Connection to database system not possible with identifier "LCA".

-


 

-


 

 

-


|----


System environment

SAP-Release 700

Application server... "

Network address...... "

Operating system..... "Windows NT"

Release.............. "5.2"

Hardware type........ "8x AMD64 Level"

Character length.... 16 Bits

Pointer length....... 64 Bits

Work process number.. 8

Shortdump setting.... "full"

Database server... "

Database type..... "ORACLE"

Database name..... "SC7"

Database user ID.. "SAPSC7"

Terminal................. " "

Char.set.... "C"

SAP kernel....... 701

created (date)... "Jul 6 2009 23:47:55"

create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"

Database version. "OCI_10201_SHARE (10.2.0.2.0) "

Patch level. 50

Patch text.. " "

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

SAP database version. 701

Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows

NT 6.0"

-


 

 

 

-


Information on where terminated

Termination occurred in the ABAP program "SAPLSLCAPPS" - in

"LCA_EXISTS_LCA_ROUTINE".

The main program was "/SAPAPO/TS_BATCH_RUN ".

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

of the (Include) program "LSLCAPPSU05".

The program "SAPLSLCAPPS" was started as a background job.

Job Name....... "MACROS"

Job Initiator.. "SC7GEN"

Job Number..... 10222002

The termination is caused because exception "CX_SY_NATIVE_SQL_ERROR" occurred

in

procedure "LCA_EXISTS_LCA_ROUTINE" "(FUNCTION)", but it was neither handled

locally nor declared

in the RAISING clause of its signature.

The procedure is in program "SAPLSLCAPPS "; its source code begins in line

1 of the (Include program "LSLCAPPSU05 ".

-


 

 

Please help me to resolve the issue.

 

Suraj


Viewing all articles
Browse latest Browse all 1545

Trending Articles