Enhancing Security - Expert Oracle and Java Security - page 308

@D:\app\oracle\product\11.2.0\dbhome_1\RDBMS\ADMIN\prvtmail.plb
The extension on that second script file ( plb ) should look familiar to us now. It is a wrapped
procedure.

Install DBMS_JAVA package
If you have installed Java in Oracle database before, or if you've looked at the instructions for doing so,
you may have seen a precursor step listed. It used to be that you needed to specify memory pool sizes for
java, setting java_pool_size and shared_pool_size to 150M each. This is no longer required, as of Oracle
Database 11g. These allocations are handled automatically as a part of 11g Automatic Memory
Management.
You can see the current settings for these parameters by selecting them from the database.
SELECT NAME,VALUE FROM V$PARAMETER WHERE NAME IN ('SHARED_POOL_SIZE','JAVA_POOL_SIZE');
You'll see that in 11g, these parameters are both set to 0. The required memory will be automatically
provided from the global MEMORY_TARGET and TARGET_SGA settings. Recall that when we mounted the
database we saw a report of the Total System Global Area. That is the memory that is partially available
to Java in the database.
A number of scripts are used to configure and enable the Oracle JVM. We will only be running two of
them—the ones we need for our application verification security processes. Of the five scripts generally
listed to build Java into the Oracle database, we will only execute initjvm.sql and catjava.sql . Again, our
reasoning for being selective is that we will only enable the capabilities we need, thus avoiding some
potential security weaknesses.
@D:\app\oracle\product\11.2.0\dbhome_1\javavm\install\initjvm.sql;
--@D:\app\oracle\product\11.2.0\dbhome_1\xdk\admin\initxml.sql;
--@D:\app\oracle\product\11.2.0\dbhome_1\xdk\admin\xmlja.sql;
@D:\app\oracle\product\11.2.0\dbhome_1\RDBMS\ADMIN\catjava.sql;
--@D:\app\oracle\product\11.2.0\dbhome_1\RDBMS\ADMIN\catexf.sql;
Running initjvm.sql will take a while, so take a break. After all that, it is time to close our spool log
file, so execute the SPOOL OFF command. Then you can browse the spool file for errors—it is in the
current directory from which you started SQL*Plus.
SPOOL OFF

See What's Installed
Shut down the database and restart the TNSListener and database services from the Computer
Management application (type Computer Management at the Start menu/Run command):
SHUTDOWN IMMEDIATE;
EXIT

Computer Management

Restart TNSlistener service

Start orcl instance service

Restart apver instance service