please try to run
dbmcli -d xxx -u control,<pw> user_sysdba superdba
first and afterwards the load_systab.
regards,
Lars
Hello Christian,
You will get the error "-24907,ERR_DBAWRONG: wrong SYSDBA", if you loaded the system tables with the wrong password of SYSDBA user.
Try "sql_connect superdba,<passwd> " to check if the password is correct or not.
Thank you and best regards, Natalia Khlopina
Hello Lars, hello Natalia,
both suggestions did not work:
dbmcli -d XXX -u control,<pwd> user_sysdba superdba
gave me a
ERR
-24996,ERR_PARAM: wrong parameters
sql_connect superdba,admin
gave me a
ERR
-24988,ERR_SQL: SQL error
-4008,Unknown user name/password combination
so I tried
user_put superdba password=<pass>
ERR
-24907,ERR_DBAWRONG: wrong SYSDBA
But note 25591 - Changing the DBM, SYSDBA and DBA user passwords mentiones, that:
The SYSDBA is the user with the most privileges in the database. This user is specified when the database is activated. util_activate superdba,admin (SAP DB Versions 7.3/7.4) db_activate superdba,admin (MaxDB Versions >= 7.5)
So I did a
db_admin
db_activate superdba,<pass>
OK
sql_connect superdba,<pass>
OK
load_systab -u superdba,<pass> -ud domain
OK
...
Installation successfully finished
Thank you very much for your help.
Best regards
Christian
> So I did a
> db_admin
> db_activate superdba,<pass>
> OK
> sql_connect superdba,<pass>
> OK
> load_systab -u superdba,<pass> -ud domain
> OK
> ...
> Installation successfully finished
>
> Thank you very much for your help.
>
Hmmm.... I hope there had not been any user data in that db before, because it would be gone by now.
regards,
Lars
Hello,
1. "dbmcli -d XXX -u control,<pwd> user_sysdba superdba"
See syntax/document at http://maxdb.sap.com/doc/7_7/45/1befa8be505d7be10000000a11466f/content.htm
But it will not help with reported error.
2. "sql_connect superdba,admin
gave me a
ERR
-24988,ERR_SQL: SQL error
-4008,Unknown user name/password combination"
Exactly, what I wrote, that you got the error during the loading system tables, because you used the wrong password.
Example on the local server:
dbmcli -d NLK -u control,test
dbmcli on NLK>sql_connect superdba,test
OK
dbmcli on NLK>sql_release
OK
dbmcli on NLK>load_systab -u superdba,admin
ERR
-24907,ERR_DBAWRONG: wrong SYSDBA
dbmcli on NLK>load_systab -u superdba,test
u2026 done.
3. "so I tried
user_put superdba password=<pass>
ERR
-24907,ERR_DBAWRONG: wrong SYSDBA"
The Sap note 25591 gave the correct procedure to change the sysdba password.
< read the section "3. Changing the password for the SYSDBA user "!>
You could not use the dbm command user_put to change the SYSDBA user password.
4. As you are running the database installation, you could run "db_activate superdba,<pass>" to initialize the database again. At that time you know the password of the superdba user. But the database is initialized, so don't use this option when you will have application data in the database!
The database was already online, when you posted this question on forum.
What password did you select for SYSDBA (UserDatabase System Administrator) during installation?
Are you running new installation?
The XCMDOUT.log need to be checked.
Thank you and best regards, Natalia Khlopina
Hi Natalia,
I am doing a homogenous systemcopy, using backup restore.
I am sorry, but I can't get the difference between
The Sap note 25591 gave the correct procedure to change the sysdba password.
< read the section "3. Changing the password for the SYSDBA user "!>
and:
You could not use the dbm command user_put to change the SYSDBA user password.
Best regards
Christian
Hello Christian,
1. "The Sap note 25591 gave the correct procedure to change the sysdba password.
< read the section "3. Changing the password for the SYSDBA user "!>"
As it was written in the note, to change the SYSDBA user password the database has to be online,
then you need to connect to the database as SYSDBA user & change the password with the
given SQL statement. After the password is changed & you could connect to the database as
SYSDBA user with the new password, you could adjust the UPC containers with new password
of the SYSDBA user.
You could reload the system tables or run the dbm command 'user_sysdba superdba,<new-pwd>'.
Read the document at MaxDB library: http://maxdb.sap.com/doc/7_6/default.htm
-> Basic Information -> MaxDB Security Guide -> User Administration and Authentication ->
Changing the Passwords of Standard Users
"ALTER PASSWORD" statement => see documentation in
"SQL Statements: Overview" in "SQL Reference Manual"
at MAXDB library: http://maxdb.sap.com/doc/7_6/default.htm
see the documentation on dbm command user_put from the list of
"Overview of All DBM Commands" at
MaxDB library: http://maxdb.sap.com/doc/7_6/default.htm -> Tools -> Database Manager CLI
2. "a homogenous systemcopy"
Please review the SAP notes SAP Note No. 129352 2C & SAP Note No. 1090087.
The loading system tables in the target database copy should work with the SYSDBA
user & password of the sysdba user in source database.
Do you know the password of the SYSDBA user in the source database?
I recommend to create the SAP ticket, if you will need SAP support further.
Thank you and best regards, Natalia Khlopina
Hello Christian,
1. "The Sap note 25591 gave the correct procedure to change the sysdba password.
< read the section "3. Changing the password for the SYSDBA user "!>"
As it was written in the note, to change the SYSDBA user password the database has to be online,
then you need to connect to the database as SYSDBA user & change the password with the
given SQL statement. After the password is changed & you could connect to the database as
SYSDBA user with the new password, you could adjust the UPC containers with new password
of the SYSDBA user, you could reload the system tables or run the dbm command
'user_sysdba superdba,<new-pwd>'.
Read the document at MaxDB library: http://maxdb.sap.com/doc/7_6/default.htm
-> Basic Information -> MaxDB Security Guide -> User Administration and Authentication ->
Changing the Passwords of Standard Users
"ALTER PASSWORD" statement => see documentation in
"SQL Statements: Overview" in "SQL Reference Manual"
at MAXDB library: http://maxdb.sap.com/doc/7_6/default.htm
see the documentation on dbm command user_put from the list of
"Overview of All DBM Commands" at
MaxDB library: http://maxdb.sap.com/doc/7_6/default.htm -> Tools -> Database Manager CLI
2. "a homogenous systemcopy"
Please review the SAP notes SAP Note No. 129352 2C & SAP Note No. 1090087.
The loading system tables in the target database copy should work with the SYSDBA
user & password of the sysdba user in source database.
Do you know the password of the SYSDBA user in the source database?
I recommend to create the SAP ticket, if you will need SAP support further.
Thank you and best regards, Natalia Khlopina
Hi Natalia,
I called our outsourcer to get the correct password, and laoding systabs worked.
Thats what I mean when I said that loading the systabs with the correct password ist fun, because it works! 
Many thanks
Christian
Sorry, was quiet late last night.
There was data in the database, now it is gone .. I am trying a recovery with initialisation...
Best regards
Christian
Hi,
I called our outsourcing partnerto request the password.
load_systab is really fun using the correct password ....
Thank you.
But, is there no way to reset this when it is unknown?
i.e I saw the feature to set a second password for the DBM operators in DBMGui which does not work because of wrong first password....
Best regards
Christian
> load_systab is really fun using the correct password ....
Well, it usually works without problems - but I wouldn't call that 'fun'...
> But, is there no way to reset this when it is unknown?
Unfortunately not.
> i.e I saw the feature to set a second password for the DBM operators in DBMGui which does not work because of wrong first password....
Hmm... yes you might use the feature, but:
- there's no frontend part for it in DB Studio
- you have to assign the 2nd password in advance
- you have to remember the 2nd password.
If you think about it, that's not really an advantage to having just one password.
best regards,
Lars
