Try testing with bigger volume of data atleast 100,000 rows to see if
there is a problem. Bulk load is something you should do for highvolume
of data. And it needs a X lock on the table.
> Hi,
>
[quoted text clipped - 8 lines]
> Thanks,
> Sumanth
Sumanth - 13 Jul 2006 18:40 GMT
I was trying this as a test. Have been using bulk load to load large
volumes. Taking more than 10 seconds to upload a single row
only on this particular instance indicates to me something is amiss, the
very same operation takes less than a second on other instances.
Any pointers on what parameters I need to look into ?
Thanks,
Sumnath
> Try testing with bigger volume of data atleast 100,000 rows to see if
> there is a problem. Bulk load is something you should do for highvolume
[quoted text clipped - 12 lines]
>> Thanks,
>> Sumanth
Visu - 13 Jul 2006 19:03 GMT
What are using to load ? Informatica?
> I was trying this as a test. Have been using bulk load to load large
> volumes. Taking more than 10 seconds to upload a single row
[quoted text clipped - 21 lines]
> >> Thanks,
> >> Sumanth
Sumanth - 13 Jul 2006 20:34 GMT
sas to db2.
Thanks,
Sumanth
> What are using to load ? Informatica?
>
[quoted text clipped - 25 lines]
>> >> Thanks,
>> >> Sumanth
Ian - 14 Jul 2006 11:34 GMT
> Try testing with bigger volume of data atleast 100,000 rows to see if
> there is a problem. Bulk load is something you should do for highvolume
> of data. And it needs a X lock on the table.
Visu is correct.
The amount of time required to initiate a load will also depend on
whether you are in a partitioned (DPF) environment -- if so, there is
additional overhead involved in setting up the communications and
processes at all partitions involved in the load. For a large
partitioned environment, the setup can be significant (esp. if you
are comparing to a non-partitioned database).