Can't connect to Oracle database - ORA-00955

Still need help?

The Atlassian Community is here for you.

Ask the community


Migrate database to Oracle will have the following in the atlassian-fisheye-<date>.log:

2012-06-01 11:35:25,170 ERROR [ThreadPool2 ] DBEditHelper-doGet - Database migration failed: com.cenqua.crucible.hibernate.CruDBException: Problem with create tables script E:\fecru\sql\ORACLE\schema\tables_76.sql
com.cenqua.crucible.hibernate.CruDBException: Problem with create tables script E:\fecru\sql\ORACLE\schema\tables_76.sql
	at com.cenqua.crucible.hibernate.DefaultDBControl.createTables(
	at com.atlassian.crucible.migration.item.DBImporter.importData(
	at com.atlassian.crucible.actions.admin.database.DBEditHelper$
	at com.atlassian.crucible.actions.admin.database.DBEditHelper$
	at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
	at Source)
Caused by: com.cenqua.crucible.hibernate.CruDBException: SQL script error on line 1: "create table cru_base_star_model (cru_star_id number(10,0) not null, cru_item_type varchar2(80 char) not null, cru_string_key1 varchar2(255 char), cru_string_key2 varchar2(255 char), cru_string_key3 varchar2(255 char), cru_string_key4 varchar2(255 char), cru_string_key5 varchar2(255 char), cru_int_key1 number(10,0), cru_int_key2 number(10,0), cru_int_key3 number(10,0), cru_int_key4 number(10,0), cru_int_key5 number(10,0), cru_text_key1 clob, cru_text_key2 clob, cru_user_name varchar2(255 char), cru_date_created number(19,0), cru_label varchar2(255 char), primary key (cru_star_id));" 
(ORA-00955: name is already used by an existing object), please contact
Caused by: java.sql.SQLException: ORA-00955: name is already used by an existing object


  1. The database user does not have correct table space permission.
  2. The database already has a pre-existing sequence in it which needs to be removed, which often occurs in Active Objects tables. You may need to drop the sequence from the database.


Resolution for Cause #1

  1. Stop Fisheye/Crucible.
  2. Ensure that the database has been correctly configured, as in our Database Setup for Oracle documentation.
  3. Start Fisheye/Crucible. 
tip/resting Created with Sketch.

Please ensure you are looking at the document corresponding to your Fisheye/Crucible version.

Resolution for Cause #2

  1. Identify the sequence that is causing the error - this can be done by reviewing the error in the logs, it will display an error such as the below

  2. Stop Fisheye/Crucible.
  3. Have your Oracle DBA delete the existing sequence.
  4. There may be more than one Oracle sequence causing errors. Using the steps above, locate all sequences causing errors within the log files and remove them.
  5. Start Fisheye/Crucible.

Last modified on Nov 14, 2018

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.