Troubleshooting
Problem
After upgrading a Maximo 6.2 database to 7.1, several columns on table COMMLOG do not match the way that the columns are defined in Maximo.
Symptom
In Integrity Checker report:
BMXAA0443E -- ERROR -- BMXAA0494E -- The Maximo definition of this column does not match the actual column:
BMXAA6841I - COMMLOG.BCC, Maximo definition is CLOB, Database column is VARCHAR2(4000)
BMXAA0443E -- ERROR -- BMXAA0494E -- The Maximo definition of this column does not match the actual column:
BMXAA6841I - COMMLOG.CC, Maximo definition is CLOB, Database column is VARCHAR2(4000)
BMXAA0443E -- ERROR -- BMXAA0494E -- The Maximo definition of this column does not match the actual column:
BMXAA6841I - COMMLOG.SENDTO, Maximo definition is CLOB, Database column is VARCHAR2(4000)
Cause
.
Environment
The problem is known to occur on Oracle. It may occur on other database platforms as well. SQL statements in this technote are specific to Oracle. Similar can be created for SQL Server or DB2.
Diagnosing The Problem
In Maximo 7.1, columns COMMLOG.BCC, COMMLOG.CC, and COMMLOG.SENDTO should be data type CLOB. This query will display the datatype(s) of the columns:
Select table_name, column_name, data_type, data_length From user_tab_columns Where table_name='COMMLOG' And column_name In ('BCC', 'CC', 'SENDTO') ;
Resolving The Problem
1. For each column, add to table COMMLOG a new column with data type CLOB. For example:
Alter Table commlog Add bccnew CLOB;
2. Copy the original column to the new column. For example:
Update commlog Set bccnew = bcc ;
3. Drop the original column. For example:
Alter Table commlog Drop Column bcc ;
4. Rename the new column to the original name. For example:
Alter Table commlog Rename Column bccnew To bcc ;
5. Run Integrity Checker again to verify that the errors are no longer reported.
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21648165