Re: ORA-03113 when executing the initjvm script

2001-10-02 Thread Beatriz Martínez Jiménez
Thanks, christoffer, finally I have solved this and it works. The parameters set I have now, is the following: shared_pool_size 68157440 (size in bytes ) shared_pool_reserved_size 3407872 large_pool_size 614400 java_pool_size 5250 java_soft_sessionspace_limit 0

ORA-03113 when executing the initjvm script

2001-10-01 Thread Beatriz Martínez Jiménez
Hello all of you, I get the ORA-03113 (end-of-file on communication channel) error when I execute the initjvm script. This script is needed to use utl_smtp package. Here is the output I get: *** ERROR: ORA-03114: not connected to ORACLE create or replace java system; * ERROR en línea 1:

Re: ORA-03113 when executing the initjvm script

2001-10-01 Thread Christian Trassens
Look in trace files. Probably you are hitting a 4030 error. If this the case, not only shared_pool_size or java_pool_size are the parameters to be increased. Also increase java_soft_sessionspace_limit or java_max_sessionspace_size. If it isn't a 4030 case, put the event to get the errorstack of

RE: ORA-03113 when executing the initjvm script

2001-10-01 Thread Christopher Spence
I notice this happens when you don't have enough rollback space. You may want to go through and check back and see what the original error was. You may want to increase your SP a little and decrease your JP a little. Although it is recommended to have SP: 20M JP: 30M for the install, 90M of

RE: ORA-03113 when executing the initjvm script

2001-10-01 Thread K Gopalakrishnan
Chris, Basically the error 3113 is bit different from the other errors. Most of the errors (if not all ORA errors other than 3113 and 1041 I think) are generated from rdbms kernel where as 3113 is generated from the client side, You won't be able to get an error stack trace or

RE: ORA-03113 when executing the initjvm script

2001-10-01 Thread Jamadagni, Rajendra
Gopal, I have tried it many times (dumping errorstack at level 3 on 3113) but somehow it didn't give the analyst any clue. I don't know why ... and neither did he (the analyst). Of course none of my errors are related to JVM, we haven't started putting JAVA in our DB, that's for 9i