安裝Oracle 10.2.0.5 RAC for AIX6(五)

yangtingkun發表於2011-07-17

簡單介紹在AIX6上安裝10.2.0.5 RAC的過程。

這一篇描述安裝過程中碰到的問題。

安裝Oracle 10.2.0.5 RAC for AIX6(一):http://yangtingkun.itpub.net/post/468/520680

安裝Oracle 10.2.0.5 RAC for AIX6(二):http://yangtingkun.itpub.net/post/468/520729

安裝Oracle 10.2.0.5 RAC for AIX6(三):http://yangtingkun.itpub.net/post/468/520795

安裝Oracle 10.2.0.5 RAC for AIX6(四):http://yangtingkun.itpub.net/post/468/520850

 

 

其實這次的安裝過程整體非常順利,除了由於PUBLIC_ID的設定不當,使得10gCLUSTER沒有辦法自動找到設定PUBLIC_ID的網路卡,需要手工啟動VIPCA圖形工具來解決這個問題,整個安裝過程幾乎沒有碰到其他任何問題。而這個IP地址的問題由來已久,在我第一次安裝RAC的時候就曾經碰到過,而且在以往的安裝過程中,由於PUBLIC_IP的設定,碰到這個問題的可能性反而比這個問題不出現的可能性還大。

不過在RAC環境完全安裝成功後,利用srvctl嘗試重啟CLUSTER時,碰到了錯誤:

$ srvctl start db -d ywdb
PRKP-1001 : Error starting instance ywdb1 on node ywdb1
CRS-0215: Could not start resource 'ora.ywdb.ywdb1.inst'.
PRKP-1001 : Error starting instance ywdb2 on node ywdb2
CRS-0215: Could not start resource 'ora.ywdb.ywdb2.inst'.

檢查alert告警檔案:

$ tail -100 /opt/oracle/admin/ywdb/bdump/alert_ywdb1.log
DIAG started with pid=3, OS id=13304120
PSP0 started with pid=4, OS id=11337892
LMON started with pid=5, OS id=14549180
LMD0 started with pid=6, OS id=3408122
LMS0 started with pid=7, OS id=12452102
LMS1 started with pid=8, OS id=11534814
MMAN started with pid=9, OS id=15859942
DBW0 started with pid=10, OS id=11403748
LGWR started with pid=11, OS id=13828208
CKPT started with pid=12, OS id=12779546
SMON started with pid=13, OS id=14680228
RECO started with pid=14, OS id=12321000
CJQ0 started with pid=15, OS id=13172782
MMON started with pid=16, OS id=9437552
Fri Apr 15 03:39:58 CDT 2011
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
MMNL started with pid=17, OS id=11403418
Fri Apr 15 03:39:58 CDT 2011
starting up 1 shared server(s) ...
Fri Apr 15 03:40:09 CDT 2011
lmon registered with NM - instance id 1 (internal mem no 0)
Fri Apr 15 03:40:09 CDT 2011
Reconfiguration started (old inc 0, new inc 4)
List of nodes:
0 1
Global Resource Directory frozen
* allocate domain 0, invalid = TRUE
Communication channels reestablished
Master broadcasted resource hash value bitmaps
Non-local Process blocks cleaned out
Fri Apr 15 03:40:09 CDT 2011
LMS 1: 0 GCS shadows cancelled, 0 closed
Fri Apr 15 03:40:09 CDT 2011
LMS 0: 0 GCS shadows cancelled, 0 closed
Set master node info
Submitted all remote-enqueue requests
Dwn-cvts replayed, VALBLKs dubious
All grantable enqueues granted
Post SMON to start 1st pass IR
Fri Apr 15 03:40:09 CDT 2011
LMS 1: 0 GCS shadows traversed, 0 replayed
Fri Apr 15 03:40:09 CDT 2011
LMS 0: 0 GCS shadows traversed, 0 replayed
Fri Apr 15 03:40:09 CDT 2011
Submitted all GCS remote-cache requests
Fix write in gcs resources
Reconfiguration complete
LCK0 started with pid=20, OS id=10616844
Fri Apr 15 03:40:10 CDT 2011
ALTER DATABASE MOUNT
Fri Apr 15 03:40:19 CDT 2011
Setting recovery target incarnation to 1
Fri Apr 15 03:40:19 CDT 2011
Successful mount of redo thread 1, with mount id 2807738276
Fri Apr 15 03:40:19 CDT 2011
Database mounted in Shared Mode (CLUSTER_DATABASE=TRUE)
Completed: ALTER DATABASE MOUNT
Fri Apr 15 03:40:20 CDT 2011
ALTER DATABASE OPEN
This instance was first to open
Fri Apr 15 03:40:20 CDT 2011
Errors in file /opt/oracle/admin/ywdb/bdump/ywdb1_dbw0_11403748.trc:
ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
ORA-01110: data file 1: '/ywdb01/oradata/ywdb/system01.dbf'
ORA-27092: size of file exceeds file size limit of the process
Additional information: 131071
Additional information: 262145
Fri Apr 15 03:40:20 CDT 2011
Errors in file /opt/oracle/admin/ywdb/bdump/ywdb1_dbw0_11403748.trc:
ORA-01157: cannot identify/lock data file 2 - see DBWR trace file
ORA-01110: data file 2: '/ywdb01/oradata/ywdb/undotbs01.dbf'
ORA-27092: size of file exceeds file size limit of the process
Additional information: 131071
Additional information: 1048577
Fri Apr 15 03:40:20 CDT 2011
Errors in file /opt/oracle/admin/ywdb/bdump/ywdb1_dbw0_11403748.trc:
ORA-01157: cannot identify/lock data file 3 - see DBWR trace file
ORA-01110: data file 3: '/ywdb01/oradata/ywdb/sysaux01.dbf'
ORA-27092: size of file exceeds file size limit of the process
Additional information: 131071
Additional information: 524289
Fri Apr 15 03:40:20 CDT 2011
Errors in file /opt/oracle/admin/ywdb/bdump/ywdb1_dbw0_11403748.trc:
ORA-01157: cannot identify/lock data file 4 - see DBWR trace file
ORA-01110: data file 4: '/ywdb01/oradata/ywdb/undotbs02.dbf'
ORA-27092: size of file exceeds file size limit of the process
Additional information: 131071
Additional information: 1048577
Fri Apr 15 03:40:20 CDT 2011
Errors in file /opt/oracle/admin/ywdb/bdump/ywdb1_dbw0_11403748.trc:
ORA-01157: cannot identify/lock data file 5 - see DBWR trace file
ORA-01110: data file 5: '/ywdb01/oradata/ywdb/users01.dbf'
ORA-27092: size of file exceeds file size limit of the process
Additional information: 131071
Additional information: 131073
ORA-1157 signalled during: ALTER DATABASE OPEN...
Fri Apr 15 03:40:23 CDT 2011
Shutting down instance (abort)
License high water mark = 1
Instance terminated by USER, pid = 5374168

嘗試直接使用sqlplus進行操作,結果並未碰到錯誤:

$ sqlplus / as sysdba

SQL*Plus: Release 10.2.0.5.0 - Production on Fri Apr 15 04:04:08 2011

Copyright (c) 1982, 2010, Oracle. All Rights Reserved.

Connected to an idle instance.

SQL> startup
ORACLE instance started.

Total System Global Area 3.3554E+10 bytes
Fixed Size 2157904 bytes
Variable Size 3120562864 bytes
Database Buffers 3.0417E+10 bytes
Redo Buffers 14618624 bytes
Database mounted.
Database opened.

檢查oracle使用者的限制,也完全符合安裝的要求。

如果sqlplus沒有問題,且oracle使用者的限制也沒有問題,而使用srvctl命令時出現錯誤,且根據錯誤資訊ORA-27092: size of file exceeds file size limit of the process進行分析,問題確實是由於oracle資料庫超過了使用者的檔案大小的限制。不過這裡並不是oracle使用者的限額不足,而是root使用者:

SQL> exit
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - 64bit Production
With the Partitioning, Real Application Clusters, OLAP, Data Mining
and Real Application Testing options
$ su -
root's Password:
# smit chuser

設定root使用者的限制後,再次使用srvctl啟動RAC環境,問題消失。

 

 

來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/4227/viewspace-702424/,如需轉載,請註明出處,否則將追究法律責任。

相關文章