Need help for "Fatal Error: Not a v1.1 type: decimal[20

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
vjd
Participant
Posts: 4
Joined: Tue Jan 09, 2007 1:07 pm

Need help for "Fatal Error: Not a v1.1 type: decimal[20

Post by vjd »

When we include decimal and timestamp data types in any paralle job, we are getting the following fatal error.
"Fatal Error: Not a v1.1 type: decimal[20,5]"

This is a new datastage 8.x installation.

Thanks
V
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Welcome aboard. :D

There is not enough information in what you've posted. Please post the entire (detail) error message. In particular, we need to have some idea which stage type generated it. We then may have questions about the syntax you used within that stage.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
vjd
Participant
Posts: 4
Joined: Tue Jan 09, 2007 1:07 pm

More details

Post by vjd »

This is a simple parallel job that reads a flat file and copies it to another flat file with a transformer in the middle. There is no transformation logic in the transformer stage. The input and output files have two decimal fields of types decimal(20,5).
In the datastage logs, we are not seeing any detailed messages except for the following message and message id IIS-DSEE-TFCM-00079.

"main_program: Fatal Error: Not a v1.1 type: decimal[20,5]"

Thanks again
V
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Well, there's some information there. The error code ought to make it possible to find some information in the Parallel Engine Message Reference manual.
IIS = IBM Information Server
DSEE = DataStage Enterprise Edition
TFCM = class manager (I think)

... And that's where it all falls down. There are no TFCM messages in the manual.

I think it's time to contact your "official" support provider.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
vjd
Participant
Posts: 4
Joined: Tue Jan 09, 2007 1:07 pm

Post by vjd »

Ray,
Thank you for the reply. But I am not finding any TFCM messages at all in "Parallel Engine Message Reference".
- V
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Read my post again. That's exactly what I found, which is why I suggested you contact your "official" support provider.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
nick.bond
Charter Member
Charter Member
Posts: 230
Joined: Thu Jan 15, 2004 12:00 pm
Location: London

Post by nick.bond »

If you change the metadata to (38,10) does it work?
Regards,

Nick.
lfong
Premium Member
Premium Member
Posts: 42
Joined: Fri Sep 09, 2005 7:48 am

Post by lfong »

set the APT_AUTO_TRANSPORT_BLOCK_SIZE to false in the administrator .
vjd
Participant
Posts: 4
Joined: Tue Jan 09, 2007 1:07 pm

Post by vjd »

setting the APT_AUTO_TRANSPORT_BLOCK_SIZE to false solved the problem. Thanks, V
vjd
Datastage Consultant
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Time to mark this thread as Resolved, then.

Why was APT_AUTO_TRANSPORT_BLOCK_SIZE ever set to anything but False?
Transport blocks are only relevant for transmitting fixed-length records.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Post Reply