[Info-vax] InnoDB memory issue in MariaDB

[issinoho]

On Friday, 9 October 2020 at 17:59:57 UTC+1, issinoho wrote:
> On Friday, 9 October 2020 at 17:57:50 UTC+1, 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? 
> > 
> > TIA as always.
> Additionally from the [.log]aria_log.00000001 
> 
> %TYPE-F-WRITEERR, error writing SYS$OUTPUT:.; 
> -RMS-F-SYS, QIO system service request failed 
> -SYSTEM-F-EXQUOTA, process quota exceeded

Asked and answered... process limits of the account needed to be increased to match those of the MYSQL051_SRV account.