Database Error Number 0 Has Occurred Maximo
Contents |
INPUT STRING: "994,843" Subscribe You can track all active APARs for this component. APAR status Closed as program error. Error description When interfacing Maximo 7.1 with Oracle Applications 12, you may encounter this error bmxaa4211e - database error number -803 when sending Inventory Reservation to the Oracle Applications. The error occurs when the ExternalRefID value
Database Error Number Has Occurred
for an Inventory item is a value that will contain a Thousands separator. The error indicates a Mismatch of the EXTERNALREFID value which bmxaa4210e database error number 0 is a maxtype of ALN or Oracle type of Varchar2, that is being placed into the field OA_ITEM_ID which has a maxtype of INTEGER or an Oracle type of number. The Oracle Adapter is unable to place
Bmxaa4211e Database Error Number 803
the Alpha Numeric value into the Numeric field in the associated Interface table for the Inventory Reservation Transaction. Local fix None Available Problem summary **************************************************************** * USERS AFFECTED: Thousand separator in ExternalRefId field. * **************************************************************** * PROBLEM DESCRIPTION: When interfacing Maximo 7.1 with Oracle * * Applications 12, you may * * * * encounter this error when sending * * Inventory Reservation to the * * * * Oracle Applications. The error occurs bmxaa4211e - database error number 1400 has occurred * * when the ExternalRefID * * * * value for an Inventory item is a value * * that will contain a * * * * Thousands separator. The error * * indicates a Mismatch of the * * * * EXTERNALREFID value which is a maxtype * * of ALN or Oracle type of * * * * Varchar2, that is being placed into the * * field OA_ITEM_ID which * * * * has a maxtype of INTEGER or an Oracle * * type of number. The * * * * Oracle Adapter is unable to place the * * Alpha Numeric value into * * * * the Numeric field in the associated * * Interface table for the * * * * Inventory Reservation Transaction. * * * * LOCAL FIX: * * * * None Available * * * **************************************************************** * RECOMMENDATION: * * * * * * * **************************************************************** BMXAA4210E - DATABASE ERROR NUMBER 0 HAS OCCURRED. FOR INPUT STRING: "994,843" Problem conclusion Class InvResOutExt.java changed. The fix for this APAR is contained in the following maintenance package: | release\fix pack | REL 7.1.0.0 - BS | release\fix pack | REL 7.1.1.7 - BS | release\fix pack | REL 7.5.0.0 OR Temporary fix Comments APAR Information APAR numberIZ92548 Reported component nameMAXIMO UTILITIE Reported component ID57
(troubleshooting) Problem(Abstract) When exporting data from Maximo to an External System by using Interface Tables, Maximo may raise an error as above. Symptom OutBound Interface cannot send data out. You will see an error similar to the following: nullBMXAA4210E - Database error number 904 has occurred. ORA-00904: "PLUSCISMTECLASS": invalid identifier Cause This error happens due to a column mismatch between the Maximo MBO and the Interface table. When a new Product, Industry Solution or Add-on is installed, new columns may be added http://www-01.ibm.com/support/docview.wss?uid=swg1IZ92548 to Maximo core tables, but these columns will not be automatically applied to the Interface Tables and when MIF tries to write data in to the iface tables the insert will fail and raise the error ORA-00904 Environment Maximo 7.x Database Server: Oracle Resolving the problem There are two possible solutions for this issue: 1 - Re-create the Interface Table in the http://www-01.ibm.com/support/docview.wss?uid=swg21515454 External System Application. All data in the Interface Table will be lost. 1.1 - Go to > Integration > External System > 1.2 - Select any External System 1.3 - Select Action > Create Interface Table > 1.4 - Select the endpoint and the table to be recreated > Click the Create Button 2 - Remove the "Invalid" column from the Object Structure Schema. 2.1 - Go to > Integration > Object Structure 2.2 - Select the Object Structure being used 2.3 - Select Action > Exclude / Include Fields 2.4 - Check the "Exclude" checkbox for all fields you want to remove. 2.5 - Click OK 2.6 - Select Action > Generate Schema / View XML > OK 2.7 - Click OK in the Pop-up dialog Retest your Integration. Document information More support for: Maximo Asset Management MEA: Generic Software version: 7.1, 7.1.1, 7.5, 7.6 Operating system(s): Platform Independent Reference #: 1515454 Modified date: 2012-01-30 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
ORDERS. Subscribe You can track all active APARs for this component. APAR status Closed as program error. Error description When a user is approving and printing multiple work orders, the system freezes. An error is logged. A user is selecting multiple work orders to approve and print them http://www.ibm.com/support/docview.wss?uid=swg1IZ54006 and the system is freezing. A dialog appears which says "Processing is Complete" but then it freezes. https://www.ibm.com/developerworks/community/forums/html/topic?id=6bc8f3d3-fbbd-41a0-8878-8f577f2b4972 The error shown on the screen is: BMXAA4210E - Database error number 0 has occured. ResultSet is closed. Maximo 7.1.1.4 Local fix N/A Problem summary **************************************************************** * USERS AFFECTED: N/A * **************************************************************** * PROBLEM DESCRIPTION: When a user is approving and printing * * multiple work orders, the system * * freezes. An error is logged. A user is * * selecting multiple work orders to * * approve database error and print them and the system * * is freezing. A dialog appears which * * says "Processing is * * * * Complete" but then it freezes. The * * error shown on the screen is: * * * * BMXAA4210E - Database error number 0 * * has occured. ResultSet is closed. * * * * * * * * * * * * Maximo 7.1.1.4 * * * * LOCAL FIX: N/A * * * * * * * * * * * * database error number Steps to reproduce for client: * * * * -Goto the WOTRACK application * * * * -Filter for WAPPR status and narrow the * * search down to less then 200 records * * (client has had the problem with 60+ so * * far) * * * * -Select Records and Select All the * * Records * * * * -Click the Green Checkmark in the * * Toolbar to Approve Work Orders * * * * -When the dialog comes up to Approve, * * Check the "Print Work Order(s)" * * Checkbox * * * * -Click Ok and it takes awhile * * * * -Client gets the error after all the * * statuses are changed * * * * -Statuses change successfully, and the * * Report gets sent to the printer, but * * the error shows up and when you click * * on OK on the error nothing happens, you * * need to refresh the session to use * * Maximo again * * * * * * * * * * * * In support I was only able to reproduce * * a similar error once on one environment * * but never again. My error was sg * * 16909, Level 16, State 1, Line 1, * * Sqlstate 01000 * * * * SERVERNAME sp_cursorfetch: The cursor * * identifier value provided (abdcfe7) is * * not valid. * * * * * * * * * * * * The
process automation solutions > Topic: None-persistent column when using Interface tables 1 reply Latest Post - 2014-08-20T18:43:49Z by davisbri Display:ConversationsBy Date 1-2 of 2 Previous Next MarkLeadbetter 120000BT02 2 Posts Pinned topic None-persistent column when using Interface tables 2014-08-13T11:22:39Z | Tags: Answered question This question has been answered. Unanswered question This question has not been answered yet. Hi I have hit an issue when setting up an Integration using database interface tables. The issue I have is with the none-persistent column DESCRIPTION_LONGDESCRIPTION on an INCDENT object I created. Standard information from Tivoli can be found here http://www-01.ibm.com/support/docview.wss?uid=swg21417266 which is what I did however, when the interface table is created, via the External System, the DESCRIPTION_LONGDESCRIPTION column is not created along with the persistent columns that are not excluded. Also if you try and submit data the following error is generated; psdi.util.MXSystemException: BMXAA4210E - Database error number {0} has occurred. Invalid SQL queries are logged in the log file. Check the SQL query to identify the error. [jcc][10150][10300][3.64.114] Invalid parameter: Unknown column name DESCRIPTION_LONGDESCRIPTION. ERRORCODE=-4460, SQLSTATE=null at psdi.iface.intertables.FlatTableRowSet.getFieldValue(FlatTableRowSet.java:144) at psdi.iface.intertables.FlatToXMLConverter.createObjectAttrElement(FlatToXMLConverter.java:393) at psdi.iface.intertables.FlatToXMLConverter.prepareObjectXML(FlatToXMLConverter.java:336) at psdi.iface.intertables.FlatToXMLConverter.convert(FlatToXMLConverter.java:160) at psdi.iface.intertables.IfaceTbCronTask.createIfaceRowList(IfaceTbCronTask.java:1040) at psdi.iface.intertables.IfaceTbCronTask.processData(IfaceTbCronTask.java:1004) at psdi.iface.intertables.IfaceTbCronTask.processIfaceData(IfaceTbCronTask.java:830) at psdi.iface.intertables.Ifac