本文共 44285 字,大约阅读时间需要 147 分钟。
Installing Oracle9i 32-bit on Red Hat Enterprise Linux Advanced Server 4, 3, 2.1, and on Red Hat 9, 8.0, 7.3, 7.2, 7.1 (x86)
Here is a summary (HOWTO) how I installed: Oracle 9iR2 (9.2.0.6.0) 32-bit Database on Red Hat Advanced Server 4 (x86, kernel 2.6.9-5.EL, glibc-2.3.4-2) Oracle 9iR2 (9.2.0) 32-bit Database on Red Hat Advanced Server 3 (x86, kernel 2.4.21-4.EL, glibc 2.3.2-95.3) Oracle 9iR2 (9.2.0) 32-bit Database on Red Hat Advanced Server 2.1 (x86, kernel 2.4.9-e.3, glibc 2.2.4-26) Oracle 9iR2 (9.2.0) 32-bit Database on Red Hat 9 (x86, kernel kernel-2.4.20-6, glibc 2.3.2-5) Oracle 9iR2 (9.2.0) 32-bit Database on Red Hat 8.0 (x86, kernel 2.4.18-18.8.0, glibc 2.2.93-5) Oracle 9iR2 (9.2.0) 32-bit Database on Red Hat 7.3 (x86, kernel 2.4.18-3, glibc 2.2.5-34) Oracle 9iR1 (9.0.1) 32-bit Database on Red Hat 7.3 (x86, kernel 2.4.18-3, glibc 2.2.5-34) Oracle 9iR1 (9.0.1) 32-bit Database on Red Hat 7.2 (x86, kernel 2.4.7-10, glibc 2.2.4-13) Oracle 9iR1 (9.0.1) 32-bit Database on Red Hat 7.1 (x86, kernel 2.4.2-2, glibc 2.2.2-10)
People recommended this installation guide also for Red Hat Fedora Core 2. Validation/Certification: For Validations/Certifications, check the following links: Errors and Problems: Some of the Oracle errors and problems covered here were only experienced in connection with 9i (9.0.1) and some only with 9iR2 (9.2.0). But since I cannot say for sure that a 9i (9.0.1) installation error will never show up during 9iR2 (9.2.0) installation, I simply kept all errors and problems listed together, see and . Red Hat Enterprise Linux Advanced Server 3 (RHEL AS 3) In order to install an Oracle9iR2 database on RH AS 3, the "Oracle9iR2 Patch Set 3 9.2.0.4.0" patchset and some other patches must be applied. Some errors can only be fixed by applying the 9.2.0.4 patchset. For more information, see . Red Hat 9: Red Hat 9 includes the Native POSIX Thread Library (NPTL) which is an improved implementation of POSIX threads for Linux. But using NPTL will cause several problems for Oracle applications. Note that Oracle9i has not been certified on Red Hat 9! So to fix this problem, you can set the environment variable LD_ASSUME_KERNEL to 2.4.1, which means that the old "Linuxthreads with floating stacks" implementation will be used. Otherwise the Oracle installer runInstaller will hang, the Database Configuration Assistant dbca won't start etc.; see for more information. To see where this environment variable can be set, see . For more information on LD_ASSUME_KERNEL, see . NOTE: Before you install Oracle9iR2, make sure that you first read the information about the error message "Error in invoking target install of make file /u01/app/oracle/product/9.2.0/network/lib/ins_oemagent.mk" in the section! Red Hat 8.0: The only problem I experienced with Oracle 9iR2 (9.2.0) on Red Hat 8.0 was: "Error in invoking target install of makefile /u01/app/oracle/product/9.2.0/ctx/lib/ins_ctx.mk" But this does not necessarily mean that you won't see other problems described here. See for more information. This article covers the following subjects and steps: * * * * * * * * * * * * * * * * * * * *zcat lnx_920_disk1.cpio.gz | cpio -idmv zcat lnx_920_disk2.cpio.gz | cpio -idmv zcat lnx_920_disk3.cpio.gz | cpio -idmvTwo step procedure:
# Uncompress # Unpack the downloaded files:For Oracle9i (9.0.1): One step procedure (uses less disk space and is faster): Two step procedure:
# Uncompress # Unpack the downloaded files:Now you should have 3 directories containing installation files:
Disk1Disk2Disk3I executed the following commands when I burned the 3 CDs: (You can get the dev numbers when you execute cdrecord -scanbus).
ORA-27123: unable to attach to shared memory segment.I temporarely increased the shmmax setting for the kernel by executing the following command:
$ # 33554432# # 1073741824It is recommended to increase the shmmax setting permanently for Oracle. For more information, see . For more information on optimizing shared memory settings for Oracle databases on Linux, see . These parameters apply to all Red Hat Linux versions. But note that except for the shmmax parameter, these parameter do not need to be changed for installing Oracle on Linux. But you might want to adjust all shared memory settings later to optimize the server for Oracle.
$If you do not have enough space in the /tmp directory, you can temporarily create a tmp directory in another filesystem. Here is how you can do this:
# used by Oracle# used by Linux programs like the linker "ld"When you are done with your Oracle installation, shutdown Oracle and remove the temporary directory:
"Error invoking target install of makefile /u01/app/oracle/product/9.0.1/plsql/lib/ins_plsql.mk"And fix this problem as described in . I recommend this approach since it obviates the need to change binutils.
su - rootrpm -Uvh --force --nodeps binutils-2.10.0.18-1.i386.rpmWhen you are done with the Oracle installation, you upgrade your binutil RPM back to the version you had before you downgraded. E.g. on the Red Hat 7.2 server I did:
rpm -Uvh --force --nodeps binutils-2.11.90.0.8-9.i386.rpm
$ Archive: p4198954_21_LINUX.zip creating: 4198954/ inflating: 4198954/compat-oracle-rhel4-1.0-5.i386.rpm inflating: 4198954/compat-libcwait-2.0-2.i386.rpm inflating: 4198954/README.txt#Note that the compat-oracle-rhel4 and compat-libcwait packages require the xorg-x11-deprecated-libs and xorg-x11-deprecated-libs-devel packages, see above. To install the two RPMs from the 4198954 patch, run:
#
# group of users to be granted with SYSDBA system privilege# group owner of Oracle filesFor more information on the "oinstall" group account, see .
### Use the "Linuxthreads with floating stacks" implementation instead of NPTL: # # # Oracle Environment# export TNS_ADMIN= Set if sqlnet.ora, tnsnames.ora, etc. are not in $ORACLE_HOME/network/admin# Set shell search pathsI successfully installed Oracle9iR2 without setting the following CLASSPATH environment variable:
# CLASSPATH=$ORACLE_HOME/JRE:$ORACLE_HOME/jlib:$ORACLE_HOME/rdbms/jlib# CLASSPATH=$CLASSPATH:$ORACLE_HOME/network/jlib# export CLASSPATHYou can put these environment settings at the end of the ~oracle/.bash_profile file if you use bash. By this way you don't have to set the environment variables again when you login as "oracle", or when you switch to the user "oracle" by executing " su - oracle".
yourdesktop:user$Step 2: Open a new window and login to the Oracle server " oracleserver" as root. This window will be used for mounting and unmounting the Oracle CDs.
oracleserver:$ oracleserver:root#Step 3: From the console of your Oracle server " oracleserver" where you will run runInstaller, execute the following commands:
oracleserver:$ oracleserver:oracle$Step 4: Now execute runInstaller as "oracle". Do not cd to /mnt/cdrom !!
oracleserver:oracle$NOTE 1: If you use for example Red Hat Fedora Core 3 as your desktop and you want to install the database on another machine, then you need to set the DisallowTCP entry in /etc/X11/gdm/gdm.conf for the GNOME Display Manager to read: After that you need to restart your X server. I usually do this with the init command: NOTE 2: Don't run runInstaller for Red Hat Enterprise Linux Advanced Server 3 (RHEL AS 3) yet! See for more information.
You could also use "dba" which I do not recommend for security reasons. For more information on the "oinstall" group account, see .- Full path name for Oracle Home: etc.
# if g++ doesn't exist, then gcc-c++ was not installedWhen you execute runInstaller from the Oracle 9iR2 (9.2.0) CD, you will get the following error message: To resolve the __libc_wait symbol issue, download the p3006854_9204 patch p3006854_9204_LINUX.zip from . See bug 3006854 for more information. To apply the patch, run
# Archive: p3006854_9204_LINUX.zip creating: 3006854/ inflating: 3006854/rhel3_pre_install.sh inflating: 3006854/README.txt# # Applying patch...Patch successfully applied#NOTE: If you get the following error when you run rhel3_pre_install.sh: Then you forgot to install or link gcc, see above. This means you can't start any binaries any more:
###To fix that, run the echo command which is a built-in shell command:
#And start over again. Now runInstaller can be started from the CD:
$ # it is important that this variable is set!2.4.1$ - Welcome Screen: - Inventory Location: - Unix Group Name: - File Locations: - Available Products: - Installation Types: - Available Products: - Components Locations: - Privileged Operating System Groups: - Oracle Managent Server Repository: - Create database: - Summary: - Configuration tools: -You may get the following errors: Error in invoking target install of makefile /u01/app/oracle/product/9.2.0/network/lib/ins_oemagent.mk. The /u01/app/oracle/product/9.2.0/install/make.log file reads: Click ignore. This will be fixed by applying the patch 3119415 after the 9.2.0.4 patchset has been applied. You won't be able to apply the patch 3119415 at this time since the file /u01/app/oracle/oraInventory/ContentsXML/comps.xml doesn't exist yet. Error in invoking target install of makefile /u01/app/oracle/product/9.2.0/ctx/lib/ins_ctx.mk. The /u01/app/oracle/product/9.2.0/install/make.log file reads: Click ignore. This is fixed by applying the 9.2.0.4 patchset. To patch Oracle9iR2, download the Oracle 9i Release 2 Patch Set 3 Version 9.2.0.4.0 for Linux x86 from . Copy the downloaded " p3095277_9204_LINUX.zip" file to e.g. /tmp and run the following command:
$ $ $ Archive: p3095277_9204_LINUX.zip inflating: 9204_lnx32_release.cpio inflating: README.html inflating: patchnote.css$$ Disk1/stage/locksDisk1/stage/Patches/oracle.apache.isqlplus/9.2.0.4.0/1/DataFiles/bin.1.1.jarDisk1/stage/Patches/oracle.apache.isqlplus/9.2.0.4.0/1/DataFiles/lib.1.1.jar...To patch the runInstaller, run:
$ # it is important that this variable is set!2.4.1$ $ - Welcome Screen: - File Locations: - Available Products: - Components Locations: - Summary: -To patch Oracle9iR2, run:
$ # it is important that this variable is set!2.4.1$ $ - Welcome Screen: - File Locations: - Available Products: - Summary: -You may get the following error: Error in invoking target install of makefile /u01/app/oracle/product/9.2.0/network/lib/ins_oemagent.mk. The /u01/app/oracle/product/9.2.0/install/make.log file reads: Click ignore. This will be fixed by applying the patch 3119415 after the 9.2.0.4 patchset has been applied. The patch 3119415 cannot be applied while the patch process for the 9.2.0.4 patchset is running. After the 9.2.0.4 patchset has been applied, download the patch p3119415_9204_LINUX.zip from . See bug 3119415 for more information. Also, download the opatch Release 2.2.0 utility from . See bug 2617419 for more information. To install opatch, run:
$ $ $Before you apply the 3119415 patch, you need to make sure the fuser binary can be found by the oracle user, see the PATH environment variable below. Otherwise the patch can't be applied because the fuser binary is used by opatch. To apply the 3119415 patch, run
$ $ $ $ # the patch needs "fuser" which is located in /sbin$ /tmp/OPatch/opatch$Now you should be able to create a database with dbca: When you run "agentctl start" (Oracle 9.2.0.4), dbsnmp will crash:
$ $To resolve this problem, apply the patch p3238244_9204_LINUX.zip from . See bug/patch 3238244 for more information. Before you apply the patch, make sure the instance is down! Also make sure the opatch script. appears in your $PATH. See for information on getting and installing opatch. To verify if opatch is in your $PATH, run the which command:
$ $ /tmp/OPatch/opatch$To apply now the patch, run:
$ $ $ $ # the patch needs "fuser" which is located in /sbin$Now you need to relink dbsnmp. This is the binary that crashed when running agentctl start. To find which makefile handles the linking of dbsnmp, you can run:
$ $ /u01/app/oracle/product/9.2.0/network/lib/ins_oemagent.mk/u01/app/oracle/product/9.2.0/network/lib/env_oemagent.mk$I relinked dbsnmp and all associated executables which are maintained by the ins_oemagent.mk makefile:
$ $ $Now you should be able to start the agent:
$ $NOTE: Don't forget to undo the changes (links) to /usr/bin/gcc and /usr/bin/g++ if you don't need it any more. Also don't forget the /etc/ld.so.preload file.
$ $ 2.4.19$Now launch runInstaller:
$ 2.4.19$ - Welcome Screen: - Inventory Location: - Unix Group Name: - File Locations: - Available Products: - Installation Types: - Available Products: - Components Locations: - Privileged Operating System Groups: - Oracle Managent Server Repository: - Create database: - Summary:Download the patch 3948480 (Oracle9i Patch Set Release 2 (9.2.0.6) Patch Set 5) from and execute the following commands:
$ $ $ Archive: p3948480_9206_LINUX.zip creating: Disk1/ creating: Disk1/stage/ creating: Disk1/stage/Patches/...Now download the patch 4188455 from . This patch is needed for launching the runInstaller that came with the patch 3948480 we just downloaded above.
$ $ $ Archive: p4188455_10103_LINUX.zip inflating: oraparam.ini inflating: README.txt$The /tmp/oraparam.ini file will now be used for launching the runInstaller that came with the patch 3948480. To patch the runInstaller itself, run:
$ 2.4.19$ - Welcome Screen: - File Locations: - Available Products: - Summary: -Ensure that no Oracle processes are running: Now to patch Oracle9iR2, run:
$ # it is important that this variable is set!2.4.19$ - Welcome Screen: - File Locations: - Available Products: - Summary: -After the 9.2.0.6 patchset has been applied, download the patch 4190568 from . Also, download the opatch utility for release 10.1.0.2 (patch 2617419) from . To install opatch, run:
$ $ $ $To apply the 4190568 patch, run
$ $ $ $If you intend to use Direct I/O Support, you must also download and apply patch 2448994. Now you should be able to create a database with dbca: When dbca died on my system with the following error: I executed the following command: and restarted dbca. If you know a better solution, let me know!
For instance, to startup the database, run the following commands:
oracle$ SQL> SQL>The slash connects you to the schema owned by SYS. So in this example you will be connected to the schema owned by SYS with the privilege SYSDBA. SYSDBA gives you the following privileges: - sysoper privileges WITH ADMIN OPTION - create database - recover database until $ORACLE_HOME/bin/dbstart and $ORACLE_HOME/bin/dbshut You can also use $ORACLE_HOME/bin/dbstart to startup the database, and $ORACLE_HOME/bin/dbshut to shutdown the database. You can place $ORACLE_HOME/bin/dbstart into the /etc/rc.d/rc.local boot script. to automatically bring up the database at system boot time. To get $ORACLE_HOME/bin/dbstart and $ORACLE_HOME/bin/dbshut working, you need to change the third field for your Oracle SID in /etc/oratab from "N" to "Y". For example, for the Oracle SID "test" I changed the line in /etc/oratab from:
test:/u01/app/oracle/product/9.2.0:to read:
test:/u01/app/oracle/product/9.2.0:In some cases for 9.2.0 I also had to copy the init file for my SID "test" from /u01/app/oracle/admin/test/pfile to $ORACLE_HOME/dbs to get dbstart and dbshut working: But first make sure if your init file already exists in $ORACLE_HOME/dbs!
Xlib: connection to ":0.0" refused by serverXlib: Client is not authorized to connect to ServerIn this case, I always had to kill runInstaller in Oracle9iR1 (9.0.1) which was still running in the background. If I didn't do this in 9.0.1, runInstaller didn't completely come up any more without displaying any error messages. You might also want to clean up /tmp/OraInstall.
First check always the error logs for 9.2.0 in /tmp/OraInstall (e.g /tmp/OraInstall2002-07-04_09-50-19PM), and for 9.0.1 in /tmp/OraInstall. When you get make problems, check also the file $ORACLE_HOME/install/make.log.
Make sure that gcc is installed on your system:$ /usr/bin/gccHere is the command to find the RPM package name for /usr/bin/gcc:$ gcc-2.96-98Check also the other error messages below. See also for more information.
I saw this error only when I installed Oracle9iR2 ( 9.2.0). This was also the only problem I experienced with Oracle 9i R2 on Red Hat 8.0. However, this does not necessarily mean that you won't experience other problems described here. When I had this problem, the following errors showed up in $ORACLE_HOME/install/make.log:/lib/libdl.so.2: undefined reference to `_dl_addr@GLIBC_PRIVATE' /lib/libdl.so.2: undefined reference to `_dl_open@GLIBC_PRIVATE' /lib/libdl.so.2: undefined reference to `_dl_close@GLIBC_PRIVATE' /lib/libdl.so.2: undefined reference to `_dl_sym@GLIBC_PRIVATE' /lib/libdl.so.2: undefined reference to `_dl_vsym@GLIBC_PRIVATE'This error comes up when the following step is executed:/usr/bin/make -f ins_ctx.mk install ORACLE_HOME=/u01/app/oracle/product/9.2.0Edit the file $ORACLE_HOME/ctx/lib/env_ctx.mk, go to " INSO_LINK =", and add a " $(LDLIBFLAG)dl" to the line and save it. Here is the full line with the added " $(LDLIBFLAG)dl" flag: INSO_LINK = -L$(CTXLIB) $(LDLIBFLAG)m $(LDLIBFLAG)dl $(LDLIBFLAG)sc_ca $(LDLIBFLAG)sc_fa $(LDLIBFLAG)sc_ex $(LDLIBFLAG)sc_da $(LDLIBFLAG)sc_ut $(LDLIBFLAG)sc_ch $(LDLIBFLAG)sc_fi $(LLIBCTXHX) $(LDLIBFLAG)c -Wl,-rpath,$(CTXHOME)lib $(CORELIBS) $(COMPEOBJS) After that hit retry in the error popup. If this didn't work, then try the following: Edit the file $ORACLE_HOME/ctx/lib/env_ctx.mk again, go to " INSO_LINK =", remove the above entry you made and add a " `cat $(LIBHOME)/sysliblist`" to the line and save it. Here is the full line with the added " `cat $(LIBHOME)/sysliblist`" string: INSO_LINK = -L$(CTXLIB) $(LDLIBFLAG)m `cat $(LIBHOME)/sysliblist` $(LDLIBFLAG)sc_ca $(LDLIBFLAG)sc_fa $(LDLIBFLAG)sc_ex $(LDLIBFLAG)sc_da $(LDLIBFLAG)sc_ut $(LDLIBFLAG)sc_ch $(LDLIBFLAG)sc_fi $(LLIBCTXHX) $(LDLIBFLAG)c -Wl,-rpath,$(CTXHOME)lib $(CORELIBS) $(COMPEOBJS) After that hit retry in the error popup.
I saw this error only when I installed Oracle 9i R2 ( 9.2.0). This error message came up when the Oracle Database Configuration Assistant was running. I executed the following command to temporarily increase the maximum shared memory size:# 33554432# 1073741824#Then click "Retry" for the Oracle Database Configuration Assistant. It is recommended to increase the shmmax setting permanently for Oracle9i. So if you want to increase the maximum shared memory size permanently, add the following line to the /etc/sysctl.conf file: For more information on setting shared memory parameters for Oracle, see .
I saw this error when I've run the "Database Configuration Assistant" and " sqlplus". When the "Database Configuration Assistant" gave me this error during Oracle9iR2 (9.2.0) installation on Red Hat 2.1 AS, I simply removed the shared memory segments owned by the Oracle user and I restarted the "Database Configuration Assistant". I'm not sure if this is the right way but it always worked for me. Here is what I did to get the "Database Configuration Assistant" running again: Database Configuration Assistant: I executed the ipcs command to get the address of the shared memory segments that have been allocated by Oracle:$ # ------ Shared Memory Segments --------key shmid owner perms bytes nattch status0x00000000 0 root 600 196608 20x00000001 32769 root 600 655360 20x00000000 458755 oracle 660 4194304 00x00000000 491524 oracle 660 33554432 00x00000000 524293 oracle 660 33554432 00x00000000 557062 oracle 660 33554432 00x00000000 589831 oracle 660 33554432 00x00000000 622600 oracle 660 33554432 00x00000000 655369 oracle 660 33554432 00x00000000 688138 oracle 660 33554432 00x3ecee0b0 720907 oracle 660 4194304 0------ Semaphore Arrays --------key semid owner perms nsems status------ Message Queues --------key msqid owner perms used-bytes messages#Then I removed all shared memory segments that were owned by the Oracle user during the installation with the following command:#After that I restarted the "Database Configuration Assistant". Once the installation was done I immediately restarted the DB as well. Caveat: I'm not sure if this procedure can cause any further problems if this is done during the installation. But so far I haven't seen any issues with this approach. sqlplus: If you get this problem in connection with sqlplus, then simply make sure that the database is down and exit sqlplus. After that, follow the procedure above by removing all shared memory segments that belong to the Oracle user. To my knowledge, this should not cause any problems. For more information on shared memory segments, see . NOTE: To solve this problem permanently, increase the kernel shmmax size. For more information, see and .
I saw this error only when I installed Oracle 9i ( 9.0.1). People have sent me emails pointing out that the following solution also works for Mandrake 8.1, Mandrake 8.2, and for SuSE 8.0. Edit the file $ORACLE_HOME/bin/genclntsh and change the following line:LD_SELF_CONTAINED="-z defs"to read: After that run the script. $ORACLE_HOME/bin/genclntsh as the user "oracle" and not as the user "root". Also make sure you have all the Oracle environments set correctly!$ $ Created /u01/app/oracle/product/9.0.1/lib/libclntst9.a$After that hit Retry in the error dialog window. This always worked for me. Here is Oracle's official solution for Oracle 9iR1 and 9iR1 iAS on RedHat 2.1 Advanced Server:
If you see this error on Red Hat Enterprise Linux 3, follow the guideline at . On Red Hat 9 I performed the following steps here when the ORACLE_HOME/install/make.log file contained the error messages:... /u01/app/oracle/product/9.2.0/network/lib/libnmi.a(snmitcln.o)(.text+0x159d): In function `Nls_ScanCmd': : undefined reference to `__ctype_b' /u01/app/oracle/product/9.2.0/network/lib/libnmi.a(snmitcln.o)(.text+0x1603): more undefined references to `__ctype_b' followThe issue here is that __ctype_b() is actually gone for __ctype_b_loc() because Red Hat uses a new locale model. However, in libc.so, __ctype_b is still exported as compatibility symbol; at least that's the case with RH 9 glibc-2.3.2-5. And here is the reason why some people have this problem with Red Hat 9 and why some don't: When you bought the Red Hat 9 CDs in a store, then you will probably find glibc-2.3.2-5.i686.rpm on the first CD. This glibc version exports __ctype_b():$ /lib/i686/libc.so.6/lib/libc.so.6/lib/tls/libc.so.6$ 001315f8 D __ctype_b00022340 T __ctype_b_loc$ 00133c58 D __ctype_b000223a0 T __ctype_b_loc$But when you downloaded Red Hat 9 from redhat.com or from one of the mirror sites, then you will find glibc-2.3.2-11.9.i686.rpm on the image. This glibc version does not export __ctype_b(). This is also the case with glibc-devel-2.3.2-27.9.i386.rpm.$ /lib/i686/libc.so.6/lib/libc.so.6/lib/tls/libc.so.6$ 00131718 D __ctype_b@GLIBC_2.0000223a0 T __ctype_b_loc$ 00133d58 D __ctype_b@GLIBC_2.0000223f0 T __ctype_b_loc$Check the glibc version on your system: First check if the glibc packages on your RH 9 system work with the Oracle installer:$If you got the following error mesages:package glibc-2.3.2-5 is not installed package glibc-common-2.3.2-5 is not installed package glibc-devel-2.3.2-5 is not installedthen you have glibc packages on your system that don't work with the Oracle installer and you need to follow the "Work Around" procedure here. But if your system has the 2.3.2-5 glibc versions installed, then you are fine and you don't need to follow the described "Work Around" procedure! Work Around Procedure: Since I was not able to find the glibc-2.3.2-5 RPMs available for download, I'm making the RPMs available on my website. These RPMs are copies of the glibc RPMs that came with the RH 9 CDs I bought in the store. I do not recommend to use any of the "compat" RPMs from older Red Hat distributions since RH 9 contains major changes. Here is the procedure for installing glibc-2.3.2-5 temporarely on your RH 9 server: Download the 2.3.2-5 glibc RPMs from on my web site. First make sure if these downloaded RPM's are not corrupt and if they were really built and signed by Red Hat. You never know if someone fiddled with these RPMs or replaced them. To ensure the integrity and origin of these Red Hat's RPMs, run the following commands:$ # # add Red Hat's PGP public key to the RPM database # glibc-2.3.2-5.i686.rpm: (sha1) dsa sha1 md5 gpg OK glibc-common-2.3.2-5.i386.rpm: (sha1) dsa sha1 md5 gpg OK glibc-devel-2.3.2-5.i386.rpm: (sha1) dsa sha1 md5 gpg OK #Downgrade glibc, glibc-common, and glibc-devel:#If you get the following error:error: Failed dependencies: glibc = 2.3.2-11.9 is needed by (installed) glibc-debug-2.3.2-11.9 glibc = 2.3.2-11.9 is needed by (installed) glibc-utils-2.3.2-11.9 glibc-devel = 2.3.2-11.9 is needed by (installed) glibc-debug-2.3.2-11.9 glibc-devel = 2.3.2-11.9 is needed by (installed) nptl-devel-2.3.2-11.9then you can temporarily remove these RPMs (glibc-debug, glibc-utils, nptl-devel) from your system until you upgrade the glibc RPMs after your Oracle installation:#Now try to run runInstaller again. After Oracle has been installed, you can upgrade glibc, glibc-common, and glibc-devel again. For example:#According to Red Hat, binary compatibility in Red Hat Linux is always guaranteed for binaries and shared libraries accross releases, but not for .o files nor .a files. However, compatibility is guaranteed for .o files and .a files. _within_ a realease. Since glibc-2.3.2-5 and glibc-2.3.2-11.9 are from the same release, compatibility should be guaranteed for .o files (Oracle's .o files which have been created during the Oracle installation) and .a files. This means that Oracle should be fine when you upgrade glibc after the Oracle installation. If you have any problems or issues with this solution, or if you have any comments, please let me know. You can find my email address at the bottom of this web site.
$ agentctl start
You are probably trying to start the agent on RH AS 3. See how to resolve it.
$ dbcaOr on e.g. RHEL4:
If this happens, try the following:$Now try to restart dbca. Another option is to edit $ORACLE_HOME/bin/dbca and to put the following lines under comment except the line marked in blue:# if [ -f /etc/rac_on ]; then # Run DBCA # else # Run DBCA # $JRE_DIR/bin/jre -DORACLE_HOME=$OH ... # fiNow try to restart dbca.
gcc -o /u01/app/oracle/product/9.2.0/rdbms/lib/oracle -L/u01/app/oracle/product/9.2.0/rdbms/lib/ ......
I've seen this error on RH AS 3. To fix the linking problem, I executed the following commands:# # # #Now you should be able to relink the oracle binary again. Once you are done, make sure to revert back the changes you've made above:# #
You are probably trying to run a 64-bit Oracle version on a 32-bit Linux system. Make sure you downloaded the right Oracle version for your Linux system. To check if runInstaller is a 32-bit binary or a 64-bit binary, run the following command:$ $ install/linux/runInstaller: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.0.0, dynamically linked (uses shared libs), not strippedTo check if your Linux system is 32-bit system or a 64-bit system, run e.g. the following command:$ /sbin/init: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.2.5, dynamically linked (uses shared libs), not stripped
This problem comes up on RH 9 and on RH AS 3. You probably forgot to set the environment variable LD_ASSUME_KERNEL to 2.4.1. To rectify this problem, run the following command and restart runInstaller:oracle$For more information on this issue, see .
You are probably running the wrong rman binary which belongs to the XFree86-devel RPM:$ /usr/X11R6/bin/rman
I saw this error only with Oracle 9i R2 ( 9.2.0) when It tried to start the database with dbstart. I copied the init file for my SID "test" from /u01/app/oracle/admin/test/pfile to $ORACLE_HOME/dbs to get dbstart and dbshut working:
This happens if you didn't burn your CD correctly. Either you burn your CD again to include dot files or you copy the .extract_args file from your downloaded image to where runInstaller complains it is missing.
or
First check if ORACLE_SID is set correctly. If ORACLE_SID is set correctly, then you probably have a trailing slash "/" on the ORACLE_HOME environment variable. Remove it and try again to connect to sys (e.g from ORACLE_HOME=/u01/app/oracle/product/9.2.0/ to ORACLE_HOME=/u01/app/oracle/product/9.2.0).
You are probably running runInstaller on a 586 machine, or your AMD CPU gets recognized as 586 (e.g. AMD K6-III-400). You can check your machine (hardware) type by executing " uname -m". If you are not running on a 586 or on a AMD machine, try to link jre to java and see if this solves your problem. To rectify the problem with the 586 machine or with the AMD CPU, create a link for lib and bin from i586 to i686 and make the i686 directories read only. For example: Now restart runInstaller.
You probably forgot to install the compat-libstdc++ RPM which is a package for "Standard C++ libraries for Red Hat Linux 6.2 backwards compatibility". To rectify this problem, install the compat-libstdc++ RPM. For example on Red Hat 9: See also for more information.
I experienced this problem when I was running the Database Configuration Assistant dbca on Red Hat 9 without setting the LD_ASSUME_KERNEL environment variable. To rectify this problem, run the following command on Red Hat 9 and RHEL 3 and restart dbca:oracle$For more information on this issue, see .
$ lsnrctl startOR$ lsnrctl status
One of the possibilities are that the /var/tmp/.oracle directory doesn't exist. This happened with fresh new Oracle 9.2.0.4.0 CDs on RH AS 3. If that's the case, run the following commands: Now try to run lsnrctl start as oracle again.
Ensure you followed the instructions at very closely. NOTE: If you use for example Red Hat Fedora Core 3 as your desktop and you want to install the database on another machine, then you need to set the DisallowTCP entry in /etc/X11/gdm/gdm.conf for the GNOME Display Manager to read: After that you need to restart your X server. I usually do this with the init command:
You might want to check out the .Copyright © 2007 PUSCHITZ.COM The information provided on this website comes without warranty of any kind and is distributed AS IS. Every effort has been made to provide the information as accurate as possible, but no warranty or fitness is implied. The information may be incomplete, may contain errors or may have become out of date. The use of this information described herein is your responsibility, and to use it in your own environments do so at your own risk
来自 “ ITPUB博客 ” ,链接:http://blog.itpub.net/12330444/viewspace-607485/,如需转载,请注明出处,否则将追究法律责任。
转载于:http://blog.itpub.net/12330444/viewspace-607485/