IZ23430: UPGRADE ERROR 6.5.1 - JAVA.SQL.SQLEXCEPTION: ORA-00904: "N": INVALID IDENTIFIER

APAR status

• Closed as program error.

Error description

• Upgrading from Maximo 5.2 P5
  MAXIMO application Server 6.2.1 Build 156 DB Build V600-530,
  Upgrade 6.5.01 Build 207 DB build V600-0
  
  Receiving the the following error:
  
  Sat May 24 18:35:38 EDT 2008
  Update maxvars Set varvalue = 'UpgradeLoadMetaData08' Where
  varname = 'LASTUPGCALLOUT'
  ;
  commit
  ;
  Upgrade calling DropBackup. Sat May 24 18:35:38 EDT 2008
  Upgrade calling ConfigDB. Sat May 24 18:35:41 EDT 2008
  rollback
  ;
  java.sql.SQLException: ORA-00904: "N": invalid identifier
  
   at
  oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError
  .java:112)
   at
  oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331)
   at
  oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:288)
   at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:743)
   at
  oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:207)
   at
  oracle.jdbc.driver.T4CStatement.executeForRows(T4CStatement.java
  :946)
   at
  oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleSt
  atement.java:1168)
   at
  oracle.jdbc.driver.OracleStatement.executeInternal(OracleStateme
  nt.java:1687)
   at
  oracle.jdbc.driver.OracleStatement.execute(OracleStatement.java:
  1653)
  
  Email communications:
  
  Thanks Karen!
  
  Siva, can you create an APAR?  Please include this email trail.
  
  Steve
  -----
  Maxattributecfg for masterpm.applympmtoasset is added with
  maxtype YORN and defaultvalue '1'.  Later in the log the
  defaultvalue is updated to 'N'.  This new defaultvalue is wrong.
  The log indicates that the 'N' defaultvalue is assigned by
  callout UpgradeLoadMetaData04.
  
  Karen
  -----
  Hi Siva,
  
  It looks like configure is throwing the error because of the
  following:
  update masterpm set applympmtoasset = N where applympmtoasset is
  null
  ;
  
  My guess is that the default value in MaxAttribute for
  applypmtoasset is N when it should be 0.   I am not sure if this
  is a bug in the upgrade or not.  In the meantime, I think that
  if the client sets this to 0, then they should be ok.  I am not
  sure if this is an Upgrade bug because I would have thought
  people would have ran into this before.
  
  Max/Karen, any other thoughts/opinions?
  
  Steve
  

Local fix

• No workaround
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: useres of the upgrade                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: see summary                             *
  *                                                              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  *                                                              *
  *                                                              *
  *                                                              *
  ****************************************************************
  tried to populate new-style numeric 6.0 YORN column with
  old-style alpha 5.2 YORN values (Y/N)
  

Problem conclusion

• need to convert old-style YORN values to new-style YORN values
  

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:

Modules/Macros

• MAXIMO
  

Fix information

• Fixed component name

  UPGRADE PROGRAM

• Fixed component ID

  5724R46UP

Applicable component levels

• R415 PSY

     UP