ORA-01418: specified index does not exist though the index exist !!

Hi all,
This problem occures only sometimes. I'm getting the list of indexes from the user_indexes table and later perform on them a rebuild operation by using the command :
Alter index index_name coalesce
This might cause on some indexes to the following error:
ORA-01418: specified index does not exist
I know these indexes exist and I didn't find any reson for this situation.
Does anyone have any idea about it ?
Thanks,
Lital

The index name can be created in sensitive case. Try to use double-quote.
Alter index "index_name" coalesce;That give something like this :
SCOTT@demo102> create index "Titi" on emp2(empno);
Index created.
SCOTT@demo102> alter index titi coalesce;
alter index titi coalesce
ERROR at line 1:
ORA-01418: specified index does not exist
SCOTT@demo102> alter index "Titi" coalesce;
Index altered.
SCOTT@demo102> Nicolas.
Add example
Message was edited by:
N. Gasparotto

Similar Messages

  • ORA-02149: Specified partition does not exist

    ORA-31693: Table data object "aaaa"."bbbbb":"P_2012112216" failed to load/unload and is being skipped due to error:
    ORA-02149: Specified partition does not exist
    SQL> select partition_name from dba_tab_partitions where table_name=‘DME_bbbbb_RES’ and TABLE_OWNER=aaaa;
    no rows selected
    请问一下是什么原因造成的.

    数据库版本 10.2.0.1
    用数据泵导出的时侯报ORA-02149: Specified partition does not exist
    nohup expdp \'/ AS SYSDBA\' directory=DATADUMP SCHEMAS=aa dumpfile=EXPDP_aa_%u.dmp logfile=EXPDP_WIPNMS.log parallel=4 exclude=STATISTICS &

  • GATHER_TABLE_STATS ORA-02149: Specified partition does not exist

    Database was upgraded from 8.1.7 to 11.1.0.7 . This type of error appear in alert.log file.
    GATHER_STATS_JOB: GATHER_TABLE_STATS('"abc"','"PLAN_M2"','"PLAN_MAR"', ..
    ORA-02149: Specified partition does not exist
    GATHER_STATS_JOB: GATHER_TABLE_STATS('"abc"','"PLAN_M2"','"PLAN_APR"', ..
    ORA-02149: Specified partition does not exist
    All partitions exists for this table. Does anybody have idea why these errors occur during GATHER STATS JOB run ?

    See if the partition(s) were created using the public/private synonym. If that is the case, then redefining the strategy may solve the issue...

  • Tethering does not work - though the carrier supports it

    Hi, I know that this topic has been discussed many times. But...
    My carrier eplus offers the tethering function, iI downloaded the appropriate files and can see them in the menu "profiles" as installed. But there is no tethering function in the network.
    What am I doing wrong? Thanks a lot for your help.

    If your carrier supports tethering, and such is provisioned on your account, then you need the proper carrier file to implement tethering on your phone. You can connect your phone to itunes, and on the summary tab, click "check for updates" to see if a carrier file is available. If you're positive you've installed the proper carrier file, you can try turning your phone off, then back on, as many carrier updates are implemented this way. If you still don't see the tethering option, then you need to contact your carrier as this is strictly a carrier enabled feature.

  • Primary index does not exist in database but shows in SE14?

    I added a couple of key fields to a Z table and activated it. Every thing went well - adjusted it with SE14 also.
    When I checked the Runtime object - it is OK.
    When I checked Database Object, it is showing that the Primary Index does not exist in Database but SE14 says that the Priamry Index exists in Database.
    Please advise how to correct this. I saw another psoting when I searched per this error message: "Indexes: Inconsistent with DDIC source" . It tells to create this index at Database but need to know the steps.
    pl advise.
    (reposting here)
    Edited by: Venkatabby on Mar 26, 2008 4:05 PM

    hi,
    To create a index for a table,
    go to se11->click on Indexes tab and create  a primary index.
    Indexes speed up data selection from the database. They consist of selected fields of a table, of which a copy is then made in sorted order. If you specify the index fields correctly in a condition in the WHERE or HAVING clause, the system only searches part of the index (index range scan).
    The system automatically creates the primary index. It consists of the primary key fields of the database table. This means that for each combination of fields in the index, there is a maximum of one line in the table. This kind of index is also known as UNIQUE.
    If you cannot use the primary index to determine the result set because, for example, none of the primary index fields occur in the WHERE or HAVINGclauses, the system searches through the entire table (full table scan). For this case, you can create secondary indexes, which can restrict the number of table entries searched to form the result set.
    You create secondary indexes using the ABAP Dictionary. There you can create its columns and define it as UNIQUE.
    reward points if useful.
    regards
    sandhya

  • ORA-20211: Active job does not exist, cannot link to job record.

    Getting the above error while executing OWB mapping in production environment.
    Details of the error :
    ORA-20211: Active job does not exist, cannot link to job record.
    ORA-06512: at "RADRUN.WB_RT_MAPAUDIT", line 1278
    ORA-06512: at "RADRUN.WB_RT_MAPAUDIT", line 2110
    ORA-06512: at "RADSTG.MAP_STG_AIRCRAFT", line 2384
    ORA-06512: at "RADSTG.MAP_STG_AIRCRAFT", line 2513
    RADRUN -- runtime schema
    RADSTG -- Target schema where mappings deployed.
    source database is accessed through a DB link.
    OWB version - 10.1.0.4.0
    Oracle - 9.2.0.6.0
    Here mappings are getting executed by calling a pl/sql procedure. This pl/sql procedure is executed every day by scheduling a dbms_job. After the error, the job is in hanging.
    Last week also the same error happened, on that occasion , restarted the database and re submitted the job. Mapping executed without any error.
    Looking for the expert comments

    Hi.
    See Note:125860.1 in metalink (and please, lol to solution #3). It applies to older OWB versions though... Are you using DBMS_JOB or OEM to run these mappings? If so, then the metalink note might be useful help.
    Karesz, I believe if the source database was down, it would fail with an ORA-12XXX Error.
    Regards,
    Marcos

  • ORA-29829: implementation type does not exist

    Hello,
    I get ORA-29829: implementation type does not exist when creating an external table in
    Oracle 10g 10.2.0.3.0. Anyone knows why this happens?
    Wrote file afiedt.buf
    1 CREATE TABLE tim
    2 ORGANIZATION EXTERNAL
    3 (
    4 TYPE ORACLE_DATA_PUMP
    5 DEFAULT DIRECTORY tim_dir
    6 LOCATION ('tim.dmp')
    7 )
    8* AS SELECT * FROM dba_tables
    AB0318@ditoa1> /
    CREATE TABLE tim
    ERROR at line 1:
    ORA-29829: implementation type does not exist
    AB0318@ditoa1> select * from V$OPTION;
    PARAMETER VALUE
    ================================================================ ===================================
    Objects TRUE
    Regards,
    Tim

    ORA-29829: implementation type does not exist
    Cause: The implementation type specified with USING clause could not be found.
    Action: Check to see if the type exists and the user has EXECUTE privilege on this type.

  • ORA-39083,ORA-00959: tablespace 'TEST_LIVE' does not exist

    Hi,
    I am trying to import using impdp but i am facing the below mentioned error..
    Connected to: Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    Master table "TEST_230511"."SYS_IMPORT_FULL_01" successfully loaded/unloaded
    Starting "TEST_230511"."SYS_IMPORT_FULL_01": TEST_230511/********@GEMSDB REMAP_SCHEMA=TEST_220511:test_230511 DIRECTORY=dump_dict DUMPFILE=test_live_230511.DMP LOGFILE = test_230511.LOG
    Processing object type SCHEMA_EXPORT/USER
    ORA-31684: Object type USER:"TEST_230511" already exists
    Processing object type SCHEMA_EXPORT/SYSTEM_GRANT
    Processing object type SCHEMA_EXPORT/ROLE_GRANT
    Processing object type SCHEMA_EXPORT/DEFAULT_ROLE
    Processing object type SCHEMA_EXPORT/PRE_SCHEMA/PROCACT_SCHEMA
    Processing object type SCHEMA_EXPORT/DB_LINK
    Processing object type SCHEMA_EXPORT/SEQUENCE/SEQUENCE
    Processing object type SCHEMA_EXPORT/TABLE/TABLE
    ORA-39083: Object type TABLE failed to create with error:
    ORA-00959: tablespace 'TEST_LIVE' does not exist
    Failing sql is:
    CREATE TABLE "TEST_230511"."C_EXPENSECLAIMS_EMPLOYEE" ("C_EXPENSECLAIMS_EMPLOYEE_ID" NUMBER(10,0), "AD_CLIENT_ID" NUMBER(10,0), "AD_ORG_ID" NUMBER(10,0), "ISACTIVE" CHAR(1), "CREATED" DATE, "CREATEDBY" NUMBER(10,0), "UPDATED" DATE, "UPDATEDBY" NUMBER(10,0), "TRANSACTION_DATE" DATE, "EXPENSE_DATE" DATE, "EXPENSE_TYPE_ID" NUMBER(10,0), "BUDGETED" CHAR(1) DEFAULT ('N'), "AMOUNT" NUMBER
    ORA-39083: Object type TABLE failed to create with error:
    ORA-00959: tablespace 'TEST_LIVE' does not exist

    Hi;
    Pelase check below notes which is mention similar error like you hit
    IMPDP REMAP_SCHEMA Option Does Not Import To Default Tablespace [ID 796671.1]
    Also see:
    OERR: ORA 959 "tablespace '%s' does not exist" [ID 18553.1]
    Can't Drop Text Domain Index Which Came Imported To 11.1.0.7 From 10.2.0.4 Export Due to ORA-29868 [ID 751883.1]
    Import Partition Table Fails With Ora-00959: Tablespace '_$Deleted$0$0' [ID 798142.1]
    Regard
    Helios

  • ORA-00959: tablespace 'EXAMPLE' does not exist

    hi ! i want to import hr schema to my application server 10g from oracle 10g database.
    oracle application server:
    [oracle@apps ~]$ sqlplus / as sysdba
    SQL> SQL> SELECT * FROM V$VERSION ;
    BANNER
    Oracle Database 10g Enterprise Edition Release 10.1.0.4.2 - Prod
    PL/SQL Release 10.1.0.4.2 - Production
    CORE 10.1.0.4.0 Production
    TNS for Linux: Version 10.1.0.4.0 - Production
    NLSRTL Version 10.1.0.4.2 - Production
    oracle database 10g;
    [oracle@test ~]$ sqlplus / as sysdba
    SQL> SELECT * FROM V$VERSION ;
    BANNER
    Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod
    PL/SQL Release 10.2.0.1.0 - Production
    CORE 10.2.0.1.0 Production
    TNS for Linux: Version 10.2.0.1.0 - Production
    NLSRTL Version 10.2.0.1.0 - Production
    exporting schema in oracle database 10g.................
    [oracle@test dpdump]$ expdp DIRECTORY=DATA_PUMP_DIR DUMPFILE=hrschema.dmp logfile=hrschema.log SCHEMAS=hr version=10.1.0.4.2
    Export: Release 10.2.0.1.0 - Production on Friday, 30 April, 2010 9:45:30
    Copyright (c) 2003, 2005, Oracle. All rights reserved.
    Username: sys as sysdba
    Password:
    Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
    With the Partitioning, OLAP and Data Mining options
    Starting "SYS"."SYS_EXPORT_SCHEMA_01": sys/******** AS SYSDBA DIRECTORY=DATA_PUMP_DIR DUMPFILE=hrschema.dmp logfile=hrschema.log SCHEMAS=hr version=10.1.0.4.2
    Estimate in progress using BLOCKS method...
    Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
    Total estimation using BLOCKS method: 448 KB
    Processing object type SCHEMA_EXPORT/USER
    Processing object type SCHEMA_EXPORT/SYSTEM_GRANT
    Processing object type SCHEMA_EXPORT/ROLE_GRANT
    Processing object type SCHEMA_EXPORT/DEFAULT_ROLE
    Processing object type SCHEMA_EXPORT/PRE_SCHEMA/PROCACT_SCHEMA
    Processing object type SCHEMA_EXPORT/SEQUENCE/SEQUENCE
    Processing object type SCHEMA_EXPORT/TABLE/TABLE
    Processing object type SCHEMA_EXPORT/TABLE/GRANT/OWNER_GRANT/OBJECT_GRANT
    Processing object type SCHEMA_EXPORT/TABLE/INDEX/INDEX
    Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
    Processing object type SCHEMA_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS
    Processing object type SCHEMA_EXPORT/TABLE/COMMENT
    Processing object type SCHEMA_EXPORT/PROCEDURE/PROCEDURE
    Processing object type SCHEMA_EXPORT/PROCEDURE/ALTER_PROCEDURE
    Processing object type SCHEMA_EXPORT/VIEW/VIEW
    Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/REF_CONSTRAINT
    Processing object type SCHEMA_EXPORT/TABLE/TRIGGER
    Processing object type SCHEMA_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
    . . exported "HR"."COUNTRIES" 6.085 KB 25 rows
    . . exported "HR"."DEPARTMENTS" 6.632 KB 27 rows
    . . exported "HR"."EMPLOYEES" 15.76 KB 107 rows
    . . exported "HR"."JOBS" 6.609 KB 19 rows
    . . exported "HR"."JOB_HISTORY" 6.585 KB 10 rows
    . . exported "HR"."LOCATIONS" 7.710 KB 23 rows
    . . exported "HR"."REGIONS" 5.289 KB 4 rows
    Master table "SYS"."SYS_EXPORT_SCHEMA_01" successfully loaded/unloaded
    Dump file set for SYS.SYS_EXPORT_SCHEMA_01 is:
    /d01/app/oracle/product/10.2.0/db/admin/orcl/dpdump/hrschema.dmp
    ^[[AJob "SYS"."SYS_EXPORT_SCHEMA_01" successfully completed at 09:45:50
    *transfering the schema dump file to appliaction server..............................*
    [oracle@test dpdump]$ scp hrschema.dmp apps:/d01/backupdp/hrschema.dmp
    oracle@apps's password:
    hrschema.dmp 100% 596KB 596.0KB/s 00:00
    [oracle@test dpdump]$
    Now importing datapump schema from that dump file............................
    [oracle@apps backupdp]$ ls
    example01.dbf hrschema.dmp
    [oracle@apps backupdp]$ impdp DIRECTORY=backupdp DUMPFILE=hrschema.dmp logfile=hrschema.log SCHEMAS=hr
    Import: Release 10.1.0.4.2 - Production on Friday, 30 April, 2010 9:54
    Copyright (c) 2003, Oracle. All rights reserved.
    Username: sys as sysdba
    Password:
    Connected to: Oracle Database 10g Enterprise Edition Release 10.1.0.4.2 - Production
    With the Partitioning, OLAP and Data Mining options
    Master table "SYS"."SYS_IMPORT_SCHEMA_01" successfully loaded/unloaded
    Starting "SYS"."SYS_IMPORT_SCHEMA_01": sys/******** AS SYSDBA DIRECTORY=backupdp DUMPFILE=hrschema.dmp logfile=hrschema.log SCHEMAS=hr
    Processing object type SCHEMA_EXPORT/USER
    ORA-31684: Object type USER:"HR" already exists
    Processing object type SCHEMA_EXPORT/SYSTEM_GRANT
    Processing object type SCHEMA_EXPORT/ROLE_GRANT
    Processing object type SCHEMA_EXPORT/DEFAULT_ROLE
    Processing object type SCHEMA_EXPORT/PRE_SCHEMA/PROCACT_SCHEMA
    Processing object type SCHEMA_EXPORT/SEQUENCE/SEQUENCE
    Processing object type SCHEMA_EXPORT/TABLE/TABLE
    ORA-39083: Object type TABLE failed to create with error:
    ORA-00959: tablespace 'EXAMPLE' does not exist
    Failing sql is:
    CREATE TABLE "HR"."COUNTRIES" ("COUNTRY_ID" CHAR(2) CONSTRAINT "COUNTRY_ID_NN" NOT NULL ENABLE, "COUNTRY_NAME" VARCHAR2(40), "REGION_ID" NUMBER, CONSTRAINT "COUNTRY_C_ID_PK" PRIMARY KEY ("COUNTRY_ID") ENABLE) ORGANIZATION INDEX NOCOMPRESS PCTFREE 10 INITRANS 2 MAXTRANS 255 NOLOGGING STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 FREELISTS 1 FREELIST
    ORA-39083: Object type TABLE failed to create with error:
    ORA-00959: tablespace 'EXAMPLE' does not exist
    Failing sql is:
    CREATE TABLE "HR"."REGIONS" ("REGION_ID" NUMBER CONSTRAINT "REGION_ID_NN" NOT NULL ENABLE, "REGION_NAME" VARCHAR2(25)) PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 NOCOMPRESS NOLOGGING STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT) TABLESPACE "EXAMPLE"
    ORA-39083: Object type TABLE failed to create with error:
    ORA-00959: tablespace 'EXAMPLE' does not exist
    Failing sql is:
    CREATE TABLE "HR"."LOCATIONS" ("LOCATION_ID" NUMBER(4,0), "STREET_ADDRESS" VARCHAR2(40), "POSTAL_CODE" VARCHAR2(12), "CITY" VARCHAR2(30) CONSTRAINT "LOC_CITY_NN" NOT NULL ENABLE, "STATE_PROVINCE" VARCHAR2(25), "COUNTRY_ID" CHAR(2)) PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 NOCOMPRESS NOLOGGING STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 FREELI
    ORA-39083: Object type TABLE failed to create with error:
    ORA-00959: tablespace 'EXAMPLE' does not exist
    Failing sql is:
    CREATE TABLE "HR"."DEPARTMENTS" ("DEPARTMENT_ID" NUMBER(4,0), "DEPARTMENT_NAME" VARCHAR2(30) CONSTRAINT "DEPT_NAME_NN" NOT NULL ENABLE, "MANAGER_ID" NUMBER(6,0), "LOCATION_ID" NUMBER(4,0)) PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 NOCOMPRESS NOLOGGING STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT
    ORA-39083: Object type TABLE failed to create with error:
    ORA-00959: tablespace 'EXAMPLE' does not exist
    Failing sql is:
    CREATE TABLE "HR"."JOBS" ("JOB_ID" VARCHAR2(10), "JOB_TITLE" VARCHAR2(35) CONSTRAINT "JOB_TITLE_NN" NOT NULL ENABLE, "MIN_SALARY" NUMBER(6,0), "MAX_SALARY" NUMBER(6,0)) PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 NOCOMPRESS NOLOGGING STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT) TABLESPACE "EXAMPL
    ORA-39083: Object type TABLE failed to create with error:
    ORA-00959: tablespace 'EXAMPLE' does not exist
    Failing sql is:
    CREATE TABLE "HR"."EMPLOYEES" ("EMPLOYEE_ID" NUMBER(6,0), "FIRST_NAME" VARCHAR2(20), "LAST_NAME" VARCHAR2(25) CONSTRAINT "EMP_LAST_NAME_NN" NOT NULL ENABLE, "EMAIL" VARCHAR2(25) CONSTRAINT "EMP_EMAIL_NN" NOT NULL ENABLE, "PHONE_NUMBER" VARCHAR2(20), "HIRE_DATE" DATE CONSTRAINT "EMP_HIRE_DATE_NN" NOT NULL ENABLE, "JOB_ID" VARCHAR2(10) CONSTRAINT "EMP_JOB_NN" NOT NULL ENABLE, "SALARY" NUM
    ORA-39083: Object type TABLE failed to create with error:
    ORA-00959: tablespace 'EXAMPLE' does not exist
    Failing sql is:
    CREATE TABLE "HR"."JOB_HISTORY" ("EMPLOYEE_ID" NUMBER(6,0) CONSTRAINT "JHIST_EMPLOYEE_NN" NOT NULL ENABLE, "START_DATE" DATE CONSTRAINT "JHIST_START_DATE_NN" NOT NULL ENABLE, "END_DATE" DATE CONSTRAINT "JHIST_END_DATE_NN" NOT NULL ENABLE, "JOB_ID" VARCHAR2(10) CONSTRAINT "JHIST_JOB_NN" NOT NULL ENABLE, "DEPARTMENT_ID" NUMBER(4,0)) PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 NOCOMPRESS
    Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
    Processing object type SCHEMA_EXPORT/TABLE/GRANT/OWNER_GRANT/OBJECT_GRANT
    ORA-39112: Dependent object type OBJECT_GRANT:"HR" skipped, base object type TABLE:"HR"."COUNTRIES" creation failed
    ORA-39112: Dependent object type OBJECT_GRANT:"HR" skipped, base object type TABLE:"HR"."COUNTRIES" creation failed
    ORA-39112: Dependent object type OBJECT_GRANT:"HR" skipped, base object type TABLE:"HR"."LOCATIONS" creation failed
    ORA-39112: Dependent object type OBJECT_GRANT:"HR" skipped, base object type TABLE:"HR"."LOCATIONS" creation failed
    ORA-39112: Dependent object type OBJECT_GRANT:"HR" skipped, base object type TABLE:"HR"."DEPARTMENTS" creation failed
    ORA-39112: Dependent object type OBJECT_GRANT:"HR" skipped, base object type TABLE:"HR"."JOBS" creation failed
    ORA-39112: Dependent object type OBJECT_GRANT:"HR" skipped, base object type TABLE:"HR"."EMPLOYEES" creation failed
    ORA-39112: Dependent object type OBJECT_GRANT:"HR" skipped, base object type TABLE:"HR"."EMPLOYEES" creation failed
    ORA-39112: Dependent object type OBJECT_GRANT:"HR" skipped, base object type TABLE:"HR"."JOB_HISTORY" creation failed
    Processing object type SCHEMA_EXPORT/TABLE/INDEX/INDEX
    ORA-39112: Dependent object type INDEX:"HR"."REG_ID_PK" skipped, base object type TABLE:"HR"."REGIONS" creation failed
    ORA-39112: Dependent object type INDEX:"HR"."LOC_ID_PK" skipped, base object type TABLE:"HR"."LOCATIONS" creation failed
    ORA-39112: Dependent object type INDEX:"HR"."LOC_CITY_IX" skipped, base object type TABLE:"HR"."LOCATIONS" creation failed
    ORA-39112: Dependent object type INDEX:"HR"."LOC_STATE_PROVINCE_IX" skipped, base object type TABLE:"HR"."LOCATIONS" creation failed
    ORA-39112: Dependent object type INDEX:"HR"."LOC_COUNTRY_IX" skipped, base object type TABLE:"HR"."LOCATIONS" creation failed
    ORA-39112: Dependent object type INDEX:"HR"."DEPT_ID_PK" skipped, base object type TABLE:"HR"."DEPARTMENTS" creation failed
    ORA-39112: Dependent object type INDEX:"HR"."DEPT_LOCATION_IX" skipped, base object type TABLE:"HR"."DEPARTMENTS" creation failed
    ORA-39112: Dependent object type INDEX:"HR"."JOB_ID_PK" skipped, base object type TABLE:"HR"."JOBS" creation failed
    ORA-39112: Dependent object type INDEX:"HR"."EMP_EMAIL_UK" skipped, base object type TABLE:"HR"."EMPLOYEES" creation failed
    ORA-39112: Dependent object type INDEX:"HR"."EMP_EMP_ID_PK" skipped, base object type TABLE:"HR"."EMPLOYEES" creation failed
    ORA-39112: Dependent object type INDEX:"HR"."EMP_DEPARTMENT_IX" skipped, base object type TABLE:"HR"."EMPLOYEES" creation failed
    ORA-39112: Dependent object type INDEX:"HR"."EMP_JOB_IX" skipped, base object type TABLE:"HR"."EMPLOYEES" creation failed
    ORA-39112: Dependent object type INDEX:"HR"."EMP_MANAGER_IX" skipped, base object type TABLE:"HR"."EMPLOYEES" creation failed
    ORA-39112: Dependent object type INDEX:"HR"."EMP_NAME_IX" skipped, base object type TABLE:"HR"."EMPLOYEES" creation failed
    ORA-39112: Dependent object type INDEX:"HR"."JHIST_EMP_ID_ST_DATE_PK" skipped, base object type TABLE:"HR"."JOB_HISTORY" creation failed
    ORA-39112: Dependent object type INDEX:"HR"."JHIST_JOB_IX" skipped, base object type TABLE:"HR"."JOB_HISTORY" creation failed
    ORA-39112: Dependent object type INDEX:"HR"."JHIST_EMPLOYEE_IX" skipped, base object type TABLE:"HR"."JOB_HISTORY" creation failed
    ORA-39112: Dependent object type INDEX:"HR"."JHIST_DEPARTMENT_IX" skipped, base object type TABLE:"HR"."JOB_HISTORY" creation failed
    Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
    ORA-39112: Dependent object type CONSTRAINT:"HR"."REG_ID_PK" skipped, base object type TABLE:"HR"."REGIONS" creation failed
    ORA-39112: Dependent object type CONSTRAINT:"HR"."LOC_ID_PK" skipped, base object type TABLE:"HR"."LOCATIONS" creation failed
    ORA-39112: Dependent object type CONSTRAINT:"HR"."DEPT_ID_PK" skipped, base object type TABLE:"HR"."DEPARTMENTS" creation failed
    ORA-39112: Dependent object type CONSTRAINT:"HR"."JOB_ID_PK" skipped, base object type TABLE:"HR"."JOBS" creation failed
    ORA-39112: Dependent object type CONSTRAINT:"HR"."EMP_SALARY_MIN" skipped, base object type TABLE:"HR"."EMPLOYEES" creation failed
    ORA-39112: Dependent object type CONSTRAINT:"HR"."EMP_EMAIL_UK" skipped, base object type TABLE:"HR"."EMPLOYEES" creation failed
    ORA-39112: Dependent object type CONSTRAINT:"HR"."EMP_EMP_ID_PK" skipped, base object type TABLE:"HR"."EMPLOYEES" creation failed
    ORA-39112: Dependent object type CONSTRAINT:"HR"."JHIST_DATE_INTERVAL" skipped, base object type TABLE:"HR"."JOB_HISTORY" creation failed
    ORA-39112: Dependent object type CONSTRAINT:"HR"."JHIST_EMP_ID_ST_DATE_PK" skipped, base object type TABLE:"HR"."JOB_HISTORY" creation failed
    Processing object type SCHEMA_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS
    ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"HR"."REG_ID_PK" creation failed
    ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type TABLE:"HR"."COUNTRIES" creation failed
    ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"HR"."LOC_ID_PK" creation failed
    ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"HR"."LOC_CITY_IX" creation failed
    ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"HR"."LOC_STATE_PROVINCE_IX" creation failed
    ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"HR"."LOC_COUNTRY_IX" creation failed
    ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"HR"."DEPT_ID_PK" creation failed
    ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"HR"."DEPT_LOCATION_IX" creation failed
    ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"HR"."JOB_ID_PK" creation failed
    ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"HR"."EMP_EMAIL_UK" creation failed
    ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"HR"."EMP_EMP_ID_PK" creation failed
    ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"HR"."EMP_DEPARTMENT_IX" creation failed
    ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"HR"."EMP_JOB_IX" creation failed
    ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"HR"."EMP_MANAGER_IX" creation failed
    ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"HR"."EMP_NAME_IX" creation failed
    ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"HR"."JHIST_EMP_ID_ST_DATE_PK" creation failed
    ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"HR"."JHIST_JOB_IX" creation failed
    ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"HR"."JHIST_EMPLOYEE_IX" creation failed
    ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"HR"."JHIST_DEPARTMENT_IX" creation failed
    Processing object type SCHEMA_EXPORT/TABLE/COMMENT
    ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."COUNTRIES" creation failed
    ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."COUNTRIES" creation failed
    ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."COUNTRIES" creation failed
    ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."COUNTRIES" creation failed
    ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."LOCATIONS" creation failed
    ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."LOCATIONS" creation failed
    ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."LOCATIONS" creation failed
    ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."LOCATIONS" creation failed
    ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."LOCATIONS" creation failed
    ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."LOCATIONS" creation failed
    ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."LOCATIONS" creation failed
    ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."DEPARTMENTS" creation failed
    ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."DEPARTMENTS" creation failed
    ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."DEPARTMENTS" creation failed
    ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."DEPARTMENTS" creation failed
    ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."DEPARTMENTS" creation failed
    ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."JOBS" creation failed
    ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."JOBS" creation failed
    ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."JOBS" creation failed
    ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."JOBS" creation failed
    ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."JOBS" creation failed
    ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."EMPLOYEES" creation failed
    ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."EMPLOYEES" creation failed
    ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."EMPLOYEES" creation failed
    ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."EMPLOYEES" creation failed
    ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."EMPLOYEES" creation failed
    ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."EMPLOYEES" creation failed
    ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."EMPLOYEES" creation failed
    ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."EMPLOYEES" creation failed
    ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."EMPLOYEES" creation failed
    ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."EMPLOYEES" creation failed
    ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."EMPLOYEES" creation failed
    ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."EMPLOYEES" creation failed
    ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."JOB_HISTORY" creation failed
    ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."JOB_HISTORY" creation failed
    ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."JOB_HISTORY" creation failed
    ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."JOB_HISTORY" creation failed
    ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."JOB_HISTORY" creation failed
    ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"HR"."JOB_HISTORY" creation failed
    Processing object type SCHEMA_EXPORT/PROCEDURE/PROCEDURE
    Processing object type SCHEMA_EXPORT/PROCEDURE/ALTER_PROCEDURE
    ORA-39082: Object type ALTER_PROCEDURE:"HR"."ADD_JOB_HISTORY" created with compilation warnings
    Processing object type SCHEMA_EXPORT/VIEW/VIEW
    ORA-39082: Object type VIEW:"HR"."EMP_DETAILS_VIEW" created with compilation warnings
    Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/REF_CONSTRAINT
    ORA-39112: Dependent object type REF_CONSTRAINT:"HR"."COUNTR_REG_FK" skipped, base object type TABLE:"HR"."COUNTRIES" creation failed
    ORA-39112: Dependent object type REF_CONSTRAINT:"HR"."LOC_C_ID_FK" skipped, base object type TABLE:"HR"."LOCATIONS" creation failed
    ORA-39112: Dependent object type REF_CONSTRAINT:"HR"."DEPT_MGR_FK" skipped, base object type TABLE:"HR"."DEPARTMENTS" creation failed
    ORA-39112: Dependent object type REF_CONSTRAINT:"HR"."DEPT_LOC_FK" skipped, base object type TABLE:"HR"."DEPARTMENTS" creation failed
    ORA-39112: Dependent object type REF_CONSTRAINT:"HR"."EMP_MANAGER_FK" skipped, base object type TABLE:"HR"."EMPLOYEES" creation failed
    ORA-39112: Dependent object type REF_CONSTRAINT:"HR"."EMP_JOB_FK" skipped, base object type TABLE:"HR"."EMPLOYEES" creation failed
    ORA-39112: Dependent object type REF_CONSTRAINT:"HR"."EMP_DEPT_FK" skipped, base object type TABLE:"HR"."EMPLOYEES" creation failed
    ORA-39112: Dependent object type REF_CONSTRAINT:"HR"."JHIST_DEPT_FK" skipped, base object type TABLE:"HR"."JOB_HISTORY" creation failed
    ORA-39112: Dependent object type REF_CONSTRAINT:"HR"."JHIST_EMP_FK" skipped, base object type TABLE:"HR"."JOB_HISTORY" creation failed
    ORA-39112: Dependent object type REF_CONSTRAINT:"HR"."JHIST_JOB_FK" skipped, base object type TABLE:"HR"."JOB_HISTORY" creation failed
    Processing object type SCHEMA_EXPORT/TABLE/TRIGGER
    ORA-39112: Dependent object type TRIGGER:"HR"."SECURE_EMPLOYEES" skipped, base object type TABLE:"HR"."EMPLOYEES" creation failed
    ORA-39112: Dependent object type TRIGGER:"HR"."UPDATE_JOB_HISTORY" skipped, base object type TABLE:"HR"."EMPLOYEES" creation failed
    Processing object type SCHEMA_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
    ORA-39112: Dependent object type TABLE_STATISTICS skipped, base object type TABLE:"HR"."REGIONS" creation failed
    ORA-39112: Dependent object type TABLE_STATISTICS skipped, base object type TABLE:"HR"."COUNTRIES" creation failed
    ORA-39112: Dependent object type TABLE_STATISTICS skipped, base object type TABLE:"HR"."LOCATIONS" creation failed
    ORA-39112: Dependent object type TABLE_STATISTICS skipped, base object type TABLE:"HR"."DEPARTMENTS" creation failed
    ORA-39112: Dependent object type TABLE_STATISTICS skipped, base object type TABLE:"HR"."JOBS" creation failed
    ORA-39112: Dependent object type TABLE_STATISTICS skipped, base object type TABLE:"HR"."EMPLOYEES" creation failed
    ORA-39112: Dependent object type TABLE_STATISTICS skipped, base object type TABLE:"HR"."JOB_HISTORY" creation failed
    Job "SYS"."SYS_IMPORT_SCHEMA_01" completed with 123 error(s) at 09:55
    [oracle@apps backupdp]$ ls
    example01.dbf hrschema.dmp hrschema.log
    *[oracle@apps backupdp]$ more hrschema.log*
    Import: Release 10.1.0.4.2 - Production on Friday, 30 April, 2010 9:54
    Copyright (c) 2003, Oracle. All rights reserved.
    Connected to: Oracle Database 10g Enterprise Edition Release 10.1.0.4.2 - Producti
    on
    With the Partitioning, OLAP and Data Mining options
    Master table "SYS"."SYS_IMPORT_SCHEMA_01" successfully loaded/unloaded
    Starting "SYS"."SYS_IMPORT_SCHEMA_01": sys/******** AS SYSDBA DIRECTORY=backupdp
    DUMPFILE=hrschema.dmp logfile=hrschema.log SCHEMAS=hr
    Processing object type SCHEMA_EXPORT/USER
    ORA-31684: Object type USER:"HR" already exists
    Processing object type SCHEMA_EXPORT/SYSTEM_GRANT
    Processing object type SCHEMA_EXPORT/ROLE_GRANT
    Processing object type SCHEMA_EXPORT/DEFAULT_ROLE
    Processing object type SCHEMA_EXPORT/PRE_SCHEMA/PROCACT_SCHEMA
    Processing object type SCHEMA_EXPORT/SEQUENCE/SEQUENCE
    Processing object type SCHEMA_EXPORT/TABLE/TABLE
    ORA-39083: Object type TABLE failed to create with error:
    *ORA-00959: tablespace 'EXAMPLE' does not exist*
    Failing sql is:
    CREATE TABLE "HR"."COUNTRIES" ("COUNTRY_ID" CHAR(2) CONSTRAINT "COUNTRY_ID_NN" NOT
    NULL ENABLE, "COUNTRY_NAME" VARCHAR2(40), "REGION_ID" NUMBER, CONSTRAINT "COUNTR
    Y_C_ID_PK" PRIMARY KEY ("COUNTRY_ID") ENABLE) ORGANIZATION INDEX NOCOMPRESS PCTFRE
    E 10 INITRANS 2 MAXTRANS 255 NOLOGGING STORAGE(INITIAL 65536 NEXT 1048576 MINEXTEN
    TS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 FREELISTS 1 FREELIST
    ORA-39083: Object type TABLE failed to create with error:
    ORA-00959: tablespace 'EXAMPLE' does not exist
    Failing sql is:
    CREATE TABLE "HR"."REGIONS" ("REGION_ID" NUMBER CONSTRAINT "REGION_ID_NN" NOT NULL
    [oracle@apps backupdp]$
    [oracle@apps backupdp]$
    now it is giving error that EXAMPLE tablespace doesnot exist .....so now should i use transporatble tablespace for to trasport example tablepsace from oracle 10g to application server 10g.
    please help.......

    Then i use Transportable tablespaces for transporting example tablespace to application server from oracle 10g.....................
    exported in oracle 10g;
    [oracle@test orcl]$ sqlplus / as sysdba
    SQL*Plus: Release 10.2.0.1.0 - Production on Fri Apr 30 10:08:06 2010
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    Connected to:
    Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
    With the Partitioning, OLAP and Data Mining options
    SQL>
    SQL> alter tablespace example read only;
    alter tablespace example read only
    ERROR at line 1:
    ORA-01644: tablespace 'EXAMPLE' is already read only
    [oracle@test dpdump]$ expdp DIRECTORY=DATA_PUMP_DIR DUMPFILE=exampletbs.dmp transport_tablespaces=example logfile=exampletbs.log version=10.1.0.4.2;
    Export: Release 10.2.0.1.0 - Production on Friday, 30 April, 2010 10:03:29
    Copyright (c) 2003, 2005, Oracle. All rights reserved.
    Username: sys as sysdba
    Password:
    Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
    With the Partitioning, OLAP and Data Mining options
    Starting "SYS"."SYS_EXPORT_TRANSPORTABLE_01": sys/******** AS SYSDBA DIRECTORY=DATA_PUMP_DIR DUMPFILE=exampletbs.dmp transport_tablespaces=example logfile=exampletbs.log version=10.1.0.4.2
    Processing object type TRANSPORTABLE_EXPORT/PLUGTS_BLK
    Processing object type TRANSPORTABLE_EXPORT/TYPE/TYPE_SPEC
    Processing object type TRANSPORTABLE_EXPORT/TABLE
    Processing object type TRANSPORTABLE_EXPORT/GRANT/OWNER_GRANT/OBJECT_GRANT
    Processing object type TRANSPORTABLE_EXPORT/INDEX
    Processing object type TRANSPORTABLE_EXPORT/CONSTRAINT/CONSTRAINT
    Processing object type TRANSPORTABLE_EXPORT/INDEX_STATISTICS
    Processing object type TRANSPORTABLE_EXPORT/COMMENT
    Processing object type TRANSPORTABLE_EXPORT/CONSTRAINT/REF_CONSTRAINT
    Processing object type TRANSPORTABLE_EXPORT/TRIGGER
    Processing object type TRANSPORTABLE_EXPORT/INDEX/FUNCTIONAL_AND_BITMAP/INDEX
    Processing object type TRANSPORTABLE_EXPORT/INDEX/STATISTICS/FUNCTIONAL_AND_BITMAP/INDEX_STATISTICS
    Processing object type TRANSPORTABLE_EXPORT/TABLE_STATISTICS
    Processing object type TRANSPORTABLE_EXPORT/DOMAIN_INDEX/INDEX
    Processing object type TRANSPORTABLE_EXPORT/MATERIALIZED_VIEW
    Processing object type TRANSPORTABLE_EXPORT/POST_INSTANCE/PROCACT_INSTANCE
    Processing object type TRANSPORTABLE_EXPORT/POST_INSTANCE/PROCDEPOBJ
    Processing object type TRANSPORTABLE_EXPORT/POST_INSTANCE/PLUGTS_BLK
    Master table "SYS"."SYS_EXPORT_TRANSPORTABLE_01" successfully loaded/unloaded
    Dump file set for SYS.SYS_EXPORT_TRANSPORTABLE_01 is:
    /d01/app/oracle/product/10.2.0/db/admin/orcl/dpdump/exampletbs.dmp
    Job "SYS"."SYS_EXPORT_TRANSPORTABLE_01" successfully completed at 10:04:01
    transfer the example datafile to application server.............
    [oracle@test dpdump]$ scp exampletbs.dmp apps:/d01/backupdp/exampletbs.dmp
    oracle@apps's password:
    exampletbs.dmp 100% 3528KB 3.5MB/s 00:00
    [oracle@test dpdump]$
    [oracle@test dpdump]$
    Import in oracle application server................
    [oracle@apps backupdp]$ ls
    exampletbs.dmp hrschema.dmp hrschema.log
    [oracle@apps backupdp]$ impdp DIRECTORY=backupdp DUMPFILE=exampletbs.dmp transport_datafiles='/d01/backupdp/example01.dbf' logfile=exampletbs.log;
    Import: Release 10.1.0.4.2 - Production on Friday, 30 April, 2010 10:20
    Copyright (c) 2003, Oracle. All rights reserved.
    Username: sys as sysdba
    Password:
    Connected to: Oracle Database 10g Enterprise Edition Release 10.1.0.4.2 - Production
    With the Partitioning, OLAP and Data Mining options
    Master table "SYS"."SYS_IMPORT_TRANSPORTABLE_03" successfully loaded/unloaded
    Starting "SYS"."SYS_IMPORT_TRANSPORTABLE_03": sys/******** AS SYSDBA DIRECTORY=backupdp DUMPFILE=exampletbs.dmp transport_datafiles=/d01/backupdp/example01.dbf logfile=exampletbs.log
    Processing object type TRANSPORTABLE_EXPORT/PLUGTS_BLK
    ORA-39123: Data Pump transportable tablespace job aborted
    ORA-00721: changes by release 10.2.0.1.0 cannot be used by release 10.1.0.2.0
    Job "SYS"."SYS_IMPORT_TRANSPORTABLE_03" stopped due to fatal error at 10:21
    [oracle@apps backupdp]$
    [oracle@apps backupdp]$ more exampletbs.log
    Import: Release 10.1.0.4.2 - Production on Friday, 30 April, 2010 10:20
    Copyright (c) 2003, Oracle. All rights reserved.
    Connected to: Oracle Database 10g Enterprise Edition Release 10.1.0.4.2 - Producti
    on
    With the Partitioning, OLAP and Data Mining options
    Master table "SYS"."SYS_IMPORT_TRANSPORTABLE_03" successfully loaded/unloaded
    Starting "SYS"."SYS_IMPORT_TRANSPORTABLE_03": sys/******** AS SYSDBA DIRECTORY=ba
    ckupdp DUMPFILE=exampletbs.dmp transport_datafiles=/d01/backupdp/example01.dbf log
    file=exampletbs.log
    Processing object type TRANSPORTABLE_EXPORT/PLUGTS_BLK
    ORA-39123: Data Pump transportable tablespace job aborted
    ORA-00721: changes by release 10.2.0.1.0 cannot be used by release 10.1.0.2.0
    Job "SYS"."SYS_IMPORT_TRANSPORTABLE_03" stopped due to fatal error at 10:21
    [oracle@apps backupdp]$
    please can anybody help........................

  • Why an "ORA-01006: bind variable does not exist" error when no dynamic SQL?

    Hi all,
    While running PL/SQL in SQL Developer 3.2.09, I got the following error after adding a section of code. Note that nothing I'm doing has anything to do with dynamic SQL (which is what 01006 is supposedly about).
    Error report:
    ORA-01006: bind variable does not exist
    01006. 00000 - "bind variable does not exist"
    *Cause:   
    *Action:
    After commenting out the new chunk of code that caused the error, the error persisted.
    After deleting the new code, the error went away.
    What the heck!?!? If you have any ideas, please lay 'em on me.
    Thanks so much,
    Kim
    P.S. It's a few hundred lines of code, so I didn't append it to this post and I don't see how to attach a file.

    Let's review a few facts:
    1. You post a question in the sql developer forum that has no apparent relation to sql developer. You could confirm this by doing the test using sql*plus or some other tool.
    2. You provide NO information about what database you are even using. The only clue is an ORA -xxx message that means SOME version of Oracle is involved.
    3. You provide NO information about what the four digit version of Oracle DB is being used.
    4. You provide NO information about what the code in general or what that specific section of the code is even doing. The code could be doing literally anything that Oracle is capable of doing.
    That's a bit like calling a mechanic you don't know, telling them your car is making a funny noise and asking them what the problem with your car is.
    >
    While running PL/SQL in SQL Developer 3.2.09, I got the following error after adding a section of code. Note that nothing I'm doing has anything to do with dynamic SQL (which is what 01006 is supposedly about).
    Error report:
    ORA-01006: bind variable does not exist
    01006. 00000 - "bind variable does not exist"
    *Cause:
    *Action:
    The error gives no indication of where the error occurred in the code.
    >
    Your first clue that your troubleshooting method is seriously flawed is when you make statements that aren't supported by any evidence at all but appear to be nothing but your opinion.
    Your second clue is when those statements appear to directly contradict what Oracle is telling you.
    I'm talking about these two statements you make; which you state as if they were universal truths
    >
    nothing I'm doing has anything to do with dynamic SQL
    (which is what 01006 is supposedly about).
    >
    If thoe were true then your 'unstated' conclusion appears to be that Oracle is wrong in saying 'bind variable does not exist'
    Sorry - but I would place my money on Oracle.
    I'm sure the above may sound harsh - it is intended to be. My four major rules (there are more) when troubleshooting Oracle problems.
    1. Assume that Oracle is CORRECT when it tells you there is a problem.
    2. Assume that you are WRONG if your opinion conflicts with what Oracle is telling you - see rule #1.
    3. Don't make ANY other assumptions. You can form hypotheses but don't state them as facts until they are proven.
    4. Your 'opinion' is only useful to the extent that it can help you form meaningful hypotheses - see rule #3.
    >
    To reiterate, there is no dynamic SQL in the code.
    >
    To reiterate - if, as you state, that error relates to dynamic SQL and bind variables then it can not be disputed that:
    ORACLE DOESN'T AGREE WITH YOU!
    So let's try it my way and hypothesize that Oracle is correct (see rule #1 above).
    Then by definition this statement by Oracle is correct
    >
    ORA-01006: bind variable does not exist
    >
    And that should immediately raise this question:
    1. where might there be a bind variable that does not exist?
    which leads to a prerequisite question:
    2. where are ALL of the bind variables that might be being used?
    Question #2 is where you need to start your search. Here are at least five possibilities (there are more)
    1. your code - this should be easiest to check and you state that your 'anonymous' block does not have any.
    2. a table trigger - triggers that use the :NEW, :OLD or :PARENT pseudocolumns. Those psuedocolumns are BIND variables and the trigger code that uses them is, by definition, dynamic sql.
    3. a pl/sql package/function/procedure - any of these might be being called from trigger code or a view that is involved in the transaction. Any of these could take a parameter and/or use bind variables and cause your problem if that bind variable does 'not exist'.
    4. a functional index - can also trigger code from #3 above
    5. an audit trigger that logs the audit activity that your user or your code is performing. This code could be trying to use a SYS_CONTEXT environment variable that has not been created and cause a 'bind variable does not exist' error.
    See rule #1 - Oracle is CORRECT. Until you have identified and examined ALL of the code (not just your anonymous block) being executed and ruled it out you should continue with the hypotheses that Oracle is CORRECT.
    In the (extremely) unlikely event that you can show that Oracle is NOT correct you should file a SOR with Oracle.

  • Warning: Index does not exist in database system MSSQL

    Hi,
    After activating the Index from SE11,
    I receive the following Warning:
    Index does not exist in database system MSSQL.
    What does this mean? Has performance been increased or does the index 1st have to exist in the database system MSSQL?

    When you create index at SE11 and you need activate database utility.
    utilitities-database utility->then click activate and adjust database.
    else you can use SE14 and so that Index will create databse level.
    Reward Points if it is helpful
    Thanks
    Seshu

  • Index does not exist in database system ORACLE??????

    Hi Experts,
    I created a Secondary Index in DEV, its fine and the message is,
    <b><i>Index KNA1~Z01 exists in database system ORACLE</i></b>
    I moved it to TEST and there I got the message is like,
    <i><b>Index does not exist in database system ORACLE</b></i>
    So,
    1 - Wht I hv to do now? Shuld I see BASIS people?
    2- Why its happened like that? Coz of not enough space?
    ThanQ.

    thanq sudheer,
    I got the return code as 4, so Can I go for creation of new request and there by moving to test?
    1 - Anyways, so, after Activating Seconadyr Index, Shuld I come back and Do I need to activate the Table also?
    or
    2- Just activating the index is enough?
    thanq.
    Message was edited by:
            Srikhar

  • Index does not exist in database system DB6 sap

    Hi All
    In development system i have added a field into already existing  index and activated successfully without any errors or warnings and after transported the TR  into Quality system,In Quality system it shows the warning Index does not exist in database system DB6 sap
    Thanks
    Vamsi

    Hi Mohan,
    After any change in the existing structure of the table you need to adjust and then activate it.
    It can be done using SE14 tcode, please try using this.
    Regards,
    Mohammed

  • Index Does Not Exist In Database System MSSQL

    Hello,
    I have an Index that has this message:
    " Index Does Not Exist In Database System MSSQL"
    Can someone guide me how to update Index to the database?
    Thank you.

    Check this thread:
    missing primary index
    Otherwise, a few more informations would help! Thanks.

  • Index does not exist in database system DB6

    Hi,
    Problem : <b>Index does not exist in database system DB6</b>.
    I need further explanation why when i transport index from Development Client to Production Client the index is active but does not exist in database system DB6.
    So when the cases is occurs i must re-create the index again in Production Level...
    Can someone give me some ideas?
    Thanks.

    Hi,
    it might be due to some BUG in RDBMS...
    First Check the Secondary index in TEST system
    Look at the Transport Number in DEV system, If this is having error, then it will show you the error details also,
    If that not moved Properly then you need to create another request for the INDEX and move it again
    See the threads with similar problem...
    Warning: Index does not exist in database system MSSQL
    Index does not exist in database system ORACLE??????
    Re creation of database index
    Hope it will solve your problem...
    <b>Reward Points if useful</b>
    Thanks & Regards
    ilesh 24x7

Maybe you are looking for