Shulou(Shulou.com)05/31 Report--

Editor to share with you Red Hat 6.5 installation of Oracle 10g faults, I hope you will learn something after reading this article, let's discuss it together!

1. OS version is compatible

The compatibility between OS and Database Software is the first hurdle we need to consider. In the Oracle 10g era, the general version of Linux was 4.x, so for our installation of Red Hat 6.5, there was an error during the installation compatibility check.

This problem is relatively easy to solve. In principle, there is no essential difference between version 6. 5 and previous Linux versions. Moreover, when we choose the Linux installation, we still choose the higher version as possible to try. The way to solve this problem is to "cheat" the installation process of Oracle software.

Oracle verifies the version, mainly to view the version information in the / etc/redhat-release file. After we modify it by hand, it will be fine.

-- before revision

[root@SimpleLinux ~] # cat / etc/redhat-release

Red Hat Enterprise Linux Server release 6.5 (Santiago)

-after revision

[root@SimpleLinux ~] # cat / etc/redhat-release

Red Hat Enterprise Linux Server release 4.8 (Santiago)

The test passed.

2. The graphical interface activates the error reporting libXp.so

During the installation of the software, the graphical interface is used to install the software. Run the runInstaller script and report an error.

[oracle@CRSimpleLinux database] $. / runInstaller

Starting Oracle Universal Installer...

Checking installer requirements...

Checking operating system version: must be redhat-3, SuSE-9, redhat-4, UnitedLinux-1.0, asianux-1 or asianux-2

Passed

All installer requirements met.

Preparing to launch Oracle Universal Installer from / tmp/OraInstall2014-05-1911 12-33-59PM. Please wait. [oracle@CRSimpleLinux database] $Exception in thread "main" java.lang.UnsatisfiedLinkError: / tmp/OraInstall2014-05-1911 12-33-59PM/jre/1.4.2/lib/i386/libawt.so: libXp.so.6: cannot open shared object file: No such file or directory

At java.lang.ClassLoader$NativeLibrary.load (Native Method)

At java.lang.ClassLoader.loadLibrary0 (Unknown Source)

At java.lang.ClassLoader.loadLibrary (Unknown Source)

At java.lang.Runtime.loadLibrary0 (Unknown Source)

At java.lang.System.loadLibrary (Unknown Source)

At sun.security.action.LoadLibraryAction.run (Unknown Source)

At java.security.AccessController.doPrivileged (Native Method)

At sun.awt.NativeLibLoader.loadLibraries (Unknown Source)

At sun.awt.DebugHelper. (Unknown Source)

At java.awt.Component. (Unknown Source)

The author is no stranger to libXp, in the past 32bit system installation 10g, it is necessary to install the libXP package. So libXp has been installed before.

[oracle@CRSimpleLinux database] $rpm-qa | grep libXp

LibXpm-3.5.10-2.el6.x86_64

LibXp-1.0.0-15.1.el6.x86_64

Not only the XWindows tool, but also the interface tool cannot be started directly through the local operation. The clue to the solution lies in i386 in the error directory. The author's server is 64bit, and unlike 32bit, many installations (including dependency packages) are supported by the 32bit software version. The guess is that the 32bit version of libXp needs to be installed during execution.

[root@CRSimpleLinux packages] # rpm-ivh libXp-1.0.0-15.1.el6.i686.rpm

Warning: libXp-1.0.0-15.1.el6.i686.rpm: Header V3 RSA/SHA256 Signature, key ID fd431d51: NOKEY

Preparing... # [100%]

1:libXp # # [100%]

After installation, both versions of libXp exist on the system.

[root@CRSimpleLinux packages] # rpm-qa | grep libXp

LibXpm-3.5.10-2.el6.x86_64

LibXp-1.0.0-15.1.el6.x86_64

LibXp-1.0.0-15.1.el6.i686

After that, the startup script is normal.

[oracle@CRSimpleLinux database] $. / runInstaller

Starting Oracle Universal Installer...

Checking installer requirements...

Checking operating system version: must be redhat-3, SuSE-9, redhat-4, UnitedLinux-1.0, asianux-1 or asianux-2

Passed

All installer requirements met.

Preparing to launch Oracle Universal Installer from / tmp/OraInstall2014-05-1911 12-40-28PM. Please wait... [oracle@CRSimpleLinux database] $

This problem tells us that you can't take things for granted. In a 64bit environment, many software packages for installing databases require both 32bit and 64bit to be installed.

3. Link error in ins_ctx.mk compilation

During the installation process, after entering the continuous running state, the operation is terminated in the link step Oracle, which mistakenly reports that link failed. Check the error log as follows:

INFO: chmod 751 / u01/app/oracle/product/10.2.0/db_1/bin/ctxlc

INFO: gcc-M32-o ctxhx-L/u01/app/oracle/product/10.2.0/db_1/ctx//lib32/-L/u01/app/oracle/product/10.2.0/db_1/lib32/-L/u01/app/oracle/product/10.2.0/db_1/lib32/stubs/ / u01/app/oracle/product/10.2.0/db_1/ctx/lib/ctxhx.o-L/u01/app/oracle/ Product/10.2.0/db_1/ctx/lib/-ldl-lm-lctxhx-Wl -rpath,/u01/app/oracle/product/10.2.0/db_1/ctx/lib-lsnls10-lnls10-lcore10-lsnls10-lnls10-lcore10-lsnls10-lnls10-lxml10-lcore10-lunls10-lsnls10-lnls10-lcore10-lnls10 `cat / u01/app/oracle/product/10.2.0/db_1/lib/

INFO: sysliblist`

INFO: / usr/bin/ld: crt1.o: No such file: No such file or directory

INFO: collect2: ld returned 1 exit status

INFO: make: * [ctxhx] Error 1

INFO: End output from spawned process.

INFO:--

INFO: Exception thrown from action: make

Exception Name: MakefileException

Exception String: Error in invoking target 'install' of makefile' / u01 * See'/ u01/app/oracle/oraInventory/logs/installActions2014-05-12 October 06-22-42 PM. Log 'for details.

Exception Severity: 1

INFO: * Cancel Dialog: *

INFO: User Selected: Stop installation of all products.

INFO: Error in invoking target 'install' of makefile' / u01 * See'/ u01/app/oracle/oraInventory/logs/installActions2014-05-12 October 06-22-42 PM. Log 'for details.

INFO: Setting variable 'PREREQ_CONFIG_LOCATION' to'. Received the value from variable association.

After the query, it was found that it was the problem of installing the dependency package. In the 32bit environment, when we use rpm direct installation or yum installation, only the 32bit version can be installed. However, in the 64bit environment, you need to install both versions. In this process, you need to strictly comply with the requirements of the documentation for installing the package. After the full package is installed, the error disappears.

4. Ins_emdb.mk problem

After all the installation packages have been installed, the error is still reported during the link phase when the installation continues.

INFO: make [1]: Leaving directory `/ u01ActureUniplex product10.2.0ActureUniplicationsysmanUnipleslib'

INFO: / u01/app/oracle/product/10.2.0/db_1/sysman/lib/snmccolm.o: could not read symbols: File in wrong format

INFO: collect2: ld returned 1 exit status

Make [1]: * * [/ u01/app/oracle/product/10.2.0/db_1/sysman/lib/nmccollector] Error 1

Make: * * [nmccollector] Error 2

INFO: End output from spawned process.

INFO:--

INFO: Exception thrown from action: make

Exception Name: MakefileException

Exception String: Error in invoking target 'collector' of makefile' / u01 apprenticespact oracle.product10.2.0 apprenticeships. See'/ u01/app/oracle/oraInventory/logs/installActions2014-05-12 October 06-34-52 PM. Log 'for details.

Exception Severity: 1

This question is more complex, the author inquired about a lot of information and did not have a definite response. Finally, a senior's solution was found on the Internet.

First click ignore to skip the steps, and then you can directly complete the execution of the runInstaller script. In the $ORACLE_HOME/bin directory, change the oracle file to oracle.bin.

Create the file oracle in the same directory as follows:

#! / bin/bash

Export DISABLE_HUGETLBFS=1

Exec $ORACLE_HOME/bin/oracle.bin $@

EOF

Use the chmod aquix oracle command to modify the permissions of the file after saving. After this policy modification, the subsequent dbca process of Oracle to create the database executes normally.

However, there are some problems in the background process, we can not see the common background processes such as pmon through ps-ef, only a series of objects of oracle.bin.

[root@CRSimpleLinux packages] # ps-ef | grep pmon

Root 542 406 0 12:57 pts/1 00:00:00 grep pmon

[root@CRSimpleLinux packages] # ps-ef | grep oracle

Root 32748 0 12:32 pts/0 00:00:00 su-oracle

Oracle 327 326 0 12:32 pts/0 00:00:00-bash

Oracle 389 10 12:34? 00:00:00 / u01/app/oracle/product/10.2.0/db_1/bin/oracle.bin (LOCAL=NO)

Oracle 391 10 12:34? 00:00:00 / u01/app/oracle/product/10.2.0/db_1/bin/oracle.bin (LOCAL=NO)

Oracle 399 10 12:35? 00:00:00 / u01/app/oracle/product/10.2.0/db_1/bin/oracle.bin (LOCAL=NO)

Oracle 401 10 12:35? 00:00:00 / u01/app/oracle/product/10.2.0/db_1/bin/oracle.bin (LOCAL=NO)

Oracle 3172 10 May13? 00:00:02 / u01/app/oracle/product/10.2.0/db_1/bin/oracle.bin

Oracle 3181 10 May13? 00:00:00 / u01/app/oracle/product/10.2.0/db_1/bin/oracle.bin

Oracle 3183 10 May13? 00:00:01 / u01/app/oracle/product/10.2.0/db_1/bin/oracle.bin

(for reasons of space, there are omissions. )

The rest of the compatibility issues have not been found.

5 、 Memory Notification in alert log

After the installation is complete, monitor the alert log information to make sure that the database is running properly. Periodic hints of memory changes are found in the database log.

Mon May 12 19:39:09 2014

Memory Notification: Library Cache Object loaded into SGA

Heap size 3596K exceeds notification threshold (2048K)

KGL object name: XDB.XDbD/PLZ01TcHgNAgAIIegtw==

Mon May 12 19:39:09 2014

Memory Notification: Library Cache Object loaded into SGA

Heap size 3567K exceeds notification threshold (2048K)

Details in trace file / u01/app/oracle/admin/chinaredb/udump/chinaredb_ora_20268.trc

KGL object name: XDB.XDA8XlWX/h+P3gQFeMmGQWfg==

After entering 10g, some memory and file alarm notification mechanisms are introduced into the running process of Oracle. Oracle has its own control mechanism for some performance concerns, such as SGA objects and Swap usage. Once the set threshold is exceeded, it will be recorded in alert log to remind the user.

This memory notification is very simple, that is, after a relatively large library cache object is introduced into the SGA, it will be automatically written into it, and there is no big performance problem. If the solution is to modify the internal control threshold, do not let prompts occur too frequently.

SQL > alter system set "_ kgl_large_heap_warning_threshold" = 8388608 scope=spfile

SQL > shutdown immediate

SQL > startup

The internal parameter _ kgl_large_heap_warning_threshold plays this role. Restart the database after modifying the parameters, and the error message no longer appears.

After reading this article, I believe you have a certain understanding of "what are the faults of Red Hat 6.5. installation of Oracle 10g". If you want to know more about it, welcome to follow the industry information channel. Thank you for your reading!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.