Maxdb don't go online

[Former Member]

I have a problem with my database.

Suddenly I was no access to my db via database manager, "unknown user / password combination".

After many attempts I made a u201Crecover_configu201D (dbmcli) from a backup that I had. Now the db is in Admin mode, but not going to online.

u201C-24988 sql error [db_warm_f]; -8888, connection broken.

I try to make a u201Ccheck database structure u2026 state ADMINu201D but after a lot of time give me the same error.

Someone can help me ....

DB 7.3.00.35

Database Manager 7.6

Best regards

[former_member182034 · Accepted solution]

Hi Paulo,

trick, just rename the file SID.dbm.shm in Drive\sapdb\data\wrk and retry.

I hope you problem will resolve.

Regards,

[Former Member · Accepted solution]

Hi magamil.

I don't have that file. The only shm file is "irtrace.shm".

*knlidag*

2011-05-10 09:28:04 0x830 ERR 51361 RESTART CONTROL USER ALR. EXISTS; 0

2011-05-10 09:28:04 0x830 ERR 18196 DBCRASH vabort:Emergency Shutdown, vgg01.c: 2374

2011-05-10 09:28:04 0x830 ERR 19999 BTRACE module file name |.text start |.text end

2011-05-10 09:28:04 0x830 ERR 19999 BTRACE kernel.exe | 0x00400000 | 0x00844000

2011-05-10 09:28:04 0x830 ERR 19999 BTRACE dbghelp.dll | 0x6d580000 | 0x6d628000

2011-05-10 09:28:04 0x830 ERR 19999 BTRACE WS2HELP.dll | 0x71bf0000 | 0x71bf8000

2011-05-10 09:28:04 0x830 ERR 19999 BTRACE WS2_32.dll | 0x71c00000 | 0x71c17000

2011-05-10 09:28:04 0x830 ERR 19999 BTRACE sqltcp.dll | 0x76000000 | 0x7600d000

2011-05-10 09:28:04 0x830 ERR 19999 BTRACE IMM32.DLL | 0x76290000 | 0x762ad000

2011-05-10 09:28:04 0x830 ERR 19999 BTRACE imagehlp.dll | 0x76c10000 | 0x76c38000

2011-05-10 09:28:04 0x830 ERR 19999 BTRACE DNSAPI.dll | 0x76ed0000 | 0x76efa000

2011-05-10 09:28:04 0x830 ERR 19999 BTRACE Secur32.dll | 0x76f50000 | 0x76f63000

2011-05-10 09:28:04 0x830 ERR 19999 BTRACE rasadhlp.dll | 0x76f80000 | 0x76f85000

2011-05-10 09:28:04 0x830 ERR 19999 BTRACE USER32.dll | 0x77380000 | 0x77411000

2011-05-10 09:28:04 0x830 ERR 19999 BTRACE comctl32.dll | 0x77420000 | 0x77523000

2011-05-10 09:28:04 0x830 ERR 19999 BTRACE ole32.dll | 0x77670000 | 0x777a9000

2011-05-10 09:28:04 0x830 ERR 19999 BTRACE VERSION.dll | 0x77b90000 | 0x77b98000

2011-05-10 09:28:04 0x830 ERR 19999 BTRACE msvcrt.dll | 0x77ba0000 | 0x77bfa000

2011-05-10 09:28:04 0x830 ERR 19999 BTRACE GDI32.dll | 0x77c00000 | 0x77c49000

2011-05-10 09:28:04 0x830 ERR 19999 BTRACE RPCRT4.dll | 0x77c50000 | 0x77cef000

2011-05-10 09:28:04 0x830 ERR 19999 BTRACE SHLWAPI.dll | 0x77da0000 | 0x77df2000

2011-05-10 09:28:04 0x830 ERR 19999 BTRACE kernel32.dll | 0x77e40000 | 0x77f42000

2011-05-10 09:28:04 0x830 ERR 19999 BTRACE ADVAPI32.dll | 0x77f50000 | 0x77feb000

2011-05-10 09:28:04 0x830 ERR 19999 BTRACE ntdll.dll | 0x7c800000 | 0x7c8c0000

2011-05-10 09:28:04 0x830 ERR 19999 BTRACE SHELL32.dll | 0x7c8d0000 | 0x7d0cf000

2011-05-10 09:28:04 0x830 ERR 19999 BTRACE -

---

> Stack Back Trace <----

2011-05-10 09:28:04 0x830 ERR 19999 BTRACE ntdll!KiFastSystemCallRet

2011-05-10 09:28:04 0x830 ERR 19999 BTRACE kernel!_eo670_CTraceContextStack + 106 bytes

2011-05-10 09:28:04 0x830 ERR 19999 BTRACE kernel!_eo670_CTraceStack + 70 bytes

2011-05-10 09:28:04 0x830 ERR 19999 BTRACE kernel!_sql50k_excepthandler + 1992 bytes

2011-05-10 09:28:04 0x830 ERR 19999 BTRACE kernel!__vabort + 67 bytes

2011-05-10 09:28:04 0x830 ERR 19999 BTRACE kernel!_g01abort + 199 bytes

2011-05-10 09:28:04 0x830 ERR 19999 BTRACE kernel!_ak36restart_second_part + 159 bytes

2011-05-10 09:28:04 0x830 ERR 19999 BTRACE kernel!_ak36restart + 251 bytes

2011-05-10 09:28:04 0x830 ERR 19999 BTRACE kernel!_a36_call_semantic + 273 bytes

2011-05-10 09:28:04 0x830 ERR 19999 BTRACE kernel!_a30_init_utility + 684 bytes

2011-05-10 09:28:04 0x830 ERR 19999 BTRACE kernel!_ak94utility + 564 bytes

2011-05-10 09:28:04 0x830 ERR 19999 BTRACE kernel!_ak94mess_type_analysis + 93 bytes

2011-05-10 09:28:04 0x830 ERR 19999 BTRACE kernel!_ak94one_command + 175 bytes

2011-05-10 09:28:04 0x830 ERR 19999 BTRACE kernel!_a94_service_commands + 482 bytes

2011-05-10 09:28:04 0x830 ERR 19999 BTRACE kernel!_ak91run_non_sql_process + 70 bytes

2011-05-10 09:28:04 0x830 ERR 19999 BTRACE kernel!_ak91run_user_process + 200 bytes

2011-05-10 09:28:04 0x830 ERR 19999 BTRACE kernel!_a91mainprogram + 92 bytes

2011-05-10 09:28:04 0x830 ERR 19999 BTRACE kernel!_sql88k_release_curr_task_or_fiber + 211 bytes

2011-05-10 09:28:04 0x830 ERR 19999 BTRACE kernel!_sql88k_ukt + 971 bytes

2011-05-10 09:28:05 0x830 19820 EXCEPT calling ak dump for T5

2011-05-10 09:28:05 0x830 19624 EXCEPT Kernel aborts

2011-05-10 09:28:05 0xFC4 19617 DEVIO Single I/O attach, 'knltrace', UKT:1

2011-05-10 09:28:05 0x830 19684 TASKING Tracewriter termination timeout: 1200 sec

2011-05-10 09:28:06 0xFC4 19619 TASKING Releasing tracewriter

2011-05-10 09:28:06 0x830 19600 VERSION 'Kernel 7.3.0 Build 035-000-090-294'

2011-05-10 09:28:06 0x830 19654 DBSTATE SERVERDB 'SDB' has stopped

Paulo

Edited by: Paulo Oliveira on May 10, 2011 3:23 PM

[markus_doehr2 · Accepted solution]

The kernel dies in a very early state.

Now we need to know EXACTLY what commands you entered before this happened.

Markus

[Former Member · Accepted solution]

this happens when I click on the database manager in the green light.

if I try to start de db in dbmcli "db_start" the database stay in ADMIN mode.

Paulo

[markus_doehr2 · Accepted solution]

Yes - but what "recover_config" command did you enter?

Markus

[Former Member · Accepted solution]

the steps that I made were the following:

dbmcli -d sdb -u ...,...

service_connect

recover_config .... (here I put the name of a backup medium)

[markus_doehr2 · Accepted solution]

Ok - and then did you start the recover?

Markus

[Former Member · Accepted solution]

yes, was instantaneous

Edited by: Paulo Oliveira on May 11, 2011 11:00 AM

[Former Member · Accepted solution]

Marcus,

do you not have an idea how can I solve this problem?

Paulo

[former_member229109 · Accepted solution]

Hello,

1.

You reported error:

u201CERR 51361 RESTART CONTROL USER ALR. EXISTSu201D

=>

You failed to restart the target database with the error:

RESTART CONTROL USER ALR. EXISTS; 0

because you initialized the database parameters from backup which has user value of controluserid and

this user is SYSDBA user in your database, may be.

It has to be corrected.

Please update with additional information:

-> Output of the dbm commands:

param_directget controluserid

user_getall

-> What are DBM and SYSDBA users of your database?

2. u201CAfter many attempts I made a u201Crecover_configu201D (dbmcli) from a backup that I had.u201D

What kind of backup it was? Was it the backup of the current database or another database?

When the backup was created => what was DBM, control by default SAP install, user and DBM-pwd of the database?

3. Are you SAP customer?

Regards, Natalia Khlopina

[Former Member · Accepted solution]

Hello

dbmcli on SDB>param_directget controluserid

OK

CONTROLUSERID SUPERDBA

dbmcli on SDB>user_getall

OK

CONTROL

SUPERDBA

domain

PAULO

The recover_config itu2019s from a full backup of the same database.

The user that I use is "SUPERDBA"

Yes, Iu2019m a SAP customer

2011-05-17 11:52:02 0x137C ERR 51361 RESTART CONTROL USER ALR. EXISTS; 0

2011-05-17 11:52:02 0x137C ERR 18196 DBCRASH vabort:Emergency Shutdown, vgg01.c: 2374

2011-05-17 11:52:02 0x137C ERR 19999 BTRACE module file name |.text start |.text end

2011-05-17 11:52:02 0x137C ERR 19999 BTRACE kernel.exe | 0x00400000 | 0x00844000

2011-05-17 11:52:02 0x137C ERR 19999 BTRACE dbghelp.dll | 0x6d580000 | 0x6d628000

2011-05-17 11:52:02 0x137C ERR 19999 BTRACE WS2HELP.dll | 0x71bf0000 | 0x71bf8000

2011-05-17 11:52:02 0x137C ERR 19999 BTRACE WS2_32.dll | 0x71c00000 | 0x71c17000

2011-05-17 11:52:02 0x137C ERR 19999 BTRACE sqltcp.dll | 0x76000000 | 0x7600d000

2011-05-17 11:52:02 0x137C ERR 19999 BTRACE IMM32.DLL | 0x76290000 | 0x762ad000

2011-05-17 11:52:02 0x137C ERR 19999 BTRACE imagehlp.dll | 0x76c10000 | 0x76c38000

2011-05-17 11:52:02 0x137C ERR 19999 BTRACE DNSAPI.dll | 0x76ed0000 | 0x76efa000

2011-05-17 11:52:02 0x137C ERR 19999 BTRACE Secur32.dll | 0x76f50000 | 0x76f63000

2011-05-17 11:52:02 0x137C ERR 19999 BTRACE rasadhlp.dll | 0x76f80000 | 0x76f85000

2011-05-17 11:52:02 0x137C ERR 19999 BTRACE USER32.dll | 0x77380000 | 0x77411000

2011-05-17 11:52:02 0x137C ERR 19999 BTRACE comctl32.dll | 0x77420000 | 0x77523000

2011-05-17 11:52:02 0x137C ERR 19999 BTRACE ole32.dll | 0x77670000 | 0x777a9000

2011-05-17 11:52:02 0x137C ERR 19999 BTRACE VERSION.dll | 0x77b90000 | 0x77b98000

2011-05-17 11:52:02 0x137C ERR 19999 BTRACE msvcrt.dll | 0x77ba0000 | 0x77bfa000

2011-05-17 11:52:02 0x137C ERR 19999 BTRACE GDI32.dll | 0x77c00000 | 0x77c49000

2011-05-17 11:52:02 0x137C ERR 19999 BTRACE RPCRT4.dll | 0x77c50000 | 0x77cef000

2011-05-17 11:52:02 0x137C ERR 19999 BTRACE SHLWAPI.dll | 0x77da0000 | 0x77df2000

2011-05-17 11:52:02 0x137C ERR 19999 BTRACE kernel32.dll | 0x77e40000 | 0x77f42000

2011-05-17 11:52:02 0x137C ERR 19999 BTRACE ADVAPI32.dll | 0x77f50000 | 0x77feb000

2011-05-17 11:52:02 0x137C ERR 19999 BTRACE ntdll.dll | 0x7c800000 | 0x7c8c0000

2011-05-17 11:52:02 0x137C ERR 19999 BTRACE SHELL32.dll | 0x7c8d0000 | 0x7d0cf000

2011-05-17 11:52:02 0x137C ERR 19999 BTRACE -

---

> Stack Back Trace <----

2011-05-17 11:52:02 0x137C ERR 19999 BTRACE ntdll!KiFastSystemCallRet

2011-05-17 11:52:02 0x137C ERR 19999 BTRACE kernel!_eo670_CTraceContextStack + 106 bytes

2011-05-17 11:52:02 0x137C ERR 19999 BTRACE kernel!_eo670_CTraceStack + 70 bytes

2011-05-17 11:52:02 0x137C ERR 19999 BTRACE kernel!_sql50k_excepthandler + 1992 bytes

2011-05-17 11:52:02 0x137C ERR 19999 BTRACE kernel!__vabort + 67 bytes

2011-05-17 11:52:02 0x137C ERR 19999 BTRACE kernel!_g01abort + 199 bytes

2011-05-17 11:52:02 0x137C ERR 19999 BTRACE kernel!_ak36restart_second_part + 159 bytes

2011-05-17 11:52:02 0x137C ERR 19999 BTRACE kernel!_ak36restart + 251 bytes

2011-05-17 11:52:02 0x137C ERR 19999 BTRACE kernel!_a36_call_semantic + 273 bytes

2011-05-17 11:52:02 0x137C ERR 19999 BTRACE kernel!_a30_init_utility + 684 bytes

2011-05-17 11:52:02 0x137C ERR 19999 BTRACE kernel!_ak94utility + 564 bytes

2011-05-17 11:52:02 0x137C ERR 19999 BTRACE kernel!_ak94mess_type_analysis + 93 bytes

2011-05-17 11:52:02 0x137C ERR 19999 BTRACE kernel!_ak94one_command + 175 bytes

2011-05-17 11:52:02 0x137C ERR 19999 BTRACE kernel!_a94_service_commands + 482 bytes

2011-05-17 11:52:02 0x137C ERR 19999 BTRACE kernel!_ak91run_non_sql_process + 70 bytes

2011-05-17 11:52:02 0x137C ERR 19999 BTRACE kernel!_ak91run_user_process + 200 bytes

2011-05-17 11:52:02 0x137C ERR 19999 BTRACE kernel!_a91mainprogram + 92 bytes

2011-05-17 11:52:02 0x137C ERR 19999 BTRACE kernel!_sql88k_release_curr_task_or_fiber + 211 bytes

2011-05-17 11:52:02 0x137C ERR 19999 BTRACE kernel!_sql88k_ukt + 971 bytes

2011-05-17 11:52:54 --- Starting ---

best regards, Paulo

Edited by: Paulo Oliveira on May 17, 2011 1:29 PM

[former_member229109 · Accepted solution]

Hello,

1. I recommend to create the SAP message.

2. You failed to restart the target database with the error:

RESTART CONTROL USER ALR. EXISTS; 0

as I already wrote you, because you initialized the database parameters from backup which has user value of controluserid and this user is SYSDBA user in your database, may be.

It has to be corrected.

-> What are DBM and SYSDBA users of your database?

-> According your last information you the database DBM user - "SUPERDBA".

Is it also SYSDBA user of your database?

Please update with additional information:

Output of the dbm commands:

user_get control

user_get superdba

Thank you and best regards, Natalia Khlopina

[Former Member · Accepted solution]

hello

i-> According your last information you the database DBM user - "SUPERDBA".

Is it also SYSDBA user of your database?

I donu2019t have sure. I think so

---

dbmcli on sdb>user_get control

OK

SERVERRIGHTS=DBInfoRead,ExecLoad,SystemCmd,UserMgm,FileFull,FileRead,DBFileRead,

Backup,InstallMgm,LoadSysTab,ParamCheckWrite,ParamFull,ParamRead,DBStart,DBStop,

Recovery,AccessSQL,AccessUtility

GUIRIGHTS=

SECONDPASSWORD=NO

DBMUSER=YES

SQLUSER=NO

SQLUSERMODE=DBA

DISABLED=NO

SYSTEMNAME=

COMMENT=

---

dbmcli on sdb>user_get superdba

OK

SERVERRIGHTS=DBInfoRead,ExecLoad,SystemCmd,UserMgm,FileFull,FileRead,DBFileRead,

Backup,InstallMgm,LoadSysTab,ParamCheckWrite,ParamFull,ParamRead,DBStart,DBStop,

Recovery,AccessSQL,AccessUtility

GUIRIGHTS=

SECONDPASSWORD=NO

DBMUSER=YES

SQLUSER=NO

SQLUSERMODE=DBA

DISABLED=NO

SYSTEMNAME=

COMMENT=

---

Iu2019m already create a sap message. Iu2019m waiting!

But you have another clue.

best regards, Paulo

[former_member229109 · Accepted solution]

Hello,

1.

"Iu2019m already create a sap message. Iu2019m waiting!"

What is your message number?

2.

"But you have another clue."

I'm right with my assumption.

You should not use the SUPERDBA user as DBM user.

It's not DBM user in UPC containers too.

Please post output of the dbm commands:

dbm_configget SAPDB12

dbm_configget SAPDB5

3.

Someone can help me ....

DB 7.3.00.35

Database Manager 7.6

If you have the complete cold database backup for migration, then recreate the database for restore,

more details in the note - 129352.

Create the database with control user.

4.

"the steps that I made were the following:

dbmcli -d sdb -u ...,...

service_connect

recover_config .... (here I put the name of a backup medium)

"

Why did you run those steps?

What user did you use at that time to connect to the database?

Regards, Natalia Khlopina

[Former Member · Accepted solution]

1.

Message 404150/2011

2.

dbmcli on sdb>dbm_configget SAPDB12

OK

SUPERDBA

dbmcli on sdb>dbm_configget SAPDB5

OK

SUPERDBA

4.

I'm always used the user "superdba"

Regards, Paulo

[former_member229109 · Accepted solution]

Hello Paulo

You could NOT have the same user "SUPERDBA" as COLD < DBM - control by defauld SAP install > and SYSDBA < superdba by default SAP install >.

Please review the note:

25591 Changing the DBM, SYSDBA and DBA user passwords

"I'm always used the user "superdba""

You could use the superdba user to run the database administration. But the question is with what user did you create the database.

If the database was restartable before you didn't have the user "SUPERDBA" set to control user id.

To find the best solution for you the database logs need to be checked.

Still you didn't answer why you initialized the DB parameters from backup.

When the database backup was created?

What database users you had when the database backup was created?

Regards, Natalia Khlopina

PS: For SAP liveCache documentation see the SAP note 767598

[Former Member · Accepted solution]

For me you are an angel to be trying to help...

[Former Member · Accepted solution]

Hello Natalia

One last question.

At the time of the error I tried to import additional backups.

Unfortunately that was not the last. Can I now import this last backup without having problems?

If the problem recurs, what steps should I do?

sorry to be so boring, Paulo

[former_member229109 · Accepted solution]

Hello Paulo,

1. You have old DB version - DB 7.3.00.35

See the SAP note - 129352 :

"Version 7.2 and 7.3

Either you generated a consistent data backup (migration) on the

source system or subsequent log backups or consistent incremental

backups are available on the source system."

2. You wrote, that you initialized DB parameters from backup only.

If you run only the DB parameters initialization from database backup, you know that that the database parameters were not changed since the database backup was created => fine, the database will be restartable.

If the database parameters were changed since the database backup was created => additional steps need to be done or

this database backup could not be used for the initialization of the database parameters.

Regards, Natalia Khlopina

[markus_doehr2]

Please check knldiag for errors.

Markus