It's interesting how from time to time something happens that makes sense and seems logical afterwards, but at the time it causes a bit of a surprise. Part of the fun of working with this type of software!
A few days ago we had an incident in an Oracle DW database wheb a developer tried to load an infinitely big file from a very large source. Yeah, you got it: big-data-ish!
Suffice to say:
A recurrent question I have often heard about Hekaton objects is the following: Is an accidental deletion of the compilation files of a hekaton table on the file system irreversible and could this compromise the execution of SQL Server?
To check the SQL Server behaviour in such situation, we can perform the following test with an in-memory optimized table:
It is well known that poor performance on the standby server of a DataGuard pair can affect the performance of the primary database. This post shows an example and how to use the view GV$EVENT_HISTOGRAM to track down an issue.
The databases were 220.127.116.11 on HPUX. I had been seeing alerts from OEM to state that the standby was seeing lag_apply delays when applying redo to standby. Looking at the primary database alert log I could see the entries
Are you heading to Austin over the next few days? Come say "Howdy" at one of our SXSW events.
On Exadata (or when setting cell_offload_plan_display = always on non-Exadata) you may see the storage() predicate in addition to the usual access() and filter() predicates in an execution plan:
SQL> SELECT * FROM dual WHERE dummy = 'X'; D - X
Check the plan:
Alliances between market competitors and scientists have led some organizations to implement data-sharing tools. Whereas some executives believe that digital information should remain confidential, others are finding that collaborative efforts produce profitable results. Due to the complexity of such an operation, a number of corporations are hiring remote database support companies to connect them with other organizations.
Another day, another airport lounge – another quick note: one of the changes that appeared in 12c was a tweak to the “broadcast” distribution option of parallel queries. I mentioned this in a footnote to a longer article a couple of months ago; this note simply expands on that brief comment with an example. We’ll start with a simple two-table hash join – which I’ll first construct and demonstrate in 18.104.22.168:
With the recent release of SQL Developer 4.0.1 there has been some very minor bug fixes for Oracle Data Miner. But there has been one particular enhancement that I wanted to have a look at. This blog post will look at this new feature and how you can use it too. In the previously released version of the Oracle Data Miner tool we had a Graph Node. This is really a new feature that came with SQL Developer 4 and was available in the Early Adopter releases since July 2013.