Oracle installation

[Randy Binns]

I am trying to install Oracle 9.2.0.1. on HPUX 11.11. When I run the runInstaller script I get "Execute permission denied". The installation files were downloaded from Oracle and extracted to the hard drive as Disk1, Disk2 and Disk3. All files and directories belong to the oracle user that was created per the pre-installation setup instructions and all have permissions of 755. I am running runInstaller as the oracle user.

As far as I can tell all required patches are installed, but all documentation that I can find regarding required patches is for 11.00 and not 11.11.

Any ideas?

Thanks
Randy Binns
hp telecom

[Zafar A. Mohammed_1]

did you created the separate oracle "group" apart from user also.

Thanks
Zafar

[Michael Steele_2]

From my notes, and please check with oracle about this, I have oracle:dba as owner and group for all oracle /dev's with either 660 or 777 permissions. For example:

chmod 660 /dev/vg_ops/rlv*
chown oracle:dba /dev/vg_ops/rlv*
chmod 777 /dev/vg_ops

[Gary Yu]

did you get this error at the begining of the installation or in the middle, say, when creating the database?

If it was the error when creating database, then most probably you set the wrong permission on the dbs data file directory.

thanks,
Gary

[Randy Binns]

I created a group named dba of which the oracle user is a member. I also created a group named oinstall to which I added the oracle user in the /etc/group file.

I get this error at the very beginning of the installation.

oracle:dba owns the disk that I am running
runInstaller from. (Disk1)

In the installation instructions there is a section that I am not sure how to do:
"For HP users, the OSDBA group must be granted the HP system privileges RTSCHED, RTPRIO and MLOCK. For more information, refer to the Oracle9i Administrator's Reference Release 2 (9.2.0.1.0) for UNIX Systems".

I am trying to locate the above mentioned document.

[Ravi_8]

Hi,

refer the URL:
http://otn.oracle.com/docs/products/oracle9i/doc_library/release2/A96167_01/html/pre.htm#CHDCJDHI

[Steven E. Protter]

You probably expanded the oracle cpio files as root.

Now you are trying to hopefully install as oracle.

You most definitely need an oracle user and group.

That user needs to own the files you are doing the install from.

That user needs to be logged on and have an $ORACLE_HOME value set prior to installation.

You need to be pretty current on patches, December 2002, and java http://www.hp.com/go/java prior to proceeding.

SEP

[Indira Aramandla]

Hi Randy,

If you created the user ORACLE assigned to the DBA group. Then the error that you are experiencing is typically a result of your .profile. I would recheck, or see if you have a /var/opt/oracle/oraInst.loc (on Solaris for example) and if so, delete it. I know that this file exists in another location on other UNIX platforms... so I would suggest a search for oraInst.loc, if it does not exist under /var/opt/oracle/. The oraInst.loc file points to the oraInventory location.

If the above did not work then please refer this.

During the INITIAL install of oracle on a UNIX system, the OUI will prompt first for a UNIX groupID (referred to as the generic 'oinstall' group) to be assigned ownership of the oraInventory and ORACLE_HOME directories that get created by the OUI. Secondly the OUI will prompt for a UNIX groupID (referred to as the generic 'dba' group) to be assigned database administrative privileges in the ORACLE_HOME that gets created by the OUI. This groupID(dba) gets internalized into the Oracle software and is used to determine who can 'connect / as sysdba' without a password.

On subsequent installs of oracle on the same UNIX system, the OUI will ONLY prompt for a UNIX GroupID (dba) to be assigned administrative privileges within the new ORACLE_HOME. This is because subsequent installs of oracle will use the same oraInventory and not create a new one. If you provided two groupIDs during your initial install of oracle, 'oinstall' & 'dba' for instance, your oraInventory directory and ORACLE_HOME should be owned by 'oinstall', but only members of the 'dba' group will be allowed to administer the databases in the new ORACLE_HOME. To put it plainly, 'oinstall' owns the ORACLE_HOME and oraInventory directories, while 'dba' administers the Database. Most people use the same UNIX GroupID for both purposes.

Background on the oraInventory directory:-
-----------------------
The OUI maintains information about installed oracle products in the oraInventory directory. This directory is only useable to the OUI. The OUI verifies things like the ORACLE_HOME location and version information from here to allow patchsets to be installed (This is also where the 'Installed Products' listing gets populated from). The OUI finds the oraInventory directory by reading the /var/opt/oracle/oraInst.loc file on most platforms and /etc/oraInst.loc on AIX.

[Indira Aramandla]

Hi Randy,

If you created the user ORACLE assigned to the DBA group. Then the error that you are experiencing is typically a result of your .profile. I would recheck, or see if you have a /var/opt/oracle/oraInst.loc (on Solaris for example) and if so, delete it. I know that this file exists in another location on other UNIX platforms... so I would suggest a search for oraInst.loc, if it does not exist under /var/opt/oracle/. The oraInst.loc file points to the oraInventory location.

If the above did not work then please refer this.

During the INITIAL install of oracle on a UNIX system, the OUI will prompt first for a UNIX groupID (referred to as the generic 'oinstall' group) to be assigned ownership of the oraInventory and ORACLE_HOME directories that get created by the OUI. Secondly the OUI will prompt for a UNIX groupID (referred to as the generic 'dba' group) to be assigned database administrative privileges in the ORACLE_HOME that gets created by the OUI. This groupID(dba) gets internalized into the Oracle software and is used to determine who can 'connect / as sysdba' without a password.

On subsequent installs of oracle on the same UNIX system, the OUI will ONLY prompt for a UNIX GroupID (dba) to be assigned administrative privileges within the new ORACLE_HOME. This is because subsequent installs of oracle will use the same oraInventory and not create a new one. If you provided two groupIDs during your initial install of oracle, 'oinstall' & 'dba' for instance, your oraInventory directory and ORACLE_HOME should be owned by 'oinstall', but only members of the 'dba' group will be allowed to administer the databases in the new ORACLE_HOME. To put it plainly, 'oinstall' owns the ORACLE_HOME and oraInventory directories, while 'dba' administers the Database. Most people use the same UNIX GroupID for both purposes.

Background on the oraInventory directory:-
-----------------------
The OUI maintains information about installed oracle products in the oraInventory directory. This directory is only useable to the OUI. The OUI verifies things like the ORACLE_HOME location and version information from here to allow patchsets to be installed (This is also where the 'Installed Products' listing gets populated from). The OUI finds the oraInventory directory by reading the /var/opt/oracle/oraInst.loc file on most platforms and /etc/oraInst.loc on AIX.

[Indira Aramandla]

If you created the user ORACLE belonging to the DBA group. The error that you are experiencing is typically a result of your .profile. I would recheck, or see if you have a /var/opt/oracle/oraInst.loc (on Solaris for example) and if so, delete it. I know that this file exists in another location on other UNIX platforms... so I would suggest a search for oraInst.loc, if it does not exist under /var/opt/oracle/. The oraInst.loc file points to the oraInventory location.

If the above did not work then please refer this.

During the INITIAL install of oracle on a UNIX system, the OUI will prompt first for a UNIX groupID (referred to as the generic 'oinstall' group) to be assigned ownership of the oraInventory and ORACLE_HOME directories that get created by the OUI. Secondly the OUI will prompt for a UNIX groupID (referred to as the generic 'dba' group) to be assigned database administrative privileges in the ORACLE_HOME that gets created by the OUI. This groupID(dba) gets internalized into the Oracle software and is used to determine who can 'connect / as sysdba' without a password.

On subsequent installs of oracle on the same UNIX system, the OUI will ONLY prompt for a UNIX GroupID (dba) to be assigned administrative privileges within the new ORACLE_HOME. This is because subsequent installs of oracle will use the same oraInventory and not create a new one. If you provided two groupIDs during your initial install of oracle, 'oinstall' & 'dba' for instance, your oraInventory directory and ORACLE_HOME should be owned by 'oinstall', but only members of the 'dba' group will be allowed to administer the databases in the new ORACLE_HOME. To put it plainly, 'oinstall' owns the ORACLE_HOME and oraInventory directories, while 'dba' administers the Database. Most people use the same UNIX GroupID for both purposes.

Background on the oraInventory directory:- The OUI maintains information about installed oracle products in the oraInventory directory. This directory is only useable to the OUI. The OUI verifies things like the ORACLE_HOME location and version information from here to allow patchsets to be installed (This is also where the 'Installed Products' listing gets populated from). The OUI finds the oraInventory directory by reading the /var/opt/oracle/oraInst.loc file on most platforms and /etc/oraInst.loc on AIX.

[Indira Aramandla]

If you created the user ORACLE belonging to the DBA group. The error that you are experiencing is typically a result of your .profile. I would recheck, or see if you have a /var/opt/oracle/oraInst.loc (on Solaris for example) and if so, delete it. I know that this file exists in another location on other UNIX platforms... so I would suggest a search for oraInst.loc, if it does not exist under /var/opt/oracle/. The oraInst.loc file points to the oraInventory location.

If the above did not work then please refer this.

During the INITIAL install of oracle on a UNIX system, the OUI will prompt first for a UNIX groupID (referred to as the generic 'oinstall' group) to be assigned ownership of the oraInventory and ORACLE_HOME directories that get created by the OUI. Secondly the OUI will prompt for a UNIX groupID (referred to as the generic 'dba' group) to be assigned database administrative privileges in the ORACLE_HOME that gets created by the OUI. This groupID(dba) gets internalized into the Oracle software and is used to determine who can 'connect / as sysdba' without a password.

On subsequent installs of oracle on the same UNIX system, the OUI will ONLY prompt for a UNIX GroupID (dba) to be assigned administrative privileges within the new ORACLE_HOME. This is because subsequent installs of oracle will use the same oraInventory and not create a new one. If you provided two groupIDs during your initial install of oracle, 'oinstall' & 'dba' for instance, your oraInventory directory and ORACLE_HOME should be owned by 'oinstall', but only members of the 'dba' group will be allowed to administer the databases in the new ORACLE_HOME. To put it plainly, 'oinstall' owns the ORACLE_HOME and oraInventory directories, while 'dba' administers the Database. Most people use the same UNIX GroupID for both purposes.

Background on the oraInventory directory:- The OUI maintains information about installed oracle products in the oraInventory directory. This directory is only useable to the OUI. The OUI verifies things like the ORACLE_HOME location and version information from here to allow patchsets to be installed (This is also where the 'Installed Products' listing gets populated from). The OUI finds the oraInventory directory by reading the /var/opt/oracle/oraInst.loc file on most platforms and /etc/oraInst.loc on AIX.

[Tim Sanko]

If oracle doesn't own the distribution the ownership I would set everything to is

chown -R oracle:dba DISK1
chown -R oracle:dba DISK2
chown -R oracle:dba DISKX-Z



Next, I would export an ORACLE_HOME,ORACLE_SID and then prepare for my install. This is assuming you are creating a new install.

Remember not to take the defaults for the system table or the TEMP table. They need to be much larger for real use. I set my system table to be 500 MB and my temp to 1GB for small test environment implementations. (Our GL_DETAIL indexes are 16 GB).

I have no idea what size you need, but size it accordingly.

I have a 3/4 TB database for production and 500 MB for each test environment. That is just DB no application. Please remember that when you create a tablespace the area in the tablespace is allocated, but you need to use other techniques to know how much space is available, or needed.

I hope my old age, grey hair, and mature wisdom (too lazy to do it over) can help you.

[Randy Binns]

I downloaded 9.2.0.1 from the otn.oracle website. The installer works on this version.
There must be something wrong with 9.2.0.2
installer (the version I was originally attempting to install).

Thanks for your time
Randy Binns