RedHat Enterprise Client 5.3 安裝Oracle 9.2.0.4
Jun 07, 2016 pm 05:01 PM1、安裝Redhat Enterprise Client 5.3現(xiàn)在Redhat的安裝過程已經(jīng)做的非常的人性化,整個(gè)安裝過程不是太復(fù)雜。安裝過程中最要注意的
1、安裝RedHat Enterprise Client 5.3
現(xiàn)在Redhat的安裝過程已經(jīng)做的非常的人性化,整個(gè)安裝過程不是太復(fù)雜。安裝過程中最要注意的一個(gè)地方是Linux交換分區(qū)的設(shè)置,通常為物理內(nèi)存了1.5-2倍之間。
Redhat Enterprise Client 5.3的下載地址請(qǐng)參考本博的另外一個(gè)帖子。
2、檢查系統(tǒng)需求以及環(huán)境設(shè)置
這部分的系統(tǒng)需求特指的是redhat安裝Oracle9204對(duì)軟件包的需求。
2.1、軟件包檢查
下述軟件包都可以在Redhat Enterprise Client 5.3安裝光盤client目錄里找到,在系統(tǒng)里查詢這些軟件包,可以通過rpm -aq | grep 這類的命令查找,也可以通過系統(tǒng)自帶的“添加/刪除軟件包”程序在GNOME環(huán)境里查找。推薦使用后一種方法。
binutils-2.17.50.0.6-9.el5.i386.rpm
compat-libstdc++-33-3.2.3-61.i386.rpm
elfutils-0.137-3.el5.i386.rpm
elfutils-devel-0.137-3.el5.i386.rpm
gcc-4.1.2-44.el5.i386.rpm
gcc-c++-4.1.2-44.el5.i386.rpm
glibc-2.5-34.i386.rpm
glibc-common-2.5-34.i386.rpm
glibc-devel-2.5-34.i386.rpm
glibc-headers-2.5-34.i386.rpm
libaio-0.3.106-3.2.i386.rpm
libaio-devel-0.3.106-3.2.i386.rpm
libgcc-4.1.2-44.el5.i386.rpm
libstdc++-4.1.2-44.el5.i386.rpm
libstdc++-devel-4.1.2-44.el5.i386.rpm
make-3.81-3.el5.i386.rpm
sysstat-7.0.2-3.el5.i386.rpm
unixODBC-2.2.11-7.1.i386.rpm
unixODBC-devel-2.2.11-7.1.i386.rpm
注:對(duì)于系統(tǒng)缺少的軟件包,可以root用戶登錄,使用rpm -Uvh這個(gè)命令安裝。
2.2、修改Linux內(nèi)核參數(shù)
每個(gè)版本的Oracle對(duì)內(nèi)核參數(shù)的要求都不一樣,對(duì)這些內(nèi)核參數(shù)的修改最好的參考資料就是與Oracle版本對(duì)應(yīng)的官方文檔里提供的Installation Guide。如果你的版本不是oracle9204,,請(qǐng)參考與你版本對(duì)應(yīng)的Installation Guide。
以本次安裝的為例,以root身份登錄,修改/etc/sysctl.conf添加以下內(nèi)容
net.core.rmem_default = 4194304
net.core.rmem_max = 4194304
net.core.wmem_default = 262144
net.core.wmem_max = 262144
fs.file-max = 65536
net.ipv4.ip_local_port_range = 1024 65000
修改完成后,運(yùn)行sysctl -p使內(nèi)核參數(shù)生效。
3 、添加安裝Oracle用戶組
3.1、創(chuàng)建oracle安裝用戶組及用戶帳號(hào)
#groupadd dba
#groupadd oinstall
#useradd oracle -g oinstall -G dba
#passwd oracle
3.2、建立oracle安裝文件夾;以oracle用戶身份登錄
$mkdir /db
/db目錄用于安裝oracle
$mkdir /db/sw
/db/sw這個(gè)文件夾用于存放oracle安裝文件,本次安裝采用的是硬盤安裝方式。
3.3 、設(shè)置oracle用戶環(huán)境變量
以oracle用戶登錄后,編輯~/.bash_profile文件,整個(gè)文件內(nèi)容如下所示:
# .bash_profile
# Get the aliases and functions
if [ -f ~/.bashrc ]; then
. ~/.bashrc
fi
# User specific environment and startup programs
export ORACLE_SID=test
export ORACLE_BASE=/db/oracle
export ORACLE_HOME=$ORACLE_BASE/product/9.2.0.4/db_1
export? ORACLE_SID? ORACLE_BASE? ORACLE_HOME
PATH=$PATH:$ORACLE_HOME/bin:$HOME/bin
export?? PATH
3.4、以oracle身份下載三個(gè)文件
以oracle身份下載oracle9204的三個(gè)文件ship_9204_linux_disk1.cpio、ship_9204_linux_disk2.cpio、ship_9204_linux_disk3.cpio至/db/sw目錄,在/db/sw這個(gè)目錄下執(zhí)行下述命令:
cpio -idmv
cpio -idmv
cpio -idmv
執(zhí)行完命令后會(huì)生成Disk1、Disk2、Disk3三個(gè)目錄。
然后為這三個(gè)文件夾里的內(nèi)容指定可執(zhí)行,采用下述命令
chmod -r u+x Disk1
chmod -r u+x Disk2
chmod -r u+x Disk3
4、開始安裝oracle
以oracle身份登錄系統(tǒng),切換到/db/sw/Disk1目錄.
(以下是本人在安裝過程中出現(xiàn)的故障與解決方法)
4.1 故障一:運(yùn)行./runInstaller這個(gè)命令時(shí),出現(xiàn)下述錯(cuò)誤
Initializing Java Virtual Machine from /tmp/OraInstall2009-07-30_02-58-15AM/jre/bin/java. Please wait...
Error occurred during initialization of VM
Unable to load native library: /tmp/OraInstall2009-07-30_02-58-15AM/jre/lib/i386/libjava.so: symbol __libc_wait, version GLIBC_2.0 not defined in file libc.s
故障原因:
缺少p3006854_9204_LINUX補(bǔ)丁,
解決辦法:
下載p3006854_9204_LINUX補(bǔ)丁,以root身份登錄,執(zhí)行下述命令
unzip p3006854_9204_LINUX.zip
# cd 3006854
# sh rhel3_pre_install.sh
成功完成后,切換到oracle用戶繼續(xù)安裝,安裝界面出現(xiàn),卻是亂碼。

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

GTID (Global Transaction Identifier) ??solves the complexity of replication and failover in MySQL databases by assigning a unique identity to each transaction. 1. It simplifies replication management, automatically handles log files and locations, allowing slave servers to request transactions based on the last executed GTID. 2. Ensure consistency across servers, ensure that each transaction is applied only once on each server, and avoid data inconsistency. 3. Improve troubleshooting efficiency. GTID includes server UUID and serial number, which is convenient for tracking transaction flow and accurately locate problems. These three core advantages make MySQL replication more robust and easy to manage, significantly improving system reliability and data integrity.

MySQL main library failover mainly includes four steps. 1. Fault detection: Regularly check the main library process, connection status and simple query to determine whether it is downtime, set up a retry mechanism to avoid misjudgment, and can use tools such as MHA, Orchestrator or Keepalived to assist in detection; 2. Select the new main library: select the most suitable slave library to replace it according to the data synchronization progress (Seconds_Behind_Master), binlog data integrity, network delay and load conditions, and perform data compensation or manual intervention if necessary; 3. Switch topology: Point other slave libraries to the new master library, execute RESETMASTER or enable GTID, update the VIP, DNS or proxy configuration to

The steps to connect to the MySQL database are as follows: 1. Use the basic command format mysql-u username-p-h host address to connect, enter the username and password to log in; 2. If you need to directly enter the specified database, you can add the database name after the command, such as mysql-uroot-pmyproject; 3. If the port is not the default 3306, you need to add the -P parameter to specify the port number, such as mysql-uroot-p-h192.168.1.100-P3307; In addition, if you encounter a password error, you can re-enter it. If the connection fails, check the network, firewall or permission settings. If the client is missing, you can install mysql-client on Linux through the package manager. Master these commands

InnoDB is MySQL's default storage engine because it outperforms other engines such as MyISAM in terms of reliability, concurrency performance and crash recovery. 1. It supports transaction processing, follows ACID principles, ensures data integrity, and is suitable for key data scenarios such as financial records or user accounts; 2. It adopts row-level locks instead of table-level locks to improve performance and throughput in high concurrent write environments; 3. It has a crash recovery mechanism and automatic repair function, and supports foreign key constraints to ensure data consistency and reference integrity, and prevent isolated records and data inconsistencies.

MySQL's default transaction isolation level is RepeatableRead, which prevents dirty reads and non-repeatable reads through MVCC and gap locks, and avoids phantom reading in most cases; other major levels include read uncommitted (ReadUncommitted), allowing dirty reads but the fastest performance, 1. Read Committed (ReadCommitted) ensures that the submitted data is read but may encounter non-repeatable reads and phantom readings, 2. RepeatableRead default level ensures that multiple reads within the transaction are consistent, 3. Serialization (Serializable) the highest level, prevents other transactions from modifying data through locks, ensuring data integrity but sacrificing performance;

MySQL transactions follow ACID characteristics to ensure the reliability and consistency of database transactions. First, atomicity ensures that transactions are executed as an indivisible whole, either all succeed or all fail to roll back. For example, withdrawals and deposits must be completed or not occur at the same time in the transfer operation; second, consistency ensures that transactions transition the database from one valid state to another, and maintains the correct data logic through mechanisms such as constraints and triggers; third, isolation controls the visibility of multiple transactions when concurrent execution, prevents dirty reading, non-repeatable reading and fantasy reading. MySQL supports ReadUncommitted and ReadCommi.

IndexesinMySQLimprovequeryspeedbyenablingfasterdataretrieval.1.Theyreducedatascanned,allowingMySQLtoquicklylocaterelevantrowsinWHEREorORDERBYclauses,especiallyimportantforlargeorfrequentlyqueriedtables.2.Theyspeedupjoinsandsorting,makingJOINoperation

To add MySQL's bin directory to the system PATH, it needs to be configured according to the different operating systems. 1. Windows system: Find the bin folder in the MySQL installation directory (the default path is usually C:\ProgramFiles\MySQL\MySQLServerX.X\bin), right-click "This Computer" → "Properties" → "Advanced System Settings" → "Environment Variables", select Path in "System Variables" and edit it, add the MySQLbin path, save it and restart the command prompt and enter mysql--version verification; 2.macOS and Linux systems: Bash users edit ~/.bashrc or ~/.bash_
