Error 20089,Check knldiag!

[Former Member]

Hi all,

I have installed SCM 7.0 SR1 on AIX 5.3, LiveCache Version is 7.7.04.29.

When I trying to Initialize LiveCache by using LC10, I get the following error:

• START *****************************

liveCache LGA (init)

19.08.2009

18:29

-

---

Installation path is /sapdb/LGA/db

Operating system is AIX

The liveCache state is ONLINE

DBMServer 7.7.04 Build 029-123-196-543

Stopping LGA

Starting LGA into ADMIN

ERR

-24994,ERR_RTE: Runtime environment error

20089,Check knldiag! Kernel died before reaching ADMIN state

ERROR : liveCache LGA not initialized

-

---

19.08.2009

18:31

• END ******************************

Could anyone help? What's the meaning of "20089,Check knldiag! Kernel died before reaching ADMIN state"?

When I using the MaxDB Database Manager to Inistialize the Database,

no error occurred.

Thank you for all replys.

Best regards

Matthias

[lbreddemann · Accepted solution]

> Starting LGA into ADMIN

> ERR

> -24994,ERR_RTE: Runtime environment error

> 20089,Check knldiag! Kernel died before reaching ADMIN state

> ERROR : liveCache LGA not initialized

> -

---

> 19.08.2009

> 18:31

> ************************* END ******************************

>

> Could anyone help? What's the meaning of "20089,Check knldiag! Kernel died before reaching ADMIN state"?

Would you mind to do what the error message proposes?

Check the KNLDIAG file! (Ok, it's named KNLMSG in 7.7. ...)

If that does not give you a clue - open a support message for this.

regards,

Lars

[Former Member · Accepted solution]

Hi Lars,

I hava analyzed the mentioned file and found the following messages. There are some problems with the memory settings on AIX. Could you give me any recommendation which parameter to set on which value?

Many, many thanks!

Matthias

Maximum number of processes: 1024

Maximum core file size: 0 MB

Maximum number of open files: 32000

Maximum file size: unlimited

Maximum number of threads: 32767

Maximum stack size: 4096 MB

Maximum virtual memory size: unlimited

Resident set size: 32 MB

Maximum heap size: 128 MB

Requested memory size exceeds available heap size

ACTION:

Contact your system administrator. Show him the error

message which points to an operating system configuration

error and then contact the database support if your

system administrator can not fix the error.

....

System page cache released no free blocks

System page cache still holding 186 pages in 2 splitted blocks

System page cache released no free blocks

System page cache still holding 186 pages in 2 splitted blocks

trace message of SAPDBMem_RawAllocator RTEMem_Allocator:RTEMem_Allocator : could not allocate memory,_FILE=SAPDBMem_RawAllocator-k.cpp,_LINE=1194

trace message of SAPDBMem_RawAllocator RTEMem_Allocator:required : 336,_FILE=SAPDBMem_RawAllocator-k.cpp,_LINE=1194

trace message of SAPDBMem_RawAllocator RTEMem_Allocator:allocated : 0,_FILE=SAPDBMem_RawAllocator-k.cpp,_LINE=1194

trace message of SAPDBMem_RawAllocator RTEMem_Allocator:supplement : 1048576,_FILE=SAPDBMem_RawAllocator-k.cpp,_LINE=1194

trace message of SAPDBMem_RawAllocator RTEMem_Allocator:limit : -1,_FILE=SAPDBMem_RawAllocator-k.cpp,_LINE=1194

[lbreddemann · Accepted solution]

> I hava analyzed the mentioned file and found the following messages. There are some problems with the memory settings on AIX. Could you give me any recommendation which parameter to set on which value?

> Maximum number of processes: 1024

> Maximum core file size: 0 MB

> Maximum number of open files: 32000

> Maximum file size: unlimited

> Maximum number of threads: 32767

> Maximum stack size: 4096 MB

> Maximum virtual memory size: unlimited

> Resident set size: 32 MB

> Maximum heap size: 128 MB

>

> Requested memory size exceeds available heap size

> ACTION:

> Contact your system administrator. Show him the error

> message which points to an operating system configuration

> error and then contact the database support if your

> system administrator can not fix the error.

If that's no something!

Just one reply ago you didn't know about the knldiag and now you're already knee-deep in analysing memory allocation issues.

Well done!

Ok, the problem here are the process limitation that are imposed to the MaxDB kernel process.

With e.g. a maximum heap size of 128 MB there is not much space for the Cache of the database and/or for the user thread memory.

Please review

SAP Note 628131 SAP DB / MaxDB operating system parameters on Unix

and make sure that the ulimit settings are set to unlimited.

best regards and keep on learning!

Lars

[Former Member · Accepted solution]

Hi Lars,

many, many thanks for your help!

The problem is solved. The <SID>adm user has to be set to "ulimit -d unlimited".

Best regards

Matthias

[Former Member · Accepted solution]

HI!

I have the same problem on my LCA database.

This is my scenario

MaxDB version: 7.7.04.32

AIX version: AIX myapodb 1 6 00CC6E914C00

Unfortunately my OS users have all the ulimit set to "unlimited".

I have checked: SIDadm and sdb users.

But if I try to start the LCA DB from LC10 I receive this errors:

___ Stopping GMT 2011-02-10 10:49:27           7.7.04   Build 032-133-214-176
--- Starting GMT 2011-02-10 10:49:42           7.7.04   Build 032-133-214-176
SAPDBMem_RawAllocator-k.cpp:1194
trace message of SAPDBMem_RawAllocator RTEMem_Allocator:RTEMem_Allocator  : could not allocate memory
SAPDBMem_RawAllocator-k.cpp:1194
trace message of SAPDBMem_RawAllocator RTEMem_Allocator:required   : 336
SAPDBMem_RawAllocator-k.cpp:1194
trace message of SAPDBMem_RawAllocator RTEMem_Allocator:allocated  : 0
SAPDBMem_RawAllocator-k.cpp:1194
trace message of SAPDBMem_RawAllocator RTEMem_Allocator:supplement : 1048576
SAPDBMem_RawAllocator-k.cpp:1194
trace message of SAPDBMem_RawAllocator RTEMem_Allocator:limit      : -1
SAPDBMem_RawAllocator-k.cpp:1194

Any idea ?

Regards

Pierfrancesco