Migration Fails with Oracle - Identifier Is Too Long

Metastorm

The information in this article applies to:

Product: Metastorm BPM
Version: 6.6.x 7.x

Issue

• During a migration from version 6.6.x to 7.x when Oracle is used, the migration tool generates errors similar to the following:

  Failed to rename TwentyEightCharactersMapName - ORA-00972: identifier is too long
  Failed to transfer data from eDBCTwentyEightCharactersMapName to TwentyEightCharactersMapName - ORA-00972: identifier is too long

Resolution

• Oracle has a limit of 30 characters for a table name. During migration, the Metastorm Migrator creates a temp table for each custom variable table and prefixes each table with eDBC. Thus any custom variable table name (map name) that is 27 or more characters in length will fail to migrate.

  Starting with version 6.6, the Designer strictly enforces the 20 character limit on map names, so this problem with migration should only occur with existing procedures that have never been published with a version 6.6.x Designer.

• If the problem does occur, there is a workaround.

  1. ALTER TABLE TwentyEightCharactersMapName RENAME TO TwentySixCharactersMapName;
     COMMIT;
  2. UPDATE eMap SET ETABLENAME = 'TwentySixCharactersMapName' WHERE ETABLENAME = 'TwentyEightCharactersMapName';
     COMMIT;
  3. Run Migration tool
  4. DROP TABLE TwentyEightCharactersMapName;
     COMMIT;
  5. ALTER TABLE TwentySixCharactersMapName RENAME TO TwentyEightCharactersMapName;
     COMMIT;