Skip to main content
Participating Frequently
May 23, 2023
Question

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

  • May 23, 2023
  • 3 replies
  • 2403 views

Hi,

Trying to using the Oracle DB instead of sqlserver DB, and ran into below error.

ormSettings.dbcreate = "update";

With above configuration after calling ormreload() call, application keeps spinning forever.  and getting below error.

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

 

when i change the above setting to "none",

ormSettings.dbcreate = " none ";

application throws table does not exist error, but in backend we have a table database.

when i change the same setting to 

ormSettings.dbcreate = "dropcreate";

we are losing all data and tables got created newly. Application loading/running successfully.

 

By using “update” option, our application is working fine in MicrosoftSQLServer.

When we use the same configuration for oracle database, by changing the required configuration like dialect and more

We landed on this errors.

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

 

Using

Windows Server 2022 Standard

ColdFusion 2021 server Enterprise Trial version 10 days left

Oracle Database 21c Express Edition Release **** - Production

 

Any insight would be appreciated.

    This topic has been closed for replies.

    3 replies

    Participating Frequently
    May 25, 2023

    After loading till request time out, application throws below error "Error executing DDL via JDBC Statement" and in hibernate sql log file i can see below script running which is wrong.

    Hibernate: create table XYZ ( ******, ****** )

    in short,

    after calling ormreload() method server trying to create tables which is why i am getting "Error executing DDL via JDBC Statement" Error message.

    BKBK
    Community Expert
    Community Expert
    May 25, 2023
    1.  Did you apply the correct JVM flags as I suggested in my last post?
    2.  In your Application.cfc, what is the value of this.ormsettings.dialect ?
    BKBK
    Community Expert
    Community Expert
    May 25, 2023

    There is something else. Looking back just now, I see the following in your original post:

     

    ormSettings.dbcreate = " none ";

    ormSettings.dbcreate = "dropcreate";

     

    To be sure, these settings should be, respectively 

    this.ormSettings.dbcreate = " none ";
    this.ormSettings.dbcreate = "dropcreate";

    You should make corrections where necessary.

    Participating Frequently
    May 24, 2023

    Hi,

    same issue with 

    Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production

    BKBK
    Community Expert
    Community Expert
    May 27, 2023
    quote

    Hi,

    same issue with 

    Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production


    By @khadar299107844wkv

     

    Thanks for the update. I had missed it.

    Community Expert
    May 23, 2023

    My guess is that your Oracle example uses Oracle reserved words and your SQL Server example doesn't. Here's a list of Oracle reserved words. I didn't search for a 21c list of reserved words.

     

    https://docs.oracle.com/cd/A97630_01/appdev.920/a42525/apb.htm

     

    The best advice I can give here is, don't use reserved words for variables etc in your programs. The next-best advice I can give is to give them minor changes. For example, instead of "update" maybe use "update1".

     

    Dave Watts, Eidolon LLC

    Dave Watts, Eidolon LLC
    Participating Frequently
    May 24, 2023

    Hi Dave, 

    Thanks for your suggestions.

    FYI, i am using below setting for reserved word as jvm arugemts.

     -Dhibernate.globally_quoted_identifier=true

    -Dhibernate.auto_quote_keyword=true 

    BKBK
    Community Expert
    Community Expert
    May 24, 2023

    Hi @khadar299107844wkv ,

    That flag should not be -Dhibernate.globally_quoted_identifier=true. It should instead be (in plural form):

    -Dhibernate.globally_quoted_identifiers=true

     

    Furthermore, verify from a suitable Hibernate reference whether you need to add the additional flag, 

    -Dhibernate.globally_quoted_identifiers_skip_column_definitions=true