OLAP statistics: EVENTID descriptions
Hi, all
Is there detailed description of events codes, shown in rsrt query statistics?
I found only table RSDDSTATEVENTS, which contains texts. This does not explain activity for this events.
Maybe there is howto, describing it.
Most needed event descriptions are 9000,19900, 3110 and 3200
Hi,
please search the forums first before posting questions. This avoids redundant effort and saves time and resources of your peers.
Please check underneath thread and potentially many more. Use the search term 'Statistics'.
Cheers
SAP NetWeaver BI Organisation
<a href="https://forums.sdn.sap.com/click.jspa?searchID=202721&messageID=2511213">https://forums.sdn.sap.com/click.jspa?searchID=202721&messageID=2511213</a>
Similar Messages
-
OLAP Statistics table RSDDSTAT is locked
I am working on BW 3.1C and my issue is:
The OLAP Statistics table RSDDSTAT is locked due to some data base rollback activities. When users execute the query, it is first hitting the statistics table and since it is already locked, I am getting -913 sql short dumps. In order to avoid this, I have used the following option:
RSA1 --> Tools --> BW Statistics for Infoprovider.
I have unchecked all data targets. When I ran the query in RSRT/RSRT2, the query gets successfully executed without hitting the statistics table.
But when I tried to execute the query from Web, it is hitting the statistics table which again causing me short dumps. Is there any Tcode where I can turn-off the statistics settings. Please mention that I am in 3.1C version and do not have T.code RSDDSTAT.
Please let me know how to resolve this issue?Hi,
In BI 7 there's a table RSDDSTATOBJLEVEL which we can decide record statistics or not.. Can you try to whether it exist in your machine? I don't have BW 3.x system at hand.
Regards,
Frank -
MS SQL Server Analysis Services (SSAS) OLAP Connection - Dimension descriptions
Hello,
We are trying to create some reports on BO 4.0 on top of BPC 10 MS information.
In order to overcome some issues related to standard connector between BO and BPC (XMLA Planning and consolidation 10 for Microsoft platform), we created a new connection based on discussion MS SQL Server Analysis Services (SSAS) OLAP Connection - Business Intelligence (BusinessObjects) - SCN Wiki
However we have a major issue with this approach. We cannot see on BO dimension member descriptions.
Is there anything that we missed?
Could you help?
Regards,
Vitor RamalhoBill,
So, what you need is a model like SQL Server failover cluster instances. (before sql server 2012)
In SQL Server 2012, AlwaysOn replaces SQL Server failover cluster, and it has been seperated to
AlwaysOn Failover Cluster Instances (SQL Server) and
AlwaysOn Availability Groups (SQL Server).
Since your requirement is not in database level, I think the best option is to use AlwaysOn Failover Cluster Instances (SQL Server).
As part of the SQL Server AlwaysOn offering, AlwaysOn Failover Cluster Instances leverages Windows Server Failover Clustering (WSFC) functionality to provide local high availability through redundancy at the server-instance level—a
failover cluster instance (FCI). An FCI is a single instance of SQL Server that is installed across Windows Server Failover Clustering (WSFC) nodes and, possibly, across multiple subnets. On the network, an FCI appears to be an instance of SQL
Server running on a single computer, but the FCI provides failover from one WSFC node to another if the current node becomes unavailable.
It is similar to SQL Server failover cluster in SQL 2008 R2 and before.
Please refer to these references:
Failover Clustering in Analysis Services
Installing a SQL Server 2008 R2 Failover Cluster
Iric Wen
TechNet Community Support -
Error in Running a dimension ( BIB-9509 Oracle OLAP did not create cursor.)
oracle.dss.dataSource.common.QueryRuntimeException: BIB-9509 Oracle OLAP did not create cursor.
oracle.express.ExpressServerExceptionError class: OLAPI
Server error descriptions:
DPR: Unable to create server cursor, Generic at TxsOqDefinitionManagerSince9202::crtCurMgrs4
OES: ORA-00938: not enough arguments for function
, Generic at TxsRdbRandomAccessQuery::TxsRdbRandomAccessQuery
help is appreciated
Thanks, PrasadThis is the patch: 2529822
"Best Practices for Tabular Cube Aggregation & Query Operations". Thanks very much for your advice.
I followed the instructions in the document, but it did not seem to make a difference when
trying to follow the tutorial instructions and using the SALES measure.
However, I selected the stock price measures and it worked ok.
Is there a size limit here? I am looking at Oracle OLAP and BIBeans to replace our Cognos installation,
which is expensive and unreliable on unix. Of course our managers and customers want every dimension
across a huge fact table to be available for end users... -
Does the user have to be the owner of CWM2 objects to access them via OLAP API?
Hi,
What are required for RDBMS users to use OLAP API? Regarding page 6-9 of Oracle9i OLAP User's Guide 9.2.0.1, following access rights are required.
CONNECT role
QUERY REWRITE system privilege
SELECT privilegs on the database objects containing the data to be analyzed
So, I created a new user TEST1 and granted all the priviges above. Then I tried to create a new crosstab using New Crosstab Wizard in JDev903_pre(OLAPConnecton is using TEST1). When I choose a measure that is created in CWM1, I could create a crosstab without problem. But when I tried to create a crosstab from a measure that is created in CWM2 by OLAPSYS user, I recieved the following error.
BIB-9509 Oracle OLAP did not create cusor.
oracle.express.ExpressServerExceptionError class:OLAPI
Server error descriptions:
DPR: Unable to create server cursor, Generic at TxsOqDefinitionManager::createCursorManager
OES: ORA, Generic at TxsRdbSelectStatement:execute()
The curious thing is that I can create a crosstab from the same measure if I use another connection that uses OLAPSYS. Does the user that connects to CWM2 using OLAP API have to be the owner of those CWM2 objects?
Thank you.
Best Regards,
SeijiThe user does not have to be the owner of the cwm2 objects to access them. Access to cwm2 objects is based on database security. Therefore, if the user is not the owner of the object (if user is the owner, they obviously have access to the object), then as long as the user has been granted access to the underlying physical object (i.e., the table the dimension or cube has been mapped to), the user will be able to access the object.
-
Hi Friends,
I want to gather system statistics in my Oracle 9.2.07 (windows) environment...
created one statistics table...
execute DBMS_STATS.CREATE_STAT_TABLE ('SYS','MY_STATS');
(2) Gathering SYSTEM Statistics Script during office hours ( 8 hours) (8am to 4pm)
begin
execute dbms_stats.gather_system_stats(
gathering_mode=> 'interval',
interval => 480,
stattab=> 'MY_STATS',
STATID=> 'OLTP');
END;
REM
REM
REM END of Script
REM===================================================
(3) Import the Collected System Statistics
Import the statistics daily around 8AM...because..users starts entering the transactions....
variable jobno number;
begin
dbms_job.submit(:jobno,'dbms_stats.import_system_stats(''IMAL_STATS'',''OLTP'');',
SYSDATE,'SYSDATE+1');
COMMIT;
END;
========================================================
OLAP..also i will collect during night time....
gathering system statiscs will end after 4pm....so..it takes system statistics during 8 hours interval time...and i am going to import them next day 8am..
is this the correct method????.please sched some light on this...Hi,
Oracle recommends to gather system statistics from oracle 9i onwards....this the line from Oracle 9i R2 document...
Oracle9i Database Performance Tuning Guide and Reference
Release 2 (9.2)
Gathering System Statistics
System statistics enable the optimizer to consider a system's I/O and CPU performance and utilization. For each plan candidate, the optimizer computes estimates for I/O and CPU costs. It is important to know the system characteristics to pick the most efficient plan with optimal proportion between I/O and CPU cost.
System I/O characteristics depend on many factors and do not stay constant all the time. Using system statistics management routines, database administrators can capture statistics in the interval of time when the system has the most common workload. For example, database applications can process OLTP transactions during the day and run OLAP reports at night. Administrators can gather statistics for both states and activate appropriate OLTP or OLAP statistics when needed. This enables the optimizer to generate relevant costs with respect to available system resource plans.
When Oracle generates system statistics, it analyzes system activity in a specified period of time. Unlike table, index, or column statistics, Oracle does not invalidate already parsed SQL statements when system statistics get updated. All new SQL statements are parsed using new statistics. Oracle Corporation highly recommends that you gather system statistics.The DBMS_STATS.GATHER_SYSTEM_STATS routine collects system statistics in a user-defined timeframe. You can also set system statistics values explicitly using DBMS_STATS.SET_SYSTEM_STATS. Use DBMS_STATS.GET_SYSTEM_STATS to verify system statistics.
So better performanace, as per above document, we need system statistics.
if not needed.why it is not need...can u please describe this...
Message was edited by:
bsubbu -
Hi all,
We have BW 7.0 EhP1 Service pack level 4 and I am planning to set up the BW statistics process chains. When I try to run the process chains, most of the info packages are running but getting issues with the below:
Query Runtime Statistics - Init
Info source - Front-End and OLAP Statistics (Highly Ag(0TCT_ISA1) -
Data Load Statistics - Delta
BW Statistics: Transaction Data Process Chain Statistics(0TCT_DS21)
BW Statistics: Transaction Data DTP Statistics(0TCT_DS22)
BW Statistics: Transaction Data InfoPackages(0TCT_DS23)
I am getting the below system log when I kick off the info package:
"MESSAGE BRAIN 299: SAPLRRSI INITIALIZE-1-
Run-time error "UNCAUGHT_EXCEPTION" occurred"
Please let me know if anybody has come across similar issues, if so please let me know how did you fix it?
Thanks,
Ramana
Edited by: Ramana Korada on Nov 9, 2009 12:37 PMHi
To recognize this error early on, the attached corrections check whether the references are correct. If they are not, the following termination occurs:
"System error in program SAPLRRSI and form INITIALIZE-1- (see long text)".
The content version of the characteristic 0REQUEST is usually correct. You can see this in transaction RSD5 (dropdown content). If this is the case, you can transfer the InfoObject from the content again:
Transaction RSOR -> BI Content -> Object Types -> under InfoObjects select 0REQUEST and transfer it to the right (note the following settings: "Only Necessary Objects"; collection mode: "Collect Automatically").
If the termination still occurs in your system, contact SAP.
Apply this note
Note 1157796 - Characteristic 0REQUEST must reference 0REQUID
hope your issue will be solved
santosh -
Missing content of BI statistics table?
Hi,
Recently ( Two months back ) we have upgarded our BW system To BI 7.0 and also activated its Technical content!
But the Table RSDDSTAT_OLAP has so many objects lists missing in its contents like infoprovider, Processchain, etc--
How to activate these missing contents so that i cud see these entries in the table RSDDSTAT_OLAP??
RajHi Raj,
RSDDSTAT_OLAP db view is only relevant for front-end & olap statistics. Here is a list of all the source tables:
OLAP Statistics
- Front-end & OLAP Statistics: RSDDSTAT_OLAP (DB view)
- Data Manager Statistics: RSDDSTAT_DM (DB view)
WHM Statistics
- Process Chain Statistics: RSPCLOGCHAIN, RSPCPROCESSLOG
- DTP Statistics: RSDDSTATDTP, RSBKREQUEST
- InfoPackage Statistics: RSDDSTATWHM
WHM Status
- BI Object Status: RSMDATASTATE_EXT
- Process Status: RSPCPROCESSLOG, RSPCLOGCHAIN
For more information you can refer also to this document (BI administration cockpit and BI statistics in SAP NetWeaver 7.0):
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/50f95b21-7fb8-2910-0c81-f6935d4c654b
Regards,
Theodoros -
Any setup reqd for Disco for OLAP to attach multiple AWs per schema...
I have a schema with two AWs - A, B (created the new AW - B recently). <br><br>
When i log on to Discoverer Plus for OLAP via an App Server (givign the schema user/pass), i do not get to pick the AW B explicitly. <br><br>
All Measure folders/cubes from both AWs A and B are displayed and i can choose the cube from AW B. However after all the worksheet creation steps are done, the worksheet query fails with the error --<br><br>
========================================<br>
oracle.dss.dataSource.common.OLAPException: null<br>
java.lang.NullPointerException<br>
java.lang.NullPointerException<br>
oracle.dss.dataSource.common.QueryRuntimeException: BIB-9009 Oracle OLAP could not create cursor.<br>
<br>
========================================<br><br>
D4O Diagnostic test gives the following:<br>
<br>
oracle.dss.d4o.common.D4OException: BIB-9009 Oracle OLAP could not create cursor.<br>
oracle.express.ExpressServerExceptionError class: OLAPI
Server error descriptions:<br>
DPR: Unable to execute the query, Generic at TxsOqCursorManager::fetchInitialBlocks<br>
OES: ORA-34224: Analytic workspace <<schema>>.<<AW_B>> is not attached.<br>
, Generic at TxsRdbResultSet:absolute()<br>
<br>
========================================<br><br>
The dimension selections etc (intermediate steps of the wizard) are working on the right data/hierarchies.. So the second AW did get attached.<br><br>
If i create a worksheet based on cubes present in AW #1: A, then it works fine.<br><br>
Is there any special settings/program... ONATTACH, AUTOGO kind... which is required while using multiple AWs within a schema?<br><br>
The schema has olap_user and olap_dba roles as well as access to the Discoverer Catalog via iAS Discoverer Admin.<br><br>
Thanks in advance for any help.<br>
Shankar<br>
Message was edited by: <br>
user498007<br>
Trying to make it readable... Didn't retain line breaks. Now it does.<br><br>Discoverer for OLAP should see all measures and dimensions that you have access to. You never need to explicitly attach an AW.
You are correct in thinking that the AW did get attached if you get to a point in the Workbook Wizard where data is displayed. The error messages are not meaningful to mean. I would guess that it is the result of some sort of metadata error. You might see if AW 'A' is causing any sort of confict by revoking SELECT on AW$A (you'll need to do this as a different user than the owner of the AW) an then attempting to view AW 'B'. -
Hi All,
We are in the process of BI technical upgrade. I read somewhere the BI Statistics concept has changed in BI 7.0. The statistics are part of our scope.
It would be great if anyone shares "How to Statistics in BI 7.0?" or let me know the changes and the necessary actions to be taken to make sure Statistics work in BI 7.0
Regards,
SumanSuman,
Some of the key points from the presentation below while configuring the BI Stats in v 7.0.
a) The new technical content for BI statistics renders the previous u201CBW
statisticsu201D content obsolete with SAP NetWeaver 7.0 BI.
b) The BI Administration Cockpit is based on new InfoProviders that are
delivered with the new technical content for BI statistics.
u2013 It is not possible to migrate old statistics into new InfoCubes, and there is no
provision for migrating old statistics into the new InfoCubes.
c) The new BI statistics content provides:
u2013 InfoCubes for historical data
u2013 Virtual Providers for current data
u2013 MultiProviders for combined view of current and historical
d) OLAP statistics table RSDDSTAT no longer is updated, and it has been
split / extended to several different RSDDSTAT* tables.
e) As of SAP NetWeaver 7.0 BI, transaction ST03 is based on the Technical
Content InfoProviders (unlike prior releases). Therefore, using transaction
ST03 for BI Monitoring requires the Technical Content to be activated and
to be populated periodically with statistics data.
See full details in this useful presentation:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/50f95b21-7fb8-2910-0c81-f6935d4c654b?quicklink=events&overridelayout=true
Regards,
Ramesh. -
Hi all,
RSA1 t-code top displaying Data warehouse workbench and System component version is SAP NetWeaver 2004s, but all
objects developed in 3.5 data flow. My doubt now i going to install BI Statistics whether i have to install below IC also. Please give
suggestion on this.
BW Statistics 3.5 (No Longer Install) 0BWTCT_STA_35
BW Statistics - OLAP 0BWTC_C02
BW Statistics - WHM 0BWTC_C05
Regards,
R. SaravananHI Srinivas ,
Please give conformation below list cubes and MP i am going to install. I hope u know what i looking for. Please give
conformation.
BI Statistics 0BWTCT_STA
BW Statistics - OLAP, Detail Navigation 0BWTC_C03
BW Statistics - Aggregates 0BWTC_C04
BW Statistics: Condensing InfoCubes 0BWTC_C09
BW Statistics: Deleting Data from InfoCubes 0BWTC_C11
Front-End and OLAP Statistics (Aggregated) 0TCT_C01
Front-End and OLAP Statistics (Details) 0TCT_C02
Data Manager Statistics (Details) 0TCT_C03
Process Statistics 0TCT_C21
DTP Statistics 0TCT_C22
InfoPackage Statistics 0TCT_C23
Front-End and OLAP Statistics (Highly Aggregated) 0TCT_CA1
Front-End and OLAP Statistics (Aggregated) 0TCT_VC01
Front-End and OLAP Statistics (Details) 0TCT_VC02
Data Manager Statistics (Details) 0TCT_VC03
BI Object Request Status 0TCT_VC11
Process Status 0TCT_VC12
Process Statistics 0TCT_VC21
DTP Statistics 0TCT_VC22
InfoPackage Statistics 0TCT_VC23
Front-End and OLAP Statistics (Highly Aggregated) 0TCT_VCA1
BW Statistics 0BWTC_C10
Front-End and OLAP Statistics (Aggregated) 0TCT_MC01
Front-End and OLAP Statistics (Details) 0TCT_MC02
Data Manager Statistics (Details) 0TCT_MC03
BI Object Request Status 0TCT_MC11
Process Status 0TCT_MC12
Process Statistics 0TCT_MC21
DTP Statistics 0TCT_MC22
InfoPackage Statistics 0TCT_MC23
Front-End and OLAP Statistics (Highly Aggregated) 0TCT_MCA1
BI Metadata 0BWTCT_META
BW Metadata 0BWTC_C08 -
Dear All,
I am having some doughts on BW Statistics Setting,
In selection for BW Statistics settings ( AWB->Tools-> BW Statistics for infoprovider) all objects including Master data object/ODS/Cube is selected.
My doughts is that is BW Statistics work for Master data objects/ODS ?
or it only work for Cube.
Do we need to deselect all check box in seting for Master Data object/ODS and only need to be checked for Cube.
Thanks All in advance.Hi,
With the new architecture for BI reporting, collection of statistics for query runtime analysis was enhanced or changed. The parallelization in the data manager area (during data read) that is being used more frequently has led to splitting the previous "OLAP" statistics data into "data manager" data (such as database access times, RFC times) and front-end and OLAP times. The statistics data is collected in separate tables, but it can be combined using the InfoProvider for the technical content.
The information as to whether statistic data is collected for an object no longer depends on the InfoProvider. Instead it depends on those objects for which the data is collected, which means on a query, a workbook or a Web template. The associated settings are maintained in the RSDDSTAT transaction.
Effects on Existing Data, Due to the changes in the OLAP and front-end architecture, the statistic data collected up to now can only partially be compared with the new data.
Since the structure of the new tables differs greatly from that of the table RSDDSTAT, InfoProviders that are based on previous data (table RSDDSTAT) can no longer be supplied with data.
Effects on Customizing
The Collect Statistics setting is obsolete. Instead you have to determine whether and at which granularity you wish to display the statistics data for the individual objects (query, workbook, Web template). In the RSDDSTAT transaction, you can turn the statistics on and off for all queries for an InfoProvider. The maintenance of the settings (such as before) from the Data Warehousing Workbench can be reached using Tools ® BW Statistics.
You can use this BRCONNECT function to update the statistics on the Oracle database for the cost-based optimizer.
By running update statistics regularly, you make sure that the database statistics are up-to-date, so improving database performance. The Oracle cost-based optimizer (CBO) uses the statistics to optimize access paths when retrieving data for queries. If the statistics are out-of-date, the CBO might generate inappropriate access paths (such as using the wrong index), resulting in poor performance.
From Release 4.0, the CBO is a standard part of the SAP System. If statistics are available for a table, the database system uses the cost-based optimizer. Otherwise, it uses the rule-based optimizer.
Partitioned tables, except where partitioned tables are explicitly excluded by setting the active flag in the DBSTATC table to I. For more information, see SAP
InfoCube tables for the SAP Business Information Warehouse (SAP BW)
You can update statistics using one of the following methods:
DBA Planning Calendar in the Computing Center Management System (CCMS)
For more information, see Update Statistics for the Cost-Based Optimizer in CCMS (Oracle). The DBA Planning Calendar uses the BRCONNECT commands.
We recommend you to use this approach because you can easily schedule update statistics to run automatically at specified intervals (for example, weekly).
To use the CBO, make sure that the parameter OPTIMIZER_MODE in the Oracle initialization profile init.ora is set to CHOOSE.
BRCONNECT performs update statistics using a two-phase approach.
1. Checks each table to see if the statistics are out-of-date
2. If required, updates the statistics on the table immediately after the check
For more information about how update statistics works, see Internal Rules for Update Statistics.
You can influence how update statistics works by using the -force options. For more information, see -f stats.
Unless you have special requirements, we recommend you to perform the standard update statistics, using one of the following tools to schedule it on a regular basis (for example, daily or weekly):
DBA Planning Calendar, as described above in "Integration."
A tool such as cron (UNIX) or at (Windows NT) to execute the following standard call:
brconnect -u / -c -f stats -t all
This is also adequate after an upgrade of the database or SAP System. It runs using the OPS$ user without operator intervention.
Update statistics only for tables and indexes with missing statistics
brconnect -u / -c -f stats -t missing
Check and update statistics for all tables defined in the DBSTATC table
brconnect -u / -c -f stats -t dbstatc_tab
For examples of how you can override the internal rules for update statistics, see -force with Update Statistics.
The InfoCube tables used in SAP Business Information Warehouse (SAP BW) and Advanced Planner and Optimizer (APO) need to be processed in a special way when the statistics are being updated. Usually, statistics should be created using histograms, Statistics for the InfoCube tables can be updated, together with other tables in a run. In this case, the statistics for the InfoCube tables are always created with histograms. You can specify which tables are to be handled as InfoCube tables using the init.sap parameters:
stats_table
stats_exclude
stats_dbms_stats
The function of this keyword is to ensure that only InfoCube tables are processed in accordance with the selected parameter settings.
Statistics are only checked for InfoCube tables and updated, if required
brconnect -u / -c -f stats -t all -e info_cubes
Statistics are checked for all tables besides InfoCube tables and updated, if necessary.
stats_dbms_stats = INFO_CUBES:R:4
brconnect -u / -c -f stats -t all, Statistics are checked for all tables and updated, if necessary. New statistics for InfoCube tables are created with the DBMS_STATS package using row sampling and an internal parallel degree of 4.
This is the default. Statistics are checked for all tables and updated, if necessary. If InfoCube tables are present and selected following the update check, statistics are generated for them using histograms.
You can update statistics on the Oracle database using the Computing Center Management System (CCMS).
By running update statistics regularly, you make sure that the database statistics are up-to-date, so improving database performance. The Oracle cost-based optimizer (CBO) uses the statistics to optimize access paths when retrieving data for queries. If the statistics are out-of-date, the CBO might generate inappropriate access paths (such as using the wrong index), resulting in poor performance.
The CBO is a standard part of the SAP system. If statistics are available for a table, the database system uses the cost-based optimizer. Otherwise, it uses the rule-based optimizer.
You can also run update statistics for your Oracle database using BRCONNECT. Refer to Update Statistics with BRCONNECT. This is the recommended way to update statistics.
Update statistics after installations and upgrades
You need to update statistics for all tables in the SAP system after an installation or an upgrade. This is described in the relevant installation or upgrade documentation.
1. You use the DBA Planning Calendar in CCMS to schedule regular execution of check statistics and, if necessary, update statistics. For more information.
2. If required, you run one-off checks on tables to see if the tables statistics are out-of-date, and then run an update statistics for the table if required. This is useful, for example, if the data in a table has been significantly updated, but the next scheduled run of update statistics is not for a long time.
You can check, create, update, or delete statistics for:
¡ Single tables
¡ Groups of tables
3. If required, you configure update statistics by amending the parameters in the control table DBSTATC . This control table contains a list of the database tables for which the default values for update statistics are not suitable. If you change this table, all runs of update statistics in BRCONNECT, CCMS, or the DBA Planning Calendar are affected. Configuring update statistics makes sense with large tables, for which the default parameters might not be appropriate.
Do not add, delete, or change table entries unless you are aware of the consequences.
Tables from the DBSTATC table with either of the following values:
ACTIVE field U
ACTIVE field R or N and USE field A(relevant for the application monitor)
6. BRCONNECT writes the results of update statistics to the DBSTATTORA table and also, for tables with the DBSTATC history flag or usage type A, to the DBSTATHORA table.
7. For tables with update statistics using methods EI, EX, CI, or CX, BRCONNECT validates the structure of all associated indexes and writes the results to the DBSTATIORA table and also, for tables with the DBSTATC history flag or usage type A, to the DBSTAIHORA table.
8. BRCONNECT immediately deletes the statistics that it created in this procedure for tables with the ACTIVE flag set to N or R in the DBSTATC table. -
Oracle OLAP Catalog BI checkconfig diagnose warning
Hi,
platform server:
- HP-UX
- Oracle 9.0.6. RDBMS (according to Disco requirements the right version)
platform client:
- Discoverer 10.2.1 'Drake'
- Windows 2000
- Internet Explorer
We are trying tot connect our Analytical Workspace with the new Discoverer. We want to use the OLAP functionallity of Disco. In production we already use OLAP Web Agent and OLAP_TABLE functions tot connect our AW, but that is whitout the use of the catalog.
After succesfully installing Disco on the server we get in de 'Extensive Diagnose' (same as the bi_checkconfig BI Beans procedure) of Oracle Discoverer this messages:
<?xml version="1.0" encoding="UTF-8" ?>
<D4OCheckConfig version="1.0.0.0">
<Check key="JDK version" value="1.4.2_04"/>
<Check key="BI Beans internal version" value="3.2.1.0.13"/>
<Check key="Discoverer Plus OLAP version" value="10.1.2.07.59"/>
<Check key="Discoverer version" value="10.1.2.45.46c"/>
<Check key="port" value="-1"/>
<Check key="Connect to database" value="Successful"/>
<Check key="JDBC driver version" value="10.1.0.3.0"/>
<Check key="JDBC JAR file location" value="\zeias07.csodom1.cso.drp.minjus\disco\plus_files\d4o_double.jarjar"/>
<Check key="Database version" value="9.2.0.6.0"/>
<Check key="OLAP API Server version" value="9.2.0.6.0"/>
<Check key="OLAP AW Engine version" value="9.2.0.6.0"/>
<Check key="OLAP Catalog version" value="9.2.0.6.0"/>
<Check key="BI Beans Catalog version" value="3.2.1.0.13"/>
<Check key="Discoverer Catalog version" value="10.1.2.07.59"/>
<Check key="Authorized for Discoverer Plus OLAP catalog" value="Yes"/>
<Check key="OLAP API JAR file version" value="9.2"/>
<Check key="OLAP API JAR file location" value="\zeias07.csodom1.cso.drp.minjus\disco\plus_files\d4o_double.jarjar"/>
<Check key="Load OLAP API metadata" value="Successful"/>
<Check key="Number of metadata folders" value="2"/>
<Check key="Number of metadata measures" value="179"/>
<Check key="Number of metadata dimensions" value="9"/>
<Check key="OLAP API Metadata">
<![CDATA[==============================================================================
Type Name (S=Schema, C=Cube, M=Measure, D=Dimension) Status
========= ======================================================= ============
Folder... ROOT
Measure.. DFTE_OD Successful
S=SH1DWH, C=DC_PERSONEEL, M=DFTE_OD
Measure.. DFTE_RM Successful
S=SH1DWH, C=DC_PERSONEEL, M=DFTE_RM
Measure.. DTFB_NEG_OD Successful
S=SH1DWH, C=DC_PERSONEEL, M=DTFB_NEG_OD
Measure.. DTFB_NEG_RM Successful
S=SH1DWH, C=DC_PERSONEEL, M=DTFB_NEG_RM
Measure.. DTFB_POS_OD Successful
S=SH1DWH, C=DC_PERSONEEL, M=DTFB_POS_OD
Measure.. DTFB_POS_RM Successful
S=SH1DWH, C=DC_PERSONEEL, M=DTFB_POS_RM
Measure.. DZKT_AFSP_OD_KORT_NEG Successful
S=SH1DWH, C=DC_PERSONEEL, M=DZKT_AFSP_OD_KORT_NEG
Measure.. DZKT_AFSP_OD_KORT_POS Successful
S=SH1DWH, C=DC_PERSONEEL, M=DZKT_AFSP_OD_KORT_POS
Measure.. DZKT_AFSP_OD_LANG_NEG Successful
S=SH1DWH, C=DC_PERSONEEL, M=DZKT_AFSP_OD_LANG_NEG
Measure.. DZKT_AFSP_OD_LANG_POS Successful
S=SH1DWH, C=DC_PERSONEEL, M=DZKT_AFSP_OD_LANG_POS
Measure.. DZKT_AFSP_OD_ZWAN_NEG Successful
S=SH1DWH, C=DC_PERSONEEL, M=DZKT_AFSP_OD_ZWAN_NEG
Measure.. DZKT_AFSP_OD_ZWAN_POS Successful
S=SH1DWH, C=DC_PERSONEEL, M=DZKT_AFSP_OD_ZWAN_POS
Measure.. DZKT_AFSP_PCT_OD_KORT_NEG Successful
S=SH1DWH, C=DC_PERSONEEL, M=DZKT_AFSP_PCT_OD_KORT_NEG
Measure.. DZKT_AFSP_PCT_OD_KORT_POS Successful
S=SH1DWH, C=DC_PERSONEEL, M=DZKT_AFSP_PCT_OD_KORT_POS
Measure.. DZKT_AFSP_PCT_OD_LANG_NEG Successful
S=SH1DWH, C=DC_PERSONEEL, M=DZKT_AFSP_PCT_OD_LANG_NEG
Measure.. DZKT_AFSP_PCT_OD_LANG_POS Successful
S=SH1DWH, C=DC_PERSONEEL, M=DZKT_AFSP_PCT_OD_LANG_POS
Measure.. DZKT_AFSP_PCT_OD_ZWAN_NEG Successful
S=SH1DWH, C=DC_PERSONEEL, M=DZKT_AFSP_PCT_OD_ZWAN_NEG
Measure.. DZKT_AFSP_PCT_OD_ZWAN_POS Successful
S=SH1DWH, C=DC_PERSONEEL, M=DZKT_AFSP_PCT_OD_ZWAN_POS
Measure.. DZKT_AFSP_PCT_RM_KORT_NEG Successful
S=SH1DWH, C=DC_PERSONEEL, M=DZKT_AFSP_PCT_RM_KORT_NEG
Measure.. DZKT_AFSP_PCT_RM_KORT_POS Successful
S=SH1DWH, C=DC_PERSONEEL, M=DZKT_AFSP_PCT_RM_KORT_POS
Measure.. DZKT_AFSP_PCT_RM_LANG_NEG Successful
S=SH1DWH, C=DC_PERSONEEL, M=DZKT_AFSP_PCT_RM_LANG_NEG
Measure.. DZKT_AFSP_PCT_RM_LANG_POS Successful
S=SH1DWH, C=DC_PERSONEEL, M=DZKT_AFSP_PCT_RM_LANG_POS
Measure.. DZKT_AFSP_PCT_RM_ZWAN_NEG Successful
S=SH1DWH, C=DC_PERSONEEL, M=DZKT_AFSP_PCT_RM_ZWAN_NEG
Measure.. DZKT_AFSP_PCT_RM_ZWAN_POS Successful
S=SH1DWH, C=DC_PERSONEEL, M=DZKT_AFSP_PCT_RM_ZWAN_POS
Measure.. DZKT_AFSP_RM_KORT_NEG Successful
S=SH1DWH, C=DC_PERSONEEL, M=DZKT_AFSP_RM_KORT_NEG
Measure.. DZKT_AFSP_RM_KORT_POS Successful
S=SH1DWH, C=DC_PERSONEEL, M=DZKT_AFSP_RM_KORT_POS
Measure.. DZKT_AFSP_RM_LANG_NEG Successful
S=SH1DWH, C=DC_PERSONEEL, M=DZKT_AFSP_RM_LANG_NEG
Measure.. DZKT_AFSP_RM_LANG_POS Successful
S=SH1DWH, C=DC_PERSONEEL, M=DZKT_AFSP_RM_LANG_POS
Measure.. DZKT_AFSP_RM_ZWAN_NEG Successful
S=SH1DWH, C=DC_PERSONEEL, M=DZKT_AFSP_RM_ZWAN_NEG
Measure.. DZKT_AFSP_RM_ZWAN_POS Successful
S=SH1DWH, C=DC_PERSONEEL, M=DZKT_AFSP_RM_ZWAN_POS
Measure.. DZKT_AFSP_TOTL Successful
S=SH1DWH, C=DC_PERSONEEL, M=DZKT_AFSP_TOTL
Measure.. DZKT_PCT_OD_KORT Successful
S=SH1DWH, C=DC_PERSONEEL, M=DZKT_PCT_OD_KORT
Measure.. DZKT_PCT_OD_LANG Successful
S=SH1DWH, C=DC_PERSONEEL, M=DZKT_PCT_OD_LANG
Measure.. DZKT_PCT_OD_ZWAN Successful
S=SH1DWH, C=DC_PERSONEEL, M=DZKT_PCT_OD_ZWAN
Measure.. DZKT_PCT_RM_KORT Successful
S=SH1DWH, C=DC_PERSONEEL, M=DZKT_PCT_RM_KORT
Measure.. DZKT_PCT_RM_LANG Successful
S=SH1DWH, C=DC_PERSONEEL, M=DZKT_PCT_RM_LANG
Measure.. DZKT_PCT_RM_ZWAN Successful
S=SH1DWH, C=DC_PERSONEEL, M=DZKT_PCT_RM_ZWAN
Measure.. DZKT_REAL_OD_KORT Successful
S=SH1DWH, C=DC_PERSONEEL, M=DZKT_REAL_OD_KORT
Measure.. DZKT_REAL_OD_LANG Successful
S=SH1DWH, C=DC_PERSONEEL, M=DZKT_REAL_OD_LANG
Measure.. DZKT_REAL_OD_ZWAN Successful
S=SH1DWH, C=DC_PERSONEEL, M=DZKT_REAL_OD_ZWAN
Measure.. DZKT_REAL_RM_KORT Successful
S=SH1DWH, C=DC_PERSONEEL, M=DZKT_REAL_RM_KORT
Measure.. DZKT_REAL_RM_LANG Successful
S=SH1DWH, C=DC_PERSONEEL, M=DZKT_REAL_RM_LANG
Measure.. DZKT_REAL_RM_ZWAN Successful
S=SH1DWH, C=DC_PERSONEEL, M=DZKT_REAL_RM_ZWAN
Dimension DLAMICIE Successful
S=SH1DWH, D=DD_LAMICIE
Dimension DLOCATIE Successful
S=SH1DWH, D=DD_LOCATIE
Dimension DTIJD Successful
S=SH1DWH, D=DD_TIME
Dimension GEBRUIKER Successful
S=SH1DWH, D=D_GEBRUIKER
Folder... Deze Collection bevat alle Dimensions en Cubes, behalve de Cubes C_Productie en C_TFB. Met de OWB-OLAP bridge deze Collection deployen (voor de OLAP Catalog) en de Analytic Workspace laten aanmaken en vullen.
Measure.. UIT_VERS_ARR Unsuccessful
S=SH1DWH, C=C_PRDARRCAT, M=UIT_VERS_ARR
Measure.. UIT_AFSP_POS_ARR Unsuccessful
S=SH1DWH, C=C_PRDARRCAT, M=UIT_AFSP_POS_ARR
Measure.. UIT_AFSP_NEG_ARR Unsuccessful
S=SH1DWH, C=C_PRDARRCAT, M=UIT_AFSP_NEG_ARR
Measure.. UIT_AFSP_ARR Unsuccessful
S=SH1DWH, C=C_PRDARRCAT, M=UIT_AFSP_ARR
Measure.. TFB_BRKD_RM_ARR Unsuccessful
S=SH1DWH, C=C_PRDARRCAT, M=TFB_BRKD_RM_ARR
Measure.. TFB_BRKD_OD_ARR Unsuccessful
S=SH1DWH, C=C_PRDARRCAT, M=TFB_BRKD_OD_ARR
Measure.. DLT_VERS_DGN_ARR Unsuccessful
S=SH1DWH, C=C_PRDARRCAT, M=DLT_VERS_DGN_ARR
Measure.. DLT_AFSP_DGN_POS_ARR Unsuccessful
S=SH1DWH, C=C_PRDARRCAT, M=DLT_AFSP_DGN_POS_ARR
Measure.. DLT_AFSP_DGN_NEG_ARR Unsuccessful
S=SH1DWH, C=C_PRDARRCAT, M=DLT_AFSP_DGN_NEG_ARR
Measure.. DLT_AFSP_DGN_ARR Unsuccessful
S=SH1DWH, C=C_PRDARRCAT, M=DLT_AFSP_DGN_ARR
Measure.. WRK_REAL_ARR Unsuccessful
S=SH1DWH, C=C_PRDARRMEL, M=WRK_REAL_ARR
Measure.. UIT_REAL_ARR Unsuccessful
S=SH1DWH, C=C_PRDARRMEL, M=UIT_REAL_ARR
Measure.. INS_REAL_ARR Unsuccessful
S=SH1DWH, C=C_PRDARRMEL, M=INS_REAL_ARR
Measure.. DLT_REAL_ZKN_ARR Unsuccessful
S=SH1DWH, C=C_PRDARRMEL, M=DLT_REAL_ZKN_ARR
Measure.. DLT_REAL_GMD_ARR Unsuccessful
S=SH1DWH, C=C_PRDARRMEL, M=DLT_REAL_GMD_ARR
Measure.. DLT_REAL_DGN_ARR Unsuccessful
S=SH1DWH, C=C_PRDARRMEL, M=DLT_REAL_DGN_ARR
Measure.. WRK_VERS_ARR Unsuccessful
S=SH1DWH, C=C_PRDARRSUB, M=WRK_VERS_ARR
Measure.. WRK_AFSP_POS_ARR Unsuccessful
S=SH1DWH, C=C_PRDARRSUB, M=WRK_AFSP_POS_ARR
Measure.. WRK_AFSP_NEG_ARR Unsuccessful
S=SH1DWH, C=C_PRDARRSUB, M=WRK_AFSP_NEG_ARR
Measure.. WRK_AFSP_ARR Unsuccessful
S=SH1DWH, C=C_PRDARRSUB, M=WRK_AFSP_ARR
Measure.. TFB_VERS_RM_ARR Unsuccessful
S=SH1DWH, C=C_PRDARRSUB, M=TFB_VERS_RM_ARR
Measure.. TFB_VERS_OD_ARR Unsuccessful
S=SH1DWH, C=C_PRDARRSUB, M=TFB_VERS_OD_ARR
Measure.. TFB_FEIT_RM_ARR Unsuccessful
S=SH1DWH, C=C_PRDARRSUB, M=TFB_FEIT_RM_ARR
Measure.. TFB_FEIT_OD_ARR Unsuccessful
S=SH1DWH, C=C_PRDARRSUB, M=TFB_FEIT_OD_ARR
Measure.. TFB_BRKD_RM_POS_ARR Unsuccessful
S=SH1DWH, C=C_PRDARRSUB, M=TFB_BRKD_RM_POS_ARR
Measure.. TFB_BRKD_RM_NEG_ARR Unsuccessful
S=SH1DWH, C=C_PRDARRSUB, M=TFB_BRKD_RM_NEG_ARR
Measure.. TFB_BRKD_OD_POS_ARR Unsuccessful
S=SH1DWH, C=C_PRDARRSUB, M=TFB_BRKD_OD_POS_ARR
Measure.. TFB_BRKD_OD_NEG_ARR Unsuccessful
S=SH1DWH, C=C_PRDARRSUB, M=TFB_BRKD_OD_NEG_ARR
Measure.. INS_VERS_ARR Unsuccessful
S=SH1DWH, C=C_PRDARRSUB, M=INS_VERS_ARR
Measure.. INS_AFSP_POS_ARR Unsuccessful
S=SH1DWH, C=C_PRDARRSUB, M=INS_AFSP_POS_ARR
Measure.. INS_AFSP_NEG_ARR Unsuccessful
S=SH1DWH, C=C_PRDARRSUB, M=INS_AFSP_NEG_ARR
Measure.. INS_AFSP_ARR Unsuccessful
S=SH1DWH, C=C_PRDARRSUB, M=INS_AFSP_ARR
Measure.. TFB_BRKD_RM_SOM Unsuccessful
S=SH1DWH, C=C_PRDKTGCAT, M=TFB_BRKD_RM_SOM
Measure.. TFB_BRKD_RM_KTG Unsuccessful
S=SH1DWH, C=C_PRDKTGCAT, M=TFB_BRKD_RM_KTG
Measure.. TFB_BRKD_OD_SOM Unsuccessful
S=SH1DWH, C=C_PRDKTGCAT, M=TFB_BRKD_OD_SOM
Measure.. TFB_BRKD_OD_KTG Unsuccessful
S=SH1DWH, C=C_PRDKTGCAT, M=TFB_BRKD_OD_KTG
Measure.. WRK_REAL_SOM Unsuccessful
S=SH1DWH, C=C_PRDKTGMEL, M=WRK_REAL_SOM
Measure.. WRK_REAL_KTG Unsuccessful
S=SH1DWH, C=C_PRDKTGMEL, M=WRK_REAL_KTG
Measure.. UIT_REAL_SOM Unsuccessful
S=SH1DWH, C=C_PRDKTGMEL, M=UIT_REAL_SOM
Measure.. UIT_REAL_KTG Unsuccessful
S=SH1DWH, C=C_PRDKTGMEL, M=UIT_REAL_KTG
Measure.. INS_REAL_SOM Unsuccessful
S=SH1DWH, C=C_PRDKTGMEL, M=INS_REAL_SOM
Measure.. INS_REAL_KTG Unsuccessful
S=SH1DWH, C=C_PRDKTGMEL, M=INS_REAL_KTG
Measure.. DLT_REAL_ZKN_SOM Unsuccessful
S=SH1DWH, C=C_PRDKTGMEL, M=DLT_REAL_ZKN_SOM
Measure.. DLT_REAL_ZKN_KTG Unsuccessful
S=SH1DWH, C=C_PRDKTGMEL, M=DLT_REAL_ZKN_KTG
Measure.. DLT_REAL_GMD_SOM Unsuccessful
S=SH1DWH, C=C_PRDKTGMEL, M=DLT_REAL_GMD_SOM
Measure.. DLT_REAL_GMD_KTG Unsuccessful
S=SH1DWH, C=C_PRDKTGMEL, M=DLT_REAL_GMD_KTG
Measure.. DLT_REAL_DGN_SOM Unsuccessful
S=SH1DWH, C=C_PRDKTGMEL, M=DLT_REAL_DGN_SOM
Measure.. DLT_REAL_DGN_KTG Unsuccessful
S=SH1DWH, C=C_PRDKTGMEL, M=DLT_REAL_DGN_KTG
Dimension LAMICIE Successful
S=SH1DWH, D=D_LAMICIE
Dimension LOCATIE Successful
S=SH1DWH, D=D_LOCATIE
Dimension TIJD Unsuccessful
S=SH1DWH, D=D_TIME
Folder... Deze Collection bevat alleen de Cubes C_Productie en C_TFB. Met de OWB-OLAP bridge deze Collection wel deployen (voor de OLAP Catalog), maar NIET de Analytic Workspace laten aanmaken en vullen.
Measure.. FIN_VERS_REAL_BUDG_PR_JTD Unsuccessful
S=SH1DWH, C=C_FINANCIEEL, M=FIN_VERS_REAL_BUDG_PR_JTD
Measure.. FIN_VERS_REAL_BUDG_PR Unsuccessful
S=SH1DWH, C=C_FINANCIEEL, M=FIN_VERS_REAL_BUDG_PR
Measure.. FIN_VERS_REAL_BUDG_MT_JTD Unsuccessful
S=SH1DWH, C=C_FINANCIEEL, M=FIN_VERS_REAL_BUDG_MT_JTD
Measure.. FIN_VERS_REAL_BUDG_MT Unsuccessful
S=SH1DWH, C=C_FINANCIEEL, M=FIN_VERS_REAL_BUDG_MT
Measure.. FIN_VERS_BUDG_PROG_PR Unsuccessful
S=SH1DWH, C=C_FINANCIEEL, M=FIN_VERS_BUDG_PROG_PR
Measure.. FIN_VERS_BUDG_PROG_MT Unsuccessful
S=SH1DWH, C=C_FINANCIEEL, M=FIN_VERS_BUDG_PROG_MT
Measure.. FIN_REAL_PR_JTD Unsuccessful
S=SH1DWH, C=C_FINANCIEEL, M=FIN_REAL_PR_JTD
Measure.. FIN_REAL_PR Unsuccessful
S=SH1DWH, C=C_FINANCIEEL, M=FIN_REAL_PR
Measure.. FIN_REAL_MT_JTD Unsuccessful
S=SH1DWH, C=C_FINANCIEEL, M=FIN_REAL_MT_JTD
Measure.. FIN_REAL_MT Unsuccessful
S=SH1DWH, C=C_FINANCIEEL, M=FIN_REAL_MT
Measure.. FIN_PROG_PR_POS Unsuccessful
S=SH1DWH, C=C_FINANCIEEL, M=FIN_PROG_PR_POS
Measure.. FIN_PROG_PR_NEG Unsuccessful
S=SH1DWH, C=C_FINANCIEEL, M=FIN_PROG_PR_NEG
Measure.. FIN_PROG_PR Unsuccessful
S=SH1DWH, C=C_FINANCIEEL, M=FIN_PROG_PR
Measure.. FIN_PROG_MT_POS Unsuccessful
S=SH1DWH, C=C_FINANCIEEL, M=FIN_PROG_MT_POS
Measure.. FIN_PROG_MT_NEG Unsuccessful
S=SH1DWH, C=C_FINANCIEEL, M=FIN_PROG_MT_NEG
Measure.. FIN_PROG_MT Unsuccessful
S=SH1DWH, C=C_FINANCIEEL, M=FIN_PROG_MT
Measure.. FIN_KOST_FEIT_BEZ Unsuccessful
S=SH1DWH, C=C_FINANCIEEL, M=FIN_KOST_FEIT_BEZ
Measure.. FIN_JAARBUDGET_PR Unsuccessful
S=SH1DWH, C=C_FINANCIEEL, M=FIN_JAARBUDGET_PR
Measure.. FIN_JAARBUDGET_MT Unsuccessful
S=SH1DWH, C=C_FINANCIEEL, M=FIN_JAARBUDGET_MT
Measure.. FIN_BUDG_PR_POS_JTD Unsuccessful
S=SH1DWH, C=C_FINANCIEEL, M=FIN_BUDG_PR_POS_JTD
Measure.. FIN_BUDG_PR_POS Unsuccessful
S=SH1DWH, C=C_FINANCIEEL, M=FIN_BUDG_PR_POS
Measure.. FIN_BUDG_PR_NEG_JTD Unsuccessful
S=SH1DWH, C=C_FINANCIEEL, M=FIN_BUDG_PR_NEG_JTD
Measure.. FIN_BUDG_PR_NEG Unsuccessful
S=SH1DWH, C=C_FINANCIEEL, M=FIN_BUDG_PR_NEG
Measure.. FIN_BUDG_PR_JTD Unsuccessful
S=SH1DWH, C=C_FINANCIEEL, M=FIN_BUDG_PR_JTD
Measure.. FIN_BUDG_PR Unsuccessful
S=SH1DWH, C=C_FINANCIEEL, M=FIN_BUDG_PR
Measure.. FIN_BUDG_MT_POS_JTD Unsuccessful
S=SH1DWH, C=C_FINANCIEEL, M=FIN_BUDG_MT_POS_JTD
Measure.. FIN_BUDG_MT_POS Unsuccessful
S=SH1DWH, C=C_FINANCIEEL, M=FIN_BUDG_MT_POS
Measure.. FIN_BUDG_MT_NEG_JTD Unsuccessful
S=SH1DWH, C=C_FINANCIEEL, M=FIN_BUDG_MT_NEG_JTD
Measure.. FIN_BUDG_MT_NEG Unsuccessful
S=SH1DWH, C=C_FINANCIEEL, M=FIN_BUDG_MT_NEG
Measure.. FIN_BUDG_MT_JTD Unsuccessful
S=SH1DWH, C=C_FINANCIEEL, M=FIN_BUDG_MT_JTD
Measure.. FIN_BUDG_MT Unsuccessful
S=SH1DWH, C=C_FINANCIEEL, M=FIN_BUDG_MT
Measure.. KWA_SCORE Unsuccessful
S=SH1DWH, C=C_KWALITEIT, M=KWA_SCORE
Measure.. KWA_NORM_POS Unsuccessful
S=SH1DWH, C=C_KWALITEIT, M=KWA_NORM_POS
Measure.. KWA_NORM_NEG Unsuccessful
S=SH1DWH, C=C_KWALITEIT, M=KWA_NORM_NEG
Measure.. NRM_MINUTEN_RM_RB Unsuccessful
S=SH1DWH, C=C_NORMTIJD, M=NRM_MINUTEN_RM_RB
Measure.. NRM_MINUTEN_RM_KTG Unsuccessful
S=SH1DWH, C=C_NORMTIJD, M=NRM_MINUTEN_RM_KTG
Measure.. NRM_MINUTEN_OD_RB Unsuccessful
S=SH1DWH, C=C_NORMTIJD, M=NRM_MINUTEN_OD_RB
Measure.. NRM_MINUTEN_OD_KTG Unsuccessful
S=SH1DWH, C=C_NORMTIJD, M=NRM_MINUTEN_OD_KTG
Measure.. ZKT_REAL_RM_ZWAN Unsuccessful
S=SH1DWH, C=C_PERSONEEL, M=ZKT_REAL_RM_ZWAN
Measure.. ZKT_REAL_RM_LANG Unsuccessful
S=SH1DWH, C=C_PERSONEEL, M=ZKT_REAL_RM_LANG
Measure.. ZKT_REAL_RM_KORT Unsuccessful
S=SH1DWH, C=C_PERSONEEL, M=ZKT_REAL_RM_KORT
Measure.. ZKT_REAL_OD_ZWAN Unsuccessful
S=SH1DWH, C=C_PERSONEEL, M=ZKT_REAL_OD_ZWAN
Measure.. ZKT_REAL_OD_LANG Unsuccessful
S=SH1DWH, C=C_PERSONEEL, M=ZKT_REAL_OD_LANG
Measure.. ZKT_REAL_OD_KORT Unsuccessful
S=SH1DWH, C=C_PERSONEEL, M=ZKT_REAL_OD_KORT
Measure.. ZKT_PCT_RM_ZWAN Unsuccessful
S=SH1DWH, C=C_PERSONEEL, M=ZKT_PCT_RM_ZWAN
Measure.. ZKT_PCT_RM_LANG Unsuccessful
S=SH1DWH, C=C_PERSONEEL, M=ZKT_PCT_RM_LANG
Measure.. ZKT_PCT_RM_KORT Unsuccessful
S=SH1DWH, C=C_PERSONEEL, M=ZKT_PCT_RM_KORT
Measure.. ZKT_PCT_OD_ZWAN Unsuccessful
S=SH1DWH, C=C_PERSONEEL, M=ZKT_PCT_OD_ZWAN
Measure.. ZKT_PCT_OD_LANG Unsuccessful
S=SH1DWH, C=C_PERSONEEL, M=ZKT_PCT_OD_LANG
Measure.. ZKT_PCT_OD_KORT Unsuccessful
S=SH1DWH, C=C_PERSONEEL, M=ZKT_PCT_OD_KORT
Measure.. ZKT_AFSP_TOTL Unsuccessful
S=SH1DWH, C=C_PERSONEEL, M=ZKT_AFSP_TOTL
Measure.. ZKT_AFSP_RM_ZWAN_POS Unsuccessful
S=SH1DWH, C=C_PERSONEEL, M=ZKT_AFSP_RM_ZWAN_POS
Measure.. ZKT_AFSP_RM_ZWAN_NEG Unsuccessful
S=SH1DWH, C=C_PERSONEEL, M=ZKT_AFSP_RM_ZWAN_NEG
Measure.. ZKT_AFSP_RM_LANG_POS Unsuccessful
S=SH1DWH, C=C_PERSONEEL, M=ZKT_AFSP_RM_LANG_POS
Measure.. ZKT_AFSP_RM_LANG_NEG Unsuccessful
S=SH1DWH, C=C_PERSONEEL, M=ZKT_AFSP_RM_LANG_NEG
Measure.. ZKT_AFSP_RM_KORT_POS Unsuccessful
S=SH1DWH, C=C_PERSONEEL, M=ZKT_AFSP_RM_KORT_POS
Measure.. ZKT_AFSP_RM_KORT_NEG Unsuccessful
S=SH1DWH, C=C_PERSONEEL, M=ZKT_AFSP_RM_KORT_NEG
Measure.. ZKT_AFSP_PCT_RM_ZWAN_POS Unsuccessful
S=SH1DWH, C=C_PERSONEEL, M=ZKT_AFSP_PCT_RM_ZWAN_POS
Measure.. ZKT_AFSP_PCT_RM_ZWAN_NEG Unsuccessful
S=SH1DWH, C=C_PERSONEEL, M=ZKT_AFSP_PCT_RM_ZWAN_NEG
Measure.. ZKT_AFSP_PCT_RM_LANG_POS Unsuccessful
S=SH1DWH, C=C_PERSONEEL, M=ZKT_AFSP_PCT_RM_LANG_POS
Measure.. ZKT_AFSP_PCT_RM_LANG_NEG Unsuccessful
S=SH1DWH, C=C_PERSONEEL, M=ZKT_AFSP_PCT_RM_LANG_NEG
Measure.. ZKT_AFSP_PCT_RM_KORT_POS Unsuccessful
S=SH1DWH, C=C_PERSONEEL, M=ZKT_AFSP_PCT_RM_KORT_POS
Measure.. ZKT_AFSP_PCT_RM_KORT_NEG Unsuccessful
S=SH1DWH, C=C_PERSONEEL, M=ZKT_AFSP_PCT_RM_KORT_NEG
Measure.. ZKT_AFSP_PCT_OD_ZWAN_POS Unsuccessful
S=SH1DWH, C=C_PERSONEEL, M=ZKT_AFSP_PCT_OD_ZWAN_POS
Measure.. ZKT_AFSP_PCT_OD_ZWAN_NEG Unsuccessful
S=SH1DWH, C=C_PERSONEEL, M=ZKT_AFSP_PCT_OD_ZWAN_NEG
Measure.. ZKT_AFSP_PCT_OD_LANG_POS Unsuccessful
S=SH1DWH, C=C_PERSONEEL, M=ZKT_AFSP_PCT_OD_LANG_POS
Measure.. ZKT_AFSP_PCT_OD_LANG_NEG Unsuccessful
S=SH1DWH, C=C_PERSONEEL, M=ZKT_AFSP_PCT_OD_LANG_NEG
Measure.. ZKT_AFSP_PCT_OD_KORT_POS Unsuccessful
S=SH1DWH, C=C_PERSONEEL, M=ZKT_AFSP_PCT_OD_KORT_POS
Measure.. ZKT_AFSP_PCT_OD_KORT_NEG Unsuccessful
S=SH1DWH, C=C_PERSONEEL, M=ZKT_AFSP_PCT_OD_KORT_NEG
Measure.. ZKT_AFSP_OD_ZWAN_POS Unsuccessful
S=SH1DWH, C=C_PERSONEEL, M=ZKT_AFSP_OD_ZWAN_POS
Measure.. ZKT_AFSP_OD_ZWAN_NEG Unsuccessful
S=SH1DWH, C=C_PERSONEEL, M=ZKT_AFSP_OD_ZWAN_NEG
Measure.. ZKT_AFSP_OD_LANG_POS Unsuccessful
S=SH1DWH, C=C_PERSONEEL, M=ZKT_AFSP_OD_LANG_POS
Measure.. ZKT_AFSP_OD_LANG_NEG Unsuccessful
S=SH1DWH, C=C_PERSONEEL, M=ZKT_AFSP_OD_LANG_NEG
Measure.. ZKT_AFSP_OD_KORT_POS Unsuccessful
S=SH1DWH, C=C_PERSONEEL, M=ZKT_AFSP_OD_KORT_POS
Measure.. ZKT_AFSP_OD_KORT_NEG Unsuccessful
S=SH1DWH, C=C_PERSONEEL, M=ZKT_AFSP_OD_KORT_NEG
Measure.. TFB_POS_RM Unsuccessful
S=SH1DWH, C=C_PERSONEEL, M=TFB_POS_RM
Measure.. TFB_POS_OD Unsuccessful
S=SH1DWH, C=C_PERSONEEL, M=TFB_POS_OD
Measure.. TFB_NEG_RM Unsuccessful
S=SH1DWH, C=C_PERSONEEL, M=TFB_NEG_RM
Measure.. TFB_NEG_OD Unsuccessful
S=SH1DWH, C=C_PERSONEEL, M=TFB_NEG_OD
Measure.. FTE_RM Unsuccessful
S=SH1DWH, C=C_PERSONEEL, M=FTE_RM
Measure.. FTE_OD Unsuccessful
S=SH1DWH, C=C_PERSONEEL, M=FTE_OD
Measure.. SCD_VORIG Successful
S=SH1DWH, C=C_SCORECARD, M=SCD_VORIG
Measure.. SCD_SCORE Unsuccessful
S=SH1DWH, C=C_SCORECARD, M=SCD_SCORE
Measure.. SCD_REAL Successful
S=SH1DWH, C=C_SCORECARD, M=SCD_REAL
Measure.. SCD_PROG Successful
S=SH1DWH, C=C_SCORECARD, M=SCD_PROG
Measure.. SCD_AFSP_POS Successful
S=SH1DWH, C=C_SCORECARD, M=SCD_AFSP_POS
Measure.. SCD_AFSP_NEG Successful
S=SH1DWH, C=C_SCORECARD, M=SCD_AFSP_NEG
Measure.. SCD_AFSP Successful
S=SH1DWH, C=C_SCORECARD, M=SCD_AFSP
Dimension LAMICIE Successful
S=SH1DWH, D=D_LAMICIE
Dimension LOCATIE Successful
S=SH1DWH, D=D_LOCATIE
Dimension TIJD Unsuccessful
S=SH1DWH, D=D_TIME
Dimension KWALITEIT Successful
S=SH1DWH, D=D_KWALITEIT
Dimension SCORECARD Successful
S=SH1DWH, D=D_SCORECARD
]]>
</Check>
<Check key="StackTrace">
<![CDATA[============================================================================
Queries on the following measures or dimensions failed
(S=Schema, C=Cube, M=Measure, D=Dimension)
"UIT_VERS_ARR" measure query with S=SH1DWH, C=C_PRDARRCAT, M=UIT_VERS_ARR
"UIT_AFSP_POS_ARR" measure query with S=SH1DWH, C=C_PRDARRCAT, M=UIT_AFSP_POS_ARR
"UIT_AFSP_NEG_ARR" measure query with S=SH1DWH, C=C_PRDARRCAT, M=UIT_AFSP_NEG_ARR
"UIT_AFSP_ARR" measure query with S=SH1DWH, C=C_PRDARRCAT, M=UIT_AFSP_ARR
"TFB_BRKD_RM_ARR" measure query with S=SH1DWH, C=C_PRDARRCAT, M=TFB_BRKD_RM_ARR
"TFB_BRKD_OD_ARR" measure query with S=SH1DWH, C=C_PRDARRCAT, M=TFB_BRKD_OD_ARR
"DLT_VERS_DGN_ARR" measure query with S=SH1DWH, C=C_PRDARRCAT, M=DLT_VERS_DGN_ARR
"DLT_AFSP_DGN_POS_ARR" measure query with S=SH1DWH, C=C_PRDARRCAT, M=DLT_AFSP_DGN_POS_ARR
"DLT_AFSP_DGN_NEG_ARR" measure query with S=SH1DWH, C=C_PRDARRCAT, M=DLT_AFSP_DGN_NEG_ARR
"DLT_AFSP_DGN_ARR" measure query with S=SH1DWH, C=C_PRDARRCAT, M=DLT_AFSP_DGN_ARR
"WRK_REAL_ARR" measure query with S=SH1DWH, C=C_PRDARRMEL, M=WRK_REAL_ARR
"UIT_REAL_ARR" measure query with S=SH1DWH, C=C_PRDARRMEL, M=UIT_REAL_ARR
"INS_REAL_ARR" measure query with S=SH1DWH, C=C_PRDARRMEL, M=INS_REAL_ARR
"DLT_REAL_ZKN_ARR" measure query with S=SH1DWH, C=C_PRDARRMEL, M=DLT_REAL_ZKN_ARR
"DLT_REAL_GMD_ARR" measure query with S=SH1DWH, C=C_PRDARRMEL, M=DLT_REAL_GMD_ARR
"DLT_REAL_DGN_ARR" measure query with S=SH1DWH, C=C_PRDARRMEL, M=DLT_REAL_DGN_ARR
"WRK_VERS_ARR" measure query with S=SH1DWH, C=C_PRDARRSUB, M=WRK_VERS_ARR
"WRK_AFSP_POS_ARR" measure query with S=SH1DWH, C=C_PRDARRSUB, M=WRK_AFSP_POS_ARR
"WRK_AFSP_NEG_ARR" measure query with S=SH1DWH, C=C_PRDARRSUB, M=WRK_AFSP_NEG_ARR
"WRK_AFSP_ARR" measure query with S=SH1DWH, C=C_PRDARRSUB, M=WRK_AFSP_ARR
"TFB_VERS_RM_ARR" measure query with S=SH1DWH, C=C_PRDARRSUB, M=TFB_VERS_RM_ARR
"TFB_VERS_OD_ARR" measure query with S=SH1DWH, C=C_PRDARRSUB, M=TFB_VERS_OD_ARR
"TFB_FEIT_RM_ARR" measure query with S=SH1DWH, C=C_PRDARRSUB, M=TFB_FEIT_RM_ARR
"TFB_FEIT_OD_ARR" measure query with S=SH1DWH, C=C_PRDARRSUB, M=TFB_FEIT_OD_ARR
"TFB_BRKD_RM_POS_ARR" measure query with S=SH1DWH, C=C_PRDARRSUB, M=TFB_BRKD_RM_POS_ARR
"TFB_BRKD_RM_NEG_ARR" measure query with S=SH1DWH, C=C_PRDARRSUB, M=TFB_BRKD_RM_NEG_ARR
"TFB_BRKD_OD_POS_ARR" measure query with S=SH1DWH, C=C_PRDARRSUB, M=TFB_BRKD_OD_POS_ARR
"TFB_BRKD_OD_NEG_ARR" measure query with S=SH1DWH, C=C_PRDARRSUB, M=TFB_BRKD_OD_NEG_ARR
"INS_VERS_ARR" measure query with S=SH1DWH, C=C_PRDARRSUB, M=INS_VERS_ARR
"INS_AFSP_POS_ARR" measure query with S=SH1DWH, C=C_PRDARRSUB, M=INS_AFSP_POS_ARR
"INS_AFSP_NEG_ARR" measure query with S=SH1DWH, C=C_PRDARRSUB, M=INS_AFSP_NEG_ARR
"INS_AFSP_ARR" measure query with S=SH1DWH, C=C_PRDARRSUB, M=INS_AFSP_ARR
"TFB_BRKD_RM_SOM" measure query with S=SH1DWH, C=C_PRDKTGCAT, M=TFB_BRKD_RM_SOM
"TFB_BRKD_RM_KTG" measure query with S=SH1DWH, C=C_PRDKTGCAT, M=TFB_BRKD_RM_KTG
"TFB_BRKD_OD_SOM" measure query with S=SH1DWH, C=C_PRDKTGCAT, M=TFB_BRKD_OD_SOM
"TFB_BRKD_OD_KTG" measure query with S=SH1DWH, C=C_PRDKTGCAT, M=TFB_BRKD_OD_KTG
"WRK_REAL_SOM" measure query with S=SH1DWH, C=C_PRDKTGMEL, M=WRK_REAL_SOM
"WRK_REAL_KTG" measure query with S=SH1DWH, C=C_PRDKTGMEL, M=WRK_REAL_KTG
"UIT_REAL_SOM" measure query with S=SH1DWH, C=C_PRDKTGMEL, M=UIT_REAL_SOM
"UIT_REAL_KTG" measure query with S=SH1DWH, C=C_PRDKTGMEL, M=UIT_REAL_KTG
"INS_REAL_SOM" measure query with S=SH1DWH, C=C_PRDKTGMEL, M=INS_REAL_SOM
"INS_REAL_KTG" measure query with S=SH1DWH, C=C_PRDKTGMEL, M=INS_REAL_KTG
"DLT_REAL_ZKN_SOM" measure query with S=SH1DWH, C=C_PRDKTGMEL, M=DLT_REAL_ZKN_SOM
"DLT_REAL_ZKN_KTG" measure query with S=SH1DWH, C=C_PRDKTGMEL, M=DLT_REAL_ZKN_KTG
"DLT_REAL_GMD_SOM" measure query with S=SH1DWH, C=C_PRDKTGMEL, M=DLT_REAL_GMD_SOM
"DLT_REAL_GMD_KTG" measure query with S=SH1DWH, C=C_PRDKTGMEL, M=DLT_REAL_GMD_KTG
"DLT_REAL_DGN_SOM" measure query with S=SH1DWH, C=C_PRDKTGMEL, M=DLT_REAL_DGN_SOM
"DLT_REAL_DGN_KTG" measure query with S=SH1DWH, C=C_PRDKTGMEL, M=DLT_REAL_DGN_KTG
"TIJD" dimension query with S=SH1DWH, D=D_TIME
"FIN_VERS_REAL_BUDG_PR_JTD" measure query with S=SH1DWH, C=C_FINANCIEEL, M=FIN_VERS_REAL_BUDG_PR_JTD
"FIN_VERS_REAL_BUDG_PR" measure query with S=SH1DWH, C=C_FINANCIEEL, M=FIN_VERS_REAL_BUDG_PR
"FIN_VERS_REAL_BUDG_MT_JTD" measure query with S=SH1DWH, C=C_FINANCIEEL, M=FIN_VERS_REAL_BUDG_MT_JTD
"FIN_VERS_REAL_BUDG_MT" measure query with S=SH1DWH, C=C_FINANCIEEL, M=FIN_VERS_REAL_BUDG_MT
"FIN_VERS_BUDG_PROG_PR" measure query with S=SH1DWH, C=C_FINANCIEEL, M=FIN_VERS_BUDG_PROG_PR
"FIN_VERS_BUDG_PROG_MT" measure query with S=SH1DWH, C=C_FINANCIEEL, M=FIN_VERS_BUDG_PROG_MT
"FIN_REAL_PR_JTD" measure query with S=SH1DWH, C=C_FINANCIEEL, M=FIN_REAL_PR_JTD
"FIN_REAL_PR" measure query with S=SH1DWH, C=C_FINANCIEEL, M=FIN_REAL_PR
"FIN_REAL_MT_JTD" measure query with S=SH1DWH, C=C_FINANCIEEL, M=FIN_REAL_MT_JTD
"FIN_REAL_MT" measure query with S=SH1DWH, C=C_FINANCIEEL, M=FIN_REAL_MT
"FIN_PROG_PR_POS" measure query with S=SH1DWH, C=C_FINANCIEEL, M=FIN_PROG_PR_POS
"FIN_PROG_PR_NEG" measure query with S=SH1DWH, C=C_FINANCIEEL, M=FIN_PROG_PR_NEG
"FIN_PROG_PR" measure query with S=SH1DWH, C=C_FINANCIEEL, M=FIN_PROG_PR
"FIN_PROG_MT_POS" measure query with S=SH1DWH, C=C_FINANCIEEL, M=FIN_PROG_MT_POS
"FIN_PROG_MT_NEG" measure query with S=SH1DWH, C=C_FINANCIEEL, M=FIN_PROG_MT_NEG
"FIN_PROG_MT" measure query with S=SH1DWH, C=C_FINANCIEEL, M=FIN_PROG_MT
"FIN_KOST_FEIT_BEZ" measure query with S=SH1DWH, C=C_FINANCIEEL, M=FIN_KOST_FEIT_BEZ
"FIN_JAARBUDGET_PR" measure query with S=SH1DWH, C=C_FINANCIEEL, M=FIN_JAARBUDGET_PR
"FIN_JAARBUDGET_MT" measure query with S=SH1DWH, C=C_FINANCIEEL, M=FIN_JAARBUDGET_MT
"FIN_BUDG_PR_POS_JTD" measure query with S=SH1DWH, C=C_FINANCIEEL, M=FIN_BUDG_PR_POS_JTD
"FIN_BUDG_PR_POS" measure query with S=SH1DWH, C=C_FINANCIEEL, M=FIN_BUDG_PR_POS
"FIN_BUDG_PR_NEG_JTD" measure query with S=SH1DWH, C=C_FINANCIEEL, M=FIN_BUDG_PR_NEG_JTD
"FIN_BUDG_PR_NEG" measure query with S=SH1DWH, C=C_FINANCIEEL, M=FIN_BUDG_PR_NEG
"FIN_BUDG_PR_JTD" measure query with S=SH1DWH, C=C_FINANCIEEL, M=FIN_BUDG_PR_JTD
"FIN_BUDG_PR" measure query with S=SH1DWH, C=C_FINANCIEEL, M=FIN_BUDG_PR
"FIN_BUDG_MT_POS_JTD" measure query with S=SH1DWH, C=C_FINANCIEEL, M=FIN_BUDG_MT_POS_JTD
"FIN_BUDG_MT_POS" measure query with S=SH1DWH, C=C_FINANCIEEL, M=FIN_BUDG_MT_POS
"FIN_BUDG_MT_NEG_JTD" measure query with S=SH1DWH, C=C_FINANCIEEL, M=FIN_BUDG_MT_NEG_JTD
"FIN_BUDG_MT_NEG" measure query with S=SH1DWH, C=C_FINANCIEEL, M=FIN_BUDG_MT_NEG
"FIN_BUDG_MT_JTD" measure query with S=SH1DWH, C=C_FINANCIEEL, M=FIN_BUDG_MT_JTD
"FIN_BUDG_MT" measure query with S=SH1DWH, C=C_FINANCIEEL, M=FIN_BUDG_MT
"KWA_SCORE" measure query with S=SH1DWH, C=C_KWALITEIT, M=KWA_SCORE
"KWA_NORM_POS" measure query with S=SH1DWH, C=C_KWALITEIT, M=KWA_NORM_POS
"KWA_NORM_NEG" measure query with S=SH1DWH, C=C_KWALITEIT, M=KWA_NORM_NEG
"NRM_MINUTEN_RM_RB" measure query with S=SH1DWH, C=C_NORMTIJD, M=NRM_MINUTEN_RM_RB
"NRM_MINUTEN_RM_KTG" measure query with S=SH1DWH, C=C_NORMTIJD, M=NRM_MINUTEN_RM_KTG
"NRM_MINUTEN_OD_RB" measure query with S=SH1DWH, C=C_NORMTIJD, M=NRM_MINUTEN_OD_RB
"NRM_MINUTEN_OD_KTG" measure query with S=SH1DWH, C=C_NORMTIJD, M=NRM_MINUTEN_OD_KTG
"ZKT_REAL_RM_ZWAN" measure query with S=SH1DWH, C=C_PERSONEEL, M=ZKT_REAL_RM_ZWAN
"ZKT_REAL_RM_LANG" measure query with S=SH1DWH, C=C_PERSONEEL, M=ZKT_REAL_RM_LANG
"ZKT_REAL_RM_KORT" measure query with S=SH1DWH, C=C_PERSONEEL, M=ZKT_REAL_RM_KORT
"ZKT_REAL_OD_ZWAN" measure query with S=SH1DWH, C=C_PERSONEEL, M=ZKT_REAL_OD_ZWAN
"ZKT_REAL_OD_LANG" measure query with S=SH1DWH, C=C_PERSONEEL, M=ZKT_REAL_OD_LANG
"ZKT_REAL_OD_KORT" measure query with S=SH1DWH, C=C_PERSONEEL, M=ZKT_REAL_OD_KORT
"ZKT_PCT_RM_ZWAN" measure query with S=SH1DWH, C=C_PERSONEEL, M=ZKT_PCT_RM_ZWAN
"ZKT_PCT_RM_LANG" measure query with S=SH1DWH, C=C_PERSONEEL, M=ZKT_PCT_RM_LANG
"ZKT_PCT_RM_KORT" measure query with S=SH1DWH, C=C_PERSONEEL, M=ZKT_PCT_RM_KORT
"ZKT_PCT_OD_ZWAN" measure query with S=SH1DWH, C=C_PERSONEEL, M=ZKT_PCT_OD_ZWAN
"ZKT_PCT_OD_LANG" measure query with S=SH1DWH, C=C_PERSONEEL, M=ZKT_PCT_OD_LANG
"ZKT_PCT_OD_KORT" measure query with S=SH1DWH, C=C_PERSONEEL, M=ZKT_PCT_OD_KORT
"ZKT_AFSP_TOTL" measure query with S=SH1DWH, C=C_PERSONEEL, M=ZKT_AFSP_TOTL
"ZKT_AFSP_RM_ZWAN_POS" measure query with S=SH1DWH, C=C_PERSONEEL, M=ZKT_AFSP_RM_ZWAN_POS
"ZKT_AFSP_RM_ZWAN_NEG" measure query with S=SH1DWH, C=C_PERSONEEL, M=ZKT_AFSP_RM_ZWAN_NEG
"ZKT_AFSP_RM_LANG_POS" measure query with S=SH1DWH, C=C_PERSONEEL, M=ZKT_AFSP_RM_LANG_POS
"ZKT_AFSP_RM_LANG_NEG" measure query with S=SH1DWH, C=C_PERSONEEL, M=ZKT_AFSP_RM_LANG_NEG
"ZKT_AFSP_RM_KORT_POS" measure query with S=SH1DWH, C=C_PERSONEEL, M=ZKT_AFSP_RM_KORT_POS
"ZKT_AFSP_RM_KORT_NEG" measure query with S=SH1DWH, C=C_PERSONEEL, M=ZKT_AFSP_RM_KORT_NEG
"ZKT_AFSP_PCT_RM_ZWAN_POS" measure query with S=SH1DWH, C=C_PERSONEEL, M=ZKT_AFSP_PCT_RM_ZWAN_POS
"ZKT_AFSP_PCT_RM_ZWAN_NEG" measure query with S=SH1DWH, C=C_PERSONEEL, M=ZKT_AFSP_PCT_RM_ZWAN_NEG
"ZKT_AFSP_PCT_RM_LANG_POS" measure query with S=SH1DWH, C=C_PERSONEEL, M=ZKT_AFSP_PCT_RM_LANG_POS
"ZKT_AFSP_PCT_RM_LANG_NEG" measure query with S=SH1DWH, C=C_PERSONEEL, M=ZKT_AFSP_PCT_RM_LANG_NEG
"ZKT_AFSP_PCT_RM_KORT_POS" measure query with S=SH1DWH, C=C_PERSONEEL, M=ZKT_AFSP_PCT_RM_KORT_POS
"ZKT_AFSP_PCT_RM_KORT_NEG" measure query with S=SH1DWH, C=C_PERSONEEL, M=ZKT_AFSP_PCT_RM_KORT_NEG
"ZKT_AFSP_PCT_OD_ZWAN_POS" measure query with S=SH1DWH, C=C_PERSONEEL, M=ZKT_AFSP_PCT_OD_ZWAN_POS
"ZKT_AFSP_PCT_OD_ZWAN_NEG" measure query with S=SH1DWH, C=C_PERSONEEL, M=ZKT_AFSP_PCT_OD_ZWAN_NEG
"ZKT_AFSP_PCT_OD_LANG_POS" measure query with S=SH1DWH, C=C_PERSONEEL, M=ZKT_AFSP_PCT_OD_LANG_POS
"ZKT_AFSP_PCT_OD_LANG_NEG" measure query with S=SH1DWH, C=C_PERSONEEL, M=ZKT_AFSP_PCT_OD_LANG_NEG
"ZKT_AFSP_PCT_OD_KORT_POS" measure query with S=SH1DWH, C=C_PERSONEEL, M=ZKT_AFSP_PCT_OD_KORT_POS
"ZKT_AFSP_PCT_OD_KORT_NEG" measure query with S=SH1DWH, C=C_PERSONEEL, M=ZKT_AFSP_PCT_OD_KORT_NEG
"ZKT_AFSP_OD_ZWAN_POS" measure query with S=SH1DWH, C=C_PERSONEEL, M=ZKT_AFSP_OD_ZWAN_POS
"ZKT_AFSP_OD_ZWAN_NEG" measure query with S=SH1DWH, C=C_PERSONEEL, M=ZKT_AFSP_OD_ZWAN_NEG
"ZKT_AFSP_OD_LANG_POS" measure query with S=SH1DWH, C=C_PERSONEEL, M=ZKT_AFSP_OD_LANG_POS
"ZKT_AFSP_OD_LANG_NEG" measure query with S=SH1DWH, C=C_PERSONEEL, M=ZKT_AFSP_OD_LANG_NEG
"ZKT_AFSP_OD_KORT_POS" measure query with S=SH1DWH, C=C_PERSONEEL, M=ZKT_AFSP_OD_KORT_POS
"ZKT_AFSP_OD_KORT_NEG" measure query with S=SH1DWH, C=C_PERSONEEL, M=ZKT_AFSP_OD_KORT_NEG
"TFB_POS_RM" measure query with S=SH1DWH, C=C_PERSONEEL, M=TFB_POS_RM
"TFB_POS_OD" measure query with S=SH1DWH, C=C_PERSONEEL, M=TFB_POS_OD
"TFB_NEG_RM" measure query with S=SH1DWH, C=C_PERSONEEL, M=TFB_NEG_RM
"TFB_NEG_OD" measure query with S=SH1DWH, C=C_PERSONEEL, M=TFB_NEG_OD
"FTE_RM" measure query with S=SH1DWH, C=C_PERSONEEL, M=FTE_RM
"FTE_OD" measure query with S=SH1DWH, C=C_PERSONEEL, M=FTE_OD
"SCD_SCORE" measure query with S=SH1DWH, C=C_SCORECARD, M=SCD_SCORE
============================================================================
Exception stacktrace for "UIT_VERS_ARR" measure query with S=SH1DWH, C=C_PRDARRCAT, M=UIT_VERS_ARR
============================================================================
1) BIB-9509 Oracle OLAP heeft cursor niet gemaakt.
oracle.express.ExpressServerExceptionError class: OLAPI
Server error descriptions:
DPR: Unable to create server cursor, Generic at TxsOqDefinitionManagerSince9202::crtCurMgrs2
OES: ORA-12801: error signaled in parallel query server P007
ORA-00910: specified length too long for its datatype
, Generic at TxsRdbSelectStatement:execute()
2) null
1) BIB-9509 Oracle OLAP heeft cursor niet gemaakt.
oracle.express.ExpressServerExceptionError class: OLAPI
Server error descriptions:
DPR: Unable to create server cursor, Generic at TxsOqDefinitionManagerSince9202::crtCurMgrs2
OES: ORA-12801: error signaled in parallel query server P007
ORA-00910: specified length too long for its datatype
, Generic at TxsRdbSelectStatement:execute()
============================================================================
oracle.dss.dataSource.common.OLAPException: BIB-9509 Oracle OLAP heeft cursor niet gemaakt.
oracle.express.ExpressServerExceptionError class: OLAPI
Server error descriptions:
DPR: Unable to create server cursor, Generic at TxsOqDefinitionManagerSince9202::crtCurMgrs2
OES: ORA-12801: error signaled in parallel query server P007
ORA-00910: specified length too long for its datatype
, Generic at TxsRdbSelectStatement:execute()
oracle.express.ExpressServerExceptionError class: OLAPI
Server error descriptions:
DPR: Unable to create server cursor, Generic at TxsOqDefinitionManagerSince9202::crtCurMgrs2
OES: ORA-12801: error signaled in parallel query server P007
ORA-00910: specified length too long for its datatype
, Generic at TxsRdbSelectStatement:execute()
at oracle.dss.dataSource.QueryEvaluator.setUpCursors(QueryEvaluator.java:3645)
at oracle.dss.dataSource.QueryEvaluator._setUpCursorsForMainQuery(QueryEvaluator.java:2547)
at oracle.dss.dataSource.QueryEvaluator.getCursorForCube(QueryEvaluator.java:2579)
at oracle.dss.dataSource.QueryEvaluator.createCubeAndCursor(QueryEvaluator.java:940)
at oracle.dss.dataSource.MainQueryEvaluator.createCubeAndCursor(MainQueryEvaluator.java:144)
at oracle.dss.dataSource.QueryServer.createCubeAndCursor(QueryServer.java:3698)
at oracle.dss.dataSource.QueryServer._createCommonQuery(QueryServer.java:3681)
at oracle.dss.dataSource.QueryServer._initCubeQuery(QueryServer.java:3561)
at sun.reflect.GeneratedMethodAccessor84.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at oracle.dss.util.Operation.execute(Operation.java:72)
at oracle.dss.dataSource.OperationQueue.update(OperationQueue.java:68)
at oracle.dss.dataSource.common.BaseOperationQueue.addOperation(BaseOperationQueue.java:176)
at oracle.dss.dataSource.common.BaseOperationQueue.addOperation(BaseOperationQueue.java:146)
at oracle.dss.dataSource.QueryServer.queueOperation(QueryServer.java:6966)
at oracle.dss.dataSource.QueryServer.initCubeQuery(QueryServer.java:3511)
at sun.reflect.GeneratedMethodAccessor83.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at oracle.dss.util.Operation.execute(Operation.java:72)
at oracle.dss.dataSource.QueryManagerServer.sendQueue(QueryManagerServer.java:1991)
at oracle.dss.dataSource.common.OperationQueue.update(OperationQueue.java:207)
at oracle.dss.dataSource.common.BaseOperationQueue.addOperation(BaseOperationQueue.java:176)
at oracle.dss.dataSource.common.BaseOperationQueue.addOperation(BaseOperationQueue.java:146)
at oracle.dss.dataSource.client.QueryClient._initCubeQuery(QueryClient.java:2335)
at oracle.dss.dataSource.client.QueryClient.initCubeQuery(QueryClient.java:2318)
at oracle.dss.datautil.client.BICheckConfig.runDefaultMeasureQuery(BICheckConfig.java:500)
at oracle.dss.datautil.client.BICheckConfig.printFolder(BICheckConfig.java:426)
at oracle.dss.datautil.client.BICheckConfig.printFolder(BICheckConfig.java:485)
at oracle.dss.d4o.common.D4OCheckConfig.checkConnection(Unknown Source)
at oracle.dss.d4o.common.D4OCheckConfig.checkConnection(Unknown Source)
at oracle.dss.d4o.gui.common.DiagnoseDialog$ConfigTask.construct(Unknown Source)
at oracle.dss.d4o.gui.common.SwingWorker$4.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
2)
============================================================================
oracle.express.ExpressServerExceptionError class: OLAPI
Server error descriptions:
DPR: Unable to create server cursor, Generic at TxsOqDefinitionManagerSince9202::crtCurMgrs2
OES: ORA-12801: error signaled in parallel query server P007
ORA-00910: specified length too long for its datatype
, Generic at TxsRdbSelectStatement:execute()
at oracle.express.olapi.data.full.DefinitionManager$ExceptionTranslator.translateExpressException(DefinitionManager.java:571)
at oracle.express.olapi.data.full.DefinitionManager$ExceptionTranslator.translateException(DefinitionManager.java:551)
at oracle.express.olapi.data.full.DefinitionManager.translateException(DefinitionManager.java:515)
at oracle.express.olapi.data.full.DefinitionManager.translateException(DefinitionManager.java:520)
at oracle.express.olapi.data.full.DefinitionManagerSince9202.createCursorManagerInterfaces(DefinitionManagerSince9202.java:522)
at oracle.express.olapi.data.full.DefinitionManagerSince9202.createOLAPICursorManagers(DefinitionManagerSince9202.java:891)
at oracle.express.olapi.data.full.ExpressDataProvider.createCursorManagers(ExpressDataProvider.java:1671)
at oracle.express.olapi.data.full.ExpressDataProvider.createCursorManagers(ExpressDataProvider.java:1544)
at oracle.dss.dataSource.SplitBatchPageQueryCursorManager.createCursorManager(SplitBatchPageQueryCursorManager.java:77)
at oracle.dss.dataSource.QueryEvaluator.setUpCursors(QueryEvaluator.java:3546)
at oracle.dss.dataSource.QueryEvaluator._setUpCursorsForMainQuery(QueryEvaluator.java:2547)
at oracle.dss.dataSource.QueryEvaluator.getCursorForCube(QueryEvaluator.java:2579)
at oracle.dss.dataSource.QueryEvaluator.createCubeAndCursor(QueryEvaluator.java:940)
at oracle.dss.dataSource.MainQueryEvaluator.createCubeAndCursor(MainQueryEvaluator.java:144)
at oracle.dss.dataSource.QueryServer.createCubeAndCursor(QueryServer.java:3698)
at oracle.dss.dataSource.QueryServer._createCommonQuery(QueryServer.java:3681)
at oracle.dss.dataSource.QueryServer._initCubeQuery(QueryServer.java:3561)
at sun.reflect.GeneratedMethodAccessor84.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at oracle.dss.util.Operation.execute(Operation.java:72)
at oracle.dss.dataSource.OperationQueue.update(OperationQueue.java:68)
at oracle.dss.dataSource.common.BaseOperationQueue.addOperation(BaseOperationQueue.java:176)
at oracle.dss.dataSource.common.BaseOperationQueue.addOperation(BaseOperationQueue.java:146)
at oracle.dss.dataSource.QueryServer.queueOperation(QueryServer.java:6966)
at oracle.dss.dataSource.QueryServer.initCubeQuery(QueryServer.java:3511)
at sun.reflect.GeneratedMethodAccessor83.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at oracle.dss.util.Operation.execute(Operation.java:72)
at oracle.dss.dataSource.QueryManagerServer.sendQueue(QueryManagerServer.java:1991)
at oracle.dss.dataSource.common.OperationQueue.update(OperationQueue.java:207)
at oracle.dss.dataSource.common.BaseOperationQueue.addOperation(BaseOperationQueue.java:176)
at oracle.dss.dataSource.common.BaseOperationQueue.addOperation(BaseOperationQueue.java:146)
at oracle.dss.dataSource.client.QueryClient._initCubeQuery(QueryClient.java:2335)
at oracle.dss.dataSource.client.QueryClient.initCubeQuery(QueryClient.java:2318)
at oracle.dss.datautil.client.BICheckConfig.runDefaultMeasureQuery(BICheckConfig.java:500)
at oracle.dss.datautil.client.BICheckConfig.printFolder(BICheckConfig.java:426)
at oracle.dss.datautil.client.BICheckConfig.printFolder(BICheckConfig.java:485)
at oracle.dss.d4o.common.D4OCheckConfig.checkConnection(Unknown Source)
at oracle.dss.d4o.common.D4OCheckConfig.checkConnection(Unknown Source)
at oracle.dss.d4o.gui.common.DiagnoseDialog$ConfigTask.construct(Unknown Source)
at oracle.dss.d4o.gui.common.SwingWorker$4.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Exception stacktrace for "UIT_AFSP_POS_ARR" measure query with S=SH1DWH, C=C_PRDARRCAT, M=UIT_AFSP_POS_ARR
============================================================================
1) BIB-9509 Oracle OLAP heeft cursor niet gemaakt.
oracle.express.ExpressServerExceptionError class: OLAPI
Server error descriptions:
DPR: Unable to create server cursor, Generic at TxsOqDefinitionManagerSince9202::crtCurMgrs2
OES: ORA-12801: error signaled in parallel query server P009
ORA-00910: specified length too long for its datatype
, Generic at TxsRdbSelectStatement:execute()
2) null
1) BIB-9509 Oracle OLAP heeft cursor niet gemaakt.
oracle.express.ExpressServerExceptionError class: OLAPI
Server error descriptions:
DPR: Unable to create server cursor, Generic at TxsOqDefinitionManagerSince9202::crtCurMgrs2
OES: ORA-12801: error signaled in parallel query server P009
ORA-00910: specified length too long for its datatype
, Generic at TxsRdbSelectStatement:execute()
============================================================================
oracle.dss.dataSource.common.OLAPException: BIB-9509 Oracle OLAP heeft cursor niet gemaakt.
oracle.express.ExpressServerExceptionError class: OLAPI
Server error descriptions:
DPR: Unable to create server cursor, Generic at TxsOqDefinitionManagerSince9202::crtCurMgrs2anybody knows what this can mean. Espacially the testquerie results like:
-DPR: Unable to create server cursor, Generic at TxsOqDefinitionManagerSince9202::crtCurMgrs2
-oracle.dss.dataSource.common.OLAPException: BIB-9509 Oracle OLAP heeft cursor niet gemaakt.
-Exception stacktrace for "UIT_AFSP_POS_ARR" measure query with S=SH1DWH, C=C_PRDARRCAT, M=UIT_AFSP_POS_ARR
In Dicoverer we can connect tot the measures in the AW but the query created by Oracle Discoverer fails.A couple of questions:
Did you create any cubes and measure in your database?
Did you install the BIBDEMO demo schema that comes with BI Beans, and did it work? -
BIB-9509 OLAPI error viewing cubes data
Hi, I'm using 11.1.0.7 Oracle Server and AWM 11.1.0.7.0B. Last week I created a cube, mantained it and I could view all the data. Today when I try to view the cube data I get this error:
An error has occurred on the server
Error class: OLAPI
Server error descriptions:
DPR: Unable to create server cursor, Generic at TxsOqDefinitionManager::crtCurMgrs4
OES: ORA-00600: internal error code, arguments: xscbTest, 18446744073709551615], [, ], [, ], [, ], [, ], [, []
, Generic at TxsRdbSQLQuery::absolute()
at oracle.dss.dataSource.QueryEvaluator.setUpCursors(QueryEvaluator.java:3979)
at oracle.dss.dataSource.QueryEvaluator._setUpCursorsForMainQuery(QueryEvaluator.java:2822)
at oracle.dss.dataSource.QueryEvaluator.getCursorForCube(QueryEvaluator.java:2854)
at oracle.dss.dataSource.QueryEvaluator.createCubeAndCursor(QueryEvaluator.java:1234)
at oracle.dss.dataSource.MainQueryEvaluator.createCubeAndCursor(MainQueryEvaluator.java:171)
at oracle.dss.dataSource.QueryServer.createCubeAndCursor(QueryServer.java:3863)
at oracle.dss.dataSource.QueryServer._createCommonQuery(QueryServer.java:3822)
at oracle.dss.dataSource.QueryServer._initCubeQuery(QueryServer.java:3702)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at oracle.dss.util.Operation.execute(Operation.java:72)
at oracle.dss.dataSource.OperationQueue.update(OperationQueue.java:68)
at oracle.dss.dataSource.common.BaseOperationQueue.addOperation(BaseOperationQueue.java:176)
at oracle.dss.dataSource.common.BaseOperationQueue.addOperation(BaseOperationQueue.java:146)
at oracle.dss.dataSource.QueryServer.queueOperation(QueryServer.java:7079)
at oracle.dss.dataSource.QueryServer.initCubeQuery(QueryServer.java:3652)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at oracle.dss.util.Operation.execute(Operation.java:72)
at oracle.dss.dataSource.QueryManagerServer.sendQueue(QueryManagerServer.java:2001)
at oracle.dss.dataSource.common.OperationQueue.update(OperationQueue.java:207)
at oracle.dss.dataSource.common.BaseOperationQueue.addOperation(BaseOperationQueue.java:176)
at oracle.dss.dataSource.common.BaseOperationQueue.addOperation(BaseOperationQueue.java:146)
at oracle.dss.dataSource.client.QueryClient._initCubeQuery(QueryClient.java:2385)
at oracle.dss.dataSource.client.QueryClient.initCubeQuery(QueryClient.java:2368)
at oracle.olap.awm.dataobject.dialog.olapi.UBiBeanUtil.doQueryTop3(Unknown Source)
at oracle.olap.awm.dataobject.dialog.olapi.UBiBeanUtil.showCrosstab(Unknown Source)
at oracle.olap.awm.dataobject.dialog.olapi.UBiBeanUtil.showData(Unknown Source)
at oracle.olap.awm.navigator.node.olapi.UCubeNode.actionPerformed(Unknown Source)
at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source)
at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
at javax.swing.AbstractButton.doClick(Unknown Source)
at javax.swing.plaf.basic.BasicMenuItemUI.doClick(Unknown Source)
at javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(Unknown Source)
at java.awt.Component.processMouseEvent(Unknown Source)
at javax.swing.JComponent.processMouseEvent(Unknown Source)
at java.awt.Component.processEvent(Unknown Source)
at java.awt.Container.processEvent(Unknown Source)
at java.awt.Component.dispatchEventImpl(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Window.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)
anyone can help me??It is clearly a database bug. It could be related to
Bug 7329946 - ORA-600 [XSCBTEST] WHEN TRYING TO VIEW CUBE DATA WITH AWM DATA VIEWER
The AWM data viewer uses the BI Beans code, so it is probably the same thing. It is related to
Bug 8719947 - CC CRASHES WHEN THERE IS NEGATIVE VALUES IN CCINCR TUPLES
My advice is to raise a service request so that you can supply proper trace file information and can get a patch for your specific platform.
For a faster response to OLAP server related problems you could post to the OLAP Forum
OLAP -
BIB-9009 Oracle OLAP could not create cursor.
Hi,
I am working on OLAP catalog. I created one cube and 6 Dim. And OEM Console mgs showing this as valid CUbe. When I m trying to create Presentation after selecting my Measure it gives this error:-
oracle.dss.dataSource.common.QueryRuntimeException: BIB-9009 Oracle OLAP could not create cursor.
oracle.express.ExpressServerExceptionError class: OLAPI
Server error descriptions:
DPR: Unable to execute the query, Generic at TxsOqCursorManager::fetchInitialBlocks
SEL: Unexpected error occurred. Contact Oracle Support!, Generic at null
java.lang.CloneNotSupportedException: BIB-9009 Oracle OLAP could not create cursor.
oracle.express.ExpressServerExceptionError class: OLAPI
Server error descriptions:
DPR: Unable to execute the query, Generic at TxsOqCursorManager::fetchInitialBlocks
SEL: Unexpected error occurred. Contact Oracle Support!, Generic at null
void oracle.dss.dataSource.common.QueryDataDirector.addDataDirectorListener(oracle.dss.util.DataDirectorListener)
QueryDataDirector.java:687
void oracle.dss.dataView.ModelAdapter.setDataDirector(oracle.dss.util.DataDirector)
ModelAdapter.java:145
void oracle.dss.crosstab.CrosstabModelAdapter.setDataSource(oracle.dss.util.DataSource)
CrosstabModelAdapter.java:49
void oracle.dss.dataView.Dataview.setDataSource(oracle.dss.util.DataSource)
Dataview.java:386
void oracle.dss.addins.wizard.presentation.PresentationWizardState.applyQuery()
PresentationWizardState.java:106
void oracle.dss.addins.wizard.presentation.PresentationWizardDialog.wizardFinished(oracle.bali.ewt.wizard.WizardEvent)
It is little urgent.
JDev version is 9.0.3.3 (Build 1205)
Business Comp Version 9.0.3.11.50
OS Win 2000 Proff
DOwn Loaded BIBean9032 and bibeans90321 patchI suspect your metadata is incomplete. Please refer to the bi_checkconfig utility to test your metadata. This can be found on the documentation section of the BI Beans section of OTN:
Displaying Information about your BI Beans Client Configuration using the bi_checkconfig utility
http://www.oracle.com/technology/products/bib/htdocs/904/tech_notes/bicheckconfig/bi_checkconfig_tn.html
This will allow you to test the structures in your metadata to ensure each object (dimension, cube) can in fact be queried.
Hope this helps
Business Intelligence Beans Product Management Team
Oracle Corporation
Maybe you are looking for
-
Error in creating leave request
Hi , I am new to HR and i am working on Leave management. When i am trying to crate a leave request workflow, i am getting the below error msg: 'Absence type 100 was not found in Customizing for 21.10.2010' What could be the reason?\ Thanks, Krish.
-
I have a button where i need to call one event from another... does anyone have any ideas on what the syntax would be? public class PushButton extends Button public PushButton() * Mouse Pressed Event this.addEventHandler(MouseEvent.MOUSE_PRESSED, new
-
[BUG] Photoshop CC crashed immediately after selecting NVIDIA GeForce GTX 680M GPU
I just started using Photoshop CC trial and I immediately ran into problem with my video card. First Photoshop doesn't recognized my GPU which is Nvidia GTX 680M. I'm using a new Alienware R4 with Win8 pro, I then searched the forum and followed this
-
I'm trying to figure out what this Network Preferences option is useful for: "Disconnect when logging out". Any ideas?
-
i recently downloaded hundreds of midis, many of them had names that didin't have relevance to the song or artist. So- i changed names on the files. When i dumped tham all into iTunes, many of these names were ignored by iTunes. So- i changed them in