This is an archive of the Maximo Yahoo Community. The content of this pages may be a sometimes obsolete so please check post dates.
Thanks to the community owner Christopher Wanko for providing the content.
Hello everyone,
Here is what I'm working on, I was in workflow designer and I created a new revision to my PURCHREQ workflow to make some changes, it created revision 13. My changes didn't work so I deleted the process revision 13. Now when I go back to create a new revision I get an error.
Here is what the error says:
Database error number 2601 has occurred when operating on WFASSIGNMENT Assignment=1 Process=PURCHREQ Process Revision=13 Workflow ID=0 Node ID=5.
[PRSEAMS] Cannot insert duplicate key row in object
'dbo.wfassignment' with unique index 'wfassign_ndx1'
Has anyone come across something like this and if so how can I fix it?
Maximo 6.2.1
Weblogic
SQL Server 2005
thx,
mrggutz
Hi George: I have run across that issue before. If I recall correctly,
it's fixed in a later patch, but in the mean time, you need to run the
following against the database:
Delete from wfassignment where processed = 'PURCHREQ' and processrev = 13
Note: this assumes you have no transactions related to this revision
(although if you're able to delete it, you shouldn't have any).
Shannon
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of
George
Sent: April-11-12 5:05 PM
To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] Process Revision Issue
Hello everyone,
Here is what I'm working on, I was in workflow designer and I created a new
revision to my PURCHREQ workflow to make some changes, it created revision
13. My changes didn't work so I deleted the process revision 13. Now when I
go back to create a new revision I get an error.
Here is what the error says:
Database error number 2601 has occurred when operating on WFASSIGNMENT
Assignment=1 Process=PURCHREQ Process Revision=13 Workflow ID=0 Node ID=5.
[PRSEAMS] Cannot insert duplicate key row in object
'dbo.wfassignment' with unique index 'wfassign_ndx1'
Has anyone come across something like this and if so how can I fix it?
Maximo 6.2.1
Weblogic
SQL Server 2005
thx,
mrggutz