MDM 5.5 SP1 - Installation Problem

[Former Member]

Hi,

I am trying to install MDM 5.5 on Oracle database. When We use "System" Id and unarchive/create a repository, it takes lot of time and finally displays the status as "Invalid".

Then we tried to create another user and grant all privilages of "System". Please check the script below that we used.

-

---

CREATE USER "MDME" PROFILE "DEFAULT"

IDENTIFIED BY "mdme" DEFAULT TABLESPACE "USERS"

TEMPORARY TABLESPACE "TEMP"

ACCOUNT UNLOCK;

GRANT UNLIMITED TABLESPACE TO "MDME" WITH ADMIN OPTION;

GRANT ALTER ON "SYS"."INCEXP" TO "MDME";

GRANT ALTER ON "SYS"."INCFIL" TO "MDME";

GRANT ALTER ON "SYS"."INCVID" TO "MDME";

GRANT DEBUG ON "SYS"."INCEXP" TO "MDME";

GRANT DEBUG ON "SYS"."INCFIL" TO "MDME";

GRANT DEBUG ON "SYS"."INCVID" TO "MDME";

GRANT DELETE ON "SYS"."INCEXP" TO "MDME";

GRANT DELETE ON "SYS"."INCFIL" TO "MDME";

GRANT DELETE ON "SYS"."INCVID" TO "MDME";

GRANT EXECUTE ON "SYS"."DBMS_ALERT" TO "MDME";

GRANT EXECUTE ON "SYS"."DBMS_AQ" TO "MDME" WITH GRANT OPTION;

GRANT EXECUTE ON "SYS"."DBMS_AQADM" TO "MDME" WITH GRANT OPTION;

GRANT EXECUTE ON "SYS"."DBMS_AQELM" TO "MDME" WITH GRANT OPTION;

GRANT EXECUTE ON "SYS"."DBMS_AQ_IMPORT_INTERNAL" TO "MDME" WITH GRANT OPTION;

GRANT EXECUTE ON "SYS"."DBMS_DEFER_IMPORT_INTERNAL" TO "MDME";

GRANT EXECUTE ON "SYS"."DBMS_REPCAT" TO "MDME";

GRANT EXECUTE ON "SYS"."DBMS_RULE_EXIMP" TO "MDME" WITH GRANT OPTION;

GRANT EXECUTE ON "SYS"."DBMS_SYS_ERROR" TO "MDME";

GRANT EXECUTE ON "SYS"."DBMS_TRANSFORM_EXIMP" TO "MDME" WITH GRANT OPTION;

GRANT EXECUTE ON "SYS"."SYS_GROUP" TO "MDME";

GRANT FLASHBACK ON "SYS"."INCEXP" TO "MDME";

GRANT FLASHBACK ON "SYS"."INCFIL" TO "MDME";

GRANT FLASHBACK ON "SYS"."INCVID" TO "MDME";

GRANT INDEX ON "SYS"."INCEXP" TO "MDME";

GRANT INDEX ON "SYS"."INCFIL" TO "MDME";

GRANT INDEX ON "SYS"."INCVID" TO "MDME";

GRANT INSERT ON "SYS"."INCEXP" TO "MDME";

GRANT INSERT ON "SYS"."INCFIL" TO "MDME";

GRANT INSERT ON "SYS"."INCVID" TO "MDME";

GRANT ON COMMIT REFRESH ON "SYS"."INCEXP" TO "MDME";

GRANT ON COMMIT REFRESH ON "SYS"."INCFIL" TO "MDME";

GRANT ON COMMIT REFRESH ON "SYS"."INCVID" TO "MDME";

GRANT QUERY REWRITE ON "SYS"."INCEXP" TO "MDME";

GRANT QUERY REWRITE ON "SYS"."INCFIL" TO "MDME";

GRANT QUERY REWRITE ON "SYS"."INCVID" TO "MDME";

GRANT REFERENCES ON "SYS"."INCEXP" TO "MDME";

GRANT REFERENCES ON "SYS"."INCFIL" TO "MDME";

GRANT REFERENCES ON "SYS"."INCVID" TO "MDME";

GRANT SELECT ON "SYS"."INCEXP" TO "MDME";

GRANT SELECT ON "SYS"."INCFIL" TO "MDME";

GRANT SELECT ON "SYS"."INCVID" TO "MDME";

GRANT SELECT ON "WMSYS"."WM$UDTRIG_INFO" TO "MDME";

GRANT UPDATE ON "SYS"."INCEXP" TO "MDME";

GRANT UPDATE ON "SYS"."INCFIL" TO "MDME";

GRANT UPDATE ON "SYS"."INCVID" TO "MDME";

GRANT "AQ_ADMINISTRATOR_ROLE" TO "MDME" WITH ADMIN OPTION;

GRANT "DBA" TO "MDME" WITH ADMIN OPTION;

BEGIN

dbms_resource_manager_privs.grant_switch_consumer_group(

grantee_name => 'MDME',

consumer_group => 'SYS_GROUP',

grant_option => FALSE

);

END;

BEGIN

dbms_resource_manager.set_initial_consumer_group(

user => 'MDME',

consumer_group => 'SYS_GROUP'

);

END;

-

---

When we are trying to set the DBMS settings with this new user, Console displays the error message "Unable to set current database with database server".

Please treat this as urgent and help us resolving this issue.

Regards,

RK

[Former Member]

I don't remember now by hart and I have no Oracle here but if my memory serves me right you had to set up this user in mds.ini file. Didn't you forget to do it?

[Former Member]

Hi Roman,

I checked the mds.ini file. Yhis file has "SYSTEM" user which means I should be able to use atleast "SYSTEM" Id which is not the case.

Any idea why it fails like that?

Regards,

RK

[Former Member]

I miss it now. You said that with System you're able to connect at least but the repository is invalid. But with MDME user you can't even connect? To put MDME in fact you have to change it in the ini file. If you want to fight the invalid problem did you try after creating\unarchiving the repository just to restart MDM server? I understand that the server is up and runnig but the repository is invalid. Is it true?

[Former Member]

Hi Roman,

There are two issues.

1. We tried with user - "SYSTEM". With this user when the repository is unarchived, the final status is shown as "Invalid". Same is the case when we try to create a repository. At this stage I tried to unmount the repository and mount the repository and then tried to load the repository. But the loading of repository goes for ever. I am just trying to unarchive the standard vendor repository. I also tried stopping the server and starting again... but of no use.

The log is as follows:

Report of type "Preload" says that "Preload Aborted with Error (2181234944: Unhandled Exception)."

2. Because the above userwe had issues, we tried to create another user with equal previlages of "SYSTEM" and use that for unarchiving.

For me it is enough if I can load the repository properly.

Regards,

Rajani Kumar

Message was edited by: Rajani Kumar

[Former Member]

Sounds like a bug anyway:-(

1. Try after getting the Invalid status just to restart the console. Don't stop or unload the server or the repository. Though the chances are low I'd give it a try.

2. To try another user you have to change it in the ini file. But apparetnly SYSTEM user is not the problem since you can conntect to the database.

[Former Member]

Hi,

Tried restarting the console. But, that is also of no use. One strange thing is, when I try to loadthe repository, the status in the right grid changes as follows:

"Loading Checking imageids.."

and then it fails to load.

Any clue?

Regards,

Rajani Kumar

[Former Member]

Now my creativity is exosted. There was a bug with updating status in the console while repository was loading. So it was getting stuck but if you waited a bit and simply restartd the console it would show an OK status. I thought your case is similar.

Can you create a new repository? Not to unarchive one.

[Former Member]

Hi Roman,

Even I am running out of ideas and decided to log OSS message for this. Thanks for your help.

Regards,

Rajani Kumar