We are running data propagator on AIX 4.3.3 with UDB V7.2 fxpck8.
We are having a strange problem when running the apply program (pull configuration). We are pulling data from MVS.
Basically, the apply program starts successfully the first time in full refresh mode. All subscription sets complete successfully the first time in full refresh mode, then it starts a second time.
After a while, I can see that the apply hangs.
I have no error in the applytrail table, no error in the APPLYQUAL.TRC log file nor in APPLYQUAL.APP file.
The spill file xxxxxx.000 is not removed........
Here is the applytrail table :
--> db2 "select set_name, status, lastrun from asn.ibmsnap_applytrail order by lastrun"
1) Check the directory where your apply program is running ... Are there any temp files .... I think they have extensions .001,.002 etc .. These are the files apply uses to build the insert statements for the target
2) Set the MAX_SYNCH_MINUTES in asn.ibmsnap_subs_set to a small value ...
3) Will it be possible to put a trace on in your apply program ?
Visit the new-look IDUG Website , register to gain access to the excellent content.
Thanks a lot for your answer.
There is only one spill file in the directory I launch the apply in. File name is APPLYQUAL.000 .
I changed the value of field MAX_SYNCH_MINUTES in table ASN.IBMSNAP_SUBS_SET to 5 (it previously was null), but it doesn't change anything.
I have plenty of space left on my disk, so it is not a space problem.
I just started the apply process again, and this time it did hang before completion of first subscription set. And again no error message in the log/trail table, the spill file remains blocked and nothing happens.
How can I put a trace ? The syntax I use is the following :
asnapply <APPLYQUAL> <db name> trcflow trcfile&