My Oracle Support Banner

Account Analysis - (180 Char) Error: JVMCI161: FATAL ERROR in native method (Doc ID 1300008.1)

Last updated on DECEMBER 22, 2023

Applies to:

Oracle Application Object Library - Version 12 to 12.1.3 [Release 12 to 12.1]
Information in this document applies to any platform.
GLACTANL2, Account Analysis - (180 Char), JVMCI161, FATAL ERROR, Wrong method ID used
 


Symptoms

Even after the application of patch 9726201 and setting the environment variable CA_FILEIO_64 to "YES", when running the General Ledger "Account Analysis - (180 Char)" report for the full account range for a month, the following for error occurs:

stat_low = 86
stat_high = 0
emsg:was terminated by signal 6
Enter Password:
JVMCI161: FATAL ERROR in native method: Wrong method ID used to invoke a Java method
at oracle.reports.engine.EngineImpl.CRunReport(Native Method)
at oracle.reports.engine.EngineImpl.run(EngineImpl.java:437)
at oracle.reports.server.JobManager.runJobInEngine(JobManager.java:969)
at oracle.reports.server.ExecAsynchJobThread.run(ExecAsynchJobThread.java:54)

Report Builder: Release 10.1.2.2.0 - Production on Fri Jun 18 11:36:22 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.

JVMDG217: Dump Handler is Processing Signal 6 - Please Wait.
JVMDG303: JVM Requesting Java core file
JVMDG304: Java core file written to /applcommon01/<SID>/log/<SID>/javacore2424916.1276880474.txt
JVMDG215: Dump Handler has Processed Error Signal 6.

 


Note: The same report runs and completes successfully with a smaller selection

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
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.