Teamwork Challenges - One of the newer guys on the team asked our project manager for some info. He needed to figure out how to get his scripts logging in to run unattended. Th...
Now an object you compile into the database will also have an entry in USER_OBJECTS. That is also familiar territory. But there is also a USER_OBJECT_SIZE view. I bet you can figure out what that view tells you. Now other views hold object information of a certain kinds. Your triggers are shown in USER_TRIGGERS, and your procedures in USER_PROCEDURES. But have you ever heard of the view USER_TRIGGERS_COLS? Me neither. Looks like it maps triggers to the table/columns they use.
I have never queried USER_ERRORS directly. I just type SHOW ERRORS in SQL*Plus. To do some source code analysis, it looks like I might check out USER_DEPENDENCIES, USER_ARGUMENTS, or USER_IDENTIFIERS. Looks like I got some homework to do. If I find anything of use, I will definitely share it.
I had heard about the V$SESSTAT view before. But I had not used it before and did not even know how to use it. This important view will help you determine what resources are being used. Yessir good stuff. You should really check out the Artical in the Nov/Dev 2012 Oracle magazine. Perhaps it is online somewhere. The title was "Beginning Performance Tuning: Diagnose the Past". Good luck peeps.