Be the first to like this
Every developer knows the problem. An application doesn't do what it should and the existing logging output doesn't help. Usually, the presumed defective program area is iteratively extended by further logging calls to locate the error. If this is of no use, a colleague is called in. Maybe he has an idea. In such cases I recommend using the PL/SQL debugger. The debugger not only helps to find the error faster but is also an excellent tool to display the context of a concrete use case and to better understand the program.