tag:blogger.com,1999:blog-6392616969060675513.post5261500146677576206..comments2023-11-24T01:23:27.652-08:00Comments on Learn Oracle Database Administration: IMPDP TABLE_EXISTS_ACTION = APPEND, REPLACE, [SKIP] and TRUNCATEArvind Toorpuhttp://www.blogger.com/profile/02536712992750057274noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-6392616969060675513.post-44957021275523959162017-12-08T02:58:14.650-08:002017-12-08T02:58:14.650-08:00Thank you for your article. It was helpful in show...Thank you for your article. It was helpful in showing what happens for importing for the different parameters of TABLE_EXISTS_ACTION. :) I saw that for each of the options (Skip, Truncate, Append, Replace), all except REPLACE ignored the metadata.<br /><br />Question: If I do an impdp with CONTENT=METADATA_ONLY, how does that work if I specify also TABLE_EXISTS_ACTION=REPLACE ?<br /><br /> Will all data in the destination DB be dropped? (because no new data is coming in from the import, so the data is "replaced" with emptiness)<br /><br />Context: I am trying to import the metadata of a database into another database. The databases have a similar structure already, but there may be some differences in the table definitions (an extra column, additional constraint, etc). I would like to import the metadata differences, but keep the table rows in the destination DB, if possible. <br /><br />I have had previous experience of trying to import a db, and ran into the issue of it skipping tables (because that was the default behaviour), and none of the new metadata information that I wanted was imported... So I suspected that I need to specify another behaviour for the TABLE_EXISTS_ACTION.Ann Ynoreply@blogger.com