Resolution:
Description:
============
Changing the identifier limit to be more than 30 characters in BusinessEvents (BE) 3.0.1.

Environment:
==========

   o TIBCO BusinessEvents 3.0.1

  

Symptoms:
=========
BE Engine throws the following exception -

java.sql.SQLException: ORA-01948: identifier's name length (37) exceeds maximum (30)


Cause:
=====
In BE 3.0, extra jars are added for Query Agent functionality. These jars are conflicting with the old jars used by BusinessWorks (BW). As far as BE is concerned there is no problem at run time. At design time for generating web services, the following resolution can be used.


Resolution:
==========

1. Open the following file for editing:
       &ltname for db schema>.aliases (For example, acme.aliases)

This file is created when oradeploy is run and there are any entity, property or state machine names that exceed 30 characters.

2. For each entity, property or state machine name that exceeds 30 characters in length, provide an alias using a name that is shorter than 30 characters.

3.  Execute oradeploy using the following format, replacing items in angle brackets with your actual values:

     &ltengine executable> &ltTRA file> &ltpath to EAR> &ltname for db schema>

Example:
    oradeploy.exe oradeploy.tra c:/temp/FraudDetection.ear acme

NOTE: Now the aliases file is used to create names that are within the 30-character limitation.

4.  At the SQL prompt, type the following to run each script in turn.
    a. @base_types.sql
    b. @create_tables.sql
    c. @&ltname for db schema>.sql (for example, @acme.sql)

Changing the identifier limit to be more than 30 characters in BusinessEvents (BE) 3.0.1.