Olap Analytic Workspace Invalid | Olap (Online Analytical Processing) 34 개의 정답

당신은 주제를 찾고 있습니까 “olap analytic workspace invalid – OLAP (Online Analytical Processing)“? 다음 카테고리의 웹사이트 https://chewathai27.com/you 에서 귀하의 모든 질문에 답변해 드립니다: https://chewathai27.com/you/blog. 바로 아래에서 답을 찾을 수 있습니다. 작성자 Chuc Nguyen Van 이(가) 작성한 기사에는 조회수 4,839회 및 좋아요 35개 개의 좋아요가 있습니다.

olap analytic workspace invalid 주제에 대한 동영상 보기

여기에서 이 주제에 대한 비디오를 시청하십시오. 주의 깊게 살펴보고 읽고 있는 내용에 대한 피드백을 제공하세요!

d여기에서 OLAP (Online Analytical Processing) – olap analytic workspace invalid 주제에 대한 세부정보를 참조하세요

KHÓA HỌC ONLINE PHÂN TÍCH DỮ LIỆU XEM TẠI ĐÂY: https://lnkd.in/grB6KGbx

olap analytic workspace invalid 주제에 대한 자세한 내용은 여기를 참조하세요.

OLAP Analytic Workspace INVALID after Upgrade from 11.2.0.1

Connected / as sysdba, run the following script, which will rebuild the SYS-owned OLAP AWs and rerun the valation routine for the registry …

+ 자세한 내용은 여기를 클릭하십시오

Source: vmdk.wordpress.com

Date Published: 11/10/2021

View: 1424

Step to remove database componentes – Doyensys Blog

SELECT object_name FROM dba_objects WHERE status = ‘INVALID’;. 2. Remove OLAP Analytic Workspace: … @?/olap/admin/catnoaps.sql.

+ 여기에 더 보기

Source: doyensys.com

Date Published: 4/24/2022

View: 2838

OLAP API INVALID after upgrading 10.2.0.1 to 10.2.0.3 &amp

Packages of Java database Oracle 10.2.0.3.0 VALID Analytic workspace VALID OLAP 10.2.0.3.0. API of OLAP Oracle 10.2.0.3.0 INVALID

+ 여기에 더 보기

Source: www.eehelp.com

Date Published: 9/27/2022

View: 8950

How to uninstall/remove invalid OLAP components since …

APS OLAP Analytic Workspace 11.2.0.3.0. XOQ Oracle OLAP API 11.2.0.3.0. AMD OLAP Catalog 11.2.0.3.0. Short Steps:.

+ 여기를 클릭

Source: www.dbaglobe.com

Date Published: 6/10/2021

View: 7117

Oracle OLAP (XOQ, APS, AMD) Clean Up in Oracle Database …

The recompilation will clean up the inval objects. … APS – OLAP Analytic Workspace. To clean up APS you must unlink OLAP first.

+ 자세한 내용은 여기를 클릭하십시오

Source: mikedietrichde.com

Date Published: 7/10/2021

View: 2930

Remove OLAP From the Standard Edition database – AdnanDBA

This will remove the OLAP Catalog option from the database but OLAP Analytic Workspace and Oracle OLAP API will remain in an inval state. set lines 200;

+ 여기를 클릭

Source: adnandba.blogspot.com

Date Published: 10/17/2021

View: 3301

Deleting OLAP Catalog Metadata

CWM2_OLAP_DELETE deletes both val and inval metadata. … To rebuild analytic workspaces, use the OLAP DML to export the contents of the workspace to an …

+ 여기를 클릭

Source: www.cis.famu.edu

Date Published: 5/20/2022

View: 7625

Oracle Application DBA Information: January 2020

OLAP – Analytic Workspaces 09-SEP-12 12-MAY-13 … A) After then we will run utlrp.sql for Valate all Inval objects.

+ 자세한 내용은 여기를 클릭하십시오

Source: appsdbafurqan.blogspot.com

Date Published: 6/6/2021

View: 7424

주제와 관련된 이미지 olap analytic workspace invalid

주제와 관련된 더 많은 사진을 참조하십시오 OLAP (Online Analytical Processing). 댓글에서 더 많은 관련 이미지를 보거나 필요한 경우 더 많은 관련 기사를 볼 수 있습니다.

OLAP (Online Analytical Processing)
OLAP (Online Analytical Processing)

주제에 대한 기사 평가 olap analytic workspace invalid

  • Author: Chuc Nguyen Van
  • Views: 조회수 4,839회
  • Likes: 좋아요 35개
  • Date Published: 2021. 2. 26.
  • Video Url link: https://www.youtube.com/watch?v=5hECIfJtnzU

Step to remove database componentes

1. Remove Oracle Text:

***********************

@?/ctx/admin/catnoctx.sql

drop procedure sys.validate_context;

select comp_id, comp_name, version, status from dba_registry where COMP_ID=’CONTEXT’;

SELECT object_name FROM dba_objects WHERE status = ‘INVALID’;

2. Remove OLAP Analytic Workspace:

************************************

shutdown immediate;

startup

@?/olap/admin/catnoaps.sql

alter public synonym DBA_AW_PROP compile;

alter public synonym USER_AW_PROP compile;

alter public synonym ALL_AW_PROP compile;

OLAP API INVALID after upgrading 10.2.0.1 to 10.2.0.3 & remove/reinstall

Oracle OLAP API invalid to upgrade to 11.2.0.3 Hello

I upgraded a database on Win64 11.2.0.1 to 11.2.0.3 Patch 10 .

The “Information Tool pre-upgrade’ says ‘Oracle OLAP API [upgrade] not VALID’ bevore the upgrade. The upgrade procedure did not then upgrade OLAP. Now several objects of OLAPSYS and CTXSYS object. DRIOPT are not valid and cannot be validated by the compilation. What should I do now?

Thanks in advance.

Kind regards

Martin If you make no use of OLAP functionality (which sounds like the case since your source database had this option not VALID), you can ignore these errors. HTH

Srini

Oracle Text invalid after upgrade to 11.2.0.3 Hello

I upgraded a database on Win64 11.2.0.1 to 11.2.0.3 Patch 10 .

Now, the object CTXSYS. DRIOPT is not valid and cannot be validated by the compilation.

Here is the output of DBA_REGISTRY:

STATUS OF VERSION COMPUTERNAME

——————————————————————–

JServer JAVA Virtual Machine 11.2.0.3.0 VALID

OLAP Analytic Workspace 11.2.0.1.0 OPTION OFF

OLAP catalog 11.2.0.1.0 OPTION OFF

Oracle Application Express 4.1.0.00.32 VALID

Oracle 11.2.0.3.0 database catalog view (s) VALID

Oracle database Java packages 11.2.0.3.0 VALID

Database Oracle and 11.2.0.3.0 Types VALID packets

Oracle Enterprise Manager 11.2.0.3.0 VALID

INVALID Filter Expression Oracle 11.2.0.3.0

Oracle Multimedia 11.2.0.3.0 VALID

Oracle OLAP API 11.2.0.1.0 OFF OPTION

Rules of Oracle Manager VALID 11.2.0.3.0

Oracle Text 11.2.0.3.0 INVALID

Oracle Workspace Manager 11.2.0.3.0 VALID

Oracle XDK 11.2.0.3.0 VALID

11.2.0.3.0 Server Oracle XML VALID

OWB 11.2.0.1.0 VALID

space 11.2.0.1.0 OPTION OFF

Thanks in advance.

Kind regards

Martin Hello.. I had the same problem… followed note meta… problem solved… * Manuelle installation, uninstallation, and Oracle 11 g 2 [970473.1 ID] text verification *.

My apple ID became invalid after the recent upgrade to ios 9.3 My apple ID became invalid after the recent upgrade to ios 9.3. What can I do to reactivate the ID? I tried to reset my password several times even. For now, I am unable to pay for anything because I can’t access the function of apple on the phone pay. Hello Follow the instructions here, include a link to get help from Apple with your Apple ID: If your identifier Apple is locked – Apple supports

Invalid objects after upgrade of database 11g Hello

I’ve updated 11i EBS 10.2.0.3 for 11.1.0.7 database.

Prior to upgradation all invalid objects have been compiled, and there is no invalid object

After upgradation I 329 invalid objects, I tried the script utlrp.sql running but no luck, they are still non valid and County remains the same. Please can someone guide me to this point.

Thanks in advance…

Concerning Hello You can use the ADCOMPSC.pls script for other schemas (such as sys and system). See these documents for more details. Note: 104457,1 – invalid objects in Oracle Applications FAQ

Note: 143734.1 – how to compile invalid objects Kind regards

Hussein

Sound does not load after upgrading to El captain Hello After upgrading my iMac (late 2009) to El captain the sound no longer works. Trying to open the preferences-> the error message appear that this could not be loaded. Other sounds associated with apps like audio / midi set up crashes. Please launch the Console application in one of the following ways: ☞ Enter the first letters of his name in a Spotlight search. Select from the results (it should be at the top). ☞ In the Finder, select go utilities ▹ of menu bar or press the combination of keys shift-command-U. The application is in the folder that opens. ☞ Open LaunchPad and start typing the name. The title of the Console window should be all Messages. If it isn’t, select SYSTEM LOG QUERIES ▹ all Messages in the list of logs on the left. If you don’t see this list, select List of newspapers seen ▹ display in the menu at the top of the screen bar. Click on the clear view icon in the toolbar. Then take an action that does not work the way you expect. Select all of the lines that appear in the Console window. Copy to the Clipboard by pressing Control-C key combination. Paste into a reply to this message by pressing command + V. The journal contains a large amount of information, almost everything that is not relevant to solve a particular problem. When you post a journal excerpt, be selective. A few dozen lines are almost always more than enough. Please don’t dump blindly thousands of lines in the journal in this discussion. Please do not post screenshots of log messages – text poster. Some private information, such as your name or e-mail address, can appear in the log. Anonymize before posting. When you post the journal excerpt, an error message may appear on the web page: “you include content in your post that is not allowed”, or “the message contains invalid characters.” It’s a bug in the forum software. Thanks for posting the text on Pastebin, then post here a link to the page you created. If you have an account on Pastebin, please do not select private in exposure menu to paste on the page, because no one else that you will be able to see it.

Time Machine does not work after upgrade to Sierra The Time Machine (TM) fail to start backup and there is still “preparing backup…”. “for more than an hour. This right after upgrading to Mac OS Sierra. Another weird thing happens to the toolbar of the Mac Mail. The Junk button is replaced by another button. trying to put back in place, but remove the button become a button. Please help with the backup problem mentioned above. Thank you much in advance. How long have you waited? After a new installation, it must be a fair while even with a SSD to prepare the first backup due to the number of modified files. Make sure the TM drive is in the list of items excluded from Spotlight indexing. ICloud newsletter and other cloud services.

Not able to scan with the preview after upgrade from Mac OS Sierra… After upgrading to Mac OS Sierra. I’m unable to use the preview to scan. Before this upgrade, it worked fine. The HP scanner software does NOT work something like OS 10.8 or 10.9. Preview worked perfectly so far. If anyone knows how to solve this problem, your contribution will be greatly appreciated. Thanks in advance. Have you tried scanning with Capture of Image instead? It worked for me.

Projector does not work after upgrade from Sierra My projector does not work after upgrade to Sierra. Or search in Outlook (I use outlook for Mac due to having MS 365 for labour) or the search function in the finder. I use this all the time and need this feature back. I tried to reindex spotlight and nothing. Anyone has any ideas. Try to rebuild Spotlight rebuild the Spotlight to your Mac – Apple Support index

I can’t print after upgrade to Mac OS Sierra (error “Unable to filter”) I can’t print after upgrade to MacOS Sierra, always shown “cannot filter. I use AirPrint for Epson L355. Tried to reset the printer settings, uninstall and then install the printer, always in vain ‘filter ‘. I think it has something to do with MacOS Sierra 10.12.1 Beta (16B2333a). Help, please! Update to the Sierra officially released

What happened to the flashlight after upgrade to ios10 What happened to the flashlight after upgrading to IOS 10 Flashlight is the control center? I swear that I saw on one of these demo phones in an Apple store.

Notes, do not sync on the iPhone after upgrade After upgrading to IOS10.0.2 on iPhone no matter who has experienced problems with Notes is no longer sync with other devices? Hi jimbjazz57, I understand that, after the update your iPhone to iOS 10, you had some problems with your notes, do not sync with other devices. I know it’s important to have your information available on any device you use, so I’m happy to help you. If use you iCloud for synchronize your notes, and then connect to iCloud.com and see if your notes are sync to iCloud at all. We want to, on your iPhone, make sure you create notes in the right folder. Open the Notes app, and then tap left arrow in the upper left corner of the app. Make sure that you have the appropriate folder selected here when entering new tickets. If your notes are not yet the timing, we will try to switch your Notes and turn it back on. To make this opening settings > iCloud. Disable notes, restart your iPhone, and then turn on again them. Thank you for using communities Support from Apple. See you soon!

Photostream not working after upgrade to Sierra I noticed after upgrading to Sierra, that my photo stream on the Macbook no longer works. When I connect to www.icloud.com I see that there are new photos downloaded from my iPhone to the iCloud, but not to my Macbook, no news pictures showed in Photos on my Mac. I tried login/out my iCloud on the Macbook and the iPhone account, but nothing has changed. Any ideas on how to solve this problem? Start by providing details What are your parameters to iCloud every IOS device on your Mac and if you use iCloud library what his status on each device Your message is confusing – you cannot see or access MyPhotoStream on the icloud.com – on iCloud.com/Photos see you iCloud photo library photos only – and if a device has not finished to upload to ICPL it downloads pictures So to help, we need to know what services you are using and what their status is LN

Oracle OLAP (XOQ, APS, AMD) Clean Up in Oracle Database 11.2-19c

Oracle OLAP (XOQ, APS, AMD) Clean Up in Oracle Database 11.2-19c requires recompilation and some workarounds in most releases. Nevertheless, I’m documenting the removal steps for all 3 OLAP parts:

XOQ – OLAP API

– OLAP API APS – OLAP Analytical Workspace

– OLAP Analytical Workspace AMD – OLAP Catalog

Again, let me emphasize that none of these blog posts is meant to recommend the removal of any component. It is just meant to explain procedures and workarounds as I sometimes face the situation to remove a component from a database.

Oracle OLAP (XOQ, APS, AMD) Clean Up in Oracle Database 11.2-19c

Even though a lot of fantastic analytical functions have made it over time into the standard set of Oracle SQL commands, Oracle OLAP is still very useful and has good market traction. Oracle OLAP cubes deliver sophisticated calculations using simple SQL queries – producing results with speed of thought response times. This outstanding query performance may be leveraged transparently when deploying OLAP cubes as materialized views – enhancing the performance of summary queries against detail relational tables. Because Oracle OLAP is embedded in Oracle Database 12c, it allows centralized management of data and business rules in a secure, scalable and enterprise-ready platform.

Oracle OLAP is an extra cost option.

Before you start removing anything from your database please make sure you read my introductory blog post about how to Remove and Clean Up Components from Oracle 11.2 – 19c You’ll find links to monitor proper component removal there as well as in the SQL Scripts Repository on this blog.

Please read MOS Note: 332351.1 – How to remove or reinstall the OLAP option to 10g/11g upfront. You can combine each of the following 3 steps into one script and recompile afterwards.

.

Oracle Database 11.2.0.4

XOQ – OLAP API

To remove XQO you will have to execute to scripts but add recompilation as well as approximately 20 synonyms will stay invalid:

$ sqlplus / as sysdba SQL> @?/olap/admin/olapidrp.plb SQL> @?/olap/admin/catnoxoq.sql SQL> @?/rdbms/admin/utlrp.sql

The recompilation will clean up the invalid objects. Furthermore the removal scripts have some failing “ drop ” statements. Please ignore them.

APS – OLAP Analytic Workspace

To clean up APS you must unlink OLAP first.

$ chopt disable olap

In the next step execute the removal script and recompile. The recompilation is necessary to clean up 3 invalid synonyms.

$ sqlplus / as sysdba SQL> @?/olap/admin/catnoaps.sql SQL> @?/rdbms/admin/utlrp.sql

AMD – OLAP Catalog

AMD is the third OLAP component. You can remove it with one script anytime without recompilation, restart or relink. MOS Note: 332351.1 – How to remove or reinstall the OLAP option to 10g/11g offers a description. Furthermore this option does not exist anymore in Oracle Database 12.1 and therefore can be removed before an upgrade safely to safe upgrade time.

$ sqlplus / as sysdba SQL> @?/olap/admin/catnoamd.sql

Oracle Database 12.1.0.2

XOQ – OLAP API

To remove XQO you will have to execute to scripts but add recompilation as well as approximately 38 synonyms will stay invalid:

$ sqlplus / as sysdba SQL> @?/olap/admin/olapidrp.plb SQL> @?/olap/admin/catnoxoq.sql SQL> @?/rdbms/admin/utlrp.sql

The recompilation will clean up the invalid objects. Furthermore the removal scripts have some failing “ drop ” statements. Please ignore them.

APS – OLAP Analytic Workspace

To clean up APS you must unlink OLAP first.

$ chopt disable olap

In the next step execute the removal script and recompile. The recompilation is necessary to clean up 3 invalid public synonyms.

$ sqlplus / as sysdba SQL> @?/olap/admin/catnoaps.sql SQL> @?/rdbms/admin/utlrp.sql

AMD – OLAP Catalog

In Oracle Database 12c the OLAP Catalog (AMD) does not exist anymore. We will switch it to OPTION OFF during the upgrade but you can remove it upfront to save on upgrade time. Once the AMD component is detected by the preupgrd.sql you’ll receive these messages:

INFORMATION: –> OLAP Catalog(AMD) exists in database Starting with Oracle Database 12c, OLAP Catalog component is desupported. If you are not using the OLAP Catalog component and want to remove it, then execute the ORACLE_HOME/olap/admin/catnoamd.sql script before or after the upgrade.

And:

INFORMATION: –> There are existing Oracle components that will NOT be upgraded by the database upgrade script. Typically, such components have their own upgrade scripts, are deprecated, or obsolete. Those components are: OLAP Catalog

Please go forward and remove it in your previous environment. You will find the steps also in the Oracle Database 11.0.2.4 section.

.

Oracle Database 12.2.0.1

XOQ – OLAP API

non-CDB

Remove XOQ by executing these scripts but add recompilation as well as approximately 20 synonyms will stay invalid:

$ sqlplus / as sysdba SQL> @?/olap/admin/olapidrp.plb SQL> @?/olap/admin/catnoxoq.sql SQL> @?/rdbms/admin/utlrp.sql

The recompilation will clean up the invalid objects. Furthermore the removal scripts have some failing “ drop ” statements. Please ignore them.

CDB

I adjusted this procedure slightly to comply with Oracle 19c. For Oracle 12.2.0.1 and Oracle 18c you may need to close and restart the PDBs after the first removal step. This is not necessary anymore in Oracle 19c, at least not in my environment.

At first, run this removal script can run in all PDBs:

$ORACLE_HOME/perl/bin/perl catcon.pl -n 1 -C ‘CDB$ROOT’ -e -b olapidrp_pdbs -d $ORACLE_HOME/olap/admin/ olapidrp.plb

The following steps must be execute for PDB after PDB as otherwise you’ll receive an ORA-65023: active transaction exists in container PDB$SEED during drop package dbms_cube_advise .

$ORACLE_HOME/perl/bin/perl catcon.pl -n 1 -c ‘PDB1’ -e -b catnoxoq_pdb1 -d $ORACLE_HOME/olap/admin/ catnoxoq.sql $ORACLE_HOME/perl/bin/perl catcon.pl -n 1 -c ‘PDB2’ -e -b catnoxoq_pdb2 -d $ORACLE_HOME/olap/admin/ catnoxoq.sql $ORACLE_HOME/perl/bin/perl catcon.pl -n 1 -c ‘PDB$SEED’ -e -b catnoxoq_pdbseed -d $ORACLE_HOME/olap/admin/ catnoxoq.sql $ORACLE_HOME/perl/bin/perl catcon.pl -n 1 -c ‘CDB$ROOT’ -e -b olapidrp_cdb -d $ORACLE_HOME/olap/admin/ olapidrp.plb $ORACLE_HOME/perl/bin/perl catcon.pl -n 1 -c ‘CDB$ROOT’ -e -b catnoxoq_cdb -d $ORACLE_HOME/olap/admin/ catnoxoq.sql $ORACLE_HOME/perl/bin/perl catcon.pl -n 1 -e -b utlrp -d ”’.”’ utlrp.sql

The recompilation at the end is required.

APS – OLAP Analytic Workspace

non-CDB

At first unlink the option from the Oracle kernel:

chopt disable olap

In the next step execute the removal script and recompile. The recompilation is necessary to clean up invalid public synonyms.

$ sqlplus / as sysdba @?/olap/admin/catnoaps.sql @?/rdbms/admin/utlrp.sql

CDB

When you remove APS from a Multitenant container database you must unlink the option from the Oracle kernel first. The database has to be shutdown during the relink operation. Afterwards all pluggable databases need to be opened again.

chopt disable olap

If you want to remove APS you will have to do this PDB after PDB, then at last in the CDB$ROOT as otherwise you’ll receive:

create or replace procedure aps_clean as * ERROR at line 1: ORA-65023: active transaction exists in container PDB$SEED

This issue still exists in Oracle 19c as it did exist since 12.2.0.1. A recompilation afterwards is mandatory.

$ORACLE_HOME/perl/bin/perl catcon.pl -n 1 -c ‘PDB2’ -e -b catnoaps_pdb2 -d $ORACLE_HOME/olap/admin/ catnoaps.sql $ORACLE_HOME/perl/bin/perl catcon.pl -n 1 -c ‘PDB1’ -e -b catnoaps_pdb1 -d $ORACLE_HOME/olap/admin/ catnoaps.sql $ORACLE_HOME/perl/bin/perl catcon.pl -n 1 -c ‘PDB$SEED’ -e -b catnoaps_pdbseed -d $ORACLE_HOME/olap/admin/ catnoaps.sql $ORACLE_HOME/perl/bin/perl catcon.pl -n 1 -c ‘CDB$ROOT’ -e -b catnoaps_cdb -d $ORACLE_HOME/olap/admin/ catnoaps.sql $ORACLE_HOME/perl/bin/perl catcon.pl -n 1 -e -b utlrp -d ”’.”’ utlrp.sql

AMD – OLAP Catalog

AutoUpgrade will give you a similar message such as:

============== BEFORE UPGRADE ============== RECOMMENDED ACTIONS =================== + Remove OLAP Catalog by running the 11.2.0.4.0 SQL script $ORACLE_HOME/olap/admin/catnoamd.sql script. The OLAP Catalog component, AMD, exists in the database. Starting with Oracle Database 12c, the OLAP Catalog (OLAP AMD) is desupported and will be automatically marked as OPTION OFF during the database upgrade if present. Oracle recommends removing OLAP Catalog (OLAP AMD) before database upgrade.

And in the “AFTER UPGRADE” section:

============= AFTER UPGRADE ============= INFORMATION ONLY ================ + Check the Oracle documentation for the identified components for their specific upgrade procedure. The database upgrade script will not upgrade the following Oracle components: OLAP Catalog,OWB The Oracle database upgrade script upgrades most, but not all Oracle Database components that may be installed. Some components that are not upgraded may have their own upgrade scripts, or they may be deprecated or obsolete.

If you are not using OLAP AMD, safely remove it from your Oracle 11.2.0.4 database before attempting the upgrade. As you will remove it in the source environment beforehand you won’t get into a situation with OLAP AMD in a Multitenant database.

Component Clean Up Series

Finally download a slide deck about the Component Clean Up on this blog:

https://mikedietrichde.com/slides/

Share this:

AdnanDBA: Remove OLAP From the Standard Edition database

OLAP is not an option available with standard edition database but it gets added in an invalid state when a database is created using one of…

Deleting OLAP Catalog Metadata

If you choose to delete a cube and generate a command report, you will see the following.

As long as you have directed the output of the SQL buffer to the screen or to a file, you will see messages describing the success or failure of each stored procedure call. If you choose to delete a cube without generating a command report, you will see only the following.

Use the CWM2_OLAP_MANAGER.SET_ECHO_ON procedure to display the command report on the screen. Use the CWM2_OLAP_MANAGER.BEGIN_LOG procedure to direct the report to a log file. See “Directing Output” for more information.

If you choose to drop the dimension objects associated with CWM1 dimensions, the report will also include the following command.

Depending on the metadata entities that you want to delete, the report will list commands like the following.

Each procedure in the CWM2_OLAP_DELETE package accepts a parameter that causes a command report to be written to the SQL buffer. You can generate this report without deleting any metadata. A separate parameter controls whether or not you actually execute the delete commands.

If your database includes users ‘TEST_USER1’ and ‘TEST_USER2’, you could delete the ‘TEST’ cube belonging to each of these users with the following command.

If your database includes users ‘TESTUSER1’ and ‘TESTUSER2’, you could delete the ‘TEST’ cube belonging to each of these users with the following command.

The following command deletes all the cubes in the GLOBAL schema whose names start with ‘a’.

For example, the following command deletes all the cubes belonging to the owner ‘GLOBAL’.

Wildcard characters are the underscore “_” and the percent sign “%”. An underscore replaces any single character, and a percent sign replaces any zero or more characters. An underscore, but not a percent sign, is also a legal character in a metadata owner or entity name. Any underscore character in the owner or entity name is treated as a wildcard, unless you precede it with a backslash “\” which acts as an escape character.

You can use wildcard characters to delete cubes, dimensions, and measure folders whose names meet certain criteria.

To rebuild analytic workspaces, use the OLAP DML to export the contents of the workspace to an EIF file, then import it in a new workspace. See “Procedure: Import a workspace from a 9i Database into a 10g Database” . If you are running in Oracle9i compatibility mode, you will need to re-enable the workspaces and re-create the metadata for the workspaces. See “Enabling Relational Access” .

To rebuild the OLAP Catalog metadata for a relational data source, you can export the data and metadata, delete it, then import it. Use the CWM2_OLAP_EXPORT package and the Oracle Export utility to do the export. Use CWM2_OLAP_DELETE to delete the metadata. Drop the source tables, then use the Oracle import utility to do the import. See Chapter 13, “CWM2_OLAP_EXPORT” .

OLAP dimensions created in Oracle Enterprise Manager use Oracle Database dimension objects. When deleting these CWM1 dimensions, you can choose whether or not to delete the associated dimension objects. For more information on Oracle dimension objects, see “CREATE DIMENSION” in the .

You can use the CWM2_OLAP_DELETE package to delete individual cubes, dimensions, or measure folders, or the entire contents of the OLAP Catalog. CWM2_OLAP_DELETE deletes CWM2 metadata created by the CWM2 PL/SQL packages and CWM1 metadata created by Oracle Enterprise Manager. CWM2_OLAP_DELETE deletes both valid and invalid metadata.

Summary of CWM2_OLAP_DELETE Subprograms

Table 10-1 CWM2_OLAP_DELETE Subprogram Description DELETE_CUBE Procedure

Deletes a cube in the OLAP Catalog. DELETE_DIMENSION Procedure

Deletes a dimension in the OLAP Catalog. DELETE_MEASURE_CATALOG Procedure

Deletes a measure folder in the OLAP Catalog. DELETE_OLAP_CATALOG Procedure

Deletes all the metadata in the OLAP Catalog.

DELETE_CUBE Procedure

This procedure can be used to delete a cube or group of cubes in the OLAP Catalog. You can also use this procedure to list the commands that will delete the cubes. You can choose to execute these commands or simply list them, without actually deleting the cubes. See “Using a Command Report”.

You can identify a group of cubes by specifying wildcard characters in the cube_owner and cube_name parameters. See “Using Wildcards to Identify Metadata Entities”.

When you delete a cube, its dimensions are not deleted.

OLAP Catalog cubes are displayed in the view ALL_OLAP2_CUBES.

Syntax

DELETE_CUBE ( cube_owner IN VARCHAR2, cube_name IN VARCHAR2, delete_report IN VARCHAR2, delete_cube IN VARCHAR2);

Parameters

Table 10-2 DELETE_CUBE Procedure Parameters Parameter Description cube_owner The owner of the cube. See “Using Wildcards to Identify Metadata Entities”. cube_name The name of the cube. See “Using Wildcards to Identify Metadata Entities”. delete_report Whether or not to list the commands that will delete the cubes. Specify ‘YES’ to list the commands. Otherwise specify ‘NO’. To display the output on the screen, use the CWM2_OLAP_MANAGER.SET_ECHO_ON procedure. To send the output to a file, use the CWM2_OLAP_MANAGER.BEGIN_LOG procedure. See “Directing Output” for more information. delete_cube Whether or not to actually delete the cubes. Specify ‘YES’ to delete the cubes. Otherwise specify ‘NO’.

Example

The following example first generates a command report for deleting the cwm2 cube PRICE_COST in the GLOBAL schema, then actually deletes the cube.

>set serveroutput on size 1000000 >execute cwm2_olap_manager.set_echo_on; >select * from all_olap2_cubes where OWNER =’GLOBAL’; OWNER CUBE_NAME NVALID DISPLAY_NAME SHORT_DESCRIPTION DESCRIPTION MV —— ——— —— ———— —————– ———– — GLOBAL PRICE_CUBE O PRICE_CUBE RU GLOBAL UNITS_CUBE O UNITS_CUBE RU GLOBAL PRICE_COST N PRICE_COST GS >execute cwm2_olap_delete.delete_cube(‘GLOBAL’, ‘PRICE_COST’, ‘yes’, ‘no’); EXECUTE cwm2_olap_cube.Drop_Cube(‘GLOBAL’, ‘PRICE_COST’); >select * from all_olap2_cubes where OWNER =’GLOBAL’; OWNER CUBE_NAME NVALID DISPLAY_NAME SHORT_DESCRIPTION DESCRIPTION MV —— ——— —— ———— —————– ———– — GLOBAL PRICE_CUBE O PRICE_CUBE RU GLOBAL UNITS_CUBE O UNITS_CUBE RU GLOBAL PRICE_COST N PRICE_COST GS >execute cwm2_olap_delete.delete_cube(‘GLOBAL’, ‘PRICE_COST’, ‘yes’, ‘yes’); EXECUTE cwm2_olap_cube.Drop_Cube(‘GLOBAL’, ‘PRICE_COST’); AMD-00003 dropped Cube “GLOBAL.PRICE_COST” >select * from all_olap2_cubes where OWNER =’GLOBAL’; OWNER CUBE_NAME NVALID DISPLAY_NAME SHORT_DESCRIPTION DESCRIPTION MV —— ——— —— ———— —————– ———– — GLOBAL PRICE_CUBE O PRICE_CUBE RU GLOBAL UNITS_CUBE O UNITS_CUBE RU

DELETE_DIMENSION Procedure

This procedure can be used to delete a dimension or group of dimensions in the OLAP Catalog. You can also use this procedure to list the commands that will delete the dimensions. You can choose to execute these commands or simply list them, without actually deleting the dimensions. See “Using a Command Report”.

You can identify a group of dimensions by specifying wildcard characters in the dimension_owner and dimension_name parameters. See “Using Wildcards to Identify Metadata Entities”.

If the dimension was created in Oracle Enterprise Manager, it is a CWM1 dimension. CWM1 dimensions have OLAP Catalog metadata and an associated Oracle dimension object.

When you delete a dimension, all references within cubes to the dimension are also deleted. This causes any cubes that used the dimension to become invalid.

OLAP Catalog dimensions are displayed in the view ALL_OLAP2_DIMENSIONS.

Syntax

DELETE_DIMENSION ( dimension_owner IN VARCHAR2, dimension_name IN VARCHAR2, delete_cwm1_dimension IN VARCHAR2, delete_report IN VARCHAR2, delete_dimension IN VARCHAR2);

Parameters

Table 10-3 DELETE_DIMENSION Procedure Parameters Parameter Description dimension_owner The owner of the dimension. See “Using Wildcards to Identify Metadata Entities”. dimension_name The name of the dimension. See “Using Wildcards to Identify Metadata Entities”. delete_cwm1_dimension Whether or not to delete the Oracle dimension object associated with a CWM1 dimension. Specify ‘YES’ to delete the Oracle dimension object. Otherwise specify ‘NO’. This parameter has no effect on CWM2 dimensions. delete_report Whether or not to list the commands that will delete the dimensions. Specify ‘YES’ to list the commands. Otherwise specify ‘NO’. To display the output on the screen, use the CWM2_OLAP_MANAGER.SET_ECHO_ON procedure. To send the output to a file, use the CWM2_OLAP_MANAGER.BEGIN_LOG procedure. See “Directing Output” for more information. delete_dimension Whether or not to actually delete the dimensions. Specify ‘YES’ to delete the dimensions. Otherwise specify ‘NO’.

Example

The following example first generates a command report for deleting the PROD dimension in the GLOBAL schema, then actually deletes the dimension. Since the dimension is a CWM2 dimension, the third parameter to the DELETE_DIMENSION procedure is ignored.

>set serveroutput on size 1000000 >execute cwm2_olap_manager.set_echo_on; >execute cwm2_olap_delete.delete_dimension (‘GLOBAL’, ‘PROD’, ‘no’,’yes’, ‘no’); EXECUTE cwm2_olap_dimension.Drop_Dimension(‘GLOBAL’, ‘PROD’); >execute cwm2_olap_delete.delete_dimension (‘GLOBAL’, ‘PROD’, ‘no’,’yes’, ‘yes’); EXECUTE cwm2_olap_dimension.Drop_Dimension(‘GLOBAL’, ‘PROD’); AMD-00003 dropped Dimension “GLOBAL.PROD”

DELETE_MEASURE_CATALOG Procedure

This procedure can be used to delete a measure folder or group of measure folders in the OLAP Catalog. You can also use this procedure to list the commands that will delete the measure folders. You can choose to execute these commands or simply list them, without actually deleting the measure folders. See “Using a Command Report”.

You can identify a group of measure folders by specifying wildcard characters in the measure_folder_name parameter. See “Using Wildcards to Identify Metadata Entities”.

OLAP Catalog measure folders are displayed in the view ALL_OLAP2_CATALOGS.

Syntax

DELETE_MEASURE_CATALOG ( measure_folder_name IN VARCHAR2, delete_report IN VARCHAR2, delete_measure_catalog IN VARCHAR2);

Parameters

Table 10-4 DELETE_MEASURE_CATALOG Procedure Parameters Parameter Description measure_folder_name The name of the measure folder. See “Using Wildcards to Identify Metadata Entities”. delete_report Whether or not to list the commands that will delete the measure folders. Specify ‘YES’ to list the commands. Otherwise specify ‘NO’. To display the output on the screen, use the CWM2_OLAP_MANAGER.SET_ECHO_ON procedure. To send the output to a file, use the CWM2_OLAP_MANAGER.BEGIN_LOG procedure. See “Directing Output”. delete_measure_catalog Whether or not to actually delete the measure folders. Specify ‘YES’ to delete the measure folder. Otherwise specify ‘NO’.

Example

The following example deletes the two measure folders whose names start with ‘TEMP’.

>set serveroutput on size 1000000 >execute cwm2_olap_manager.set_echo_on; >execute cwm2_olap_delete.delete_measure_catalog (‘TEMP%’, ‘no’, ‘yes’); AMD-0003 dropped Catalog “Temp1” AMD-0003 dropped Catalog “Temp2”

DELETE_OLAP_CATALOG Procedure

This procedure can be used to delete all the metadata in the OLAP Catalog. You can also use this procedure to list the commands that will drop each metadata entity. You can choose to execute these commands or simply list them, without actually deleting the metadata. See “Using a Command Report”.

OLAP Catalog metadata is displayed in the OLAP Catalog metadata views, described in Chapter 5.

Syntax

DELETE_OLAP_CATALOG ( delete_cwm1_dimension IN VARCHAR2, delete_report IN VARCHAR2, delete_olap_catalog IN VARCHAR2);

Parameters

Table 10-5 DELETE_OLAP_CATALOG Procedure Parameters Parameter Description delete_cwm1_dimension Whether or not to delete the Oracle dimension object associated with each CWM1 dimension. Specify ‘YES’ to delete the Oracle dimension object. Otherwise specify ‘NO’. This parameter has no effect on CWM2 dimensions. delete_report Whether or not to list the commands that will delete the metadata. Specify ‘YES’ to list the commands. Otherwise specify ‘NO’. To display the output on the screen, use the CWM2_OLAP_MANAGER.SET_ECHO_ON procedure. To send the output to a file, use the CWM2_OLAP_MANAGER.BEGIN_LOG procedure. See “Directing Output” for more information. delete_olap_catalog Whether or not to actually delete all the metadata in the OLAP Catalog. Specify ‘YES’ to delete the metadata. Otherwise specify ‘NO’.

Example

The following example deletes all the metadata in the OLAP Catalog without generating a command report. Any associated Oracle dimension objects are not deleted.

>set serveroutput on size 1000000 >execute cwm2_olap_manager.set_echo_on; >execute cwm2_olap_delete.delete_olap_catalog(‘no’, ‘no’, ‘yes’);

키워드에 대한 정보 olap analytic workspace invalid

다음은 Bing에서 olap analytic workspace invalid 주제에 대한 검색 결과입니다. 필요한 경우 더 읽을 수 있습니다.

이 기사는 인터넷의 다양한 출처에서 편집되었습니다. 이 기사가 유용했기를 바랍니다. 이 기사가 유용하다고 생각되면 공유하십시오. 매우 감사합니다!

사람들이 주제에 대해 자주 검색하는 키워드 OLAP (Online Analytical Processing)

  • 동영상
  • 공유
  • 카메라폰
  • 동영상폰
  • 무료
  • 올리기

OLAP #(Online #Analytical #Processing)


YouTube에서 olap analytic workspace invalid 주제의 다른 동영상 보기

주제에 대한 기사를 시청해 주셔서 감사합니다 OLAP (Online Analytical Processing) | olap analytic workspace invalid, 이 기사가 유용하다고 생각되면 공유하십시오, 매우 감사합니다.

Leave a Comment