cancel
Showing results for 
Search instead for 
Did you mean: 

IDM 8.0 Identity Management Database not updated properly

0 Kudos

Hi,

Yesterday I upgraded successfully my SAP IDM 7.2 instance to 8.0.

After configuring SSL for Eclipse I recieve the error message on Login: Identity Management Database not updated properly

Before this message I got the Error message on the idmdevstudio Java Application:


ErrorCode: 0, ErrorMessage: The SELECT permission was denied on the object 'mc_dbschema', database 'mxmc_db', schema 'dbo'.
OpenSQLExceptionCategories: [], CausedBy: 0


I changed the select rights on this table to public (for testcases) and it "worked"

I re-run the mxmc_update.cmd script with no success.

The first time I ran the script all Identity Stores where updated successfully (status code 0).

There is the RDS kit installed from 7.2

It's a Windows Server 2012 with SQL Server 2012, I installed all on the same machine.

I ran the update script with user mxmc_oper and the db connection on netweaver is configured with mxmc_prov.

Any Ideas how to debug?

Or any Ideas how to fix?

Thanks, Patrick

Accepted Solutions (1)

Accepted Solutions (1)

0 Kudos

I restored the the identity db and updated again, here is the log:

Updating schema

*** Start installing update 1200...

*** Update 1200 installed

*** Start installing update 1201...

*** Update 1201 installed

*** Start installing update 1202...

*** Update 1202 installed

*** Start installing update 1203...

*** Update 1203 installed

*** Start installing update 1204...

*** Update 1204 installed

*** Start installing update 1500...

*** Update 1500 installed

*** Start installing update 1501...

*** Update 1501 installed

*** Start installing update 1502...

*** Update 1502 installed

*** Start installing update 1503...

*** Update 1503 installed

*** Start installing update 1504...

*** Update 1504 installed

*** Start installing update 1505...

*** Update 1505 installed

*** Start installing update 1506...

*** Update 1506 installed

*** Start installing update 1507...

*** Update 1507 installed

*** Start installing update 1508...

*** Update 1508 installed

*** Start installing update 1509...

*** Update 1509 installed

*** Start installing update 1510...

*** Update 1510 installed

*** Start installing update 1511...

*** Update 1511 installed

*** Start installing update 1512...

*** Update 1512 installed

*** Start installing update 1513...

*** Update 1513 installed

*** Start installing update 1514...

*** Update 1514 installed

*** Start installing update 1515...

*** Update 1515 installed

*** Start installing update 1516...

*** Update 1516 installed

*** Start installing update 1517...

*** Update 1517 installed

*** Start installing update 1518...

*** Update 1518 installed

*** Start installing update 1519...

*** Update 1519 installed

*** Start installing update 1520...

*** Update 1520 installed

*** Start installing update 1521...

*** Update 1521 installed

*** Start installing update 1522...

*** Update 1522 installed

*** Start installing update 1523...

*** Update 1523 installed

*** Start installing update 1524...

*** Update 1524 installed

*** Start installing update 1525...

*** Update 1525 installed

*** Start installing update 1526...

*** Update 1526 installed

*** Start installing update 1527...

Msg 2627, Level 14, State 1, Server WIBW12SAPIDM, Line 25

Violation of PRIMARY KEY constraint 'PK_mxi_error'. Cannot insert duplicate key in object 'dbo.MXI_ERROR'. The duplicate key value is (152).

Creating functions

Done creating functions

Creating views

Done creating views

Creating stored procedures

Done creating stored procedures

*******************************************************************

*** ERROR.

    Mismatch between schema version (1526) and procedure version (1527)

*******************************************************************

Creating triggers

Done creating triggers

Enabling 7.2 approval mechanism views

Enabling Configuration Lifecycle Management

Creating admin user Administrator. This user must also exist in UME to be able to log on from the Identity Management Developer Studio

User Administrator created

Creating default packages in existing IdStores

----- IdStore1/Enterprise People -----

Created default package for IdStore 1/Enterprise People

*   Package qualified name: sapidm.NewPackage1

*   Package owner:          1/Administrator

----- IdStore2/PrivRoles -----

Created default package for IdStore 2/PrivRoles

*   Package qualified name: sapidm.NewPackage2

*   Package owner:          1/Administrator

----- IdStore3/HCM_Staging_Area -----

Created default package for IdStore 3/HCM_Staging_Area

*   Package qualified name: sapidm.NewPackage3

*   Package owner:          1/Administrator

----- IdStore4/SPML_IDS -----

Created default package for IdStore 4/SPML_IDS

*   Package qualified name: sapidm.NewPackage4

*   Package owner:          1/Administrator

Populate mc_repository.mcQualifiedName from mc_repository_type

Refactor tasks: 183 task changes made

Configuration Lifecycle Management enabled

Updating IdStore schema 

Checking jdbc connection 

[20.03.2015 14:39:54-725] - Reading Db Info - STATEMENT PREPARED: SELECT INFOVALUE FROM MC_DBINFO where INFONAME='TYPENUM'

jdbcconnection OK 

Updating IdStore schema 

[20.03.2015 14:39:56-201] - Reading Db Info - STATEMENT PREPARED: SELECT INFOVALUE FROM MC_DBINFO where INFONAME='TYPENUM'

Updating schema on identity store 3

Identity store 3 was initialized with status: 0

Updating schema on identity store 4

Identity store 4 was initialized with status: 0

Updating schema on identity store 2

Identity store 2 was initialized with status: 0

Updating schema on identity store 1

Identity store 1 was initialized with status: 0

IdStore schema updated 

Former Member
0 Kudos

Hi,

You have a problem with Update 1527 du to an error from the MXI_ERROR table.

I am not able to find any problem with the schema update file.

Is it possible you have error 152 defined in the system you are upgrading?

This problem makes the mismatch problem because update 1527 is required and with this mismatch the system is unusable.

Check what you have in the mxi_error table.

Ole K.

Former Member
0 Kudos

Hi,

I have checked the installation files for 7.2 SP9 P13 and 8.0.

They both have the same update for the MXI_ERROR table using the same error numbers.

In 7.2 SP9 P13 this is Update 1130, and in 8.0 the same is done in Update 1527.

The consequence is that it is impossible to upgrade from 7.2 SP9 P13 to 8.0.

Please open an OSS for this.

The workaround is to remove the two INSERT statements in Update 1527 (in 4-updates.sql)

making this into a dummy update.

Regards, Ole K.

Chenyang
Contributor
0 Kudos

Hi Ole,

I am preparing a IDM 8 upgrade demo and I am having the same error with Patrick.

I have tried your workaround and I am able to logon to Eclipse. But there are quite a lot follow up DB authorization issues. I guess there is something wrong with the DB scripts.

Do you have any suggestions on the issues below?

Thanks,

Chenyang Xiong

Former Member
0 Kudos

Hi,

From the error messages it looks like you have configured the DevStudio datasource with the db user <prefix>_prov. You should use <prefix>_admin.

Regards, Ole K.

Chenyang
Contributor
0 Kudos

Ah I see. Thank you Ole.

This is different from IDM 7.2 and should be emphasis during upgrade/migration.

The data source is using <prefix>_prov as db user name in IDM 7.2 and it should be changed to <prefix>_admin in IDM 8.0.

Former Member
0 Kudos

Hi,

Just to clarify, in IdM 8 there are two datasources created, one for the UI, as for 7.2, and one for that Developer Studio.

The one for the UI should still use the <prefix>_prov user, but the one for Developer Studio should use the <prefix>_admin user.

Regards, Ole K.

Chenyang
Contributor
0 Kudos

Thanks for clarification, Ole.

It works now.

Answers (5)

Answers (5)

Former Member
0 Kudos

Dear All

I am working on SAP IDM 8.0 SP1, this is my first time getting hands on on IDM.

At first, i was unable to create any Identity directly in identity store using IDM UI.

then i ran the mxmc-update.cmd command successfuly & i was able to create an identity in the IDM UI & save successfully.

But when i tried to login to IDM Eclipse studio, there was a login error message saying " Identity Management database not update properly"

hence i tried to run the same command with mxmc-oper user id & mxmc-admin user id, in both cases the update was successfully completed, but the Eclipse login still remains.

pls suggest the corrective measures if i am missing any?

Naveen

former_member2987
Active Contributor
0 Kudos

Hi Naveen,

Are you upgrading or doing a new install?  I'd suggest double checking the documentation along with your BASIS and DBA teams.  If that doesn't help, please open a new discussion thread for this issue.

Thanks,

Matt

Former Member
0 Kudos

Hi Naveen,

check if all updates are installed in db. (mxmc-update script)
IDM checks for the last update in the list to be present in mc_dbschema table.

check if core component (db schema) and runtime on the same SP.

0 Kudos

Hey,

Just so enhance my experience with SAP IDM 8.0

I imported the packages, that comes with the installation and tried to create a role/privilege from a task. And I got always "Could not expand values for attribute MX_CTX_TYPE"

I edited the SQL Query to get the Values of the attribute like:

After that, it worked

Patrick

Former Member
0 Kudos

Hi,

So this indicates that %ID_STORE% does not work in the Attribute Values tab?

Ole K.

0 Kudos

sorry, I changed the SQL Query from:

SELECT ocName FROM mxi_objectclasses WHERE ocIsId=B1535064-32F1-47AD-B87D-07C35C0E2DAB AND ocContext>0 ORDER BY ocName

to this in the screenshot.

Patrick

Former Member
0 Kudos

Hi,

My installation had %ISID% and not the GUID, and anyway, the mxi_objectclasses does not have a GUID:

Ole K.

0 Kudos

Hi,

Finally I dropped the DB and started over. But this should not be a solution,

I'll restore the db, comment out this line and try the upgrade again.

I had this permission denied entries as well, you have to setup a new datasource for Eclipse with user <prefix>_admin.

Patrick

Former Member
0 Kudos

Hi,

The MXI_ERROR problem is said to be corrected by SAP, and a patch is available since yesterday.

Regards, Ole K.

youssef_anegay3
Explorer
0 Kudos

Hello

i have tried to update to IdM 8.0 and i have the exact same error. So something might be wrong in the update scripts ... or in the way we setup the connection.

BR
Y.

Former Member
0 Kudos

Hi Patrick,

It looks as if you have configured the JDBC datasource for Developer Studio to run with the wrong user.

Check if you are using the <Prefix>_admin user in this datasource.

Regards,

Ole K.

0 Kudos

Hi Ole,

I created a new Custom JDBC Datasource IDM_DataSource_DevStudio with mxmc_admin user, but no success. Still same error.

Thanks, Patrick

Former Member
0 Kudos

Hi Patrick,

Just a dumb question, did you also change your connection setting in DevStudio to point to the new datasource?

Regards, Ole K.

0 Kudos

yes, I pointed to the new datasource.

Is there a way so see which requests are sent by eclipse?

it doesn't matter if I connector to localhost, 127.0.0.1 or the hostname, I don't get a certificate warning.

I have only a certificate for the name "localhost"

It's strange.

Patrick

Former Member
0 Kudos

Hi Patrick,

This sound strange, I had the same problem with the same error messages and the reason was using the wrong db user.

Next step would be to check the developer traces on AS Java, you may find an explanation there.

Regards, Ole K.

0 Kudos

There is no new log entry when trying to connect in AS Java Logs:

C:\usr\sap\<SID>\J00\j2ee\cluster\server0\log

Ig got a warning message in Eclipse, when trying to connect the first time:

NLS missing message: ERR_MISSING_ENTTRY_TYPE in: com.sap.idm.ic.messages.pterrormessages