Scenario:
After upgrading from 14.1 CP10 to IM 14.3 CP2, the administrator migrated the Task Persistence Database to a new SQL server.
After the migration, the tasks created in the old environment do not appear in the new Environment.
Release : 14.3 CP2
Component : CA Identity Manager
The original Database was configured as Environment_ID 1 and, the new Database was Environment_ID 2. This meant that data from the original system was visible to IM through VST.
To overcome this we changed the environment_id in the sequence table so when the data is migrated it retained the same Environment_ID allowing the events to be visible and then reset the environment_ID back to 2 for any subsequent environments to be created.
This approach was only suggested as this was a DEV environment. We would not recommend this approach in production as it could lead to duplicate tasksession ids.