IZ79166: OBJECTSERVER INTEGER(4) IS NOT EQUAL TO ORACLE NUMBER(4) - Reporter Schema

APAR status

• Closed as fixed if next.

Error description

• ObjectServer Integer(4) is not equal to Oracle Number(4), so the
  gateway scripts for Oracle need to have NUMBER(16) instead.
  
  The absence of this causes the folowing error:
  
  
  
  ORA-01438: value larger than specified precision allowed for
  this
  column.
  
  ========================================================
  
  Customer observation:
  
  Describing the alerts.status table from OMNIbus database you can
  see
  that all the numbers datatype are set as INTEGER(4). The integer
  datatype have 4 bytes size, meaning that you can insert numbers
  from 0
  to 4,294,967,295.
  
  
  
  Looking at the script oracle.reporter.sql, all the collumns that
  are set
  as INTEGER(4) (meaning 4 bytes) in OMNIbus database are set as
  NUMBER(4)
  in Oracle.
  
  
  
  In an Oracle Database NUMBER(4) is different from INTEGER.
  That`s
  because the syntax to declare a column as NUMBER is
  NUMBER(precision,scale).The precision is the number of algarisms
  and the
  scale is the number of algarisms after the dot ".". When you
  declare
  NUMBER(4) means that is a number with precision 4 and scale 0,
  so this
  number can go from 0 to 9999.
  
  =============================================================
  

Local fix

• Change all NUMBER(4) occurrences in the script or db schema to
  NUMBER(16).
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of nco_g_reporter_scripts.
  ****************************************************************
  PROBLEM DESCRIPTION:
  Field size mismatch for Oracle scripts in reporter script.
  ****************************************************************
  RECOMMENDATION:
  Customer provide a feedback that the workaround solution which
  is implemented in the test fix solved the problem. Fixed in
  nco_g_reporter_scripts 3.4 .
  ****************************************************************
  

Problem conclusion

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

• R100 PSY

     UP