table partition failed in oracle11g expdp exported

Hi gurus of the Oracle,.

64-bit RHEL
Oracle11g node 2 RAC/GRID
Version: 11.2.0.1.0

Every day, we take the datapump application backup

But today, we found the following errors in the rest of the table datapump newspapers are exported successfully

in fact, there is a TBLSESSION of our application that had 8 partiton table created in hash methods

. . exported "USERNAME". "" TBLMSESSION ":"PART2"22,00 MB 123764 lines
. . exported "USERNAME". "' TBLMSESSION ': 'PART3" 22.09 MB 124279 lines
. . exported "USERNAME". "' TBLMSESSION ': 'PART4' 22,08 Mo 124182 lines
. . exported "USERNAME". "" TBLMSESSION ":"PART5"22,07 MB 124140 lines
. . exported "USERNAME". "' TBLMSESSION ': 'PART7' 22,05 MB 124027 lines
ORA-31693: Data Table object 'USERNAME '. "' TBLMSESSION ': 'PART8' could not load/unload and being ignored because of the error:
ORA-19502: write error on file ' / backup/exp_username_dbname_28041214550101.dmp ', block number 33591 (block size = 4096)
ORA-27072: IO file error
Additional information: 4
Additional information: 33591
Additional information: 4096
. . exported "USERNAME". "" TBLMSESSION ":"PART1"123949 lines 22,03 MB
. . exported "USERNAME". "' TBLMSESSION ': 'PART6' 22,08 Mo 124169 lines


We tried also selected in separate but record partition data is counted with success

Select count (1) in the PARTITION TBLMSESSION (PART1);
Select count (1) in the PARTITION TBLMSESSION (PART2);
Select count (1) in the PARTITION TBLMSESSION (PART3);
Select count (1) in the PARTITION TBLMSESSION (PART4);
Select count (1) in the PARTITION TBLMSESSION (PART5);
Select count (1) in the PARTITION TBLMSESSION (PART6);
Select count (1) in the PARTITION TBLMSESSION (PART7);
Select count (1) in the PARTITION TBLMSESSION (PART8);

How to troubleshoot and resolve the problem?

Concerning
Hitgon

Hi Hitgon

I find this on metalink and found the paragraphs below. See meatlink note:
DataPump export fails with error ORA-39125 ORA-19502 ORA-27072 error 11 temporarily unavailable [resource ID 831746.1]

Neeraj-

Tags: Database

Similar Questions

  • space missing after the process of partitioning failed. I lost 500 GB and can not get it back.

    Hi, space on my hard drive disappeared after the process of partitioning failed. I interrupted the process, and after my boot drive lost 500 GB that I wanted to use it to boot camp. Now I can't get it back. Used diskutil resize the volume, but get the error message about the wrong size on cs and advice to make any repair. : Basic storage logical volume supplied has an incorrect size. You must run repair disc-set

    Help, please.

    pavadebo wrote:

    Hi, space on my hard drive disappeared after the process of partitioning failed. I interrupted the process, and after my boot drive lost 500 GB that I wanted to use it to boot camp. Now I can't get it back. Used diskutil resize the volume, but get the error message about the wrong size on cs and advice to make any repair. : Basic storage logical volume supplied has an incorrect size. You must run repair disc-set

    The message is correct. Start Internet recovery (command + Opt + R during startup) and click on utilities-> disk utility, click on the outermost disk and click first aid or repair.

  • Slow running queries on a table partitioned by date

    I have a table partitioned by COLDATE, when I write a query to get the data is slow, even if I try to only get 1 day data. How can I correct this query runs faster?

    Oracle Version: 10g

    Number of lines:

    See the below query

    select COL1, COL2 RANK() OVER (PARTITION BY   COL1, COLDATE ORDER BY OTHER_DATE DESC) SHOW_RANK
    from 
    SAMPLETABLE
    where COLDATE BETWEEN '01-JAN-2015' AND '01-JAN-2015'
    
    
    create table SAMPLETABLE
    (
      COL1   NUMBER(10) not null,
      COL2        NUMBER(10) not null,
      COLDATE       DATE not null,
      OTHER_DATE DATE
    )
    partition by range (COLDATE)
    (
      partition PARTITION_01_2015 values less than (TO_DATE(' 2015-02-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
        tablespace MYTABLESPACE_2015
        pctfree 20
        initrans 1
        maxtrans 255
        storage
        (
          initial 64K
          minextents 1
          maxextents unlimited
        ),
      partition PARTITION_02_2015 values less than (TO_DATE(' 2015-03-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
        tablespace MYTABLESPACE_2015
        pctfree 20
        initrans 1
        maxtrans 255
        storage
        (
          initial 64K
          minextents 1
          maxextents unlimited
        ),
      .
      .
      .
      .
      .
      .
      partition PARTITION_12_2016 values less than (TO_DATE(' 2017-01-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
        tablespace MYTABLESPACE_2016
        pctfree 20
        initrans 1
        maxtrans 255
        storage
        (
          initial 64K
          minextents 1
          maxextents unlimited
        )
    

    Force the session in parallel mode and check with the parallel hint option.

    SQL > alter session force parallel dml.

    SQL > select / * + parallel (table_name, none of the servers) * / colA, colB from table_name;

  • DBA_TABLES. NULL for tables partitioned, yet Nom_tablespace DBMS_METADATA. GET_DDL displays a name...

    Hello

    Hence the name of tablespace comes when you make one

    ~ Select DBMS_METATDATA. GET_DDL ('TABLE', 'tname', 'owner')...

    on a table partitioned, where you see things like:

    ~ CREATE TABLE...

    ~ ...

    ~ STORAGE(INITIAL 134217728 NEXT 134217728 MINEXTENTS 1 MAXEXTENTS 2147483645)

    (~ DEFAULT USER_TABLES)

    ~ TABLESPACE "ABCD_LOGD2".

    before all the blocks related to the different partitions of this table, where a

    ~ Select nom_tablespace from dba_tables where table_name = 'TNOM '...

    Returns a null value?

    Whence dbms_metatdata this ABCD_LOGD2 value? (in what dictionary?,)

    DBA_SEGMENTS/extents display only the partitions information...)

    Thank you...

    SEB

    Hello

    What is the value of 'deffered_segment_creation '.

    Take a look of it

    Select def_tablespace_name in the dba_part_tables where table_name = 'tname'--> your table

    Concerning

  • Table partitioning

    I have a table in my DB with stored more then 24 million and is growing every day. Growth rate increases with the passage of time. I want this partition table, in such a way that three first partitions such as each partition contains 10 years of data, and the remaining partition such as each partition contains data for 5 years.
    This is the first time that I am any table partitioning, I understand following sql is not correct, I need your help in resolving this issue.
    ALTER TABLE cb_pen_pmt_slip_dtl
    ADD
    PARTITION BY range (payment_date)
    INTERVAL (NUMTOYMINTERVAL(5,'YEAR'))
    (PARTITION p1 VALUES LESS THAN (TO_DATE('2000-01-01','YYYY-MM-DD'))
    partition p2 values less than (maxvalue));

    Hello

    This link can help you...
    >

    Kind regards

  • Table Partitioned parallelized vs

    Hello
    (11.2 server, OS = OL5)

    I have a table that contains more than 50 million lines. I created this table with option 'parallel degree (x).

    It seems that the time required to execute a query on this table does not change when I share that, for example partition range dividing the table to 3 partitions.

    (access the request a unique index in the table and the query criteria match exactly one of the partitions)

    the question:
    1. What is the difference of strategy parallelism between «Parallel degree...» "and the"Division "?
    2. which of them are better in what scenario?
    3. is it better to use PARALLEL_AUTOMATIC_TUNING?
    4 and especially why the performance doesn't change even with a local index on the partitions?

    Thank you
    SMSK.

    >
    It seems that the time required to execute a query on this table does not change when I share that, for example partition range dividing the table to 3 partitions
    . . .
    (access the request a unique index in the table and the query criteria match exactly one of the partitions
    . . .
    @Adam Martin: thanks, but I was explained to question 4 that the performance does not change when I toggle locality index.
    >
    I do not see why it would be necessarily change just of partitioning. What is your reason to think so?

    If the index access is used it is basically to get the IDENTIFIER of a line of interest. The line can then be retrieved using the ROWID. The recovery time will be essentially the same way regardless of the line in a partitioned table or non-partitioned table, and regardless of whether the line of partition. This is because the ROWID is (simple explanation here) a FILE ID (which file?), a BLOCK number (relative block in the file) and a LINE NUMBER (which line in the block. It doesn't matter if the segment that is the block is a segment of the table, partitioned table segment, segment index, etc.

    It is the only factor that COULD change the time of the query when the index is used if the access of the index itself is more effective when the table is partitioned when the table is not partitioned.

    Clearly if it is an overall index, there is a change since the index access itself will be the same.

    The only factor now that MIGHT change the time of the request is so if 1) the index is changed locally and 2) the local index has a different structure than the old index that allows to find the best performing required index entries.

    You have not published information on the index of structure, so let me give you an analogy which shows a scenario where it is clear that the access to the index would not change.

    Assume that the overall index is analogous to a catalogue of cards with 26 entries - one for each letter of the alphabet. My query accesses the entries beginning with the letter 'F' As discussed above in table access to aid a ROWID obtained from the index will be the same, if the table is partitioned or not.

    So now I have the partition table and have 26 partitions - one for each letter of the alphabet.

    With the help of the global index of the access to the partition of 'F' will be the same.

    Now, if I create a local index (instead of global) it's almost as if I now 26 index, one for each letter of the alphabet. The first entry for the 'F' in the global index can be found by reading the root node and perhaps one or two other nodes - then that an index scan can be performed.

    The first entry for the 'F' in the local index is at the beginning of the index - no need to jump or to do a binary search to ignore the 'A', 'B', etc. entered.

    This time difference is microscopic.

    Once I found the first entry for the 'F' either in the overall index, or local 'F' remaining entries in the index are consecutive, so access time will be the same.

    I don't know if there is a structural difference between the indices and the that you tried, but the above should show if the structure (order) has not changed it would not be a noticeable difference in access.

  • Become table partitioning

    Hi I have a table where about 260 bln + records. and actionaly of infromation inserted. the structure of the table.

    CREATE TABLE NUM_CALLS
    (
    NUMBER OF N_BLK
    NUMBER,
    NUMBER OF SRV_A
    NUMBER OF SRV_B
    NUMBER OF IND_B
    START DATE,
    NUMBER OF PTT,
    NUMBER OF AIR,
    NUM VARCHAR2 (2000 BYTE),
    NUMBER OF HARD,
    VARCHAR2 (240 BYTE) SERVICES,
    STATUS VARCHAR2 (1 BYTE),
    VARCHAR2 (240 BYTE) DSC,
    INCOMING NUMBER,
    THE NUMBER LEAVING,
    NUMBER OF BILLPAR
    NUMBER OF AIR_SUB
    NUM_A VARCHAR2 (2000 BYTE),
    NUMBER OF PTT_SUB
    DIR CHAR (1 BYTE).
    YOUR VARCHAR2 (5 BYTE)
    NUMBER OF PTT_TOLL
    NUMBER OF R_ROAMFILE_SEQ
    NUMBER OF INDICATED,
    NUMBER OF SRV_TOLL
    PTT_TOLL2 NUMBER,
    SRV_TOLL2 NUMBER,
    IMEI VARCHAR2 (50 BYTE),
    RTYPE VARCHAR2 (10 BYTE),
    NUMBER OF R_MSCID
    NUMBER OF R_CALLS_LOG
    NUMBER OF UTC,
    NUMBER OF TRANSACTIONS,
    NUMBER OF SRC_SEQN
    NUMBER OF FWD_TYPE
    NUMBER OF TM_EVENTS
    DST VARCHAR2 (20 BYTE),
    ACCUM RAW (2000).
    UTTYPE CHAR (1 BYTE),
    TM_MODIFIERS RAW (2000)
    )
    TABLESPACE CDR
    PCTUSED 40
    PCTFREE 10
    INITRANS 1
    MAXTRANS 255
    STORAGE)
    80K INITIAL
    MINEXTENTS 1
    MAXEXTENTS UNLIMITED
    PCTINCREASE 0
    FREELISTS 1
    FREELIST GROUPS 1
    DEFAULT USER_TABLES
    )
    LOGGING
    NOCOMPRESS
    NOCACHE
    NOPARALLEL
    NOMONITORING;

    There is no primary key on the table, and this table records are not unique.



    I want to become this table partitioning column by TRT (date) by date. is it possible to become the partitioning table after and if this table actionaly used? If possible then how can I do?

    Create the new table with a different name, but same structure as NUM_CALL with no data ex create table new_table in new_table select * from YOUR_TABLE_NAME where 1 = 2;
    or just get ddl for the use of this table:

    SELECT DBMS_METADATA. GET_DDL('TABLE','YOUR_TABLE_NAME') FROM dual;

    Modify this script, create the new table, and then create the partition you want (daily, monthly, annual) of course you can also create a subpartition.

    prepare a few anonymous PLSQL block, and then insert the data into the new partition table, that's all.

    stop the execution of the process, drop old table and rename the new table with the old name (deleted table)

  • Why cannot create the table partitioned successfully?

    Why cannot create the table partitioned successfully?
    SQL> create table hr.gps_log_his
    (id number,
    name varchar2(10),
    time date)
    tablespace ts_log_his
    PARTITION BY RANGE (TIME)
    (PARTITION udp_part09110707 VALUES LESS THAN (TO_DATE('09110708','yymmddhh24')),
    PARTITION udp_part09110708 VALUES LESS THAN (TO_DATE('09110709','yymmddhh24')),
    PARTITION udp_part09110709 VALUES LESS THAN (TO_DATE('09110710','yymmddhh24')),
    PARTITION udp_part09110710 VALUES LESS THAN (maxvalue)
    );
    
    (PARTITION udp_part09110707 VALUES LESS THAN (TO_DATE('09110708','yymmddhh24')),
    Error on line 7: 
    ORA-14120: DATE columns did not specify the complete partitioning limits.

    The detailed error message is as follows:

    ORA-14120: incompletely specified partition bound for a DATE column
    
    Cause: An attempt was made to use a date expression whose format does not fully
    (i.e. day, month, and year (including century)) specify a date as a partition bound
    for a DATE column. The format may have been specified explicitly (using TO_DATE()
    function) or implicitly (NLS_DATE_FORMAT).
    
    Action: Ensure that date format used in a partition bound for a DATE column supports
    complete specification of a date (i.e. day, month, and year (including century)). If
    NLS_DATE_FORMAT does not support complete (i.e. including the century) specification
    of the year, use TO_DATE() (e.g. TO_DATE('01-01-1999', 'MM-DD-YYYY') to fully
    express the desired date. 
    

    Action: Change to_date('09110708','yymmddhh24') to
    to_date('2009110708','yyyymmddhh24')

  • Schema expdp export missing tables

    Hello world

    I'm trying to implement a scheme to export with expdp on 12.1.0.2 (Windows7, 64-bit) with the following call:

    "Usr/usr@db EXPDP SCHEMAS = XXX DIRECTORY = TMP_EXPDP VERSION = 10.2.0.1.0 EXCLUDE = STATISTICS dumpfile = tt.sad logfile = tt.log"

    In the log file that results, I see that at least 2 Tables are missing?

    Is there someone who can explain this behavior?

    Made the excluded paintings contains virtual columns or the (archived) LOBs, in other words, some features that is not available to the point 10.2

  • expdp, export only 1000 of each table

    Hi gurus of the oracle,.

    My Version of oracle is 12 c,

    I have 1000 tables in the database of mu, the database size is 700 GB,

    purpose of test, I need examples of 1000lignes data from each table.

    so, how can I export 1000 rows in each table by using expdp

    Thanks in advance

    Concerning

    REDA

    Hi reda,.

    you need not escpae characters in him parfile then it should look like this:

    dumpfile = 1000rowss.dmp logfile = 1000r2.log = directory backup schemas = bipub query = "where rownum"<>

    See you soon,.

    Rich

  • How to find tables partitioned, whose loading may fail with error ORA-14400

    Hello

    We have several partitioned tables. Sometimes when partitions are not created for this month, we get this error

    ORA-14400 does map to any partition inserted partition key

    May I know if there are any script or sql that I can use to discover arrays that may fail to load if DBA creates partitions in the next 2 weeks?

    Thank you
    Sarayu K.S.

    Of course, you can:

    1. look in DBA_TAB_PARTITIONS by nom_partition if you are using a special naming convention, where owner = and table_name = and nom_partition =

    2. without entering the name of the partition, you could use dba_tab_partitions and instead check that there is a partition to your table with a high_value you plan to use. Know that the high_value is a long data type, then you will probably need to convert it into a varchar2.

    3. before your big load, you can also insert a row into the table of destination with the new partition key that will be used and intercept errors with an exception handler. Roll it back if he succeeds.

    4. a number of partitions may be created in advance to avoid the constant surveillance of the new partitions.

    5 or you could also consider switching to interval partitioning if you're on 11 g and get out of the business of having to manually create partitions.

  • Table view is different in expdp/impdp?

    11.2 / Linux

    With exp/imp original: OWNER, TABLES and FULL modes are mutually exclusive. IE in original exp, if you want to make a backup of the EMP table in the scott schema, the following will be error
    exp / tables= EMP owner=SCOTT file=selected_tables.dmp log=selected_tables.log
    
    But this will end up in
    EXP-00026: conflicting modes specified
    EXP-00000: Export terminated unsuccessfully
    You must prefix the name of the owner (tables = < owner >. < table_name >) as below for the prescription above
    exp / tables= SCOTT.EMP file=selected_tables.dmp log=selected_tables.log
    But in impdp things work differently

    I provided a dump expdp of REG_TRACK_EVT of a CLS_USR_PROD scheme. I wanted to import that table in the schema of development CLS_USR_DEV. So, I did. But launch error ORA - 39166 TI kept as below
    $ impdp userid=\'/ as sysdba\' DIRECTORY=DPUMP_DIR DUMPFILE= reg_track_evt.dmp LOGFILE=reg_track_evt-imp.log tables=CLS_USR_DEV.REG_TRACK_EVT
    
    Import: Release 11.2.0.1.0 - Production on Mon Jul 30 18:24:32 2012
    
    Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.
    
    Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    ORA-39002: invalid operation
    ORA-39166: Object CLS_USR_DEV.REG_TRACK_EVT was not found.
    To solve this problem, I had to remove the parameter TABLES (!) and use the REMAP_SCHEMA parameter
    impdp userid=\'/ as sysdba\' DIRECTORY=DPUMP_DIR DUMPFILE= reg_track_evt.dmp LOGFILE=reg_track_evt-imp.log REMAP_SCHEMA=CLS_USR_PROD:CLS_USR_DEV
    If this is the case, then what's the point of having the TABLES parameter in impdp?

    It's really the same thing regarding conflicting modes. Of what you have used in your import command:

    Impdp userid =------"/ ACE sysdba\ ' DIRECTORY = DUMPFILE DPUMP_DIR = LOGFILE reg_track_evt.dmp = reg_track_evt - imp.log REMAP_SCHEMA = CLS_USR_PROD:CLS_USR_DEV

    If you are remapping CLS_USR_PROD:CLS_USR_DEV then the table in the dumpfile is called CLS_USR_PROD. REG_TRACK_EVT and you tried to import CLS_USR_DEV. REG_TRACK_EVT and this table did not exist.

    What you specify on the tables = command is the table in the desired dumpfile. What you specify in the remapping of the color settings is where you want the table created, therefore, your first order was close, you need this:

    Impdp userid =------"/ ACE sysdba\ ' DIRECTORY = DUMPFILE DPUMP_DIR = LOGFILE reg_track_evt.dmp = reg_track_evt - imp.log tables = CLS_USR_PROD. REG_TRACK_EVT REMAP_SCHEMA = CLS_USR_PROD:CLS_USR_DEV

    I hope this helps.

    Dean

  • Create no partition Table partitioning

    Dear all,

    I have a table that is not partition, and it has about 20 G data... If I want that table with say DATE_M partition column

    Please can anyone suggest the best way to do it.

    Thank you

    To create a partitioned table

    (1) you must make a backup of the existing one you can take expdp or DEC

    (2) remove the table and create the same table now with partitions (a minimum score is required)

    you want a range of ex-based partition if you use a date column

    (3) loading data from the previous table into the new partitioned table, either by DEC or impdp, the inserts will be automatically in their respective partitions and you don't mention explicitly.

    Their is no other possible way to partition a non partitioned table, you can do than workarounds to minimize the downtime of the table trying different ways to load data into the partitioned table.

    You can use the enable row movement clause of create table and also use local indexes for easy maintenance partition.

  • table partitioned and unique keys

    I really don't understand why Oracle does not apply in some cases, unique keys.

    Let's say I have a table

    create table t (t_type not null, t_key not null, id not null, not null value)

    list partition (t_type)

    (

    type1 partition values ('ppp1"),

    rest of partition (default) values

    ) as

    Select "ppp" | rownum, rownum, rownum, rownum of double connect by rownum < = 100;

    And following changes in the indices for unique keys

    -1

    create index idx_1 on t (t_key, id);

    ALTER table t add constraint t_uk unique (t_key) using index idx_1;

    ALTER table drop constraint t_uk drop index;

    -2

    create index idx_1 on t (t_key, id, t_type);

    ALTER table t add constraint t_uk unique (t_key) using index idx_1;

    ALTER table drop constraint t_uk drop index;

    -3

    create index idx_1 on t (t_key, id, t_type) local;

    ALTER table t add constraint t_uk unique (t_key) using index idx_1;

    Drop index idx_1;

    -4

    create an index only idx_1 on t (t_key, id);

    ALTER table t add constraint t_uk unique (t_key) using index idx_1;

    Drop index idx_1;

    -5

    create an index only idx_1 on t (t_key, id, t_type);

    ALTER table t add constraint t_uk unique (t_key) using index idx_1;

    Drop index idx_1;

    -6

    create an index only idx_1 on t (t_key, id, t_type) local;

    ALTER table t add constraint t_uk unique (t_key) using index idx_1;

    Drop index idx_1;

    -7

    create index idx_1 on t (t_key, t_type, id) local;

    ALTER table t add t_uk unique constraint (t_key, t_type) using index idx_1;

    ALTER table drop constraint t_uk drop index;

    -8

    create an index only idx_1 on t (t_key, t_type, id) local;

    ALTER table t add t_uk unique constraint (t_key, t_type) using index idx_1;

    Drop index idx_1;

    I got the set of questions:

    1. first and second cases were performed with success while 4th and 5th failed.

    The only difference is that the overall index in 4th and 5th cases are unique.

    It is unclear why ' ORA-14196: specified index cannot be used to apply the constraint. ' has occurred.

    2. in the third case index is similar to that in second place with the only difference that it is local.

    Still, it is not clear why it failed with ORA-14196.

    3 and the last question why ORA-14196 arose in 8 cases, while the 7th, it didn't.

    The only difference is the local index in 8 cases is unique.

    Thank you

    Hi Alex

    (1) index 4 and 5 cannot be used to police the unique constraint as a unique index must have the same list of column under duress. Index 4, to establish in a non-unique index or to remove the column id of the index. To index 5, you will need to make a non-unique index or remove the columns id and index t_type.

    (2) 3 index cannot be used to the unique constraint of police that it is a local index and is not partitioned column (t_type) in both the definition of index/constraint. If allowed, this would require Oracle having to visit each partition to ensure that any new value of t_key is truly unique, that would not scale. Include the t_type column in the constraint and the index to both t_type and t_key as of the columns (so move the id column 3rd position) and it would be successful.

    (Index 3) 8 fails for the same reason as in 1). It's a unique index with a different column from the constraint list. Remove the id column of the index or to make it a non-unique index and it will be successful.

    In summary, a unique index MUST have the same list of column than the constraint and a local index MUST have the partitioning columns in both the definition of index/constraint.

    See you soon

    Richard Foote

    http://richardfoote.WordPress.com/

  • using multiple tables in a query in expdp clause

    Is it possible to use the table of multiples in a query of expdp option? I'm doing the following and it fails with the message 'Invalid identifier' I use Oracle version 10.2.0.3 10

    Settings (x.par)

    ************************

    DIRECTORY = DATA_PUMP_DIR

    USERID=XYZ/XYZ@DB1

    DUMPFILE = X.DMP

    LOGFILE = X.LOG

    CONTENT = DATA_ONLY

    TABLES = "TAB1".

    QUERY = TAB1: "WHERE EXISTS (SELECT 1 FROM TAB2 WHERE TAB2.)" KEYID = TAB1. KEYID).

    expdp parfile = x.par

    Error

    ******

    ORA-00904: "TAB1". "" KEYID ": invalid identifier

    Please share your ideas

    Thank you

    Great, thank you very much.it very really worked.

Maybe you are looking for