Exception: "SaveTransaction failed. Error=ORA-00957: duplicate column name code=957".

Exception: "SaveTransaction failed. Error=ORA-00957: duplicate column name code=957".

book

Article ID: KB0087177

calendar_today

Updated On:

Products Versions
TIBCO BusinessEvents Enterprise Edition -
Not Applicable -

Description

Resolution:
Description:
===========
After installing the backingstore, in the inference log the following exception is seen:

SaveTransaction failed. Error=ORA-00957: duplicate column name code=957

SQL scripts are generated with jdbc export of business studio.

Environment:
===========
TIBCO BusinessEvents 5.1.1
All Operating Systems

Symptoms:
===========
After investigating the alias file generated by exporting, the same alias names are found in the alias file.

Cause:
===========
According to Oracle, the table name can by 30 bytes and the column name can be 30 bytes.

Refer to http://docs.oracle.com/cd/B28359_01/server.111/b28286/sql_elements008.htm

Alias file contains the aliases for column or table names that exceed maximum size (30) imposed by target database.

Resolution:
===========
Two options to resolve the issue:

1). Update all duplicate alias names manually in the alias file and re-generate the SQL scripts.

2). Confirm that the column names are less than 30 characters. Confirm the SQL script can execute successfully.

Note:Some characters are used by BE( 'D_' and '_rrf$', e.g.). If a customer wanted to avoid aliases, they can shorten the names (23 for concepts, 30 for fields except date-time fields which then should be 27) - With join tables for contained concepts and arrays etc., they can still hit the limit.

Issue/Introduction

Exception: "SaveTransaction failed. Error=ORA-00957: duplicate column name code=957".