BMXAA4076E - There was no value found for the system start date. The database load may not have completed successfully. Contact your system administrator to ensure that the database was installed properly.

BMXAA4076E - There was no value found for the system start date. The database load may not have completed successfully. Contact your system administrator to ensure that the database was installed properly.

This error will occur when maxinst.bat or configdb.bat or updatedb.bat file execution completed with errors.  Make sure all are executed successfully without any errors. Thereafter, there will be an entry in dummy_crypto column of dummy_table. Based on this crypto value "System Start Date" will generate by class (MXServer).

PM generating WO but not able to see record in Work Order Tracking application

We can generate a work order from PM application. Some times we can see the message that work order is generated, but not able to find that WO in work order tracking application.

Cause: When PM is created while admin mode is ON, it will create a PM record, but doesn't create a record in PMANCESTOR table. Such PM's doesn't generate work order and also it will not throw any error, just displays a message "PM **** generated work order ****".

Work Around: Identify the PM's which doesn't has entry in PMANCESTOR. Insert a record in PMANCESTOR from backend. Restart the server and generate a work order. It will successfully create a WO.

Solution: Before creating PM, make sure admin mode is OFF.

Maximo: update table without rowstamp

In system properties, you can find property called "mxd.db.updateWithoutRowstamp". If this property is 1, then we can update table without rowstamp.

Usually interface tables doesn't have rowstamp. To update these kind of tables by using mbo customization, set this property to 1.

how to customise rich tooltips / record hovers

Please find the information by clicking below link - IBM site:

https://www.ibm.com/developerworks/community/blogs/e25892f0-20f7-46ff-bbe9-c7c03fb3036f/entry/customizing_rich_tooltips_on_sccd_also_known_as_record_hovers?lang=en

Import classifications in Maximo 7.x

While importing classifications in Maximo 7.1 version, I was facing many problems like class structure is blank and hierarchal problems.

Firstly, my requirement is to load classifications with given hardcoded class structure id rather than auto generated integer number.

Secondly, need to import parent and child hierarchal structure.

1.       Duplicate MXCLASSIFICATION Object Structure and name it as per your requirement, remove the Inbound processing class.

2.       In ‘Restrict Attributes’ menu option, In the Source Object List, select CLASSSTRUCTURE

3.       Uncheck Restrict checkbox and check Override checkbox for below fields:

a.       Classstructureid

b.      Parent

4.     - Select Action > Exclude / Include Fields

5.     In the Source Object List, select CLASSSTRUCTURE

6.     In the Persistant Fields sub-tab, look for HASCHILDREN and UNCHECK the EXCLUDE checkBox. This will include the field in the schema.

Using discardable MBOs

Whenever we are going to get MboSet for traversing purpose, then it is better to make mbo set discardable.
By this, Mboset will not cache the MBOs as it fetches from directly from database. This will minimise the JVM memory usage.

Discardable Mbo Sets used for traversing forward only and not to be edited/saved. Discardable Mbo Sets are always read only.

Sample Code:

MboSetRemote poSet = getMboSet("PO");
poSet.setFlag(MboConstants.DISCARDABLE, true);
......
.........
............
.................
poSet.close();

Disable Maximo 7.x login page autocomplete

Some times clients will ask not to store either user name or password in Maximo login page.

There are two ways to do disable auto complete:

1. By using IE settings. Hopefully every body aware about this. But this is applicable to entire Internet Explorer, irrespective of any login page.

2. Another way is by modifying Maximo login.jsp.

Source: IBM

Link: http://www-01.ibm.com/support/docview.wss?uid=swg21587221 

1. Modify the login.jsp file and add autocomplete="off" to the input lines pointed by the arrow below. Login.jsp is usually located

at <MAXIMO_Root>\applications\maximo\maximouiweb\webmodule\webclient\login\ directory:

Existing login.jsp:


After changes:



2. Save the modified file.
3. Stop the MXServer
4. Rebuild maximo ear (make a backup of the existing maximo ear before rebuilding)
5. Deploy the new maximo ear
6. Start the MXServer
7. Clear the browser cache.

The auto-complete will be disabled. You will have to type in the username/password every time logging in to Maximo.