cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Problem during installation SAP Solution Manager 7.1 on MaxDB (RHEL6)

Former Member

on ‎11-23-2011 8:24 AM

0 Kudos

Hello all!

Help me please with the problem.

Sapinst is interrupted in step "Import Java Dump" with the error:

<html> <head> </head> <body> <p> An error occurred while processing option <i>SAP Solution Manager 7.1 > SAP Systems > MaxDB > Central System > Central System( Last err
or reported by the step :<html> <head> </head> <body> Execution of <font face="Monospaced">JLoad</font> tool '/opt/IBMJava2-amd64-142/bin/java -classpath /tmp/sapinst_i
nstdir/SOLMAN71/SYSTEM/ADA/CENTRAL/AS/install/sharedlib/launcher.jar -showversion -Xmx1024m com.sap.engine.offline.OfflineToolStart com.sap.inst.jload.Jload /tmp/sapins
t_instdir/SOLMAN71/SYSTEM/ADA/CENTRAL/AS/install/lib/iaik_jce.jar:/tmp/sapinst_instdir/SOLMAN71/SYSTEM/ADA/CENTRAL/AS/install/sharedlib:/sapdb/clients/SLM/runtime/jar/s
apdbc.jar -sec SLM,jdbc/pool/SLM,/usr/sap/SLM/SYS/global/security/data/SecStore.properties,/usr/sap/SLM/SYS/global/security/data/SecStore.key -dataDir /sapdb/SLM/swdc/S
olman71_MaxDB/51040039_SAP_Solution_M_71_Java_Components/DATA_UNITS/SOLMAN_JAVA_EXPORT_JDMP -job /tmp/sapinst_instdir/SOLMAN71/SYSTEM/ADA/CENTRAL/AS/IMPORT.XML -log jlo
ad.log' aborts with return code 1.<br>SOLUTION: Check 'jload.log' and '/tmp/sapinst_instdir/SOLMAN71/SYSTEM/ADA/CENTRAL/AS/jload.java.log' for more information. </body>
</html>)</i>. You can now: </p> <ul> <li> Choose <i>Retry</i> to repeat the current step. </li> <li> Choose <i>Log Files</i> to get more information about the error. </
li> <li> Stop the option and continue with it later. </li> </ul> <p> Log files are written to <code>/tmp/sapinst_instdir/SOLMAN71/SYSTEM/ADA/CENTRAL/AS</code>. </p> </b
ody></html>

I looked at the logs jload.java.log:

java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 2.3)
IBM J9 VM (build 2.3, J2RE 1.4.2 IBM J9 2.3 Linux amd64-64 j9vmxa64142ifx-20101119 (JIT enabled)
J9VM - 20101118_68931_LHdSMr
JIT  - 20090210_1447ifx2_r8
GC   - 200902_24)

Warning : /sapdb/clients/SLM/runtime/jar/sapdbc.jar file stated but does not exist !
Jload R 7.12 V 0 A 0
Jload -sec SLM,jdbc/pool/SLM,/usr/sap/SLM/SYS/global/security/data/SecStore.properties,/usr/sap/SLM/SYS/global/security/data/SecStore.key -dataDir /sapdb/SLM/swdc/Solma
n71_MaxDB/51040039_SAP_Solution_M_71_Java_Components/DATA_UNITS/SOLMAN_JAVA_EXPORT_JDMP -job /tmp/sapinst_instdir/SOLMAN71/SYSTEM/ADA/CENTRAL/AS/IMPORT.XML -log jload.l
og
Connecting to database
Couldn't connect to DB
com.sap.inst.common.exception.DBConnectionException: com.sap.sql.log.OpenSQLException: Could not load class com.sap.dbtech.jdbc.DriverSapDB.
        at com.sap.inst.common.db.DBConnection.connect(DBConnection.java:157)
        at com.sap.inst.jload.Jload.main(Jload.java:222)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:88)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:61)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
        at java.lang.reflect.Method.invoke(Method.java:391)
        at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
Caused by: com.sap.sql.log.OpenSQLException: Could not load class com.sap.dbtech.jdbc.DriverSapDB.
        at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:106)
        at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:143)
        at com.sap.sql.connect.OpenSQLDataSourceImpl.createConnection(OpenSQLDataSourceImpl.java:522)
        at com.sap.sql.connect.OpenSQLDataSourceImpl.getConnection(OpenSQLDataSourceImpl.java:276)
        at com.sap.inst.common.db.DBConnection.connectViaSecureStore(DBConnection.java:111)
        at com.sap.inst.common.db.DBConnection.connect(DBConnection.java:151)
        ... 7 more
Caused by: java.lang.ClassNotFoundException: com.sap.dbtech.jdbc.DriverSapDB
        at java.lang.Class.forNameImpl(Native Method)
        at java.lang.Class.forName(Class.java:119)
        at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:134)
        ... 11 more

An error occured during execution. Please consult SAP note 942766 for first steps on troubleshooting the problem.

The MaxDB works fine and I connect to it without any problems with Database Manager.

As I understand the problem in file sapdbc.jar?

Where can I get it?

Show replies
Show replies
Answer

Accepted Solutions (0)

Answers (2)

Answers (2)

former_member188883
Active Contributor
‎11-23-2011 8:46 AM
0 Kudos

Hi,

Please refer to the link below

http://maxdb.sap.com/doc/7_8/37/5f6b6e966242aead8025bdc5296489/content.htm

Hope this helps in resolving the issue.

Regards,

Deepak Kori

Show replies
Show replies
Former Member
‎11-23-2011 12:56 PM
0 Kudos

I found this file sapdbc.jar. It is located in the directory /sapdb/programs/runtime/jar.

But how to install it? I need to just copy it to the right place?

I have also done the following command:

export CLASSPATH=$CLASSPATH:/sapdb/programs/runtime/jar/sapdbc.jar

I run sapinst again, but the problem remained.

And I have no such directory /sapdb/clients/SLM/runtime/jar/

I use MaxDB 7.7.04.28

markus_doehr2
Active Contributor
‎11-23-2011 1:06 PM
0 Kudos

> And I have no such directory /sapdb/clients/SLM/runtime/jar/

> I use MaxDB 7.7.04.28

According to PAM Solution Manager 7.1 is only available on MaxDB 7.8.

To not start all over I suggest you run a MaxDB upgrade to 7.8, install the latest patch and continue then with your installation.

Markus

Former Member
‎11-23-2011 3:53 PM
0 Kudos

Thanks Marcus, I have not looked at PAM.

Now I began to update the database to 7.8.

I do everything according to guide: Upgrade to SAP MaxDB Version 7.8 UNIX

I downloaded the package 51041558_12 (MaxDB RDBMS 7.8 Update)

But I got the error:


[root@sap MAXDB_UPDATE]# ./DBUPDATE.SH

Do you want to continue the upgrade [Y] :

Check installation of C++ runtime
...execution 17:29:40
OK

IndepProgPath : /sapdb/programs
IndepDataPath : /sapdb/data

Please enter SAP MaxDB Name    [SID] :
SLM
Please enter SAP System Name   [SID] :
SLM
Please enter DBM User Name [control] :
Please enter DBM User Password       :


INSTROOT        : /sapdb/SLM/db
Authorization successful
DB KERNEL       : 64-BIT
DB VERSION      : 7.7.04 Build 28
Database instance version supported
PrivateDataPath : NO

Check availability of SAP users
...execution 17:29:53
SLMadm
SAP System Administrator   : slmadm
sqdSLM
SAP Database Administrator : sqdslm
OK

SAP VERSION     : -4001,Unknown user name/password combination in operational state ADMIN
ERROR: DVD directory access failed !
--> Check existence of Linux directory and ensure that
--> this operating system is supported on the SAP MaxDB DVD.
--> Otherwise, please contact the SAP support team.

I work as user root and to file DBUPDATE.SH I assigned the owner root:sapsys

I'm doing something wrong?

markus_doehr2
Active Contributor
‎11-23-2011 4:01 PM
0 Kudos

> I work as user root and to file DBUPDATE.SH I assigned the owner root:sapsys

Is the password for superdba you entered correct?

is the DVD on NFS? If yes, try locally

Markus

Former Member
‎11-24-2011 7:41 AM
0 Kudos

Here's a more detailed log:


[root@sap MAXDB_UPDATE]# ./DBUPDATE.SH

INFORMATION : This program upgrades the SAP MaxDB database instance
              from at least version >= 7.5
              to SAP MaxDB version 7.8.

              CAUTION:
              The upgrade phase "migrate catalog"
              will need a long operating time.
              Don't cancel the execution of the upgrade.
              Otherwise the risk of data leakage exists!

              Note:
              With version 7.8,
              the Isolated Installation is introduced.

              Upgrade strategy:
              In-Place Upgrade with SDBUPD

              To prepare for the upgrade you need a data backup
              as described in the upgrade guide:
              'Upgrade to SAP MaxDB version 7.8' !
              You can find this on SAP Service Marketplace at:
              http://service.sap.com/instguides -> Database Upgrades -> MaxDB

Do you want to continue the upgrade [Y] :  y

Check installation of C++ runtime
...execution 09:33:56
OK

IndepProgPath : /sapdb/programs
IndepDataPath : /sapdb/data

Please enter SAP MaxDB Name    [SID] :  SLM
Please enter SAP System Name   [SID] :  SLM
Please enter DBM User Name [control] :  control
Please enter DBM User Password       :

INSTROOT        : /sapdb/SLM/db
Authorization successful
DB KERNEL       : 64-BIT
DB VERSION      : 7.7.04 Build 28
Database instance version supported
PrivateDataPath : NO

Check availability of SAP users
...execution 09:34:08
SAP System Administrator   : slmadm
SAP Database Administrator : sqdslm
OK

SAP VERSION     : -4001,Unknown user name/password combination in operational state ADMIN
ls: /51041558/DATA_UNITS/MAXDB_UPDATE/../MAXDB_[Ll][Ii][Nn][Uu][Xx]_[Xx]86_64: No such file or directory
ERROR: DVD directory access failed !
--> Check existence of Linux directory and ensure that
--> this operating system is supported on the SAP MaxDB DVD.
--> Otherwise, please contact the SAP support team.
[root@sap MAXDB_UPDATE]#

I can not understand what it means line:

ls: /51041558/DATA_UNITS/MAXDB_UPDATE/../MAXDB_[Ll][Ii][Nn][Uu][Xx]_[Xx]86_64: No such file or directory

can anyone experienced this?

former_member188883
Active Contributor
‎11-24-2011 9:46 AM
0 Kudos

Hi,

SAP VERSION     : -4001,Unknown user name/password combination in operational state ADMIN
ls: /51041558/DATA_UNITS/MAXDB_UPDATE/../MAXDB_[Ll][Ii][Nn][Uu][Xx]_[Xx]86_64: No such file or directory
ERROR: DVD directory access failed !

Your MaxDB software directory is not accessible. Can you make the permission as 777 and try again.

Also try to keep the DVD path smaller.

Regards,

Deepak Kori

Former Member
‎11-25-2011 8:00 AM
0 Kudos

until I decide one problem - there are new problems:)

Now I have one server has two instances DVL and SLM.

DVL is ERP 6.0 SR3 at MaxDB 7.7

SLM - it is interrupted installation Solution Manager 7.1

To complete the installation Solution Manager 7.1 I started to update the database instance SLM from 7.7 to 7.8.

Update was successful.

Now I want to upgrade and DVL. But I have an error occurs. Here's the log:


START_TIME = 20111124165732

INFORMATION : This program upgrades the SAP MaxDB database instance
              from at least version >= 7.5
              to SAP MaxDB version 7.8.

              CAUTION:
              The upgrade phase "migrate catalog"
              will need a long operating time.
              Don't cancel the execution of the upgrade.
              Otherwise the risk of data leakage exists!

              Note:
              With version 7.8,
              the Isolated Installation is introduced.

              Upgrade strategy:
              In-Place Upgrade with SDBUPD

              To prepare for the upgrade you need a data backup
              as described in the upgrade guide:
              'Upgrade to SAP MaxDB version 7.8' !
              You can find this on SAP Service Marketplace at:
              http://service.sap.com/instguides -> Database Upgrades -> MaxDB

Do you want to continue the upgrade [Y] :

Check installation of C++ runtime
...execution 16:57:34
OK

IndepProgPath : /sapdb/programs
IndepDataPath : /sapdb/data

Please enter SAP MaxDB Name    [SID] :
DVL
Please enter SAP System Name   [SID] :
DVL
Please enter DBM User Name [control] :
Please enter DBM User Password       :

INSTROOT        : /sapdb/DVL/db
Authorization successful
DB KERNEL       : 64-BIT
DB VERSION      : 7.7.04 Build 28
Database instance version supported
PrivateDataPath : NO

Check availability of SAP users
...execution 16:57:48
DVLadm
SAP System Administrator   : dvladm
sqdDVL
SAP Database Administrator : sqddvl
OK

SAP VERSION     : -4001,Unknown user name/password combination in operational state ADMIN

Please confirm the upgrade start [Y] :

Update of dbenv scripts for SAP System Administrator 'dvladm'
...execution 16:57:51
.dbenv.sh found
.dbenv.sh
.dbenv.sh updated with /swdc/Solman71_MaxDB/MAXDB_LINUX_X86_64/DBENV/DBENV.SH
.dbenv.csh found
.dbenv.csh
.dbenv.csh updated with /swdc/Solman71_MaxDB/MAXDB_LINUX_X86_64/DBENV/DBENV.CSH
No updatable MaxDB environment file .dbenv_sap.sh found.
--> Check home directory of SAP System Administrator

---------------------------------------------------------------------
Do you want to specify a different dbenv filename
(e.g. for virtual hostnames) [Y] :

I have been unable to locate this file dbenv_sap.sh

how do I upgrade DVL instance from 7.7 to 7.8?

former_member188883
Active Contributor
‎11-25-2011 9:49 AM
0 Kudos

Hi,

Can you search this file dbenv_sap.sh. Atleast trace the location of this file using find command in unix.

Regards,

Deepak Kori

markus_doehr2
Active Contributor
‎11-25-2011 1:02 PM
0 Kudos

This script is not there yet because the installation is not yet finished.

Copy for both <sid>adm and sqd<SID> the .dbenv.csh to the given filename in the home directory of the user, then re-execute the upgrade.

Markus

Former Member
‎11-25-2011 2:39 PM
0 Kudos

I found the files, they were hidden.

I updated the base from 7.7 to 7.8 successfully:

Execution of DB server upgrade
...execution 15:53:07
Info: MajorUpgrade, includes update of installation Global.
OK

Installation of isolated (dedicated) client software for SAP System SLM
...execution 15:57:30
Installation Name = CL_SLM
Installation Path = /sapdb/clients/SLM
OK
test

######################################################
#  Upgrade to MaxDB version 7.8 finished successful  #
######################################################

C A U T I O N :
Perform a complete backup so that you can
recover the new database state if necessary.

Note: Continue with the post-upgrade activities
      described in the upgrade guide.

N O T E :
Relogin with the sidadm and sqdsid users
for the environment changes to take effect.

but now I can not run the instance DVL!

markus_doehr2
Active Contributor
‎11-25-2011 2:40 PM
0 Kudos

> but now I can not run the instance DVL!

What is "instance DVL"?

Markus

Former Member
‎11-25-2011 2:46 PM
0 Kudos

Sorry, Marcus, I worry

DVL It is SAP ERP 6.0 SR3 on the MaxDB7.7

I updated MaxDB from 7.7 to 7.8 and tried to start.

But it does not start...

markus_doehr2
Active Contributor
‎11-25-2011 2:47 PM
0 Kudos

> Sorry, Marcus, I worry

> DVL It is SAP ERP 6.0 SR3 on the MaxDB7.7

> I updated MaxDB from 7.7 to 7.8 and tried to start.

What exactly is not starting? the database or the SAP application?

Markus

Former Member
‎11-25-2011 2:54 PM
0 Kudos

The database starts, I connect to it with the Database Manager 7.6.

Do not start the SAP application.

Currently looking in the logs, what is wrong?

markus_doehr2
Active Contributor
‎11-25-2011 2:55 PM
0 Kudos

Check the logfile

dev_w0

Markus

Former Member
‎11-25-2011 3:07 PM
0 Kudos

I find this file, but I do not understand what the problem is:

---------------------------------------------------
trc file: "dev_w0", trc level: 1, release: "700"
---------------------------------------------------
*
*  ACTIVE TRACE LEVEL           1
*  ACTIVE TRACE COMPONENTS      all, MJ
*
M sysno      10
M sid        DVL
M systemid   390 (AMD/Intel x86_64 with Linux)
M relno      7000
M patchlevel 0
M patchno    310
M intno      20050900
M make:      single threaded, Unicode, 64 bit, optimized
M pid        27169
M
M
M Fri Nov 25 16:00:37 2011
M  kernel runs with dp version 247000(ext=110000) (@(#) DPLIB-INT-VERSION-247000-UC)
M  length of sys_adm_ext is 576 bytes
M  ThInit: rdisp/cleanup_after_crash = 1
M  ***LOG Q01=> ThInit, WPStart (Workproc 0 1 27169) [thxxhead.c   1354]
M  ThInit: running on host sap-dvl
M  calling db_connect ...
B  Loading DB library '/usr/sap/DVL/SYS/exe/run/dbsdbslib.so' ...
B  Library '/usr/sap/DVL/SYS/exe/run/dbsdbslib.so' loaded
B  Version of '/usr/sap/DVL/SYS/exe/run/dbsdbslib.so' is "700.08", patchlevel (0.301)
C
C  DBSDBSLIB : version 700.08, patch 0.301 (Make PL 0.310)
C  MAXDB shared library (dbsdbslib) patchlevels (last 10)
C    (0.301) UPDSTAT with SAPSYSTEMNAME longer as 3 characters (note 1584921)
C    (0.272) Empty string handling for NUMC, DATE and TIME (note 1509705)
C    (0.261) ABAP: Return technical database PPMS information (note 1419552)
C    (0.256) Unknown primary key (note 1459400)
C    (0.256) Connection table corrected (note 1466271)
C    (0.247) Use SCHEMANAME instead of OWNER for MaxDB 7.8 (note 1353266)
C    (0.244) Support of  MaxDB 7.8 (note 1353266)
C    (0.211) MVCC support for MaxDB (note 1332203)
C    (0.204) Sapinst on windows/maxdb stop with error (note 1323436)
C    (0.202) NUMC conversion corrected (note 1288313)

C  Loading SQLDBC client runtime ...
C  SQLDBC SDK Version : SQLDBC.H  7.6.0    BUILD 002-121-083-965
C  SQLDBC Library Version : libSQLDBC 7.6.6    BUILD 010-123-229-880
C  SQLDBC client runtime is MaxDB 7.6.6.010 CL 229880
C  SQLDBC supports new DECIMAL interface : 0
C  SQLDBC supports VARIABLE INPUT data   : 1
C  SQLDBC supports keepAlive indicator   : 0
C  INFO : SQLOPT= -I 0 -t 0 -S SAPR3
C  Try to connect (DEFAULT) on connection 0 ...
C  *** ERROR => Connect to database failed, rc = -10709 (Connection failed (RTE:[1] protocol error))
 [dbsdbsql.cpp 137]
B  ***LOG BV3=> severe db error -10709    ; work process is stopped [dbsh#3 @ 1203] [dbsh    1203 ]
B  ***LOG BY2=> sql error -10709 performing CON [dblink#8 @ 433] [dblink  0433 ]
B  ***LOG BY0=> Connection failed (RTE:[1] protocol error) [dblink#8 @ 433] [dblink  0433 ]
M  ***LOG R19=> ThInit, db_connect ( DB-Connect 000256) [thxxhead.c   1513]
M  in_ThErrHandle: 1
M  *** ERROR => ThInit: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c   10806]
M
M  Info for wp 0
M
M    pid = 27169
M    severity = 0
M    status = 0
M    stat = WP_RUN
M    waiting_for = NO_WAITING
M    reqtype = DP_RQ_DIAWP
M    act_reqtype = NO_REQTYPE
M    rq_info = 0
M    tid = -1
M    mode = 255
M    len = -1
M    rq_id = 65535
M    rq_source =
M    last_tid = 0
M    last_mode = 0
M    semaphore = 0
M    act_cs_count = 0
M    csTrack = 0
M    csTrackRwExcl = 0
M    csTrackRwShrd = 0
M    mode_cleaned_counter = 0

M    control_flag = 0
M    int_checked_resource(RFC) = 0
M    ext_checked_resource(RFC) = 0
M    int_checked_resource(HTTP) = 0
M    ext_checked_resource(HTTP) = 0
M    report = >                                        <
M    action = 0
M    tab_name = >                              <
M    attachedVm = no VM
M  PfStatDisconnect: disconnect statistics
M  Entering TH_CALLHOOKS
M  ThCallHooks: call hook >ThrSaveSPAFields< for event BEFORE_DUMP
M  *** ERROR => ThrSaveSPAFields: no valid thr_wpadm [thxxrun1.c   730]
M  *** ERROR => ThCallHooks: event handler ThrSaveSPAFields for event BEFORE_DUMP failed [thxxtool3.c  262]
M  ThCallHooks: call hook >BtcCallLgCl< for event BEFORE_DUMP
M  Entering ThSetStatError
M  ThIErrHandle: do not call ThrCoreInfo (no_core_info=0, in_dynp_env=0)
M  Entering ThReadDetachMode
M  call ThrShutDown (1)...
M  ***LOG Q02=> wp_halt, WPStop (Workproc 0 27169) [dpuxtool.c   269]

markus_doehr2
Active Contributor
‎11-25-2011 3:10 PM
0 Kudos

> C Try to connect (DEFAULT) on connection 0 ...

> C *** ERROR => Connect to database failed, rc = -10709 (Connection failed (RTE:[1] protocol error))

> [dbsdbsql.cpp 137]

> B ***LOG BV3=> severe db error -10709 ; work process is stopped [dbsh#3 @ 1203] [dbsh 1203 ]

> B ***LOG BY2=> sql error -10709 performing CON [dblink#8 @ 433] [dblink 0433 ]

> B ***LOG BY0=> Connection failed (RTE:[1] protocol error) [dblink#8 @ 433] [dblink 0433 ]

> M ***LOG R19=> ThInit, db_connect ( DB-Connect 000256) [thxxhead.c 1513]

> M in_ThErrHandle: 1

> M *** ERROR => ThInit: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c 10806]

I woudl recommend updating this database (DVL) also to MaxDB 7.8.

It seems there's now a kind of mixed up environment.

Markus

Former Member
‎11-25-2011 3:17 PM
0 Kudos

I did not understand.

I also updated the database instance DVL to 7.8 and not started. Until then, it was 7.7 and worked fine

markus_doehr2
Active Contributor
‎11-25-2011 3:29 PM
0 Kudos

> I did not understand.

According to what you wrote here you update the instance SLM for go on with the installation of Solution Manager.

> I also updated the database instance DVL to 7.8 and not started. Until then, it was 7.7 and worked fine

when did you update that?

It's very difficult if you give only partial information (such as the fact, that other database versions are installed on the same server).

Markus

Former Member
‎11-25-2011 3:53 PM
0 Kudos

Yes, Markus, I'm sorry, I wrote above, that this server is another SAP system DVL

I also updated it and now it does not work.

This is an work system and the developers are working there.

So I temporarily put off the installation Solution Manager.

From the logs I see that it can not connect to the database.

Probably need something to update. I found the note 1393687, which may be necessary to update the file startdb.

But I have the latest version of the kernel SAPEXEDB_310-20001347 and SAPEXE_310-20001346.

markus_doehr2
Active Contributor
‎11-25-2011 4:00 PM
0 Kudos

> Probably need something to update. I found the note 1393687, which may be necessary to update the file startdb.

> But I have the latest version of the kernel SAPEXEDB_310-20001347 and SAPEXE_310-20001346.

The system says "protocol error" - which makes me assume that there are version incosistencies on the system.

I would open an OSS call under BC-DB-SDB and let the support have a look on the system, they may give you better advised if they can check the logs themselves.

Markus

markus_doehr2
Active Contributor
‎11-23-2011 8:40 AM
0 Kudos

> Warning : /sapdb/clients/SLM/runtime/jar/sapdbc.jar file stated but does not exist !

Is this file exiting at that place?

What database version are you using?

Markus

Show replies
Show replies
Ask a Question