gunzip /tmp/EMCPower.HPUX.PI.5.1.0.GA.b160.tar.gz
swinstall -x autoreboot=true -x mount_all_filesystems=false -s /tmp/EMCPower.HPUX.PI.5.1.0.GA.b160.tar EMCpower

source

# ioscan -fnC disk
# insf -e

source

ioscan -fnCfc
fcmsutil /dev/fcd0

source

HP-UX bdf replacement

source bdfmegs

instl_adm -> check current settings

instl_adm -t <ip-of-server> -> change ip address

source

On the server (10.10.10.4):

mkdir -p /var/opt/ignite/recovery/archives/client_host
chown bin:bin /var/opt/ignite/recovery/archives/client_host

/etc/exports:
/var/opt/ignite/clients -anon=2
/var/opt/ignite/recovery/archives/client_host -anon=2,access=client_host

#exportfs -av

/etc/hosts:
10.10.10.2 client_host

#time /opt/ignite/bin/make_net_recovery -x inc_entire=vg00 -x exclude=/var/DAILY_SAVED -s 10.10.10.4

SHELL>dbprofile -dn test -sip <Server_IP_Address> -cip <Client_IP_address> -gip <Gateway_IP_address> -m <subnet_mask> -b /opt/ignite/boot/nbp.efi

SHELL>dbprofile — this lists the boot profiles.

SHELL>lanboot -dn test

source

#! /bin/ksh
#
# oracle        Startup script for start oracle database server
#

case $1 in

‘start’)
echo -n $”Starting oracle”
su – oracle -c “ORACLE_SID=SID lsnrctl start”
su – oracle -c “ORACLE_SID=SID sqlplus ‘/as sysdba’ @/etc/startsid.sql”
;;

‘stop’)
echo -n $”Stopping oracle”
su – oracle -c “ORACLE_SID=SID sqlplus ‘/as sysdba’ @/etc/stopsid.sql”
su – oracle -c “ORACLE_SID=SID lsnrctl stop”
;;

*)
echo “oracleSID start|stop”
exit
;;

esac
exit

/etc/startsid.sql:
startup open;
exit

/etc/stopsid.sql:
shutdown immediate;
exit

also see

01. Create the system recovery image of the system to be cloned using “make_net_recovery” command

02. The recovery configurations and archives created by make_net_recovery are stored in a separate directory on Ignite-UX server for each client. If the client to be installed does not currently have a directory in /var/opt/ignite/clients but is up and running, create the directory using “Add new Client for Recovery” from Actions menu on Ignite-UX GUI (From server). Alternatively, we can also run add_new_client -s <ignite-ux_server_name> from the client. If the client is not running, you will have to boot the system from the Ignite-UX server to get the directory created.
03. Copy the CINDEX and recovery directory from the source client to the target client directory. If the CINDEX file already exits, either create a backup copy of the CINDEX or edit the CINDEX file to add the desired entries from the source client.

 cd /var/opt/ignite/clients/src_client_name
 find CINDEX recovery | cpio -pdvma ../target_client_name

04. Give the target client NFS access to recovery image of the source system
05. From the Ignite GUI select
Actions + Boot client…
Actions + Install Client + New Install…
06. Change the system networking parameters for the client during installation

For more information, refer Cloning Using Ignite-UX.PDF

source1 source2

Create a directory for the volume group

 # mkdir /dev/vggis

Create device file named “group”

 # mknod  /dev/vggis/group c 64 0x010000

Create a physical volume using pvcreate with the -B option.

 # pvcreate /dev/rdsk/c9t0d0

Create a VG [with PE size of 32MB and with 50000 extends]

 # vgcreate [-s 32 -e 50000] /dev/vggis /dev/dsk/c9t0d0
 # vgcreate -s <PE Size>) -e <max PE per PV>
 Volume group "/dev/vggis" has been successfully created.
 Volume Group configuration for /dev/vggis has been saved in /etc/lvmconf/vggis.conf

Create LV with 10GB size

 # lvcreate -n oracle -L 10240 vggis
 Warning: rounding up logical volume size to extent boundary at size "10016" MB.
 Logical volume "/dev/vggis/oracle" has been successfully created with
 character device "/dev/vggis/roracle".
 Logical volume "/dev/vggis/oracle" has been successfully extended.
 Volume Group configuration for /dev/vggis has been saved in /etc/lvmconf/vggis.conf

Create file system with largefiles enabled

 #newfs -F vxfs -o largefiles /dev/vggis/rgis

source1 source2