Oracle Technologies Blog

By ASKM

Archive for the ‘VMWARE’ Category

Installing 11gR2 Single Instance Database With Non-ASM Storage

Posted by Srikrishna Murthy Annam on December 17, 2010

The present demo shows you how to install 11gR2 single instance database with Non-ASM storage.
Following sequence is followed ..

  1. Install Linux 5.x on VMware server linux machine
  2. Prepare Linux Machine for 11gR2 software installation
  3. Install 11gR2 software
  4. Create 11gR2 database with Non-ASM storage

1. Install Linux 5.x on VMware server linux machine

Follow the demo  VMware Server – Linux installation and complete the linux installation.

2. Prepare Linux Machine for 11gR2 software installation

Follow the article  Prepare Linux virtual machine for 11gR2 installation on Linux 5.x and prepare Linux OS for 11gR2 Database Installation.

3. Install 11gR2 software

Follow the following demo and install 11gR2 software.

4. Create 11gR2 database with Non-ASM storage

Follow the following demo to create 11gR2 database with Non-ASM storage.

Now you installed 11gR2 database successfully.

Hope it helps

SRI


Add to FaceBookAdd to TwitterAdd to Google BookmarkAdd to MySpaceAdd to DiggAdd to DeliciousAdd to NewsvineAdd to RedditAdd to StumbleUponAdd to Technorati

<iframe src=”http://www.facebook.com/plugins/like.php?href=http%3A%2F%2Flearnwithme11g.wordpress.com&amp;layout=standard&amp;show_faces=true&amp;width=450&amp;action=like&amp;font=arial&amp;colorscheme=light&amp;height=80&#8243; scrolling=”no” frameborder=”0″ style=”border:none; overflow:hidden; width:450px; height:80px;” allowTransparency=”true”></iframe>

Posted in Database Articles, VMWARE | Tagged: , , , , | 2 Comments »

How to add more disk space to Linux Virtual Machine

Posted by Srikrishna Murthy Annam on September 15, 2010

The present demo shows how to add more disk space to linux virtual machine. If you are creating Linux virtual machines for testing purpose , obviously you will create with less disk space. If there is any requirement to add more disk space to linux virtual machine, just follow the steps in the demo and add more disk space to linux virtual machine.

[root@dhcppc1 ~]# fdisk -l

Disk /dev/sda: 8589 MB, 8589934592 bytes
255 heads, 63 sectors/track, 1044 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        1044     8281507+  8e  Linux LVM

Disk /dev/sdb: 8589 MB, 8589934592 bytes
255 heads, 63 sectors/track, 1044 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/sdb doesn’t contain a valid partition table
[root@dhcppc1 ~]# fdisk /dev/sdb
Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel
Building a new DOS disklabel. Changes will remain in memory only,
until you decide to write them. After that, of course, the previous
content won’t be recoverable.

The number of cylinders for this disk is set to 1044.
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)
Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)

Command (m for help): p

Disk /dev/sdb: 8589 MB, 8589934592 bytes
255 heads, 63 sectors/track, 1044 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot      Start         End      Blocks   Id  System

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

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

Calling ioctl() to re-read partition table.
Syncing disks.
[root@dhcppc1 ~]# fdisk -l

Disk /dev/sda: 8589 MB, 8589934592 bytes
255 heads, 63 sectors/track, 1044 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        1044     8281507+  8e  Linux LVM

Disk /dev/sdb: 8589 MB, 8589934592 bytes
255 heads, 63 sectors/track, 1044 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1        1044     8385898+  83  Linux
[root@dhcppc1 ~]# mkfs -t ext3 /dev/sdb1
mke2fs 1.39 (29-May-2006)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
1048576 inodes, 2096474 blocks
104823 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=2147483648
64 block groups
32768 blocks per group, 32768 fragments per group
16384 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632

Writing inode tables: done
Creating journal (32768 blocks):

done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 33 mounts or
180 days, whichever comes first.  Use tune2fs -c or -i to override.
[root@dhcppc1 ~]#
[root@dhcppc1 ~]#
[root@dhcppc1 ~]# mkdir /u01
[root@dhcppc1 ~]# chmod 777 /u01
[root@dhcppc1 ~]# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
3.9G  3.1G  657M  83% /
/dev/sda1              99M   20M   75M  21% /boot
tmpfs                 864M     0  864M   0% /dev/shm
none                  864M  104K  864M   1% /var/lib/xenstored
[root@dhcppc1 ~]# mount /dev/sdb1 /u01
[root@dhcppc1 ~]# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
3.9G  3.1G  657M  83% /
/dev/sda1              99M   20M   75M  21% /boot
tmpfs                 864M     0  864M   0% /dev/shm
none                  864M  104K  864M   1% /var/lib/xenstored
/dev/sdb1             7.9G  147M  7.4G   2% /u01
[root@dhcppc1 ~]# vi /etc/fstab
[root@dhcppc1 ~]# grep -i “/dev/sdb1” /etc/fstab
/dev/sdb1               /u01                    ext3    defaults        0  0
[root@dhcppc1 ~]#

Hope it helps

SRI

Posted in Linux, VMWARE | Tagged: , , , , , , , | Leave a Comment »

Installing VMware tools

Posted by Srikrishna Murthy Annam on September 14, 2010

When you are working with VMware linux machine, you may feel some difficulty with the cursor movement. When you move your cursor to the vmware linux machine, it takes the control of the cursor and you cant move your cursor outside the vmware linux machive. To release the cursor , you have to press CTRL+ALT. Then Vmware linux machine releases the cursor to Host operating system.

It also enhances the graphical appearance of the vmware virtual linux machine.

There are two ways , we can install VMware tools. One way is to use VMwaretools.tar.gz file and another way is to install VMwaretools.rpm and then running mware-config-tools.pl  file to install VMware tools.

Pls follow the demo to install VMware tools using xxx.tar.gz file.

The following session log shows how to install rpm and then run the mware-config-tools.pl file to install VMware tools.

[root@localhost rpms]# rpm -ivh VMwareTools-7.7.6-203138.i386.rpm
Preparing…                ########################################### [100%]
1:VMwareTools            ########################################### [100%]

The installation of VMware Tools 7.7.6 for Linux completed successfully.
You can decide to remove this software from your system at any time by
invoking the following command: “rpm -e VMwareTools”.

Before running VMware Tools for the first time, you need to
configure it for your running kernel by invoking the
following command: “/usr/bin/vmware-config-tools.pl”.

Enjoy,

–the VMware team

[root@localhost rpms]#

[root@localhost rpms]# /usr/bin/vmware-config-tools.pl

Stopping VMware Tools services in the virtual machine:
Guest operating system daemon:[  OK  ]

None of the pre-built vmmemctl modules for VMware Tools is suitable for your
running kernel.  Do you want this program to try to build the vmmemctl module
for your system (you need to have a C compiler installed on your system)?
[yes]

Using compiler “/usr/bin/gcc”. Use environment variable CC to override.

What is the location of the directory of C header files that match your running
kernel? [/lib/modules/2.6.18-164.el5xen/build/include]

Extracting the sources of the vmmemctl module.

Building the vmmemctl module.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vmmemctl-only’
make -C /lib/modules/2.6.18-164.el5xen/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/kernels/2.6.18-164.el5-xen-i686′
CC [M]  /tmp/vmware-config0/vmmemctl-only/backdoorGcc32.o
CC [M]  /tmp/vmware-config0/vmmemctl-only/os.o
CC [M]  /tmp/vmware-config0/vmmemctl-only/vmballoon.o
LD [M]  /tmp/vmware-config0/vmmemctl-only/vmmemctl.o
Building modules, stage 2.
MODPOST
CC      /tmp/vmware-config0/vmmemctl-only/vmmemctl.mod.o
LD [M]  /tmp/vmware-config0/vmmemctl-only/vmmemctl.ko
make[1]: Leaving directory `/usr/src/kernels/2.6.18-164.el5-xen-i686′
cp -f vmmemctl.ko ./../vmmemctl.o
make: Leaving directory `/tmp/vmware-config0/vmmemctl-only’
The vmmemctl module loads perfectly into the running kernel.

None of the pre-built vmhgfs modules for VMware Tools is suitable for your
running kernel.  Do you want this program to try to build the vmhgfs module for
your system (you need to have a C compiler installed on your system)? [yes]

Extracting the sources of the vmhgfs module.

Building the vmhgfs module.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vmhgfs-only’
make -C /lib/modules/2.6.18-164.el5xen/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/kernels/2.6.18-164.el5-xen-i686′
CC [M]  /tmp/vmware-config0/vmhgfs-only/backdoor.o
CC [M]  /tmp/vmware-config0/vmhgfs-only/backdoorGcc32.o
CC [M]  /tmp/vmware-config0/vmhgfs-only/bdhandler.o
CC [M]  /tmp/vmware-config0/vmhgfs-only/cpName.o
CC [M]  /tmp/vmware-config0/vmhgfs-only/cpNameLinux.o
CC [M]  /tmp/vmware-config0/vmhgfs-only/cpNameLite.o
CC [M]  /tmp/vmware-config0/vmhgfs-only/dentry.o
CC [M]  /tmp/vmware-config0/vmhgfs-only/dir.o
CC [M]  /tmp/vmware-config0/vmhgfs-only/file.o
CC [M]  /tmp/vmware-config0/vmhgfs-only/filesystem.o
CC [M]  /tmp/vmware-config0/vmhgfs-only/fsutil.o
CC [M]  /tmp/vmware-config0/vmhgfs-only/hgfsBd.o
CC [M]  /tmp/vmware-config0/vmhgfs-only/hgfsEscapeLinux.o
CC [M]  /tmp/vmware-config0/vmhgfs-only/hgfsUtil.o
CC [M]  /tmp/vmware-config0/vmhgfs-only/inode.o
CC [M]  /tmp/vmware-config0/vmhgfs-only/kernelStubsLinux.o
CC [M]  /tmp/vmware-config0/vmhgfs-only/link.o
CC [M]  /tmp/vmware-config0/vmhgfs-only/messageBackdoor.o
CC [M]  /tmp/vmware-config0/vmhgfs-only/message.o
CC [M]  /tmp/vmware-config0/vmhgfs-only/module.o
CC [M]  /tmp/vmware-config0/vmhgfs-only/page.o
CC [M]  /tmp/vmware-config0/vmhgfs-only/request.o
CC [M]  /tmp/vmware-config0/vmhgfs-only/rpcout.o
CC [M]  /tmp/vmware-config0/vmhgfs-only/staticEscape.o
CC [M]  /tmp/vmware-config0/vmhgfs-only/stubs.o
CC [M]  /tmp/vmware-config0/vmhgfs-only/super.o
LD [M]  /tmp/vmware-config0/vmhgfs-only/vmhgfs.o
Building modules, stage 2.
MODPOST
CC      /tmp/vmware-config0/vmhgfs-only/vmhgfs.mod.o
LD [M]  /tmp/vmware-config0/vmhgfs-only/vmhgfs.ko
make[1]: Leaving directory `/usr/src/kernels/2.6.18-164.el5-xen-i686′
cp -f vmhgfs.ko ./../vmhgfs.o
make: Leaving directory `/tmp/vmware-config0/vmhgfs-only’
The vmhgfs module loads perfectly into the running kernel.

None of the pre-built vmxnet modules for VMware Tools is suitable for your
running kernel.  Do you want this program to try to build the vmxnet module for
your system (you need to have a C compiler installed on your system)? [yes]

Extracting the sources of the vmxnet module.

Building the vmxnet module.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vmxnet-only’
make -C /lib/modules/2.6.18-164.el5xen/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/kernels/2.6.18-164.el5-xen-i686′
CC [M]  /tmp/vmware-config0/vmxnet-only/vmxnet.o
In file included from /tmp/vmware-config0/vmxnet-only/vmxnet.c:39:
/tmp/vmware-config0/vmxnet-only/compat_netdevice.h:273: error: redefinition of ‘struct napi_struct’
/tmp/vmware-config0/vmxnet-only/vmxnet.c: In function ‘vmxnet_probe_device’:
/tmp/vmware-config0/vmxnet-only/vmxnet.c:993: warning: cast to pointer from integer of different size
make[2]: *** [/tmp/vmware-config0/vmxnet-only/vmxnet.o] Error 1
make[1]: *** [_module_/tmp/vmware-config0/vmxnet-only] Error 2
make[1]: Leaving directory `/usr/src/kernels/2.6.18-164.el5-xen-i686′
make: *** [vmxnet.ko] Error 2
make: Leaving directory `/tmp/vmware-config0/vmxnet-only’
Unable to build the vmxnet module.

The fast network device driver (vmxnet module) is used only for our fast
networking interface. The rest of the software provided by VMware Tools is
designed to work independently of this feature.
If you wish to have the fast network driver enabled, you can install the driver
by running vmware-config-tools.pl again after making sure that gcc, binutils,
make and the kernel sources for your running kernel are installed on your
machine. These packages are available on your distribution’s installation CD.
[ Press Enter key to continue ]

None of the pre-built vmblock modules for VMware Tools is suitable for your
running kernel.  Do you want this program to try to build the vmblock module
for your system (you need to have a C compiler installed on your system)?
[yes]

Extracting the sources of the vmblock module.

Building the vmblock module.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config1/vmblock-only’
make -C /lib/modules/2.6.18-164.el5xen/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/kernels/2.6.18-164.el5-xen-i686′
CC [M]  /tmp/vmware-config1/vmblock-only/linux/block.o
CC [M]  /tmp/vmware-config1/vmblock-only/linux/control.o
CC [M]  /tmp/vmware-config1/vmblock-only/linux/dbllnklst.o
CC [M]  /tmp/vmware-config1/vmblock-only/linux/dentry.o
CC [M]  /tmp/vmware-config1/vmblock-only/linux/file.o
CC [M]  /tmp/vmware-config1/vmblock-only/linux/filesystem.o
CC [M]  /tmp/vmware-config1/vmblock-only/linux/inode.o
CC [M]  /tmp/vmware-config1/vmblock-only/linux/module.o
CC [M]  /tmp/vmware-config1/vmblock-only/linux/stubs.o
CC [M]  /tmp/vmware-config1/vmblock-only/linux/super.o
LD [M]  /tmp/vmware-config1/vmblock-only/vmblock.o
Building modules, stage 2.
MODPOST
CC      /tmp/vmware-config1/vmblock-only/vmblock.mod.o
LD [M]  /tmp/vmware-config1/vmblock-only/vmblock.ko
make[1]: Leaving directory `/usr/src/kernels/2.6.18-164.el5-xen-i686′
cp -f vmblock.ko ./../vmblock.o
make: Leaving directory `/tmp/vmware-config1/vmblock-only’
The vmblock module loads perfectly into the running kernel.

[EXPERIMENTAL] The VMware FileSystem Sync Driver (vmsync) is a new feature that
creates backups of virtual machines. Please refer to the VMware Knowledge Base
for more details on this capability. Do you wish to enable this feature?
[no]

None of the pre-built vmci modules for VMware Tools is suitable for your
running kernel.  Do you want this program to try to build the vmci module for
your system (you need to have a C compiler installed on your system)? [yes]

Extracting the sources of the vmci module.

Building the vmci module.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config1/vmci-only’
make -C /lib/modules/2.6.18-164.el5xen/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/kernels/2.6.18-164.el5-xen-i686′
CC [M]  /tmp/vmware-config1/vmci-only/kernelStubsLinux.o
CC [M]  /tmp/vmware-config1/vmci-only/vmciDatagram.o
CC [M]  /tmp/vmware-config1/vmci-only/vmci_drv.o
CC [M]  /tmp/vmware-config1/vmci-only/vmciEvent.o
CC [M]  /tmp/vmware-config1/vmci-only/vmciGuestDs.o
CC [M]  /tmp/vmware-config1/vmci-only/vmciGuestKernelIf.o
CC [M]  /tmp/vmware-config1/vmci-only/vmciKernelIf.o
CC [M]  /tmp/vmware-config1/vmci-only/vmciProcess.o
CC [M]  /tmp/vmware-config1/vmci-only/vmciQueuePair.o
CC [M]  /tmp/vmware-config1/vmci-only/vmciUtil.o
LD [M]  /tmp/vmware-config1/vmci-only/vmci.o
Building modules, stage 2.
MODPOST
CC      /tmp/vmware-config1/vmci-only/vmci.mod.o
LD [M]  /tmp/vmware-config1/vmci-only/vmci.ko
make[1]: Leaving directory `/usr/src/kernels/2.6.18-164.el5-xen-i686′
cp -f vmci.ko ./../vmci.o
make: Leaving directory `/tmp/vmware-config1/vmci-only’
The vmci module loads perfectly into the running kernel.

None of the pre-built vsock modules for VMware Tools is suitable for your
running kernel.  Do you want this program to try to build the vsock module for
your system (you need to have a C compiler installed on your system)? [yes]

Extracting the sources of the vsock module.

Building the vsock module.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config1/vsock-only’
make -C /lib/modules/2.6.18-164.el5xen/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/kernels/2.6.18-164.el5-xen-i686′
CC [M]  /tmp/vmware-config1/vsock-only/linux/af_vsock.o
CC [M]  /tmp/vmware-config1/vsock-only/linux/driverLog.o
CC [M]  /tmp/vmware-config1/vsock-only/linux/util.o
CC [M]  /tmp/vmware-config1/vsock-only/linux/vsockAddr.o
LD [M]  /tmp/vmware-config1/vsock-only/vsock.o
Building modules, stage 2.
MODPOST
WARNING: “VMCIDatagram_CreateHnd” [/tmp/vmware-config1/vsock-only/vsock.ko] undefined!
WARNING: “VMCIDatagram_DestroyHnd” [/tmp/vmware-config1/vsock-only/vsock.ko] undefined!
WARNING: “VMCIEvent_Subscribe” [/tmp/vmware-config1/vsock-only/vsock.ko] undefined!
WARNING: “VMCI_DeviceGet” [/tmp/vmware-config1/vsock-only/vsock.ko] undefined!
WARNING: “VMCIMemcpyFromQueueV” [/tmp/vmware-config1/vsock-only/vsock.ko] undefined!
WARNING: “VMCIQueuePair_Detach” [/tmp/vmware-config1/vsock-only/vsock.ko] undefined!
WARNING: “VMCI_GetContextID” [/tmp/vmware-config1/vsock-only/vsock.ko] undefined!
WARNING: “VMCIDatagram_Send” [/tmp/vmware-config1/vsock-only/vsock.ko] undefined!
WARNING: “VMCIQueuePair_Alloc” [/tmp/vmware-config1/vsock-only/vsock.ko] undefined!
WARNING: “VMCIEvent_Unsubscribe” [/tmp/vmware-config1/vsock-only/vsock.ko] undefined!
WARNING: “VMCIMemcpyToQueueV” [/tmp/vmware-config1/vsock-only/vsock.ko] undefined!
CC      /tmp/vmware-config1/vsock-only/vsock.mod.o
LD [M]  /tmp/vmware-config1/vsock-only/vsock.ko
make[1]: Leaving directory `/usr/src/kernels/2.6.18-164.el5-xen-i686′
cp -f vsock.ko ./../vsock.o
make: Leaving directory `/tmp/vmware-config1/vsock-only’
The vsock module loads perfectly into the running kernel.

Detected X.org version 7.1.

Please choose one of the following display sizes that X will start with (1 –
29):

[1]  “320×200”
[2]  “320×240”
[3]  “400×300”
[4]  “512×384”
[5]  “640×400”
[6]  “640×480”
[7]  “720×480”
[8]  “800×480”
[9]  “854×480”
[10]  “720×576”
[11]  “800×600”
[12]  “1024×768”
[13]  “1280×720”
[14]  “1280×768”
[15]  “1152×864”
[16]  “1280×800”
[17]  “1366×768”
[18]  “1280×960”
[19]  “1440×900”
[20]  “1280×1024”
[21]  “1400×1050”
[22]  “1680×1050”
[23]  “1600×1200”
[24]  “1920×1080”
[25]  “1920×1200”
[26]  “1920×1440”
[27]  “2048×1536”
[28]  “2560×1600”
[29]  “2560×1920”
Please enter a number between 1 and 29:

[3]

X Window System Version 7.1.1
Release Date: 12 May 2006
X Protocol Version 11, Revision 0, Release 7.1.

Then reboot the machine once.

Hope it helps

SRI

Posted in VMWARE | Tagged: , , , , , , | 1 Comment »

Accessing Linux Virtual Machine outside VMware

Posted by Srikrishna Murthy Annam on September 14, 2010

You created a virtual machine in VMware server and if you want to access this virtual machine outside the VMware(ie host Operating system), Pls configure network settings as shown in the demo.

Hope it helps

SRI

Posted in VMWARE | Tagged: , , , , | 2 Comments »

VMware Server – Linux installation

Posted by Srikrishna Murthy Annam on September 12, 2010

Linux installation on vmware server  Part 1

Linux installation on vmware server part 2

Posted in Linux, VMWARE | Tagged: , , , | 2 Comments »

 
%d bloggers like this: