on 06-20-2008 11:02 PM
For some reason my NSP server is starting with MMC, but then after about a minute it stops again. Please see the log files below. It seems to be a database problem but I don't know how to fix it...
dev_w0
---------------------------------------------------
trc file: "dev_w0", trc level: 1, release: "700"
---------------------------------------------------
*
* ACTIVE TRACE LEVEL 1
* ACTIVE TRACE COMPONENTS all, MJ
*
B
B Fri Jun 20 23:50:24 2008
B create_con (con_name=R/3)
B Loading DB library 'C:\usr\sap\NSP\DVEBMGS00\exe\dbsdbslib.dll' ...
B Library 'C:\usr\sap\NSP\DVEBMGS00\exe\dbsdbslib.dll' loaded
B Version of 'C:\usr\sap\NSP\DVEBMGS00\exe\dbsdbslib.dll' is "700.08", patchlevel (0.19)
B New connection 0 created
M sysno 00
M sid NSP
M systemid 560 (PC with Windows NT)
M relno 7000
M patchlevel 0
M patchno 23
M intno 20050900
M make: multithreaded, ASCII
M pid 4928
M
M kernel runs with dp version 202(ext=109) (@(#) DPLIB-INT-VERSION-202)
M length of sys_adm_ext is 360 bytes
M ***LOG Q0Q=> tskh_init, WPStart (Workproc 0 4928) [dpxxdisp.c 1288]
I MtxInit: 30000 0 0
M DpSysAdmExtCreate: ABAP is active
M DpSysAdmExtCreate: VMC (JAVA VM in WP) is not active
M DpShMCreate: sizeof(wp_adm) 5280 (880)
M DpShMCreate: sizeof(tm_adm) 3351072 (16672)
M DpShMCreate: sizeof(wp_ca_adm) 1200 (60)
M DpShMCreate: sizeof(appc_ca_adm) 1200 (60)
M DpCommTableSize: max/headSize/ftSize/tableSize=500/8/528040/528048
M DpShMCreate: sizeof(comm_adm) 528048 (1048)
M DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
M DpShMCreate: sizeof(file_adm) 0 (72)
M DpShMCreate: sizeof(vmc_adm) 0 (1076)
M DpShMCreate: sizeof(wall_adm) (22440/34344/56/100)
M DpShMCreate: sizeof(gw_adm) 48
M DpShMCreate: SHM_DP_ADM_KEY (addr: 04C80040, size: 3950264)
M DpShMCreate: allocated sys_adm at 04C80040
M DpShMCreate: allocated wp_adm at 04C81978
M DpShMCreate: allocated tm_adm_list at 04C82E18
M DpShMCreate: allocated tm_adm at 04C82E48
M DpShMCreate: allocated wp_ca_adm at 04FB5068
M DpShMCreate: allocated appc_ca_adm at 04FB5518
M DpShMCreate: allocated comm_adm at 04FB59C8
M DpShMCreate: system runs without file table
M DpShMCreate: allocated vmc_adm_list at 05036878
M DpShMCreate: allocated gw_adm at 050368B8
M DpShMCreate: system runs without vmc_adm
M DpShMCreate: allocated ca_info at 050368E8
M DpShMCreate: allocated wall_adm at 050368F0
Y *** ERROR => ztta/diag_area is 64000. [sapinit.c 325]
Y *** ERROR => ztta/diag_area adjusted to 128000 (minimum value). [sapinit.c 327]
Y *** ERROR => ztta/cua_area is 90000. [sapinit.c 963]
Y *** ERROR => ztta/cua_area adjusted to 250000. [sapinit.c 967]
X EmInit: MmSetImplementation( 2 ).
X MM diagnostic options set: 0
X <ES> client 0 initializing ....
X Using implementation flat
M <EsNT> Memory Reset disabled as NT default
X ES initialized.
M
M Fri Jun 20 23:50:25 2008
M ThInit: running on host PackardBell
M calling db_connect ...
C
C DBSDBSLIB : version 700.08, patch 0.019 (Make PL 0.23)
C MAXDB shared library (dbsdbslib) patchlevels (last 10)
C (0.019) UPDSTAT optimized (note 870327)
C (0.010) MaxDB DBSL patch collection 1 2005 (note 850830)
C (0.009) New stream compression available with LVC 7.6.0 b12 (note 835809)
C (0.008) Support of SDBUPDEXCL (note 847616)
C (0.005) Switch stream compression on/off (note 835809)
C (0.005) ITAB stream handling optimized (note 835809)
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.0 BUILD 018-123-113-357
C SQLDBC client runtime is MaxDB 7.6.0.018 CL 113357
C INFO : SQLOPT= -I 0 -t 0
C Try to connect (DEFAULT) on connection 0 ...
C *** ERROR => Connect to database failed, rc = -10757 (XUSER error (the USERKEY is unknown))
[dbsdbsql.cpp 98]
C Try to connect (SQLOPT) on connection 0 ...
C *** ERROR => Connect to database failed, rc = -10709 (Connection failed (RTE:Database name is missing))
[dbsdbsql.cpp 118]
B ***LOG BV3=> severe db error -10709 ; work process is stopped [dbsh#1 @ 1195] [dbsh 1195 ]
B ***LOG BY2=> sql error -10709 performing CON [dblink#3 @ 431] [dblink 0431 ]
B ***LOG BY0=> Connection failed (RTE:Database name is missing) [dblink#3 @ 431] [dblink 0431 ]
M ***LOG R19=> ThInit, db_connect ( DB-Connect 000256) [thxxhead.c 1391]
M in_ThErrHandle: 1
M *** ERROR => ThInit: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c 9995]
M
M Info for wp 0
M
M stat = 4
M reqtype = 1
M act_reqtype = -1
M rq_info = 0
M tid = -1
M mode = 255
M len = -1
M rq_id = 65535
M rq_source = 255
M last_tid = 0
M last_mode = 0
M semaphore = 0
M act_cs_count = 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 vm = V-1
M
M *****************************************************************************
M *
M * LOCATION SAP-Server PackardBell_NSP_00 on host PackardBell (wp 0)
M * ERROR ThInit: db_connect
M *
M * TIME Fri Jun 20 23:50:25 2008
M * RELEASE 700
M * COMPONENT Taskhandler
M * VERSION 1
M * RC 13
M * MODULE thxxhead.c
M * LINE 10180
M * COUNTER 1
M *
M *****************************************************************************
M
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 720]
M *** ERROR => ThCallHooks: event handler ThrSaveSPAFields for event BEFORE_DUMP failed [thxxtool3.c 260]
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 4928) [dpnttool.c 327]
Ok I eventually figured it out... The SAP Application Server starts the database using the XUSER authentication - For some reason my system lost all settings for this.
In order to recreate, I had to use the command prompt and use the XUSER command.
Firstly "XUSER LIST" lists all user keys - I had none.
I then needed to set the default XUSER:
XUSER -d NSP -u SAPNSP,<password>
<password> is the password for the user specified
Then I created the "c" key:
XUSER -d NSP -U c -u SAPNSP,<password>
The reason I set up the "c" XUSER is because I noticed that in "\usr\sap\NSP\DVEBMGS00\exe\" there is a batch file used to start the DB - "strdbs.cmd". Inside this file it uses "c" as the user key in order to set the state of the DB.
After all of that it worked again...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
76 | |
9 | |
8 | |
7 | |
6 | |
5 | |
5 | |
5 | |
5 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.