Kinh Nghiệm Việt Nam - Thủ Thuật PC

How to reset General "Chassis intrusion Assert" on SuperMicro

noreply@blogger.com (Unknown) — Wed, 04 Nov 2015 06:23:00 +0000

How to reset General "Chassis intrusion Assert" on SuperMicro

1. Boot CD rom Hirens.BootCD.15.2.iso => Select Linux PartedMagic boot
2. Config IP remote connect

# sudo ifconfig eth0 up
# iconfig eth0 121.30.143.15 netmask 255.255.255.128 broadcast 121.30.143.127
# route add default gw 121.30.143.1

2. SSH Connect to "PartedMagic" default password root is partedmagic
# cd /tmp/
# wget ftp://ftp.supermicro.com/utility/SuperDoctor_II/Linux/Release/SD2_2.111.456-140922.tar.gz
# tar -xvf SD2_2.111.456-140922.tar.gz

root@PartedMagic:/tmp/superdoctor# ./quickinstall
./quickinstall: line 14: /usr/bin/clear: Input/output error
Is there an IPMI BMC card installed in this system? (y/n) y

There are two options that you can choose as the IPMI device drivers.
Linux kernel ver. | Option 1             | Option 2
-------------------+----------------------+----------------------------------
2.4.20 and earlier | YES (Recommended)    | NO
                   | IPMI 1.5/2.0         |
2.4.21 ~ 2.4.25    | YES, IPMI 1.5/2.0    | YES (Recommended), IPMI 1.5 only
2.4.26 and later   | YES, IPMI 1.5/2.0    | YES (Recommended), IPMI 1.5/2.0 *
2.6.6 and earlier | No                   | YES (Recommended), IPMI 1.5 only
2.6.7 and later    | No                   | YES (Recommended), IPMI 1.5/2.0 *
-------------------+----------------------+----------------------------------
* For detail, please read the file doc/README-IPMI.htm.

*** Option 1 (smbmc driver) ***
The smbmc driver is developed by SUPERMICRO and is available at
ftp://ftp.supermicro.com/CDR-0010_2.01_for_IPMI_Server_Managment/IPMI_Solution/Linux/GPC_Agent/

*** Option 2 (IPMI drivers in kernel) ***
These drivers are available in the Linux kernel since 2.4.21 and 2.6.0.
Please have them compiled either into kernel or as modules.

Current Linux kernel ver.: 3.5.6-pmagic
Which option do you like to choose? (1 or 2) 2

List of IPMI device drivers compiled as modules for this kernel(3.5.6-pmagic):
/lib/modules/3.5.6-pmagic/kernel/drivers/char/ipmi:
total 113
-rw-r--r-- 1 root root 8956 Oct 8 2012 ipmi_devintf.ko
-rw-r--r-- 1 root root 32280 Oct 8 2012 ipmi_msghandler.ko
-rw-r--r-- 1 root root 9700 Oct 8 2012 ipmi_poweroff.ko
-rw-r--r-- 1 root root 43836 Oct 8 2012 ipmi_si.ko
-rw-r--r-- 1 root root 19272 Oct 8 2012 ipmi_watchdog.ko
248
grep: /etc/rc.local: No such file or directory

To provide the SNMP function of SuperDoctor II, do as below manually.
1. Add the following line into the file /etc/snmp/snmpd.conf.
     pass .1.3.6.1.4.1.10876 /usr/sbin/sd_extension
2. Restart the SNMP agent.

root@PartedMagic:/tmp/superdoctor# ./sdt.x86

*****************************************************************************
SuperDoctor II - Linux version 2.111(140922)
Copyright(c) 1993-2014 by Super Micro Computer, Inc. http://supermicro.com/
*****************************************************************************
>> Disable monitoring of non-activated item: Fan2 Fan Speed
>> Disable monitoring of non-activated item: Fan4 Fan Speed
>> Disable monitoring of non-activated item: Fan5 Fan Speed
>> Disable monitoring of non-activated item: Fan6 Fan Speed
>> Disable monitoring of non-activated item: FanA Fan Speed

Monitored Item            High Limit Low Limit     Status
----------------------------------------------------------------------
Fan1 Fan Speed                              300       3515
Fan3 Fan Speed                              300       3524
FanB Fan Speed                              300       3534
CPU1 Vcore Voltage              1.49       0.53       0.91
CPU2 Vcore Voltage              1.49       0.53       0.82
VDIMM AB Voltage                1.65       1.20       1.33
VDIMM CD Voltage                1.65       1.20       1.34
VDIMM EFGH Voltage              1.65       1.20       1.34
CPU1 VSA Voltage                1.33       0.53       0.90
CPU2 VSA Voltage                1.33       0.53       0.88
VTT Voltage                     1.34       0.91       1.04
+5VSB Voltage                   5.50       4.48       4.99
+1.5V Voltage                   1.65       1.34       1.49
+5V Voltage                     5.50       4.48       4.99
+12V Voltage                   13.24      10.80      11.97
+3.3V Voltage                   3.65       2.93       3.31
+3.3VSB Voltage                 3.65       2.93       3.26
VBAT Voltage                    3.31       2.69       3.22
CPU1 Temperature              95/203                43/109
CPU2 Temperature              95/203                47/116
System Temperature            85/185                 32/89
Peripheral Temperature        85/185                40/104
PCH Temperature               95/203                45/113
Chassis Intrusion                                      Bad   Warning!
Power Supply Status                                   Good
--------------------------------------------- Wed Nov 4 13:10:25 2015
root@PartedMagic:/tmp/superdoctor# ./sdt.x86 -r "Chassis Intrusion"

*****************************************************************************
SuperDoctor II - Linux version 2.111(140922)
Copyright(c) 1993-2014 by Super Micro Computer, Inc. http://supermicro.com/
*****************************************************************************
Done.
root@PartedMagic:/tmp/superdoctor# ./sdt.x86

*****************************************************************************
SuperDoctor II - Linux version 2.111(140922)
Copyright(c) 1993-2014 by Super Micro Computer, Inc. http://supermicro.com/
*****************************************************************************
Monitored Item            High Limit Low Limit     Status
----------------------------------------------------------------------
Fan1 Fan Speed                              300       3506
Fan3 Fan Speed                              300       3524
FanB Fan Speed                              300       3488
CPU1 Vcore Voltage              1.49       0.53       0.91
CPU2 Vcore Voltage              1.49       0.53       0.82
VDIMM AB Voltage                1.65       1.20       1.33
VDIMM CD Voltage                1.65       1.20       1.34
VDIMM EFGH Voltage              1.65       1.20       1.34
CPU1 VSA Voltage                1.33       0.53       0.88
CPU2 VSA Voltage                1.33       0.53       0.88
VTT Voltage                     1.34       0.91       1.04
+5VSB Voltage                   5.50       4.48       4.99
+1.5V Voltage                   1.65       1.34       1.49
+5V Voltage                     5.50       4.48       4.99
+12V Voltage                   13.24      10.80      11.97
+3.3V Voltage                   3.65       2.93       3.31
+3.3VSB Voltage                 3.65       2.93       3.26
VBAT Voltage                    3.31       2.69       3.22
CPU1 Temperature              95/203                42/107
CPU2 Temperature              95/203                47/116
System Temperature            85/185                 32/89
Peripheral Temperature        85/185                40/104
PCH Temperature               95/203                45/113
Chassis Intrusion                                     Good
Power Supply Status                                   Good
--------------------------------------------- Wed Nov 4 13:10:40 2015
root@PartedMagic:/tmp/superdoctor#

Fix error "This computer can't connect to the remote computer."

noreply@blogger.com (Unknown) — Mon, 04 May 2015 11:29:00 +0000

Problem or Question:

RDP not working
Error: "This computer can't connect to the remote computer. The connection was lost due to a network error. Try connecting again. If the problem continues, contact your network administrator or technical support."

Environment:

RDP

Solution or Answer:

1. Check in Error Log on target Machine for this error:
Event Type: Error
Event Source: TermDD
Event ID: 50
Description: The RDP protocol component "DATA ENCRYPTION" detected an error in the protocol stream and has disconnected the client.
2. Try to delete certificate as the following
3. Start Registry Editor. [Start => regedit] or [Start => Run => regedit]
4. Locate and then click the following registry subkey:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TermService\Parameters

5. Under this registry subkey, delete the following values:

Certificate
X509 Certificate
X509 Certificate ID

6. Quit Registry Editor, and then restart the computer.

VMware ESXI 5.x Shrink LVM without dataloss

noreply@blogger.com (Unknown) — Sat, 02 May 2015 06:30:00 +0000

In Vmware ESXI host

# ls -ltr
total 91829760
-rw-r--r--    1 root     root           265 Apr 4 13:04 copy73 (2).vmxf
-rw-------    1 root     root           516 Apr 22 09:07 copy73.vmdk
-rw-------    1 root     root     25769803776 Apr 22 11:37 copy73-flat.vmdk
-rw-r--r--    1 root     root            43 Apr 23 17:42 copy73 (2).vmsd
-rw-------    1 root     root     25769803776 Apr 23 18:15 copy73_2-flat.vmdk
-rw-r--r--    1 root     root        167490 Apr 23 18:25 vmware-1.log
-rw-------    1 root     root           492 Apr 23 18:28 copy73_2.vmdk
-rw-------    1 root     root           496 Apr 23 18:28 copy73 (2)_2.vmdk
-rw-------    1 root     root           496 Apr 23 18:28 copy73 (2)_1.vmdk
-rw-------    1 root     root     21474836480 Apr 23 18:28 copy73 (2)_2-flat.vmdk
-rw-------    1 root     root     21474836480 Apr 23 18:28 copy73 (2)_1-flat.vmdk
-rw-------    1 root     root          8684 Apr 23 18:36 copy73 (2).nvram
-rw-r--r--    1 root     root        134657 Apr 23 18:36 vmware.log
-rwxr-xr-x    1 root     root          3142 May 1 10:27 copy73 (2).vmx

1. Clone copy disk to backup, before convert
/vmfs/volumes/4a2ea43a-dcf1b3df-3141-00215e74a364/copy73 (2) # vmkfstools -i copy73_2.vmdk copy73_3.vmdk
Destination disk format: VMFS zeroedthick
Cloning disk 'copy73_2.vmdk'...
Clone: 10% done.

2. Edit vitual machine add disk from clone step 1

3. Reboot and check disk
[root@TT4-Web00-S ~]# df -h
Filesystem            Size Used Avail Use% Mounted on
/dev/VolGroup00/LogVol00
                       14G 6.5G 6.5G 50% /
/dev/sda1              99M   13M   82M 14% /boot
tmpfs                 3.0G     0 3.0G   0% /dev/shm
/dev/sdb1              11G 9.0G 593M 94% /u02
/dev/sdc1              20G 8.0G   11G 43% /u03
[root@TT4-Web00-S ~]#

4. Boot Troubleshooting => Rescue a CentOS system
Use: CentOS-7-x86_64-DVD-1503-01.iso

5. Check volume group name
bash-3.2# lvm vgscan
Reading all physical volumes. This may take a while...
Found volume group "VolGroup00" using metadata type lvm2

bash-3.2# lvm vgchange -a y
2 logical volume(s) in volume group "VolGroup00" now active

bash-3.2# ls /dev/VolGroup00/
LogVol00 LogVol01

6. You can display information about the logical volumes using lvm lvs
bash-3.2# lvm lvs
LV       VG         Attr   LSize Origin Snap% Move Log Copy% Convert
LogVol00 VolGroup00 -wi-ao 14.12G
LogVol01 VolGroup00 -wi-ao 9.75G

7. Display Logical Volumes
bash-3.2# lvdisplay
--- Logical volume ---
LV Name                /dev/VolGroup00/LogVol00
VG Name                VolGroup00
LV UUID                zG2Jef-Jn3f-gqgj-VsCX-OCBd-jcpM-n0spR8
LV Write Access        read/write
LV Status              available
# open                 1
LV Size                14.12 GB
Current LE             452
Segments               1
Allocation             inherit
Read ahead sectors     auto
- currently set to     256
Block device           253:0

--- Logical volume ---
LV Name                /dev/VolGroup00/LogVol01
VG Name                VolGroup00
LV UUID                ceUxVm-GypP-PNRR-WPFP-sUqv-MhPB-CWRgeu
LV Write Access        read/write
LV Status              available
# open                 1
LV Size                9.75 GB
Current LE             312
Segments               1
Allocation             inherit
Read ahead sectors     auto
- currently set to     256
Block device           253:1

bash-3.2# vgscan
Reading all physical volumes. This may take a while...
Found volume group "VolGroup00" using metadata type lvm2
bash-3.2# lvscan
ACTIVE            '/dev/VolGroup00/LogVol00' [14.12 GB] inherit
ACTIVE            '/dev/VolGroup00/LogVol01' [9.75 GB] inherit

bash-3.2# vgdisplay
--- Volume group ---
VG Name               VolGroup00
System ID
Format                lvm2
Metadata Areas        1
Metadata Sequence No 3
VG Access             read/write
VG Status             resizable
MAX LV                0
Cur LV                2
Open LV               2
Max PV                0
Cur PV                1
Act PV                1
VG Size               23.88 GB
PE Size               32.00 MB
Total PE              764
Alloc PE / Size       764 / 23.88 GB
Free PE / Size       0 / 0
VG UUID               zeIZpI-rZkO-MKFA-NgAC-OuU5-rt7f-jwRHQB

7. Resize to from 14G to 10G data
[root@livecd ~]# e2fsck -f /dev/VolGroup00/LogVol00
e2fsck 2.39 (29-May-2006)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/VolGroup00/LogVol00: 92069/4704768 files (1.3% non-contiguous), 1285660/4702208 blocks

[root@livecd ~]# resize2fs /dev/VolGroup00/LogVol00 10G
resize2fs 1.39 (29-May-2006)
Resizing the filesystem on /dev/VolGroup00/LogVol00 to 2097152 (4k) blocks.
The filesystem on /dev/VolGroup00/LogVol00 is now 2097152 blocks long.

[root@livecd ~]# lvreduce -L 10G /dev/VolGroup00/LogVol00
WARNING: Reducing active logical volume to 10.00 GB
THIS MAY DESTROY YOUR DATA (filesystem etc.)
Do you really want to reduce LogVol00? [y/n]: y
Reducing logocal volume LogVol00 to 10.00 GB
Logical volume LogVol00 successfully resized

bash-3.2# lvdisplay /dev/VolGroup00/LogVol00
--- Logical volume ---
LV Name                /dev/VolGroup00/LogVol00
VG Name                VolGroup00
LV UUID                zG2Jef-Jn3f-gqgj-VsCX-OCBd-jcpM-n0spR8
LV Write Access        read/write
LV Status              available
# open                 1
LV Size                10 GB
Current LE             320
Segments               1
Allocation             inherit
Read ahead sectors     auto
- currently set to     256
Block device           253:0

[root@livecd ~]# pvscan
    PV /dev/sda22   VG VolGroup00   lvm2 [23.88 GB / 4.12 GB free]
Total: 1 [23.88 GB] / in use: 1 [23.88 GB] / in no VG: 0 [0   ]

[root@livecd ~]# lvscan
ACTIVE    '/dev/VolGroup00/LogVol00' [10.00 GB] inherit
ACTIVE    '/dev/VolGroup00/LogVol01' [9.75 GB] inherit

8. Remove Volume Swap
[root@livecd ~]# lvremove /dev/VolGroup00/LogVol01
Can't remove open logical volume "LogVol01"

[root@livecd ~]# swapoff /dev/VolGroup00/LogVol01

[root@livecd ~]# lvremove /dev/VolGroup00/LogVol01
Do you really want to remove active logical volume LogVol01? [y/n]:y
Logical volume "LogVol01" successfully removed

[root@livecd ~]# lvcreate -L 2G -n LogVol01 VolGroup00
Logical volume "LogVol01" created

[root@livecd ~]# mkswap /dev/VolGroup00/LogVol01
Setting up swapspace vrsion 1, size = 2147479 kB

[root@livecd ~]# swapon /dev/VolGroup00/LogVol01

[root@livecd ~]# pvscan
PV /dev/sda2   VG VolGroup00   lvm2 [23.88GB / 11.88 GB free]
Total: 1 [23.88 GB] / in use: 1 [23.88 GB] / in on FV: 0 [0   ]

[root@livecd ~]# pvresize --setphysicalvolumesize 12G /dev/sda2
/dev/sda2: cannot resize to 383 extents as 384 are allocated.
0 physical volume(s) resized / 1 physical volumes(s) not resized

[root@livecd ~]# pvresize --setphysicalvolumesize 12500M /dev/sda2
Physical volume "/dev/sda2" changed
1 physical volume(s) resized / 0 physical volumes(s) not resized

[root@livecd ~]# pvscan
PV /dev/sda2   VG VolGroup00   lvm2 [12.19　GB / 192.00 MB free]
Total: 1 [12.19 GB] / in use: 1 [12.19 GB] / in on FV: 0 [0   ]

12500M-192M = 12308M

[root@livecd ~]# pvresize --setphysicalvolumesize 12308M /dev/sda2
Physical volume "/dev/sda2" changed
1 physical volume(s) resized / 0 physical volumes(s) not resized

[root@chuo221 ~]# pvscan
PV /dev/sda2   VG VolGroup00   lvm2 [12.00 GB / 0    free]
Total: 1 [12.00 GB] / in use: 1 [12.00 GB] / in no VG: 0 [0   ]

9. Shrinking VMWare disk

Calculate the desired size
vmdk_shrunken = [x * (1024*1024*1024)] / 512
where x is the size in Gigabytes

=> [12 * (1024*1024*1024)] / 512 = 25165824

Change to the desired size

Locate the lines that look like:
# Extent description
RW 25165824 VMFS “foo-flat.vmdk”

/vmfs/volumes/4a2ea43a-dcf1b3df-3141-00215e74a364/copy73 (2) # vi copy73_3.vmdk

# Disk DescriptorFile
version=1
encoding="UTF-8"
CID=c0e13e2a
parentCID=ffffffff
isNativeSnapshot="no"
createType="vmfs"

# Extent description
RW 25165824 VMFS "copy73_3-flat.vmdk"

# The Disk Data Base
#DDB

ddb.adapterType = "lsilogic"
ddb.deletable = "true"
ddb.geometry.cylinders = "3133"
ddb.geometry.heads = "255"
ddb.geometry.sectors = "63"
ddb.longContentID = "67a55ef19ceef3110ed453dec0e13e2a"
ddb.uuid = "60 00 C2 9c a1 49 6f 68-bb 51 38 e1 15 63 5c 5d"
ddb.virtualHWVersion = "7"

10 Export to a new VMDK

/vmfs/volumes/4a2ea43a-dcf1b3df-3141-00215e74a364/copy73 (2) # vmkfstools -i copy73_3.vmdk copy73_4.vmdk
Destination disk format: VMFS zeroedthick
Cloning disk 'copy73_3.vmdk'...
Clone: 49% done.

Remove old disk from VM, add new disk to VM
Remove VM from inventory, Re-add VM to inventory

http://technogrip.blogspot.com/2012/04/shrinking-linux-centos-lvm-disk-on.html
http://www.vmwarearena.com/2013/03/shrink-virtual-machine-vmdk.html

11. Fixing LVM I/O Errors

[root@TT4-Web00-S ~]# pvscan
/dev/sda2: read failed after 0 of 4096 at 25662783488: Input/output error
/dev/sda2: read failed after 0 of 4096 at 25662865408: Input/output error
PV /dev/sda2   VG VolGroup00   lvm2 [12.97 GB / 992.00 MB free]
Total: 1 [12.97 GB] / in use: 1 [12.97 GB] / in no VG: 0 [0   ]

[root@TT4-Web00-S ~]# fdisk /dev/sda

The number of cylinders for this disk is set to 1958.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
   (e.g., DOS FDISK, OS/2 FDISK)

Command (m for help): p

Disk /dev/sda: 16.1 GB, 16106127360 bytes
255 heads, 63 sectors/track, 1958 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id System
/dev/sda1   *           1          13      104391   83 Linux
/dev/sda2              14        3133    25061400   83 Linux

Command (m for help): d
Partition number (1-4): 2

Command (m for help): p

Disk /dev/sda: 16.1 GB, 16106127360 bytes
255 heads, 63 sectors/track, 1958 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id System
/dev/sda1   *           1          13      104391   83 Linux

Command (m for help): n
Command action
   e   extended
   p   primary partition (1-4)
p
Partition number (1-4): 2
First cylinder (14-1958, default 14): 14
Last cylinder or +size or +sizeM or +sizeK (14-1958, default 1958): 1958

Command (m for help): t
Partition number (1-4): 2
Hex code (type L to list codes): 8e
Changed system type of partition 2 to 8e (Linux LVM)

Command (m for help): p

Disk /dev/sda: 16.1 GB, 16106127360 bytes
255 heads, 63 sectors/track, 1958 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id System
/dev/sda1   *           1          13      104391   83 Linux
/dev/sda2              14        1958    15623212+ 8e Linux LVM

Command (m for help): w
The partition table has been altered!

Calling ioctl() to re-read partition table.

WARNING: Re-reading the partition table failed with error 16: Device or resource busy.
The kernel still uses the old table.
The new table will be used at the next reboot.
Syncing disks.
reboot ...done

Fix [INS-40718] Single Client Access Name (SCAN):clus-scan could not be resolved.

noreply@blogger.com (Unknown) — Wed, 15 Apr 2015 10:41:00 +0000

Two host machines with following settings

rac1.dbaora.com
rac2.dbaora.com

	public	private	vip
rac1	192.168.0.50	192.168.56.60	192.168.0.70
rac2	192.168.0.51	192.168.56.61	192.168.0.71

with single client access name (SCAN) address

	public
rac-scan	192.168.0.20 192.168.0.21 192.168.0.22

My WIFI router generates ip adress like 192.168.1.X so it doesn’t interfere with RAC public, private and SCAN. It’s important to have your internet network on separate subnet.

So my entry in “/ect/hosts” looks following. As you can notice SCAN entries are commented and will be resolved via dnsmasq.

127.0.0.1     localhost.localdomain localhost

#public
192.168.0.50   rac1        rac1.dbaora.com
192.168.0.51   rac2        rac2.dbaora.com

#private
192.168.56.60  rac1-priv   rac1-priv.dbaora.com 
192.168.56.61  rac2-priv   rac2-priv.dbaora.com

#virtual
192.168.0.70   rac1-vip    rac1-vip.dbaora.com
192.168.0.71   rac2-vip    rac2-vip.dbaora.com

#scan
#192.168.0.20   rac-scan    rac-scan.dbaora.com
#192.168.0.21   rac-scan    rac-scan.dbaora.com
#192.168.0.22   rac-scan    rac-scan.dbaora.com

Install and configure dnsmasq

1. To install dnsmasq run as root following command

yum install dnsmasq

2. Configure dnsmasq
create new file “/etc/racdns” with settings for SCAN

[root@rac1 ~]# cat /etc/racdns
#scan
192.168.0.20   rac-scan    rac-scan.dbaora.com
192.168.0.21   rac-scan    rac-scan.dbaora.com
192.168.0.22   rac-scan    rac-scan.dbaora.com

modify dnsmasq default configuration file “/etc/dnsmasq.conf”. One parameter addn-hosts should be changed to point to file “/etc/racdns”.

[root@rac1 ~]# cat /etc/dnsmasq.conf | grep addn-hosts
addn-hosts=/etc/racdns

3. Start dnsmasq

service dnsmasq start
chkconfig dnsmasq on

4. Next step is to resolve problem with file “/etc/resolv.conf”
I’m using third network card as NAT with DHCP so each time you restart network card or reboot host the file is overwritten with automatically generated settings. Nameserver points for 192.168.1.1 which is required to resolve internet entries but not enough to resolve SCAN settings via dnsmasq.

[root@rac1 ~]# cat /etc/resolv.conf
# Generated by Networkmanager
search dbaora.com
nameserver 192.168.1.1

As default dnsmasq is running on ip adress 127.0.0.1 so it requires following settings in “/etc/resolv.conf”.

[root@rac1 ~]# cat /etc/resolv.conf
# Generated by Networkmanager
nameserver 127.0.0.1
search dbaora.com
nameserver 192.168.1.1

You must protect the file from being automatically overwritten by host reboot, network card restart etc.

[root@rac1 ~]# chattr +i /etc/resolv.conf

Verification
It’s just running nslookup to verify all is working fine
rac-scan

[root@rac1 ~]# nslookup rac-scan
Server:        127.0.0.1
Address:    127.0.0.1#53

Name:    rac-scan.dbaora.com
Address: 192.168.0.22
Name:    rac-scan.dbaora.com
Address: 192.168.0.20
Name:    rac-scan.dbaora.com
Address: 192.168.0.21

[root@rac1 ~]# nslookup rac-scan
Server:        127.0.0.1
Address:    127.0.0.1#53

Name:    rac-scan.dbaora.com
Address: 192.168.0.20
Name:    rac-scan.dbaora.com
Address: 192.168.0.21
Name:    rac-scan.dbaora.com
Address: 192.168.0.22

[root@rac1 ~]# nslookup rac-scan
Server:        127.0.0.1
Address:    127.0.0.1#53

Name:    rac-scan.dbaora.com
Address: 192.168.0.21
Name:    rac-scan.dbaora.com
Address: 192.168.0.22
Name:    rac-scan.dbaora.com
Address: 192.168.0.20

rac1, rac2, rac1-priv, rac2-priv, rac1-vip, rac2-vip

[root@rac1 ~]# nslookup rac1
Server:        127.0.0.1
Address:    127.0.0.1#53

Name:    rac1.dbaora.com
Address: 192.168.0.50

[root@rac1 ~]# nslookup rac2
Server:        127.0.0.1
Address:    127.0.0.1#53

Name:    rac2.dbaora.com
Address: 192.168.0.51

[root@rac1 ~]# nslookup rac1-priv
Server:        127.0.0.1
Address:    127.0.0.1#53

Name:    rac1-priv.dbaora.com
Address: 192.168.56.60

[root@rac1 ~]# nslookup rac2-priv
Server:        127.0.0.1
Address:    127.0.0.1#53

Name:    rac2-priv.dbaora.com
Address: 192.168.56.61

[root@rac1 ~]# nslookup rac1-vip
Server:        127.0.0.1
Address:    127.0.0.1#53

Name:    rac1-vip.dbaora.com
Address: 192.168.0.70

[root@rac1 ~]# nslookup rac2-vip
Server:        127.0.0.1
Address:    127.0.0.1#53

Name:    rac2-vip.dbaora.com
Address: 192.168.0.71

Have a fun

How to install Oracle RAC 12C using Oracle Linux 6.4 on VMware 5.x

noreply@blogger.com (Unknown) — Wed, 15 Apr 2015 10:02:00 +0000

Installing a Virtualized Oracle 12cR1 RAC Cluster using Oracle Linux 6.4 Virtual Machines on VMware ESXi 5

Last updated 27-Sep-2013

A new release of Oracle means it’s time for a new walkthrough. In this fourth “RAC on ESX” walkthrough, I’ll go over the process of building an Oracle 12c RAC cluster on VMware ESXi 5 from start to finish. My goal in this walkthrough is to have you up and running with a virtualized Oracle cluster with minimal hassle. Since this guide is step by step, you don't need to be an expert to follow along, but the more experience you have the better.
The following diagram will give you a conceptual idea of the cluster.

As I’ve mentioned in previous walkthroughs, this configuration is meant only for testing, and to give you a way to learn RAC without buying the expensive hardware a traditional RAC cluster entails. If you’re building a production RAC cluster, I suggest you read the Grid Infrastructure and RAC installation guides, and the RAC Administration and Deployment Guide. The following MOS (My Oracle Support) notes will also provide you with guidance (this requires an Oracle support subscription):

RAC and Oracle Clusterware Best Practices and Starter Kit (Platform Independent) (Doc ID 810394.1)
RAC: Frequently Asked Questions (Doc ID 220970.1)

The following is required in order to succeed in following this guide:
Hardware Requirements

An operational VMware ESXi 5 server.
80GB of available space in your ESX storage location (30GB of storage for each virtual machine, and 20GB of shared storage).
8GB available RAM for virtual machines (4GB per virtual machine).

Software Requirements

The Oracle Linux 6.4 x86_64 Installation ISO. This is freely available at https://edelivery.oracle.com/linux.
The Grid Infrastructure and Oracle Database 12.1.0.1.0 installation media. Licensed customers can download the media through edelivery. The media can also be downloaded from OTN under the OTN license agreement. The OTN download URL is http://www.oracle.com/technetwork/database/enterprise-edition/downloads/database12c-linux-download-1959253.html.

Network Requirements
We will need 9 IP addresses for the RAC cluster. 2 public communication IP addresses, 2 Virtual IPs, 2 Interconnect IP addresses, and 3 SCAN (single client access name) addresses. The public communication IP addresses, SCAN addresses, and VIP addresses need to be on the same segment. The private addresses need to be on their own segment. This is how it looks in my network:

Node Hostname	Public IP	Interconnect IP	VIP
node1.example.com	192.168.2.220	10.0.0.1	192.168.2.222
node2.example.com	192.268.2.221	10.0.0.2	102.168.2.223

Lastly our SCAN addresses will be 192.168.2.117, 192.168.2.118, and 192.168.2.119. The SCAN addresses should be configured in DNS rather than in the hosts file, as 3 round-robin A records. If you don't have DNS configured, or are unable to configure DNS, you can place the SCAN addresses in the hosts file. Placing the SCAN addresses in the host file is against best practices. I gave them a name of clus-scan. Make sure these addresses are resolvable from the nodes.

Your networking environment is probably different from mine. Feel free to configure the IPs to be on whatever network segment you use, just make sure that the Public IPs, SCAN addresses, and VIPs are on the same segment. If you do use different addresses, make sure to use them during the OS install and update /etc/hosts appropriately.

Hypervisor Configuration and Virtual Machine Creation

Each RAC node requires two network connections; one connection is for public communication, and the other is for the Interconnect. In order to isolate Interconnect traffic, we will create a virtual switch as shown below. It's likely that the RAC Interconnect will work without following this step, however I haven't tested this and Interconnect traffic is supposed to be isolated over its own VLAN or switch in the real world anyway.

Virtual Switch Creation
Log into the ESXi host using the vSphere client, select the host, and click the "Configuration" tab.

Click "Networking" in the "Hardware" box.

Click "Add Networking..." in the upper right corner of the pane.

Select "Virtual Machine" as the connection type and click the "Next" button.

Make sure "Create a vSphere standard switch" is selected, and click the "Next" button.

I used "RAC Interconnect" as my network label. Feel free to use any label you want to, and click the "Next" button.

Click "Finish" to create the virtual switch.

Virtual Machine Creation

Right click on the ESXi host, and click "New Virtual Machine..." to begin the process.

Select the "Custom" configuration option.

Set "node1.example.com" as the virtual machine name.

Select the storage location for the virtual machine files.

Select "Virtual Machine Version: 8."

Select "Linux" as the guest operating system, and then select "Oracle Linux 4/5/6 (64-bit)" from the version dropdown.

I just left this screen set to the defaults, but you can change them if needed.

Set the memory size to 4236MB. You'll notice this is slightly more than the required 4GB. I am doing this because the virtual machine reserves a small amount of memory that isn't visible to the guest operating system. Setting this amount of memory allows the guest to have a full 4GB available. The Cluster Verification Utility memory check will fail otherwise.

Configure the networking as shown below. Make sure that this setting is consistent across all RAC nodes.

I left the controller setting at the default, but you can change it if you have a specific reason to do so.

Select "Create a new virtual disk."

Set the disk size to 30GB, and select "Thick Provision Eager Zeroed."

I left these settings at their defaults.

Click the "Finish" button to create the virtual machine. This may take some time to complete.

Next, the second cluster node virtual machine will be created. Repeat the same process you used for node1, but use "node2.example.com" as the name of the virtual machine instead.

Oracle Linux Installation

As listed in the prerequisites section, you'll need the Oracle Linux 6.4 installation ISO to follow this guide. You can mount it in the virtual machine by selecting the virtual machine, then mounting the ISO as shown below. The screenshot below has me mounting the ISO from the datastore, but you can also mount it from a local ISO image (which means the installation will run over the network). On my hypervisor that option is grayed out until I turn on the virtual machine.

Select the newly created virtual machine, and click the play button to start it.

Once the virtual machine is started, you can view its console by right clicking on it and then clicking "Open Console."

From the console of the virtual machine, you can mount the ISO.

From my virtual machine, I clicked "Send Ctrl+Alt+del" in order to restart it and boot from the installation ISO.

The virtual machine will boot from the ISO. Press enter to proceed with the default installation option.

I selected "Skip." Feel free to test the installation media if you want to.

The graphical installation will commence.

Select your desired language.

Select your desired keyboard.

Select "Basic Storage Devices."

You may see a warning pop up, in which case you can click "Yes, discard any data."

Type in "node1.example.com" or a different hostname if you prefer. Click "Configure Network."

Select "System eth0," and then click "Edit."

Configure the network settings for the public interface as required. Make sure that "Connect automatically" is checked. I left IPv6 turned off, which is the default. Click "Apply" when you're finished.

Select "System eth1," and then click "Edit."

Configure the network settings for the private interface as required. Make sure that "Connect automatically" is checked. I left IPv6 turned off, which is the default. Click "Apply" when you're finished, and then click the "Close" button when the "Network Connections" screen pops up.

Select your desired time zone.

Enter a password for the root user.

Select "Use All Space." Click "Write changes to disk" when the warning pops up.

Change the installation type from "Basic Server" to "Minimal."

The dependency check will run and then the installation process will begin.

The installation is finished.

The Oracle Linux installation is now complete on node1. Repeat the process on node2, but make sure to use the correct hostname and IP address. The fully-qualified hostname for node2 is node2.example.com. Use the same root password on both nodes.

Pre-installation Tasks

All steps are run on both nodes as the root user, unless specified otherwise.
Disable SELinux

{
echo \# This file controls the state of SELinux on the system.
echo \# SELINUX= can take one of these three values:
echo \# enforcing - SELinux security policy is enforced.
echo \# permissive - SELinux prints warnings instead of enforcing.
echo \# disabled - No SELinux policy is loaded.
echo SELINUX=disabled
echo \# SELINUXTYPE= can take one of these two values:
echo \# targeted - Targeted processes are protected,
echo \# mls - Multi Level Security protection.
echo SELINUXTYPE=targeted
} > /etc/selinux/config

The node must be rebooted in order for the change to take effect (reboot or shutdown -r now). You can verify the change by running getenforce. The output should be "Disabled."

Install Required OS Packages

yum install compat-libcap1.x86_64 compat-libstdc++-33.x86_64 gcc.x86_64 gcc-c++.x86_64 glibc-devel.x86_64 ksh.x86_64 libstdc++-devel.x86_64 libaio-devel.x86_64 libXmu.x86_64 libXxf86dga.x86_64 libXxf86misc.x86_64 libdmx.x86_64 make.x86_64 nfs-utils.x86_64 sysstat.x86_64 mlocate.x86_64 compat-libstdc++-33.i686 glibc-devel.i686 libstdc++.i686 libstdc++-devel.i686 libaio-devel.i686 glibc.i686 libgcc.i686 libaio-devel.i686 libXext.i686 libXtst.i686 libX11.i686 libXau.i686 libxcb.i686 libXi.i686 xorg-x11-twm.x86_64 xorg-x11-server-utils.x86_64 xorg-x11-utils.x86_64 xorg-x11-xauth.x86_64 oracleasm-support.x86_64 tigervnc-server.x86_64 xterm.x86_64 ntp.x86_64 nscd.x86_64 openssh-clients.x86_64 unzip.x86_64 smartmontools.x86_64 parted.x86_64 wget.x86_64 bind-utils.x86_64 -y

Check all package install

rpm -q --qf '%{NAME}-%{VERSION}-%{RELEASE}(%{ARCH})\n' compat-libcap1.x86_64 compat-libstdc++-33.x86_64 gcc.x86_64 gcc-c++.x86_64 glibc-devel.x86_64 ksh.x86_64 libstdc++-devel.x86_64 libaio-devel.x86_64 libXmu.x86_64 libXxf86dga.x86_64 libXxf86misc.x86_64 libdmx.x86_64 make.x86_64 nfs-utils.x86_64 sysstat.x86_64 mlocate.x86_64 compat-libstdc++-33.i686 glibc-devel.i686 libstdc++.i686 libstdc++-devel.i686 libaio-devel.i686 glibc.i686 libgcc.i686 libaio-devel.i686 libXext.i686 libXtst.i686 libX11.i686 libXau.i686 libxcb.i686 libXi.i686 xorg-x11-twm.x86_64 xorg-x11-server-utils.x86_64 xorg-x11-utils.x86_64 xorg-x11-xauth.x86_64 oracleasm-support.x86_64 tigervnc-server.x86_64 xterm.x86_64 ntp.x86_64 nscd.x86_64 openssh-clients.x86_64 unzip.x86_64 smartmontools.x86_64 parted.x86_64 wget.x86_64 bind-utils.x86_64

The ASMlib tools package (oracleasmlib-2.0.4-1.el6) is not available on the public YUM repository, so we will download it and install it manually.

wget http://download.oracle.com/otn_software/asmlib/oracleasmlib-2.0.4-1.el6.x86_64.rpm
rpm -iv oracleasmlib-2.0.4-1.el6.x86_64.rpm

Configure System Services

chkconfig iptables off && /etc/init.d/iptables stop && \
chkconfig ip6tables off && /etc/init.d/ip6tables stop && \
chkconfig nscd on && /etc/init.d/nscd start && \
chkconfig ntpd on

Configure the Network Time Protocol Daemon

{
echo OPTIONS=\"-x -u ntp:ntp -p /var/run/ntpd.pid\"
} > /etc/sysconfig/ntpd

I changed the following lines in /etc/ntp.conf:

server 0.rhel.pool.ntp.org
server 1.rhel.pool.ntp.org
server 2.rhel.pool.ntp.org

To the following:

server nist1-ny.ustiming.org
server nist.time.nosc.us
server nist1-la.ustiming.org

Feel free to use any NTP servers you want, or leave it at the defaults. I changed the NTP servers in my configuration in order to avoid the "PRVF-5408 : NTP Time Server is common only to the following node" errors that occur when the Cluster Verification Utility runs.
Synchronize time on our nodes using ntpdate (use any NTP server you want):

ntpdate nist1-ny.ustiming.org

Start ntpd:

/etc/init.d/ntpd start

PRVF-5413 : Node "node1" has a time offset of -2355.8 that is beyond permissible limit of 1000.0 from NTP Time Server ".LOCL."

Login using root user and execute on both nodes one by one.

[root@node2 ~]# service ntpd stop
[root@node2 ~]# ntpdate 10.151.110.28
[root@node2 ~]# service ntpd start

[root@node1 ~]# service ntpd stop
[root@node1 ~]# ntpdate 10.151.110.28
[root@node1 ~]# service ntpd start

Now, crosscheck the output with below command.

[root@ ~]# ssh node2 date;ssh node1 date

Configure /etc/hosts

{
echo \#Do not remove the following line, or various programs
echo \# that require network functionality will fail.
echo 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
echo ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
echo
echo \#public
echo 192.168.2.220 node1 node1.example.com
echo 192.168.2.221 node2 node2.example.com
echo
echo \#private
echo 10.0.0.1 node1-priv node1-priv.example.com
echo 10.0.0.2 node2-priv node2-priv.example.com
echo
echo \#vip
echo 192.168.2.222 node1-vip node1-vip.example.com
echo 192.168.2.223 node2-vip node2-vip.example.com
} > /etc/hosts

Configure the Shared Memory Filesystem
Open /etc/fstab and change the following line:

tmpfs /dev/shm tmpfs defaults 0 0

To the following:

tmpfs /dev/shm tmpfs rw,exec,size=4G 0 0

Then remount the file system:

mount -o remount /dev/shm

Set Linux Kernel Parameters

{
echo
echo \# BEGIN ORACLE RAC KERNEL PARAMETERS
echo \# kernel.shmall = 1/2 of physical memory in pages
echo \# See MOS note 301830.1
echo kernel.shmall = 2097152
echo \# kernel.shmmax = 1/2 of physical memory in bytes
echo \# See MOS note 567506.1
echo kernel.shmmax = 2148726784
echo kernel.shmmni = 4096
echo kernel.sem = 250 32000 100 128
echo fs.file-max = 6815744
echo fs.aio-max-nr = 1048576
echo net.ipv4.ip_local_port_range = 9000 65500
echo net.core.rmem_default = 262144
echo net.core.rmem_max = 4194304
echo net.core.wmem_default = 262144
echo net.core.wmem_max = 1048576
echo \# END ORACLE RAC KERNEL PARAMETERS
} >> /etc/sysctl.conf

/sbin/sysctl -p

Create and Configure OS Groups, Users, Directories, and Permissions

groupadd -g 1000 oinstall
groupadd -g 1100 asmadmin
groupadd -g 1200 dba
groupadd -g 1201 oper
groupadd -g 1202 backupdba
groupadd -g 1203 dgdba
groupadd -g 1204 kmdba
groupadd -g 1300 asmdba
groupadd -g 1301 asmoper
useradd -u 1100 -g oinstall -G asmadmin,asmdba,asmoper,dba grid
useradd -u 1101 -g oinstall -G dba,oper,asmdba,backupdba,dgdba,kmdba oracle
mkdir -p /u01/app/grid
mkdir -p /u01/app/12.1.0/grid
chown -R grid:oinstall /u01
mkdir -p /u01/app/oracle
chown oracle:oinstall /u01/app/oracle
chmod -R 775 /u01

After the oracle and grid users have been created, set passwords for the accounts with "passwd oracle" and "passwd grid"

Set Shell Limits for the Oracle and Grid Users

{
echo
echo "if [ \$USER = "oracle" ] || [ \$USER = "grid" ]"
echo "then"
echo " if [ \$SHELL = "/bin/ksh" ]"
echo " then"
echo " ulimit -p 16384"
echo " ulimit -n 65536"
echo " else"
echo " ulimit -u 16384 -n 65536"
echo " fi"
echo " umask 022"
echo "fi"
} >> /etc/profile

{
echo
echo "oracle soft nproc 2047"
echo "oracle hard nproc 16384"
echo "oracle soft nofile 1024"
echo "oracle hard nofile 65536"
echo "oracle soft stack 10240"
echo "oracle hard stack 10240"
echo "grid soft nproc 2047"
echo "grid hard nproc 16384"
echo "grid soft nofile 1024"
echo "grid hard nofile 65536"
echo "grid soft stack 10240"
echo "grid hard stack 10240"
} >> /etc/security/limits.conf

{
echo
echo \# Default limit for number of user\'s processes to prevent
echo \# accidental fork bombs.
echo \# See rhbz \#432903 for reasoning.
echo \# Update: this limit has been ammended for Oracle RAC
echo \# See MOS note 1487773.1
echo
echo \# \* soft nproc 1024
echo \* - nproc 1024
echo root soft nproc unlimited
} > /etc/security/limits.d/90-nproc.conf

{
echo
echo session required pam_limits.so
} >> /etc/pam.d/login

Configure the Bash Profiles for the Oracle and Grid Users
Run the following on node1:

{
echo
echo "export EDITOR=vi"
echo "export ORACLE_HOME=/u01/app/oracle/product/12.1.0/dbhome_1"
echo "export ORACLE_BASE=/u01/app/oracle"
echo "export PATH=\$PATH:\$ORACLE_HOME/bin:\$ORACLE_HOME/OPatch"
echo "export ORACLE_SID=ORCL1"
echo "export ORACLE_UNQNAME=ORCL"
echo "export LD_LIBRARY_PATH=\$ORACLE_HOME/lib"
echo
} >> /home/oracle/.bash_profile

{
echo
echo "export EDITOR=vi"
echo "export ORACLE_HOME=/u01/app/12.1.0/grid"
echo "export ORACLE_BASE=/u01/app/grid"
echo "export PATH=\$PATH:\$ORACLE_HOME/bin:\$ORACLE_HOME/OPatch"
echo "export ORACLE_SID=+ASM1"
echo "export LD_LIBRARY_PATH=\$ORACLE_HOME/lib"
echo
} >> /home/grid/.bash_profile

Run the following on node2:

{
echo
echo "export EDITOR=vi"
echo "export ORACLE_HOME=/u01/app/oracle/product/12.1.0/dbhome_1"
echo "export ORACLE_BASE=/u01/app/oracle"
echo "export PATH=\$PATH:\$ORACLE_HOME/bin:\$ORACLE_HOME/OPatch"
echo "export ORACLE_SID=ORCL2"
echo "export ORACLE_UNQNAME=ORCL"
echo "export LD_LIBRARY_PATH=\$ORACLE_HOME/lib"
echo
} >> /home/oracle/.bash_profile

{
echo
echo "export EDITOR=vi"
echo "export ORACLE_HOME=/u01/app/12.1.0/grid"
echo "export ORACLE_BASE=/u01/app/grid"
echo "export PATH=\$PATH:\$ORACLE_HOME/bin:\$ORACLE_HOME/OPatch"
echo "export ORACLE_SID=+ASM2"
echo "export LD_LIBRARY_PATH=\$ORACLE_HOME/lib"
echo
} >> /home/grid/.bash_profile

Configure SSH Equivalency for the Oracle and Grid Users

We will start with the Oracle user. Start this process as the root user. On each node run the following to generate the RSA keys. Use the default key location, and leave the passphrase blank.

su - oracle
mkdir ~/.ssh
chmod 700 ~/.ssh
ssh-keygen -t rsa

The following commands will append the public keys to the authorized_keys file. Run the following on node1:

touch ~/.ssh/authorized_keys
cd ~/.ssh

Now run the following on node1 to authorize the RSA key on node1:

cat /home/oracle/.ssh/id_rsa.pub >> authorized_keys

Next run the following on node1 to authorize the RSA key on node2:

ssh node2 cat /home/oracle/.ssh/id_rsa.pub >> authorized_keys

Our keys have been appended to the authorized_keys file, and now we must copy this file to the second node. Run the following on node1:

scp authorized_keys node2:/home/oracle/.ssh

Run the following on each node:

chmod 600 /home/oracle/.ssh/authorized_keys

Next we will test equivalency on each node. On node2 you will be asked if you wish to continue connecting. Type yes. You should not see this warning again. Your output should look like the following:

[oracle@node1 ~]$ ssh node1 date
Thu Sep 19 08:54:09 CDT 2013
[oracle@node1 ~]$ ssh node2 date
Thu Sep 19 08:54:10 CDT 2013

Now we will configure equivalency for the grid user. On each node run the following to generate the RSA keys. Use the default key location, and leave the passphrase blank.

su - grid
mkdir ~/.ssh
chmod 700 ~/.ssh
ssh-keygen -t rsa

The following commands will append the public keys to the authorized_keys file. Run the following on node1:

touch ~/.ssh/authorized_keys
cd ~/.ssh

Now run the following on node1 to authorize the RSA key on node1:

cat /home/grid/.ssh/id_rsa.pub >> authorized_keys

Next run the following on node1 to authorize the RSA key on node2:

ssh node2 cat /home/grid/.ssh/id_rsa.pub >> authorized_keys

Our keys have been appended to the authorized_keys file, (Run the following on node1) and now we must copy this file to the second node.

scp authorized_keys node2:/home/grid/.ssh

Run the following on each node:

chmod 600 /home/grid/.ssh/authorized_keys

Next we will test equivalency on each node. On node2 you will be asked if you wish to continue connecting. Type yes. You should not see this warning again. Your output should look like the following:

[grid@node1 .ssh]$ ssh node1 date
Fri Jan 28 01:40:30 CST 2011
[grid@node1 .ssh]$ ssh node2 date
Fri Jan 28 01:40:32 CST 2011

Installation Media Preparation
I transferred the compressed grid installation media to the grid user's home directory. I transferred the media to the node from a Windows system with WinSCP, which can be downloaded for free from http://winscp.net/eng/download.php. When I used WinSCP, I connected to the node using the grid user; this will assure that the grid user will have ownership permissions on the compressed media. I did the same thing for the database installation media, except I connected with the oracle user.

[grid@node1 ~]$ unzip V38501-01_1of2.zip && unzip V38501-01_2of2.zip
[grid@node1 ~]$ ls -l
total 1906444
drwxr-xr-x 7 grid oinstall 4096 Jun 10 07:15 grid
-rw-r--r--. 1 grid oinstall 1750478910 Jun 26 04:36 V38501-01_1of2.zip
-rw-r--r--. 1 grid oinstall 201673595 Jun 26 03:44 V38501-01_2of2.zip
[oracle@node1 ~]$ unzip V38500-01_1of2.zip && unzip V38500-01_2of2.zip
[oracle@node1 ~]$ ls -l
total 2419504
drwxr-xr-x 7 oracle oinstall 4096 Jun 10 07:14 database
-rw-r--r--. 1 oracle oinstall 1361028723 Jun 26 04:29 V38500-01_1of2.zip
-rw-r--r--. 1 oracle oinstall 1116527103 Jun 26 04:23 V38500-01_2of2.zip

You may need to free up some space by removing the compressed media files after you unzip them. I did this by running the following as root:

rm -rf /home/oracle/V38500-01* /home/grid/V38501-01*

Installing CVUQDISK
CVUQDISK is required by the cluster verification utility. Below are the steps I took to install it. I unzipped the grid installation media to /home/grid. If you placed it elsewhere, you'll need to adjust the commands below.
This is how I copied the package to node2:

su - grid
scp ~/grid/rpm/cvuqdisk-1.0.9-1.rpm node2:/home/grid

Install the package on node1, as root:

CVUQDISK_GRP=oinstall; export CVUQDISK_GRP

cd /home/grid/grid/rpm/
rpm -iv cvuqdisk-1.0.9-1.rpm

Install the package on node2, as root:

cd /home/grid
CVUQDISK_GRP=oinstall; export CVUQDISK_GRP
rpm -iv cvuqdisk-1.0.9-1.rpm

Configuring Shared Storage

We will be creating three shared disk files, with their purposes and sizes as follows:

Name	Size	Disk Group	Contents
crs.vmdk	5GB	+CRS	Grid Infrastructure Management Repository, voting files, and the Oracle Cluster Registry (OCR)
data.vmdk	5GB	+DATA	Database files
fra.vmdk	10GB	+FRA	Fast Recovery Area

Creating shared disks on the VMware ESXi host

You'll need to install VCLI in order to configure the shared disks. VCLI can be downloaded for free from https://my.vmware.com/web/vmware/downloads.
Once you have VCLI installed, cd to the following directory:

Run the following commands to create each disk file on the ESX host. You'll need to substitute the IP after -server with the IP of your ESX host, and use the correct path for your data store. I placed my shared disks in a folder called 12cR1RAC. If you want to create your own folder you can do so by using the Datastore Browser. This will take a while.

vmkfstools -d eagerzeroedthick -c 5G /vmfs/volumes/datastore2/rac_datastore/crs.vmdk
vmkfstools -d eagerzeroedthick -c 5G /vmfs/volumes/datastore2/rac_datastore/data.vmdk
vmkfstools -d eagerzeroedthick -c 10G /vmfs/volumes/datastore2/rac_datastore/fra.vmdk

Now that we've created our shared disks, we'll be adding them to our virtual machines.
Shutdown the virtual machines by executing shutdown -h now on each virtual machine. Once they are powered off right click node1 and select "Edit Settings...."

Click the "Add...."

Select "Hard Disk."

Select "Use an existing virtual disk."

Click "Browse..." and select the crs.vmdk file you just created.

Under "Virtual Device Node," select "SCSI (1:0)". This will create a new disk controller. Select "Independent" and "Persistent."

Review "Ready to Complete" and click "Finish." Don't click the "OK" button yet.

There are two more drives to add. Repeat the drive adding process, and use an incrementing virtual device node (1:0, 1:1, and 1:2). Select the new SCSI controller and select "Physical." Now, go ahead and click "OK" to have the change take effect.

Repeat this process on node2. Make sure that the drives have matching virtual device node IDs on each RAC node. After adding crs.vmdk, I added data.vmdk and finally fra.vmdk. Do this in the same order on both nodes.
Start the nodes. They should now have the drives attached to them. A listing of the devices should be similar to the following.

[root@node1 ~]# fdisk -l|egrep sd[bcd]
Disk /dev/sdb: 5368 MB, 5368709120 bytes
Disk /dev/sdc: 5368 MB, 5368709120 bytes
Disk /dev/sdd: 10.7 GB, 10737418240 bytes

[root@node2 ~]# fdisk -l|egrep sd[bcd]
Disk /dev/sdb: 5368 MB, 5368709120 bytes
Disk /dev/sdc: 5368 MB, 5368709120 bytes
Disk /dev/sdd: 10.7 GB, 10737418240 bytes

Configure Storage Devices
Next, we'll partition the disks we added to the virtual machines. These disks will be used by ASM. Run the following on node1:

fdisk /dev/sdb

Create a new partition with n, then select primary, partition number 1, and use the defaults for the starting and ending cylinder. Type w to write changes.

[root@node1 ~]# fdisk /dev/sdb

Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel
Building a new DOS disklabel with disk identifier 0x61f217af.
Changes will remain in memory only, until you decide to write them.
After that, of course, the previous content won't be recoverable.

Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)
WARNING: DOS-compatible mode is deprecated. It's strongly recommended to
switch off the mode (command 'c') and change display units to
sectors (command 'u').
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 1
First cylinder (1-522, default 1):
Using default value 1
Last cylinder, +cylinders or +size{K,M,G} (1-522, default 522):
Using default value 522
Command (m for help): w
The partition table has been altered!
Calling ioctl() to re-read partition table.
Syncing disks.
Do the same thing for /dev/sdc, and /dev/sdd. The partitions are now visible on node1.
[root@node1 ~]# ls -l /dev/sd[bcd]1
brw-rw---- 1 root disk 8, 17 Sep 19 17:21 /dev/sdb1
brw-rw---- 1 root disk 8, 33 Sep 19 17:22 /dev/sdc1
brw-rw---- 1 root disk 8, 49 Sep 19 17:22 /dev/sdd1

On node2, run partprobe. Now node2 you should now be able to see the new partitions.

[root@node2 ~]# partprobe

Warning: WARNING: the kernel failed to re-read the partition table on /dev/sda (Device or resource busy). As a result, it may not reflect all of your changes until after reboot.

[root@node2 ~]# ls -l /dev/sd[bcd]1
brw-rw---- 1 root disk 8, 17 Sep 19 17:29 /dev/sdb1
brw-rw---- 1 root disk 8, 33 Sep 19 17:29 /dev/sdc1
brw-rw---- 1 root disk 8, 49 Sep 19 17:29 /dev/sdd1

Configure ASMlib
This step will be done on both nodes. Run /etc/init.d/oracleasm configure, and use the following parameters:

Default user to own the driver interface []: grid
Default group to own the driver interface []: asmadmin
Start Oracle ASM library driver on boot (y/n) [n]: y
Scan for Oracle ASM disks on boot (y/n) [y]: y

Now, we will configure our 3 shared disks to use ASMlib. This needs to be done on node1.

# /etc/init.d/oracleasm createdisk CRS01 /dev/sdb1

Marking disk "CRS01" as an ASM disk: [ OK ]

# /etc/init.d/oracleasm createdisk DATA01 /dev/sdc1

Marking disk "DATA01" as an ASM disk: [ OK ]

# /etc/init.d/oracleasm createdisk FRA01 /dev/sdd1

Marking disk "FRA01" as an ASM disk: [ OK ]

On node2, run the following so that the disks are available on node2 as well:

/etc/init.d/oracleasm scandisks

Once this is complete, oracleasm listdisks should show the newly created ASMlib disks on both nodes:

[root@node1 rpm]# /etc/init.d/oracleasm listdisks
CRS01
DATA01
FRA01
[root@node2 grid]# /etc/init.d/oracleasm listdisks
CRS01
DATA01
FRA01

Pre-installation Cluster Verification
We should now be ready to install Grid Infrastructure. You can use the Cluster Verification Utility to make sure there are no major underlying problems with the node configuration. I ran the following command as user grid on node1.

~/grid/runcluvfy.sh stage -pre crsinst -n node1,node2 -verbose > cluvfy_results

The only check that failed was the membership check for the grid user in the dba group. Since this is intentional, you can ignore this. If you'd like to see what my output looked like, you can download it here: cluvfy_results.txt

Fix error
http://kinhnghiem.luyenthianhvan.org/2015/04/fix-ins-40718-single-client-access-name.html

Installing Oracle Grid Infrastructure

Start a VNC session on node1 as the grid user by typing:

vncserver

Then, enter a password of your choice.
Now, connect to the session with a client such as tight VNC client, using the syntax :1. Once connected, start the installer.

cd grid
./runInstaller

Click the "Add" button and fill in the appropriate node name and node VIP name.
The installation runs. Click "Yes" when the configuration scripts popup appears.

I skipped software updates, but feel free to try this if you want to.

Select "Install and Configure Oracle Grid Infrastructure for a Cluster."

Select "Configure a Standard cluster."

Select "Advanced Installation."

Select your desired product language.

As previously mentioned, I configured SCAN records in DNS, so I'm not going to configure GNS.

Fix [INS-40718] Single Client Access Name (SCAN):clus-scan could not be resolved.

http://kinhnghiem.luyenthianhvan.org/2015/04/fix-ins-40718-single-client-access-name.html

Click the "Add" button to add the additional node, and then click "Next."

For the eth1 interface, select "Private" from the "Use for" dropdown.

Select "Yes."

Select "Use Standard ASM for storage."

This disk group will be used by the clusterware. Configure it as shown below.

This cluster is just for testing purposes, so I used a single password.

Select "Do not use Intelligent Platform Management Interface (IPMI)."

By default the correct operating system groups should be selected.

By default the correct software locations should be filled in.

By default the correct inventory location should be filled in.

You can fill this in if you want to have the installer execute the root scripts for you.

The prerequisite checks will now run. There shouldn't be any failures or errors.

Review the summary screen to make sure everything is correct, and then click "Install."

This will generally take a while, depending on your hardware. If you opted to automated the root script execution, you'll see a popup requesting additional approval before the installer will actually do it.

If you see the following screen, it means there were no issues with the installation. You're ready to install the database software.

Installing Oracle Database 12c

Run the following as the oracle user to start a vncserver session.

vncserver

Connect to the session as we did before with your VNC client. Because there may now be two VNC sessions running, you may need to connect by typing :2, which will connect you to the second VNC session running.
From the VNC session as the oracle user, run the installer.

cd database
./runInstaller

Uncheck "I wish to receive security updates via My Oracle Support." Click "Yes" when the popup appears.

Select "Skip software updates."

Select "Install database software only."

Select "Oracle Real Application Clusters database installation."

Make sure both nodes are selected.

Select your desired language.

Select "Enterprise Edition" in order to be able to test the full feature set of Oracle.

By default the correct locations should be filled in.

By default the correct OS groups should be selected.

The prerequisite checks will run. There should be no warnings or errors, and the installer should automatically go to the next screen.

Review the summary screen to make sure everything is correct, and then click "Install."

The installation runs.

Run the root script on each node.

You should now see the following screen. Click "Close."

Creating a RAC Database

We're just about done. Now that the software is installed, let's create a RAC database!
We still have two ASM disks that we need to create disk groups with. We'll be doing this from a vnc session as the grid user. Start the ASMCA by running asmca.

[grid@node1 ~]$ vncserver

Click the "Disk Groups" tab and click "Create."

Configure the "DATA", Externel(None) disk group as shown below, and click "OK" to create the disk group.

Configure the "FRA" disk group as shown below, Externel(None), and click "OK" to create the disk group.

The disk groups should be listed as shown below.

Feel free to click the "ASM Instances" tab to verify that ASM is running on both nodes. Click "Exit."

We will now use the Database Configuration Assistant to create a RAC database. From another VNC session being run under the oracle user, run dbca. "Create Database" should be selected.

Select "Advanced Mode."

Select "Admin-Managed" as the configuration type.

Type "ORCL" as the "Global Database Name," which will cause the SID prefix to automatically be filled in.

Add node2 to the "Selected" list.

I left this screen at its defaults.

Since this is for testing, I used the same password for the administrative accounts.

Select the "+DATA" disk group as the common location for all database files. I specified 10,000MB as the size of my FRA, and enabled archiving.

I added the sample schemas, and left the other settings at their defaults.

You can leave this at the defaults. The only thing I changed was enabling Automatic Memory Management.

"Create Database" should be checked by default.

The prerequisite checks will run. There should be no warnings or errors, and the installer should automatically go to the next screen.

Review the summary, then click "Finish" to have DBCA create the database.

The creation process runs.

The following popup should eventually appear, indicating that the database was successfully created. Click "Exit."

You should see the following screen. Click "Close."

If you've made it this far, you've successfully completed the installation and created a functional RAC database!

Post-installation Tasks

Clear Temp Files
The various installers used /tmp for their storage location. To free up some space you can run the following to clean this location out. Always double check what you've typed before pressing enter when using rm -rf. Run the following as root on each node.

rm -rf /tmp/*

Edit /etc/oratab

Add a new line to the bottom of /etc/oratab on node1 and node2, so that ORCL1 and ORCL2 are the SID values, respectfully. An example follows.

ORCL1:/u01/app/oracle/product/12.1.0/dbhome_1:N:

Verification

Verify that CRS is running:

[grid@node1 grid]$ crsctl check cluster -all
**************************************************************
node1:
CRS-4537: Cluster Ready Services is online
CRS-4529: Cluster Synchronization Services is online
CRS-4533: Event Manager is online
**************************************************************
node2:
CRS-4537: Cluster Ready Services is online
CRS-4529: Cluster Synchronization Services is online
CRS-4533: Event Manager is online
**************************************************************

Check the status of the SCAN:

[grid@node1 grid]$ srvctl status scan
SCAN VIP scan1 is enabled
SCAN VIP scan1 is running on node node2
SCAN VIP scan2 is enabled
SCAN VIP scan2 is running on node node1
SCAN VIP scan3 is enabled
SCAN VIP scan3 is running on node node1
Check the status of the ASM instances:
[grid@node1 grid]$ srvctl status asm
ASM is running on node1,node2

Check the status of the database instances:

[grid@node1 ~]$ srvctl status database -d ORCL
Instance ORCL1 is running on node node1
Instance ORCL2 is running on node node2

Check the node apps:

[grid@node1 grid]$ srvctl status nodeapps
VIP node1-vip is enabled
VIP node1-vip is running on node: node1
VIP node2-vip is enabled
VIP node2-vip is running on node: node2
Network is enabled
Network is running on node: node1
Network is running on node: node2
ONS is enabled
ONS daemon is running on node: node1
ONS daemon is running on node: node2

Check the SCAN config:
[grid@node1 grid]$ srvctl config scan
SCAN name: clus-scan, Network: 1
Subnet IPv4: 192.168.2.0/255.255.255.0/eth0
Subnet IPv6:
SCAN 0 IPv4 VIP: 192.168.2.117
SCAN name: clus-scan, Network: 1
Subnet IPv4: 192.168.2.0/255.255.255.0/eth0
Subnet IPv6:
SCAN 1 IPv4 VIP: 192.168.2.119
SCAN name: clus-scan, Network: 1
Subnet IPv4: 192.168.2.0/255.255.255.0/eth0
Subnet IPv6:
SCAN 2 IPv4 VIP: 192.168.2.118

Check the database config:
[grid@node1 grid]$ srvctl config database -d ORCL
Database unique name: ORCL
Database name: ORCL
Oracle home: /u01/app/oracle/product/12.1.0/dbhome_1
Oracle user: oracle
Spfile: +DATA/ORCL/spfileORCL.ora
Password file: +DATA/ORCL/orapworcl
Domain:
Start options: open
Stop options: immediate
Database role: PRIMARY
Management policy: AUTOMATIC
Server pools: ORCL
Database instances: ORCL1,ORCL2
Disk Groups: DATA
Mount point paths:
Services:
Type: RAC
Start concurrency:
Stop concurrency:
Database is administrator managed

Verify that you can connect to the database:

[oracle@node1 ~]$ sqlplus / as sysdba
SQL*Plus: Release 12.1.0.1.0 Production on Tue Sep 24 02:03:35 2013
Copyright (c) 1982, 2013, Oracle. All rights reserved.
Connected to:
Oracle Database 12c Enterprise Edition Release 12.1.0.1.0 - 64bit Production
With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
Advanced Analytics and Real Application Testing options
SQL>

Verify the status for our instances:

SQL> select instance_name, status, startup_time from gv$instance;

INSTANCE_NAME    STATUS       STARTUP_T
---------------- ------------ ---------
ORCL1            OPEN         24-SEP-13
ORCL2            OPEN         24-SEP-13

And that's it! If you've made it this far, you've finished the install and verified that RAC is up and running. You'll probably want to study the documentation in more detail at this point to get a better understanding of RAC concepts and administration. I truly hope this article has been of use to you!
Miscellaneous Notes

Oracle RDBMS Pre-Install RPM
You may have noticed that I didn't use the oracle-rdbms-server-12cR1-preinstall.x86_64 RPM. I actually did initially, but it left so many things out that I decided not to bother with it and just configure everything myself. The side benefit of this is that the installation process I documented will more closely align with installations on other distributions, such as RHEL, that do not have the pre-install RPM.

The Disk I/O Scheduler
I didn't need to configure Deadline for I/O scheduling because we are using the UEK kernel, which uses Deadline for I/O scheduling by default.

References

Requirements for Installing Oracle Database 12.1 on RHEL6 or OL6 64-bit (x86-64) (Doc ID 1529864.1)
Oracle® Database Installation Guide 12c Release 1 (12.1) for Linux
Oracle® Grid Infrastructure Installation Guide 12c

Fix error “Relocating modules and starting up the kernel" in VMWare ESXi 5.5 installer

noreply@blogger.com (Unknown) — Sat, 04 Apr 2015 06:06:00 +0000

Press shift+O during ESXi boot

Append “ignoreHeadless=TRUE” to the options

When the system reboots after the install, perform steps 1 and 2 again

From the ESXi shell, run the following command (this applies the ignoreHeadless option permanently): esxcfg-advcfg --set-kernel "TRUE" ignoreHeadless

Installation of rsync on Solaris 10

noreply@blogger.com (Unknown) — Wed, 31 Dec 2014 01:08:00 +0000

Installation of rsync on Solaris 10

Go to http://www.sunfreeware.com/

Download
http://ftp.riken.jp/Sun/sunfreeware/sparc/10/rsync-3.0.9-sol10-sparc-local.gz
http://ftp.riken.jp/Sun/sunfreeware/sparc/10/libiconv-1.14-sol10-sparc-local.gz
http://ftp.riken.jp/Sun/sunfreeware/sparc/10/libgcc-3.4.6-sol10-sparc-local.gz

# pkgadd -G -d rsync-3.0.9-sol10-sparc-local
# pkgadd -G -d libiconv-1.14-sol10-sparc-local
# pkgadd -G -d libgcc-3.4.6-sol10-sparc-local

Oracle Table Fragmentation

noreply@blogger.com (Unknown) — Tue, 28 Oct 2014 02:01:00 +0000

What is Table fragmentation
When rows are not stored contiguously, or if rows are split onto more than one page, performance decreases because these rows require additional page accesses. Table fragmentation is distinct from file fragmentation.

When lots of DML operation apply on tables then tables is fragmented.
because DML is not release free space from table below HWM.

Hint: HWM is indicator for USED BLOCKS in database. Blocks below the high water mark (used blocks) have at least once contained data. This data might have been deleted.
Since Oracle knows that blocks beyond the high water mark don't have data, it only reads blocks up to the high water mark in a full table scan.

DDL statement always reset HWM.

How to find table fragmentation

SQL> select count(*) from big1;

1000000 rows selected.

SQL> delete from big1 where rownum <= 300000;

300000 rows deleted.

SQL> commit;

Commit complete.

SQL> update big1 set object_id = 0 where rownum <=350000;

342226 rows updated.

SQL> commit;

Commit complete.

SQL> exec dbms_stats.gather_table_stats('SCOTT','BIG1');

PL/SQL procedure successfully completed.

Table Size ( with fragmented)

SQL> select table_name,round((blocks*8),2)||'kb' "size"
2 from user_tables
3 where table_name = 'BIG1';

TABLE_NAME size
------------------------------ ------------------------------------------
BIG1 72952kb

Actual data in table

SQL> select table_name,round((num_rows*avg_row_len/1024),2)||'kb' "size"
2 from user_tables
3 where table_name = 'BIG1';

TABLE_NAME size
------------------------------ ------------------------------------------
BIG1 30604.2kb

Note= 72952 – 30604 = 42348 Kb is wasted space in table

The difference between two values is 60% and Pctfree 10% (default) so table is 50% extra space which is wasted because there is no data.

How to reset HWM / remove fragemenation
For that we need to reorganize fragmented table

We have four options to reorganize fragmented tables

1. alter table … move + rebuild indexes
2. export / truncate / import
3. create table as select ( CTAS)
4. dbms_redefinition

Option: 1 “alter table … move + rebuild indexes”

SQL> alter table BIG1 move;

Table altered.

SQL> select status,index_name from user_indexes
2 where table_name = 'BIG1';

STATUS INDEX_NAME
-------- ------------------------------
UNUSABLE BIGIDX

SQL> alter index bigidx rebuild;

Index altered.

SQL> select status,index_name from user_indexes
2 where table_name = 'BIG1';

STATUS INDEX_NAME
-------- ------------------------------
VALID BIGIDX

SQL> exec dbms_stats.gather_table_stats('SCOTT','BIG1');

PL/SQL procedure successfully completed.

SQL> select table_name,round((blocks*8),2)||'kb' "size"
2 from user_tables
3 where table_name = 'BIG1';

TABLE_NAME size
------------------------------ ------------------------------------------
BIG1 38224kb

SQL> select table_name,round((num_rows*avg_row_len/1024),2)||'kb' "size"
2 from user_tables
3 where table_name = 'BIG1';

TABLE_NAME size
------------------------------ ------------------------------------------
BIG1 30727.37kb

Option: 2 “Create table as select”

SQL> create table big2 as select * from big1;

Table created.

SQL> drop table big1 purge;

Table dropped.

SQL> rename big2 to big1;

Table renamed.

SQL> exec dbms_stats.gather_table_stats('SCOTT','BIG1');

PL/SQL procedure successfully completed.

SQL> select table_name,round((blocks*8),2)||'kb' "size"
2 from user_tables
3 where table_name = 'BIG1';

TABLE_NAME size
------------------------------ ------------------------------------------
BIG1 85536kb

SQL> select table_name,round((num_rows*avg_row_len/1024),2)||'kb' "size"
2 from user_tables
3 where table_name = 'BIG1';

TABLE_NAME size
------------------------------ ------------------------------------------
BIG1 68986.97kb

SQL> select status from user_indexes
2 where table_name = 'BIG1';

no rows selected

SQL> --Note we need to create all indexes.

Option: 3 “export / truncate / import”

SQL> select table_name, round((blocks*8),2)||'kb' "size"
2 from user_tables
3 where table_name = 'BIG1';

TABLE_NAME size
------------------------------ ------------------------------------------
BIG1 85536kb

SQL> select table_name, round((num_rows*avg_row_len/1024),2)||'kb' "size"
2 from user_tables
3 where table_name = 'BIG1';

TABLE_NAME size
------------------------------ ------------------------------------------
BIG1 42535.54kb

SQL> select status from user_indexes where table_name = 'BIG1';

STATUS
--------
VALID

SQL> exit
Disconnected from Oracle Database 10g Enterprise Edition Release 10.1.0.5.0 - Pr
oduction
With the Partitioning, OLAP and Data Mining options

C:\>exp scott/tiger@Orcl file=c:\big1.dmp tables=big1

Export: Release 10.1.0.5.0 - Production on Sat Jul 28 16:30:44 2007

Copyright (c) 1982, 2005, Oracle. All rights reserved.

Connected to: Oracle Database 10g Enterprise Edition Release 10.1.0.5.0 - Produc
tion
With the Partitioning, OLAP and Data Mining options
Export done in WE8MSWIN1252 character set and AL16UTF16 NCHAR character set

About to export specified tables via Conventional Path ...
. . exporting table BIG1 468904 rows exported
Export terminated successfully without warnings.

C:\>sqlplus scott/tiger@orcl

SQL*Plus: Release 10.1.0.5.0 - Production on Sat Jul 28 16:31:12 2007

Copyright (c) 1982, 2005, Oracle. All rights reserved.

Connected to:
Oracle Database 10g Enterprise Edition Release 10.1.0.5.0 - Production
With the Partitioning, OLAP and Data Mining options

SQL> truncate table big1;

Table truncated.

SQL> exit
Disconnected from Oracle Database 10g Enterprise Edition Release 10.1.0.5.0 - Pr
oduction
With the Partitioning, OLAP and Data Mining options

C:\>imp scott/tiger@Orcl file=c:\big1.dmp ignore=y

Import: Release 10.1.0.5.0 - Production on Sat Jul 28 16:31:54 2007

Copyright (c) 1982, 2005, Oracle. All rights reserved.

Connected to: Oracle Database 10g Enterprise Edition Release 10.1.0.5.0 - Produc
tion
With the Partitioning, OLAP and Data Mining options

Export file created by EXPORT:V10.01.00 via conventional path
import done in WE8MSWIN1252 character set and AL16UTF16 NCHAR character set
. importing SCOTT's objects into SCOTT
. . importing table "BIG1" 468904 rows imported
Import terminated successfully without warnings.

C:\>sqlplus scott/tiger@orcl

SQL*Plus: Release 10.1.0.5.0 - Production on Sat Jul 28 16:32:21 2007

Copyright (c) 1982, 2005, Oracle. All rights reserved.

Connected to:
Oracle Database 10g Enterprise Edition Release 10.1.0.5.0 - Production
With the Partitioning, OLAP and Data Mining options

SQL> select table_name, round((blocks*8),2)||'kb' "size"
2 from user_tables
3 where table_name = 'BIG1';

TABLE_NAME size
------------------------------ ------------------------------------------
BIG1 85536kb

SQL> select table_name, round((num_rows*avg_row_len/1024),2)||'kb' "size"
2 from user_tables
3 where table_name = 'BIG1';

TABLE_NAME size
------------------------------ ------------------------------------------
BIG1 42535.54kb

SQL> exec dbms_stats.gather_table_stats('SCOTT','BIG1');

PL/SQL procedure successfully completed.

SQL> select table_name, round((blocks*8),2)||'kb' "size"
2 from user_tables
3 where table_name = 'BIG1';

TABLE_NAME size
------------------------------ ------------------------------------------
BIG1 51840kb

SQL> select table_name, round((num_rows*avg_row_len/1024),2)||'kb' "size"
2 from user_tables
3 where table_name = 'BIG1';

TABLE_NAME size
------------------------------ ------------------------------------------
BIG1 42542.27kb

SQL> select status from user_indexes where table_name = 'BIG1';

STATUS
--------
VALID

SQL> exec dbms_redefinition.can_redef_table('SCOTT','BIG1',-
> dbms_redefinition.cons_use_pk);

PL/SQL procedure successfully completed.

Option: 4 “dbms_redefinition”

SQL> create table TABLE1 (
2 no number,
3 name varchar2(20) default 'NONE',
4 ddate date default SYSDATE);

Table created.

SQL> alter table table1 add constraint pk_no primary key(no);

Table altered.

SQL> begin
2 for x in 1..100000 loop
3 insert into table1 ( no , name, ddate)
4 values ( x , default, default);
5 end loop;
6 end;
7 /

PL/SQL procedure successfully completed.

SQL> create or replace trigger tri_table1
2 after insert on table1
3 begin
4 null;
5 end;
6 /

Trigger created.

SQL> select count(*) from table1;

COUNT(*)
----------
100000

SQL> delete table1 where rownum <= 50000;

50000 rows deleted.

SQL> commit;

Commit complete.

SQL> exec dbms_stats.gather_table_stats('SCOTT','TABLE1');

PL/SQL procedure successfully completed.

SQL> select table_name, round((blocks*8),2)||'kb' "size"
2 from user_tables
3 where table_name = 'TABLE1';

TABLE_NAME size
------------------------------ ------------------------------------------
TABLE1 2960kb

SQL> select table_name, round((num_rows*avg_row_len/1024),2)||'kb' "size"
2 from user_tables
3 where table_name = 'TABLE1';

TABLE_NAME size
------------------------------ ------------------------------------------
TABLE1 822.69kb

SQL> --Minimum Privs required "DBA" role or "SELECT" on dbms_redefinition pkg
SQL> --First check table is condidate for redefinition.
SQL>
SQL> exec sys.dbms_redefinition.can_redef_table('SCOTT',-
> 'TABLE1',-
> sys.dbms_redefinition.cons_use_pk);

PL/SQL procedure successfully completed.

SQL> --After verifying that the table can be redefined online, you manually crea
te an empty interim table (in the same schema as the table to be redefined)
SQL>
SQL> create table TABLE2 as select * from table1 WHERE 1 = 2;

Table created.

SQL> exec sys.dbms_redefinition.start_redef_table ( 'SCOTT',-
> 'TABLE1',-
> 'TABLE2');

PL/SQL procedure successfully completed.

SQL> --This procedure keeps the interim table synchronized with the original tab
le.
SQL>
SQL> exec sys.dbms_redefinition.sync_interim_table ('SCOTT',-
> 'TABLE1',-
> 'TABLE2');

PL/SQL procedure successfully completed.

SQL> --Create PRIMARY KEY on interim table(TABLE2)
SQL> alter table TABLE2
2 add constraint pk_no1 primary key (no);

Table altered.

SQL> create trigger tri_table2
2 after insert on table2
3 begin
4 null;
5 end;
6 /

Trigger created.

SQL> --Disable foreign key on original table if exists before finish this proces
s.
SQL>
SQL> exec sys.dbms_redefinition.finish_redef_table ( 'SCOTT',-
> 'TABLE1',-
> 'TABLE2');

PL/SQL procedure successfully completed.

SQL> exec dbms_stats.gather_table_stats('SCOTT','TABLE1');

PL/SQL procedure successfully completed.

SQL> select table_name, round((blocks*8),2)||'kb' "size"
2 from user_tables
3 where table_name = 'TABLE1';

TABLE_NAME size
------------------------------ ------------------------------------------
TABLE1 1376kb

SQL> select table_name, round((num_rows*avg_row_len/1024),2)||'kb' "size"
2 from user_tables
3 where table_name = 'TABLE1';

TABLE_NAME size
------------------------------ ------------------------------------------
TABLE1 841.4kb

SQL> select status,constraint_name
2 from user_constraints
3 where table_name = 'TABLE1';

STATUS CONSTRAINT_NAME
-------- ------------------------------
ENABLED PK_NO1

SQL> select status ,trigger_name
2 from user_triggers
3 where table_name = 'TABLE1';

STATUS TRIGGER_NAME
-------- ------------------------------
ENABLED TRI_TABLE2

SQL> drop table TABLE2 PURGE;

Table dropped.

How to Replace disk on freenas for CLI

noreply@blogger.com (Unknown) — Mon, 27 Oct 2014 04:37:00 +0000

[root@freenas] ~# camcontrol identify ada0 | grep LBA48
LBA48 supported       5860533168 sectors
[root@freenas] ~# camcontrol identify ada2 | grep LBA48
LBA48 supported       5860533168 sectors
[root@freenas] ~#
[root@freenas] ~# smartctl -a /dev/ada1 | grep "Serial"
Serial Number:    W1F390KB
[root@freenas] ~# smartctl -a /dev/ada2 | grep "Serial"
Serial Number:    WCC1T1236411
[root@freenas] ~# smartctl -a /dev/ada0 | grep "Serial"
Serial Number:    W1F3M4FP
[root@freenas] ~#

[root@freenas] ~# cat /etc/version
FreeNAS-8.3.2-RELEASE-x86 (r12686+70c2cb8)

[root@freenas] ~# camcontrol devlist sysctl kern.disks

at scbus0 target 0 lun 0 (pass0,ada0)

at scbus1 target 0 lun 0 (pass1,ada1)

at scbus2 target 0 lun 0 (pass2,ada2)

at scbus3 target 0 lun 0 (pass3,ada3)

at scbus4 target 0 lun 0 (pass4,ada4)

          at scbus5 target 0 lun 0 (pass5,ada5)
    at scbus8 target 0 lun 0 (pass6,da0)

[root@freenas] ~#glabel status

                                      Name Status Components

gptid/55414a31-55c3-11e3-b6e3-4ce676286ed3     N/A ada0p2

gptid/55ecb111-55c3-11e3-b6e3-4ce676286ed3     N/A ada1p2

          gpt/Microsoft reserved partition     N/A ada2p1

gptid/fa7d0f15-3dff-4dbb-87b4-2719b856d7ad     N/A ada2p1

gptid/573cee31-55c3-11e3-b6e3-4ce676286ed3     N/A ada3p2

gptid/57e5235e-55c3-11e3-b6e3-4ce676286ed3     N/A ada4p2

gptid/5877a718-55c3-11e3-b6e3-4ce676286ed3     N/A ada5p1

gptid/58928e16-55c3-11e3-b6e3-4ce676286ed3     N/A ada5p2

                             ufs/FreeNASs3     N/A da0s3

                             ufs/FreeNASs4     N/A da0s4

                            ufs/FreeNASs1a     N/A da0s1a

gptid/ef001e5f-03b8-4b2a-867d-30b9de1d8301     N/A zvol/nas12t/lptrungp1

[root@freenas] ~# gpart show

=>        34 5860533101 ada0 GPT (2.7T)

          34          94        - free - (47k)

         128     4194304     1 freebsd-swap (2.0G)

     4194432 5856338696     2 freebsd-zfs (2.7T)

5860533128           7        - free - (3.5k)

=>        34 5860533101 ada1 GPT (2.7T)

          34          94        - free - (47k)

         128     4194304     1 freebsd-swap (2.0G)

     4194432 5856338696     2 freebsd-zfs (2.7T)

5860533128           7        - free - (3.5k)

=>        34 5860533101 ada2 GPT (2.7T)

          34      262144     1 ms-reserved (128M)

      262178 5860270957        - free - (2.7T)

=>        34 5860533101 ada3 GPT (2.7T)

          34          94        - free - (47k)

         128     4194304     1 freebsd-swap (2.0G)

     4194432 5856338696     2 freebsd-zfs (2.7T)

5860533128           7        - free - (3.5k)

=>        34 5860533101 ada4 GPT (2.7T)

          34          94        - free - (47k)

         128     4194304     1 freebsd-swap (2.0G)

     4194432 5856338696     2 freebsd-zfs (2.7T)

5860533128           7        - free - (3.5k)

=>        34 5860533101 ada5 GPT (2.7T)

          34          94        - free - (47k)

         128     4194304     1 freebsd-swap (2.0G)

     4194432 5856338696     2 freebsd-zfs (2.7T)

5860533128           7        - free - (3.5k)

=>      63 30945217 da0 MBR (14G)

        63   1930257    1 freebsd [active] (942M)

   1930320        63       - free - (31k)

   1930383   1930257    2 freebsd (942M)

   3860640      3024    3 freebsd (1.5M)

   3863664     41328    4 freebsd (20M)

   3904992 27040288       - free - (12G)

=>      0 1930257 da0s1 BSD (942M)

        0       16         - free - (8.0k)

       16 1930241      1 !0 (942M)

=>     34 4194237 zvol/nas12t/lptrung GPT (2.0G)

       34     2014                       - free - (1M)

     2048 4192223                    1 !aa31e02a-400f-11db-9590-000c2911d1b8 (2G)

[root@freenas] ~# zpool status

pool: nas12t

state: DEGRADED

status: One or more devices could not be opened. Sufficient replicas exist for

    the pool to continue functioning in a degraded state.

action: Attach the missing device and online it using 'zpool online'.

   see: http://www.sun.com/msg/ZFS-8000-2Q

scan: scrub repaired 0 in 651h3m with 0 errors on Sat Aug 30 03:03:53 2014

config:

    NAME                                            STATE     READ WRITE CKSUM

    nas12t                                          DEGRADED     0     0     0

    raidz1-0                                      DEGRADED     0     0     0

        gptid/55414a31-55c3-11e3-b6e3-4ce676286ed3 ONLINE       0     0     0

        gptid/55ecb111-55c3-11e3-b6e3-4ce676286ed3 ONLINE       0     0     0

        16889620854227218693                        UNAVAIL      0     0     0 was /dev/gptid/5694c48b-55c3-11e3-b6e3-4ce676286ed3
        gptid/573cee31-55c3-11e3-b6e3-4ce676286ed3 ONLINE       0     0     0

        gptid/57e5235e-55c3-11e3-b6e3-4ce676286ed3 ONLINE       0     0     0

        gptid/58928e16-55c3-11e3-b6e3-4ce676286ed3 ONLINE       0     0     0

errors: No known data errors

[root@freenas] ~# zpool replace nas12t /dev/gptid/5694c48b-55c3-11e3-b6e3-4ce676286ed3 ada2

[root@freenas] ~# zpool status

pool: nas12t

state: DEGRADED

status: One or more devices is currently being resilvered. The pool will

    continue to function, possibly in a degraded state.

action: Wait for the resilver to complete.

scan: resilver in progress since Sun Oct 26 06:09:47 2014

        180G scanned out of 9.47T at 110M/s, 24h32m to go

        30.0G resilvered, 1.86% done

config:

    NAME                                            STATE     READ WRITE CKSUM

    nas12t                                          DEGRADED     0     0     0

    raidz1-0                                      DEGRADED     0     0     0

        gptid/55414a31-55c3-11e3-b6e3-4ce676286ed3 ONLINE       0     0     0

        gptid/55ecb111-55c3-11e3-b6e3-4ce676286ed3 ONLINE       0     0     0

        replacing-2                                 UNAVAIL      0     0     0

          16889620854227218693                      UNAVAIL      0     0     0 was /dev/gptid/5694c48b-55c3-11e3-b6e3-4ce676286ed3

          ada2                                      ONLINE       0     0     0 (resilvering)

        gptid/573cee31-55c3-11e3-b6e3-4ce676286ed3 ONLINE       0     0     0

        gptid/57e5235e-55c3-11e3-b6e3-4ce676286ed3 ONLINE       0     0     0

        gptid/58928e16-55c3-11e3-b6e3-4ce676286ed3 ONLINE       0     0     0

errors: No known data errors

Wait many hour => for complete

[root@freenas] ~# zpool status
pool: nas12t
state: DEGRADED
scan: resilvered 1.58T in 14h28m with 0 errors on Sun Oct 26 20:38:20 2014
config:

        NAME                                            STATE     READ WRITE CKSUM
        nas12t                                          DEGRADED     0     0     0
          raidz1-0                                      DEGRADED     0     0     0
            gptid/55414a31-55c3-11e3-b6e3-4ce676286ed3 ONLINE       0     0     0
            gptid/55ecb111-55c3-11e3-b6e3-4ce676286ed3 ONLINE       0     0     0
            replacing-2                                 UNAVAIL      0     0     0
              16889620854227218693                      UNAVAIL      0     0     0 was /dev/gptid/5694c48b-55c3-11e3-b6e3-4ce676286ed3
              ada2                                      ONLINE       0     0     0
            gptid/573cee31-55c3-11e3-b6e3-4ce676286ed3 ONLINE       0     0     0
            gptid/57e5235e-55c3-11e3-b6e3-4ce676286ed3 ONLINE       0     0     0
            gptid/58928e16-55c3-11e3-b6e3-4ce676286ed3 ONLINE       0     0     0

errors: No known data errors

[root@freenas] ~# zpool detach nas12t 16889620854227218693
[root@freenas] ~# zpool status
pool: nas12t
state: ONLINE
scan: resilvered 1.58T in 14h28m with 0 errors on Sun Oct 26 20:38:20 2014
config:

        NAME                                            STATE     READ WRITE CKSUM
        nas12t                                          ONLINE       0     0     0
          raidz1-0                                      ONLINE       0     0     0
            gptid/55414a31-55c3-11e3-b6e3-4ce676286ed3 ONLINE       0     0     0
            gptid/55ecb111-55c3-11e3-b6e3-4ce676286ed3 ONLINE       0     0     0
            ada2                                        ONLINE       0     0     0
            gptid/573cee31-55c3-11e3-b6e3-4ce676286ed3 ONLINE       0     0     0
            gptid/57e5235e-55c3-11e3-b6e3-4ce676286ed3 ONLINE       0     0     0
            gptid/58928e16-55c3-11e3-b6e3-4ce676286ed3 ONLINE       0     0     0

errors: No known data errors
[root@freenas] ~#

FreeBSD Fix bug not connect to USB

noreply@blogger.com (Unknown) — Fri, 23 May 2014 06:35:00 +0000

root@freenas] ~# camcontrol devlist

at scbus0 target 0 lun 0 (ada0,pass0)

at scbus1 target 0 lun 0 (ada1,pass1)

at scbus2 target 0 lun 0 (ada2,pass2)

at scbus3 target 0 lun 0 (ada3,pass3)

at scbus4 target 0 lun 0 (ada4,pass4)

          at scbus5 target 0 lun 0 (ada5,pass5)
        at scbus8 target 0 lun 0 (pass6,da0)
       at scbus9 target 0 lun 0 (da1,pass7)
       at scbus10 target 0 lun 0 (da2,pass8)

[root@freenas] ~# usbconfig
ugen0.1: at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE
ugen1.1: at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE
ugen2.1: at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE
ugen3.1: at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE
ugen4.1: at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE
ugen4.2:

at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON
ugen0.2: at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=ON
ugen0.3: at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=ON
ugen4.3: at usbus4, cfg=255 md=HOST spd=HIGH (480Mbps) pwr=ON

[root@freenas] ~# usbconfig -u 4 -a 3 power_off
[root@freenas] ~# usbconfig
ugen0.1: at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE
ugen1.1: at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE
ugen2.1: at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE
ugen3.1: at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE
ugen4.1: at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE
ugen4.2:

at scbus0 target 0 lun 0 (ada0,pass0)

at scbus1 target 0 lun 0 (ada1,pass1)

at scbus2 target 0 lun 0 (ada2,pass2)

at scbus3 target 0 lun 0 (ada3,pass3)

at scbus4 target 0 lun 0 (ada4,pass4)

          at scbus5 target 0 lun 0 (ada5,pass5)
        at scbus8 target 0 lun 0 (pass6,da0)
       at scbus9 target 0 lun 0 (da1,pass7)
       at scbus10 target 0 lun 0 (da2,pass8)
        at scbus11 target 0 lun 0 (da3,pass9)
[root@freenas] ~#

Sun Storage Solaris Multipathing Software

noreply@blogger.com (Unknown) — Mon, 21 Apr 2014 09:38:00 +0000

Configuration files

For Solaris 10 and earlier

/kernel/drv/fp.conf	Fiber channel port configuration file (For Fiber Channel Devices)
/kernel/drv/mpt.conf	mpt scsi/SAS HBA controller driver configuration file (For SAS Devices)
/kernel/drv/scsi_vhci.conf	MPXIO operation configuration file (Used to define loadbalancing and failback modes and configure 3rd party devices)
/kernel/drv/iscsi_conf	iSCSI MPxIO configuration file (For iSCSI devices)

For Solaris 11

In case of Solaris 11, files in the directory /kernel/drv/ and /etc/driver/drv are the sample default configuration files delivered with OS (not used by MPxIO). Do not edit these files. The location of the configuration files is /etc/driver/drv/. The 4 configuration files used in case of Solaris 11 are the same, performing the same task. Although the syntax may be different.

/etc/driver/drv/fp.conf
/etc/driver/drv/mpt.conf
/etc/driver/drv/scsi_vhci.conf
/etc/driver/drv/iscsi_conf

It is best practice to edit these files using the stmsboot utility, rather than editing them manually.

Enabling/Disabling MPxIO

The syntax of the command stmsboot used to enable/disable MPxIO is :

stmsboot [-D fp|mpt] [-d | -e | -u | -L | -l controller_number]

where:
-D fp|mpt -> to select the protocol where you want to enable/disable mpxio
-e -> to enable STMS on all HBA
-d -> to disable STMS on all HBA
-u -> to update vfstable and dump config after manual file configuration
-l or -L unchanged - see the manpage of stms for a full description.

Few examples of using stmsboot command are :

# stmsboot -e	To enable MPxIO or all devices (globally)
# stmsboot -D fp -e	To enable MPxIO for fiber channel devices
# stmsboot -d	To disable MPxIO for all devices (globally)

How to confirm MPxIO is enabled

To make sure that MPxIO is enabled for a LUN, simply run the format command and check for the /scsi_vhci in the logical path of the LUN.

# format
4. c6t60060E800561CF00000061CF00000002d0 
          /scsi_vhci/ssd@g60060e800561cf00000061cf00000002

Another way is to check the “mpxio-disable” parameter in the configuration files :

Solaris 7,8,9

# egrep "^mpxio-disable=" /kernel/drv/*.conf
/kernel/drv/scsi_vhci.conf:mpxio-disable="no";

Solaris 10

# egrep "^mpxio-disable=" /kernel/drv/*.conf
/kernel/drv/fp.conf:mpxio-disable="no";

Solaris 11

# egrep "^mpxio-disable=" /etc/driver/drv/*.conf
/etc/driver/drv/fp.conf:mpxio-disable="no";

For Solaris 10 and 11, MPxIO is enabled by default on X86 platforms.

Verifying that the scsi_vhci module is loaded

scsi_vhci is the virtual host controller interconnect driver used to manage path of storage LUN. If you find that the scsi_vhci module is not loaded, then most likely MPxIO is not enabled.

Solaris[TM] 7,8,9,10,11
# modinfo -c |grep scsi_vhci
 21          1 scsi_vhci                        LOADED/INSTALLED

Verifying Health of paths

We can check the multiple paths to the storage array LUNs by using mpathadm or luxadm command. The various states for the paths are :

ONLINE/primary
ONLINE/secondary
STANDBY/secondary
OFFLINE/*
UNAVAILABLE/*

mpathadm (supported for FC/SAS/iSCSI) [Works on Solaris 10, 11]
luxadm (supported on FC only) [Works on Solaris 7,8,9,10,11]

# mpathadm list LU
        /dev/rdsk/c9t60080E50001C0300000006464D8C9044d0s2
                Total Path Count: 2 
                Operational Path Count: 2

To check the health of the paths using mpathadm :

# mpathadm show LU  /dev/rdsk/c9t60080E50001C0300000006464D8C9044d0s2

Logical Unit:  /dev/rdsk/c9t60080E50001C0300000006464D8C9044d0s2
        mpath-support:  libmpscsi_vhci.so
        Vendor:  SUN     
        Product:  LCSM100_F
        Revision:  0777
        Name Type:  unknown type
        Name:  60080e50001c0300000006464d8c9044
        Asymmetric:  yes
        Current Load Balance:  round-robin
        Logical Unit Group ID:  NA
        Auto Failback:  on
        Auto Probing:  NA

        Paths:  
                Initiator Port Name:  210000e08b07922c
                Target Port Name:  203d0080e51c2cc4
                Override Path:  NA
                Path State:  OK
                Disabled:  no

                Initiator Port Name:  210000e08b07f32c
                Target Port Name:  203e0080e51c2cc4
                Override Path:  NA
                Path State:  OK
                Disabled:  no
.........

To check health of paths using luxadm :

# luxadm probe
                Found Fibre Channel device(s):
                  ......
                Logical Path:/dev/rdsk/c6t60060E800561CF00000061CF00000002d0s2
                Node WWN:203e0080e51c2cc4  Device Type:Disk device
                   ......

# luxadm display 203e0080e51c2cc4
DEVICE PROPERTIES for disk: 203e0080e51c2cc4
  Vendor:               SUN     
  Product ID:           LCSM100_F ------------> this is a 2540 or 2540-M2 array
  Revision:             0777
  Serial Num:           SV04720931      
  Unformatted capacity: 5120.000 MBytes
  Write Cache:          Enabled
  Read Cache:           Enabled
    Minimum prefetch:   0x3
    Maximum prefetch:   0x0
  Device Type:          Disk device
  Path(s):

  /dev/rdsk/c9t60080E50001C0300000006464D8C9044d0s2
  /devices/scsi_vhci/ssd@g60080e50001c0300000006464d8c9044:c,raw
   Controller           /devices/pci@1d,700000/SUNW,qlc@1/fp@0,0
    Device Address              203d0080e51c2cc4,0
    Host controller port WWN    210000e08b07922c
    Class                       primary
    State                       ONLINE
   Controller           /devices/pci@1c,600000/SUNW,qlc@1/fp@0,0
    Device Address              203e0080e51c2cc4,0
    Host controller port WWN    210000e08b07f32c
    Class                       secondary
    State                       ONLINE

Load Balancing policies

MPxIO also provides the load balancing capability to the I/O. There are basically 3 options to configure load balancing :

Round Robin	Selects all paths in a round robin way.
Logical Block	I/Os within the range specified by range_size parameter would go on the same path. Improves performance on some storage arrays which have per path caching of data.
None	No load balancing – only one path is used.

The load balancing policy can be set in the configuration file /kernel/drv/scsi_vhci.conf for solaris 10 and earlier or in the /etc/driver/drv/scsi_vhci.conf file for solaris 11.

load-balance="round-robin";

Auto-failback policy

Auto-failback policy enables the re-enable the failed path after it has recovered from the failure. By default the auto-failback is enabled. There are 2 ways to enable the auto-failback :
Non-persistent way
By this method, the auto-failback option does not persist across reboots.

# mpathadm modify mpath-support --autofailback on libmpscsi_vhci.so
# mpathadm modify mpath-support -a on libmpscsi_vhci.so

Persistent way
For the changes to persist across reboots set the auto-failback parameter in the configuration file /kernel/drv/scsi_vhci.conf for solaris 10 and earlier or in the /etc/driver/drv/scsi_vhci.conf file for solaris 11. This requires a reconfiguration reboot.

auto-failback="enable";

Verifying auto-failback
To confirm that the auto-failback is enabled use :

# mpathadm show mpath-support libmpscsi_vhci.so | grep -i failback
           Supported Auto Failback Config:  1
           Auto Failback:  on  <--- 0="" current="" failback="" max="" polling="" pre="" rate="">

========================================================

bash-3.2# egrep "^mpxio-disable=" /kernel/drv/*.conf
/kernel/drv/fp.conf:mpxio-disable="yes"; => change to no/kernel/drv/iscsi.conf:mpxio-disable="no";
/kernel/drv/mpt.conf:mpxio-disable="yes"; => change to no
/kernel/drv/mpt_sas.conf:mpxio-disable="no";

bash-3.2# mpathadm list lu
        /dev/rdsk/c6t20000018620E6681d0s2
                Total Path Count: 1
                Operational Path Count: 1
        /dev/rdsk/c6t20000018620E42AFd0s2
                Total Path Count: 1
                Operational Path Count: 1
        /dev/rdsk/c6t20000018620E400Bd0s2
                Total Path Count: 1
                Operational Path Count: 1
        /dev/rdsk/c6t20000018620E4155d0s2
                Total Path Count: 1
                Operational Path Count: 1
        /scsi_vhci/ses@g5080020000284028
                Total Path Count: 1
                Operational Path Count: 1
        /dev/rdsk/c6t600A0B800018B3CA000052F6534DB0C5d0s2
                Total Path Count: 2
                Operational Path Count: 2
        /dev/rdsk/c6t600A0B800018B3CA000052EF534DB005d0s2
                Total Path Count: 2
                Operational Path Count: 2


bash-3.2# fcinfo hba-port
HBA Port WWN: 210000144f415c2a
        OS Device Name: /dev/cfg/c1
        Manufacturer: QLogic Corp.
        Model: 2200
        Firmware Version: 02.01.145
        FCode/BIOS Version: ISP2200 FC-AL Host Adapter Driver: 1.15 04/03/22
        Serial Number: not available
        Driver Name: qlc
        Driver Version: 20120717-4.01
        Type: L-port
        State: online
        Supported Speeds: 1Gb
        Current Speed: 1Gb
        Node WWN: 200000144f415c2a
HBA Port WWN: 10000000c9c25df0
        OS Device Name: /dev/cfg/c4
        Manufacturer: Emulex
        Model: LP11000-S
        Firmware Version: 2.82a4 (B3D2.82A4)
        FCode/BIOS Version: Boot:5.02a1 Fcode:1.50a9
        Serial Number: 0999BT0-1121000JC2
        Driver Name: emlxs
        Driver Version: 2.80.8.0 (2012.09.17.15.45)
        Type: L-port
        State: online
        Supported Speeds: 1Gb 2Gb 4Gb
        Current Speed: 2Gb
        Node WWN: 20000000c9c25df0
HBA Port WWN: 10000000c9c25d6f
        OS Device Name: /dev/cfg/c5
        Manufacturer: Emulex
        Model: LP11000-S
        Firmware Version: 2.82a4 (B3D2.82A4)
        FCode/BIOS Version: Boot:5.02a1 Fcode:1.50a9
        Serial Number: 0999BT0-1121000J8Z
        Driver Name: emlxs
        Driver Version: 2.80.8.0 (2012.09.17.15.45)
        Type: L-port
        State: online
        Supported Speeds: 1Gb 2Gb 4Gb
        Current Speed: 2Gb
        Node WWN: 20000000c9c25d6f



bash-3.2# mpathadm list mpath-support
mpath-support: libmpscsi_vhci.so

bash-3.2# mpathadm list initiator-port
Initiator Port: 210000144f415c2a
Initiator Port: 10000000c9c25df0
Initiator Port: 10000000c9c25d6f
Initiator Port: iqn.1986-03.com.sun:01:00144f415c2a.5354dd03,4000002a00ff

bash-3.2# mpathadm show initiator-port 10000000c9c25df0
Initiator Port: 10000000c9c25df0
        Transport Type: Fibre Channel
        OS Device File: /devices/pci@9,600000/SUNW,emlxs@1/fp@0,0
bash-3.2# mpathadm show initiator-port 10000000c9c25d6f
Initiator Port: 10000000c9c25d6f
        Transport Type: Fibre Channel
        OS Device File: /devices/pci@9,600000/SUNW,emlxs@2/fp@0,0


bash-3.2# mpathadm show lu /dev/rdsk/c6t600A0B800018B3CA000052F6534DB0C5d0s2
Logical Unit: /dev/rdsk/c6t600A0B800018B3CA000052F6534DB0C5d0s2
        mpath-support: libmpscsi_vhci.so
        Vendor: SUN
        Product: CSM100_R_FC
        Revision: 0660
        Name Type: unknown type
        Name: 600a0b800018b3ca000052f6534db0c5
        Asymmetric: yes
        Current Load Balance: round-robin
        Logical Unit Group ID: NA
        Auto Failback: on
        Auto Probing: NA

        Paths:
                Initiator Port Name: 10000000c9c25df0
                Target Port Name: 200400a0b81ffbef
                Override Path: NA
                Path State: OK
                Disabled: no

                Initiator Port Name: 10000000c9c25d6f
                Target Port Name: 200500a0b81ffbef
                Override Path: NA
                Path State: OK
                Disabled: no

        Target Port Groups:
                ID: 6
                Explicit Failover: yes
                Access State: standby
                Target Ports:
                        Name: 200400a0b81ffbef
                        Relative ID: 0

                ID: 7
                Explicit Failover: yes
                Access State: active
                Target Ports:
                        Name: 200500a0b81ffbef
                        Relative ID: 0

=================================
Test multipath

bash-3.2# fcinfo hba-port

HBA Port WWN: 10000000c9c25df0
        OS Device Name: /dev/cfg/c4
        Manufacturer: Emulex
        Model: LP11000-S
        Firmware Version: 2.82a4 (B3D2.82A4)
        FCode/BIOS Version: Boot:5.02a1 Fcode:1.50a9
        Serial Number: 0999BT0-1121000JC2
        Driver Name: emlxs
        Driver Version: 2.80.8.0 (2012.09.17.15.45)
        Type: L-port
        State: online
        Supported Speeds: 1Gb 2Gb 4Gb
        Current Speed: 2Gb
        Node WWN: 20000000c9c25df0
HBA Port WWN: 10000000c9c25d6f
        OS Device Name: /dev/cfg/c5
        Manufacturer: Emulex
        Model: LP11000-S
        Firmware Version: 2.82a4 (B3D2.82A4)
        FCode/BIOS Version: Boot:5.02a1 Fcode:1.50a9
        Serial Number: 0999BT0-1121000J8Z
        Driver Name: emlxs
        Driver Version: 2.80.8.0 (2012.09.17.15.45)
        Type: L-port
        State: online
        Supported Speeds: 1Gb 2Gb 4Gb
        Current Speed: 2Gb
        Node WWN: 20000000c9c25d6f
bash-3.2# luxadm -e forcelip /dev/cfg/c4

$ luxadm -e forcelip /dev/cfg/c4

bash-3.2# tail -f /var/adm/messages

[ID 349649 kern.info] [ 5.06C6]emlxs1: NOTICE: 730: Link reset. (Resetting link...)
[ID 349649 kern.info] [ 5.03DD]emlxs1: NOTICE: 710: Link down.
[ID 349649 kern.info] [ 5.0715]emlxs1: NOTICE: 730: Link reset.
[ID 349649 kern.info] [ 5.061B]emlxs1: NOTICE: 720: Link up. (2Gb, loop, initiator)

[ID 349649 kern.info] [ 5.06C6]emlxs0: NOTICE: 730: Link reset. (Resetting link...)
[ID 349649 kern.info] [ 5.03DD]emlxs0: NOTICE: 710: Link down.
[ID 349649 kern.info] [ 5.0715]emlxs0: NOTICE: 730: Link reset.
[ID 349649 kern.info] [ 5.061B]emlxs0: NOTICE: 720: Link up. (2Gb, loop, initiator)

Mac OS enable X11 Forwarding with SSH

noreply@blogger.com (Unknown) — Fri, 18 Apr 2014 04:02:00 +0000

Installation of the third-party software XQuartz.

$ if [ -z $DISPLAY ]; then export DISPLAY=:0.0; fi
$ ssh -X -Y oracle@10.151.100.247
$ ssh -X -Y oracle@10.151.100.247

Sun Sparc Install solaris with DHCP on Mac OS

noreply@blogger.com (Unknown) — Fri, 18 Apr 2014 03:38:00 +0000

Step 1: Prepare File System

$ hdiutil create -size 1g -type SPARSE -fs HFSX -volname "install" install
$ hdiutil attach install.sparseimage -mountpoint /install

Step 2: Open file ISO

$ open sol-10-u8-ga-x86-dvd.iso

$ df -h
/dev/disk3     2.1Gi 2.1Gi    0Bi   100%        0        0 100%   /Volumes/SOL_10_811_SPARC

Step 3: NFS config

$ sudo vi /etc/exports

/install                  -alldirs -maproot=root
/Volumes/SOL_10_811_X86 -alldirs -maproot=root

Start NFS
$ sudo nfsd checkexports && sudo nfsd disable
$ sudo nfsd checkexports && sudo nfsd enable

Check export

$ showmount -e
Exports list on localhost:
/Volumes/SOL_10_811_SPARC             Everyone
/install                            Everyone

Step 4, TFTP

$ sudo vi /System/Library/LaunchDaemons/tftp.plist

[...]
    ProgramArguments
    
        /usr/libexec/tftpd
        -i
        -s
        /install/tftpboot
    
[...]

$ mkdir /install/tftpboot
$ sudo launchctl unload -w /System/Library/LaunchDaemons/tftp.plist
$ sudo launchctl load -w /System/Library/LaunchDaemons/tftp.plist

Test tftp
echo "testing" >/install/tftpboot/testfile
printf "verbose\ntrace\nget testfile\n" | tftp localhost
rm /install/tftpboot/testfile

Step 5 rsync

$ rsync -av /Volumes/SOL_10_811_SPARC/Solaris_10/Tools/Boot/platform
/install/tftpboot/boot_sparc/

View file

TRUNGs-MacBook-Pro:tam lptrung$ cd /install/tftpboot/boot_sparc/platform/
TRUNGs-MacBook-Pro:platform lptrung$ ls
sun4u   sun4us   sun4v
TRUNGs-MacBook-Pro:platform lptrung$ cd sun4u
TRUNGs-MacBook-Pro:sun4u lptrung$ ls -ltr
total 2584
-rw-r--r-- 1 root wheel 1092272 Aug 23 2011 wanboot
-rw-r--r-- 1 root wheel   221584 Aug 23 2011 inetboot
lrwxrwxrwx 1 root wheel       34 Aug 23 2011 boot_archive -> ../../../../../boot/sparc.miniroot

Step 6 Config network server

$ ifconfig -a

en1: flags=8863 mtu 1500
    ether 4c:8d:79:e0:59:ac
    inet6 fe80::4e8d:79ff:fee0:59ac%en1 prefixlen 64 scopeid 0x4
    inet 192.168.100.1 netmask 0xffffff00 broadcast 192.168.100.255
    media: autoselect
    status: active

Step 7, DHCP with ISC DHCP

$ cat /etc/dhcpd.conf
option domain-name "example.com";
option domain-name-servers 192.168.100.1;
option subnet-mask 255.255.255.0;

ddns-update-style none;
authoritative;
default-lease-time 43200;
max-lease-time 86400;
server-name "servername";

###########SOLARIS SPARC 10 ######################

subnet 192.168.100.0 netmask 255.255.255.0 {
pool {range 192.168.100.5 192.168.100.254;}
option routers 192.168.100.1;
}

option space SUNW;
option SUNW.root-mount-options code 1 = text;
option SUNW.root-server-ip-address code 2 = ip-address;
option SUNW.root-server-hostname code 3 = text;
option SUNW.root-path-name code 4 = text;
option SUNW.swap-server-ip-address code 5 = ip-address;
option SUNW.swap-file-path code 6 = text;
option SUNW.boot-file-path code 7 = text;
option SUNW.posix-timezone-string code 8 = text;
option SUNW.boot-read-size code 9 = unsigned integer 16;
option SUNW.install-server-ip-address code 10 = ip-address;
option SUNW.install-server-hostname code 11 = text;
option SUNW.install-path code 12 = text;
option SUNW.sysid-config-file-server code 13 = text;
option SUNW.JumpStart-server code 14 = text;
option SUNW.terminal-name code 15 = text;
option SUNW.root-mount-options "rsize=32768";

group {

        filename "/boot_sparc/platform/sun4u/inetboot";

        vendor-option-space SUNW;

        next-server 192.168.100.1;

        option SUNW.JumpStart-server "191.168.100.1:/Volumes/SOL_10_811_SPARC/Solaris_10/";
        option SUNW.install-server-hostname "191.168.100.1";
        option SUNW.install-server-ip-address 191.168.100.1;
        option SUNW.install-path "/Volumes/SOL_10_811_SPARC";
        option SUNW.root-server-hostname "191.168.100.1";
        option SUNW.root-server-ip-address 191.168.100.1;
        option SUNW.root-path-name "/Volumes/SOL_10_811_SPARC/Solaris_10/Tools/Boot/";

        host v445 {
                hardware ethernet 00:14:4f:a0:c0:dc;
                fixed-address 192.168.100.10;
                option host-name "TT4-V445-A";
                option SUNW.sysid-config-file-server "191.168.100.1:/install/jumpstart";
        }

}

#########END SOLARIS SPARC 10 ################################

subnet 192.168.2.0 netmask 255.255.255.0 {
        option broadcast-address 192.168.2.255;
        option subnet-mask 255.255.255.0;
        option routers 192.168.2.1;
        pool { range 192.168.2.116 192.168.2.254; }
}

host client3 {
filename "/boot/grub/pxegrub";
server-name "servername";
next-server 192.168.2.166;
hardware ethernet 00:1C:42:C4:CF:1D;
fixed-address 192.168.2.100;
}
----------------------------------------------------------------------------------------------------

Test DHCP
$ sudo dhcpd
Listening on BPF/en1/4c:8d:79:e0:59:ac/192.168.100.0/24
Sending on   BPF/en1/4c:8d:79:e0:59:ac/192.168.100.0/24

$sudo /opt/local/sbin/dhcpd -q -f$ ps -ef |grep dhcp
    0   187     1   0 2:25PM ??         0:00.56 /opt/local/sbin/dhcpd -q -f
501 1815   990   0 10:03AM ttys001    0:00.00 grep dhcp

Note: if dhcpd not start, You can kill -9 ID DHCP and start it

Step 8: Boot Server V890 and boot net dhcp
Testing /pci@8,600000/network@1
Testing /pci@8,600000/SUNW,qlc@2
Testing /pci@9,700000/ebus@1/i2c@1,2e
Testing /pci@9,700000/ebus@1/i2c@1,30
Testing /pci@9,700000/ebus@1/i2c@1,50002e

- Send break load ok mode

ok show-nets
ok cd /pci@8,600000/network@1
ok .properties => find search mac address
ok device-end
ok boot /pci@........:dhcp

Step 9: After install config network ipmp
$ dladm show-dev

$ vi /etc/hostname.bge0
10.151.100.240 netmask + broadcast + group ipmp0 up

$ vi /etc/hostname.bge1
group ipmp0 standby up

$vi /etc/netmasks
10.151.100.192 255.255.255.192

$vi /etc/defaultrouter
10.151.100.193

$ svcadm restart network/physical

After ping test network, if not run please reboot and test ipmp

Step 10: Enable SSH for root
$ vi /etc/ssh/sshd_config
You can change PermitRootLogin yes

$svcadm restart svc:/network/ssh:default

Step 11: Map disk from SAN to server and scan device create ZFS

$echo | format

Use the command to find the newly created drive and load its drivers.
$devfsadm

Check port
luxadm -e port
prtconf -vp | grep wwn
fcinfo hba-port

Install oracle 11g silent

noreply@blogger.com (Unknown) — Fri, 18 Apr 2014 02:06:00 +0000

Copy from Oracle sample file: /database/response/db_install.rsp

oracle.install.responseFileVersion=/oracle/install/rspfmt_dbinstall_response_schema_v11_2_0
oracle.install.option=INSTALL_DB_SWONLY
UNIX_GROUP_NAME=oinstall
INVENTORY_LOCATION=/oracle/OraInventory
ORACLE_HOME=/oracle/product/11.2.0/template
ORACLE_BASE=/oracle
oracle.install.db.InstallEdition=EE
oracle.install.db.DBA_GROUP=dba
oracle.install.db.OPER_GROUP=dba
DECLINE_SECURITY_UPDATES=true

2) Silent installation
./runInstaller -silent -noconfig -responseFile /u01/download/db11ginstall.rsp

Starting Oracle Universal Installer...

Checking Temp space: must be greater than 120 MB.   Actual 22753 MB    Passed
Checking swap space: must be greater than 150 MB.   Actual 3817 MB    Passed
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2011-06-17_09-02-07PM. Please wait ..
$ You can find the log of this install session at:
 /oracle/OraInventory/logs/installActions2011-06-17_09-02-07PM.log
The following configuration scripts need to be executed as the "root" user.
 #!/bin/sh
 #Root scripts to run

/oracle/product/11.2.0/template/root.sh
To execute the configuration scripts:
         1. Open a terminal window
         2. Log in as "root"
         3. Run the scripts
         4. Return to this window and hit "Enter" key to continue

Successfully Setup Software.

Example:

####################################################################
## Copyright(c) Oracle Corporation 1998,2011. All rights reserved.##
##                                                                ##
## Specify values for the variables listed below to customize     ##
## your installation.                                             ##
##                                                                ##
## Each variable is associated with a comment. The comment        ##
## can help to populate the variables with the appropriate        ##
## values.         ##
##                                                                ##
## IMPORTANT NOTE: This file contains plain text passwords and    ##
## should be secured to have read permission only by oracle user  ##
## or db administrator who owns this installation.                ##
##                                                                ##
####################################################################

#------------------------------------------------------------------------------
# Do not change the following system generated value. 
#------------------------------------------------------------------------------
oracle.install.responseFileVersion=/oracle/install/rspfmt_dbinstall_response_schema_v11_2_0

#------------------------------------------------------------------------------
# Specify the installation option.
# It can be one of the following:
# 1. INSTALL_DB_SWONLY
# 2. INSTALL_DB_AND_CONFIG
# 3. UPGRADE_DB
#-------------------------------------------------------------------------------
oracle.install.option=INSTALL_DB_SWONLY

#-------------------------------------------------------------------------------
# Specify the hostname of the system as set during the install. It can be used
# to force the installation to use an alternative hostname rather than using the
# first hostname found on the system. (e.g., for systems with multiple hostnames 
# and network interfaces)
#-------------------------------------------------------------------------------
ORACLE_HOSTNAME=TT4-V890-B

#-------------------------------------------------------------------------------
# Specify the Unix group to be set for the inventory directory.  
#-------------------------------------------------------------------------------
UNIX_GROUP_NAME=oinstall

#-------------------------------------------------------------------------------
# Specify the location which holds the inventory files.
# This is an optional parameter if installing on
# Windows based Operating System.
#-------------------------------------------------------------------------------
INVENTORY_LOCATION=/u01/app/oraInventory

#-------------------------------------------------------------------------------
# Specify the languages in which the components will be installed.             
# 
# en   : English                  ja   : Japanese                  
# fr   : French                   ko   : Korean                    
# ar   : Arabic                   es   : Latin American Spanish    
# bn   : Bengali                  lv   : Latvian                   
# pt_BR: Brazilian Portuguese     lt   : Lithuanian                
# bg   : Bulgarian                ms   : Malay                     
# fr_CA: Canadian French          es_MX: Mexican Spanish           
# ca   : Catalan                  no   : Norwegian                 
# hr   : Croatian                 pl   : Polish                    
# cs   : Czech                    pt   : Portuguese                
# da   : Danish                   ro   : Romanian                  
# nl   : Dutch                    ru   : Russian                   
# ar_EG: Egyptian                 zh_CN: Simplified Chinese        
# en_GB: English (Great Britain)  sk   : Slovak                    
# et   : Estonian                 sl   : Slovenian                 
# fi   : Finnish                  es_ES: Spanish                   
# de   : German                   sv   : Swedish                   
# el   : Greek                    th   : Thai                      
# iw   : Hebrew                   zh_TW: Traditional Chinese       
# hu   : Hungarian                tr   : Turkish                   
# is   : Icelandic                uk   : Ukrainian                 
# in   : Indonesian               vi   : Vietnamese                
# it   : Italian                                                   
#
# all_langs   : All languages
#
# Specify value as the following to select any of the languages.
# Example : SELECTED_LANGUAGES=en,fr,ja
#
# Specify value as the following to select all the languages.
# Example : SELECTED_LANGUAGES=all_langs  
#------------------------------------------------------------------------------
SELECTED_LANGUAGES=en

#------------------------------------------------------------------------------
# Specify the complete path of the Oracle Home.
#------------------------------------------------------------------------------
ORACLE_HOME=/u01/app/oracle/product/11.2.0.3/dbhome_1

#------------------------------------------------------------------------------
# Specify the complete path of the Oracle Base. 
#------------------------------------------------------------------------------
ORACLE_BASE=/u01/app/oracle

#------------------------------------------------------------------------------
# Specify the installation edition of the component.                        
#                                                             
# The value should contain only one of these choices.        
# EE     : Enterprise Edition                                
# SE     : Standard Edition                                  
# SEONE  : Standard Edition One
# PE     : Personal Edition (WINDOWS ONLY)
#------------------------------------------------------------------------------
oracle.install.db.InstallEdition=EE

#------------------------------------------------------------------------------
# This variable is used to enable or disable custom install and is considered
# only if InstallEdition is EE.
#
# true  : Components mentioned as part of 'optionalComponents' property
#         are considered for install.
# false : Value for 'optionalComponents' is not considered.
#------------------------------------------------------------------------------
oracle.install.db.EEOptionsSelection=false

#------------------------------------------------------------------------------
# This variable is considered only if 'EEOptionsSelection' is set to true. 
#
# Description: List of Enterprise Edition Options you would like to enable.
#
#              The following choices are available. You may specify any
#              combination of these choices.  The components you choose should
#              be specified in the form "internal-component-name:version"
#              Below is a list of components you may specify to enable.
#        
#              oracle.oraolap:11.2.0.3.0 - Oracle OLAP
#              oracle.rdbms.dm:11.2.0.3.0 - Oracle Data Mining
#              oracle.rdbms.dv:11.2.0.3.0 - Oracle Database Vault
#              oracle.rdbms.lbac:11.2.0.3.0 - Oracle Label Security
#              oracle.rdbms.partitioning:11.2.0.3.0 - Oracle Partitioning
#              oracle.rdbms.rat:11.2.0.3.0 - Oracle Real Application Testing
#------------------------------------------------------------------------------
oracle.install.db.optionalComponents=oracle.rdbms.partitioning:11.2.0.3.0,oracle.oraolap:11.2.0.3.0,oracle.rdbms.dm:11.2.0.3.0,oracle.rdbms.dv:11.2.0.3.0,oracle.rdbms.lbac:11.2.0.3.0,oracle.rdbms.rat:11.2.0.3.0

###############################################################################
#                                                                             #
# PRIVILEGED OPERATING SYSTEM GROUPS                                         #
# ------------------------------------------                                  #
# Provide values for the OS groups to which OSDBA and OSOPER privileges       #
# needs to be granted. If the install is being performed as a member of the   #  
# group "dba", then that will be used unless specified otherwise below.       #
#                                                                             #
# The value to be specified for OSDBA and OSOPER group is only for UNIX based #
# Operating System.                                                           #
#                                                                             #
###############################################################################

#------------------------------------------------------------------------------
# The DBA_GROUP is the OS group which is to be granted OSDBA privileges.
#------------------------------------------------------------------------------
oracle.install.db.DBA_GROUP=dba

#------------------------------------------------------------------------------
# The OPER_GROUP is the OS group which is to be granted OSOPER privileges.
# The value to be specified for OSOPER group is optional.
#------------------------------------------------------------------------------
oracle.install.db.OPER_GROUP=dba

#------------------------------------------------------------------------------
# Specify the cluster node names selected during the installation.
# Example : oracle.install.db.CLUSTER_NODES=node1,node2
#------------------------------------------------------------------------------
oracle.install.db.CLUSTER_NODES=

#------------------------------------------------------------------------------
# This variable is used to enable or disable RAC One Node install.
#
# true  : Value of RAC One Node service name is used.
# false : Value of RAC One Node service name is not used.
#
# If left blank, it will be assumed to be false
#------------------------------------------------------------------------------
oracle.install.db.isRACOneInstall=false

#------------------------------------------------------------------------------
# Specify the name for RAC One Node Service. 
#------------------------------------------------------------------------------
oracle.install.db.racOneServiceName=

#------------------------------------------------------------------------------
# Specify the type of database to create.
# It can be one of the following:
# - GENERAL_PURPOSE/TRANSACTION_PROCESSING             
# - DATA_WAREHOUSE                                
#------------------------------------------------------------------------------
oracle.install.db.config.starterdb.type=GENERAL_PURPOSE

#------------------------------------------------------------------------------
# Specify the Starter Database Global Database Name. 
#------------------------------------------------------------------------------
oracle.install.db.config.starterdb.globalDBName=utility

#------------------------------------------------------------------------------
# Specify the Starter Database SID.
#------------------------------------------------------------------------------
oracle.install.db.config.starterdb.SID=utility

#------------------------------------------------------------------------------
# Specify the Starter Database character set.
#                                              
# It can be one of the following:
# AL32UTF8, WE8ISO8859P15, WE8MSWIN1252, EE8ISO8859P2,
# EE8MSWIN1250, NE8ISO8859P10, NEE8ISO8859P4, BLT8MSWIN1257,
# BLT8ISO8859P13, CL8ISO8859P5, CL8MSWIN1251, AR8ISO8859P6,
# AR8MSWIN1256, EL8ISO8859P7, EL8MSWIN1253, IW8ISO8859P8,
# IW8MSWIN1255, JA16EUC, JA16EUCTILDE, JA16SJIS, JA16SJISTILDE,
# KO16MSWIN949, ZHS16GBK, TH8TISASCII, ZHT32EUC, ZHT16MSWIN950,
# ZHT16HKSCS, WE8ISO8859P9, TR8MSWIN1254, VN8MSWIN1258
#------------------------------------------------------------------------------
oracle.install.db.config.starterdb.characterSet=AL32UTF8

#------------------------------------------------------------------------------
# This variable should be set to true if Automatic Memory Management 
# in Database is desired.
# If Automatic Memory Management is not desired, and memory allocation
# is to be done manually, then set it to false.
#------------------------------------------------------------------------------
oracle.install.db.config.starterdb.memoryOption=true

#------------------------------------------------------------------------------
# Specify the total memory allocation for the database. Value(in MB) should be
# at least 256 MB, and should not exceed the total physical memory available 
# on the system.
# Example: oracle.install.db.config.starterdb.memoryLimit=512
#------------------------------------------------------------------------------
oracle.install.db.config.starterdb.memoryLimit=4096

#------------------------------------------------------------------------------
# This variable controls whether to load Example Schemas onto
# the starter database or not.
#------------------------------------------------------------------------------
oracle.install.db.config.starterdb.installExampleSchemas=false

#------------------------------------------------------------------------------
# This variable includes enabling audit settings, configuring password profiles
# and revoking some grants to public. These settings are provided by default. 
# These settings may also be disabled.    
#------------------------------------------------------------------------------
oracle.install.db.config.starterdb.enableSecuritySettings=false

###############################################################################
#                                                                             #
# Passwords can be supplied for the following four schemas in the       #
# starter database:                  #
#   SYS                                                                       #
#   SYSTEM                                                                    #
#   SYSMAN (used by Enterprise Manager)                                       #
#   DBSNMP (used by Enterprise Manager)                                       #
#                                                                             #
# Same password can be used for all accounts (not recommended)         #
# or different passwords for each account can be provided (recommended)       #
#                                                                             #
###############################################################################

#------------------------------------------------------------------------------
# This variable holds the password that is to be used for all schemas in the
# starter database.
#-------------------------------------------------------------------------------
oracle.install.db.config.starterdb.password.ALL=sys236

#-------------------------------------------------------------------------------
# Specify the SYS password for the starter database.
#-------------------------------------------------------------------------------
oracle.install.db.config.starterdb.password.SYS=

#-------------------------------------------------------------------------------
# Specify the SYSTEM password for the starter database.
#-------------------------------------------------------------------------------
oracle.install.db.config.starterdb.password.SYSTEM=

#-------------------------------------------------------------------------------
# Specify the SYSMAN password for the starter database.
#-------------------------------------------------------------------------------
oracle.install.db.config.starterdb.password.SYSMAN=

#-------------------------------------------------------------------------------
# Specify the DBSNMP password for the starter database.
#-------------------------------------------------------------------------------
oracle.install.db.config.starterdb.password.DBSNMP=

#-------------------------------------------------------------------------------
# Specify the management option to be selected for the starter database. 
# It can be one of the following:
# 1. GRID_CONTROL
# 2. DB_CONTROL
#-------------------------------------------------------------------------------
oracle.install.db.config.starterdb.control=DB_CONTROL

#-------------------------------------------------------------------------------
# Specify the Management Service to use if Grid Control is selected to manage 
# the database.      
#-------------------------------------------------------------------------------
oracle.install.db.config.starterdb.gridcontrol.gridControlServiceURL=

###############################################################################
#                                                                             #
# SPECIFY BACKUP AND RECOVERY OPTIONS                                        #
# ------------------------------------                                #
# Out-of-box backup and recovery options for the database can be mentioned    #
# using the entries below.            # 
#                                                                             #
###############################################################################

#------------------------------------------------------------------------------
# This variable is to be set to false if automated backup is not required. Else 
# this can be set to true.
#------------------------------------------------------------------------------
oracle.install.db.config.starterdb.automatedBackup.enable=false

#------------------------------------------------------------------------------
# Regardless of the type of storage that is chosen for backup and recovery, if 
# automated backups are enabled, a job will be scheduled to run daily to backup 
# the database. This job will run as the operating system user that is 
# specified in this variable.
#------------------------------------------------------------------------------
oracle.install.db.config.starterdb.automatedBackup.osuid=

#-------------------------------------------------------------------------------
# Regardless of the type of storage that is chosen for backup and recovery, if 
# automated backups are enabled, a job will be scheduled to run daily to backup 
# the database. This job will run as the operating system user specified by the 
# above entry. The following entry stores the password for the above operating 
# system user.
#-------------------------------------------------------------------------------
oracle.install.db.config.starterdb.automatedBackup.ospwd=

#-------------------------------------------------------------------------------
# Specify the type of storage to use for the database.
# It can be one of the following:
# - FILE_SYSTEM_STORAGE
# - ASM_STORAGE
#------------------------------------------------------------------------------
oracle.install.db.config.starterdb.storageType=FILE_SYSTEM_STORAGE

#-------------------------------------------------------------------------------
# Specify the database file location which is a directory for datafiles, control
# files, redo logs.         
#
# Applicable only when oracle.install.db.config.starterdb.storage=FILE_SYSTEM_STORAGE 
#-------------------------------------------------------------------------------
oracle.install.db.config.starterdb.fileSystemStorage.dataLocation=/u01/oradata

#-------------------------------------------------------------------------------
# Specify the backup and recovery location.
#
# Applicable only when oracle.install.db.config.starterdb.storage=FILE_SYSTEM_STORAGE 
#-------------------------------------------------------------------------------
oracle.install.db.config.starterdb.fileSystemStorage.recoveryLocation=

#-------------------------------------------------------------------------------
# Specify the existing ASM disk groups to be used for storage.
#
# Applicable only when oracle.install.db.config.starterdb.storage=ASM_STORAGE
#-------------------------------------------------------------------------------
oracle.install.db.config.asm.diskGroup=

#-------------------------------------------------------------------------------
# Specify the password for ASMSNMP user of the ASM instance.                  
#
# Applicable only when oracle.install.db.config.starterdb.storage=ASM_STORAGE 
#-------------------------------------------------------------------------------
oracle.install.db.config.asm.ASMSNMPPassword=

#------------------------------------------------------------------------------
# Specify the My Oracle Support Account Username.
#
#  Example   : MYORACLESUPPORT_USERNAME=abc@oracle.com
#------------------------------------------------------------------------------
MYORACLESUPPORT_USERNAME=abc@oracle.com

#------------------------------------------------------------------------------
# Specify the My Oracle Support Account Username password.
#
# Example    : MYORACLESUPPORT_PASSWORD=password
#------------------------------------------------------------------------------
MYORACLESUPPORT_PASSWORD=123

#------------------------------------------------------------------------------
# Specify whether to enable the user to set the password for
# My Oracle Support credentials. The value can be either true or false.
# If left blank it will be assumed to be false.
#
# Example    : SECURITY_UPDATES_VIA_MYORACLESUPPORT=true
#------------------------------------------------------------------------------
SECURITY_UPDATES_VIA_MYORACLESUPPORT=false

#------------------------------------------------------------------------------
# Specify whether user doesn't want to configure Security Updates.
# The value for this variable should be true if you don't want to configure
# Security Updates, false otherwise. 
#
# The value can be either true or false. If left blank it will be assumed
# to be false.
#
# Example    : DECLINE_SECURITY_UPDATES=false
#------------------------------------------------------------------------------
DECLINE_SECURITY_UPDATES=true

#------------------------------------------------------------------------------
# Specify the Proxy server name. Length should be greater than zero.
#
# Example    : PROXY_HOST=proxy.domain.com 
#------------------------------------------------------------------------------
PROXY_HOST=

#------------------------------------------------------------------------------
# Specify the proxy port number. Should be Numeric and atleast 2 chars.
#
# Example    : PROXY_PORT=25 
#------------------------------------------------------------------------------
PROXY_PORT=

#------------------------------------------------------------------------------
# Specify the proxy user name. Leave PROXY_USER and PROXY_PWD 
# blank if your proxy server requires no authentication.
#
# Example    : PROXY_USER=username 
#------------------------------------------------------------------------------
PROXY_USER=

#------------------------------------------------------------------------------
# Specify the proxy password. Leave PROXY_USER and PROXY_PWD  
# blank if your proxy server requires no authentication.
#
# Example    : PROXY_PWD=password 
#------------------------------------------------------------------------------
PROXY_PWD=

#------------------------------------------------------------------------------
# Specify the proxy realm. This value is used if auto-updates option is selected.
#
# Example    : PROXY_REALM=metalink 
#------------------------------------------------------------------------------
PROXY_REALM=

#------------------------------------------------------------------------------
# Specify the Oracle Support Hub URL. 
# 
# Example    : COLLECTOR_SUPPORTHUB_URL=https://orasupporthub.company.com:8080/
#------------------------------------------------------------------------------
COLLECTOR_SUPPORTHUB_URL=

#------------------------------------------------------------------------------
# Specify the auto-updates option. It can be one of the following:
# a.MYORACLESUPPORT_DOWNLOAD
# b.OFFLINE_UPDATES
# c.SKIP_UPDATES
#------------------------------------------------------------------------------
oracle.installer.autoupdates.option=SKIP_UPDATES
#------------------------------------------------------------------------------
# In case MYORACLESUPPORT_DOWNLOAD option is chosen, specify the location where
# the updates are to be downloaded.
# In case OFFLINE_UPDATES option is chosen, specify the location where the updates 
# are present.
oracle.installer.autoupdates.downloadUpdatesLoc=
#------------------------------------------------------------------------------
# Specify the My Oracle Support Account Username which has the patches download privileges  
# to be used for software updates.
#  Example   : AUTOUPDATES_MYORACLESUPPORT_USERNAME=abc@oracle.com
#------------------------------------------------------------------------------
AUTOUPDATES_MYORACLESUPPORT_USERNAME=

#------------------------------------------------------------------------------
# Specify the My Oracle Support Account Username password which has the patches download privileges  
# to be used for software updates.
#
# Example    : AUTOUPDATES_MYORACLESUPPORT_PASSWORD=password
#------------------------------------------------------------------------------
AUTOUPDATES_MYORACLESUPPORT_PASSWORD=

How to setup Jumpstart from OSX

noreply@blogger.com (Unknown) — Tue, 15 Apr 2014 03:38:00 +0000

Step 1, Prepare File System

First off, create a dedicated file system which we can export our jumpstart configuration from. You can probably skip this and just use any existing file system but this way everything is self-contained and we avoid NFS exporting more than we need.

We use HFSX to ensure that the file system is case sensitive, HFS+ can cause problems with pkgadd(1M).

$ hdiutil create -size 1g -type SPARSE -fs HFSX -volname "install" install
$ hdiutil attach install.sparseimage -mountpoint /install
Next up, download and mount sol-10-u10-ga-x86-dvd.iso.

$ open sol-10-u8-ga-x86-dvd.iso

MacBook-Pro:tftpboot$ df -h
Filesystem      Size   Used Avail Capacity iused    ifree %iused Mounted on
/dev/disk1s2   238Gi 209Gi   29Gi    88% 54790142 7514728   88%   /
devfs          195Ki 195Ki    0Bi   100%      674        0 100%   /dev
/dev/disk0s2   299Gi   34Gi 265Gi    12% 8878443 69413608   11%   /Volumes/DATA1
map -hosts       0Bi    0Bi    0Bi   100%        0        0 100%   /net
map auto_home    0Bi    0Bi    0Bi   100%        0        0 100%   /home
/dev/disk0s3   399Gi   94Gi 305Gi    24% 24653272 79955649   24%   /Volumes/DATA2
/dev/disk2s1   1.0Gi 113Mi 911Mi    12%    28899   233233   11%   /install
/dev/disk3     2.1Gi 2.1Gi    0Bi   100%        0        0 100%   /Volumes/SOL_10_811_X86
/dev/disk4     2.1Gi 2.1Gi    0Bi   100%        0        0 100%   /Volumes/SOL_10_811_SPARC

Step 2, NFS

Share /install and the DVD via NFS with the correct options. -alldirs allows clients to mount from any point within that file system (which jumpstart requires), and -maproot=root is also required by jumpstart. As this allows root-owned files to be created, make sure you understand the security risks.

$ sudo vi /etc/exports

/install                  -alldirs -maproot=root
/Volumes/SOL_10_811_X86 -alldirs -maproot=root

$ sudo nfsd checkexports && sudo nfsd enable

$ sudo nfsd checkexports && sudo nfsd disable
$ sudo nfsd checkexports && sudo nfsd enable

Check export

$ showmount -e
Exports list on localhost:
/Volumes/SOL_10_811_X86             Everyone
/install                            Everyone

Step 3, DHCP

$ cat /etc/bootpd.plist


<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>dhcp_enabled</key>
    <string>en1</string>
    <key>Subnets</key>
    <array>
        <dict>
            <key>name</key>
            <string>10.151.120</string>
            <key>net_mask</key>
            <string>255.255.255.0</string>
            <key>net_address</key>
            <string>10.151.120.0</string>
            <key>net_range</key>
            <array>
                <string>10.151.120.194</string>
                <string>10.151.120.254</string>
            </array>
            <key>allocate</key>
            <true/>
            <key>dhcp_option_66</key>
            <string>10.151.120.193</string>
            <key>dhcp_option_67</key>
            <data>L2Jvb3QvZ3J1Yi9weGVncnViAA==</data>
        </dict>
    </array>
</dict>
</plist>

Note 10.151.120.193 => IP server (source setup)

If the file /etc/bootpd.plist already exists, turn off Internet Sharing in System Preferences > Sharing. Then the file will be removed, and you can create it as in this step.

(Make sure to move /etc/bootpd.plist to the Trash and disable the DHCP server before turning Internet Sharing back on. See "Uninstall steps" below.)
If you are using an ethernet port other than en1 (see System Information or System Profiler for the port name), change the value for the dhcp_enabled key to the port you are using.
The data for the dhcp_option_67 key is the bootloader filename "pxelinux.0" (see step 9 below), null terminated and encoded into base64. This can be generated with the free DHCP Option Code Utility, or by entering the following command in Terminal:

 $ printf %s00 `echo -n /boot/grub/pxegrub | xxd -p` | xxd -r -p | openssl base64

L2Jvb3QvZ3J1Yi9weGVncnViAA==

(See this discussion thread.)

The string for the dhcp_option_66 key is the IP address of the tftp server, i.e. the address of the Mac from step 2.

Stop and start service DHCP

$ sudo /bin/launchctl unload -w /System/Library/LaunchDaemons/bootps.plist
$ sudo /bin/launchctl load -w /System/Library/LaunchDaemons/bootps.plist

Most parts of these configurations should be self-explanatory. The /boot/grub/pxegrub entry is important for our next step, and I’d recommend using that exact pathname for reasons explained later.

Step 4, TFTP

Now, enable the TFTP server which comes with OSX. I added the -s option so tftpd would chroot to the tftpboot directory, both for security reasons and also to ensure that paths specified as /path/to/file would work correctly (relative to /install/tftpboot).

I also changed the location of the tftpboot directory so that everything was self-contained within the UFS image. In previous attempts I didn’t do this and ran into problems with GRUB which I think are again caused by case-insensitive file systems.

$ sudo vi /System/Library/LaunchDaemons/tftp.plist

[...]
    <key>ProgramArguments</key>
    <array>
        <string>/usr/libexec/tftpd</string>
        <string>-i</string>
        <string>-s</string>
        <string>/install/tftpboot</string>
    </array>
[...]

$ mkdir /install/tftpboot
$ sudo launchctl unload -w /System/Library/LaunchDaemons/tftp.plist
$ sudo launchctl load -w /System/Library/LaunchDaemons/tftp.plist

Test tftp
You can then create a test file and check that it’s working as you expect, using:

echo "testing" >/install/tftpboot/testfile
printf "verbose\ntrace\nget testfile\n" | tftp localhost
rm /install/tftpboot/testfile

Step 5, GRUB

Next up, configure PXE booting using GRUB. We need to copy the GRUB images and configuration from the Solaris install DVD then modify it for our environment:

$ rsync -av /Volumes/SOL_10_811_X86/boot/grub /install/tftpboot/boot/
$ rsync -av /Volumes/SOL_10_811_X86/boot/multiboot /install/tftpboot/sol10u8x/
$ rsync -av /Volumes/SOL_10_811_X86/boot/x86.miniroot /install/tftpboot/sol10u8x/

As we are copying the boot files from the DVD, they come hardcoded with particular pathnames to e.g. the menu.lst file. While it may be possible to pass extra parameters to pxegrub and load this from a different path, I simply recommend doing as I do and replicating the /boot/grub/ path structure so that everything Just Works.

The menu.lst file includes kernel arguments and allows you to choose which type of install to perform at startup. My file listed below has 3 choices:

    Unattended install using a graphical environment (if available). The “install” keyword after the kernel instructs it to perform an unattended install, so long as it can find the necessary settings from sysidcfg etc.
    As above, but force the use of the console and do not start a graphical environment (using the “nowin” keyword)
    A manual install, so you need to go through the steps of layout out disks, selecting packages, etc.

$ vi /install/tftpboot/boot/grub/menu.lst

default=0
timeout=60

title Solaris PXE Unattended Install
    kernel /sol10u8x/multiboot kernel/unix - install -B \
      install_media=10.151.120.193:/Volumes/SOL_10_811_X86,\
      sysid_config=10.151.120.193:/install/jumpstart,\
      install_config=10.151.120.193:/install/jumpstart
    module /sol10u8x/x86.miniroot

title Solaris PXE Unattended Install (console)
    kernel /sol10u8x/multiboot kernel/unix - install nowin -B \
      install_media=10.151.120.193:/Volumes/SOL_10_811_X86,\
      sysid_config=10.151.120.193:/install/jumpstart,\
      install_config=10.151.120.193:/install/jumpstart
    module /sol10u8x/x86.miniroot

title Solaris PXE Manual Install
    kernel /sol10u8x/multiboot kernel/unix -B \
      install_media=10.151.120.193:/Volumes/SOL_10_811_X86
    module /sol10u8x/x86.miniroot

Anyone used to doing jumpstart but with RARP/bootparams will notice the symmetry between install_config etc in the GRUB configuration and similar options in /etc/bootparams. Make sure that the full kernel arguments are all on one line, and that there are no spaces in between the install_media=..,sysid_config=.. options.

Step 6, Jumpstart

Finally, set up your Jumpstart configuration. Here’s what I personally use, you may want something different:

$ mkdir /install/jumpstart
$ cd /install/jumpstart
$ vi sysidcfg

#password is password
root_password=uHL9FDUAkZpGs
timeserver=localhost
timezone=Europe/London
security_policy=NONE
service_profile=limited_net
system_locale=C
terminal=vt100
keyboard=US-English
name_service=none
network_interface=ce0 { hostname=TT4-V890-A
ip_address=10.151.120.248
protocol_ipv6=no
netmask=255.255.255.192
default_route=10.151.120.193}
nfs4_domain=dynamic

Ordinarily this file is processed using a check script available in the jumpstart_sample directory on the Solaris DVD, however this only works from a Solaris host. To create the rules.ok file, we need to strip out any comments and put entries on one line, then create the checksum (although this isn’t actually necessary).

$ vi rules

hostname host1 - profile -

$ cp rules rules.ok
$ echo "# version=2 checksum=$(cksum -o 2 rules | awk '{print $1}')" >> rules.ok

Machine profile. This gives me a full Solaris install (minus OEM stuff) on mirrored ZFS disks with additional dump/swap space (the defaults made dump a bit too small I found).

$ vi profile

install_type    initial_install
pool            store auto 4g 4g mirror c1t0d0s0 c1t1d0s0
bootenv         installbe bename sol10u8x
cluster         SUNWCall

Step 7 Change IP server

And check IP status

$ ifconfig -a

en1: flags=8963 mtu 1500
    ether 4c:8d:79:e0:59:ac
    inet6 fe80::4e8d:79ff:fee0:59ac%en1 prefixlen 64 scopeid 0x5
    inet 10.151.120.193 netmask 0xffffff00 broadcast 10.151.120.255
    media: autoselect
    status: active

Step 8, Make A Cup Of Tea

With everything set up you should be able to enable PXE booting in your BIOS and watch it automatically install. One small minor problem you may have if you don’t have a BIOS which allows you to hit F12 or similar and choose PXE booting for one boot only is that it will infinitely cycle through installing, rebooting, installing, rebooting.. until you change your boot options.

Running Mac OS X's built-in DHCP server

noreply@blogger.com (Unknown) — Mon, 14 Apr 2014 04:22:00 +0000

It turns out that Mac OS X comes with a DHCP server built-in. There don't seem to be any good and simple instructions out there on how to use it. Or at least, there weren't any.... until now!
The server is called bootpd and does both DHCP and BOOTP. These instructions just describe using it for DHCP, however.

To start, you need to create a configuration file for the server. The file should be stored in /etc/bootpd.plist. Here's a sample configuration file:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>bootp_enabled</key>
    <false/>
    <key>detect_other_dhcp_server</key>
    <integer>1</integer>
    <key>dhcp_enabled</key>
    <array>
        <string>en0</string>
    </array>
    <key>reply_threshold_seconds</key>
    <integer>0</integer>
    <key>Subnets</key>
    <array>
        <dict>
            <key>allocate</key>
            <true/>
            <key>lease_max</key>
            <integer>86400</integer>
            <key>lease_min</key>
            <integer>86400</integer>
            <key>name</key>
            <string>192.168.33</string>
            <key>net_address</key>
            <string>192.168.33.0</string>
            <key>net_mask</key>
            <string>255.255.255.0</string>
            <key>net_range</key>
            <array>
                <string>192.168.33.2</string>
                <string>192.168.33.254</string>
            </array>
        </dict>
    </array>
</dict>
</plist>

This file sets up the DHCP server to run on the interface named en0, which is typically the (non-wireless) Ethernet port. It assumes that that port has been configured with the IP address 192.168.33.1, and dishes out addresses from 192.168.33.2 to 192.168.33.254.
To get more information on editing this file, take a look at the bootpd manfile:

man bootpd

To start the server, run the following command:

sudo /bin/launchctl load -w /System/Library/LaunchDaemons/bootps.plist

Stopping the server is very similar:

sudo /bin/launchctl unload -w /System/Library/LaunchDaemons/bootps.plist

If you want to create static assignments, so that a given device always has the same IP address, you need to create a file called /etc/bootptab. There's a small sample of the file below. For more information, just do man bootptab

%%
# machine entries have the following format:
#
# hostname      hwtype  hwaddr              ipaddr          bootfile
client1         1       00:01:02:03:04:05   10.0.0.20
client2         1       00:a0:b2:ef:ff:0a   10.0.0.20

Make sure to include the %% at the top of the file. It's safe to leave the bootfile field empty because we're just using bootpd as a DHCP server, not a bootp server.

Create database Oracle form command

noreply@blogger.com (Unknown) — Thu, 16 Jan 2014 10:06:00 +0000

Step 1
export ORACLE_SID=orcl
export ORACLE_HOME=/path/to/oracle/home

Step 2
$ORACLE_HOME/dbs/init.ora

Step 3
control_files = (/u02/app/oracle/oradata/orcl/control1.ctl,/u02/app/oracle/oradata/orcl/control2.ctl,/u02/app/oracle/oradata/orcl/control3.ctl)
undo_management = AUTO
undo_tablespace = UNDOTBS1
db_name = orcl
db_block_size = 8192
sga_max_size = 11G
sga_target = 11G
Step4

$ORACLE_HOME/bin/orapwd file=$ORACLE_HOME/dbs/pwdorcl.ora password=abc123 entries=5

Chý ý: Cần khi emctl start dbconsole

orapwd FILE=orapw$ORACLE_SID ENTRIES=30

Step4

sqlplus / as sysdba
startup nomount

create database solieu
logfile group 1 ('/u02/app/oracle/oradata/solieu/redo1.log') size 500M,
group 2 ('/u02/app/oracle/oradata/solieu/redo2.log') size 500M,
group 3 ('/u02/app/oracle/oradata/solieu/redo3.log') size 500M
character set AL32UTF8
national character set utf8
datafile '/u01/oradata/solieu/system.dbf' size 500M autoextend on next 10M maxsize unlimited extent management local
sysaux datafile '/u01/oradata/solieu/sysaux.dbf' size 100M autoextend on next 10M maxsize unlimited
undo tablespace undotbs1 datafile '/u01/oradata/solieu/undotbs1.dbf' size 100M
default temporary tablespace temp tempfile '/u01/oradata/solieu/temp01.dbf' size 100M;

sql> @?/rdbms/admin/catalog.sqlsql> @?/rdbms/admin/catproc.sql

sql> alter user sys identified by sys115;sql> alter user system identified by sys115;

Fix dbconsole: emca -config dbcontrol db fails with grid control error

noreply@blogger.com (Unknown) — Thu, 16 Jan 2014 09:59:00 +0000

$ orapwd FILE=orapw$ORACLE_SID ENTRIES=30

sql > drop user sysman cascade;sql > drop user MGMT_VIEW cascade;sql > drop role MGMT_USER;sql > drop public synonym MGMT_TARGET_BLACKOUTS;sql > drop public synonym SETEMVIEWUSERCONTEXT;sql > drop public synonym MGMT_AVAILABILITY;sql > drop public synonym MGMT_CURRENT_AVAILABILITY;sql > emca -deconfig dbcontrol db -repos dropsql > emca -config dbcontrol db -repos create

First tried to start up dbconsole:

$ emctl start dbconsole
OC4J Configuration issue.
 /home/oracle/oracle1123/product/oc4j/j2ee/OC4J_DBConsole_perf234-target1.delphix.com_SOE60G 
#ff0000;">not found.

\OK, missing file. EM wasn’t configured for this database, make sense. Let’s configure it

$ emca -config dbcontrol db -repos create
...
#ff0000;">SEVERE: Dbcontrol Repository already exists.  
Fix the error(s) and run EM Configuration Assistant again in standalone mode.

Looks like there is already a repository, so lets configure EM with out making the repository

# emca -config dbcontrol db
#ff0000;">WARNING: ORA-00942: table or view does not exist
SEVERE: The existing database you have specified has Grid Control repository. 
This operation is not supported.

Hmm, what table is missing? Put db in sql trace mode to see what SQL statement ran into the 942 error

sqlplus / as sysdba
alter database set sql_trace=true
exit

rerun and grep for 942 in trace files in user_dump_dest

cd /home/oracle/oracle1123/diag/rdbms/soe60g/SOE60G/trace
grep 942 *

this show a dozen or so files.
Open each one up and searched for 942 and found two distinct SQL queries:

SELECT ATTRIBUTE,SCOPE,NUMERIC_VALUE,CHAR_VALUE,DATE_VALUE FROM #ff0000;">SYSTEM.PRODUCT_PRIVS
WHERE (UPPER('SQL*Plus') LIKE UPPER(PRODUCT)) AND (USER LIKE USERID)

select count(*) from #ff0000;">sysman.mgmt_versions where status > 0 and component_mode
like 'SYSAUX' and component_name in ('DB','CORE')

The first table is from not having run $ORACLE_HOME/sqlplus/admin/pupbld.sql
Second is the problem emca was running into. Let’s look at sysman’s objects and see what’s there.

sqlplus sysman/sys
select object_name from user_objects;
-> no rows returned

OK, sysman looks empty , let’s drop it and recreated it

sqlplus / as sysdba
drop user sysman cascade;
drop user MGMT_VIEW cascade;

someone’s blog had suggested dropping the following but I didn’t

# drop role MGMT_USER;
# drop public synonym MGMT_TARGET_BLACKOUTS;
# drop public synonym SETEMVIEWUSERCONTEXT;
#                                                        host      port  SID
# $ORACLE_HOME/sysman/admin/emdrep/bin/RepManager antarctic 2483 sprod -action drop
# ./emca -repos create

rerun emca

$ emca -config dbcontrol db -repos create
....
Do you wish to continue? [yes(Y)/no(N)]: y
Apr 20, 2013 7:27:51 AM oracle.sysman.emcp.EMConfig perform
INFO: This operation is being logged at 
/home/oracle/oracle1123/cfgtoollogs/emca/SOE60G/emca_2013_04_20_07_27_38.log.
Apr 20, 2013 7:27:51 AM oracle.sysman.emcp.ParamsManager checkListenerStatusForDBControl
#ff0000;">WARNING: ORA-01031: insufficient privileges
Apr 20, 2013 7:27:51 AM oracle.sysman.emcp.EMConfig perform
SEVERE:
Database connection through listener failed. Fix the error and run EM Configuration Assistant again.
Some of the possible reasons may be:
1) Listener port 1521 provided is incorrect. Provide the correct port.
2) Listener is not up. Start the Listener.
3) Database service SOE60G is not registered with listener. Register the database service.
4) Listener is up on physical host and ORACLE_HOSTNAME environment variable is set to
 virtual host. Unset ORACLE_HOSTNAME environment variable.
5) Listener is up on virtual host. Set environment variable ORACLE_HOSTNAME=.
6) /etc/hosts does not have correct entry for hostname.

Notice the ORA-01031. Hmm, I can connect as sqlplus / as sysdba but connecting as sysdba through the listener requires a password file. Let’s see if password files are set up

sqlplus / as sysdba
show parameters remote_login_passwordfile
remote_login_passwordfile            string      EXCLUSIVE

that’s set correct, but is there a password file?

cd $ORACLE_HOME/dbs
ls orapw$ORACLE_SID
ls: cannot access orapwdSOE60G: No such file or directory

not there, let’s create it

orapwd FILE=orapw$ORACLE_SID ENTRIES=30

now emca works !
Now what URL to I use to access OEM for the second database?
It’s the same URL as the first database but with different port. We can find the ports for each database in the following file

cat $ORACLE_HOME/install/portlist.ini
Enterprise Manager Console HTTP Port (o1123) = 1158
Enterprise Manager Agent Port #ff0000;">(o1123) = 3938
Enterprise Manager Console HTTP Port (SOE60G) = 5500
Enterprise Manager Agent Port #ff0000;">(SOE60G) = 1830

Post script
After the above steps, one of the bizarre things I ran into was being able to access OEM database page in Chrome but nothing else. Coming into OEM, I’m first asked for a login. I login as system, I see the database home page, then if I click on the performance tab, then I get prompted for the login again. I then login again, and I’m back at the database home page. No matter what tab I click, I end up back at the database home page after giving login credentials.
In Firefox, though once I login, I can go to any of the other tabs and it works!

PS when running emca above I was prompted for a number of variables. didn’t try this, but looks like all the arguments can be given in the command line

emca -repos create -silent -ORACLE_HOSTNAME perf234-target1 -SID SOE60G 
-SERVICE_NAME SOE60G -ORACLE_HOME /home/oracle/oracle1123/product
 -SYS_PWD sys -DBSNMP_PWD sys -SYSMAN_PWD sys 
-HOST_USER oracle -HOST_USER_PWD  -PORT 1521

Post Script II:
Never seen this one before and it was super annoying. I set up a VM in Virtual Box on my Mac with LINUX and Oracle 11.2.0.3 and OEM. On the VM I could access OEM but not from my Mac. On my Mac I kept getting

Configuring FreeNAS 8 for iSCSI on VMware vSphere 5 part 3

noreply@blogger.com (Unknown) — Tue, 26 Nov 2013 06:09:00 +0000

iSCSI stands for Internet SCSI and allows client machines to send SCSI commands to remote storage servers such as FreeNAS. This allows you to consolidate your storage drives into a single machine for lower cost per GB and easier maintenance, with the illusion of local disk drives on your client machines. The functionality to use iSCSI drives is built into both Windows Vista and Server 2008 natively. At the higher end you can also use iSCSI for low cost clustering solutions and disaster recovery.

In Part 1 of the tutorial we Installed and Configured FreeNAS Server on a VM.. in Part 2, We configured FreeNAS as a iSCSI..

In this Part, we are going to add the newly created iSCSI to an ESXi Server.

Once you have your ESXi ready, first thing to do is log on to it using VMware vSphere Client

Go to Configuration Tab -> "Storage adapters" and click "Add" to add a software iSCSI adapter if it does not exist already.

Click OK when prompted as shown below

You now will have to configure the iSCSI properties. to continue, click OK

You should see the newly added iSCSI Software Adapter as shown below. Click on Properties

You will first need to enable your iSCSI initiator. To do this, click “Configure” in the properties dialog.

In my case, it was already enabled.

On the next Tab (Dynamic Discovery), click on “Add” and enter the IP address of one of your iSCSI ports of your SAN.. in our case, the FreeNAS server IP was 192.168.2.155

the Static Discovery Tab should auto-populate if your FreeNAS Server (iSCSI) was configured properly. Click “Close” to quite the properties window.

Once this is done, vSphere will prompt you to rescan the iSCSI host for any new LUNS available, click “Yes”

Once the adapter is rescanned (Takes a couple of seconds), your LUN will be shown in the list view below.

Now, your SAN LUN is Added to ESXi. Only config left is to tell ESXi what to use the new storage for.
Click on “Storage” on the left menu in the “Hardware” section, where you will see it displays my current local datastore (datastore1) which is only the local hard drives. Click on “Add Storage”

In the Add Storage wizard first page, select “Disk/LUN” and click Next

Your Added LUN will be in the list, select it, and click “Next”

Select the File System Version..
NOTE: VMFS-5 does not support older ESXi versions i.e. any version older than 5 will not be supported.

Next will be a summary of your disk layout, click Next
(NOTE: If you get an error when this page loads, it will probably be because there is a SAN operation running on the LUN like Initialization, Syncing, capacity expansion, etc – all in all, if you get an error here, your LUN isn’t ready on the SAN)

Next enter a Name for the LUN (Just so you can identify it). I have named it as SHARED_DATASTORE

On the next page you will see the file formatting config, I left the defaults, and clicked Next

You will get a final summary page to confirm everything, click “Finish”

Once you have successfully finished the wizard, you will see your LUN storage ready in the storage list.

That's it from me for now..

Configuring FreeNAS 8 for iSCSI on VMware vSphere 5 part 2

noreply@blogger.com (Unknown) — Tue, 26 Nov 2013 06:08:00 +0000

iSCSI stands for Internet SCSI and allows client machines to send SCSI commands to remote storage servers such as FreeNAS. This allows you to consolidate your storage drives into a single machine for lower cost per GB and easier maintenance, with the illusion of local disk drives on your client machines. The functionality to use iSCSI drives is built into both Windows Vista and Server 2008 natively. At the higher end you can also use iSCSI for low cost clustering solutions and disaster recovery.

In the past this was usually done using special hardware and Fibre cabling, though with iSCSI you can leverage your existing network infrastructure. It should be noted that depending on the network load and performance requirements of your servers this can be drastically slower than the dedicated options. For a high performance production application you can still use iSCSI but I would look at setting it up on its own network at 1GB speeds.

How Does iSCSI Work?

There are two parts to the iSCSI protocol, the first being clients and the second being storage devices.

Clients are called iSCSI initiators and can be configured either using hardware or software solutions. As I mentioned earlier this functionality is already built into Vista and Server 2008, so we will not have to add any software/hardware to these machines.
The storage devices are called iSCSI targets and must be running some type of software/hardware to receive the incoming requests from the iSCSI initiators. Luckily FreeNAS has the ability to create iSCSI drives as part of its core package so I am going to use the FreeNAS server I used in a past demo.

Setup iSCSI Target Drive on FreeNAS Server

I’m going to use FreeNAS as the iSCSI target, and if you are going to follow along with this demo, it is imperative that you have one setup as well.
If you don’t you can read how to setup FreeNAS server and then come back to this article for the next steps.

This demo is going to assume that while the hard drives are installed in the server they are NOT added to the FreeNAS interface.

You must add the second hard disk (or partition) to use as iSCSI storage disk.
I have added one more virtual hard disk to my VMware Workstation virtual machine.

NOTE: You can follow these same steps for configuring a iSCSI in VMware vSphere Environments as well..

First, we will add a new HDD to the FreeNAS VM.

Open the Settings Wizard of the FreeNAS VM

In the "Add Hardware Wizard", select the Hard Disk and click Next

Select "Create New Virtual Disk" and click Next

Select "SCSI" and click Next

Provide the disk space for the new HDD. I have provide 20 GB.. You can use your imagination here !!

NOTE: The space that you provide here will be used as a iSCSI storage, so plan accordingly and provision.

Click FINISH when done

The best part of FreeNAS is that the newly added disk automatically shows up on the FreeNAS VM Console as shown below:

We now Create the volume as shown below:
Storage –> Volumes –> Create Volume

Select the disk you want to add to Volume pool. Provide a Volume Name (testvolume).. select ZFS as the filesystem type and when done, click Add Volume

You should see the new volume as shown below:

To configure iSCSI, go to Services –> iSCSI

If you like you can change the ‘Target Global Base Name’ under iSCSI settings. Otherwise, leave with existing example name. I changed as below (iqn.2011-03.test)

Add portal in next step. You can leave the default or provide the IPv4 address of FreeNAS virtual machine. In my case it is 192.168.2.155, so I can add 192.168.2.155:3260 in portal filed, but I left if with default 0 values.

Add the Authorized Initiator now.

You can go with default option ‘ALL’, if more security is required then insert the particular network in Authorized network, like 192.168.2.155/24

Now we need to create Targets, Extends and match them in Associated Targets.

NOTE: We have to repeat the same steps for each iSCSI disks we are going to create.

Create a target first:

Specify the target name (disk1), the TYPE (disk), the Target Flags (read-Write), Portal Group ID, Initiator ID

NOTE: If you have multiple HDDs, then do the same step again for second target

Add Extends now.

Provide a Extent Name (extent1)

‘Path to the extend’ filed should contain mounted storage name (Created earlier.. testvolume) with extended name. I have allocated 17 GB as below.

NOTE: Follow the same for the second extend if you are creating two iSCSI disks in FreeNAS

Go to ‘Associated Targets’ and match the targets and extends we have created earlier.

We are almost done, but the important part is still pending, which is enabling iSCSI service in FreeNAS 0.8, it was disabled by default.

Go to ‘Services’ and Click on OFF to make it ON in iSCSI.

Now your iSCSI storage disks in FreeNAS is ready to connect from other hosts

Configuring FreeNAS 8 for iSCSI on VMware vSphere 5 part 1

noreply@blogger.com (Unknown) — Tue, 26 Nov 2013 06:06:00 +0000

FreeNAS is a NAS (Network Attached Storage) server OS based on FreeBSD 8.0 supporting wide range of technologies. FreeNAS™ 8 features a ground up redesign of the web user interface.

No mess, no fuss – your server is easily controlled from any web-enabled device. Configuration is straightforward and simple, and you can make your changes on the fly. One of FreeNAS™ 8′s most important features is full support for the ZFS filesystem.

ZFS includes data integrity protection, practically unlimited size caps, cloneable snapshots, automatic repair, RAID-Z, and more. ZFS is fully open-source, and is a great way to store and manage your important files.

10Gig Ethernet drivers are included in FreeNAS™ 8. If you’ve got onboard 10GigE, or better yet, a 10GigE card, FreeNAS™ 8 becomes screamingly fast when transferring files. This is especially noticeable for video streaming, and multiple simultaneous connections.

If your data is somehow lost, FreeNAS™ makes it easy to restore from a previously generated snapshot. With the periodic snapshots feature, you can worry less about data loss, and use your system stress free. It takes far less time than a full backup, but a continuous set of snapshots will provide the same level of protection.

So lets get started..

Firstly, download the latest edition of FreeNAS from HERE

NOTE: For this tutorial I have used FreeNAS v8.0.4

Create a simple new virtual machine on VMware Workstation..

NOTE: You can follow the same installation steps for VMware vSphere Environments also.

in the "New Virtual Machine Wizard" Specify your “FreeNAS” ISO path in “Installer Disc Image file” & click next.

Select Operating System as “Other” & Version as “FreeBSD 64-bit” & click next.

Specify the disk size. You can give it a minimalistic HDD size. I gave it 5 GB. This is just going to be used for the installation of the OS.

I am going to add one hard disk for my FreeNAS Server in following steps for Additional storage & that will be used as a NFS storage.

Set minimum 256 MB, recommended is 512MB memory for VM.

Once done, Power ON the VM

You can go with default option 1. If you don't provide any options, it will automatically boot FreeNAS

Select the Install option in next screen.

FreeNAS 8 should be installed on any of the disks. As we only have a single disk (5 GB), we will install the OS on this HDD

Proceed with the installation as shown. This will basically format the disk for installing the OS.

Once installed, it will prompt you to REBOOT the VM

Select option 3 and hit OK

Once the reboot completes, you will be shown the URL to access the web console

Make sure VMware network is connected to virtual machine and it’s in any type of networks where host and guest can communicate. In our case, we have used a Bridged Network for the VM

Once you have logged in, FreeNAS will prompt you to change the Admin password by showing a ALERT in the top right hand corner of your browser as shown:

Click on My Account --> Change Admin Password

Provide the old password as "freenas" and a new one of your choice.

That’s the end of How to Install FreeNAS 8 on VMware.

FreeNAS is an ideal solution to make your old computer or virtual machine as storage for production and testing environment -

Bảo mật dữ liệu cho website PHP sử dụng Share host linux

noreply@blogger.com (Unknown) — Fri, 18 Oct 2013 04:07:00 +0000

Ngày nay các ứng dụng web với mã nguồn mở phát triển rất mạnh, trong đó đặc biệt phổ biến là PHP – MySQL. Nhưng công nghệ phát triển đồng thời kéo theo những “tin tặc” trẻ luôn muốn khẳng định mình sau khi xem những hướng dẫn tấn công, khai thác lỗi đầy rẫy trên các forum hacker.

Bất kì một website nào cũng có khả năng bị tấn công bất cứ lúc nào, đặc biệt là các site cá nhân, tập thể vừa và nhỏ sẽ chọn giải pháp là thuê shared hosting trên một server. Vì các shared hosting ở cùng server nên độ riêng tư không cao, việc kiên cố hoá website trên shared hosting là rất cần thiết.

1. Phân quyền hợp lí

A. Tìm hiểu về chmod:
Là sự phân quyền truy cập vào một file hay một folder đối với các lớp người dùng giống như các thuộc tính dùng lệnh attrib trong DOS.
+ Các lớp người dùng gồm có: Owner – Group – World

- Owner : người “sở hữu” host.
- Group : là nhóm người dùng.
- World : bất kì ai.

+ Các quyền khi chmod:

- Read : đọc (r = 4)
- Write : ghi (w = 2)
- Execute : thực thi (x = 1)

VD: chmod 751 = rwxr-x–x
+ Cách chmod: xem thêm chmod
B. CHMOD thế nào để an toàn:
Cách CHMOD tối ưu nhất :
- chmod 404 (chỉ cho phép đọc) tất cả các file.
- chmod 101 (chỉ cho thực thi) tất cả các folder.
- chmod 501 thư mục /public_html/
Các cách chmod trên đều không cho write, do đó bố cục được bảo toàn, đồng thời không thể xem cấu trúc site, thư mục, file. Có thể nói đó là các chmod an toàn nhất mà ứng dụng web như diễn đàn, site nhạc, tin tức có thể hoạt động ổn định. Tuy nhiên không phải server nào cũng cho phép bạn chmod như vậy, nếu bạn dùng FTP không thể chmod được như vậy, thì hãy chmod như sau:
- chmod 704 (chỉ cho phép đọc) tất cả các file.
- chmod 701 (chỉ cho thực thi) tất cả các folder.
Lưu ý: Phiên bản cPanel 11 có File Manager V3, có thể dùng để chmod hàng loạt rất tốt và có thể chmod được file 404, folder 101.
Cách CHMOD cho tệp tin (file) và thư mục (folder/directory)

2. “Ẩn mình” – Hide path

Khi đăng kí hosting, domain chính thường được trỏ vào ngay trong thư mục /public_html/, điều này giúp “kẻ tấn công” dễ dàng mò đến file quan trọng của website (vd như file config.php của các forum chẳng hạn), và khi đó thông tin đăng nhập quản lí cơ sở dữ liệu của website đã bị kẻ xấu lấy mất. Điều tệ hại gì sẽ xảy ra ?
Để khắc phục điểm này, ta nên yêu cầu bên cung cấp hosting tạo host không có domain (tên miền) chính và để ta tự gắn vào bằng chức năng add-on domain. Khi add domain sẽ có chỗ để bạn nhập đường dẫn đến thư mục mà domain sau khi gắn thành công sẽ trỏ vào như hình:
VD: /public_html/foder1/folder2/folder3/forum/
Sau khi bạn bấm add các thư mục folder1, folder2, …, forum sẽ được tự động tạo ra. Và bây giờ bạn áp dụng cách chmod ở trên để chmod các thư mục folder1, folder2 … để giấu đường dẫn của site trên server.

3. Không hiển thị lỗi nếu phát sinh

Khi có lỗi phát sinh, PHP sẽ hiện thông báo ra trình duyệt và chỉ rõ lỗi ở file nào, dòng nào và đường dẫn của file, vì thế điều này rất nguy hiểm. Để che lỗi, bạn tạo một file php.ini với nội dung như sau:

display_errors = Off
log_errors = On

Sau đó upload lên thư mục chứa website. Gợi ý: bạn nên up file php.ini trên vào các thư mục mà người dùng sẽ truy cập bằng trình duyệt, thường là thư mục chứa website, thư mục quản trị, thư mục của user …

4. Bật safe-mode (chế độ an toàn) và vô hiệu các hàm nguy hiểm

Thêm hoặc edit 2 dòng sau trong nội dung file php.ini
disable_functions = passthru, system, shell_exec, exec, dir, readfile, virtual,proc_terminate
safe-mode = on
Lưu ý: bạn có thể bỏ bớt các hàm trong danh sách hàm bị vô hiệu nếu hàm đó cần cho website của bạn hoạt động.

5. Phân quyền account truy cập cơ sở dữ liệu MySQL

Khi bạn tạo user truy cập vào database, bạn cần lưu ý:

- Không dùng user và pass của host làm user của database.
- Không cấp quyền DROP như hình.

6. Tránh chmod 777 cho folder/file

Đôi khi bạn gặp một số yêu cầu chmod 777 cho file/folder để thực hiện công việc gì đó, bạn hãy chú ý chmod lại sau khi công việc đã được thực hiện xong.

7. Mã hoá các file chứa thông tin nhạy cảm

Các file nhạy cảm chứa các thông tin kết nối cơ sở dữ liệu như config.php với các kiểu mã hoá như base64 của PHP hoặc mã hoá dùng phần mềm zendguard của www.zend.com. Nếu mã hoá base64 PHP thì các bạn có thể dùng google để tìm với từ khoá “base64 encode”. Mình xin giới thiệu một link để các bạn mã hoá base64 file php: http://dnstools.it-4vn.com/phpencode.php

8. Ngăn download source code khi server gặp sự cố:

Tạo file .htaccess nội dung như sau:

Order Allow,Deny
Deny from All

Ví dụ:

Order Allow,Deny
Deny from All

Mục đích để ngăn cản việc download source code khi PHP bị overload hoặc terminated. Nguyên nhân có thể đến từ bên trong hoặc bên ngoài. Tôi không đề cập ở đây.

9. Vô hiệu hoá biên dịch mã PHP trong thư mục chỉ định

Nếu bạn có một thư mục dành cho việc upload, bạn nên vô hiệu hoá việc biên dịch và thực thi mã PHP trong thư mục ấy vì attacker có thể lợi dụng việc upload để đưa script độc (webshell) lên host của bạn. Tạo file .htaccess đặt vào thư mục đó với nội dung như sau:
php_admin_flag engine off
Sau đó chmod 444 cho file.

10. Thường xuyên cập nhật vá lỗi cho website và đặt một mật khẩu quản trị tương đối kiên cố, liên hệ với nhà cung cấp dịch vụ để sửa lỗi.

Lưu ý cuối cùng:
- File php.ini mình đề cập ở trên chỉ có tác dụng tại thư mục chứa nó, các thư mục không chứa nó sẽ không bị nó chi phối mà sẽ bị cấu hình trong php.ini của server chi phối.
- Các file php.ini và .htaccess nên chmod 444 để bảo vệ cấu hình.

Download YouTube videos with youtube-dl

noreply@blogger.com (Unknown) — Sat, 04 May 2013 03:35:00 +0000

Install & using

1. install youtube-dl

sudo apt-get update && sudo apt-get install youtube-dl

2. use this command to download files from YouTube

youtube-dl -o [name of output file] [YouTube URL]

3. To view all options youtube-dl, paste this in command line

man youtube-dl

To quit from manual press q key

Examples

1. Download classic flv type and save it as file.flv

youtube-dl -o file.flv "http://www.youtube.com/watch?v=Y54ABqSOScQ"

2. Download Full HD mp4 file and save it as file.mp4

youtube-dl -o file.mp4 -f 37 "http://www.youtube.com/watch?v=Y54ABqSOScQ"

This table from Wikipedia may be useful

Comparison of YouTube media types

Installing FFMPEG on CentOS with ATRPMS repo

noreply@blogger.com (Unknown) — Sat, 04 May 2013 03:05:00 +0000

Import Key

rpm --import http://packages.atrpms.net/RPM-GPG-KEY.atrpms

Create repo file

vim /etc/yum.repos.d/atrpms.repo

[atrpms]
name=Fedora Core $releasever - $basearch - ATrpms
baseurl=http://dl.atrpms.net/el$releasever-$basearch/atrpms/stable
gpgkey=http://ATrpms.net/RPM-GPG-KEY.atrpms
gpgcheck=1
enabled=0

[atrpms-testing]
name=Fedora Core $releasever - $basearch - ATrpms
baseurl=http://dl.atrpms.net/el$releasever-$basearch/atrpms/testing
gpgkey=http://ATrpms.net/RPM-GPG-KEY.atrpms
gpgcheck=1
enabled=0

Install from Atrpms (example output)

[root@computer ~]# yum --enablerepo=atrpms* install ffmpeg

Loaded

NGINX location priority rules

noreply@blogger.com (Unknown) — Thu, 02 May 2013 08:31:00 +0000

NGINX is great. Fast, efficient, etc. But the “location” rules are a bit cryptic and not very well explained in the manuals.

There are 4 types of location rule, and are applied with the following priorities:

1: Exact matches
There can be only one exact match – the clue is in the name!

location = /foo/bar {
# exact match
}

2: High priority prefix
There can be more than one match, the longest one takes priority

location ^~ /foo {
# request beginning with /foo
}

3: Regex
There can be more than one match, the first one found takes priority. There are two variants
location ~ .foo$ {
# case-sensitive regex
}
location ~* .foo$ {
# case-insensitive regex
}
4: Low priority prefix
There can be more than one match, the longest one takes priority

location /foo {
# request beginning with /foo
}