We load a big flat file into hash partitioned table. It seems in DS 3.2 parallel load is not working for hash type as “enable partition” option can not be set in table properties.
Can someone advise some ways of performance improvement in this situation. Current bulk rate is 2m records per minute. It is a poor load from flat file into a table. No queries or transformations.
The “Enable partitioning” is disabled because DS doesn’t know how to handle hash partitions. List partitions are easy and range partitions just a little more work. DS doesn’t look at the the Oracle table’s metadata at runtime to figure out what partitions the table has configured. It uses whatever was available when the table was imported.
I’m guessing that DS doesn’t know which partition a row is going go into when the partition method is hash.