Description:
EAI_DB steps fail to run with the error:

ORA_SYS_ERR - Oracle error code :6550 - ORA-06550: line 1, column 7:

Symptoms:
EAI_DB steps fail to run with the error:

ORA_SYS_ERR - Oracle error code :6550 - ORA-06550: line 1, column 7:

Cause:
The EAI_DB step called the SSOLITE stored procedure using the following:
ssolite.sw_casestart

The SSOLITE package exists within the iProcess Engine Oracle background database users schema. This defaults to the swpro user.

From the iProcess Engine 11.4.0 versions onward, all the iProcess Engine processes now connect to the Oracle database using the iProcess Engine Oracle foreground database user (This defaults to the swuser user).

The SSOLITE package does not exists in the swuser schema causing the error.

There are two solutions.  

1). Update the iProcess procedures.

    Updating the procedure involves editing the EAI_DB steps that call SSOLite stored procedure and add the schema owner at the start of the procedure name.

    change ssolite.sw_casestart

    to swpro.ssolite.sw_casestart

 

   The new procedure will have to be released in iProcess and the existing cases migrated to the new procedure version.

  

2). Create synonyms for the swuser to the objects in the swpro1 schema. 

    The issue is that the following packages do not exist in the foreground iProcess database user schema (swuser).

    SSOLITE

    SSOLITE_DATA

    SSOLITE_MSG

    The solution is to create synonyms in the swuser schema to reference the objects in the swpro1 schema. First connect to the database as a DBA and grant the CREATE SYNONYM privilege to swuser

     grant create synonym to swuser;

    Then connect to the database as swuser and create the synonyms using SQL:

     = = = = = 

     create synonym ssolite swpro.ssolite;

   create synonym ssolite_data swpro.ssolite_data;

   create synonym ssolite_msg swpro.ssolite_msg;

    = = = = =

    The EAI_DB steps will now be able to call the SSOLITE stored procedures. The synonyms only need to be created manually (one-off). This will avoid having to release new procedure(s) as part of the upgrade.

EAI_DB steps fail after upgrading to TIBCO iProcess 11.4.0 or later.

iProcess Engine 11.4.0 Release Notes