RE: cursor_sharing set to force on its own
From: Yong Huang <yong321_at_yahoo.com>
Date: Fri, 11 Apr 2008 08:06:23 -0700 (PDT)
Message-ID: <310898.94856.qm@web80603.mail.mud.yahoo.com>
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Date: Fri, 11 Apr 2008 08:06:23 -0700 (PDT)
Message-ID: <310898.94856.qm@web80603.mail.mud.yahoo.com>
Thanks Pat. You're right. There's a trigger in an application user's schema
created as "after logon on database... execute immdeiate 'alter session set
cursor_sharing=force'". After disabling the trigger, the problem is gone. The
trigger should have been created with the word "schema" instead of "database".
It takes a few seconds' thinking to realize that a regular user's trigger can have such effect on anybody's logon, just because it has the "logon on database" phrase. But it's us DBA's error because we created it.
Yong Huang
- "Elliott, Patrick" <patrick.elliott_at_medtronic.com> wrote:
> Look for a login or startup trigger that is setting this parameter.
>
>
> Pat
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
-- http://www.freelists.org/webpage/oracle-lReceived on Fri Apr 11 2008 - 10:06:23 CDT