IJ28481: ISSUES CHANGING DATABASE FROM DB2 TO ORACLE

APAR status

• Closed as program error.

Error description

• Customer followed instructions on how to import objects from
  DB2 to Oracle using the link below:
  
  https://www.ibm.com/support
  /knowledgecenter/SSGSPN_9.4.0/com.ibm.tivoli.itws.doc_9.4/distr/
  src_ad/awsadpardatamigrfromdb2.htm
  
  However, at the end they
  are receiving errors when trying to import pool objects. This
  was resolved by following the instructions on the link below,
  which is not present in the 9.4 documentation:
  
  https://www.ibm.
  com/support/knowledgecenter/SSRULV_9.5.0/com.ibm.tivoli.itws.doc
  _9.5/distr/src_tr/awstrswitchdb.htm
  
  The migration to Oracle DB
  was successful. However, upon running JnextPlan, the customer
  gets the error below:
  
  AWSJCS011E An internal error has
  occurred. The error is the following:
  "java.lang.NullPointerException"..
  
  Upon further investigation
  by L2.5 it seems that the preproduction plan was not migrated
  to the Oracle database. The documentation further proves the poi
  nt:
  
  https://www.ibm.com/support/knowledgecenter/SSGSPN_9.4.0/co
  m.ibm.tivoli.itws.doc_9.4/distr/src_ad/awsaddatamigration.htm
  
  
  
  Neither of these procedures migrate the following information
  from the source database:
  
   The preproduction plan
   The history
  of job runs and job statistics
   The state of running event rule
  instances. This means that any complex event rules, where part
  of the rule has been satisfied prior to the database migration,
  are generated after the migration as new rules. Even if the
  subsequent conditions of the event rule are satisfied, the
  record that the first part of the rule was satisfied is no
  longer available, so the rule will never be completely
  satisfied.
  
  In our documentation for "Reconfiguration from DB2
  to Oracle", we see this step:
  
  "...
  13.) Update the Symphony
  file by creating a plan with 0
  extension period that begins at
  the end of the current plan:
  
  JnextPlan -from start_time -for
  0000
  
  where start_time is
  the date and time when the current
  plan ends.
  ..."
  
  The problem is that the Symphony file exits,
  but the preproduction plan does not exist yet. The MakePlan
  step has the following logic:
  
  if [ $SYM_FOUND = 0 ]
  then
   set
  +e
   `maestro`/bin/planman -timeout $TIMEOUT crt $*
  ....
  
  if [
  $SYM_FOUND = 1 ]
  then
   set +e
   `maestro`/bin/planman -timeout
  $TIMEOUT ext $*
  ...
  
  This means that if the Symphony file is
  found that the command 'planman ... ext $*' will be called. The
  "ext" action isn't valid if the preproduction plan does not
  exist.
  
  The workaround using 'planman -crttrial...' creates the
  preproduction plan.
  

Local fix

• L3 created a tentative fix called CPPlanner.jar to fix the
  issue of java.lang.NullPointerException error when running
  JnextPlan after migrating to Oracle DB. Was applied and tested
  successfully by Matt Dufner.
  

Problem summary

• See apar description
  

Problem conclusion

• This apar will be fixed into 9.4 Fp7 nd
  9.5 fp3
  

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

• Fixed component name

  TIV WKLD SCHDL

• Fixed component ID

  5698WKB94

Applicable component levels

• R9A4 PSY

     UP