Export/import OWB Business Area definitions

i have generated the Business Area definition (Logical Tree) in OWB. I can now see the Dimension and Facts definition within the logical tree section.
i then did a metadata export using the Discoverer4 bridge and saved into an EEX file. I did not get any errors in this process.
when i imported the EEX file into my existing Discoverer EUL (the owner and admin is similar to what i specified earlier in the OWB export process), i get a list of warnings saying things like 'There are invalid characters ~![] used'. The import was still flagged as successful.
The thing is, i now get sort of a duplicate entry for each item i defined in OWB. Eg. i have a Product dimension (DIM_PROD), i see a "grayed out" entry with the name 'DIM_PROD' and also another entry called 'DIM_PROD: Default'. seems like Discoverer is treating the latter as the active item ... the same goes for my Facts.
i could still build Discoverer Workbooks but now i have a very messy and duplicate items with no use when i log into Discoverer Admin. i have attempted to delete them (and succeeded with no side effects) but when i redo an import (to refresh changes i did in OWB), i get the same result again !!
any idea why this is the case ?
i am using OWB Client 9.0.2.62.3, OWB Repository 9.0.2, Discoverer Admin Client/EUL library 9.0.2.39.01 (EUL 5.0.0.0.0.0)
i suspect it's the metadata import/export process ...
thanks for any replies in advance !

Similar Messages

Import selected business area from an exported EUL file

Hi,
Iam using Oracle Business Intelligence Discoverer 10g Release 2 (10.1.2.1) , Is there a way to import selected business Area from an Exported EUL file into the Discoverer.
Thanks,
Krishna

Hi Krishna,
We cannot import a specific business area from the exported file as the file is combo of all BA's in .eex format.
Instead before exporting process,i.e when going through the export wizard you can select specific business area required and then import it.Hope this helps you.
Regards,
Kranthi.

Export views and business areas from dev to prod.

Hi Gurus,
I am using oracle database 10gR2 and Oracle BI Discoverer Administration 10gR2.
I have an End User Layer disadmin1 with 10 business areas. This EUL also have folders for the views in its own schema. I used original import/export utility to export this EUL from Development to Production environment.I exported the schema disadmin1 form development and imported it into production into same shcema disadmin1 (This exported the views too) . It is absolutely working fine.
Now I have to develop 5 more business areas in the same EUL as phase 2 development I am keeping the EUL disadmin1 for bug fixing for initial 10 BAs, and I have another EUL disadmin2 to develop new business areas. For these new business areas, I have to firrst create views and then create folders on these views in disadmin2. I will export the new business areas form discoverer utility 'Selected Business Areas' from disadmin2 and will import them into production in original EUL disadmin1. My problem is how can I export new views from development to production.
Thanks for the help.

With Discoverer, there is not necessarily one right way to do things. There is certainly nothing wrong with the process you are doing. I believe Oracle had a different process in mind with Oracle, but that does not mean your process is wrong. Did you install the seeded (Oracle term) business areas that come with Discoverer, and activated the business views for those Oracle business areas? Put those into Production and your users can develop workbooks on the fly in Production, rather than wait for something to go through a development-test-production process. Which can be good or bad depending on your individual situation. As for creating new views, I suggest talking to your Oracle technical team to see what process they have for approving new views in production and getting those views created. I would suggest getting those approved and created first before relying on using them for Discoverer development (just in case the creation is not approved), but that is just my opinion.
John Dickey

Export/Import of Business Rules

Hi
Can we automate the export/import of Business Rules using Workspace? I want to use this for backup/restoration purpose.
Thanks

Here you go :) - Re: Exporting Hyperion Business Rules as Text files
Cheers
John
http://john-goodwin.blogspot.com/

Export/import OWB (10.1 and PARIS) metadata problems

I am attempting to import an OWB 10.1–exported map into an OWB 10.2/PARIS repository .. this failed as follows from the Paris Design Center menu bar ...
Design – Import – Warehouse Builder Metadata and specify a previously exported OWB 10.1 map. I receive the following message … ”Metadata version is not compatible with you current repository version. Upgrading the file is required to import your metadata”
… Selecting ”UPGRADE” yields the following …
Upgrade started at Jul 25, 2006 12:02:05 PM
Preloading objects from release 9.2
Upgrading objects from release 9.2 to 10.0
Project "SIRR_DATA_CONVERSION"
"Error occurred importing from file "C:\MKS\ConfigurationMgmt\OWB\Unit Testing\Build 1.13\Client Account\OWBC_ALS_CLI_CLIENT\OWBC_ALS_CLI_CLIENT.mdl".
CNV0002-0025(ERROR): Unexpected error occurred. Upgrade terminated. See log file C:\MKS\ConfigurationMgmt\OWB\Unit Testing\Build 1.13\Client Account\OWBC_ALS_CLI_CLIENT\OWBC_ALS_CLI_CLIENT_10_0_upgrade.log for details. Please contact"
The log contained over 16000 lines of info associated with mapping parameter/mapping parameter properties/property values, groups and finally, before failing, mappingparameterconnection --> mappingparameterconnection .. I can email the log if anybody is interested in taking a look.
Two things with error above .. I do not have a 9.2 map (seems the upgrade is assuming a 9.2 map) but a 10.1 map .. and the error message seems to be truncated after ”Please contact”
any advice on importing OWB 10.1 metadata(maps) into OWB PARIS ? as I am trying to create business case for upgrading from OWB 10.1 to PARIS.

There is a similar issue logged in our Support database relating to this type of problem. The bug (ref number 5309802) has some workarounds relating to issues within an MDL file relating to non-unique IDs and blank properties for certain objects.
The log file should tell you exactly where the problem objects are located, row and column reference. If you could open a TAR with Oracle Support and send them the log file and the associated MDL file they should be able to organize a fix for you.
If you want to try this yourself then make a backup of the MDL file. Next open the MDL file using Winzip and extract the two files within the MDL file. The larger of the two files is in fact an XML file. Open this file in a text editor that shows line and column numbers. Now refer back to the log file and find the error messages from that file and cross reference row/column numbers within the XML file and see if the error makes sense to you. If it does, correct the error and then rezip everything back into an MDL file and try importing the MDL file again.
Alternatively you may want to leave this to Oracle Support to manage for you.
Hope this helps
Keith

Import Standard Business Area of Oracle Applications

Dear all,
I install Discoverer Administration 4i and i create EUL (Apps) to connect to Oracle Applications 11.5.0, when I import Standard(BASE) Business Area of Applications
,some BA are imported but not all.
Can anyone help me to import all BA ?
Thanks to all

Hi,
If you are just starting off, then you would be better off using the latest Discoverer 10g as Discoverer 4i is in de-support mode by Oracle.
see
Note 237607.1
Note 313418.1 Using Discoverer 10.1.2 with Oracle E-Business Suite 11i
the java EUL command-line, comes with a logging feature.
Note 139516.1 Using Discoverer 4i with Oracle Applications 11i

Suggestions needed for Export/Import Business Area Problem

I'm trying to export/import a Business Area from one instance to another and I get the following error during import processes.
Database Error - ORA-00001: unique constraint (EUL4_US.EUL4_EXP_PK) violated
The Business Area I'm trying to import doesn't exists in new instance. During the import wizard I've checked refresh existing object and match by identifiers.
I think my target instance has objects with same identifiers, so I went ahead and changed the identifiers in my source, but still problem persists. How can I correct this error?
Thanks

Did you happen to copy the EUL from one database to another before you were importing/exporting the BA?
Discoverer recognizes EULs using unique reference numbers. However, if you use the database export and import utilities to copy an EUL, the new EUL (including its reference number) will be identical to the original EUL. When EULs have the same reference number, EUL consistency issues can arise if you do both of the following:
* If you modify objects in both the original EUL and in the new EUL
* Having modified objects in both EULs, if you then attempt to copy objects between the two EULs using the Discoverer Export Wizard and Import Wizard (or the Discoverer /export and /import commands)
To avoid potential EUL consistency issues, run the eul5_id.sql script as the owner of the new EUL. The eul5_id.sql script gives a new refererence number to the new EUL and thereby avoids any potential EUL consistency issues.
Reference
* How to import an EUL using the standard database import utility
http://download-west.oracle.com/docs/html/B13916_04/maintain_eul.htm#i1008632
For 4i, you will ned to run:
sql> update EUL4_VERSIONS set VER_EUL_TIMESTAMP =TO_CHAR(SYSDATE, 'YYYYMMDDHH24MISS');
sql> commit;
Some similar EUL inconsistencies are documented in:
Note.267476.1 Discoverer Workbook Fails With 'Cannot join tables.Item dependency "" not found in EUL' After EUL Migration, Importing Or Cloning
You might want to check that if the EUL version timestamps are the same.
~Steve.

Business Area Export/Import Conditions Error

Hi,
I'm working on exporting one business area from one schema X to another Y.
Well I'm exporting the business area from the X schema using the administrator
and following the next steps:
[Menu]
File/Export...
[Export wizard Dialog]
Selected objects in the EUL/ Selecting Business Area Definitions,
folders,Workbooks.
I'm saving the resultant file like "BusinesArea.eex"
So, I'm importing the "BusinesArea.eex" file to the Y schema, using the command
line:
..\Dis51adm /connect usr/[email protected] /import BusinesArea.eex
All seems to works fine,but when I try to open one of the exported workbooks I get
the next error:
1) First a dialog box appears asking me for "Open the workbook in the current db
account."
2) when I accept the previous option, I get an Error dialog box with the "Missing
Item condition" text.
Apparently the conditions are not exported to the file.
Does anyone know how could I export all the X schema Business area conditions,
in order to import them to the Y schema, avoiding this error?
Thanks in advance.

Hi,
Thanks for your answer Skunitha,
Well, just to clarify this a little bit more my question:
I'm trying to open the workbooks using the discoverer desktop client (9.0.2.39.01) and the conditions were created in the desktop not in the administrator.
Well the process I'm runnig a script to delete the EUL in the Y schema, create a new EUL (in the Y schema), and import into the Y schema the exported BA from the X schema.
All works fine, but when I open in the Administrator the recent imported Business Area in Y, I can see all the folders and its items, But when I open the Desktop to select one of the workbooks, the workbook list appears empty.
I made what you said Skunitha, to validate the folders and I getting beside the folders the next error:
ORA-02019: connection description for remote database not found
Does any body know why I'm getting this?

Importing business areas

When exporting and importing business areas (from test to prod e.g.) i sometimes get the following problem.
For some workbooks I would like to use joins between folders in different business areas without "sharing" the folders between the business areas. This works fine when setting it up directly, but I have problems when exporting and importing. From previous advice I understood that I need to export and import both business areas and that the order in which I do so makes a difference. I tried this and found that it sometimes works and sometimes does not. So far I have not been able to determine why. Any help ? I use Disc Admin 4.1

It may be a similar issue to the Oracle BIS views. If you bring in the business areas by the import / export utility, it will order the input alphabetically, not an order that makes sense.
For example, if you had 2 business areas, and 1 was called: A and the second B (original names huh), if business area A had a folder joined to B, then at the time it comes in, B is not defined and I believe the join may go by the wayside.
I definitely know this is an issue with BIS and the most reliable way to not have this occur is to using a Unix emulator that Oracle recommends to bring the business areas in, in the correct order so that the joins are correct.
In your case, I'd check to see if this could be the problem and if so, could you alter the names of the business areas so that if imported back in the alphabetically order would work?
Just a thought.
Russ

CAN NOT IMPORT BUSINESS AREA AS IT SAYS - JOINS NOT FOUND WHERE REQUIRED

We have recently migrated from Disco 4.1.48.08 to 10.1.2
Everything looks ok - we are able to look at existing workbooks and business areas. And we can export business areas successfully.
However
When we try to import some business areas it returns - JOINS NOT FOUND WHERE REQUIRED and fails. This is now causing a problem with how we promote from our test/uat and prod environments.
any ideas ?

Here's some information from Support that helped me...
Discoverer has many options on exporting and importing objects. Entire End User Layers, Entire Business Areas or only selected objects could be exported. To simplify the process of exporting and importing Business Areas, it is suggested that the export and import process should be done with entire Business Areas. The reason why it is not recommended that selected objects are exported and imported as a norm is to simplify maintenance.
It is still possible to export and import selected objects, but a knowledgeable Administrator is recommended to head the procedure. The process could get
very complex and difficult to manage.
Some Additional Notes:
- Join conditions are exported, but are not indicated as an object. Join conditions are only exported ** if ** the joining folders are exported.
- If the ‘refresh’ option is performed in Discoverer Administrator on an object and the underlying object on the database is not available, the object is dropped from the EUL. It is of utmost importance that the objects exist on the underlying database before the ‘refresh’ option is executed.
- Functions and Workbooks are not exported when exporting an entire Business Area. Functions and Workbooks have to be exported separately.
The first bullet is what was giving me this error "JOINS NOT FOUND WHERE REQUIRED". I was unable to do a full export - another unrelated error, so I came up with an alternate solution. I created a new BA that only contained the standard folders that my two custom BA's referenced - by JOINS and inclusion in my complex folders. I exported all 3 and they imported into the new instance with no issue.
Jewell

Importing business area and then using workbook file

I need to use a workbook that was created by another user and saved as an external file.
They exported their business area and sent it to me with the workbook.
When I tried to open the workbook after sucessfully importing the business area I could not find the imported business area and the components that go with it and their was no way to browse to find them.
Can anyone help me with this problem.
Thanks.

If you want to use an external workbook that was saved to the desktop. You choose open and then click the icon with the label computer underneath.
If the components in your business area are not the same as the ones where the workbook was created you will be given the option to substitute values to match what is in the workbook with what is in the business area.
When you choose this option however, it displays only the first three business areas you have access to. There is an up and down arrow but no scroll bar implying that these are all the options. However usual windows practice did not apply and the ommitted scroll bar did not mean that all the list was displayed, clicking the down arrow would uncover more business areas.
When I finished sustituting the variables I still got a join error. It was taking too much time so I got username and password of the account where the workbook was created.

Business Area import issue

In Test I had to delete a couple folders from a Business Area(BA). But after migration a new copy of BA into Production those folders still appear. Here is my migration plan:
1. Export the BA from Test
2. Import the BA into Production using the following criteria:
- Refresh the object and then check the sub-box called Preserve display related properties
- two objects be matched by Identifier
3. Refresh the BA
Also I`d like to mention that this BA was in Production before Migration
Thank you in Advance.

Hi
It sounds as though you may have deleted the folders from the business area but not from the EUL. If this is the case, and the folders still exist inside Production, then when you import from Test into Production, the folders will be there attached to the business area.
If you really don't want the folders you should completely delete them from the Test EUL, or are you saying that you did this? If you're absolutely certain that you deleted them from Test, then exported the Test business area and imported it into Production, matching by identifier, then it sounds like there is an issue. You may need to manually delete folders in both areas.
You see, if a folder exists in production and not in the import from Test, how does Discoverer know that you did not intentionally not export that folder? I don't think it can detect that something is no longer there. Its a bit like saying give me the ID numbers of all the rows in the database that got deleted today so that I can go and delete them from the data warehouse. You cannot because they don't exist. I think your best plan would be to delete them from both areas, either that or delete the business area from production and reimport it from Test.
Does this help and what do the other Discoverer experts think about what I have said?
Regards
Michael

Error while importing business area

Hi everyone,
I'm working with Oracle Applications standard EUL, based on the BIS views
I have exported "Order Management" business area. When I try to import it in my EUL with the following command line, my command gets aborted:
$ eulapi -connect apps_user/apps_user@sid -eul EUL_US -apps_user -apps_responsibility "System Administrator" -import import_file.eex -import_rename_mode refresh -identifier
But when I import it using Oracle Discoverer Administrator, there's no problem.
I tried with another business area (Accounts Receivable), and it also works using java command line.
I don't understand why my import doesn't work. I don't have any info about the possible error, even using -log option.
It's a quite strange problem. I hope someone has an idea.
Thanks.
Daniel.

Thanks for your quick response, Michael!
I have another question on import. I imported a folder and it got imported with a warning (A folder named 'Folder Name' was created or modified during the import but is not in a business area
Import completed, but with warnings. Please check the result.
I can see the folder in the database table. Is there a way to add this folder to the business area? Or my only option is to delete the folder out of EUL?
Thanks once again!
AJ

Import business area issue

Hi Discoverer friends,
I recently created a buisness area with a workbook in development eul and imported into the production eul. I first exported the business area and workbook separatly from Dev/Test using discoverer admin.I then Imported the BA and workbook into Production in admin using the default settings except that - Refresh the object( the sub-box Preserve display related properties was not checked) I also refresh the BA. The imported workbook worked fine, but a workbook for another BA ( say BA1) failed to work. I looked into the issue and discovered that there were multiple BAs in the same EUL where the new BA (say BA3) was imported into. The folders in BA3 were 80% the same as what in BA2. However, the problem was in BA1 as some of the worksheets failed. I looked into the SQL for the failed worksheet and to my surprise, the query in BA1 joined with some of the tables in BA3. Please note: BA1 had no such folder and even no joint to these tables in BA3.
It is either a bug or something I missed or did wrong with my import of the BA3 as after I deleted both BA1/BA3, imported BA1 only and it turned out OK for BA1.
So What I should do to import the BA3?
Any help or advice will be greatly appreciated.
my Discoverer admin edition is 9.0.4. Database 9.2.4. Application server 9.0.4.2 and Discoverer Plus used is 9.0.4.45.02.
Thank you very much,
Jeff

Hi
It sounds as though you may have deleted the folders from the business area but not from the EUL. If this is the case, and the folders still exist inside Production, then when you import from Test into Production, the folders will be there attached to the business area.
If you really don't want the folders you should completely delete them from the Test EUL, or are you saying that you did this? If you're absolutely certain that you deleted them from Test, then exported the Test business area and imported it into Production, matching by identifier, then it sounds like there is an issue. You may need to manually delete folders in both areas.
You see, if a folder exists in production and not in the import from Test, how does Discoverer know that you did not intentionally not export that folder? I don't think it can detect that something is no longer there. Its a bit like saying give me the ID numbers of all the rows in the database that got deleted today so that I can go and delete them from the data warehouse. You cannot because they don't exist. I think your best plan would be to delete them from both areas, either that or delete the business area from production and reimport it from Test.
Does this help and what do the other Discoverer experts think about what I have said?
Regards
Michael

Building Business Area through Command Line

Hi --
Some of the adminstrator tasks such as...
1) Creating a folder
2) Creating a join
3) Creating a item class and attaching the item class to a filed
I would like to do these tasks eighter programtically (via PL/SQL) or through a command line script.
Just wondering whether discoverer has some APIs or commands which i can use to accomplish these tasks.
Any information regarding this would be really helpful.
Thanks

Hello,
I did try with the scripts given by you and the log says -
Exported the following Data:
Exported the following Business Areas:
Payables
Exported the following Folders:
Exported the following Item classes:
Exported the following Item Hierarchies:
Exported the following Date Hierarchies:
Exported the following Functions:
Exported the following Summaries:
Exported the following Workbooks:
Exported the following Automated Summary Management Policies:
13/05/2008 13:49:07
Are you sure that complete business area has been exported?
When I tried with Administrator GUI, the log file contains list of all folder names, items,item classes etc. Even the Administrator Guide says :
/business_area
The /business_area modifier enables you to specify a business area for import, export or deletion
Information Details
Syntax:
/business_area <business area>
Notes:
When used with the /export command, this modifier only exports the business area definition (e.g. business area name and description).
If you want to export the entire business area (i.e. including folders, item classes, hierarchies etc), use with the /all modifier also
This can be found at - http://download-west.oracle.com/docs/html/B13916_02/command_line.htm#sthref1227
So, what is your say ? Shall I ignore the log file and go ahead and import it or something is missing in the scripts.
Thanks.

Export/import OWB Business Area definitions

Similar Messages

Maybe you are looking for