Hi All, DB2 v5.2 on AIX. Instead of using db2 exit, I am setting up DB2 online backup by db2 backup database xxxx online use adsm dsmc archive the transaction log (with serialization = share dynamic in copygroup) In order to test the serialization=sharedynamic, during online backup I run a script to insert records to a table continuously to make the transaction log keep on changing. Example of dsmc archive log: Normal File--> 4,104,192 /home/db2inst2/db2inst2/NODE0000/SQL00001/SQLOG DIR/S0000072.LOG Changed Retry # 1 Normal File--> 4,104,192 /home/db2inst2/db2inst2/NODE0000/SQL 00001/SQLOGDIR/S0000072.LOG Changed Retry # 2 Normal File--> 4,104,192 /home/db2inst2/db2inst2/NODE0000/SQL 00001/SQLOGDIR/S0000072.LOG Changed Retry # 3 Normal File--> 4,104,192 /home/db2inst2/db2inst2/NODE0000/SQL 00001/SQLOGDIR/S0000072.LOG Changed Retry # 4 Normal File--> 4,104,192 /home/db2inst2/db2inst2/NODE0000/SQL 00001/SQLOGDIR/S0000072.LOG [Sent] I can perform db2 restore and retrieve the transaction log, db2 rollforward successful and everything is OK. Just want to know if there is any risk to archive transaction log by using serialization=share dynamic. Thanks in advance. Regards, Eric Tang
