[Info-vax] InnoDB memory issue in MariaDB

Arne Vajhøj arne at vajhoej.dk
Fri Oct 9 13:16:04 EDT 2020


On 10/9/2020 12:57 PM, issinoho wrote:
> FreeAXP 4.0.0.646
> VSI AXPVMS VMS V8.4-2L1
> VSI AXPVMS TCPIP V5.7-13ECO5F
> VSI AXPVMS SSL111 V1.1-1GB
> VSI AXPVMS CSWS V2.4-38D
> PHP 7.2.29 (Berrymans)
> 
> Trying to install and run mariadb-5_5_64.zip (Berrymans)...
> 
> 201009 17:48:24 InnoDB: The InnoDB memory heap is disabled
> 201009 17:48:24 InnoDB: Mutexes and rw_locks use VMS atomic functions
> 201009 17:48:24 InnoDB: Compressed tables use zlib 1.2.11
> 201009 17:48:27 InnoDB: Initializing buffer pool, size = 128.0M
> InnoDB: mmap(136249344 bytes) failed; errno 65535
> 201009 17:48:27 InnoDB: Completed initialization of buffer pool
> 201009 17:48:27 InnoDB: Fatal error: cannot allocate memory for the buffer pool
> 201009 17:48:27 [ERROR] Plugin 'InnoDB' init function returned error.
> 201009 17:48:27 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
> 201009 17:48:27 [ERROR] Unknown/unsupported storage engine: InnoDB
> 201009 17:48:27 [ERROR] Aborting
> 
> So, is this a physical memory issue, a page/swap issue, or a database engine tuning issue?

Readme.VMS in the dist contains suggestions for account quotas.

I used:

mod mysql$server 
/fil=1000/bio=1000/dio=1000/ast=2500/enq=5000/byt=200000/pgfl=2000000

with 5.5.68 on Alpha.

Arne



More information about the Info-vax mailing list