Exporting Statistics

This was surprisingly more difficult than I expected. We know that we can export stats from the dictionary to a table, and from the table to a file, and that file can be copied and imported to another database for the stats to be imported. Easy right? 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 $ sqlplus / as sysdba SQL*Plus: Release 12.


We are running a data conversion. The powers that be decided to use APIs to convert the data as they contain error checking. The problem is that they are generally designed for interactive use updating one row at a time, so they are very slow to update large batches of data. This was tuned and is getting much faster, however we noticed that there are a lot of waits on cursor: pin: S wait on X.

Crash Consistent Recovery

Problem Since Oracle 12c, you can recover a crash consistent snapshot. Oracle support note 604683.1 says how to do this. We had an issue where the recovery wanted to effectively run to the end of time, and wouldn’t ever finish. No matter how many logs were applied, it said: 1 2 3 ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below ORA-01194: file 1 needs more recovery to be consistent ORA-01110: data file 1: '/CS_SR/system/system01.

Tech 17 - Oracle 18c The Next Update

Dominic Giles drew our attention to the safe harbour statement. Anything can change between now and when the new version is released. There has been some confusion about the announcements regarding autonomous database. This is a service on top of oracle 18c. Oracle 18c is a product. Release Schedule Oracle will change its release process to release annually. Hopefully this will lead to more stable releases, as there won’t be a rush to get the new features into the current version of the database.

Tech 17 - Oracle Database 12c Release 2 - What is new in the Oracle Optimiser

The first session after lunch was Oracle Database 12c Release 2 - What is new in the Oracle Optimiser. It was taken by Nigel Baylis who is the product manager for the oracle optimiser. I was impressed by Nigel’s honesty when he talked about what worked, what didn’t and how things are being changed to correct the mistakes of the past. This is the main reason to come to user groups of course.

Tech 17 - New Indexing Features

For the last session before lunch I listened to Richard Foote talking about new index features in 12.2. Richard is well known as the Oracle Indexing expert, and so I was eager to hear what he had to say. Object name length Indexes can now have 128 character names, where before they could only be 30 characters. I expect this will make life easier where naming standards dictate long names for whatever reason.

Tech17 - Auditing the Oracle Database

The presenter was Pete Finnigan. Pete talked through a solution (PFCATK) he had developed for auditing the oracle database. This appears to be currently in development and not available for general use. He seemed inclined to release the core tool and sell a pretty front end or consultancy, but it seemed he hadn’t yet decided. The lack of anything to play with (Unless you ask for a copy of the tool and agree to install it and give feedback) made this session less interesting than it might otherwise be.

Tech 17 -The Answer to the Ultimate Question of SQL, Performance Tuning and Everything

This is second session I attended in Tech 17. It was presented by Martin Bach and David Kurtz. The answer is eDB360. The session was in two parts with a presentation by Martin, then a demo with David. Martin discussed the problems of doing a database health check, particularly for a third party company who may not actually have access to the database. It needs a standard approach, which is consistent across databases, and repeatable.