IDM UI Error(s) After Offline/DB-Restore (BRRESTORE)

[Former Member]

After Offline/DB-Restore (BRRESTORE):

We received the following error(s) when calling :

"http://vhsap3808:50200/webdynpro/dispatcher/sap.com/tc_idmwd~workflow/Idm"

error: Could not get the self service tasks for user

and

! Vorhandene Werte für Attribut #MX_MXREF_MX_PRIVILEGE_DN ...konnten nicht ermittelt werden

The IDM Schema is in the same DB as the Java Stack. The Java Stack runns fine after BRRESTORE. The Identity Center also runns without showing any error.

HP-UX 11.23,Oracle 10.2.0.4

NW7.0 SP20 (Java only)

[Former Member]

Very much THANKS for the support!!!

[Former Member]

Dann ist ja alles gut

I was jumping around on the version so much, because I got that error on a sandbox of mine where the versions were not equal.

Good to hear it works again.

Have a good day

Chris

[Former Member]

This usually happens, if the version of the UI is not equal the version of the DB.

What does it say on your MMC at Version an Latest Schema update? (Database Tab of your IDM configuration)

[Former Member]

Hi Christian!

Thanks for the fast answer!

The MMC says that the Version of the Latest Schema update is 543.

How to solve the Problem? Is there a Schema Update anywhere to fix this?

Kind regards,

Karsten!

[Former Member]

543 is Service Pack 3.

What version you got on the Web UI?

[Former Member]

Hi , sorry my mistake

I´ve forgotten to post, that we are

using a full installation of IDM SP3!

I don´t exactely know what you mean with

"UI" Version....

If i log on in the Browser....there is now way to see the "Version" of the UI...

(or i´m not able to "find" it!)

If i connect to the Java engine i see this:

Information for SCA IDMIC 1000.7.00.3.0.20090828130144

....is it possible that i send you my phone numer via mail, so that we

can fix this soon?

Greetings,

Karsten!

[Former Member]

I had another idea:

What does it say in the MMC under Identity Center Version?

UI = User Interface, which you deploy to Java.

[Former Member]

Hi thanks for the support!

The MMC says under Identity Center Version:

7.10.3.1-ORA-2009-11-13

Greetings,

Karsten!

[Former Member]

You got Service Pack 3 Patch 1 on the DB.

The User Infterface is Service Pack 3 Patch 0.

This should work however.

You could try running mxmc_update (to Service Pack 3 Patch 1) again.

Maybe something went wrong during the restore.

[Former Member]

Hi there!

We had already found this "trick" in an older Post.

We´ve let running mxmc_update (to Service Pack 3 Patch 1) again...

but the Problem still is there

Hope you have another idea to solve this?

Greetings,

Karsten!

Edited by: Karsten Kautz on Feb 23, 2010 11:01 AM

[Former Member]

Thats really strange.

If you go to SQL Plus

mxmc_prov

And then select * from mxiv_values where mskey = 1006;

This should return you the details of Administrator.

Maybe something went wrong with the permissions.

[Former Member]

Hi I´ve done the sql statement, but i only can identify right´s in a SAP repository:

SQL> select * from mxiv_values where mskey=1006;

MSKEY CHANGENUMBER CHANGETYPE CHANGEDBY MODIFYTIME

-

-

---

-

-

---

-

-

---

-

-

---

-

-

---

AVALUE

-

-

---

ALONG

-

-

---

SEARCHVALUE

-

-

---

VALOWNER ATTR_ID EXPIRYTIME

-

-

---

-

-

---

-

-

---

USERID

-

-

---

IS_ID BCHECKSUM IDAUDIT PARENTAUDITID AUDITID DISABLED PARENTMSKEY

-

-

---

-

-

---

-

-

---

-

-

---

-

-

---

-

-

---

-

-

---

EXECSTATUS M

-

-

---

-

1006 7955 2 -3 14-JAN-10

MSKEY CHANGENUMBER CHANGETYPE CHANGEDBY MODIFYTIME

-

-

---

-

-

---

-

-

---

-

-

---

-

-

---

AVALUE

-

-

---

ALONG

-

-

---

SEARCHVALUE

-

-

---

VALOWNER ATTR_ID EXPIRYTIME

-

-

---

-

-

---

-

-

---

USERID

-

-

---

IS_ID BCHECKSUM IDAUDIT PARENTAUDITID AUDITID DISABLED PARENTMSKEY

-

-

---

-

-

---

-

-

---

-

-

---

-

-

---

-

-

---

-

-

---

EXECSTATUS M

-

-

---

-

PRIV:ROLE:KFS100:SAP_ICM_S_DOC_UNDO

MSKEY CHANGENUMBER CHANGETYPE CHANGEDBY MODIFYTIME

-

-

---

-

-

---

-

-

---

-

-

---

-

-

---

AVALUE

-

-

---

ALONG

-

-

---

SEARCHVALUE

-

-

---

VALOWNER ATTR_ID EXPIRYTIME

-

-

---

-

-

---

-

-

---

USERID

-

-

---

IS_ID BCHECKSUM IDAUDIT PARENTAUDITID AUDITID DISABLED PARENTMSKEY

-

-

---

-

-

---

-

-

---

-

-

---

-

-

---

-

-

---

-

-

---

EXECSTATUS M

-

-

---

-

MSKEY CHANGENUMBER CHANGETYPE CHANGEDBY MODIFYTIME

-

-

---

-

-

---

-

-

---

-

-

---

-

-

---

AVALUE

-

-

---

ALONG

-

-

---

SEARCHVALUE

-

-

---

VALOWNER ATTR_ID EXPIRYTIME

-

-

---

-

-

---

-

-

---

USERID

-

-

---

IS_ID BCHECKSUM IDAUDIT PARENTAUDITID AUDITID DISABLED PARENTMSKEY

-

-

---

-

-

---

-

-

---

-

-

---

-

-

---

-

-

---

-

-

---

EXECSTATUS M

-

-

---

-

PRIV:ROLE:KFS100:SAP_ICM_S_DOC_UNDO

MSKEY CHANGENUMBER CHANGETYPE CHANGEDBY MODIFYTIME

-

-

---

-

-

---

-

-

---

-

-

---

-

-

---

AVALUE

-

-

---

ALONG

-

-

---

SEARCHVALUE

-

-

---

VALOWNER ATTR_ID EXPIRYTIME

-

-

---

-

-

---

-

-

---

USERID

-

-

---

IS_ID BCHECKSUM IDAUDIT PARENTAUDITID AUDITID DISABLED PARENTMSKEY

-

-

---

-

-

---

-

-

---

-

-

---

-

-

---

-

-

---

-

-

---

EXECSTATUS M

-

-

---

-

2

MSKEY CHANGENUMBER CHANGETYPE CHANGEDBY MODIFYTIME

-

-

---

-

-

---

-

-

---

-

-

---

-

-

---

AVALUE

-

-

---

ALONG

-

-

---

SEARCHVALUE

-

-

---

VALOWNER ATTR_ID EXPIRYTIME

-

-

---

-

-

---

-

-

---

USERID

-

-

---

IS_ID BCHECKSUM IDAUDIT PARENTAUDITID AUDITID DISABLED PARENTMSKEY

-

-

---

-

-

---

-

-

---

-

-

---

-

-

---

-

-

---

-

-

---

EXECSTATUS M

-

-

---

-

MSKEY CHANGENUMBER CHANGETYPE CHANGEDBY MODIFYTIME

-

-

---

-

-

---

-

-

---

-

-

---

-

-

---

AVALUE

-

-

---

ALONG

-

-

---

SEARCHVALUE

-

-

---

VALOWNER ATTR_ID EXPIRYTIME

-

-

---

-

-

---

-

-

---

USERID

-

-

---

IS_ID BCHECKSUM IDAUDIT PARENTAUDITID AUDITID DISABLED PARENTMSKEY

-

-

---

-

-

---

-

-

---

-

-

---

-

-

---

-

-

---

-

-

---

EXECSTATUS M

-

-

---

-

1 24656 0 0

MSKEY CHANGENUMBER CHANGETYPE CHANGEDBY MODIFYTIME

-

-

---

-

-

---

-

-

---

-

-

---

-

-

---

AVALUE

-

-

---

ALONG

-

-

---

SEARCHVALUE

-

-

---

VALOWNER ATTR_ID EXPIRYTIME

-

-

---

-

-

---

-

-

---

USERID

-

-

---

IS_ID BCHECKSUM IDAUDIT PARENTAUDITID AUDITID DISABLED PARENTMSKEY

-

-

---

-

-

---

-

-

---

-

-

---

-

-

---

-

-

---

-

-

---

EXECSTATUS M

-

-

---

-

0

.

.

.

.

[Former Member]

So seems the user can read the DB too.

Did you change anything on the Java side?

The only idea I got left is maybe try to upgrade it all to SP4. But maybe you should open a call to SAP...

[Former Member]

Hi!

The SAP found the "error"

.

.

.

Hi,

So the datasource seems to be defined properly, but I see that this

oracle installation is suffering from empty tablespace. I'm not sure

if that affects the IdM application (and if so, to what extent). But

I think you should start on analyzing this empty table space before

we go further on the IdM application.

In the default traces there are quite a few lines with the message:

ORA-25153: Temporary Tablespace is Empty

Best regards,

.

.

.

In our case it was PSAPTEMP what wasn´t attached properly after the db recovery!

VERY much THANKS for your help!

Kind regards,

Karsten!

Edited by: Karsten Kautz on Feb 24, 2010 6:01 PM

Edited by: Karsten Kautz on Feb 24, 2010 6:02 PM

Edited by: Karsten Kautz on Feb 24, 2010 6:03 PM