Description:
If the TIBCO iProcess Engine (iPE) database has been exported from one Oracle version, for example 10g, and imported to another version of Oracle, for example 11g, an error during the iPE upgrade may occur during the database update section when running the uorai115_00_tok.sql script.

Symptoms:
During an upgrade, the following type of output will be displayed indicating the error log file.

Example upgrade output:

About to configure Oracle database to run TIBCO iProcess Engine
Configuring DB Users ...
Upgrading Oracle Tables (This may take some time) ...
Running upgrade script uorai115_00.sql

**********************************************
**********************************************
Possible errors located in logfile /opt/app/ipe//logs/uorai115_00-8203.tablelog
**********************************************
**********************************************

Please check the logfile before continuing.
Abort this upgrade? (Y/N - default Y) :

ERROR: Errors found during database configuration.  Exiting.
 

= = = = =

 

In the log, the following errors are reported for a number of tables:

 

create table dev2pro.attachment (
*
ERROR at line 1:
ORA-00955: name is already used by an existing object

 

 

PL/SQL procedure successfully completed.

create table dev2pro.pack_attach (
*
ERROR at line 1:
ORA-00955: name is already used by an existing object

Cause:
There appears to be an Oracle issue where if a constraint is dropped the associated index is not dropped if the schema has been
exported and imported across different Oracle versions.

In the 'uorai115_00_tok.sql' script a check is made for the existence of the index but it seems the check is performed after the
table has been renamed. Therefore the index is not dropped because the check is using the original table name and not the
renamed table name.

All supported operating systems and Oracle databases

The attached (Filename: uorai115_00_tok.zip) copy of the uorai115_00_tok.sql script has an additional check for the constraint index before the table is renamed. The updated file should replace the one supplied in the distribution set prior to performing the upgrade.

For Windows upgrades use the steps:
1. Run the setup.exe to perform the custom installation for upgrading.
2. Respond to the prompts as appropriate.
3. Once you have selected the node to upgrade you should be prompted with a "Question" message about removing custom constraints, statistics and indexes etc. At this point DO NOT press the Yes button.
4. Identify the directory associated with the TEMP system variable for the user running the upgrade, for example use the 'set' command in a command window.
5. Using File Manager for example navigate to the directory associated with the TEMP system variable identified in point 4.
6. You should have a sub-directory with the name something like "_ISTMP1.DIR" which has a sub-directory something like "_ISTMP0.DIR". In this directory should be a number the extracted installation files including the database upgrade scripts.
7. Move the current uorai115_00_tok.sql file to a location outside the temporary installation directory and replace it with the updated one supplied with this update. Ensure ownership and permissions are the same as the others and the one it replaced.
8. Continue with the upgrade by responding to the prompts as appropriate.

Database errors during upgrade of the TIBCO iProcess Engine version 11.5 when running the uorai115_00_tok.sql script.

Fixed in iProcess Engine version 11.6.1. See defect reference IPE-3799 in product Release Notes document.
https://docs.tibco.com