When BusinessConnect is configured with an Oracle datamanager (IM job database), it throws the following exception on startup: java.sql.SQLException: ORA-00972: identifier is too long

When BusinessConnect is configured with an Oracle datamanager (IM job database), it throws the following exception on startup: java.sql.SQLException: ORA-00972: identifier is too long

book

Article ID: KB0086051

calendar_today

Updated On:

Products Versions
TIBCO BusinessConnect -
Not Applicable -

Description

Resolution:
If the datamanager tables are not created beforehand, they will be created by the BC engine upon startup. The default "IM_SUBJ_PREFIX" (see the runENV script), which is also used as the tablename prefix for the data manager tables, is '&ltbc_installation_name>.&ltbc_installation_name>.hub'. This can be too long for Oracle table names. The solution is to override this default by explicitly specifying a table name prefix of a shorter string value.

Define the following property to an appropriate value in BCMiscProperties.cfg:

#string used to prefix all system table names
#must be a valid SQL table string
#default is the IM subject prefix with "."s replaced by "_"s
DataManager.Tablename.Prefix: &ltvalue>

Issue/Introduction

When BusinessConnect is configured with an Oracle datamanager (IM job database), it throws the following exception on startup: java.sql.SQLException: ORA-00972: identifier is too long