Tag: oracle

Sun ILOM targets

Here is the Sun / Oracle ILOM targets

-> help targets

Target Meaning

/ Contains all static objects
/HOST Host Information
/HOST/bootmode Bootmode Control
/HOST/diag Host Diagnostics Control
/HOST/domain Host Domain Info
/HOST/domain/control Control Domain Info
/SYS Sensors, Indicators, and FRU Information
/SP Service Processor
/SP/alertmgmt Alert rule management
/SP/alertmgmt/rules Alert rules
/SP/check_physical_presence Require a physical presence check for certain system commands
/SP/clients Clients that connect to external services
/SP/clients/activedirectory Active Directory sub-directory
/SP/clients/activedirectory/admingroups administrator groups sub-directory
/SP/clients/activedirectory/alternateservers alternate servers sub-directory
/SP/clients/activedirectory/alternateservers/1/cert cert directory
/SP/clients/activedirectory/alternateservers/2/cert cert directory
/SP/clients/activedirectory/alternateservers/3/cert cert directory
/SP/clients/activedirectory/alternateservers/4/cert cert directory
/SP/clients/activedirectory/alternateservers/5/cert cert directory
/SP/clients/activedirectory/cert cert sub-directory
/SP/clients/activedirectory/customgroups custom groups sub-directory
/SP/clients/activedirectory/dnslocatorqueries DNS service record sub-directory
/SP/clients/activedirectory/opergroups operator groups sub-directory
/SP/clients/activedirectory/userdomains user domain sub-directory
/SP/clients/dns DNS resolution configuration
/SP/clients/dns/auto_dns When enabled, any manually configured entries will be overwritten with the values obtained via DHCP.
/SP/clients/dns/nameserver Up to three comma separated name server IP addresses in preferred search order
/SP/clients/dns/retries The number of retry attempts used in the event of a timeout.
/SP/clients/dns/searchpath Up to six comma separated search suffixes in preferred search order
/SP/clients/dns/timeout The number of seconds to wait for a response to a query.
/SP/clients/ldap LDAP Client Properties
/SP/clients/ldapssl LDAP/SSL sub-directory
/SP/clients/ldapssl/admingroups administrator groups sub-directory
/SP/clients/ldapssl/alternateservers alternate servers sub-directory
/SP/clients/ldapssl/alternateservers/1/cert cert directory
/SP/clients/ldapssl/alternateservers/2/cert cert directory
/SP/clients/ldapssl/alternateservers/3/cert cert directory
/SP/clients/ldapssl/alternateservers/4/cert cert directory
/SP/clients/ldapssl/alternateservers/5/cert cert directory
/SP/clients/ldapssl/cert cert sub-directory
/SP/clients/ldapssl/customgroups custom groups sub-directory
/SP/clients/ldapssl/opergroups operator groups sub-directory
/SP/clients/ldapssl/userdomains user domain sub-directory
/SP/clients/ntp NTP configuration
/SP/clients/ntp/server NTP server configuration
/SP/clients/radius RADIUS Client Properties
/SP/clients/smtp SMTP SERVER
/SP/clients/syslog syslogd management
/SP/clients/syslog/1 syslogd remote logging management 1
/SP/clients/syslog/2 syslogd remote logging management 2
/SP/clock Clock management
/SP/config Config Backup / Restore settings
/SP/console Redirection of console stream to SP
/SP/console/history console history
/SP/diag SP/Host Diagnositics Configuration
/SP/diag/snapshot Take snapshot of system for diagnostic purposes
/SP/faultmgmt FRUs with faults
/SP/firmware Firmware Base TARGET
/SP/firmware/localimage Firmware local image TARGET
/SP/firmware/localimage/upload_date Firmware local image date
/SP/firmware/localimage/version Firmware local image version
/SP/logs Log events
/SP/logs/event Designations for event log
/SP/logs/event/list Designations for event log
/SP/network External network interface
/SP/policy Policy Configuration
/SP/serial Serial interfaces
/SP/serial/external External serial interface
/SP/services Available services
/SP/services/http HTTP service
/SP/services/https HTTPS service
/SP/services/https/ssl HTTPS SSL Certficate Settings
/SP/services/https/ssl/custom_cert Custom SSL Certficate Settings
/SP/services/https/ssl/custom_key Custom SSL Private Key Settings
/SP/services/https/ssl/default_cert Default SSL Certficate Settings
/SP/services/ipmi Management of the IPMI service
/SP/services/servicetag Servicetag configuration
/SP/services/snmp SNMP agent service configuration
/SP/services/snmp/communities snmp communities
/SP/services/snmp/communities/private snmp community
/SP/services/snmp/communities/public snmp community
/SP/services/snmp/users SNMP users
/SP/services/ssh Secure shell
/SP/services/ssh/keys Keys for secure shell
/SP/services/ssh/keys/dsa DSA key for secure shell
/SP/services/ssh/keys/rsa RSA key for secure shell
/SP/services/sso Single Sign-on Configuration
/SP/sessions Session description
/SP/users User description

List all the users on ILOM

-> show /SP/users

/SP/users
Targets:
root

Properties:

Commands:
cd
create
delete
set
show

Creating a new user

-> create /SP/users/admin password=12345678
Creating user…
Created /SP/users/admin

Setting the role to administrator

-> set /SP/users/admin role=Administrator
Set ‘role’ to ‘Administrator’

If you want to use ILOM exactly as an ALOM, set the CLI mode to ALOM

-> set /SP/users/admin cli_mode=alom
Set ‘cli_mode’ to ‘alom’

A Cluster with Solaris and Oracle RAC – Avoid panic when rebooting

You just rebooted a server that you know that runs Oracle RAC and the other node rebooted. This happened because CRS was active and you first need to disable to reboot the other node. You’ll see this message on /var/adm/messages

Jun 5 14:15:19 solaris_rac2 root: Oracle clsomon failed with fatal status 12.
Jun 5 14:15:20 solaris_rac2 root: Oracle CRS failure. Rebooting for cluster integrity.
rebooting…

Run this command to stop CRS. Your path may vary according to where you installed the binary.

root@solaris_rac1:~ # /u01/app/oracle/product/11.1.0/bin/crsctl stop crs
Stopping resources.
This could take several minutes.
Successfully stopped Oracle Clusterware resources
Stopping Cluster Synchronization Services.
Shutting down the Cluster Synchronization Services daemon.
Shutdown request successfully issued.

Check the status with crsctl check crs. It should display the message below

root@solaris_rac1:~ # /u01/app/oracle/product/11.1.0/bin/crsctl check crs
Failure 1 contacting Cluster Synchronization Services daemon
Cannot communicate with Cluster Ready Services
Cannot communicate with Event Manager

After you reestablish the machine, CRS should start automatically

root@solaris_rac1:~ # /u01/app/oracle/product/11.1.0/bin/crsctl check crs
Cluster Synchronization Services appears healthy
Cluster Ready Services appears healthy
Event Manager appears healthy

Starting an Oracle database instance

Here is a reference if I need to start an Oracle database instance. It may not be the best way but this is how I done.

I became the user oracle

root@solaris:/ # su – oracle

Exported the variable that sets the instance that I’ll deal with

oracle@solaris:~ $ export ORACLE_SID=testing

Started sqlplus

oracle@solaris:~ $ sqlplus /nolog
SQL*Plus: Release 9.2.0.8.0 – Production on Fri Jun 18 10:57:30 2010
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.

Connected as user sysdba

SQL> connect /as sysdba
Connected to an idle instance.

And finally started the instance

SQL> startup
ORACLE instance started.

Total System Global Area 209747872
bytes

Fixed Size 728992
bytes

Variable Size 167772160
bytes

Database Buffers 40960000
bytes

Redo Buffers 286720

bytes

Database mounted.
Database opened.

Pressed CTRL+D to exit sqlplus

SQL> Disconnected from Oracle9i Enterprise Edition Release 9.2.0.8.0 – 64bit Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.8.0 – Production

You’ll also need to start the Oracle Database Listener

Problems mounting an OCFS2 filesystem under Linux – Transport endpoint is not connected

I had a problem mounting an ocfs2 filesystem under Oracle Cluster Management Software.

root@oracm1:~# mount -a
mount.ocfs2: Transport endpoint is not connected while mounting /dev/mapper/oravg01-lvu03 on /u03. Check ‘dmesg’ for more information on this error.

The error message said to check dmesg for more information and there it was. The cluster was not handshaking with the other node because the network timeout was different.

root@oracm1:~# dmesg
Buffer I/O error on device sdab, logical block 262143
(8290,0):o2net_check_handshake:1180 node oracm2 (num 1) at 192.168.2.101:7777 uses a network idle timeout of 10000 ms, but we use 30000 ms locally.  disconnecting
(8211,0):dlm_request_join:901 ERROR: status = -107
(8211,0):dlm_try_to_join_domain:1049 ERROR: status = -107
(8211,0):dlm_join_domain:1321 ERROR: status = -107
(8211,0):dlm_register_domain:1514 ERROR: status = -107
(8211,0):ocfs2_dlm_init:2024 ERROR: status = -107
(8211,0):ocfs2_mount_volume:1133 ERROR: status = -107
ocfs2: Unmounting device (253,7) on (node 0)

I entered the other cluster node to check the cluster status. The heartbeat is active and the timeout is 10000.

root@oracm2:~# service o2cb status
Module “configfs”: Loaded
Filesystem “configfs”: Mounted
Module “ocfs2_nodemanager”: Loaded
Module “ocfs2_dlm”: Loaded
Module “ocfs2_dlmfs”: Loaded
Filesystem “ocfs2_dlmfs”: Mounted
Checking O2CB cluster ocfs2: Online
Heartbeat dead threshold: 61
Network idle timeout: 10000
Network keepalive delay: 5000
Network reconnect delay: 2000
Checking O2CB heartbeat: Active

root@oracm1:~# service o2cb status
Module “configfs”: Loaded
Filesystem “configfs”: Mounted
Module “ocfs2_nodemanager”: Loaded
Module “ocfs2_dlm”: Loaded
Module “ocfs2_dlmfs”: Loaded
Filesystem “ocfs2_dlmfs”: Mounted
Checking O2CB cluster ocfs2: Online
Heartbeat dead threshold: 61
Network idle timeout: 30000
Network keepalive delay: 5000
Network reconnect delay: 2000
Checking O2CB heartbeat: Not active

The host oracm1 needs to have exactly the same configuration as oracm2, so I invoked the o2cb script with the configure parameter to reconfigure the timeout.

root@oracm1:~# service o2cb configure
Configuring the O2CB driver.

This will configure the on-boot properties of the O2CB driver.
The following questions will determine whether the driver is loaded on
boot.  The current values will be shown in brackets (‘[]’).  Hitting
<ENTER> without typing an answer will keep that current value.  Ctrl-C
will abort.

Load O2CB driver on boot (y/n) [y]: y
Cluster to start on boot (Enter “none” to clear) [ocfs2]: ocfs2
Specify heartbeat dead threshold (>=7) [61]: 61
Specify network idle timeout in ms (>=5000) [30000]: 10000
Specify network keepalive delay in ms (>=1000) [5000]: 5000
Specify network reconnect delay in ms (>=2000) [2000]: 2000
Writing O2CB configuration: OK
O2CB cluster ocfs2 already online

I restarted the o2cb service

root@oracm1:~# service o2cb stop
root@oracm1:~# service o2cb start

And checked that the node entered the cluster.

root@oracm1:$ORACLE_HOME/oracm/log # grep “Successful reconfiguration” cm.log
Successful reconfiguration,  2 active node(s) node 1 is the master, my node num is 0 (reconfig 22) {Thu Jun 11 13:17:32 2009 }

root@oracm1:~# df -h /u03
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/oravg01-lvu03
30G   29G  1.1G  97% /u03
root@oracm1:~# mount | grep u03
/dev/mapper/oravg01-lvu03 on /u03 type ocfs2 (rw,_netdev,datavolume,nointr,heartbeat=local)