cancel
Showing results for 
Search instead for 
Did you mean: 

Memory Error while starting MaxDB

Former Member
0 Kudos

Hi,

I have a fresh installation liveCache 7.6.0 Build 29 on AIX.

Just after the installation, while giving command db_admin or db_warm, I'm receiving below error : (from log file knldiag.err)

2007-07-09 11:55:24 --- Starting GMT 2007-07-09 09:55:24 7.6.00 Build 029-123-130-265

2007-07-09 11:55:28 1 ERR 8 RTEMem No more system pages for 12288 bytes available,BYTE_SIZE=4096,DESCRIPTION=valloc,ERRORTEXT=ENOMEM ? out of memory

2007-07-09 11:55:28 1 ERR 11 RTEMem + Used 130539520 bytes from system heap with a limit of system imposed limitation bytes,ALLOC_COUNT=24,FREE_COUN

2007-07-09 11:55:28 1 ERR 11 RTEMem + T=0,ERROR_COUNT=255,BYTES_MAX_USED=1077141504

2007-07-09 11:55:28 1 ERR 11872 MEMORY Not enough memory for I/O buffer cache wanted : 1048576 kB!

2007-07-09 11:55:29 0 ERR 12006 DBCRASH Kernel exited without core and exit status 0x200

2007-07-09 11:55:29 0 ERR 12010 DBCRASH Kernel exited exit code 2

2007-07-09 11:55:29 ___ Stopping GMT 2007-07-09 09:55:29 7.6.00 Build 029-123-130-265

memory usage is as below :

Memory Use Physical Virtual

% Used 82.3% 4.7%

MB Used 13489.7MB 2610.3MB

MB Free 2893.8MB 52685.7MB

Total(MB) 16384.0MB 55296.0MB

Any idea?

Best Regards,

Gökhan

Accepted Solutions (1)

Accepted Solutions (1)

markus_doehr2
Active Contributor
0 Kudos

Fist, I´d check, if the required operating system patchlevels are there:

Note 720261 - System requirement AIX - liveCache/MaxDB 7.4, 7.5, 7.6

Also check if the OS kernel parameters are set correctly:

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

Basically, this seems to be your error since the system can´t allocate enough memory. Also check the ulimits of the user starting the x_server (see above note also).

--

Markus

Former Member
0 Kudos

Hi Markus,

Thanks for the recommendations. I'll check those notes.

But as an info, there are also 2 other liveCache servers running on the same server.

On is 7.4.3 Build 38, the other is 7.6.0 Build 29.

I'll also check the limits of x_server starter user.

Kind Regards,

Gökhan

Former Member
0 Kudos

Hi Markus,

Thanks for the tip.

Either your of increasing the user limits or stopping all other liveCaches and starting up the new installed one, or both solved the problem.

Kind Regards,

Gökhan

Answers (1)

Answers (1)

TTK
Employee
Employee
0 Kudos

Hello Gökhan

For me, it looks like, that some memory depending parameters are set too high. How are CACHE_SIZE, MAXUSERTASKS etc. set?

Regards Thomas

Former Member
0 Kudos

Hi Thomas,

General Parameters

CACHE_SIZE 131072

INSTANCE_TYPE LVC

KERNELVERSION KERNEL 7.6.00 B

LOG_MIRRORED NO

LOG_SEGMENT_SIZE 87381

MAXBACKUPDEVS 2

MAXCPU 1

MAXDATAVOLUMES 11

MAXLOCKS 300000

MAXLOGVOLUMES 2

MAXUSERTASKS 34

MCOD NO

OPMSG1 /dev/console

Extended Parameters

DATACACHE_RGNS 48

_MAXEVENTS 100

MAXMESSAGE_FILES 64

OMSREGIONS 16

ROWRGNS 8

TABRGNS 8

TRANSRGNS 8

_UNICODE YES

UTILITYPROTFILE dbm.utl

Supp. Parameters

WORKDATASIZE 8192

WORKSTACKSIZE 8192

Kind Regards,

Gökhan