VMWare tools Oracle-Linux-UEK and ‘The path “” is not a valid path to the kernel’

when you get the following message while building the vmware tools:

Searching for a valid kernel header path…
The path “” is not a valid path to the 3.8.13-16.3.1.el6uek.x86_64 kernel
headers.
Would you like to change it? [yes]

you first have to install the kernel-devel and kernel-header package:

> yum install kernel-uek-devel kernel-uek-headers

but there is still a version-file missing… a link can help:

ln -s /usr/src/kernels/3.8.13-16.3.1.el6uek.x86_64/include/generated/uapi/linux/version.h /usr/src/kernels/3.8.13-16.3.1.el6uek.x86_64/include/linux/version.h

Register 11.2 database to 12.1 grid infrastructure…

some permission have changed between 11 and 12, before creating a 11 database in an 12 grid environment some permission have to be changed:

./crsctl modify type ora.database.type -attr “ATTRIBUTE=TYPE_ACL, DEFAULT_VALUE=’owner:root:rwx,pgrp:dba:rwx,other::r–,group:dba:r-x,user:oracle:rwx'”

./crsctl modify type ora.service.type  -attr “ATTRIBUTE=TYPE_ACL, DEFAULT_VALUE=’owner:root:rwx,pgrp:dba:rwx,other::r–,group:dba:r-x,user:oracle:rwx'”

otherwise you will get an permission error when the database will be added to the grid.

if you already got the error while creating the database with dbca then you can add the database manually to the grid, but you have to use srvctl from the 11 home directory:

/home/app/product/11.2.0/dbhome/bin/srvctl add database -d <DB> -o /home/app/product/11.2.0/dbhome

 

How to set dns-server and search domain in solaris 5.11

root@solaris:~# svccfg

svc:> select dns/client
svc:/network/dns/client> setprop config/nameserver = net_address: 192.168.1.14
svc:/network/dns/client> setprop config/search = astring: rocworks.local
svc:/network/dns/client> select default
svc:/network/dns/client:default> refresh
svc:/network/dns/client:default> validate

svc:/network/dns/client:default> select name-service/switch
svc:/system/name-service/switch> setprop config/host = astring: “files dns
svc:/system/name-service/switch> select default
svc:/system/name-service/switch:default> refresh
svc:/system/name-service/switch:default> validate

check the result in /etc/resolv.conf (don’t edit this file, it will be set by svc on (re)boot)

search rocworks.local
nameserver 192.168.1.14

Solaris nfs mount at boot (for oracle db_recovery_file_dest)

svcadm enable -r nfs/client
 
/etc/vfstab:
nas2:/vols/disk/oradata – /data/oradata nfs – yes rw,xattr,rsize=32768,wsize=32768,hard
 
SQL> show parameter db_recovery
NAME TYPE VALUE
———————————— ———– ——————————
db_recovery_file_dest string /data/oradata
db_recovery_file_dest_size big integer 80G

Oracle RAC ologgerd process high cpu load…

The ologgerd is part of Oracle Cluster Health Monitor and is used by the Oracle Support to troubleshoot RAC problems. If ologgerd process is consuming a lot of CPU and writes a lot of data to disk, it can be stopped by executing on both nodes:

# crsctl stop resource ora.crf -init

to disable ologgerd permanently, execute:

# crsctl delete resource ora.crf -init