ORA-00955: name is already used by an existing object

[Former Member]

Hi, I'm getting an error during system initialization (using Hybris 6.2 v. with Oracle XE 11g) "ORA-00955: name is already used by an existing object", screenshot is below:. There is similar question opened Here with error during the JUnit tenant initialization but without answer why this happens.

[Former Member]

Did you find a solution to this problem? We are having the same issue on Oracle servers. MySQL is running fine.

[Former Member]

Hi, I think in my case it was caused from changing the itemtype name, but using the same deployment table code (for e.g item_1 (10001) -> item_2 (10001)), then initialization drops tables from items.xml, but the old item_1 remained and had the same code as item_2 and therefore it threw "name is already used by an existing object" error.

[Former Member]

Hi, We are also facing same issue when we do system update on oracle. Could you please let me know if you got any solution for this.

Regards Govind

[Former Member]

Hey Govind,

Could you tell me how did u fix it . we are facing this while system update.

Thanks

[Former Member]

I had the same problem. (update directly to Hybris 6.3) By running all lines of the update_master_schema_20170523-145945.sql (sql created by dry run of updatesystem) i found out that the problem(on my setup) is the line CREATE INDEX sapglobalconfigurationRelIDX_9 ON saplogicalsystems (p_sapglobalconfiguration); as there is already a sapglobalconfigurationRelIDX_9, pointing to "SAPPRODUCTSALES2CATALOG" ("P_SAPGLOBALCONFIGURATION"). I droped this index prior to the updatesystem und redo updatesystem to a backup of the db.

I don't know why hybris create the same index name for a other type..

[Former Member]

I had the same problems when initializing the Junit tenant using Oracle, and the reason was that I had an item with exactly 24 characters in its name. Like restrictedshippingregion.

When generating the junit tables and having one localized attribute in this model, the generated table with the prefix "junit_" had the final name like junit_restrictedshippingregion.

Those are exactly 30 characters which is the limit in Oracle for all table names.

Knowing that hybris creates another table with the same name and with the suffix "lp" for the localized attributes, the resultant table name is: junit_restrictedshippingregionlp Those are 32 characters, and Hybris (or Oracle) cuts this name to the max length: (junit_restrictedshippingregion)

Finally, what we've got are 2 tables with the same name generated in the DDL script. and the ORA-00955 appears. Reducing the name of those items or the prefix for junit tenant tables, we can avoid this issue.

I hope this helps.

[VinayKumarS]

Guys, Usually this problem comes with Case sensitivity issue. If you are using mysql. Then create Collation as Case insensitive to fix it.

Similarly you have to check the necessary configuration with Oracle.

link text

[sasethia]

We faced a similar problem while upgrading to 6.2 version, to solve this you need to drop all the existing DB indexes and also if there are new unique indexes for product and media tables so you will need to delete duplicate records from those tables.