ManuelRodriguez
IS-IT--Management
Hello everyone,
This is my first tip that I am posting here. This should be very helpful to those that use Cognos with MSSQL Server.
We all know how dangerous it is to stop a go-to-production process while it's running. If one of your users has ever decided to stop or cancel a go to production process (cut down, reconcile, etc) unwisely, this may cause any number of events to occur. Also it will cause some locks on your tables and restrict the user from going to the access rights of contributor. Here is a simple process and script that cleans up all tasks left over from that process.
1. Open up a query analyzer session connecting to your server containing the pad that you use in Contributor.
2. First check to see everything that is in the rwobject table of the pad database:
select * from pad_name.dbo.rwobject where roobjecttypeid = 'Job_Task'
Remember to replace the pad_name with the name of your pad.
3. Now delete all the ones that are found:
delete from pad_name.dbo.rwobject where roobjecttypeid = 'Job_Task'
4. And your done, stop and restart the ep planning service and the planning73 com service and try the go-to-production again.
Hope this helps anyone that goes encounters this issue.
This is my first tip that I am posting here. This should be very helpful to those that use Cognos with MSSQL Server.
We all know how dangerous it is to stop a go-to-production process while it's running. If one of your users has ever decided to stop or cancel a go to production process (cut down, reconcile, etc) unwisely, this may cause any number of events to occur. Also it will cause some locks on your tables and restrict the user from going to the access rights of contributor. Here is a simple process and script that cleans up all tasks left over from that process.
1. Open up a query analyzer session connecting to your server containing the pad that you use in Contributor.
2. First check to see everything that is in the rwobject table of the pad database:
select * from pad_name.dbo.rwobject where roobjecttypeid = 'Job_Task'
Remember to replace the pad_name with the name of your pad.
3. Now delete all the ones that are found:
delete from pad_name.dbo.rwobject where roobjecttypeid = 'Job_Task'
4. And your done, stop and restart the ep planning service and the planning73 com service and try the go-to-production again.
Hope this helps anyone that goes encounters this issue.