Following is a sample AutoLoader configuration file (on AIX):
############### # release level ############### RELEASE=V6.00 ################## # CLP load command ################## db2 load from /home/user/atld_work/test.dat of del replace into user.test ############### # database name ############### database=wsdb ################# # split partition list ################# SPLIT_NODES=(0,2) ############## # running mode ############## mode=split_and_load ################ # log file token ################ logfile=mylog ###################################### # frequency of progressive information # # print out progressive info every 10 # mega-bytes of data ###################################### STATUS_INTERVAL=10
The following command issued against this configuration file includes the path and the temporary working directory accessible from each of the participating database partitions. The name of the configuration file, sample.atld.cfg, is also specified:
/home/user/atld_work/ $ db2atld -config sample.atld.cfg
Invocation of this command produces the following output:
/home/user/atld_work/ $ db2atld -config sample.atld.cfg Utility program: "db2atld". Version: "06000". Start reading autoloader configuration file: sample.atld.cfg Finish reading autoloader configuration file: sample.atld.cfg Start initializing autoloader process. Finish initializing autoloader process. The Autoloader is now issuing all LOAD requests. The LOAD operation has begun on partition "0". The LOAD operation has begun on partition "1". The LOAD operation has begun on partition "2". The LOAD operation has begun on partition "3". The Autoloader is now issuing all split requests. Start db2split on node "0" in background. Start db2split on node "2" in background. The utility has read "10" megabytes from the source data. The utility has read "20" megabytes from the source data. The utility has read "30" megabytes from the source data. The utility has read "40" megabytes from the source data. The utility has read "50" megabytes from the source data. The utility has read "60" megabytes from the source data. The utility has read "70" megabytes from the source data. The utility has read "80" megabytes from the source data. The utility has read "90" megabytes from the source data. The utility has read "100" megabytes from the source data. The utility has read "110" megabytes from the source data. The utility has read "120" megabytes from the source data. The utility has read "130" megabytes from the source data. The utility has completed reading "130" megabytes from the user data. The Autoloader is waiting for all splitters to complete. The Autoloader is waiting for all LOAD operations to complete. The remote execution of the splitter utility on partition "2" finished with remote execution code "0". The remote execution of the splitter utility on partition "0" finished with remote execution code "0". Operation Node SQL Code Result ___________________________________________________________ LOAD 000 +00000000 Success. ___________________________________________________________ LOAD 001 +00000000 Success. ___________________________________________________________ LOAD 002 +00000000 Success. ___________________________________________________________ LOAD 003 +00000000 Success. ___________________________________________________________ SPLIT 000 +00000000 Success. ___________________________________________________________ SPLIT 002 +00000000 Success. ___________________________________________________________ PSPLIT 000 +00000000 Success. ___________________________________________________________ RESULTS: 4 of 4 LOADs completed successfully. ___________________________________________________________ Rows Read 1310848 Rows Skipped 0 Rows Loaded 1310848 Rows Rejected 0 Rows Deleted 0 Rows Committed 1310848
The main body of the messages generated by the AutoLoader pertain to the initialization of the participating database partitions. Both splitting and loading processes are logged. Termination of the AutoLoader processes is also recorded.
A summary table of operations performed, partitions used, SQL codes returned, and results obtained, is also generated. If an SQL code other than zero is returned, a review of the message file will show the specific warnings or errors that were recorded.
A record summary for the AutoLoader job completes the output.