Tables created by Pega are using incorrect tablespace
Tables created by Pega for data classes and data pages are not using the tablespace that is expected in a DB2 environment.
They are supposed to go to a custom userspace.
Steps to Reproduce
The steps to reproduce this issue is not known.
Unlike with the Oracle database the DB2 database does not allow you to specify a default tablespace for a user’s tables to be added to.
There are ways to force the creation of tables in the tablespace that user want by specifying the tablespace in the create command or by restricting which tablespaces the user has privileges to write to.
From within the Pega Platform there is currently no way to specify what tablespace user requires the schema tables to be created in.
And in this case the tables were in the correct schema but not in the tablespace that user required.
Local-change is to migrate the tables from an environment into the correct tablespaces using in-house DB2 tools.
This should be done prior to loading the application Rule-Admin-Product (RAP) in case if it is applicable to the migration method.
This will ensure the correct tablespaces are used going forward.
Alternatively, perform the following resolution steps:
1. Backup the table data.
2. Remove and recreate the table outside of Pega with the correct tablespace.
3. Migrate the data back.
Note:In addition, enhancement request FDBK-5604 has been opened for this to be conisdered for inclusion in a future release.