DB2 Transaction Log Errors for large data loads

[Guest_imported]

Hi

My datawarehouse has tables that are loaded with data through the Informatica Tool. The data is about 18 GB for a single set. There are 6 such sets.

All of this data needs to be loaded. we cannot have a load file of less then 1 GB. So we have to load a minimum of 1 GB of data at a time.

The ram is 2 GB and the Tables are database manaed. There has been proper database size estimation done and applied. There are 25 Primary logs and 20 Secondary logs summing it up to 2 GB. The other memory parameters are optimized to help the load.

But during the loading the systems gives error of transaction log full.

H E L P !!!

Regards
samasaya

 

[g046678]

If you are using the load utility, of course it does not log. The import utility can be made to commit after so many records. I am not familiar with informatica, but if this is doing your loading via insert, then you have little recourse but to either use gigantic logs or create the targetr tables with the phrase "not logged initially". With this attribute of the table it is possible within a unit of work to not log your inserts. Basically, everthing is logged as normal until you execute the SQL statement "alter table not logged" or something to that effect. From that point, until the next commit logs are not written. Please see the doc for more in-depth info.

HTH