Maximo Wire - The IBM Maximo Help & Discussion Forum
May 22, 2012, 09:59:07 pm *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: Welcome to Maximo Wire, the IBM Maximo help forum. Feel free to register and ask any Maximo related questions you like.
 
  Home Help Search Login Register  
*
Pages: [1]   Go Down
  Print  
Author Topic: Create first GL Account (Attribute key error)  (Read 1158 times)
0 Members and 1 Guest are viewing this topic.
shane_mann
Newbie
*

Karma: 0
Posts: 5


View Profile Email
« on: March 19, 2009, 12:48:59 am »

Hi all,

Just found this forum and hopefully will be able to contibute (and get some help) regarding maximo.

The big picture is that we have a version 4 production installation, and are migrating to version 6.2. However, before we do the migration, we are attempting to prove some functionality using a standard version 6 installation. The install went well and we have both the Maximo application and database up and running 9the DB is empty). I've followed the admin guide to create a customer but we cannot create a GL Account.

When we try to add a new row for the GL Account - we get an error as follows:
"More than one attribute has primary column equal to 1. They must be different for each attribute"

I assume there is a primary key constraint on a table in the database but can't find where/how to reset or fix it?

Any ideas? is this a known bug/issue?

Any help appreciated.

Cheers,
Shane
Logged
amdisuk
Administrator
Full Member
*****

Karma: -1
Posts: 199


allandonaldson@hotmail.com
View Profile WWW
« Reply #1 on: March 19, 2009, 10:41:00 am »

Hi Shane,

I assume that this is a customization gone wrong. If you know the table that is causing the problem then you should be able to find the fields in Database Configuration.  I am surprised that you were allowed to do this. Anyway it shouldn't be difficult to change.

Hope that helps.

Al
Logged

Big Al
shane_mann
Newbie
*

Karma: 0
Posts: 5


View Profile Email
« Reply #2 on: March 20, 2009, 05:26:07 am »

Not sure if it was our customisation or not - but I found this:

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

And it shed enough light on the problem to find the problem Attribute. Once I reset them it seems to be working OK.

Cheers,
Shane
Logged
amdisuk
Administrator
Full Member
*****

Karma: -1
Posts: 199


allandonaldson@hotmail.com
View Profile WWW
« Reply #3 on: March 20, 2009, 07:47:06 am »

Lol, ok that is not a customization then. It's an IBM bug Cheesy
Logged

Big Al
shane_mann
Newbie
*

Karma: 0
Posts: 5


View Profile Email
« Reply #4 on: March 23, 2009, 05:31:39 am »

yeah - I don't think the database should allow itself to get into this situation. In our case the 'TOOLINV' objectname had multiple rows where primarykeycolseq was 1, then some other rows where it was 2,3,4. So after nulling out the rows equal to 1, there was a primarykeycolseq 'gap' error as it went null,2,3,4 if that makes sense.

eg:

SQL> update maximo.maxattribute set primarykeycolseq=null where objectname='TOOL
INV' and primarykeycolseq=1;

2 rows updated.

SQL> select objectname, attributename, primarykeycolseq from maximo.maxattribute
 where objectname='TOOLINV' and primarykeycolseq<>1;

OBJECTNAME         ATTRIBUTENAME   PRIMARYKEYCOLSEQ

TOOLINV            ITEMSETID      4

TOOLINV            SITEID      3

TOOLINV            LOCATION      2
         

SQL> update maximo.maxattribute set primarykeycolseq=null where objectname='TOOL
INV' and attributename='ITEMSETID';

1 row updated.

SQL> update maximo.maxattributecfg set primarykeycolseq=null where objectname='T
OOLINV' and attributename='ITEMSETID';

1 row updated.

SQL> update maximo.maxattribute set primarykeycolseq=null where objectname='TOOL
INV' and attributename='SITEID';

1 row updated.

SQL> update maximo.maxattributecfg set primarykeycolseq=null where objectname='T
OOLINV' and attributename='SITEID';

1 row updated.

SQL> update maximo.maxattribute set primarykeycolseq=null where objectname='TOOL
INV' and attributename='LOCATION';

1 row updated.

SQL> update maximo.maxattributecfg set primarykeycolseq=null where objectname='T
OOLINV' and attributename='LOCATION';

1 row updated.

SQL> commit;

Commit complete.

Seems to be working now. Not sure if this is a very good fix though - will probably cause problems in the long run. This won't be our production database anyway so not too concerned.

Cheers,
Shane
Logged
Pages: [1]   Go Up
  Print  
 
Jump to:  

Recent

TinyPortal v1.0 beta 4 © Bloc
Powered by MySQL Powered by PHP Powered by SMF 1.1.15 | SMF © 2011, Simple Machines Valid XHTML 1.0! Valid CSS!