Applying DST JVM Patch Creates Invalid JAVA DATA Objects Like JAVA$POLICY$SHARED$00000001
(Doc ID 415428.1)
Last updated on JANUARY 06, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 8.1.7.4 to 10.2.0.4 [Release 8.1.7 to 10.2]Information in this document applies to any platform.
This problem can occur on any platform.
Symptoms
After applying DST JVM patch successfully, you run query below to check invalid java objects in the database:
SQL> select object_name, object_type, owner from all_objects
where object_type like '%JAVA%' and status <> 'VALID' and owner='SYS';
This query returns several invalid objects as shown below:
OBJECT_NAME OBJECT_TYPE OWNER
----------- ----------- -----
JAVA$POLICY$SHARED$00000001 JAVA DATA SYS
JAVA$POLICY$SHARED$00000002 JAVA DATA SYS
JAVA$POLICY$SHARED$00000003 JAVA DATA SYS What is the impact of these invalid objects and what action do you need to take to resolve this ?
Changes
Applying DST JVM patch and running post install steps.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |