Unable to login SAP installation stopped at ddic check password step

Question

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

Answer 1

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>