OLAP Bridge NullPointerException
I'm getting the following exception trying to run the OLAP Bridge from the Oracle by example series (http://www.oracle.com/technology/obe/obe_bi/index.html) ...
begin
cwm_olap_dim_attribute.Create_Dimension_Attribute(USER, 'T_TIME', 'Long_Description', 'Long_Description', 'Full Description');
select descriptor_id into id from all_olap_descriptors where descriptor_value='Long Description';
cwm_classify.add_entity_descriptor_use(id, cwm_utility.DIMENSION_ATTRIBUTE_TYPE,USER,
BRD-02501: Internal Error: Bridge run failed due to a system exception! Please contact Oracle Support with the stack trace and the details on how to reproduce it.
java.lang.NullPointerException
at java.io.Writer.write(Writer.java:126)
at oracle.cwm.bridge.cwmlite.ImportCommon.trace(ImportCommon.java:51)
at oracle.cwm.bridge.cwmlite.ImportUtil.traceOut(ImportUtil.java:648)
at oracle.cwm.bridge.cwmlite.ImportUtil.runPLSQL(ImportUtil.java:628)
at oracle.cwm.bridge.cwmlite.ImportMain.runBridge(ImportMain.java:151)
at oracle.cwm.tools.bridge.BridgeWrapper.run(BridgeWrapper.java:509)
at java.lang.Thread.run(Thread.java:534)Any ideas?
For OLAP on 10g you might need the patch 10.1.0.3.0A. See the note 286770.1 on metalink.oracle.com for installation.
Regards:
Igor
Similar Messages
-
I have recently began trying to use the OLAP bridge to transfer data from OWB to be used by BI Beans applications (ROLAP, not MOLAP/AW). I have set up the bridge to run, but I always get the following error on my first dimension. Am I missing a step?
BRD-05030: Error occurred while executing the PL/SQL file, see log file for details.
ORA-06501: PL/SQL: program error
ORA-06512: at line 361
ORA-06510: PL/SQL: unhandled user-defined exception
ORA-06512: at "OLAPSYS.CWM$OLAP$DIMENSION", line 242
ORA-06510: PL/SQL: unhandled user-defined exception
ORA-06512: at "OLAPSYS.CWM$UTIL", line 367
ORA-01403: no data found
ERROR:: dimension_not_found
Object Type: DIMENSION
Object Owner: OLAPSYS
Object Name: COMPLAINT_DIM
Secondary Name:
Tertiary Name:
User-Defined Exception
BRD-05030: Error occurred while executing the PL/SQL file, see log file for details.
disconnecting ...
closing output file
closing log stream
**! Transfer logging stopped at Wed Jun 30 12:53:33 EDT 2004 !**
THANKS TO ANYONE WHO HELPS!!!Mark,
The error indicates that the dimensions have not been deployed to the database prior to running of the OLAP bridge. You must deploy dependent dimensions using OWB Deployment Manager first.
For future reference, there is a "Troubleshooting OWB OLAP Integration" document on Metalink:
http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=260948.1
Nikolai Rochnik -
OLAP Bridge not generate View Definitions
Hi
I try to get scripts for generating AW but
Oracle 9i OLAP Bridge generate neither View Definitions
nor Materialized Views.
OWB Client 9.2.0.2.8
OWB Repository 9.2.0.2.0
WinXP Prof SP1a
parameter file:
log_level=1
log_file=C:\TEMP\bridges\log\null-nullMy_Metadata_Transfer1076068690437.log
olapimp.deploytoaw=Y
olapimp.awname=AW_BP
olapimp.awobjprefix=
olapimp.loadcubedata=N
olapimp.dimuniquekeys=N
olapimp.awuser=
olapimp.createviews=Y
olapimp.viewprefix=
olapimp.viewaccesstype=OLAP
olapimp.creatematviews=Y
olapimp.viewscriptdir=E:\AW
olapimp.deploy=N
olapimp.username=
olapimp.password=
olapimp.host=
olapimp.port=1521
olapimp.sid=
olapimp.inputfilename=C:\TEMP\bridges\null-nullMy_Metadata_Transfer1076068690437.XMI
olapimp.outputfilename=D:\AW\BP\BP
Thanks in advanceFrom the parameter file, i notice a few parameters like awobjprefix and viewprefix are not set and needed to be. These prefix are set by using the OLAP bridge wizard. Go back and rerun the OLAP bridge wizard and be sure to answer all the questions.
-
I keep getting the following error message when I try to create the AW, OLAP export file.
**! Transfer logging started at Tue Sep 28 15:58:19 CDT 2004 !**
OWB Bridge processed arguments
**! Transfer logging stopped at Tue Sep 28 15:58:33 CDT 2004 !**
Am I doing the export right? We want to take advantage of OWB and the OLAP feature. I'm using OWB 10g.From the log you mention it is difficult to understand what is the problem. Are you getting some additional error messages? And, most importantly ... what version of OWB/DB are you using?
Regards:
Igor -
OWB 9.2.0.4
Oracle 9.2.0.4
I have ran the metadata bridge several time and had to fix a few errors that the troubleshooting guide helped with, but now I am receiving this and am not sure what to do.
BRD-05030: Error occurred while executing the PL/SQL file, see log file for details.
ORA-06501: PL/SQL: program error
ORA-06512: at line 71
ORA-06510: PL/SQL: unhandled user-defined exception
ORA-06512: at "OLAPSYS.DBMS_AWM_PRV", line 672
ORA-01403: no data found
AMD-00100 not found: Dimension "ALCDEV.ALC_DIM_COMPANY_ORGANIZATION"
AMD-00101 cannot create Dimension "ALCDEV.ALC_DIM_COMPANY_ORGANIZATION"; metadata entity already exists
AMD-00100 not found: AWDimLoad "ALC_DIM_COMPANY_ORGANIZATION.ALCDEV.ALC_DIM_COMPANY_ORGANIZATION"
BRD-05030: Error occurred while executing the PL/SQL file, see log file for details.
disconnecting ...
closing output file
closing log stream
Thank you for any help that can be provided.From the messages it seems that it is trying to overwrite an already existing object (dimension). What parameters did you use when running the bridge? Did you provide the prefix?
Also, please provide the OWB and DB versions.
Regards:
Igor -
Metadata export bridge to OLAP problem
I have a collection consisting of 2 dimensions and 1 cube.
We are using:
OWB Client 10.1.0.4
OWB Repository 10.1.0.4
DB Version
Oracle9i Enterprise Edition Release 9.2.0.7.0 - Production
Parameters in bridge
OWB Exported Collections: SALES
OWB translated language: American English
Deploy to AW: YES
AW NAME: BI
AW Object Prefix: BI
Aggregate Data in AW: Partial, every other level
Load Cube Data: Yes
Generate Surrogate keys: No
Generate View definitions: Yes
Generate Materialized Views: No
Generate view Directory: c:\temp
Deploy PL/SQL in database -Yes (If it is No, I don't get an error)
Username Password Hostname Port Service- All provided
PL/SQL Output file - Provided
Log level - Information
I get the following error when running the bridge to 9i OLAP:
BRD-05030: Error occurred while executing the PL/SQL file, see log file for details.
ORA-06501: PL/SQL: program error
ORA-06512: at line 27
ORA-06510: PL/SQL: unhandled user-defined exception
AMD-00100 not found: Dimension "WH_DATA_MARTS.BICUSTOMER"
BRD-05030: Error occurred while executing the PL/SQL file, see log file for details.
disconnecting ...
closing output file
closing log stream
**! Transfer logging stopped at Wed Aug 30 17:42:42 PDT 2006 !**
The dimension CUSTOMER is deployed and is part of the collection. I tried it without specifiying the AW Object Prefix, but I still get the same error.
Any ideas? This problem has been bugging for a few days.Take a look at the troubleshooting doc on MetaLink for the OWB OLAP Bridge, however it is intended for version 9.0.4-9.2. You may want to upgrade OWB. More importantly, be sure to be running RDBMS 9.2.0.4 with the OLAP 9.2.0.4.1 patch (PS# 3084634).
Troubleshooting OWB OLAP Integration
http://metalink.oracle.com/metalink/plsql/showdoc?db=NOT&id=260948.1 -
Hi,
I have questions regarding the OWB 9.0.4 and his OLAP features. I tried to set up an Analytical Workspace
and OLAP objects (dimensions and a cube) as it was written in the OWB904UsersGuide. Therefore I created
an PL/SQL script with the OWB Export Wizard. The script created the OLAP objects but I also got some errors,
that several Identifiers need to be declared. Well, I thought it worked fine, cause when I checked the OLAP
directory node in the OEM, I found my cube and dimensions there. But when I tried to load the OLAP objects
with the WB_OLAP_LOAD_DIMENSION and WB_OLAP_LOAD_CUBE transformations from OWB I got the error that my dimensions are invalid, even if the OEM shows them as valid.
I read several articles in the OWB and the OLAP forum about this issue and I'm a bit confused now. Does the OWB now support OLAP at all, and when will the post 9.2.0.3 patch be released?
Is there an other way to convert the relational OWB starschema into an OLAP schema and to load it with data?
Can I use BI Beans on the relational starschema without an working OLAP schema?
Thanks in advance,
DirkWhich version of the database is being used? The AW work involves a patch that has not yet been released. The OLAP 9.2.0.3 patch is due to be released in July, the exact
release date is unknown.
OWB provides the bridge which will populate the metadata for a relational OLAP cube in the OLAP catalog. BI Beans can be used on this relational cube. The bridge also supports cloning of this relational cube in an OLAP analytic workspace, both the metadata for the AW and the data loading programs are generated from the bridge. The OWB 9.0.4.10 patch has a number of improvements and bug fixes that will help deploying to OLAP. The OLAP 9.2.0.3 patch is due to be released in July, the exact
release date is unknown.
The OLAP metadata for ROLAP cubes can either be created using OWB, or through OEM or manually. If by OLAP schema
you mean an AW, then either use OWB to clone the ROLAP cube in an AW, or use the Analytic Workspace Manager
(AWM) that will clone the ROLAP cube and provide some more options or manually code up the OLAP DML metadata etc. Manual coding of the AW is a specialized task that involves substantial knowledge of OLAP DML (the Express SPL language) to write both the data object definitions and performant data loader programs, also the enabling of the AW through SQL for BI Beans is a complex task. All of these manual tasks are provided by both the OWB OLAP bridge and the AWM.
For BI Beans, the ROLAP metadata must be populated in the OLAP catalog, so can be achieved using OWB to deploy the
relational star schema then the OWB OLAP bridge to populate only the ROLAP metadata. OWB does this using CWM1 apis. BI Beans can be used on top of the ROLAP cube. -
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? -
Export metadata from OWB to OLAP
Hi there,
I have OWB 9.2.0.3, DB release 2.
I'm having some trouble with the metadata export, i have created my mappings with the appropriate configuration to olap aw.
When I run the Metadata Export - Bridge , I get the following message:
**! Transfer logging started at Sat Jan 31 13:09:57 CST 2004 !**
OWB Bridge processed arguments
**! Transfer logging stopped at Sat Jan 31 13:09:58 CST 2004 !**
But nothing happens.
Any idea? Do I need to configure or install something in the server? I already have the olapsys.
Any help would be appreciated, thanks in advance.
Xochitl.Take a look at the troubleshooting doc on MetaLink for the OWB OLAP Bridge, however it is intended for version 9.0.4-9.2. You may want to upgrade OWB. More importantly, be sure to be running RDBMS 9.2.0.4 with the OLAP 9.2.0.4.1 patch (PS# 3084634).
Troubleshooting OWB OLAP Integration
http://metalink.oracle.com/metalink/plsql/showdoc?db=NOT&id=260948.1 -
OWB Patch 10.1.0.4 is available in Metalink
Hi,
Patch 10.1.0.4 is available in Metalink.
Cheers
DetlefThe patch number is 4703215, a hefty 528M (for Windows).
From the documentation:
7.2 Bugs Fixed in 10.1.0.4
4110189 NO COMMIT BACKPORTING TO 10.1.0.X (BOMBAY)
3994801 OMB PLUS PL/SQL SCRIPT CONTAINS MORE AS 2499 CHARACTERS / SP2-0027
4350443 ''NO OCIJDBC10 IN JAVA.LIBRARY.PATH'' ERROR WHEN STARTING RAB IN LINUX
4187143 DWPRD: OWB - CANNOT START IT AFTER ORACLE_HOME CHANGE FOR DATABASE
4633954 BACKPORT BUG 3286037 FIX TO 10.1.0.4 VERSION ON SOLARIS 32 BIT PLATFORM
4609436 BLR BACKPORT OF BUG 3870981 ON TOP OF VERSION 10.1.0.3
3820028 VERY SLOW GENERATION OF PROCESS FLOW PACKAGE WITH 150+ PROCESS FLOWS
3882583 PROBLEM WITH EXTERNAL TABLE
4088890 RPE-02083 WHEN PURGING AUDIT INFORMATION WHILE WORKFLOW PROCESS IS RUNNING
4183568 UPGRADE DEPLOYMENT MGR SCRIPT DOES NOT INCLUDE THE TBS NAME
4373822 SLOW LOGON & NAVIGATION OF LARGE REPOSITORY DUE TO SQL FTS
4428430 RECOVERY SHOULD BE OPTIONAL
3997600 UNABLE TO SET DEPLOYABLE PROPETY OF FOREIGN KEY OF CUBE WITH OMBPLUS
3994878 RUNTIME AUDIT BROWSER PERFORMANCE
4425752 IMPORTING THE MDL FILE GETTING THE ERROR API0407 AT 10%
4393188 FORWARD PORT 4183568
4393182 FORWARD PORT 4106056 TO 10.1.0.4
4144163 PROCESS FLOW PACKAGE VALIDATION HANGS IN OWB 10G
4340763 RUNTIME SERVICE LOG FILE CANNOT BE DELETED WHEN SERVICE IS RUNNING
4106056 PARALLEL EXECUTION OF PROCESS FLOWS FAILS WITH RPE-01003
3836845 UNABLE TO DEPLOY PUBLIC TRANSFORMATION
3829240 DBG1034 AND ORA-00904 WHEN DEBUGGING MAPPING WITH MS-SQLSERVER SOURCE
3773182 OBJECT STATUS UNCERTAIN AFTER SUCCESFULL DEPLOYMENT
4551773 FORWARD PORT OF BUG 3997600
4488992 [7/11]ERROR API8532 VALIDATING EXPRESSION API-8532
4542250 OLAP BRIDGE FAILING ON 10G WITH BRD-02501
4537766 OWB10G BOMBAY DOES NOT INSTALL ON 10G RELEASE 2 DATABASE
4497246 ORA-06502: PL/SQL: NUMERIC OR VALUE ERROR: CHARACTER STRING BUFFER TOO SMALL
4407615 EXPLICIT GARBAGE COLLECTION CAN CAUSE PERFORMANCE PROBLEMS
3165476 UNABLE TO USE DATES BEFORE 1-1-1950; IMPLICIT CONVERSION
4159683 OWB DOES NOT IMPORT SQL QUERY WHILE IMPORTING VIEW DEFINITIONS
3952986 UPGRADING MULTIPLE TABLES FROM UI GIVES DEPLOYMENT FAILURE AS RETURN
3989847 GENERATED CODE HAS INVALID ALIASES AFTER UPGRADE FROM 9.0.3 TO 9.2.0.4
4232118 WBSECURITYSERVICEIMPL SECURITY HOLE
4212170 MAPPING GENERATES INCORRECT TARGET CODE/DATA WHEN SPLITTER INCLUDED
4308848 SLOW PERFORMANCES WHILE LOGIN TO DESIGN REPOSITORY
4311885 PROCESSFLOW FAILS; ORA-20002 3133 ACTIVITY INSTANCE X IS NOT A NOTIFIED ACTIVITY
4543947 UPGRADE OPTION DURING DEPLOYING DIMENSIONS/CUBES IS NOT WORKING CORRECTLY
3872199 JAVA.LANG.NULLPOINTEREXCEPTION WHEN CREATING MODULE WITH LOCAL SET TO TURKISH
4530332 REPOSITORY ASSISTANTS HANG ON STARTUP ON WINDOWS 2000 SP4 - PENTIUM IV XEON
4397564 EXECUTION DELAY WHEN EXECUTING ACTIVITIES DURING HIGH CONCURRENCY
4644829 PURGE TEMPLATE AND SUPPORTING PACKAGES NOT CONSISTENT
4120422 AFTER APPLING SECURITY PATCHSET 68 (3875927), PROCESS FLOWS NO LONGER FUNCTION
4078382 INSTALLING OWB 10G RUNTIME REPO ON AIX 5.2 WITH 8.1.7.4 RDBMS IS NOT POSSIBLE
4260822 ALL_IV_OBJECT_PROPERTIES VIEW NOT SHOWING VALUES
3943759 OMBEXPORT FAILS WITH: TOO MANY NESTED CALLS TO EVAL (INFINITE LOOP?)
3150520 NLS: MONTH DISPLAY AS UPSIDE DOWN OF ? FOR CHINESE CHINA
3826870 MDL FROM OWB 9.0.3 WILL NOT IMPORT
4169687 ENH: REQUEST FOR OPTION TO DISABLE AUDITING COMPLETELY
4402849 NO_ROWS ERROR DURING EXECUTION ON RAC
4213253 PUBLIC VIEWS UNAVAILABLE: ALL_IV_IMPACT_DEPENDENTS AND ALL_IV_LINEAGE_DEPENDENTS -
How do i show descriptions instead of dimension values at presentations ?
We are facing a problem that could be a BIBeans problem or could be an OLAP problem, please inform if to change forum:
We are using jdev 903/BIB903 accessing an AW created at Oracle OLAP 9205 with AWM.
All our dimensions were created at OWB 10g and deployed to RDBMS following the general rules below:
DIM X
ID_X - sequence primary key
CD_X - original key from source systems
DS_X, NM_X, and so on - description fields and hierarchy fields related to this record.
i.e.:
SQL> desc dim_rota
Name Null? Type
ID_ROTA NOT NULL NUMBER(6)
CD_EMPRESA NOT NULL NUMBER(2)
CD_FILIAL NOT NULL NUMBER(2)
CD_ROTA NOT NULL VARCHAR2(3)
NM_FILIAL NOT NULL VARCHAR2(40)
NM_ROTA NOT NULL VARCHAR2(30)
CD_SETOR NOT NULL VARCHAR2(1)
ID_SETOR NOT NULL NUMBER(6)
NM_SETOR NOT NULL VARCHAR2(30)
this dimension has 1 hierarchy with 2 levels called SETOR and ROTA.
when we generated the AW using AWM, each field (except ID) is created as a variable dimensioned by DIM_ROTA, as shown below:
->listby dim_rota
35 objects dimensioned by or related to DIM_ROTA in analytic workspace AW1
DIM_ROTA_CD_EMPRESA
DIM_ROTA_CD_FILIAL
DIM_ROTA_CD_ROTA
DIM_ROTA_CD_SETOR
DIM_ROTA_CREATEDBY
DIM_ROTA_FAMILYREL
DIM_ROTA_GID
DIM_ROTA_INHIER
DIM_ROTA_LEVELCOLMAP
DIM_ROTA_LEVELREL
DIM_ROTA_NM_FILIAL
DIM_ROTA_NM_ROTA
DIM_ROTA_NM_SETOR
DIM_ROTA_ORDER
DIM_ROTA_PARENTREL
ID field was concatenated with level name to generate the dimension value - so, for the following relational record:
SQL> select id_rota, cd_rota, nm_rota from dim_rota where ID_ROTA = 233;
ID_ROTA CD_ROTA NM_ROTA
233 A99 A99-Consig. Sup. Setor A
we have at multidimensional side:
->LIMIT DIM_ROTA TO 'ROTA.233'
->rpr dim_rota
DIM_ROTA
ROTA.233
->dsc dim_rota_nm_rota
DEFINE DIM_ROTA_NM_ROTA VARIABLE TEXT <DIM_ROTA DIM_ROTA_HIERLIST ALL_LANGUAGES>
LD IMPLEMENTATION NM_ROTA Attribute for DIM_ROTA Dimension
->rpr down dim_rota w 30 dim_rota_nm_rota
ALL_LANGUAGES: AMERICAN_AMERICA
-------DIM_ROTA_NM_ROTA-------
------DIM_ROTA_HIERLIST-------
DIM_ROTA ROTA
ROTA.233 A99-Consig. Sup. Setor A
here comes our question: how do we show at BIBeans designer/presentations the related descriptive fields and NOT the dimension values themselves?
thanks in advance,
FlavioThere a re two additional attributes that need to be mapped within OWB for each dimension:
Long Description - this is used by the presentation beans and query and calc builder to replace the dimension values with more meaningful/end-user friendly descriptions
Short Descriptions - this can be used where the long description is too long for display purposes. In BI Beans 10g Release 2 (due out soon) you will be able to select between long/short descriptions when using many of the new tags.
These new attributes will be automatically picked up by the OLAP Bridge in OWB and automatically added to the OLAP catalog.
Hope this helps
Business Intelligence Beans Product Management Team
Oracle Corporation -
How do i show descriptions instead of dimensions at BIBeans ?
We are facing a problem that could be a BIBeans problem or could be an OLAP problem, please inform if to change forum:
We are using jdev 903/BIB903 accessing an AW created at Oracle OLAP 9205 with AWM.
All our dimensions were created at OWB 10g and deployed to RDBMS following the general rules below:
DIM X
ID_X - sequence primary key
CD_X - original key from source systems
DS_X, NM_X, and so on - description fields and hierarchy fields related to this record.
i.e.:
SQL> desc dim_rota
Name Null? Type
ID_ROTA NOT NULL NUMBER(6)
CD_EMPRESA NOT NULL NUMBER(2)
CD_FILIAL NOT NULL NUMBER(2)
CD_ROTA NOT NULL VARCHAR2(3)
NM_FILIAL NOT NULL VARCHAR2(40)
NM_ROTA NOT NULL VARCHAR2(30)
CD_SETOR NOT NULL VARCHAR2(1)
ID_SETOR NOT NULL NUMBER(6)
NM_SETOR NOT NULL VARCHAR2(30)
this dimension has 1 hierarchy with 2 levels called SETOR and ROTA.
when we generated the AW using AWM, each field (except ID) is created as a variable dimensioned by DIM_ROTA, as shown below:
->listby dim_rota
35 objects dimensioned by or related to DIM_ROTA in analytic workspace AW1
DIM_ROTA_CD_EMPRESA
DIM_ROTA_CD_FILIAL
DIM_ROTA_CD_ROTA
DIM_ROTA_CD_SETOR
DIM_ROTA_CREATEDBY
DIM_ROTA_FAMILYREL
DIM_ROTA_GID
DIM_ROTA_INHIER
DIM_ROTA_LEVELCOLMAP
DIM_ROTA_LEVELREL
DIM_ROTA_NM_FILIAL
DIM_ROTA_NM_ROTA
DIM_ROTA_NM_SETOR
DIM_ROTA_ORDER
DIM_ROTA_PARENTREL
ID field was concatenated with level name to generate the dimension value - so, for the following relational record:
SQL> select id_rota, cd_rota, nm_rota from dim_rota where ID_ROTA = 233;
ID_ROTA CD_ROTA NM_ROTA
233 A99 A99-Consig. Sup. Setor A
we have at multidimensional side:
->LIMIT DIM_ROTA TO 'ROTA.233'
->rpr dim_rota
DIM_ROTA
ROTA.233
->dsc dim_rota_nm_rota
DEFINE DIM_ROTA_NM_ROTA VARIABLE TEXT <DIM_ROTA DIM_ROTA_HIERLIST ALL_LANGUAGES>
LD IMPLEMENTATION NM_ROTA Attribute for DIM_ROTA Dimension
->rpr down dim_rota w 30 dim_rota_nm_rota
ALL_LANGUAGES: AMERICAN_AMERICA
-------DIM_ROTA_NM_ROTA-------
------DIM_ROTA_HIERLIST-------
DIM_ROTA ROTA
ROTA.233 A99-Consig. Sup. Setor A
here comes our question: how do we show at BIBeans designer/presentations the related descriptive fields and NOT the dimension values themselves?
thanks in advance,
FlavioThere a re two additional attributes that need to be mapped within OWB for each dimension:
Long Description - this is used by the presentation beans and query and calc builder to replace the dimension values with more meaningful/end-user friendly descriptions
Short Descriptions - this can be used where the long description is too long for display purposes. In BI Beans 10g Release 2 (due out soon) you will be able to select between long/short descriptions when using many of the new tags.
These new attributes will be automatically picked up by the OLAP Bridge in OWB and automatically added to the OLAP catalog.
Hope this helps
Business Intelligence Beans Product Management Team
Oracle Corporation -
Why cann't i see the cube that i create with owb ??
hello:
owb version:10.1.0.4
db version:10.2.1.0.1
Business Intelligence 10.1.2.0.2
windows 2003
i use owb create 3 dimensions and 1 cube,and deploy on target schema successfully.
and export the metadata to eex file, and import eex file into discoverer administrator ,when create workbook i can see the cube created with owb;
then i selected ORACLE BI DISCOVERER option to connect target_schema,so i can see my cube and dimension;
but when i selected ORACLE BI DISCOVERER FOR OLAP option to connect target_schema, login in successful , but when i create my workbook ,cann't see my cube and demension
why for this,and how to do it,so i can see them?
pls help me!There are three ways to deploy a multi-dimensional model and the final model selection depends on the database options you have purchased and they tools you have at your displosal:
relational access - You can define relational cubes and dimensions within OWB and deploy these to your target schema. The dimensions are implemented as query re-write objects and can be viewed within the view USER_DIMENSIONS. The data relating to the dimension is stored within a simple relational table, either as a snowflake or star schema format. The cube object does not really exist as such but is implemented as fact table. Typically, access to this type of implementation is via Discoverer and you need to create a Discoverer EUL to view the deployed tables. Within Discoverer you will not see the dimension or cubes listed but you will see tables and/or views relating to your deployed schema.
The Discoverer Bridge will create the eex/EUL file to install the schema within Discoverer Administrator. However, you must use Discoverer Plus/Viewer with the relational connection details.
As an FYI the management of Discoverer EULs is integrated within OWB 10gR2.
OLAP models - OWB also supports the deployment a schema as either a relational OLAP model or within an analytic workspace (this creates a MOLAP model). The OLAP deployment can be viewed only using Discoverer OLAP, however, management of the schema does not require an EUL and the administration is managed by Discoverer Administrator. All the administration is managed by OWB. To access a multi-dimensional model using Discoverer OLAP you must first run the OLAP bridge from within OWB. This will deploy all the required metadata for Discoverer OLAP to connect to your schema.
However, I would recommend you urgently upgrade to OWB10gR2 as this provides additional tuning options for the OLAP data model that are not present in your current version of OWB 10.1.0.4. Unfortunately, with your current OWB version building an OLAP model is a two stage process, a form of data staging. You need to create a relational target schema first and then replicate that target schema within an OLAP model. OWB10gR2 allows you to map data from a source object directly to a multi-dimensional object with no need to stage the data.
If you cannot upgrade at this point my suggestion would be to use OWB to design the target relational schema and then use Analytic Workspace Manager (AWM) to design your OLAP schema for Discoverer OLAP access. AWM will provide you with all the tools for tuning and managing your OLAP model within a 10gR2 database schema.
Once you have upgraded to OWB10gR2 you can stop using AWM as all the tuning features are within OWB.
Hope this makes sense and is helpful.
Keith -
Creating Database Standard Form Analytic Workspaces
Just been looking through the new 9.2.0.4.1 documentation and came across the following. Thought it might be useful.
The 9.2.0.4.1 release of Oracle OLAP introduces a new concept known as �Database Standard Form� Analytic Workspaces. This is a way of constructing analytic workspaces in a standard way such that they can be used by tools such as the Analytic Workspace Manager, the Java OLAP API, and BI Beans.
When analytic workspaces are created from a relational star-schema using the Analytic Workspace Manager, it automatically creates the analytic workspace in standard form as part of the migration process. However, if you�re migrating an Express database to Oracle OLAP, the migrated database has to be processed to be in standard form before it is usable by any of the new Oracle OLAP GUI tools.
If you create an analytic workspace using PL/SQL or the OLAP Worksheet, of course you can create dimensions, variables, relations and so on in any form, just as you can create table structures, joins, views and columns in any form in a relational database. However, the database standard form requirement stipulates that;
Certain objects and properties need to be found in the analytic workspace, that are used by tools such as the Analytic Workspace Manager to perform tasks such as aggregation, data loads, and OLAP API enablement. OLAP DML views (beginning with AW$) need to created in the analytic workspace, to provide metadata and to identify relationships between objects in the analytic workspace. Objects need to be registered in the OLAP Catalog, and these registrations have to be kept in sync so that the OLAP tools are aware of changes to the base objects. Data that is migrated in to an analytic workspace, from a relational star-schema using the Analytic Workspace Manager, is already in database standard form and no further work is needed. However, some work is needed to get migrated Express databases into standard form, and Oracle have provided a utility with the 9.2.0.4.1 release of Oracle OLAP to help accomplish this.
This utility, known as CREATE_DB_STDFORM, is an OLAP DML program that takes existing Oracle Express Objects metadata in a migrated Express database, and uses this to create the additional metadata required to make the analytic workspace �database standard form�.
Once CREATE_DB_STDFORM has been used to create this additional metadata, it can also be used to import data into the workspace either from flat files, or from Oracle tables and views. If you don�t have Express Objects metadata in the Express database, CREATE_DB_STDFORM doesn�t work, and you�ll have to use Oracle Warehouse Builder 9.2 to initially create a relational star-schema that equates to the Express database, then use the OLAP Bridge within OWB to export the data into a database standard form analytic workspace.
CREATE_DB_STDFORM, once run, allows the migrated Express database to be accessed via BI Beans straight afterwards, as it creates all the OLAP Catalog entries required for the OLAP API. If the Express database only contains data at the lowest level (i.e. it hasn�t been rolled up), aggregation wizards in the Analytic Workspace Manager can be used to summarise the data as required.
CREATE_DB_STDFORM doesn�t do everything, however. First of all, you need to have created Oracle Express Objects metadata within the Express database, which is an additional step and not always appropriate for all systems. In addition, you need to create time dimensions in a particular way, which may require the data model to be adjusted to meet this requirement. Lastly, any Express language programs within the Express database may need to be adjusted to remove or change commands that have changed or become obsolete.
The new document, �Oracle OLAP Application Developers Guide Release 9.2.0.4.1�, available on metalink under note 251352.1, details how database standard form works, has code examples, and walks through the migration of the XADEMO Express database to an analytic workspace using database standard form.In your message, you wrote "Certain objects and properties need to be found ... aware of changes to base objects". A large bit is represented by "...". Question is whether I have any commands or package functions that I can use to set up all the proper objects and relationships to make it have database standard form, short of regressing to a ROLAP star schema and usnig the AWM wizard. I have what appears to be working MOLAP activity, all created at the OLAP worksheet prompt, and loaded with DML program. Do I really have to put that all aside and start with a star schema? No way to put my AW in standard form for OLAP API without this?
-
Dimension tables versus dimension Objects
Hi,
We are trying to model a Data Warehouse and I am a little confused about the way the word dimension is used to describe a table and also an object in Oracle.
Our situation is that we will be pulling data from the source system into a staging area made up of materialised views. We thought we would then build dimension tables and fact tables as per Ralph Kimball's definition, but we stumbled across the 'CREATE DIMENSION' command in Oracle that seems to contain so much more than just columns.
Could someone clarify this for me?
Thanks,
MikeYou create dimensions in Oracle just like in any other rdbms using create table statement.
The create dimension statement is optional and is used to optimize certain queries (query rewrite, star transform etc - you can find more about it in oracle warehouse docs).
If you create a dimension using the OEM wizard then create dimension statements are executed as well. In addition, if OLAP option is installed then statements from an OLAP PL/SQL package are executed as well. These statements are only of importance if you plan to use the OLAP feature. Unfortunately, you have only one shot to capture these statements - there is no way to re-create them after the dimension is created. There is no equivalent of 'Show DDL' option available for 'regular' tables. For this reason, OEM is problematic as a tool in designing dimensions: You can tweak them to your heart's content but then when the time comes to deploy them somewhere else - you are stuck. OWB is a little better: it has 'Show DDL' option but that displays only the CREATE DIMENSION statements and not the OLAP package statements. You can get the latter by exporting OWB model to an OLAP bridge however the OWB model does not contain all that is required for OLAP so you end-up with generated defaults.
Maybe you are looking for
-
I have other members of my family use my iPad for educational/recreational use, young children who may want to play kid games. I don't want them to accdently get into my data stored in the three business apps from apple. I would like to password prot
-
Connecting to a shared printer on a local network
I want to connect my iBook G4 to my Dell Windows computer to utilize a shared printer on the Dell. We currently use a local area network. What do I have to do to my iBook to use this printer. Should the printers we are trying to connect to appear on
-
Finding newest file in given directory
I have a program that needs to automatically take data from a text file made earlier. There are several text files in a certain directory, and i need the program to take the newest file. The text files are labeled as so: mm-dd-yyyy-time.txt ex: 12-21
-
Weblogic 6 Post Installation Problem - weblogic.Server not found
I reinstalled my recent downloads of the evaluation copy of Weblogic 6.0 server three times on my NT 4.0 Service pack 6 notebook computer. Installation works. However, I can't start the server using the "startWebLogic.cmd". I get an error that says t
-
Hi Gurus, while i run MRBR report i am getting the list of invoices with error message "The list of blocked invoices is incomplete." What will be exact problem with report , and how we can rectify the same . If some one come across this kind of isssu