When the imp query clause outputs data in the difference exp between unix and windows platforms, it is occasionally required to import only part of the data in a large table. In this case, the query clause may involve numeric, string, or date types in the query clause. To do this, perform a simple test to create tables and data: www.2cto.com create table test_qu (col_num number (10), col_var varchar2 (10), col_dat date); insert into test_quselect rownum, to_char (rownum * 5), round (sysdate + rownum) from dual connect by rownum <20; commit; select * from test_qu; UNIX: 123exp report/oracle @ ora10 file = 1.dmp TABLES = \ (test_qu \) QUERY = \ "WHERE col_num \> = 5 \" exp report/oracle @ ora 10 file = 1.dmp TABLES = \ (test_qu \) QUERY = \ "WHERE col_var \> = \ '5 \ '\" exp report/oracle @ ora10 file = 1.dmp TABLES = \ (test_qu \) QUERY = \ "WHERE col_dat \> = to_date \ (\ '2017 \ ', \ 'yyyymmdd \' \) \" WINDOWS: www.2cto.com exp report/oracle @ ora10 file = 1.dmp TABLES = (test_qu) QUERY = "'where col_num> = 5'" exp report/oracle @ ora10 file = 1.dmp TABLES = (test_qu) QUERY = '"WHERE col_num> = 5" 'exp report/oracle @ ora10 file = 1.dm P TABLES = (test_qu) QUERY = "'where col_var> = '5'" exp report/oracle @ ora10 file = 1.dmp TABLES = (test_qu) QUERY = '"WHERE col_var> = '5'" 'exp report/oracle @ ora10 file = 1.dmp TABLES = (test_qu) QUERY = "'where col_dat> = to_date ('201312''', ''yyymmdd') '" exp report/oracle @ ora10 file = 1.dmp TABLES = (test_qu) QUERY = '"WHERE col_dat> = to_date ('201312''', ''yyymmdd')"' is a simple example of three common types of data. Www.2cto.com it should be noted that if the server uses version 9.2 while the client uses version 10g, the error EXP-00056: ORACLE error 6550 encounteredORA-06550: line 1, column 41: PLS-00302: component 'set _ NO_OUTLINES 'must be declaredORA-06550: line 1, column 15: PL/SQL: Statement ignoredEXP-00000: Export terminated unsuccessfully