OLAP API 10G Source objects - drilling

I have a block of code that works in 11G to set a point in a dimension and then lists its children
StringSource top = (StringSource) mdmDim.getSource();
Source topp = top.selectValue("TOTAL_CHAMPION_HIER::TOTAL_CHAMPION::62404");
//Source foo = dim.join(hier.getSource());
Source foo = hier.getSource().selectDescendants(topp,hier.getParentAttribute().getSource());
// Create a Cursor for the query.
Source bar = foo.join(foo,mdmDim.getValueDescriptionAttribute().getSource());
But when i port this code over to 10G, it compiles just fine and the docs make it look like all the calls do the same thing, but no i am getting a mismatched dimension when i create the cursor, it says my Dim is unmatched and i think that is because my topp Source is coming out with no data.
Any clues?

AH replying to my own thread, tacky
Here is the gist of what i want to do in 10G through the API.
I have a short key ie "Y2005" instead of "CALENDAR::YEAR::Y2005",
i have the MdmHierarchy and MdmDimension and i want to produce a Source objetc that will tell me the children of "Y2005" in my MdmHierarchy, which is a MdmLevelHierarchy. And returning the shortdescription would be nice. That is what i am trying to do above.

Similar Messages

  • 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,
    Seiji

    The 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.

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

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

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

  • Error: Derivation Source object, DIMENSION_NAME , is not correctly bound

    Hi,
    I have installed Oracle Database 10g Enterprise Edition Release 10.2.0.1.0
    and OWB 10.2.0.1.0 on Windows XP Professional.
    I've created a simple MOLAP dimension with a default hierarchy and one level within it.
    I've maped it to source table, deployed and loaded it. I can see its data.
    Description of dimension:
    Configuration
    Deployable: yes
    Deployment options: Deploy to Catalog only
    Storage
    MOLAP
    Generate surrogate keys in the analytic workspace
    Attributes
    NAME::IDENTIFIER::DATA TYPE::LENGTH
    ID::NULL::VARCHAR2::25
    CODE::Business::VARCHAR2::32
    NAME::NULL::VARCHAR2:255
    Problem:
    When I trying to derive definitions I receive an error in wizard: Derivation Source object, <DIMENSION_NAME>, is not correctly bound.
    As result, there are no business definitions there.
    This problem goes with all my MOLAP dimensions.
    Please, maybe somebody faced with this trouble...

    Hi,
    Are you trying to Derive this into the Business Defintions area? In that case, this is not supported. For MOLAP objects you can use Discoverer and use an OLAP connection, then you will see your dimensions as query objects.
    Derive only works for relational objects (e.g. ROLAP storage), and that is why you get that error (not bound) as the MOLAP object is not bound to a table.
    Jean-Pierre

  • Unable to select OLAP API metadata

    I am using oracle rdbms 9.2.0.5
    Initially I was able to view BIBDEMO schema cubes using cubeviewer. I also created my own cubes using CWM2 API and was able to view through the bibeans. All of sudden it stopped working and I am currently unable to even view the demo cubes in BIBDEMO schema using cube viewer, it throws a "red bell with no error message" dialog.
    I validated the entire OLAP catalog using the CWM2 API, all the objects are valid.
    I do not have a time dimension and any AW cubes.
    The bi_checkconfig utility returned the following results.
    <?xml version="1.0" encoding="UTF-8" ?>
    <BICheckConfig version="1.0.0.0">
    <Check key="JDEV_ORACLE_HOME" value="d:\Program Files\JDev_903"/>
    <Check key="JAVA_HOME" value="D:\JDK\1.3.1_11"/>
    <Check key="JDeveloper version" value="9.0.3.4.1247"/>
    <Check key="BI Beans version" value="9.0.3.6.0A"/>
    <Check key="BI Beans internal version" value="2.7.0.14"/>
    <Check key="host" value="199.254.233.44"/>
    <Check key="port" value="1521"/>
    <Check key="sid" value="config3"/>
    <Check key="user" value="kaisernw"/>
    <Check key="Connecting to the database" value="Successful"/>
    <Check key="JDBC driver version" value="9.2.0.3.0"/>
    <Check key="JDBC JAR file location" value="d:\Program Files\JDev_903\jdbc\lib"/>
    <Check key="Database version" value="9.2.0.5.0"/>
    <Check key="OLAP Catalog version" value="9.2.0.5.0"/>
    <Check key="OLAP AW Engine version" value="9.2.0.5.0"/>
    <Check key="OLAP API Server version" value="9.2.0.5.0"/>
    <Check key="BI Beans Catalog version" value="N/A; not installed in kaisernw"/>
    <Check key="OLAP API JAR file version" value="9.2"/>
    <Check key="OLAP API JAR file location" value="d:\Program Files\JDev_903\jdev\lib\ext"/>
    <Check key="OLAP API Metadata Load" value="Unsuccessful"/>
    <Check key="Failure Point" value="MDMLoadFailed"/>
    <Check key="StackTrace">
    <![CDATA[
    ============================================================================
    1) An error occurred during olap API metadata retrieval. This is probably caused by inconsistent metadata.
    1) An error occurred during olap API metadata retrieval. This is probably caused by inconsistent metadata.
    ============================================================================
    oracle.express.ExpressServerExceptionError class: Unknown Error
    Server error descriptions:
    INI: System failure, Generic at TxsOqConnection::getDefaultDatabase
         void oracle.olapi.metadata.BaseMetadataProvider.<init>(oracle.olapi.data.source.DataProvider)
              BaseMetadataProvider.java:68
         void oracle.olapi.metadata.mdm.MdmMetadataProvider.<init>(oracle.olapi.data.source.DataProvider)
              MdmMetadataProvider.java:127
         oracle.olapi.metadata.MetadataProvider oracle.express.olapi.data.full.ExpressDataProvider.getDefaultMetadataProvider()
              ExpressDataProvider.java:912
         oracle.express.mdm.MdmMetadataProvider oracle.dss.metadataManager.server.drivers.mdm._92.MDMMetadataDriverImpl_92.getMdmMetadataProvider()
              MDMMetadataDriverImpl_92.java:1134
         oracle.dss.metadataUtil.PropertyBag oracle.dss.metadataManager.server.drivers.mdm._92.MDMMetadataDriverImpl_92.attach(oracle.dss.metadataUtil.PropertyBag)
              MDMMetadataDriverImpl_92.java:811
         oracle.dss.metadataUtil.PropertyBag oracle.dss.metadataManager.server.drivers.mdm.MDMMetadataDriverImpl.attach(oracle.dss.metadataUtil.PropertyBag)
              MDMMetadataDriverImpl.java:133
         void oracle.dss.metadataManager.server.MetadataManagerImpl.buildObjectModel()
              MetadataManagerImpl.java:1085
         oracle.dss.metadataManager.common.MDRoot oracle.dss.metadataManager.server.MetadataManagerImpl.attach(oracle.dss.metadataManager.common.MDRoot, oracle.dss.metadataUtil.PropertyBag)
              MetadataManagerImpl.java:962
         int oracle.dss.metadataManager.client.MetadataManager.attach(oracle.dss.metadataUtil.PropertyBag)
              MetadataManager.java:866
         int oracle.dss.metadataManager.client.MetadataManager.attach()
              MetadataManager.java:792
         oracle.dss.metadataUtil.OrderedHashtable BICheckConfig.checkConnection(java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.io.OutputStream, boolean)
              BICheckConfig.java:250
         void BICheckConfig.main(java.lang.String[])
              BICheckConfig.java:1172
    ]]>
    </Check>
    </BICheckConfig>
    How can I debug this issue.
    Thank you,
    Senthil

    I figured what the problem is, I missed one of the invalid objects in my OLAP validation log file when I scanned before.
    As part of another issue (Issue #1), I dropped and recreated some dimensions. But did not reattach those dimensions to the cube. So in the log, that particular cube was marked as invalid with the error "no dimensions".
    FYI - (Issue #1)
    When creating dimensions, by mistake I mapped some of the fields using CWM2 map table API to a VIEW. The CWM2 validation API, validated these dimensions and marked them as valid.
    But from the query builder I was not able to progress forward from the layout panel to the dimension panel, it will just sit there without throwing any errors. Once I changed the view to the base table in the dimension definition, the querybuilder started working.
    Thank you,
    Senthil

  • Data access through the OLAP API

    We have created a number of Cubes from the AWM, and access the cubes from a web based application through the OLAP API. The cubes have both base measures and custom measures. Custom Measures are computed by creating the source object for given Formula Expression. The application works fine for a single user, but when a same cube is accessed concurrently by multiple users, we get the TransactionalObjectInvalidException when we call the MdmMeasure.getSource() function for the custom measures.
    Since each individual users have individual contexts and the static methods are properly sunchronized, we havent not been able to trace this error so far. The exception is thrown by oracle.olapi.data.source.ImmutableDefinition.checkValidity() API method. Error Trace is:
    oracle.olapi.transaction.TransactionalObjectInvalidException
    at oracle.olapi.data.source.ImmutableDefinition.checkValidity(Loracle.olapi.transaction.Transaction;)V(ImmutableDefinition.java:40)
    at oracle.olapi.data.source.SourceDefinition.getCurrentTransaction()Loracle.olapi.transaction.Transaction;(SourceDefinition.java:206)
    at oracle.olapi.data.source.SourceDefinition.getSource()Loracle.olapi.data.source.Source;(SourceDefinition.java:320)
    at oracle.olapi.metadata.mdm.MdmSource.getSource()Loracle.olapi.data.source.Source;(MdmSource.java:141)
    Any help will be highly appreciated.
    --Saajan                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

    We have created a number of Cubes from the AWM, and access the cubes from a web based application through the OLAP API. The cubes have both base measures and custom measures. Custom Measures are computed by creating the source object for given Formula Expression. The application works fine for a single user, but when a same cube is accessed concurrently by multiple users, we get the TransactionalObjectInvalidException when we call the MdmMeasure.getSource() function for the custom measures.
    Since each individual users have individual contexts and the static methods are properly sunchronized, we havent not been able to trace this error so far. The exception is thrown by oracle.olapi.data.source.ImmutableDefinition.checkValidity() API method. Error Trace is:
    oracle.olapi.transaction.TransactionalObjectInvalidException
    at oracle.olapi.data.source.ImmutableDefinition.checkValidity(Loracle.olapi.transaction.Transaction;)V(ImmutableDefinition.java:40)
    at oracle.olapi.data.source.SourceDefinition.getCurrentTransaction()Loracle.olapi.transaction.Transaction;(SourceDefinition.java:206)
    at oracle.olapi.data.source.SourceDefinition.getSource()Loracle.olapi.data.source.Source;(SourceDefinition.java:320)
    at oracle.olapi.metadata.mdm.MdmSource.getSource()Loracle.olapi.data.source.Source;(MdmSource.java:141)
    Any help will be highly appreciated.
    --Saajan                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

  • UnmatchedInputsException in 9i OLAP API

    Hi All
    I'm using 9206 OLAP API now. Everything was working fine(I can't get all dimension value) but I have getted this exception when querying cube data:
    oracle.olapi.data.source.UnmatchedInputsException
    At the following program:
    private void getMeasureData(MdmMeasure mdmMeasure)
    System.out.println("===========getMeasureData(Source source)");
    TransactionProvider tp = dp.getTransactionProvider();
    StringSource timeSource = (StringSource)timesDim.getSource();
    Source timeSel = timeSource.selectValue("1997");
    Source source = mdmMeasure.getSource();
    source = source.join(timeSel);
    try
    tp.prepareCurrentTransaction();
    catch (NotCommittableException e)
    e.printStackTrace();
    System.out.println("Caught exception " + e + ".");
    tp.commitCurrentTransaction();
    CursorManagerSpecification cursorMngrSpec = dp.createCursorManagerSpecification(source);
    SpecifiedCursorManager cursorMngr = dp.createCursorManager(cursorMngrSpec); ////// Here occurred exception/////
    Cursor cursor = cursorMngr.createCursor();
    ValueCursor values = (ValueCursor) cursor;
    values.setPosition(1);
    String value = values.getCurrentString();
    System.out.println("time value:" + value);
    cursorMngr.close();
    Can anyone can shared your experience to me or let me know what the problem is...
    Thks!

    correct:
    I can get all dimension values!
    With the same exception in my 10g program that I tyied.
    Help me pleeeeezzzzzzzzzzz!
    Where are u, Sharon?

  • Difference between BI Beans and olap api

    HI
    is there anyone can tell me the difference between
    BI and olap api ,
    is BI a language or components ,why
    when i build crosstab with BI beans it uses classes
    different from olap pi classes (oracle.dss.*)
    and olap api (oracle.express.*)
    so BI is another language independent of olap api
    or it uses olap api to connect to OLAP
    BI works , OLAP api doesn't work
    thanks

    Hi,
    This is a great question. The OLAP API is an Oracle published Java API for access to Oracle OLAP. This exposes the OLAP cube/dimension model via Java. The OLAP API documentation can be found on the OLAP secion of OTN, see the link on the BI Beans section of OTN. Within the documention section there is a link to the acle9i OLAP Release 2 - Developer's Guide to the OLAP API:
    http://otn.oracle.com/products/bi/pdf/OLAPIguide.pdf
    Customers can write their own Java code directly against this public API to display and manage OLAP objects. The OLAP API documentation explains how to do this.
    As users typically will want to present OLAP data in either a crosstab and/or graph Oracle created a pre-packaged set of components to help customers to quickly and easily create powerful OLAP applications. BI Beans are a set of fully J2EE compliant java beans that provide major components such as:
    - presentation beans (graph/crosstab/table)
    - OLAP beans
    - catalog services beans
    These components have extensive APIs to allow developers to comprehensively customize an application, both Java client and thin client (HTML/JSP and UIX).
    By default BI Beans connect to an Oracle database using the OLAP API as a primary data source (although users can create their own non-OLAP data sources). This allows developers and end-users to directly access dimensions and measures created to the OLAP specification.
    This is explained in more detail in the Oracle BI Beans Technical Whitepaper:
    http://otn.oracle.com/products/bib/htdocs/collateral/bi_beans_white_paper.pdf
    Hope this helps
    Business Intelligence Beans Product Management Team
    Oracle Corporation

  • Error getting schema root with OLAP API

    I am getting the following error:
    java.sql.SQLException: Io exception: Connection reset by peer: JVM_recv in socket input stream read
         void oracle.jdbc.dbaccess.DBError.throwSqlException(java.lang.String, java.lang.String, int)
         void oracle.jdbc.dbaccess.DBError.throwSqlException(int, java.lang.Object)
         void oracle.jdbc.dbaccess.DBError.throwSqlException(java.io.IOException)
         void oracle.jdbc.driver.OracleStatement.executeNonQuery(boolean)
         void oracle.jdbc.driver.OracleStatement.doExecuteOther(boolean)
         void oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout()
         int oracle.jdbc.driver.OraclePreparedStatement.executeUpdate()
         boolean oracle.jdbc.driver.OraclePreparedStatement.execute()
         oracle.express.idl.ExpressMdmModule.MetadataPropertyBagUnion[] oracle.express.idl.ExpressMdmModule.MetadataProviderInterfaceStub.getMetadataPropertyBags(java.lang.String[])
         oracle.express.mdm.MetadataPropertyBag[] oracle.express.mdm.MetadataPropertyBagFetcher.fetchMetadataPropertyBags(java.lang.String[])
         oracle.express.mdm.MdmObject oracle.express.mdm.MdmMetadataProvider.getMetadataObject(java.lang.String)
         oracle.express.mdm.MdmSchema oracle.express.mdm.MdmMetadataProvider.getRootSchema()
         void mypackage3.olaptest.<init>()
         void mypackage3.olaptest.main(java.lang.String[])
    java.lang.NullPointerException
         oracle.express.mdm.MetadataPropertyBag[] oracle.express.mdm.MetadataPropertyBagFetcher.fetchMetadataPropertyBags(java.lang.String[])
         oracle.express.mdm.MdmObject oracle.express.mdm.MdmMetadataProvider.getMetadataObject(java.lang.String)
         oracle.express.mdm.MdmSchema oracle.express.mdm.MdmMetadataProvider.getRootSchema()
         void mypackage3.olaptest.<init>()
         void mypackage3.olaptest.main(java.lang.String[])
    ***Exception encountered : java.lang.NullPointerException
    Process exited with exit code 0.
    ... when running the following code
    try {
    Class.forName("oracle.jdbc.driver.OracleDriver");
    String url = "jdbc:oracle:thin:@jonm2000:1521:jonm";
    String user = "sh";
    String password = "sh";
    oracle.jdbc.OracleConnection conn = (oracle.jdbc.OracleConnection)java.sql.DriverManager.getConnection(url, user, password);
    ExpressTransactionProvider tp = new ExpressTransactionProvider();
    ExpressDataProvider dp = new ExpressDataProvider(conn, tp);
    dp.initialize();
    MdmMetadataProvider mp = null;
    mp = (MdmMetadataProvider) dp.getDefaultMetadataProvider();
    MdmSchema root = mp.getRootSchema();
    dp.close();
    conn.close();
    catch(Exception e) {
    System.out.println("***Exception encountered : " + e.toString());
    e.printStackTrace();
    It is also brings down the Oracle database.
    I am running:
    JDeveloper 9.0.2.822.0
    Oracle Database 9.0.2.1.0
    The code I am running is pretty much copied from the Oracle OLAP API guide - does anyone know why I am getting problems?

    It appears to be missing metadata. Since you are trying to get the schema, this is most likely a field that is required but not present (something silly, like labels). Try the following scripts posted below that verify metadata.
    When creating solved level hierarchies, all of these dimensions require 4 special dimension attributes. All 4 of these dimension attributes require a level attribute to be mapped to a populated column in each of the solved hierarchies.
    The 4 special attributes are:
    GID
    PARENT_GID
    ET
    PARENT_ET.
    You can check if these attributes exist with the following query:
    SELECT DA.OWNER,\n\
    DA.DIMENSION_NAME,\n\
    DA.ATTRIBUTE_NAME,\n\
    NVL(DA.DISPLAY_NAME, DA.ATTRIBUTE_NAME),\n\
    NVL(DA.DESCRIPTION, DA.ATTRIBUTE_NAME),\n\
    (CASE WHEN D.DESCRIPTOR_VALUE = 'Long Description' THEN 4\n\
    WHEN D.DESCRIPTOR_VALUE = 'Short Description' THEN 5\n\
    WHEN D.DESCRIPTOR_VALUE = 'End Date' THEN 1\n\
    WHEN D.DESCRIPTOR_VALUE = 'Time Span' THEN 2\n\
    WHEN D.DESCRIPTOR_VALUE = 'Year Ago Period' THEN 3\n\
    WHEN D.DESCRIPTOR_VALUE = 'Grouping ID' THEN 6\n\
    WHEN D.DESCRIPTOR_VALUE = 'Parent Grouping ID' THEN 7\n\
    WHEN D.DESCRIPTOR_VALUE = 'ET Key' THEN 8\n\
    WHEN D.DESCRIPTOR_VALUE = 'Parent ET Key' THEN 9\n\
    ELSE 0\n\
    END)\n\
    FROM ALL_OLAP2_DIM_ATTRIBUTES DA,\n\
    all_olap2_entity_desc_uses edu,\n\
    all_olap_descriptors d\n\
    where\n\
    DA.OWNER = EDU.ENTITY_OWNER (+)\n\
    AND DA.DIMENSION_NAME = EDU.ENTITY_NAME (+)\n\
    AND DA.ATTRIBUTE_NAME = EDU.CHILD_ENTITY_NAME (+)\n\
    AND EDU.DESCRIPTOR_ID = D.DESCRIPTOR_ID (+)\n\
    ORDER BY DA.OWNER, DA.DIMENSION_NAME, DA.ATTRIBUTE_NAME
    For these 4 attributes, it's not enough that they just exist, (note you can name them whatever you want) but they also have to be marked as the appropriate type as per the above SQL.
    Note also that the above SQL checks for other specially marked attributes such as Long/Short Description and End Date/Time Span. These attributes can exist without being marked as such (and can even be missing completely), and OLAP API will still function. However, I believe the OLAP API functions "better" if these attributes exist and are marked as special.
    The below SQL will check your column mappings for all attributes. (As a general rule, you shouldn't have to worry too much about mapping any CWMLITE logical entity to a valid table/column, because the CWMLITE API should catch if you don't use a valid table/column.)
    select owner,\n\
    dimension_name,\n\
    hierarchy_name,\n\
    level_name,\n\
    attribute_name,\n\
    table_owner,\n\
    table_name,\n\
    column_name,\n\
    (case when dtype = 'NUMBER' then 0\n\
    when dtype = 'DOUBLE' then 5\n\
    when dtype = 'FLOAT' then 4\n\
    when dtype = 'DATE' then 7\n\
    else 1 end)\n\
    from\n\
    all_olap2_dim_level_attr_maps\n\
    ORDER BY OWNER, DIMENSION_NAME, HIERARCHY_NAME, ATTRIBUTE_NAME
    Finally, note that any hierarchy which you map as coming from an AW will be a solved level hierarchy.

  • Read existing cubes with Java OLAP API

    Hi,
    i am new to the Oracle OLAP API and i have a question for which a do not find the answer in the documentation..
    I need to access all existing cubes in a database, get the names, the corresponding dimensions etc.
    There is no problem in reading the dimensions their hierarchies, the measures an so on. But i found no method or class to read out the information about cubes (names, dimension).
    The only thing i found in the documentation to get a cube was over a MtmMeasureMap, but when i call this method i get the exception: Not supported by server version ORAOLAP10.2.0.1.0
    Any hints?
    Thanks

    In current releases, the OLAP API is primarily a query API. Queries can include measures from multiple cubes, so there is no real purpose for a cube object. Therefore there is no Cube class in the Mdm logical metadata package.
    Cubes are useful in OLAP mappings, and there is an MtmCube class in the Mtm mapping metadata package. It is possible to navigate between Mdm and Mtm objects. The code that follows prints out the names of all of the cubes and the names of their dimensions.
    I don't understand the "Not supported by server version" error that you got. This sample code works for me in 10.1.0.4, and I expect it would work in 10.2, too.
    Geof
    MdmMetadataProvider mdp; // given
    Hashtable cubes = new Hashtable();
    MdmSchema rootSchema = mdp.getRootSchema();
    Iterator subSchemas = rootSchema.getSubSchemas().iterator();
    collectCubes(rootSchema, cubes);
    while (subSchemas.hasNext())
    collectCubes((MdmSchema) subSchemas.next(), cubes);
    // enumerate cubes
    Enumeration cubeList = cubes.keys();
    while (cubeList.hasMoreElements())
    MtmCube cube = (MtmCube) cubes.get(cubeList.nextElement());
    System.out.print(cube.getName() + ": ");
    Iterator dimensionMaps = cube.getDimensionMaps().iterator();
    boolean first = true;
    while (dimensionMaps.hasNext())
    MtmDimensionMap dimensionMap = (MtmDimensionMap) dimensionMaps.next();
    MdmDimension dimension = (MdmDimension) dimensionMap.getMdmSource();
    if (first)
    first = false;
    else
    System.out.print(", ");
    System.out.print(dimension.getName());
    System.out.println();
    void collectCubes(MdmSchema schema, Hashtable cubes)
    Iterator measures = schema.getMeasures().iterator();
    while (measures.hasNext())
    MdmMeasure measure = (MdmMeasure) measures.next();
    MtmMeasureMap measureMap = measure.getMeasureMap();
    MtmCube cube = measureMap.getCube();
    // See if we have already visited this cube for another measure
    String id = cube.getID();
    if (null == cubes.get(id))
    cubes.put(id, cube);
    }

  • Oracle9i 9.0.1 olap api

    hi guys
    i tried to write my first olap api program using oracle9i release 1 9.0.1 and when i tried to create connection it faild and i don't understand the code which in document (oracle9i olap users guid) and it uses corba to make connection
    and there is line in code ( object name =/bi/olapService) is this line is constant or i should use or it depends on my PC)
    can any one explain it and exaplain the connectionj code
    thanks

    hi oracle guys
    thanks , but i can't do this at all.
    did u mean i can patch olap engine to newer one
    and keep my DBMS oracle9i release 1
    but i need to solve to my proplem, and how to make
    the connection not to change my oracle because
    this not just joke to change my oracle release
    so did any one tried to connect to olap oracle9i 9.0.1
    please help ,my project depends on this project

  • ORA-37118: The OLAP API library was not preloaded. -AWM

    ...is what I get when trying to create an analytical workspace with Analytical Workspace Manager.
    The actual error message is as follows:
    oracle.express.idl.util.OlapiException: java.sql.SQLException: ORA-37118: The OLAP API library was not preloaded.
    ORA-06512: at "SYS.CONNECTIONINTERFACE", line 29
    ORA-06512: at line 1
    AWM version is 10.2.0.2.0A
    DB version is 10g 10.2.0 - (installation type is CUSTOM-FULL)
    Anyone?

    I'm not sure if this is relevent, but I observed "emoms.log" and the following appears during 10g startup:
    2006-09-10 22:01:45,961 [Orion Launcher] ERROR app.ContextInitializer contextInitialized.271 - Integration Class not found: oracle.sysman.ias.ias.IASIntegration
    2006-09-10 22:01:46,722 [Orion Launcher] ERROR app.ContextInitializer contextInitialized.271 - Integration Class not found: oracle.sysman.eml.target.slb.common.SLBIntegration
    2006-09-10 22:01:47,162 [Orion Launcher] ERROR app.ContextInitializer contextInitialized.271 - Integration Class not found: oracle.sysman.eml.ssl.intg.SSLIntegration
    2006-09-10 22:01:47,443 [Orion Launcher] ERROR app.ContextInitializer contextInitialized.271 - Integration Class not found: oracle.tip.oem.central.domain.ProcessConnectDomainIntg
    2006-09-10 22:01:47,443 [Orion Launcher] ERROR app.ContextInitializer contextInitialized.271 - Integration Class not found: oracle.tip.oem.central.instance.ProcessConnectInstanceIntg
    2006-09-10 22:01:47,473 [Orion Launcher] ERROR app.ContextInitializer contextInitialized.271 - Integration Class not found: oracle.webdb.admin.em.PortalIntegration
    2006-09-10 22:01:47,483 [Orion Launcher] ERROR app.ContextInitializer contextInitialized.271 - Integration Class not found: oracle.webdb.admin.em.SSOIntegration
    2006-09-10 22:01:47,483 [Orion Launcher] ERROR app.ContextInitializer contextInitialized.271 - Integration Class not found: oracle.reports.em.RepIntg
    2006-09-10 22:01:47,483 [Orion Launcher] ERROR app.ContextInitializer contextInitialized.271 - Integration Class not found: oracle.sysman.ocs.mntr.target.OcsEmailIntegration
    2006-09-10 22:01:47,483 [Orion Launcher] ERROR app.ContextInitializer contextInitialized.271 - Integration Class not found: oracle.sysman.ocs.mntr.target.OcsOidIntegration
    2006-09-10 22:01:47,493 [Orion Launcher] ERROR app.ContextInitializer contextInitialized.271 - Integration Class not found: oracle.sysman.ocs.mntr.target.OcsOvfIntegration
    2006-09-10 22:01:47,503 [Orion Launcher] ERROR app.ContextInitializer contextInitialized.271 - Integration Class not found: oracle.sysman.ocs.mntr.target.OcsWebconfIntegration
    2006-09-10 22:01:47,503 [Orion Launcher] ERROR app.ContextInitializer contextInitialized.271 - Integration Class not found: oracle.sysman.ocs.mntr.target.OcsWirelessIntg
    2006-09-10 22:01:47,503 [Orion Launcher] ERROR app.ContextInitializer contextInitialized.271 - Integration Class not found: oracle.sysman.ocs.mntr.target.OcsCalGrpIntegration

  • OLAP API does not finish Template code sample, can I get it?

    I am using the OLAP API JavaDoc as well as the OLAPAPI Guide, specifically referring to the Templates and how to use them, Chapter 10 in the guide. Example 10-4...
    Where is the code for the SingleSelectionTemplate as well as the MetadataState and Source Generator implementations that would have to be implemented for this? Both the javadoc and the code example talk about this, but there is not an example of implementation and I'd like to see what it is...Can you please provide all the code necessary to get example 10-4 to compile and run?
    Thank you,
    Lisa Cox
    OCLC Inc.

    You can get the complete code for the SingleSelectionTemplate class by downloading the
    Oracle OLAP Java API Reference for Oracle Database Release 1 (10.1.0.4) from the Oracle OTN website at http://otn.oracle.com/products/bi/olap/olap.html.
    After extracting the files from the zip file, open the toc.htm or index.html file in a browser. From the Overview page, select Example Oracle OLAP Java API Programs. At the bottom of the examples page are links to the Java files that contain the code for the TopBottomTemplate and SingleSelectionTemplate classes and the TopBottomTest class that uses the Template classes.
    The MedatadataState and SourceGenerator classes for the TopBottomTemplate class are implemented as inner classes of TopBottomTemplate. The same is true for the SingleSelectionTemplate.
    From that same OTN website you can download the Global Schema for Documentation, which is the schema that the example programs use.

  • Access Subform - Can the Subforms Source Object be defined by an SQL SP result set?

    Hi Guys,
    I can't clearly answer this question with a yes or no.
    I have an Access Sub Form that I am populating with a record set from a Store Procedure. Fairly early on I discovered that for this to work correctly the Source Object for the Sub Form Control must be set first, and most examples (including a working version
    of my own) achieve this by defining an Access Query and setting the Source Object to this.
    What I would really like to do is define the Source Object using the results of a SQL Store Procedure using ONLY code within VBA.
    Now before anyone starts providing alternatives "why don't you just..."  I'm noting now that I have a semi complex solution that makes most non-VBA based approaches ineffective. While it does work at present with an Access Query I'm needing
    to make the result set more dynamic meaning in future I will not know how many columns will be returned or the name of them, only the SP will have this information.
    Thanks in advance!

    Well after much trial and error I've got something which does what I want, although I'm not thrilled that I couldn't do this via my existing ADODB connections, in any case example provided below;
        Dim db As DAO.Database
        Dim qdf As New DAO.QueryDef
        Set db = CurrentDb()
       'qryMyTest refers to a dummy Access query (non pass through). 
        With db.QueryDefs("qryMyTest")
            .Connect = CurrentDb.TableDefs("tblSomeTestSQLTable").Connect
            .SQL = "exec sp_MyTestSP"
            Me.subfrmTest1.SourceObject = "Query.qryMyTest"
        End With   
        Set qdf = Nothing
    I've also marked your response Alphonse as an answer as it lead me onto the right path.

  • Crystal report for visual studio 2010 data source object is not valid error

    Hello,
    I receive an "data source object is not valid" error when I want to print one CR document after setting an ADODB.Recordset on SetDataSource method of my report.
    On my developer station, this operation works without problem but on client station, I get this error.
    The redistributable package for client is installed on client side (CRRuntime_32bit_13_0_1.msi).
    Can someone help me?
    Thank you.

    Thank's for your answers
    Dim rsPkLst As ADODB.Recordset = Nothing
    Dim report As New crPickingList
    ' Fill ADODB.Recordset with SQL Statment
    If rsPkLst.RecordCount > 0 Then
          report.SetDataSource(rsPkLst) ' Error : The data source object is invalid
    EndIf
    This error appears during  "report.SetDataSource(rsPkLst)" instruction.
    ADODB drivers are already installed and my ADODB.Recordset is filled with good records.
    This project is an updated project from Visual Studio 2003 to Visual studio 2010 and the old version was running fine.
    Developer and client station runs under Windows XP SP3.
    On developer side I install CRforVS_13_0_1 (BuildVersion=13.0.1.220.Cortez_CR4VS).
    On client side I install CRRuntime_32bit_13_0_1.msi.
    Both stations use Microsoft .Net Framework 4.
    Move to ADO.NET is a solution but, for the moment, I do not have the time to change all applications from my company.
    (I get this error from all application updated from VS 2003 to VS 2010 developed since 2005)
    David.

Maybe you are looking for