Maximo Error Fetch
Contents |
Classification update TPAELOCATIONS; SCCD; BMXAA6713E Technote (troubleshooting) Problem(Abstract) Adding an attribute to bmxaa6713e - the mbo fetch operation failed in the mboset with the sql error code 1000 the Maximo Classification with over 900 children in SCCD may
Sql Error Code 17006
cause an error with SQL error code -805. Symptom The following error appears in System Out
Sql Error Code 17008
log: [2015-11-03 08:29:50:392 CET] 00051690 SystemOut O 03 nov 2015 08:29:50:392 [ERROR] [MXServer] [server1234] BMXAA6713E - The MBO fetch operation failed in the mboset with the
Sql Error Code 904
SQL error code -805. The record could not be retrieved from the database. See the log file for more details about the error. Cause When following these steps, the action errors: 1) Go to the Classifications application and bring up a classification. 2) Try to add an attribute to classification. The following error is displayed: BMXAA4210E - Database error -805 3) Check "Apply down hierarchy". Environment The problem was reproduced in SCCD 7.5.0.2, TPAE 7.5.0.4 and DB2 NT 9.7 Resolving the problem Confirm that the know Maximo defect IV65191 is resolved. APAR IV65191 CANNOT ADD ATTRIBUTE TO CLASSIFICATION WHEN ATTRIBUTE ALREADY ADDED TO ASSET SPECIFICATIONS. Otherwise, it could be related to the DB2 configuration to handle largeSQL statements in sections in 9.7. As per the DB2 Technote below, check how the CLIPkg is set in the db2cli.ini file. http://www-01.ibm.com/support/knowledgecenter/SSEPGG_9.7.0/com.ibm.db2.luw.apdv.cli.doc/doc/r0008961.html Cross reference information Segment Product Component Platform Version Edition Systems and Asset Management Maximo Asset Management Document information More support for: Maximo Asset Management Classifications Software version: Version Independent Operating system(s): Platform Independent Reference #: 1974465 Modified date: 12 January 2016 Site availability Site assistance Contact and feedback Need support? Submit feedback to IBM Support 1-800-IBM-7378 (USA) Directory of worldwide contacts Contact Privacy Terms of use Accessibility
Maximo Classification SCCD TPAE Maximo db2cli BMXAA6713E -805 DB2 IV65191 Technote (troubleshooting) Problem(Abstract) During the classifications in the SCCD application, adding an attirbute caused the error in the system log. The action is then not completed Symptom Error in System Log: [2015-11-03 08:29:50:392 CET] 00051690 SystemOut O 03 nov 2015 08:29:50:392 [ERROR] [MXServer] [server1234] BMXAA6713E - The MBO fetch operation failed http://www-01.ibm.com/support/docview.wss?uid=swg21974465 in the mboset with the SQL error code -805. The record could not be retrieved from the database. See the log file for more details about the error. Cause This has been identified as a product defect under APAR IV65191 however in some cases the problem persists. The database configuration is http://www-01.ibm.com/support/docview.wss?uid=swg21974464 also a contributing factor as it needs to handle largeSQL statements in sections in DB2. Environment Identified in the following combination: SCCD 7.5.0.2, TPAE 7.5.0.4 and DB2/NT64 9.7 Diagnosing the problem The classification structure with a parent and 996 child classifications. On adding a new attribute to the parent class then selecting "Apply down Hierarchy" will generate the error. Resolving the problem Confirm the fix for Maximo IV65191 has been resolved in environment. This could also be related to the DB2 configuration to handle largeSQL statements in sections in 9.7. Check the settings in db2cli.ini as per DB2 Technote: http://www-01.ibm.com/support/knowledgecenter/SSEPGG_9.7.0/com.ibm.db2.luw.apdv.cli.doc/doc/r0008961.html Document information More support for: Maximo Asset Management Classifications Software version: Version Independent Operating system(s): Platform Independent Reference #: 1974464 Modified date: 14 March 2016 Site availability Site assistance Contact and feedback Need support? Submit feedback to IBM Support 1-800-IBM-7378 (USA) Directory of worldwide contacts Contact Privacy Terms of use Accessibility
APAR status Closed as program error. Error description Environment: Maximo Asset Manager 7.5.0.3 Websphere 7.0.0.21 Oracle 11.2 Concerns/Problem: This error happens after going to any application (not just Location) and returning http://www-01.ibm.com/support/docview.wss?uid=swg1IV46065 to the WO Tracking application. Basically the changes on the called application are not reflected in the calling application with "return with value" feature, unless the record on the calling application is re-opened. As a result of this, any workflows expecting data that was filled up in the called application are not working correctly. Steps to reproduce the issue: 1. Create a action to set value to 'Test' for Attribute "LOCATION.description" sql error 2. Create a simple Workflow with start and stop nodes only. 3. In the connection line property, add the action created above 4. Active the workflow and associated to Work Order Tracking application 5. Open a work order with status = WAPPR and has a location associated 6. From the Location field, click Go To Location 7. In Locations application, changed the location (e.g. change the location description). Then return with sql error code value back to Work Order Tracking application 8. Route the workflow just created above, 9. Get the error message: BMXAA8229W - Record LOCATIONS : Site=BEDFORD Location=OFFICE has been updated by another user. Your changes have not been saved. Refresh the record and try again. If try to route the workflow again, it works. Local fix N/A Problem summary **************************************************************** * USERS AFFECTED: * * Maximo 75 users who upgraded from rel 6 * **************************************************************** * PROBLEM DESCRIPTION: * * Refetch error occurred when routing work flow after * * applinking to a different application and used Return with * * Values to the main application. * **************************************************************** * RECOMMENDATION: * * Please upgrade to 7.5.0.6 or request hotfixes * **************************************************************** Problem conclusion This is fixed in code. The fix for this APAR is contained in the following maintenance package: | release\fix pack | Interim Fix for Release 7.5.0.6 Product Temporary fix Comments APAR Information APAR numberIV46065 Reported component nameWORK & MTRL APP Reported component IDTIVOWRKMM Reported release750 StatusCLOSED PER PENoPE HIPERNoHIPER Special AttentionNoSpecatt / Xsystem Submitted date2013-07-23 Closed date2013-09-24 Last modified date2013-09-24 APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros MAXIMO Fix information Fixed component nameWORK & MTRL