Preparing to convert the IBS_SPEC_ASSIGNMENTS table
Prepare your database before you convert the IBS_SPEC_ASSIGNMENTS table.
About this task
Procedure
-
Make sure that your IBM
TRIRIGA Application Platform
build number is the same as the build number of the Module Level Associations (MLA) converter.
- Perform your normal platform-upgrade regression testing.
- Make sure that your applications behave as expected. Validate the upgrade before you start the MLA conversion.
-
Create a backup of your current database before you run the converter in your working
environment.
- You cannot reverse this conversion process. The only way to return to the single IBS_SPEC_ASSIGNMENTS table is to restore it from your backup.
- The database that you use must be comparable in size to the database that you use in a production environment.
- The length of time that the conversion process takes is proportional to the capabilities of the database server, the chunk size, and the size of your IBS_SPEC_ASSIGNMENTS table.
- In tests, the conversion took between four to ten hours on a large IBS_SPEC_ASSIGNMENTS table. The same conversion took days when run on a low-powered database server.
-
Make sure that your database server has enough memory and disk space to perform the
conversion.
- Make sure that your database server has enough available disk space for the conversion. Available space must be at least double the size of the IBS_SPEC_ASSIGNMENTS table.
- The conversion is a resource-intensive process.
- Make sure that your database adheres to Best practices for optimizing performance.
- Test your database I/O speed and connection with the Performance Monitor in the Administrator Console. The database test results return are highlighted in green.
- Run this converter in a supported database type: Oracle or Db2. Currently, this converter does not support Microsoft SQL Server.
- Make sure that your database does not have any customized configurations for IBS_SPEC_ASSIGNMENTS. These customized configurations include partitioning, materialized views, triggers, and other configurations.
-
Make sure that your IBM®
TRIRIGA®
system does not process reverse association filters.
- The Reverse Association flag is no longer supported or allowed with queries and reports in the IBM TRIRIGA Report Manager.
- To determine whether your IBM
TRIRIGA
system still has reverse associations:
- Go to Administrator Console > Database Query Tool.
- Run the following SQL query:
Q13a Find ALL queries using reverse associations (PLATFORM_AUDIT - No Hops)
- If you do not have this query, go to the Administrator Console > MustGather Tool.
- Clear the Send Report to IBM TRIRIGA Support option.
- Clear any other fields that have testing or irrelevant data.
- Select the Perform Audit option.
- Select Submit MustGather and wait a few minutes.
- When the process is completed, you can find the query starting with Q13a in the Database Query Tool.
- If any reverse association queries are found, then determine whether they are still used, and fix or remove them before the conversion. If a query with a Reverse Association flag is encountered in a converted database, the query is run, a message is logged, and the reverse association is ignored.
- For more information, see Query and report performance.
-
If you are using Linux®, use the export command to set the
MLA_CONV_DIR environment property to equal the directory in which the converter
file resides.
- Run the command in the same terminal session from which the converter is started.
- For example: export MLA_CONV_DIR="/home/user/IBM/Tririga/tools/MLA-Converter"
-
Determine the chunk size for the conversion. By default, the chunk size is set to 100 million
records.
- To change the default value, run the following SQL statement. This example sets the chunk size
to 50 million
records:
insert into ENVIRONMENT_PROPERTIES (PROPERTY, ENVIRONMENT, VALUE) values ('isa.chunk.size', 'platform', '50000000')
- A zero chunk size means no chunking. In this case, the converter attempts to copy all the data for a particular module into its association table.
- Do not use a zero chunk size unless you have a high-end database server.
- To change the default value, run the following SQL statement. This example sets the chunk size
to 50 million
records:
- Make sure that there are no other active connections to the database that you are converting. Turn off any application servers, and any Oracle SQL Developer or IBM Data Studio sessions, that are running against the database server. If you do not turn off active connections, the conversion might fail because of a deadlock or transaction timeout.