All database tables used by Moves are being migrated to their own schema (MOVESMGR). The tables are in two groups:

  1. Tables specific to Moves (e.g. stack definitions)
  2. Tables used by OS Workflow (e.g. Moves workflow history)

[Note that OS Workflow tables also exist in INFRAMGR - those tables are for use by all other (i.e. not Moves) apps using OS Workflow.]

Because the OS Workflow tables now exist in two separate schemas (INFRAMGR and MOVESMGR), we must take care to use the correct database synonyms to point to the right set of tables.

Creating and Removing Private Synonyms for OS Workflow tables

Just to clarify: if you are running Moves locally (on your workstation), you need private synonyms created under your database account for the OS workflow tables. The SQL statements to create the synonyms are:

– Sequence
CREATE SYNONYM HIBERNATE_SEQUENCE for MOVESMGR.HIBERNATE_SEQUENCE;
– Tables
CREATE SYNONYM OS_CURRENTSTEP for MOVESMGR.OS_CURRENTSTEP;
CREATE SYNONYM OS_HISTORYSTEP for MOVESMGR.OS_HISTORYSTEP;
CREATE SYNONYM OS_PROPERTYENTRY for MOVESMGR.OS_PROPERTYENTRY;
CREATE SYNONYM OS_WFDEFINITION for MOVESMGR.OS_WFDEFINITION;
CREATE SYNONYM OS_WFENTRY for MOVESMGR.OS_WFENTRY;

A downloadable script for creating the synonyms is also provided here.

Similarly, if you are running an OS Workflow app that is not Moves (e.g. IAP, ETP), you should make sure you do NOT have these private synonyms defined for your database account. To remove the synonyms, this is the SQL:

– SequenceDROP SYNONYM HIBERNATE_SEQUENCE;
-- Tables
DROP SYNONYM OS_CURRENTSTEP ;
DROP SYNONYM OS_HISTORYSTEP ;
DROP SYNONYM OS_PROPERTYENTRY ;
DROP SYNONYM OS_WFDEFINITION ;
DROP SYNONYM OS_WFENTRY ;

A downloadable script for removing the synonyms is also provided here.