資料庫從11.2.0.1到11.2.0.x版本注意事項
-- Oracle OLAP API失效錯誤,錯誤提示如下:
![](https://i.iter01.com/images/5b983aa3c3df0c7261bf1af760cc9cc065bd7616b7799d4013ac2778f83803e3.jpg)
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.
這是否意味著我們忽略即可?現在資料庫暫定測試沒有問題,暫定這樣先用吧。
![](https://i.iter01.com/images/5b983aa3c3df0c7261bf1af760cc9cc065bd7616b7799d4013ac2778f83803e3.jpg)
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 資料庫設計和注意事項MySql資料庫
- MySQL JDBC驅動版本與資料庫版本的對應關係及注意事項MySqlJDBC資料庫
- Oracle資料庫表設計時的注意事項Oracle資料庫
- 大資料學習注意事項大資料
- Oracle 資料匯出注意事項Oracle
- PG 資料庫 DTS 遷移需要注意的事項:資料庫
- 不同版本exp/imp使用注意事項
- 資料網格的注意事項 - Kineret
- 敏捷企業的資料管理注意事項敏捷
- 應用升級SpringCloud版本時的注意事項(Dalston升級到Edgware)SpringGCCloud
- 【odoo】[經驗分享]資料遷移注意事項Odoo
- MAVEN新增本地倉庫和注意事項!Maven
- weblogic版本升級遷移需要注意事項Web
- 【exp/imp不同版本】Oracle不同版本的exp/imp使用注意事項Oracle
- RandomAccessFile注意事項randomMac
- @Lombok注意事項Lombok
- XtraBackup 搭建從庫的一般步驟及 XtraBackup 8.0 的注意事項
- 函式注意事項函式
- 生產注意事項
- 電量注意事項
- CSP 考前注意事項
- 快取注意事項快取
- 資料所有權設定中需要注意的事項
- MySQL 8.0.20 MGR資料遷移過程以及注意事項MySql
- Mysql資料庫自定義函式的定義、使用方法及操作注意事項MySql資料庫函式
- DZone Research:資料庫附加註意事項資料庫
- 2.9 資料庫建立後的狐疑事項資料庫
- 達夢資料裝載工具-dmfldr使用注意事項總結
- 部署專案注意事項
- iOS 程式碼注意事項iOS
- 換工作的注意事項
- Oracle使用*的注意事項Oracle
- VRPs 論文注意事項VR
- Python——常見注意事項Python
- 程式設計注意事項程式設計
- layer open div 注意事項
- [Android開發] 注意事項Android
- Android元件化注意事項Android元件化