Pages

Monday, February 13, 2012

mos#loaderror after dbconfig or on restart

Such cases arises if the MOS are not properly loaded after the dbconfig.
If u can see log of time of dbconfig and if u find any error like mos#loaderror. 

This error occurs when any persistent attributes is excluded from the integration object or a non-persistent attribute is included in the integration object and during the dbconfig these attributes are removed but the reference of these attributes in maxintobjcols is not removed.
In such cases if u are lucky integration wont work only for that interface,  some times whole integration may not work. 

To remove such error check the attribute for which it is giving such errors and remove them from maxintobjcols table. The biggest funny thing is that at one time u can see only one attribute at a time. If there are many such attributes then it may require many restarts of the server.


No comments:

Post a Comment