I came across an interesting foible of the DAC today after opening an SR with Oracle. Apparently using the import function and not selecting Truncate Repository Tables will result in extremely unpredictable results, for instance image suffixes on tables not being imported etc:
The general advice from Oracle seems to be always use the Truncate Repository Tables option, although this means you'll always have to export/import all Applications/SSC which is a pain as the import process is so incredibly slow.
Also, when exporting you will often find an error in the export.log like this:
W_ETL_SA objects: 31
37 INFO Fri Sep 18 19:02:38 CEST 2009 Exporting entity W_ETL_SA for application Universal
38 INFO Fri Sep 18 19:02:38 CEST 2009 Moved W_ETL_SA: 62 objects
39 INFO Fri Sep 18 19:02:38 CEST 2009 Exporting entity W_ETL_SA for application Siebel 8.0 Vertical
40 WARNING Fri Sep 18 19:02:38 CEST 2009 Mismatch between the number of records in the object reference table and objects
According to Oracle these errors can be safely ignored, personally I find them a bit disconcerting as I am worried that some objects are being missed in the import...
selecting truncate tables will also delete all containers in your DAC repository. You would not want to do that if you intend on keeping other containers in the target DAC repository that you do not want to lose.
ReplyDelete