Football and oracle series (5): The directX library missing in the voda14 game is similar to the oracle rpm package

Football and oracle series (5): The directX library missing in the voda14 game is similar to the oracle rpm package

**************************************** ******************************** **************

Original Works are from the blog of "Deep Blue blog". You are welcome to repost them. Please indicate the source when you repost them. Otherwise, the copyright will be held legally responsible.

Please leave a message or email (hyldba@163.com) indicating that there is an error. Thank you very much.

This article reprint must be kept here: http://blog.csdn.net/huangyanlong/article/details/39303989

Deep Blue blog: http://blog.csdn.net/huangyanlong

**************************************** **************************************** *******************

Football series introduction:

Since I have learned a few simple tricks for oracle, I cannot afford to sell it to anyone. Just after a meal, I joined several friends in the library. It is just a bit humorous and it can also be used to make fun of others.

Welcome to shoot bricks. This will be the biggest motivation for my growth.

Today, I want to briefly talk about oracle's rpm package, which is also due to today's "reinstalling the system ". Because the system was reinstalled, the semi A14 football game was reinstalled, which immediately caused a small problem. There is an analogy between this "minor game running problem" and "rpm package required for oracle Installation". Although the comparison between games and technologies is far-fetched, however, I think the "dependency" principle is still the same.

Next we will combine the process of solving the issue of ipva14 and re-migrate the rpm package process in oracle installation. When it comes to installing oracle databases, installing the rpm package is a headache for many beginners. If you have no experience installing the rpm package for the first time, it is difficult to complete the installation in one go, I usually search for summary documents on the Internet, but the summary documents are uneven. I think it is better to have a certain understanding of installation and then refer to them, in many cases, the installation ideas of the author of the document are different, so it is easy to mislead beginners to a certain extent. For example, in my personal opinion, I used to use yum for early installation of rpm packages. At 10 Gb, I felt quite comfortable, but at 11 GB, several rpm packages reported some problems when they were installed through yum. I was confused when I first found out. All these problems were due to the fact that I didn't have a deep understanding of yum at the time, blindly believe that yum can solve all dependencies. In fact, it is the most authoritative and simple way to do it in the order of official documents.

The following is a combination of oracle's rpm package, which records the process of solving the issue of the voda14 game. It will be a pleasure to help fifa game fans!

Scenario 1: fifa file oracle File

The downloaded javasa14 file (a file larger than 6 GB) is as follows:

After decompression, an error is returned, as shown below:

The error message is: the procedure entry point D3DXCreateEffectEx cocould not be located in The dynamic link library d3dx9_43.dll.

After the analysis, it was preliminarily determined that the system was modified because the installed WIN7 system is ghost, and the relevant direct plug-in may be missing. Therefore, we plan to download the DirectX Repair Tool. I can find the following online versions:

[Think about oracle]

File, which is easy to think of. Preparing the installation package is like a game installation package, as shown in:

After installation, if the relevant rpm package is not installed in Linux, the installation process is usually similar to the following:

(The image is retained when the package is missing for 10 Gb installation)

Let's take a look at the oracle errors when the rpm package is missing and the directX plug-in is missing on the iisa14. Is there any inspiration? Next let's take a look at the solution process.

Scenario 2: DirectX plugin repair and rpm package installation

Find the Repair Tool and install it to complete the directX repair, as shown below:

The C ++ library is automatically updated as follows:

After the repair is completed, as shown in:

(We can see that the missing directX files are all caused by the ghost version. O (others _ FILES) O Haha ~)

After the repair is completed, as shown in:

After the repair is completed, as shown in:

So far, the missing directX library has been repaired. Next, let's move on to oracle.

[Think about oracle]

Let's take a look at oracle's rpm package. Let's go to the official documentation and find the document index link first, as shown below:

After entering, find the installation preparation section, as shown below:

After entering the document, go down to the document content. Here we will add some usage instructions for the document. If you use the official document, you will find a lot of content, because it covers almost all the technical knowledge and introduction, so in the Process of use, we need to constantly learn to filter useful information from the document. Find the rpm package requirements as follows.

In fact, yum is not applicable to oracle Installation. For the dependency, we need to install the official documentation and find the corresponding package from the system disk. As follows:

After finding the relevant package, I used to write a seemingly lengthy but easy-to-understand script file for execution, as shown below:

Execute the script:

# Vi CentOS5.6-11g-script.sh

-- Script implements two functions

-- Function 1: Install the rpm package, record the log, and delete the package after installation.

-- Function 2: Check the installed rpm package and record the log

rpm -ivh binutils-2.17.50.0.6-14.el5.x86_64.rpm >> rpm.log 2>&1rpm -ivh binutils-devel-2.17.50.0.6-14.el5.i386.rpm >> rpm.log 2>&1rpm -ivh binutils-devel-2.17.50.0.6-14.el5.x86_64.rpm >> rpm.log 2>&1rpm -ivh compat-libstdc++-33-3.2.3-61.i386.rpm >> rpm.log 2>&1rpm -ivh compat-libstdc++-33-3.2.3-61.x86_64.rpm >> rpm.log 2>&1rpm -ivh elfutils-libelf-0.137-3.el5.i386.rpm >> rpm.log 2>&1rpm -ivh elfutils-libelf-0.137-3.el5.x86_64.rpm >> rpm.log 2>&1rpm -ivh elfutils-libelf-devel-0.137-3.el5.i386.rpm >> rpm.log 2>&1rpm -ivh elfutils-libelf-devel-0.137-3.el5.x86_64.rpm >> rpm.log 2>&1rpm -ivh elfutils-libelf-devel-static-0.137-3.el5.i386.rpm >> rpm.log 2>&1rpm -ivh elfutils-libelf-devel-static-0.137-3.el5.x86_64.rpm >> rpm.log 2>&1rpm -ivh gcc-4.1.2-50.el5.x86_64.rpm >> rpm.log 2>&1rpm -ivh gcc-c++-4.1.2-50.el5.x86_64.rpm >> rpm.log 2>&1rpm -ivh glibc-2.5-58.i686.rpm >> rpm.log 2>&1rpm -ivh glibc-2.5-58.x86_64.rpm >> rpm.log 2>&1rpm -ivh glibc-common-2.5-58.x86_64.rpm >> rpm.log 2>&1rpm -ivh glibc-devel-2.5-58.i386.rpm >> rpm.log 2>&1rpm -ivh glibc-devel-2.5-58.x86_64.rpm >> rpm.log 2>&1rpm -ivh glibc-headers-2.5-58.x86_64.rpm >> rpm.log 2>&1rpm -ivh libaio-0.3.106-5.i386.rpm >> rpm.log 2>&1rpm -ivh libaio-0.3.106-5.x86_64.rpm >> rpm.log 2>&1rpm -ivh libaio-devel-0.3.106-5.i386.rpm >> rpm.log 2>&1rpm -ivh libaio-devel-0.3.106-5.x86_64.rpm >> rpm.log 2>&1rpm -ivh libao-0.8.6-7.i386.rpm >> rpm.log 2>&1rpm -ivh libao-0.8.6-7.x86_64.rpm >> rpm.log 2>&1rpm -ivh libgcc-4.1.2-50.el5.i386.rpm >> rpm.log 2>&1rpm -ivh libgcc-4.1.2-50.el5.x86_64.rpm >> rpm.log 2>&1rpm -ivh libstdc++-4.1.2-50.el5.i386.rpm >> rpm.log 2>&1rpm -ivh libstdc++-4.1.2-50.el5.x86_64.rpm >> rpm.log 2>&1rpm -ivh libstdc++-devel-4.1.2-50.el5.i386.rpm >> rpm.log 2>&1rpm -ivh libstdc++-devel-4.1.2-50.el5.x86_64.rpm >> rpm.log 2>&1rpm -ivh make-3.81-3.el5.x86_64.rpm >> rpm.log 2>&1rpm -ivh numactl-0.9.8-11.el5.i386.rpm >> rpm.log 2>&1rpm -ivh numactl-0.9.8-11.el5.x86_64.rpm >> rpm.log 2>&1rpm -ivh pdksh-5.2.14-36.el5.x86_64.rpm >> rpm.log 2>&1rpm -ivh sysstat-7.0.2-3.el5_5.1.x86_64.rpm >> rpm.log 2>&1rm -rf binutils-2.17.50.0.6-14.el5.x86_64.rpmrm -rf binutils-devel-2.17.50.0.6-14.el5.i386.rpmrm -rf binutils-devel-2.17.50.0.6-14.el5.x86_64.rpmrm -rf compat-libstdc++-33-3.2.3-61.i386.rpmrm -rf compat-libstdc++-33-3.2.3-61.x86_64.rpmrm -rf elfutils-libelf-0.137-3.el5.i386.rpmrm -rf elfutils-libelf-0.137-3.el5.x86_64.rpmrm -rf elfutils-libelf-devel-0.137-3.el5.i386.rpmrm -rf elfutils-libelf-devel-0.137-3.el5.x86_64.rpmrm -rf elfutils-libelf-devel-static-0.137-3.el5.i386.rpmrm -rf elfutils-libelf-devel-static-0.137-3.el5.x86_64.rpmrm -rf gcc-4.1.2-50.el5.x86_64.rpmrm -rf gcc-c++-4.1.2-50.el5.x86_64.rpmrm -rf glibc-2.5-58.i686.rpmrm -rf glibc-2.5-58.x86_64.rpmrm -rf glibc-common-2.5-58.x86_64.rpmrm -rf glibc-devel-2.5-58.i386.rpmrm -rf glibc-devel-2.5-58.x86_64.rpmrm -rf glibc-headers-2.5-58.x86_64.rpmrm -rf libaio-0.3.106-5.i386.rpmrm -rf libaio-0.3.106-5.x86_64.rpmrm -rf libaio-devel-0.3.106-5.i386.rpmrm -rf libaio-devel-0.3.106-5.x86_64.rpmrm -rf libao-0.8.6-7.i386.rpmrm -rf libao-0.8.6-7.x86_64.rpmrm -rf libgcc-4.1.2-50.el5.i386.rpmrm -rf libgcc-4.1.2-50.el5.x86_64.rpmrm -rf libstdc++-4.1.2-50.el5.i386.rpmrm -rf libstdc++-4.1.2-50.el5.x86_64.rpmrm -rf libstdc++-devel-4.1.2-50.el5.i386.rpmrm -rf libstdc++-devel-4.1.2-50.el5.x86_64.rpmrm -rf make-3.81-3.el5.x86_64.rpmrm -rf numactl-0.9.8-11.el5.i386.rpmrm -rf numactl-0.9.8-11.el5.x86_64.rpmrm -rf pdksh-5.2.14-36.el5.x86_64.rpmrm -rf sysstat-7.0.2-3.el5_5.1.x86_64.rpmrpm -qa|grep binutils >> queryrpm.log 2>&1rpm -qa|grep compat-libstdc >> queryrpm.log 2>&1rpm -qa|grep elfutils >> queryrpm.log 2>&1rpm -qa|grep gcc >> queryrpm.log 2>&1rpm -qa|grep glibc >> queryrpm.log 2>&1rpm -qa|grep kernel >> queryrpm.log 2>&1rpm -qa|grep ksh >> queryrpm.log 2>&1rpm -qa|grep libaio >> queryrpm.log 2>&1rpm -qa|grep libgcc >> queryrpm.log 2>&1rpm -qa|grep libgomp >> queryrpm.log 2>&1rpm -qa|grep libstdc++- >> queryrpm.log 2>&1rpm -qa|grep make >> queryrpm.log 2>&1rpm -qa|grep sysstat >> queryrpm.log 2>&1 

 

# Sh CentOS5.6-11g-script.sh

So far, the oracle rpm package has been installed. After modifying the relevant configuration according to the document, you can install oracle. after entering the oracle Installation interface, as shown below:

(Note: Please refer to the author's other documents for the complete oracle Installation Process)

Another happy event is that after the restoration of directory a14, you can resume the execution of the game (.exe file) and access the directory normally, as shown below:

The following is a simple comparison:

1. megaa14 games rely on the directX library;

2. oracle software depends on rpm packages (in Linux ).

**************************************** ******************************** **************

Original Works are from the blog of "Deep Blue blog". You are welcome to repost them. Please indicate the source when you repost them. Otherwise, the copyright will be held legally responsible.

Please leave a message or email (hyldba@163.com) indicating that there is an error. Thank you very much.

This article reprint must be kept here: http://blog.csdn.net/huangyanlong/article/details/39303989

Deep Blue blog: http://blog.csdn.net/huangyanlong

**************************************** **************************************** *******************

Chapter link:

Football and oracle series (1): 32-way zhoudianbing, overall view of group A Brazil smon process of oracle32 process Alliance

Football and oracle series (2)

Football and oracle series (3): oracle process rankings, the World Cup round is about to fight!

Football and oracle series (4): from Brazil to Germany, think of the different RAC topology comparison!