6 Replies Latest reply: Dec 12, 2005 11:08 AM by 274340 RSS

    Database startup error message

    274340
      Hi Guys,
      When I startup my Database, I always see this error message printed in the trace file:

      Error in executing triggers on database startup
      *** 2005-12-09 11:12:42.817
      ksedmp: internal or fatal error
      ORA-00604: error occurred at recursive SQL level 1
      ORA-12663: Services required by client not available on the server
      ORA-36961: Oracle OLAP is not available.
      ORA-06512: at "SYS.OLAPIHISTORYRETENTION", line 1
      ORA-06512: at line 15
      Error in executing triggers on database startup
      *** 2005-12-09 11:12:42.869
      ksedmp: internal or fatal error
      ORA-00604: error occurred at recursive SQL level 1
      ORA-06502: PL/SQL: numeric or value error: character string buffer too small
      ORA-06512: at line 4

      I have a few questions about the above message:

      1. How can I see which database startup trigger is having this error? Is there a way to determine that?
      2. Is there a way I can disable all triggers that fire on database startup? (just like we can disable triggers on a table)
      3. Any idea what ORA-36961: Oracle OLAP is not available. means?

      Thanks
        • 1. Re: Database startup error message
          176447
          You may check the dba_triggers - trigger_body for the similar contents in the error message. You also look for triggering_event for identifying startup triggers.

          Yes. You can disable the trigger.

          OLAP is an optional product for analytical processing.

          Ashok
          • 2. Re: Database startup error message
            274340
            hey..thanks for the reply, I have checked to see if any triggers are enabled on startup from the USER_TRIGGERS

            SQL> select TRIGGER_NAME from DBA_TRIGGERS where TRIGGERING_EVENT='STARTUP';

            no rows selected

            SQL>

            But when I start my database, I again see this error message:

            Error in executing triggers on database startup
            *** 2005-12-12 05:32:40.778
            ksedmp: internal or fatal error
            ORA-00604: error occurred at recursive SQL level 1
            ORA-06502: PL/SQL: numeric or value error: character string buffer too small
            ORA-06512: at line 4


            Is there any way I can check what trigger Oracle is complaining about?

            Also, how can I disable OLAP so that I don't see the OLAP error message?

            Thanks
            • 3. Re: Database startup error message
              274340
              nevermind about the OLAP part. I took care of that by disabling OLAPISTARTUPTRIGGER and OLAPISHUTDOWNTRIGGER. But I still get this error:

              Error in executing triggers on database startup
              *** 2005-12-12 06:16:18.522
              ksedmp: internal or fatal error
              ORA-00604: error occurred at recursive SQL level 1
              ORA-06502: PL/SQL: numeric or value error: character string buffer too small
              ORA-06512: at line 4
              • 4. Re: Database startup error message
                464041
                Try to disable triggers with the below init.ora parameter to make sure that the issue is not with startup triggers

                systemtrigger_enabled = false

                To further investigate the error 6502 set the following parameters and startup the databse, you may get more information in the trace files.

                event="6502 trace name errorstack level 12"
                timed_statistics = true;
                sql_trace=true;

                Regards
                Srinath
                • 5. Re: Database startup error message
                  19426
                  Hi,
                  replace "where TRIGGERING_EVENT='STARTUP';" by "where TRIGGERING_EVENT like '%STARTUP%';"

                  you should see a result.

                  Werner
                  • 6. Re: Database startup error message
                    274340
                    Thanks for the replies. I have that sorted out. Basically, I was looking into the triggers in the SYS schema. I have the user scott assigned SYSDBA privs to that scott can do database startup/shutdown and play around with associated triggers. The offending trigger was in scott's schema, once I disabled it, it works fine.