12c on Café Com Cloud

12cR1 + Suse 12 SP2 = take a look on this post

Sat, 10 Jun 2017 22:19:15 -0300

Today I face a weird issue during a HAS 12.1.0.2 in Suse 12 SP2 for a customer.

Everything went smooth during the runInstaller, but roothas.pl failed with the follow error:

SERVER_BLA:/u01/grid/12.1.0.2 # /u01/grid/12.1.0.2/perl/bin/perl -I/u01/grid/12.1.0.2/perl/lib -I/u01/grid/12.1.0.2/crs/install /u01/grid/12.1.0.2/crs/install/roothas.pl Using configuration parameter file: /u01/grid/12.1.0.2/crs/install/crsconfig_params LOCAL ADD MODE Creating OCR keys for user ‘ora12c’, privgrp ‘dba’.. Operation successful. LOCAL ONLY MODE Successfully accumulated necessary OCR keys. Creating OCR keys for user ‘root’, privgrp ‘root’.. Operation successful. CRS-4664: Node SERVER_BLA successfully pinned. 2017/06/10 00:46:42 CLSRSC-330: Adding Clusterware entries to file ‘oracle-ohasd.service’

PRCR-1006 : Failed to add resource ora.ons for ons PRCR-1115 : Failed to find entities of type resource type that match filters (TYPE_NAME ends .type) and contain attributes CRS-0184 : Cannot communicate with the CRS daemon. 2017/06/10 00:47:04 CLSRSC-180: An error occurred while executing the command ‘srvctl add ons’ (error code 0)

2017/06/10 00:47:55 CLSRSC-115: Start of resource ‘ora.evmd’ failed

2017/06/10 00:47:55 CLSRSC-202: Failed to start EVM daemon

This PRCR-1006 drive me nuts. Turns out, after long hours digging the web + metalink + caffeine, that you need to:

vi /etc/ld.so.conf and add /lib64/noelision on top of it.

The file should be like this after vi:

SERVER_BLA:/u01/grid/12.1.0.2/crs/install# cat /etc/ld.so.conf /lib64/noelision /usr/local/lib64 /usr/local/lib include /etc/ld.so.conf.d/*.conf

And then, add the symlink on GI_HOME:

SERVER_BLA:/u01/grid/12.1.0.2/lib# lns -s /lib64/noelision/libpthread-2.22.so libpthread.so.0

And only after this run root.sh/roothas.pl. If you are reading this post problably you already executed roothas.pl ( =[ sadly). So you need to deconfigure first, execute the steps above, and then execute roothas.pl again.

After this, happiness is back =]

***Update***

When patching GI home, remove the symlink created, apply the patch, and make the symlink again.

Feedbacks are always welcome! See you around

Hang,

First impression on 12cR2 database install

Thu, 16 Mar 2017 16:00:00 -0300

Today I’ll describe my first impressions on install the new 12cR2 (available for premises on march 2017) for linux and Solaris.

Inicially I felt a little bit strange because there are only one file for database and only one for grid install (on other versions since 11gR2, there are 2 files for database and one or more for grid - depends of version that you install).

So I downloaded and install it on OEL6.8 for study purposes.

The install process is almost similar than 12cR1 process, except you need more free space to install it (at least 8 GB).

Other point, when you unzip the single file, keep careful in uncompress on a folder (for organization, because all files will be uncompress in same directory that you are).

Then I will keep study and publish some more new features! :-)

To be or not to be (lazy)

Mon, 06 Mar 2017 20:49:44 -0300

Sometimes you are an Oracle DBA just tired of perform setup ( I like to install everything from scratch…since oracle 7.3 it was always an adventure for me :) )

If you only want to download and have fun on some cool new features, a pre-installed ova is the gold medal for you..

Check out last this Jeff Smith (SQL Developer and lots of fun on his blog) here.

Its a OVA with 12.2, APEX, SQL Developer and other cool stuff :)

See you around!

12.2 on-prem available for download

Thu, 02 Mar 2017 20:27:05 -0300

Finally :)

We will post shortly about some cool new features - like online move for non partitioned tables, sharding, v$index_usage_info and more!

See you around!

Why and Why not use table recover - Oracle 12c

Fri, 24 Feb 2017 22:23:53 -0300

Today will gonna discuss about RMAN table recovery, one of new features of Oracle 12c and my personal view of this feature.

Official documentation you could found here.

Basically RMAN use the mecanism of Point in Time recovery and automates the way that we can do a recover for a single table. Before Oracle 12c we can do it manually.

Inside of this mecanism, RMAN create auxiliary instance to perform recovery, get only necessary information: RMAN restore and recover the SYSTEM, SYSAUX, UNDO tablespaces + tablespace where table resides and use a datapump (expdp and impdp - if you configurate to import this on database) to get point-in-time information.

Why use this mecanism?

Because it permitted to get the old information dropped (accidentally or not for some user, of course if you have the previous backup) without restore all database.
It very easy to use: its permitted to recover the information of tape or disk backup based. You only have the information available.
You can set the recover to import table with another name or just generate a dump.

Why not use this mecanism? (until 12cR1)

If you have index associate with required table and this index was on different tablespace, you can have some trouble.
You can’t configure options like parallelism or exclude index on datapump.