main_program: Fatal Error: Not a v1.1 type: decimal[10,0]

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
dspradeep
Participant
Posts: 59
Joined: Fri Aug 21, 2009 12:58 am

main_program: Fatal Error: Not a v1.1 type: decimal[10,0]

Post by dspradeep »

I am getting this error while running my job.

My Job Design is

ESS-->xml-->trans--> Oraclestage

Oracle stage field info
id --> Number(8)
name--> varchar(50)

while import this table it's coming like

id --> decimal(38,10)
name-->varchar(50)

Note : I did not change the metadata and this job is designed last week and upto yesterday it's working fine but today i am getting this error

Code: Select all

main_program: Fatal Error: Not a v1.1 type: decimal[10,0]
i don't know why i am getting this error. I have tried with yesterday file also but i am getting same error. After that i have changed decimal datatype into integer but again i am getting same error.

pls help me
venky
Participant
Posts: 18
Joined: Thu Apr 29, 2004 1:10 pm

Post by venky »

change APT_AUTO_TRANSPORT_BLOCK_SIZE to false and try to run the job
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Re: main_program: Fatal Error: Not a v1.1 type: decimal[10,0

Post by chulett »

dspradeep wrote:Note : I did not change the metadata and this job is designed last week and upto yesterday it's working fine but today i am getting this error
What changed between then and now? The job? The Oracle table? Something obviously did, the problem is going to be figuring out what. I would suspect the latter.
-craig

"You can never have too many knives" -- Logan Nine Fingers
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

venky wrote:change APT_AUTO_TRANSPORT_BLOCK_SIZE to false and try to run the job
Why do you give this advice? Transport blocks only apply to fixed-width records, and is given in bytes. In most cases it's calculated using a formula that involves APT_MIN_TRANSPORT_BLOCK_SIZE, APT_MAX_TRANSPORT_BLOCK_SIZE as well as record size and latency.
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