Problem with dbua with Oracle 9.2.02 on IA64 with HP-UX11.23

[Ronny Horgen]

Hi, we get an error message when we try to start dbua(database upgrade utility):

### Error Messages: ###
Exception in thread "main" java.security.AccessControlException: access denied
(java.lang.RuntimePermission setIO)
at java.security.AccessControlContext.checkPermission(Unknown Source)
at java.security.AccessController.checkPermission(Unknown Source)
at java.lang.SecurityManager.checkPermission(Unknown Source)
at java.lang.System.checkIO(Unknown Source)
at java.lang.System.setErr(Unknown Source)
at oracle.ops.mgmt.trace.Trace.enableLogging(Trace.java:751)
at oracle.ops.mgmt.trace.Trace.enableLogging(Trace.java:720)
at oracle.sysman.assistants.dbma.backend.CompManager.setLoggings(CompManager.java:3390)
at oracle.sysman.assistants.dbma.backend.CompManager.initialize(CompManager.java:297)
at oracle.sysman.assistants.dbma.ui.UICompManager.initialize(UICompManager.java:141)
at oracle.sysman.assistants.dbma.Dbma.execute(Dbma.java:90)
at oracle.sysman.assistants.dbma.Dbma.statusMain(Dbma.java:177)
at oracle.sysman.assistants.dbma.Dbma.main(Dbma.java:158)

Anyone seen the same, and do anyone have a solution? The dbca(database config assistant) works fine.

[Brian Crabtree]

Ronny,

Just to make sure, you can run 'xclock' and have it bring up a clock on the system where your DISPLAY variable is configured, correct?

Thanks,

Brian

[Jeff Schussele]

Hi,

Is this supposed to be run by root?

Rgds,
Jeff

[Steven E. Protter]

I do not know where Jeff came up with his question but I do add this.

Absolutely no database operation, or installation operation other than those specifically called for by the universal isntaller may be done by root.

If you try and start a database with root, shared memory will become locked.

You should not make root the owner of database binaries.

You should use root to install the java tools SDK,JRE, plugins that are required prior to the installation.

SEP

[Ronny Horgen]

Hi, thx for the replay's. As you can see the dbca work fine - no problem with $DISPLAY. Looks like the dbua are using an very old Java(1.1.8), and this is surly not supported on IA64. Maybe dbua is not supported on this configuration, and we have to do the upgrade manually, or do the upgrade on an PA-RISC machine and then move the converted databases.

[Brian Crabtree · Accepted solution]

There is a possible solution in metalink:

In the home directory of the Oracle user create a file
named ".java.policy" with the following contents:

grant {
permission java.security.AllPermission;
};

The following is the link to the document:
http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=FOR&p_id=330013.995

Thanks,

brian

[Jeff Schussele]

Do you feel better now SEP?
Hey sparky, anytime perms come into play, its not out of bounds to question the owning user.
Do you really think that was a question that *shouldn't* have been asked? Do you think the poster ran it as joe_user?

Jeff (Who was perfectly willing to let it go, but is always ready to stand up to any challenge)

[Ronny Horgen]

Thanks Brian! Your hint on the .java.policy did the work, and dbua is working. Very good....