Issue :Unable to start OTM 6.3.x instance right after the installation or migration/upgrade. Following errors has been noticed in weblogic console log under $GLOG_HOME/logs/console.logError logs from fresh installed instance:
Another piece of good news — Oracle has opened a bug for yet another anomaly I reported earlier in my blog: row-by-row processing of bulk DML when the block size on the target table is less than the default 8k. So it’s now officially bug 20039770 – “DML SLOW WITH 4K BLOCK SIZE VS 8K BLOCK SIZE”.
When you have sessions blocked on locks, you probably have all information about the waiters (they call you and anyway their waiting session is visible in v$session our ASH). But you usually need to get enough information that help to identify the blocker. Here is a query I use to get that quickly, based on V$WAIT_CHAINS
Here is the result I want to get:
Situation: Have ADF transaction processing 2 tables (a, b) data logic and committing them in same transaction.
ADF Application Transaction T1 starts
Table A, record A1 updated
Table B, new record B1 inserted --> After insert Autonomous database Trigger T1 fires
Trigger T1 logic: Based on A1 updated value, insert new Record B2 record in Table B and explicitly commit in trigger logic.
Transaction completes (commit)
I was in Munich a few weeks ago running a course on Designing Optimal SQL and Troubleshooting and Tuning, but just before I flew in to Munich one of the attendees emailed me with an example of a statement that behaved a little strangely and asked me if we could look at it during the course. It displays an odd little feature, and I thought it might be interesting to write up what I did to find out what was going on. We’ll start with the problem query and execution plan:
only in Enterprise Edition at the moment, and now available on HPUX, zLinux and AIX
I'm quickly checking the planning for DOAG these 3 days and here is the list of sessions I would like to attend.
There are still a lot of interesting ones even if my choice is limited by the language (I would like to understand German but I'm limited so sessions in English). And I've still some concurrency issues to solve because I cannot be at two places at the same time.
SQL plan Directives have been introduced in 12c. If you have scripts that check their states (and I have that as I prefer to monitor closely the features that are new) you probably have seen a difference when going from 18.104.22.168 - the first release of 12c and the only one avilable yet in Standard Edition - and 22.214.171.124 - the first patchest. I'll explain here what are the SQL Plan Directive states and how they changed.