[ianlo]

Hi,

Has anyone encountered this error in the course of using OTM reports? If so, any workarounds to avoid this problem?

Here are my Report Server config settings:
* Engine ID rwEng
* Initial Engines (initEngine) 10
* Maximum Engines (maxEngine) 30
* Minimum Engines (minEngine) 10
* Maximum Jobs Before Shutdown (engLife) 50
* Maximum Idle Before Shutdown (maxIdle) (minutes) 30
* Cache Size (MB) 50
Idle Timeout (minutes) 15
Maximum Connections 150
Maximum Queue Size 1000

Thanks!

[chrisplough]

Ian,

Can you post the full error that you encountered, including a stacktrace - if one exists? I've seen these types of errors in 3 cases:

1. When the OTM-defined connection pool doesn't have enough DB connections to support the current requests. This most likely isn't there case here - as this usually happens on app-server intensive processes like bulk-plans, integration, etc. This is more closely related to a previous post: http://www.otmfaq.com/forums/f14/exc...r-release-129/
2. When there aren't enough connections defined in the DB itself to support all of the connections from both OTM and Oracle Reports. The minimum recommended value is 200 (per the Admin guide), though I usually use 300.
3. When there aren't enough Oracle Reports engines to satisfy the current requests. From you config, you can run up to 30 at one time, which should be enough - though I'd need to know more about how many reports you usually run.

Hope this helps!

--Chris

[Stefano]

Hello All,
We are using ORACLE report server to implement report for our customers, but we have a lot of problem, printing large report...

• Problem of engine crash, where in reports log (extendend one) you can't understand why happens. Otherwise usually if you re-print same report after a while or after have printed another one small report , report works without problem.
• Problem of internal server error on OTM page, but report continues to work and if you control on report server control console you can see that report finish later without problem...we change our timeout parameter..but seems don't use it.
• problem of presentation in HTML format where sometimes you have rows overlapped

Looking at this situation we are asking if someone use a different rugged solution for implementing report to connect to OTM, for example Jasper??

Thanks in advance for your answer.

[ianlo]

Originally Posted by Stefano

Hello All,
We are using ORACLE report server to implement report for our customers, but we have a lot of problem, printing large report...

• Problem of engine crash, where in reports log (extendend one) you can't understand why happens. Otherwise usually if you re-print same report after a while or after have printed another one small report , report works without problem.
• Problem of internal server error on OTM page, but report continues to work and if you control on report server control console you can see that report finish later without problem...we change our timeout parameter..but seems don't use it.
• problem of presentation in HTML format where sometimes you have rows overlapped

Looking at this situation we are asking if someone use a different rugged solution for implementing report to connect to OTM, for example Jasper??

Thanks in advance for your answer.

Hi Stefano,

Which OS is your reports server on? I am using Windows 2003 Server and what I do is that I created a CMD script to be executed every 3 days (Wed and Sunday) that restarts OTM Reports Server and Oracle Reports Server. This might help resolve #1 and #2. However #3 is also what I am experiencing when my result set is very large.

Let me know if you want the CMD scripts.

[Stefano]

Hello inalo
Sorry for delay in my request, but could you send me your CMD in order to check and use it, we need to solve this problems.
Coudl I ask also your memory configuration/allocation for your WIN report server and user#

my email s.giommi@reply.it

thanks in advance

[ianlo]

Hi Stefano,

Please find the scripts as attached. I have a 4 GB RAM Windows 2003 Standard Server. The number of users using is about 5 - 10.

Hope this helps!

[ianlo]

Hi Stefano,

In addition you can create a Scheduled Tasks in Windows 2003 to call the CMD files to shutdown and restart the servers.

Goto Scheduled Tasks > Task > Run C:\Applications\Stop_GC3_Reports_server.cmd

The CMD script will stop and start the Reports Server in the correct sequence as well

Thanks!

[Stefano]

Thanks ianlo