Oracle 8.1.7 JVM install

[AK]

Hi,

I've recently had to take over responsibility for a number of Oracle
databases, and armed with a week of training from a certain member of
this list :) I'm embarking on solving my first little problematic issue...

I need to set up the local JVM in Oracle. Currently, the databases I
manage have a 'half baked' installation, done by my predecessor (who was
way overworked and probably just didnt have time to fix it). To start
with a clean slate, I ran rmjvm.sql as the sys user (connect sys) from
svrmgrl. This was after reading articles 105472.1 on Metalink and also
reading through some of Tom Kyte's website. The rmjvm.sql script seems
to have done its thing, in removing all java objects, so I ran the
initjvm.sql script. This init script threw the following error:

ORA-29541: class SYS.oracle/aurora/rdbms/security/PolicyTableManager
could not be resolved

So, if the script cannot find a class, does this mean that the CLASSPATH
environment variable is not set up right? I'm unsure how to work what
this CLASSPATH ought to be.

All docs I have read simply say to run initjvm.sql and then go home. I
did that, and it didnt work... so I logged a TAR on Metalink and went to
the pub. Its been a while since then, and I haven't heard back from a
Metalink analyst.

Some help would be greatly appreciated.

-Abhinav

[Van Messner]

These are the steps I follow to add Java to 8i (You didn't mention a
version).

Script 18 xxx_setup2a.sql - Call Oracle scripts for Java pieces
This script, script 18, calls a number of Oracle-supplied scripts to set up
the Java objects Oracle needs when users want to use Oracle's Java
capabilities
Run this in svrmgrl
connect internal
-- set the default tablespace for system back to normal
alter user system default tablespace SYSTEM;
-- Load the initial set of Java classes necessary to support Java, the SQLJ
compiler, JDBC runtime,
-- CORBA, ORB, EJB, the package DBMS_Java and load classes in the SYS
schema. Make
-- synonyms for the classes and define database startup and shutdown
triggers.
-- This step can take 30 minutes.
-- note that if the next step fails you MUST run rmjvm.sql to clean up
before another attempt !!!
@/ora_sw/8.1.7/javavm/install/initjvm.sql
-- Load the XML components into Jserver
-- This script also takes awhile to complete.
@/ora_sw/8.1.7/oracore/admin/initxml.sql
-- Load the XMLSQL utility (aka XSU) into the database. This utility
transforms relational data
-- XML for communication purposes
@/ora_sw/8.1.7/rdbms/admin/catxsu.sql
-- Do the JIS installation which puts in the Oracle servlet engine. This
engine works as a web server
-- This script takes awhile to complete - 30 minutes or more.
@/ora_sw/8.1.7/javavm/install/init_jis.sql
-- Turn on JAccelerator. This product is supposed to increase performance.
If you use Oracle's Java
-- features you might well wonder what things would be like without this
acceleration.
-- Note that this step can take over an hour. The install may appear to be
hung. Give it enough time to
-- work before you kill anything!!
@/ora_sw/8.1.7/javavm/install/jisja.sql
-- Add default end points to the server
@/ora_sw/8.1.7/javavm/install/jisaephc.sql
-- Load PL/SQL gateway servlet jar files into the database. This allows you
to run PL/SQL stored
-- procedures as servlets.
@/ora_sw/8.1.7/rdbms/admin/initplgs.sql
-- Install Oracle Java Server Pages functionality. This is a SUN specified
product that allows you to
-- include Java code snippets and calls to external Java components within
your HTML or XML code
-- In a typical application a JSP page will call component such as a
JavaBean to access the database
-- through JDBC.
-- This script is a relatively long-running one.
@/ora_sw/8.1.7/jsp/install/initjsp.sql
-- Load the JAccelerator classes for the JSP functionality. Jaccelerator
allows for native
-- compilation of Java code.
@/ora_sw/8.1.7/jsp/install/jspja.sql
-- Initialize the Java library needed by PL/SQL.
@/ora_sw/8.1.7/rdbms/admin/initplsj.sql
-- Load the AQ/JMS jar files into the database. Oracle's Java Messaging
Service provides a Java API
-- for Advanced Queueing based on the JMS standard.
@/ora_sw/8.1.7/rdbms/admin/initjms.sql
-- Load the RepAPI server class and its helper class into the database.
RepAPI is a runtime library
-- that enables clients to replicate data with Oracle servers.
@/ora_sw/8.1.7/rdbms/admin/initrepapi.sql
-- Load SQL, objects, extensibility and XML related Java classes into the
database.
@/ora_sw/8.1.7/rdbms/admin/initsoxx.sql
-- Configure the OSE default admin Web Service and add the set of default
end points to the server.
@/ora_sw/8.1.7/javavm/install/jisaep admin 8080 9090
This is a small test script to see whether you have problems with invalid
objects.
select owner, object_type, object_name, status
from dba_objects
where status <> 'VALID';

"AK" <a...@ak.org> wrote in message
news:QBzqb.679$_z4....@news.optus.net.au...

[Van Messner]

Sorry, you DID mention a version

"AK" <a...@ak.org> wrote in message
news:QBzqb.679$_z4....@news.optus.net.au...

[AK]

Thanks for the reply Van, the solution to this problem was not in the
script execution but rather in the resources given to the scripts.
There was plenty of conflicting information about java_pool_size, with
some sources saying that 20M or even 10M would suffice. I raised it to
50M as suggested by other sources and then things started to work. I
did not run everything you have suggested below simply because I dont
know what half of them do...

I can now successfully write a 'hello world' java program, compile it,
load it and execute it within sql...

thanks again.
Abhinav