LiveCache ERROR => DlLoadLib()==DLENOACCESS - LoadLibrary

[Former Member]

Hi,

I have upgraded my SCM 4.1 Systems to 7.02. During the upgrade I have come to a stage where Upgrade tool SUM is asking me to upgrade the LiveCache DB.

LiveCache database upgrade is from 7.5 to 7.9. I have done the Livecache upgrade and also the database client on SCM server.

But I am facing the problem with connecting the SCM system with LiveCache database. It is giving the below error:

In SM21 --> No shared library found for the database with ID LCA

When I went to check the Work Process Trace I found the below error:

B Loading DB library 'F:\USR\SAP\DSC\dvebmgs00\exe\dbsdbslib.dll' ...

M *** ERROR => DlLoadLib()==DLENOACCESS - LoadLibrary

("F:\USR\SAP\DSC\dvebmgs00\exe\dbsdbslib.dll")

Error 126 = "The specified module could not be found." [dlnt.c

255]

M {root-id=005056A674CA1EE28EFC8BC11EA771F8}_{conn-

id=70E43BE2E057F1E7B1F8005056A674CA}_1

B *** ERROR => Couldn't load library 'F:\USR\SAP\DSC\dvebmgs00

\exe\dbsdbslib.dll'

[dbcon.c 5767]

Though I can see that the required files are present in the kernel

directory. I have also done the Database client upgrade. I have also

referred to the SAP Notes# 649814 & 822239 but to no avail.

Though I did not have any problem while upgrading the Sandbox.

In DB59 --> Connection Test, It is giving the below error:

SDBINFO:

Name and Server : DLC - ctnhsapdlc

Function : DBM_GETF

Command : SDBINFO

Error : DBM Error

Return Code : -24589

Error Message : ERR_FILENOEXIST: File 'H:\sapdb\data\wrk

Please also find the result of the command SDBREGVIEW -L as below:

Installation: Global F:\sapdb\programs

Global Listener 7.9.07.09 valid 64 bit

Installation Compatibility 7.9.07.09 valid 64 bit

Installer 7.9.07.09 valid

SAP Utilities Compatibility 7.9.07.09 valid 64 bit

Installation: Legacy F:\sapdb\programs

JDBC F:\sapdb\programs 7.6.00.12 valid

Loader F:\sapdb\programs 7.5.00.31 valid 64 bit

ODBC F:\sapdb\programs 7.5.00.31 valid 64 bit

PCR 7301 F:\sapdb\programs 7.3.01.19 valid

PCR 7500 F:\sapdb\programs 7.5.00.31 valid 64 bit

Installation: CL_DSC F:\sapdb\clients\DSC

Base 7.9.08.03 valid 64 bit

Fastload API 7.9.08.03 valid 64 bit

JDBC 7.6.06.09 valid

Loader 7.9.08.03 valid 64 bit

Messages MSG 0.10302 valid

ODBC 7.9.08.03 valid 64 bit

Redist Python 7.9.08.03 valid 64 bit

SAP Utilities 7.9.08.03 valid 64 bit

SQLDBC 7.9.08.03 valid 64 bit

SQLDBC 76 7.6.06.22 valid 64 bit

SQLDBC 77 7.9.08.03 valid 64 bit

I have already gone through the various SAP Notes# 822239, 649814 and have applied all the recommendations like updating the DB library and Environment variable but to no avail. I did the same upgrade in the Sandbox environment but could not face the same problem.

Please help me on this.

With Regards, Ashish Sureka

[Former Member · Accepted solution]

Hi Ashish,

As per the relevant LiveCache upgrade guide(Upgrade Guide SAP SCM 7.0 EHP 2  Standalone Engine SAP liveCache Technology 7.9: Windows) in section 5.1(post activities), there is a command that must be executed in order to upgrade the livecache client as well:

1. Log on as a user with administrator rights.
2. Stop the SAP central and dialog instances.
3. Stop the server for Remote SQL: x_server stop
4. Start the client software upgrade with the liveCache DVD:  <liveCache DVD>:\LC_UPDATE\LCUPDATE.BAT -s <SAPSID> -client

5. Log on again as a user with administrator rights.

NOTE: Make sure that you log on from the beginning because the user environment should be  changed.

6. Restart the SAP instance service SAP<SID>_<instance number>.
7. Start the SAP instance using the Microsoft Management Console.
8. If you stopped other SAP MaxDB instances, restart them and also restart the server for Remote SQL using the following command: x_server start.

After that, please check whether you can perform the DB59 conectivity tests.

Regards,

Sachin

[Former Member · Accepted solution]

Hi Sachin,

I have already done the client Upgrade as advised in the upgrade guide and also mentioned by you.

In fact I have successfully upgraded my Sandbox Environment. I do not know why this issue is coming to me in Development box.

Please let me know in case something else has to be done.

With Regards, Ashish Sureka

[premsukh_bishnoi · Accepted solution]

Hi,

did you check the environment variables for <sid>adm user? It must

contain the path to the MaxDB client software. For a detailed

explanation of this topic please refer to note 822271.

Can you please refer below sap note carefully.

822271 FAQ: SAP MaxDB client software

Please execute from the commandbox the command:

echo %PATH%

Kind Regards, Premsukh

[Former Member · Accepted solution]

Hi,

please provide the extracts from below mentioned logs:

sapstartsrv.log
sapstart.log
dev_disp

Regards,
Sachin

[Former Member · Accepted solution]

Hi Premsukh,

I have checked the Note# 822271 and have followed each steps.

Please also find the belwo logs:

SAPSTART.LOG

SAP-R/3-Startup Program

Starting at 2012/12/03  3:51:56
Startup Profile: "F:\usr\sap\DSC\SYS\profile\START_DVEBMGS00_CTNHSAPDSC"
Starting Programs
(764) Execute: F:\usr\sap\DSC\SYS\exe\uc\NTAMD64\sapcpe.EXE pf=F:\usr\sap\DSC\SYS\profile\DSC_DVEBMGS00_CTNHSAPDSC
(3028) Execute: F:\usr\sap\DSC\SYS\exe\uc\NTAMD64\strdbs.cmd DSC
(3336) CreateProcess: F:\usr\sap\DSC\DVEBMGS00\exe\msg_server.exe pf=F:\usr\sap\DSC\SYS\profile\DSC_DVEBMGS00_CTNHSAPDSC
(448) CreateProcess: F:\usr\sap\DSC\DVEBMGS00\exe\disp+work.exe pf=F:\usr\sap\DSC\SYS\profile\DSC_DVEBMGS00_CTNHSAPDSC

SAPSTARTSRV.LOG

[Thr 1700] Mon Dec 03 03:40:18 2012
SAP HA Trace: SAP Microsoft Cluster library '720, patch 325, changelist 1374614' initialized
CCMS agent initialization for instance type ABAP: return code 0.
CCMS agent start: return code 0.
Initializing SAPControl Webservice
Starting AutoRestart thread
AutoRestart thread started, version check is enabled
SapSSLInit failed => https support disabled
Starting WebService Named Pipe thread
Starting WebService thread
Webservice named pipe thread started, listening on port \\.\pipe\sapcontrol_00
Webservice thread started, listening on port 50013

CORP\dscadm is starting SAP System at 2012/12/03  3:51:56
SAP HA Trace: FindClusterResource: OpenCluster failed: 1060 [sapwinha.cpp, line 213]
SAP HA Trace: SAP_HA_FindSAPInstance returns: SAP_HA_FAIL [sapwinha.cpp, line 920]

DISP+WORK

---------------------------------------------------
trc file: "dev_disp", trc level: 1, release: "720"
---------------------------------------------------
sysno      00
sid        DSC
systemid   562 (PC with Windows NT)
relno      7200
patchlevel 0
patchno    325
intno      20020600
make       multithreaded, Unicode, 64 bit, optimized
profile    F:\usr\sap\DSC\SYS\profile\DSC_DVEBMGS00_CTNHSAPDSC
pid        448

kernel runs with dp version 137000(ext=119000) (@(#) DPLIB-INT-VERSION-137000-UC)
length of sys_adm_ext is 588 bytes
*** SWITCH TRC-HIDE on ***
***LOG Q00=> DpSapEnvInit, DPStart (00 448) [dpxxdisp.c   1317]
shared lib "dw_xml.dll" version 325 successfully loaded
shared lib "dw_xtc.dll" version 325 successfully loaded
shared lib "dw_stl.dll" version 325 successfully loaded
shared lib "dw_gui.dll" version 325 successfully loaded
shared lib "dw_mdm.dll" version 325 successfully loaded
shared lib "dw_rndrt.dll" version 325 successfully loaded
shared lib "dw_abp.dll" version 325 successfully loaded
shared lib "dw_sym.dll" version 325 successfully loaded
shared lib "dw_aci.dll" version 325 successfully loaded
rdisp/softcancel_sequence :  -> 0,5,-1
rdisp/dynamic_wp_check : 1
rdisp/calculateLoadAverage : 1

Mon Dec 03 03:52:11 2012
*** WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 5 seconds
***LOG GZZ=> 1 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c  6437]
MtxInit: 30000 0 0
DpSysAdmExtInit: ABAP is active
DpSysAdmExtInit: VMC (JAVA VM in WP) is not active
DpIPCInit2: write dp-profile-values into sys_adm_ext
DpIPCInit2: start server >CTNHSAPDSC_DSC_00                       <
DpShMCreate: sizeof(wp_adm)  40608 (2256)
DpShMCreate: sizeof(tm_adm)  54923456 (27448)
DpShMCreate: sizeof(wp_ca_adm)  64000 (64)
DpShMCreate: sizeof(appc_ca_adm) 128000 (64)
DpCommTableSize: max/headSize/ftSize/tableSize=2000/16/5536064/5536080
DpShMCreate: sizeof(comm_adm)  5536080 (2744)
DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0
DpShMCreate: sizeof(slock_adm)  0 (296)
DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
DpShMCreate: sizeof(file_adm)  0 (80)
DpShMCreate: sizeof(vmc_adm)  0 (2160)
DpShMCreate: sizeof(wall_adm)  (416064/352496/64/192)
DpShMCreate: sizeof(gw_adm) 48
DpShMCreate: sizeof(j2ee_adm) 3952
DpShMCreate: SHM_DP_ADM_KEY  (addr: 000000000DC50050, size: 61478976)
DpShMCreate: allocated sys_adm at 000000000DC50060
DpShMCreate: allocated wp_adm_list at 000000000DC530B0
DpShMCreate: allocated wp_adm at 000000000DC532A0
DpShMCreate: allocated tm_adm_list at 000000000DC5D150
DpShMCreate: allocated tm_adm at 000000000DC5D1A0
DpShMCreate: allocated wp_ca_adm at 00000000110BE270
DpShMCreate: allocated appc_ca_adm at 00000000110CDC80
DpShMCreate: allocated comm_adm at 00000000110ED090
DpShMCreate: system runs without slock table
DpShMCreate: system runs without file table
DpShMCreate: allocated vmc_adm_list at 00000000116349F0
DpShMCreate: system runs without vmc_adm
DpShMCreate: allocated gw_adm at 0000000011634AA0
DpShMCreate: allocated j2ee_adm at 0000000011634AE0
DpShMCreate: allocated ca_info at 0000000011635A60
DpShMCreate: allocated wall_adm at 0000000011635AF0
DpCommAttachTable: attached comm table (header=00000000110ED090/ft=00000000110ED0A0)
DpSysAdmIntInit: initialize sys_adm
rdisp/test_roll : roll strategy is DP_NORMAL_ROLL
dia token check not active (7 token)
MBUF state OFF
DpCommInitTable: init table for 2000 entries
DpRqQInit: keep protect_queue / slots_per_queue 0 / 2001 in sys_adm
rdisp/queue_size_check_value :  -> on,50,30,40,500,50,500,80
EmInit: MmSetImplementation( 2 ).
MM global diagnostic options set: 0
<ES> client 0 initializing ....
<ES> EsILock: use spinlock for locking
<ES> InitFreeList
<ES> block size is 4096 kByte.
<ES> Info: em/initial_size_MB( 16382MB) not multiple of em/blocksize_KB( 4096KB)
<ES> Info: em/initial_size_MB rounded up to 16384MB
Using implementation view
<EsNT> Using memory model view.
<EsNT> Memory Reset disabled as NT default
<ES> 4095 blocks reserved for free list.
ES initialized.
mm.dump: set maximum dump mem to 96 MB
DpVmcSetActive: set vmc state DP_VMC_NOT_ACTIVE
MPI: dynamic quotas disabled.
MPI init: pipes=4000 buffers=1279 reserved=383 quota=10%

Mon Dec 03 03:52:12 2012
*** WARNING => System running without ICM - check rdisp/start_icman [dpxxdisp.c   13418]
rdisp/http_min_wait_dia_wp : 1 -> 1
***LOG CPS=> DpLoopInit, ICU ( 4.0.1 4.0.1 5.1) [dpxxdisp.c   1703]
***LOG Q0K=> DpMsAttach, mscon ( CTNHSAPDSC) [dpxxdisp.c   12654]
MBUF state LOADING
DpStartStopMsg: send start message (myname is >CTNHSAPDSC_DSC_00                       <)
DpStartStopMsg: start msg sent

Mon Dec 03 03:52:13 2012
CCMS: Initialized monitoring segment of size 60000000.
CCMS: Initialized CCMS Headers in the shared monitoring segment.
CCMS: Checking Downtime Configuration of Monitoring Segment.
CCMS: AlMsUpload called by wp 1024.

Mon Dec 03 03:52:17 2012
CCMS: AlMsUpload successful for F:\usr\sap\DSC\DVEBMGS00\log\ALMTTREE.DAT (1563 MTEs).

Mon Dec 03 03:52:19 2012
CCMS: start to initalize 3.X shared alert area (first segment).
DpMBufHwIdSet: set Hardware-ID
***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c   1296]
MBUF state ACTIVE
DpWpBlksLow: max wp blocks in queue is 800 (80 %)
MBUF component UP
DpMsgProcess: 1 server in MBUF
DpAppcBlksLow: max appc blocks in queue is 1000 (50 %)

Mon Dec 03 03:52:29 2012
DpModState: change server state from STARTING to ACTIVE

With Regards, Ashish Sureka

[Former Member · Accepted solution]

Hi Sachin,

Have u started your SCM server application successfully ?

Have u upgraded your LC client ?

What is your landscape of SCM and plateform ?

Regards

Ganesh Datt Tiwari

[Former Member · Accepted solution]

Hi,

Yes, I am able to start the SCM application successfully.

We are running SCM 702 (After Upgrade) on Windows 2008 and SQL 2008 database.

With Regards, Ashish Sureka

[Former Member · Accepted solution]

Hi Ashish,

Is your LC installed on different server ?

have you change master password in SCM server  ?

control user oassword is maintained correctly ?

Before com[pleteing the SCM upgrade have u followed all the consistency check of LC and downloaded all the data as per upgrade guide.

Please check.

Regards

Ganesh Datt Tiwari

[Former Member · Accepted solution]

Hi,

My LIveCache is installed on different server. I have reconfigured the connection and maintained the correct passwords. We have done the consistency check of LiveCache but still I have the problem.

Regards, Ashish Sureka

[Former Member · Accepted solution]

Hi Ashish,

Please check your x server is running or not

/sapdb/programs/bin/ if u have sapdb.

Also check that hostname of SCM server and LC server is maintained in host file of each other and services are maintained.

Regards

Ganesh Datt Tiwari

[Former Member · Accepted solution]

Hi Ganesh,

The X_Server is running and we have /sapdb/programs/bin.

Hostanames of SCM server and LC server is maintained in the host file of each other and services are maintained, The problem is very similar to the SAP Note# 1500638 but the solution suggested in the Note has not worked.

Regards, Ashish Sureka

[Former Member · Accepted solution]

Hi,

There was the problem of Windows 2008 Patches. We have applied all the windows patches and problem resolved.

Thanks everyone for all the valuable suggestions.

Regards, Ashish Sureka

[Former Member · Accepted solution]

Hi,

Thats great that issue has been resolved.

Congratulations

Rgds,

Sachin