Output of Oracle8i "deployejb" tool

Question

Hi,
To deploy the EJB successfully, Oracle recommends that we deploy their Sample EJB's, which ships with Oracle8i product,
before proceeding with our EJBs. This would help us verify the installation.
The sample EJB's are available at %ORACLE_HOME%\javavm\demo\demo.zip.When the demo.zip file is extracted, a
folder \examples\ejb\basic\helloworld, is created in the extracted path.The makeit.bat and runit.bat files in this folder
should run successfully to deploy the EJB in the DB.
When I attempt to execute, makeit.bat doesnot run properly.The output is pasted here for your reference.As you may notice,
ClassCastException occurs, when a call is given to deployejb, through the makeit.bat file.
C:\Oracle8i\javavm\demo\extract\examples\ejb\basic\helloworld>call deployejb -republish -temp temp -u scott -p tiger
-s sess_iiop://localhost:2481:oracle8i -descriptor hello.ejb
server.jar
Exception in thread "main" java.lang.ClassCastException: com.sun.corba.se.internal.iiop.ORB
at oracle.aurora.jndi.orb_dep.IRFinder.getObject(IRFinder.java:24)
at oracle.aurora.jndi.orb_dep.IRFinder.initialReferences(IRFinder.java:78)
at oracle.aurora.jndi.sess_iiop.SessionCtx.initialContext(SessionCtx.java:499)
at oracle.aurora.jndi.sess_iiop.SessionCtx.<init>(SessionCtx.java:35)
at oracle.aurora.jndi.sess_iiop.ServiceCtx.createSession(ServiceCtx.java:130)
at oracle.aurora.jndi.sess_iiop.ServiceCtx.login(ServiceCtx.java:295)
at oracle.aurora.server.tools.sess_iiop.ToolImpl.initializeSession(ToolImpl.java:101)
at oracle.aurora.server.tools.sess_iiop.ToolImpl.parseStdArgs(ToolImpl.java:213)
at oracle.aurora.server.tools.sess_iiop.ToolImpl.invoke(ToolImpl.java:121)
at oracle.aurora.ejb.deployment.GenerateEjb.main(GenerateEjb.java:445)
Any help/comments on this would be appreciated.
Thanks,
Sandeep

Answer 1

"Memory"  If you are trying to look at the memory usage of an OS process connected to Oracle you have an issue you need to be aware of, namely, most UNIX/Linux utilities cannot distinguish between private memory used by a process and shared memory.  Since the SGA exists in shared memory the process memory statistics can show as using huge amounts of memory and the sum of all your Oracle connected processed can far exceed the available memory because of this double counting.
HTH -- Mark D Powell --
I missed that you had posted two separate questions.  I will just answer in one.  The questions I posted were about what it is you want the script to provide you and what value each column in the display has.  I would point out that if you have issues looking at the OS level is unlikely to identify the problem in many cases.  You may not see a process with extremely high cpu or memory at the OS level.  The problem could be lock waiting or latch waiting.  You will only be able to determine this by looking in the database.  That is not to say that sometimes a problem session will not show up with high cpu only that in many cases the problem may be elsewhere.  Eventually you are going to have to look in the database at the session so why not start there.  After all top/topmonitor etc ... already exist at the OS level to find the high cpu, io, memory sessions.  To find and fix database session issues you have to eventually connect to the database and high cpu, memory, and io sessions can all be found with queries.