Entry Not Removed From Javasnm After Dropjava (Doc ID 1205683.1)

Last updated on JULY 05, 2017

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.1 and later
Information in this document applies to any platform.

Symptoms

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.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms