DB2 Load against Partitioned Tables
Posted: Fri Apr 28, 2006 7:58 am
Hello,
I am so frustrated. How the heck does the DB2 Load work against partioned tables. Here is my deal.
When I load a non-partitioned table and specify non-recoverable --- everything is fine and I can immediatly select, update, insert and delete from table.
When I load a partionted table and specify non-recoverable --- the load succeeds, but the tablespace gets put in backup pending and I cannot update the table. I feel like nonrecoverable is actually only getting sent to one of the partitions. Any ideas. I am so frustrated.
What are the good ways to use this load stage. I want to be able to do a bulk load against partitioned tables, I am fine losing any data that was in the process of being loaded, but I do not want to lose all the records that were in the table before the load has started --- which seems like what I am having happen. I am hitting a DB2/6000 8.2.2 DB.
I am using the enterprise edition DB2 UDB stage and specifying Load-append. Non-Recoverable is set to True.
I am so frustrated. How the heck does the DB2 Load work against partioned tables. Here is my deal.
When I load a non-partitioned table and specify non-recoverable --- everything is fine and I can immediatly select, update, insert and delete from table.
When I load a partionted table and specify non-recoverable --- the load succeeds, but the tablespace gets put in backup pending and I cannot update the table. I feel like nonrecoverable is actually only getting sent to one of the partitions. Any ideas. I am so frustrated.
What are the good ways to use this load stage. I want to be able to do a bulk load against partitioned tables, I am fine losing any data that was in the process of being loaded, but I do not want to lose all the records that were in the table before the load has started --- which seems like what I am having happen. I am hitting a DB2/6000 8.2.2 DB.
I am using the enterprise edition DB2 UDB stage and specifying Load-append. Non-Recoverable is set to True.