10g Report service.

Question

hi,
I am unable to restart 10g report service. My report server is hanging most of the time. I am using spreadsheet in reports. if the report data is big the report service hangs.
I tried to restart the report service from the Application server, but i could not.
i have even tried the Below command. but i am getting Rep-0238 authentication failed. please help.
C:\oracle10g\FRHome_1\opmn\bin>rwserver server= rep_dbserver_frhome1 shutdown=n
ormal authid=system/<pass>

Answer 1

locate your report_service_name.conf file under $ORACLE_HOME/reports/conf directory and set engine parameters as follows:
initEngine
Default: 1
The number of engines you want Reports Server to start at initialization.
The server process will spawn this many engines when it is started.
maxEngine
Default: 1
The maximum number of this type of engine that can run on the server at any time. The server process will attempt to keep no more than this many engines active. Ensure that you have sufficient memory and resources available to accommodate these many engines.
Recommendations : Per CPU you can have a maximum of 4 engines running. (For multi core -dual / quad core, etc - please refer to Note:738920.1)
minEngine
Default: 0
The minimum number of this type of engine that is maintained by the server at all times. The server process will attempt to keep at least this many engines active. This should not be more that the initEngine value, it may be less than or equal to initEngine.
Recommendations : If the workload is very steady and generally keeps the engines busy all the time, the minengine and maxengines values should be close together e.g within a difference of one to three engines.
If the workload is intermittent, not constant or consistent, lower the minengine (and possibly initengine too) value, especially if the host machine is running other applications besides Oracle Reports.
engLife
Default: 50
The number of jobs the engine can run before the engine is terminated, and, if necessary, a new engine is started. This feature is available to thwart memory leaks.
Setting engLife="1" will recycle engines after each job they run, but this will also lead to performance issues since for each submitted job, the server will start the engine first and then run the job. Whereas, a large value for engLife can cause the runtime engine to use up enough memory to cause a crash.
maxIdle
Default: 30
The number of minutes of allowable idle time before the engine is shut down, provided the current number of engines is higher than minEngine. For example, if minEngine is 0, maxIdle is 30, and one engine has been running but unused for 30 minutes, that engine will shut down. If, under the same conditions, minEngine is 1, the active engine will not shut down, even if it has been idle for 30 minutes.
There is a bug (internal) in this, which states: all idle engines shutdown after maxidle is reached and then specified number are restarted to honour minengine.
callbackTimeOut
Default: 60000
The number of milliseconds of allowable waiting time between when the server launches an engine and the engine calls the server back. If the engine does not respond by this time, the reports server assumes the engine got hung or otherwise failed to completely initialize, and if the engine process is still present when this times out, the reports server will kill it and try again.
Recommendations : If the machine that hosts the server is very fast, you can reduce this number for faster performance. Server will wait for time specified for the engines to connect to it, and then it will shut itself down if they fail to do so. A common error occuring in this scenario is :
"REP-56097 Engine callback timed out"
In case of this error, callbacktimeout value should be increased.
you need to restart the reports service after any modification