Having system triggers disabled in regular mode of operation (that is,
not during upgrade or patch set install) is not ok in my books, so
this is NOT normal. I believe that one more step is necessary before
flipping system triggers back to enabled: running ?/rdbms/admin/utlrp.sql
to forcibly revalidate all PL/SQL modules. This should revalidate
dependencies for system triggers without them trying to kick in.
--
Vladimir Zakharychev (bob@dpsp-yes.com) http://www.dpsp-yes.com
Dynamic PSP(tm) - the first true RAD toolkit for Oracle-based internet applications.
All opinions are mine and do not necessarily go in line with those of my employer.
"Joe Fischer" <jfischer_at_insight.rr.com> wrote in message
news:3e35c721.244341003_at_news-server.insight.rr.com...
> There were some posts back in 08/2002 about getting messages
> like "ORA-04045 ORA-04045: errors during recompilation/revalidation of
> SYS.CDC_ALTER_CTABLE_BEFORE." A solution was posted about doing:
>
> -- disable system triggers
> alter system set "_system_trig_enabled"=false;
> @?/rdbms/admin/catalog
> @?/rdbms/admin/catproc
> -- re-enable system triggers
> alter system set "_system_trig_enabled"=true;
>
> This is on a 9.2 database. When I set system_trigger back to
> true, the original problem shows up whenever somebody tries to connect
> to the database. If I leave it set to false, everything seems to work
> OK. Is this normal OK?
> ---
> Joe
Received on Tue Jan 28 2003 - 03:18:38 CST
