Example with Error Logging - Aster Client

Use the same assumptions as in the previous example, and assume we will log malformed rows (that is, rows that the loader cannot interpret and therefore cannot load) to a table called “2010MarchSales_error_table,” tagging each error row with the label “2010MarchSalesErr”. At the end of the load attempt, the error data will also be copied to the file, /home/ccrisp/2010MarchSales_error.txt. We’ll set a limit of 100 error rows; if more than 100 errors are encountered, the load will be cancelled.

1. Create the custom error logging table: Run ACT as a user with table creation rights (for example, a user with the catalog_admin role) and type:

   CREATE TABLE 2010MarchSales_error_table () INHERITS 	(nc_errortable_part);

2. Exit ACT, return to the command line, and type:

   $  ./ncluster_loader -h  10.50.25.100  –w  beehive  -D  "~"  --el-enabled 
--el-label  2010MarchSalesErr  --el-limit  100  --el-table  
2010MarchSales_error_table  --el-errfile  /home/ccrisp/	2010MarchSales_error.txt sales_fact 2010MarchSales_data.txt

For more information on logging malformed rows, see the Error Logging section.