Rep-0069: Internal Error java.lang.OutOfMemoryError Running Reports with "Page X of Y" Feature (Doc ID 859067.1)

Last updated on NOVEMBER 06, 2015

Applies to:

Oracle Reports Developer - Version 10.1.2.0.2 to 10.1.2.3 [Release Oracle10g to 10gr2]
Information in this document applies to any platform.
"Checked for relevance on 29-May-2012"
"Checked for relevance on 02-Nov-2013"

Symptoms

Running a long report that uses "Page X of Y" for pagination like the following example fails with the following error:

Example

Page F_1 / F_2

Where F_1 has a field source of "Physical Page Number" and F_2 has a field source of "Total Physical Pages"

The following error is displayed in browser:

ERR REP-0069: Internal error
java.lang.OutOfMemoryError

When Reports Trace is enabled the following trace information is recorded:

rwserver.trc

[2009/7/9 7:10:5:967] Debug 50103 (JobManager:updateJobStatus): Finished updating job: 5
[2009/7/9 7:10:8:71] State 56016 (JobManager:updateJobStatus): Job 5 status is: Running the report Formatting page 1
[2009/7/9 7:10:8:71] Debug 50103 (JobManager:updateJobStatus): Finished updating job: 5
[2009/7/9 7:10:8:72] State 56016 (JobManager:updateJobStatus): Job 5 status is: Running the report Formatting page 659
[2009/7/9 7:10:8:72] Debug 50103 (JobManager:updateJobStatus): Finished updating job: 5
[2009/7/9 7:10:10:240] State 56016 (JobManager:updateJobStatus): Job 5 status is: Running the report Formatting page 1
[2009/7/9 7:10:10:240] Debug 50103 (JobManager:updateJobStatus): Finished updating job: 5
[2009/7/9 7:10:10:240] State 56016 (JobManager:updateJobStatus): Job 5 status is: Running the report Formatting page 660
[2009/7/9 7:10:10:240] Debug 50103 (JobManager:updateJobStatus): Finished updating job: 5

From above trace information you can see report formatting page 660 and then there is no more formatting information and all the next job requests are being queued and waiting for an available engine. In this particular scenario Reports Server maxEngine was set to "1".

rwEng-0.trc

[2009/7/9 7:10:11:20] APP 50103 (C Engine): 19:10:11 APP ........ ) Text Field F_IA2
[2009/7/9 7:10:11:20] APP 50103 (C Engine): 19:10:11 APP ....... ) Frame M_4
[2009/7/9 7:10:11:21] APP 50103 (C Engine): 19:10:11 APP ....... ( Database Column IA3
[2009/7/9 7:10:11:21] APP 50103 (C Engine): 19:10:11 APP ....... ) Database Column IA3
[2009/7/9 7:10:11:21] PLSQL 50103 (C Engine): 19:10:11 PLS ....... ( Function: m_3formattrigger
[2009/7/9 7:10:11:22] PLSQL 50103 (C Engine): 19:10:11 PLS ....... ) Function: m_3formattrigger
[2009/7/9 7:10:11:22] APP 50103 (C Engine): 19:10:11 APP ....... ( Database Column IA1
[2009/7/9 7:10:11:22] APP 50103 (C Engine): 19:10:11 APP ....... ) Database Column IA1
[2009/7/9 7:10:12:190] Error 50103 (C Engine): 19:10:11 APP ....... ) Database Column IA1
[2009/7/9 7:10:12:191] Error 50103 (C Engine): 19:10:12 ERR REP-0069: Internal error
java.lang.OutOfMemoryError
[2009/7/9 7:10:12:191] PLSQL 50103 (C Engine): 19:10:12 PLS ....... ( Function: m_2formattrigger
[2009/7/9 7:10:12:191] PLSQL 50103 (C Engine): 19:10:12 PLS ....... ) Function: m_2formattrigger
[2009/7/9 7:10:12:192] APP 50103 (C Engine): 19:10:12 APP ....... ( Frame M_2
[2009/7/9 7:10:12:192] APP 50103 (C Engine): 19:10:12 APP ........ ( Text Field F_IA1
[2009/7/9 7:10:12:192] APP 50103 (C Engine): 19:10:12 APP ......... ( Database Column IA1
[2009/7/9 7:10:12:193] APP 50103 (C Engine): 19:10:12 APP ......... ) Database Column IA1
[2009/7/9 7:10:12:193] APP 50103 (C Engine): 19:10:12 APP ........ ) Text Field F_IA1
[2009/7/9 7:10:12:193] APP 50103 (C Engine): 19:10:12 APP ........ ( Text Field F_SLDO1
[2009/7/9 7:10:12:194] APP 50103 (C Engine): 19:10:12 APP ......... ( Database Column tot
[2009/7/9 7:10:12:194] APP 50103 (C Engine): 19:10:12 APP ......... ) Database Column tot

 

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