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........................
Similar Messages
-
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 supportup
-
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 existHi;
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 -
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 PMSQL> 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. -
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 existThe 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 -
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 $ -
ORA-27473: argument 1 does not exist
Hello
I've been trying to create a file_watcher to check for files arriving at the filesystem. But keep getting the error "ORA-27473: argument 1 does not exist ". I've searched forums but can't find an answer to get me on track.
Does anyone know why I get this error?
The examples I've been following are those provided by oracle and some from the web. All very simple and run, but mine does not.
The system I'm using is a Oracle prebuilt VM 'Database App Development VM', where the OS is Oracle Linux 5 and Oracle Database 11.2 EE.
An example is this: http://awads.net/wp/2011/03/29/did-you-know-about-file-watchers/
/JacMaJust wondering whether your enter this part correctly ?
BEGIN
2 DBMS_SCHEDULER.create_program (
3 program_name => 'image_watcher_p',
4 program_type => 'stored_procedure',
5 program_action => 'process_image_files',
6 number_of_arguments => 1,
7 enabled => FALSE);
8 DBMS_SCHEDULER.define_metadata_argument (
9 program_name => 'image_watcher_p',
10 metadata_attribute => 'event_message',
11 argument_position => 1);
12 DBMS_SCHEDULER.enable ('image_watcher_p');
13 END;
14 / -
About ora-01006 :bind variable does not exist
Hi all of you,i have this dynamic sql :
DECLARE
v_query clob;
cpt number;
begin
v_query:='
SELECT
count(TBA.ANT_ID)
FROM
WHERE TBA.ANT_FUT_ID = TFT.FUT_ID
AND TBA.ANT_KATEGORIE_CODE_ID = TAKCL.ANT_KATEGORIE_CODE_ID(+)
AND TBA.ANT_KFZ_REIHEN_ID = TKR.KFZ_REIHEN_ID(+)
AND TBA.ANT_ID = F1.ANT_ANT_ID(+)
AND TBA.ANT_ID = F2.ANT_ANT_ID(+)
AND TBA.ANT_ID = F3.ANT_ANT_ID(+)
AND TBA.ANT_ID = ERS.ers_bdk(+)
AND TBA.ANT_ID = F1_2.ANT_ANT_ID(+)
AND TBA.ANT_ID = F2_3.ANT_ANT_ID(+)
AND TBA.ANT_ID = MFU.MFU_ANT_ID(+)
AND MFU.MFU_NIETGEOMETRIE_ID = NG.NG_ID(+)
AND MFU.MFU_MATRIZEN_BEICHNUNG_ID = MZB.MZB_ID(+)
-- Suchkriterien: --
--Ersteller
AND DECODE( ERS.ers_id, NULL, ''%'', ERS.ers_name ) LIKE DECODE('':1'',NULL,''%'','''')||''''|| :1 ||''''||DECODE('':1'',NULL,''%'','''')
--Fahrzeug
AND DECODE( TKR.NAME, NULL, ''%'', TKR.NAME ) LIKE DECODE('':2'',NULL,''%'','''')||''''|| :2 ||''''|| DECODE('':2'',NULL,''%'','''')
--BDK
AND DECODE( fuege_db.bdk_nummer( TBA.ANT_ID,''.'' ), NULL, ''%%'',
fuege_db.bdk_nummer( TBA.ANT_ID,''.'' ) ) LIKE ''%''||:3||''%''
--Technologie
AND TBA.ANT_FUT_ID LIKE DECODE('':4'',NULL,''%'','''')||''''|| :4 ||''''||DECODE('':4'',NULL,''%'','''')
--Art
AND ((TBA.ANT_WFP_ID is null and 1=DECODE('':5'',NULL,1,1,1) ) or (TBA.ANT_WFP_ID is not null and 2=DECODE('':5'',NULL,2,2,2)))
--VTA
AND TBA.ANT_VTA = decode('':6'',1,1,TBA.ANT_VTA) ';
execute immediate v_query
into cpt USING
'Dominik Hussmann',
'AU736_Q7_SUV' ,
'WPS Stahl',
'0';
end ;
In the execution,i have this error :ora-01006 :bind variable does not exist, after analyzing,i have found that the problem is with parameters :5 and :6 ,i don't understand they have the same syntax
as bind variables 1,2,3 and 4.
Than you for any suggestion.I hope you do realise that there are 13 bind-variables in your sql, not 6?
Variables are bound by position. You cannot use the same bind variable twice, they will be 2 distinct bind variables.
For example, you use :1 three times, so you need to provide three arguments, in this case three times the same value. -
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,
LitalThe 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 -
ORA-20001 FLEX-ID DOES NOT EXIST
Hi Experts,
Please am having this issue when running create Grade api for HCM of Oracle EBS.
When i execute this script below to existing Business Group( Vision University 1759 or Vision Corporation 202 ) data is transferred to per_grades and per_grade_definitions tables
But when i execute this same script pointing to a Business Group (TEST BG 7891) we created by ourself it gives error code ORA-20001 FLEX-ID DOES NOT EXIST
I have a strong feeling that creating our Business Group and setting up the Grade Flexfield has a problem, but i can 't trace the fault, am not EBS expert
Please can you please advice where am going wrong !!
Thanks,
Kwesi
SCRIPT BELOW:
Procedure Create_Grade
is
l_Validate Boolean := FALSE;
l_Business_Group_id Number(15,2);
l_Date_From Date;
l_Sequence Number(15,2);
l_Grade_id Number(15,2);
l_Object_Version_Number Number(15,2);
l_Grade_Definition_id Number(15,2);
l_Name Varchar2(100);
l_OVN Number(15,2) := 1;
i Number;
Begin
For Grad In (Select * from chr_Grades where OVN IN l_OVN) loop
Begin
apps.hr_grade_api.Create_Grade(
p_Validate => l_Validate,
p_Business_Group_id =>7891,
p_Date_From => to_Date(sysdate,'DD-MM-YYYY'),
p_Sequence => 11,
p_Grade_id => l_Grade_id,
p_Object_Version_Number => l_Object_Version_Number,
p_Grade_Definition_id => l_Grade_Definition_id,
p_Name => l_Name,
p_segment1 => Grad.Grade_id,
p_segment2 => Grad.Grade_Name,
p_segment3 => Grad.Grade_Description
Update chr_Grades Set OVN = 2
where Grade_id = Grad.Grade_id;
End;
End loop;
Commit;
End Create_Grade;Well, i found the solution to my problem, and is just creating the segment you want to use in your flexfield without PASSING ANY VALUESET.
-
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 commentsHi.
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 -
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; -
ORA-15001: diskgroup "FRA" does not exist or is not mounted
Dear Experts,
We noticed the error "ORA-15001: diskgroup "FRA" does not exist or is not mounted" on the 2nd node of our 4 nodes RAC database system.
During this weekend, we moved our system to a new data center. After the move was done, we were able to bring up the 4 instances around 3:00 AM. However, 4 hours later (7:00 AM), OEM Grid control alerted us with "archival error" on the 2nd instance. From our investigating, we saw the FRA was dismounted. Below is the oracle alert log file (For secuirty reson, the SID is modified):
Sat Feb 7 03:46:03 2009
Completed: ALTER DATABASE OPEN
Sat Feb 7 03:50:18 2009
Sat Feb 7 07:01:36 2009
Thread 2 advanced to log sequence 8534
Current log# 3 seq# 8534 mem# 0: +REDOGRPA/xyz/onlinelog/redo_03.log
Current log# 3 seq# 8534 mem# 1: +REDOGRPB/xyz/onlinelog/redo_03b.log
Sat Feb 7 07:01:39 2009
ARCH: Archival stopped, error occurred. Will continue retrying
Sat Feb 7 07:01:39 2009
ORACLE Instance XYZ2 - Archival Error
Sat Feb 7 07:01:39 2009
ORA-16038: log 11 sequence# 8533 cannot be archived
ORA-00254: error in archive control string ''
ORA-00312: online log 11 thread 2: '+REDOGRPA/xyz/onlinelog/redo_11.log'
ORA-00312: online log 11 thread 2: '+REDOGRPB/xyz/onlinelog/redo_11b.log'
ORA-15001: diskgroup "FRA" does not exist or is not mounted
ORA-15001: diskgroup "FRA" does not exist or is not mounted It is my understanding, that Oracle will automatically mount the diskgroups on the ASM when the instances are started. In our case, all other diskgroups are started OK but not the FRA diskgroup. Is this a bug with FRA where FRA can not be automatically started up after recycling the instance? Did anyone experience the same situation? Can someone advice?
Thanks!Hello,
We are running oracle 10.2.0.2.
Which section of the alert log file for +ASM2 we need here? I will paste it here the ones when "alter diskgroup all mounted" started at 3:00 AM all the way upto 4:00 AM on Saturday, Feb 7:
SQL> ALTER DISKGROUP ALL MOUNT
Sat Feb 7 03:44:15 2009
NOTE: cache registered group FRA' number=1 incarn=0x1e5bf0d2
NOTE: cache registered group DATAX number=2 incarn=0xbcabf0d1
NOTE: cache registered group REDO2 number=4 incarn=0x1e5bf0d3
NOTE: cache registered group REDOGRPA number=5 incarn=0xbcbbf0d4
NOTE: cache registered group REDOGRPB number=6 incarn=0xbcbbf0d5
NOTE: cache registered group TEMPX number=7 incarn=0xbcbbf0d6
NOTE: cache registered group TEMP number=8 incarn=0x1e6bf0d7
NOTE: cache registered group TIBDATA number=9 incarn=0xbcbbf0d8
NOTE: cache registered group TIBREDO number=10 incarn=0xbcbbf0d9
NOTE: cache registered group TIBTEMP number=11 incarn=0x1ebbf0da
Sat Feb 7 03:44:15 2009
ERROR: no PST quorum in group 1: required 2, found 0
Sat Feb 7 03:44:15 2009
NOTE: cache dismounting group 1/0x1E5BF0D2 (FRA')
NOTE: dbwr not being msg'd to dismount
ERROR: diskgroup FRA' was not mounted
Sat Feb 7 03:44:15 2009
NOTE: Hbeat: instance not first (grp 2)
ERROR: no PST quorum in group 4: required 2, found 0
Sat Feb 7 03:44:15 2009
NOTE: cache dismounting group 4/0x1E5BF0D3 (REDO2)
NOTE: dbwr not being msg'd to dismount
ERROR: diskgroup REDO2 was not mounted
Sat Feb 7 03:44:15 2009
NOTE: Hbeat: instance not first (grp 5)
Sat Feb 7 03:44:15 2009
NOTE: Hbeat: instance not first (grp 6)
Sat Feb 7 03:44:15 2009
NOTE: Hbeat: instance not first (grp 7)
ERROR: no PST quorum in group 8: required 2, found 0
Sat Feb 7 03:44:15 2009
NOTE: cache dismounting group 8/0x1E6BF0D7 (TEMP)
NOTE: dbwr not being msg'd to dismount
ERROR: diskgroup TEMP was not mounted
Sat Feb 7 03:44:15 2009
NOTE: Hbeat: instance not first (grp 9)
Sat Feb 7 03:44:15 2009
NOTE: Hbeat: instance not first (grp 10)
ERROR: no PST quorum in group 11: required 2, found 0
Sat Feb 7 03:44:15 2009
NOTE: cache dismounting group 11/0x1EBBF0DA (TIBTEMP)
NOTE: dbwr not being msg'd to dismount
ERROR: diskgroup TIBTEMP was not mounted
NOTE: cache opening disk 0 of grp 2: DATAX_0000 path:/dev/raw/raw61
NOTE: F1X0 found on disk 0 fcn 0.0
NOTE: cache mounting (not first) group 2/0xBCABF0D1 (DATAX)
Sat Feb 7 03:44:16 2009
kjbdomatt send to node 0
kjbdomatt send to node 2
kjbdomatt send to node 3
Sat Feb 7 03:44:16 2009
NOTE: attached to recovery domain 2
Sat Feb 7 03:44:16 2009
NOTE: opening chunk 4 at fcn 0.1158090 ABA
NOTE: seq=54 blk=4821
Sat Feb 7 03:44:16 2009
NOTE: cache mounting group 2/0xBCABF0D1 (DATAX) succeeded
SUCCESS: diskgroup DATAX was mounted
NOTE: cache opening disk 0 of grp 5: REDOGRPA_0000 path:/dev/raw/raw20
NOTE: F1X0 found on disk 0 fcn 0.0
NOTE: cache mounting (not first) group 5/0xBCBBF0D4 (REDOGRPA)
Sat Feb 7 03:44:16 2009
kjbdomatt send to node 0
kjbdomatt send to node 2
kjbdomatt send to node 3
Sat Feb 7 03:44:16 2009
NOTE: recovering COD for group 2/0xbcabf0d1 (DATAX)
SUCCESS: completed COD recovery for group 2/0xbcabf0d1 (DATAX)
Sat Feb 7 03:44:16 2009
NOTE: attached to recovery domain 5
Sat Feb 7 03:44:16 2009
NOTE: opening chunk 4 at fcn 0.103802 ABA
NOTE: seq=43 blk=2123
Sat Feb 7 03:44:16 2009
NOTE: cache mounting group 5/0xBCBBF0D4 (REDOGRPA) succeeded
SUCCESS: diskgroup REDOGRPA was mounted
NOTE: cache opening disk 0 of grp 6: REDOGRPB_0000 path:/dev/raw/raw12
NOTE: F1X0 found on disk 0 fcn 0.0
NOTE: cache mounting (not first) group 6/0xBCBBF0D5 (REDOGRPB)
Sat Feb 7 03:44:16 2009
kjbdomatt send to node 0
kjbdomatt send to node 2
kjbdomatt send to node 3
Sat Feb 7 03:44:17 2009
NOTE: attached to recovery domain 6
Sat Feb 7 03:44:17 2009
NOTE: opening chunk 4 at fcn 0.75866 ABA
NOTE: seq=20 blk=1704
Sat Feb 7 03:44:17 2009
NOTE: cache mounting group 6/0xBCBBF0D5 (REDOGRPB) succeeded
SUCCESS: diskgroup REDOGRPB was mounted
NOTE: cache opening disk 0 of grp 7: TEMPX_0000 path:/dev/raw/raw71
NOTE: F1X0 found on disk 0 fcn 0.25328
NOTE: cache opening disk 1 of grp 7: TEMPX_0001 path:/dev/raw/raw7
NOTE: cache mounting (not first) group 7/0xBCBBF0D6 (TEMPX)
Sat Feb 7 03:44:17 2009
kjbdomatt send to node 0
kjbdomatt send to node 2
kjbdomatt send to node 3
Sat Feb 7 03:44:17 2009
NOTE: attached to recovery domain 7
Sat Feb 7 03:44:17 2009
NOTE: opening chunk 4 at fcn 0.69473 ABA
NOTE: seq=42 blk=432
Sat Feb 7 03:44:17 2009
NOTE: cache mounting group 7/0xBCBBF0D6 (TEMPX) succeeded
SUCCESS: diskgroup TEMPX was mounted
NOTE: cache opening disk 0 of grp 9: TIBDATA path:/dev/raw/raw86
NOTE: F1X0 found on disk 0 fcn 0.0
NOTE: cache mounting (not first) group 9/0xBCBBF0D8 (TIBDATA)
Sat Feb 7 03:44:17 2009
kjbdomatt send to node 0
kjbdomatt send to node 2
kjbdomatt send to node 3
Sat Feb 7 03:44:17 2009
NOTE: attached to recovery domain 9
Sat Feb 7 03:44:17 2009
NOTE: opening chunk 4 at fcn 0.102912 ABA
NOTE: seq=12 blk=2050
Sat Feb 7 03:44:17 2009
NOTE: cache mounting group 9/0xBCBBF0D8 (TIBDATA) succeeded
SUCCESS: diskgroup TIBDATA was mounted
NOTE: cache opening disk 0 of grp 10: TIBREDO path:/dev/raw/raw87
NOTE: F1X0 found on disk 0 fcn 0.0
NOTE: cache mounting (not first) group 10/0xBCBBF0D9 (TIBREDO)
Sat Feb 7 03:44:18 2009
kjbdomatt send to node 0
kjbdomatt send to node 2
kjbdomatt send to node 3
Sat Feb 7 03:44:18 2009
NOTE: attached to recovery domain 10
Sat Feb 7 03:44:18 2009
NOTE: opening chunk 4 at fcn 0.18970 ABA
NOTE: seq=12 blk=6577
Sat Feb 7 03:44:18 2009
NOTE: cache mounting group 10/0xBCBBF0D9 (TIBREDO) succeeded
SUCCESS: diskgroup TIBREDO was mounted
Sat Feb 7 03:44:19 2009
NOTE: recovering COD for group 5/0xbcbbf0d4 (REDOGRPA)
SUCCESS: completed COD recovery for group 5/0xbcbbf0d4 (REDOGRPA)
NOTE: recovering COD for group 6/0xbcbbf0d5 (REDOGRPB)
SUCCESS: completed COD recovery for group 6/0xbcbbf0d5 (REDOGRPB)
NOTE: recovering COD for group 7/0xbcbbf0d6 (TEMPX)
SUCCESS: completed COD recovery for group 7/0xbcbbf0d6 (TEMPX)
NOTE: recovering COD for group 9/0xbcbbf0d8 (TIBDATA)
SUCCESS: completed COD recovery for group 9/0xbcbbf0d8 (TIBDATA)
NOTE: recovering COD for group 10/0xbcbbf0d9 (TIBREDO)
SUCCESS: completed COD recovery for group 10/0xbcbbf0d9 (TIBREDO)
Sat Feb 7 03:45:18 2009
Starting background process ASMB
ASMB started with pid=17, OS id=16122
Sat Feb 7 03:49:35 2009
NOTE: ASMB process exiting due to lack of ASM file activity
Starting background process ASMB
ASMB started with pid=18, OS id=25963
Sat Feb 7 03:54:34 2009
NOTE: ASMB process exiting due to lack of ASM file activity
Sat Feb 7 03:54:50 2009
Starting background process ASMB
ASMB started with pid=18, OS id=913
Sat Feb 7 03:57:55 2009
NOTE: ASMB process exiting due to lack of ASM file activity
Sat Feb 7 04:07:26 2009
Starting background process ASMB
ASMB started with pid=21, OS id=23012
Sat Feb 7 04:13:59 2009
NOTE: ASMB process exiting due to lack of ASM file activity
Starting background process ASMB
ASMB started with pid=22, OS id=31320
Sat Feb 7 04:36:43 2009
NOTE: ASMB process exiting due to lack of ASM file activity -
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,
TimORA-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.
Maybe you are looking for
-
How can I get the selected action of content type by javascript from Firefox Options Applications?
I works on my website, and it have to check the PDF file will be opened in which plugins So we have to implement some javascript to check the selected action of Content Type from Tool>Options>Application Do we have any javascript code to check this
-
Multiple users/computers and email
Hi folks, At home I've been using BT Broadband and an iMac for 4-5 years. Three user accounts each with own email address. Just got a new iMac and have run the standard Apple "migration" from the old to the new machine. Seems to have worked ok - most
-
Dear Experts, We have a difference in the month of Feb-2011 in tr.code KE5T for an Account XXXXX (B/s Account), upto Jan-2011 we dont find any difference CoCd Account Crcy Year Base ledger CompLedger Difference XXXX XXXXX XXX 2011 5,003,
-
How are Adobe Photoshop Lightroom and Adobe Lightrom different
Hi, I found two products as "ADOBE PHOTOSHOP LIGHTROOM" and other one says "ADOBE LIGHTROOM". Below is the snapshot as well which is getting me confused. Appreciate the help!!! Thanks, Regards, -Pinaki
-
I can't get my apps to launch