When you export a very large application or export from a very active process center, the export time might take over an hour. The export process might even fail or result in an incomplete file.
Diagnosing The Problem
Check the following key points to resolve this problem:
- Verify that the user, who is exporting the application, is a local user or LDAP user.
- Examine the row count size of the LSW_PO_VERSIONS table.
- Obtain a list of indexes in the LSW_PO_VERSIONS table.
- Obtain the current size of the buffer cache and the shared pool size for the database.
Resolving The Problem
Apply these settings to the process center. The indexes and database cache sizes are applicable to Process Server as well.
There are several resolutions to this problem. You might need to address one or all of the following resolutions to decrease the time to export an application:
- If a local user export is faster, apply the fix for APAR IC91473, which is available through the following links in Fix Central:
- The growth of the LSW_PO_VERSIONS table is normal and expected. When the row size reaches 2 million rows or more, the time to export an application can increase. Each save to an asset in the process designer is a new row in this table. The following indexes can assist with the speed of the export process. Add the indexes and have the database server process these indexes before running the export process again.
- CREATE INDEX IDXA_PO_VERSIONS ON lsw_po_versions
(PO_TYPE,BRANCH_ID,START_SEQ_NUM,END_SEQ_NUM,PO_VERSION_ID) COMPUTE STATISTICS;
- CREATE INDEX IDXB_PO_VERSIONS ON lsw_po_versions
- CREATE INDEX IDXC_PO_VERSIONS ON lsw_po_versions
(BRANCH_ID,START_SEQ_NUM,END_SEQ_NUM) COMPUTE STATISTICS;
- CREATE INDEX IDXD_PO_VERSIONS ON lsw_po_versions
(BRANCH_ID,END_SEQ_NUM,PO_TYPE,PO_ID) COMPUTE STATISTICS;
- CREATE INDEX IDXE_PO_VERSIONS ON lsw_po_versions
- The database also needs to have adequate cache space. The buffer cache should be 2 GB or more. The shared pool size should be 1 GB or greater.
15 June 2018