![]() You can avoid these error messages by restricting your export to tables that contain a column CHANGE_DATE. ORA-00904: "CHANGE_DATE": invalid identifier You will get an error message for each table that does not contain a column CHANGE_DATE ORA-31693: Table data object "AUD"."" failed to load/unload and is being skipped due to error: ![]() In Oracle9 and higher, the Export utility always exports user data, including Unicode data, in the character sets of the Export server. exp user/pwdconnectionString DIRECTY LOGmyLog.LOG OWNERmyUser FILEmyFile.dat. So finally the following INCLUDE parameter file is sufficient INCLUDE=TABLE The OWNER parameter specifies this mode in Export. You can say that you only want to import tables. You already restrict your export to the AUD schema so there is not need to filter out the tables with owner='AUD' in the INCLUDE-clause. Of course I can put all parameters in the same line instead. Note that I use the back slash () at the end of each line to avoid a very long line in the shell command line. INCLUDE=TABLE:"\"IN(select table_name from dba_tables where owner ='AUD')\"" \ If you want to use these parameter in the shell command line then you can do the following expdp system/xxxxxxx DIRECTORY=EXPDP_DIR \ Note that you use single quotes (') to enclose string literals and double quotes (") to enclose parameters the are not oly single words. The FILESIZE parameter will limit the maximum size of each dump file to 2 gigabytes. Query="where change_date > to_date('3','DD-MON-YYYY')" expdp hr/hr directoryTESTDIR tableshr.emp2. INCLUDE=TABLE:"IN(select table_name from dba_tables where owner ='AUD')" The text of the parameter file is DIRECTORY=EXPDP_DIR The simplest way to circumvent these problems is to write a parameter file for expdp that contains the parameters. You have a problem to wirte down the code appropriate for the shell.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |