OWB Metadata export to OBIEE

Background:
I have extended the OWB metadata by adding the Business Metadata (Technical and operational metadata is there out of the box). Business metadata is expected to be maintained by business users and consists of business terms and categories and has a number of attached attributes. I will like to leverage all the metadata in OWB repository to drive my OBIEE development and production.
Question: How can OBIEE ingest the OWB metadata, in particular the business metadata and make it available to developers and the OBIEE business users?

Hi
The OWB 10.2 and 11.1 releases of OWB support OBI SE (Discoverer), the OWB 11gR2 (in beta) has support for OBI EE.
Cheers
David

Similar Messages

Error in SQL script generated from OWB 10.1.0.4.0 Metadata Export Bridge

Hi... maybe i´m abusing this forum .. but .. when you have questions .. you have to look for answers
I use OWB 10.1.0.4 to buid some dimensions and one cube. I validate and generate this object and the result was successful.
I made the deployment and everithing goes OK !!!.
The problem appears when i want to generate metadata over this objects. I use the option Project > Metadata > Export > Gridge and use the option "Oracle 9i OLAP" like the product where i want to transfer the metadata .. and i got the SQL script without any errors. I suppose that i take the sql script i run it into SQL*plus ... so i do it.. and i got this errors:
declare
ERROR at line 1:
ORA-06501: PL/SQL: program error
ORA-06512: at line 119
ORA-06510: PL/SQL: unhandled user-defined exception
The same error for any dimension in script..
Any help .. will be fully valued for me ..
best regards
Lisandro.

But how did you identify that there are no runtime records in all_rt_audit_executions for your PL/SQL procedure?
I guess you tried to search by procedure name... (but what column you used for searching)
In my case all_rt_audit_executions and wb_rtv_audit_executions contains the same number of records, so they should be always in sync.
Oleg

AWM hangs after OBIEE metadata export

Hi All ,
Does anyone face the problem of AWM hangs after OBIEE metadata export using AWM 11.2.0.2A ?
It was not previously hanged but now when I try to copy the UDML in clipboard after that the screen hangs. Any reason for that ?
Also I can see the UDML not copied from the clipboard and showing can not paste object from clipboard and after executing thorugh nQUDMLexec I can't figure out the issue as it is reffering some dimension Hierarchy attribute name not found while the same is present under AWM and I can view the data.
Not sure what's going on ..
Thanks,
DxP

Please be sure that you are using the very latest OBIEE plug-in
which is 11.2.0.2.0A - Revision 1. You can get it from the following link:
http://www.oracle.com/technetwork/database/options/olap/olap-downloads-098860.html
The hang issue is likely due to the plug-in falling over with a nullPointerException.
Are you running this against an 11.1.0.7 rdbms? There was a bug that would cause the
11.2.0.2.0A plug-in to fall over against an 11.1.0.7 rdbms which has been fixed with the
latest OBIEE plug-in as above.
Let me know how you do with the very latest OBIEE plug-in.
David

Metadata export/import to other BI tools?

Metadata export/import to other BI tools?
Hi ,
I am using SQL DM 3.0.0.665. I need your thoughs on following.
As we build our logical/physical models in SQL data Modeler, we create our metadata for our attributes/columns.
After creating our physical model, other BI and reporting tools acquire access to the physical tables. Each tool has a process of creating their reporting layer and able to bring the tables/columns into reporting layer. It shows the column names as it is. It is not business friendly.
Do we have a mechanism to export attribute business names as meta data of DB tables?
If we define the meta data as part of physical model using modeling tools such as Oracle SQL Developer or ERWIN, will we able to import those into BI tools as report elements meta data?
Where can I find details?
How do we do that?
Thanks in helping us out.

Hi,
there is no problem if you are building reports on top of our reporting repository - table DMRS_MAPPINGS holds information for pairs - (entity- table), (attribute-column)...., and you can take implementation and business name.
Exchange to BI tools - you need to know how particular BI tool can recognize and link implementation and business names and then you can use transformation script in order to provide required information. There are examples on this forum how to deal with files and database connection using transformation script.
Philip

Manage table function's source code in OWB metadata

Hi all,
please I would like to know if it possible to code a table function in OWB's metadata.
I'll try to better explain myself; I know how to use a tf in a mapping but I also would like to manage the table function's source code in OWB metadata repository.
It appears you cant code a table function as procedures/functions: there's no ref_cursor as input , no pipelined option and so on.
I'm workin on 10.2.0.4 OWB repos.
Any information will be appreciated, thanks.
best regards, David

... you are right. You cannot write the code of a table function inside owb. You must write the table function external and create it in the database. In owb you only can call the table function.
Regards,
Detlef

HSS "Deployment Metadata" export (partly) fails with 4 error messages:

The "Deployment Metadata"-export fails.
It fails both on HSS user interface or via the LCM utility on the foundation server and on a non foundation machine.
Perhaps its due to the fact that we have 3 essbase servers with a couple of essbase application/ database with the same names. But if thats the case this should not happen I guess.
(ApplicationX.DatabaseY exists both on Essbase serverA and essbase serverB)
Any help will be great.
kind regards,
Detlev
Error in migrating artifact, "/Shared Services Registry/Essbase/Cluster - inform.acc@inform/Properties".
EPMREG-10003: An unexpected error occurred during storing the artifact Properties. Detailed message is /Shared Services Registry/Essbase/Cluster - inform.acc@inform
Error in migrating artifact, "/Shared Services Registry/Essbase/Cluster - inform.check@inform/Properties".
EPMREG-10003: An unexpected error occurred during storing the artifact Properties. Detailed message is /Shared Services Registry/Essbase/Cluster - inform.check@inform
Warning in migrating artifact, "/Shared Services Registry/Essbase/ITC - EssbaseServer@inform/Properties".
EPMLCM-35003: Application artifact listing metadata contains duplicate resource information for /Shared Services Registry/Essbase/ITC - EssbaseServer@inform/Properties.
Warning in migrating artifact, "/Shared Services Registry/Foundation Services/Shared Services/ITC - Foundation@inform/Properties".
EPMLCM-35003: Application artifact listing metadata contains duplicate resource information for /Shared Services Registry/Foundation Services/Shared Services/ITC - Foundation@inform/Properties.
Warning in migrating artifact, "/Shared Services Registry/Interactive Reporting/Agent Module@ServerX_6814,6815/RAService - DataAccess@serverX/Das Dsn@ServerY/Properties".
EPMLCM-35003: Application artifact listing metadata contains duplicate resource information for /Shared Services Registry/Interactive Reporting/Agent Module@ServerX_6814,6815/RAService - DataAccess@ServerX/Das Dsn@ServerY/Properties
Edited by: Detlev on Apr 8, 2013 4:46 PM

Could you try to use adt to package the AIR file?
There might be some error messages that doesn't get caught by Flash Builder.
Have you modified the Application Descriptor since last succeful packaging?

Transportable tablespace (metadata export with READ WRITE tablespace set)

Is it possible to use transportable tablespace backup for import if data files for tablespace set has been copied when tablespaces were READ ONLY but the metadata export (or a part of it) is taken after tablespaces has been set to READ WRITE?

Actually the size of datafile(s) are too huge so unable to test the same on test box with TTS export backup.
But my question is if there were no structural changes (DML might be there on tablespace objects) even after making tablespaces to READ WRITE till the time metadata export is completed(data files are copied to staging location already before tablespaces has been set READ WRITE), Shall I use these backup for import?

COMMAND TO EXECUTE SCRIPT GENERATED BY OWB TO EXPORT METADATA

Sorry but I'm trying to execute the script to export metadata to OLAP like is descripbed in the Oracle Warehouse Builder User's Guide, but it doesn't function it give the usege:
TARGET is the schema where is data:
sqlplus OLAPDBA/[email protected] TARGET
Usage: SQLPLUS [ [<option>] [<logon>] [<start>] ]
where <option> ::= -H | -V | [ [-C <v>] [-L] [-M <o>] [-R <n>] [-S] ]
<logon> ::= <username>[<password>][@<connect_identifier>] | / | /NOLOG
<start> ::= @<URL>|<filename>[.<ext>] [<parameter> ...]
"-H" displays the SQL*Plus version banner and usage syntax
"-V" displays the SQL*Plus version banner
"-C" sets SQL*Plus compatibility version <v>
"-L" attempts log on just once
"-M <o>" uses HTML markup options <o>
"-R <n>" uses restricted mode <n>
"-S" uses silent mode
Thanks in advance.

Simth,
Since you use the OWB framework, you would deploy the generated script using the deployment manager and then you can execute using the deployment manager also.
Please refer to the quick guide:
http://otn.oracle.com/products/warehouse/pdf/92QuickStartGuide.pdf
You also may want to check out the deployment and execution section of the user's guide:
http://otn.oracle.com/documentation/warehouse.html
Thanks,
Mark.

Metadata export error

hi,
I try to transfer my metadata with oracle WB Transfer.
I Trace it and recieve folloing log :
**! Transfer logging started at Mon Feb 07 16:47:45 IRST 2005 !**
**! Client is 127.0.0.1 !**
**! Server is 127.0.0.1 !**
OWB Bridge processed arguments
Bridge Parameters are:
<BA>=<KAFA_COLLECTION2>
<LANGUAGE>=<All Languages>
<LOCKREPOSITORY>=<True>
<file>=<C:\TEMP\bridges\null-nullMy_Metadata_Transfer1107782265830.XMI>
Using attribute sorting
export to file
Default local= fa_IR
Exporting project:KAFA_PROJECT2
initializing project:KAFA_PROJECT2
Initializing module :KAFA_DW_MODULE
exportSchema:KAFA_DW_MODULE SCHM14314
Exporting cube:EMPLOYEMENT_CUBE
exportCube:EMPLOYEMENT_CUBE/EMPLOYEMENT_CUBE Cube14396
exportCubeDimUse:CDU14344FK14400
exportFactLevelUse:FLU14396FK14400
exportCubeDimUse:CDU14359FK14403
exportFactLevelUse:FLU14396FK14403
exportCubeDimUse:CDU14379FK14397
exportFactLevelUse:FLU14396FK14397
exportClassificationEntry for:KAFA_COLLECTION2 CLE_0
exportMeasure:SALARY/SALARY MEA38108
Exporting cube:HOKM_CUBE
exportCube:HOKM_CUBE/HOKM_CUBE Cube38100
exportCubeDimUse:CDU14344FK38101
exportFactLevelUse:FLU38100FK38101
exportCubeDimUse:CDU14359FK38104
exportFactLevelUse:FLU38100FK38104
exportClassificationEntry for:KAFA_COLLECTION2 CLE_2
exportMeasure:ESTEKHDAMDATE/ESTEKHDAMDATE MEA38109
exportMeasure:SALARY/SALARY MEA38110
Exporting dimension:DEP_DIM
exportDimension:DEP_DIM/DEP_DIM DIM14359
exportClassificationEntry for:KAFA_COLLECTION2 CLE_3
exportLevel:DEP_MAIN/DEP_MAIN LEV14360
exportClassificationEntry for:Description CLE_4
exportLevelAttribute:DEP_ID/DEP_ID LATR14363
exportLevelAttribute:DEP_NAME/DEP_NAME LATR14367
exportKey:DEP_MAIN_UK/DEP_MAIN_UK KEY14361
exportKeyAttributeUse:KEYAU14363KEY14361
exportHierarchy:HIE_DEP/HIE_DEP HEIR14374
exportHierarchyLevelUse:HLU14374LEV14360
Exporting dimension:EMP_DIM
exportDimension:EMP_DIM/EMP_DIM DIM14344
exportClassificationEntry for:KAFA_COLLECTION2 CLE_6
exportLevel:EMP_MAIN/EMP_MAIN LEV14345
exportClassificationEntry for:Description CLE_7
exportLevelAttribute:EMP_ID/EMP_ID LATR14348
exportLevelAttribute:EMP_NAME/EMP_NAME LATR14352
exportKey:EMP_MAIN_UK/EMP_MAIN_UK KEY14346
exportKeyAttributeUse:KEYAU14348KEY14346
exportHierarchy:HIE_EMP/HIE_EMP HEIR14354
exportHierarchyLevelUse:HLU14354LEV14345
Exporting dimension:JOB_DIM
exportDimension:JOB_DIM/JOB_DIM DIM14379
exportClassificationEntry for:KAFA_COLLECTION2 CLE_8
exportLevel:JOB_MAIN/JOB_MAIN LEV14380
exportClassificationEntry for:Description CLE_9
exportLevelAttribute:JOB_ID/JOB_ID LATR14383
exportLevelAttribute:JOB_NAME/JOB_NAME LATR14389
exportKey:JOB_MAIN_UK/JOB_MAIN_UK KEY14381
exportKeyAttributeUse:KEYAU14383KEY14381
exportHierarchy:HIE_JOB/HIE_JOB HEIR14391
exportHierarchyLevelUse:HLU14391LEV14380
Exporting mappings
exportDimensionTableMap:DTMAP14359
exportItemMap:IMAP14364
exportItemUse:TIU14363
exportItemUse:SIU14364
exportItemMap:IMAP14368
exportItemUse:TIU14367
exportItemUse:SIU14368
exportDimensionEntityUse:EU_DIM14359
exportDimensionTableUse:EU_TAB14359
exportDimensionTableMap:DTMAP14344
exportItemMap:IMAP14349
exportItemUse:TIU14348
exportItemUse:SIU14349
exportItemMap:IMAP14353
exportItemUse:TIU14352
exportItemUse:SIU14353
exportDimensionEntityUse:EU_DIM14344
exportDimensionTableUse:EU_TAB14344
exportDimensionTableMap:DTMAP14379
exportItemMap:IMAP14384
exportItemUse:TIU14383
exportItemUse:SIU14384
exportItemMap:IMAP14390
exportItemUse:TIU14389
exportItemUse:SIU14390
exportDimensionEntityUse:EU_DIM14379
exportDimensionTableUse:EU_TAB14379
exportFactTableMap:FTMAP14396
exportMapDependency:MAPDEP14396DTMAP14344
exportMapDependency:MAPDEP14396DTMAP14359
exportMapDependency:MAPDEP14396DTMAP14379
exportItemMap:IMAP38108
exportItemUse:TIU38108
exportItemUse:SIU38108
exportCubeEntityUse:EU_Cube14396
exportFactUse:EU_TAB14396
exportFactLevelGroup:FLG_TAB14396
exportFactTableMap:FTMAP38100
exportMapDependency:MAPDEP38100DTMAP14344
exportMapDependency:MAPDEP38100DTMAP14359
exportItemMap:IMAP38109
exportItemUse:TIU38109
exportItemUse:SIU38109
exportItemMap:IMAP38110
exportItemUse:TIU38110
exportItemUse:SIU38110
exportCubeEntityUse:EU_Cube38100
exportFactUse:EU_TAB38100
exportFactLevelGroup:FLG_TAB38100
Exporting table:DEP_DIM
exportTable:DEP_DIM/DEP_DIM TAB14359
exportKey:DEP_DIM_DEP_MAIN_UK/DEP_DIM_DEP_MAIN_UK KEY14362
exportKeyAttributeUse:KEYAU14364KEY14362
exportColumn:DEP_MAIN DEP_ID/DEP_MAIN_DEP_ID COL14364
exportColumn:DEP_MAIN_DEP_NAME/DEP_MAIN_DEP_NAME COL14368
exportClassificationEntry for:KAFA_COLLECTION2 CLE_10
Exporting table:EMP_DIM
exportTable:EMP_DIM/EMP_DIM TAB14344
exportKey:EMP_DIM_EMP_MAIN_UK/EMP_DIM_EMP_MAIN_UK KEY14347
exportKeyAttributeUse:KEYAU14349KEY14347
exportColumn:EMP_MAIN EMP_ID/EMP_MAIN_EMP_ID COL14349
exportColumn:EMP_MAIN_EMP_NAME/EMP_MAIN_EMP_NAME COL14353
exportClassificationEntry for:KAFA_COLLECTION2 CLE_11
Exporting table:JOB_DIM
exportTable:JOB_DIM/JOB_DIM TAB14379
exportKey:JOB_DIM_JOB_MAIN_UK/JOB_DIM_JOB_MAIN_UK KEY14382
exportKeyAttributeUse:KEYAU14384KEY14382
exportColumn:JOB_MAIN JOB_ID/JOB_MAIN_JOB_ID COL14384
exportColumn:JOB_MAIN_JOB_NAME/JOB_MAIN_JOB_NAME COL14390
exportClassificationEntry for:KAFA_COLLECTION2 CLE_12
Exporting table:EMPLOYEMENT_CUBE
exportTable:EMPLOYEMENT_CUBE/EMPLOYEMENT_CUBE TAB14396
exportKey:SEG_UK_EMPLOYEMENT_CUBE/SEG_UK_EMPLOYEMENT_CUBE KEY14406
exportKeyAttributeUse:KEYAU14401KEY14406
exportKeyAttributeUse:KEYAU14404KEY14406
exportKeyAttributeUse:KEYAU14398KEY14406
exportForeignKey:FK_EMPLOYEMENT_CUBE_14362/FK_EMPLOYEMENT_CUBE_14362 FK14403
exportKeyAttributeUse:KEYAU14404FK14403
exportForeignKey:FK_EMPLOYEMENT_CUBE_14347/FK_EMPLOYEMENT_CUBE_14347 FK14400
exportKeyAttributeUse:KEYAU14401FK14400
exportForeignKey:FK_EMPLOYEMENT_CUBE_14382/FK_EMPLOYEMENT_CUBE_14382 FK14397
exportKeyAttributeUse:KEYAU14398FK14397
exportColumn:DEP_MAIN_DEP_ID/DEP_MAIN_DEP_ID COL14404
exportColumn:EMP_MAIN_EMP_ID/EMP_MAIN_EMP_ID COL14401
exportColumn:JOB_MAIN_JOB_ID/JOB_MAIN_JOB_ID COL14398
exportColumn:SALARY/SALARY COL38108
exportClassificationEntry for:KAFA_COLLECTION2 CLE_13
Exporting table:HOKM_CUBE
exportTable:HOKM_CUBE/HOKM_CUBE TAB38100
exportForeignKey:FK_HOKM_CUBE_14362/FK_HOKM_CUBE_14362 FK38104
exportKeyAttributeUse:KEYAU38105FK38104
exportForeignKey:FK_HOKM_CUBE_14347/FK_HOKM_CUBE_14347 FK38101
exportKeyAttributeUse:KEYAU38102FK38101
exportColumn:DEP_MAIN_DEP_ID/DEP_MAIN_DEP_ID COL38105
exportColumn:EMP_MAIN_EMP_ID/EMP_MAIN_EMP_ID COL38102
exportColumn:ESTEKHDAMDATE/ESTEKHDAMDATE COL38109
exportColumn:SALARY/SALARY COL38110
exportClassificationEntry for:KAFA_COLLECTION2 CLE_14
exportContext:CTXT00
exportTypeSet:TSET
Exporting datatypes
exportScalarDatatype:NUMBER DTYP7836
exportScalarDatatype:VARCHAR2 DTYP7839
exportClassification:KAFA_COLLECTION2 CLAS1
exportClassificationType:Warehouse Builder Business Area CLT15
exportClassification:Description CLAS5
exportClassificationType:Dimensional Attribute Descriptor CLT16
Exporting project KAFA_PROJECT2 complete.
**! Target bridge jvm parameters = "..\..\..\jdk\jre\bin\javaw" -mx50m -DORCLCWM_META_MODEL_FILE=..\..\bridges\admin\orcl_cwm.xml -classpath .;..\..\bridges\lib\bridge_cwmlite10.jar;..\..\bridges\lib\bridge_parser10.jar;..\..\bridges\lib\vek10.jar;..\..\..\lib\xmlparserv2.jar;..\..\..\jdbc\lib\ojdbc14.jar;..\..\bridges\lib\util10.jar;..\..\lib\int\util.jar;..\..\lib\int\rts.jar;..\..\..\jlib\rts2.jar;..\..\bridges\lib\bridge_cwmlite10.jar;..\..\bridges\lib\bridge_parser10.jar;..\..\bridges\lib\vek10.jar;..\..\..\lib\xmlparserv2.jar;..\..\..\jdbc\lib\ojdbc14.jar;..\..\bridges\lib\util10.jar;..\..\lib\int\util.jar;..\..\lib\int\rts.jar;..\..\..\jlib\rts2.jar;"..\..\..\jdk\jre\lib\rt.jar;..\..\..\jdk\jre\lib\charsets.jar";"..\..\bridges\admin;..\..\bridges\lib\bridge_wrapper10.jar;..\..\bridges\lib\util10.jar;..\..\lib\int\reposimpl.jar;..\..\lib\int\repossdk.jar;..\..\lib\int\rts.jar;..\..\..\jlib\rts2.jar;..\..\lib\int\util.jar" oracle.cwm.tools.bridge.BridgeWrapper -bridge_name oracle.cwm.bridge.cwmlite.ImportMain !**
**! Target bridge parameters = -log_level 2 -log_file C:\TEMP\bridges\log\null-nullMy_Metadata_Transfer1107782265830.log -olapimp.deploytoaw Y -olapimp.awname dw_targetschema -olapimp.awobjprefix dw_ts -olapimp.loadcubedata Y -olapimp.awaggregate 1 -olapimp.dimuniquekeys Y -olapimp.awuser -olapimp.createviews Y -olapimp.viewprefix -olapimp.viewaccesstype OLAP -olapimp.creatematviews Y -olapimp.viewscriptdir -olapimp.deploy Y -olapimp.username dw_targetschema -olapimp.password password -olapimp.host 200.20.20.11 -olapimp.port 1521 -olapimp.sid ora10g -olapimp.inputfilename C:\TEMP\bridges\null-nullMy_Metadata_Transfer1107782265830.XMI -olapimp.outputfilename C:\Documents and Settings\stabatabaee\Desktop\test.sql -paramfile C:\TEMP\bridges\1107782266112.par !**
setting parameter: olapimp.deploytoaw = Y
setting parameter: olapimp.awname = dw_targetschema
setting parameter: olapimp.awobjprefix = dw_ts
setting parameter: olapimp.loadcubedata = Y
setting parameter: olapimp.awaggregate = 1
setting parameter: olapimp.dimuniquekeys = Y
setting parameter: olapimp.awuser =
setting parameter: olapimp.createviews = Y
setting parameter: olapimp.viewprefix =
setting parameter: olapimp.viewaccesstype = OLAP
setting parameter: olapimp.creatematviews = Y
setting parameter: olapimp.viewscriptdir =
setting parameter: olapimp.deploy = Y
setting parameter: olapimp.username = dw_targetschema
setting parameter: olapimp.host = 200.20.20.11
setting parameter: olapimp.port = 1521
setting parameter: olapimp.sid = ora10g
setting parameter: olapimp.inputfilename = C:\TEMP\bridges\null-nullMy_Metadata_Transfer1107782265830.XMI
setting parameter: olapimp.outputfilename = C:\Documents and Settings\stabatabaee\Desktop\test.sql
Loading Metadata
Loading XMI input file
connecting ...
processing dim: DEP_DIM
processing level: DEP_MAINin dimension DEP_DIM
processing level attribute use: DEP_MAIN_DEP_ID in level DEP_MAIN for level attribute DEP_ID
processing level attribute : DEP_ID in level DEP_MAIN
processing level attribute use: DEP_MAIN_DEP_NAME in level DEP_MAIN for level attribute DEP_NAME
processing level attribute : DEP_NAME in level DEP_MAIN
declare
id number;
s_id number;
l_id number;
levelday_id number;
levelmonth_id number;
levelquarter_id number;
levelyear_id number;
f_id number;
begin
select descriptor_id into l_id from all_olap_descriptors where descriptor_value='Long Description';
select descriptor_id into s_id from all_olap_descriptors where descriptor_value='Short Description';
select descriptor_id into levelday_id from all_olap_descriptors where descriptor_value='Day';
select descriptor_id into levelmonth_id from all_olap_descriptors where descriptor_value='Month';
select descriptor_id into levelquarter_id from all_olap_descriptors where descriptor_value='Quarter';
select descriptor_id into levelyear_id from all_olap_descriptors where descriptor_value='Year';
cwm_olap_dimension.Set_Description (USER, 'DEP_DIM', '');
cwm_olap_dimension.Set_Display_Name(USER, 'DEP_DIM', 'DEP_DIM');
cwm_olap_dimension.Set_Plural_Name(USER, 'DEP_DIM', 'DEP_DIM');
cwm_olap_level.Set_Description (USER, 'DEP_DIM', 'DEP_MAIN', '');
cwm_olap_level.Set_Display_Name(USER, 'DEP_DIM', 'DEP_MAIN', 'DEP_MAIN');
begin
cwm_olap_level_attribute.set_name(USER, 'DEP_DIM', 'DEP_MAIN', 'DEP_MAIN_DEP_ID', 'DEP_ID');
exception when OTHERS then null;
end;
begin
cwm_olap_level_attribute.Set_Display_Name(USER, 'DEP_DIM', 'DEP_MAIN', 'DEP_ID', 'DEP_ID');
exception when OTHERS then null;
end;
begin
cwm_olap_level_attribute.Set_description(USER, 'DEP_DIM', 'DEP_MAIN', 'DEP_ID', '');
exception when OTHERS then null;
end;
begin
cwm_olap_level_attribute.set_name(USER, 'DEP_DIM', 'DEP_MAIN', 'DEP_MAIN_DEP_NAME', 'DEP_NAME');
exception when OTHERS then null;
end;
begin
cwm_olap_level_attribute.Set_Display_Name(USER, 'DEP_DIM', 'DEP_MAIN', 'DEP_NAME', 'DEP_NAME');
exception when OTHERS then null;
end;
begin
cwm_olap_level_attribute.Set_description(USER, 'DEP_DIM', 'DEP_MAIN', 'DEP_NAME', '');
exception when OTHERS then null;
end;
begin
cwm_olap_dim_attribute.drop_Dimension_Attribute(USER, 'DEP_DIM', 'Short_Description');
exception when others then null;
end;
begin
cwm_olap_dim_attribute.Create_Dimension_Attribute(USER, 'DEP_DIM', 'Short_Description', 'Short_Description', 'Short Description');
select descriptor_id into id from all_olap_descriptors where descriptor_value='Short Description';
cwm_classify.add_entity_descriptor_use(id, cwm_utility.DIMENSION_ATTRIBUTE_TYPE,USER, 'DEP_DIM', 'Short_Description');
exception when others then null;
end;
begin
cwm_olap_dim_attribute.drop_Dimension_Attribute(USER, 'DEP_DIM', 'Long_Description');
exception when others then null;
end;
begin
cwm_olap_dim_attribute.Create_Dimension_Attribute(USER, 'DEP_DIM', '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, 'DEP_DIM', 'Long_Description');
exception when others then null;
end;
begin
cwm_olap_dim_attribute.Add_Level_Attribute(USER, 'DEP_DIM', 'Short_Description', 'DEP_MAIN', 'DEP_NAME');
exception when cwm_exceptions.attribute_already_exists then null; when cwm_exceptions.attribute_not_found then null;
end;
begin
cwm_olap_dim_attribute.Add_Level_Attribute(USER, 'DEP_DIM', 'Long_Description', 'DEP_MAIN', 'DEP_NAME');
exception when cwm_exceptions.attribute_already_exists then null; when cwm_exceptions.attribute_not_found then null;
end;
commit;
exception when others then dbms_output.enable(1000000); cwm_utility.dump_error(); raise program_error;
end;
processing dim: EMP_DIM
processing level: EMP_MAINin dimension EMP_DIM
processing level attribute use: EMP_MAIN_EMP_ID in level EMP_MAIN for level attribute EMP_ID
processing level attribute : EMP_ID in level EMP_MAIN
processing level attribute use: EMP_MAIN_EMP_NAME in level EMP_MAIN for level attribute EMP_NAME
processing level attribute : EMP_NAME in level EMP_MAIN
declare
id number;
s_id number;
l_id number;
levelday_id number;
levelmonth_id number;
levelquarter_id number;
levelyear_id number;
f_id number;
begin
select descriptor_id into l_id from all_olap_descriptors where descriptor_value='Long Description';
select descriptor_id into s_id from all_olap_descriptors where descriptor_value='Short Description';
select descriptor_id into levelday_id from all_olap_descriptors where descriptor_value='Day';
select descriptor_id into levelmonth_id from all_olap_descriptors where descriptor_value='Month';
select descriptor_id into levelquarter_id from all_olap_descriptors where descriptor_value='Quarter';
select descriptor_id into levelyear_id from all_olap_descriptors where descriptor_value='Year';
cwm_olap_dimension.Set_Description (USER, 'EMP_DIM', '');
cwm_olap_dimension.Set_Display_Name(USER, 'EMP_DIM', 'EMP_DIM');
cwm_olap_dimension.Set_Plural_Name(USER, 'EMP_DIM', 'EMP_DIM');
cwm_olap_level.Set_Description (USER, 'EMP_DIM', 'EMP_MAIN', '');
cwm_olap_level.Set_Display_Name(USER, 'EMP_DIM', 'EMP_MAIN', 'EMP_MAIN');
begin
cwm_olap_level_attribute.set_name(USER, 'EMP_DIM', 'EMP_MAIN', 'EMP_MAIN_EMP_ID', 'EMP_ID');
exception when OTHERS then null;
end;
begin
cwm_olap_level_attribute.Set_Display_Name(USER, 'EMP_DIM', 'EMP_MAIN', 'EMP_ID', 'EMP_ID');
exception when OTHERS then null;
end;
begin
cwm_olap_level_attribute.Set_description(USER, 'EMP_DIM', 'EMP_MAIN', 'EMP_ID', '');
exception when OTHERS then null;
end;
begin
cwm_olap_level_attribute.set_name(USER, 'EMP_DIM', 'EMP_MAIN', 'EMP_MAIN_EMP_NAME', 'EMP_NAME');
exception when OTHERS then null;
end;
begin
cwm_olap_level_attribute.Set_Display_Name(USER, 'EMP_DIM', 'EMP_MAIN', 'EMP_NAME', 'EMP_NAME');
exception when OTHERS then null;
end;
begin
cwm_olap_level_attribute.Set_description(USER, 'EMP_DIM', 'EMP_MAIN', 'EMP_NAME', '');
exception when OTHERS then null;
end;
begin
cwm_olap_dim_attribute.drop_Dimension_Attribute(USER, 'EMP_DIM', 'Short_Description');
exception when others then null;
end;
begin
cwm_olap_dim_attribute.Create_Dimension_Attribute(USER, 'EMP_DIM', 'Short_Description', 'Short_Description', 'Short Description');
select descriptor_id into id from all_olap_descriptors where descriptor_value='Short Description';
cwm_classify.add_entity_descriptor_use(id, cwm_utility.DIMENSION_ATTRIBUTE_TYPE,USER, 'EMP_DIM', 'Short_Description');
exception when others then null;
end;
begin
cwm_olap_dim_attribute.dBRD-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.ImportCube.importCubeAW(ImportCube.java:139)
at oracle.cwm.bridge.cwmlite.ImportMain.runBridge(ImportMain.java:152)
at oracle.cwm.tools.bridge.BridgeWrapper.run(BridgeWrapper.java:509)
at java.lang.Thread.run(Thread.java:534)
**! Transfer logging stopped at Mon Feb 07 16:49:32 IRST 2005 !**
hat is the problem ???
thanks,
shima

Does anyone else have any insight into a 'named pipes error' when attempting to export WSUS metadata from the Windows Internal Database?
RRS
Truly, it makes very little sense. Named Pipes is the ONLY way to communicate with a Windows Internal Database. If Named Pipes were not enabled, the WSUS Server would not work.
From your original post...
I have enabled the TCP/IP and Named Pipes protocols in SQL. They are selected under surface area configuration as well.
You're aware that you cannot do this for the Windows Internal Database?
Which then brings us to a second variation on the previous question -- How many, and what type, of SQL Server instances are installed on this machine?
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

Issue while exporting report - OBIEE 11g - IIS 7.5

Hi,
We are currently on OBIEE 11.1.1.7.0 version of OBIEE and we have set up proxy through IIS 7.5 on Windows 2008 R2 server.
While exporting our reports, we need to ensure that both Export to excel options (2003 and 2007+) are working fine. However, for some reports, when we try to download the reports to Excel 2007+ format, we get a "Internet Explorer cannot display the webpage" error message. This issue does not appear if we change the URL to directly access Weblogic server (instead of routing through IIS). Wanted to know if anyone have faced similar issue and have found any solution/workaround for same.
Thanks
Hyder

Hyder,
I have achieved this.We have deployed our OBIEE application on Weblogic server not on IIS.
Sasi Nagireddy: How to Export Analysis in Excel 2007 +
Thanks,
Sasi Nagireddy..

UDF fields missing in Deployment Manager User Metadata export wizzard

Hi,
When I try to export UDF-s using Deployment Manager, not all UDF-s appear in the Deployment Manager wizard step1 Search list for User Metadata type.
It seems that UDF Lookup type-s are not included.
Also, some text type UDF-s are missing as well, while the rest of the text type UDF-s are in the list.
I wonder if someone has encountered the issue? Is there any solution for this?
Thanks in advance.

Hi,
I have tried your suggestion, exported sandbox, than published the sandbox. The UDF-s are included in the UserEO.xml.xml file, but are still cannot be retrieved in Deployment Manager wizard step1 Search list.
Even if I enter the exact name of the attribute (USR_UDF_DEPT_NO) it is not found.
The problem is even more severe:
- the UDF missing from the export, which is a lookup type field, cannot be mapped in a GTC connector.
- this UDF field is NOT CREATED in the DATABASE.
Error message:
<Error> <oracle.iam.configservice.impl> <BEA-000000> <The attribute DEPT_NO does not exist!>
<Error> <oracle.iam.ui.formservice.model.modeler.FormService> <BEA-000000> <Updating User field DEPT_NO with params....failed>
OIM version: 11.1.2.1.0
Can someone confirm if this a bug? Is there a workaround?
Best regards.

Page X of Y functionality for PDF export in OBIEE

Hi,
Can any one of you please let me know how to implement page 1(2) and page 2(2) functionality in OBIEE when we export in PDF. Its very urgent requirement for us.

Hi,
Go to edit your report,
look at your PDF Control setting and use below syntax this will give u no of pages for each report
Sample report name @{pageNumber} of @{numberOfPages}
Thanks
Deva

Bulk Metadata Export Not Working!

I'm a longtime Aperture user and I ran into an issue today that I wasn't having before that latest update.
If I export one picture at a time the metadata transfers and I can read it in other programs. If I bulk export (select 24 or more shots) with the exact same settings (jpeg current size, transfer metadata) the metadate does not transfer.
Anoyone else run into this problem?

Hi Ernie,
I was just about to update this. It turns out it was working. I was using Preview to check the keywords (what I thought I was losing) and that's where things got weird. After I'd completed my export I would go to the folder and open ONE jpeg to check. That jpeg would not show keyword data. I would then check a few more files individually and had the same problem. However, if I did a 'select all' and opened Preview the keywords would show in the inspector. Preview does see the keyword data if I open one jpeg that was exported from Aperture by itself. I hope you followed that. At the end of the day it's not a problem with Aperture or and not much of an issue at all. Just an oddity that I can't explain.
Will

Can't minimize metadata exporting from Lightroom 1.4.1

I want to strip out EXIF camera metadata when I prepare TIFF images for clients. I've tried setting the "Minimize Embedded Metadata" toggle in the Export dialogue of Lightroom 1.4.1, but this only works when I am exporting JPGS, not with TIFF or PSD files. How can I strip out camera and exposure info for TIFFs and PSDs?

hi,
If you just bought the pre then its best to contact your carrier for help. If sprint cant help you or still having prob they will usually escalate the call to palm tech itself.
On your case the prob really is difficult cause you need to sync first your data into ICAL/ADDRESSBOOK and the only way to do that is to use isync or other third apps program out there. The setup of isync is quite complicated.
Its best your guided properly..
hope this helps..
=)

Best practice metadata export/import for WebCenter portal

Hi
I'm using JDeveloper to build the WebCenter portal. When I let's say register a portlet producer along with my portal, the information about it is stored in the metadata. In case I want to move my portal from the integrated WLS which JDeveloper provides to another WebLogic server with WebCenter installation - steps which I need to do are:
1) Export the metadata from JDeveloper
2) Import metadata to my target Weblogic server
3) deploy the application
Am I missing something?
To export/import metadata from JDeveloper to another Weblogic (equipped with WebCenter) server I should use the WLST script, right?
Thanks

A little correction: IAS Version is Oracle9i Application Server Release 1 version 1.0.2.2.2

OWB Metadata export to OBIEE

Similar Messages

Maybe you are looking for