Wrong SYSDBA Error -24908

[Former Member]

Greetings,

We are having a problem with SAPDB that I am not able to solve. We restored a full backup from another server, and after installing it, I managed to bring it online (after some trouble, we ran into some bugs in our particular version of DBMGUI). I can log into both SQL and DBM, but the DBA user was missing after restore (in DBMGUI, it's registered in the SQL). I created the SUPERDBA user, intending it to be the DBA user, but it doesn't show up anything special in DBMCLI. When I log into the SQLStudio and do a check on the users with SELECT * FROM DOMAIN.USERS, SUPERDBA does show up as having SYSDBA mode.

When trying to do a load_systab from DBMCLI, however, it gives the error: -24908 Wrong SYSDBA.

That's great, since there is no other SYSDBA. The DB Engine is 7.4.3.19 Yes, I am aware that it isn't supported, but that doesn't mean it shouldn't work We have to use 7.4 for this project, otherwise I would gladly use 7.7.

(And yes, we are an SAP customer, and I have already put in an OSS note, but I prefer the forum if possible so everyone can see the answer).

Also in the log we get:

ERR_DBAWRONG: wrong SYSDBA

I checked in the help for MaxDB and there is a command (something like conf_sysdba) to change the sysdba user - but that only works on 7.6 or newer. How can we force it to recognize the SYSDBA user on 7.4.3.x?

(Also, I have seen some mysterious commands changing config settings like SAPDB12, but is this stuff documented anywhere).

Thank you very much,

Noah Silva

[lbreddemann]

Hi Noa,

> I created the SUPERDBA user, intending it to be the DBA user, but it doesn't show up anything special in DBMCLI.

Ok, this should never be done - SUPERDBA (the SYSDBA in SAP installations) get's created during the initial load of systemtables, that is, when the database is created.

If the user is missing after a systemcopy via backup/restore it's quite likely that there is something wrong on the source system.

> When trying to do a load_systab from DBMCLI, however, it gives the error: -24908 Wrong SYSDBA.

Well, now the error is likely because you created an additional user.

> That's great, since there is no other SYSDBA. The DB Engine is 7.4.3.19 Yes, I am aware that it isn't supported, but that doesn't mean it shouldn't work We have to use 7.4 for this project, otherwise I would gladly use 7.7.

> (And yes, we are an SAP customer, and I have already put in an OSS note, but I prefer the forum if possible so everyone can see the answer).

If this database is not for a SAP product (which cannot be, since you have to use a unsupported version of SAP DB), than it doesn't matter if you're a SAP customer or not.

You won't get support for your own SAP DB project via support messages (as long as you did not buy the available extra support for such requests).

> I checked in the help for MaxDB and there is a command (something like conf_sysdba) to change the sysdba user - but that only works on 7.6 or newer. How can we force it to recognize the SYSDBA user on 7.4.3.x?

The goal here should not be to change the SYSDBA but to fix the original problem.

Does a load_systab run through on the source system?

> (Also, I have seen some mysterious commands changing config settings like SAPDB12, but is this stuff documented anywhere).

Sure - we have it here available internal, acessible for development and support stuff.

But I can promise: this is likely not what we will need here.

First check the source database!

regards,

Lars

[Former Member]

>>I created the SUPERDBA user, intending it to be the DBA user, but it doesn't show up anything special in

>> DBMCLI.

>Ok, this should never be done - SUPERDBA (the SYSDBA in SAP installations) get's created during the >initial load of systemtables, that is, when the database is created.

See I am a little confused here, it seems when the backup is restored, it restores the SQL users, but not the DBM users. The SQL users are obviously stored in the Database, but where are the DBM users stored? a Config file?

>If the user is missing after a systemcopy via backup/restore it's quite likely that there is something wrong

> on the source system.

The source system works fine.

[Former Member]

>If this database is not for a SAP product (which cannot be, since you have to use a unsupported version

>of SAP DB), than it doesn't matter if you're a SAP customer or not.

>You won't get support for your own SAP DB project via support messages (as long as you did not buy

>the available extra support for such requests).

We have to use the unsupported version of SAPDB because that version is the version needed by the (old) version of the SAP product we are using. The customer has an old version and new version, and wants a working copy of the old system.

>I checked in the help for MaxDB and there is a command (something like conf_sysdba) to change the

>sysdba user - but that only works on 7.6 or newer. How can we force it to recognize the SYSDBA user

>on 7.4.3.x?

>The goal here should not be to change the SYSDBA but to fix the original problem.

>Does a load_systab run through on the source system?

It runs on the destination system when we use the version of DBMGUI mentioned, but after restore there is only one DBM user (whichever one we make in the Installation wizard).

Anyway apparently my co-workers solved the problem by cloning the original system (via imaging and import into VMWare). We were worried that taking that route would cause too many problems with changing the hostname, but apparently it's less work than fixing this problem. I do greatly appreciate the help though.