Problemas al Instalar Oracle 7.3.2.3

ORACLE Server/Installation
--------------------------
Installations
-------------
Top 20 issues
-------------
19-APR-1999
CONTENTS
--------
1. During a 7.3.x install the error "User Interface Failure: Application
Initialization" occurs.
2. A SOLARIS (453) 7.3.2.1 character or motif install immediately gives a core
dump and/or segmentation fault.
3. While doing a motif install, selecting the "OK" button in the "Installation
Activity Choice" screen gives a segmentation fault.
4. A core dump occurs while running the Oracle installer.
5. Execution of orainst gives error "User Interface Failure: Window System
Startup"
6. During install get "unix.stp(6293): UNBOUND VARIABLE GROUP"
7. While installing or upgrading the Oracle7 Server on UNIX, an error such as
"rdbms.vrf(####): Unbound variable 'xxxxx'" is encountered
8. When changing directory to /SD_CDROM/orainst during the Oracle Release 7.3.3
install on HP (2) platform the system hangs.
9. When installing RDBMS v7 on Unix, get error of "tk2.vrf: File not found"
10. At the Software Asset Manager screen of the install there are no available
products listed to install.
11. During an installation of RDBMS V7. X on a Unix system, an error such as
"a permission denied error occurred when creating <directory>".
12. Installing Workgroup Server gives a segmentation fault, immediately after
the installer (./wgstart) is initiated.
13. Execution of wgstart gives error "User Interface Failure: Window System
Startup".
14. RDBMS V7.3.2.1 installer does not allow the installation and/or creation of
a database in a non-ofa compliant directory structure.
15. When linking the RDBMS, the installer errors out with undefined symbols such
as gss_init_sec_context, gss_acquire_cred, gss_display_name, and gss_open.
16. Linking fails while running start. Sh during the installation of Oracle RDBMS
V7. X from CD-ROM.
17. "CDROM" does not show up as an install source on the Installer Actions
screen.
18. Running the "start.sh" script gives error of "unable to make link _UNLOCK:1
to. Unlock"
19. Get "./wgrootpre.sh: /etc/cron.d/cron.allow: cannot create" during Workgroup
Server install.
20. Installing Workgroup Server v7.3.2.x on SCO UNIX gives errors of executables
not being relinked.
PROBLEM & SOLUTIONS
1. During a 7.3.x install the error "User Interface Failure: Application
Initializaton" occurs.
Problem
-------
The installer is either looking for the "/usr/lib/X11/nls" directory and cannot
find it or needs permission to that directory.
Solution
--------
Make sure that the "/usr/lib/X11/nls" directory is present and that oracle has
read and write permissions for owner, group, and other.
References
----------
<PRE 1030572.6> USER INTERFACE FAILURE: APPLICATION INITIALIZATION ERROR DURING
INSTALL OF WGS OR RDBMS V7.3.2
2. A SOLARIS (453) 7.3.2.1 character or motif install immediately gives a core
dump and/or segmentation fault.
Problem
-------
This is bug 443961.
Solution
--------
Install the installer off of the 7.3.2.2 or 7.3.2.3 media and use this to
install 7.3.2.1 software.
References
----------
<Bug 443961> 7.3.2.1 INSTALLER SEG FAULT IN CHAR AND MOTIF ON 2.5 AT OS PATCH
LEVEL 103093-06
<PRE 1025011.6> SOLARIS: CORE DUMP AND/OR SEGMENTATION FAULT FROM RUNNING MOTIF
OR CHARACTER MODE INSTALLER
3. While doing a motif install, selecting the "OK" button in the "Installation
Activity Choice" screen gives a segmentation fault.
Problem
-------
The wrong version of motif library, libXm, is being used.
Solution
--------
Reset LD_LIBRARY_PATH to point to the shared Motif library on the CDROM, then
rerun the installer.
References
----------
<Bug 359895> MOTIF INSTALLER CORE DUMPS AFTER SELECTING OKAY ON THE ACTIVITY
CHOICE SCREEN
<PRE 1017467.6> 'SEGMENTATION FAULT' RUNNING ORAINST IN MOTIF MODE
4. A core dump occurs while running the Oracle installer.
Problem
-------
Many core dumps are a result of not having the system properly set up for oracle
to be installed.
Solution
--------
If a core dump occurs during an install check for sufficient UNIX system
resources:
/tmp should have at least 50MB of free space
Swap Space should be 2 1/2 to 3X RAM
For example: RAM = 64M, SWAP=192M
Review the "Requirements" and "Issues and Restrictions" chapters of the "Oracle7
Installation and Configuration Guide". Verify that all the listed hardware and
software requirements have been met.
Check the installation log for additional errors, usually found in:
$ORACLE_HOME/orainst/install.log
References
----------
<PRE 1009810.6> CORE DUMP WHILE RUNNING ORACLE INSTALLER
5. Execution of orainst gives error "User Interface Failure: Window System
Startup"
Problem
-------
The environmental variable TERM or ORACLE_TERM is set to a invalid terminal
type.
Solution
--------
Ensure that TERM or ORACLE_TERM is set to a terminal type for which a resource
file exists in the directory where the install is being done.
The available resource files that can be used to install are tk2c<term type>.res
i.e. ORACLE_TERM=vt100 would use /<mount_point>/orainst/tk2cvt100.res
References
----------
<PRE 1012360.6> "USER INTERFACE FAILURE WINDOW SYSTEM STARTUP FAILURE" DURING
INSTALL
6. During install get "unix.stp(6293): UNBOUND VARIABLE GROUP"
Problem
-------
The machine in which Oracle is being installed on is a client of NIS/NIS+ or
yellow pages service. When NIS is running, password authentication and identifi-
cation of users is done through the network by a NIS server. The Oracle
installer is then unable to retrieve the proper value for the variable GROUP.
This problem can also happen if the user has logged into the oracle account via
the "su" command. When properly logged in to oracle account, the environmental
variable USER should be set to oracle.
Solution
--------
Turning off NIS and defining the user oracle on the install machine allows the
install to bypass the network password authentication and identify the user
"oracle" locally on the machine. After the install has completed, NIS can be
turned back on.
Installs should be done with the user logged into the oracle account directly
and not through the "su" command.
If the variable USER is not set to oracle then it needs to be reset to the
correct value.
References
----------
<PRE 1033660.6> SOLARIS: "UNIX.STP(6293):UNBOUND VARIABLE GROUP" DURING RDBMS
INSTALLATION
<PRE 1014652.6> UNIX.STP ERROR DURING RELINK STAGE OF INSTALL
7. While installing or upgrading the Oracle7 Server on UNIX, an error such as
"rdbms.vrf(####): Unbound variable 'XXXXX'" is encountered
Problem
-------
The *.vrf files are scripts that perform the following function for each
individual product:
- Product dependancy analysis to decide whether to load
the product files. If the dependency(ies) are not met,
installation will terminate.
- Acquire product executables relink options (if applicable).
- Collect configuration information from the user for the
<Product_Name> database objects creation (if applicable).
A typical vrf error appears in the $ORACLE_HOME/orainst/install.log in the
following format:
<product_name>.vrf[#####]
The product-name indicates the product that encountered the problem. The
number [####] indicates the line in the vrf script where the installation
terminated.
This problem can also be caused if the installation source is not correct.
For example, if a permanent staging area is being used, verify that the
permanent stage was created by the same version of Oracle you are trying to
install.
Solution
--------
By going to line number in the *. Vrf file the problem can usually be resolved
by looking at the syntax or the commented section that occurs right before the
error.
Also, verify that the orainst that is being used to install the software, has
come from the same distribution media as the software.
References
----------
<PRE 1026138.6> TROUBLESHOOTING RDBMS.VRF,OCOMMON.VRF & PLSQL.VRF ERRORS
<PRE 1014535.6> OCOMMON.VRF ERROR OCCURS DURING INSTALL
8. When changing directory to /SD_CDROM/orainst during the Oracle Release 7.3.3
install on HP (2) platform the system hangs.
Problem
-------
When the user exits as root the 2 "pfs" processes (i.e. Pfs_mountd and pfsd)
that
are created during the mount command steps, as described in the ORACLE7 SERVER
INSTALLATION GUIDE RELEASE 7.3.3 for HP, are killed.
Solution
--------
Use the "nohup" command in steps 1 and 2 of mounting the CD-ROM:
step 1. # nohup /usr/sbin/pfs_mountd &
step 2. # nohup /usr/sbin/pfsd &
Now proceed with the remaining steps as described in the Installation Guide.
References
----------
<PRE 1032447.6> HP:CANNOT MOUNT THE 7.3.3 CD-ROM;SESSION HANGING
9. When installing RDBMS v7 on Unix, get error of "tk2.vrf: File not found"
Problem
-------
A tk2. Vrf: FILE NOT FOUND error, typically means that the installer can't find
the files that it's looking for.
This can be caused by running the installer from the /cdrom/orainst directory
when it should be run from the <oracle_link_path>/orainst directory (the only
exceptions to this rule are the two Sun and the two DEC ports).
Also, if the CD-ROM has not been mounted with the correct options, it could
prevent the installer from finding the desired files.
The "tk2.vrf: File not found" error may arise from the CD-ROM directory being
NFS mounted from a dissimilar Unix machine.
Solution
--------
Make sure that the media is mounted correctly with the correct mount commands
and that the orainst installer is run from the correct location.
If you want to NFS-mount the CD-ROM onto your machine, you should ensure you're
mounting it from another machine
running the *same* operating system and operating system version. Formats and
mount commands differ between platforms and os versions.
References
----------
<PRE 1010936.6> "TK2.VRF: FILE NOT FOUND" WHEN INSTALLING RDBMS V7 ON UNIX
<PRE 1014716.6> CAN'T FIND RESOURCE FILE /CDROM/ORACLE/ORAINST/TK2{TERM}.RES
<PRE 1006339.6> FILE AND DIRECTORY NAMES ARE TRUNCATED IN THE CD-ROM DIRECTORY
<PRE 1010604.6> WHAT IS THE ORACLE LINK DIRECTORY?
10. At the Software Asset Manager screen of the install there are no available
products listed to install.
Problem
-------
The installer looks at a unix.prd file to determine the list of products that
can be installed. During the install, if the wrong location is given for the
location of the distribution media then this file will not be found.
This problem occurs if you enter the CD-ROM mount point, instead of the
oracle_link directory, when prompted for the permanent staging area.
Solution
--------
Reinvoke the installer and select install from cdrom. Then when prompted for
link directory enter oracle_link location. If installing from stage area then
select install from stage area and then enter stage directory location when
prompted.
References
----------
<PRE 1006889.6> ORACLE INSTALLER CANNOT FIND PRODUCTS WHILE INSTALLING FROM
CD-ROM
11. During an installation of RDBMS V7. X on a Unix system, an error such as
"a permission denied error occurred when creating <directory>".
Problem
-------
Orainst has problems recognizing:
- symbolic links to $ORACLE_HOME
- NIS/NIS+ (yellow-paged) users
- NFS mounted file systems
Solution
--------
Verify the oracle user is LOCAL to the machine in the /etc/password file *AND*
the /etc/group file.
Verify there are no symbolic links to $ORACLE_HOME.
Verify $ORACLE_HOME is not NFS mounted from another machine.
If NIS/NIS+ (yellow pages) is being used disable it before doing the install.
References
----------
<PRE 1016031.6> 'PERMISSION DENIED WHEN CREATING <DIRECTORY>' DURING INSTALL
ON UNIX
<PRE 1034344.6> ERRORS INSTALLING RDBMS V7.3.2.1 (SOFTWARE ONLY)
12. Installing Workgroup Server gives a segmentation fault, immediately after
the installer (./wgstart) is initiated.
Problem
-------
The workgroup server installer is failing because it is a motif install and the
display is not set to PseudoColor.
Solution
--------
Verify the default value for the visual class is PseudoColor by using the
"xdpyinfo" command which is usually found in the "/usr/bin/X11" directory.
References
----------
<PRE 1024462.6> SEGMENTATION FAULT AND CORE DUMP ON WGSTART
13. Execution of orainst gives error "User Interface Failure: Window System
Startup".
Problem
-------
This occurs when doing 73x Workgroup Server installs if the operating system is
not running a gui base interface.
Solution
--------
For 73x Workgroup Server installs, start the gui interface prior to running
./Wgstart or get script via PRE 1031802.6 to run install in character mode.
References
----------
<PRE 1031802.6> WGS CHARACTER MODE INSTALL SCRIPT
14. RDBMS V7.3.2.1 installer does not allow the installation and/or creation of
a database in a non-ofa compliant directory structure.
Problem
-------
Oracle Flexible Architecture (OFA) is the default directory structure for
7.3.2.1 installations on Unix. Versions 7.3.2.2 and above allow for creation
of a database in a non-OFA structure.
The 'Install New Products' and 'Create Database Objects' options of the
installer can only be used with the OFA format.
Solution
--------
'Add/Upgrade Software' will allow for the install of the software in a non-OFA
format (in the specified $ORACLE_HOME) without creating a database. The database
must then be manually create, with the database files being placed in defined
directories (instead of /<mount_point>/oradata, as in OFA installs).
References
----------
<Bug 357329> NO WAY TO HAVE THE INSTALLER CREATE A DATABASE IF SOFTWARE IS
NON OFA-COMPLIANT
<PRE 1016802.6> INSTALLING 7.3 IN A NON-OFA COMPLIANT DIRECTORY STRUCTURE ON
UNIX
<PRE 1006497.6> CREATING A DATABASE IN THE UNIX ENVIRONMENT
15. When linking the RDBMS, the installer errors out with undefined symbols such
as gss_init_sec_context, gss_acquire_cred, gss_display_name, and gss_open.
Problem
-------
During the installation the Advanced Networking Options were selected from the
Software Asset Manager screen as product to install. These products require that
the supported 3rd party Authentication Adapter be installed on the operating
system.
Solution
--------
Deinstall the Advanced Networking Option and SQL*Net Version 2 and
then reinstall SQL*Net Version 2.
In order to relink the RDBMS with the Advanced Networking Option, a
third-party Authentication Adapter must be installed. See SQL*Net
Version 2 Requirements in the Installation and Configuration Guide.
References
----------
<PRE 1034600.6> UNDEFINED SYMBOLS WHEN RELINKING RDBMS V7.3.3
<PRE 1030959.6> UNDEFINED SYMBOLS RELINKING SQL*NET
16. Linking fails while running start. Sh during the installation of Oracle
RDBMS
V7.x from CD-ROM.
Problem
-------
If the oracle_link directory is running out of space, inodes, or has wrong
permissions on it, the following error can be generated:
unable to make link: <file name >
This error is also sometimes followed by:
OAURM.RES:1 to oarun.res_1
mkdir : cannot create orainst
Orainst: no space left on device
Solution
--------
Use the "df" command, with the appropriate options, to see how much space is
left on the file system. Try relocating the oracle_link directory to a file
system with more space (atleast 60MB) and restart the installation.
Use the "df" command to check if the oracle_link directory (or the selected
directory where the links are to be made) has sufficient inodes. At least 8000
inodes should be allocated to this directory.
Note that inodes are different from disk space.
Verify the permission for oracle_link is 777.
References
----------
<PRE 1009380.6> "UNABLE TO MAKE LINK" DURING INSTALL FROM CD-ROM
17. "CDROM" does not show up as an install source on the Installer Actions
screen.
Problem
-------
The orainst.motif binary was executed without going through the orainst shell
script. This can happen if the installer is invoked with the "./orainst.motif"
command instead of "./orainst /m". As a result, the ORAINST_CDROMONLY environ-
Ment variable (which should be set to TRUE) remains unset, so the CDROM option
does not appear in the available options list.
Solution
--------
Make sure the installer was invoked correctly
% cd $ORACLE_HOME/orainst
% ./orainst
or
% ./orainst /m
or
% ./orainst /c
References
----------
<PRE 1026296.6> CDROM IS NOT LISTED AS AN INSTALL SOURCE OPTION
18. Running the "start.sh" script gives error of "unable to make link _UNLOCK:1
to. Unlock"
Problem
-------
The error means that the executable "cd_link", which is run by "start.sh", was
unable to create a symbolic link from <oracle_link>/.unlock -> /cdrom/_UNLOCK:1.
Solution
--------
This is result of running start.sh a second time without removing all the old
files from the oracle_link directory. The error can be safely ignored without
any harm to the install process. However, the oracle_link directory should al-
ways be completely delete after any installation is complete or if the CD-ROM
has been dismounted.
References
----------
<PRE 1020639.6> UNABLE TO MAKE LINK ERROR WHEN RUNNING START.SH
19. Get "./wgrootpre.sh: /etc/cron.d/cron.allow: cannot create" during Workgroup
Server install
Problem
-------
This error occurs due to the existence of the "cron.allow" or
"cron.deny" script. These files reside in the following
locations:
AIX /var/adm/cron
DEC /var/adm/cron
HP /usr/lib/cron
IRIX /etc/cron.d
SCO Unix /usr/lib/cron
Solaris /etc/cron.d
Sun OS /var/spool/cron
Solution
--------
Workgroup Server MUST be run by "root" so "root" must either be listed
in the "cron.allow" file or NOT listed in the "cron.deny" file in
order for the installation to work.
References
----------
<PRE 1028818.6> INSTALLATION OF WORKGROUP SERVER FAILS DURING RELINKING
20. Installing Workgroup Server v7.3.2.x on SCO UNIX gives errors of executables
not being relinked.
Problem
-------
The "make" command does not exist on system.
Solution
--------
Oracle Workgroup Server v7.1.5 supplies a floppy disk for the utility GNU
make, but v7.3.2.x does not supply this.
The command can be obtained through a free CD supplied with SCO OpenServer 5.0
called Skunkware CD or via web site
http://www2.sco.com/Skunk96/dist/Tools/gds-95q4/index.html
References
----------
<PRE 1024642.6> MISSING GNU MAKE ON SCO INSTALL
Mi mail : [email protected]