Runinstaller Segmentation Fault Oracle

Posted on by admin

This chapter describes installation and their workarounds associated with Oracle Application Server. It includes the following topics:

  1. Segmentation Fault In C
  2. Segmentation Fault Mac
  3. Segmentation Fault Fortran
  4. Runinstaller Segmentation Fault Oracle Arena
  5. Segmentation Fault Debugging

Oracle GoldenGate Installation, Part 1. We all know replication using Oracle Streams technology. Streams are improving from version to version of the RDBMS, and now it is a very well managed and reliable technology with a large set of options and capabilities. But, in the document Oracle – GoldenGate Statement of Direction (PDF).

2.1 Installation Issues

This section describes issues with installation of Oracle Application Server. It includes the following topics:

2.1.1 Using the Unified Oracle SOA Suite Installer for the mySOACompany Topology

Oracle Application Server Enterprise Deployment Guide 10g Release 3 (10.1.3.1.0) describes how to install the mySOACompany topology in a distributed environment, i.e., the various SOA components are installed in separate containers. Oracle recommends this environment for availability and performance isolation reasons. If these issues are not important to you, you may install all of the SOA components in a single container. To do this, launch Oracle Application Server SOA Suite 10.1.3.1.0 installer and select the J2EE Server, Web Server, and SOA Suite installation type.

2.1.2 IPv6 Not Supported

This release of Oracle Application Server is not certified to run on machines that are configured with IPv6. You have to install and run this release of Oracle Application Server on machines that are configured with IPv4.

2.1.3 Response Files Created through the Record Mode Are Not Supported

If you want to run the installer with a response file (to perform a silent or non-interactive installation), you cannot use response files created through the -record command-line option in the installer, as described in the 'Creating Response Files by Using the Record Mode in the Installer' section in the Oracle Application Server Installation Guide. Instead, you must use response files that were created from the provided response file templates; you replace the placeholder values in the template files with your own values.

2.1.4 Set Kernel Parameter Prior to Installation of Oracle HTTP Server on Red Hat Linux 4.0

Prior to installation of Oracle HTTP Server as part of an Oracle Application Server installation on Red Hat Linux 4.0, set the following kernel parameter:

file-max >= 131072

Failure to set the preceding parameter may result in an error in installation of Oracle Application Server.

Segmentation Fault In C

2.1.5 Asian Languages Do Not Display Correctly with Java 5.0

Asian language characters including Japanese, Korean, Traditional Chinese, and Simplified Chinese are not displayed on SuSE platform due to lack of support of JDK.

To resolve this issue, you can modify the font properties/config files. Refer to the following Sun Microsystems Java Web site URL for details:

However, both Sun and Oracle do not support these modifications and if you need support, then you will need to reproduce the product functional errors with an unaltered JDK.

2.1.6 Japanese Characters Affected on Red Hat Linux

On Red Hat Linux Release 4 (Nahant Update 1) and Red Hat Linux Release 3 (version older than Taroon Update 3), Japanese (ja_JP) characters appears as square boxes on the Oracle Universal Installer installation screens for Oracle Application Server 10g Release 3 (10.1.3.1.0). This issue is due to the use of the Java Runtime Engine (JRE) version that is shipped with Oracle Application Server; 1.4.2_05 or an earlier version of the JRE.

To work around this issue use version number1.4.2._06 or a newer version of the JRE.

2.1.7 Check gcc Version Before Installing 10.1.3 on a Host with a 9.0.4 Installation

Oracle Application Server 10g Release 3 (10.1.3.1.0) requires a version of gcc that depends upon your operating system. See Oracle Application Server Installation Guide 10g Release 3 (10.1.3.1.0) for Linux x86 for the version of gcc required for your operating system.

If your host contains an Oracle Application Server 10g (9.0.4) installation, you may have installed gcc-2.95 or gcc-2.96 on your system, as outlined in Oracle Application Server Quick Installation and Upgrade Guide 10g (9.0.4) for Linux x86. The procedure involved creating symbolic links for /usr/bin/gcc and /usr/bin/cc to the appropriate version of the executables.

To check whether these links exist:

Check if the gcc and cc commands are symbolic links, for example:

If the links exist, remove them and create new links to the version of gcc required for 10.1.3:

  1. Install the version of gcc required for your version of Linux. For example:

  2. Remove the existing symbolic links:

  3. Create links to the new version of gcc:

  4. Install Oracle Application Server 10g Release 3 (10.1.3.1.0).

2.1.8 Install Software Packages for Red Hat Linux

If you are installing on Red Hat Enterprise Linux AS/ES 4.0, Update 1 or higher, certified on AMD64 and Intel EM64T, the following packages (or higher versions) are required:

  • glibc-2.3.4-2.9.i686.rpm (32-bit)

  • glibc-2.3.4-2.9.x86_64.rpm

  • glibc-common-2.3.4-2.9.x86_64.rpm

  • glibc-devel-2.3.4-2.9.i386.rpm (32bit)

  • glibc-devel-2.3.4-2.9.x86_64.rpm

  • gcc-3.4.3-22.1.x86_64.rpm

  • gcc-c++-3.4.3-22.1.x86_64.rpm

  • gnome-libs-1.4.1.2.90-44.1.x86_64.rpm

  • libstdc++-3.4.3-22.1.i386.rpm (32-bit)

  • libstdc++-3.4.3-22.1.x86_64.rpm

  • libstdc++-devel-3.4.3-22.1.i386.rpm (32-bit)

  • libstdc++-devel-3.4.3-22.1.x86_64.rpm

  • make-3.80-5.x86_64.rpm

  • pdksh-5.2.14-30.x86_64.rpm

  • sysstat-5.0.5-1.x86_64.rpm

  • binutils-2.15.92.0.2-13.x86_64.rpm

  • compat-db-4.1.25-9.i386.rpm (32-bit)

  • compat-db-4.1.25-9.x86_64.rpm

  • control-center-2.8.0-12.x86_64.rpm

  • xscreensaver-4.18-5.rhel4.2.x86_64.rpm

  • setarch-1.6-1.x86_64

  • openmotif21-2.1.30-11.RHEL4.4.i386.rpm (32-bit)

2.1.9 Error Messages after Setting VIRTUAL_HOST_NAME

After successfully completing the Basic Installation with the VIRTUAL_HOST_NAME environment variable set, you may find the following error messages in ORACLE_HOMEopmnlogsdefault_group~home~default_group~1:

These error messages are benign and can be safely ignored.

2.1.10 Error Message in application.log File

After successful installation of Oracle Application Server, you may find the following error message in the application.log file:

This error message is benign and can be safely ignored.

2.1.11 Tool and Script Failure

Multiple Oracle Application Server tools and scripts will fail during Oracle Application Server installation due to the incorrect setting of the ANT_HOME environmental variable.

To workaround this issue, unset the ANT_HOME environmental variable prior to installing Oracle Application Server.

After you have unset the ANT_HOME environmental variable, you can either:

  • remove the /etc/ant.conf file

  • comment out the line in the /etc/ant.conf file that incorrectly sets the ANT_HOME environmental variable

2.1.12 Middle Tier Installation Failure for Turkish Locale

Installation of an Oracle Application Server middle-tier fails for Turkish locale.

Oracle recommends that you avoid running the Oracle Universal Installer to install Oracle Application Server using the Turkish locale because some of the installation screens will not be displayed properly and will not be usable.

Oracle Application Server components such as OWSM and BPEL are not functional for the Turkish locale.

2.1.13 Recommended Locales for Simplified Chinese and Traditional Chinese

To avoid issues with installation of Oracle Application Server in locales using simplified Chinese and Traditional Chinese, Oracle recommends using:

  • zh_CN.gbk instead of zh_CN.gb18030 for Simplified Chinese

  • zh_TW.big instead of zh_TW.eucTW for Traditional Chinese

2.1.14 Icon and URL Link Errors in Spanish and Brazilian Portuguese Language Locales

In advanced Oracle Application Server installations in Spanish and Brazilian Portuguese Language locales, the Rules Control icon is not displayed.

Additionally the URL link to Oracle Application Server is not placed correctly.

There is no Rules control link in Brazilian Portuguese locale installations.

2.1.15 Oracle HTTP Server Welcome Page Displays Only In English

Oracle HTTP Server Welcome page displays in English only following installation of Oracle Application Server.

In order to view the translated Oracle HTTP Server Welcome page, you need to enter you installation information in the following format where <lang> is the language you would like to use to view the Welcome page:

For example,

http://<host>.<port>/index.html.ja (Japanese)

http://<host>.<port>/index.html.ko (Korean)

http://<host>.<port>/index.html.zh_TW (Traditional Chinese)

http://<host>.<port>/index.html.zh_CN (Simplified Chinese)

http://<host>.<port>/index.html.de (German)

http://<host>.<port>/index.html.fr (French)

http://<host>.<port>/index.html.it (Italian)

http://<host>.<port>/index.html.es (Spanish)

Runinstaller Segmentation Fault Oracle

http://<host>.<port>/index.html.pt_BR (Brazilian Portuguese)

2.1.16 opmnctl Command Time Out with Old Data

The opmnctl stopall command times out if the BPEL schema in your OracleAS Metadata Repository Database contains old schemas.

To fix this issue, run the production irca.sh to load new schemas in the Oracle database.

2.1.17 Exception in Error Log when Installing MainCD

After successful installation of Oracle Application Server SOA MainCD, you may find the following Exception message in the oraInstallyyyy-mm-dd_hh-mm-ssAM/PM.err file:

This exception message is benign and can be safely ignored.

2.1.18 Exception Message on the Configuration Assistants Screen on System Locales Using UTF-8 Encoding

If your system locale is using a UTF-8 encoding, the Oracle Application Server installation throws a sun.io.MalformedInputException message. For example, while performing an advanced J2EE Server, Web Server and SOA Suite installation, the following error message is displayed on the Configuration Assistants Screen:

Note:

To know if your system is using a UTF-8 encoding, examine the locale-specific environment variables such as LANG or LC_ALL to see if they end with the suffix .UTF-8 or UTF8.

To fix this issue, remove the .UTF-8 suffix from the value of locale-specific environment variables. You need to use the following command to check the value of a locale-specific environment variable like LANG:

Segmentation Fault Mac

Set the value of LANG parameter to en_us by the following command:

2.1.19 Executing runInstaller gives Segmentation Fault When TMP variable is Set to 45 Characters or More

Executing runInstaller gives an error message during the installation of Oracle Application Server. This causes the installation to exit and happens when the length of TMP variable is more than 45 characters. The following error message is displayed:

To fix this issue, you need to do one of the following before starting the installation process:

  • Reset TMP variable to a shorter length less than 45 characters. For example, use the following command to reset TMP to less than 45 characters:

    where the value of variable is less than or equal to 45.

  • Unset TMP variable so that it uses /tmp as the temporary directory. You need to give the following command for doing this:

2.1.20 TaskManager or TaskActionHandler Processes in Oracle BPEL Control Fail to Deploy After Installing Oracle Application Server

The TaskManager or TaskActionHandler processes in Oracle BPEL Control fail to deploy after installing Oracle Application Server. This issue manifests itself in the following ways:

  • The domain.log file present in ORACLE_HOME/bpel/domains/default/logs directory contains compilation failures and XML parser errors.

  • A file named bpel_TaskManager_1.0.jar.failed is present in the ORACLE_HOME/bpel/domains/default/deploy directory.

  • Either the TaskManager or TaskActionHandler processes(or both) do not show up in the BPEL console.

The workaround for this issue is the following:

  1. Navigate to the deploy directory by using the following command:

  2. Rename the bpel_TaskManager_1.0.jar.failed file to bpel_TaskManager_1.0.jar

  3. If the oc4j_soa process is up and running, deployment happens automatically after you rename bpel_TaskManager_1.0.jar file.

  4. If the oc4j_soa process is not running, you need to start the process using the following command:

When deployment happens successfully with this workaround, bpel_TaskManager_1.0.jar file will be removed from the ORACLE_HOME/bpel/domains/default/deploy directory, and the BPEL console will show the TaskManager (and/or TaskActionHandler) process successfully listed in the BPEL console.

2.1.21 ONS Port Conflict When Oracle Database is Installed After Oracle Application Server

When you install Oracle Application Server, the ONS localport is set to 6101 by default. If you then install Oracle Database on the same host, the database ONS port may also be set to 6101. This results in a port conflict. The workaround is to manually change one of the ONS ports to a different port number after installation. Refer to Oracle Application Server Administrator's Guide for instructions for changing the ONS port number.

2.1.22 OPMJA.MSG Message Format is Invalid

Using the Japanese_Japan locale for user opmn startup causes opmn to become unstable because of a logging function problem. instead of using Japanese_Japan, use another language locale, such as American_America.

2.2 Documentation Errata

This section describes issues with Oracle Application Server documentation. It includes the following topics:

Segmentation Fault Fortran

2.2.1 Incorrect Installation Directory Path in Graphic

An incorrect directory path for the Installation directory is specified in Figure 4-1, 'Oracle Application Server SOA Suite 10.1.3.1.0 Installation Screen' in the Oracle Application Server Installation Guide.

The installation directory path should be /scratch/oracle/product/10.1.3.1/OracleAS.

Runinstaller Segmentation Fault Oracle Arena

2.2.2 ASG Standalone Kit Runinstaller Location Correction

Segmentation Fault Debugging

The following directory location is referenced in section 6.5.4, Installing the OracleAS 10g (10.1.3.1.0) Standalone Install of OracleAS Guard into Oracle Homes of Oracle Application Server Installation Guide:

The correct directory location is:

2.2.3 Incorrect Installation Requirements in the Screenshot of Select Installation Type Page

In Chapter 2, Section 5.3.2, 'Select Installation Type Screen' of the Oracle Application Server Installation Guide, the following incorrect installation requirements were listed in the screenshot of the Select Installation Type page:

  • J2EE Server, Web Server, and SOA Suite (874 MB)

  • J2EE Server and Web Server (659 MB)

  • J2EE Server (622 MB)

  • Web Server (535 MB)

The correct installation requirements are:

  • J2EE Server, Web Server, and SOA Suite (1.18 GB)

  • J2EE Server and Web Server (830 MB)

  • J2EE Server (800 MB)

  • Web Server (670 MB)

2.2.4 Incorrect URL

After installation is complete, the readme.txt is displayed and it contains a typo in the URL in the following section:

Online documentation for Oracle Application Server is available at: http://download.oracle.com/docs/cd/B31017-01/index.htm

The correct URL should be:

The dash (-) in the URL should be an underscore (_) character.

2.2.5 Additional Requirement for /etc/hosts File not Documented

In Chapter 2, 'Requirements,' of the Oracle Application Server Installation Guide, some additional information regarding the /etc/hosts file is missing.

The following entry must be present in the /etc/hosts file in order for the installation to start oc4j:home: