Symptom
SAP MaxDB online failed and KnlMsg shows error :
KnlMsg
Thread 0x1958 Task 109 2025-01-27 10:39:31 ERR SYSERROR 51080: -9407 unexpected error
Thread 0x1958 Task 109 2025-01-27 10:39:31 ERR Admin 3: The database is going offline,_FILE=Kernel_Administration.cpp,_LINE=1003
2025-01-27 10:39:31 KernelCommo 6: Internal errorcode, Error code 6433 "system_error"
2025-01-27 10:39:31 WNG Admin 20025: ACTIVATE is missing
Thread 0x1958 Task 109 2025-01-27 10:39:31 CONNECT 19651: Connection released (SDB, T109, connection obj. 1f91edbd6c0)
Thread 0x1958 Task 109 2025-01-27 10:39:31 RTEKernel 61: rtedump written to file 'rtedump'
Thread 0x1958 Task 109 2025-01-27 10:39:31 RTEKernel 112: Offline KILL requested
Thread 0x1958 Task 109 2025-01-27 10:39:31 RunTime 3: State changed from ADMIN to SHUTDOWNKILL
Thread 0x924 Task - 2025-01-27 10:39:31 ERR Messages 7: Begin of dump of registered messages,_FILE=Msg_Registry.cpp,_LINE=507
Thread 0x924 Task - 2025-01-27 10:39:31 KernelCommo 6: Internal errorcode, Error code 6433 "system_error"
Thread 0x924 Task - 2025-01-27 10:39:31 ERR Admin 3: The database is going offline,_FILE=Kernel_Administration.cpp,_LINE=1003
2025-01-27 10:39:31 KernelCommo 6: Internal errorcode, Error code 6433 "system_error"
2025-01-27 10:39:31 WNG Admin 20025: ACTIVATE is missing
And by checking previous error, before "ACTIVATE is missing" first time occurs, we can see the database restore fails, which result the database activation not performed.
KnlMsgArchive
Thread 0xDF4 Task 109 2025-01-26 23:52:34 AdminMsg 0: 0000 RDB RETURNCODE -104;RESTORE DATA CANCEL
Thread 0xDF4 Task 109 2025-01-26 23:52:34 ERR Recovery 6: Data recovery failed,_FILE=Kernel_Administration.cpp,_LINE=2535
2025-01-26 23:52:33 ERR Recovery 7: Data area too small.,NUMBER3=5343316,NUMBER2=42746528,NUMBER1=3839994,NUMBER=30719952,_FILE=vkb39.cpp,_LINE=4134
DESCRIPTION:
The data backup could not be imported because the data area of the database with 30719952' KB or '3839994' pages is configured too small. For the data contained in the backup, page space of at least '42746528' KB or '5343316' is needed.
Please notice that you need a safety margin for the size of the data area to prevent an immediate "full database" situation after recreating the database.
ACTION:
Expand the data area of the database to the desired size by adding one or more data volumes.
2025-01-26 23:52:33 SrvTasks 17: Servertask Info: because Error in backup task occured
2025-01-26 23:52:33 SrvTasks 10: Job 1 (Backup / Restore Medium Task) [executing] WaitingT109 Result=3310
2025-01-26 23:52:33 KernelCommo 6: Error in backup task occured, Error code 3310 "devsize_too_small"
Thread 0x848 Task - 2025-01-27 10:05:38 MsgOutput 28: ___ Stopping GMT 2025-01-27 06:05:38 7.9.10 Build 004-123-265-969
Thread - Task - 2025-01-27 10:34:45 MsgOutput 27: --- Starting GMT 2025-01-27 06:34:45 7.9.11 Build 008-123-274-177
Thread 0x2B98 Task 109 2025-01-27 10:35:14 AdminMsg 0: 679729220004 0000 RST RESTART
Thread 0x2B98 Task 109 2025-01-27 10:35:14 ERR SYSERROR 51080: -9407 unexpected error
Thread 0x2B98 Task 109 2025-01-27 10:35:14 ERR Admin 3: The database is going offline,_FILE=Kernel_Administration.cpp,_LINE=1003
2025-01-27 10:35:14 KernelCommo 6: Internal errorcode, Error code 6433 "system_error"
2025-01-27 10:35:14 WNG Admin 20025: ACTIVATE is missing
Read more...
Environment
SAP MaxDB
Product
Keywords
MaxDB, services, error, local logon, Database studio, restore, recovery, backup, database size, ACTIVATE is missing, system_error, 6433 , KBA , BC-DB-SDB , MaxDB , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.