Multiple Schemas with same Workbooks

Question

Hello
I have a problem with discoverer. I have 1 database instance with 1 discoverer instance. In the database are 15 comparable schemas (development, test, produktiv 1-13). For me it's not possible to let the same workbook (or make change of schema-owner) run on different schema_tables.
I have all time to new design the workbook for each schema.
In the SQL-Inspector i can see the statement that i connect every time to the same schema-table but i cound't change the schema.
Also the SQL*export and import doesn't function well because i lose the layout for the workbook.
One solution is to revoke the access from discoverer-administrator for the the table (who i have designer the workbook) and open the workbook. Then there are some screen to redefine all items within my workbook (there are more then 30). But to do this for 10 Workbooks multiply with 15 schemas. this is a very hard work and is near that to design from new for each.
Martin

Answer 1

Hi,
Well, you could have one workbook that worked with all the schemas, by creating a view that was a union all of the underlying tables from the different schemas, then use a context in the view to select the schema that you want use in your report.
Assuming that you want to create a set of workbooks for each schema, then you can get Discoverer to change the mapping in the workbook to a new folder by changing the EUL timestamp located in the EUL5_VERSION table.
Basically, when a workbook is open I think it goes a workflow similar to this to determine the mapping to the EUL items:
1. If the EUL timestamp in the workbook is the same as in the EUL then it selects the items using the id held in the workbook.
2. If the EUL timestamp is different or the item is not found using the id, then it uses the developer key in the workbook to select the item.
3. If the item is still not found then it uses the item name and folder name in the workbook to retrieve the item from the EUL.
So, if you have a workbook wb1 using folder f1 which is mapped to a table in schema s1 then you can try this workflow to create workbook wb2 pointing to schema s2 by:
1. Create a f2 folder mapping to S2.
2. Change the developer key in f1 to be a new key DK2.
3. Connect as Desktop/Plus and open the workbook wb1 and save as wb2.
4. Change the developer key in f1 back to the original key and the developer key in f2 to the new key DK2.
5. Change the EUL timestamp.
6. Open the workbook wb2 and save, it should now be pointing at folder f2 and schema S2.
7. Open the workbook wb1 and save, it should still be pointing to S1.
Rod West