Search This Blog

Monday, May 27, 2013

How to find the HPUX is PA-RISC or Itanium

Itanium will show ia64

systemname:/# uname -a
HP-UX sys-abc B.11.23 U ia64 3875925350 unlimited-user license

PA-RISC will not but instead show the series (9000/800)

systemname:/# uname -a
HP-UX sys-abc B.11.23 U 9000/800 139872607 unlimited-user license

Friday, March 15, 2013

vgextend: Couldn't install the physical volume "/dev/dsk/". Too many links

Problem Description:vgextend: Couldn't install the physical volume "/dev/dsk/".
Too many links

root@indrtest# vgextend /dev/indrtests /dev/dsk/c40t5d2 /dev/dsk/c43t5d2
vgextend: Couldn't install the physical volume "/dev/dsk/c40t5d2".
Too many links
vgextend: Couldn't install the physical volume "/dev/dsk/c43t5d2".
Too many links
root@indrtest# vgextend /dev/indrtests /dev/dsk/c40t5d2
vgextend: Couldn't install the physical volume "/dev/dsk/c40t5d2".
Too many links

Solution:
Unfortuantely that probably means you reached the maximum number of PV allowed for this Volume Group.

do a
#vgdisplay -v indrtest|more

and check that your Max PV is higher than the Cur PV. If they are equal (which is what I think is happening right now), that means you cannot add any more disks into that VG.

You either have to create a new VG, or re-create this current VG with option -p to have more disks than the actual value.
Cooperation is doing with a smile what you have to do anyhow.

root@marssvr# vgdisplay -v /dev/indrtests|more
--- Volume groups ---
VG Name                     /dev/indrtests
VG Write Access             read/write    
VG Status                   available                
Max LV                      255   
Cur LV                      34    
Open LV                     34    
Max PV                      32    
Cur PV                      32    
Act PV                      32    
Max PE per PV               14687       
VGDA                        64 
PE Size (Mbytes)            4              
Total PE                    319278 
Alloc PE                    319278 
Free PE                     0      
Total PVG                   0       
Total Spare PVs             0             
Total Spare PVs in use      0

Monday, March 4, 2013

VCS WARNING V-16-1-10484 Group dependency is violated


root@hostname2# hagrp -switch depkms_sg -to hostname2 
VCS WARNING V-16-1-10484 Group dependency is violated if group depkms_sg goes offline on system hostname1

Cause:
In an online Gloabal Dependency, a child service group must be online on a system in the cluster before the parent service group can come online

The child service group cannot be taken offline while the parent service group is online, however the parent service group can be taken offline while the child service group is online

Solution:

1) Determine the child and parent service groups

root@hostname1# hagrp -dep depkms_sg       
#Parent      Child      Relationship
unica_sg     depkms_sg  online global firm


2) Offline the parent service group, switch the child service group to another system and thenonline the parent service group again.

root@hostname2# hagrp -offline unica_sg -sys hostname2

root@hostname2# hastatus -summ

-- SYSTEM STATE
-- System               State                Frozen              

A  hostname1             RUNNING              0                    
A  hostname2             RUNNING              0                    

-- GROUP STATE
-- Group           System               Probed     AutoDisabled    State          

B  depkms_sg       hostname1             Y          N               ONLINE         
B  depkms_sg       hostname2             Y          N               OFFLINE        
B  unica_sg        hostname1             Y          N               OFFLINE        
B  unica_sg        hostname2             Y          N               OFFLINE 

root@hostname2# hagrp -switch depkms_sg -to hostname2


root@hostname2# hastatus -summ

-- SYSTEM STATE
-- System               State                Frozen              

A  hostname1             RUNNING              0                    
A  hostname2             RUNNING              0                    

-- GROUP STATE
-- Group           System               Probed     AutoDisabled    State          

B  depkms_sg       hostname1             Y          N               ONLINE         
B  depkms_sg       hostname2             Y          N               OFFLINE        
B  unica_sg        hostname1             Y          N               OFFLINE        
B  unica_sg        hostname2             Y          N               ONLINE         

Wednesday, February 27, 2013

How To Start, Stop and Restart Oracle Listener


How To Start, Stop and Restart Oracle Listener

1. Display Oracle Listener Status

Before starting, stopping or restarting make sure to execute lsnrctl status command to check the oracle listener status as shown below. Apart from letting us know whether the listener is up or down, you can also find the following valuable information from the lsnrctl status command output.

Listner Start Date and Time.
Uptime of listner – How long the listener has been up and running.
Listener Parameter File – Location of the listener.ora file. Typically located under $ORACLE_HOME/network/admin
Listener Log File – Location of the listener log file. i.e log.xml

If the Oracle listener is not running, you’ll get the following message.


# lsnrctl status
LSNRCTL for HPUX: Version 9.2.0.7.0 - Production on 27-FEB-2013 05:37:54
Copyright (c) 1991, 2002, Oracle Corporation.  All rights reserved.
Connecting to (ADDRESS=(PROTOCOL=tcp)(PORT=1521))
TNS-12541: TNS:no listener
 TNS-12560: TNS:protocol adapter error
  TNS-00511: No listener
   HPUX Error: 239: Connection refusedLSNRCTL for Linux: Version 11.1.0.6.0 - Production on 04-APR-2009 16:27:39
Copyright (c) 1991, 2007, Oracle.  All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=192.168.1.2)(PORT=1521)))
TNS-12541: TNS:no listener
 TNS-12560: TNS:protocol adapter error
  TNS-00511: No listener
   Linux Error: 111: Connection refused
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC)))
TNS-12541: TNS:no listener
 TNS-12560: TNS:protocol adapter error
  TNS-00511: No listener
   Linux Error: 2: No such file or directory


If the Oracle listener is running, you’ll get the following message.

# lsnrctl status      
LSNRCTL for HPUX: Version 9.2.0.7.0 - Production on 27-FEB-2013 05:40:28
Copyright (c) 1991, 2002, Oracle Corporation.  All rights reserved.
Connecting to (ADDRESS=(PROTOCOL=tcp)(PORT=1521))
STATUS of the LISTENER
------------------------
Alias                     LISTENER
Version                   TNSLSNR for HPUX: Version 9.2.0.7.0 - Production
Start Date                27-FEB-2013 05:40:20
Uptime                    0 days 0 hr. 0 min. 8 sec
Trace Level               off
Security                  OFF
SNMP                      OFF
Listener Parameter File   /var/opt/oracle/listener.ora
Listener Log File         /opt/oracle/product/920_ee_64/network/log/listener.log
Listening Endpoints Summary...
  (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=hostname.dc-dublin.de)(PORT=1521)))
The listener supports no services
The command completed successfully

2. Start Oracle Listener

If the Oracle listener is not running, start the listener as shown below. This will start all the listeners. If you want to start a specific listener, specify the listener name next to start. i.e lsnrctl start [listener-name]


#  lsnrctl start
LSNRCTL for HPUX: Version 9.2.0.7.0 - Production on 27-FEB-2013 05:40:20
Copyright (c) 1991, 2002, Oracle Corporation.  All rights reserved.
Starting /opt/oracle/product/920_ee_64/bin/tnslsnr: please wait...
TNSLSNR for HPUX: Version 9.2.0.7.0 - Production
System parameter file is /var/opt/oracle/listener.ora
Log messages written to /opt/oracle/product/920_ee_64/network/log/listener.log
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=hostname.dc-dublin.de)(PORT=1521)))
Connecting to (ADDRESS=(PROTOCOL=tcp)(PORT=1521))
STATUS of the LISTENER
------------------------
Alias                     LISTENER
Version                   TNSLSNR for HPUX: Version 9.2.0.7.0 - Production
Start Date                27-FEB-2013 05:40:20
Uptime                    0 days 0 hr. 0 min. 0 sec
Trace Level               off
Security                  OFF
SNMP                      OFF
Listener Parameter File   /var/opt/oracle/listener.ora
Listener Log File         /opt/oracle/product/920_ee_64/network/log/listener.log
Listening Endpoints Summary...
  (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=hostname.dc-dublin.de)(PORT=1521)))
The listener supports no services
The command completed successfully

3. Stop Oracle Listener

If the Oracle listener is running, stop the listener as shown below. This will stop all the listeners. If you want to stop a specific listener, specify the listener name next to stop. i.e lsnrctl stop [listener-name]


$ lsnrctl stop
LSNRCTL for Linux: Version 11.1.0.6.0 - Production on 04-APR-2009 16:27:37
Copyright (c) 1991, 2007, Oracle.  All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=192.168.1.2)(PORT=1521)))
The command completed successfully

4. Restart Oracle Listener

To restart the listener use lsnrctl reload as shown below instead of lsnrctl stop and lsnrctl start. realod will read the listener.ora file for new setting without stop and start of the Oracle listener.