How to stop a manual report while it is running

[cspadola]

Occasionally we have an issue with 1-2 of our reports taking a long time to run. This could be a result of a few different causes but nonetheless, we would like to know if it is possible to stop a manually run report from running after it has been submitted by the user to run.

I can go into View Scheduled Jobs in the Reporting menu and view the current jobs and it will show me the report that is taking too long to run. However, it does not give me the option to stop the report from that menu.

Is there anywhere in OTM that this can be done? Simply closing or logging out of the session does not stop the report from continuing to run.

Thanks.

[nick.polites]

Re: How to stop a manual report while it is running

You'll need to kill the report using the Oracle Reports interface. This can be done by accessing the URL your Oracle Reports instance is running eg. reports.company.com:7777/reports/rwservlet/killjobid22?server=RepServer

Where 22 is the Job Number and server= is your Oracle Reports ID.

[cspadola]

Re: How to stop a manual report while it is running

Hi Nick...is it possible to access this servlet and have it show all the reports that are running? I don't know the report job number.

I tried to access using http://<server>:7777/reports/rwservlet but the page does not display.

Thanks

[nick.polites]

Re: How to stop a manual report while it is running

The jobid can be acquired from the running processes when you are viewing the scheduled jobs link. You won't be able to access the reports server URL directly if it is behind your firewall. You'll need to talk to your sysadmins about obtaining access to that URL. Also the port may not be 7777 which is the default port. You’ll need to check your glog.properties file to confirm what port is configured.

[cspadola]

Re: How to stop a manual report while it is running

Hi Nick...very good info, thanks.

I can tell I won't be able to access our rpeort server URL directly. When I check the properties file, it is hitting the report server using a different FQDN than the one I use to SSH to it from my location. I am unable to connect to the FQDN which means I will probably have to be granted access through the firewall. I am in a different physical location from where our servers are.

Thanks for your help on this.