IBM Support

Error BMXAA7901E

Technote (troubleshooting)

This document applies only to the following language version(s):



When trying to login to Maximo BMXAA7901E - You cannot log in at this time. Contact the system administrator.


Error in logs shows unique constraint on logintrackingid whenever user tries to log in.

java.sql.SQLException: ORA-00001: unique constraint (MAXIMO.LOGINTRACKING_NDX) violated

at oracle.jdbc.driver.SQLStateMapping.newSQLException(
at oracle.jdbc.driver.DatabaseError.newSQLException(
at oracle.jdbc.driver.DatabaseError.throwSqlException(
at oracle.jdbc.driver.T4CTTIoer.processError(
at oracle.jdbc.driver.T4CTTIoer.processError(
at oracle.jdbc.driver.T4C8Oall.receive(


This is caused by the oracle sequence logintrackinguseq having an incorrect last_number. This can happen when exporting sequences from one database and importing them to a new database incorrectly.

Resolving the problem

To fix, you can recreate the sequence with the correct number to increment from. This can be achieved with the following statements:

select max(logintrackingid) from logintracking;

drop sequence logintrackinguseq;

create sequence logintrackinguseq start with #### (number one higher
than selected above);

for example

create sequence logintrackinguseq start with 1000;

Cross reference information
Segment Product Component Platform Version Edition
Systems and Asset Management Maximo Asset Management Essentials
Systems and Asset Management Tivoli Asset Management for IT
Systems and Asset Management Control Desk
Systems and Asset Management Tivoli Change and Configuration Management Database
Systems and Asset Management Tivoli Service Request Manager

Document information

More support for: Maximo Asset Management

Software version: 6.2, 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, Version Independent

Operating system(s): Platform Independent

Software edition: All Editions

Reference #: 1617333

Modified date: 14 November 2012

Translate this page: