More details: I ran initjvm.sql, but none of the other initialization scripts.
When applying the patch I ran all the patch scripts (including load_jis.sql, jisja.sql, initjsp.sql). Unfortunately the patch documention doesn't specify that some of them require the other init scripts to be run first. Some of these failed with errors which is (I presume) why Oracle suggested I remove java and reinstall from the beginning. All the patch documentation says is that you should check if java is installed by doing desc dbms_java Sigh. Jay Miller -----Original Message----- [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 09, 2002 2:11 AM To: Multiple recipients of list ORACLE-L Jay, My understanding is it turns off system triggers - ie logon, logoff, database startup, object drop, creation etc Whether I would allow user access would depend on if your application uses these sort of triggers. eg do you have triggers to audit object dropping / creation? Do you have DB startup triggers that run necessary packages, do you have a login triggers that (eg) sets a default schema? Note, as per another lister, I also have had problems removing JVM and re-installing it. By problems, I mean I had to drop the database and rebuild it to reload the JVM - luckily this was only in test. I opened a TAR on it but the response was over a number of months and never reached a solution. Why do you need to drop the JVM totally? Did you have JVM in your 804 database (I don't think this was possible) or have you started the install since going up to 817? Can you just continue the JVM install on from where you were up to before? Regards, Bruce Reardon -----Original Message----- Sent: Wednesday, 9 January 2002 8:21 Due to time constraints during my recent 8.0.4 -> 8.1.7 upgrade (we had a disk failure while I was doing my cold backup which delayed my start time from midnight to 3:30am) I was unable to finish installing the JVM (not a priority since no one is using it yet). What I need to do now is run rmjvm.sql, restart the instance with _system_trig_enabled=false, reinstall everything, and restart the database with _system_trig_enabled=true. Nothing in the documentation says that users shouldn't connect while _system_trig_enabled=false. I opened a TAR with Oracle and the person told me that I'd "probably" be fine so long as I wasn't running auditing or certain security programs. I'm uncomfortable with that "probably". Can anyone here confirm or deny problems with allowing user access and DML while _system_trig_enabled is set to false? What exactly is this parameter doing? Thanks! Jay Miller -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Reardon, Bruce (CALBBAY) INET: [EMAIL PROTECTED] Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists -------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Miller, Jay INET: [EMAIL PROTECTED] Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists -------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
