Delete dimension members thru OLAP API?

Hi All,
I would like to delete dimension members from an AW that we have painfully BI Beans enabled.
Adding rows to my dimension table get properly updated in my AW dimension but I haven't found a way (call to a package) to delete that member so that the metadata (in OLAPSYS) doesn't get mixed up.
Any idea, hint or pointer (to a document may be) would be greatly appreciated.
Thanks in advance,
Pierre

Adding or deleting rows in tables doesn't affect any metadata structure. As a matter of fact, you can define metadata without any row in tables because what it's looking at is the structure of tables.
To delete what you just added, try:
1. Delete rows from source table
2. Run refresh AW on the dimension

Similar Messages

Deleting dimension members

We have an AW with cubes refreshing every day. Fast solve of these cubes with incremental set of data finishes usually within an hour or two.
Our recent requirement needs for us to remove some old facts as well as a few dimension members. The facts can be cleared but we noticed that deleting dimension members (using synch load) is causing a full cube solve due to changed relations. With the amount of data existing in this AW, full solve takes about 2 days to complete. Deleting dimension members for which we never ever loaded any facts also causes the same result as above.
I was wondering if there is any way we can delete these dimension members without triggering a full cube solve.
Another question is if it is possible to update dimension primary keys inside of the AW?
Any help is really appreciated.
Database Version 11.2.0.3

These types of questions have been answered in the past by David Greenfield.
There are two ways to delete a dimension member through commands.
(1). OLAP dml command "REMOVE_DIMENSION_MEMBER" explained here: http://docs.oracle.com/cd/E11882_01/olap.112/e17122/dml_commands_2042.htm#OLADM2692
OR
(2). dbms_cube.build command:
exec dbms_cube.build(q'! "TIME" USING (DELETE FROM DIMENSION WHERE MEMBER = 'APR-2011') !');
Take a look at this old post, where David Greenfield explained it.
https://forums.oracle.com/message/9426946
There is no way to rename a dimension member in a standard-form analytical workspace. There is "MAINTAIN RENAME" olap dml command, but it will not work with dimensions created through AWM. You can add the new dimension member, then copy cube data associated with old/existing member to the new member and then delete the old member.
For cube copy data example, take a look at these old (15-Feb-2011, 16-Feb-2011 and 17-Feb-2011) posts by David Greenfield:
https://forums.oracle.com/thread/2176409

Delete dimension members

Hi,
I am trying to delete some members in a dimension, however when I process the dimension, I get an error message, saying the member is being used.
I had run the CLEAR DM package for the member in question, so I was a bit surprised but then found that the database still contained zero values for this member.
I found this thread (Delete member of a dimension) where is says to either run a light optimize or compress the cube.
I did run the light optimize, which made no difference at all, the zero values are still present.
My question is, how do I compress the cube with zero-eliminations. Is that something I can do from the BPC Admin console?
Thanks,
Arnold

Hi
The following possibilities are there:
01. The Dimension along with its members might be used by Calling/linking it in to another Application
02. The member access to the dimension might be given to all users in the AppSet and used it by some of the users.
(The possibilites of revoking the permissions granted to that Dimesnion prior to used by another user for another Application are remote, unless the another Application has to be deleted)
03. Though you've tried to delete the data from the existing member forcibly from back end, it still exist with its image of Cube as it is referring to another Application.
suggestions: Please cross verify the above possibilites
regards
ukraghu

7.5 NW: Uunable to delete dimension members from the entity dimension

Hi,
I would really appreciate a solution to this. We are planning on implementing an IFRS consolidation using the SAP IFRS Starter Kit. We have created a copy of the IFRS Starter Kit, without any data. In order to customise it for our purposes, we have decided to keep the sample dimension members in Accounts, Flow and AuditID but delete the data in other dimensions. We have managed to delete the sample dimension members from the Time, Inter-company and Conoscope dimensions but are unable to do it for the Entity and RateEntity dimension.
Can anyone please explain why this is happening? There is no data in the application and so, why is this happening? We are on Service Pack 5.
Many thanks in advance.

Hi,
Before going into the BPFs, i am sure you would have already checked, I would do the following:
-Try to process the entity dimension in offline mode. I have seen this happening with some dimenions that i know there is absolutely no transaction action. Just check processing the entity in offline mode. Do not untick 'take the appset offline'.
- You would have done this. Double check for the transaction data.
- Regarding BPFs, its not easy to check this. we had this situation earlier. Please go into the backend and in se16 you will find all the BPF tables with UJB*
There would around 10-12 such tables. Have alook in them. Not all tables need to be looked into. But please have a check there.
- Also check if entity has been referenced to any other dimension. Its good to check if you have INTCO dimension to see if it is referenced there.
Thanks,
Sreeni

Error while enabling dimension for OLAP API and BI Beans

Hi, I've created some dimensions in OLAP Catalog using CWM2 packages. These dimensions have only one hierarchy and one or two levels.
I also have an Analytic Workspace, and I've created these dimensions in this A.W. using CREATE_AWDIMENSION method from DBMS_AWM package.
Everything ok at this point.
Next, I've tried to enable these aw dimensions for the OLAP Api and BI Beans, using CREATE_AWDIMENSION_ACCESS_FULL/CREATE_AWDIMENSION_access methods from DBMS_AWM. Strangely, dimensions whith two levels are enabled ok, but dimensions with only one level can't be enabled. If I use CREATE_AWDIMENSION_ACCESS and I execute generated script, an error appears when trying VALIDATE_DIMENSION, with a text like this:
.ENTITY TYPE ENTITY NAME STATUS COMMENT
. Dimension AW1.DIM1 INVALID ERROR: Component entity.
- Default Display Hierarchy: "J0".
. Hierarchy J0 INVALID ERROR: Hierarchy Top Level not found.
My database ir 9.2.0.6. What is failing ? Some idea ? Thanks by your help.

Not sure if it's valid to have a dimension with 1 hierarchy and 1 level in that hierarchy. The hierarchy may have to have at least 2 levels. If you want the configuration of a dimension with 1 hierarchy and 1 level, CWM2 may want you to omit the hierarchy, thus creating the dimension with only 1 level.

Delete dimension/cube in Analytic Workspace

Hello, I've created some dimensions and cubes in an analytic workspace using DBMS_AW package. But, How can I delete these objects using a similar methodology? I have not found any procedure like CREATE_AWDIMENSION/CREATE_AWCUBE that helps me to delete the object.
Thanks by your help.

In 9.2x code stream, having it not in cwm2/all_olap2_dimensions means it will be invisible/unaccessible to the OLAP API but, as you point out, it still exists in the AW, and as such, it still exists in all_olap2_aw_dimensions.
The early comment was a way to potentially "work around" the inability of no automation to "fully" delete it, by suggesting a way to "partially" delete it so as to "hide" the dimension from the OLAP API, without actually deleting it (or any of it's storage, obviously) from the AW.

Java olap api

hi all,
my application uses SQL queries to pull data from Oracle10g.
now i'm going to enhance it with OLAP support
don know how to use JAVA OLAP APIs to pull data from relational tables
after reading documents provided in www.oracle.com/.... i could see that there are a many ways to do. don know how to start. no document gives a step by step procedure.
the main problem is i want to pull data from existing relational tables only using my JAVA code thru OLAP APIs.
not able to understand the sample codes available in oracle web site.
anyone can help me with simple java olap codes
regards
swetha

You should post this question to the OLAP forum.

How to delete the members in one dimension use the maxl script

i have question that i want to delete the members in one dimension useing the maxl script, but i do not know how to do it. can the maxl delete the members in one dimension? if can, please provide an sample script, thank you so mcuh.

MaxL does not have commands to alter an outline directly, except the reset command which can delete all dimensions but not members selectively. The best you could do would be to run a rules file (import dimensions) using a file that contains the members you want to keepload rule for the dimension. As typical the warning is to test this first before you do it on a production database

Dimension members were not deleted after refresh in Planning desktop

Hi
A Planning application's outline was restored from backup.
It contains some dimension members which were deleted from Planning Web some weeks before and there were made many Planning refreshes after. Full database refresh had been made in Planning desktop and these members were not removed. As refreshing is a procedure to keep metadata in correspondence such result isn't expected in my opinion.
Is it normal behavior ?

Hi
i had a similar problem before. here is what i did
add the member again.
refresh
delete the member
refresh again.
this solves the relational repositories sync issue.
hope this helps.
Dornakal.
www.dornakal.blogspot.com

Not able to delete any Entity Dimension members

Hi All,
I am trying to delete some Entity Dimension members but its not allowing me to delete. This problem is only for Entity Dimension.
I can edit Entity member name or properties successfully but not able to delete or move the position.
I also tried to check member usage but its not giving me any results, a blank screen comes and planning goes down after some time. Same happens when I try to delete any Entity member.
I have admin rights on Planning and I can delete other dimension member but not for Entity. There is no workflow started for Entity but If it is than also it pop-ups that after member deletion all planning unit will be lost. I have bounced planning DB and also restarted all Hyperion services but still no luck.
Please let me know if anyone has faced this issue or have any solution to resolve.
Regards
Vishal

Hi John,
After uncheck of "enabled for process management" for all Scenario along with Version dimension members , this issue is now resolved. But its a temporary resolution as client has not yet started any workflow so we can uncheck that options ,but when they need to start workflow process then we have to check this options again which will start this issue again.
Do you have any permamant resolution for this issue?
Thanks for your help.
Regards
Vishal

Delete a GROUP thru API

Hello everyone;
I used one of HTMLDB API: HTMLDB_UTIL.CREATE_USER_GROUP thru a table trigger to create a User groups for categorizing users and managing user privileges.
I searched all the forum and HTMLDB document but couldn't find how to delete USER_GROUP thru API something like
HTMLDB_UTIL.DELETE_USER_GROUP or HTMLDB_UTIL.REMOVE_USER_GROUP
Is any way to delete or remove USER_GROUP by using API?
Thank you.
Shaun

Just curious if you can delete a group through the API since this thread?
Thanks
Matt

Deleting custom Period dimension members

Hi,
We are in Planning 11.1.2.1. and we created custom period dimension members (while creating application). Now we would like to delete one of those members (whcih is at level0). Obviously we don't see an option of delete in planning web interface. One option is to recreate the application but is there any way we can delete this member in oracle database. If yes, it would be great if you can provide us the table details.
Thanks,
Siva

As John suggested it is not advisible, however you can delete in Essbase using Planning:
1. Edit custom dimsion
2. un-select all plan type
3. cube referesh
Hope this will help.

How to delete all members at same sub level under one dimension?

Hello,
How do I delete all members at a certain sub level in a demension? I know I can do this manually in the hyperion essbase admin panel, but the number of members is large. How would I go about removing these members using a script or excel?

Hi,
The API used in the excel template is 9.2. You may need to update this according to your version of Essbase.
You can delete the existing module and import the esb32.bas and esberror.bas module which is located at C:\Hyperion\AnalyticServices\api\include directory (this is for version 9)
You also need to install the API when you install essbase client (add-ins) on your PC.
To open the VBA, click Ctrl-F11 after you open the workbook.
The program should output 3 message if everything is OK:
1. Write Outline Success: hOutline = ... (any number)
2. Restructre Successful: hCtx = ..., ESB_DOR_ALLDATA = 1
3. Close outline Successful: hOutline = ... (any number)
Regards

HOW can i delete the members in dim using MAXL

Hi All,
I want to delete the all the memebers for dimensions before reloading so how ca n i write the maxl script for this to delete the members in the dimensions
plz can any one help on this its very urjent ,
It would be appriciated ...
Thanks

There is no way to alter an outline with MaxL, MaxL is an admin language for processing. The only option, as Glenn mentioned is to issue the reset all command to blow away everything. But you probably don't want to do that, so instead you use Maxl to run a series of load rules to achieve your goal.
Load rules do not have functionality to delete outline members, it does have a feature however that allows you to remove unspecified members from a dimension build, so when loading in your members, if existing members are not in the import, they are removed. So Glenn's point was to create a source file with a single dummy member. When you load using "Remove Unspecified" it will delete all the members and just keep the one dummy member. Then when you go back a second time and actually load the real members, the dummy member will be removed and you will have a clean dim with only your new members. This is a work around solution, but it's what a lot of people do.
Now if you have 15 dimensions you need to do this with, you might want to take a slightly different approach. I'm assuming 15 dimensions is probably an ASO cube and this method will be preferable to avoid outline fragmentation.
Create a copy of your outline with all the base dimensions that do not change intact. For the ones that do change, just have your dim root member. Consider this your starting outline template and save a copy of it. When you want to rebuild your cube have a server process that takes the copy of your template outline and copies it over your existing outline file in the directory structure. Then run your load rules to import your new members.

An error occurred during olap API metadata retrieval. This is probably caus

this is what i have done so far. i really nead some help asap!!!
1. Install Oracle 9i Release 2 (9.2.0.1) Enterprise Edition with the General purpose database configuration (Data warehouse works as well). At the end of the installation I chose the password management button to change passwords for the few necessary accounts: SYS, SYSTEM, OLAPSYS, SH.
2. Download the p3948480_9206_WINNT.zip from metalink, the 9.2.0.6 patchset
3. Shut down any existing Oracle9i database instances with normal or immediate priority. Stop all listener and other services running in the Oracle home directory where you want to install the patch set.
4. unzip the content of thepatch to a temp directory
5. start setup.exe under the temp directory (it will start the Oracle Universal installer 10.1.0.3)
6. install the patchset to your Oracle home, selecting the source in the temp_dir\stage\products.jar file
7. review carefully the post-installation tasks for the patchset:
Review the following sections before upgrading a database (quote from the patchset html readme):
8.2.1.1If JServer is part of the installation ensure that there is at least 10 MB of free space allocated to the SYSTEM tablespace.
8.2.1.2 Check XDB Tablespace Size
For RAC installations, ensure that there is at least 50 MB of free space allocated to the XDB tablespace.
8.2.1.3 Set the SHARED_POOL_SIZE and JAVA_POOL_SIZE Initialization Parameters
Set the value of the SHARED_POOL_SIZE and the JAVA_POOL_SIZE initialization parameters as follows:
Start the database:
SQL> STARTUP
If necessary, enter the following command to determine whether the system uses an initialization parameter file (initsid.ora) or a server parameter file (spfiledbname.ora):
SQL> SHOW PARAMETER PFILE;
This command displays the name and location of the server parameter file or the initialization parameter file.
Determine the current values of these parameters:
SQL> SHOW PARAMETER SHARED_POOL_SIZE
SQL> SHOW PARAMETER JAVA_POOL_SIZE
If the system is using a server parameter file:
If necessary, set the value of the SHARED_POOL_SIZE initialization parameter to at least 150 MB:
SQL> ALTER SYSTEM SET SHARED_POOL_SIZE='150M' SCOPE=spfile;
If necessary, set the value of the JAVA_POOL_SIZE initialization parameter to at least 150 MB:
SQL> ALTER SYSTEM SET JAVA_POOL_SIZE='150M' SCOPE=spfile;
If the system uses an initialization parameter file, if necessary, change the values of the SHARED_POOL_SIZE and the JAVA_POOL_SIZE initialization parameters to at least 150 MB in the initialization parameter file (initsid.ora).
Shut down the database:
SQL> SHUTDOWN
8.2.2 Upgrade the Database
After you install the patch set, you must complete the following steps on every database associated with the upgraded Oracle home:
Log on as a member of the Administrators group to the computer where the Oracle components are installed.
Use SQL*Plus to login to the database as the SYS user with SYSDBA privileges:
sqlplus /NOLOG
CONNECT SYS/password AS SYSDBA
Enter the following SQL*Plus commands:
SQL> STARTUP MIGRATE
SQL> SPOOL patch.log
SQL> @ORACLE_BASE\ORACLE_HOME\rdbms\admin\catpatch.sql
SQL> SPOOL OFF
Restart the database:
SQL> SHUTDOWN
SQL> STARTUP
Run the utlrp.sql script to recompile all invalid PL/SQL packages now instead of when the packages are accessed for the first time. This step is optional but recommended.
SQL> @ORACLE_BASE\ORACLE_HOME\rdbms\admin\utlrp.sql
12. Install JDeveloper 9.0.4 (download it from OTN and just unzip it in a directory ... it doesn't require an oracle home)
13. Install BI Beans 9.0.4 (download it from OTN as well), run the setup.exe that comes with it and in the destination oracle home select the directory where you installed JDeveloper and give an oracle home name to it)
14. Install the BIBDEMO schema:
Create a directory on the computer that is running the Oracle9i database. This install_home directory is the location to which you will upload the data files that are required to build the BIBDEMO schema.
On the computer where BI Beans is installed, locate the bibeans_home\bibdemo_schema folder (where bibeans_home is the root folder of your BI Beans installation). Copy all of the files found in this folder to the install_home folder on your server machine.
Open a DOS prompt and navigate to the install_home folder.
Run bibdemo.bat to install the schema, using the following syntax:
bibdemo.bat <path to Oracle database files >
For example, for an instance named my9iService, enter the following:
bibdemo.bat D:\OraHome1\oradata\my9iService
You are prompted for the password for the sys as sysdba user.
The script takes approximately 15 minutes to run, depending on the machine specifications. It is normal to see some error messages while the script is running. In addition, when materialized views are being created in the database, the script will appear to stop; this is also normal. A clear message will tell you when the script has completed.
The log files (*.log) that are generated by the installation script are stored in the folder from which you ran the script.
Here's what
bi_checkconfig.bat -h ana -po 1521 -sid proiect -u bibdemo -p bibdemo -q
returned:
BI Beans Diagnostics(v1.0.2.0) 2/28/05
===============================================================================
JDEV_ORACLE_HOME .......................... = E:\OraDS
JAVA_HOME ................................. = E:\OraDS\jdk
JDeveloper version ........................ = 9.0.4.1.1.1436
BI Beans release description .............. = BI Beans 9.0.4 Production Release
BI Beans component number ................. = 9.0.4.23.0
BI Beans internal version ................. = 2.7.5.32
Connect to database ....................... = Successful
JDBC driver version ....................... = 9.2.0.4.0
JDBC JAR file location .................... = E:\OraDS\jdev\lib\patches
Database version .......................... = 9.2.0.6.0
OLAP Catalog version ...................... = 9.2.0.1.0
OLAP AW Engine version .................... = 9.2.0.1.0
OLAP API Server version ................... = 9.2.0.1.0
BI Beans Catalog version .................. = N/A; not installed in bibdemo
OLAP API JAR file version ................. = 9.2
OLAP API JAR file location ................ = E:\OraDS\jdev\lib\ext
Load OLAP API metadata .................... = Successful
Number of metadata folders ................ = 2
Number of metadata measures ............... = 12
Number of metadata dimensions ............. = 8
Testing sample query for measures and dimensions
(S=Schema, C=Cube, M=Measure, D=Dimension)
1/21) Measure Budget ................... = Successful
S=BIBDEMO, C=BIBDEMO_BUDGET_CUBE, M=BUDGET
2/21) Measure Actual ................... = Successful
S=BIBDEMO, C=BIBDEMO_ACTUAL_CUBE, M=ACTUAL
3/21) Measure Close Price .............. = Successful
S=BIBDEMO, C=BIBDEMO_STKPRICE_CUBE, M=STKPRICE_CLOSE
4/21) Measure Open Price ............... = Successful
S=BIBDEMO, C=BIBDEMO_STKPRICE_CUBE, M=STKPRICE_OPEN
5/21) Measure Low Price ................ = Successful
S=BIBDEMO, C=BIBDEMO_STKPRICE_CUBE, M=STKPRICE_LOW
6/21) Measure High Price ............... = Successful
S=BIBDEMO, C=BIBDEMO_STKPRICE_CUBE, M=STKPRICE_HIGH
7/21) Measure Stock Volume ............. = Successful
S=BIBDEMO, C=BIBDEMO_STKPRICE_CUBE, M=STKPRICE_VOLUME
8/21) Dimension Division ............... = Successful
S=BIBDEMO, D=DIVISION
9/21) Dimension Line Items ............. = Successful
S=BIBDEMO, D=LINE
10/21) Dimension Time ................... = Successful
S=BIBDEMO, D=TIME
11/21) Dimension Day .................... = Successful
S=BIBDEMO, D=DAY
12/21) Dimension Stock .................. = Successful
S=BIBDEMO, D=STOCK
13/21) Measure Costs .................... = Successful
S=BIBDEMO, C=ANALYTIC_CUBE, M=F.COSTS
14/21) Measure Promotion ................ = Successful
S=BIBDEMO, C=ANALYTIC_CUBE, M=F.PROMO
15/21) Measure Quota .................... = Successful
S=BIBDEMO, C=ANALYTIC_CUBE, M=F.QUOTA
16/21) Measure Units .................... = Successful
S=BIBDEMO, C=ANALYTIC_CUBE, M=F.UNITS
17/21) Measure Sales .................... = Successful
S=BIBDEMO, C=ANALYTIC_CUBE, M=F.SALES
18/21) Dimension Channel ................ = Successful
S=BIBDEMO, D=CHANNEL
19/21) Dimension Geography .............. = Successful
S=BIBDEMO, D=GEOGRAPHY
20/21) Dimension Product ................ = Successful
S=BIBDEMO, D=PRODUCT
21/21) Dimension Time ................... = Successful
S=BIBDEMO, D=TIME
Metadata output location .................. = E:\OraDS\bibeans\bi_checkconfig\bi
_metadata.txt
To interpret this output, see the "Displaying Information about your Oracle9i Bu
siness Intelligence Beans Client Configuration" technical note, whose file name
is bi_checkconfig_tn.html
These diagnostics are captured in: E:\OraDS\bibeans\bi_checkconfig\bi_checkconfi
g.xml
now: i have created some new stuff:
1). user ana with roles:
-dba
-olap_dba
-connect
-resource
(same roles as bibdemo)
2).schema ana; tablespace ana (permanent), tablespace anatemp (temporary)
3).i have created some relational tables and i have inserted some data in them:
agent, aparat (cofee machines), beneficiar (clients), locatii (city), raport (REPORT), timp (time), tipaparat (types of cofee machines), tipbautura (products : types of cofee made by all the cofee machines), zone (state)
4). one fact table with:
- sold cantity (measure)
- id_bautura (id_product) primary key
- id_timp(id_time) primary key
- id_beneficiar (id_client) primary key
- id_agent primary key
- id_locatie (id_city) primary key
- id_aparat (id_cofee_machine)primary key
i have inserted some data also
5).dimensions:
AGENT_DIM :levels: codag(id_agent), numeag (agent name), telefag (agent phone number)from relational table agent
BENEFICIAR_DIM :levels: codben (id_client), denumire (client name), adresa (adress) ,codl (id_city) etc from relatinal table beneficiar (clients)
TIMP_DIM :levels: id, year, month from relational table timp (time)
TIPBAUTURA_DIM :levels: codbautura (id_product), numebautura (product name)from relational table tipbautura (products)
ZONA_DIM :levels: codzona (id state), numezona (state name), codoras (id city), numeoras (city name) with ierarhy id_state---id_city FROM 2 RELATINAL TABLES CITY AND STATE!!!!!!!! AM I ALOUD TO DO THAT?????
DO I NEED TO CREATE A DIMENSION FROM ONLY ONE TABLE???????
APARAT_DIM :LEVELS: codben (id client), codtip (id machine type), denumireap (machine type name), matricolap ((machine id) (FROM 2 RELATIONAL TABLES ALSO!!!!!!! FROM TYPES OF COFEE MACHINES AND COFEE MACHINES!!!!!
6). I HAVE NOW CREATED THE CUBE FROM THE FACT TABLE AND WITH ALL THE DIMENSIONS
7). summary advisor wizard NOT WORKING! IT NEVER STOPS!
8). I HAVE CREATED ALSO ONE materialized view FOR THE CUBE
IF I COMPILE IT... NO ERRORS
9). CUBE VIEWER NOT WORKING!!!!!!! IT ONLY APEARS A BELL!!!
NOW IF I RUN BI_CHECK CONFIG ON ANA AND ALSO ON BIBDEMO!!!!!!!!!!!!
IT SAYS:
1) An error occurred during olap API metadata retrieval. This is probably caused by inconsistent metadata.
============================================================================
oracle.express.ExpressServerExceptionError class: Unknown Error
Server error descriptions:
INI: System failure, Generic at TxsOqConnection::getDefaultDatabase
at oracle.express.olapi.data.full.ExpressDataProvider.getMetadataProviderInterface(ExpressDataProvider.java:1003)
at oracle.olapi.metadata.MetadataFetcher.initialize(MetadataFetcher.java:73)
at oracle.olapi.metadata.MetadataFetcher.<init>(MetadataFetcher.java:45)
at oracle.olapi.metadata.BaseMetadataProvider.<init>(BaseMetadataProvider.java:47)
at oracle.olapi.metadata.mdm.MdmMetadataProvider.<init>(MdmMetadataProvider.java:130)
at oracle.express.olapi.data.full.ExpressDataProvider.getDefaultMetadataProvider(ExpressDataProvider.java:964)
at oracle.dss.metadataManager.server.drivers.mdm._92.MDMMetadataDriverImpl_92.getMdmMetadataProvider(MDMMetadataDriverImpl_92.java:1133)
at oracle.dss.metadataManager.server.drivers.mdm._92.MDMMetadataDriverImpl_92.attach(MDMMetadataDriverImpl_92.java:810)
at oracle.dss.metadataManager.server.drivers.mdm.MDMMetadataDriverImpl.attach(MDMMetadataDriverImpl.java:125)
at oracle.dss.metadataManager.server.MetadataManagerImpl.buildObjectModel(MetadataManagerImpl.java:1092)
at oracle.dss.metadataManager.server.MetadataManagerImpl.attach(MetadataManagerImpl.java:969)
at oracle.dss.metadataManager.client.MetadataManager.attach(MetadataManager.java:876)
at oracle.dss.metadataManager.client.MetadataManager.attach(MetadataManager.java:799)
at BICheckConfig.checkConnection(BICheckConfig.java:277)
at BICheckConfig.main(BICheckConfig.java:1348)
I TRYED ALSO WITH USER ANA WITH ROLES:
- DBA
- CONNECT
-RESOURCE
- OLAP_USER
NOT WORKING! AND ALSO BIBDEMO NOT WORKING!
WHAT AM I MISSING? SHOULD I USE AW MANAGER? OR DO I NEED TO CREATE AN AMNALITIC WORKSPACE???
WHAT ARE THE STEPS TO CREATE A GOOD METADATA????

Hi,
The issue here is if the whole catalog is corrupt or just one schema. So to try and determine the status of the catalog I would try:
1) Using OEM remove all the objects you created
2) I presume you created your database using the Database Configuration Assistant? You should have used the warehouse template
3) Make sure the following accounts are unlocked and also not expired : SH, OLAPSYS
4) Make sure the password for the SH schema is SH
5) Make sure the password for the OLAPSYS account is manager
6) Install the BIBDEMO schema that is shipped with BI Beans. This in the jdev_home/bibeans/bibdemo_schema
The installation process will remove SH schema from the OLAP catalog.
7)Once this is installed use JDeveloper to see if you can create a crosstab or graph.
8) If the BIBDEMO schema works try creating your new schemas one at a time.
9) Make sure the if you define the a dimension as type time it has END_DATE (column type DATE) and TIME_SPAN (column type number) defined. Otherwise don't define the dimension as type time.
Hope this helps
Keith Laker
Product Manager
Oracle Business Intelligence Beans

Delete dimension members thru OLAP API?

Similar Messages

Maybe you are looking for