Oracle Data Miner Repository Version - You can find the repository version by running the query shown in Determining the Status and Version of the Repository. Oracle Data Miner Extension - When you select the SQL Developer Help menu, then in the Extensions tab you can view the Oracle Data Miner version number. SQL Developer - When you select the SQL Developer Help menu, then in the About tab you can view the build and version number of Oracle SQL Developer. The version numbers shown in the columns of the table are described as follows: The version number combinations that are supported in each release are listed in Table A-1. When you evaluate how to address the errors shown in Figure A-1 and Figure A-2, you must take several version numbers into account. Feel free to download this report from there (right-click and “save as” then, in SQLDev’s reports tab, right-click on the “User Defined Reports” folder and select “Open Report”).Īnd if you’d like to see more features in this report, feel free to have your say in the comments below.Figure A-2 Newer Oracle Data Miner Repository Errorĭescription of "Figure A-2 Newer Oracle Data Miner Repository Error" This report is available for download in my SQL Developer Repository on GitHub. (It seems that you cannot change the super small font size in the html window. Go vote for my enhancement request at SQL Developer Exchange) Here’s how it looks when only active LongOps are shown and the SQL Monitor (html) child tab is selected: So check out the SQL behind the report(s) and fit them to your purpose. I’ve commented out some filters or additional columns in this report, mainly for compatibility with older versions of Oracle. The Flash report is equivalent to the monitoring feature in Oracle Enterprise Manager and has many nitty-gritty extras, but it needs an internet connection to download the embedded renderer from Oracle.īeware, though, that SQL Monitor is part of the Diagnostics Pack and needs to be properly licensed! SQL Monitor: Live SQL Monitoring report, shown either in plain text, html or html with embedded Flash animation.It shows all child cursors and cumulative statistics for this sql_id. Explain Plan: DBMS_XPLAN output for the sql_id associated with the selected LongOp.Idle waits are pushed down to the end of the list. Wait Summary: The waits for this specific session, longest wait times on top.Session Detail: Everything v$session can show about the session running the selected LongOp.SQLDev” Jeff Smith described its usage in his article “ SQL Developer Query & Grid Tricks“, so I don’t need to dive deeper here. SQLDev’s gauge feature comes in quite handy as a progress bar for this report. The unit of “Work” is defined separately and shown in the message – it can be amongst others “tables”, “indexes”, “blocks” and so on. The main SQL of this report basically reads from v$session_longops which contains information about the session id, the sql_id associated to this LongOp, the work done so far, the total work expected as well as elapsed and estimated remaining time. “Wait a minute”, you might say, “there’s already the session report in SQL Developer’s standard reports that shows Session_LongOps”! – and you’re right, it’s been integrated in SQLDev for quite some time.īUT: I wanted to view the LongOps from a different perspective: To find out what’s taking so long in the database generally, it would be better in my humble opinion to start with ALL LongOps and drill down from there. Today here’s a shorter post about my experiments with Oracle SQL Developer’s user-defined reports: A report on all long running operations (“LongOps”) with details on session wait events, explain plans and live SQL monitoring.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |