Resolution:
The Berkeley DB data file migration from BE 1.4 to 2.0 without containing state machine is fairly simple. You just need to dump the BE 1.4 data files to an Oracle database using the Database Utility Tool be-dbutls in BE 1.4, and load the data back to a new set of Berkeley DB files using the be-dbutls in BE 2.0, so the new Berkeley DB files have BE 2.0 format.
Please NOTE that currently we only support Oracle database. We have tested with Oracle 10g Express Edition.

The following are the steps and notes for the migration:

Configuring be-dbutils.tra in both BE 1.4 and BE 2.0:

1. You may need to add %PSP%%TPCL_HOME%/lib/entrust to the tibco.env.STD_EXT_CP property in the BE 1.4 be-dbutls.tra file.

2. Ensure the jdbc driver path is part of tibco.env.CUSTOM_EXT_PREPEND_CP in the be-dbutils.tra files.

3. Ensure java.property.jdbc.drivers has the correct driver string in the db-dbutils.tra files.

4. Ensure be.trace.enable is true in the BE 2.0 be-dbutils.tra file to avoid a null pointer exception.

You can either configure all the properties below the "#DbUtils parameters" heading in BE (1.4 and 2.0) be-dbutils.tra files, or specify the parameters as the be-dbutils executable command line options. Properties specified in the command line override the corresponding ones in be-utils.tra file.

be-dbutils executable usage (command line option –h):

be-dbutils –h
Usage:

        be-dbutils &ltcreate|dump|load> [-pr &ltproperty file>] [-d &ltjdbc url>] [-u &ltjdbc user>] [-p <[password>] [-b &ltBerkeleyDB Dir> [-s] [-r repoDirectory]

        create: Create the SQL Schema
        dump: Dump from BE to SQL db
        load: Load from SQL db to BE Berkeley DB files
        -pr Specify the property file. The default property file is be-dbutils.tra in the current directory.
            Same as -property or /property or /p
        -d  Specify the JDBC URL that will be passed to the JDBC driver
            Same as -db or /d or /db
        -u  Specify the username used to connect to the database.
            Same as -user or /u or /user
        -p  Specify the password for the user used to connect to the database.
            Same as -password or /p or /password
        -b  Specify the directory where the BE Berkeley DB exists or is to be created.
            Same as -bedb or /b or /bedb
        -s  Use Short table names. (For databases that do not support long table names)
            Same as -shortnames or /s or /shortnames
        -r  Specify the directory where the designer repo lives.
            Same as -repo or /r or /repo
        -h  Display this usage. Same as -help or /help or /h

Note: You need to specify –s in the command line or configure the property “be.dbutils.jdbc.shortnames” as “true” in the be-dbutils.tra file, because Orable limits the maximum table name to be 30 characters.

Steps:

1. Use be-dbutils executable in BE 1.4 to create the SQL database tables with the BE project repo directory that has been saved in Designer that uses the BE 1.4 palettes.

2. Use be-dbutils executable in BE 1.4 to dump the persisted data from the existing BE 1.4 Berkeley DB files into the SQL database tables being created.

3. Use be-dbutils executable in BE 2.0 to load the data from the SQL database into a new set of Berkeley DB files that use the correct format for the BE 2.0 engine.

You are done!

The following are the sample commands. Except “create”, “dump” or “load”, you do not have to specify the options beginning with “-“ if you have configured the corresponding ones in the be-dbutils.tra files.

C:\tibco\be\1.4\bin&gtbe-dbutils.exe create -s -d jdbc:oracle:thin:@localhost:1521:XE -u &ltusername> -p &ltpassword> -b c:\dbutiltest\AIM-BE-RulesEngine-BERulesEngineArchive-14 -r c:\dbutiltest\BEProject14 > create.txt

C:\tibco\be\1.4\bin&gtbe-dbutils.exe dump -s -d jdbc:oracle:thin:@localhost:1521:XE -u &ltusername> -p &ltpassword> -b c:\dbutiltest\AIM-BE-RulesEngine-BERulesEngineArchive-14 -r c:\dbutiltest\BEProject14 > dump.txt

C:\tibco\be\1.4\bin&gtcd ..\..\2.0\bin

C:\tibco\be\2.0\bin&gtbe-dbutils.exe load -s -d jdbc:oracle:thin:@localhost:1521:XE -u &ltusername> -p &ltpassword> -b c:\dbutiltest\AIM-BE-RulesEngine-BERulesEngineArchive-20 -r c:\dbutiltest\BEProject20 > load.txt    

Explanation of paths used in above sample commands:

c:\dbutiltest\BEProject14 is a copy of the Designer project that has been saved using an instance of Designer that was using the BE 1.4 palettes.

c:\dbutiltest\BEProject20 is a copy of the Designer project that has been saved using an instance of Designer that was using the BE 2.0 palettes.

c:\dbutiltest\AIM-BE-RulesEngine-BERulesEngineArchive-14 is the directory that has the Berkeley DB files to be migrated

c:\dbutiltest\AIM-BE-RulesEngine-BERulesEngineArchive-20 is where to write the migrated Berkeley DB files.    

Sample be-dbutils.tra files for BE 1.4 and 2.0 are attached.

How to migrate TIBCO BusinessEvents persistence DB files from V1.4 to V2.0?