A fix is available
APAR status
Closed as program error.
Error description
Oracle NUMBER type is imported as Double of precision 53 by ODBC plugin and this becomes Decimal(38,10) instead of Double when loaded to ODBC Enterprise stage
Local fix
Problem summary
**************************************************************** USERS AFFECTED: ODBC Enterprise stage **************************************************************** PROBLEM DESCRIPTION: In earlier DataStage releases, a function was added to make the following adjustments when loading imported metadata to the Oracle Enterprise stage Double -> Decimal(38, 10) Decimal(38,0) -> Decimal(38, 10) Decimal(10,0) -> BigInt Decimal(x,0) -> Integer, x<10 However, the function affected other parallel stages by mistake. **************************************************************** RECOMMENDATION: Apply patch JR38332 ****************************************************************
Problem conclusion
Modified the client to restrict metadata adjustments to the Oracle Enterprise stage only, and show warning messages to allow the user to decide if the adjustments should be made.
Temporary fix
Comments
APAR Information
APAR number
JR38332
Reported component name
WIS DATASTAGE
Reported component ID
5724Q36DS
Reported release
810
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-11-24
Closed date
2011-09-23
Last modified date
2011-09-23
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WIS DATASTAGE
Fixed component ID
5724Q36DS
Applicable component levels
R810 PSY
UP
R850 PSY
UP
[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSVSEF","label":"InfoSphere DataStage"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.1"}]
Document Information
Modified date:
06 October 2021