My Oracle Support Banner

MGW gateway fails on startup with ORA-28576 after altering MGW memory parameters (Doc ID 391517.1)

Last updated on MARCH 06, 2019

Applies to:

Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
IBM AIX on POWER Systems (64-bit)
Checked for currency 02-Aug-12



Symptoms

MGW fails to start and shows the following error on MGW_GATEWAY view:

ORA-28576: lost RPC connection to external procedure agent

For example, on AIX5L Based Systems (64-bit)  the MGW.LOG file displays similar information:

Unable to alloc heap of requested size, perhaps the maxdata value is too small
- see README.HTML for more information.
Unable to allocate an initial java heap of 536870912 bytes.
**Out of memory, aborting**

*** panic: JVMST016: Cannot allocate memory for initial java heap

Changes

Problem occurs after an attempt of increasing the max_memory parameter for the agent

BEGIN DBMS_MGWADM.ALTER_AGENT (
max_threads => 3
,max_connections => 3
,max_memory => 512);
END;
/

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.