|
|
|
![]()
| [일반] ORA-29532 xml 파일핸들링할때 권한주기 |
|
| 호석 님께서 쓴 글입니다 - 211.♡.74.31 |
읽음:4888 |
|
|
제목: How to Resolve ORA-29532 Java Permission Problems In Database
문서 ID: 공지:134280.1 유형: BULLETIN
마지막 갱신 날짜: 16-FEB-2006 상태: PUBLISHED
- 오라클 scott 계정에 xml file을 로딩할수 있도록 권한부여
SQL> grant javauserpriv to scott;
SQL> grant javasyspriv to scott;
Problem Description
-------------------
Sometimes an application running in the Oracle JVM
will fail with a java permissions error having the
following format:
(Note: Message shown below have been reformatted for easier readability.)
java.sql.SQLException: ORA-29532:Java call terminated by uncaught Java exception:
followed by a detailed error message similar to one of the following messages:
-----------
Example # 1
-----------
java.security.AccessControlException: the Permission
(java.net.SocketPermission hostname resolve)
has not been granted by dbms_java.grant_permission to
SchemaProtectionDomain(SCOTT|PolicyTableProxy(SCOTT))
-----------
Example # 2
-----------
java.security.AccessControlException: the Permission
(java.util.PropertyPermission * read,write)
has not been granted by dbms_java.grant_permission to
SchemaProtectionDomain(SCOTT|PolicyTableProxy(SCOTT))
-----------
Example # 3
-----------
java.security.AccessControlException: the Permission
(java.io.FilePermission \matt1.gif read)
has not been granted by dbms_java.grant_permission to
SchemaProtectionDomain(SCOTT|PolicyTableProxy(SCOTT))
-----------
Explanation
-----------
The java 2 permission stated in line # 2 of each of the above "Examples"
has not been granted to the user specified in line 4 of the above "Examples".
--------------------
Solution Description
--------------------
The methodology to solve this issue is identical for all java 2 permissions
cases.
1) Format a call "dbms_java.grant_permission" procedure as described below.
2) Logon as SYS or SYSTEM
3) Issue the TWO commands shown below
4) Logoff as SYS or SYSTEM
5) Retry your application
---------------
For Example # 1
---------------
1) Logon as SYS or SYSTEM
2) Issue the following commands :
a) call dbms_java.grant_permission('SCOTT',
'java.net.SocketPermission',
'hostname',
'resolve');
b) commit;
Note: Commit is mandatory !!
3) Logoff as SYS or SYSTEM
4) Retry your application
---------------
For Example # 2
---------------
1) Logon as SYS or SYSTEM
2) Issue the following commands :
a) call dbms_java.grant_permission('SCOTT',
'java.util.PropertyPermission',
'*',
'read,write');
b) commit;
Note: Commit is mandatory !!
3) Logoff as SYS or SYSTEM
4) Retry your application
---------------
For Example # 3
---------------
1) Logon as SYS or SYSTEM
2) Issue the following commands :
a) call dbms_java.grant_permission('SCOTT',
'java.io.FilePermission',
'\matt1.gif',
'read');
b) commit;
Note: Commit is mandatory !!
3) Logoff as SYS or SYSTEM
4) Retry your application
Other ORA-29532 related documents
----------------------------------
Note 142969.1 Java Stored Procedure Call External Program fails with ORA-29532
Note 1015353.102 ORA-29532: JAVA CALL TERMINATED BY UNCAUGHT JAVA EXCEPTION
Note 155517.1 ORA-29532 JAVA CALL TERMINATED BY UNCAUGHT JAVA EXCEPTION
.
|
|
|
|
|
|
