metadata mismatch

Post questions here relative to DataStage Server Edition for such areas as Server job design, DS Basic, Routines, Job Sequences, etc.

Moderators: chulett, rschirm, roy

Post Reply
radarada
Participant
Posts: 17
Joined: Wed Jul 16, 2008 7:42 am

metadata mismatch

Post by radarada »

The source metadata was imported through the orchestrate schema. The field in the table is defined as a CHAR(1) however when the job runs the Oracle stage throws out the below error.

Implicit conversion from source type "string[max=32]" to result type "string[1]"

This field does not exists as anything but CHAR in the environment we are pulling from. Where does DS get this info as several other fields also had the same issue in that the string was higher in DS then on the database.
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

CHAR is the same as Char(1) is the same as string[1]
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
radarada
Participant
Posts: 17
Joined: Wed Jul 16, 2008 7:42 am

Post by radarada »

right but the error is telling me that DS is reading that the source has a string 32 and i am trying to put it into a string 1. The source has a char(1) and my job has a char(1). Where is it getting the string 32?
Post Reply