[EN] Run root.sh from a directory that has read/execute access to the grid owner 'oracle'

Problem:
To configure Grid Infrastructure for a Stand-Alone Server run the following command as the root user:
/oracle/app/oracle/product/11.2.0/grid/perl/bin/perl -I/oracle/app/oracle/product/11.2.0/grid/perl/lib -I/oracle/app/oracle/product/11.2.0/grid/crs/install /oracle/app/oracle/product/11.2.0/grid/crs/install/roothas.pl

xynndp09:/oracle/app/oracle/product/11.2.0/grid/perl/bin/perl -I/oracle/app/oracle/product/11.2.0/grid/perl/lib -I/oracle/app/oracle/product/11.2.0/grid/crs/install /oracle/app/oracle/product/11.2.0/grid/crs/install/roothas.pl
Using configuration parameter file: /oracle/app/oracle/product/11.2.0/grid/crs/install/crsconfig_params
su: Illegal option -c
usage:   su  [-]  [username  [arguments]]
         su  [-]  -d  [username]
Run root.sh from a directory that has read/execute access to the grid owner 'oracle'

[EN] The user is root. OPatch cannot continue if the user is root. OPatch failed with error code 255

Problem: The user is root. OPatch cannot continue if the user is root. OPatch failed with error code 255

[HHYTS]/u01/app/oracle/admin $

[HHYTS]/u01/app/oracle/product/11.2.0/dbhome_1/oui/bin $ sudo su -

[root@hhytsdb1 ~]#

[root@hhytsdb1 ~]# cd /u01/app/oracle/patchdepot

[root@hhytsdb1 patchdepot]# export PATH=$PATH:/u01/app/11.2.0.3/grid/OPatch

[root@hhytsdb1 patchdepot]# opatch apply 13513783

The user is root. OPatch cannot continue if the user is root.

OPatch failed with error code 255

[root@vfxadb03 patchdepot]# whoami

root

Solution: OPatch can not run as user root. When "opatch apply" statement runs, it initiates Java OPatch and Java OPatch can not run as user root. But when "opatch auto" statement runs, it initiates "autopatch" and autopatch can run as user root. So when you get this error, it means you must use "opatch auto".

[EN] Error starting ORMI server ... port 5520 The socket name is already in use

Problem: Enterprise Manager Console won't start with error "Error starting ORMI server ... port 5520. The socket name is already in use".

Solution: 

1. Shutdown Enterprise Manager Console.
emctl stop dbconsole

2. Check if there are any processes with name like "oc4j". If there are, kill them.
ps -ef | grep oc4j
kill -9 ....

3.  Open Enterprise Manager Console.  
emctl start dbconsole

[EN] 8 Quick Steps of IPS via ADRCI

----------- STEP 1 ------------------

[ASOS3]/u01/app/oracle/admin/asos3/bdump $ adrci

ADRCI: Release 11.2.0.3.0 - Production on Fri Mar 23 10:13:47 2012
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
ADR base = "/u01/app/oracle"

----------- STEP 2 ------------------

adrci> show home

ADR Homes:
diag/rdbms/asos/ASOS3
...
...

----------- STEP 3 ------------------

[TR] Global Database Name

Global Database Name
-------------------------------


Distributed bir Database Sistemine dahil olan tüm db'lerin Global Database Name'leri farklı olmak zorundadır.

Global Database Name, bir db yaratılırken aşağıdaki 2 başlangıç parametresinin değerleriyle belirlenir ve data dictionary'de saklanır. Formül şu şekildedir;

Global Database Name = DB_NAME.DB_DOMAIN (DB_NAME, en fazla 8 karakter olabilir)

Örnekler;
ALFADB.xxdomain.com
sales.us.oracle.com

Db yaratıldıktan sonra; DB_DOMAIN başlangıç parametresi değiştirilirse, aynı zamanda Global Database Name de değiştirilmiş olmaz. Global Database Name'i de bu şekilde güncellemek için ayriyetten "ALTER DATABASE RENAME GLOBAL_NAME TO db_name.yeni_db_domain;" komutu çalıştırılmalıdır.

Bir db'nin Global Database Name'ini öğrenmek için aşağıdaki komut kullanılır;

SELECT * FROM GLOBAL_NAME;