While creating a BPM project simulation in the JDeveloper 12c IDE, I noticed some differences in behavior as opposed to 11g. Although the functionality is mostly unchanged, the UI is different. Most of them are more intuitive, but you might want to check them out and save some time.
Simulations are not always listed by default in the BPM project navigator. You can add them by right-clicking on the project, select New … | From (more...)
I keep thinking I’m moving forward with this Oracle database 12c stuff, but around every corner there is another surprise. A few days ago I was setting up a demo for Transparent Data Encryption (TDE) in 12c using my existing articles (10g, 11g). That’s when I noticed things had changed, so I had to use an 11g instance for the demo and make a note to revisit TDE for 12c…
Yeah, it’s indeed true and official. So if you still haven’t started reading and learning Multitenant architecture introduced in 188.8.131.52 and enhanced in 184.108.40.206, it’s high time that you start doing it. Not because that it’s new but because the old architecture you are familiar with, it’s officially on the verge of extinction.
A recent thread on the OTN database forum supplied some code that seemed to show that In-memory DB made no difference to performance when compared with the traditional row-store mechanism and asked why not. (It looked as if the answer was that almost all the time for the tests was spent returning the 3M row result set to the SQL*Plus client 15 rows at a time.)
The responses on the thread led to the question: (more...)
Oracle Database 12c brings us many new features including: the long needed ability to run OPatch and query the patch software installed in the Oracle Home programatically through SQL using the new DBMS_QOPATCH package.
If you’re a DBA working in an environment where patching consistently among databases is important, this is a welcomed enhancement. Sometimes one-off critical bug fix patches are important in the environment. Other times regular and consistent application of the quarterly (more...)
The replicat process is the apply process within the Oracle GoldenGate environment. The replicat is responsible for reading the remote trail files and applying the data found in cronilogical order. This ensures that the data is applied in the same order it was captured.
Until recently there was only one version of a replicat, that version was the classic version. As of 220.127.116.11, there are now three distinct versions of a (more...)
The Data Pump group is an secondary extract group that is used to help send data over a network. Although a data pump is another extract group, don’t confuse it with the primary extrat group. The main purpose of the data pump extract is to write the captured data over the network to the remote trail files on the target system.
Note: if the data pump is not confgured then the primary extract group (more...)
The extract process of Oracle GoldenGate is used to perform change data capture from the source database. The extract can be used to read the online transaction log (in Oracle the online redo logs) or the associated archive logs. The data that is extracted from the source database is then placed into an trail file (another topic for a post) for shipping to the apply sided.
To configure an extract process there needs to (more...)
There are many different ways of monitoirng Oracle GoldenGate; I have posted about many of these in earlier blog posts. Additionally, I have talked about the different ways of monitoring Oracle GoldenGate at a few conferences as well. (The slides can be found on my slideshare site if wanted). In both my blog and presentations I highlight many different approaches; yet I forgot one that I think is really cool! This one was shown to (more...)
I've been having a bit of a play with the Oracle 12c database over the past few days and I thought I'd mention a gotcha I encountered.
Of course, oracle-base is a great place to start for clear & concise information on new features and I was trying out some of the WITH clause enhancements (a.k.a. subquery factoring clause). As a developer I'm pretty excited about these in particular.
Recently we came across a issue where our DB crashed with ORA-00338 error . Errors in file /oracle/diag/rdbms/orcl11g/orc11g/trace/orc11g_lgwr_24118.trc: ORA-00338: log 2 of thread 1 is more recent than control file ORA-00312: online log 2 thread 1: '/oracle/oradata/orcl11g/redo02.log' LGWR (ospid: 24118): terminating the instance due to error 338 DB couldn't be restarted as it gave same errors…
Is Oracle Database Time Correct? Something Is Not Quite Right.
Oracle Database tuning and performance analysis is usually based on time. As I blogged HERE, the Oracle "database time" statistic is more interesting than simply "time spent in the database." It is the sum of CPU consumption and non-idle wait time. And Elapsed Time is the sum of all the database time related to perhaps a session or a SQL statement execution. However...