1. LOGON trigger to restrict user connections filtering USERNAME and HOST: 2. LOGON trigger to enable session tracing: 3. Trigger to capture DDL statements: 4. Trigger to capture on SERVERERROR: 5. Trigger on server shutdown: Hope these examples will help you to build triggers based on your project requirements
1. UNDO usage on the database might hit the water mark making the job to administer it tedious.Monitor who is using UNDO: 2. Script to estimate the amount of UNDO tablespace size required for the database 3. Estimate the amount of time required for a transaction to use UNDO:
Let us see how to set the listener password step wise. 1. Check the current status of the listener. 2. Security is ON but for Local OS Authentication. Now let us check the listener.ora file: 3. Now Stop the listener and configure password to the listener. 4. Let us verify the listener functionality with password: […]
Oracle strongly recommends that you run your database in automatic undo mode by leavingthe UNDO_MANAGEMENT initialization parameter set to AUTO, which is the default. In addition,set the UNDO_RETENTION initialization parameter to an interval large enough to include theoldest data you anticipate needing. For more information refer to the documentation on the UNDO_MANAGEMENT and UNDO_RETENTIONinitialization parameters […]
1. Identify who is using TEMP on Oracle database: 2. To monitor temp usage on the database(This query do not include AUTO EXTENDED size):
