RedHat 5.8 安裝Oracle 11gR2_Grid集群
Jun 07, 2016 pm 05:26 PMRedHat 5.8 安裝Oracle 11gR2_Grid集群
首頁(yè) → 數(shù)據(jù)庫(kù)技術(shù)
背景:
閱讀新聞
RedHat 5.8 安裝Oracle 11gR2_Grid集群
[日期:2013-01-30] 來(lái)源:Linux社區(qū)? 作者:wuweilong [字體:]
RedHat 5.8 安裝Oracle 11gR2_Grid集群
1、 通過(guò)rpm安裝相應(yīng)軟件包:
rpm -ivh binutils-2*.i386.rpm
rpm -ivh binutils-2*.x86_64.rpm
rpm -ivh compat-libstdc++-33-*i*
rpm -ivh compat-libstdc++-33-x*
rpm -ivh elfutils-libelf-0*.i386.rpm
rpm -ivh elfutils-libelf-0*.x*
rpm -ivh elfutils-libelf-devel-0*.i386.rpm
rpm -ivh elfutils-libelf-devel-0.137-3.el5.x*
rpm -ivh compat-libstdc++-2*.i*.rpm
rpm -ivh compat-libstdc++-3*.i*.rpm
rpm -ivh compat-libstdc++-3*.x*.rpm
rpm -ivh gcc-4*.i*
rpm -ivh gcc-4*.x*
rpm -ivh gcc-4.1.2-52.el5.i386.rpm
rpm -ivh gcc-c++-*.x*.rpm
rpm -ivh gcc-c++-*.i*.rpm
rpm -ivh glibc-2.5-81.i*.rpm
rpm -ivh glibc-2.5-81.x*.rpm
rpm -ivh glibc-common-*.i*.rpm
rpm -ivh glibc-common-*.x*.rpm
rpm -ivh glibc-devel*.i*.rpm
rpm -ivh glibc-devel*.x*.rpm
rpm -ivh glibc-headers*.i*.rpm
rpm -ivh glibc-headers*.x*.rpm
rpm -ivh ksh-*.x*.rpm
rpm -ivh ksh-*.i*.rpm
rpm -ivh pdksh-*.i*.rpm
rpm -ivh pdksh-*.x*.rpm
rpm -ivh libaio-0*.i*.rpm
rpm -ivh libaio-0*.x*.rpm
rpm -ivh libaio-devel*.i*.rpm
rpm -ivh libaio-devel*.x*.rpm
rpm -ivh libgcc-4*.i*.rpm
rpm -ivh libgcc-4*.x*.rpm
rpm -ivh libstdc++-4*.i*.rpm
rpm -ivh libstdc++-4*.x*.rpm
rpm -ivh libstdc++-devel*.i*.rpm
rpm -ivh libstdc++-devel*.x*.rpm
rpm -ivh make-3*.i*.rpm
rpm -ivh make-3*.x*.rpm
rpm -ivh sysstat-*.i*.rpm
rpm -ivh sysstat-*.x*.rpm
rpm -ivh unixODBC-libs-*.i*.rpm
rpm -ivh unixODBC-libs-*.x*.rpm
rpm -ivh unixODBC-2*.i*.rpm
rpm -ivh unixODBC-2*.x*.rpm
rpm -ivh unixODBC-devel*.i*.rpm
rpm -ivh unixODBC-devel*.x*.rpm
--DNS相關(guān)軟件包
rpm -ivh bind-9*.i*.rpm
rpm -ivh bind-9*.x*.rpm
rpm -ivh bind-utils*.i*.rpm
rpm -ivh bind-utils*.x*.rpm
rpm -ivh caching-nameserver*.i*.rp
rpm -ivh caching-nameserver*.x*.rp
rpm -ivh system-config-bind*.i*.rpm
rpm -ivh system-config-bind*.rpm
rpm -ivh bind-chroot*.i*.rpm
rpm -ivh bind-chroot*.x*.rpm
rpm -ivh oracleasm-support-2.1.7-1.el5.i386.rpm
rpm -ivh oracleasm-2.6.18-308.el5-2.0.5-1.el5.i686.rpm
rpm -ivh oracleasmlib-2.0.4-1.el5.i386.rpm
?
2、修改主機(jī)名
[root@localhost Server]# vi /etc/sysconfig/network
NETWORKING=yes
NETWORKING_IPV6=no
HOSTNAME=grid01/grid02
?
3、配置host文件
[root@grid01 ~]# cat /etc/hosts
# Do not remove the following line, or variousprograms
# that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost
?
#public
172.168.9.15 grid01.prudentwoo.com grid01
172.168.9.16 grid02.prudentwoo.com grid02
?
#private
10.10.10.1 pri01.prudentwoo.com pri01
10.10.10.2 pri02.prudentwoo.com pri02
?
#virtual
172.168.9.21 vip01.prudentwoo.com vip01
172.168.9.22 vip02.prudentwoo.com vip02
?
#scan
172.168.9.17 scan.prudentwoo.com scan
172.168.9.18 scan.prudentwoo.com scan
172.168.9.19 scan.prudentwoo.com scan
172.168.9.20 scan.prudentwoo.com scan
ORA-01017/ORA-02063 DbLink建立錯(cuò)誤問(wèn)題分析及解決
批量遷移Oracle數(shù)據(jù)文件,日志文件及控制文件
相關(guān)資訊 ? ? ? 集群? RedHat 5.8? Oracle 11gR2_Grid?
圖片資訊 ? ? ?
本文評(píng)論 查看全部評(píng)論 (0)
評(píng)論聲明
最新資訊
本周熱門(mén)
Linux公社簡(jiǎn)介 - 廣告服務(wù) - 網(wǎng)站地圖 - 幫助信息 - 聯(lián)系我們
本站(LinuxIDC)所刊載文章不代表同意其說(shuō)法或描述,僅為提供更多信息,,也不構(gòu)成任何建議。
Copyright ? 2006-2011 Linux公社 All rights reserved 浙ICP備06018118號(hào)

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

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

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.

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_
