ORA-39125 importing tablespace

Oracle SE 10g
SO- Unix
I'm traying import a tablespace using EM, but y got this error, can somebody give me an advise?
Processing object type TABLE_EXPORT/TABLE/TABLE_DATA
ORA-39125: Worker unexpected fatal error in KUPW$WORKER.GET_TABLE_DATA_OBJECTS while calling DBMS_LOB.CREATETEMPORARY []
ORA-25153: Temporary Tablespace is Empty
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPW$WORKER", line 6228
----- PL/SQL Call Stack -----
object line object
handle number name
c000000116b34ee8 14916 package body SYS.KUPW$WORKER
c000000116b34ee8 6293 package body SYS.KUPW$WORKER
c000000116b34ee8 9108 package body SYS.KUPW$WORKER
c0
00000116b34ee8 3870 package body SYS.KUPW$WORKER
c000000116b34ee8 6910 package body SYS.KUPW$WORKER
c000000116b34ee8 1259 package body SYS.KUPW$WORKER
c0000001167c3828 2 anonymous block

The normal procedure would be
- one reads the error stack
- one decides the second line is the most important error message
- one looks this error up in the documentation
- (error specifc)) one fixes this error making sure the temporary tablespace actually does have a tempfile
The procedure here seems to be:
- one hits CTRL-C
- one dumps it in this forum, without doing anything
not learning to be independent.
Sybrand Bakker
Senior Oracle DBA

Similar Messages

Error ORA-39125 and ORA-04063 during export for transportable tablespace

I'm using the Oracle Enterprise Manager (browser is IE) to create a tablespace transport file. Maintenance...Transport Tablespaces uses the wizard to walk me through each step. The job gets created and submitted.
The 'Prepare' and 'Convert Datafile(s)' job steps complete successfully. The Export step fails with the following error. Can anyone shed some light on this for me?
Thank you in advance!
=======================================================
Output Log
Export: Release 10.2.0.2.0 - Production on Sunday, 03 September, 2006 19:31:34
Copyright (c) 2003, 2005, Oracle. All rights reserved.
Username:
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - Production
With the Partitioning, OLAP and Data Mining options
Starting "SYS"."GENERATETTS000024": SYS/******** AS SYSDBA dumpfile=EXPDAT_GENERATETTS000024.DMP directory=EM_TTS_DIR_OBJECT transport_tablespaces=SIEBEL job_name=GENERATETTS000024 logfile=EXPDAT.LOG
Processing object type TRANSPORTABLE_EXPORT/PLUGTS_BLK
Processing object type TRANSPORTABLE_EXPORT/TABLE
Processing object type TRANSPORTABLE_EXPORT/TABLE_STATISTICS
ORA-39125: Worker unexpected fatal error in KUPW$WORKER.UNLOAD_METADATA while calling DBMS_METADATA.FETCH_XML_CLOB [TABLE_STATISTICS]
ORA-04063: view "SYS.KU$_IOTABLE_VIEW" has errors
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 105
ORA-06512: at "SYS.KUPW$WORKER", line 6241
----- PL/SQL Call Stack -----
object line object
handle number name
2CF48130 14916 package body SYS.KUPW$WORKER
2CF48130 6300 package body SYS.KUPW$WORKER
2CF48130 2340 package body SYS.KUPW$WORKER
2CF48130 6861 package body SYS.KUPW$WORKER
2CF48130 1262 package body SYS.KUPW$WORKER
2CF0850C 2 anonymous block
Job "SYS"."GENERATETTS000024" stopped due to fatal error at 19:31:44

More information:
Using SQL Developer, I checked the view SYS.KU$_IOTABLE_VIEW referred to in the error message, and it does indeed report a problem with that view. The following code is the definition of that view. I have no idea what it's supposed to be doing, because it was part of the default installation. I certainly didn't write it. I did, however, execute the 'Test Syntax' button (on the Edit View screen), and the result was this error message:
=======================================================
The SQL syntax is valid, however the query is invalid or uses functionality that is not supported.
Unknown error(s) parsing SQL: oracle.javatools.parser.plsql.syntax.ParserException: Unexpected token
=======================================================
The SQL for the view looks like this:
REM SYS KU$_IOTABLE_VIEW
CREATE OR REPLACE FORCE VIEW "SYS"."KU$_IOTABLE_VIEW" OF "SYS"."KU$_IOTABLE_T"
WITH OBJECT IDENTIFIER (obj_num) AS
select '2','3',
t.obj#,
value(o),
-- if this is a secondary table, get base obj and ancestor obj
decode(bitand(o.flags, 16), 16,
(select value(oo) from ku$_schemaobj_view oo, secobj$ s
where o.obj_num=s.secobj#
and oo.obj_num=s.obj#),
null),
decode(bitand(o.flags, 16), 16,
(select value(oo) from ku$_schemaobj_view oo, ind$ i, secobj$ s
where o.obj_num=s.secobj#
and i.obj#=s.obj#
and oo.obj_num=i.bo#),
null),
(select value(s) from ku$_storage_view s
where i.file# = s.file_num
and i.block# = s.block_num
and i.ts# = s.ts_num),
ts.name, ts.blocksize,
i.dataobj#, t.bobj#, t.tab#, t.cols,
t.clucols, i.pctfree$, i.initrans, i.maxtrans,
mod(i.pctthres$,256), i.spare2, t.flags,
t.audit$, t.rowcnt, t.blkcnt, t.empcnt, t.avgspc, t.chncnt, t.avgrln,
t.avgspc_flb, t.flbcnt, t.analyzetime, t.samplesize, t.degree,
t.instances, t.intcols, t.kernelcols, t.property, 'N', t.trigflag,
t.spare1, t.spare2, t.spare3, t.spare4, t.spare5, t.spare6,
decode(bitand(t.trigflag, 65536), 65536,
(select e.encalg from sys.enc$ e where e.obj#=t.obj#),
null),
decode(bitand(t.trigflag, 65536), 65536,
(select e.intalg from sys.enc$ e where e.obj#=t.obj#),
null),
(select c.name from col$ c
where c.obj# = t.obj#
and c.col# = i.trunccnt and i.trunccnt != 0
and bitand(c.property,1)=0),
cast( multiset(select * from ku$_column_view c
where c.obj_num = t.obj#
order by c.col_num, c.intcol_num
) as ku$_column_list_t
(select value(nt) from ku$_nt_parent_view nt
where nt.obj_num = t.obj#),
cast( multiset(select * from ku$_constraint0_view con
where con.obj_num = t.obj#
and con.contype not in (7,11)
) as ku$_constraint0_list_t
cast( multiset(select * from ku$_constraint1_view con
where con.obj_num = t.obj#
) as ku$_constraint1_list_t
cast( multiset(select * from ku$_constraint2_view con
where con.obj_num = t.obj#
) as ku$_constraint2_list_t
cast( multiset(select * from ku$_pkref_constraint_view con
where con.obj_num = t.obj#
) as ku$_pkref_constraint_list_t
(select value(ov) from ku$_ov_table_view ov
where ov.bobj_num = t.obj#
and bitand(t.property, 128) = 128), -- IOT has overflow
(select value(etv) from ku$_exttab_view etv
where etv.obj_num = o.obj_num)
from ku$_schemaobj_view o, tab$ t, ind$ i, ts$ ts
where t.obj# = o.obj_num
and t.pctused$ = i.obj# -- For IOTs, pctused has index obj#
and bitand(t.property, 32+64+512) = 64 -- IOT but not overflow
-- or partitioned (32)
and i.ts# = ts.ts#
AND (SYS_CONTEXT('USERENV','CURRENT_USERID') IN (o.owner_num, 0) OR
EXISTS ( SELECT * FROM session_roles
WHERE role='SELECT_CATALOG_ROLE' ));
GRANT SELECT ON "SYS"."KU$_IOTABLE_VIEW" TO PUBLIC;

Import - error ORA-14519: Conflicting tablespace blocksizes

Hi all,
I have a user with only one partitioned table within tablespaces with 16k block size.
Another tables use default tablespace with 8k block size.
I've exported this user to dump file.
when I try to import this dump file, I got the following error:
ORA-14519: Conflicting tablespace blocksizes for table : Tablespace TS$DATA_LP_537 block size 16384 [subpartition specfi
cation] conflicts with previously specified/implied tablespace TBS_DATA_ADCSL7K block size 8192 [object-level default]How can I do to solve this?
I need to import with partitioned table.
Thanks!!!!
[]´s

What's Oracle version?
Are you using original exp/imp or data pump.
You can dump out the DDL of this table from dump file, and see what it looks like.
You might consider precreate all 16K tablespaces that this table use.
ORA-14519: Conflicting tablespace blocksizes for string string: Tablespace string block size string [string] conflicts with previously specified/implied tablespace string block size string [string]
Cause: An attempt has been made to create a partitioned object in a manner that would require the partitioned object to span tablespaces of more than one block size.
Action: Ensure that all tablespaces specified in the DDL command for the given object as well as any tablespaces implicitly assigned to partitions or subpartitions of the object being created are all of the same block size.

Impdp error ORA-39125: Worker unexpected fatal error in KUPW$WORKER.PUT_DDL

Hi,
I am trying to generate sql script form the dmp file.
but getting this error.
C:\Documents and Settings\satish.HTSS>impdp egift/egift@local directory=DIR1 dum
pfile=exp.dmp sqlfile=create.sql
Import: Release 10.2.0.1.0 - Production on Saturday, 24 May, 2008 0:16:07
Copyright (c) 2003, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Produc
tion
With the Partitioning, OLAP and Data Mining options
Master table "EGIFT"."SYS_SQL_FILE_FULL_01" successfully loaded/unloaded
Starting "EGIFT"."SYS_SQL_FILE_FULL_01": egift/********@local directory=DIR1 du
mpfile=exp.dmp sqlfile=create.sql
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/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/PACKAGE/PACKAGE_SPEC
Processing object type SCHEMA_EXPORT/FUNCTION/FUNCTION
Processing object type SCHEMA_EXPORT/PROCEDURE/PROCEDURE
Processing object type SCHEMA_EXPORT/PACKAGE/COMPILE_PACKAGE/PACKAGE_SPEC/ALTER_
PACKAGE_SPEC
Processing object type SCHEMA_EXPORT/FUNCTION/ALTER_FUNCTION
Processing object type SCHEMA_EXPORT/PROCEDURE/ALTER_PROCEDURE
Processing object type SCHEMA_EXPORT/VIEW/VIEW
Processing object type SCHEMA_EXPORT/PACKAGE/PACKAGE_BODY
Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/REF_CONSTRAINT
Processing object type SCHEMA_EXPORT/TABLE/TRIGGER
ORA-39125: Worker unexpected fatal error in KUPW$WORKER.PUT_DDLS while calling D
BMS_METADATA.CONVERT []
ORA-06502: PL/SQL: numeric or value error
LPX-00007: unexpected end-of-file encountered
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPW$WORKER", line 6235
----- PL/SQL Call Stack -----
object      line object
handle    number name
20B135F8     14916 package body SYS.KUPW$WORKER
20B135F8      6300 package body SYS.KUPW$WORKER
20B135F8     12279 package body SYS.KUPW$WORKER
20B135F8      3279 package body SYS.KUPW$WORKER
20B135F8      3956 package body SYS.KUPW$WORKER
20B135F8      6931 package body SYS.KUPW$WORKER
20B135F8      1262 package body SYS.KUPW$WORKER
18E96684         2 anonymous block
Job "EGIFT"."SYS_SQL_FILE_FULL_01" stopped due to fatal error at 00:16:31and this error always comes when it turns to generate sql for the triggers.
i am facing this error continuously.
thanks

Hi,
Its an unpatched db.So you must patch it first.Here is what is mentioned about this error
39125, 00000, "Worker unexpected fatal error in %s while calling %s [%s]" // *Cause: An unhandled exception was detected internally within the worker
// process for the Data Pump job while calling the specified external
// routine. This is an internal error. Additional information may be
// supplied.
// *Action: If problem persists, contact Oracle Customer Support.
So the better part is to contact Support.See if this thread can help you.Its not having much but still ,
Error ORA-39125 and ORA-04063 during export for transportable tablespace
Aman....

How to import tablespace

hi,
anyone tell me how to import tablespace as i am repeatedly getting the different error.
actually wat i did is during export i made the corresponding tablespace which i am going to export 'read only' and exported successfully.
during import i dropped the corresponding tablespace including contents and datafiles with cascade constraints
and tried to import but receiving the error
here i given what i did during import
$ imp \'sys\sys as sysdba\' transport_tablespace=y tablespaces=HEMU file=/export/home/oracle8i/exptab.dmp datafiles=/export/home/oracle8i/migdb/data/hem.dbf log
=hemulog0.log
Import: Release 8.1.7.3.0 - Production on Fri Jun 2 09:49:49 2006
(c) Copyright 2000 Oracle Corporation. All rights reserved.
Password:
Connected to: Oracle8i Enterprise Edition Release 8.1.7.3.0 - Production
JServer Release 8.1.7.3.0 - Production
Export file created by EXPORT:V08.01.07 via conventional path
About to import transportable tablespace(s) metadata...
import done in US7ASCII character set and US7ASCII NCHAR character set
. importing SYS's objects into SYS
IMP-00017: following statement failed with ORACLE error 19721:
"BEGIN sys.dbms_plugts.checkDatafile(NULL,741328370,10,5120,14,10,4194302,"
"1,398490,524480,314544,41943042,NULL,NULL,NULL); END;"
IMP-00003: ORACLE error 19721 encountered
ORA-19721: Cannot find datafile with absolute file number 10 in tablespace HEMU
ORA-06512: at "SYS.DBMS_PLUGTS", line 1577
ORA-06512: at line 1
IMP-00000: Import terminated unsuccessfully
with regards
Boo

Hi,
first check all dbf that are related with this tablespace should move to target database.
second ,may be ur hitting bug 1826474.
check metalink note 1826474.8.
Thanks
Kuljeet

Error during impdp - ORA-39125

Hi Techies ,
i m doing an import using impdp utility for a 16bit 10.2.04. Database . But the import fails with the below error
Processing object type SCHEMA_EXPORT/PRE_SCHEMA/PROCACT_SCHEMA
ORA-39125: Worker unexpected fatal error in KUPW$WORKER.PUT_DDLS while calling DBMS_METADATA.CONVERT []
ORA-06502: PL/SQL: numeric or value error
LPX-00229: input source is empty
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPW$WORKER", line 6307
As per metalink and Google , i have tried to run initmeta.sql , but even after running it i get the same error while importing ,
aq_tm_process=5 of my DB .
packages are all valid .
Please help ,
Thanks

Hi Luis ,
Please find the answers for ur queries below inline :
1) are you trying to impdp in the same server that generate the expdp file?
--> No , its on the DEV server ,
2) or did you transfer the file via ftp/scp?
--> SCP i did an scp of dump files to this server from prod server .
3) what OS?
--> Linux x86_64 x86_64 x86_64 GNU/Linux
4) have you set NLS_LANG?
---> Yes its AMERICAN
5) could you please post the entire impdp command and log output?
--> Sure
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Master table "SYS"."SYS_IMPORT_FULL_01" successfully loaded/unloaded
Starting "SYS"."SYS_IMPORT_FULL_01": userid="/******** AS SYSDBA" directory=DATAPUMPDIR dumpfile=edw.dmp logfile=edw.log
Processing object type SCHEMA_EXPORT/USER
ORA-31684: Object type USER:"APPUSER1" already exists
ORA-31684: Object type USER:"BI" already exists
ORA-31684: Object type USER:"BI_STAGING" already exists
ORA-31684: Object type USER:"DEPT_BILLING" already exists
ORA-31684: Object type USER:"LOGS" already exists
Processing object type SCHEMA_EXPORT/SYSTEM_GRANT
Processing object type SCHEMA_EXPORT/DEFAULT_ROLE
Processing object type SCHEMA_EXPORT/TABLESPACE_QUOTA
Processing object type SCHEMA_EXPORT/PRE_SCHEMA/PROCACT_SCHEMA
ORA-39125: Worker unexpected fatal error in KUPW$WORKER.PUT_DDLS while calling DBMS_METADATA.CONVERT []
ORA-06502: PL/SQL: numeric or value error
LPX-00229: input source is empty
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPW$WORKER", line 6307
----- PL/SQL Call Stack -----
object line object
handle number name
0x97c8e880 15032 package body SYS.KUPW$WORKER
0x97c8e880 6372 package body SYS.KUPW$WORKER
0x97c8e880 12391 package body SYS.KUPW$WORKER
0x97c8e880 3346 package body SYS.KUPW$WORKER
0x97c8e880 6972 package body SYS.KUPW$WORKER
0x97c8e880 1314 package body SYS.KUPW$WORKER
0x96092e50 2 anonymous block
Thanks

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 $

Oracle 10g expdp fatal error (ORA-39125 & ORA-01801)

Key phrases: ORA-39125 ... DBMS_METADATA.FETCH_XML_CLOB [TABLE_STATISTICS] ... date format is too long
Hello,
While performing a routine export (expdp) of schemas in an Oracle 10.2 instance on Linux, a fatal error (ORA-39125) was genereted. A screen capture, including the error messages follows.
Export: Release 10.2.0.1.0 - 64bit Production on Wednesday, 20 May, 2009 15:34:44
Copyright (c) 2003, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
Processing object type SCHEMA_EXPORT/TABLE/TRIGGER
Processing object type SCHEMA_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
ORA-39125: Worker unexpected fatal error in KUPW$WORKER.UNLOAD_METADATA while calling DBMS_METADATA.FETCH_XML_CLOB [TABLE_STATISTICS]
ORA-01801: date format is too long for internal buffer
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 105
ORA-06512: at "SYS.KUPW$WORKER", line 6241
----- PL/SQL Call Stack -----
object line object
handle number name
0x807d2378 14916 package body SYS.KUPW$WORKER
0x807d2378 6300 package body SYS.KUPW$WORKER
0x807d2378 2340 package body SYS.KUPW$WORKER
0x807d2378 6861 package body SYS.KUPW$WORKER
0x807d2378 1262 package body SYS.KUPW$WORKER
0x801d2490 2 anonymous block
Job "SYSTEM"."SYS_EXPORT_SCHEMA_13" stopped due to fatal error at 15:34:54
Has anyone run into this problem?
Is it related to an Oracle bug?
Are there fixes/workarounds?
Thanks in advance,
Alan

Hi,
There have been fixes to this area. I don't know if this exact error has been fixed, but getting the latest patchset would be a good place to start.
Thanks
Dean

Expdp gives error ORA-39125 ,ORA-31642 DBMS_RULE_EXP_RULES

DB version=10.2.0.4 64bit
os =linux OEL 64bit
When i execute expdp it gives the following errors and exit :
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
ORA-39125: Worker unexpected fatal error in KUPW$WORKER.GET_TABLE_DATA_OBJECTS while calling DBMS_METADATA.FETCH_XML_CLOB []
ORA-31642: the following SQL statement fails:
BEGIN "SYS"."DBMS_RULE_EXP_RULES".SCHEMA_CALLOUT(:1,0,1,'10.02.00.04.00'); END;
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 86
ORA-06512: at "SYS.DBMS_METADATA", line 907
ORA-08103: object no longer exists
what is the problem?! i searched in metalink and could not find any solution.

Pl post the complete expdp command used. Can you reproduce this issue consistently ?
OERR: ORA-8103 "object no longer exists" / Troubleshooting, Diagnostic and Solution [ID 8103.1]
HTH
Srini

EXPDP fails with ORA-39125: Worker unexpected fatal error in KUPW $

Hi Friends,
Oracle 10.2.0.4.0 on Sun OS
Im trying to do metadata_only export using EXPDP
Facing the below error
ORA-39125: Worker unexpected fatal error in KUPW $ WORKER.UNLOAD_METADATA while calling DBMS_METADATA.FETCH_XML_CLOB []
ORA-31642: The following SQL statement fails:
BEGIN "SYS". "DBMS_RULE_EXP_RULES." SCHEMA_CALLOUT (1,1,1, '10 .02.00.04.00 ') END;
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 86
ORA-06512: at "SYS.DBMS_METADATA", line 907
ORA-00942: table or view does not exist
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPW $ WORKER", line 6307
PL / SQL Call Stack
object line object
handle number name
51bf5dc20 15032 package body SYS.KUPW $ WORKER
51bf5dc20 6372 package body SYS.KUPW $ WORKER
51bf5dc20 2396 package body SYS.KUPW $ WORKER
51bf5dc20 6944 package body SYS.KUPW $ WORKER
51bf5dc20 1314 package body SYS.KUPW $ WORKER
51c7e8650 2 anonymous block
====================================
Findings:
I check the status of DBMS_RULE_EXP_RULES
OWNER OBJECT_NAME OBJECT_TYPE STATUS
SYS DBMS_RULE_EXP_RULES PACKAGE BODY VALID
SYS DBMS_RULE_EXP_RULES PACKAGE VALID
PUBLIC DBMS_RULE_EXP_RULES SYNONYM VALID
DBMS_METADATA & DBMS_SYS_ERROR packages are valid.
======================================================
Error in the alert:
The value (30) of MAXTRANS parameter ignored.
kupprdp: master process DM00 started with pid=25, OS id=6506
to execute - SYS.KUPM$MCP.MAIN('SYS_EXPORT_SCHEMA_01', 'SYS', 'KUPC$C_1_20120908075037', 'KUPC$S_1_20120908075037', 0);
kupprdp: worker process DW01 started with worker id=1, pid=26, OS id=6633
to execute - SYS.KUPW$WORKER.MAIN('SYS_EXPORT_SCHEMA_01', 'SYS');
when i check the trace file, find the below error
ORA-04063: package body "SCH.COLLECTION" has errors
But when I check the status of the package, it's valid.
Thanks for your help
KSG

Hi;
Is it full exp? Of yes please review:
DataPump Export Fails With Errors ORA-39125 ORA-31642 ORA-1422 [ID 790988.1]
Full And Schema DataPump Exports Fail With Errors ORA-39125 ORA-31642 During DBMS_SCHED_EXPORT_CALLOUTS.SCHEMA_CALLOUT [ID 1109045.1]
EXPDP FAILS WITH ORA-39125 ORA-31642 DBMS_SCHED_EXPORT_CALLOUTS [ID 445291.1]
Full Database DataPump Export (EXPDP) Fails With Errors ORA-39125 ORA-4045 ORA-1031 On XDB.XDB_PI_TRIG [ID 1102434.1]
Errors ORA-39125 ORA-1801 When Running DataPump Export (EXPDP) [ID 815683.1]
Regard
Helios

ORA-39125:Worker unexpected fatal error for different different objects...

Hi All,
I am using Oracle database 10.2.0.4 on windows 2003 server.
I want to take full bakup/schema level backup, for this I am using expdp. when I run this expdp it's getting failed with below error:=
===================================================================================
take the schema level backup: Starting "SYSTEM"."SYS_EXPORT_SCHEMA_03": system/********@TEST schemas=JISPBILCORBILLING501 directory=BACKUP_DIR dumpfile=JISPBILCORBILLING501.dmp logfile=JISPBILCORBILLING501.log
Estimate in progress using BLOCKS method...
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
ORA-39125: Worker unexpected fatal error in KUPW$WORKER.GET_TABLE_DATA_OBJECTS while calling DBMS_METADATA.FETCH_XML_CLOB []
ORA-01115: IO error reading block from file 5 (block # 3913)
ORA-01110: data file 5: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\TEST\JISPBILCORBILLING501.DBF'
ORA-27091: unable to queue I/O
ORA-27070: async read/write failed
OSD-04006: ReadFile() failure, unable to read from file
O/S-Error: (OS 38) Reached the end of the file.
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPW$WORKER", line 6307
----- PL/SQL Call Stack -----
object line object
handle number name
000007FF9ABA7AC0 15032 package body SYS.KUPW$WORKER
000007FF9ABA7AC0 6372 package body SYS.KUPW$WORKER
000007FF9ABA7AC0 9206 package body SYS.KUPW$WORKER
000007FF9ABA7AC0 1936 package body SYS.KUPW$WORKER
000007FF9ABA7AC0 6944 package body SYS.KUPW$WORKER
000007FF9ABA7AC0 1314 package body SYS.KUPW$WORKER
000007FF94192598 2 anonymous block
Job "SYSTEM"."SYS_EXPORT_SCHEMA_03" stopped due to fatal error at 11:12:50
==================================================================================================
On the same server if I take the other database full backup then also getting similar type of error:
Starting "SYSTEM"."SYS_EXPORT_FULL_11": system/********@jisp full=y directory=BACKUP_DIR dumpfile=jispratcorbilling501_full%U.dmp filesize=3G logfile=jispratcorbilling.log
ORA-39125: Worker unexpected fatal error in KUPW$WORKER.UNLOAD_METADATA while ca
lling DBMS_METADATA.FETCH_XML_CLOB [TYPE:"SYSMAN"."MGMT_CONTAINER_CRED_ARRAY"]
ORA-22813: operand value exceeds system limits
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 229
ORA-06512: at "SYS.KUPW$WORKER", line 889
----- PL/SQL Call Stack -----
object line object
handle number name
000007FFCB72CDB0 15032 package body SYS.KUPW$WORKER
000007FFCB72CDB0 6372 package body SYS.KUPW$WORKER
000007FFCB72CDB0 2396 package body SYS.KUPW$WORKER
000007FFCB72CDB0 6944 package body SYS.KUPW$WORKER
000007FFCB72CDB0 1314 package body SYS.KUPW$WORKER
000007FFCBAA7290 2 anonymous block
Job "SYSTEM"."SYS_EXPORT_FULL_11" stopped due to fatal error at 11:48:49
====================================================================================================
Can anyone suggest me what to look for this error?
Thanks...

I did
1. DMSYS account unlock as well change the password .
2. run this query and verify it VALID status.
select COMP_NAME,VERSION,STATUS from dba_registry where COMP_NAME='Oracle Data Mining';
is any thing else require?

Export / import tablespace with all objects (datas, users, roles)

Hi, i have a problem or question to the topic export / import tablespace.
On the one hand, i have a database 10g (A) and on the other hand, a database 11g (B).
On A there is a tablespace called PRO.
Furthermore 3 Users:
PRO_Main - contains the datas - Tablespace PRO
PRO_Users1 with a role PRO_UROLE - Tablespace PRO
PRO_Users2 with a role PRO_UROLE - Tablespace PRO
Now, i want to transfer the whole tablespace PRO (included users PRO_MAIN, PRO_USER1, PRO_User2 and the role PRO_UROLE) from A to B.
On B, I 've created the user PRO_Main and the tablespace PRO.
On A , i execute following statement:
expdp PRO_Main/XXX TABLESPACES=PRO DIRECTORY=backup_datapump DUMPFILE=TSpro.dmp LOGFILE=TSpro.log
On B:
impdp PRO_Main/XXX TABLESPACES=PRO DIRECTORY=backup_datapump DUMPFILE=TSpro.dmp LOGFILE=TSpro.log
Result:
The User PRO_Main was imported with all the datas.
But i 'm missing PRO_USER1, PRO_User2 and the role PRO_UROLE...
I assume, i 've used wrong parameters in my expd and / or impdp.
It would be nice, if anybody can give me a hint.
Thanks in advance.
Best Regards,
Frank

When you do a TABLESPACE mode export by specifying just the tablespaces, then all that gets exported are the tables and their dependent objects. The users, roles, and the tablespace definitions themselves don't get exported.
When you do a SCHEMA mode export by specifying the schemas, you will get the schema definitions (if the schema running the export is privied) and all of the objects that the schema owns. The schema does not own roles or tablespace definitions.
In your case, you want to move
1. schemas - which you already created 1 on your target database
2. roles
3. everything in the tablespaces owned by multiple schemas.
There is no 1 export/import command that will do this. This is how i would do this:
1 - move the schema definitions
a. you can either create these manually or
b1. expdp schemas=<your list of schemas> include=user
b2 impdp the results from b1.
2. move the roles
expdp full=y include=role ...
remember, this will include all roles. If you want to limit what gets exported, then use:
include=role:"in ('ROLE1', 'ROLE2', ETC.)
impdo the roles just exported
3. move the user information
a. If you want to move all of the schema's objects like functions, packages, etc, then you need to use a schema mode
export
expdp user/password schemas=a,b,c ...
b. If you want to move only the objects in those tablespaces, then use the tablespace export
expdp user/password tablespaces=tbs1, tbs2, ...
c. import the dumpfile generated in step 3
impdp user/password ...
Hope this helps.
Dean

ORA-10914: invalid TABLESPACE GROUP clause

hai im trying to create a database in oracle 10g
tablespace sysaux datafile 'E:\oracle\product\10.1.0\oradata\multi\ts_sysaux01.d
bf' size 10m autoextend on extent management local
ERROR at line 9:
ORA-10914: invalid TABLESPACE GROUP clause
can any one explain me ,
regards,
ashik

first i thank u mr.venkat and user526020 for replied for ,
here i enclosed my database creation for ur ref,
create database multi logfile
group 1 'E:\oracle\product\10.1.0\oradata\multi\redo01.log' size 10m,
group 2 'E:\oracle\product\10.1.0\oradata\multi\redo02.log' size 10m,
group 3 'E:\oracle\product\10.1.0\oradata\multi\redo03.log' size 10m
datafile 'E:\oracle\product\10.1.0\oradata\multi\system01.dbf' size 10m autoextend on
default tablespace users datafile 'E:\oracle\product\10.1.0\oradata\multi\ts_users01' size 10m autoextend on extent management local
default undo tablespace undotbs datafile 'E:\oracle\product\10.1.0\oradata\multi\ts_undotbs01.dbf' size 10m autoextend on
default temporary tablespace temptbs tempfile 'E:\oracle\product\10.1.0\oradata\multi\ts_temptbs01.tmp' size 10m autoextend on
tablespace sysaux datafile 'E:\oracle\product\10.1.0\oradata\multi\ts_sysaux01.dbf' size 10m autoextend on extent management local
character set al32utf8
SYS at multi>/
tablespace sysaux datafile 'E:\oracle\product\10.1.0\oradata\multi\ts_sysaux01.d
bf' size 10m autoextend on extent management local
ERROR at line 9:
ORA-10914: invalid TABLESPACE GROUP clause
here im getting error only on sysaux tablespace size then i tried to increase the size even it shows the same,
so can any one give solution.
regards,
ashik

ORA-39186: No tablespaces in the specified list exist.

HI All
I have problem with dbms_datapump
I have 11.2.0.2 in AIX when I use PLSQL
declare
lv_ts_list VARCHAR2(200) ;
lv_data_ts VARCHAR2(100) :='TD1M20120501';
lv_idx_ts VARCHAR2(100) := 'TI1M20120501';
lv_filename VARCHAR2(200) := 'TTS.PBEB_AS1.20120501.dmp';
lv_logname VARCHAR2(200) := 'TTS.PBEB_AS1.20120501.log';
pv_directory VARCHAR2(200) := 'UPA_OS_COMM_DIR';
ln_handle number;
begin
-- lv_ts_list:='('''||lv_data_ts||'''),('''||lv_idx_ts||''')';
ln_handle:=dbms_datapump.open('EXPORT','TRANSPORTABLE',NULL);
dbms_output.put_line('--->TABLESPACE'||lv_ts_list);
dbms_output.put_line('--->file :'||lv_filename);
dbms_output.put_line('--->log:'||lv_logname);
dbms_output.put_line('--->DIR:'||pv_directory);
dbms_datapump.add_file(ln_handle,lv_logname,pv_directory,filetype=>dbms_datapump.KU$_FILE_TYPE_LOG_FILE);
dbms_datapump.add_file(ln_handle,lv_filename,pv_directory,filetype=>dbms_datapump.KU$_FILE_TYPE_DUMP_FILE);
dbms_datapump.metadata_filter(ln_handle,'TABLESPACE_LIST',lv_ts_list);
dbms_datapump.start_job(ln_handle);
end;
in our test environment is all ok but in test env our PLSQL failed
Starting "SVC"."SYS_EXPORT_TRANSPORTABLE_15":
ORA-39123: Data Pump transportable tablespace job aborted
ORA-39186: No tablespaces in the specified list exist.
Job "SVC"."SYS_EXPORT_TRANSPORTABLE_15" stopped due to fatal error at 10:52:26
when I replace
dbms_datapump.metadata_filter(ln_handle,'TABLESPACE_LIST',lv_ts_list); with list of tablespace dbms_datapump.metadata_filter(ln_handle,'TABLESPACE_LIST','''TD1M20120501'',''TI1M20120501'''); all work ok
Do You have any idea ?
thank You Brano

Hi
Pelase review:
DataPump Export TRANSPORT_TABLESPACES Fails With Error UDE-19 [ID 791221.1]
Regard
Helios

Oci_execute() [function.oci-execute]:ORA-25153:Temporary Tablespace isEmpty

hi all,
One of the user told us that they are facing problem while developing membership online fee payment, when theay are trying to access member table in oracle server. It works fine for single or fewer records,but when we try to fetch all records for the purpose of membership/date of birth site it generates some oracle error:
Warning: oci_execute() [function.oci-execute]: ORA-25153: Temporary Tablespace is Empty in /usr/local/apache/htdocs/memberdbupdateoracle.php on line 41
Warning: oci_fetch_array() [function.oci-fetch-array]: ORA-24374: define not done before fetch or execute and fetch in /usr/local/apache/htdocs/memberdbupdateoracle.php on line 49Db version is oracle 9.2.0.6
pls suggest me...

My suggestion is you look up the error message in the online docs, and add the tempfile to the temporary tablespace as indicated.
My suggestion is also you read the Forums Etiquette post, and stop bothering this forum with questions for which you can find the answer yourself without effort.
This forum is not about having someone else do your work for free.
Sybrand Bakker
Senior Oracle DBA

ORA-39125 importing tablespace

Similar Messages

Maybe you are looking for