Andreas Klenk wrote: > > > That sounds strange. > > Did you (try to) rename some dba? > No. > > > Do you see table SYSMONITOR without prefixing it with DBA. ? > No. Works only with the prefix. > > > Did you try to load the systemtables anew (load_systab in > dbmcli) ? > > I tried to load it but can't get it to work. > ./dbmcli -d TISYS -u dbm,dbm load_systab -u dba,dba -ud domain > -24907,ERR_DBAWRONG: wrong SYSDBA > > The strange thing is, that I can log in as dba using SQL Studio. The > TISYS.upc file exists but is not human readable. > > Thank You. > Andreas Klenk >
Some mails out of the list explained, that a backup from another machine was recovered. After this the problem occured. It could be verified by select sysdba from DBA.DUAL where not DBA, but his sysdba-name was the result. Explanation: If one takes a backup/a living database from kernel version x, NEVER use an older (with smaller version number) kernel to restart/work with this backup/database. This will always (until a bug will be fixed and that new kernel version released) cause this problem or even harder ones. One cannot change the incorrect sysdba-value to the correct one. --> if you want to use backups from machine m1 to be used for m2, use the same kernel version (that with the higher version number). BTW in this case: 7.3.0.34 is 10 month old. What about switching BOTH machines to a newer version? Elke SAP Labs Berlin -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
