cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

MAXDB service down

Former Member

on ‎01-19-2009 11:12 AM

0 Kudos

Hi All,

I am facing a problem, MAXDB service in the windows services is down. I can use the database in Admin mode but not able to bring it up in the online mode as a result my SAP is down.

when I try to restart the service manually it throws an error 1067: the process treminated unexceptedly.

so is there is any way to reinstall the MAXDB service in the windows services.I had tried reading logs in the working directory but it doesn't help much

regards,

sen

Edited by: Sen Thongam on Jan 19, 2009 12:12 PM

Show replies
Show replies
Answer

Accepted Solutions (0)

Answers (1)

Answers (1)

markus_doehr2
Active Contributor
‎01-19-2009 11:16 AM
0 Kudos

> when I try to restart the service manually it throws an error 1067: the process treminated unexceptedly.

> so is there is any way to reinstall the MAXDB service in the windows services.I had tried reading logs in the working directory but it doesn't help much

- logon as <sid>adm

- open a cmd.exe

- execute "dbmcli -U c db_online"

if that fails, post the last lines of "knldiag" logfile in the work directory.

Markus

Show replies
Show replies
Former Member
‎01-19-2009 11:31 AM
0 Kudos

hello Markus,

That command fails its give error runtime enviroment error

these are the last few lines of the knldiag files

2009-01-19 19:25:56 0x1560 ERR 19999 BTRACE Params: 01:000000af 02:0b28fe80 03:0b28ff00 04:b37f0470

2009-01-19 19:25:56 0x1560 ERR 19999 BTRACE Source: rst_redoreadtask.cpp ( Line: 438 )

2009-01-19 19:25:56 0x1560 ERR 19999 BTRACE kernel!Rst_RedoManager::ReadLogAndCreateRedoFiles + 34 bytes

2009-01-19 19:25:56 0x1560 ERR 19999 BTRACE SFrame: IP:00674f52 RA:00984ea7 FP:0b28e05c SP:0b28e064

2009-01-19 19:25:56 0x1560 ERR 19999 BTRACE Params: 01:000000af 02:0b28fe80 03:0b28ff00 04:00000000

2009-01-19 19:25:56 0x1560 ERR 19999 BTRACE Source: rst_redomanager.cpp ( Line: 426 )

2009-01-19 19:25:56 0x1560 ERR 19999 BTRACE kernel!SrvTasks_JobRedo::ExecuteIntern + 87 bytes

2009-01-19 19:25:56 0x1560 ERR 19999 BTRACE SFrame: IP:00984ea7 RA:005f6f19 FP:0b28e088 SP:0b28e090

2009-01-19 19:25:56 0x1560 ERR 19999 BTRACE Params: 01:00aa9dc0 02:b37f04ad 03:0b28e83c 04:00000000

2009-01-19 19:25:56 0x1560 ERR 19999 BTRACE Source: srvtasks_jobredo.cpp ( Line: 85 )

2009-01-19 19:25:56 0x1560 ERR 19999 BTRACE kernel!SrvTasks_Job::Execute + 601 bytes

2009-01-19 19:25:56 0x1560 ERR 19999 BTRACE SFrame: IP:005f6f19 RA:005f802b FP:0b28e170 SP:0b28e178

2009-01-19 19:25:56 0x1560 ERR 19999 BTRACE Params: 01:b5131468 02:0b28fe80 03:00000000 04:00000000

2009-01-19 19:25:56 0x1560 ERR 19999 BTRACE Source: srvtasks_job.cpp ( Line: 283 )

2009-01-19 19:25:56 0x1560 ERR 19999 BTRACE kernel!SrvTasks_Task::Run + 1259 bytes

2009-01-19 19:25:56 0x1560 ERR 19999 BTRACE SFrame: IP:005f802b RA:00670d78 FP:0b28e72c SP:0b28e734

2009-01-19 19:25:56 0x1560 ERR 19999 BTRACE Params: 01:b5131468 02:0b28fe80 03:0b28fe80 04:00044000

2009-01-19 19:25:56 0x1560 ERR 19999 BTRACE Source: srvtasks_task.cpp ( Line: 151 )

2009-01-19 19:25:56 0x1560 ERR 19999 BTRACE kernel!Kernel_NonUserTask + 488 bytes

2009-01-19 19:25:56 0x1560 ERR 19999 BTRACE SFrame: IP:00670d78 RA:0099277b FP:0b28e8cc SP:0b28e8d4

2009-01-19 19:25:56 0x1560 ERR 19999 BTRACE Params: 01:b5131468 02:0b28fe80 03:0b28ff00 04:0b28ff00

2009-01-19 19:25:56 0x1560 ERR 19999 BTRACE Source: kernel_initialization.cpp ( Line: 297 )

2009-01-19 19:25:56 0x1560 ERR 19999 BTRACE kernel!Kernel_Main + 107 bytes

2009-01-19 19:25:56 0x1560 ERR 19999 BTRACE SFrame: IP:0099277b RA:00689c7c FP:0b28ff74 SP:0b28ff7c

2009-01-19 19:25:56 0x1560 ERR 19999 BTRACE Params: 01:b5131468 02:b52a1a10 03:006d7e0f 04:00000000

2009-01-19 19:25:56 0x1560 ERR 19999 BTRACE Source: kernel_main.cpp ( Line: 164 )

2009-01-19 19:25:56 0x1560 ERR 19999 BTRACE kernel!RTETask_TaskMain + 76 bytes

2009-01-19 19:25:56 0x1560 ERR 19999 BTRACE SFrame: IP:00689c7c RA:006d7e0f FP:0b28ff80 SP:0b28ff88

2009-01-19 19:25:56 0x1560 ERR 19999 BTRACE Params: 01:00000000 02:00000000 03:b5112e98 04:00000000

2009-01-19 19:25:56 0x1560 ERR 19999 BTRACE Source: rtetask_task.cpp ( Line: 390 )

2009-01-19 19:25:56 0x1560 ERR 19999 BTRACE kernel!sql88k_kernel_fiber + 191 bytes

2009-01-19 19:25:56 0x1560 ERR 19999 BTRACE SFrame: IP:006d7e0f RA:77e64829 FP:0b28ffbc SP:0b28ffc4

2009-01-19 19:25:56 0x1560 ERR 19999 BTRACE Params: 01:b5112e98 02:00000000 03:00000000 04:b5112e98

2009-01-19 19:25:56 0x1560 ERR 19999 BTRACE Source: vos88k.cpp ( Line: 433 )

2009-01-19 19:25:56 0x1560 ERR 19999 BTRACE kernel32!GetModuleHandleA + 223 bytes

2009-01-19 19:25:56 0x1560 ERR 19999 BTRACE SFrame: IP:77e64829 RA:77e52575 FP:0b28fff0 SP:0b28ffc4

2009-01-19 19:25:56 0x1560 ERR 19999 BTRACE Params: 01:006d7d50 02:b5112e98 03:00000000 04:00000000

2009-01-19 19:25:56 0x1560 ERR 19999 BTRACE kernel32!GlobalReAlloc + 380 bytes

2009-01-19 19:25:56 0x1560 ERR 19999 BTRACE SFrame: IP:77e52575 RA:00000000 FP:00000000 SP:0b28ffc4

2009-01-19 19:25:56 0x1560 ERR 19999 BTRACE Params: 01:00000000 02:00000000 03:00000000 04:00000000

2009-01-19 19:25:56 0x8C8 ERR 19999 BTRACE Mini dump file 'KnlMini.dmp' written!

2009-01-19 19:25:56 0xB7C ERR 7 Messages Begin of dump of registered messages

2009-01-19 19:25:56 0xB7C ERR 8 Messages End of the message list registry dump

2009-01-19 19:25:56 0xE7C 20000 Trace Start flush kernel trace

2009-01-19 19:25:56 0xB7C 19684 TASKING Tracewriter termination timeout: 1200 sec

2009-01-19 19:25:56 0xE7C 19617 VOLUMEIO Single I/O attach, 'knltrace', UKT:1

2009-01-19 19:25:56 0xE7C 20001 Trace Stop flush kernel trace

2009-01-19 19:25:56 0xE7C 20002 Trace Start flush kernel dump

2009-01-19 19:25:56 0xE7C 20003 Trace Stop flush kernel dump

2009-01-19 19:25:56 0xE7C 19619 TASKING Releasing tracewriter

2009-01-19 19:25:56 0xB7C 19890 DIAGHIST Backup of diagnostic files will be forced at next restart

2009-01-19 19:25:56 0xB7C 19600 VERSION 'Kernel 7.6.00 Build 035-123-139-084'

2009-01-19 19:25:56 0xB7C 19654 DBSTATE SERVERDB 'BI1' has stopped

-

current write position -

Thanks,

sen

markus_doehr2
Active Contributor
‎01-19-2009 11:46 AM
0 Kudos

2009-01-19 19:25:56 0x1560 ERR 19999 BTRACE Params: 01:000000af 02:0b28fe80 03:0b28ff00 04:b37f0470

2009-01-19 19:25:56 0x1560 ERR 19999 BTRACE Source: rst_redoreadtask.cpp ( Line: 438 )

2009-01-19 19:25:56 0x1560 ERR 19999 BTRACE kernel!Rst_RedoManager::ReadLogAndCreateRedoFiles + 34 bytes

2009-01-19 19:25:56 0x1560 ERR 19999 BTRACE SFrame: IP:00674f52 RA:00984ea7 FP:0b28e05c SP:0b28e064

2009-01-19 19:25:56 0x1560 ERR 19999 BTRACE Params: 01:000000af 02:0b28fe80 03:0b28ff00 04:00000000

2009-01-19 19:25:56 0x1560 ERR 19999 BTRACE Source: rst_redomanager.cpp ( Line: 426 )

This doesn´t look good - something is wrong with your logfile and/or the content of it.

I suggest you open an OSS call (BC-DB-SDB) and let the support have a look on the system.

Markus

lbreddemann
Active Contributor
‎01-19-2009 11:55 AM
0 Kudos

Hi there,

MaxDB 7.6 Build 35 is very old and there had been quite some bugs related to recovery.

Could it be that you use multiple logqueues? (check parameter MAX_LOG_QUEUE_COUNT).

regards,

Lars

Former Member
‎01-19-2009 11:56 AM
0 Kudos

Hi Markus,

Thanks Markus for your quick reply.

Any idea about re-setting the MAXDB service. As that of sap service (sapstartsrv)

Thanks,

sen

markus_doehr2
Active Contributor
‎01-19-2009 12:04 PM
0 Kudos

Any idea about re-setting the MAXDB service. As that of sap service (sapstartsrv)

??

Your problem is not the service.

The database is corrupt and can´t be started. You need to restore it from a backup.

Markus

Former Member
‎01-19-2009 12:16 PM
0 Kudos

Hello Markus,

I had taken the backup. this service failed when the system was rebooted after a complete backup and archiving log files.

Is there changes that this will up after restoring of databackup, I mean this service once i restore the BACKUP.

thanks,

sen

markus_doehr2
Active Contributor
‎01-19-2009 12:17 PM
0 Kudos

Did you shutdown the database before you rebooted? This is usually not done automatically.

I suggest again: Open an OSS call and let the support have a look on the system to find out, what went wrong. Only they can tell you if your database will be able to be started with the current log.

Markus

lbreddemann
Active Contributor
‎01-19-2009 1:38 PM
0 Kudos

Hi there,

the problem here is that the content of the log area leads to a kernel crash.

There had been some bugs in the older builds of 7.6, e.g. when the kernel tried to recover certain log information that was created with multiple Log Queues.

That's why I asked about this.

Be very clear about this: the data area is full intact on this system (at least there is no reason to believe anything else). What's causing the error is the log area.

If you can live with that, you may simply delete the log area and use the last written savepoint as the new state of the database.

If you desperately need the information from the log area, you should perform a log backup first and try a point-in-time recovery to a time before the last log entries had been written.

regards,

Lars

Ask a Question