System tasks of work items that existed on a system prior to SAS^® Drug Development 4.4 do not work after the system is upgraded to either SAS^® Drug Development 4.4 or 4.5.1 (upgrade of SAS 9.3 to SAS 9.4). The behavior observed was that the work items were “stuck” on the system tasks that were activated. New work items with system tasks created after the upgrade work correctly.

The cause of this issue is due to a change introduced by the SAS^® 9.4 upgrade by SAS^® Workflow Service. Task identifiers were changed (“unqualified”) by the workflow service in SAS^® 9.4. The SAS^® Drug Development stores these task identifiers as task scoped internal Data Objects for use in call backs to SAS^® Drug Development through HTTP Request policies of system tasks. Since these identifiers changed, the call backs from system tasks were not working.

This issue is addressed by updating the old task identifiers in the data objects table with the new ones from the SAS^® 9.4 process table by correlating the tasks using the unchanged real_id.

The steps to fix the issue are as follows:

1. Perform a shutdown of all SAS^® tcServer processes (sddserveradmin, sddserver1, sddserver2, and so on)
2. Perform a shutdown of all SAS server processes on the SAS^® Metadata Server (WIP) and SAS^® processing server machines (ex: /sso/biconfig/940/Lev1/sas.servers stop)
3. SAS^® Drug Development Database Administrator Tasks:
   1. Execute the upgrade_9.3_to_9.4_wf_taskid_operands.sql script found in the Downloads tab on this note. This script generates SQL update statements to be used in Step 3.b. This script should be run as the Oracle SYSTEM user and assumes the schema’s below are defined. If those schema names are not used, update the upgrade_9.3_to_9.4_wf_taskid_operands.sql script with the schema names that were used.
      • SAS 9.3 – SASWF1
      • SAS 9.4 – SAS94WF1
   2. Execute the generated SQL update statements that were produced in Step 3.a.
4. Perform a start-up of all SAS server processes on the SAS Metadata Server (WIP) and SAS processing server machines (ex: /sso/biconfig/940/Lev1/sas.servers stop)
5. Perform a start-up of all SDD tcServer processes (sddserveradmin, sddserver1, sddserver2, and so on)

Within SAS^® Drug Development, restart the work items with system tasks that were in the stuck state to verify that they complete.

Operating System and Release Information

Product Family	Product	System	Product Release		SAS Release
			Reported	Fixed*	Reported	Fixed*
SAS System	SAS Drug Development	Linux for x64	4.4	4.4	9.4 TS1M1	9.4 TS1M1

* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.

---

upgrade_9.3_to_9.4_wf_taskid_operands.zip

Type:	Problem Note
Priority:	medium

Date Modified:	2015-07-17 13:47:51
Date Created:	2015-07-16 16:59:13