Invalid Precision Error in parameter

A forum for discussing DataStage<sup>®</sup> basics. If you're not sure where your question goes, start here.

Moderators: chulett, rschirm, roy

Post Reply
mourya33
Participant
Posts: 8
Joined: Fri Mar 20, 2009 3:53 am

Invalid Precision Error in parameter

Post by mourya33 »

We are running a parallel job which loads data from oracle database to oracle database. We have not used any transformations anywhere.The job is aborting with the folowing error.

"APT_CombinedOperatorController(0),2:[Data Direct][ODBC Wire Protocol Driver] Invalid Precision Value. Error in Parameter 9".

We replaced the target ODBC stage with Dynamic RDBMS stage and ran the job. Now, we are receiving the warning for timestamp columns as below
"[DataDirect][ODBC Oracle Wire Protocol driver]Timestamp parameters with a scale, must have a scale less than ten and a precision equal to 20 plus the scale. You specified a precision of 19 and scale of 3. Error in parameter 14."

It shows that the precision is 19 and scale is 3, even though we did not define any scale value in the datastage or in the table definition. We created the table using SQL developer in Oracle database, with the data type as DATE, which translates to timestamp (19).

One more strange issue is that the data for all the columns in the target is truncated, i mean, the last character is truncated no matter what the length of the column is in the database. For example, if we give the value "DUMMY" for a particular column, it is inserted as "DUMM". If we manually fire an insert query using SQL developer in the database, the data is populated correctly. We are not able to get any clues. We have tried using datasets and all the values are loaded correctly. But we have other similar jobs which run perfectly fine without any issues.

Any inputs on getting rid of this problem will be really appreciable.


Regards,
Mourya
Mourya
sayeedahmad
Participant
Posts: 3
Joined: Mon Feb 23, 2009 4:22 am

Re: Invalid Precision Error in parameter

Post by sayeedahmad »

mourya33 wrote:We are running a parallel job which loads data from oracle database to oracle database. We have not used any transformations anywhere.The job is aborting with the folowing error.

"APT_CombinedOperatorController(0),2:[Data Direct][ODBC Wire Protocol Driver] Invalid Precision Value. Error in Parameter 9".

We replaced the target ODBC stage with Dynamic RDBMS stage and ran the job. Now, we are receiving the warning for timestamp columns as below
"[DataDirect][ODBC Oracle Wire Protocol driver]Timestamp parameters with a scale, must have a scale less than ten and a precision equal to 20 plus the scale. You specified a precision of 19 and scale of 3. Error in parameter 14."

It shows that the precision is 19 and scale is 3, even though we did not define any scale value in the datastage or in the table definition. We created the table using SQL developer in Oracle database, with the data type as DATE, which translates to timestamp (19).

One more strange issue is that the data for all the columns in the target is truncated, i mean, the last character is truncated no matter what the length of the column is in the database. For example, if we give the value "DUMMY" for a particular column, it is inserted as "DUMM". If we manually fire an insert query using SQL developer in the database, the data is populated correctly. We are not able to get any clues. We have tried using datasets and all the values are loaded correctly. But we have other similar jobs which run perfectly fine without any issues.

Any inputs on getting rid of this problem will be really appreciable.


Regards,
Mourya
Hi Experts,

I am encountering similar error using Dynamic RDBMS stage on Datastage 8.0.1 on AIX. The error I am getting is "Dynamic_RDBMS_8,0: Warning: Test.Dynamic_RDBMS_8: [DataDirect][ODBC DB2 Wire Protocol driver]Timestamp parameters with a scale, must have a scale less than ten and a precision equal to 20 plus the scale. You specified a precision of 20 and scale of 3. Error in parameter 2."

Changing the scale and precision doesn't affect anything. Keeps showing the same error. I have no idea from where it is picking precision as 20 and scale as 3.

Please help
DS
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Please start your own post in the Enterprise Edition forum. We frown on "hijacking" other people's posts, one should always create a new post unless you are attempting to help with an existing one.

Thanks.
-craig

"You can never have too many knives" -- Logan Nine Fingers
Post Reply