Maximo Database Error 2601
Contents |
error 2601; Archive; creating workorder error; saving work order; TPAEWORK bmxaa4211e - database error number -803 Technote (troubleshooting) Problem(Abstract) While trying to save a work order
Bmxaa4211e - Database Error Number 1400 Has Occurred
a BMXAA4211E Database Error is displayed in the logs. Symptom Steps to reproduce: 1) Create maximo bmxaa4211e database error number 1 a new work order. 2) Enter the required information. 3) Save the work order. The result is that following error is displayed: "Database error database error number 1 has occurred when operating on occurred when operating on Workview : Record *** Class = *** and Site = ***. Report Error to the owner of deployment." Cause This is happening because there may already be existing records within the database that Maximo is unaware of. This can be very old data, and it can
Bmxaa4211e - Database Error Number 2601 Has Occurred When Operating On Assetancestor.
be data that was not used. The reason this error occurs is because Maximo is trying to write to the database and that record (the primary key value) already exists. Resolving the problem To resolve this issue, we suggest that you proceed to archive your data, and when doing so, you should select the option to remove the data that is being archived from the current database. When this is done, you should able to store the newly created work orders. Document information More support for: Maximo Asset Management Work Order Tracking Software version: 6.2.1, 6.2.2, 6.2.3, 6.2.4, 6.2.5, 6.2.6, 6.2.7, 6.2.8, 7.1.1, 7.5, 7.6 Operating system(s): AIX, HP-UX, Linux, Solaris, Windows Reference #: 1634274 Modified date: 10 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
error 2601; duplicate key; unique index; sql server; maximo; base services; TPAEUI:TPAESS2005; TPAESS2008 Technote (troubleshooting) Problem(Abstract) Cannot insert duplicate key row in object bmxaa4211e - database error number 29861 "X" with unique index 'Y" error showing after Maximo 7.1.x patch update is done (On SQL Server only) Symptom After a Maximo 7.1.x patch update on SQL Server you could get a duplicate index error showing Cause Often this is caused as the sequence generator appears to be out of sequence for the mentioned object's uid table. Environment SQL Server only Diagnosing the problem http://www-01.ibm.com/support/docview.wss?uid=swg21634274 As an example ,when testing a new Maximo 7.1.x update and it appears it is no longer possible to move an asset from location to location. There are some error messages displayed, for example: BMXAA0066E - Asset "X" in site "Y" was not moved successfully. BMXAA4211E - Database error number 2601 has occurred when operating on ASSET "X" [SQL1\SQL1] Cannot insert duplicate key row http://www-01.ibm.com/support/docview.wss?uid=swg21419788 in object 'dbo.asset' with unique index 'asset_ndx1'. Resolving the problem It this example the sequence generator is out of sequence for the assetuid table. To fix this on SQL Server with Maximo 7.1.x: a) Get the highest current value for assetuid plus 1: select max(assetuid)+1 from asset b1) Update the sequence, use the number from the select for the ### value below: update maxsequence set maxreserved = ### where tbname='ASSET' and name = 'assetuid' b2) E.g. if the maximum number is 600, then the update statement is: update maxsequence set maxreserved = 601 where tbname='ASSET' and name = 'ASSETID' N.B!: It is necessary to restart Maximo after updating the sequence, so please restart from the Web Sphere console when it is convenient. c) Test:Create a new asset and or move an asset from a location to another location. Cross reference information Segment Product Component Platform Version Edition Systems and Asset Management Tivoli Asset Management for IT Not Applicable AIX, HP-UX, Linux, Solaris, Windows 7.1, 7.1.1, 7.1.2 Systems and Asset Management Tivoli Change and Configuration Management Database Not Applicable AIX, Linux, Windows, Solaris, HP-UX 7.1.1, 7.1.2 Systems and Asset Management Tivoli S
Database error number 2601; 2601 has occurred when operating on http://www-01.ibm.com/support/docview.wss?uid=swg21609490 PLUSPWOPRICETOTALS; Report the error to the owner of the deployment; Cannot insert duplicate key row; unique index; duplicate key value Technote (troubleshooting) Problem(Abstract) Unable https://maximotimes.com/forum/general-maximo-7-support/bmxaa4211e-database-error-number-2601-has-occurred-when-operating-on-maxuser/ to return rotating assets using the Issues and Transfers application. Symptom Steps to reproduce: 1. Go to the Inventory module. 2. Go to the database error Issues and Transfers application. 3. Select a storeroom. 4. Select "Items for Return". 5. Choose a rotating asset. 6. Save. Error message comes up: "BMXAA4211E - Database error number 2601 has occurred when operating on PLUSPWOPRICETOTALS : Site=BEDFORD Work Order=12345. Report the error to the owner of the database error number deployment." Excerpt from log file: Cannot insert duplicate key row in object 'dbo.pluspwopricetotals' with unique index 'pluspwopricetotals_ndx2'. The duplicate key value is (BEDFORD, 12345). com.microsoft.sqlserver.jdbc.SQLServerException: Cannot insert duplicate key row in object 'dbo.pluspwopricetotals' with unique index 'pluspwopricetotals_ndx2'. The duplicate key value is (BEDFORD, 12345). Environment Sql server environment. Diagnosing the problem Upgraded from Maximo version 6.2 Resolving the problem Delete the indexes PLUSPWOPRICETOTALS_NDX1 AND PLUSPWOPRICETOTALS_NDX2 by running the script below: drop index PLUSPWOPRICETOTALS.PLUSPWOPRICETOTALS_NDX1 go drop index PLUSPWOPRICETOTALS.PLUSPWOPRICETOTALS_NDX2 go Document information More support for: Maximo Asset Management Issues & Transfers Software version: 6.2.1, 6.2.2, 6.2.3, 6.2.4, 6.2.5, 6.2.6, 6.2.7, 6.2.8, 7.1, 7.1.1, 7.5 Operating system(s): AIX, HP-UX, Linux, Solaris, Windows Reference #: 1609490 Modified date: 13 August 2014 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
EZMaxMobile – Maximo Mobile Solution EZDash – Custom Maximo Dashboard EZEnergyDash – Maximo Dashboard WebAssign – Workorder Assignment & Scheduling WebMaint – Customer Service Request Module Contact Register Sign Up Lost Password All Things MaximoYou are here: Home / MAXIMO ForumMAXIMO Forum This forum requires Javascript to be enabled for posting content Please consider registeringguest Log In Register Login name Password Remember me Register | Lost password? Select Forum Tutorial Requests General MAXIMO 6 Support General MAXIMO 7 Support MAXIMO Enterprise Adapter (MEA) MAXIMO Integration Framework (MIF) MAXIMO Scheduler MAXIMO Reports Application Designer New/Recently Updated Topics Advanced Search | WHERE Clause BMXAA0024E - ADD is not allowed in LabTr… Upgrade from 628 to 7603 - Websphere rel… Apply Template to Multiple Service Reque… Move Asset to another location using Aut… [WORKFLOW] Add labor to new WO… Transfer current item problem 7.6.0.3 Edit Mode Sum column on one table and add to anoth… Numbers display format Issue in fetching contract lines from PO… Can you add advanced search field to que… Create Work order from Asset Using escal… Using Maximo REST API for sending data f… Update XY thru web service Errors testing my endpoint Date Based Status Snapshot BIRT - Javascript expression Adding new Available Fields to Ad-Hoc re… How to create new UI control ? Search Advanced Search Advanced Search—Forum Scope—Current forumAll forums—Match—Match any wordMatch all wordsMatch phrase—Forum Options—Posts onlyTopic titles onlyPosts and topic titlesTags only (single tag)Minimum search word length is 3 characters - maximum search word length is 84 characters Search Home MAXIMO Forum General MAXIMO 7 Support BMXAA4211E - Database error number 2601 has occurred when operating on MAXUSER Topic RSS Related Topics BMXAA4211E - Database error number 2601 has occurred when operating on MAXUSER BMXAA4211E - Database error number 2601 has occurred when operating on MAXUSER Tags: BMXAA4211EDatabase error number 2601operating on MAXUSER November 18, 20145:46 pm KaarlH Member Members F