MWA Memory Usage (Doc ID 1499898.1)

Last updated on DECEMBER 04, 2014

Applies to:

Oracle Mobile Application Server - Version 12.1.1 to 12.1.3 [Release 12.1]
Information in this document applies to any platform.
Performance

Symptoms

   Customer is reporting that they are having a very high memory usage on database server coming from MWJDBC:
 
 

  SID       SERIAL    USERNAME   MACHINE   PROGRAM              NAME                  TOTAL(MB)   HASHVALUE   MODULE
  ------    -------   --------   --------  -----------------    -------------------   ---------   ----------  ---------
   340      18269      APPS      auohs35   JDBC Thin Client     session pga  memory   1875        0            MWAJDBC
  4591      43021      APPS      auohs35   JDBC Thin Client     session pga  memory   1875        0            MWAJDBC
  2071      64629      APPS      auohs35   JDBC Thin Client     session pga  memory   1874        0            MWAJDBC
  1582      18921      APPS      auohs35   JDBC Thin Client     session pga  memory   1868        2762973842   MWAJDBC

 
 
  The memory is already at 1.8G of memory when first starting the transaction.
  They are having to bounce MWA 3 or 4 times a day because of this issue.
  After the user disconnects, the memory does not get released, and they have to bounce MWA before the memory gets released.
 
  Warehouse Management responsibility and go trough Tasks > Direct Tasks > Intercalled Tasks > Accept Any Tasks
 
  WORKAROUNDS
  ===========
  Bounce MWA


Changes

 Upgraded to R12.1.X

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms