MINI MINI MANI MO

############################################################################
#  
# Attention JAVAVM users: changing this file usually has no apparent effect!!
# Please read the Java Dev Guide or the info below to understand logging 
# control in JAVAVM. 
#  
############################################################################
# 
#     Configuring Logging in OJVM
# 
############################################################################
# 
# To enhance security of logging configuration management, and to
# support per-user logging configurations, OJVM extends the JDK Java
# Logging API in the area of logging properties lookup as described
# below.
# 
#     For details on Java Logging APIs, see
#     http://docs.oracle.com/javase/1.5.0/docs/guide/logging/index.html,
#     and specifically, 1.8 Configuration File:
#     http://docs.oracle.com/javase/1.5.0/docs/guide/logging/overview.html#1.8
# 
# Logging properties in OJVM are initialized once per session, when
# LogManager is activated in the session. The initialization described
# in LogManager API is extended with DB-resident resource lookup as
# follows.  If the "java.util.logging.config.class" property is set, the
# behavior is as in JDK. Otherwise, before trying property
# java.util.logging.config.file, OJVM inspects resource
# javavm/lib/logging.properties for being present in the current user
# schema. If present, the resource is used as LogManager's
# configuration. Otherwise, property java.util.logging.config.file is
# inspected and if specified, it is used as described in LogManager
# API. Otherwise, the resource javavm/lib/logging.properties in schema
# SYS is used. This resource is a copy of
# $(java.home)/lib/logging.properties file loaded into SYS at DB creastion
# time (javavm/install/initjvm5.sql). 
# In practical terms this means that by default, the
# LogManager behaves as if configured with file
# $(java.home)/javavm/lib/logging.properties, yet altering this file has
# no effect until the java system (or the whole DB) is re-created.
# 
# If you are not satisfied with the default settings in
# javavm/lib/logging.properties, prepare a different set of properties
# and load them up in your schema using loadjava as resource named
# 
#   javavm/lib/logging.properties
#
# For example, if your
# schema is SCOTT and your current file directory is mydir, then create
# directory javavm/lib/ under mydir and specify required properties in
# file logging.properties under mydir/javavm/lib/. Invoke loadjava from
# mydir as
# 
#   mydir% loadjava -u scott -v -r javavm/lib/logging.properties
#
# Or if your application that needs logging is uploaded from jar foobar.jar, then 
# add resource javavm/lib/logging.properties to the jar.
#
# After that, file mydir/javavm/lib/logging.properties can be
# deleted. Any session running as SCOTT will active LogManager in it
# from SCOTT-private DB-resident resource.
# 
# Logging APIs and security in OJVM: because OJVM always runs with a
# security manager, SCOTT must be granted logging permissions. This is
# required regardless of what configuration method is used. In most
# cases, the following call issued by a privileged user is sufficient:
# 
#     call dbms_java.grant_permission( 'SCOTT', 
#           'SYS:java.util.logging.LoggingPermission', 'control', '');
# 
# 

############################################################
#  	Default Logging Configuration File
#
# You can use a different file by specifying a filename
# with the java.util.logging.config.file system property.  
# For example java -Djava.util.logging.config.file=myfile
############################################################

############################################################
#  	Global properties
############################################################

# "handlers" specifies a comma separated list of log Handler 
# classes.  These handlers will be installed during VM startup.
# Note that these classes must be on the system classpath.
# By default we only configure a ConsoleHandler, which will only
# show messages at the INFO and above levels.
handlers= java.util.logging.ConsoleHandler

# To also add the FileHandler, use the following line instead.
#handlers= java.util.logging.FileHandler, java.util.logging.ConsoleHandler

# Default global logging level.
# This specifies which kinds of events are logged across
# all loggers.  For any given facility this global level
# can be overriden by a facility specific level
# Note that the ConsoleHandler also has a separate level
# setting to limit messages printed to the console.
.level= INFO

############################################################
# Handler specific properties.
# Describes specific configuration info for Handlers.
############################################################

# default file output is in user's home directory.
java.util.logging.FileHandler.pattern = %h/java%u.log
java.util.logging.FileHandler.limit = 50000
java.util.logging.FileHandler.count = 1
java.util.logging.FileHandler.formatter = java.util.logging.XMLFormatter

# Limit the message that are printed on the console to INFO and above.
java.util.logging.ConsoleHandler.level = INFO
java.util.logging.ConsoleHandler.formatter = java.util.logging.SimpleFormatter


############################################################
# Facility specific properties.
# Provides extra control for each logger.
############################################################

# For example, set the com.xyz.foo logger to only log SEVERE
# messages:
com.xyz.foo.level = SEVERE
############################################################
# Properties controling debug output for JDBC for utilities
# Refer to jdbc/demo/OracleLog.properties for more details
# Utilities need to set Handler level to ALL.
############################################################
 
oracle.jdbc.level = CONFIG
oracle.sql.level = CONFIG
#oracle.jdbc.driver.level = FINER
#oracle.jdbc.internal.level = FINE
#oracle.jdbc.oci.level = FINER
#oracle.jdbc.connector.level = FINE
#oracle.jdbc.oracore.level = FINE
#oracle.jdbc.pool.level = FINE
#oracle.jdbc.rowset.level = FINE
#oracle.jdbc.util.level = FINE
#oracle.jdbc.xa.level = FINE
#oracle.jdbc.xa.client.level = FINE
#oracle.jpub.level = FINE
#oracle.net.ns.level = TRACE_20