info command errors with "Unknown user name/password combination"

[Former Member]

Hi,

I have 2 new MaxDB installations on Linux, Rel. 7.8.02.28. If I connect as control user and run any info command (i.e. info state), the system throws "Unknown user name/password combination".

Systems with Rel. 7.8.02.27 don't show this behaviour. Is this a bug? Can anyone please check with the same version? Any hints to solve this?

dbmcli on IHP>user_getrights control serverrights

OK

UserMgm                 +       User management

InstallMgm              +       Installation management

SystemCmd               +       Execute operating system commands

DBFileRead              +       Database file access (read only)

AccessUtility           +       Access to utility session

Recovery                +       Restoring backups

Backup                  +       Saving backups

ParamFull               +       Parameter access (read and write)

ParamCheckWrite         +       Parameter access (checked write)

ParamRead               +       Parameter access (read only)

AccessSQL               +       Access to SQL session

ExecLoad                +       Execute the LOAD program

LoadSysTab              +       Load the system tables

DBStop                  +       Stop database instance

DBStart                 +       Start database instance

DBInfoRead              +       Request status data

SharedMemoryMgm         +       Shared memory management

SchedulerMgm            +       Scheduler management

Scheduling              +       Scheduler use

EvtDispMgm              +       Event Dispatcher management

EvtDisp                 +       Event Dispatcher use

dbmcli on IHP>user_name_get

OK

control

dbmcli on IHP>info state
ERR
-24988,ERR_SQL: SQL error
-4008,Unknown user name/password combination

Thanks a lot.

Best regards,

Dirk

[Former Member]

For all running into the same problem: The error occures, if you use a password for the affected user (control in my case), which has more then 8 characters.

Solution:

Use a shorter password.

[yashwanthkumar_kethineed]

Hi Dirk,

SAP MaxDB clients with software version < 7.8 can only handle users with a maximum password length of 9 characters. So if an old client software version is used in combination with a MaxDB version >= 7.8 the used passwords still can only have a length of 9 characters. Otherwise the old client won’t be able to connect to the database. Is this the same case in your situation ?

If not, MaxDB with version >=7.8 in your case should be able to handle upto 256 Characters. Refer to the link below for more information on this.

http://maxdb.sap.com/doc/7_8/44/c37584865960efe10000000a155369/content.htm

Also check this thread - MaxDB -7.7 - http://scn.sap.com/thread/1659482

Regards,

Yashwanth

[Former Member]

Hi Yashwanth,

this is just the theory. You may set dbm passwords larger then 8 characters, but you'll run into the described problem with this release (didn't try higher releases). The affected systems were freshly installed by sapinst and there's no other MaxDB installation on this host, a completely clean 7.8 installation.

I had an SAP call open and they experimented on our host until they found the problem.

Regards,

Dirk

[former_member229109]

Hello Dirk,

1. Please let me know the output of dbm command "user_get control".

2. How did you create this database?

3. If you had set the xuser entries correctly for OS user, then you could connect to the database using Xuser entries key after login to the server as this OS user.

4. Are you SAP customer?

Regards, Natalia Khlopina

[Former Member]

Hello Natalia,

1.

dbmcli on IHP>user_get control
OK
SERVERRIGHTS=UserMgm,InstallMgm,SystemCmd,DBFileRead,AccessUtility,Recovery,Backup,ParamFull,ParamCheckWrite,ParamRead,AccessSQL,ExecLoad,LoadSysTab,DBStop,DBStart,DBInfoRead,SharedMemoryMgm,SchedulerMgm,Scheduling,EvtDispMgm,EvtDisp
GUIRIGHTS=
SECONDPASSWORD=NO
DISABLED=NO
COMMENT=
USERTYPE=DBM
EXTERNAL_IDS=

---

2. I didn't create the database by myself, but it is an SAP Java system, so it should have been created by sapinst.

3.

kdejenl0011:sqdihp 946> dbmcli -U c

dbmcli on IHP>info infos
ERR
-24988,ERR_SQL: SQL error
-4008,Unknown user name/password combination

---

XUSER Entry  4

--------------

Key           :c

Username      :CONTROL

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

Password      :?????????

PasswordUCS2  :?????????

Long Password :?????????

Dbname        :IHP

Nodename      :<unspecified>

Sqlmode       :<unspecified>

Cachelimit    :-1

Timeout       :-1

Isolation     :-1

Charset       :<unspecified>

4. Yes, I opened a message, after I didn't get a solution here.

Thank you.

Best regards,

Dirk

[nelis]

Java Application servers are usually installed with a "c_J2EE" key for the control user, dual stack will have both a "c" and the "c_J2EE" key, a single Abap system will have only a "c" key. Does the "c_J2EE" key exist ?

--

Nelis

[Former Member]

Hi Nelis,

yes this key exists too, but I preferr "c", because it's shorter. I't doesn't make a difference, which key I use or if I logon as control without any key, the problem persists.

Thank you.

Best regards,

Dirk

[nelis]

Hi,

I don't get that error in 7.8.02.28 ...tested on two systems.

What happens if you use the control user key, do you get the same error ?

dbmcli -U c -d <DB> info state

Regards,

Nelis

[Former Member]

Hi Nelis,

that's what I've done. It doesn't make a difference, if I connect via xuser key or via user,password.

Thank you.

Best regards,

Dirk

[nelis]

Hi,

Then I'm not sure.

If nobody else replies with a solution I would try changing the password to see if it makes a difference. Notes 25591 and 39439 deal with this.

Regards,

Nelis