P
Patrice Perrot
Guest
Hi everyone, Perhaps i missed something on binary Dump/Load (DumpSpecified or Index 0). At the end of the load, you must rebuild your indexes. How many time will it take to do it, it think it will be more than one hour. (The size of this database is ~4 TB WITH a downtime less than one hour.) If you end by a binary load (partial or full table) you must rebuild the indexes of the whole table. On the Dumpspecified, you can specify only the first field of an index (perhaps not enough, a partition could have 16 fields) And if you are using a binary load after a several dumpspecified with the option "build indexes" , you will delete all the index entries you have build before => you must rebuild the indexes of the whole table. I think this is the reason why Pro2 and the "CDC" are ended by capturing the changes and then loading them into the target by some 4gl coding (or something like). IMHO , CDC is the next "level" of Audit option (no licence ? + 10.2B08 ?), it is a little bit more complex to use than CDC but you could do the job with this option. IMHO , Unique keys / without unique keys : - Be careful some Unique keys could change during the life cycle of a record - if you have a table without unique keys but few records (less than 10 for eaxample) for each index entries you can work with multiples records (delete alll records for this entry in the new DB, load of all the record for it from the old Db to the new DB).
Continue reading...
Continue reading...