The following was reported loading data file in 12.10.FC10 on
linux x86_64 from an external table
data file that was created from unloading a regular table via
external table in same version on sol64.
The defect is unpredictable but can yield errors like below in
the external tables rejectfile:
/work4/statements.fail~9179~FIELD_TOO_LONG~account~
/work4/statements.fail~9181~FIELD_TOO_LONG~account~
The problem can be seen loading from external tables that are
delimited and contain byte/text data types.
An example of schema where the problem was observed:
create database wf in sandbox_et1_data;
create table statements
(
account varchar(25) not null,
statementdate date not null,
client_id smallint not null,
product_cd varchar(25) not null,
ptow_flag char(1),
hold_cd char(1),
loan_assume_date date,
loan_assume_file_nbr integer,
purge_date date,
sor_ref_code varchar(50),
source_file varchar(50),
nbr_of_bytes integer,
format varchar(50),
checksum char(32),
image byte in sandbox_et1_blobsp
) in sandbox_et1_data extent size 3640 next size 256 lock mode
row;
CREATE EXTERNAL TABLE statements1a_ext
SAMEAS statements
USING (
format "delimited",
DATAFILES (
"DISK:/work4/statements.fail"
),
DELIMITER "|",
ESCAPE,
REJECTFILE "statements1a.rej",
MAXERRORS 2
);
Because of the nature of the defect, it is likely possible to
split the datafile into smaller files to
workaround the problem as the defect is dependent on a
particular usage of buffers that are
used to read the external file. |
