cancel
Showing results for 
Search instead for 
Did you mean: 

MaxDB login problem during installation

Former Member
0 Kudos

Hello!

When we are installing a second SAP ECC5.0 MaxDB75 Build 28 on a shared SLES8 server we got following login problem during ABAP-part of the database installation.

What user does R3Load rely on? We have considered all xuser entrys which is default and looks okay for me.

R3trans -d returns the same error message.

/sapmnt/TEP/exe/R3load: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#6 $ SAP

/sapmnt/TEP/exe/R3load: version R6.40/V1.4 [UNICODE]

/sapmnt/TEP/exe/R3load -dbcodepage 4103 -i /usr/sap/TEP/DB_inst/SAPPOOL.cmd -l /usr/sap/TEP/DB_inst/SAPPOOL.log -nolog

DbSl Trace: Connect to database failed : sqlcode=-4008 (Unknown user name/password combination)

(DB) ERROR: db_connect rc = 256

DbSl Trace: Connect to database failed : sqlcode=-4008 (Unknown user name/password combination)

Message was edited by: Fredrik Rosengren

Accepted Solutions (1)

Accepted Solutions (1)

roland_mallmann
Advisor
Advisor
0 Kudos

Hi,

can you show me the output of (using user '<sid>'adm):

xuser -list

Kind regards,

Roland

Former Member
0 Kudos

exts0020:tepadm 33> xuser list

-


XUSER Entry 1

-


Key :DEFAULT

Username :SAPTEP

UsernameUCS2:S.A.P.T.E.P. . . . . . . . . . . . . . . . . . . . . . . . . . .

Password :?????????

PasswordUCS2:?????????

Dbname :TEP

Nodename :exts0020

Sqlmode :SAPR3

Cachelimit :-1

Timeout

Isolation

Charset :<unspecified>

-


XUSER Entry 2

-


Key :c

Username :CONTROL

UsernameUCS2:C.O.N.T.R.O.L. . . . . . . . . . . . . . . . . . . . . . . . . .

Password :?????????

PasswordUCS2:?????????

Dbname :TEP

Nodename :exts0020

Sqlmode :<unspecified>

Cachelimit :-1

Timeout :-1

Isolation :-1

Charset :<unspecified>

-


XUSER Entry 3

-


Key :c_J2EE

Username :CONTROL

UsernameUCS2:C.O.N.T.R.O.L. . . . . . . . . . . . . . . . . . . . . . . . . .

Password :?????????

PasswordUCS2:?????????

Dbname :TEP

Nodename :exts0020

Sqlmode :<unspecified>

Cachelimit :-1

Timeout :-1

Isolation :-1

Charset :<unspecified>

-


XUSER Entry 4

-


Key :w

Username :SUPERDBA

UsernameUCS2:S.U.P.E.R.D.B.A. . . . . . . . . . . . . . . . . . . . . . . . .

Password :?????????

PasswordUCS2:?????????

Dbname :TEP

Nodename :exts0020

Sqlmode :<unspecified>

Cachelimit :-1

Timeout :-1

Isolation :-1

Charset :<unspecified>

exts0020:tepadm 34>

roland_mallmann
Advisor
Advisor
0 Kudos

Hi,

we need to find out which user is having the db_connect problem (error -4008). In order to identify the user, we would need to make a precompiler trace.

The most convenient way in this case would to set the SQLOPT environment variable for a certain shell (temporarily should be enough) to '-X –F <file_name>.pct'.

After setting the above environment variable, retry the 'R3trans -d' command. The <file_name>.pct file should then contain some more detailed information, including the username for which apparently the user/password combination is incorrect.

Regards,

Roland

Message was edited by: Roland Mallmann

Former Member
0 Kudos

exts0020:tepadm 53> more output.pct6.pct

<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body ><PRE><PLAINTEXT>

PRODUCT : SAP DB C-PreComp Runtime

DRIVER : /sapdb/programs/runtime/7403/lib/libpcr

WARNING : VERSIONS ARE DIFFERENT

PRECOMPILER : 7.4.3 005

LIBRARY : 7.4.3 039

BUILD : 039-121-092-249

version :P_1, P_2

SQL STATEMENT : FROM MODULE : dbadautl AT LINE : 644

Statement Name : :0x000010

OUTPUT : LZU : X32/LINUX 7.4.3 Build 039-121-092-249

OUTPUT : PCR : C-PreComp 7.4.3 Build 039-121-092-249

START : DATE : 2006-01-24 TIME : 0015:52:56

END : DATE : 2006-01-24 TIME : 0015:52:56

OPTION : PARSEINFOCACHE=OFF

SESSION : 1;

DATABASE : DB_000

USERKEY : DEFAULT

SQLMODE : SAPR3

SERVERDB : TEP

SERVERNODE: exts0020

CONNECT "SAPTEP " IDENTIFIED BY :A SQLMODE SAPR3 ISOLATION LEVEL 0

TIMEOUT 0

SQL STATEMENT : FROM MODULE : dbadautl AT LINE : 92

Statement Name : :0x000001

SQLCODE: -4008 Unknown user name/password combination

SQLERRD(INDEX_5) : 1 SEC. FOR STATEMENT

START : DATE : 2006-01-24 TIME : 0015:52:56

END : DATE : 2006-01-24 TIME : 0015:52:57

exts0020:tepadm 54>

roland_mallmann
Advisor
Advisor
0 Kudos

Hi again,

it seems the correct user is taken ('SAPTEP'), but maybe the password is incorrectly specified in the xuser data?

Can you try (and show me the output):

1a) dbmcli -d TEP -u control,<password>

1b) dbmcli -d TEP -u control,control -uSQL saptep,<password> sql_execute select * from dual

2a) dbmcli -d TEP -U c_J2EE

2b) dbmcli -d TEP -U c_J2EE -USQL DEFAULT sql_execute select * from dual

Please be specifically careful with upper- and lowercases.

Regards,

Roland

Message was edited by: Roland Mallmann

Former Member
0 Kudos

exts0020:tepadm 54> dbmcli -d TEP -u control,control

dbmcli on TEP>exit

OK

---

exts0020:tepadm 55> dbmcli -d TEP -u control,control -uSQL saptep,sap sql_execute select * from dual

ERR

-24988,ERR_SQL: sql error

-4008,Unknown user name/password combination

exts0020:tepadm 56>

exts0020:tepadm 57> dbmcli -d TEP -U c_J2EE

dbmcli on exts0020 : TEP>exit

OK

---

exts0020:tepadm 58> dbmcli -d TEP -U c_J2EE -USQL DEFAULT sql_execute select * from dual

ERR

-24988,ERR_SQL: sql error

-4008,Unknown user name/password combination

exts0020:tepadm 59>

roland_mallmann
Advisor
Advisor
0 Kudos

Good morning,

can you try:

dbmcli -d TEP -u control,control -uSQL <b>sapr3</b>,<password> sql_execute select * from dual

Former Member
0 Kudos

Good morning,

exts0020:tepadm 63> dbmcli -d TEP -u control,control -uSQL sapr3,sap sql_execute select * from dual

ERR

-24988,ERR_SQL: sql error

-4008,Unknown user name/password combination

exts0020:tepadm 64>

Regards,

Fredrik

roland_mallmann
Advisor
Advisor
0 Kudos

Ok ok,

then let's try:

dbmcli -d TEP -u control,control -uSQL superdba,admin sql_execute select * from users

Regards,

Roland

Former Member
0 Kudos

will not work either...

exts0020:tepadm 52> dbmcli -d TEP -u control,control -uSQL superdba,admin sql_execute select * from users

ERR

-24988,ERR_SQL: sql error

-4008,Unknown user name/password combination

exts0020:tepadm 53>

//Fredrik

Message was edited by: Fredrik Rosengren

roland_mallmann
Advisor
Advisor
0 Kudos

Ok, then:

dbmcli -d TEP -u control,control

Then, while <b>staying in the DBMCLI session</b>, issue:

dbmcli on TEP>sql_connect superdba,<password>

Please also try, should the above fail:

dbmcli -d TEP -u control,control user_getall

Message was edited by: Roland Mallmann

Former Member
0 Kudos

exts0020:tepadm 53> dbmcli -d TEP -u control,control

dbmcli on TEP>sql_connect superdba,sap

ERR

-24988,ERR_SQL: sql error

-4008,Unknown user name/password combination

---

dbmcli on TEP>exit

OK

---

exts0020:tepadm 54> dbmcli -d TEP -u control,control user_getall

OK

CONTROL

SUPERDBA

DOMAIN

exts0020:tepadm 55>

roland_mallmann
Advisor
Advisor
0 Kudos

The standard password for user 'superdba' is 'admin', please try that again:

exts0020:tepadm 53> dbmcli -d TEP -u control,control

dbmcli on TEP>sql_connect superdba,<b>admin</b>

---

The command 'user_getall' at least showed us that the name of the dba-user is indeed 'superdba'.

Former Member
0 Kudos

exts0020:tepadm 56> dbmcli -d TEP -u control,control

dbmcli on TEP>sql_connect superdba,admin

ERR

-24988,ERR_SQL: sql error

-4008,Unknown user name/password combination

---

dbmcli on TEP>

roland_mallmann
Advisor
Advisor
0 Kudos

Hi Fredrik,

do you remember if you gave the superdba user a specific password?

You could try 'secret' as its password once, but as I wrote before, 'admin' is the standard.

Regards,

Roland

Former Member
0 Kudos

Roland,

sdbverify reports "inconsistant packages", se below.

This might be the cause of our problem.

//Fredrik

exts0020:tepadm 54> sdbverify

Loader 7.5.00.28 32 bit in /sapdb/programs

-


check files... ok

check dependencies... ok

package data is consistent

Base 7.5.00.28 32 bit in /sapdb/programs

-


check files... failed

/sapdb/programs/bin/starter/sdbstarter not found

/sapdb/programs/bin/getdbroot was modified

check dependencies... ok

package data is inconsistent

Server Utilities 7.5.00.28 32 bit in /sapdb/programs

-


check files... failed

/sapdb/programs/pgm/starter/sdbstarter not found

check dependencies... ok

package data is inconsistent

JDBC 7.6.00.00 in /sapdb/programs

-


check files... ok

check dependencies... ok

package data is consistent

PCR 7300 7.3.00.53 in /sapdb/programs

-


check files... ok

check dependencies... ok

package data is consistent

PCR 7301 7.3.01.18 in /sapdb/programs

-


check files... ok

check dependencies... ok

package data is consistent

ODBC 7.5.00.28 32 bit in /sapdb/programs

-


check files... ok

check dependencies... ok

package data is consistent

DB Analyzer 7.5.00.28 32 bit in /sapdb/programs

-


check files... ok

check dependencies... ok

package data is consistent

PCR 7403 7.4.03.39 32 bit in /sapdb/programs

-


check files... ok

check dependencies... ok

check rte registration of package... ok

package data is consistent

PCR 7500 7.5.00.28 32 bit in /sapdb/programs

-


check files... ok

check dependencies... ok

check rte registration of package... ok

package data is consistent

Database Kernel 7.5.00.28 32 bit in /sapdb/TEP/db

-


check files... failed

/sapdb/TEP/db/pgm/starter/sdbstarter not found

check dependencies... ok

check rte registration of package... ok

package data is inconsistent

Database Kernel 7.5.00.28 32 bit in /sapdb/TEQ/db

-


check files... failed

/sapdb/TEQ/db/pgm/starter/sdbstarter not found

check dependencies... ok

check rte registration of package... ok

package data is inconsistent

VERIFICATION SUMMARY:

*********************

INVALID PACKAGES: 0

VALID PACKAGES: 12

INCONSISTENT PACKAGES: 4

TOTAL FILES: 451

MISSED FILES: 4

MODIFIED FILES: 1

FILES WITH MODIFIED PERMISSIONS: 0

exts0020:tepadm 55>

Former Member
0 Kudos

Sorry, above "inconsistant" problem was caused by running "sdbverify" as user "tepadm". When running as root I got all "packages consistant" reported.

//Fredrik

exts0020:~ # /sapdb/programs/bin/sdbverify

Loader 7.5.00.28 32 bit in /sapdb/programs

-


check files... ok

check dependencies... ok

package data is consistent

Base 7.5.00.28 32 bit in /sapdb/programs

-


check files... ok

check dependencies... ok

package data is consistent

Server Utilities 7.5.00.28 32 bit in /sapdb/programs

-


check files... ok

check dependencies... ok

package data is consistent

JDBC 7.6.00.00 in /sapdb/programs

-


check files... ok

check dependencies... ok

package data is consistent

PCR 7300 7.3.00.53 in /sapdb/programs

-


check files... ok

check dependencies... ok

package data is consistent

PCR 7301 7.3.01.18 in /sapdb/programs

-


check files... ok

check dependencies... ok

package data is consistent

ODBC 7.5.00.28 32 bit in /sapdb/programs

-


check files... ok

check dependencies... ok

package data is consistent

DB Analyzer 7.5.00.28 32 bit in /sapdb/programs

-


check files... ok

check dependencies... ok

package data is consistent

PCR 7403 7.4.03.39 32 bit in /sapdb/programs

-


check files... ok

check dependencies... ok

check rte registration of package... ok

package data is consistent

PCR 7500 7.5.00.28 32 bit in /sapdb/programs

-


check files... ok

check dependencies... ok

check rte registration of package... ok

package data is consistent

Database Kernel 7.5.00.28 32 bit in /sapdb/TEP/db

-


check files... ok

check dependencies... ok

check rte registration of package... ok

package data is consistent

Database Kernel 7.5.00.28 32 bit in /sapdb/TEQ/db

-


check files... ok

check dependencies... ok

check rte registration of package... ok

package data is consistent

VERIFICATION SUMMARY:

*********************

INVALID PACKAGES: 0

VALID PACKAGES: 12

INCONSISTENT PACKAGES: 0

TOTAL FILES: 451

MISSED FILES: 0

MODIFIED FILES: 0

FILES WITH MODIFIED PERMISSIONS: 0

exts0020:~ #

Former Member
0 Kudos

Roland,

"superdba,admin" works for login, but not in a "-uSQL" statement.

Se below, this means that superdba really still got the default "admin"-password.

//Fredrik

exts0020:tepadm 51> dbmcli -d TEP -u superdba,dummy

Error! Connection failed to node (local) for database TEP: ERR_USRFAIL: user authorization failed

exts0020:tepadm 52>

exts0020:tepadm 61> dbmcli -d TEP -u superdba,admin

dbmcli on TEP>exit

OK

---

exts0020:tepadm 62> dbmcli -d TEP -u control,control -uSQL superdba,admin sql_execute select * from dual

ERR

-24988,ERR_SQL: sql error

-4008,Unknown user name/password combination

exts0020:tepadm 63>

roland_mallmann
Advisor
Advisor
0 Kudos

Ok, then try:

1a. dbmcli -d TEP -u control,control

<stay in the dbmcli-session>

1b. dbmcli on TEP>sql_execute select * from users

---

1a. dbmcli -d TEP -u superdba,admin

<stay in the dbmcli-session>

1b. dbmcli on TEP>sql_execute select * from users

Former Member
0 Kudos

Now the installation is running again! I have to look in log files tomorrow to find any information of what cause the problem?? What different db_state must one consider installing/working with maxDB?

roland_mallmann
Advisor
Advisor
0 Kudos

Hi Fredrik,

I'm as flabbergasted as you are. Did you change anything prior to the reinstall attempt at all?

I was going to recommend creating new UPC-files, but it seems your issue has been solved another way?

Please let me know what you find.

Regards,

Roland

Answers (0)