Databases that require specific privileges to access another schema

Databases other than Derby must have specific privileges to access data in another schema. You must have these privileges for the migration because the process reads the data from the old schema to copy it to the current schema.

For DB2, MySQL, PostgreSQL, Oracle, SQL Server and Sybase databases, an administrator must execute the script that creates the required role.

With these databases, after the role is created and granted to a user, it is automatically available, which means that this user retains the role privileges for any new connection. Consequently, you must restart Decision Center after the administrator grants the role to the data source user.

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.