I have more than 300 scheduled IWR reports.
I need to bring the IWR server online after an extended shutdown period. This means that all scheduled jobs would be due as soon as the server is up.
So whenever I bring the servers back up a tremenduous load gets placed on it as all report processes and queues fill up immediately with the backlog.
Is there any way I can disable or stagger the schedules without actually going to individual reports and disabling them.
NKT
This info is probably stored in one of the IWR .db files, maybe iwr71job.db. Open with a benign text editor and look for the scheduling info. If you find it you should be able to modify it.
Sorry, that wont work if the file is too big. Also it is a mixture of binary and text data. I believe you can rename this particular file (after stopping the IWR service/s) and a new one will be created when the services are restarted.
Hi Blue
Yes the information is stored in a db file called iwr71sm.db or something like that.
It is a binary file.
I thought about splitting the DB into multiple parts so that at the time of server startup, jobs will be executed one part at a time.
However I am not sure how I can split the database. Also this is a production and a legacy system at the same time so I would rather not meddle around with databases.
NKT
Have you tried changing the IWR Scheduler Grace Period to 0?Ã, If not, IWR will attempt to process all missed scheduled events and reports within the defined period as soon as it comes back up, which is what seems to be your problem.
To change it, get to a command prompt, and enter
iwrconfig -attr schedulergraceperiod=0
The value (0) is the length of the grace period in hours.
To see the current setting without changing anything, enter
iwrconfig -attr schedulergraceperiod
This will display the currently configured value.
The iwrconfig command is located within Program Files\Cognos\cer4\bin so you may need to sit in this folder to run the commands above.
Once you have disabled the grace period, it's then an easy job to fire off your events one by one from the command line:
iwrruncmd event "<youreventname>"
This will then allow you more control over how your events are run, and you will be able to leave appropriate intervals to allow the IWR server to process the reports from one event before you fire off the next.
Best regards,
MF.
Hi MFGF
Thank you for your response. Appreciate your help.
Regards
NKT