janemcs123
Active Member
Hi All,
I was wondering if anyone could help me. I have written a custom UBE to export large volumes of data to custom Z files to then be loaded into an external system. The UBE extracts records from F0101, F0006 and F4801 in turn, so very large volumes involved.
For each record the UBE checks whether the record exists in the custom Z file and if it doesn't it inserts it. Very simple stuff!
Obviously though, this involves a hell of a lot of table I/O and I have had lots of performance issues with it. Run locally, it was terminating unexpectedly, and i would have to run it 3 or 4 times before it would completely load all 3 tables. On the server, it would load all three tables, but then wouldn't complete and would have to be terminated.
I've since modified the program to use buffered inserts. This made a huge difference locally, and the report loaded all 3 tables in around 25 minutes - much faster than previously with no errors or problems.
Great! I thought, but when I ran it on the server this morning, it still loaded all the tables (a little faster), but failed to complete again and had to be terminated.
Has anyone got any ideas as to why this might be happening, or what I can do to prevent it. Incidentally, this only happens on the initial load, whith huge volumes of inserts involved. All subsequent runs, where only NEW data is loaded, everything is fine.
Thanks in advance (and sorry it's so long)
I was wondering if anyone could help me. I have written a custom UBE to export large volumes of data to custom Z files to then be loaded into an external system. The UBE extracts records from F0101, F0006 and F4801 in turn, so very large volumes involved.
For each record the UBE checks whether the record exists in the custom Z file and if it doesn't it inserts it. Very simple stuff!
Obviously though, this involves a hell of a lot of table I/O and I have had lots of performance issues with it. Run locally, it was terminating unexpectedly, and i would have to run it 3 or 4 times before it would completely load all 3 tables. On the server, it would load all three tables, but then wouldn't complete and would have to be terminated.
I've since modified the program to use buffered inserts. This made a huge difference locally, and the report loaded all 3 tables in around 25 minutes - much faster than previously with no errors or problems.
Great! I thought, but when I ran it on the server this morning, it still loaded all the tables (a little faster), but failed to complete again and had to be terminated.
Has anyone got any ideas as to why this might be happening, or what I can do to prevent it. Incidentally, this only happens on the initial load, whith huge volumes of inserts involved. All subsequent runs, where only NEW data is loaded, everything is fine.
Thanks in advance (and sorry it's so long)