Skip to Content
0
Former Member
Apr 14, 2010 at 12:29 PM

error loading systabs

179 Views

Hi all,

I just did a recovery with initialization for a MaxDB 7.6.05.15. After the recovery the database could not be set to online, because of a error with the system triggers (please have a look at note 1303323 - Missing system triggers prevent MaxDB starting). So I set ENABLE_SYSTEM_TRIGGERS" to "NO" and the system came up.

Now I am hanging at task three: Load the system tables

This breaks with a

-24964,ERR_EXECUTE: error in program execution

256,/sapdb/XXX/db/bin/x_python /sapdb/XXX/db/env/lsystab.py -R /sapdb/XXX/db -d XXX -u superdba,*

-


Traceback----


-


Error----


sql.SQLError: [-4008] (at 1) Unknown user name/password combination

Traceback (most recent call last):

File "/sapdb/XXX/db/env/lsystab.py", line 202, in ?

connectAndInstall (install, install.__doc__)

File "/sapdb/XXX/db/env/installib.py", line 404, in connectAndInstall

session = connect (options)

File "/sapdb/XXX/db/env/installib.py", line 353, in connect

alterUserNotExclusive(options)

File "/sapdb/XXX/db/env/installib.py", line 341, in alterUserNotExclusive

session.release()

AttributeError: 'NoneType' object has no attribute 'release'

so it seems, that there is a problem with the user superdba and its password

I can logon to the system using

dbmcli -d XXX -n server -u superdba,<iknowthepassword>

but loading the systab with load_systab or load_systab -u throws the erro written above.

When I try to set the password with (note 25591 - Changing the DBM, SYSDBA and DBA user passwords part 3)

user_put superdba password=<knownoldpassword>

I get a

ERR

-24988,ERR_UNKNOWN: unknown error

When I try to set the password with dbmgui I have to login as superdba (that works, because I know the password...) but I can't change the password for superdba, because of

-24988 SQL error [sql_error ALTER USER "SUPERDBA" TIMEOUT NULL COSTWARNING NULL COSTLIMIT NOTT NOT EXCLUSIVE ENABLE CONNECT];

-5001, Missing provilege: OWNER

It seems, that there is a difference in SQL password and DBM password ... but how to fix it?

At the moment I am thinking about a recovery with initialization setting ENABLE_SYSTEM_TRIGGERS before restarting the system ...

Do you have any suggestions?

Thank you.

Best regards

Christian