ORA-00955

Dear friends,
After creating a table in oracle 9i Data Base through Java (Eclipse). The Oracle refused to add records to the table. I tryed several time to delete tables directly by using SQL but the problem remained the same.
This is the code:
import java.sql.*;
public class DDL_QUERIES_2 {
     public static void main(String[] args)throws Exception {
          Statement stmt=null;
          Connection conn=null;
          String url="jdbc:oracle:thin:@SS-EC55E45BC763:1521:faiz";
          String driver="oracle.jdbc.driver.OracleDriver";
          String user="HR";
          String pwd="HR";
          Class.forName(driver);
          conn=DriverManager.getConnection(url,user,pwd);
          stmt=conn.createStatement();
          stmt.executeUpdate("INSERT INTO COFFEES" + "VALUES('French_Roast',49,8.99,0,0)");
          stmt.executeUpdate("INSERT INTO COFFEES" + "VALUES ('Espresso', 150, 9.99, 0, 0)");
          stmt.executeUpdate("INSERT INTO COFFEES" + "VALUES ('Colombian_Decaf', 101, 8.99, 0, 0)");
          stmt.executeUpdate("INSERT INTO COFFEES" + "VALUES ('French_Roast_Decaf', 49, 9.99, 0, 0)");
          stmt.close();
          conn.close();
and the exceptions:
xception in thread "main" java.sql.SQLException: ORA-00955: name is already used by an existing object
     at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:180)
     at oracle.jdbc.ttc7.TTIoer.processError(TTIoer.java:208)
     at oracle.jdbc.ttc7.Oall7.receive(Oall7.java:543)
     at oracle.jdbc.ttc7.TTC7Protocol.doOall7(TTC7Protocol.java:1451)
     at oracle.jdbc.ttc7.TTC7Protocol.parseExecuteFetch(TTC7Protocol.java:862)
     at oracle.jdbc.driver.OracleStatement.executeNonQuery(OracleStatement.java:1839)
     at oracle.jdbc.driver.OracleStatement.doExecuteOther(OracleStatement.java:1764)
     at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:2354)
     at oracle.jdbc.driver.OracleStatement.executeUpdate(OracleStatement.java:858)
     at DDL_QUERIES.main(DDL_QUERIES.java:28)

The COFFEES table leads me to believe that you're going through the Sun JDBC tutorial using Oracle. Very good.
Your SQL is bad.
I have no idea why you arbitrarily turn one String into two like this:
"INSERT INTO COFFEES" + "VALUES('French_Roast',49,8.99,0,0)"But if you look at it, you'll see that there's no space between COFFEES and VALUES, so this isn't valid SQL. You want it to end up like this:
"INSERT INTO COFFEES VALUES('French_Roast',49,8.99,0,0)"I'm assuming that COFFEES has exactly five columns, and that you're providing values for each of them in the proper order.
Some words to the wise: skip ahead and read about PreparedStatement.
%

Similar Messages

  • ORA-00955 reports when I try to "create global temporary table" in windows

    Hi,
    When I try to run the sql in my oracle 9i server which is installed in a windows2000 machine,
    Create global temporary table test ...;
    For the first time, I can create table successfully.
    But I cannot access this table any more:
    drop table test;
    desc test;
    select * from test;
    In addition, if I try to create the table again, I got the error:
    ORA-00955: name is already used by an existing object
    While the same table can be created and dropped in another oracle9i server which is installed in Solaris 9 machine.
    So I suspect that this sould be a bug of window oracle server.
    Is there anyone who can confirm this?
    Or who can tell me how to report this bug to oracle?
    Thanks in advance.
    Please also refer the message at:
    http://asktom.oracle.com/pls/ask/f?p=4950:8:::::F4950_P8_DISPLAYID:1046974576560
    If you search the text: "create global temporary table sess_event", you can see for the first time, the table is created successfully.
    But the ORA-00955 reports when the author try to create table for the second time.
    This problem is exactly the same as my problem.
    I have also made a search both in Google and in Oracle website and I cannot find any solution of it.

    Read      Metalink Note:68098.1 Subject:      Overview of Temporary Tables
    How did you difine the temporary tables? on commit delete rows are reserv rows?
    http://download-west.oracle.com/docs/cd/B10501_01/appdev.920/a96590/adg03sch.htm#7794
    Jaffar
    Message was edited by:
    The Human Fly

  • ORA-00955 Errors during R3load for WEB AS Abap 6.40 installation

    Dear Gurus,
    I am encountering a problem during the R3load phase of the WEB AS ABAP 6.40 DB instance installation; I have patched the Oracle Database using the 9.2.0.7 patch set beforehand and resumed the SAPINST. There after errors occur during the DB load phase, below are the logs for reference (there are multiple occurences of 'ORA-00955: name is already used by an existing object' in existing logs)
    /sapmnt/P21/exe/R3load: START OF LOG: 20080627032739
    /sapmnt/P21/exe/R3load: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#4 $ SAP
    /sapmnt/P21/exe/R3load: version R6.40/V1.4 [UNICODE]
    /sapmnt/P21/exe/R3load -ctf I /sapcd/NetweaverSR1_Export/EXP3/DATA/SAPDODS.STR /tmp/sapinst_instdir/NW04SR1/WEBAS_ABAP_ORA_UC
    /DB/DDLORA.TPL /tmp/sapinst_instdir/NW04SR1/WEBAS_ABAP_ORA_UC/DB/SAPDODS.TSK ORA -l /tmp/sapinst_instdir/NW04SR1/WEBAS_ABAP_O
    RA_UC/DB/SAPDODS.log
    /sapmnt/P21/exe/R3load: job completed
    /sapmnt/P21/exe/R3load: END OF LOG: 20080627032739
    /sapmnt/P21/exe/R3load: START OF LOG: 20080627032814
    /sapmnt/P21/exe/R3load: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#4 $ SAP
    /sapmnt/P21/exe/R3load: version R6.40/V1.4 [UNICODE]
    /sapmnt/P21/exe/R3load -dbcodepage 4102 -i /tmp/sapinst_instdir/NW04SR1/WEBAS_ABAP_ORA_UC/DB/SAPDODS.cmd -l /tmp/sapinst_inst
    dir/NW04SR1/WEBAS_ABAP_ORA_UC/DB/SAPDODS.log -stop_on_error
    (DB) INFO: connected to DB
    (DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8
    (rscpsumg) Please look also into "/tmp/sapinst_instdir/NW04SR1/WEBAS_ABAP_ORA_UC/DB/SAPDODS001.xml".
    (DB) ERROR: DDL statement failed
    (CREATE TABLE "RSDMODSTAB" ( "CHARACT" VARCHAR2(3) DEFAULT ' ' NOT NULL , "ATTRIBUTE" VARCHAR2(3) DEFAULT ' ' NOT NULL  ) TA
    BLESPACE PSAPP21 STORAGE (INITIAL 16384 NEXT 0000040960K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) )
    DbSlExecute: rc = 102
      (SQL error 955)
      error message returned by DbSl:
    ORA-00955: name is already used by an existing object
    (DB) INFO: disconnected from DB
    /sapmnt/P21/exe/R3load: job finished with 1 error(s)
    /sapmnt/P21/exe/R3load: END OF LOG: 20080627032815
    /sapmnt/P21/exe/R3load: START OF LOG: 20080627035407
    /sapmnt/P21/exe/R3load: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#4 $ SAP
    /sapmnt/P21/exe/R3load: version R6.40/V1.4 [UNICODE]
    /sapmnt/P21/exe/R3load -dbcodepage 4102 -i /tmp/sapinst_instdir/NW04SR1/WEBAS_ABAP_ORA_UC/DB/SAPDODS.cmd -l /tmp/sapinst_inst
    dir/NW04SR1/WEBAS_ABAP_ORA_UC/DB/SAPDODS.log -stop_on_error

    Hello,
    Strange error, check if you didn't run out of space. If this is new installation, nor upgrade or migration, I would suggest to you drop the table and re-run export once more.
    Otherwise you can open message to SAP as you can expect that this will happen also for other tables. Looks table or tables exist at Oracle but sapinst don't have info about it
    Peter

  • ORA-00955 when upgrading from Content Server 5.0.2 to Publisher?

    I am upgrading Content Server 5.0.2 to Publisher.
    After running the sw installation and having imported the publisher.pte file, I am starting the Publisher and receiving an Oracle error "ORA-00955: name is already used by an existing object". From the messages logged, it looks like the error is encountered when recreating the object PCSACTIVE.PK_PCSACTIVE (first SQL statement with "Recreating ...", all others before where "Adding ...".
    My questions:
    1. has somebody else encounteered the same error?
    2. does anybody know how to trap the SQL being executed?As the upgrade is done automatically by the Publisher when starting, I have found so far no way of checking the SQL or knowing which SQL statements are executed against the DB) when "Recreating" an object.
    Thanks in advance for your help.
    P.S. Customer Support has also been contacted, but it looks like noone else has reported this kind of problems.

    Pl post OS details - are you using DBUA to upgrade ? Are there any errors in the database alert log ?
    ORA-00600 [kodpunp-nulltds], ORA-00600 [kokeeiix1], [600] When Upgrading To 11GR2 [ID 1367827.1]     
    HTH
    Srini

  • Error ORA-00955:

    Hi,
    Why would I get this error message when I run the script below.
    SQL> START test.sql;
    Table dropped.
    Table created.
    create TABLE student *
    ERROR at line 1:
    ORA-00955: name is already used by an existing object
    script:
    drop TABLE student
    create TABLE student
    (stu_id NUMBER(5) NOT NULL,
    stu_firstname VARCHAR2(30) DEFAULT 'unknown' NOT NULL,
    stu_lastname VARCHAR2(30) NOT NULL,
    stu_address VARCHAR2(30) NOT NULL,
    stu_suburb VARCHAR2(30) NOT NULL,
    stu_postcode VARCHAR2(4),
    stu_state VARCHAR2(3),
    stu_country VARCHAR2(30) NOT NULL,
    stu_phone_h VARCHAR2(30),
    stu_phone_w VARCHAR2(30),
    stu_fax VARCHAR2(30),
    stu_email VARCHAR2(30),
    stu_gender VARCHAR2(30),
    stu_dob VARCHAR2(30),
    stu_status VARCHAR2(2) CHECK(stu_status in ('FT','PT')));
    Thank you for your kind help
    Andonny

    Youw problem is caused by the semi-colon (;) with which you close the create statement and the "/" on the last line. The combination of these characters causes the statement to execute twice. So you can either remove the slash or the semi-colon and your script should run perfectly.

  • OWB11g ORA-00955 in Repository Assistant

    I´m just starting an installation of OWB11g and running the Repository Assistant in order to create workspaces, users, etc. in the default OWBSYS schema;
    I get a disgusting ;-) error at the end: "java.sql.SQLException: ORA-00955: name is already used by an existing object"
    !!Please, any idea about it will be wellcome!!.
    May the OWBSYS schema be corrupted? In that case, Is there any way to create another OWBSYS schema or clean it?
    The dafault Warehouse Builder schema (OWBSYS) has already been unlocked:
    SQL> ALTER USER OWBSYS ACCOUNT UNLOCK;
    SQL> ALTER USER OWBSYS IDENTIFIED BY <pass>;
    Document reference: http://download.oracle.com/docs/cd/B28359_01/owb.111/b31280/install_rep02.htm
    Thanks in advance,
    Javier Sánchez Ramírez
    Genasys II Spain, S.A.
    www.genasys.com
    ----------------------------------------------

    Hi,
    I too am experiencing this error when trying to configure a repository. I enter all the SYS details and for the OWB a/c. There was mention of invalid characters in the password , we use '-' , would this cause a problem.
    Also, I am using an Oracle XE database for the repository, is there any limitation on this? Or do I need a full 10g instance?
    Many thanks
    Gary Revell.

  • Cannot create a constraint beacuse of ORA-00955

    Hi !
    I was trying to create a constraint on a table after dropping it just in case:
    ALTER TABLE NEQResultByChunk
    DROP CONSTRAINT pk_neqresultbychunk
    OUTPUT: >> ERROR at line 2:
    ORA-02443: Cannot drop constraint - nonexistent constraint
    ALTER TABLE NEQResultByChunk
    ADD (
    CONSTRAINT pk_neqresultbychunk PRIMARY KEY
    (woName, sdtName, neqrIndex, sotName, soName)
    USING INDEX TABLESPACE &&idxtspace
    OUTPUT: >> ALTER TABLE NEQResultByChunk
    ERROR at line 1:
    ORA-00955: name is already used by an existing object
    There has to be somethink hang somewhere since using a different name works for the constraint works ok. I could not find this constraint in user_constraints table.
    Any idea on where to look for it ?
    I already brought dow the DB.
    Thanks,
    Mike

    Why should i delete the index manually?
    In most cases, the index will be remove when i delete the corresponding constraint.

  • Cannot resolve ORA-00955 error.

    I have a script which I run to drop and create preferences, set attributes and drop and create a context index. When dropping and creating preferences and setting the attributes everything works fine and I get the standard messages.
    My problem is I get the
    ORA-00955 name is already used by an existing object
    even after seeing the messages "index dropped" and index created.
    I have checked the ctx_user_index_errors view and the timestamps are from when I approximately ran my script so it seems the index worked.
    I have tried prefacing the index name with the schema name both when dropping and creating the index and I have even tried to use the keyword "force" when trying to drop the index, yet I still get the ORA-00955 error.
    A snippet from my code is below:
    PROMPT 23 DROP oracle text context index
    DROP INDEX schema1.my_index;
    PROMPT 24 CREATE the oracle text context with the above preferences and attributes
    CREATE INDEX schema1.my_index ON docs(doc_contents)
    INDEXTYPE IS ctxsys.context
    PARAMETERS('DATASTORE docs_data_store
    FILTER CTXSYS.INSO_FILTER
    FORMAT COLUMN oracle_text_format_column
    LEXER docs_lexer
    STOPLIST CTXSYS.DEFAULT_STOPLIST
    SECTION GROUP docs_group
    SYNC(ON COMMIT)' )
    /

    I think my problem was I really had a semi colon and a a foward slash at the end of the file, hence there was attempt to create the index twice, once for when the command was ended with a semicolon and once with the foward slash. I just removed the slash and everything worked fine.

  • ORA-02443 & ORA-00955

    Hello guy;
    I have a table with a unique constraint which should be made of three keys but made of one key. I decided to drop it and re-create it with the three keys but I got a message saying that says "ORA-02443: Cannot drop constraint - nonexistence constraint". And whenever I try to recreate that constraint with the same name, I get "ORA-00955: name already used bu an existing object."
    What do I need to do because I am frustrated with this controversial error message?
    Plz help.

    Welcome to the forum.
    Make sure to read {message:id=9360002} from the SQL and PL/SQL FAQ @ https://forums.oracle.com/forums/ann.jspa?annID=1535
    Is your constraint created as quoted identifier? (between '"'s?):
    {code}
    SQL> create table t (col number);
    Table created.
    SQL> alter table t add constraint "t_Uk" unique(col);
    Table altered.
    SQL> alter table t drop constraint t_uk;
    alter table t drop constraint t_uk
    ERROR at line 1:
    ORA-02443: Cannot drop constraint - nonexistent constraint
    SQL> alter table t drop constraint "t_Uk";
    Table altered.
    {code}

  • Rerunning script (DML and DDL) without ora-00001 and ora-00955 errors

    What is the best way to write a DML and DDL script so that it can be run multiple times without these ORA errors:
    ORA-00955: name is already used by an existing object
    ORA-00001: unique constraint (JILL.SYS_C00160247) violated
    I have just joined a product development company using SQL Server as there primary database. They have just completed a port to Oracle.
    Their product release upgrades (given to clients) include sql scripts with database changes (structure and data). They require that the client be able to rerun the scripts more than once with no errors. In SQL Server, the accomplish it this way.
    For DDL:
    if not exists (select * from dbo.sysobjects where id = object_id(N'[dbo].[MyTab]') and OBJECTPROPERTY(id, N'IsUserTable') = 1)
    Begin
         CREATE TABLE [dbo].[MyTab] (
              [ID]int IDENTITY(1,1),
              [InvID] uniqueidentifier not null
    For DML:
    IF NOT EXISTS (SELECT 1 FROM [dbo].[mytab] WHERE [Name] = 'Smith' and [ID] = 3)
    BEGIN
    INSERT INTO [dbo].[mytab]
    ([ID] ,[Name]
    VALUES (3,'Smith')
    END
    I am tasked with duplicating this logic on the Oracle side. The only way I can think of so far is using plsql and checking for existence before every insert and create statement. The other options I thought of cannot be used in this case
    - "whenever sqlerror continue" - gives the same response for all errors. True errors should stop the code, so this is too risky.
    - "log errors into ... reject limit unlimited" on the insert - I thought this was my best solution until I found out that it doesn't support lobs.
    Do you know of any more elegant (and more efficient) solution other than plsql cursors to check for existence before running each insert/create?
    Any suggestions would be greatly appreciated.

    select table_name from user_tables will give you the table exist or not.
    all_tables/dba_tables
    http://download.oracle.com/docs/cd/B14117_01/server.101/b10755/statviews_1190.htm#i1592091

  • Export dump failing with ora -06512 and ORA-00955

    Hi
    While running export data pump, I am getting this error. Any inputs helps ... Thanks in advance.
    Regards,
    K
    Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - 64bit Production
    With the Partitioning, OLAP and Data Mining options
    ORA-31626: job does not exist
    ORA-31633: unable to create master table "OPS$ORACLE.EXPFULL"
    ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
    ORA-06512: at "SYS.KUPV$FT", line 863
    ORA-00955: name is already used by an existing object

    You may have to drop the table OPS$ORACLE.EXPFULL and then try again.
    HTH
    Thanks
    Chandra

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

    Hi,
    I got blow error while upgrading 12.1.1 to 12.1.3, please suggest me how to move forward...
    This will be grate help for me....
    sqlplus -s MTH/***** @/d01/VIS/apps/apps_st/appl/mth/12.0.0/patch/115/sql/mth_pre_upgrade.sql
    Connected.
    DECLARE
    ERROR at line 1:
    ORA-00955: name is already used by an existing object
    ORA-06512: at line 59
    Regard
    suresh

    Hi,
    blow is the sql query....
    /* $Header: mth_pre_upgrade.sql 120.0.12010000.15 2010/06/11 08:45:13 sdonthu noship $ */
    REM dbdrv: sql ~PROD ~PATH ~FILE none none none sqlplus_owner &phase=con \
    REM dbdrv: checkfile:~PROD:~PATH:~FILE
    REM
    REM UPDATE SCRIPT FOR MOC
    REM
    REM DESCRIPTION: Upgrade script for MOC.
    REM
    REM History:
    REM
    REM Yong Feng 11/3/08 Rename non-partitioned staging tables to be
    REM to be removed later on
    REM
    SET VERIFY OFF;
    WHENEVER SQLERROR EXIT FAILURE ROLLBACK;
    WHENEVER OSERROR EXIT FAILURE ROLLBACK;
    DECLARE
    CURSOR c_non_p_stg_tables IS
    SELECT table_name
    FROM USER_TABLES
    WHERE partitioned = 'NO' AND
    TABLE_NAME in
    ('MTH_DAY_STG','MTH_DIM_HIERARCHY_STG','MTH_DIM_LEVEL_LOOKUP_STG',
    'MTH_EQUIPMENTS_STG','MTH_EQUIP_HIERARCHY_STG','MTH_EQUIP_OUTPUT_STG',
    'MTH_EQUIP_PROD_PERFORMANCE_STG','MTH_EQUIP_PROD_SCHEDULE_STG',
    'MTH_EQUIP_STANDARD_RATES_STG','MTH_EQUIP_STATUSES_STG','MTH_ITEMS_STG',
    'MTH_ITEM_CATEGORIES_STG','MTH_ITEM_COST_STG','MTH_ITEM_HIERARCHY_STG',
    'MTH_MTL_CONSUMED_TXN_LOT_STG','MTH_MTL_PRODUCED_TXN_LOT_STG',
    'MTH_PERIOD_STG','MTH_PERSONNEL_STG','MTH_PRODUCTION_SCHEDULES_STG',
    'MTH_PRODUCTION_SEGMENTS_STG','MTH_PROD_MTL_CONSUMED_STG',
    'MTH_PROD_MTL_CONSUMED_TXN_STG','MTH_PROD_MTL_PRODUCED_STG',
    'MTH_PROD_MTL_PRODUCED_TXN_STG','MTH_PROD_SEGMENTS_TXN_STG',
    'MTH_PROD_SUB_SEGMENTS_STG','MTH_QUARTER_STG','MTH_RESOURCES_STG',
    'MTH_RESOURCE_COST_STG','MTH_RESOURCE_REQUIREMENTS_STG',
    'MTH_RESOURCE_TXN_STG','MTH_TIME_HIERARCHY_STG',
    'MTH_USER_DIM_ENTITIES_STG','MTH_USER_DIM_HIERARCHY_STG',
    'MTH_WEEK_STG','MTH_WORKDAY_SHIFTS_STG','MTH_WO_SALES_ORDERS_STG',
    'MTH_YEAR_STG','MTH_TAG_READINGS_RAW','MTH_EQUIP_ENTITIES_STG');
    CURSOR c_mth_resources_d IS
    SELECT table_name
    FROM USER_TABLES where table_name='MTH_RESOURCES_D';
    v_rename_query VARCHAR2(200);
    v_drop_query VARCHAR2(200);
    v_res_query VARCHAR2(300);
    v_table_name VARCHAR2(100);
    v_tmp_table_name VARCHAR2(100);
    v_update_eqp_prd_prfrm VARCHAR2(200);
    v_res_tab VARCHAR2(100);
    BEGIN
    FOR table_name_rec IN c_non_p_stg_tables LOOP
    v_table_name := table_name_rec.table_name;
    -- rename table from MTH_WEEK_STG to be MTH_WEEK_S_P
    v_tmp_table_name := substr(v_table_name, 1, (Length(v_table_name) -2)) || '_P';
    v_rename_query := 'ALTER TABLE ' || v_table_name || ' rename to ' ||
    v_tmp_table_name ;
    -- v_drop_query := 'DROP TABLE ' || v_table_name;
    --BEGIN                 
    EXECUTE IMMEDIATE v_rename_query;
    --EXCEPTION
    --WHEN OTHERS THEN
    --BEGIN
    --EXECUTE IMMEDIATE v_drop_query;
    --EXCEPTION
    --WHEN OTHERS THEN NULL;
    --END;
    --END;
    END LOOP;
    FOR table_res_d IN c_mth_resources_d LOOP
    v_res_tab := table_res_d.table_name;
    v_res_query := 'CREATE TABLE MTH_RESOURCES_D_TEMP AS SELECT * FROM '|| v_res_tab;
    EXECUTE IMMEDIATE v_res_query;
    EXECUTE IMMEDIATE 'TRUNCATE TABLE MTH_RESOURCES_D';
    END LOOP;
    END;
    commit;
    exit;

  • RME-02105 AND ORA-00955 WHEN EXPORTING APPLICATION SYSTEM

    WHEN TRYING TO EXPORT APPLICATION SYSTEM FROM RON.
    and after resbonding to the messsage "Export tables are already populated,you want to clear them?" by "yes" ,I RECIEVED THE ABOVE ERRORS .
    I USE ORACLE databse 8.1.7 with Oracle Designer 6i Version 6.5.52.1.0.
    is ther any help?

    OK,
    I have read the link and I have talked with our DBA. He says taht we are working with a 9.2 (9.2.0.7 exactly) version. In this version he believes taht the only way to use the flashback query feature was through the use of the utility package DBMS_FLASHBACK. Therefore, the sentence ALTER database flashback that would work on a 10g version off does'nt have sense on 9.2.
    Anyone knows how to avoid the flashback error in a 9.2 environment?

  • ORA-29855: erreur d'exécution de la routine ODCIINDEXCREATE

    Hello
    i have an error when creating a full text index on a simple table which has a primary key
    CREATE TABLE tab_1(aa nvarchar2(50) PRIMARY KEY,bb clob)
    CREATE INDEX xtab_1_bb ON tab_1 (bb) INDEXTYPE IS CTXSYS.CONTEXT
    ORA-29855: erreur d'exécution de la routine ODCIINDEXCREATE
    ORA-20000: Erreur Oracle Text
    DRG-10528: clé primaires de type NVARCHAR2 non autorisées
    ORA-06512: à "CTXSYS.DRUE", ligne 160
    ORA-06512: à "CTXSYS.TEXTINDEXMETHODS", ligne 364
    if i retry to recreate the full text index, i get
    ORA-00955: ce nom d'objet existe déjà
    however, if i create the full text index before creating the primary key it works good
    CREATE TABLE tab_2(aa nvarchar2(50) ,bb clob)
    CREATE INDEX xtab_2_bb ON tab_2 (bb) INDEXTYPE IS CTXSYS.CONTEXT
    ALTER TABLE tab_2 ADD CONSTRAINT pk_bb PRIMARY KEY(aa)
    help me pleaze

    Raj Kr Pandit wrote:
    where is the issue?The issue is your code is apples and oranges:
    SQL> CREATE TABLE tab_1(aa nvarchar2(50) PRIMARY KEY,bb clob)
      2  /
    Table created.
    SQL> CREATE INDEX xtab_1_bb ON tab_1 (bb) INDEXTYPE IS CTXSYS.CONTEXT
      2  /
    CREATE INDEX xtab_1_bb ON tab_1 (bb) INDEXTYPE IS CTXSYS.CONTEXT
    ERROR at line 1:
    ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
    ORA-20000: Oracle Text error:
    DRG-10528: primary keys of type NVARCHAR2 are not allowed
    ORA-06512: at "CTXSYS.DRUE", line 160
    ORA-06512: at "CTXSYS.TEXTINDEXMETHODS", line 364
    SQL> SY.

  • Oracle 10.2.0.4 to 11.2.0.2 fails with ORA-03113

    This is Oracle upgrade from 10.2.0.2 to Oracle 11.2   (on Windows platform)
    Since 10202 to 11 is not SAP supported, we upgrade from 10.2.0.4 first before upgrade to 11
    10202 to 10204 upgrade finished fine.  All post upgrade sql files are run without any issues.
    During 10204 to 11202 upgrade, at 42% complete the Database Upgrade Assistant gives
    ORA-03113: end-of-file on communication channel
    Upgrade failed due to running the step "Upgrading Oracle Server"
    The upgrade was repeated and it always gets the same error at the same spot.
    Once the error occurs, if I try to rerun the upgrade script, it complains that objects already exist.
    Looking at the \oracle\cfgtoollogs\dbua\<SID>\upgrade1 directory, I see the log file which shows at the end of the file:
    GRANT INSERT ON sys.impdp_stats TO PUBLIC
    2  /
    Grant succeeded.
    GRANT DELETE ON sys.impdp_stats TO PUBLIC
    2  /
    Grant succeeded.
    Rem ===================================
    Rem End  User stats table format change
    Rem ===================================
    Rem==========================================================================
    Rem Call script to upgrade type dictionary tables from 8.0 image to
    Rem 8.1 image format. If they are already in 8.1 image format, the
    Rem script will do nothing.
    Rem==========================================================================
    set serveroutput on
    EXECUTE dbms_objects_utils.upgrade_dict_image;
    BEGIN dbms_objects_utils.upgrade_dict_image; END;
    ERROR at line 1:
    ORA-03113: end-of-file on communication channel
    ERROR:
    So the problem is at running  dbms_objects_utils.upgrade_dict_image procedure
    "This procedure upgrades the type dictionary images from 8.0 to 8.1. The dictionary tables that could be in 8.0 are kottd$, kottb$, kottbx$, kotad$ and kotmd$, which existed in 8.0 or 8.1, when 8.0 compatibility was possible, kotadx$ was created in 9iR2 when we required 8.1 minimum  compatibility. The source code is fully exposed for both package header and body."
    /rdbms/admin/dbmsobj.sql
    If I try to run that same procedure within SQLPlus (after the upgrade failed), I get the error message ORA-00955: name is already used by an existing object.   This tells me that the upgrade script actually created the newer version of the dictionary images, but for some reason failed to complete.  And so when I re-run the upgrade script, it complains.
    We've searched google, SAP Notes, sdn, etc. but havent gotten anywhere.    Help or hints would be greatly appreciated.
    Thanks

    HI,
    Check below details from oracle Metalink.
    Curtesy of Oracle Metalink
    A1) Errors connecting as SYSDBA / Internal OR on startup nomount
    There is something fundamental wrong with the software / environment
    if you cannot connect to Server Manager as a DBA user.
    The steps here cover errors such as ORA-3113, ORA-12547: TNS:lost contact
    or similar errors connecting to Oracle or starting the instance NOMOUNT.
    Check the following items:
    A1.1) If possible reboot the server disabling any automatic
    startup of Oracle before you do so. This may seem drastic
    but helps make sure you are working from a consistent
    starting point.
    A1.2) Check your environment points at the expected ORACLE_HOME
    and ORACLE_SID and that TWO_TASK is not set (Unix) or
    LOCAL is not set (NT registry).
    Check the USER_DUMP_DEST and BACKGROUND_DUMP_DEST and default
    trace directories under this environment for any user trace
    files or alert log entries generated. These may help indicate
    the cause of the problem.
    Eg: ORA-600[SKGMINVALID] may indicate a problem with the
    shared memory Unix parameters on Unix systems.
    Try to show that any trace file / alert log entry you
    find is truely related to the "CONNECT" command by re-issuing
    the "connect" and checking for a new trace file / alert entry
    at the time of the error.
    A1.3) Unix only:
    Some Unix platforms need LD_LIBRARY_PATH to be set
    correctly to resolve any dynamically linked libraries.
    As the user with the problem:
    % script /tmp/ldd.out
    % id
    % cd $ORACLE_HOME/bin
    % ldd oracle
    % exit
    If the 'ldd' command does not exist go to the next step below.
    Check that all lines listed show a full library file. If there
    are any 'not found' lines reported contact Oracle support
    with the output of /tmp/ldd.out .
    A1.4) Unix only:
    Your 'oracle' executable may be corrupt. Relink it thus:
    Log in as the 'oracle' user.
    % script /tmp/relink.out
    % cd $ORACLE_HOME/rdbms/lib
    % mv $ORACLE_HOME/bin/oracle $ORACLE_HOME/bin/oracle.dd.mon.yy
    % rm -f ./oracle
    % make -f ins_rdbms.mk ioracle
    % exit
    Prior to Oracle7.3 the relink command was:
    make -f oracle.mk ioracle
    If this reports any errors Oracle support will need to see
    the contents of the file /tmp/relink.out .
    A1.5) Have you installed the Parallel Server Option ?
    ORA-3113 can occur if you have installed the Parallel
    Server Option but do NOT have a Distributed Lock Manager
    installed or running correctly.
    Unix:
    If the Parallel Server Option was installed by accident
    then it can be de-installed by relinking.
    Eg:
    Shut down any Oracle instances
    % script /tmp/relink.out
    % cd $ORACLE_HOME/rdbms/lib
    'oracle' should not exist so delete it if it present
    % rm -f oracle
    % make -f ins_rdbms.mk no_parropt ioracle
    % exit
    NB: Do NOT deinstall the Parallel Server Option if the
    database is using Parallel Server unless both nodes
    are shut down otherwise database corruption could occur.
    A1.6) If the error is on STARTUP NOMOUNT:
    Check the init.ora file used to start the database.
    This provides the configuration details used
    configure the instance. To help isolate the problem
    it may be useful use a very basic init.ora file
    when starting the instance. If this works then
    parameters can be increased / introduced one at a
    time to see if there is a problem with a particular
    setting.
    A1.7) Check for server side trace files which may give more
    indication what the underlying problem is.
    See section C for details on how to check
    for server trace files.
    A1.8) Ensure there is free disk space in:
    a. Your USER_DUMP_DEST and BACKGROUND_DUMP_DEST locations
    b. Your AUDIT destination (Unix)
    The default is $ORACLE_HOME/rdbms/audit
    c. Your Oracle Trace directory if Oracle Trace is enabled
    See <Note:45482.1>
    A2) Errors Mounting the database
    Check all the items in A1 first.
    If an error occurs when mounting the database there may be problems
    with the control-files or data files, or with resources required to
    open these files.
    A2.1) The location of the control files are specified in the
    init.ora file. Try mounting using each controlfile in
    turn.
    eg: "Shutdown abort",
    edit the init.ora to refer to ONE of the controlfiles only,
    "startup nomount",
    "alter database mount"
    Repeat for each controlfile to see if any controlfile works.
    A2.2) It is possible to re-create the controlfiles if you know the
    location of all datafiles and online logs, or to restore an old
    backup controlfile. Always back up the current controlfiles before
    restoring any backup copies or issuing a CREATE CONTROLFILE
    command.
    The steps for this are not documented here.
    A2.3) Unix:
    Some unix platforms have a 'truss' command (or 'tusc').
    If available this can be used to help trace how far Oracle
    gets before the error occurs.
    Eg:
    % truss -o /tmp/truss.out -f svrmgrl
    Keep the file /tmp/truss.out safe - Oracle Support MAY need to see it.
    Regards,
    Venkata S Pagolu
    Edited by: Venkata Pagolu on Mar 10, 2012 12:10 PM

Maybe you are looking for