Skip to main content

The status of the OLAP components in the dba_registry is LOADED OR UPGRADED

The status of the OLAP components in the dba_registry is LOADED OR UPGRADED


For 9i OLAP is still functional in UPGRADED or LOADED Status.

For 10G/11g, OLAP is only functional with a VALID status.


To check the status of the components, use the following Sql command:

SQL> select substr(comp_id,1,20)"COMP_ID",substr(comp_name,1,25)"Component
Name",substr(version,1,10) "version",status from dba_registry;
 

The results:

 

COMP_ID     Component                               Name version              STATUS

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

APS            OLAP Analytic Workspace           10.2.0.3                     LOADED
XOQ           Oracle OLAP API                        10.2.0.3                      LOADED
AMD           OLAP Catalog                              10.2.0.3                      LOADED


Solution:


1) Check if there are any invalid objects in the OLAPSYS schema.


SQL> select owner, object_name, object_type, status from dba_objects where
status = 'INVALID' and OWNER = 'OLAPSYS' ;
 

b) If objects are invalid, recompile all individual objects logged in as OLAPSYS
.


SQL> alter package <package_name> compile; (package specification)
SQL> alter package <package_name> compile body; (package body)
SQL> alter view <view_name> compile; (view)
 

2) After validating all the OLAPSYS objects in the dba_registry, update the registry .

SQL> connect / as sysdba
SQL> execute dbms_registry.valid('AMD');

SQL> execute dbms_registry.valid('APS');

SQL> execute dbms_registry.valid('XOQ');
 
3. Confirm the status in dba_regisrty:

SQL> select substr(comp_id,1,20)"COMP_ID",substr(comp_name,1,25)"Component
Name",substr(version,1,10) "version",status from dba_registry;
 


Note: You should only do the above if all olap objects are valid. If not, to validate individual components in the dba_registry, reload the invalid component using the following scripts. These scripts are for 10G and may not be available for 9i.
Must log in as sysdba:

ORACLE_HOME/rdbms/admin/olappl.sql  --- This script will reload Olap Analytic workspace.
ORACLE_HOME/olap/admin/apsrelod.sql ---  This script validates Olap analytic workspace.
ORACLE_HOME/olap/admin/xoqrelod.sql --- Reloads Oracle OLAP API .
ORACLE_HOME/olap/admin/amdrelod.sql --- Reloads OLAP CATALOG .
ORACLE_HOME/rdbms/admin/utlrp.sql  ----  This script recompiles any invalid objects.



If you like please follow and comment

Comments

Popular posts from this blog

WebLogic migration to OCI using WDT tool

WebLogic migration to OCI using WDT tool Oracle WebLogic Deploy Tool (WDT) is an open-source project designed to simplify and streamline the management of Oracle WebLogic Server domains. With WDT, you can export configuration and application files from one WebLogic Server domain and import them into another, making it a highly effective tool for tasks like migrating on-premises WebLogic configurations to Oracle Cloud. This blog outlines a detailed step-by-step process for using WDT to migrate WebLogic resources and configurations. Supported WLS versions Why Use WDT for Migration? When moving Oracle WebLogic resources from an on-premises environment to Oracle Cloud (or another WebLogic Server), WDT provides an efficient and reliable approach to: Discover and export domain configurations and application binaries. Create reusable models and archives for deployment in a target domain. Key Pre-Requisites Source System: An Oracle WebLogic Server with pre-configured resources such as: Applica...

How to Validate TDE Wallet Password in Oracle Database

How to Validate TDE Wallet Password in Oracle Database Validating the Transparent Data Encryption (TDE) wallet password is crucial, especially when ensuring that the password is correct without using the OPEN or CLOSE commands in the database. This blog post explains a straightforward method to validate the TDE password using the mkstore utility. Steps to Validate TDE Wallet Password Follow these steps to validate the TDE wallet password: Step 1: Copy the Keystore/Wallet File Navigate to your existing TDE wallet directory. Copy only the ewallet.p12 file to a new directory. If a cwallet.sso file exists, do not copy it . The absence of cwallet.sso ensures that the wallet does not use auto-login, forcing the utility to prompt for the password. Step 2: Validate Using mkstore Use the mkstore utility to check the contents of the wallet file. The mkstore utility will prompt you for the TDE wallet password, allowing you to validate its correctness. Command Syntax To display the conten...

Rename a PDB in Oracle Database Multitenant Architecture in TDE and Non TDE Environment

Rename a PDB in Oracle Database Multitenant Architecture I am sharing a step-by-step guide to help you rename a PDB. This approach uses SQL commands. Without TDE or encryption Wallet Initial Check Check the Current Database Name and Open Mode: SQL > SELECT NAME, OPEN_MODE FROM V$DATABASE; NAME OPEN_MODE --------- -------------------- BEECDB READ WRITE List Current PDBs: SQL > SHOW PDBS; CON_ID CON_NAME OPEN MODE RESTRICTED ---------- ------------------------------ ---------- ---------- 2 PDB$SEED READ ONLY NO 3 FUAT READ WRITE NO We need to RENAME FUAT to BEE  Steps to Rename the PDB Step 1: Export ORACLE_SID Set the Oracle SID to the Container Database (CDB): export ORACLE_SID=BEECDB Step 2: Verify Target PDB Name Availability If the target PDB name is different from the current PDB name, ensure no service exists with the target PDB name. Run SQL to Check Exi...