Problem with DBMS_JAVA, GRANT_PERMISSION

Question

I am having a problem running the GRANT PERMISSION procedure in the DBMS_JAVA package as user SYS on Oracle 8.1.6. on Windows 2000.
I ran the INITJVM script and the package DBMS_JAVA exists, and contains many more procedures than I can access.
i.e. I can see the following procs/functions:
PROCEDURE register_ep;
PROCEDURE delete_ep;
PROCEDURE server_startup;
etc. thru:
-- debugging interface --
procedure start_debugging(host varchar2, port number, timeout number);
procedure stop_debugging;
procedure restart_debugging(timeout number);
However, I cannot access the rest of the procs/functions in the package header:
procedure export_source(name varchar2, schema varchar2, blob BLOB)
as language java name
'oracle.aurora.rdbms.ExportSchemaObjects.exportSource(java.lang.String, java.lang.String, oracle.sql.BLOB)';
procedure export_source(name varchar2, blob BLOB)
as language java name
'oracle.aurora.rdbms.ExportSchemaObjects.exportSource(java.lang.String, oracle.sql.BLOB)';
procedure export_source(name varchar2, schema varchar2, clob CLOB)
as language java name
'oracle.aurora.rdbms.ExportSchemaObjects.exportSource(java.lang.String, java.lang.String, oracle.sql.CLOB)';
etc. Thru.
procedure grant_permission(
grantee varchar2, permission_type varchar2,
permission_name varchar2, permission_action varchar2,
key OUT number)
as language java name
'oracle.aurora.rdbms.security.PolicyTableManager.grant(
java.lang.String, java.lang.String, java.lang.String,
java.lang.String, long[])';
-- similar to grant except create a restrict row.
procedure restrict_permission(
grantee varchar2, permission_type varchar2,
permission_name varchar2, permission_action varchar2,
key OUT number)
as language java name
'oracle.aurora.rdbms.security.PolicyTableManager.restrict(
java.lang.String, java.lang.String, java.lang.String,
java.lang.String, long[])';
... etc. Thru the rest of the package header. These procedures and functions are defined "AS LANGUAGE JAVA NAME ..." and don't seem to work properly.
Any assistance is greatly appreciated!!!!!
Thanks,
Jim
null

Answer 1

I have investigated the problem a little further. During generation of the dump file, the file is writable of course. It changes to read-only when the following function is called:
dbms_datapump.detach(l_dp_handle);
However the documentation on detach (http://download-west.oracle.com/docs/cd/B14117_01/appdev.101/b10802/d_datpmp.htm#997383) says nothing about this behaviour. So I guess that my problem is just caused by a bug in the oracle server.
Best regards
Niels Dybdahl