Wednesday 23 July 2014

Maximo database migration error

Below errors may occur while doing Maximo 7.5 SQL Server migration to DB2 by using maxinst.bat (to import .db2 file). 

Error: The row length of the table exceeded a limit of "32677" bytes.

Generated "db2demo.db2" file from unlvct.bat contains wrong lengths for few columns.

For example: MAXMESSAGES table has more columns which has varchar (2000). But create table script in db2demo.db2 file may contain varchar (4000). It means unlvct.bat file doubled the length of the column.

To resolve the issue open the .db2 file and modify a error table (not always MAXMESSAGES) to decrease the length half (from 4000 to 2000, some cases 2000 to 1000 or 8000 to 4000).

Error: "N.ROWSTAMP" is not valid in the context where it is used.

Generated "db2demo.db2" file from unlvct.bat contains trigger scripts for interface related tables. Just modify .db2 file to remove/comment all scripts related to interface tables triggers.

For example:
  • MXIN_INTER_TRANS_T
  • MXIN_INTER_TRANS_U
  • MXOUT_INTER_TRANST
  • MXOUT_INTER_TRANSU
and also interface table related triggers. For instance, there was an existing interface table for PO called PO_IFACE. There must be a triggers in .db2 file, PO_IFACE_T and PO_IFACE_U. Just remove these trigger scripts in .db2 file.

Hope this article may help. Please correct me, if anything wrong.





No comments:

Maximo SOAPUI error javax.xml.ws.WebServiceException

SOAPUI error while sending payload to below url (in cluster environment) http://localhost:9080/meaweb/services/MXASSET Error : <f...