Page 1 of 1

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

Posted: Sat Apr 21, 2007 3:34 pm
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

Posted: Sat Apr 21, 2007 3:44 pm
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.

More details

Posted: Sat Apr 21, 2007 4:28 pm
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

Posted: Sat Apr 21, 2007 5:57 pm
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.

Posted: Sat Apr 21, 2007 6:32 pm
by vjd
Ray,
Thank you for the reply. But I am not finding any TFCM messages at all in "Parallel Engine Message Reference".
- V

Posted: Sun Apr 22, 2007 1:31 am
by ray.wurlod
Read my post again. That's exactly what I found, which is why I suggested you contact your "official" support provider.

Posted: Sun Apr 22, 2007 7:52 pm
by nick.bond
If you change the metadata to (38,10) does it work?

Posted: Wed May 16, 2007 5:53 am
by lfong
set the APT_AUTO_TRANSPORT_BLOCK_SIZE to false in the administrator .

Posted: Thu May 17, 2007 6:35 am
by vjd
setting the APT_AUTO_TRANSPORT_BLOCK_SIZE to false solved the problem. Thanks, V

Posted: Thu May 17, 2007 5:30 pm
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.