欢迎您访问程序员文章站本站旨在为大家提供分享程序员计算机编程知识!
您现在的位置是: 首页  >  数据库

Oracle Database RAC 11.2.0.3 for AIX6.1TL7安装记录

程序员文章站 2024-02-11 11:53:34
...

在AIX平台安装Oracle RAC就是个坑爹的事情,今日再次验证了这点,只因为bug太多!记录问题也只因为bug太多!强烈推荐及看好Oracl

>存储:IBM DS 5020
> 操作系统:

mzrac2@root[/oracle]oslevel -s

6100-07-00-0000
> Oracle Grid&Database:11.2.0.3

一.安装过程出现如下问题:

1.在检查过程中出现如下的告警:

Oracle Database RAC 11.2.0.3 for AIX6.1TL7安装记录


经过检查,在AIX6.1TL7上是不需要这两个补丁的,因此可以直接忽略。

2.安装Grid的时候出现如下的报错:

Oracle Database RAC 11.2.0.3 for AIX6.1TL7安装记录


点击"Retry"之后又可以顺利通过。

之后安装Database软件的时候比较顺利。

3.使用dbca创建数据库的时候问题又来了,创建过程中始终报ORA-03113的错误,如下图:

Oracle Database RAC 11.2.0.3 for AIX6.1TL7安装记录


虽然报错,但是数据库又能继续创建,直到创建成功!坑爹啊,这么创建的数据库谁敢用啊!!!

4.core_* dump目录及文件撑爆你的$ORACLE_HOME/dbs目录。
在这种情况下创建的数据库会在$ORACLE_HOME/dbs目录下生成大量的core_* dump目录及文件,直到文件系统被撑爆!!!

--------------------------------------------------------------------------------

Linux-6-64下安装Oracle 12C笔记

在CentOS 6.4下安装Oracle 11gR2(x64)

Oracle 11gR2 在VMWare虚拟机中安装步骤

Debian 下 安装 Oracle 11g XE R2

--------------------------------------------------------------------------------


二.下面是排错记录:

1.在METALINK上找到如下的文章说明了ORA-03113的错误:

"ld: 0711-780 SEVERE ERROR: Symbol .ksmpclrpga" and "ORA-7445 [KSMPCLRPGA()+23248]" [ID 1379908.1]

修改时间 27-JUN-2012 类型 PROBLEM 状态 PUBLISHED

In this Document

Applies to:

Oracle Server - Enterprise Edition - Version 11.2.0.1 to 11.2.0.3 [Release 11.2]
IBM AIX on POWER Systems (64-bit)

Symptoms

Installation / Relink of 11.2.0.x on AIX with following version
AIX 5.3 TL 8 and above
AIX 6.1 TL 6 and above
AIX 7.1 SP3 (7100.00.03.1115), TL 1 (7100-01-01-1141) and above

Fail with following relink errors :

ld: 0711-783 WARNING: TOC overflow. TOC size: 225720 Maximum size: 65536
Extra instructions are being generated for each reference to a TOC
symbol if the symbol is in the TOC overflow area.
ld: 0711-780 SEVERE ERROR: Symbol .ksmpfpva (entry 58964) in object /oracle/lib//libserver11.a[ksmp.o]:
Relocation overflow in reference to: dbkea_prm_rate_ (entry 8601)
Address: 0x00008056; RLD type: R_TOC; RLD length: 16
ld: 0711-780 SEVERE ERROR: Symbol .ksmpfpva (entry 58964) in object /oracle/lib//libserver11.a[ksmp.o]:
Relocation overflow in reference to: dbkea_prm_rtl_ (entry 8603)
Address: 0x0000805e; RLD type: R_TOC; RLD length: 16
ld: 0711-780 SEVERE ERROR: Symbol .ksmpfpva (entry 58964) in object /oracle/lib//libserver11.a[ksmp.o]:
Relocation overflow in reference to: dbkea_prm_ctl_ (entry 8605)
Address: 0x00008062; RLD type: R_TOC; RLD length: 16
ld: 0711-780 SEVERE ERROR: Symbol .ksmpfpva (entry 58964) in object /oracle/lib//libserver11.a[ksmp.o]:
Relocation overflow in reference to: dbkehackflg_ (entry 8607)
Address: 0x0000806a; RLD type: R_TOC; RLD length: 16
ld: 0711-780 SEVERE ERROR: Symbol .ksmpfpva (entry 58964) in object /oracle/lib//libserver11.a[ksmp.o]:
Relocation overflow in reference to: dbkedPix_ (entry 8609)
Address: 0x00008076; RLD type: R_TOC; RLD length: 16
ld: 0711-780 SEVERE ERROR: Symbol .ksmpfpva (entry 58964) in object /oracle/lib//libserver11.a[ksmp.o]:
Relocation overflow in reference to: dbkehackprm_ (entry 8611)
Address: 0x0000807e; RLD type: R_TOC; RLD length: 16
ld: 0711-780 SEVERE ERROR: Symbol .ksmpfpva (entry 58964) in object /oracle/lib//libserver11.a[ksmp.o]:
Relocation overflow in reference to: dbkeddmper_ (entry 8613)
Address: 0x00008082; RLD type: R_TOC; RLD length: 16


Further, if the above relink error is ignored while installation and database is created OR upgraded, then following error is noticed while shutting down the database.

ORA-03113: end-of-file on communication channel

Changes

AIX O.S. was installed / upgraded to a new TL level

Cause

This is due to the
"Bug 13342637: 0711-780 SEVERE ERROR: SYMBOL .KSMPFPVA AND .KSMPCLRPGA"

Other bugs referenced / raised for similar issue

Unpublished Bug 10380509: ORACLE LINK ISSUE
Bug 13354044: LINK ERROR - LD: 0711-780 SYMBOL .KSMPFPVA IN OBJECT LIBSERVER11.A[KSMP.O]

BUG 13384572 - ORA-7445 [KSMPCLRPGA()+23248]

Solution

Please work with IBM to get a fix for your OS Version, as you look to be running into AIX O.S. issue, you need to provide your current O.S. level to IBM to get the appropriate fix.

Following are the iFixes need to be applied