Problem with P2V

This is a tough nut. But it is not entirely my problem.
It's a old Compaq Proliant ML370 G3 server, running Windows 2000. The hardware raid controller is Smart Array 532. The P2V using VMware Converter failed at 97%, just about time i were ready to tell customer to celebrate. Backup using Symantec BMR also failed, it was unable to run discovery job. The error is status -1, the hardware controller's driver was unable to be determined.
Symantec advised me to re-install the driver, which customer is very uncomfortable to do so.
I still have to spend quite some effort it seems.

How to get the Fibre Channel Adpater WWNN

AIX
========

1. Check the available FC HBA in the host.

# lsdev -Cc adapter | grep fc
fcs0 Available 1Z-08 FC Adapter


2. Use lscfg command to get the WWNN.

# lscfg -vl fcs0 | grep -w "Network Address"
Network Address.............10000000C9427D30

Solaris - Qlogic or Emulex
============================
root@ sun:/root# fcinfo hba-port | grep WWN
HBA Port WWN: 2100111b32xxxxxx
Node WWN: 2000111b32xxxxxx


Solaris - Fujitsu
======================
root@sun:/# /opt/FJSVpfca/sbin/ns_show -n fjpfca0

fjpfca#0 :
port_id=011200 node_name=50000e1000012100 port_name=50000e1000012100
alias=fc1slot2

OPN Tests

I am busy certifying myself for OPN specialization. A lot of test to be taken. For me, it's a mixture of skills that are tested. DB, Cluster, Systems ,etc..

VxVM Disk Group Split/Join

A script which is used to perform VxVM disk group split/join for daily backup:

production diskgroup: svrdg
snap diskgroup: sdg
volumes: prod02, prod03, prod04
snap volumes: sz02, sz03, sz04

****************************************************

#/bin/sh
date > /dailybackup/logs/snap1/log.`date '+%d%m%Y'`

#Unmount all the Snapshot Volumes after Backup completed

umount /sz02
umount /sz03
umount /sz04

sleep 5

#Join the Snapshot Volumes back to the Oracle Database Disk Group

vxdg join sdg svrdg
sleep 5
vxrecover -g svrdg -s
sleep 5

#Start all the Snapshot Volumes prepared for next time syncchronize.

vxvol -g svrdg startall

sleep 5

/u01/Ora10/script/start_backup.sh

sleep 60
echo "HotBackup mode is activated Now!!"

#Volume Manager will now start sync to snapshot Volumes.

vxsnap -g svrdg refresh sz02
vxsnap -g svrdg syncwait prod02

vxsnap -g svrdg refresh sz03
vxsnap -g svrdg syncwait prod03

vxsnap -g svrdg refresh sz04
vxsnap -g svrdg syncwait prod04



#sleep 600
sleep 4800

/z01/Oracle10/script/BBSSEC/off_backup.sh

sleep 60
echo "HotBackup mode is now deactivated!!!!"

vxdg -o expand split svrdg sdg sz02 sz03 sz04

sleep 5

vxrecover -g sdg -s

sleep 5

vxvol -g sdg startall

sleep 5

fsck -F vxfs /dev/vx/rdsk/sdg/sz02
fsck -F vxfs /dev/vx/rdsk/sdg/sz03
fsck -F vxfs /dev/vx/rdsk/sdg/sz04

sleep 10

mount -F vxfs /dev/vx/dsk/sdg/sz02 /sz02
mount -F vxfs /dev/vx/dsk/sdg/sz03 /sz03
mount -F vxfs /dev/vx/dsk/sdg/sz04 /sz04

sleep 5
exit 0

ORA-12518 TNS listener could not hand off client connection

As part of Oracle tuning exercise, we have increased sga_target and pg_aggregate_target to a higher value. This is a 32-bit Windows 2008 Enterprise server.
Users complaint application returned this error after changing init.ora parameters. After checking and some troubleshooting, we found that this is due to 32-bit restriction of 2gb virtual memory for each process.

With sga_target = 1.3g, pga_aggregate_target=0.5g, we had used 1.8g out of 2gb. Oracle ddl and process overhead took up 150mb, all this totals up to 1950gb. This leaves little for the user connections. With each connection takes 2.14mb, this only allows about 20 user connections (50/2.14) before it hit the 2gb limit.

We reduced the sga and pga and things back to normal, but the performance didn't get improved. This is some solutions for this large sga requirements. We will explore further.

This error 12518 can be caused by many things like hitting process or session limits, and this case it was not. We need to increase user memory space and this is some solutions on 32-bit systems. We will explore later.

NetBackup for Oracle : ORA-27029 error while restoring db

Encountered the following error while restoring database from master server:


RMAN> RUN {
ALLOCATE CHANNEL ch00
TYPE 'SBT_TAPE';
SEND 'NB_ORA_SERV=servername.mtv.ccc.com';
RESTORE ARCHIVELOG FROM SEQUENCE 4170 UNTIL SEQUENCE 4217;
RELEASE CHANNEL ch00;
}
2> 3> 4> 5> 6> 7>
allocated channel: ch00
channel ch00: sid=7 devtype=SBT_TAPE
channel ch00: Veritas NetBackup for Oracle - Release 7.0 (2010010418)

sent command to channel: ch00

Starting restore at 02-DEC-11

channel ch00: starting archive log restore to default destination
channel ch00: restoring archive log
archive log thread=1 sequence=4170
channel ch00: restoring archive log
archive log thread=1 sequence=4171
channel ch00: restoring archive log
archive log thread=1 sequence=4172
channel ch00: restoring archive log
archive log thread=1 sequence=4173
channel ch00: restoring archive log
archive log thread=1 sequence=4174
channel ch00: restoring archive log
archive log thread=1 sequence=4175
channel ch00: restoring archive log
archive log thread=1 sequence=4176
channel ch00: restoring archive log
archive log thread=1 sequence=4177
channel ch00: restoring archive log
archive log thread=1 sequence=4178
channel ch00: restoring archive log
archive log thread=1 sequence=4179
channel ch00: restoring archive log
archive log thread=1 sequence=4180
channel ch00: restoring archive log
archive log thread=1 sequence=4181
channel ch00: restoring archive log
archive log thread=1 sequence=4182
channel ch00: restoring archive log
archive log thread=1 sequence=4183
channel ch00: restoring archive log
archive log thread=1 sequence=4184
channel ch00: restoring archive log
archive log thread=1 sequence=4185
channel ch00: restoring archive log
archive log thread=1 sequence=4186
channel ch00: restoring archive log
archive log thread=1 sequence=4187
channel ch00: restoring archive log
archive log thread=1 sequence=4188
channel ch00: restoring archive log
archive log thread=1 sequence=4189
channel ch00: restoring archive log
archive log thread=1 sequence=4190
channel ch00: restoring archive log
archive log thread=1 sequence=4191
channel ch00: restoring archive log
archive log thread=1 sequence=4192
channel ch00: restoring archive log
archive log thread=1 sequence=4193
channel ch00: restoring archive log
archive log thread=1 sequence=4194
channel ch00: restoring archive log
archive log thread=1 sequence=4195
channel ch00: restoring archive log
archive log thread=1 sequence=4196
channel ch00: restoring archive log
archive log thread=1 sequence=4197
channel ch00: restoring archive log
archive log thread=1 sequence=4198
channel ch00: restoring archive log
archive log thread=1 sequence=4199
channel ch00: restoring archive log
archive log thread=1 sequence=4200
channel ch00: restoring archive log
archive log thread=1 sequence=4201
channel ch00: restoring archive log
archive log thread=1 sequence=4202
channel ch00: restoring archive log
archive log thread=1 sequence=4203
channel ch00: restoring archive log
archive log thread=1 sequence=4204
channel ch00: restoring archive log
archive log thread=1 sequence=4205
channel ch00: restoring archive log
archive log thread=1 sequence=4206
channel ch00: restoring archive log
archive log thread=1 sequence=4207
channel ch00: restoring archive log
archive log thread=1 sequence=4208
channel ch00: restoring archive log
archive log thread=1 sequence=4209
channel ch00: restoring archive log
archive log thread=1 sequence=4210
channel ch00: restoring archive log
archive log thread=1 sequence=4211
channel ch00: restoring archive log
archive log thread=1 sequence=4212
channel ch00: restoring archive log
archive log thread=1 sequence=4213
channel ch00: restoring archive log
archive log thread=1 sequence=4214
channel ch00: restoring archive log
archive log thread=1 sequence=4215
channel ch00: restoring archive log
archive log thread=1 sequence=4216
channel ch00: restoring archive log
archive log thread=1 sequence=4217
released channel: ch00
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 12/02/2011 12:23:24
ORA-19507: failed to retrieve sequential file, handle="arch_u50msg690_s160_p1_t768088352", parms=""
ORA-27029: skgfrtrv: sbtrestore returned error
ORA-19511: Error received from media manager layer, error text:
VxBSAValidateFeatureId: Failed with error:
Server Status: cannot connect on socket

RMAN> quit


*********************************************************
Solution:
Found the server name is wrongly specified in the /etc/hosts.
This can also happened if name in bp.conf and /etc/hosts and dns must be matching.
This is normally network related, can be due to firewall sometimes.
*********************************************************