SHUBH25

 Profile Answers by SHUBH25 

• Feb 15th, 2008

 

Fload uses 2 error tables

Error table 1: where format of data is not correct.

Error table 2: violations of UPI

Mload also uses 2 error tables (ET and UV), 1 work table and 1 log table

1. ET TABLE - Data error

MultiLoad uses the ET table, also called the Acquisition Phase error table, to store data errors found during the acquisition phase of a MultiLoad import task.

2. UV TABLE - UPI violations

MultiLoad uses the UV table, also called the Application Phase error table, to store data errors found during the application phase of a MultiLoad import or delete task

3. WORK TABLE - WT

Mload loads the selected records in the work table

4. LOG TABLE

A log table maintains record of all checkpoints related to the load job, it is essential/madatory to specify a log table in mload job. This table will be useful in case you have a job abort or restart due to any reason.

Shubhangi

pritampatil

 Profile Answers by pritampatil 

• Aug 12th, 2008

 

Fast load (Fload) requires two error tables that you specify in the Beging Loading Command.

ERROR TABLE 1 - Contains one row for each row which failed to be loaded due to contraint violations or Transalation error.

ERROR TABLE 2 - Captures rows that contains duplicate Values for UPIs.

Multi Load (Mload) have two error tables, that are created for each target table.

ET_Tablename - It logs errors that are occurs during the acquisition phase.

UV_Tablename- It logs errors & exceptions that occurs during the apply phase.

ramanjulu.kakarla

 Profile Answers by ramanjulu.kakarla 

• Oct 8th, 2008

 

Two error tables can be define in multi load job they are: (i) Acquisition error table and (ii) Application Error table.

geetha_mca

 Profile Answers by geetha_mca 

• Dec 30th, 2008

 

In Fload there are 2 error table.
Error table1: Contains one row for each row which failed to be loaded due to
constraint violations or translation errors
Error table2: For non-duplicate rows, captures those rows that cause a UPI
duplicate violation.
Its possible to see the error data.

girishnayak

 Profile Answers by girishnayak 

• Jun 27th, 2009

 

Ideally, there are 2 error tables in Fload. These table contains the details about the data parcel from source to the target table. We can view the data in error table.

It has below details

ErrorCode, ErrorFieldName, and DataParcel

Madhulathamadduri

 Profile Answers by Madhulathamadduri Questions by Madhulathamadduri

• Apr 15th, 2011

 

FASTLOAD:
Error Table 1
Contains one row for each row which failed to be loaded due to constraint violations
or translation errors.

Error Table 2
Captures rows that contain duplicate values for UPIs

anil_k_nayaka

 Profile Answers by anil_k_nayaka 

• Jan 25th, 2012

 

There are 2 types of ERR tables created in both Mload & Fload
they are
ERR1:-
Created due to BAD data/Constraint Violation & this table Contains this type of data
ERR2:
Created due to duplicate data..... when the input contains duplicate records, it load ones a set of data to the target table & the duplicate data to the ERR2 table.


Answer2:-
Yes mload & fload tables can be accessed when this aborts happens.
If there is a lock on this table due to mloa or fload. Below are the procedures to release them.
MLOAD:- RELEASE MLOAD table_name;
FLOAD:- DROP & recreate the table to restart fload.

debashish.munshi

 Profile Answers by debashish.munshi 

• Sep 18th, 2012

 

How many error tables are there in fload and what are their significance/use?

FLOAD needs 2 error tables for its execution. 1 Error table for data issue and another error table for UPI violation

Can we see the data of error tables?

Yes, we can. After the completion of the Fload, it there are values in the error table, then error tables doesnt get dropped automatically, bacause FastLoad wants us to review the errors and manually drop the same. Just select from the table name to check the values.
Well you can Igrnore the Errors as well by expicitly mentioning the same while writing the FLOAD Script.

How many error tables are their in mload and what is there use?

For Multiload Utility, 2 Error tables are required for each target table, if you dont explicitly mention the names Mload will automatically create the same with ET_ and UV_. The job of this error tables are similar to that of FLOAD i.e. ET_ Error table is for data issue and UV_ error table is for UPI violation.

When mload job fails, can we access mload tables? If yes then how?

Once MLOAD Job fails we can access the taget table after Releasing the Mload lock. Mload at Phase 3 (i.e. Acquisition Phase) locks the target table because at Phase 4 (Application Phase) , data is loaded in the Target table from the work table. So if Mload fails at phase 3 or 4, then Mload locks needs to be released.

Command : Release Mload

Umar

• Oct 8th, 2013

 

My question is what if fastload fails, how can we access fastload error table ??? Quick response would be appreciated.

prasadh

• Oct 10th, 2014

 

in fload and multi load we have 2 error tables for a target table, if script run successfully with return code 0 we can see the error tables data(no errors tables will dropped).
tables are locked if script fails we can't see them its under loading....

CHetan

• Jun 8th, 2017

 

There are 2 error tables in Fastload, Error table 1 significance is to capture datawhich do not match the speciied datatype, and Error table 2 is for the Uniqueness constraint.. In case you have UPI defined on table and you try to load another record with same value in UPI column, then the record will move to Error table2. Yes you can query these tables in Fastload. For Mload :
ET: Stores data error at Acquisition pHase
UT: Stores data errors at Applicatin phase.