11g - list of Workspaces in OLAP DML

Similar Questions

• Verification of the OLAP DML queries

  I work in my thesys and I want to know if is there a way to watch or even better, checking of queries with tools like awm. AWM is a good tool with graphics options, but I need to see the exact OLAP DML queries made the analytic workspace, I mean, a kind of fine-grained auditing. Thank you very much. Furthermore, I m working with Oracle 10 G release 2, and my analytic workspace is one made with the overall scheme.

  There are a few options to try, depending on what you want to audit:
  1. turn on SQL tracing
  2. in the AWM OLAP worksheet, use the command RECAP previous DML list calls
  3 turn the tracking spreadsheet OLAP DML:

  dbgoutfile dir_alias
  prgtrace = y
  "Open data viewer.
  dbgoutfile expressions of folklore ' close file when finished.»

• [OLAP DML] display on the screen the output so that the program is running

  Hello
  
  I am running a script in AWM that is long enough, and I placed a few little 'show' I know what the program, but it won't appear on the screen exits until the program ends. I guess that he wrote all the outputs in a sort of buffer and release the contents of the buffer at the end of the program.
  
  How I get to the release of this stamp permanently?
  
  Thank you

  I think that the relational analogy would be an anonymous pl/sql block enforcement of a list of commands for displaying a list of useful log dbms_output.put_line instructions:
  Just like with the purchase SHOW and olap cmd line, you see not the newspaper of the dbms_output running while the pl/sql program is running... you have to wait until you can see the log ends.

  You can write to a file and close/exit the file every time or you can write to table and validation every time, but I guess some such heavy lifting is necessary if you want to follow the long process to half-way in the course of execution.

  NOTE: For regular operation as dbms_cube.build load/forecast/attribute/steps of the process, you can always execute queries on halfway CUBE_BUILD_LOG etc. But if it's pure olap dml actions performed so no pre-built handle carefully to check the middle of things exist.

• Anyone know of a good tutorial OLAP DML/DDL?  (and NOT reference guide)

  In addition to the analytic workspace, I'm learning to build cubes by using just the OLAP DML / DDL language.
  
  Oracle and others have published many documents of reference on the language of the OLAP DML / DDL but I can't find a real tutorials that logically guide me through the process of creating cubes and everything that goes with it (definition of the dimensions, hierarchies, measures, calculations etc...) All the reference material is divided into pieces and difficult to learn effectively. Does anyone have a good OLAP DML / DDL tutorial links they could recommend? Thank you.

  John W wrote:
  Oracle and others have published a lot of reference material on the language of the OLAP DML / DDL but I can't find a real tutorials that logically guide me through the process of creating cubes and everything that goes with it (definition of the dimensions, hierarchies, measures, calculations etc...) All the reference material is divided into pieces and difficult to learn effectively. Does anyone have a good OLAP DML / DDL tutorial links they could recommend? Thank you.

  It is a very difficult task. The OLAP DML/DDL only supports relationships, dimensions (very primitive) and multidimensional basic variables. Dimensions and the visible cubes from the outside are a building a lot of components objects (a dimension has several primitive dimensions and relationships organized to create the DIMENSION of upper level that goes hand in hand with a cube, a cube a variable multiple and other pieces that get together) in the AW, more a bunch of objects of metadata in the dictionary of the Oracle.

  You really want to try to create your own and not expect to interact with OLAPI interfaces. It is possible to build your own version of things, but you also have to make your own view generation, etc. There are applications that are created from scratch, but they are completely from scratch (including whatever interactions they have through SQL). Everything you create will not work with all interfaces provided by Oracle, or the recently announced package of Simba MDX.

  Jim

• Simple matter of OLAP DML

  I take an initial stab at the use of OLAP DML on the OLAP worksheet and I try first to apply a simple order limit on a dimension, but I can't make it work. I have several OLAP DML guides, so I lack of reading material, but they will not help with this.
  
  I have a dimension called DIM_TEAM. It has 3 levels in its hierarchy which (highest to lowest) are: ALL_TEAMS, LEAGUE and TEAMS.
  
  I want to limit the value of DIM_TEAM to "BOS". "BOS" is a value on the level down the hierarchy that caters to TEAMS
  
  When I enter the command: LIMIT DIM_TEAM to "BOS"
  
  I get the error: is not a valid AW_BALL2 BOS! DIM_TEAM
  
  Why does this work? Y at - it a preliminary order, I have to question before executing this command LIMIT? Thank you

  'HR' is the logical name of the measure; you will need to reference its physical name when using the REPORT command.

  The physical name of the variable data storage will vary depending on the version of database (10 g or 11 g?) and if your cube uses compressed composite or not.

  For reporting purposes, you could report on the cube 'formula' that will '_', where is the logical name of your cube, and will be 'HR '.

  EDIT:
  For point 2), you should not use OLAP worksheet limit orders and the viewer data in combination as limits get "confused." the data viewer should allow you to filter your PivotTable to display dimension selection results no matter what you want to report on. That are in the "Requester" topic in the data viewer.

  With respect to obtaining "Viewer and OLAP DML to be on the same page" so to speak, you will need to 'translate' between the logic of the viewer dimension value name and the name of the surrogate dimension value when you use the OLAP worksheet.

  EDIT2:
  Fix for the incorrect user account.

• How workspaces analysis OLAP export

  Hi, experts:

  I am following doc. migration 32-bit to 64-bit or through platforms OLAP (Doc ID 352306.1) to export workspaces analyses. OLAP

  I copied and pasted in step 2. as below. But I donot understand some of them. Hope you can help me.

  1. what it means by: "(NOTE: cette instruction suivante est critique donc tout dans le AW est dotée dele de statut) '?"

  2. 'replace ALIAS_DIR with one alias defined directory' this ALIAS_DIR can be anything on the current directory?

  3. I have more than 3 AW. So, I need to run the following scripts four times 3? I need to change the name of the file export_file_name.eif for each series, right?

  ========

  2. use the SQL commands following, for EACH AW that was identified in step #1 (NOTE: all quotes are single quotes).  ATTENTION: If you connect several AWs and then run the command export, ONLY the last - attached AW is exported. -Replace the OWNER. AW_NAME with the real OWNER. Name AW_NAME SQL > exec dbms_aw.execute ('aw tie OWNER.) AW_NAME rw'); --(NOTE: cette instruction suivante est critique donc tout dans le AW est dotée dele de statut) SQL > exec dbms_aw.execute ('allstat'); -Replace ALIAS_DIR by an alias of the defined directory - replace export_file_name.eif with a valid filename FEI SQL > exec dbms_aw.execute (' export all to EIF file "ALIAS_DIR/export_file_name.eif"'); -Replace the OWNER. AW_NAME with the real OWNER. Name AW_NAME SQL > exec dbms_aw.execute ('aw detach OWNER.) AW_NAME');

  =======

  Thank you very much for your help.

  1. what it means by: "(NOTE: cette instruction suivante est critique donc tout dans le AW est dotée dele de statut) '?"

  This is just a note to readers, and you can run the sql statement, as it is in the doc.

  2. 'replace ALIAS_DIR with one alias defined directory' this ALIAS_DIR can be anything on the current directory?

  Correct, but you must first create the directory - see error - EBS DB import OLAP from 32 bit to 64 for orders.

  3. I have more than 3 AW. So, I need to run the following scripts four times 3? I change export_file_name.eif file name for each series, right?

  Fix.

  Thank you

  Hussein

• How to restore a drop-down list menu workspace on the toolbar options from Photoshop CC?

  After I had tried "IU 200% scale" and then returned to the standard user interface, the workspace drop-down list has disappeared from the options bar. How can I restore it? (I can always exchange via the options menu under the tab of the window, the workspaces).

  Reset preferences:

  Hold down the CTRL - Shift - Alt from the cold Photoshop start.  If you get the keys to the low enough - quickly and you have to be VERY fast - it prompts you to confirm the removal of your established preferences, which will lead to them all being the default value.

• Decimal Cube in 11g

  I created a cube of DECIMAL type and then created count of two measures of basic and the amount. My cube is compressed cube and everything by creating what I saw after the tab "implementation Details".
  
  Choose a data type for the measure. If the cube is compressed, the measure inherits the data type of the cube.
  
  But if I do dsc on these two measures, the definition will appear as
  
  DEFINE FORMULA LOCKDFN INTEGER WITH NULLTRACKING < DIM1, DIM2 DIM3, DIM4 > TESTD_COUNT
  Convert EQ (this_aw! TESTD_STORED (this_aw! INTEGER TESTD_MEASURE_DIM 'COUNT'))
  
  It seems implicitly value is converted to INTEGER in DECIMAL number, but I must point out decimal values also then Oracle 11 g does not support the cubes with the DECIMAL data type?
  
  Thank you
  
  Published by: user3953230 on January 20, 2011 13:54

  I now understand what is happening.

  SQL is a set of data types, NUMBER, VARCHAR2, etc.. OLAP DML has a different set of DECIMAL, TEXT data types, etc. There is an overlap between the two sets and the OLAP DML all rose on the latest little, but they are always different.

  In 10g all types of data specified in AWM that were OLAP DML data types, which was very natural because it was creating an AW with OLAP DML. But in 11g AWs are so tightly integrated with SQL that all types of data in AWM are SQL data types. One of the many reasons for this is that each object in the AW, an attribute, for example, is exposed as a column in a SQL view. This column is the main way to get the data of the object and it must have a SQL data type. So it was more logical to set the object in terms of SQL data type and the conversion of types of OLAP DML data under the covers.

  But there was an exception to this rule, namely the type of storage of the cube. This matter is left as a type of OLAP DML data to give users access to real OLAP DML data types. The most important example is DECIMAL, which was recommended for cubes in 10g data type.

  Unfortunately the developers of AWM didn't understand all these subtle changes when they wrote AWM 11.2.0.1. (I don't attach you no blame here, it just happened.) Take the list of the types of data available for the cubes in 11.2.0.1 for example.

  DATE
  DATETIME
  DECIMAL
  INTEGER NUMBER
  NUMBER
  VARCHAR2
  NVARCHAR2

  Some of them are clearly the SQL data types - for example VARCHAR2. Others are clearly the OLAP DML data types - for example DATETIME. But that means DECIMAL in this list? SQL and OLAP DML have a DECIMAL data type. In SQL, it is a synonym for Number (38) while in OLAP DML is a decimal number that is platform-dependent. As it happens it was treated as a type of data OLAP DML in 11.2.0.1 (and before), but it's all very confusing.

  If you look at the XML of your cube model, you should see the following line somewhere

  CubeStorageType="DECIMAL"
  

  Compare this with the data type for the measure

  SQLDataType="DECIMAL"
  

  The CubeStorageType must be a data type OLAP DML for the SQLDataType must be a SQL data type. AWM just copied DECIMALS from one to the other without understanding the different semantics.

  If you change the SQLDataType line to be

  SQLDataType="NUMBER"
  

  recreate your cube, then your measurements must be correct. (They will be of NUMERIC type, not an INTEGER).

  So now to 11.2.0.2.

  Because of the confusion about the types of storage cube (OLAP DML or SQL) in 11.2.0.1, the server has been extended in 11.2.0.2 to allow the user to specify a type of SQL data for the cube as a whole. Here is the list in AWM 11.2.0.2.

  DATE
  DECIMAL
  INTEGER NUMBER
  NUMBER
  CHAR
  NCHAR
  VARCHAR2
  NVARCHAR2
  TIMESTAMP
  TIMESTAMP WITH TIME ZONE
  TIMESTAMP WITH LOCAL TIME ZONE
  BINARY_DOUBLE
  BINARY_FLOAT TYPES
  INTERVAL DAY TO SECOND
  MONTH YEAR APART

  It is clearly meant to be a list of SQL data types. DATETIME is gone, for example. But that means DECIMAL in this list? This now means the SQL DECIMAL data type, which is equivalent to the NUMBER (38). Are you confused yet? Now let's look at the XML for the 11.2.0.1 cube. It has two attributes.

  SQLCubeStorageType="DECIMAL"
  CubeStorageType="NUMBER(38)"
  

  The good thing is that the conversion is now explicit. You can see the data types SQL and OLAP DML. Now, when I create a measure it correctly takes the SQL data type of the cube, the NUMBER instead of an INTEGER. That's why I thought I couldn't reproduce the problem in 11.2.0.2 - I didn't know AWM has turned me on the meaning of DECIMAL. The reason why I thought then that I saw the problem is AWM always reports INTEGER as data type in the "Implementation Details" tab of the measure. This is a user interface bug - the underlying objects are correct.

  The bad news is that AWM seems to have lost the ability to specify an OLAP DML DECIMAL data type. It's frustrating because the server still support it and it was a good amount of work to implement. Gripes aside, here's how to impose a data type of dml in 11.2.0.2. Change the XML code for the cube to say

  SQLCubeStorageType=""
  CubeStorageType="DECIMAL"
  

  Recreate the cube from this, and you should be set. You will receive a warning 'data type do not match', but you can reject it.

  There is no need to move you to 11.2.0.2 (unless you have other reasons to do so). You can just change to hand the XML I described. Note that XML tempate created with the data type to DECIMAL 11.2.0.1 will create 11.2.0.2 DECIMAL data type as well, so there should be no problem to upgrade.

• [MN] Analytic workspace object does not exist

  I follow the tutorial here: http://st-curriculum.oracle.com/obe/db/11g/r1/olap/cube/buildicubes.htm
  
  For our work environment, all data from the source is located in the OLAPTRAIN schema, but all dimensions and cubes are built in the User1 schema. To do this, I just changed all mappings to the good OLAPTRAIN schema. However, when I get to the step of loading and display of Cube data and click on maintain Cube SALES_CUBE I get the following error:
  
  INI: error creating a generic Manager definition to TxsOqConnection::generic < BuildProcess > INI: XOQ-00703: error running command OLAP DML «(STATLEN (USER1.» SALESTRACK_USER1! (TIME): ORA-34492: workspace object Analytics User1. SALESTRACK_USER1! There is no such thing as TIME.
  ') ', Generic TxsOqAWManager::evaluateExpression
  
  I guess that it refers to the TEMPORAL dimension of the User1, that exists. The TIME dimension was created using a template, but there seems to be something wrong with it so I recreated the dimension from scratch, you re-create the mappings between the original model of TIME. Old TIME dimension has been deleted, and now only the manually generated TIME dimension exists.
  
  Any ideas?

  Run the following command to list the dimension objects in the AW.

  set serverout on
  begin
  dbms_aw.execute(q'!
   aw attach USER1.SALESTRACK_USER1
   listnames dimension
  !');
  end;
  /
  

  The error suggests that the TIME is not a dimension in the AW. It is possible that you will find something like "(HAE) 1" instead because of the mishap of creation. To locate the name of the physical dimension associated with a logical (AWM) dimension, you can do this. (11.2.0.2 or later.)

  set serverout on
  begin
  dbms_aw.execute(q'!
    show objorg(dim owner 'USER1' 'TIME')
  !');
  end;
  /
  

• ORA-34492: analytic workspace object &lt; cubename &gt; _STORED does not exist.

  I have problems to access the data in the cube of one user other than the one where the AW will be built.
  
  Here's what I did to the user 1:
  
  1. create two AW in user-1: AW-1 and AW-2.
  
  2. create all objects in these two AW
  
  3 AW-2 is dynamically linked on the setting of the AW-1 by PERMIT startup programs. Please refer to attach several AW
  
  4 refreshed the two AW for loading data
  
  5 ALLCOMPILE - no errors.
  
  6. created some views SQL on User-1 which basically ask the views of the underlying cube. I have also a few queries using the olap_table option.
  
  7. all my querries work very well at user-1. I can access the data of 1 AW and AW-2.
  
  
  However, we provide access to views abstract SQL above by user: user-abs. In 10g, everything we did was grant select privs to all tables of $ User - 1.AW and also on all views sql. That would leave user-abs recover data from user-1 ice all.
  
  I'm not able to get the ABS users to do the same in 11g. We encounter an error stating that there is no such thing as the workspace object < cubename > _STORED. The cubename to what it refers exists AW - 2.
  
  I select given privs on all tables of $ AW, views of dimension, views of cube and the views sql abstract but the error persists.
  
  I tried to search this forum but did not find all the useful leads. Any help will be greatly appreciated.
  
  Thank you!
  
  Database - 11.2.0.1
  MN - 11.2.0.2.0A

  I think I understand the problem, and I have at least one solution for you.

  Your PERMIT_READ to USER-1 program. AW - 1 tie USER-1. AW-2, and as the attachment of part of this process, we must implement object for all objects USER-1 security. AW-2. For example, if you SELECT for X-USER-1 cube access. AW-2 but no access update, then we'll run the following

  REVIEW X_STORED
  PERMIT TO WRITE WHEN FALSE

  We run so essentially involving them objects OLAP DML USER-1. AW-2 as part of the PERMIT_READ on USER-1. AW-1. It strikes the restriction documented at PERMIT_READ I mentioned in my previous post.

  You don't hit the problem when running as a USER-1 because USER-1 automatically gets all permissions on the objects he owns, so we try not to run/PERMIT to take into ACCOUNT.

  You don't hit the problem of setting USER-1. AW-2 directly because the object security is applied outside the context of the PERMIT_READ on USER-1. AW-1

  You don't hit the problem if you have connected the USER 1. AW-2 and then withdrawn because (I think) USER-1. AW - 2 remains in a State of 'attached soft' after the initial attachment and we does not apply the security of objects that we have "attached soft" back to "hard Attaché".

  The solution is to grant all types of object security on objects of the AW-2 USER-2. This includes not only the SELECT, but also the UPDATE, INSERT, etc. Just give everything in the AWM dialog for all dimensions and all the cubes. Once you do this, the second user should be able to connect wihtout error because there is no need for us to CONSIDER/PERMIT.

  I don't know yet if this should be considered as a formal bug or if this is the expected behavior by the people who coded it.

• Expressions of QDR in OLAP cube measures calculated

  Hello everyone,

  I'm going crazy with a calculated measure in OLAP Analytic Workspace Manager, which is defined as an Expression of the following OLAP syntax:

  NVL (CUBE. MEASURE1 [DIM1 = 'A'], 0) + NVL (CUBE. Date2 [DIM2 = 'B'], 0)

  Where:

  CUBE. MEASURE1 and CUBE. Date2 are not calculated measures, they are stored measures.

  Dim1 and DIM2 are the edges of the CUBE, A and B values both exist in their dimensions.

  In most of my questions, the calculated measure retrieves the correct results, when two members of the sum gets the data. But I have other cases, the calculated measure retrieves null!

  In these cases, the calculated measure retrieves null when the CUBE. Date2 [DIM2 = 'B'] retrieves NO results. But I think that if none of the two expressions QDR retrieves no results, NVL function will be replaced by 0.

  I read about this, situations where the QDR expressions get no result, by default, it throws and error and non-null o NA value. I found that there are 2 options of ORACLE DML that can manage this type of situation:

  LIMITSTRICT = NO (http://docs.oracle.com/cd/B28359_01/olap.111/b28126/dml_options043.htm#OLADM384)

  OKNULLSTATUS = YES (http://docs.oracle.com/cd/B28359_01/olap.111/b28126/dml_options077.htm#OLADM418)

  I tried to create a DML function in the AW to define two options, first to NO, then Yes and returns 0, call this function with the instruction OLAP_DML_EXPRESSION ('MyFunc', NUMBER), but it does not work

  Exchange monitoring calculated like this: OLAP_DML_EXPRESSION ('MyFunc', NUMBER) + NVL (CUBE. MEASURE1 [DIM1 = 'A'], 0) + NVL (CUBE. Date2 [DIM2 = 'B'], 0)

  Please, I need a solution to bypass this, how can I catch these situations? Should I create a program of LMD to solve? Where I put this default option (LIMITSTRICT, OKNULLSTATUS) and put them in each measurement calculation?

  Thanks in advance for the answer.

  Great, you can not use a formula directly? No missing documents, such as observed earlier?

  For example the formula =

  IF (CUBE_MEASURE1 (DIM1 'A')) NAFLAG EQ 0 THEN CUBE_MEASURE1 (DIM1 'A') ELSE 0 + IF (CUBE_MEASURE2 (DIM2 'B')) NAFLAG EQ 0 THEN CUBE_MEASURE2 (DIM2 'B') ELSE 0

  If this expression does not work in a single formula, set rather measures 3 Meas1/2/3...

  (I generally prefer many formulas compared with olap dml program option in the mix...-online program looping on several other dimensions values is sometimes tricky to control/understand.)

  Meas1 = IF (CUBE_MEASURE1 (DIM1 'A')) NAFLAG EQ 0 THEN CUBE_MEASURE1 (DIM1 'A') ELSE 0

  and

  Meas2 = IF (CUBE_MEASURE2 (DIM2 'B')) NAFLAG EQ 0 THEN CUBE_MEASURE2 (DIM2 'B') ELSE 0

  Then set

  Meas3 = Meas1 + Meas2

• Workspace cannot be attached

  Hi all
  
  I have run below:
  
  exec DBMS_CUBE. BUILD('NN_OLAP_POC.) MARKET_SALES_CUBE, NN_OLAP_POC. BRAND_SALES_CUBE', parallelism = > 2);
  
  and it fails with:
  
  *
  ERROR on line 1:
  ORA-37162: Error OLAP
  XOQ-01707: Oracle work "JOB$ _196 ' failed during execution of the slave build
  "NN_OLAP_POC. WITH THE HELP OF MARKET_SALES_CUBE (LOAD NO SYNCHRONIZATION, RESOLVE) FROM SNA 31840126 "
  with the error ' 37162: ORA-37162: OLAP error. "
  XOQ-01600: OLAP DML error "ORA-4030: lack of memory of process trying."
  allocation of 14083672 bytes (xsCCube, xsCCube_1)' while executing DML
  'SYS. AWXML! R11_AGGREGATE_CONSISTENT('MARKET_SALES_CUBE.) CUBE'
  ' MARKET_SALES_CUBE. FIX. AGGREGATIONDEFINITION'
  SYS. AWXML! ___R11_LONG_ARG_VALUE (SYS. AWXML! "(___R11_LONG_ARG_DIM 1)"P59").
  ORA-06512: at "SYS." DBMS_CUBE', line 236
  ORA-06512: at "SYS." DBMS_CUBE', line 305
  ORA-06512: at line 1
  ".
  ORA-06512: at "SYS." DBMS_CUBE', line 236
  ORA-06512: at "SYS." DBMS_CUBE', line 280
  ORA-06512: at line 1
  
  Now I am not able to reach the AW in REad Write mode and I think that has been locked by the MN itself and I need to bounce the database to remove the lock.
  
  Can you please indicate the reason for the failure and even if faulty AW should release the lock that is not the case now.
  
  Thanks in advance,
  DxP

  The session who had joined the AW in RW mode is probably still alive, which means the AW cannot be attached RW by any other session. This may have sorted itself out by the time wherever you read this, but if not, then run the following as s/n.

  set pages 500 lines 110
  col usn format a23 heading "USER (SID,SERIAL#,SVR)"
  col aw format a22 heading "OLAP AW (ATTACHED)"
  col generation format 99999 heading "Genrtn"
  
  select
    username || ' ('||sid||','||serial#||','||
    decode(server,
      'DEDICATED','D',
      'SHARED', 'S', 'U')||')' usn,
      gvawo.inst_id,
      owner||'.'||daws.aw_name||' ('||
       decode(attach_mode,
       'READ WRITE', 'RW',
       'READ ONLY', 'RO',
       'MULTIWRITE', 'MW',
       'EXCLUSIVE', 'XW', attach_mode)||')' aw,
    generation
  from
    dba_aws daws,
    gv$aw_olap gvawo,
    gv$aw_calc gvawc,
    gv$session gvses
  where
    daws.aw_number = gvawo.aw_number
    and sid = gvawo.session_id
    and gvawc.session_id = sid
    and gvawo.inst_id = gvawc.inst_id
    and gvses.inst_id = gvawc.inst_id
  order by
    username,
    sid,
    daws.aw_name
  /
  

  Lists all attached AWs and the sessions who owns them. Similar information can be obtained AWM by using the node 'Reports-> reports OLAP DBA-> AWs' attached.

  Here is an example of output.

  USER (SID,SERIAL#,SVR)        INST_ID OLAP AW (ATTACHED)       Genrtn
  ----------------------- ---------- ---------------------- ------
  GLOBAL (16,357,D)           1 SYS.AWXML (RO)            2
  GLOBAL (16,357,D)           1 SYS.EXPRESS (RO)            2
  GLOBAL (101,4017,D)           1 SYS.EXPRESS (RO)            2
  SCOTT (18,599,D)           1 SYS.EXPRESS (RO)            2
  SCOTT (18,599,D)           1 GLOBAL.GLOBAL (RW)            0
  

  As you can see, the user SCOTT has the 'GLOBAL' named AW attached in RW mode. I can kill the session using

  alter system kill session '18,599';
  

• Error while UPGRADING OLAP AW

  Hello
  
  I use AWM 11.1.0.7.0B and the 11.1.0.7.0 BDD
  
  After one or two everyday, I get this error... Whenever I maintain the dimension, I get the following error...
  
  An error occurred on the server
  Class of error: failure of the Express
  Server error descriptions:
  INI: Error creating a generic Manager definition to < BuildProcess > TxsOqConnection::generic
  INI: XOQ-00703: error running command OLAP DML "(UPDATED MDCT. MDCT: ORA-37605: error while UPGRADING OLAP AW
  [ORA-00600: internal error code, arguments: [xspggepGenPSErase01], [], [], [], [], [], [], [], [], [], []]
  ') ', Generic TxsOqAWManager::executeCommand
  
  at oracle.olapi.data.source.DataProvider.callGeneric (unknown Source)
  at oracle.olapi.data.source.DataProvider.callGeneric (unknown Source)
  at oracle.olapi.data.source.DataProvider.executeBuild (unknown Source)
  to oracle.olap.awm.wizard.awbuild.UBuildWizardHelper$ 1.construct (unknown Source)
  to oracle.olap.awm.ui.SwingWorker$ 2.run (unknown Source)
  at java.lang.Thread.run (unknown Source)
  
  To view the data the error
  
  BIB-9509 Oracle OLAP does not create the cursor.
  An error occurred on the server
  Class of error: failure of the Express
  Server error descriptions:
  DPR: Failed to create the server-side, generic cursor at TxsOqDefinitionManager::crtCurMgrs4
  INI: XOQ-00703: error running command OLAP DML "(AW ATTACH MDCT. MDCT RO: ORA-34738 PF: a serious problem was detected. Operations of the analytic workspace have been disabled.
  ') ', Generic TxsOqAWManager::executeCommand
  
  
  And when I am trying to detach or remove the AW gives the following error...
  
  java.sql.SQLException: ORA-34738 PF: a serious problem was detected. Operations of the analytic workspace have been disabled.
  ORA-06512: at "SYS." DBMS_AW', line 93
  ORA-06512: at "SYS." DBMS_AW", line 180
  ORA-06512: at line 1
  at oracle.olap.awm.connection.AwAttachmentManager.detach (unknown Source)
  to oracle.olap.awm.connection.AwAttachmentManager$ 1DetachWorkspaceThread.run (unknown Source)
  
  
  Help, please...
  
  Thank you
  BIBA
  
  Published by: [email protected] on July 21, 2009 05:48

  I think Jim refers to a delete an import/export / in your analytic workspace via the OLAP worksheet. This is the approach I used during the restoration of broken AW.

  OLAP worksheet:

  AW attach MDCT
  allstat
  Name of the limit to all
  Export all FEI OCDM.eif of the file
  AW detach MDCT
  AW truncate MDCT
  AW attach MDCT rw
  import all Fei file "OCDM.eif" data NPO naskip
  UPD; CMM

• Five questions about OLAP makes me confused.

  1. Why do we need to map the level twice in the dimension and cube? I don't know when we cube mapping, only map the lower of
  a hierarchy. And what happens if a member of level even has been mapped with different columns of the source table?
  
  2. it defines several hierarchies of a dimension, then why do we need set one of them as the default hierarchy? In
  which scenario we need to define multiple hierarchies?
  
  3. When you create a Cube, there is an option in the aggregation-> precompute-> Cost_base aggregation - > percentage, that means
  'Percentage' used for? For a performance?
  
  4. when I do surgery in AWM, sometimes with a few errors. But it's really hard to understand what it is
  This means. As the error message below.
  /*********
  The transaction is not pensionable: "an error has occurred on the server.
  Class of error: failure of the Express
  Server error descriptions:
  DPR: Failed to create the server-side, generic cursor at TxsOqDefinitionManager::generic < CommitRoot >
  INI: XOQ-01600: OLAP DML error 'object OLAPTRAIN of the analytic workspace. SALESTRACK!
  There is no such thing as SALES_CUBE_PRODUCT_ALERT. "while executing DML 'SYS. AWXML! R11_MANAGE_CUBE
  ('SALES_CUBE.) CUBE' "DELETE") ', generic for TxsOqStdFormCommand::execute '.
  "
  at oracle.olapi.transaction.BaseTransaction.commit (unknown Source)
  at oracle.olapi.transaction.BaseTransactionProvider.commitCurrentTransaction (unknown Source)
  at oracle.olap.awm.dataobject.DatabaseDO.commitOLAPI (unknown Source)
  at oracle.olap.awm.dataobject.aw.WorkspaceDO.commitOLAPI (unknown Source)
  at oracle.olap.awm.dataobject.olapi.UModelDO.commitOLAPI (unknown Source)
  at oracle.olap.awm.dataobject.olapi.UModelDO.delete (unknown Source)
  at oracle.olap.awm.dataobject.olapi.UCubeDO.delete (unknown Source)
  at oracle.olap.awm.navigator.node.DeleteThread.run (unknown Source)
  ************/
  When he said "object OLAPTRAIN of the analytic workspace. SALESTRACK! There is no such thing as SALES_CUBE_PRODUCT_ALERT. "I do not yet know
  What is SALES_CUBE_PRODUCT_ALERT and where I can find the most detailed information for me solve the problem. I want to say is here
  a manual or a reference Oracle provided to help developers?
  
  5. is it important the order of Join Condition when we the mapping of a cube to resouce, such as a = b or b = a? What type of join is, LEFT JOIN, RIGHT JOIN, OUTER JOIN, or INNER JOIN?
  
  Thank you
  
  Satine

  You arrive on the % figure after seeing the results of time reporting and cube loading time. This can be an iterative work, but should be fruitfull later.

  Thank you
  Brijesh

  Published by: BGaur on May 11, 2009 17:02

• Calculated measure (OLAP language) of the calculated measure (Expression OLAP)

  Hi, once again!

  I need to create a calculated measure in the form of free type AWM (OLAP Expression, with the condition BOX) based on the results of another measure calculated again with the status of the CASE.

  For example, I have a few basic measure number of type 'BM1', 'BM2', "BM3" . And I create a calculated measure "BM_AMOUNT" that returns a number if 'BM1' is not null or 0 with the expression:

  CASE

  WHEN BM1 = 0 or BM1 is NULL THEN NULL

  ANOTHER (BM2 - BM3) / BM1

  END

  And then I create a different "BM_PT" calculated measure that returns points based on the value of the first expression:

  CASE

  WHEN BM_AMOUNT > 0 THEN 0

  ANOTHER 20

  END

  Now, when I want to create the second expression I get error: XOQ-01958derived measure is a type of invalid data or data of any kind.

  I found a way to work around this - I create first the measure with the NUMBER type and then change it to the expression of OLAP, and it works.

  However, the problem is when I export the cube and that you want to import on another instance. Then, I get the same error for this measure "BM_PT" and impossible to import the cube.

  The only way I've found is to edit the XML code and remove the measure, then create it manually as mentioned above (type NUMBER then change it), but it would be really nice if there is another way to knit this tour. This is so my question, is it?

  * The example is just to help understand what I want to achieve and what is not correct.

  Re: #2

  If you use OLAP DML, if CUBE_DDS is the name of the cube and DOOD is the name of the measure then the expression to use in the formula of the OLAP DML is _.

  Try with CUBE_DDS_DOOD, CUBE_DDS_F0150, CUBE_DDS_DO0, CUBE_DDS_SF0213, CUBE_DDS_F0180 etc., in the formula.

  In AWM, you can open the OLAP worksheet and check if the following expressions are valid by publishing a

  > CUBE_DDS_DOOD DSC

  order

  Formula:

  > If nafill(CUBE_DDS_DOOD,0) eq 0 then na to another ((CUBE_DDS_F0150 + (CUBE_DDS_DO0 + CUBE_DDS_SF0213) * 0.2) - CUBE_DDS_SF0213 - CUBE_DDS_F0180) / end CUBE_DDS_DOOD