Configure Oracle Grid Infrastructure for a Standalone Server

# /u01/app/11.2.0.3/grid/perl/bin/perl -I /u01/app/11.2.0.3/grid/perl/lib -I /u01/app/11.2.0.3/grid/crs/install /u01/app/11.2.0.3/grid/crs/install/roothas.pl -deconfig -force
Using configuration parameter file: /u01/app/11.2.0.3/grid/crs/install/crsconfig_params
CRS resources for listeners are still configured
PRKO-2573 : ONS daemon is already stopped.
CRS-2673: Attempting to stop 'ora.cssd' on 'omega.sun.com'
CRS-2677: Stop of 'ora.cssd' on 'omega.sun.com' succeeded
CRS-2791: Starting shutdown of Oracle High Availability Services-managed resources on 'omega.sun.com'
CRS-2673: Attempting to stop 'ora.evmd' on 'omega.sun.com'
CRS-2677: Stop of 'ora.evmd' on 'omega.sun.com' succeeded
CRS-2793: Shutdown of Oracle High Availability Services-managed resources on 'omega.sun.com' has completed
CRS-4133: Oracle High Availability Services has been stopped.
Successfully deconfigured Oracle Restart stack

# /u01/app/11.2.0.3/grid/perl/bin/perl -I /u01/app/11.2.0.3/grid/perl/lib -I /u01/app/11.2.0.3/grid/crs/install /u01/app/11.2.0.3/grid/crs/install/roothas.pl
Using configuration parameter file: /u01/app/11.2.0.3/grid/crs/install/crsconfig_params
LOCAL ADD MODE
Creating OCR keys for user 'oragrid', 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 omega.sun.com successfully pinned.
Adding Clusterware entries to inittab
omega.sun.com     2013/02/12 14:12:01     /u01/app/11.2.0.3/grid/cdata/omega.sun.com/backup_20130212_141201.olr
Successfully configured Oracle Grid Infrastructure for a Standalone Server


# ls -l /etc/inittab
-rw-r--r--   1 root     root        1130 Feb 12 14:11 /etc/inittab
root@omega.sun.ru # more /etc/inittab
# Copyright 2004 Sun Microsystems, Inc.  All rights reserved.
# Use is subject to license terms.
#
# The /etc/inittab file controls the configuration of init(1M); for more
# information refer to init(1M) and inittab(4).  It is no longer
# necessary to edit inittab(4) directly; administrators should use the
# Solaris Service Management Facility (SMF) to define services instead.
# Refer to smf(5) and the System Administration Guide for more
# information on SMF.
#
# For modifying parameters passed to ttymon, use svccfg(1m) to modify
# the SMF repository. For example:
#
#       # svccfg
#       svc:> select system/console-login
#       svc:/system/console-login> setprop ttymon/terminal_type = "xterm"
#       svc:/system/console-login> exit
#
#ident  "@(#)inittab    1.41    04/12/14 SMI"
ap::sysinit:/sbin/autopush -f /etc/iu.ap
sp::sysinit:/sbin/soconfig -f /etc/sock2path
smf::sysinit:/lib/svc/bin/svc.startd    >/dev/msglog 2<>/dev/msglog

p3:s1234:powerfail:/usr/sbin/shutdown -y -i5 -g0 >/dev/msglog 2<>/dev/msglog
pt:s1234:powerfail:/lib/svc/method/installupdates lock

h1:3:respawn:/etc/init.d/init.ohasd run >/dev/null 2>&1

#


# ps -ef|grep ohas
 oragrid 17353     1   0 14:11:35 ?           0:02 /u01/app/11.2.0.3/grid/bin/ohasd.bin reboot
    root 17766  6506   0 14:19:46 pts/3       0:00 grep ohas
    root 17322     1   0 14:11:35 ?           0:00 /bin/sh /etc/init.d/init.ohasd run
#


# /u01/app/11.2.0.3/grid/bin/crsctl status resource -t
--------------------------------------------------------------------------------
NAME           TARGET  STATE        SERVER                   STATE_DETAILS
--------------------------------------------------------------------------------
Local Resources
--------------------------------------------------------------------------------
ora.ons
               OFFLINE OFFLINE      omega.sun.com
--------------------------------------------------------------------------------
Cluster Resources
--------------------------------------------------------------------------------
ora.cssd
      1        OFFLINE OFFLINE
ora.diskmon
      1        OFFLINE OFFLINE
ora.evmd
      1        ONLINE  ONLINE       omega.sun.com


# /u01/app/11.2.0.3/grid/bin/crsctl check has
CRS-4638: Oracle High Availability Services is online

# /u01/app/11.2.0.3/grid/bin/crsctl check css
CRS-4530: Communications failure contacting Cluster Synchronization Services daemon
#

# /u01/app/11.2.0.3/grid/bin/crsctl start resource ora.cssd -init
CRS-2672: Attempting to start 'ora.cssd' on 'omega.sun.com'
CRS-2672: Attempting to start 'ora.diskmon' on 'omega.sun.com'
CRS-2676: Start of 'ora.diskmon' on 'omega.sun.com' succeeded
CRS-2676: Start of 'ora.cssd' on 'omega.sun.com' succeeded
#

# /u01/app/11.2.0.3/grid/bin/crsctl status resource -t
--------------------------------------------------------------------------------
NAME           TARGET  STATE        SERVER                   STATE_DETAILS
--------------------------------------------------------------------------------
Local Resources
--------------------------------------------------------------------------------
ora.ons
               OFFLINE OFFLINE      omega.sun.com
--------------------------------------------------------------------------------
Cluster Resources
--------------------------------------------------------------------------------
ora.cssd
      1        ONLINE  ONLINE       omega.sun.com
ora.diskmon
      1        OFFLINE OFFLINE
ora.evmd
      1        ONLINE  ONLINE       omega.sun.com
#



В 11.2.0.3 diskmon.bin  не offline только для Exadate.

Если нет процессов то переконфигурировать  Grid Infrastructure.

А так делать не нужно:

crsctl delete resource ora.cssd
.....

crsctl add resource ora.cssd
.....


# /u01/app/11.2.0.3/grid/bin/crsctl modify resource "ora.cssd" -attr "AUTO_START=1"
# /u01/app/11.2.0.3/grid/bin/crsctl modify resource "ora.diskmon" -attr "AUTO_START=1"

#
# /u01/app/11.2.0.3/grid/bin/crsctl stop has
CRS-2791: Starting shutdown of Oracle High Availability Services-managed resources on 'omega.sun.com'
CRS-2673: Attempting to stop 'ora.cssd' on 'omega.sun.com'
CRS-2677: Stop of 'ora.cssd' on 'omega.sun.com' succeeded
CRS-2673: Attempting to stop 'ora.evmd' on 'omega.sun.com'
CRS-2677: Stop of 'ora.evmd' on 'omega.sun.com' succeeded
CRS-2793: Shutdown of Oracle High Availability Services-managed resources on 'omega.sun.com' has completed
CRS-4133: Oracle High Availability Services has been stopped.

#
# /u01/app/11.2.0.3/grid/bin/crsctl start has
CRS-4123: Oracle High Availability Services has been started.
#


# /u01/app/11.2.0.3/grid/bin/crsctl status resource -t
--------------------------------------------------------------------------------
NAME           TARGET  STATE        SERVER                   STATE_DETAILS
--------------------------------------------------------------------------------
Local Resources
--------------------------------------------------------------------------------
ora.ons
               OFFLINE OFFLINE      omega.sun.com
--------------------------------------------------------------------------------
Cluster Resources
--------------------------------------------------------------------------------
ora.cssd
      1        ONLINE  ONLINE       omega.sun.com
ora.diskmon
      1        OFFLINE OFFLINE
ora.evmd
      1        ONLINE  ONLINE       omega.sun.com
root@omega.sun.ru #


Конфигурация листенера:

$netca &


$srvctl config listener
Name: LISTENER
Home: /u01/app/11.2.0.3/grid
End points: TCP:1521
$

/u01/app/11.2.0.3/grid/bin/srvctl add listener -l LISTENER -s -p TCP:1521 -o /u01/app/11.2.0.3/grid

Конфигурация ASM:

$asmca &

$srvctl config asm
ASM home: /u01/app/11.2.0.3/grid
ASM listener: LISTENER
Spfile: +DATA/asm/asmparameterfile/registry.253.807812965
ASM diskgroup discovery string: /dev/rdsk/c*s4
$

$srvctl stop asm -f

$srvctl start asm

$srvctl modify resource "ora.asm" -attr "AUTO_START=1"

$srvctl add asm -l LISTENER -p +DATA/asm/asmparameterfile/registry.253.807812965 -d /dev/rdsk/c*s4


Recreate ASM parameterfile (spfile):

vi /tmp/init+ASM.ora

*.asm_diskstring='/dev/rdsk/c*s4'
*.asm_power_limit=1
*.diagnostic_dest='/u01/app/oragrid'
*.instance_type='asm'
*.large_pool_size=12M
*.remote_login_passwordfile='EXCLUSIVE'


$sqlplus "/as sysasm"

alter diskgroup DATA mount;

create spfile='+DATA' from pfile='/tmp/init+ASM.ora';

show parameter spfile;



# /u01/app/11.2.0.3/grid/bin/crsctl start has
# /u01/app/11.2.0.3/grid/bin/crsctl stop has
# /u01/app/11.2.0.3/grid/bin/crsctl status resource -t

Перенос дисковой группы с одного диска на другой:


alter diskgroup DATA add disk new_disk;
alter diskgroup DATA drop disk old_disk;

подождать

select * from v$asm_operation;


ADD ASM

$srvctl add asm -l LISTENER -p /u01/app/11.2.0.3/grid/dbs/init+ASM.ora  -d /dev/rdsk/c*s4

$srvctl start asm


export ORACLE_SID=+ASM
export ORACLE_HOME=/u01/app/11.2.0.3/grid

sqlplus "/as sysasm"

create diskgroup DATA external redundancy
disk '/dev/rdsk/c6t.....d0s4',
disk '/dev/rdsk/c6t.....d0s4'
attribute 'compatible.asm'='11.2.0.0.0';


create pfile='/tmp/pfile' from memory;

Правим файл в другой сессии:

vi /tmp/pfile
*.asm_diskstring='/dev/rdsk/c*s4'
*.asm_power_limit=1
*.diagnostic_dest='/u01/app/oragrid'
*.instance_type='asm'
*.large_pool_size=12M
*.remote_login_passwordfile='EXCLUSIVE'


create spfile='+DATA' from pfile='/tmp/pfile';
shutdown immediate;
startup;
show parameter spfile;

orapwd file=/u01/app/11.2.0.3/grid/dbs/orapw+ASM password=oracle



When setting ASM Monitoring Configuration with SYSASM or SYSDBA In Grid Control 11g [ID 977472.1]


For 11gR2 follow the procedure below to create the ASM password file:
1. Create the password file for ASM on all nodes (if RAC) as follows:
orapwd file=$GRID_INFRASTRUCTURE_HOME/dbs/orapw+ASM password= entries=5

2. Update the password file with the following users/roles:
sqlplus / as sysasm
SQL> create user asmsnmp identified by
SQL> grant sysasm to sys;
SQL> grant sysdba to asmsnmp;

3. Review changes to the password file by querying v$pwfile_users:

SQL> select * from v$pwfile_users;
USERNAME    SYSDB SYSOP SYSAS
---------   ----- ----- -----
SYS         TRUE  TRUE  TRUE
ASMSNMP     TRUE  FALSE FALSE



For 11gR1 follow the procedure below to create the ASM password file:
1. Create the password file for ASM on all nodes (if RAC) as follows:
orapwd file=$ORA_ASM_HOME/dbs/orapw password= entries=5

2. Update the password file with the following users/roles:
sqlplus / as sysdba
SQL> grant sysasm to sys;

3. Review changes to the password file by querying v$pwfile_users:

SQL> select * from v$pwfile_users;
USERNAME  SYSDB SYSOP SYSAS
--------- ----- ----- -----
SYS       TRUE  FALSE TRUE