Debug/ Investigation relevant Need
While working in Oracle backend, there are times when you are debugging your long package procedures or functions and you want to see the values being generated in different variables at runtime. What is the best way to get these values at run time?
Logging Related Need:
This paragraph contains the overview of solution in oracle. Solution to both requirements mentioned above is same. In order to enable logging when you want to maintain it if rollback happens, the only way is to use autonomous transaction. In this article I am going to create a mechanism which we can use to create autonomous transaction based procedure that we shall be using at all places where we want to enable logging either for debug purpose or for creating an audit log mechanism.
For this solution, we shall create a table, a sequence and a procedure. We shall insert a row in our log table whenever we need to make log of an event. This insert will be done through a procedure that will be having compiler hint of autonomous transaction. In this way our insert statement will become independent of main transaction and we shall be having in store in our log table even if any rollback happens after wards.
Create a Table: This table will contain the Log Data
Create a Sequence: This sequence we shall use to generate the auto number
This is the procedure that we shall be calling on places where we want to enable logging.
CREATE OR REPLACE PROCEDURE XX_TABLE_LOG_P (
Apps Technical Interview Questions
Oracle HRMS Interview Questions
Question of the Day
9 Steps to become Oracle Apps Consultant
Hierarchy of OLM Tables
How to create backend logging mechanism
Step to Register Discoverer Report
Steps for creating custom form in Oracle Apps
Clear Global Cache in Oracle Apps
Profile Values in Oracle Forms Personalization
2 simple Steps to make a responsibility read only