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

Editor to share with you what Oracle errors are, I believe that most people do not know much about it, so share this article for your reference, I hope you will learn a lot after reading this article, let's go to know it!

1 、 / downloads/database/install/.oui: / lib/ld-linux.so.2: bad ELF interpreter: No such file or directory

Solution: yum install y ld-linux.so.2

2 、 The user is root. Oracle Universal Installer cannot continue installation if the user is root.

Solution: log in to execute with oracle user

3 、 Checking swap space: 0 MB available, 150 MB required. Failed

Solution: dd if=/dev/zero of=/data/swap bs=1G count=18

Mkswap / data/swap & & swapon / data/swap

Vim / etc/fstab (add)

/ data/swap swap swap defaults 0 0

Mount-a

4 、 Checking monitor: must be configured to display at least 256 colorsChecking monitor: must configured to display at least 256 colors

Solution: yum whatprovides "* / xhost" according to the checked package, installation, similar

Yum install-y xorg-x11-server-utils-7.7-14.el7 (implementation of x11, which connects to x server when the underlying layer is running)

5. Xhost: unable to open display ""

Solution: yum install tigervnc-server (vnc service can log in to the graphical interface through a character terminal)

(root) vncserver & & enter password & & export DISPLAY=localhost:1

(oracle) vncserver & & enter the password

After starting vnc, I still couldn't solve the problem shown above, so I started to check it again.

Http://www.jb51.net/LINUXjishu/412923.html

Xhost + (allow all IP to intervene)

Color in yum install xdpyinfo / / automatic retrieval system

Execute xdpyinfo | grep name / / and then set the printed DISPLAY variable in oracle, similar to the following

6. Exception in thread "main" java.lang.UnsatisfiedLinkError: / tmp/OraInstall2017-03-13009-56-31AM/jdk/jre/lib/i386/xawt/libmawt.so: libXext.so.6: cannot open shared object file: No such file or directory

Solution: yum install libXext.i686 (oracle requires some 32-bit lib)

7. Unable to log in to vnc client

Login method 1: it's just that the login method is not ip:port, but ip:1 ip:2 1 and 2 session numbers can be seen by ps vnc

Login method 2: on the web side, enter ip:port, then enter ip:1, and login with password

Launch: vncserver: 1 (session number)

Close: vncserver-kill: 1 vncserver-kill: 2 (can only kill themselves under their own users)

Change password: vncpasswd: 1

8. This is a prerequisite condition to test whether the system certified architecture.?)

Expected Value: x86

Actual Value:x86_64

Solution: it means that the system is 64-bit and oracle uses 32-bit, which does not match. Although it can be solved with some patches, in order to use it normally in the future, it is better to use the next 64-bit.

9. This is a prere condition to test whether the OS kernel parameter "semmni" is properly set.?)

Expected Value:128

Actual Value:0

Solution: first of all, search your / etc/sysctl.conf to see if you have set sem. If so, just skip it. Oracle does not recognize it.

10 、 packge:pdksh-5.2.14

Solution: wget http://mirror.centos.org/centos/5/os/x86_64/CentOS/pdksh-5.2.14-37.el5_8.1.x86_64.rpm 64-bit

Wget ftp://rpmfind.net/linux/opensuse/distribution/13.1/repo/oss/suse/i586/pdksh-5.2.14-948.1.2.i586.rpm 32-bit

Rpm-ivh pdksh-5.2.14-37.el5_8.1.x86_64.rpm-force-nodeps

11 、 error while loading shared libraries: libclntsh.so.11.1:

Error while loading shared libraries: libaio.so.1: cannot open shared object file: No such file or directory

Solution: first, we can ldd sqlplus to see how the library file of the sqlplus soft chain is found.

Then find this library, according to the path found by ldd, do a soft chain.

12 、

Solution: wget http://install.com:8888/unixODBC-2.2.11-7.1.i386.rpm

Rpm-ivh-force unixODBC-2.2.11-7.1.i386.rpm

Wget http://mirror.centos.org/centos/5/os/i386/CentOS/unixODBC-devel-2.2.11-10.el5.i386.rpm

Rpm-ivh unixODBC-devel-2.2.11-10.el5.i386.rpm-nodeps-force

Wget ftp://ftp.pbone.net/mirror/www.whiteboxlinux.org/whitebox/4/en/updates/i386/libstdc++-3.4.6-11.i386.rpm

Rpm-ivh libstdc++-3.4.6-11.i386.rpm-force

Wget ftp://bo.mirror.garr.it/1/smeserver/releases/obsolete/7.1/smeos/i386/CentOS/RPMS/libgcc-3.4.6-3.i386.rpm

Wget ftp://ftp.pbone.net/mirror/www.whiteboxlinux.org/whitebox/4/en/updates/i386/libaio-devel-0.3.105-2.i386.rpm

Rpm-ivh libaio-devel-0.3.105-2.i386.rpm-force

Wget ftp://ftp.muug.mb.ca/mirror/centos/5.11/os/i386/CentOS/compat-libstdc++-33-3.2.3-61.i386.rpm

Rpm-ivh compat-libstdc++-33-3.2.3-61.i386.rpm-- force

Wget ftp://ftp.pbone.net/mirror/www.whiteboxlinux.org/whitebox/4/en/updates/i386/libaio-0.3.105-2.i386.rpm

Rpm-ivh libaio-0.3.105-2.i386.rpm-force

13. The repair option cannot be clicked

Go to the log file, / tmp/OraInstallxxxxx9-07PM/installActions2xxxxxx-07PM.log

Search for Error, or search for fixup, and you will find that the owner of the following file has changed, which should have changed when the user was deleted.

Chown-R oraclll / tmp/CVU_11.2.0.1.0_oracle/

14 、 ORA-12162: TNS:net service name is incorrectly specified:

Because other users are logged in, sid,export ORACLE_SID=xxx is not set up

15. INFO: / lib64/libstdc++.so.5: undefined reference to `memcpy@GLIBC_2.14'

INFO: collect2: error: ld returned 1 exit status

INFO: make: * [ctxhx] Error 1

On the Internet, it is said that glibc version 2.17 is too high (higher than 2.14). The solution: download the bread, the package contains a static link library: / usr/lib64/libc.a

Wget http://vault.centos.org/7.3.1611/updates/Source/SPackages/glibc-2.17-157.el7_3.1.src.rpm

Wget ftp://rpmfind.net/linux/centos/7.3.1611/os/x86_64/Packages/glibc-static-2.17-157.el7.x86_64.rpm

Rpm-ivh glibc-2.17-157.el7_3.1.src.rpm

Rpm-ivh glibc-static-2.17-157.el7.x86_64.rpm

Modify / usr/local/oracle/ctx/lib/ins_ctx.mk to set the

Ctxhx: $(CTXHXOBJ)

$(LINK_CTXHX) $(CTXHXOBJ) $(INSO_LINK)

Modified to:

Ctxhx: $(CTXHXOBJ)

-static $(LINK_CTXHX) $(CTXHXOBJ) $(INSO_LINK) / usr/lib64/stdc.a

Click Retry to continue with the installation.

16. Error in invoking target 'agent nmhs' of makefile' / usr/local/oracle/sysman/lib/ins_emagent.mk.'

Solution: add parameters to the linked libnnz11 library in makefile

Modify / u01/app/oracle/product/11.2.0/dbhome_1/sysman/lib/ins_emagent.mk to set the

Change $(MK_EMAGENT_NMECTL) to: $(MK_EMAGENT_NMECTL)-lnnz11

Click Retry to continue with the installation.

Installation successful!

17 、

SQL > conn / as sysdba

Connected to an idle instance.

SQL > startup

ORA-01078: failure in processing system parameters

LRM-00109: could not open parameter file'/ usr/local/oracle/dbs/initORCL2.ora'

First of all, make sure that your database startup oracle_sid is set to ORCL2, if not, change env.

Verification method: $ORACLE_BASE//admin/orasid = = orasid, that is, the sid when you start up

18. The client pl logs in to Database character set (AL32UTF8) and Client character set (ZHS16GBK) are different. Character set conversion may cause unexpected results.

Note: you can set the client character set through the NLS_LANG environment variable or the NLS_LANG registry key in HKEY_LOCAL_MACHINESOFTWAREORACLEKEY_Oracle_10

View the server character set: select userenv ('language') from dual

Open cmd and command regedit to open the registry. Find the path to the prompt in this article and find that the value of the NLS_LANG key is:

SIMPLIFIED CHINESE_CHINA.ZHS16GBK

Change to: SIMPLIFIED CHINESE_CHINA.AL32UTF8 or SIMPLIFIED AMERICAN_AMERICA.AL32UTF8

Another possibility is that you did not choose a custom installation when installing 11g.

Database character set (AL32UTF8) and Client character set (ZHS16GBK) are different. Character set conversion may cause unexpected results. Note: you can set the client character set through the NLS_LANG environment variable or the NLS_LANG registry key in HKEY_LOCAL_MACHINE/SOFTWARE/ORACLE/KEY_OraDb11g_home

SIMPLIFIED CHINESE_CHINA.ZHS16GBK contains AMERICAN_AMERICA.AL32UTF8.

This is a hassle, not a matter of changing the client character set. To change the character set of the database:

SQL > conn / as sysdba

SQL > shutdown immediate

SQL > startup mount

SQL > ALTER SYSTEM ENABLE RESTRICTED SESSION

SQL > ALTER SYSTEM SET JOB_QUEUE_PROCESSES=0

SQL > ALTER SYSTEM SET AQ_TM_PROCESSES=0

SQL > alter database open

SQL > ALTER DATABASE CHARACTER SET ZHS16GBK

ORA-12712: new character set must be a superset of old character set prompts our character set: the new character set must be a superset of the old character set, so we can skip checking the superset and make changes: SQL > ALTER DATABASE character set INTERNAL_USE ZHS16GBK

We see that this process is exactly the same as the internal process of the previous ALTER DATABASE CHARACTER SET operation.

In other words, the help provided by INTERNAL_USE is to make the Oracle database bypass the check of subset and superset.

SQL > select * from v$nls_parameters

SQL > shutdown immediate

SQL > startup

SQL > select * from v$nls_parameters

The above is all the contents of the article "what are the Oracle mistakes?" Thank you for reading! I believe we all have a certain understanding, hope to share the content to help you, if you want to learn more knowledge, welcome to follow the industry information channel!

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.