[mnlv00]

Hi,
DBA.ADMIN ROLE IS SET TO EXTERNAL, INSTEAD OF ADMIN - HOW TO SET BACK TO ADMIN?

Oracle reco us to do these
1) Make sure O7_DICTIONARY_ACCESSIBILITY is set to TRUE. It was set to FALSE. I changed to TRUE.

2) Reran the insert_security_roles.sql script.

3) update GL_USER set IS_EXTERNAL='N' where gl_user_gid
='DBA.ADMIN'

4) Recycled the DB and app

5) Trying to bring the app, it displays these errors
"cause.ERROR_CONNECTING_TO_SERVER (exception=null, user=DBA.ADMIN)". Message in the logs (glog.exception.log, glog.app.log) when attempting to log in as DBA.ADMIN indicate "oracle.oc4j.rmi.OracleRemoteException: DBA.ADMIN is not allowed to call this EJB method" (complete message text in the attached file).

What am I missing ? PL help
TIA
Mohan

[nick.polites]

Mohan,

If you didn't have the O7_Dictionary_accessability set to true when you imported the database, you need to re-import the out of box OTM database dump again. You'll spend more time trying to fix what is broken in the database then to re-import the db. Make sure you follow the post import instructions in the admin guide.

Nick

[mnlv00]

Thx for the reply. Just a small clarification. The data in this db is not imported. It was a fresh install.
The way I read your solution is - reimport the out of box data again and not go thru the app install at all ?
If we had some seed data (created by our users), is there a way to save it ?
TIA
Mohan

[nick.polites]

Even a new install has to have an import of the default tablespaces and data from a database dump. Unfortunately the data that any users have in there will be lost. How long have you been running this environment with all of these problems for? This should have been detected almost as soon as you brought the instance online.