Oracle 11g Installation Error

Issue: 
1. Even if all the oracle software installation pre requisites are met and the DISPLAY variable is set correctly, when running the runInstaller it is throwing error. 

2. When Starting the Listener there is ERROR Linux Error: 29: Illegal seek

Environment Details:
OS: Linux Server 5.8 64bit
Database Version: 11gR2
User: oracle
Software Location: /u01/stage/database

[oracle@linux01 ~]$ cd /u01/stage/database/
[oracle@linux01 database]$ ./runInstaller
Starting Oracle Universal Installer...
Checking Temp space: must be greater than 120 MB.   Actual 132493 MB    Passed
Checking swap space: must be greater than 150 MB.   Actual 22159 MB    Passed
Checking monitor: must be configured to display at least 256 colors.    Actual 65536    Passed
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2013-07-13_09-24-35AM. Please wait ...[oracle@linux01 database]$ #
# An unexpected error has been detected by HotSpot Virtual Machine:
#
#  SIGILL (0x4) at pc=0x00000031d8614be0, pid=12186, tid=140422856902346
#
# Java VM: Java HotSpot(TM) 64-Bit Server VM (1.5.0_30-b03 mixed mode)
# Problematic frame:
# C  [ld-linux-x86-64.so.2+0x14be0]
#
# An error report file with more information is saved as hs_err_pid12186.log
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
#


[oracle@linux01 ~]$ lsnrctl start

LSNRCTL for Linux: Version 11.2.0.3.0 - Production on 13-JUL-2013 10:34:58

Copyright (c) 1991, 2011, Oracle.  All rights reserved.

Starting /u01/app/oracle/product/11.2.0/xe/bin/tnslsnr: please wait...

TNS-12537: TNS:connection closed
 TNS-12560: TNS:protocol adapter error
  TNS-00507: Connection closed

   Linux Error: 29: Illegal seek

Resolution: set the environment variable LD_BIND_NOW to 1 and then invoke the installer, it will go through. Setting the LD_BIND_NOW force the loader to do the Procedure Linkage Table fixups 

[oracle@linux01 database]$ export LD_BIND_NOW=1
[oracle@linux01 database]$ ./runInstaller

Weblogic Installation

Simple Weblogic Installation

Environment Details:
OS: Linux Server 5.8 64bit
Version: Weblogic Server 10.3.6
Installation location: /u01/app/oracle/product/fmw
User: oraem(We can have any user)

Steps to be executed as oraem user:

Step 1: First install 64 bit java of the desired version, here in our installation we are using Java 6u32 64 bit

execute the command ./jdk-6u32-linux-x64.bin, it will install the java in the particular directory 

Step 2: Invoke the command java -jar -d64 wls1036_generic.jar (here -d64 option installs 64bit version of weblogic)

Step 3: Click Next on the "Welcome Screen"

Step 4: Give the complete location where we are going to install the weblogic server and click Next

Step 5: In these screen the installer asks for the Oracle Support username password, which can be skipped by un checking the box and confirming to remained uninformed of critical issues by clicking Yes. Then click Next

Step 6: Click Custom and click Next

Step 7: This screen shows what all components we are going to install. Click Next

Step 8: Select the Java Home which we installed and uncheck the other java which was mentioned, and click Next

Step 9: Choose the Product Installation Directory, we can keep them as default and click Next

Step 10: Review the Installation Summary and click Next

Step 11: Installation Progress Screen

Step 12: The installation is over, uncheck the Run Quickstart box and click Done.

Note: After the installation is over the base domain can be created by invoking the config.sh script from location /u01/app/oracle/product/fmw/wlserver_10.3/common/bin.

Installation Issues/Error:

1. Sometime if there is a space issue on the server we may get the below mentioned error 

Fatal error encountered during self-extraction.[No space left on device]

To Resolve this we need to find a mount point where there is space available and then use the -Djava.io.tmpdiroption while doing the installation

[oraem@Linux1 stage]$ java -d64 -Djava.io.tmpdir=/u03/stage/temp -jar wls1036_generic.jar

2. In windows machine the -d64 option doesn't work and we may get the error: Could not create the Java virtual machine.

Simply invoke the installer by omitting that option(-d64)