There cases where we need to ensure that large packet “address-ability” exists. This is needed to verify configuration for non standard packet sizes, i.e, MTU of 9000. For example if we are deploying a NAS or backup server across the network.

Setting the MTU can be done by editing the configuration script for the relevant interface in /etc/sysconfig/network-scripts/. In our example, we will use the eth1 interface, thus the file to edit would be ifcfg-eth1.

Add a line to specify the MTU, for example:
DEVICE=eth1
BOOTPROTO=static
ONBOOT=yes
IPADDR=192.168.20.2
NETMASK=255.255.255.0
MTU=9000

Assuming that MTU is set on the system, just do a ifdown eth1 followed by ifup eth1.
An ifconfig eth1 will tell if its set correctly

eth1 Link encap:Ethernet HWaddr 00:0F:EA:94:xx:xx
inet addr:192.168.20.2 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::20f:eaff:fe91:407/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1
RX packets:141567 errors:0 dropped:0 overruns:0 frame:0
TX packets:141306 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:101087512 (96.4 MiB) TX bytes:32695783 (31.1 MiB)
Interrupt:18 Base address:0xc000

To validate end-2-end MTU 9000 packet management

Execute the following on Linux systems:

ping -M do -s 8972 [destinationIP]
For example: ping datadomain.viscosityna.com -s 8972

The reason for the 8972 on Linux/Unix system, the ICMP/ping implementation doesn’t encapsulate the 28 byte ICMP (8) + TCP (20) (ping + standard transmission control protocol packet) header. Therefore, take in account : 9000 and subtract 28 = 8972.

[root@racnode01]# ping -s 8972 -M do datadomain.viscosityna.com
PING datadomain.viscosityna.com. (192.168.20.32) 8972(9000) bytes of data.
8980 bytes from racnode1.viscosityna.com. (192.168.20.2): icmp_seq=0 ttl=64 time=0.914 ms

To illustrate if proper MTU packet address-ability is not in place, I can set a larger packet size in the ping (8993). The packet gets fragmented you will see
“Packet needs to be fragmented by DF set”. In this example, the ping command uses ” -s” to set the packet size, and “-M do” sets the Do Not Fragment

[root@racnode01]# ping -s 8993 -M do datadomain.viscosityna.com
5 packets transmitted, 5 received, 0% packet loss, time 4003ms
rtt min/avg/max/mdev = 0.859/0.955/1.167/0.109 ms, pipe 2
PING datadomain.viscosityna.com. (192.168.20.32) 8993(9001) bytes of data.
From racnode1.viscosityna.com. (192.168.20.2) icmp_seq=0 Frag needed and DF set (mtu = 9000)

By adjusting the packet size, you can figure out what the mtu for the link is. This will represent the lowest mtu allowed by any device in the path, e.g., the switch, source or target node, target or anything else inbetween.

Finally, another way to verify the correct usage of the MTU size is the command ‘netstat -a -i -n’ (the column MTU size should be 9000 when you are performing tests on Jumbo Frames)


We are about to apply 12102 PSU1 (19392646) on a Standalone Cluster. This patch applies the patch to RDBMS home as part of opatchauto.
Here’s the output in case anyone wants to compare:

[root@ol64afd OPatch]# ./opatchauto apply -analyze /mnt/hgfs/12cGridSoftware/12102-PSU1/19392646 -ocmrf ocm/bin/ocm.rsp
OPatch Automation Tool
Copyright (c) 2014, Oracle Corporation. All rights reserved.

OPatchauto version : 12.1.0.1.5
OUI version : 12.1.0.2.0
Running from : /u01/app/oracle/product/12.1.0/grid

opatchauto log file: /u01/app/oracle/product/12.1.0/grid/cfgtoollogs/opatchauto/19392646/opatch_gi_2014-10-30_16-03-29_analyze.log

NOTE: opatchauto is running in ANALYZE mode. There will be no change to your system.

Parameter Validation: Successful

Grid Infrastructure home:
/u01/app/oracle/product/12.1.0/grid
RAC home(s):
/u01/app/oracle/product/12.1.0/database

Configuration Validation: Successful

Patch Location: /mnt/hgfs/12cGridSoftware/12102-PSU1/19392646
Grid Infrastructure Patch(es): 19303936 19392590 19392604
RAC Patch(es): 19303936 19392604

Patch Validation: Successful
Command “/u01/app/oracle/product/12.1.0/database/OPatch/opatch version -oh /u01/app/oracle/product/12.1.0/database -invPtrLoc /u01/app/oracle/product/12.1.0/grid/oraInst.loc -v2c 12.1.0.1.5” execution failed:
bash: /u01/app/oracle/product/12.1.0/database/OPatch/opatch: No such file or directory

For more details, please refer to the log file “/u01/app/oracle/product/12.1.0/grid/cfgtoollogs/opatchauto/19392646/opatch_gi_2014-10-30_16-03-29_analyze.debug.log”.

Apply Summary:

Following patch(es) failed to be analyzed:
GI Home: /u01/app/oracle/product/12.1.0/grid: 19303936, 19392590, 19392604
RAC Home: /u01/app/oracle/product/12.1.0/database: 19303936, 19392604

opatchauto failed with error code 2.
[root@ol64afd OPatch]#

Need to copy 12.1.0.2.1 OPatch into Grid_HOME and DB_HOME. Now re-run

[root@ol64afd OPatch]# ./opatchauto apply -analyze /mnt/hgfs/12cGridSoftware/12102-PSU1/19392646 -ocmrf ocm/bin/ocm.rsp
OPatch Automation Tool
Copyright (c) 2014, Oracle Corporation. All rights reserved.

OPatchauto version : 12.1.0.1.5
OUI version : 12.1.0.2.0
Running from : /u01/app/oracle/product/12.1.0/grid

opatchauto log file: /u01/app/oracle/product/12.1.0/grid/cfgtoollogs/opatchauto/19392646/opatch_gi_2014-10-30_16-05-43_analyze.log

NOTE: opatchauto is running in ANALYZE mode. There will be no change to your system.

Parameter Validation: Successful

Grid Infrastructure home:
/u01/app/oracle/product/12.1.0/grid
RAC home(s):
/u01/app/oracle/product/12.1.0/database

Configuration Validation: Successful

Patch Location: /mnt/hgfs/12cGridSoftware/12102-PSU1/19392646
Grid Infrastructure Patch(es): 19303936 19392590 19392604
RAC Patch(es): 19303936 19392604

Patch Validation: Successful

Analyzing patch(es) on “/u01/app/oracle/product/12.1.0/database” …
Patch “/mnt/hgfs/12cGridSoftware/12102-PSU1/19392646/19303936” successfully analyzed on “/u01/app/oracle/product/12.1.0/database” for apply.
Patch “/mnt/hgfs/12cGridSoftware/12102-PSU1/19392646/19392604” successfully analyzed on “/u01/app/oracle/product/12.1.0/database” for apply.

Analyzing patch(es) on “/u01/app/oracle/product/12.1.0/grid” …
Patch “/mnt/hgfs/12cGridSoftware/12102-PSU1/19392646/19303936” successfully analyzed on “/u01/app/oracle/product/12.1.0/grid” for apply.
Patch “/mnt/hgfs/12cGridSoftware/12102-PSU1/19392646/19392590” successfully analyzed on “/u01/app/oracle/product/12.1.0/grid” for apply.
Patch “/mnt/hgfs/12cGridSoftware/12102-PSU1/19392646/19392604” successfully analyzed on “/u01/app/oracle/product/12.1.0/grid” for apply.

Apply Summary:
Following patch(es) are successfully analyzed:
GI Home: /u01/app/oracle/product/12.1.0/grid: 19303936, 19392590, 19392604
RAC Home: /u01/app/oracle/product/12.1.0/database: 19303936, 19392604

opatchauto succeeded.
[root@ol64afd OPatch]# ./opatchauto apply /mnt/hgfs/12cGridSoftware/12102-PSU1/19392646 -ocmrf ocm/bin/ocm.rsp
OPatch Automation Tool
Copyright (c) 2014, Oracle Corporation. All rights reserved.

OPatchauto version : 12.1.0.1.5
OUI version : 12.1.0.2.0
Running from : /u01/app/oracle/product/12.1.0/grid

opatchauto log file: /u01/app/oracle/product/12.1.0/grid/cfgtoollogs/opatchauto/19392646/opatch_gi_2014-10-30_16-07-28_deploy.log

Parameter Validation: Successful

Grid Infrastructure home:
/u01/app/oracle/product/12.1.0/grid
RAC home(s):
/u01/app/oracle/product/12.1.0/database

Configuration Validation: Successful

Patch Location: /mnt/hgfs/12cGridSoftware/12102-PSU1/19392646
Grid Infrastructure Patch(es): 19303936 19392590 19392604
RAC Patch(es): 19303936 19392604

Patch Validation: Successful

Stopping RAC (/u01/app/oracle/product/12.1.0/database) … Successful
Following database(s) and/or service(s) were stopped and will be restarted later during the session: yoda

Applying patch(es) to “/u01/app/oracle/product/12.1.0/database” …
Patch “/mnt/hgfs/12cGridSoftware/12102-PSU1/19392646/19303936” successfully applied to “/u01/app/oracle/product/12.1.0/database”.
Patch “/mnt/hgfs/12cGridSoftware/12102-PSU1/19392646/19392604” successfully applied to “/u01/app/oracle/product/12.1.0/database”.

Stopping CRS … Successful

Applying patch(es) to “/u01/app/oracle/product/12.1.0/grid” …
Patch “/mnt/hgfs/12cGridSoftware/12102-PSU1/19392646/19303936” successfully applied to “/u01/app/oracle/product/12.1.0/grid”.
Patch “/mnt/hgfs/12cGridSoftware/12102-PSU1/19392646/19392590” successfully applied to “/u01/app/oracle/product/12.1.0/grid”.
Patch “/mnt/hgfs/12cGridSoftware/12102-PSU1/19392646/19392604” successfully applied to “/u01/app/oracle/product/12.1.0/grid”.

Starting CRS … Successful

Starting RAC (/u01/app/oracle/product/12.1.0/database) … Successful

Apply Summary:
Following patch(es) are successfully installed:
GI Home: /u01/app/oracle/product/12.1.0/grid: 19303936, 19392590, 19392604
RAC Home: /u01/app/oracle/product/12.1.0/database: 19303936, 19392604


My new favorite 12c Oracle Clusterware command is the 'crsctl stat res "resource name" -dependency'

What this command does, is to provide a dependency tree structure for resource the in question.  This will display startup (default) and shutdown dependencies.  

From this we can understand the pull-up, pushdown, weak, and hard dependencies between clusterware resources 


[oracle@rac02 ~]$ crsctl stat res ora.dagobah.db -dependency
================================================================================
Resource Start Dependencies
================================================================================
---------------------------------ora.dagobah.db---------------------------------
ora.dagobah.db(ora.database.type)->
| type:ora.listener.type[weak:type]
| | type:ora.cluster_vip_net1.type[hard:type,pullup:type]
| | | ora.net1.network(ora.network.type)[hard,pullup]
| | | ora.gns<Resource not found>[weak:global]
| type:ora.scan_listener.type[weak:type:global]
| | ora.scan1.vip(ora.scan_vip.type)[hard,pullup]
| | | ora.net1.network(ora.network.type)[hard,pullup:global]
| | | ora.gns<Resource not found>[weak:global]
| | | type:ora.scan_vip.type[dispersion:type:active]
| | type:ora.scan_listener.type[dispersion:type:active]
| ora.ons(ora.ons.type)[weak:uniform]
| | ora.net1.network(ora.network.type)[hard,pullup]
| ora.gns<Resource not found>[weak:global]
| ora.PDBDATA.dg(ora.diskgroup.type)[weak:global:uniform]
| | ora.asm(ora.asm.type)[hard,pullup:always]
| | | ora.LISTENER.lsnr(ora.listener.type)[weak]
| | | | type:ora.cluster_vip_net1.type[hard:type,pullup:type]
| | | | | ora.net1.network(ora.network.type)[hard,pullup]
| | | | | ora.gns<Resource not found>[weak:global]
| | | ora.ASMNET1LSNR_ASM.lsnr(ora.asm_listener.type)[hard,pullup]
| | | | ora.gns<Resource not found>[weak:global]
| ora.FRA.dg(ora.diskgroup.type)[hard:global:uniform,pullup:global]
| | ora.asm(ora.asm.type)[hard,pullup:always]
| | | ora.LISTENER.lsnr(ora.listener.type)[weak]
| | | | type:ora.cluster_vip_net1.type[hard:type,pullup:type]
| | | | | ora.net1.network(ora.network.type)[hard,pullup]
| | | | | ora.gns<Resource not found>[weak:global]
| | | ora.ASMNET1LSNR_ASM.lsnr(ora.asm_listener.type)[hard,pullup]
| | | | ora.gns<Resource not found>[weak:global]
--------------------------------------------------------------------------------

Now the same for shutdown (pushdown) dependencies

[oracle@rac02 ~]$ crsctl stat res ora.dagobah.db -dependency -stop
================================================================================
Resource Stop Dependencies
================================================================================
---------------------------------ora.dagobah.db---------------------------------
ora.dagobah.db(ora.database.type)->
| ora.dagobah.hoth.svc(ora.service.type)[hard:intermediate]
| ora.dagobah.r2d2.svc(ora.service.type)[hard:intermediate]
--------------------------------------------------------------------------------

Why is this command and output important?  Well, in cases where a particular resource doesn't come up, you may want to understand relationship with its dependents
The reason is, if you are creating your own resource dependencies using the CRS API (formally known as CLSCRS API).

<pre>CLSCRS is a set of C-based APIs for Oracle Clusterware. The CLSCRS APIs enable you to manage the operation of entities that are managed by Oracle Clusterware. These entities include resources, resource types, servers, and server pools. You can use the APIs to register user applications with Oracle Clusterware so that the clusterware can manage them and maintain high availability. Once an application is registered, you can manage, monitor and query the application's status.  The APIs allow you to use the callbacks for diagnostic logging.

</pre>

If you saw the first FlexASM blog you know we installed and configured FlexASM and a CDB plus a couple of PDBs. Also, this was Policy Managed with a cardinality of 2.  Now let's see what the configuration looks like, and we can break it down using the wonderful crsctl and srvctl tools

First let's ensure we are really running in FlexASM mode:

[oracle@rac02 ~]$ asmcmd showclustermode
ASM cluster : Flex mode enabled


[oracle@rac02 ~]$ srvctl status   serverpool -serverpool naboo
Server pool name: naboo
Active servers count: 2



[oracle@rac01 trace]$ crsctl get node role status -all
Node 'rac01' active role is 'hub'
Node 'rac03' active role is 'hub'
Node 'rac02' active role is 'hub'
Node 'rac04' active role is 'hub'



[oracle@rac01 ~]$ crsctl stat res -t
--------------------------------------------------------------------------------
Name           Target  State        Server                   State details      
--------------------------------------------------------------------------------
Local Resources
--------------------------------------------------------------------------------
ora.ASMNET1LSNR_ASM.lsnr
               ONLINE  ONLINE       rac01                    STABLE
               ONLINE  ONLINE       rac02                    STABLE
               ONLINE  ONLINE       rac03                    STABLE
               ONLINE  ONLINE       rac04                    STABLE  


You notice that we have 4 ASM listeners one on each node in the Cluster.  You'll see the process as the following on each node:


[oracle@rac01 ~]$ ps -ef |grep -i asmnet

ooracle    6646     1  0 12:19 ?        00:00:00 /u01/app/12.1.0/grid/bin/tnslsnr ASMNET1LSNR_ASM -no_crs_notify -inherit



ora.CRSDATA.DATAVOL1.advm
               ONLINE  ONLINE       rac01                    Volume device /dev/a
                                                             sm/datavol1-194 is o
                                                             nline,STABLE
               ONLINE  ONLINE       rac02                    Volume device /dev/a
                                                             sm/datavol1-194 is o
                                                             nline,STABLE
               ONLINE  OFFLINE      rac03                    Unable to connect to
                                                             ASM,STABLE
               ONLINE  ONLINE       rac04                    Volume device /dev/a
                                                             sm/datavol1-194 is o
                                                             nline,STABLE
The datavol1 ADVM resource runs on all the nodes where indicated it should run.  In this case we are seeing that RAC03 is having some issues.
Let's look into that a little later.  But I like the fact crsctl tells something is amiss here on node3
 
ora.CRSDATA.dg
               ONLINE  ONLINE       rac01                    STABLE
               ONLINE  ONLINE       rac02                    STABLE
               ONLINE  ONLINE       rac03                    STABLE
               OFFLINE OFFLINE      rac04                    STABLE


ora.FRA.dg
               ONLINE  ONLINE       rac01                    STABLE
               ONLINE  ONLINE       rac02                    STABLE
               ONLINE  ONLINE       rac03                    STABLE
               OFFLINE OFFLINE      rac04                    STABLE


The crsdata and fra disk groups resource is started on all nodes except node 4



ora.LISTENER.lsnr
               ONLINE  ONLINE       rac01                    STABLE
               ONLINE  ONLINE       rac02                    STABLE
               ONLINE  ONLINE       rac03                    STABLE
               ONLINE  ONLINE       rac04                    STABLE


We all know, as in 11gR2, that this is the Node listener.


ora.PDBDATA.dg
               ONLINE  ONLINE       rac01                    STABLE
               ONLINE  ONLINE       rac02                    STABLE
               ONLINE  ONLINE       rac03                    STABLE
               OFFLINE OFFLINE      rac04                    STABLE


The pdbdata disk groups resource is started on all nodes except node 4



ora.crsdata.datavol1.acfs
               ONLINE  ONLINE       rac01                    mounted on /u02/app/
                                                             oracle/acfsmounts,ST
                                                             ABLE
               ONLINE  ONLINE       rac02                    mounted on /u02/app/
                                                             oracle/acfsmounts,ST
                                                             ABLE
               ONLINE  OFFLINE      rac03                    (2) volume /u02/app/
                                                             oracle/acfsmounts of
                                                             fline,STABLE
               ONLINE  ONLINE       rac04                    mounted on /u02/app/
                                                             oracle/acfsmounts,ST
                                                             ABLE


ACFS filesystem resource for datavol1 is started on all nodes except node3.
But I think the following has something to do w/ it :-).  Need to debug this a bit later.  I even tried:
[oracle@rac03 ~]$ asmcmd volenable --all
ASMCMD-9470: ASM proxy instance unavailable
ASMCMD-9471: cannot enable or disable volumes



ora.net1.network
               ONLINE  ONLINE       rac01                    STABLE
               ONLINE  ONLINE       rac02                    STABLE
               ONLINE  ONLINE       rac03                    STABLE
               ONLINE  ONLINE       rac04                    STABLE
ora.ons
               ONLINE  ONLINE       rac01                    STABLE
               ONLINE  ONLINE       rac02                    STABLE
               ONLINE  ONLINE       rac03                    STABLE
               ONLINE  ONLINE       rac04                    STABLE


The Network (in my case I only have only Net1) and ONS are same as in previous versions


ora.proxy_advm
               ONLINE  ONLINE       rac01                    STABLE
               ONLINE  ONLINE       rac02                    STABLE
               ONLINE  OFFLINE      rac03                    STABLE
               ONLINE  ONLINE       rac04                    STABLE


Yep, since proxy_advm is not started on node3, the filesystems won't come online….but again, i'll look at that later
--------------------------------------------------------------------------------
Cluster Resources
--------------------------------------------------------------------------------
ora.LISTENER_SCAN1.lsnr
      1        ONLINE  ONLINE       rac02                    STABLE
ora.LISTENER_SCAN2.lsnr
      1        ONLINE  ONLINE       rac03                    STABLE
ora.LISTENER_SCAN3.lsnr
      1        ONLINE  ONLINE       rac04                    STABLE
ora.MGMTLSNR
      1        ONLINE  ONLINE       rac01                    169.254.90.36 172.16
                                                             .11.10,STABLE
ora.asm
      1        ONLINE  ONLINE       rac03                    STABLE
      2        ONLINE  ONLINE       rac01                    STABLE
      3        ONLINE  ONLINE       rac02                    STABLE


Since we have the cardinality of 3 ASM instance we have 3 ASM resources active


ora.cvu
      1        ONLINE  ONLINE       rac01                    STABLE
ora.mgmtdb
      1        ONLINE  ONLINE       rac01                    Open,STABLE
ora.oc4j
      1        ONLINE  ONLINE       rac01                    STABLE
ora.rac01.vip
      1        ONLINE  ONLINE       rac01                    STABLE
ora.rac02.vip
      1        ONLINE  ONLINE       rac02                    STABLE
ora.rac03.vip
      1        ONLINE  ONLINE       rac03                    STABLE
ora.rac04.vip
      1        ONLINE  ONLINE       rac04                    STABLE
ora.scan1.vip
      1        ONLINE  ONLINE       rac02                    STABLE
ora.scan2.vip
      1        ONLINE  ONLINE       rac03                    STABLE
ora.scan3.vip
      1        ONLINE  ONLINE       rac04                    STABLE
ora.tatooine.db
      1        ONLINE  ONLINE       rac01                    Open,STABLE
      2        ONLINE  ONLINE       rac02                    Open,STABLE


As we stated above, I specified a Policy Managed database with cardinality of 2, so I have 2 database instances running
--------------------------------------------------------------------------------

Here's some other important supporting info on FlexASm:


[oracle@rac02 ~]$ srvctl config asm -detail
ASM home: /u01/app/12.1.0/grid
Password file: +CRSDATA/orapwASM
ASM listener: LISTENER
ASM is enabled.
ASM instance count: 3
Cluster ASM listener: ASMNET1LSNR_ASM


[oracle@rac02 ~]$ srvctl status  filesystem
ACFS file system /u02/app/oracle/acfsmounts is mounted on nodes rac01,rac02,rac04


ANd here's what the Database has to say about FlexASM

NOTE: ASMB registering with ASM instance as client 0x10001 (reg:1377584805)
NOTE: ASMB connected to ASM instance +ASM1 (Flex mode; client id 0x10001)
NOTE: ASMB rebuilding ASM server state
NOTE: ASMB rebuilt 2 (of 2) groups
SUCCESS: ASMB reconnected & completed ASM server state


So for the interesting part:
If you notice that ASM is not running node 4:
[oracle@rac02 ~]$ srvctl status  asm -v

ASM is running on rac01,rac02,rac03
[oracle@rac02 ~]$ srvctl status  asm -detail
ASM is running on rac01,rac02,rac03



So, how does a client (ocrdump, rman, asmcmd, etc..) connect to if ASM if there is no ASM on that node.  Well let's test this using asmcmd on node4.  You notice that a pipe is created, a connect string is generated and passed to ASMCMD to connect remotely to ASM2 on node2!!!!


22-Sep-13 12:54 ASMCMD Foreground (PID = 14106):  Pipe /tmp/pipe_14106 has been found.
22-Sep-13 12:54 ASMCMD Background (PID = 14117):  Successfully opened the pipe /tmp/pipe_14106
22-Sep-13 12:54 ASMCMD Foreground (PID = 14106):  Successfully opened the pipe /tmp/pipe_14106 in read mode
NOTE: Executing kfod /u01/app/12.1.0/grid/bin/kfod op=getclstype..
22-Sep-13 12:54 Printing the connection string
contype = 
driver = 
instanceName = <>
usr = 
ServiceName = <+ASM>
23-Sep-13 16:23 Successfully connected to ASM instance +ASM2
23-Sep-13 16:23 NOTE: Querying ASM instance to get list of disks
22-Sep-13 12:54 Registered Daemon process.
22-Sep-13 12:54 ASMCMD Foreground (PID = 14106):  Closed pipe /tmp/pipe_14106.



Due to so many people asking me other methods besides SQLplus for provisioning PDBs; such as OEM, DBCA, etc. In this blog entry I’ll DBCA, just because its simple to show. As I mentioned in my last PDB blog,
the installer DBCA (initial DBA invocation) looks different than the subsequent (post initial db creation).

The main DBCA screen shows the following pages. We will choose Manage Pluggable Database

PDB12c 2013 08 20 17 46 20

Choose the CDB, Note you could have many CDBs on the same Node or RAC cluster

PDB12c 2013 08 30 17 51 59

We choose our PDB that we created in Part 1 of the blog

PDB12c 2013 08 30 17 52 39

Ahh..we gotta open the PDB first. As before:

CDB$ROOT@YODA> alter session set container=pdbobi;
Session altered.

CDB$ROOT@YODA> alter pluggable database pdbobi open;

Pluggable database altered.

or CDB$ROOT@YODA> alter pluggable database all open;

PDB12c 2013 08 30 17 54 22

Now we can Add support for and configure Database Vault. Additionally, Label Security can be configured.
It would have been nice to enable and modify Resource Manager as well other PDB tasks.
But I get the fact that this DBCA is really driven for the PDB operations (plug,unplug, create and destroy PDB).
Bulk of the PDB admin tasks are provided in EM

PDB12c 2013 08 30 18 14 54

Let’s do a new PDB creation for grins 🙂

PDB12c 2013 08 30 18 21 01

Specify the PDB name, storage location, and a default tablespace. Again, it would have been nice to specify a TEMP tablespace too, but that was left out

PDB12c 2013 08 30 18 22 26

Progress ….

PDB12c 2013 08 30 18 23 18

And Completion….Pretty Straightforward

PDB12c 2013 08 30 18 22 53


Once we have installed 12.1 Database Software, we can create the Container Database and the Pluggable Databases. In my case I did a software only install then manually executed DBCA

In this blog entry I’ll show the screens that walk-thru the configuration of the “first” database. I noticed that once DBCA is used to create the initial database, the capability and options (screens) for DBCA are different; i.e., it much more aligned to create/manage additional databases. I’ll show those screens in Part 3 of PDB

So let’s get started by executing
$ $ORACLE_HOME/bin/dbca

Rac01 2013 09 15 22 39 12

Choose Advanced mode for Policy Managed Database or use “Default Configuration”. Being a big promoter of Policy Managed Databases and since I have 4 RAC nodes (my best practice threshold to choose Policy Managed), I’ll choose, that.

Rac01 2013 09 15 22 39 44

I’ll pick a Global Database name and choose PDB option, and also option to choose how many PDBs to create (with prefix)

Rac01 2013 09 15 22 40 30

Pick a Server Pool name, I chose a cardinality of 2

Rac01 2013 09 15 22 40 58

Define the Management Options

Rac01 2013 09 15 22 41 20

Choose the Storage locations

Rac01 2013 09 15 22 43 31

Define Database Vault Owner and also the Separate Account Manager. Note the user name definitions

Rac01 2013 09 15 22 45 31

And now the finish

Rac01 2013 09 15 22 56 41


Consolidate where possible …Isolate where necessary

In the last blog I mentioned the benefits of schema consolidation and how it dove tails directly into a 12c Oracle Database PDB implementation.
In this part 2 of the PDB blog, we will get a little more detailed and do a basic walk-through, from  "cradle to grave" of a PDB.  We'll use SQlPlus as the tool of choice, next time I'll show w/ DBCA


First verify that we are truly on 12c Oracle database

SQL> select instance_name, version, status, con_id from v$instance;

INSTANCE_NAME	 VERSION	        STATUS	    CON_ID
---------------- ----------------- ------------ ----------
yoda		      12.1.0.1.0	   OPEN 		 0



The v$database view tells us that we are dealing with a CDB based database
 
CDB$ROOT@YODA> select cdb, con_id from v$database;

CDB	CON_ID
--- ----------
YES	     0


or a more elegant way:

CDB$ROOT@YODA> select NAME, DECODE(CDB, 'YES', 'Multitenant Option enabled', 'Regular 12c Database: ') "Multitenant Option ?" , OPEN_MODE, CON_ID from V$DATABASE;

NAME	  Multitenant Option ?	     OPEN_MODE	              CON_ID
--------- -------------------------- -------------------- ----------
YODA	  Multitenant Option enabled READ ONLY	                  0


There are alot of new views and tables to support PBD/CDB. But we'll focus on the v$PDBS and CDB_PDBS views:

CDB$ROOT@YODA> desc v$pdbs
 Name                            
 --------
 CON_ID                             
 DBID                                   
 CON_UID                              
 GUID                                   
 NAME                                   
 OPEN_MODE                             
 RESTRICTED                              
 OPEN_TIME                              
 CREATE_SCN                             
 TOTAL_SIZE     

CDB$ROOT@YODA> desc cdb_pdbs
 Name					  
 --------
 PDB_ID 				    
 PDB_NAME				    
 DBID					    
 CON_UID				 
 GUID						  
 STATUS 					  
 CREATION_SCN		
 CON_ID 				
                        

The SQlPlus command con_name (container name) shows the container and the con_id we are connected to:

CDB$ROOT@YODA> show con_name


CON_NAME
------------------------------
CDB$ROOT



CDB$ROOT@YODA> show con_id

CON_ID
------------------------------
1


Let's see what PDBs that are created in this CDB and their current state:

CDB$ROOT@YODA> select CON_ID,DBID,NAME,TOTAL_SIZE from v$pdbs;


    CON_ID      DBID NAME                    	     TOTAL_SIZE
---------- ---------- ------------------------------ ----------
      2   4066465523 PDB$SEED                          283115520
      3    483260478 PDBOBI                                    0


CDB$ROOT@YODA> select con_id, name, open_mode from v$pdbs;


    CON_ID NAME                   OPEN_MODE
---------- --------------------  ----------
      2    PDB$SEED                 READ ONLY
      3    PDBOBI           	    MOUNTED


Recall from part 1 of the blog series, that we created a PDB (pdbobi) when we specified the Pluggable Database Feature on install, and that a PDB$SEED got created as part of that Install process


Now lets's connect to the two different PDBs and see what they got!!  You really shouldn't ever connect to PDB$SEED, since its just used as a template, but we're just curious :-)

CDB$ROOT@YODA> alter session set container=PDB$SEED;
Session altered.


CDB$ROOT@YODA> select name from v$datafile;


NAME
--------------------------------------------------------------------------------
+PDBDATA/YODA/DATAFILE/undotbs1.260.823892155
+PDBDATA/YODA/DD7C48AA5A4404A2E04325AAE80A403C/DATAFILE/system.271.823892297
+PDBDATA/YODA/DD7C48AA5A4404A2E04325AAE80A403C/DATAFILE/sysaux.270.823892297


As you can see that PDB$SEED houses the template tablespaces -> System, Sysaux, and Undo tablespaces


If we connect back to the root-CDB, we see that it houses essentially the traditional database tablespaces (like in pre-12c days).  

CDB$ROOT@YODA> alter session set container=cdb$root;
Session altered.


CDB$ROOT@YODA> select name from v$datafile;

NAME
--------------------------------------------------------------------------------
+PDBDATA/YODA/DATAFILE/system.258.823892109
+PDBDATA/YODA/DATAFILE/sysaux.257.823892063
+PDBDATA/YODA/DATAFILE/undotbs1.260.823892155
+PDBDATA/YODA/DD7C48AA5A4404A2E04325AAE80A403C/DATAFILE/system.271.823892297
+PDBDATA/YODA/DATAFILE/users.259.823892155
+PDBDATA/YODA/DD7C48AA5A4404A2E04325AAE80A403C/DATAFILE/sysaux.270.823892297
+PDBDATA/YODA/DD7D8C1D4C234B38E04325AAE80AF577/DATAFILE/system.276.823892813
+PDBDATA/YODA/DD7D8C1D4C234B38E04325AAE80AF577/DATAFILE/sysaux.274.823892813
+PDBDATA/YODA/DD7D8C1D4C234B38E04325AAE80AF577/DATAFILE/users.277.823892813
+PDBDATA/YODA/DD7D8C1D4C234B38E04325AAE80AF577/DATAFILE/example.275.823892813



BTW, the datafiles listed in V$datafiles differs from cbd_data_files.  cdb_data_files only shows datafiles from "open" PDB, so just be careful if you're looking for correct datafile

Let's connect to our user PDB (pdbobi) and see what we can see :-)

CDB$ROOT@YODA> alter session set container=pdbobi;
Session altered.


CDB$ROOT@YODA> select con_id, name, open_mode from v$pdbs;


    CON_ID NAME                  OPEN_MODE
---------- -----------------   -----------
      3    PDBOBI                 MOUNTED


Place PDBOBI in Read Write mode.  Note, that when you create the PDB, it is initially in mounted mode with a status of NEW. 
View the OPEN MODE status of a PDB by querying the OPEN_MODE column in the V$PDBS view or view the status of a PDB by querying the STATUS column of the CDB_PDBS or DBA_PDBS view


CDB$ROOT@YODA> alter pluggable database pdbobi open;

Pluggable database altered.

or CDB$ROOT@YODA> alter pluggable database all open;



And let's create a new tablespace in this PDB


CDB$ROOT@YODA> create tablespace obiwan datafile size 500M;

Tablespace created.


CDB$ROOT@YODA> select file_name from cdb_data_files;

FILE_NAME
--------------------------------------------------------------------------------
+PDBDATA/YODA/DD7D8C1D4C234B38E04325AAE80AF577/DATAFILE/example.275.823892813
+PDBDATA/YODA/DD7D8C1D4C234B38E04325AAE80AF577/DATAFILE/users.277.823892813
+PDBDATA/YODA/DD7D8C1D4C234B38E04325AAE80AF577/DATAFILE/sysaux.274.823892813
+PDBDATA/YODA/E456D87DF75E6553E043EDFE10AC71EA/DATAFILE/obiwan.284.824683339
+PDBDATA/YODA/DD7D8C1D4C234B38E04325AAE80AF577/DATAFILE/system.276.823892813


PDBOBI only has scope for its own PDB files.  We will illustrate this further down below.



Let's create a new clone from an existing PDB, but with a new path

CDB$ROOT@YODA> create pluggable database PDBvader from PDBOBI FILE_NAME_CONVERT=('+PDBDATA/YODA/DD7D8C1D4C234B38E04325AAE80AF577/DATAFILE','+PDBDATA');
create pluggable database PDBvader from PDBOBI FILE_NAME_CONVERT=('+PDBDATA/YODA/DD7D8C1D4C234B38E04325AAE80AF577/DATAFILE','+PDBDATA')
*
ERROR at line 1:
ORA-65040: operation not allowed from within a pluggable database


CDB$ROOT@YODA> show con_name                     


CON_NAME
------------------------------
PDBOBI


Hmm…..remember we were still connected to PDBOBI.  You can only create PDBs from root (and not even from pdb$seed).  So connect to CDBROOT


CDB$ROOT@YODA> create pluggable database PDBvader from PDBOBI FILE_NAME_CONVERT=('+PDBDATA/YODA/DD7D8C1D4C234B38E04325AAE80AF577/DATAFILE','+PDBDATA');


Pluggable database created.


CDB$ROOT@YODA> select pdb_name, status from cdb_pdbs;

PDB_NAME   STATUS
---------- -------------
PDBOBI	   NORMAL
PDB$SEED   NORMAL
PDBVADER   NORMAL

And

CDB$ROOT@YODA> select CON_ID,DBID,NAME,TOTAL_SIZE from v$pdbs;

    CON_ID	 DBID     NAME                     TOTAL_SIZE
---------- ---------- -------------          -------------
	 2 4066465523 PDB$SEED                      283115520
	 3  483260478 PDBOBI                        917504000
	 4  994649056 PDBVADER                              0


Hmm……the TOTAL_SIZE column shows 0 bytes.  Recall that all new PDBs are created and placed in MOUNTED stated 

CDB$ROOT@YODA> alter session set container=pdbvader;

Session altered.

CDB$ROOT@YODA> alter pluggable database open;

Pluggable database altered.



CDB$ROOT@YODA> select file_name from cdb_data_files;

FILE_NAME
--------------------------------------------------------------------------------
+PDBDATA/YODA/E46B24386A131109E043EDFE10AC6E89/DATAFILE/system.280.823980769
+PDBDATA/YODA/E46B24386A131109E043EDFE10AC6E89/DATAFILE/sysaux.279.823980769
+PDBDATA/YODA/E46B24386A131109E043EDFE10AC6E89/DATAFILE/users.281.823980769
+PDBDATA/YODA/E46B24386A131109E043EDFE10AC6E89/DATAFILE/example.282.823980769

Viola…. size is now reflected !!

CDB$ROOT@YODA> select CON_ID,DBID,NAME,TOTAL_SIZE from v$pdbs;

    CON_ID	 DBID     NAME	             		     TOTAL_SIZE
---------- ---------- ------------------------------ ----------
	    4   994649056 PDBVADER			 		     393216000


Again, the scope of PDBVADER is to its own container files; it can't see PDBOBI files at all.  If we connect back to cdb$root and look at v$datafile, we see that cdb$root has scope for all the datafiles in the CDB database

Incidentally, that long identifier, "E46B24386A131109E043EDFE10AC6E89", in the OMF name is the GUID or Global Identifier for that PDB.  This is not the same as container unique identifier (CON_UID).  The con_uid is a local
identifier; whereas the GUID is universal. Keep in mind that we can unplug a PDB from one CDB into another CDB, so the GUID provides this uniqueness and streamlines portability.

CDB$ROOT@YODA> select name, con_id from v$datafile order by con_id


NAME                                                                                    CON_ID
----------------------------------------------------------------------------------- ----------
+PDBDATA/YODA/DATAFILE/undotbs1.260.823892155	                                             1
+PDBDATA/YODA/DATAFILE/sysaux.257.823892063                                                  1
+PDBDATA/YODA/DATAFILE/system.258.823892109                                                  1
+PDBDATA/YODA/DATAFILE/users.259.823892155                                                   1
+PDBDATA/YODA/DD7C48AA5A4404A2E04325AAE80A403C/DATAFILE/system.271.823892297                 2
+PDBDATA/YODA/DD7C48AA5A4404A2E04325AAE80A403C/DATAFILE/sysaux.270.823892297                 2
+PDBDATA/YODA/DD7D8C1D4C234B38E04325AAE80AF577/DATAFILE/example.275.823892813                3
+PDBDATA/YODA/DD7D8C1D4C234B38E04325AAE80AF577/DATAFILE/users.277.823892813                  3
+PDBDATA/YODA/E456D87DF75E6553E043EDFE10AC71EA/DATAFILE/obiwan.284.824683339                 3
+PDBDATA/YODA/DD7D8C1D4C234B38E04325AAE80AF577/DATAFILE/system.276.823892813                 3
+PDBDATA/YODA/DD7D8C1D4C234B38E04325AAE80AF577/DATAFILE/sysaux.274.823892813                 3
+PDBDATA/YODA/E46B24386A131109E043EDFE10AC6E89/DATAFILE/sysaux.279.823980769                 4
+PDBDATA/YODA/E46B24386A131109E043EDFE10AC6E89/DATAFILE/users.281.823980769                  4
+PDBDATA/YODA/E46B24386A131109E043EDFE10AC6E89/DATAFILE/example.282.823980769                4
+PDBDATA/YODA/E46B24386A131109E043EDFE10AC6E89/DATAFILE/system.280.823980769                 4


Now that we are done testing with PDBVADER PDB, we can shutdown and drop this PDB

CDB$ROOT@YODA> alter session set container=cdb$root;

Session altered.

CDB$ROOT@YODA> drop pluggable database pdbvader including datafiles;
drop pluggable database pdbvader including datafiles
*
ERROR at line 1:
ORA-65025: Pluggable database PDBVADER is not closed on all instances.


CDB$ROOT@YODA> alter pluggable database pdbvader close;

Pluggable database altered.

CDB$ROOT@YODA> drop pluggable database pdbvader including datafiles;

Pluggable database dropped.


Just for completeness, I'll illustrate couple different ways to create a PDB

The beauty of PDB is not mobility (plug and unplug), which we'll show later, but that we can create/clone a new PDB from a "gold-image PDB" .  That's real agility and a Database as a Service (DbaaS) play. 


So let's create a new PDB in a couple of different ways.

Method #1: Create a PDB from SEED
CDB$ROOT@YODA> alter session set container=cdb$root;


Session altered.

CDB$ROOT@YODA> CREATE PLUGGABLE DATABASE pdbhansolo admin user hansolo identified by hansolo roles=(dba);

Pluggable database created.


CDB$ROOT@YODA> alter pluggable database pdbhansolo open;

Pluggable database altered.


CDB$ROOT@YODA> select file_name from cdb_data_files;

FILE_NAME
--------------------------------------------------------------------------------
+PDBDATA/YODA/E51109E2AF22127AE043EDFE10AC1DD9/DATAFILE/system.280.824693889
+PDBDATA/YODA/E51109E2AF22127AE043EDFE10AC1DD9/DATAFILE/sysaux.279.824693893


Notice that it just contains the basic files to enable a PDB.  The CDB will copy from the PDB$SEED the System and Sysaux tablesapces and instantiate them in the new PDB.




Method #2: Clone from an existing PDB (PDBOBI in our case)

CDB$ROOT@YODA> alter session set container=cdb$root;

Session altered.

CDB$ROOT@YODA> alter pluggable database pdbobi close;

Pluggable database altered.

CDB$ROOT@YODA> alter pluggable database pdbobi open read only;

Pluggable database altered.

CDB$ROOT@YODA> CREATE PLUGGABLE DATABASE pdbleia from pdbobi;

Pluggable database created.

CDB$ROOT@YODA> alter pluggable database  pdbleia open;

Pluggable database altered.

CDB$ROOT@YODA> select file_name from cdb_data_files;

FILE_NAME
--------------------------------------------------------------------------------
+PDBDATA/YODA/E51109E2AF23127AE043EDFE10AC1DD9/DATAFILE/system.281.824694649
+PDBDATA/YODA/E51109E2AF23127AE043EDFE10AC1DD9/DATAFILE/sysaux.282.824694651
+PDBDATA/YODA/E51109E2AF23127AE043EDFE10AC1DD9/DATAFILE/users.285.824694661
+PDBDATA/YODA/E51109E2AF23127AE043EDFE10AC1DD9/DATAFILE/example.286.824694661
+PDBDATA/YODA/E51109E2AF23127AE043EDFE10AC1DD9/DATAFILE/obiwan.287.824694669

Notice, that the OBI tablespace that we created in PDBOBI came over as part of this Clone process!!


You can also create a PDB as a snapshot (COW) from another PDB.  I'll post this test on the next blog report.  But essentially you'll need a NAS Appliannce, or any technology that will provide you with COW snapshot.
I plan on using ACFS as the storage container and ACFS RW Snapshot for the snapshot PDB.




I generally don’t get time to play with single instance ASM since I in live the RAC world so much. But I needed to quickly create a 12c PDB configuration over ASM.
If you recall from the 11gR2 tho is straightforward install and configuration of Grid Infrustructure. However, there are cases where the install/config doesn’t go smoothly. This exactly what happened in my case. Not sure if was an user error or just a 12c bug (the code is barely in the field) or combination of the two.

In any case, what this blog is going to touch on is how you recover, or rather escape from a mal-configured/messed up 12c Grid Infrastructure for Standalone Cluster install.

Since everybody loves logs and traces, I’ll walk through some of the issues. First off the, installation of the software went w/o out a hitch, its the scarey-tentative “root.sh” that went wacko

Here’s the error message from GI alert log:

OHASD starting
Timed out waiting for init.ohasd script to start; posting an alert
OHASD exiting; Could not init OLR
OHASD stderr redirected to ohasdOUT.log

Here’s the trace info from ohasd.log:

2013-08-16 13:10:47.347: [ default][357553728] OHASD Daemon Starting. Command string :reboot
2013-08-16 13:10:47.347: [ default][357553728] OHASD params []
2013-08-16 13:10:47.662: [ default][357553728]
2013-08-16 13:10:47.662: [ default][357553728] Initializing OLR
2013-08-16 13:10:47.662: [ default][357553728]proa_init: OLR Abstraction layer initialization. Bootlevel:[1]
2013-08-16 13:10:47.670: [  OCRAPI][357553728]a_init: Successfully initialized the patch management context.
2013-08-16 13:10:47.670: [  OCRAPI][357553728]a_init: Successfully initialized the OLR specific states.
2013-08-16 13:10:47.670: [  OCRAPI][357553728]a_init:13: Clusterware init successful
2013-08-16 13:10:47.670: [  OCRAPI][357553728]a_init:15: Successfully initialized the Cache layer.
2013-08-16 13:10:47.670: [  OCRRAW][357553728]proprioo: opening OCR device(s)
2013-08-16 13:10:47.670: [  OCRRAW][357553728]proprioo: Successfully opened the non-ASM locations if configured.
2013-08-16 13:10:47.670: [  OCRRAW][357553728]proprioo: for disk 0 (/u01/app/oracle/product/12.1.0/grid/cdata/localhost/pdb12c.olr), id match (1), total id sets, (1) need recover (0), my votes (0), total votes (0), commit_lsn (1), lsn (1)
2013-08-16 13:10:47.670: [  OCRRAW][357553728]proprioo: my id set: (799232119, 1028247821, 0, 0, 0)
2013-08-16 13:10:47.671: [  OCRRAW][357553728]proprioo: 1st set: (799232119, 1028247821, 0, 0, 0)
2013-08-16 13:10:47.671: [  OCRRAW][357553728]proprioo: 2nd set: (0, 0, 0, 0, 0)
2013-08-16 13:10:47.671: [  OCRRAW][357553728]proprinit: Successfully initialized the I/O module (proprioini).
2013-08-16 13:10:47.671: [  OCRRAW][357553728]proprinit: Successfully initialized the backend handle (propribctx).
2013-08-16 13:10:47.671: [  OCRAPI][357553728]proa_init: Successfully initialized the Storage Layer.
2013-08-16 13:10:47.674: [  OCRAPI][357553728]proa_init: Successfully initlaized the Messaging Layer.

<---- everything okay this point

2013-08-16 13:10:47.698: [  OCRAPI][357553728]a_init:18!: Thread init unsuccessful : [24]
2013-08-16 13:10:47.742: [  CRSOCR][357553728] OCR context init failure.  Error: PROCL-24: Error in the messaging layer Messaging error [gipcretFail] [1]
2013-08-16 13:10:47.743: [ default][357553728] Created alert : (:OHAS00106:) :  OLR initialization failed, error: PROCL-24: Error in the messaging layer Messaging error [gipcretFail] [1]
2013-08-16 13:10:47.743: [ default][357553728][PANIC] OHASD exiting; Could not init OLR
2013-08-16 13:10:47.743: [ default][357553728] Done.

2013-08-16 13:27:35.715: [ default][2626647616] Created alert : (:OHAS00117:) :  TIMED OUT WAITING FOR OHASD MONITOR
2013-08-16 13:27:35.716: [ default][2626647616] OHASD Daemon Starting. Command string :reboot
2013-08-16 13:27:35.716: [ default][2626647616] OHASD params []
2013-08-16 13:27:35.717: [ default][2626647616]
2013-08-16 13:27:35.717: [ default][2626647616] Initializing OLR
2013-08-16 13:27:35.717: [ default][2626647616]proa_init: OLR Abstraction layer initialization. Bootlevel:[1]
2013-08-16 13:27:35.724: [  OCRAPI][2626647616]a_init: Successfully initialized the patch management context.

2013-08-16 13:27:35.724: [  OCRAPI][2626647616]a_init: Successfully initialized the OLR specific states.
2013-08-16 13:27:35.724: [  OCRAPI][2626647616]a_init:13: Clusterware init successful
2013-08-16 13:27:35.724: [  OCRAPI][2626647616]a_init:15: Successfully initialized the Cache layer.
2013-08-16 13:27:35.724: [  OCRRAW][2626647616]proprioo: opening OCR device(s)
2013-08-16 13:27:35.724: [  OCRRAW][2626647616]proprioo: Successfully opened the non-ASM locations if configured.
2013-08-16 13:27:35.725: [  OCRRAW][2626647616]proprioo: for disk 0 (/u01/app/oracle/product/12.1.0/grid/cdata/localhost/pdb12c.olr), id match (1), total id sets, (1) need recover (0), my votes (0), total votes (0), commit_lsn (1), lsn (1)
2013-08-16 13:27:35.725: [  OCRRAW][2626647616]proprioo: my id set: (799232119, 1028247821, 0, 0, 0)
2013-08-16 13:27:35.725: [  OCRRAW][2626647616]proprioo: 1st set: (799232119, 1028247821, 0, 0, 0)
2013-08-16 13:27:35.725: [  OCRRAW][2626647616]proprioo: 2nd set: (0, 0, 0, 0, 0)
2013-08-16 13:27:35.725: [  OCRRAW][2626647616]proprinit: Successfully initialized the I/O module (proprioini).
2013-08-16 13:27:35.725: [  OCRRAW][2626647616]proprinit: Successfully initialized the backend handle (propribctx).
2013-08-16 13:27:35.725: [  OCRAPI][2626647616]proa_init: Successfully initialized the Storage Layer.
2013-08-16 13:27:35.726: [  OCRAPI][2626647616]proa_init: Successfully initlaized the Messaging Layer.
2013-08-16 13:27:35.731: [  OCRMSG][2608776960]prom_listen: Failed to listen at endpoint [1]
2013-08-16 13:27:35.732: [  OCRMSG][2608776960]GIPC error [1] msg [gipcretFail]
2013-08-16 13:27:35.732: [  OCRSRV][2608776960]th_listen: prom_listen failed retval= 24, addr= [(ADDRESS=(PROTOCOL=ipc)(KEY=procr_local_conn_0_PROL))]
2013-08-16 13:27:35.732: [  OCRSRV][2626647616]th_init: Local listener did not reach valid state

			<---- This can mean some issue with network socket file location or permission.  

2013-08-16 13:27:35.732: [  OCRAPI][2626647616]a_init:18!: Thread init unsuccessful : [24]
2013-08-16 13:27:35.776: [  CRSOCR][2626647616] OCR context init failure.  Error: PROCL-24: Error in the messaging layer Messaging error [gipcretFail] [1]
2013-08-16 13:27:35.776: [ default][2626647616] Created alert : (:OHAS00106:) :  OLR initialization failed, error: PROCL-24: Error in the messaging layer Messaging error [gipcretFail] [1]
2013-08-16 13:27:35.776: [ default][2626647616][PANIC] OHASD exiting; Could not init OLR
2013-08-16 13:27:35.777: [ default][2626647616] Done.

After triaging a bit I think we had some wrong permissions on the directory strcutures, plus some hostname stuff wasn’t accurate. Hopefully that was it. Now let’s re-do the following to recover and move forward:

I first tried to stop HAS to ensure its not active

[root@pdb12c grid]# crsctl stop  has -f 
CRS-4639: Could not contact Oracle High Availability Services
CRS-4000: Command Stop failed, or completed with errors.

[root@pdb12c grid]  cd /u01/app/oracle/product/12.1.0/grid/crs/install

Let's try to execute deconfig to fix the broken configuration:

[root@pdb12c install]# ./roothas.pl -deconfig -force
Using configuration parameter file: ./crsconfig_params
CRS-4047: No Oracle Clusterware components configured.
CRS-4000: Command Stop failed, or completed with errors.
CRS-4047: No Oracle Clusterware components configured.
CRS-4000: Command Delete failed, or completed with errors.
CRS-4047: No Oracle Clusterware components configured.
CRS-4000: Command Stop failed, or completed with errors.
2013/08/17 15:35:04 CLSRSC-357: Failed to stop current Oracle Clusterware stack during upgrade
2013/08/17 15:35:05 CLSRSC-180: An error occurred while executing the command '/etc/init.d/ohasd deinstall' (error code -1)
Failure in execution (rc=-1, 0, Inappropriate ioctl for device) for command /etc/init.d/ohasd deinstall
2013/08/17 15:35:05 CLSRSC-337: Successfully deconfigured Oracle Restart stack

Hopefully this deconfig and stop stack worked:

[

root@pdb12c install]# ps -ef|grep has
root      5679  2968  0 15:35 pts/0    00:00:00 grep has

Stack is down so let's re-run root.sh

[root@pdb12c grid]# ./root.sh
Performing root user operation for Oracle 12c 

The following environment variables are set as:
    ORACLE_OWNER= oracle
    ORACLE_HOME=  /u01/app/oracle/product/12.1.0/grid
   Copying dbhome to /usr/local/bin ...
   Copying oraenv to /usr/local/bin ...
   Copying coraenv to /usr/local/bin ...

Entries will be added to the /etc/oratab file as needed by
Database Configuration Assistant when a database is created
Finished running generic part of root script.
Now product-specific root actions will be performed.
Using configuration parameter file: /u01/app/oracle/product/12.1.0/grid/crs/install/crsconfig_params
LOCAL ADD MODE 
Creating OCR keys for user 'oracle', privgrp 'oinstall'..
Operation successful.
LOCAL ONLY MODE 
Successfully accumulated necessary OCR keys.
Creating OCR keys for user 'root', privgrp 'root'..
Operation successful.
CRS-4664: Node pdb12c successfully pinned.
2013/08/17 15:35:41 CLSRSC-330: Adding Clusterware entries to file 'oracle-ohasd.conf'
pdb12c     2013/08/17 15:35:58     /u01/app/oracle/product/12.1.0/grid/cdata/pdb12c/backup_20130817_153558.olr
2013/08/17 15:37:50 CLSRSC-327: Successfully configured Oracle Grid Infrastructure for a Standalone Server

Let’s verify this successful OLR initialization by looking at ohasd.log:

2013-08-17 15:35:46.993: [ default][2945685056] OHASD Daemon Starting. Command string :reboot
2013-08-17 15:35:46.993: [ default][2945685056] OHASD params []
2013-08-17 15:35:46.994: [ default][2945685056]
2013-08-17 15:35:46.994: [ default][2945685056] Initializing OLR
2013-08-17 15:35:46.994: [ default][2945685056]proa_init: OLR Abstraction layer initialization. Bootlevel:[1]
2013-08-17 15:35:46.998: [  OCRAPI][2945685056]a_init: Successfully initialized the patch management context.
2013-08-17 15:35:46.998: [  OCRAPI][2945685056]a_init: Successfully initialized the OLR specific states.
2013-08-17 15:35:46.998: [  OCRAPI][2945685056]a_init:13: Clusterware init successful
2013-08-17 15:35:46.998: [  OCRAPI][2945685056]a_init:15: Successfully initialized the Cache layer.
2013-08-17 15:35:46.998: [  OCRRAW][2945685056]proprioo: opening OCR device(s)
2013-08-17 15:35:46.998: [  OCRRAW][2945685056]proprioo: Successfully opened the non-ASM locations if configured.
2013-08-17 15:35:46.998: [  OCRRAW][2945685056]proprioo: for disk 0 (/u01/app/oracle/product/12.1.0/grid/cdata/localhost/pdb12c.olr), id match (1), total id sets, (1) need recover (0), my votes (0), total votes (0), commit_lsn (1), lsn (1)
2013-08-17 15:35:46.998: [  OCRRAW][2945685056]proprioo: my id set: (799232119, 1028247821, 0, 0, 0)
2013-08-17 15:35:46.998: [  OCRRAW][2945685056]proprioo: 1st set: (799232119, 1028247821, 0, 0, 0)
2013-08-17 15:35:46.998: [  OCRRAW][2945685056]proprioo: 2nd set: (0, 0, 0, 0, 0)
2013-08-17 15:35:46.999: [  OCRRAW][2945685056]proprinit: Successfully initialized the I/O module (proprioini).
2013-08-17 15:35:46.999: [  OCRRAW][2945685056]proprinit: Successfully initialized the backend handle (propribctx).
2013-08-17 15:35:46.999: [  OCRAPI][2945685056]proa_init: Successfully initialized the Storage Layer.
2013-08-17 15:35:47.000: [  OCRAPI][2945685056]proa_init: Successfully initlaized the Messaging Layer.
2013-08-17 15:35:47.003: [  OCRAPI][2945685056]a_init:18: Thread init successful
2013-08-17 15:35:47.003: [  OCRAPI][2945685056]a_init:19: Client init successful
2013-08-17 15:35:47.003: [  OCRAPI][2945685056]a_init:21: OLR init successful. Init Level [1]

			<--- this is a good sign, but we still need to ensure OHASD starts up and initializes the CRS Policy Engine:
 
2013-08-17 15:35:47.003: [ default][2945685056] Checking version compatibility...
2013-08-17 15:35:47.003: [ default][2945685056]clsvactversion:4: Retrieving Active Version from local storage.
2013-08-17 15:35:47.004: [ default][2945685056] Version compatibility check passed:  Software Version: 12.1.0.1.0 Release Version: 12.1.0.1.0 Active Version: 12.1.0.1.0
2013-08-17 15:35:47.004: [ default][2945685056] Running mode check...
2013-08-17 15:35:47.004: [ default][2945685056] OHASD running as the Non-Privileged user

			<--- this is a also good sign, getting there...

2013-08-17 15:35:47.190: [   CRSPE][2889111296] {0:0:2} PE Role|State Update: old role [MASTER] new [MASTER]; old state [Starting] new [Running]
			<--- PE is running, getting there some more...

2013-08-17 15:35:47.190: [   CRSPE][2889111296] {0:0:2} Processing pending join requests: 1
2013-08-17 15:35:47.190: [UiServer][2413815552] UI comms listening for GIPC events.
2013-08-17 15:35:47.191: [   CRSPE][2889111296] {0:0:2} Special Value map for : pdb12c
2013-08-17 15:35:47.191: [   CRSPE][2889111296] {0:0:2} CRS_CSS_NODENAME=pdb12c
2013-08-17 15:35:47.191: [   CRSPE][2889111296] {0:0:2} CRS_CSS_NODENUMBER=0
2013-08-17 15:35:47.191: [   CRSPE][2889111296] {0:0:2} CRS_CSS_NODENUMBER_PLUS1=1
2013-08-17 15:35:47.191: [   CRSPE][2889111296] {0:0:2} CRS_HOME=/u01/app/oracle/product/12.1.0/grid
2013-08-17 15:35:47.191: [   CRSPE][2889111296] {0:0:2} Server Attributes for : pdb12c
2013-08-17 15:35:47.191: [   CRSPE][2889111296] {0:0:2} ACTIVE_CSS_ROLE=UNAVAILABLE
2013-08-17 15:35:47.191: [   CRSPE][2889111296] {0:0:2} CONFIGURED_CSS_ROLE=
2013-08-17 15:35:47.191: [   CRSPE][2889111296] {0:0:2} Server [pdb12c] has been registered with the PE data model
2013-08-17 15:35:47.191: [    AGFW][2899617536] {0:0:2} Agfw Proxy Server received the message: PE_HANDHSAKE[Proxy] ID 20487:33
2013-08-17 15:35:47.191: [    AGFW][2899617536] {0:0:2} Received handshake message from PE.

		<--- PE is initialized, getting even closer...

2013-08-17 15:35:47.192: [    AGFW][2899617536] {0:0:2} Added resource type: application
2013-08-17 15:35:47.192: [    AGFW][2899617536] {0:0:2} Added resource type: cluster_resource
2013-08-17 15:35:47.192: [    AGFW][2899617536] {0:0:2} Added resource type: generic_application
2013-08-17 15:35:47.192: [    AGFW][2899617536] {0:0:2} Added resource type: local_resource

I think the basic GI stack is there, let's verify:

[root@pdb12c ohasd]# ps -ef|grep oracle
root      3241  3232  0 14:23 pts/2    00:00:00 su - oracle
oracle    3242  3241  0 14:23 pts/2    00:00:00 -bash
oracle    5959     1  0 15:35 ?        00:00:02 /u01/app/oracle/product/12.1.0/grid/bin/ohasd.bin reboot
oracle    6067     1  0 15:35 ?        00:00:00 /u01/app/oracle/product/12.1.0/grid/bin/oraagent.bin
oracle    6080     1  0 15:35 ?        00:00:00 /u01/app/oracle/product/12.1.0/grid/bin/evmd.bin
oracle    6154  6080  0 15:35 ?        00:00:00 /u01/app/oracle/product/12.1.0/grid/bin/evmlogger.bin -o /u01/app/oracle/product/12.1.0/grid/log/[HOSTNAME]/evmd/evmlogger.info -l /u01/app/oracle/product/12.1.0/grid/log/[HOSTNAME]/evmd/evmlogger.log


Check crsctl stat res

[root@pdb12c ohasd]# crsctl stat res -init -t
--------------------------------------------------------------------------------
Name           Target  State        Server                   State details       
--------------------------------------------------------------------------------
Local Resources
--------------------------------------------------------------------------------
ora.ons
               OFFLINE OFFLINE      pdb12c                   STABLE
--------------------------------------------------------------------------------
Cluster Resources
--------------------------------------------------------------------------------
ora.cssd
      1        OFFLINE OFFLINE                               STABLE
ora.diskmon
      1        OFFLINE OFFLINE                               STABLE
ora.evmd
      1        ONLINE  ONLINE       pdb12c                   STABLE
--------------------------------------------------------------------------------
Odd that CSS hasn't started yet, and even odder that ASM is not instantiated.  UGH!!
Now we have to do some stitch work.  Again, all this is unnecessary, its because  installer didn't finish its work that we have do this.
So, let's add Local Listener and ASM. In this order !!

[oracle@pdb12c grid]$ srvctl add listener

[oracle@pdb12c grid]$ srvctl config ons
ONS exists: Local port 6100, remote port 6200, EM port 2016
[oracle@pdb12c grid]$ srvctl config listener
Name: LISTENER
Home: /u01/app/oracle/product/12.1.0/grid

[oracle@pdb12c grid]$ srvctl add asm


[oracle@pdb12c grid]$ srvctl config asm
ASM home: /u01/app/oracle/product/12.1.0/grid
Password file: 
ASM listener: LISTENER
Spfile: 
ASM diskgroup discovery string: ++no-value-at-resource-creation--never-updated-through-ASM++

<--- Notice that ASM has no SPFile associated with yet, but we still start it with default parameters

[oracle@pdb12c grid]$ srvctl start asm

[oracle@pdb12c asmca]$ ps -ef|grep asm
root     51260     2  0 15:37 ?        00:00:00 [asmWorkerThread]
root     51261     2  0 15:37 ?        00:00:00 [asmWorkerThread]
root     51262     2  0 15:37 ?        00:00:00 [asmWorkerThread]
root     51263     2  0 15:37 ?        00:00:00 [asmWorkerThread]
root     51264     2  0 15:37 ?        00:00:00 [asmWorkerThread]
oracle   53092     1  0 16:26 ?        00:00:00 asm_pmon_+ASM
oracle   53094     1  0 16:26 ?        00:00:00 asm_psp0_+ASM
oracle   53096     1  3 16:26 ?        00:00:01 asm_vktm_+ASM
oracle   53100     1  0 16:26 ?        00:00:00 asm_gen0_+ASM
oracle   53102     1  0 16:26 ?        00:00:00 asm_mman_+ASM
oracle   53106     1  0 16:26 ?        00:00:00 asm_diag_+ASM
oracle   53108     1  0 16:26 ?        00:00:00 asm_dia0_+ASM
oracle   53110     1  0 16:26 ?        00:00:00 asm_dbw0_+ASM
oracle   53112     1  0 16:26 ?        00:00:00 asm_lgwr_+ASM
oracle   53115     1  0 16:26 ?        00:00:00 asm_ckpt_+ASM
oracle   53117     1  0 16:26 ?        00:00:00 asm_smon_+ASM
oracle   53119     1  0 16:26 ?        00:00:00 asm_lreg_+ASM
oracle   53121     1  0 16:26 ?        00:00:00 asm_rbal_+ASM
oracle   53123     1  0 16:26 ?        00:00:00 asm_gmon_+ASM
oracle   53125     1  0 16:26 ?        00:00:00 asm_mmon_+ASM
oracle   53127     1  0 16:26 ?        00:00:00 asm_mmnl_+ASM


Now run asmca to create the disk group using ASMCA

PDB12c 2013 08 17 16 34 15


Let's check crsctl stat res again

[oracle@pdb12c asmca]$ crsctl stat res -t
--------------------------------------------------------------------------------
Name           Target  State        Server                   State details       
--------------------------------------------------------------------------------
Local Resources
--------------------------------------------------------------------------------
ora.LISTENER.lsnr
               ONLINE  ONLINE       pdb12c                   STABLE
ora.PDBDATA.dg
               ONLINE  ONLINE       pdb12c                   STABLE
ora.asm
               ONLINE  ONLINE       pdb12c                   Started,STABLE
ora.ons
               OFFLINE OFFLINE      pdb12c                   STABLE
--------------------------------------------------------------------------------
Cluster Resources
--------------------------------------------------------------------------------
ora.cssd
      1        ONLINE  ONLINE       pdb12c                   STABLE
ora.diskmon
      1        OFFLINE OFFLINE                               STABLE
ora.evmd
      1        ONLINE  ONLINE       pdb12c                   STABLE
--------------------------------------------------------------------------------

Cool, we now have majority of the stack GI stack started!!  Also notice that the PDBDATA disk group resource got created auto magically when the disk group was created and mounted (this was the same case in 11gR2)

But I wonder how cssd got placed in the ONLINE state, we didn't change that state directly:
The answer to that has to do with the startup dependencies for ASM resource.  In this case its "hard pull-up" dependency, also ASM has a "weak" dependency on Listener, so that got Onlined too.  We can see that from  crsctl stat res ora.asm -p

[oracle@pdb12c asmca]$ crsctl stat res ora.asm -p
NAME=ora.asm
TYPE=ora.asm.type
….
….
START_DEPENDENCIES=hard(ora.cssd) weak(ora.LISTENER.lsnr)

….
….

STOP_DEPENDENCIES=hard(ora.cssd)



Note ASM is using the basic/generic init.ora file.  So let's create a real usable one:

cat $HOME/init+ASM.ora
sga_target=1536M
asm_diskgroups='PDBDATA'
asm_diskstring='/dev/sd*'
instance_type='asm'
remote_login_passwordfile='EXCLUSIVE'

SQL> create spfile='+PDBDATA' from pfile='$HOME/init+ASM.ora'
  2  ;

File created.
To really validate that GI stack is up and running and that ASM is cool, just for fun let's create an ACFS filesystem.  This validates the communication between layers of HAS/CRS stack, ASM as well the Policy Engine:

PDB12c 2013 08 17 16 37 48

...

PDB12c 2013 08 17 16 39 49

[root@pdb12c ohasd]# mkdir -p /u01/app/oracle/acfsmounts/pdbdata_pdbvol1
[root@pdb12c ohasd]# 
[root@pdb12c ohasd]# /bin/mount -t acfs /dev/asm/pdbvol1-339 /u01/app/oracle/acfsmounts/pdbdata_pdbvol1

[root@pdb12c ohasd]# df -ha
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/vg_12crac1-lv_root
                       19G   12G  5.8G  67% /
proc                     0     0     0   -  /proc
sysfs                    0     0     0   -  /sys
devpts                   0     0     0   -  /dev/pts
tmpfs                 1.4G  637M  792M  45% /dev/shm
/dev/sda1             485M   55M  405M  12% /boot
/dev/asm/pdbvol1-339  1.0G   41M  984M   4% /u01/app/oracle/acfsmounts/pdbdata_pdbvol1

ANd there you have it!  A re-sticthed back GI stack.  Again, I hope nobody has to go through that, but now at least you know!!

Now next step is to create the PDB database over ASM!!