Unable to login SAP installation stopped at ddic ...

Hi,

we are installing SAP PRD server on RHEL 5 from system copy export of dev (EHP4). now we are at ddic check password step .

when we try to logon at sap , very very long time it shown logon screen. but unable to logon through sap*.

we have done the following

#su dbuser

$sqlcli -U DEFAULT

sqlcli> delete from SAPPRD.usr02 where bname = 'SAP*' and mandt=000

where sapprd is my schema name.

we start sap it shows successfully started, but when we try to logon it immediatly return error.

Error: partner 'IP:3200' not reached
Wed May 25 18:54:21 2011
Release 720
Component NI (network interface), version 40
rc = -10, module nixxi.cpp, line 3286
Detail NiPConnect2: IP:3200
System Call connect
Error No 10061
'WSAECONNREFUSED: Connection refused

Please Guide

Best Regards

Khan

SAP Managed Tags:
SAP MaxDB

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (0)

Answers (1)

Your system doesn't seem to be started completely.

Please check

dev_w0

in /usr/sap/<SID>/DVEBMGS00/work

Markus

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

---------------------------------------------------
trc file: "dev_w0", trc level: 1, release: "701"
---------------------------------------------------
*
*  ACTIVE TRACE LEVEL           1
*  ACTIVE TRACE COMPONENTS      all, MJ
*
M sysno      00
M sid        PRD
M systemid   390 (AMD/Intel x86_64 with Linux)
M relno      7010
M patchlevel 0
M patchno    32
M intno      20020600
M make:      single threaded, Unicode, 64 bit, optimized
M pid        6989
M 
M  
M Wed May 25 11:06:40 2011
M  kernel runs with dp version 241000(ext=110000) (@(#) DPLIB-INT-VERSION-241000-UC)
M  length of sys_adm_ext is 576 bytes
M  ***LOG Q01=> ThInit, WPStart (Workproc 0 1 6989) [thxxhead.c   1290]
M  ThInit: running on host prdsap
M  calling db_connect ...
C  
C  DBSDBSLIB : version 700.08, patch 0.024 (Make PL 0.32)
C  MAXDB shared library (dbsdbslib) patchlevels (last 10)
C    (0.024) Default value for max. input variables is 2000 (note 655018)
C    (0.024) Profile parameter to define max. input variables (note 655018)
C    (0.024) Switch SQLMODE after CREATE INDEX SERIAL (note 1267841)
C    (0.024) Input parameters for SQL statements increased (note 655018)
C    (0.018) Create index serial for MaxDB 7.6 (note 1267841)
C    (0.018) More trace in case of packed to string conversion error (note 1262799)
C    (0.016) R3trans export aborts with signal 6 (note 1262245)
C    (0.007) Support DB-Type 'SAP DB' by UPDSTAT (note 1225668)
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.5    BUILD 015-123-202-938
C  SQLDBC client runtime is MaxDB 7.6.5.015 CL 202938
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  
C Wed May 25 11:06:44 2011
C  *** ERROR => Connect to database failed, rc = -4008 (POS(1) Unknown user name/password combination)
 [dbsdbsql.cpp 137]
B  ***LOG BY2=> sql error -4008  performing CON [dbsh#2 @ 1208] [dbsh    1208 ]
B  ***LOG BY0=> POS(1) Unknown user name/password combination [dbsh#2 @ 1208] [dbsh    1208 ]
B  ***LOG BY2=> sql error -4008  performing CON [dblink#3 @ 431] [dblink  0431 ]
B  ***LOG BY0=> POS(1) Unknown user name/password combination [dblink#3 @ 431] [dblink  0431 ]
M  ***LOG R19=> ThInit, db_connect ( DB-Connect 000256) [thxxhead.c   1449]
M  in_ThErrHandle: 1
M  *** ERROR => ThInit: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c   10563]
M  
M  Info for wp 0
M  
M    pid = 6989
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   723]
M  *** ERROR => ThCallHooks: event handler ThrSaveSPAFields for event BEFORE_DUMP failed [thxxtool3.c  261]
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 6989) [dpuxtool.c   269]

> C  *** ERROR => Connect to database failed, rc = -4008 (POS(1) Unknown user name/password combination)
>  [dbsdbsql.cpp 137]
> B  ***LOG BY2=> sql error -4008  performing CON [dbsh#2 @ 1208] [dbsh    1208 ]
> B  ***LOG BY0=> POS(1) Unknown user name/password combination [dbsh#2 @ 1208] [dbsh    1208 ]
> B  ***LOG BY2=> sql error -4008  performing CON [dblink#3 @ 431] [dblink  0431 ]
> B  ***LOG BY0=> POS(1) Unknown user name/password combination [dblink#3 @ 431] [dblink  0431 ]
> M  ***LOG R19=> ThInit, db_connect ( DB-Connect 000256) [thxxhead.c   1449]

As you can see the workprocesses can't connect to the database.

You have to adapt the xuser data for <sid>adm:

x_user -U DEFAULT -u <schemauser>,<password> -d <SID> -n <hostname> set

Then try to do an "R3trans -d". If that comes back with 0000 you can start the instance.

Be aware that all background jobs will start automatically as on the original system. If there are any connected systems like a BW or SRM or CRM they will be populated with the data - which you don't want.

Markus

hi master,

we logon as prdadm

prdsap:prdadm 2> x_user -U DEFAULT -u sapprd,passwd -d prd -n prdsap set
x_user: Permission denied.

prdsap:prdadm 2> x_user -U DEFAULT -u sapprd,passwd -d prd -n prdsap set
> x_user: Permission denied.

Did you install the software using sapinst or did you do some "cloning"?

Markus

master,

one thing we note that when we start or stop sap, log files (dev_w0, dev_ms, dev_disp) are update, these are showing old values. like in dev_w0 shows 11:07 AM time , while here current time is 5:55 PM. during these timing we have number of time stop & start SAP.

Yes install sap using sapinst , but through system copy using export of dev (EHP4)

> Yes install sap using sapinst , but through system copy using export of dev (EHP4)

that's interesting - somethign seems to be messed up with permissions for the user...

try to

usermod -A sdba <sid>adm
chmod 600 .XUSER.62

then try to execute xuser again.

Markus

SIDadm

prdsap:prdadm 2> usermod -A sdba prdadm 
usermod: Permission denied.

prdsap:prdadm 3> exit

exit

root

[root@prdsap ~]# usermod -A sdba prdadm
usermod: invalid option -- A

[root@prdsap ~]# chmod 600 .XUSER.62
chmod: cannot access `.XUSER.62': No such file or directory

[root@prdsap ~]# usermod -A sdba prdadm
> usermod: invalid option -- A

so your usermod doesn't understand "-A" - please check "man usermod" how to add prdadm to group sdba.

[root@prdsap ~]# chmod 600 .XUSER.62
> chmod: cannot access `.XUSER.62': No such file or directory

This file is user dependent - so try as <sid>adm

Markus

[root@prdsap ~]# usermod -a sdba prdadm

Usage: usermod [options] LOGIN

Options:
  -a, --append                  append the user to the supplemental GROUPS
                                (use only with -G)
  -c, --comment COMMENT         new value of the GECOS field
  -d, --home HOME_DIR           new home directory for the user account
  -e, --expiredate EXPIRE_DATE  set account expiration date to EXPIRE_DATE
  -f, --inactive INACTIVE       set password inactive after expiration
                                to INACTIVE
  -g, --gid GROUP               force use GROUP as new primary group
  -G, --groups GROUPS           new list of supplementary GROUPS
  -h, --help                    display this help message and exit
  -l, --login NEW_LOGIN         new value of the login name
  -L, --lock                    lock the user account
  -m, --move-home               move contents of the home directory to the new
                                location (use only with -d)
  -o, --non-unique              allow using duplicate (non-unique) UID
  -p, --password PASSWORD       use encrypted password for the new password
  -s, --shell SHELL             new login shell for the user account
  -u, --uid UID                 new UID for the user account
  -U, --unlock                  unlock the user account
  -Z, --selinux-user    new selinux user mapping for the user account

prdsap:prdadm 1> chmod 600 .Xuser.62
chmod: cannot access `.Xuser.62': Permission denied
prdsap:prdadm 2>

[root@prdsap ~]# usermod -G sdba prdadm
[root@prdsap ~]# su prdadm
prdsap:prdadm 1> chmod 600 .XUSER.62
chmod: cannot access `.XUSER.62': Permission denied
prdsap:prdadm 2>

master,

[root@prdsap ~]# usermod -G sdba prdadm
> [root@prdsap ~]# su prdadm
> prdsap:prdadm 1> chmod 600 .XUSER.62
> chmod: cannot access `.XUSER.62': Permission denied
> prdsap:prdadm 2>

Try to do the chmod as user "root" in /home/prdadm

Markus

> one thing we note that when we start or stop sap, log files (dev_w0, dev_ms, dev_disp) are update, these are showing old values. like in dev_w0 shows 11:07 AM time , while here current time is 5:55 PM. during these timing we have number of time stop & start SAP.

There seemst to be something wrong with your permissions in that system.

Markus

[root@prdsap ~]# cd /home/prdadm/
[root@prdsap prdadm]# chmod 600 .XUSER.62
[root@prdsap prdadm]# su prdadm
prdsap:prdadm 1> x_user -U DEFAULT -u control,Sap00Prd -d prd -n prdsap set
x_user: Command not found.
prdsap:prdadm 2>

master,

every thing was working fine, sap was starting and stoping fine also it shows logon screen, but it was taking time to show it.

after this command

#su dbuser
$sqlcli -U DEFAULT
sqlcli> delete from SAPPRD.usr02 where bname = 'SAP*' and mandt=000
where sapprd is my schema name.

every thing is disturbe.

Please guide what wrong with this command.

Best Regrads

Imran

Hello,

1. Let us know why you are running this command?

2. If you want the SAP* user to be initial again => create the SAP message to the BC-SEC component!

Let us know the verion of your system and the version of the database.

Regards, Natalia Khlopina

Edited by: Natalia Khlopina on May 27, 2011 6:06 PM

hi master ,

please guide , how can we check permission .

Best regards

khan

Hello Khan,

What is the current status of the problems on your system?

What error did you get?

Did you create the SAP message where the issues in this thread were reported?

Is your system ID PRD?

Do you have file .XUSER.62 in the $HOME directory of the prdadm user on the application server?

xuser -h

xuser list

ls -l $HOME/.XUSER.62

Please review the SAP Note No. 39439.

Regards, Natalia Khlopina

Thanks ,

when we startsap it says that,

[root@prdsap ~]# su - prdadm
prdsap:prdadm 1> startsap

Checking ADA db Database
------------------------------
 Database is not available via R3trans
 Running /usr/sap/PRD/SYS/exe/run/startdb 
Trying to start database ...
Log file: /home/prdadm/startdb.log
PRD database started
 /usr/sap/PRD/SYS/exe/run/startdb completed successfully 

Starting Startup Agent sapstartsrv
-----------------------------
 Instance Service on host prdsap started

My server SID is PRD, it home Dir contains

[root@prdsap prdadm]# ls -la .XUSER.62 
-rw------- 1 prdadm sapsys 1724 May 25 07:51 .XUSER.62

prdsap:prdadm 2> xuser -h
Syntax: xuser [{options}] [action]
xuser     7.7.06   Build 010-123-204-327 (record format version: 3)
Usage: List, clear or setup user specific connection information
Description: This tool is used to predefine and manage default values
             for user data and connection options. Every data set
             is stored with an XUSER key. When connecting to the
             database without specifying an XUSER key, the key DEFAULT
             is used. Additionally specified command line options
             override the XUSER data.
Options:
    -h show long helptext
    -V           show version of XUSER program
    -A ASCII8    interpret environment and batchfiles as pure ASCII8
    -b file      set user information via batch file
                 The batch file format is analogous to the way you enter
                 options and commands on the command line. Each line in
                 the batch file must contain an option list followed by
                 a command. The lines are processed in the order they
                 occur in the batch file. You can mix 'set' and 'clear'
                 commands in one batch file. You can't use the 'list'
                 command or the option -b. If an error occurs, the batch
                 execution stops at the respective line of the batch file.
       string (no restriction to the length), default '' = current user
    -U user_key           user key
       string (max. 18 characters), default 'DEFAULT'
    -u user_name,password user name/password combination
       2 strings (max. 18 characters), default '',''
    -d database_name      database name to connect to
       string (max. 18 character), default ''
    -n database_server    database server name
       string (max. 64 characters), default '' = local server
    -e encryption         Encryption type valid encryption types
                          are 'SSL'
    -S SQL_mode           SQL mode
       string (max. 8 characters), default ''
       valid modes are 'SAPDB', 'INTERNAL', 'ANSI',
                       'DB2', 'ORACLE' and 'SAPR3'
    -t timeout            connection timeout in seconds
       number (default -1 = default timeout value set in the database
                        0 = no timeout)
    -I isolation_level    isolation level
       number (default -1, valid values are -1,0,1,2,3,9,10,15,20,30)
  The following actions are defined (must always be the LAST argument):
   list    list user connection information (default all user keys)
           ignores all options, except -U
   clear   clear user connection information (default all user keys)
           ignores all options, except -U
   set     (default) set user information

prdsap:prdadm 4> xuser list
-----------------------------------------------------------------
XUSER Entry  1
--------------
Key         :DEFAULT           
Username    :CONTROL                                                         
UsernameUCS2:C.O.N.T.R.O.L. . . . . . . . . . . . . . . . . . . . . . . . . .
Password    :?????????
PasswordUCS2:?????????
Dbname      :prd               
Nodename    :prdsap                                                          
Sqlmode     :<unspecified>
Cachelimit  :-1
Timeout     :-1
Isolation   :-1
Charset     :<unspecified>     
-----------------------------------------------------------------
XUSER Entry  2
--------------
Key         :c                 
Username    :CONTROL                                                         
UsernameUCS2:C.O.N.T.R.O.L. . . . . . . . . . . . . . . . . . . . . . . . . .
Password    :?????????
PasswordUCS2:?????????
Dbname      :PRD               
Nodename    :prdsap                                                          
Sqlmode     :SAPR3   
Cachelimit  :-1
Timeout     :0
Isolation   :0
Charset     :<unspecified>     
-----------------------------------------------------------------
XUSER Entry  3
--------------
Key         :c_J2EE            
Username    :CONTROL                                                         
UsernameUCS2:C.O.N.T.R.O.L. . . . . . . . . . . . . . . . . . . . . . . . . .
Password    :?????????
PasswordUCS2:?????????
Dbname      :PRD               
Nodename    :prdsap                                                          
Sqlmode     :SAPR3   
Cachelimit  :-1
Timeout     :0
Isolation   :0
Charset     :<unspecified>     
-----------------------------------------------------------------
XUSER Entry  4
--------------
Key         :w                 
Username    :SUPERDBA                                                        
UsernameUCS2:S.U.P.E.R.D.B.A. . . . . . . . . . . . . . . . . . . . . . . . .
Password    :?????????
PasswordUCS2:?????????
Dbname      :PRD               
Nodename    :prdsap                                                          
Sqlmode     :SAPR3   
Cachelimit  :-1
Timeout     :0
Isolation   :0
Charset     :<unspecified>

according to SAP note 39439

prdsap:prdadm 7> xuser -U DEFAULT -u sapprd,sappasswd -d prd -n prdsap -S SAPR3 -t 0 -I 0 set
prdsap:prdadm 8> R3trans -d
This is R3trans version 6.14 (release 701 - 26.01.09 - 12:46:00).
unicode enabled version
R3trans finished (0000).
prdsap:prdadm 9>

prdsap:prdadm 10> startsap all

Checking ADA db Database
------------------------------
 Database is not available via R3trans
 Running /usr/sap/PRD/SYS/exe/run/startdb 
Trying to start database ...
Log file: /home/prdadm/startdb.log
PRD database started
 /usr/sap/PRD/SYS/exe/run/startdb completed successfully

when ary to logon through SAP GUI it says wait for response

dev_disp.log

Wed Jun 1 12:18:56 2011

ERROR => DpWPCheck: W9 (pid 9283) died (severity=0, status=0) [dpxxdisp.c 15662]
ERROR => DpWPCheck: W11 (pid 9284) died (severity=0, status=0) [dpxxdisp.c 15662]
ERROR => DpWPCheck: W12 (pid 9285) died (severity=0, status=0) [dpxxdisp.c 15662]
ERROR => DpWPCheck: W13 (pid 9286) died (severity=0, status=0) [dpxxdisp.c 15662]
ERROR => DpWPCheck: W14 (pid 9287) died (severity=0, status=0) [dpxxdisp.c 15662]
ERROR => DpWPCheck: W15 (pid 9288) died (severity=0, status=0) [dpxxdisp.c 15662]
ERROR => DpWPCheck: W16 (pid 9289) died (severity=0, status=0) [dpxxdisp.c 15662]

DEV_DISP

ES> client 0 initializing ....
<ES> InitFreeList
<ES> block size is 4096 kByte.
Using implementation map
<EsMap> EsMapUnamFileMapInit: Initialize the memory 10224 MB
Linux: Kernel supports shared memory disclaiming
Linux: using madvise(<pointer>, <size>, 9).
Linux: disclaiming for shared memory enabled
<ES> 2552 blocks reserved for free list.
ES initialized.
rdisp/http_min_wait_dia_wp : 1 -> 1
***LOG CPS=> DpLoopInit, ICU ( 3.0 3.0 4.0.1) [dpxxdisp.c   1681]
***LOG Q0K=> DpMsAttach, mscon ( prdsap) [dpxxdisp.c   12483]
DpStartStopMsg: send start message (myname is >prdsap_PRD_00                           <)
DpStartStopMsg: start msg sent
CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
CCMS: start to initalize 3.X shared alert area (first segment).
DpMsgAdmin: Set release to 7010, patchlevel 0
MBUF state PREPARED
MBUF component UP
DpMBufHwIdSet: set Hardware-ID
***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c   1048]
DpMsgAdmin: Set patchno for this platform to 32
Release check o.K.

Thu Jun  2 15:39:37 2011
*** ERROR => DpWPCheck: W9 (pid 12188) died (severity=0, status=65280) [dpxxdisp.c   15662]
child (pid=12188) exited with exit code 255
my types changed after wp death/restart 0xbf --> 0x89
*** ERROR => DpWPCheck: W10 (pid 12189) died (severity=0, status=65280) [dpxxdisp.c   15662]

DEV_W0

 INFO : SAP DB Comm_Size = 126976
C  INFO : DBSL buffer size = 126976
C  INFO : SAP DB MaxLocks = 300000
C  INFO : Connect to DB as 'SAPPRD'
C  Command info enabled
C  Now I'm connected to SAP DB
C  00: prdsap-PRD, since=20110602153859, ABAP= <unknown> (0)
B  Connection 0 opened (DBSL handle 0)
B  Wp  Hdl ConName          ConId     ConState     TX  PRM RCT TIM MAX OPT Date     Time   DBHost          
B  000 000 R/3              000000000 ACTIVE       NO  YES NO  000 255 255 20110602 153859 prdsap          
C  INFO : SAP RELEASE (DB) = 701
M  db_connect o.k.
M  ICT: exclude compression: *.zip,*.cs,*.rar,*.arj,*.z,*.gz,*.tar,*.lzh,*.cab,*.hqx,*.ace,*.jar,*.ear,*.war,*.css,*.pdf,*.js,*.gzip,*.uue,*.bz2,*.iso,*.sda,*.sar,*.gif,*.swc,*.swf
I  
I Thu Jun  2 15:40:14 2011
I  MtxInit: 0 0 0
M  SHM_PRES_BUF			(addr: 0x2add60a3b000, size: 4400000)
M  SHM_ROLL_AREA		(addr: 0x2ade75244000, size: 1073741824)
M  SHM_PAGING_AREA		(addr: 0x2adeb5244000, size: 536870912)
M  SHM_ROLL_ADM			(addr: 0x2add60e6f000, size: 10683916)
M  SHM_PAGING_ADM		(addr: 0x2aded5244000, size: 2622496)
M  ThCreateNoBuffer		allocated 560152 bytes for 1000 entries at 0x2aded54c7000
M  ThCreateNoBuffer		index size: 3000 elems
M  ThCreateVBAdm		allocated 12176 bytes (50 server) at 0x2adedbf95000
X  EmInit: MmSetImplementation( 2 ).
X  MM global diagnostic options set: 0
X  <ES> client 0 initializing ....
X  Using implementation map
X  Linux: Kernel supports shared memory disclaiming
X  Linux: using madvise(<pointer>, <size>, 9).
X  Linux: disclaiming for shared memory enabled
X  ES initialized.
B  dbntab: NTAB buffers attached
B  dbntab: Buffer FTAB(hash header)  (addr: 0x2aded5551088, size: 584)
B  dbntab: Buffer FTAB(anchor array) (addr: 0x2aded55512d0, size: 320072)
B  dbntab: Buffer FTAB(item array)   (addr: 0x2aded559f518, size: 1280000)

Dear Mr. Khan,

I gave you answer on the question "please guide , how can we check permission", so you used the xuser tool < NOT x_user, which gave you "permission" issue in question >. No according the last post the connection to the DB is OK.

So close this thread & open another one to help you with WP are died dispetcher < SAP kernel > issue.

Please post the question with dev log of disp to the "SAP kernel" forum.

If you are SAP customer => create the SAP message to BC-INS component & get SAP support.

Regards, Natalia Khlopina

Ask a Question

Top Q&A Solution Author

User

Count