Resolution:
Description:
========
Unable to start a BW service instance because of internalDataManager not initializedStartup. The project is making use of checkpoints.

Environment:
=========
Operating system(s): All
TIBCO Businessworks: 5.x

Symptoms:
=======
The following error stack will be found in the BW service instance log.

"Startup error: InternalDataManager not initializedStartup error: InternalDataManager not initialized
at com.tibco.pe.core.JobPoolConfigurator.completeStartup(JobPoolConfigurator.java:155)
...
caused by: java.sql.SQLException: ORA-00972: identifier is too long at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:74)
...
at com.tibco.pe.PEMain.main(PEMain.java:130)"

Cause:
=====
Oracle enforces a limitation of 30 character per object name. For checkpoints and other internal data repository, BW creates the following tables:

<TABLE_NAME_PREFIX>_internal;
<TABLE_NAME_PREFIX>_job;
<TABLE_NAME_PREFIX>_wait;
<TABLE_NAME_PREFIX>_notify;
<TABLE_NAME_PREFIX>_duplicates;

The error indicates the table name prefix and the suffix together have breached the Oracle limitation.

Resolution:
=======

The suffix is hardcoded and cannot be changed. However, the table name prefix can be updated. As the longest suffix is 11 characters, the prefix can be a maximum length of 19.

Instruction follow.

1). Stop the BW service instance.
2). Reduce the value of Database.Tablename.Prefix to 19 characters or less (property is found in <tra_home>/domain/<domain>/application/<application>/<application>.tra).
3). Restart the the BW service instance.

Unable to start a BW service instance because of internalDataManager not initializedStartup error.