Thanks to http://www.dbaglobe.com/2010/08/drop-temporary-tablespace-hang-with-enq.html it was a simple matter to resolve the above enqueue wait on an attempt to drop a previously default temporary tablespace.Continue reading ENQ: TS – Contention
Have you ever seen the error RMAN-20033: control file SEQUENCE# too low and wondered what could be causing it?Continue reading RMAN-20033: control file SEQUENCE# too low
Sometimes, just occasionally, you find yourself as a DBA on a site where, for some strange and unknown reason, you don’t have an Entity Relationship Diagram (ERD) for the database that you are working on. You could use a tool such as
SQL*Plus (or even,
SQL Developer – if you must) to generate a list of referential integrity constraints. There has to be a better way. Continue reading Generate Entity Relationship Diagrams from a SQL Script.
(Snorkelling is not quite as in depth as a “deep dive”!)
Attempting to parse a
listener.log will probably bend your brain, but I needed to do it recently to determine which unique servers and/or desktops and/or application servers were still connecting to a database prior to that database going down for maintenance. This was an exercise in confirming that the documentation we have, is correct.
You know the score, you are running an
impdp and it looks to have hung up. You’ve watched the log file (or on screen messages) and it’s sitting at something like:
Processing object type TABLE_EXPORT/TABLE/INDEX/INDEX
TraceMiner has been updated and rewritten. Numerous bugs and foibles have been fixed.
TraceAdjust is a new, useful, utility to carry out some pre-processing on a trace file before you have to use your own weary eyes to work thorough potential Oracle performance problems! That’s why I wrote it!
TraceMiner has been updated again. Mostly bug fixes, but there’s a little enhancement too. The current release is 0.21.
I have a table with dates in, and some NULLs. Two people, on the same database, running the same
SELECT query, in the same schema, with the same privileges, get vastly differing results. Why? Fine Grained Auditing is not at play here. Continue reading Interesting Foible with Oracle Dates
I recently posted a useful
oraenv for Windows utility. This has been updated so that you can run it in batch files by passing the desired Oracle SID on the command line. Details at http://qdosmsq.dunbar-it.co.uk/blog/2016/08/oraenv-for-windows/
Having recently had to learn a whole new way of working when I took on a contract migrating a database to the Windows “cloud”, I realised that there’s no equivalent to the useful Unix
oraenv utility. I had to write my own. Give me a
bash shell any day! Continue reading Oraenv for Windows
It’s always nice to know which extra cost Oracle options are enabled, whether deliberately or silently as the result of some patching that has taken place. Continue reading Which Extra Cost Oracle Options is my Windows Server Running?
I found a broken check constraint, one that simply wouldn’t work, on a database. It was created as:
... CHECK(COLUMN_NAME IN ('Y','N',NULL)) ;
Try it yourself, it doesn’t work! Anyway, I needed to find if there were any other check constraints broken in this manner, so I did the following:
This applies to Linux, Unix as well as Windows, but affected me on a Windows 2012 Server running Oracle 126.96.36.199 Enterprise Edition.
My user on the server was an administration user, but not in the
ora_dba group. This is required to
connect / as sysdba within SQL*Plus. The SYS password had been changed recently but whoever did it, did not update the password vault. The users were urgently requiring their database be started, I was the only DBA in the office, the SYS password was unknown, and my user didn’t belong directly to the
ora_dba group. What to do? Continue reading How to Start an Oracle Database When You Are Not in the DBA Group
For no reason, after many weeks of use, RMAN suddenly cannot connect:
rman target sys/******@dbadb01 catalog ... ... RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-00601: fatal error in recovery manager RMAN-03010: fatal error during library cache pre-loading RMAN-10038: database session for channel default terminated unexpectedly