ORACLE error 959 encountered ORA-00959: tablespace 'xyz' does not exist

im importing a dump to a newly created BD and im using 11g. I have already tablespaces and user for the dump to be imported.
The problems is, i have a total of 5 tablespaces created, all 4 are working well except the one tablespace and im receiving a 959 error(IMP-00003: ORACLE error 959 encountered
ORA-00959: tablespace 'xyz' does not exist). The log mentions that the tablespace does not exist even if this tablespace exist in the list of tablespace and datafiles created.
Hope you could help me with this. Thanks
Edited by: user8667617 on Feb 18, 2010 11:06 PM

SQL> Select name from v$datafile;
NAME
C:\APP\ORACLEADMIN\ORADATA\ORC11\SYSTEM01.DBF
C:\APP\ORACLEADMIN\ORADATA\ORC11\SYSAUX01.DBF
F:\ORC11DBUNDO\UNDOTBS01.DBF
E:\ORC11DBUSER\USERS01.DBF
E:\ORC11DBUSER\INT_TRANSACTIONS_DATA.DBF
E:\ORC11DBUSER\INT_DATA.DBF
E:\ORC11DBUSER\CAS_DATA.DBF
E:\ORC11DBUSER\COS_DATA.DBF
E:\ORC11DBUSER\INT_ONLINE_TRANSACTIONS_DATA.DBF
9 rows selected.
SQL> Select * from v$tablespace;
TS# NAME INC BIG FLA ENC
0 SYSTEM YES NO YES
1 SYSAUX YES NO YES
2 UNDOTBS1 YES NO YES
4 USERS YES NO YES
3 TEMP NO NO YES
6 INT_TRANSACTIONS_DATA YES NO YES
7 INT_DATA YES NO YES
8 CAS_DATA YES NO YES
9 COS_DATA YES NO YES
10 INT_ONLINE_TRANSACTIONS_DATA YES NO YES
10 rows selected.
SQL>
here are the result of my query and it seems that the tablespace is recognized by the DB.
is there still any reason why? also when i try to drop the said tablespace in getting a response of the "tablespace does not exist" but when i try to create the tablespace it says that "ORA-00604: error occurred at recursive SQL level 1
ORA-00001: unique constraint (SYS.I_TS1) violated"
hope you can help me with this.

Similar Messages

  • 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

  • 11gR2 DBCA ORA-00959: tablespace 'EXAMPLE' does not exist

    Hello everyone,
    I have searched for this specific error but found nothing on it (wonder why I am always the only one having those weird problem!!!)
    When I use DBCA, interactive graphical tool, to create a database the process won't end normally if I include example schema.
    Somewhere during the process I have an error message with the following : ORA-00959: tablespace 'EXAMPLE' does not exist. <-- well, the reason why it doesn't exist is because YOU are supposed to create it .... duh!
    Anyone have experienced the same problem?
    Database, Oracle 11gR2
    OS : Solaris 10 release 10/08
    Hardware : sparc, Sun E450
    Thank you for your time and support

    up

  • 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........................

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

    Dear all
    i using oracle 10g,when i creating create catalog tablespace "rman"; given this error ora-00959: tablespace rman not exist
    i have done already this
    step-1
    SQL> create tablespace rman
    2 datafile 'e:\vvelren\rman.dbf' size 6208k reuse
    3 autoextend on next 64k maxsize 3267m
    4 extent management local
    5 segment space management auto;
    step-2
    SQL> create user rman identified by rman
    2 default tablespace rman
    3 temporary tablespace temp
    4 quota unlimited on rman;
    step 3
    SQL> grant connect,resource,recovery_catalog_owner to rman;
    tablespace rman and datafile is showing in dictionary and also online
    after connect to target database
    rman> create catalog tablespace "rman";
    given this error-> ORACLE error from recovery catalog database: ORA-00959: tablespace 'rman' does not exist
    i am unstand where i am mistake.

    after connect to target database
    rman> create catalog tablespace "rman";
    given this error-> ORACLE error from recovery catalog database: ORA-00959: tablespace 'rman' does not existYou have to connect to the recovery catalog database not the target one. Also RMAN tablespace has to be created in the recovery catalog database. Hope you created there only.

  • How to avoid this problem "tablespace 'USERS' does not exist"

    I dont want to create all source tablespaces in target.
    I have given unlimited tablespace priv to user.Still I get this error
    IMP-00003: ORACLE error 959 encountered
    ORA-00959: tablespace 'USERS' does not exist

    The situation, I understand is as follows:
    1. An original export file contains references to the USERS tablespace
    2. You want to import it, but you don't want to create the USERS tablespace
    3. You create a user and assign USERS as its default tablespace, even though you don't have it created and you don't want to create it.
    If you assign a default tablespace to a user, first thing, make sure this tablespace exists, when import is performed if tablespace defined at import file doesn't exist, then import will use the default user's tablespace, in this case the USERS tablespace.
    So, if you want to avoid this behaviour, then assign the user an existing tablespace when defining the default tablespace for this user.
    Once corrected, retry import.
    ~ Madrid

  • Exp 报EXP-00008: ORACLE error 904 encountered;ORA-00904错误

    环境:RAC11gR2+Redhat6.1
    [oracle@bppfedb1 mouse]$ exp BPPF_EAS/ApNCNOZqGx BUFFER=64000 FILE='/home/oracle/mouse/exp_bppf_tvs20121126.DMP' log='/home/oracle/mouse/exp_bppf_tvs20121126.log' OWNER=BPPF_EAS
    Export: Release 11.2.0.3.0 - Production on Tue Nov 27 00:12:16 2012
    Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
    Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
    With the Partitioning, Real Application Clusters, Automatic Storage Management, Oracle Label Security,
    OLAP, Data Mining,
    Export done in US7ASCII character set and AL16UTF16 NCHAR character set
    server uses ZHS16GBK character set (possible charset conversion)
    About to export specified users ...
    . exporting pre-schema procedural objects and actions
    . exporting foreign function library names for user BPPF_EAS
    . exporting PUBLIC type synonyms
    EXP-00008: ORACLE error 904 encountered
    ORA-00904: : invalid identifier
    EXP-00000: Export terminated unsuccessfully
    使用
    expdp BPPF_EAS/ApNCNOZqGx directory=DATA_PUMP_DIR dumpfile=exp_bppf_tvs20121126.dmp schemas=BPPF_EAS logfile=exp_bppf_tvs20121126.log
    换用expdp可以成功
    尝试了几台服务器都遇到这个问题,暂时没有找到问题的原因

    问题已解决:
    ORACLE error 904 问题是因为回收了public 的dbms_java执行权限,重新授予解决。
    trace=y需要的权限问题: 应该需要grant dba to xxx; 单exp_full_database好像不行,下面是测试的情况
    when the Data Pump TRACE parameter is used in Oracle10g Release 2 or higher, then the user who connects to the database and runs the export DataPump job needs to have the DBA role or the EXP_FULL_DATABASE role (the same applies to Import DataPump with TRACE parameter: DBA or IMP_FULL_DATABASE role required), e.g.:
    GRANT exp_full_database TO scott;
    -- or:
    GRANT dba TO expdp_role;
    测试:
    oracle@linux:~/mouse> sqlplus /nolog
    SQL*Plus: Release 11.2.0.1.0 Production on Wed Dec 5 07:23:00 2012
    Copyright (c) 1982, 2009, Oracle. All rights reserved.
    SQL> conn /as sysdba
    Connected.
    SQL> drop user mouse cascade;
    User dropped.
    SQL> create user mouse identified by mouse_2012
    2 default tablespace users
    3 temporary tablespace temp
    4 quota unlimited on users ;
    grant connect to mouse;
    grant resource to mouse;
    grant select any table to mouse;
    grant select any dictionary to mouse;
    grant exp_full_database to mouse;
    User created.
    SQL>
    Grant succeeded.
    SQL>
    Grant succeeded.
    SQL>
    Grant succeeded.
    SQL>
    Grant succeeded.
    SQL>
    Grant succeeded.
    SQL>
    SQL>
    SQL> conn mouse/mouse_2012
    create table test as select * from dba_users;Connected.
    SQL>
    Table created.
    SQL> !
    oracle@linux:~/mouse> exp mouse/mouse_2012 tables=test file=test.dmp feedback=100000 buffer=10000000 indexes=y triggers=y trace=y;
    Export: Release 11.2.0.1.0 - Production on Wed Dec 5 07:24:35 2012
    Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
    EXP-00056: ORACLE error 1031 encountered
    ORA-01031: insufficient privileges
    EXP-00000: Export terminated unsuccessfully
    oracle@linux:~/mouse> exit
    exit
    SQL> conn /as sysdba
    Connected.
    SQL> grant dba to mouse;
    Grant succeeded.
    SQL> !
    oracle@linux:~/mouse> exp mouse/mouse_2012 tables=test file=test.dmp feedback=100000 buffer=10000000 indexes=y triggers=y trace=y;
    Export: Release 11.2.0.1.0 - Production on Wed Dec 5 07:24:50 2012
    Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
    Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    Export done in US7ASCII character set and AL16UTF16 NCHAR character set
    server uses ZHS16GBK character set (possible charset conversion)
    About to export specified tables via Conventional Path ...
    . . exporting table TEST
    33 rows exported
    Export terminated successfully without warnings
    继续跟踪

  • EXP-00056: ORACLE error 4021 encountered ORA-04021: timeout occurred while

    hi all oracle gurus ,
    i have this problem which i am facing its like this.i have a batch file that runs export every night one week back it was all okay .few days back when i looked the log files it gives me this error ---EXP-00056: ORACLE error 4021 encountered
    ORA-04021: timeout occurred while waiting to lock object
    what should i do this is a production database runing in windows platform and there is no backup pls help me .....
    export log file -------
    Connected to: Oracle Database 10g Enterprise Edition Release 10.1.0.2.0 - Production
    With the Partitioning, OLAP and Data Mining options
    Export done in AL32UTF8 character set and AL16UTF16 NCHAR character set
    About to export specified users ...
    . exporting pre-schema procedural objects and actions
    . exporting foreign function library names for user PILOT
    . exporting foreign function library names for user FINANCE
    . exporting foreign function library names for user MBCNEWS
    . exporting PUBLIC type synonyms
    . exporting private type synonyms
    . exporting PUBLIC type synonyms
    . exporting private type synonyms
    . exporting PUBLIC type synonyms
    . exporting private type synonyms
    . exporting object type definitions for user PILOT
    . exporting object type definitions for user FINANCE
    . exporting object type definitions for user MBCNEWS
    About to export PILOT's objects ...
    . exporting database links
    . exporting sequence numbers
    . exporting cluster definitions
    EXP-00056: ORACLE error 4021 encountered
    ORA-04021: timeout occurred while waiting to lock object
    ORA-06512: at "SYS.DBMS_METADATA", line 1511
    ORA-06512: at "SYS.DBMS_METADATA", line 1548
    ORA-06512: at "SYS.DBMS_METADATA", line 1864
    ORA-06512: at "SYS.DBMS_METADATA", line 3707
    ORA-06512: at "SYS.DBMS_METADATA", line 3689
    ORA-06512: at line 1
    EXP-00000: Export terminated unsuccessfully
    robyav

    this is a production database runing in windows platform and there is no backup
    what should iWell first of all you should stop using EXP for backups, it's quite unsuitable, and start using RMAN instead. Find out more.
    If you have a Metalink account you shoudl read Note:298968.1. But teh headline is there is a bug in 10gR1 which is fixed in 10gR2. This may not help you much. The workaround is to try running the export again later, which may not be any more helpful.
    Cheers, APC

  • ORA-30012: undo tablespace 'UNDOTBS' does not exist or of wrong type

    OS Version : AIX 6.1
    DB Version : 11.2.0.1
    I am duplicating database and got below error:
    contents of Memory Script:
       Alter clone database open resetlogs;
    executing Memory Script
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00601: fatal error in recovery manager
    RMAN-03004: fatal error during execution of command
    RMAN-10041: Could not re-create polling channel context following failure.
    RMAN-10024: error setting up for rpc polling
    RMAN-10005: error opening cursor
    RMAN-10002: ORACLE error: ORA-03114: not connected to ORACLE
    RMAN-03002: failure of Duplicate Db command at 02/16/2013 17:20:02
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-06136: ORACLE error from auxiliary database: ORA-01092: ORACLE instance terminated. Disconnection forced
    ORA-30012: undo tablespace 'UNDOTBS' does not exist or of wrong type
    Process ID: 44040326
    Session ID: 65 Serial number: 3
    Error is because in target database undo tablespace is UNDOTBS_NEW and in auxiliary database undo tablespace name in init file is UNDOTBS. I followed the meatlink doc 433992.1 which suggest following steps to recover from above error:
    1) edit the parameter UNDO_MANAGEMENT to "MANUAL"
    2) start database again
    3) drop the UNDO tablespace
    4) recreate UNDO tablespace which matches to name in init file.
    5) shutdown & start DB again.
    Now, i edited init file and tried to start DB and got following error:
    oracore@cph-core-db01-s $ sqlplus /nolog
    SQL*Plus: Release 11.2.0.1.0 Production on Sat Feb 16 17:22:11 2013
    Copyright (c) 1982, 2009, Oracle.  All rights reserved.
    SQL> conn sys as sysdba
    Enter password:
    Connected to an idle instance.
    SQL> startup
    ORACLE instance started.
    Total System Global Area 4275781632 bytes
    Fixed Size                  2213632 bytes
    Variable Size             822085888 bytes
    Database Buffers         3439329280 bytes
    Redo Buffers               12152832 bytes
    Database mounted.
    ORA-01113: file 1 needs media recovery
    ORA-01110: data file 1: '/u04/oradata/CORE/CORE_DUP/system01.dbf'I don't want to run duplicate command with correct UNDO tablespace name. Any other work around for this ?

    STARTUP MOUNT
    RECOVER DATABASE USING BACKUP CONTROLFILE UNTIL CANCEL
    CANCEL
    ALTER DATABASE OPEN RESETLOGS
    Above option is not working for CORE_DUP, i am getting very strange error, while trying to recover i am getting very strange error as below:
    oracore@cph-core-db01-s $ export ORACLE_SID=CORE_DUP
    SQL*Plus: Release 11.2.0.1.0 Production on Mon Feb 18 11:17:25 2013
    Copyright (c) 1982, 2009, Oracle.  All rights reserved.
    SQL> conn sys as sysdba
    Enter password:
    Connected to an idle instance.
    SQL> startup mount
    ORACLE instance started.
    Total System Global Area 4275781632 bytes
    Fixed Size                  2213632 bytes
    Variable Size             822085888 bytes
    Database Buffers         3439329280 bytes
    Redo Buffers               12152832 bytes
    Database mounted.
    SQL> alter database open resetlogs;
    alter database open resetlogs
    ERROR at line 1:
    ORA-01139: RESETLOGS option only valid after an incomplete database recovery
    SQL> recover database using backup controlfile until cancel;
    ORA-00283: recovery session canceled due to errors
    ORA-16433: The database must be opened in read/write mode.Primary database initfile:
    event="10298 trace name context forever, level 32"
    db_block_size=8192
    db_file_multiblock_read_count=16
    open_cursors=300
    db_name=CORE
    cursor_sharing='SIMILAR'
    global_names=FALSE
    diagnostic_dest=/u01/app/oracore/diag/CORE
    #background_dump_dest=/u01/app/oracore/diag/rdbms/bdump
    #core_dump_dest=/u01/app/oracore/diag/rdbms/cdump
    #user_dump_dest=/u01/app/oracore/diag/rdbms/udump
    control_files=("/u01/oradata/CORE/control01.ctl", "/u02/oradata/CORE/control02.ctl", "/u03/oradata/CORE/control03.ctl")
    log_archive_dest_1='LOCATION=/u05/oradata/CORE/'
    log_archive_format='CORE_%s%t%r.ARC'
    job_queue_processes=10
    compatible=11.2.0.1
    processes=150
    fast_start_mttr_target=300
    filesystemio_options='SETALL'
    pga_aggregate_target=500M
    recyclebin='OFF'
    remote_login_passwordfile='EXCLUSIVE'
    session_cached_cursors=100
    sga_target=4G
    undo_management='AUTO'
    undo_tablespace='UNDOTBS_NEW'
    nls_date_format='DD-MON-RRRR'
    nls_length_semantics='CHAR'initfile for CORE_DUP
    event="10298 trace name context forever, level 32"
    db_block_size=8192
    db_file_multiblock_read_count=16
    open_cursors=300
    db_name=CORE_DUP
    cursor_sharing='SIMILAR'
    global_names=FALSE
    diagnostic_dest=/u01/app/oracore/diag/CORE/CORE_DUP
    control_files=("/u01/oradata/CORE/CORE_DUP/control01.ctl", "/u02/oradata/CORE/CORE_DUP/control02.ctl", "/u03/oradata/CORE/CORE_DUP/control03.ctl")
    log_archive_dest_1='LOCATION=/u05/oradata/CORE/CORE_DUP/'
    log_archive_format='CORE_DUP%s%t%r.ARC'
    job_queue_processes=10
    compatible=11.2.0.1
    _compression_compatibility="11.2.0"
    processes=150
    fast_start_mttr_target=300
    filesystemio_options='SETALL'
    pga_aggregate_target=500M
    recyclebin='OFF'
    remote_login_passwordfile='EXCLUSIVE'
    session_cached_cursors=100
    sga_target=4G
    undo_management='AUTO'
    undo_tablespace='UNDOTBS'
    nls_date_format='DD-MON-RRRR'
    nls_length_semantics='CHAR'
    log_file_name_convert='/CORE','/CORE/CORE_DUP'
    db_file_name_convert='/CORE','/CORE/CORE_DUP'Duplicate steps are as:
    oracore@cph-core-db01-s $ rman target sys/zzzz@core catalog rmantst10/zzzzz@catdb auxiliary /
    Recovery Manager: Release 11.2.0.1.0 - Production on Mon Feb 18 15:50:00 2013
    Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.
    connected to target database: CORE (DBID=913972022)
    connected to recovery catalog database
    connected to auxiliary database: CORE_DUP (not mounted)
    RMAN> duplicate target database to CORE_DUP;
    Starting Duplicate Db at 18-FEB-13
    allocated channel: ORA_AUX_DISK_1
    channel ORA_AUX_DISK_1: SID=96 device type=DISK
    allocated channel: ORA_AUX_DISK_2
    channel ORA_AUX_DISK_2: SID=127 device type=DISK
    contents of Memory Script:
       sql clone "create spfile from memory";
    executing Memory Script
    sql statement: create spfile from memory
    contents of Memory Script:
       shutdown clone immediate;
       startup clone nomount;
    executing Memory Script
    Oracle instance shut down
    connected to auxiliary database (not started)
    Oracle instance started
    Total System Global Area    4275781632 bytes
    Fixed Size                     2213632 bytes
    Variable Size                838863104 bytes
    Database Buffers            3422552064 bytes
    Redo Buffers                  12152832 bytes
    contents of Memory Script:
       sql clone "alter system set  db_name =
    ''CORE'' comment=
    ''Modified by RMAN duplicate'' scope=spfile";
       sql clone "alter system set  db_unique_name =
    ''CORE_DUP'' comment=
    ''Modified by RMAN duplicate'' scope=spfile";
       shutdown clone immediate;
       startup clone force nomount
       restore clone primary controlfile;
       alter clone database mount;
    executing Memory Script
    sql statement: alter system set  db_name =  ''CORE'' comment= ''Modified by RMAN duplicate'' scope=spfile
    sql statement: alter system set  db_unique_name =  ''CORE_DUP'' comment= ''Modified by RMAN duplicate'' scope=spfile
    Oracle instance shut down
    Oracle instance started
    Total System Global Area    4275781632 bytes
    Fixed Size                     2213632 bytes
    Variable Size                838863104 bytes
    Database Buffers            3422552064 bytes
    Redo Buffers                  12152832 bytes
    Starting restore at 18-FEB-13
    allocated channel: ORA_AUX_DISK_1
    channel ORA_AUX_DISK_1: SID=96 device type=DISK
    allocated channel: ORA_AUX_DISK_2
    channel ORA_AUX_DISK_2: SID=127 device type=DISK
    channel ORA_AUX_DISK_1: starting datafile backup set restore
    channel ORA_AUX_DISK_1: restoring control file
    channel ORA_AUX_DISK_1: reading from backup piece /oraclebackup/CORE/DF_L1_CORE_16022013_5fo246k3_175_1
    channel ORA_AUX_DISK_1: piece handle=/oraclebackup/CORE/DF_L1_CORE_16022013_5fo246k3_175_1 tag=LEVEL1
    channel ORA_AUX_DISK_1: restored backup piece 1
    channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:03
    output file name=/u01/oradata/CORE/CORE_DUP/control01.ctl
    output file name=/u02/oradata/CORE/CORE_DUP/control02.ctl
    output file name=/u03/oradata/CORE/CORE_DUP/control03.ctl
    Finished restore at 18-FEB-13
    database mounted
    contents of Memory Script:
       set until scn  1217601;
       set newname for datafile  1 to
    "/u04/oradata/CORE/CORE_DUP/system01.dbf";
       set newname for datafile  2 to
    "/u04/oradata/CORE/CORE_DUP/sysaux01.dbf";
       set newname for datafile  4 to
    "/u04/oradata/CORE/CORE_DUP/users01.dbf";
       set newname for datafile  5 to
    "/u04/oradata/CORE/CORE_DUP/users02.dbf";
       set newname for datafile  6 to
    "/u04/oradata/CORE/CORE_DUP/users03.dbf";
       set newname for datafile  9 to
    "/u04/oradata/CORE/CORE_DUP/undotbs_new01.dbf";
       restore
       clone database
    executing Memory Script
    executing command: SET until clause
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    Starting restore at 18-FEB-13
    using channel ORA_AUX_DISK_1
    using channel ORA_AUX_DISK_2
    channel ORA_AUX_DISK_1: starting datafile backup set restore
    channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
    channel ORA_AUX_DISK_1: restoring datafile 00004 to /u04/oradata/CORE/CORE_DUP/users01.dbf
    channel ORA_AUX_DISK_1: restoring datafile 00005 to /u04/oradata/CORE/CORE_DUP/users02.dbf
    channel ORA_AUX_DISK_1: restoring datafile 00006 to /u04/oradata/CORE/CORE_DUP/users03.dbf
    channel ORA_AUX_DISK_1: reading from backup piece /oraclebackup/CORE/DF_L0_CORE_16022013_55o246fe_165_1
    channel ORA_AUX_DISK_2: starting datafile backup set restore
    channel ORA_AUX_DISK_2: specifying datafile(s) to restore from backup set
    channel ORA_AUX_DISK_2: restoring datafile 00001 to /u04/oradata/CORE/CORE_DUP/system01.dbf
    channel ORA_AUX_DISK_2: restoring datafile 00002 to /u04/oradata/CORE/CORE_DUP/sysaux01.dbf
    channel ORA_AUX_DISK_2: restoring datafile 00009 to /u04/oradata/CORE/CORE_DUP/undotbs_new01.dbf
    channel ORA_AUX_DISK_2: reading from backup piece /oraclebackup/CORE/DF_L0_CORE_16022013_56o246fe_166_1
    channel ORA_AUX_DISK_2: piece handle=/oraclebackup/CORE/DF_L0_CORE_16022013_56o246fe_166_1 tag=LEVEL0
    channel ORA_AUX_DISK_2: restored backup piece 1
    channel ORA_AUX_DISK_2: restore complete, elapsed time: 00:01:15
    channel ORA_AUX_DISK_1: piece handle=/oraclebackup/CORE/DF_L0_CORE_16022013_55o246fe_165_1 tag=LEVEL0
    channel ORA_AUX_DISK_1: restored backup piece 1
    channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:01:35
    Finished restore at 18-FEB-13
    contents of Memory Script:
       switch clone datafile all;
    executing Memory Script
    datafile 1 switched to datafile copy
    input datafile copy RECID=24 STAMP=807724355 file name=/u04/oradata/CORE/CORE_DUP/system01.dbf
    datafile 2 switched to datafile copy
    input datafile copy RECID=25 STAMP=807724355 file name=/u04/oradata/CORE/CORE_DUP/sysaux01.dbf
    datafile 4 switched to datafile copy
    input datafile copy RECID=26 STAMP=807724356 file name=/u04/oradata/CORE/CORE_DUP/users01.dbf
    datafile 5 switched to datafile copy
    input datafile copy RECID=27 STAMP=807724356 file name=/u04/oradata/CORE/CORE_DUP/users02.dbf
    datafile 6 switched to datafile copy
    input datafile copy RECID=28 STAMP=807724356 file name=/u04/oradata/CORE/CORE_DUP/users03.dbf
    datafile 9 switched to datafile copy
    input datafile copy RECID=29 STAMP=807724356 file name=/u04/oradata/CORE/CORE_DUP/undotbs_new01.dbf
    contents of Memory Script:
       set until scn  1217601;
       recover
       clone database
        delete archivelog
    executing Memory Script
    executing command: SET until clause
    Starting recover at 18-FEB-13
    using channel ORA_AUX_DISK_1
    using channel ORA_AUX_DISK_2
    channel ORA_AUX_DISK_1: starting incremental datafile backup set restore
    channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
    destination for restore of datafile 00001: /u04/oradata/CORE/CORE_DUP/system01.dbf
    destination for restore of datafile 00002: /u04/oradata/CORE/CORE_DUP/sysaux01.dbf
    destination for restore of datafile 00009: /u04/oradata/CORE/CORE_DUP/undotbs_new01.dbf
    channel ORA_AUX_DISK_1: reading from backup piece /oraclebackup/CORE/DF_L1_CORE_16022013_5eo246k2_174_1
    channel ORA_AUX_DISK_2: starting incremental datafile backup set restore
    channel ORA_AUX_DISK_2: specifying datafile(s) to restore from backup set
    destination for restore of datafile 00004: /u04/oradata/CORE/CORE_DUP/users01.dbf
    destination for restore of datafile 00005: /u04/oradata/CORE/CORE_DUP/users02.dbf
    destination for restore of datafile 00006: /u04/oradata/CORE/CORE_DUP/users03.dbf
    channel ORA_AUX_DISK_2: reading from backup piece /oraclebackup/CORE/DF_L1_CORE_16022013_5do246k2_173_1
    channel ORA_AUX_DISK_1: piece handle=/oraclebackup/CORE/DF_L1_CORE_16022013_5eo246k2_174_1 tag=LEVEL1
    channel ORA_AUX_DISK_1: restored backup piece 1
    channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
    channel ORA_AUX_DISK_2: piece handle=/oraclebackup/CORE/DF_L1_CORE_16022013_5do246k2_173_1 tag=LEVEL1
    channel ORA_AUX_DISK_2: restored backup piece 1
    channel ORA_AUX_DISK_2: restore complete, elapsed time: 00:00:01
    starting media recovery
    archived log for thread 1 with sequence 1718 is already on disk as file /u05/oradata/CORE/CORE_17181807276264.ARC
    archived log for thread 1 with sequence 1719 is already on disk as file /u05/oradata/CORE/CORE_17191807276264.ARC
    archived log for thread 1 with sequence 1720 is already on disk as file /u05/oradata/CORE/CORE_17201807276264.ARC
    archived log for thread 1 with sequence 1721 is already on disk as file /u05/oradata/CORE/CORE_17211807276264.ARC
    archived log for thread 1 with sequence 1722 is already on disk as file /u05/oradata/CORE/CORE_17221807276264.ARC
    archived log for thread 1 with sequence 1723 is already on disk as file /u05/oradata/CORE/CORE_17231807276264.ARC
    archived log for thread 1 with sequence 1724 is already on disk as file /u05/oradata/CORE/CORE_17241807276264.ARC
    archived log for thread 1 with sequence 1725 is already on disk as file /u05/oradata/CORE/CORE_17251807276264.ARC
    archived log for thread 1 with sequence 1726 is already on disk as file /u05/oradata/CORE/CORE_17261807276264.ARC
    archived log for thread 1 with sequence 1727 is already on disk as file /u05/oradata/CORE/CORE_17271807276264.ARC
    archived log for thread 1 with sequence 1728 is already on disk as file /u05/oradata/CORE/CORE_17281807276264.ARC
    archived log for thread 1 with sequence 1729 is already on disk as file /u05/oradata/CORE/CORE_17291807276264.ARC
    archived log for thread 1 with sequence 1730 is already on disk as file /u05/oradata/CORE/CORE_17301807276264.ARC
    archived log for thread 1 with sequence 1731 is already on disk as file /u05/oradata/CORE/CORE_17311807276264.ARC
    archived log for thread 1 with sequence 1732 is already on disk as file /u05/oradata/CORE/CORE_17321807276264.ARC
    archived log for thread 1 with sequence 1733 is already on disk as file /u05/oradata/CORE/CORE_17331807276264.ARC
    archived log for thread 1 with sequence 1734 is already on disk as file /u05/oradata/CORE/CORE_17341807276264.ARC
    archived log for thread 1 with sequence 1735 is already on disk as file /u05/oradata/CORE/CORE_17351807276264.ARC
    archived log for thread 1 with sequence 1736 is already on disk as file /u05/oradata/CORE/CORE_17361807276264.ARC
    archived log for thread 1 with sequence 1737 is already on disk as file /u05/oradata/CORE/CORE_17371807276264.ARC
    archived log for thread 1 with sequence 1738 is already on disk as file /u05/oradata/CORE/CORE_17381807276264.ARC
    archived log for thread 1 with sequence 1739 is already on disk as file /u05/oradata/CORE/CORE_17391807276264.ARC
    archived log for thread 1 with sequence 1740 is already on disk as file /u05/oradata/CORE/CORE_17401807276264.ARC
    archived log for thread 1 with sequence 1741 is already on disk as file /u05/oradata/CORE/CORE_17411807276264.ARC
    archived log for thread 1 with sequence 1742 is already on disk as file /u05/oradata/CORE/CORE_17421807276264.ARC
    archived log for thread 1 with sequence 1743 is already on disk as file /u05/oradata/CORE/CORE_17431807276264.ARC
    archived log for thread 1 with sequence 1744 is already on disk as file /u05/oradata/CORE/CORE_17441807276264.ARC
    channel ORA_AUX_DISK_1: starting archived log restore to default destination
    channel ORA_AUX_DISK_1: restoring archived log
    archived log thread=1 sequence=1710
    channel ORA_AUX_DISK_1: reading from backup piece /oraclebackup/CORE/ARC_1HR_CORE_16022013_5jo24jp8_179_1
    channel ORA_AUX_DISK_2: starting archived log restore to default destination
    channel ORA_AUX_DISK_2: restoring archived log
    archived log thread=1 sequence=1711
    channel ORA_AUX_DISK_2: restoring archived log
    archived log thread=1 sequence=1712
    channel ORA_AUX_DISK_2: restoring archived log
    archived log thread=1 sequence=1713
    channel ORA_AUX_DISK_2: restoring archived log
    archived log thread=1 sequence=1714
    channel ORA_AUX_DISK_2: restoring archived log
    archived log thread=1 sequence=1715
    channel ORA_AUX_DISK_2: restoring archived log
    archived log thread=1 sequence=1716
    channel ORA_AUX_DISK_2: restoring archived log
    archived log thread=1 sequence=1717
    channel ORA_AUX_DISK_2: reading from backup piece /oraclebackup/CORE/ARC_1HR_CORE_18022013_5ko296uf_180_1
    channel ORA_AUX_DISK_1: piece handle=/oraclebackup/CORE/ARC_1HR_CORE_16022013_5jo24jp8_179_1 tag=ARC_1HR
    channel ORA_AUX_DISK_1: restored backup piece 1
    channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
    archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17101807276264.ARC thread=1 sequence=1710
    channel clone_default: deleting archived log(s)
    archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17101807276264.ARC RECID=3041 STAMP=807724360
    channel ORA_AUX_DISK_2: piece handle=/oraclebackup/CORE/ARC_1HR_CORE_18022013_5ko296uf_180_1 tag=ARC_1HR
    channel ORA_AUX_DISK_2: restored backup piece 1
    channel ORA_AUX_DISK_2: restore complete, elapsed time: 00:00:08
    archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17111807276264.ARC thread=1 sequence=1711
    channel clone_default: deleting archived log(s)
    archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17111807276264.ARC RECID=3042 STAMP=807724362
    archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17121807276264.ARC thread=1 sequence=1712
    channel clone_default: deleting archived log(s)
    archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17121807276264.ARC RECID=3043 STAMP=807724363
    archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17131807276264.ARC thread=1 sequence=1713
    channel clone_default: deleting archived log(s)
    archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17131807276264.ARC RECID=3044 STAMP=807724367
    archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17141807276264.ARC thread=1 sequence=1714
    channel clone_default: deleting archived log(s)
    archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17141807276264.ARC RECID=3048 STAMP=807724367
    archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17151807276264.ARC thread=1 sequence=1715
    channel clone_default: deleting archived log(s)
    archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17151807276264.ARC RECID=3046 STAMP=807724367
    archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17161807276264.ARC thread=1 sequence=1716
    channel clone_default: deleting archived log(s)
    archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17161807276264.ARC RECID=3045 STAMP=807724367
    archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17171807276264.ARC thread=1 sequence=1717
    channel clone_default: deleting archived log(s)
    archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17171807276264.ARC RECID=3047 STAMP=807724367
    archived log file name=/u05/oradata/CORE/CORE_17181807276264.ARC thread=1 sequence=1718
    archived log file name=/u05/oradata/CORE/CORE_17191807276264.ARC thread=1 sequence=1719
    archived log file name=/u05/oradata/CORE/CORE_17201807276264.ARC thread=1 sequence=1720
    archived log file name=/u05/oradata/CORE/CORE_17211807276264.ARC thread=1 sequence=1721
    archived log file name=/u05/oradata/CORE/CORE_17221807276264.ARC thread=1 sequence=1722
    archived log file name=/u05/oradata/CORE/CORE_17231807276264.ARC thread=1 sequence=1723
    archived log file name=/u05/oradata/CORE/CORE_17241807276264.ARC thread=1 sequence=1724
    archived log file name=/u05/oradata/CORE/CORE_17251807276264.ARC thread=1 sequence=1725
    archived log file name=/u05/oradata/CORE/CORE_17261807276264.ARC thread=1 sequence=1726
    archived log file name=/u05/oradata/CORE/CORE_17271807276264.ARC thread=1 sequence=1727
    archived log file name=/u05/oradata/CORE/CORE_17281807276264.ARC thread=1 sequence=1728
    archived log file name=/u05/oradata/CORE/CORE_17291807276264.ARC thread=1 sequence=1729
    archived log file name=/u05/oradata/CORE/CORE_17301807276264.ARC thread=1 sequence=1730
    archived log file name=/u05/oradata/CORE/CORE_17311807276264.ARC thread=1 sequence=1731
    archived log file name=/u05/oradata/CORE/CORE_17321807276264.ARC thread=1 sequence=1732
    archived log file name=/u05/oradata/CORE/CORE_17331807276264.ARC thread=1 sequence=1733
    archived log file name=/u05/oradata/CORE/CORE_17341807276264.ARC thread=1 sequence=1734
    archived log file name=/u05/oradata/CORE/CORE_17351807276264.ARC thread=1 sequence=1735
    archived log file name=/u05/oradata/CORE/CORE_17361807276264.ARC thread=1 sequence=1736
    archived log file name=/u05/oradata/CORE/CORE_17371807276264.ARC thread=1 sequence=1737
    archived log file name=/u05/oradata/CORE/CORE_17381807276264.ARC thread=1 sequence=1738
    archived log file name=/u05/oradata/CORE/CORE_17391807276264.ARC thread=1 sequence=1739
    archived log file name=/u05/oradata/CORE/CORE_17401807276264.ARC thread=1 sequence=1740
    archived log file name=/u05/oradata/CORE/CORE_17411807276264.ARC thread=1 sequence=1741
    archived log file name=/u05/oradata/CORE/CORE_17421807276264.ARC thread=1 sequence=1742
    archived log file name=/u05/oradata/CORE/CORE_17431807276264.ARC thread=1 sequence=1743
    archived log file name=/u05/oradata/CORE/CORE_17441807276264.ARC thread=1 sequence=1744
    media recovery complete, elapsed time: 00:00:33
    Finished recover at 18-FEB-13
    contents of Memory Script:
       shutdown clone immediate;
       startup clone nomount;
       sql clone "alter system set  db_name =
    ''CORE_DUP'' comment=
    ''Reset to original value by RMAN'' scope=spfile";
       sql clone "alter system reset  db_unique_name scope=spfile";
       shutdown clone immediate;
       startup clone nomount;
    executing Memory Script
    database dismounted
    Oracle instance shut down
    connected to auxiliary database (not started)
    Oracle instance started
    Total System Global Area    4275781632 bytes
    Fixed Size                     2213632 bytes
    Variable Size                838863104 bytes
    Database Buffers            3422552064 bytes
    Redo Buffers                  12152832 bytes
    sql statement: alter system set  db_name =  ''CORE_DUP'' comment= ''Reset to original value by RMAN'' scope=spfile
    sql statement: alter system reset  db_unique_name scope=spfile
    Oracle instance shut down
    connected to auxiliary database (not started)
    Oracle instance started
    Total System Global Area    4275781632 bytes
    Fixed Size                     2213632 bytes
    Variable Size                838863104 bytes
    Database Buffers            3422552064 bytes
    Redo Buffers                  12152832 bytes
    sql statement: CREATE CONTROLFILE REUSE SET DATABASE "CORE_DUP" RESETLOGS ARCHIVELOG
      MAXLOGFILES     32
      MAXLOGMEMBERS      4
      MAXDATAFILES      500
      MAXINSTANCES     1
      MAXLOGHISTORY     2298
    LOGFILE
      GROUP  1 ( '/u02/oradata/CORE/CORE_DUP/redo01a.log', '/u03/oradata/CORE/CORE_DUP/redo01b.log' ) SIZE 10 M  REUSE,
      GROUP  2 ( '/u02/oradata/CORE/CORE_DUP/redo02a.log', '/u03/oradata/CORE/CORE_DUP/redo02b.log' ) SIZE 10 M  REUSE,
      GROUP  3 ( '/u02/oradata/CORE/CORE_DUP/redo03a.log', '/u03/oradata/CORE/CORE_DUP/redo03b.log' ) SIZE 10 M  REUSE
    DATAFILE
      '/u04/oradata/CORE/CORE_DUP/system01.dbf'
    CHARACTER SET AL32UTF8
    contents of Memory Script:
       set newname for tempfile  1 to
    "/u04/oradata/CORE/CORE_DUP/temp01.dbf";
       switch clone tempfile all;
       catalog clone datafilecopy  "/u04/oradata/CORE/CORE_DUP/sysaux01.dbf",
    "/u04/oradata/CORE/CORE_DUP/users01.dbf",
    "/u04/oradata/CORE/CORE_DUP/users02.dbf",
    "/u04/oradata/CORE/CORE_DUP/users03.dbf",
    "/u04/oradata/CORE/CORE_DUP/undotbs_new01.dbf";
       switch clone datafile all;
    executing Memory Script
    executing command: SET NEWNAME
    renamed tempfile 1 to /u04/oradata/CORE/CORE_DUP/temp01.dbf in control file
    cataloged datafile copy
    datafile copy file name=/u04/oradata/CORE/CORE_DUP/sysaux01.dbf RECID=1 STAMP=807724423
    cataloged datafile copy
    datafile copy file name=/u04/oradata/CORE/CORE_DUP/users01.dbf RECID=2 STAMP=807724423
    cataloged datafile copy
    datafile copy file name=/u04/oradata/CORE/CORE_DUP/users02.dbf RECID=3 STAMP=807724423
    cataloged datafile copy
    datafile copy file name=/u04/oradata/CORE/CORE_DUP/users03.dbf RECID=4 STAMP=807724423
    cataloged datafile copy
    datafile copy file name=/u04/oradata/CORE/CORE_DUP/undotbs_new01.dbf RECID=5 STAMP=807724423
    datafile 2 switched to datafile copy
    input datafile copy RECID=1 STAMP=807724423 file name=/u04/oradata/CORE/CORE_DUP/sysaux01.dbf
    datafile 4 switched to datafile copy
    input datafile copy RECID=2 STAMP=807724423 file name=/u04/oradata/CORE/CORE_DUP/users01.dbf
    datafile 5 switched to datafile copy
    input datafile copy RECID=3 STAMP=807724423 file name=/u04/oradata/CORE/CORE_DUP/users02.dbf
    datafile 6 switched to datafile copy
    input datafile copy RECID=4 STAMP=807724423 file name=/u04/oradata/CORE/CORE_DUP/users03.dbf
    datafile 9 switched to datafile copy
    input datafile copy RECID=5 STAMP=807724423 file name=/u04/oradata/CORE/CORE_DUP/undotbs_new01.dbf
    contents of Memory Script:
       Alter clone database open resetlogs;
    executing Memory Script
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00601: fatal error in recovery manager
    RMAN-03004: fatal error during execution of command
    RMAN-10041: Could not re-create polling channel context following failure.
    RMAN-10024: error setting up for rpc polling
    RMAN-10005: error opening cursor
    RMAN-10002: ORACLE error: ORA-03114: not connected to ORACLE
    RMAN-03002: failure of Duplicate Db command at 02/18/2013 15:53:50
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-06136: ORACLE error from auxiliary database: ORA-01092: ORACLE instance terminated. Disconnection forced
    ORA-30012: undo tablespace 'UNDOTBS' does not exist or of wrong type
    Process ID: 3670170
    Session ID: 33 Serial number: 7
    oracore@cph-core-db01-s $

  • Standard Data Collection Failing with Error ORA-04054: database link  does not exist.

    Hi Gurus,
    When I am running Standard Data Collection in ASCP(APS) instance R12.1.3, its failing with error : ORA-04054: database link  does not exist.
    There is no such Database link exits which is showing in above error.
    Also the database link name in the above error is not profile values in the database.
    I think, concurrent might be fetching this database link name  from some tables related to plan.
    I am not having much knowledge about how this ASCP/APS works.
    Need your help to resolve this issue.
    Thanks,

    Hi,
    ASCP Collections looks at the dblink from instances definitions from.
    1. Responsibility: Advanced Planning Administrator
    2. Navigation: Admin > Instances
    You may review the note in support.oracle.com - Understanding DB Links Setup for APS Applications - ASCP and ATP Functionality (Doc ID 813231.1)

  • 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.

  • Getting an error -ORA-20001: FLEX-ID DOES NOT EXIST in migrating Assignment

    Hi,
    I am working on migration of persons data (Person/Assignment ) etc. in Oracle HRMS. While migration of Assignments data I am getting an error: ORA-20001: FLEX-ID DOES NOT EXIST.
    Please help me.
    Regards
    Sr
    Edited by: user10939296 on Jul 9, 2009 1:21 AM

    This error occurs as FLEX-ID for different combination for KFFs has not been generated. Therefore while migration your script is unable to fetch the Flex-id as they are not generated. You can work your way around by entering the possible combinations of KFFs for a single employee and eventually entering data for one employee manually.
    eg. if for People Group Flexfield there are two segments A and B
    A having LOV Corporate and Others
    B having LOV Executive and Non Executive
    Then you have to enter the possibilities from the frontend for one employee:
    Corporate.Executive
    Corporate.Non Executive
    Others.Executive
    Others.Non Executive
    HTH

  • I am getting this error message "ORA-01006: bind variable does not exist.

    My code works fine like this:
    DECLARE
    v_JOBTYPE varchar2(8);
    v_STATUS varchar2(8);
    v_FAILURE varchar2(8);
    v_CAUSE varchar2(8);
    v_ACTION varchar2(8);
    BEGIN
    SELECT EVT_STATUS, EVT_FAILURE, EVT_CAUSE, EVT_ACTION, EVT_JOBTYPE
    INTO v_STATUS, v_FAILURE, v_CAUSE, v_ACTION, v_JOBTYPE
    FROM R5EVENTS WHERE ROWID = :ROWID;
    IF NVL(v_STATUS, 'X') = 'C' AND NVL(v_JOBTYPE , 'X') IN ('BRKD','UNPLBRKD','FILTRA', 'LUB', 'FAC') AND (v_FAILURE IS NULL OR v_CAUSE IS NULL OR v_ACTION IS NULL) THEN
    RAISE_APPLICATION_ERROR( -20001, 'FAILURE, CAUSE AND ACTION FIELDS MUST BE POPULATED');
    END IF;
    END;
    But I want to change the code to include a record (ACT_TRADE) from another table(R5ACTIVITIES). I am getting this error message "ORA-01006: bind variable does not exist - POST-UPDATE 200Before Binding". Any help would be appreciated.
    DECLARE
    v_STATUS varchar2(8);
    v_FAILURE varchar2(8);
    v_CAUSE varchar2(8);
    v_ACTION varchar2(8);
    V_CODE varchar2(8);
    V_EVENT varchar2(8);
    V_TRADE varchar2(8);
    BEGIN
    SELECT R5EVENTS.EVT_STATUS, R5EVENTS.EVT_FAILURE, R5EVENTS.EVT_CAUSE, R5EVENTS.EVT_ACTION, R5EVENTS.EVT_CODE, R5ACTIVITIES.ACT_EVENT, R5ACTIVITIES.ACT_TRADE
    INTO v_STATUS, v_FAILURE, v_CAUSE, v_ACTION, V_CODE, V_EVENT, V_TRADE
    FROM R5EVENTS, R5ACTIVITIES WHERE V_CODE = :V_EVENT;
    IF NVL(v_STATUS, 'X') = 'C' AND NVL(v_TRADE , 'X') IN ('MTM','MTL','MTMGT', 'FTM', 'FTL', 'FTMGT', 'R5') AND (v_FAILURE IS NULL OR v_CAUSE IS NULL OR v_ACTION IS NULL) THEN
    RAISE_APPLICATION_ERROR( -20001, 'FAILURE, CAUSE AND ACTION FIELDS MUST BE POPULATED');
    END IF;
    END;

    Thank you for your responses. Your feedback was helpful. This is what I ended up doing for a solution:
    DECLARE
    v_JOBTYPE varchar2(8);
    v_STATUS varchar2(8);
    v_FAILURE varchar2(8);
    v_CAUSE varchar2(8);
    v_ACTION varchar2(8);
    v_GROUP varchar2(30);
    BEGIN
    SELECT EVT_STATUS, EVT_FAILURE, EVT_CAUSE, EVT_ACTION, EVT_JOBTYPE, USR_GROUP
    INTO v_STATUS, v_FAILURE, v_CAUSE, v_ACTION, v_JOBTYPE, v_GROUP
    FROM R5EVENTS, R5USERS WHERE R5EVENTS.ROWID = :ROWID
    AND USR_CODE = O7SESS.CUR_USER;
    IF NVL(v_STATUS, 'X') = 'C' AND NVL(V_GROUP,'X') IN ('MTM','MTL','MTMGT','FTL','FTMGTS','PLANNER','DISPATCH','PMCOOR','R5') AND (v_FAILURE IS NULL OR v_CAUSE IS NULL OR v_ACTION IS NULL) THEN
    RAISE_APPLICATION_ERROR( -20001, 'FAILURE, CAUSE AND ACTION FIELDS MUST BE POPULATED');
    END IF;
    END;

  • APP-PAY-06153: System Error : Procedure pay_us_emp_dt_tax_rules.insert_fed_tax_row - ORA-20001: &1 element does not exist or has not linked to pay at step 4

    Hi Experts,
    I'm finding the below mentioned error while I'm saving assignment with Salary Basis, Location and Payroll.
    APP-PAY-06153: System Error : Procedure pay_us_emp_dt_tax_rules.insert_fed_tax_row - ORA-20001: &1 element does not exist or has not linked to pay at step 4.
    Please note that I am able to save the record if I do not any one of Salary Basis, Location. Payroll. It is basically happening on creating default tax.
    Can anyone pleas let me know if you have facing the above error and resolved?
    Guru

    Hi Guru,
    Did you check -
    Error Saving A Salary Basis - pay_us_emp_dt_tax_rules.Insert_fed_tax_row (Doc ID 302878.1)
    Cheers,
    Vignesh

  • Getting error  ORA-20001: FLEX-ID DOES NOT EXIST

    I am trying to load new jobs.. I have run the fnd_flex_val_api.create_independent_vset_value to load the values into the segments needed.. NREL HR Job Title and NREL HR Job Descriptor and the values are in there.
    I'm getting this in the hr_job_api.create_job api. thanks, Scott
    Edited by: user12036380 on Aug 26, 2010 3:18 PM

    Hi,
    What is the application release?
    Please see if these docs help.
    Error 'ORA-20001: FLEX-ID Does Not Exist' In HR_POSITIONS_API While Loading Positions [ID 790124.1]
    HR_ASSIGNMENT_EXTRA_INFO_API.UPDATE_ASSIGNMENT_EXTRA_INFO Errors with 'ORA-20001: FLEX-ID DOES NOT EXIST' [ID 1163457.1]
    HR_IN_PERSONAL_PAY_METHOD_API Error Ora-20001 Flex-Id Does Not Exist [ID 834844.1]
    Cannot Create Employee Via API - FLEX-ID DOES NOT EXIST Error Occurs [ID 554850.1]
    Thanks,
    Hussein

Maybe you are looking for