Expdp datapump Problem

Greetings Oracle comunity, i have a a problem with an export of a full metadata database, here is the log:
Processing object type DATABASE_EXPORT/SYSTEM_PROCOBJACT/PRE_SYSTEM_ACTIONS/PROCACT_SYSTEM
ORA-39127: unexpected error from call to export_string := SYS.DBMS_SCHED_JOB_EXPORT.create_exp(94477,'1
0.02.00.04.00',newblock)
ORA-01882: timezone region not found
ORA-06512: at "SYS.DBMS_SCHED_MAIN_EXPORT", line 268
ORA-06512: at "SYS.DBMS_SCHED_JOB_EXPORT", line 14
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_METADATA", line 5038
ORA-39127: unexpected error from call to export_string := SYS.DBMS_SCHED_JOB_EXPORT.create_exp(94478,'1
0.02.00.04.00',newblock)
ORA-01882: timezone region not found
ORA-06512: at "SYS.DBMS_SCHED_MAIN_EXPORT", line 268
ORA-06512: at "SYS.DBMS_SCHED_JOB_EXPORT", line 14
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_METADATA", line 5038
ORA-39127: unexpected error from call to export_string := SYS.DBMS_SCHED_JOB_EXPORT.create_exp(94479,'1
0.02.00.04.00',newblock)
ORA-01882: timezone region not found
ORA-06512: at "SYS.DBMS_SCHED_MAIN_EXPORT", line 268
ORA-06512: at "SYS.DBMS_SCHED_JOB_EXPORT", line 14
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_METADATA", line 5038
ORA-39127: unexpected error from call to export_string := SYS.DBMS_SCHED_JOB_EXPORT.create_exp(94480,'1
0.02.00.04.00',newblock)
ORA-01882: timezone region not found
ORA-06512: at "SYS.DBMS_SCHED_MAIN_EXPORT", line 268
ORA-06512: at "SYS.DBMS_SCHED_JOB_EXPORT", line 14
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_METADATA", line 5038
ORA-39127: unexpected error from call to export_string := SYS.DBMS_SCHED_JOB_EXPORT.create_exp(104143,'
10.02.00.04.00',newblock)
ORA-01882: timezone region not found
ORA-06512: at "SYS.DBMS_SCHED_MAIN_EXPORT", line 268
ORA-06512: at "SYS.DBMS_SCHED_JOB_EXPORT", line 14
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_METADATA", line 5038
ORA-39127: unexpected error from call to export_string := SYS.DBMS_SCHED_JOB_EXPORT.create_exp(123017,'
10.02.00.04.00',newblock)
ORA-01882: timezone region not found
ORA-06512: at "SYS.DBMS_SCHED_MAIN_EXPORT", line 268
ORA-06512: at "SYS.DBMS_SCHED_JOB_EXPORT", line 14
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_METADATA", line 5038
Processing object type DATABASE_EXPORT/SYSTEM_PROCOBJACT/PROCOBJ
Processing object type DATABASE_EXPORT/SYSTEM_PROCOBJACT/POST_SYSTEM_ACTIONS/PROCACT_SYSTEM
Processing object type DATABASE_EXPORT/SCHEMA/PROCACT_SCHEMA
ORA-39127: unexpected error from call to export_string := SYS.DBMS_SCHED_JOB_EXPORT.create_exp(94477,'1
0.02.00.04.00',newblock)
ORA-01882: timezone region not found
ORA-06512: at "SYS.DBMS_SCHED_MAIN_EXPORT", line 268
ORA-06512: at "SYS.DBMS_SCHED_JOB_EXPORT", line 14
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_METADATA", line 5038
ORA-39127: unexpected error from call to export_string := SYS.DBMS_SCHED_JOB_EXPORT.create_exp(94478,'1
0.02.00.04.00',newblock)
ORA-01882: timezone region not found
ORA-06512: at "SYS.DBMS_SCHED_MAIN_EXPORT", line 268
ORA-06512: at "SYS.DBMS_SCHED_JOB_EXPORT", line 14
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_METADATA", line 5038
ORA-39127: unexpected error from call to export_string := SYS.DBMS_SCHED_JOB_EXPORT.create_exp(94479,'1
0.02.00.04.00',newblock)
ORA-01882: timezone region not found
ORA-06512: at "SYS.DBMS_SCHED_MAIN_EXPORT", line 268
ORA-06512: at "SYS.DBMS_SCHED_JOB_EXPORT", line 14
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_METADATA", line 5038
ORA-39127: unexpected error from call to export_string := SYS.DBMS_SCHED_JOB_EXPORT.create_exp(94480,'1
0.02.00.04.00',newblock)
ORA-01882: timezone region not found
ORA-06512: at "SYS.DBMS_SCHED_MAIN_EXPORT", line 268
ORA-06512: at "SYS.DBMS_SCHED_JOB_EXPORT", line 14
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_METADATA", line 5038
ORA-39127: unexpected error from call to export_string := SYS.DBMS_SCHED_JOB_EXPORT.create_exp(104143,'
10.02.00.04.00',newblock)
ORA-01882: timezone region not found
ORA-06512: at "SYS.DBMS_SCHED_MAIN_EXPORT", line 268
ORA-06512: at "SYS.DBMS_SCHED_JOB_EXPORT", line 14
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_METADATA", line 5038
ORA-39127: unexpected error from call to export_string := SYS.DBMS_SCHED_JOB_EXPORT.create_exp(123017,'
10.02.00.04.00',newblock)
ORA-01882: timezone region not found
ORA-06512: at "SYS.DBMS_SCHED_MAIN_EXPORT", line 268
ORA-06512: at "SYS.DBMS_SCHED_JOB_EXPORT", line 14
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_METADATA", line 5038
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/TABLE
how you can see, the sequence of error is:
ORA-06512: at "SYS.DBMS_METADATA", line 5038
ORA-39127: unexpected error from call to export_string := SYS.DBMS_SCHED_JOB_EXPORT.create_exp(104143,'
10.02.00.04.00',newblock)
ORA-01882: timezone region not found
ORA-06512: at "SYS.DBMS_SCHED_MAIN_EXPORT", line 268
ORA-06512: at "SYS.DBMS_SCHED_JOB_EXPORT", line 14
ORA-06512: at line 1
I hope can you can help you, good bye friends!
PD: The database was upgraded from 10.2.0.2 to 10.2.0.4

Hi,do you have account on metalink?
https://support.oracle.com/CSP/ui/flash.html#tab=KBHome(page=KBHome&id=()),(page=KBNavigator&id=(bmDocID=5865329&from=BOOKMARK&bmDocTitle=ORA-01882%20IS%20ENCOUNTERED%20AFTER%20APPLYING%20DST%20PATCH%204689959&viewingMode=1143&bmDocDsrc=BUG&bmDocType=BUG))
https://support.oracle.com/CSP/ui/flash.html#tab=KBHome(page=KBHome&id=()),(page=KBNavigator&id=(bmDocID=556318.1&from=BOOKMARK&bmDocTitle=EXP-8%20ORA-1882%20When%20Running%20Full%20Export&viewingMode=1143&bmDocDsrc=KB&bmDocType=PROBLEM))

Similar Messages

Check the status expdp datapump job

All,
I have started expdp (datapump) on size of 250GB schema.I want to know when the job will be completed.
I tried to find from views dba_datapump_sessions and v$session_longops,v$session.But but all in vain.
Is it possible to find completion time of expdp job?
Your help is really appreciated.

Hi,
Have you started the Job in "Interactie mode".. ??
If yes then you can get the status of Exectuion with "STATUS"- defauly is zero (If you setting to not null value then based on that it will show the status - seconds)
Second, thing check "dba_datapump_jobs"
- Pavan Kumar N

Expdp(datapump) or exp(orignal export).

Hi
i do not have xmltype in my tables or views but in stored proc i do have for processing xml.
so should i use expdp(datapump) or exp(orignal export).
yours sincerely
Edited by: 944768 on Apr 1, 2013 4:53 AM

xml ... ?That one I have no idea. Try it and see. Test and verity your result. Know what to expect, and don't be surprised if you ... find something you were not expecting.
connected to a schemaOne does not connect to a schema, connections are opened to a database instance. A schema is a collection of database objects.
entry form but no body is using it ...That is an entirely different subject, try a google with the search terms rdbms acid test.
In oracle, the only session (connection) that can "see" updates is the updating session. No other session may sees those changes until the transaction is committed to the database. Until the commit, all other connections see the "before" value.
Queries that begin before other transactions commit see the before values, oracle keeps the old value in undo. So an export will "see" the values committed as of the time the export begins.

Why is the destination folder for expdp Datapump NOT recognized ?

I entered the following command:
expdp "D:\mydata" TABLES=CTEST DUMPFILE=tabledata.txt
Curiously the resulting dumpfile is created in the directory
...\Oracle\app\oracle\admin\dpdump rather than
in D:\mydata as intended.
How can specify the target directory for the dump file otherwise?

If you look in dba_directories view, you will see a default directory into which datapump will place/read dump files. You will find something like DATA_PUMP_DIR which points to the default location. Read and write are granted to imp_full_database and exp_full_database roles.
You can change this with the CREATE OR REPLACE DIRECTORY data_pump_dir AS <fully qualified location in single quotes >; command,
Or you can create a new directory with the same command and your own directory name. You will have to GRANT read, write ON DIRECTORY <mydir> TO ...
Now, you can use the DIRECTORY argument in the impdp and expdp

TDE (Encryption) and expdp (Datapump)

Hi,
I'm testing TDE's features on an Oracle 10g R2 database. I edit the sqlnet.ora then I created a wallet on database 1 (DEV1), a table, did inserts, pumped (expdp) data and tried re-import it in another database (DEV2) which I use with DataGuard for failover, but something went wrong. So I try re-create my wallet on the first database (DEV1) by alter system set wallet close and delete it from my hard drive and drop table purge. I went trought the whole process of creating the wallet and table but when I tried expdp I got the ORA-28362 master key not found.
How could I not be able to export my data ? What can I do to do a clean deletion of the wallet and recreate it ?
Thanks for you help
Francis

Thank you,
but I already read those pages and understand them. But as I said, even though I delete and recreate the wallet, I can't get datapump to extract data with the ENCRYPTION_PASSWORD parameter. If I don't put this parameter everything is ok! but the data is not encrypted.

Import Datapump problems on Oracle 11g

am trying to Import (using Datapump) and DMP file from Oracle 10g (10.2.0.4).
The 10g database server has nls_characterset of:
SYSTEM@testers>
PARAMETER VALUE
NLS_CHARACTERSET WE8MSWIN1252
1 row selected.
The 11g server has:
SQL> select * from v$nls_parameters
2 where parameter = upper('nls_characterset');
PARAMETER
VALUE
NLS_CHARACTERSET
AL32UTF8
Here are the errors:
Import: Release 11.2.0.2.0 - Production on Tue Nov 8 16:40:11 2011
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
Connected to: Oracle Database 11g Release 11.2.0.2.0 - 64bit Production
Master table "SYSTEM"."SYS_IMPORT_FULL_01" successfully loaded/unloaded
Starting "SYSTEM"."SYS_IMPORT_FULL_01": system/********@Testers11g DIRECTORY=impdp_dir DUMPFILE=expdpT1400.dmp REMAP_SCHEMA=t1400:t1500 LOGFILE=expdpt1500.log
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/TABLE_DATA
. . imported "T1500"."DPR_OPENING_BALANCE" 172.2 MB 4537640 rows
. . imported "T1500"."IVC_OFFSITE_OPENING_BALANCE" 199.0 MB 5120520 rows
. . imported "T1500"."IVC_OPENING_BALANCE" 187.3 MB 5171512 rows
. . imported "T1500"."FIN_AR_STATEMENT_SAVE" 33.73 MB 93 rows
. . imported "T1500"."AUDIT_CONTRACT" 17.74 MB 39855 rows
. . imported "T1500"."S1_CONTRACT_FORMAT_TEMP" 6.078 KB 2 rows
. . imported "T1500"."FO_OPENING_BALANCE" 12.42 MB 406974 rows
. . imported "T1500"."S1_TICKET_CHARGE_SAVE" 11.62 MB 24 rows
. . imported "T1500"."FO_TRANSACTION_SUMMARY" 11.76 MB 406974 rows
. . imported "T1500"."FIN_GL_ACCOUNT_BALANCE" 10.89 MB 337260 rows
. . imported "T1500"."FIN_GL_AUDIT_TRAIL_JOURNAL" 25.48 KB 30 rows
. . imported "T1500"."FIN_GL_AUDIT_TRAIL" 1.024 MB 6648 rows
. . imported "T1500"."DPR_TRANSACTION_DETAIL" 5.888 MB 74588 rows
ORA-02374: conversion error loading table "T1500"."AUDIT_RELEASE"
ORA-12899: value too large for column SHIP_TO_SHORT_NAME (actual: 11, maximum: 10)
ORA-02372: data for row: SHIP_TO_SHORT_NAME : 0X'C8746F696C65204C656D'
I also tried to Import a DMP (from Export) from Oracle10g server and got this result:
Connected to: Oracle Database 11g Release 11.2.0.2.0 - 64bit Production
Export file created by EXPORT:V10.02.01 via conventional path
import done in WE8MSWIN1252 character set and AL16UTF16 NCHAR character set
import server uses AL32UTF8 character set (possible charset conversion)
export client uses US7ASCII character set (possible charset conversion)
. importing T1400's objects into T1500
. . importing table "A1_ASYNCH_COMMUNICATION" 0 rows imported
. . importing table "A1_BROADCAST_LOCK" 1 rows imported
. . importing table "A1_BROADCAST_MESSAGE" 6 rows imported
. . importing table "A1_BROADCAST_USER" 0 rows imported
. . importing table "A1_BUILD_SCRIPT" 437 rows imported
. . importing table "A1_DBC_APPLIED_SCRIPT" 0 rows imported
. . importing table "A1_ERROR_HANDLER" 5880 rows imported
. . importing table "A1_ERROR_HANDLER_COMMON" 2956 rows imported
. . importing table "A1_ERROR_HANDLER_TITLE"
IMP-00019: row rejected due to ORACLE error 12899
IMP-00003: ORACLE error 12899 encountered
ORA-12899: value too large for column "T1500"."A1_ERROR_HANDLER_TITLE"."TITLE_DESCRIPTION" (actual: 34, maximum: 32)
Column 1 7
Column 2 FR
Column 3 Relâche des Fact. Récurr des CAP
IMP-00019: row rejected due to ORACLE error 12899
IMP-00003: ORACLE error 12899 encountered
The errors always occur when I try to import a column containing French accented characters.
What am I missing???

Multiple posts on the same topic is considered to be rude and bordering on spam - https://forums.oracle.com/forums/thread.jspa?threadID=2308355

DATAPUMP PROBLEM

Hi,
I am running datapump:
C:\>impdp system/manager directory=dp_dir dumpfile=CISADM_EXPDP_042011.dmp sqlfile=a.sql
Import: Release 11.2.0.1.0 - Production on Mon May 9 10:53:45 2011
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
UDI-00018: Data Pump client is incompatible with database version 11.01.00.07.00How can I resovel this please.
I do not want to install all types of databases version just to check if my dump is readable or corrupted. :(
Thanks

its still the same error :(
C:\>impdp system/manager directory=dp_dir dumpfile=CISADM_EXPDP_042011.dmp sqlfile=a.sql version=compatible
Import: Release 11.1.0.7.0 - Production on Monday, 09 May, 2011 11:49:57
Copyright (c) 2003, 2007, Oracle. All rights reserved.
Connected to: Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Produc
tion
With the Partitioning, OLAP, Data Mining and Real Application Testing options
ORA-39001: invalid argument value
ORA-39000: bad dump file specification
ORA-39142: incompatible version number 3.1 in dump file "d:\dump\CISADM_
EXPDP_042011.dmp"

DataPump Problem. Automaticaly change dump file name.

Deal All
I have create a plsql block and which will backup the database using datapump.
He is working fine in scheduler but he generates error because it doesnot change
file name every time. Against the following he always generates
'EXPORT%U.DMP' = EXPORT01.DMP file name.
Please tell me how i can change every file name automatically.
Thanks
Abid

Hi,
I have 10.2.0.4 db on windows and want to have a full datapump export every night and want a unique file name but this does not work for me. The script just does not execute. I have even tried this from the command line
par file is
DUMPFILE='expdp_testdb_full.'||to_char(sysdate,'YYYYMMDDHH24MISS')||'.dmp'
JOB_NAME=expdp_testdb_full
LOGFILE="expdp_full_testdb.log"
DIRECTORY=DATAPUMP_DIR
FULL=Y
ESTIMATE=STATISTICS
CONTENT=ALL
PARALLEL=20

Expdp (Datapump) question

Hi,
I am using the following expdp command to create database export for one of my schemas. The issue is when I run it manually on command window, it creates 2 files 'EXPORT01.dmp' and 'EXPORT02.dmp' which is exactly what I want. However, when I run the same command from the batch file it creates only one file: EXPORTU.dmp and runs out of space as I have limited the space to only 3m. Why does the same script not run in the batch and creates 2 files (export01.dmp and export02.dmp)?
Here's my command:
expdp system/password SCHEMAS=myschema LOGFILE=EXPDP_LOG_DIR:EXPORT.log DUMPFILE=EXPDP_DATA_DIR:EXPORT%U.dmp FILESIZE=3m
Please help.
Thank you.

Because when You run it from script it can't correctly parse "%" character. You need to solve it, try
DUMPFILE=EXPDP_DATA_DIR:EXPORT\%U.dmp FILESIZE=3m
backslash before % on most os it must work

Import problem on Vista with datapump

Hi
I've got a problem with an import into an Oracle XE database server on Vista, I keep getting Ora error "39070 Can't create log file" when executing an impdp command, whereas exactly the same command is working perfectly on Windows XP.
Here is what I'm doing: I want to create a new DB on a target laptop that runs under Vista. I have Oracle XE installed on both my source laptop where I have the source DB and on the target laptop running Vista. I export the DB on the source laptop with expdp (no problems), then copy the export dir content over to the target laptop, then create the user and all the necessary stuff on the traget laptop XE DB server (account unlock, grant create, then create dir (where the DB dump is) and grant read write on that dir to the new user), then use an impdp command like this:
impdp <user>/<password> directory=<newdb> dumpfile=newdb_schema.dmp logfile=newdb_imp.log
to import the data in the DB on the target laptop.
This fails miserably, whereas it succeeds without problems if I do exactly the same on a Win XP desktop machine set up exactly the same way !
On top of that, I succeeded 6 months ago to do the same thing on that Vista laptop, but now it refuses to work.
What's going on ? Are there known problems with the datapump on Vista, or is it a protection problem, i.e. no rights for the datapump process to write a log file in the dir where the db dump is ? What's the way to get it working ?
Thanks for your help, I'm really stuck with that one.
Regards
Balex

Which privileges has Vista user?
On Vista you must explicitly to give user ADMIN rights....
HTH

Datapump expdp dump file missing permissions

I need help on this :
After export my dump file missing the permissions for others.
-rw-r----- abc.dmp
AFter export it needs to provide read permissions to all but not working.i need like below
-rw-r--r-- abc.dump
I am using following commands before expdp (datapump)
setfacl -m mask:rwx,u:${ORACLE_OWNER}:rwx ${HOME}/dumpfiles
setfacl -m other:rwx ${HOME}/dumpfiles
Thanks in Advance,

If UMASK is set to 022 you could not generate this:
-rw-r----- abc.dmp which corresponds to a umask of 137.
I would look again. What are the user and group permissions under which it was created?

SQL*Net and Datapump export disconnects with ORA-03113 error

Hi,
I have some trouble with an Oracle 11.2.0.1.0 server installation on a Windows 2008 R2 server.
If I am connected with SQL*Plus on the database server to an instance it randomly disconnects me, but no longer than after 30-60 seconds even though I am active running simple select queries.
I can connect again without any error and soon it disconnects me again.
If I am running an expdp, datapump export it starts but displays error UDE-03113 and then ORA-03113. The datapump export continues in the background and finish successfully though.
When having a look at the Alert.log for the database instance I see this error everytime it happens:
Fatal NI connect error 12547, connecting to:
(LOCAL=NO)
VERSION INFORMATION:
     TNS for 64-bit Windows: Version 11.2.0.1.0 - Production
     Oracle Bequeath NT Protocol Adapter for 64-bit Windows: Version 11.2.0.1.0 - Production
     Windows NT TCP/IP NT Protocol Adapter for 64-bit Windows: Version 11.2.0.1.0 - Production
Time: 22-JUL-2012 21:10:40
Tracing not turned on.
Tns error struct:
ns main err code: 12547
TNS-12547: TNS:lost contact
ns secondary err code: 12560
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
opiodr aborting process unknown ospid (19800) as a result of ORA-609
Mon Jul 23 02:00:00 2012
I don't believe it is an network problem as each command I am running is on the server console. No other errors in the OS event log so I need some help where to start...
Thanks in advance!
Best Regards
Martin Gabrielsson

Thanks, no windows firewall turned on, I turned on SQL*Net tracing and this is the last part of the trc file after doing a simple select query on a table with 3 rows. After the select query has been runned I am disconnected... Any idea, help is really appreciated!
+2012-07-30 18:15:28.658650 : nsbasic_brc:packet dump+
+2012-07-30 18:15:28.658660 : nsbasic_brc:01 74 00 00 06 00 00 00 |.t......|+
+2012-07-30 18:15:28.658668 : nsbasic_brc:00 00 06 01 1A 00 26 00 |......&.|+
+2012-07-30 18:15:28.658676 : nsbasic_brc:00 00 00 00 0F 00 00 00 |........|+
+2012-07-30 18:15:28.658684 : nsbasic_brc:00 00 00 00 00 00 00 00 |........|+
+2012-07-30 18:15:28.658693 : nsbasic_brc:00 00 00 00 00 00 00 00 |........|+
+2012-07-30 18:15:28.658701 : nsbasic_brc:00 00 00 00 00 00 00 00 |........|+
+2012-07-30 18:15:28.658708 : nsbasic_brc:00 00 00 00 00 00 00 00 |........|+
+2012-07-30 18:15:28.658717 : nsbasic_brc:00 00 00 00 07 96 2C 00 |......,.|+
+2012-07-30 18:15:28.658725 : nsbasic_brc:25 06 4D 52 20 20 20 20 |%.MR....|+
+2012-07-30 18:15:28.658734 : nsbasic_brc:03 C2 1A 5F 04 C3 02 10 |..._....|+
+2012-07-30 18:15:28.658742 : nsbasic_brc:43 06 43 4C 4F 53 45 44 |C.CLOSED|+
+2012-07-30 18:15:28.658750 : nsbasic_brc:FF FF FF FF FF FF FF FF |........|+
+2012-07-30 18:15:28.658758 : nsbasic_brc:FF FF 06 4C 50 49 4D 20 |...LPIM.|+
+2012-07-30 18:15:28.658767 : nsbasic_brc:20 FF FF FF FF FF FF FF |........|+
+2012-07-30 18:15:28.658775 : nsbasic_brc:FF FF FF FF FF 0A 4D 41 |......MA|+
+2012-07-30 18:15:28.658783 : nsbasic_brc:52 47 41 42 20 20 20 20 |RGAB....|+
+2012-07-30 18:15:28.658791 : nsbasic_brc:FF 3C 77 68 65 65 6C 20 |.<wheel.|+
+2012-07-30 18:15:28.658799 : nsbasic_brc:73 68 6F 70 20 20 20 20 |shop....|+
+2012-07-30 18:15:28.658807 : nsbasic_brc:20 20 20 20 20 20 20 20 |........|+
+2012-07-30 18:15:28.658815 : nsbasic_brc:20 20 20 20 20 20 20 20 |........|+
+2012-07-30 18:15:28.658824 : nsbasic_brc:20 20 20 20 20 20 20 20 |........|+
+2012-07-30 18:15:28.658832 : nsbasic_brc:20 20 20 20 20 20 20 20 |........|+
+2012-07-30 18:15:28.658840 : nsbasic_brc:20 20 20 20 20 20 20 20 |........|+
+2012-07-30 18:15:28.658848 : nsbasic_brc:20 20 20 20 20 20 02 C1 |........|+
+2012-07-30 18:15:28.658856 : nsbasic_brc:05 07 78 66 05 03 10 09 |..xf....|+
+2012-07-30 18:15:28.658864 : nsbasic_brc:38 02 C1 02 FF 03 C2 08 |8.......|+
+2012-07-30 18:15:28.658872 : nsbasic_brc:42 FF 01 58 04 01 00 00 |B..X....|+
+2012-07-30 18:15:28.658880 : nsbasic_brc:00 14 00 01 02 00 00 00 |........|+
+2012-07-30 18:15:28.658888 : nsbasic_brc:7B 05 00 00 00 00 02 00 |{.......|+
+2012-07-30 18:15:28.658897 : nsbasic_brc:00 00 03 00 20 00 00 00 |........|+
+2012-07-30 18:15:28.658905 : nsbasic_brc:00 00 00 00 00 00 00 00 |........|+
+2012-07-30 18:15:28.658912 : nsbasic_brc:00 00 00 00 00 00 00 00 |........|+
+2012-07-30 18:15:28.658921 : nsbasic_brc:00 00 00 00 00 16 00 00 |........|+
+2012-07-30 18:15:28.658929 : nsbasic_brc:01 00 00 00 36 01 00 00 |....6...|+
+2012-07-30 18:15:28.658937 : nsbasic_brc:00 00 00 00 00 00 00 00 |........|+
+2012-07-30 18:15:28.658945 : nsbasic_brc:00 00 00 00 E0 53 D1 22 |.....S."|+
+2012-07-30 18:15:28.658953 : nsbasic_brc:00 00 00 00 00 00 00 00 |........|+
+2012-07-30 18:15:28.658961 : nsbasic_brc:00 00 00 00 00 00 00 00 |........|+
+2012-07-30 18:15:28.658969 : nsbasic_brc:00 00 00 00 00 00 00 00 |........|+
+2012-07-30 18:15:28.658977 : nsbasic_brc:00 00 00 00 00 00 00 00 |........|+
+2012-07-30 18:15:28.658987 : nsbasic_brc:00 00 00 00 00 00 00 00 |........|+
+2012-07-30 18:15:28.658996 : nsbasic_brc:00 00 00 00 00 00 00 00 |........|+
+2012-07-30 18:15:28.659004 : nsbasic_brc:00 00 00 00 00 00 00 00 |........|+
+2012-07-30 18:15:28.659012 : nsbasic_brc:00 00 00 00 17 4F 52 41 |.....ORA|+
+2012-07-30 18:15:28.659021 : nsbasic_brc:2D 30 31 34 30 33 3A 20 |-01403:.|+
+2012-07-30 18:15:28.659029 : nsbasic_brc:64 61 74 61 20 73 61 6B |data.sak|+
+2012-07-30 18:15:28.659038 : nsbasic_brc:6E 61 73 0A |nas. |+
+2012-07-30 18:15:28.659046 : nsbasic_brc:exit: oln=0, dln=362, tot=372, rc=0+
+2012-07-30 18:15:28.659054 : nioqrc:exit+
+2012-07-30 18:16:09.583993 : nioqsn:entry+
+2012-07-30 18:16:09.584062 : nioqsn:exit+
+2012-07-30 18:16:09.584086 : nioqrc:entry+
+2012-07-30 18:16:09.584097 : nsbasic_bsd:entry+
+2012-07-30 18:16:09.584107 : nsbasic_bsd:tot=0, plen=318.+
+2012-07-30 18:16:09.584116 : nttfpwr:entry+
+2012-07-30 18:16:09.584146 : ntt2err:entry+
+2012-07-30 18:16:09.584162 : ntt2err:soc 564 error - operation=6, ntresnt[0]=530, ntresnt[1]=54, ntresnt[2]=0+
+2012-07-30 18:16:09.584171 : ntt2err:exit+
+2012-07-30 18:16:09.584178 : nttfpwr:exit+
+2012-07-30 18:16:09.584192 : nserror:entry+
+2012-07-30 18:16:09.584203 : nserror:nsres: id=0, op=67, ns=12571, ns2=12560; nt[0]=530, nt[1]=54, nt[2]=0; ora[0]=0, ora[1]=0, ora[2]=0+
+2012-07-30 18:16:09.584213 : nsbasic_bsd:exit (-1)+
+2012-07-30 18:16:09.584224 : nioqrc:send failed: bl = 1, nicbl = 1+
+2012-07-30 18:16:09.584234 : nioqper: error from nioqrc+
+2012-07-30 18:16:09.584242 : nioqper: ns main err code: 12571+
+2012-07-30 18:16:09.584250 : nioqper: ns (2) err code: 12560+
+2012-07-30 18:16:09.584258 : nioqper: nt main err code: 530+
+2012-07-30 18:16:09.584266 : nioqper: nt (2) err code: 54+
+2012-07-30 18:16:09.584275 : nioqper: nt OS err code: 0+
+2012-07-30 18:16:09.584285 : nioqer:entry+
+2012-07-30 18:16:09.584293 : nioqer: incoming err = 12150+
+2012-07-30 18:16:09.584301 : niomapnserror:entry+
+2012-07-30 18:16:09.584311 : niqme:entry+
+2012-07-30 18:16:09.584321 : niqme:reporting NS-12571 error as ORA-12571+
+2012-07-30 18:16:09.584330 : niqme:exit+
+2012-07-30 18:16:09.584337 : niomapnserror:exit+
+2012-07-30 18:16:09.584344 : nioqce:entry+
+2012-07-30 18:16:09.584352 : nioqce:exit+
+2012-07-30 18:16:09.584359 : nioqer: returning err = 12571+
+2012-07-30 18:16:09.584366 : nioqer:exit+
+2012-07-30 18:16:09.584374 : nioqrc: returning error: 12571+
+2012-07-30 18:16:09.584381 : nioqrc:exit+
+2012-07-30 18:16:09.584396 : nioqrs:entry+
+2012-07-30 18:16:09.584412 : nioqrs: state = interrupted (1)+
+2012-07-30 18:16:09.584425 : nscontrol:entry+
+2012-07-30 18:16:09.584435 : nscontrol:cmd=45, lcl=0x0+
+2012-07-30 18:16:09.584442 : nscontrol:normal exit+
+2012-07-30 18:16:09.584450 : nscontrol:entry+
+2012-07-30 18:16:09.584457 : nscontrol:cmd=1, lcl=0x0+
+2012-07-30 18:16:09.584464 : nscontrol:normal exit+
+2012-07-30 18:16:09.584476 : nioqsm:entry+
+2012-07-30 18:16:09.584485 : nioqsm: Sending break packet (1)...+
+2012-07-30 18:16:09.584493 : nscontrol:entry+
+2012-07-30 18:16:09.584500 : nscontrol:cmd=45, lcl=0x0+
+2012-07-30 18:16:09.584508 : nscontrol:normal exit+
+2012-07-30 18:16:09.584516 : nsdo:entry+
+2012-07-30 18:16:09.584525 : nsdo:cid=0, opcode=67, *bl=1, *what=17, uflgs=0x100, cflgs=0x3+
+2012-07-30 18:16:09.584534 : nsdo:rank=64, nsctxrnk=0+
+2012-07-30 18:16:09.584543 : nsdo:nsctx: state=8, flg=0x400d, mvd=0+
+2012-07-30 18:16:09.584552 : nsdo:gtn=32, gtc=32, ptn=10, ptc=8191+
+2012-07-30 18:16:09.584560 : nsdofls:entry+
+2012-07-30 18:16:09.584569 : nsdofls:DATA flags: 0x0+
+2012-07-30 18:16:09.584577 : nsdofls:normal exit+
+2012-07-30 18:16:09.584587 : nsdo:sending NSPTMK packet+
+2012-07-30 18:16:09.584596 : nspsend:entry+
+2012-07-30 18:16:09.584605 : nspsend:plen=11, type=12+
+2012-07-30 18:16:09.584614 : nttwr:entry+
+2012-07-30 18:16:09.584628 : ntt2err:entry+
+2012-07-30 18:16:09.584638 : ntt2err:soc 564 error - operation=6, ntresnt[0]=530, ntresnt[1]=54, ntresnt[2]=0+
+2012-07-30 18:16:09.584646 : ntt2err:exit+
+2012-07-30 18:16:09.584657 : nttwr:exit+
+2012-07-30 18:16:09.584668 : nspsend:0 bytes to transport+
+2012-07-30 18:16:09.584677 : nspsend:transport write error+
+2012-07-30 18:16:09.584684 : nspsend:error exit+
+2012-07-30 18:16:09.584692 : nsdo:error sending NSPTMK packet+
+2012-07-30 18:16:09.584700 : nserror:entry+
+2012-07-30 18:16:09.584709 : nserror:nsres: id=0, op=67, ns=12571, ns2=12560; nt[0]=530, nt[1]=54, nt[2]=0; ora[0]=0, ora[1]=0, ora[2]=0+
+2012-07-30 18:16:09.584719 : nsdo:nsctxrnk=0+
+2012-07-30 18:16:09.584726 : nsdo:error exit+
+2012-07-30 18:16:09.584737 : nioqsm:send-break: failed to send break...+
+2012-07-30 18:16:09.584746 : nioqper: error from send-marker+
+2012-07-30 18:16:09.584753 : nioqper: ns main err code: 12571+
+2012-07-30 18:16:09.584761 : nioqper: ns (2) err code: 12560+
+2012-07-30 18:16:09.584769 : nioqper: nt main err code: 530+
+2012-07-30 18:16:09.584776 : nioqper: nt (2) err code: 54+
+2012-07-30 18:16:09.584784 : nioqper: nt OS err code: 0+
+2012-07-30 18:16:09.584792 : nioqsm:exit+
+2012-07-30 18:16:09.584799 : nioqer:entry+
+2012-07-30 18:16:09.584808 : nioqer: incoming err = 12152+
+2012-07-30 18:16:09.584817 : niomapnserror:entry+
+2012-07-30 18:16:09.584824 : niqme:entry+
+2012-07-30 18:16:09.584833 : niqme:reporting NS-12571 error as ORA-12571+
+2012-07-30 18:16:09.584840 : niqme:exit+
+2012-07-30 18:16:09.584847 : niomapnserror:exit+
+2012-07-30 18:16:09.584854 : nioqce:entry+
+2012-07-30 18:16:09.584861 : nioqce:exit+
+2012-07-30 18:16:09.584868 : nioqer: returning err = 12571+
+2012-07-30 18:16:09.584876 : nioqer:exit+
+2012-07-30 18:16:09.584884 : nioqrs:nioqrs: Couldn't send break. returning 12571+
+2012-07-30 18:16:09.584894 : nioqrs:exit+
+2012-07-30 18:16:09.584912 : nioqds:entry+
+2012-07-30 18:16:09.584921 : nioqds: disconnecting...+
+2012-07-30 18:16:09.584933 : nsclose:entry+
+2012-07-30 18:16:09.584945 : nsvntx_dei:entry+
+2012-07-30 18:16:09.584953 : nsvntx_dei:exit+
+2012-07-30 18:16:09.584964 : nstimarmed:entry+
+2012-07-30 18:16:09.584973 : nstimarmed:no timer allocated+
+2012-07-30 18:16:09.584980 : nstimarmed:normal exit+
+2012-07-30 18:16:09.584994 : nttctl:entry+
+2012-07-30 18:16:09.585009 : nttctl:entry+
+2012-07-30 18:16:09.585021 : nsfull_cls:entry+
+2012-07-30 18:16:09.585031 : nsfull_cls:cid=0, opcode=65, *bl=0, *what=0, uflgs=0x0, cflgs=0x0+
+2012-07-30 18:16:09.585040 : nsfull_cls:nsctx: state=8, flg=0x4009, mvd=0+
+2012-07-30 18:16:09.585048 : nsdo:entry+
+2012-07-30 18:16:09.585056 : nsdo:cid=0, opcode=67, *bl=0, *what=1, uflgs=0x0, cflgs=0x1+
+2012-07-30 18:16:09.585065 : nsdo:nsctx: state=8, flg=0x4009, mvd=0+
+2012-07-30 18:16:09.585074 : nsdo:gtn=32, gtc=32, ptn=10, ptc=8191+
+2012-07-30 18:16:09.585082 : nsdo:normal exit+
+2012-07-30 18:16:09.585089 : nsdofls:entry+
+2012-07-30 18:16:09.585097 : nsdofls:DATA flags: 0x40+
+2012-07-30 18:16:09.585105 : nsdofls:sending NSPTDA packet+
+2012-07-30 18:16:09.585113 : nspsend:entry+
+2012-07-30 18:16:09.585120 : nspsend:plen=10, type=6+
+2012-07-30 18:16:09.585128 : nttwr:entry+
+2012-07-30 18:16:09.585140 : ntt2err:entry+
+2012-07-30 18:16:09.585150 : ntt2err:soc 564 error - operation=6, ntresnt[0]=530, ntresnt[1]=54, ntresnt[2]=0+
+2012-07-30 18:16:09.585158 : ntt2err:exit+
+2012-07-30 18:16:09.585165 : nttwr:exit+
+2012-07-30 18:16:09.585173 : nspsend:0 bytes to transport+
+2012-07-30 18:16:09.585181 : nspsend:transport write error+
+2012-07-30 18:16:09.585188 : nspsend:error exit+
+2012-07-30 18:16:09.585196 : nserror:entry+
+2012-07-30 18:16:09.585205 : nserror:nsres: id=0, op=67, ns=12571, ns2=12560; nt[0]=530, nt[1]=54, nt[2]=0; ora[0]=0, ora[1]=0, ora[2]=0+
+2012-07-30 18:16:09.585215 : nsdofls:exit (-1)+
+2012-07-30 18:16:09.585223 : nsbfr:entry+
+2012-07-30 18:16:09.585230 : nsbaddfl:entry+
+2012-07-30 18:16:09.585239 : nsbaddfl:normal exit+
+2012-07-30 18:16:09.585247 : nsbfr:normal exit+
+2012-07-30 18:16:09.585254 : nsbfr:entry+
+2012-07-30 18:16:09.585261 : nsbaddfl:entry+
+2012-07-30 18:16:09.585268 : nsbaddfl:normal exit+
+2012-07-30 18:16:09.585276 : nsbfr:normal exit+
+2012-07-30 18:16:09.585283 : nsfull_cls:normal exit+
+2012-07-30 18:16:09.585291 : nsiocancel:entry+
+2012-07-30 18:16:09.585303 : nsiofrrg:entry+
+2012-07-30 18:16:09.585313 : nsiofrrg:cur = 5e5f3f8+
+2012-07-30 18:16:09.585321 : nsbfr:entry+
+2012-07-30 18:16:09.585328 : nsbaddfl:entry+
+2012-07-30 18:16:09.585335 : nsbaddfl:normal exit+
+2012-07-30 18:16:09.585342 : nsbfr:normal exit+
+2012-07-30 18:16:09.585350 : nsiofrrg:exit+
+2012-07-30 18:16:09.585358 : nsiocancel:exit+
+2012-07-30 18:16:09.585365 : nsclose:closing transport+
+2012-07-30 18:16:09.585375 : nttdisc:entry+
+2012-07-30 18:16:09.585438 : nttdisc:Closed socket 564+
+2012-07-30 18:16:09.585453 : nttdisc:exit+
+2012-07-30 18:16:09.585463 : nsclose:global context check-out (from slot 0) complete+
+2012-07-30 18:16:09.585471 : nsnadisc:entry+
+2012-07-30 18:16:09.585484 : nadisc:entry+
+2012-07-30 18:16:09.585496 : nacomtm:entry+
+2012-07-30 18:16:09.585506 : nacompd:entry+
+2012-07-30 18:16:09.585513 : nacompd:exit+
+2012-07-30 18:16:09.585521 : nacompd:entry+
+2012-07-30 18:16:09.585527 : nacompd:exit+
+2012-07-30 18:16:09.585535 : nacomtm:exit+
+2012-07-30 18:16:09.585545 : nas_dis:entry+
+2012-07-30 18:16:09.585553 : nas_dis:exit+
+2012-07-30 18:16:09.585562 : nau_dis:entry+
+2012-07-30 18:16:09.585577 : nau_dis:exit+
+2012-07-30 18:16:09.585587 : naeetrm:entry+
+2012-07-30 18:16:09.585596 : naeetrm:exit+
+2012-07-30 18:16:09.585604 : naectrm:entry+
+2012-07-30 18:16:09.585613 : naectrm:exit+
+2012-07-30 18:16:09.585623 : nagbltrm:entry+
+2012-07-30 18:16:09.585632 : nau_gtm:entry+
+2012-07-30 18:16:09.585640 : nau_gtm:exit+
+2012-07-30 18:16:09.585648 : nagbltrm:exit+
+2012-07-30 18:16:09.585657 : nadisc:exit+
+2012-07-30 18:16:09.585665 : nsnadisc:normal exit+
+2012-07-30 18:16:09.585675 : nsvntx_dei:entry+
+2012-07-30 18:16:09.585682 : nsvntx_dei:exit+
+2012-07-30 18:16:09.585694 : nsopenfree_nsntx:nlhthdel from mplx_ht_nsgbu, ctx=5e5e0e0 nsntx=5e5e6c0+
+2012-07-30 18:16:09.585703 : nsiocancel:entry+
+2012-07-30 18:16:09.585710 : nsiofrrg:entry+
+2012-07-30 18:16:09.585718 : nsiofrrg:exit+
+2012-07-30 18:16:09.585725 : nsiocancel:exit+
+2012-07-30 18:16:09.585732 : nsmfr:entry+
+2012-07-30 18:16:09.585741 : nsmfr:2944 bytes at 0x5e5e6c0+
+2012-07-30 18:16:09.585748 : nsmfr:normal exit+
+2012-07-30 18:16:09.585755 : nsmfr:entry+
+2012-07-30 18:16:09.585763 : nsmfr:240 bytes at 0x5f2a610+
+2012-07-30 18:16:09.585771 : nsmfr:normal exit+
+2012-07-30 18:16:09.585778 : nsmfr:entry+
+2012-07-30 18:16:09.585785 : nsmfr:280 bytes at 0x63c010+
+2012-07-30 18:16:09.585792 : nsmfr:normal exit+
+2012-07-30 18:16:09.585803 : nladtrm:entry+
+2012-07-30 18:16:09.585820 : nladtrm:exit+
+2012-07-30 18:16:09.585828 : nsmfr:entry+
+2012-07-30 18:16:09.585836 : nsmfr:1496 bytes at 0x5e5e0e0+
+2012-07-30 18:16:09.585844 : nsmfr:normal exit+
+2012-07-30 18:16:09.585851 : nsclose:normal exit+
+2012-07-30 18:16:09.585859 : nioqds:exit+
+2012-07-30 18:16:09.585868 : nsbfree:entry+
+2012-07-30 18:16:09.585876 : nsbgetfl:entry+
+2012-07-30 18:16:09.585884 : nsbgetfl:normal exit+
+2012-07-30 18:16:09.585894 : nsbaddfl:entry+
+2012-07-30 18:16:09.585901 : nsbaddfl:normal exit+
+2012-07-30 18:16:09.585909 : nsbfree:normal exit+
+2012-07-30 18:16:09.585916 : nsbfree:entry+
+2012-07-30 18:16:09.585923 : nsbgetfl:entry+
+2012-07-30 18:16:09.585930 : nsbgetfl:normal exit+
+2012-07-30 18:16:09.585938 : nsbaddfl:entry+
+2012-07-30 18:16:09.585945 : nsbaddfl:normal exit+
+2012-07-30 18:16:09.585952 : nsbfree:normal exit+
+2012-07-30 18:16:09.585961 : nigtrm:Count in the NI global area is now 2+
+2012-07-30 18:16:09.585974 : nsbfrfl:entry+
+2012-07-30 18:16:09.585982 : nsbrfr:entry+
+2012-07-30 18:16:09.585991 : nsbrfr:nsbfs at 0x5f26470, data at 0x5f26520.+
+2012-07-30 18:16:09.585999 : nsbrfr:normal exit+
+2012-07-30 18:16:09.586006 : nsbrfr:entry+
+2012-07-30 18:16:09.586015 : nsbrfr:nsbfs at 0x5f28540, data at 0x5f285f0.+
+2012-07-30 18:16:09.586025 : nsbrfr:normal exit+
+2012-07-30 18:16:09.586033 : nsbrfr:entry+
+2012-07-30 18:16:09.586040 : nsbrfr:nsbfs at 0x5e5f480, data at 0x5e5f530.+
+2012-07-30 18:16:09.586048 : nsbrfr:normal exit+
+2012-07-30 18:16:09.586055 : nsbrfr:entry+
+2012-07-30 18:16:09.586063 : nsbrfr:nsbfs at 0x5f2a610, data at 0x5f2a9f0.+
+2012-07-30 18:16:09.586073 : nsbrfr:normal exit+
+2012-07-30 18:16:09.586082 : nsbrfr:entry+
+2012-07-30 18:16:09.586090 : nsbrfr:nsbfs at 0x62c7d0, data at 0x5f2ca10.+
+2012-07-30 18:16:09.586098 : nsbrfr:normal exit+
+2012-07-30 18:16:09.586106 : nsbfrfl:normal exit+
+2012-07-30 18:16:09.586153 : nigtrm:Count in the NL global area is now 3+

Oracle 11g R2 Export hang problem...

Hi,
I tried to export full database using system user,
my statement in Oracle 11g R2 on RedHat Linux is,
exp system/******* file=/exportdb/fulldb.dmp log=/exportdb/fulldb.log full=y
I hangs at
.About to export the entire database ...
. exporting tablespace definitions
. exporting profiles
. exporting user definitions
. exporting roles
. exporting resource costs
. exporting rollback segment definitions
. exporting database links
. exporting sequence numbers
. exporting directory aliases
. exporting context namespaces
. exporting foreign function library names
. exporting PUBLIC type synonyms
. exporting private type synonyms
. exporting object type definitions
. exporting system procedural objects and actions
When i cancel this line using ctl+c it says
ORA-01013: user requested cancel of current operation
ORA-06512: at "WMSYS.LT_EXPORT_PKG", line 1379
ORA-06512: at line 1
EXP-00083: The previous problem occurred when calling WMSYS.LT_EXPORT_PKG.system_info_exp
Ctl+c again
EXP-00008: ORACLE error 1013 encountered
ORA-01013: user requested cancel of current operation
ORA-06512: at "SYS.DBMS_SERVER_ALERT_EXPORT", line 10
ORA-06512: at "SYS.DBMS_SERVER_ALERT_EXPORT", line 118
ORA-06512: at line 1
EXP-00083: The previous problem occurred when calling SYS.DBMS_SERVER_ALERT_EXPORT.system_info_exp
then it continues and shows message
Export terminated successfully with warnings.
I have granted system user with sys.dbms_defer_import_internal
and
sys.dbms_export_extension
I have also tried using 'sys/***** as sysdba'
I also run utlrp.sql script to figure out any error but it responded with '0 errors'.
Does anyone has a solution?

If I use expdp, the problem is the same, I have used this query,
$expdp directory=DATA_PUMP_DIR dumpfile=test.dmp logfile=test.log full=y
Username: system/*********
Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Starting "SYSTEM"."SYS_EXPORT_FULL_01": system/******** directory=DATA_PUMP_DIR dumpfile=test.dmp logfile=test.log full=y
Estimate in progress using BLOCKS method...
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/TABLE_DATA
Total estimation using BLOCKS method: 3.404 GB
Processing object type DATABASE_EXPORT/TABLESPACE
Processing object type DATABASE_EXPORT/PROFILE
Processing object type DATABASE_EXPORT/SYS_USER/USER
Processing object type DATABASE_EXPORT/SCHEMA/USER
Processing object type DATABASE_EXPORT/ROLE
Processing object type DATABASE_EXPORT/GRANT/SYSTEM_GRANT/PROC_SYSTEM_GRANT
Processing object type DATABASE_EXPORT/SCHEMA/GRANT/SYSTEM_GRANT
Processing object type DATABASE_EXPORT/SCHEMA/ROLE_GRANT
Processing object type DATABASE_EXPORT/SCHEMA/DEFAULT_ROLE
Processing object type DATABASE_EXPORT/SCHEMA/TABLESPACE_QUOTA
Processing object type DATABASE_EXPORT/RESOURCE_COST
Processing object type DATABASE_EXPORT/TRUSTED_DB_LINK
Processing object type DATABASE_EXPORT/SCHEMA/SEQUENCE/SEQUENCE
Processing object type DATABASE_EXPORT/SCHEMA/SEQUENCE/GRANT/OWNER_GRANT/OBJECT_GRANT
Processing object type DATABASE_EXPORT/DIRECTORY/DIRECTORY
Processing object type DATABASE_EXPORT/DIRECTORY/GRANT/OWNER_GRANT/OBJECT_GRANT
Processing object type DATABASE_EXPORT/CONTEXT
Processing object type DATABASE_EXPORT/SCHEMA/PUBLIC_SYNONYM/SYNONYM
Processing object type DATABASE_EXPORT/SCHEMA/SYNONYM
Processing object type DATABASE_EXPORT/SCHEMA/TYPE/TYPE_SPEC
Processing object type DATABASE_EXPORT/SCHEMA/TYPE/GRANT/OWNER_GRANT/OBJECT_GRANT
Processing object type DATABASE_EXPORT/SYSTEM_PROCOBJACT/PRE_SYSTEM_ACTIONS/PROCACT_SYSTEM
Processing object type DATABASE_EXPORT/SYSTEM_PROCOBJACT/PROCOBJ
Then it again got hang, and never proceeds.
Please reply for any solutions....

Skipping a table from EXPDP full backup

Hi,
Is it possible to skip a table from FULL expdp backup,if yes what would be command for the same.My database is 10.2.0.4 Windows 64bit.
Regards
Vijay

Hello,
With Datapump, the parameters EXCLUDE and INCLUDE may help you to select finely the Objects (Table, Procedure, ...) you want to export or import.
Please, find enclosed a link about the way to use these useful parameters:
http://www.oraclefaq.net/2007/03/09/expdp-datapump-excludeinclude-parameters/
As previously posted, the parameter EXCLUDE should answer to your request.
EXCLUDE and INCLUDE can be used with a FULL export / import these parameters limit the selection of the Object. More over, these parameters are mutually exclusive.
Best regards,
Jean-Valentin
Edited by: Lubiez Jean-Valentin on Jul 1, 2010 8:49 AM

DATAPUMP EXPORT FAILS (for certain table names)

I have a table name (G$_EXP$) defined in a user foo.
When I try to export the table using expdp (datapump export command like utility):-
expdp foo/foo TABLES=G$_EXP$ DIRECTORY=USERDIR EXCLUDE=TRIGGER
I get the following error messages:-
_EXP: Undefined variable.
So can expdp not handle this kind of table names.
Will appreciate any comments/responses.

It's not expdp can't handle the tablename, it's your OS interprete $xxx as variables.
Try to use " to quote the tablename, or use parameter file PARFILE

Expdp datapump Problem

Similar Messages

Maybe you are looking for