JR45825: THE ISTOOL ODBADMIN PURGEDB -UPTO DOES NOT WORK FOR MORE THAN 25 DAYS.

IBM InfoSphere Information Server, Version 9.1.2

APAR status

• Closed as program error.

Error description

• The istool ODBAdmin purgedb -upto does not work for more than 25
  days.
  
  Here is what in the script output when it is 30 days:
  
  ${ISROOT}/Clients/istools/cli/istool ODBAdmin purgedb -v -dom
  `hostname`:9081   -u dsadm -p xxxxxx -full -engine
  ${VIP_SHORTNAME}
  -upto $PURGE_DAYS -days  \
                 >>  ${LOGPATH}/${LOGFILE}
  
  Purging DSODB Database up to Last 30 days.
  
  VIP IP ADDR= <ipsddress>
  VIP HOSTNAME= <hostname>
  VIP SHORTNAME= rpcra11con1
  --------------------------------------------------
  Operations Database Maintenance Report - Purge
  Generated at:2013-02-15 10:31:32
  Run on server:RPCRA11CON1
  Constraints:
      Limited to data before:2013-03-07 03:34:13
   Restricted to engine:RPCRA11CON1
      Restricted to node:
  
  Please note the date is future date 2013-03-07.  This is not
  correct.
  

Local fix

• NA
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  This problem impacts users od the istool ODBAMDIN purgedb
  command
  ****************************************************************
  PROBLEM DESCRIPTION:
  If a purge period is given by days using a value in excess of 25
  days
  then the purge date is calculated incorrectly. Not
  e the problem only occurs if days is specified.
  ****************************************************************
  RECOMMENDATION:
  If it is required to specify a purge criteria using the number
  of days
  of data to retain then the patch should be applied
  ****************************************************************
  

Problem conclusion

• After the patch has been applied the purge date will be
  calculated correctly in all circumstances as the code has ben
  modified to use the Calendar to do its calculations. This means
  that one of the other issues with the code is circumvented, that
   being, as written the code did not handle differing numbers of
  days in a month or days in a year.
  

Temporary fix

• No temporary fix is available, the only option is to not try and
   purge between 25 and 30 days, If a purge criteria of >25 days
  is required then months should be used.
  

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

• Fixed component name

  WIS DATASTAGE

• Fixed component ID

  5724Q36DS

Applicable component levels

• R850 PSY

     UP