online log on build HDR and after

Dear Sir: when I start to restore db to the secondary db , the user do the following job: 1.rename table A to table B 2.create table A 3.build index on table A 4.insert data to table A .... about 10 tables will do the same thing ! on my 7.31UD8 online.log ( both primary & secondary db ) all will show the same message below 1:09:19 Logical Log 202410 Complete. 11:09:22 DR: Sending log 202411 (current), size 2048 pages, 1.07percent used 11:09:23 DR: Sending Logical Logs Completed 11:09:24 DR: Primary server operational 11:09:25 DR: Sending index rtd:"informix".rtd_photo_con#rtd_photo11_16521 : Started 11:09:28 Checkpoint Completed: duration was 3 seconds. 11:09:28 Checkpoint loguniq 202411, logpos 0x18018 11:09:28 DR: Sending index rtd:"informix".rtd_photo_con#rtd_photo11_16521 : Completed. 11:09:28 DR: Sending index rtd:"informix".rtd_photo_con#rtd_photo12_24174 : Started 11:09:28 DR: Sending index rtd:"informix".rtd_photo_con#rtd_photo12_24174 : Completed. 11:09:28 DR: Sending index rtd:"informix".rtd_photo_con#rtd_photo13_10213 : Started 11:09:28 DR: Sending index rtd:"informix".rtd_photo_con#rtd_photo13_10213 : Completed. then , the AP user say this rename /create table job will fail after the HDR is ok ! Is there anyone has any experience about this message ? thanks for your help ! Jack

jack wrote: > Dear Sir: > when I start to restore db to the secondary db , the user do the > following job: > 1.rename table A to table B > 2.create table A > 3.build index on table A > 4.insert data to table A Currently with HDR when an index is created on the source, that index is copied to the secondary. That means that the lock to the table is transfered from the user thread which created the index to the thread which performs the transfer. Then when the transfer is completed, the lock is released. You can do the following to avoid the impact of the index transfer.... 1) Create table A 2) Create index on table A 3) Lock table A 4) Unlock table A 5) insert data into table A M.P. > .... > about 10 tables will do the same thing ! > on my 7.31UD8 online.log ( both primary & secondary db ) > all will show the same message below > > 1:09:19 Logical Log 202410 Complete. > 11:09:22 DR: Sending log 202411 (current), size 2048 pages, 1.07> percent used > 11:09:23 DR: Sending Logical Logs Completed > 11:09:24 DR: Primary server operational > 11:09:25 DR: Sending index > rtd:"informix".rtd_photo_con#rtd_photo11_16521 : Started > 11:09:28 Checkpoint Completed: duration was 3 seconds. > 11:09:28 Checkpoint loguniq 202411, logpos 0x18018 > > 11:09:28 DR: Sending index > rtd:"informix".rtd_photo_con#rtd_photo11_16521 : Completed. > 11:09:28 DR: Sending index > rtd:"informix".rtd_photo_con#rtd_photo12_24174 : Started > 11:09:28 DR: Sending index > rtd:"informix".rtd_photo_con#rtd_photo12_24174 : Completed. > 11:09:28 DR: Sending index > rtd:"informix".rtd_photo_con#rtd_photo13_10213 : Started > 11:09:28 DR: Sending index > rtd:"informix".rtd_photo_con#rtd_photo13_10213 : Completed.> > > then , the AP user say this rename /create table job will fail after > the HDR is ok ! > Is there anyone has any experience about this message ? > thanks for your help ! > Jack >