資料庫從11.2.0.1到11.2.0.x版本注意事項
-- Oracle OLAP API失效錯誤,錯誤提示如下:
SQL> select comp_name, version, status from sys.dba_registry;
COMP_NAME VERSION STATUS
-------------------------------------------------- -------------------- ------------------------------
OWB 11.2.0.1.0 VALID
Oracle Application Express 3.2.1.00.10 VALID
Oracle Enterprise Manager 11.2.0.3.0 VALID
OLAP Catalog 11.2.0.1.0 OPTION OFF
Spatial 11.2.0.1.0 OPTION OFF
Oracle Multimedia 11.2.0.3.0 VALID
Oracle XML Database 11.2.0.3.0 VALID
Oracle Text 11.2.0.3.0 VALID
Oracle Expression Filter 11.2.0.3.0 VALID
Oracle Rules Manager 11.2.0.3.0 VALID
Oracle Workspace Manager 11.2.0.3.0 VALID
Oracle Database Catalog Views 11.2.0.3.0 VALID
Oracle Database Packages and Types 11.2.0.3.0 VALID
JServer JAVA Virtual Machine 11.2.0.3.0 VALID
Oracle XDK 11.2.0.3.0 VALID
Oracle Database Java Packages 11.2.0.3.0 VALID
OLAP Analytic Workspace 11.2.0.1.0 OPTION OFF
Oracle OLAP API 11.2.0.1.0 OPTION OFF
解決方案:
++ 官方的一個連結反饋運用系統預設模版在標準版中會出現OLAP的升級問題
Use Of Database Templates with Standard Edition Cause Problems With OLAP (Doc ID 556194.1)
Standard Edition does not support OLAP.
When trying to configure the OLAP-related components while creating the instance, OLAP-specific configurations are performed and fail due to the OLAP option not being present.
For Oracle 10g Enterprise Edition, you may choose to manually remove the (partially present) OLAP option by following these instructions (also outlined in Note 278111.1 How To Remove the Oracle OLAP API Objects From 9i and 10g):
For Standard Edition, these scripts do not exist and it is highly recommended to open a Service Request with Oracle Support to assist in the process.
不過在另外一個文件也有敘述OPTION OFF意味著我們無需理會即可。
Oracle OLAP Components listed as 'OPTION OFF' in Standard Edition Installation (Doc ID 459153.1)
Information in this document applies to any platform.
1- The Standard Edition of Oracle was installed.
2- The database instance was created using dbca.
3- When using dbca to create a database instance, Oracle OLAP is automatically included in all database selections, other than the 'Custom Database' selection.
4- Upon the initial creation all the OLAP Components will be listed as VALID when viewing the dba_registry. NOTE: the version information in this example is only for example purposes.
5- Once the database is upgraded, starting with 10.2.0.2, the STATUS will be returned as:
6- The return from the dba_registry indicating the Oracle OLAP components as 'OPTION OFF' indicates that the Oracle OLAP software option has not been installed and therefore the Oracle OLAP scripts are not present.
7- This is normal under these conditions and does not require Oracle OLAP to be removed from the instance as it is not usable and will not be looked at upon future patches or upgrades.
這是否意味著我們忽略即可?現在資料庫暫定測試沒有問題,暫定這樣先用吧。
SQL> select comp_name, version, status from sys.dba_registry;
COMP_NAME VERSION STATUS
-------------------------------------------------- -------------------- ------------------------------
OWB 11.2.0.1.0 VALID
Oracle Application Express 3.2.1.00.10 VALID
Oracle Enterprise Manager 11.2.0.3.0 VALID
OLAP Catalog 11.2.0.1.0 OPTION OFF
Spatial 11.2.0.1.0 OPTION OFF
Oracle Multimedia 11.2.0.3.0 VALID
Oracle XML Database 11.2.0.3.0 VALID
Oracle Text 11.2.0.3.0 VALID
Oracle Expression Filter 11.2.0.3.0 VALID
Oracle Rules Manager 11.2.0.3.0 VALID
Oracle Workspace Manager 11.2.0.3.0 VALID
Oracle Database Catalog Views 11.2.0.3.0 VALID
Oracle Database Packages and Types 11.2.0.3.0 VALID
JServer JAVA Virtual Machine 11.2.0.3.0 VALID
Oracle XDK 11.2.0.3.0 VALID
Oracle Database Java Packages 11.2.0.3.0 VALID
OLAP Analytic Workspace 11.2.0.1.0 OPTION OFF
Oracle OLAP API 11.2.0.1.0 OPTION OFF
解決方案:
++ 官方的一個連結反饋運用系統預設模版在標準版中會出現OLAP的升級問題
Use Of Database Templates with Standard Edition Cause Problems With OLAP (Doc ID 556194.1)
Changes
A new instance of the database is being configured using DBCA and a template other than Custom had been chosen.Cause
All templates used by DBCA(except the Custom template) use pre-configured datafiles and are based on the Enterprise Edition feature set, which includes OLAP.Standard Edition does not support OLAP.
When trying to configure the OLAP-related components while creating the instance, OLAP-specific configurations are performed and fail due to the OLAP option not being present.
Solution
When using DBCA with the Standard Edition of 10g or 11g of Oracle RDBMS, ensure that:-
In Step 2 (Database Template) of DBCA, select Custom Database.
-
In Step 9 (Database Content) of DBCA, in the Database Content tab, please uncheck the OLAP component.
For Oracle 10g Enterprise Edition, you may choose to manually remove the (partially present) OLAP option by following these instructions (also outlined in Note 278111.1 How To Remove the Oracle OLAP API Objects From 9i and 10g):
SQL> conn / as sysdba
SQL> @?/olap/admin/catnoamd.sql
SQL> @?/olap/admin/olapidrp.plb
SQL> @?/olap/admin/catnoaps.sql
SQL> @?/olap/admin/catnoxoq.sql
SQL> @?/olap/admin/catnoamd.sql
SQL> @?/olap/admin/olapidrp.plb
SQL> @?/olap/admin/catnoaps.sql
SQL> @?/olap/admin/catnoxoq.sql
For Standard Edition, these scripts do not exist and it is highly recommended to open a Service Request with Oracle Support to assist in the process.
不過在另外一個文件也有敘述OPTION OFF意味著我們無需理會即可。
Oracle OLAP Components listed as 'OPTION OFF' in Standard Edition Installation (Doc ID 459153.1)
Applies to:
Oracle OLAP - Version: 9.2 to 10.2Information in this document applies to any platform.
Goal
Why are Oracle OLAP components listed in dba_registry as 'OPTION OFF'Solution
The Oracle OLAP components are listed in a database instance as 'OPTION OFF' due to:1- The Standard Edition of Oracle was installed.
2- The database instance was created using dbca.
3- When using dbca to create a database instance, Oracle OLAP is automatically included in all database selections, other than the 'Custom Database' selection.
4- Upon the initial creation all the OLAP Components will be listed as VALID when viewing the dba_registry. NOTE: the version information in this example is only for example purposes.
SQL> col comp_name format a30
SQL> select comp_name, status, substr(version,1,10) as version from dba_registry where comp_name like '%OLAP%';
COMP_NAME STATUS VERSION
------------------------------ ----------- ----------
OLAP Analytic Workspace VALID 10.2.0.1.0
Oracle OLAP API VALID 10.2.0.1.0
OLAP Catalog VALID 10.2.0.1.0
SQL> select comp_name, status, substr(version,1,10) as version from dba_registry where comp_name like '%OLAP%';
COMP_NAME STATUS VERSION
------------------------------ ----------- ----------
OLAP Analytic Workspace VALID 10.2.0.1.0
Oracle OLAP API VALID 10.2.0.1.0
OLAP Catalog VALID 10.2.0.1.0
5- Once the database is upgraded, starting with 10.2.0.2, the STATUS will be returned as:
SQL> col comp_name format a30
SQL> select comp_name, status, substr(version,1,10) as version from
dba_registry where comp_name like '%OLAP%';
COMP_NAME STATUS VERSION
------------------------------ ----------- ----------
OLAP Analytic Workspace OPTION OFF 10.2.0.3.0
Oracle OLAP API OPTION OFF 10.2.0.3.0
OLAP Catalog OPTION OFF 10.2.0.3.0
SQL> select comp_name, status, substr(version,1,10) as version from
dba_registry where comp_name like '%OLAP%';
COMP_NAME STATUS VERSION
------------------------------ ----------- ----------
OLAP Analytic Workspace OPTION OFF 10.2.0.3.0
Oracle OLAP API OPTION OFF 10.2.0.3.0
OLAP Catalog OPTION OFF 10.2.0.3.0
6- The return from the dba_registry indicating the Oracle OLAP components as 'OPTION OFF' indicates that the Oracle OLAP software option has not been installed and therefore the Oracle OLAP scripts are not present.
7- This is normal under these conditions and does not require Oracle OLAP to be removed from the instance as it is not usable and will not be looked at upon future patches or upgrades.
這是否意味著我們忽略即可?現在資料庫暫定測試沒有問題,暫定這樣先用吧。
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/12974804/viewspace-1061540/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- MySQL 資料庫-索引注意事項MySql資料庫索引
- 把資料從MySQL遷到Oracle的幾點注意事項MySqlOracle
- Oracle 資料庫升級注意事項Oracle資料庫
- 資料庫程式設計注意事項資料庫程式設計
- MySQL 資料庫設計和注意事項MySql資料庫
- MySQL JDBC驅動版本與資料庫版本的對應關係及注意事項MySqlJDBC資料庫
- 備份 master 資料庫時的注意事項AST資料庫
- Oracle資料庫中Create user的注意事項Oracle資料庫
- oracle版本升級:從11.2.0.1到11.2.0.3Oracle
- Oracle資料庫表設計時的注意事項Oracle資料庫
- 從MySQL到ORACLE程式遷移的注意事項(轉)MySqlOracle
- 在單機linux上安裝兩個不同版本資料庫時注意事項Linux資料庫
- Oracle 資料匯出注意事項Oracle
- 大資料學習注意事項大資料
- oracle移植到mysql注意事項OracleMySql
- 不同版本exp/imp使用注意事項
- PG 資料庫 DTS 遷移需要注意的事項:資料庫
- 備份model 和msdb 資料庫時的注意事項資料庫
- XML PUBLISHER 輸出資料庫圖片需注意事項XML資料庫
- 資料網格的注意事項 - Kineret
- 複製資料庫中需要注意的幾點事項資料庫
- 12c 使用資料泵複製資料庫結構的注意事項資料庫
- 敏捷企業的資料管理注意事項敏捷
- mysql 配置注意事項、 mysql 資料型別MySQL 資料型別
- 在SQL Server資料庫中使用批處理的注意事項SQLServer資料庫
- 使用Oracle9i資料庫的九大注意事項(轉)Oracle資料庫
- 注意事項:golang 編譯的 glibc 版本Golang編譯
- Oracle 升級到 11.2.0.2 注意事項Oracle
- MySQL生產庫主從重新同步操作注意事項薦MySql
- 更改當前資料庫預設臨時表空間注意事項資料庫
- 不停機 data guard 注意事項 (重建orapw對資料庫的影響)資料庫
- 應用升級SpringCloud版本時的注意事項(Dalston升級到Edgware)SpringGCCloud
- 【odoo】[經驗分享]資料遷移注意事項Odoo
- Oracle goldengate初始化資料注意事項OracleGo
- 關於vSphere 5.5硬體版本注意事項
- 【exp/imp不同版本】Oracle不同版本的exp/imp使用注意事項Oracle
- MAVEN新增本地倉庫和注意事項!Maven
- Oracle9i資料庫的Standby端執行備份,注意事項~Oracle資料庫