Troubleshooting
Problem
When you apply Maximo fixpack 7.5.0.8 or a 7.5.0.8 IFix, upgrading the database can fail in script V7520_179.
Symptom
Error message, as found at the end of the UpdateDB log:
BMXAA7025E -- Script failed while running.;
sql#0;
An error occurred while converting the varchar value to JDBC data type INTEGER.
Cause
UpdateDB script V7520_179 identifies column CONTENTUID as the unique identifier (UID) for tables SKDLABORHRS and SKDLABORHRSTEMP. This is incorrect; CONTENTUID should not be the unique identifier for these tables. Unique Identifier columns must be datatype BIGINT; CONTENTUID columns are ALN (alphanumeric). UpdateDB attempts to convert the columns to BIGINT. If the columns contain anything other than numeric data, the conversion fails and UpdateDB fails.
This has been identified as a product defect under APAR IV72828.
Environment
TPAE 7.5.0.8. Any package that includes TPAE 7.5.0.8.
Diagnosing The Problem
The results of this SQL query will show that columns SKDLABORHRS.CONTENUID and SKDLABORHRSTEMP.CONTENTUID are ALN (alphanumeric) columns. UpdateDB attempts to convert the columns to BIGINT. If the columns contain any non-numeric data, the conversion, the script, and UpdateDB fail.
Select objectname, attributename, maxtype From maxattribute Where objectname In ('SKDLABORHRS', 'SKDLABORHRSTEMP') And attributename='CONTENTUID'
Resolving The Problem
This issue has two possible solutions. Solution #1 corrects the flaw and continues the upgrade; solution #2 is a more complete solution running the full upgrade from start to finish.
Solution 1:
// Undo the changes applied by script V7520_179 prior to the failure:
- Update maxtable Set uniquecolumnname=null Where tablename='SKDLABORHRS'
- Update maxtablecfg Set uniquecolumnname=null Where tablename='SKDLABORHRS'
// Indicate that V7520_179 completed:
- Delete From maxvars Where varname in ('BMXLASTSTATEMENT','BMXLGFFLINE')
- Delete From maxvartype Where varname in ('BMXLASTSTATEMENT','BMXLGFFLINE')
- Update maxvars Set varvalue = 'V7520-179' Where varname = 'SKDUPG'
// Restart Update. The upgrade should now run to completion.
Solution #2:
- Restore the database to pre-upgrade
- Delete the contents of file ...\SMP\maximo\tools\maximo\en\scheduler\V7520_179.dbc, and save as an empty file (0 KB).
- Run UpdateDB again from the beginning. Because V7520_179.dbc is empty, UpdateDB will skip the script and continue on.
This has been identified as a product defect under APAR IV72828.
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21965658