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: 

Problems connecting to DB during startsap routine

Go to solution
Former Member

on ‎07-07-2009 2:40 PM

0 Kudos

Hello all,

I am running an IDES installation with MaxDB on RHEL 5. Installation was very smooth and the system was functioning properly. Yesterday, someone was working with the startup profiles and SAP GUI connections became impossible. Here is a list of software versions and some log files. My experience with SAP is somewhat limited; please let me know if any other information will be pertinent.

Thank you!

SID:
   XT1
Packages:
   NW_7.0_SR3_Kernel_WINDOWS__LNX_X86
   SAP_ERP_6.0_SR3_IDES_Inst._Master
   RDBMS_MAXDB_7.6.03_Build_09


/home/xt1adm/startsap_DVEBMSGS00

Trace of system startup/check of SAP System XT1 on Tue Jul  7 09:29:40 EDT 2009


Called command: /usr/sap/XT1/SYS/exe/run/startsap DVEBMGS00

Starting SAP Instance DVEBMGS00
------------------------------
 Instance Service on host exaservXT1 started

SAP-R/3-Startup Program Rel 700 V1.8 (2003/04/24)
-------------------------------------------------

Starting at 2009/07/07 09:29:40
Startup Profile: "/usr/sap/XT1/SYS/profile/START_DVEBMGS00_exaservXT1"

Setup Environment Variables
---------------------------
(18614) SETENV LD_LIBRARY_PATH=/usr/sap/XT1/DVEBMGS00/exe:/usr/sap/XT1/DVEBMGS00/exe:/usr/sap/XT1/SYS/exe/run:/sapdb/programs/lib
(18614) SETENV SHLIB_PATH=/usr/sap/XT1/DVEBMGS00/exe:
(18614) SETENV LIBPATH=/usr/sap/XT1/DVEBMGS00/exe:

Update local Kernel Files
-------------------------
(18615) Local: /usr/sap/XT1/SYS/exe/run/sapcpe name=XT1
(18614) system(/usr/sap/XT1/SYS/exe/run/sapcpe name=XT1) returns 1
(18614) Return-Code 1 in Local-Kernel-Update. See sapcpe.log.

Execute Pre-Startup Commands
----------------------------
(18617) Local: /usr/sap/XT1/SYS/exe/run/sapcpe pf=/usr/sap/XT1/SYS/profile/XT1_DVEBMGS00_exaservXT1
(18614) system(/usr/sap/XT1/SYS/exe/run/sapcpe pf=/usr/sap/XT1/SYS/profile/XT1_DVEBMGS00_exaservXT1) returns 1
(18619) Local: /usr/sap/XT1/DVEBMGS00/exe/sapmscsa pf=/usr/sap/XT1/SYS/profile/XT1_DVEBMGS00_exaservXT1 -n
/usr/sap/XT1/DVEBMGS00/exe/sapmscsa: SCSA is attached and useable.
/usr/sap/XT1/DVEBMGS00/exe/sapmscsa: finished.
(18620) Local: rm -f ms.sapXT1_DVEBMGS00
(18621) Local: ln -s -f /usr/sap/XT1/DVEBMGS00/exe/msg_server ms.sapXT1_DVEBMGS00
(18622) Local: rm -f dw.sapXT1_DVEBMGS00
(18623) Local: ln -s -f /usr/sap/XT1/DVEBMGS00/exe/disp+work dw.sapXT1_DVEBMGS00
(18624) Local: rm -f co.sapXT1_DVEBMGS00
(18625) Local: ln -s -f /usr/sap/XT1/DVEBMGS00/exe/rslgcoll co.sapXT1_DVEBMGS00
(18626) Local: rm -f se.sapXT1_DVEBMGS00
(18627) Local: ln -s -f /usr/sap/XT1/DVEBMGS00/exe/rslgsend se.sapXT1_DVEBMGS00
(18628) Local: rm -f ig.sapXT1_DVEBMGS00
(18629) Local: ln -s -f /usr/sap/XT1/DVEBMGS00/exe/igswd_mt ig.sapXT1_DVEBMGS00

Starting Programs
-----------------

07.07.2009 09:29:40
ShmDetach
OK
(18632) Starting: local ms.sapXT1_DVEBMGS00 pf=/usr/sap/XT1/SYS/profile/XT1_DVEBMGS00_exaservXT1
(18633) Starting: local dw.sapXT1_DVEBMGS00 pf=/usr/sap/XT1/SYS/profile/XT1_DVEBMGS00_exaservXT1
(18634) Starting: local co.sapXT1_DVEBMGS00 pf=/usr/sap/XT1/SYS/profile/XT1_DVEBMGS00_exaservXT1 -F
(18635) Starting: local se.sapXT1_DVEBMGS00 pf=/usr/sap/XT1/SYS/profile/XT1_DVEBMGS00_exaservXT1 -F
(18636) Starting: local ig.sapXT1_DVEBMGS00 -mode=profile pf=/usr/sap/XT1/SYS/profile/XT1_DVEBMGS00_exaservXT1
(18614) Waiting for Child Processes to terminate.
(18614) **** 2009/07/07 09:30:04 Child 18633 terminated with Status 0 . ****
 Instance on host exaservXT1 started



/usr/sap/XT1/DVEBMGS00/work/dev_w0


---------------------------------------------------
trc file: "dev_w0", trc level: 1, release: "700"
---------------------------------------------------
*
*  ACTIVE TRACE LEVEL           1
*  ACTIVE TRACE COMPONENTS      all, MJ
*
M sysno      00
M sid        XT1
M systemid   390 (AMD/Intel x86_64 with Linux)
M relno      7000
M patchlevel 0
M patchno    144
M intno      20050900
M make:      single threaded, Unicode, 64 bit, optimized
M pid        18643
M
M
M Tue Jul  7 09:29:41 2009
M  kernel runs with dp version 232000(ext=109000) (@(#) DPLIB-INT-VERSION-232000-UC)
M  length of sys_adm_ext is 576 bytes
M  ***LOG Q01=> ThInit, WPStart (Workproc 0 1 18643) [thxxhead.c   1281]
M  ThInit: running on host exaservXT1
M  calling db_connect ...
C
C  DBSDBSLIB : version 700.08, patch 0.144 (Make PL 0.144)
C  MAXDB shared library (dbsdbslib) patchlevels (last 10)
C    (0.144) MSSQL: ODBC fastload on separate connection (note 1131805)
C    (0.144) I5/OS ldappasswd support for 5250 terminal. (note 1129573)
C    (0.139) Return DS_SQLERR instead of DS_CONNECTERR (note 1121076)
C    (0.131) Do not trace password of SQLOPT into dev trace (note 1097930)
C    (0.130) Performance optimization for UPDSTAT PREPARE (note 1096387)
C    (0.125) Update statistic prepare on row level (note 1086430)
C    (0.104) Update statistic with empty schemas (note 1041547)
C    (0.095) MaxDB DBSL patch collection 1 2007 (note 1014270)
C    (0.082) MaxDB DBSL patch collection 3 2006 (note 991258)
C    (0.079) MaxDB DBSL patch collection 2 2006 (note 984406)
C
C
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.3    BUILD 009-123-163-622
C  SQLDBC client runtime is MaxDB 7.6.3.009 CL 163622
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  Attach to SAP DB : Kernel    7.6.03   Build 009-123-163-622
C  Database release is SAP DB 7.6.03.009
C  INFO : Database 'XT1' instance is running on 'exaservXT1'
C  INFO : SAP DB Packet_Size = 131072
C  INFO : SAP DB Min_Reply_Size = 4096
C  INFO : SAP DB Comm_Size = 126976
C  INFO : DBSL buffer size = 126976
C  INFO : SAP DB MaxLocks = 300000
C  INFO : Connect to DB as 'SAPXT1'
C  *** ERROR => the connected user (SAPXT1) does not work with the right user/schema
 [dbslsdb.cpp  4780]
C  *** ERROR => application has to work with schema SAPR3 (dbs/ada/schema)
 [dbslsdb.cpp  4782]
M  ***LOG R19=> ThInit, db_connect ( DB-Connect 000256) [thxxhead.c   1440]
M  in_ThErrHandle: 1
M  *** ERROR => ThInit: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c   10468]
M
M  Info for wp 0
M
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   724]
M  *** ERROR => ThCallHooks: event handler ThrSaveSPAFields for event BEFORE_DUMP failed [thxxtool3.c  261]
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 18643) [dpuxtool.c   260]

Show replies
Show replies
Answer

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
‎07-07-2009 2:42 PM
0 Kudos

I'm sorry for the formatting of the post. Is there a particular way to use the code and quote tags?

Show replies
Show replies
lbreddemann
Active Contributor
‎07-07-2009 3:14 PM
0 Kudos

Hi Zach,

> I'm sorry for the formatting of the post. Is there a particular way to use the code and quote tags?

Don't worry, you did it right. It's just that the formatting was turned off for posts exceeding 2500 characters.

Let's look at the error message:

C *** ERROR => the connected user (SAPXT1) does not work with the right user/schema [dbslsdb.cpp 4780] 
C *** ERROR => application has to work with schema SAPR3 (dbs/ada/schema) [dbslsdb.cpp 4782]

Well. appearently, the SAP profile parameter "dbs/ada/schema" says: "We use schema SAPR3", but the logon user (which equals the default schema for the NetWeaver work processes) is SAPXT1.

Obviously, the solution is: when your data is stored in the SAPXT1 schema, change the profile parameter, otherwise change the logon data (XUSER key DEFAULT).

best regards,

Lars

Former Member
‎07-07-2009 4:19 PM
0 Kudos

Thank you Lars,

Your post led me to the a solution. I checked out not only the startup profile but also the ?instance? profile. After comparing XT1's profile to another system in the landscape I found a discrepancy. Changing XT1's format to match the other system's format led to a successful connection.

Cheers,

Zach

Answers (0)

Ask a Question