OutOfMemory running Migration dbutil.sh

Technote (troubleshooting)


Problem(Abstract)

We are migrating the IBM WebSphere Studio Asset Analyzer database from v4.1 to v.5.1.1 and dbutil.sh -getInfo returns following error messages:
"...

JSHERER/u/jsherer/wsaadbutil>dbutil.sh -getInfo
/DB2_DS1G/usr/lpp/db2/db2810/classes/db2j2classes.zip:
SYSP.DB2.DS1G.SDSNLOD2.APF:SYSM.DB2.DS1G.SDSNLOAD.APF:SYSP.DB2.DS1G.SDSN
EXIT:SYS
P.WAS.V610.SBBOLOAD.APF
/DB2_DS1G/usr/lpp/db2/db2810/lib:/lib:/usr/lib:.:/usr/lpp/HOD/hostondema
nd/lib
nd/lib
JVM version detected: 1.4.2
JVMDG217: Dump Handler is Processing OutOfMemory - Please Wait.
JVMHP002: JVM requesting System Transaction Dump
JVMHP012: System Transaction Dump written to
JSHERER.JVM.TDUMP.JSHERER2.D080910.
T163042
JVMDG315: JVM Requesting Heap dump file
.......JVMDG318: Heap dump file written to
/u/jsherer/wsaadbutil/HEAPDUMP.200809
10.163056.50333744.phd
JVMDG303: JVM Requesting Java core file
JVMDG304: Java core file written to
/u/jsherer/wsaadbutil/JAVADUMP.20080910.1630
59.50333744.txt
JVMDG274: Dump Handler has Processed OutOfMemory.
JVMST109: Insufficient space in Javaheap to satisfy allocation request
JVMDG217: Dump Handler is Processing OutOfMemory - Please Wait.
JVMHP002: JVM requesting System Transaction Dump
JVMHP012: System Transaction Dump written to
JSHERER.JVM.TDUMP.JSHERER2.D080910.
T163101
JVMDG315: JVM Requesting Heap dump file
..
.....JVMDG318: Heap dump file written to
/u/jsherer/wsaadbutil/HEAPDUMP.20080910
.163113.50333744.phd
JVMDG303: JVM Requesting Java core file
JVMDG304: Java core file written to
/u/jsherer/wsaadbutil/JAVADUMP.20080910.1631
16.50333744.txt
JVMDG274: Dump Handler has Processed OutOfMemory.
JVMST109: Insufficient space in Javaheap to satisfy allocation request
JVMDG217: Dump Handler is Processing OutOfMemory - Please Wait.
JVMHP002: JVM requesting System Transaction Dump
JVMHP004: Transaction Dump service IEATDUMP failed with
rc=0x8 (8), reason code=0x26 (38)
Failed to write dump to dataset: JSHERER.JVM.TDUMP.JSHERER2.D080910.T1
63118
JVMDG315: JVM Requesting Heap dump file
.......JVMDG318: Heap dump file written to
/u/jsherer/wsaadbutil/HEAPDUMP.200809
10.163120.50333744.phd
JVMDG303: JVM Requesting Java core file
JVMDG304: Java core file written to
/u/jsherer/wsaadbutil/JAVADUMP.20080910.1631
23.50333744.txt
JVMDG274: Dump Handler has Processed OutOfMemory.
JVMST109: Insufficient space in Javaheap to satisfy allocation request
JVMXE001
Exception in thread "main" java.lang.OutOfMemoryError
JSHERER/u/jsherer/wsaadbutil>JSHERER/u/jsherer/wsaadbutil>
..."

My TSO region size is 2096128 (the maximum allowed).

Diagnosing the problem

It looks like they have the correct JVM version and they have set

their REGION size ok.

I did some Google searches on "java memory options on omvs"
and looked on our MVS machines.

Here's a link to some information that may pertain to this issue.

http://publib.boulder.ibm.com/tividd/td/ITPME/GI11-4200-01/en_US/HTML/p122rmst137.htm

It may be that they need to set their MAXASSIZE to something higer.

The following command can be issued by an authorized TSO user under
SDSF using the following command:

/d omvs,options

Notice that our MVS system is set to MAXASSIZE = 2147483647.

I'd be interested in seeing what their settings are, and perhaps they
could change theirs if it is not set high enough. It also may be that
the userid running the migration utility needs a higher setting.


HQX7708 ----------------- SDSF PRIMARY OPTION MENU -- 11 R
COMMAND INPUT ===>
RESPONSE=WEBEC104
BPXO043I 08.45.46 DISPLAY OMVS 968
OMVS 000D ACTIVE OMVS=(16)
CURRENT UNIX CONFIGURATION SETTINGS:
MAXPROCSYS = 900 MAXPROCUSER = 100
MAXFILEPROC = 10000 MAXFILESIZE = NOLIMIT
MAXCPUTIME = 10800 MAXUIDS = 50
MAXPTYS = 800
MAXMMAPAREA = 4096 MAXASSIZE = 2147483647
MAXTHREADS = 10000 MAXTHREADTASKS = 10000
MAXCORESIZE = 4194304 MAXSHAREPAGES = 131072
IPCMSGQBYTES = 2147483647 IPCMSGQMNUM = 10000
IPCMSGNIDS = 500 IPCSEMNIDS = 500
IPCSEMNOPS = 25 IPCSEMNSEMS = 1000
IPCSHMMPAGES = 25600 IPCSHMNIDS = 500
IPCSHMNSEGS = 500 IPCSHMSPAGES = 262144
SUPERUSER = BPXROOT FORKCOPY = COW
STEPLIBLIST =


Resolving the problem

We changed the dbutil.sh script adding a parameter in the java command (Xmx512m): java -Xmx512m -classpath lib/wsaadbutil.jar:lib/...

Rate this page:

(0 users)Average rating

Document information


More support for:

WebSphere Studio Asset Analyzer

Software version:

4.1, 4.2, 5.1

Operating system(s):

AIX, OS/390, Windows, z/OS

Software edition:

All Editions

Reference #:

1358612

Modified date:

2010-10-27

Translate my page

Machine Translation

Content navigation