Error_When_Opening_dataset
Moderators: chulett, rschirm, roy
Error_When_Opening_dataset
Hi,
I have a job with lookup stage, Iam writing the Failed records to a Dataset file . After running job when I tried to open the dataset or try to use that dataset in other job Iam getting an Error saying
Error when checking operator: Could not find input field "File_TBLEID".
and in the View Data tab Iam getting the error saying
Error executing View Data command:
# # E TOPK 000000 12 : 14: 09(014) <_PEEK_IDENT_> Input dataset does not have field: "File_TBLEID".
Please some body help me why Iam getting this error . I can see that link is having 240656 rows that is going to the Dataset
Thanks,
SomaRaju
I have a job with lookup stage, Iam writing the Failed records to a Dataset file . After running job when I tried to open the dataset or try to use that dataset in other job Iam getting an Error saying
Error when checking operator: Could not find input field "File_TBLEID".
and in the View Data tab Iam getting the error saying
Error executing View Data command:
# # E TOPK 000000 12 : 14: 09(014) <_PEEK_IDENT_> Input dataset does not have field: "File_TBLEID".
Please some body help me why Iam getting this error . I can see that link is having 240656 rows that is going to the Dataset
Thanks,
SomaRaju
somaraju
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Hi Ray ,
This is the schema for that dataset
record
( LISTCH: string[2];
Tgt_RIDDEN: string[1];
Tgt_TABLEID: ustring[max=12];
COUNTRY: string[max=2];
PRICETYPE: ustring[max=3];
Tgt_VALIDFROM: date;
Tgt_CURRENCY: string[max=3];
Tgt_RELEASED: string[1];
Tgt_PRICEUSDCALC: nullable decimal[12,2];
Tgt_PRICE: nullable decimal[12,2];
Tgt_AUDITUSER: string[max=255];
Tgt_PRICEID: nullable int32;
PRUCTID: int32;
)
I can see data from Dataset viewer options on nodes .
I had on node 0 69205 records ,
node1 63503 , node3 57053 and node4 62699 records
Thanks,
SomaRaju
Thanks,
SomaRaju
This is the schema for that dataset
record
( LISTCH: string[2];
Tgt_RIDDEN: string[1];
Tgt_TABLEID: ustring[max=12];
COUNTRY: string[max=2];
PRICETYPE: ustring[max=3];
Tgt_VALIDFROM: date;
Tgt_CURRENCY: string[max=3];
Tgt_RELEASED: string[1];
Tgt_PRICEUSDCALC: nullable decimal[12,2];
Tgt_PRICE: nullable decimal[12,2];
Tgt_AUDITUSER: string[max=255];
Tgt_PRICEID: nullable int32;
PRUCTID: int32;
)
I can see data from Dataset viewer options on nodes .
I had on node 0 69205 records ,
node1 63503 , node3 57053 and node4 62699 records
Thanks,
SomaRaju
Thanks,
SomaRaju
somaraju
Hi Arnd,
I am rejecting the records that fail in lookup to a Dataset . What I found was the record schema is having column names different from what the column names Dataset has in the job . Iam confused how the record schema is having different metadata and not the metadata the Dataset had because it is a reject link. I cannot change the metadata to be same as record schema since it is a reject link it is not letting me to do.
Thanks,
SomaRaju.
I am rejecting the records that fail in lookup to a Dataset . What I found was the record schema is having column names different from what the column names Dataset has in the job . Iam confused how the record schema is having different metadata and not the metadata the Dataset had because it is a reject link. I cannot change the metadata to be same as record schema since it is a reject link it is not letting me to do.
Thanks,
SomaRaju.
somaraju
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact: