: of course, the trace 10046 per se will give to you performance measures for ALL the SQL executed in the session being traced - if this is useful to you, use this information, too. With this, you get the names of them and could compile all of them in DEBUG mode, and later debug them with SQL Developer, TOAD or whatever tool you want to use. If your session time zone is not US/Central (-06:00), alter your session to Central time: 16. Set the following session parameters to enable query rewrite: 15. ![]() ![]() ALTER SESSION SET QUERYREWRITEENABLED: 12. If you donĀ“t know the name / the list of all procedures being called by this "SAVE" routine (not a faintest idea about what it can be, but matters not), an option could be star SQL TRACE (event 10046) in the session execution the "SAVE" routine - with this, the list of executed procedures will appear in the trace file in the form : Well, for starting nothing stops you from compile in debug mode ANY PL/SQL, if you have access to the owner OR if you have admin rights/ANY privs in the database - just for security obviously you would do it in the HOMOLOGATION environment, using a COPY of the application, not directly in PROD : basic rule in Development.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |