Maximo database configuration, problems occur after you apply configuration changes, break or delete a table field

If an error occurs during database configuration or if the configuration process is interrupted and a field of a table is deleted, the system may have a problem.

Including the database configuration interface cannot query (this can be opened in the management mode, and then discard the application configuration changes, can be restored, but the database configuration should be incomplete)

And adding a field to the prompt table already exists this field, but the property interface does not have this field, and the corresponding table in the database exists this field,

This behavior may be the system is not fully configured during the database application configuration change

Workaround:
In addition to viewing the table fields of the current tables, you should also look at the maxattribute,maxattributecfg tables, add the unfinished configuration, and reference the existing data to add

Example: Add Isforce field for PM table
See if you have configured the full
SELECT * from Maxattribute where attributename= ' Isforce ' and objectname= ' PM ';

SELECT * from maxattributecfg where attributename= ' Isforce ' and objectname= ' PM ';

If there is no corresponding data, perform a data insert operation such as:
INSERT INTO Maxattribute (OBJECTNAME, AttributeName, ALIAS, Autokeyname, Attributeno, Canautonum, CLASSNAME, COLUMNNAME, DefaultValue, Domainid, eauditenabled, EntityName, esigenabled, Isldowner, Ispositive, LENGTH, Maxtype, mustbe, REQUIRED, persistent, Primarykeycolseq, REMARKS, Sameasattribute, Sameasobject, Scale, TITLE, UserDefined, SearchType, mlsupported, Mlinuse, Handlecolumnname, Maxattributeid, RESTRICTED, localizable, Rowstamp, TextDirection, complexexpression)
values (' PM ', ' isforce ', ' isforce ', NULL, 127, 0, NULL, ' Isforce ', ' 0 ', Nu ll, 0, ' PM ', 0, 0, 0, 1, ' Yorn ', 0, 1, 1, NULL, ' whether to force checkpoint ', NULL, NULL, 0, ' Force check ', 1, ' EXACT ', 0, 0, NULL, 60788, 0, 1, 5953 206, NULL, NULL);

Insert into Maxattributecfg (OBJECTNAME, AttributeName, ALIAS, Autokeyname, Attributeno, Canautonum, CLASSNAME, COLUMNNAME, DefaultValue, Domainid, eauditenabled, EntityName, esigenabled, Isldowner, Ispositive, LENGTH, Maxtype, MUSTBE, REQUIRED, persistent, Primarykeycolseq, REMARKS, Sameasattribute, Sameasobject, scale, TITLE, UserDefined, CHANGED, SearchType, mlsupported, Mlinuse, Handlecolumnname, Maxattributeid, RESTRICTED, localizable, Rowstamp, TextDirection, Complexexpression)
VALUES (' PM ', ' isforce ', ' isforce ', NULL, 127, 0, NULL, ' Isforce ', ' 0 ', NULL, 0, ' PM ', 0, 0, 0, 1, ' Yorn ', 0, 1, 1, NULL, ' Whether to force checkpoint ', NULL, NULL, 0, ' Force checkpoint ', 1, ' N ', ' EXACT ', 0, 0, NULL, 60788, 0, 1, 5994057, NULL, NULL);

One of the flag bits is whether the record is newly added or saved, and the above is the direct insert flag bit as a saved record, so the configuration changes are no longer applied in the database configuration interface.
If the data flag bit for the inserted record is added, then the configuration change should also be applied in the database configuration
The flag is in the Maxattributecfg table, which is the changed this field, the new record this field is I, the saved is n

========================
Split line with egg pain
==================
It seems that it is possible to add only maxattributecfg records for this table, then the flag bit is I (new), then apply configuration changes to the database configuration interface.

Note that if you follow such an operation, the flag bit is I, the Maxattribute table should not have corresponding records, and the corresponding table should not have corresponding fields, such as the above PM table in the Isforce is not supposed to exist,
Because this field is added to the PM table when the configuration change is applied, it will be an error to apply the change if it exists before the configuration applies the change

Tai Hang ******************************

Maxattributecfg is the contents of the corresponding database configuration display

Libraries are reading maxattributecfg, adding/modifying Maxattribute, and then adding/modifying fields in a database

As long as the actual field of Maxattributecfg Maxattribute database three can correspond to, OK

The following error is not necessarily the solution, the main thing is to look at the above to see if the configuration is complete, the following is I was looking at the system configuration log, and then the comparison with the previous configuration of the log to key out of the partial configuration execution statement, incredibly successfully solved the problem, really did not think, So it's quite a record, and it's not recommended to start with the following approach.

Application configuration change, because the database log space is full sqlcode=-964 caused the configuration to fail, causing the project to start

INSERT into Maxattribute (objectname, AttributeName, Attributeno, alias, Autokeyname, Canautonum, classname, ColumnName, Complexexpression, DefaultValue, Domainid, eauditenabled, EntityName, esigenabled, Handlecolumnname, Isldowner, ispositive, length, localizable, Maxattributeid, Maxtype, Mlinuse, mlsupported, mustbe, persistent, Primarykeycolseq, remarks, required, restricted, Sameasattribute, sameasobject, scale, SearchType, TextDirection, title , userdefined)
Select objectname, AttributeName, Attributeno, alias, Autokeyname, Canautonum, classname, ColumnName, Complexexpression, DefaultValue, Domainid, eauditenabled, EntityName, esigenabled, Handlecolumnname, Isldowner, ispositive, length, localizable, Maxattributeid, Maxtype, Mlinuse, mlsupported, mustbe, persistent, Primarykeycolseq, Remarks, required, restricted, Sameasattribute, sameasobject, scale, SearchType, TextDirection, title, UserDefined
from Maxattributecfg;

Insert into L_maxattribute (L_maxattributeid, ownerID, Langcode, title, remarks)
Select L_maxattrcfgid, ownerID, Langcode, title, remarks
From L_maxattrcfg;

Update maxattributecfg Set changed = ' n ' where changed! = ' n ';

Of course, after the change, you have to change the value of the Varvalue in the Maxvars, this change can be seen in another essay in the record, this flag is mainly the flag system has a task is executing

Then you will encounter a situation, such as the system is performing certain tasks, such as the configuration of the database, or similar to the development level of some tasks (not limited to this), and then the system was forcibly interrupted, such as the system is forced to stop or power down the whole system crashes, it will cause the system does not change the state bit back, So it will cause the system to restart when prompted what task is not completed AH is in progress ah what else ... At this time to see Maxvars in the value of varvalue, not much to say, specific can see http://www.cnblogs.com/binTke170120/p/6322843.html

Maximo database configuration, problems occur after you apply configuration changes, break or delete a table field