Error : Not bounded length

swades · Post by **swades** » Mon Feb 05, 2007 6:16 pm

Hi,
I try to read about following error message in this forum but I didnt find.

What this error message implies ?
Any help Please

Error :

APT_CombinedOperatorController(2),1: Fatal Error: Not bounded length.

Thanks

I_Server_Whale · Post by **I_Server_Whale** » Mon Feb 05, 2007 6:37 pm

What is the design and objective of your job? Are there any other surrounding warning messages? Provide more information.

DSguru2B · Post by **DSguru2B** » Mon Feb 05, 2007 7:33 pm

Are you providing the lengths of all the varchar fields?

ray.wurlod · Post by **ray.wurlod** » Mon Feb 05, 2007 8:13 pm

It means that there is at least one field in your job design defined as VarChar but without a Precision (maximum length) value.

While this is legal in some places (for example Data Set stages) it is not legal in others. Whichever operator governed by your particular combined operator controller is complaining about an unbounded string can not be determined without disabling operator combination. But you can just check for VarChar fields without a precision value and provide this value.

I_Server_Whale · Post by **I_Server_Whale** » Mon Feb 05, 2007 8:17 pm

ray.wurlod wrote:It means that there is at least one field in your job design defined as VarChar but without a Precision (maximum length) value.

Didn't know that.

Thanks! Ray.

swades · Post by **swades** » Mon Feb 05, 2007 9:40 pm

Thanks Ray and DSguru2B

I resolve that issue,
I column grid I forget to specify varchar length. that I corrected now working fine.

Thanks

narasimha · Post by **narasimha** » Mon Feb 05, 2007 9:51 pm

Time to mark the post as "Resolved"

swades · Post by **swades** » Mon Feb 05, 2007 9:54 pm

BUT now I am getting following Fatal:

Fatal:

APT_CombinedOperatorController,3: [DataDirect][ODBC lib] Program type out of range

I am writing to DB2 table via ODBC stage using userdefine query.

I set APT_DISABLE_COMBINATION to True but still same Fatal.

Thanks

narasimha · Post by **narasimha** » Mon Feb 05, 2007 10:06 pm

Check here for a similar issue.

swades · Post by **swades** » Mon Feb 05, 2007 10:57 pm

Thanks

I read that forum which says to set APT_DISABLE_COMBINATION to True.
I did that but still I am getting that. Fatal

Thanks

ArndW · Post by **ArndW** » Tue Feb 06, 2007 2:36 am

swades - the APT_DISABLE_COMBINATION switch is used in this case to help locate the stage that is causing your problem. But there is no need to do so, since your original error is telling you that it occurs in the ODBC stage.

Is this the source stage? What are your column definitions? At least one of these is incorrect for DataStage.

kumar_s · Post by **kumar_s** » Tue Feb 06, 2007 3:13 am

Don't you find any other error/warning message along with this?

DSguru2B · Post by **DSguru2B** » Tue Feb 06, 2007 8:02 am

Additional error messages would help. Did you try setting it back to "generated sql"? See if that works, once you get that part working then you can analyze how different is your sql and the generated one. Analyze in regards to any syntax or data type conversion being done.

swades · Post by **swades** » Tue Feb 06, 2007 11:01 am

Hi,
I am using ODBD stage as Target Stage. I am doing Upsert Mode, Update and then Insert.

Update Query:

UPDATE
Table_name
SET
EFF_DT = ORCHESTRATE.EFF_DT,
EXP_DT = ORCHESTRATE.EXP_DT,
C_CD = ORCHESTRATE.C_CD
WHERE
(Table_name.SUB_NM = ORCHESTRATE.SUB_NM)

AND Insert Query :

NSERT INTO Table_name
( SUB_NM, G_SK, EFF_DT,EXP_DT, C_CD, A_SK)

VALUES
(
ORCHESTRATE.SUB_NM,
ORCHESTRATE.G_SK ,
CURRENT DATE,
'9999-12-31',
'C',
ORCHESTRATE.A_SK
)

Please help me to implement this. Insert is working but Update not and I am getting following Fatal :

DataDirect][ODBC lib] Program type out of range

Thanks a lot

DSguru2B · Post by **DSguru2B** » Tue Feb 06, 2007 11:05 am

Is it because your missing an "I" from Insert