6.28.2013

Useful MOS notes on 12c

Here is the list of useful MOS notes on 12c:


  1. Oracle Database 12c Release 1 (12.1) Upgrade New Features [ID 1515747.1]
  2. NOTE:1520299.1 - Master Note For Oracle Database 12c Release 1 (12.1) Database/Client Installation/Upgrade/Migration Standalone Environment (Non-RAC)
  3. NOTE:1493645.1 - Oracle Database 12c Release 1 (12.1) DBUA : Understanding New Changes With All New 12.1 DBUA 
  4. NOTE:1503653.1 - Complete Checklist for Manual Upgrades to Oracle Database 12c Release 1 (12.1)
  5. Oracle Database 12c Release 1 (12.1) Upgrade New Features [ID 1515747.1]
  6. RMAN RECOVER TABLE Feature New to Oracle Database 12c [ID 1521524.1]
  7. How to Merge Multiple Partitions in Oracle 12C [ID 1482263.1]
  8. How to Drop/Truncate Multiple Partitions in Oracle 12C [ID 1482264.1]
  9. How to Create Interval-Reference Partitioned Tables in Oracle 12c [ID 1519042.1]


Oracle Database 12c Technology Day worldwide

Oracle quotes that 12c comes with more than 500 new features. Join the Oracle technology day event to learn firsthand how the new multitenant architecture make it easy to deploy and manage database clouds.

You will learn the following:


    • Simplify database consolidation
    • Automatically compress and tier data
    • Improve application continuity
    • Redact sensitive data
Why waiting, select your city and enroll for the event now on http://www.oracle.com/us/corporate/events/database-12c-technology-day/index.html




6.26.2013

Upgrade, Migrate and Consolidate to Oracle Database 12c slide deck by Mike Dietrich

Mike and his team did it once again. This time its 12c Upgrade/Migrate.

Here is the excerpt from his blog:

with (sorry, we've did it again!) over 500 slides covering:
  • The brand new Parallel Upgrade including new Pre/Post-Upgrade-Fix-Ups
  • The new Full Transportable Export/Import Feature
  • Obviously Oracle Multitenant, which got talked about a lot as Pluggable Databases or Container Databases before
  • Plenty of new parameters, cool and very helpful features and much more ...
  • Download the slides Upgrade, Migrate and Consolidate to Oracle Database 12c
And of course, the slide deck will see some updates in the near future :-)
-Mike

You can download the slide deck on:

https://blogs.oracle.com/UPGRADE/entry/finally_oracle_database_12c_is

6.25.2013

Oracle Database 12c - download on https://edelivery.oracle.com/

Although Oracle yet to announce the release of Oracle Database 12c publicly, if you have got MOS login credentials, download Oracle Database 12c for Linux on E-Delivery site.

https://edelivery.oracle.com

However, the documentation is not open yet.

Enjoy and good luck with all your testing!!!!!!!!!


Update:

After few hours, Oracle now made the software/documentation available on OTN too for Linux/Solaris.

Software : http://www.oracle.com/technetwork/database/enterprise-edition/downloads/index.html
Documentation : http://www.oracle.com/pls/db121/homepage

Anticipating tons of blogs, posts, papers about 12c from you people.


6.16.2013

ORA-01115: IO error reading block from file (block # ) - a list of common causes

There are situations when a single issue could arise for different reasons. Will list out some of the common causes of an 'ORA-01115: IO error reading block from file  (block # )' error over here.

Typically, when Oracle failed to read a data block from an open data file, it throws an ORA-01115 error.  Before you suspect any database issue, it is advised to have a close look at the error message stack presented before and after the ORA-01115 error in the database alert.log file. As there could be a different reason for this error when comparing the same error over the net or previous occurrence, it is pretty important that you isolate the issue looking at the other error messages represented along with this error.

One of the following would be the most common reasons for the error:
  • the datafile in the context is OFFLINE
  • database might have lost communication with the underlying ASM instance
  • caused by any hardware problems
  • physical data block corruption at the storage level
  • a Oracle BUG
We have encountered similar issue in one of our RAC databases due to communication loss with the underlying ASM instance. Here is the alert.log entries:

WARNING: ASM communication error: op 0 state 0x0 (15055)
ERROR: direct connection failure with ASM
ERROR: paging ASM fault extent map failed gn=28 fn=256 extet=715
Errors in file /u00/app/oracle/diag/rdbms/xxxDB/xxxDB2/trace/xxxDB2D2_ora_21886.trc:
ORA-00704: bootstrap process failure
ORA-01115: IO error reading block from file  (block # )
ORA-01110: data file 1: '+DG_DATA/xxxdb/datafile/system.256.680619545'
ORA-15055: unable to connect to ASM instance
ORA-15055: unable to connect to ASM instance
ORA-00020: maximum number of processes (100) exceeded
ORA-00704: bootstrap process failure
ORA-01115: IO error reading block from file  (block # )
ORA-15055: unable to connect to ASM instance
ORA-15055: unable to connect to ASM instance
ORA-00020: maximum number of processes (100) exceeded
Error 704 happened during db open, shutting down database
USER (ospid: 21886): terminating the instance due to error 704
Instance terminated by USER, pid = 21886



In a nutshell, you must examine the error stack message when you encounter similar issue to diagnose the real cause of the problem.

NOTE: I welcome your inputs, additions and you want to share your experience on this issue.

6.13.2013

Rejoining a node to a 2 node cluster on Windows Platform - Yet another learning experience

There was a situation encountered a couple of days ago where a node (second node) had to rejoin to a 2 node cluster environment on Windows 2008 platform. The Windows OS admin team rebuilt the 2 node after OS crash without DBAs being informed and requested the DBA team to rejoin the node to the existing cluster. Although the second node was clean, after the rebuilt, it wasn't properly removed from the cluster.

When addNode.bat procedure was initiated on the node 1, it failed with the following errors:

Error ocurred while retrieving node numbers of the existing nodes. Please check if clusterware home is properly configured.
SEVERE:Error ocurred while retrieving node numbers of the existing nodes. Please check if clusterware home is properly configured.


The error string doesn't yield any obvious reason of failure. And the following has been reported in the addnode_action*.logs:

Node is okay
--------------------------------------------------------------------------
INFO: Setting variable 'REMOTE_CLEAN_MACHINES' to 'xxxxxdb2'. Received the value from a code block.
INFO:  cannot initialize cluster interface skgxn error number 1311719766   operation skgxncin   location forced vacuo Could not initialize cluster
INFO: Vendor clusterware is not detected.
INFO: Error ocurred while retrieving node numbers of the existing nodes. Please check if clusterware home is properly configured.
SEVERE: Error ocurred while retrieving node numbers of the existing nodes. Please check if clusterware home is properly configured.
INFO: User Selected: Yes/OK

Both the reasons misleading in my cause though. I have verified and ensured that the cluster home is properly set before executing the addNode.bat procedure. However, the other error  'INFO:  cannot initialize cluster interface skgxn error number 1311719766   operation skgxncin   location forced vacuo Could not initialize cluster' caught my attention. Upon a little research over the net and My Oracle Support (MOS), it takes and guides me to another direction. One of the metalink  notes mentioned that this issue causes while adding the RDBMS (RAC) home not the GI home. This is due to missing olsnodes execute. If you find lsnodes, you must replace it with olsnodes and re-try the addNode.sh procedure. Fortunately, in our case, the olsnodes executable exists in GI and RAC homes.


Since the node wasn't removed properly, I wanted to have a look at the inventory to verify about the current nodes list. I found that the inventory still has the entry about two nodes. What all I have do was update the inventory (which is usually a post delete note step) and ensure only one node is listed. I did update the inventory with one node for GI and RDBMS homes. After updating the inventory, the addNode.bat procedure went smoothly and managed to add (rejoin) the node succesfully.


The bottom line is, in most circumstances, the errors reported doesn't give the right direction. Hence, it is pretty important that you review different logs, understand the history and sometimes need to think out-of-the box.