Entry Not Removed From Javasnm After Dropjava
(Doc ID 1205683.1)
Last updated on MARCH 06, 2019
Applies to:Oracle Database - Enterprise Edition - Version 184.108.40.206 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
Oracle appears to create entries in sys.javasnm if a .properties file is loaded with a name longer than 30(?) characters.
If this object is dropped (dropjava) the corresponding entry in javasnm remains.
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