Today we are going to have to look on “Bypass the execution of the AFTER LOGON trigger“.

Problem:

You might have AFTER LOGON trigger for auditing and because of faulty logic (infinite loop) or the space in auditing table is full or some other problem connected to trigger, no users are able to connect to the database including sys users.

Solution:

This solution is applied to version 10.2.0.4 or later [Release 10.2 or later]

First, we have to Kill the database process manually to bring the database down.
Now we modify the init.ora parameter
Set parameter “_system_trig_enabled”=false

drop the offending trigger

Modify the “_system_trig_enabled” parameter to an old value (Default value is true). Remove the parameter if the parameter was absence previously in init.ora file. Then start the database normally.

Thank you for giving your valuable time to read the above information.

If you want to be updated with all our articles send us the Invitation or Follow us:

Telegram Channel: https://t.me/helporacle

Skant Gupta’s LinkedIn: www.linkedin.com/in/skantali/

Joel Perez’s LinkedIn: Joel Perez’s Profile

LinkedIn Group: Oracle Cloud DBAAS

Facebook Page: OracleHelp

 

 

About The Author

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.