The opatch minimum version check for patch ... while applying PSU for grid infrastructure

In case you need to apply PSU for GI ( grid infrastructure )  and you have the error below :
The opatch minimum version check for patch /app/grid/OPatch/PSU4_GI/12827731 failed for /app/grid
The opatch minimum version check for patch /app/grid/OPatch/PSU4_GI/12827726 failed for /app/grid
Opatch version check failed for oracle home /app/grid
Opatch version check failed


solution for rmcup

export LESS

Many terminals, such as xterm, support a feature known as rmcup. It
restores the screen to what it looked like before a program was run. The situation
also occurs with any full-screen terminal program, such as man or less; the
program’s text disappears after you quit the program, and the prompt
“window” is restored http://blogs.oracle.com/samf/entry/smcup_rmcup_hate 

graphical remote connection to linux ( from windows )



gipchaInternalResolve: failed to resolve ret gipcretKeyNotFound

CRSD Fails to Start due to GIPC Communication Failure with Master [ID 1337730.1]


how to see undo space usage

the original link :  http://oracledisect.blogspot.com/2011/11/who-is-using-your-undo-space-improved.html?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+oracledbdisected+%28Oracle+Database+Disected%29

Then the script for Oracle 11g is as follows:
set pagesize 400
set linesize 140
col name for a25
col program for a50
col username for a12
col osuser for a12
SELECT a.inst_id, a.sid, c.username, c.osuser, c.program, b.name,
a.value, d.used_urec, d.used_ublk
FROM gv$sesstat a, v$statname b, gv$session c, gv$transaction d
WHERE a.statistic# = b.statistic#
AND a.inst_id = c.inst_id
AND a.sid = c.sid
AND c.inst_id = d.inst_id
AND c.saddr = d.ses_addr
AND a.statistic# = 284
AND a.value > 0

If you want to run this script on versions 10g1 and 10g2, just replace the statistic# with 176.





SSD for oracle databases


* Placing redo logs on SSD is not recommended. Exadata now has a “Smart Flash Logging” feature that uses redo logs on SSD. Note that it uses redo logs *also* on SSD. This feature allows Oracle to write redo in parallel to a file on SSD and a file on the magnetic disk, and finish the operation when one of the calls is successful. This is a no-lose situation that can only improve performance. This is not the case if you place your redo logs on both SSD and magnetic disks yourself, in which case the redo write will finish when the slowest device finishes writing, making it a no-win situation.


Direct NFS: please check that oradism is setuid

check also : http://dbamohsin.wordpress.com/2010/11/26/direct-nfs/

from note Direct NFS: FAQ [ID 954425.1]

What is oradism? When is it used by Direct NFS?

Direct NFS client uses oradism executable to perform functions that require root privileges. oradism is configured by default on a single instance and for RAC if not using shared $ORACLE_HOME.

It is used for the following special purposes:
Direct NFS client needs root privileges to start communication with the NFS filer. It uses oradism to obtain the root file handle for the exported volume and the NFS server port and NFS mount port. Once the root handle and port information is obtained, all future communication is issued by Oracle user processes using normal privileges.

Oradism executable need always to be owned by root otherwise instance will not come up and returns the error:
Direct NFS: please check that oradism is setuid

You could also try :  chown oracle:oinstall oradism    and chmod 4755 oradism

Also, you could try :  chown root:oinstall oradism      and chmod 4755 oradism

script to check baddata (number or varchar2 ) in the oracle database

Baddata Script To Check Database For Corrupt column data [ID 428526.1]

Check also this note/post : http://oradbastuff.blogspot.com/2011/11/typ2-len1-192.html

This script can be useful in case of the following errors :

Note:94185.1   - ALERT: JDBC Drivers May Insert Invalid Year 2000 Dates
Note:91207.1   - Warning for Client Code which directly manipulates Oracle DATE datatype values
Note:979657.8  - OCI allows invalid numbers to be inserted into the database
Note:4338390.8 - JDBC clients can insert corrupt data

The script can be downloaded here:


ORA-00245: control file backup operation failed



RMAN Duplicate from RAC backup fails ORA-38856 [ID 334899.1]