Sometimes we get dsnu255i running dsnutilb in a load log no resume yes of a partitionned tablespace. Load data log no replace nocopypend enforce constraints discards 1 inddn sysrec00 into table dbcreatortablename table definition but i am not sure what each and every parameters are used to and how exactly the load function is happening in database.
Working With Timesten Scaleout
Load data log yes resume yes. Load data continueif7272x resume yes into dsn8a10tdsptxt dspindex position 2 char2 lineno position 6 char2 dspline position 80 char79 if you want to replace just one table in a multiple table table space delete all rows in the table and then use load with resume yes. The ibm load utility will insert the new keys into existing indexes with resume yes leaving the indexes in need of reorganization when complete. Space occupied by rows marked as deleted or by rows of dropped tables is. The default is no unless you override it with part integer resume yes. Load with resume enforce yes or no and log yes or no. The tablespace will put in copy pending status when you load the table with option log no.
When i monitored the utility that i used to load it showed me two phases 1. Log records that db2 creates during load resume yes shrlevel change can be used by db2 datapropagator if the tables that are being loaded are defined with data capture changes. Dsnu050i dsnugutc load data inddn sysrec log no resume yes. For a load resume log yes action the db2 log contains a log record for each page of rows that are added to the table. Dsnu650i dsnugutc into table dsn8810emp. Load data resume yes log no nocopypend inddn sysrec00 into table tablename here the orginal data is deleted and new records are just inserted.
For example le last one was during the sort build phase of loading in paralell 78 records in a ts having 10 part only one index. Yes loads records into a non empty table space. When you want to specify replace option all the records or rows in the table are deleted before loading and resume option will retain the old records or rows in the table. If the table space is empty a warning message is issued but the table space is loaded. Dsnu650i dsnugutc when0000100002 x0001 dsnu650i dsnugutc empno. Load jobs with the shrlevel change option do not insert any records into sysibmsyscopy.
Dsnu000i dsnugutc output start for utility utilid xdbutilb. Loading begins at the current end of data in the table space. The message mentionned it was expected 83 record but only 78 were found. The log record for at least one page might contain both rows that were loaded in the load resume action and rows that existed in the table before the load resume action if the pre existing rows were on the same page as the rows that were loaded. And you will have to sort the data before the load to ensure the rows loaded into the tablespace are in clustering sequence to avoid the need for tablespace reorganization afterward. The load job produces the following sysout.
Gallery of Load Data Log Yes Resume Yes
/Loglikelihood+LL+Function+Sum.png)
