Databases that require specific privileges to access another schema

Databases must have specific privileges to access data in another schema. You must have these privileges for the migration because the process reads the data in the old schema to copy it to the new schema.

For the supported databases, an administrator must execute the script that creates the required role. For a list of the supported databases, see IBM® Operational Decision Manager detailed system requirements.

With Oracle, after the role is created and granted to a user, it is not automatically available to open connections, which retain the previous role privileges. Consequently, you must restart Decision Center after the administrator grants the role to the data source user. Alternatively when using WebSphere® Application Server, clear the connection pool instead of restarting the application.

If you do not restart, Decision Center might use a connection from the application server cache. This old connection does not get the new role privileges, and so the migration script cannot be executed through Decision Center.