cancel
Showing results for 
Search instead for 
Did you mean: 

[ASE Upgrade] From 15.5 to 16.0 (kernel kistartup: could not create shared memory)

marcin_najs
Explorer
0 Kudos

Hi.

I have a problem with upgrade from ASE 15.5 to ASE 16.0 (Linux 64bit).

Problem occurs when I am trying to start ASE 16.0 (with device master from 15.0) to perform 'upgrade' manually.

I use upgrade method from manual: Manually Upgrading SAP ASE

When I want to start new ASE 16.0 with master device from 15.5 to perform upgrade script I get:

The current 'max memory' value '30408704' is less than the 'total logical memory' value '1111040339'. ASE has increased the value of configuration parameter 'max memory' to '1111040339' to enable upgrade.

WHY...?

My 15.5 server runs fine with max_memory=30408704 (with 64GB RAM).

During upgrade ASE 16.0 tries to allocate more than 2TB of memory ?!?!

I read information from:

http://service.sap.com/sap/support/notes/1959916

I have tried to:

1. Reboot server

2. Turn off HugePages

3. Turn off "allocate max shared memory" parameter

4. Decrease all memory parmaeters (like data /proc /stmt caches)

5. Reset shmmax (from systcl.conf) to higher values

...

but ASE 16.0 always attempts to allocate HUGE amount of memory:

server  The configured value '6396' for parameter 'kernel resource memory' is too low. It should be atleast '10860' for the present configuration.

server  kernel resource memory' has been modified from '6396' to '10860' by the verification routine.

server  The current 'max memory' value '1111040339' is less than the 'total logical memory' value '1111044804'. ASE has increased the value of configuration parameter 'max memory' to '1111044804' to enable upgrade.

kernel  os_create_region: can't allocate 2199023255552 bytes

kernel  kbcreate: couldn't create kernel region.

kernel  kistartup: could not create shared memory

I have tested upgrade process on machine with 4GB of RAM and it worked perfecly.

I would be grateful for any help.

Regards

--

Marcin

marcin_najs
Explorer
0 Kudos

Mark,

Thank you for answer.

We do not make any manual changes in conf. file - only through sp_configure...

I added a CFG file as an attachment.

Regarding conf. file, I thought the same - it may be an invalid parameter unit (which differs between version 15.5 and 16.0).

I will try to reset more parameters to DEFAULT and check if it helps.

Regards.

--
Marcin

marcin_najs
Explorer
0 Kudos

Mark,

I have found parameter causing problem with allocation in 16.0.

user log cache size = 4194304

It is specified in bytes so I have no idea why it caused a problem.

When I switched it do DEFAULT, ASE booted without errors...

--

Marcin

jayrijnbergen
Active Participant
0 Kudos

the memory required for setting of user log cache size is related to the number of user connections

if you have configured a lot of user connections, then this amount of user log cache needs a lot of memory

why it's working in your 15.x version, no idea

btw. I don't know your app, but that's quite a HUGE size for a user log cache

the user log cache is flushed as soon as your transaction completes, you might be wasting a lot of memory

marcin_najs
Explorer
0 Kudos

Jeroen,

I think it was overconfigured after all...

ASE has 200 user connections configured (Small B. edition).

It seems that ASE 16.0 acts differently with this parameter.

After resetting this I was able to upgrade to 16.0 without problems.

Regards,

--

Marcin.

Former Member
0 Kudos

Jeroen,

Yes, the procedure cache configuration was HUGE...

Apparently, resetting it has fixed the problem, however, it is important that Marcin report this discrepancy to SAP Technical Support as the configuration parameter ironically works on an earlier version of the software.

Regards,

Jean-Pierre

Accepted Solutions (0)

Answers (0)