24-10 Oracle Fusion Middleware Administrators Guide for Oracle Business Intelligence Discoverer
you make using one version of Discoverer Administrator will not be available to users of the other version of Discoverer.
How to migrate Discoverer users to Discoverer Version 10.1.2 will depend on the Discoverer tools that they use.
To migrate Discoverer Plus and Discoverer Viewer users
1.
Install Oracle Business Intelligence Discoverer.
2.
Follow the instructions in Oracle Application Server 10g Upgrading to 10g 10.1.2 to upgrade the Discoverer components on the middle tier
To migrate Discoverer Desktop users:
1.
Install Discoverer Desktop on client machines using the CD that is supplied with Oracle Business Intelligence Tools.
The Oracle Installer installs Discoverer Desktop Version 10.1.2 in a separate directory from Discoverer Release 4.1.
Notes
When a user logs into Discoverer for the first time by using Discoverer Plus, Discoverer Desktop, or Discoverer Viewer, Discoverer searches for any Version 5.1
EULs that the user has access to, as follows:
■
If a valid EUL is found, then the user can connect and can start work in Discoverer Version 10.1.2.
■
If no valid EUL is found, then Discoverer alerts the user that they cannot connect to the database. At this point, the user must contact the Discoverer manager
because it is likely that an EUL has not yet been upgraded. Note that the user can still use Discoverer Release 4.1 against an existing Release 4.1 EUL.
Upgrade step 5: Remove the Release 4.1 EULs
When you have upgraded the Release 4.1 EULs and migrated all users to Discoverer 10.1.2, you can remove the Release 4.1 EULs.
Initially you will probably want to just prevent access to the original EULs and only allow users to access the upgraded EULs. When you are confident that all users are
successfully accessing the upgraded EULs, you can remove the old EULs.
A SQL script called eul4del.sql is shipped with Discoverer that enables you to remove Release 4.1 EULs and associated tables including summary tablesmaterialized
views.
Note the following:
■
When you run the eul4del.sql script, you are prompted for the password of the SYSTEM user. If you are not sure of the password of the SYSTEM user, then
contact the database administrator. Rather than give you the SYSTEM user’s password, the database administrator might prefer to run the script for you.
■
The eul4del.sql script will not complete successfully if there are any summary folders owned by users other than the EUL owner. The script will list any such
summary folders and their owners. The summary folder owners must delete their summary folders before you can remove the Release 4.1 EUL.
■
If you have access to Discoverer Administration Edition Release 4.1, then you can delete EULs using the EUL Manager instead of using the eul4del.sql script.
Upgrading the EUL from Earlier Versions of Discoverer 24-11
■
If users have modified the Release 4.1 EUL since you upgraded it, then their changes will not be in the Version 10.1.2 EUL. If you think significant changes
might have been made, then consider taking another backup of the Release 4.1 EUL before removing it for more information, see
Upgrade step 1: Back up the Release 4.1 EUL
. To remove a Release 4.1 EUL using the eul4del.sql script:
1.
Choose ORACLE | Application Development | SQLPlus from the Windows Start menu to display the SQLPlus Log On dialog.
2.
Enter the database user name, password, and database for the owner of the Discoverer Release 4.1 EUL that you want to remove.
3.
Type the following at the command prompt to start the Release 4.1 EUL deinstallation script:
SQL ORACLE_HOME\discoverer\util\eul4del.sql The deinstallation script removes a specified Release 4.1 EUL and any associated
database objects, including summary tablesmaterialized views. A summary of the deinstallation script is displayed:
Removing summary refresh jobs ... Discoverer End User Layer Database Tables 4.x Production deinstallation
This script will remove a version 4.x EUL and any associated database objects. It will:
1. Ask you to enter the ORACLE SYSTEM password and connect string. 2. Ask you to enter the name and password of the 4.x EUL owner.
3. Confirm that you wish to drop the 4.x EUL. 4. Check for database jobs for users other than the 4.x EUL owner.
5. Confirm whether to drop 4.x tutorial tables if any. 6. Log in as the 4.x EUL owner and remove any database jobs for it.
7. Remove all summary database objects for the 4.x EUL. 8. Remove all scheduled workbook database objects for the 4.x EUL.
9. Remove the 4.x EUL tables. 10. Remove user and public synonyms if any for the 4.x EUL tables.
4.
When prompted, enter the password and database TNS alias for the SYSTEM user. If you are not sure of the password of the SYSTEM user, then contact the database
administrator.
5.
Enter the name and password of the owner of the Release 4.1 EUL. The following text is displayed:
Preparing to remove EUL 4.x owned by username at todays date If you continue, the specified 4.x End User Layer will be PERMANENTLY dropped.
All End User Layer information and workbooks stored in the database will be deleted.
Any 5.x End User Layer tables will NOT be affected by this process. THIS PROCESS IS NON-REVERSIBLE.
Do you wish to continue [N]:
Note that the EUL removal process is not reversible.
6.
Type Y to confirm that you want to drop the Release 4.1 EUL. If the script detects the Release 4.1 tutorial tables, then you are prompted to
confirm whether to delete the tables.
24-12 Oracle Fusion Middleware Administrators Guide for Oracle Business Intelligence Discoverer
During the process of dropping the Release 4.1 EUL, the script will check whether there are any summary folders owned by users other than the EUL owner.
■
If there are no summary folders owned by other users, then the Release 4.1 EUL is dropped. You will see several messages showing the various stages of
the drop process, as follows:
Removing summary refresh jobs ... Dropping internally managed summary data ...
Removing scheduled workbook jobs ... Dropping scheduled workbook data ...
Dropping 4.x End User Layer Tables ... Removing public synonyms if any ...
Connected.
Finished removing 4.x End User Layer.
■
If there are summary folders owned by users other than the EUL owner, then the script will halt and display the following text:
The following users have managed summaries which must be dropped before this EUL can be deinstalled:
User: SCOTT, Summary: Scotts Summary User: FRED, Summary: Freds Summary
... Quitting - no changes made.
If this message appears, then the specified users must log in to Discoverer Administration Edition Release 4.1 and remove the specified summary folders for
more information, see How to delete summary folders
. When these summary folders have been removed, re-run the script eul4del.sql to remove the Release 4.1
EUL.
Upgrade step 6: Remove Discoverer Release 4.1 products from client machines
When you and your users have connected successfully to Discoverer Version 10.1.2 and you are confident that summary folders are working correctly, you can remove
Discoverer Release 4.1 products that is, Discoverer Administration Edition and Discoverer Desktop Edition from client machines.
To remove Discoverer Release 4.1 products from client machines:
1. Insert the CD from which you installed Discoverer Release 4.1 products into the
computer. The Oracle Installer starts automatically. If the Installer does not start
automatically, then access the CD-ROM with Windows Explorer and run setup.exe from the CD root directory.
2. Use the Oracle Installer dialogs to remove Discoverer Release 4.1 products.
Note: In Discoverer 4i, workbook scheduling privileges could be
granted to roles. In Discoverer 9.0.4 and 10.x, workbook scheduling privilges can be granted to users, but not to roles. When upgrading
from Discoverer 4.1 to 10.x, the old workbook scheduling privileges would remain in the EUL. You can delete the workbook scheduling
privileges manually by running the del_shd_wbk_rol_priv.sql script.
Upgrading the EUL from Earlier Versions of Discoverer 24-13
Note that any workbooks that were created in Discoverer Release 4.1 and saved in the ORACLE_HOME\discvr4 directory will not be deleted.
3.
optional To retain workbooks from the ORACLE_HOME\discvr4 directory for future use, follow these steps:
a.
Move any Discoverer Release 4.1 workbooks from the ORACLE_ HOME\discvr4 directory to a new directory for use with Discoverer Version
10.1.2.
b.
Delete the \discvr4 directory.
Upgrading from Discoverer Version 9.0.x to Discoverer Version 10.1.2
This section explains how to upgrade from Discoverer Version 9.0.2 or Discoverer Version 9.0.4 collectively referred to as Discoverer Version 9.0.x to Discoverer
Version 10.1.2 and contains the following topics:
About upgrading from Discoverer Version 9.0.x to Discoverer Version 10.1.2 Upgrade step 1: Back up the Version 5.0 EUL
Upgrade step 2: Upgrade the Version 5.0 EUL Upgrade step 3: Refresh summary folders
Upgrade step 4: Migrate users to Discoverer Version 10.1.2 Upgrade step 5: Remove Discoverer Version 9.0.x products from client machines
About upgrading from Discoverer Version 9.0.x to Discoverer Version 10.1.2
To use Discoverer Version 10.1.2, Discoverer users must have access to a Discoverer Version 5.1 End User Layer EUL.
For each EUL that needs upgrading, follow the upgrade steps below:
■
Upgrade step 1: Back up the Version 5.0 EUL
■
Upgrade step 2: Upgrade the Version 5.0 EUL
■
Upgrade step 3: Refresh summary folders
Warning: The EUL upgrade process modifies the existing Version 5.0 EUL tables.
Existing users cannot use Discoverer Version 9.0.x to access the EUL either during the upgrade process or after the upgrade process is completed.
When you are satisfied that any Version 5.0 EULs that need upgrading have been upgraded, follow the upgrade step below:
■
Upgrade step 4: Migrate users to Discoverer Version 10.1.2 When you have upgraded all users, follow the upgrade step below:
■
Upgrade step 5: Remove Discoverer Version 9.0.x products from client machines
Upgrade step 1: Back up the Version 5.0 EUL
Before you upgrade the EUL, you must first back up the EUL tables by exporting the EUL owner using the standard database export utility.
How to export the EUL owner will depend on:
■
the version of the Oracle client software that is installed on the machine
■
the version of the Oracle database on which the EUL resides
24-14 Oracle Fusion Middleware Administrators Guide for Oracle Business Intelligence Discoverer
The version of the Oracle database and the version of the Oracle database client software that are installed on the machine should be the same. If the versions are not
the same for example, if the EUL is on an Oracle9i database and the Oracle 10g client software is installed on your machine, then you might not be able to follow the
instructions in this section. If you are unable to export the EUL, then contact the database administrator who can export the EUL for you.
To back up a Version 5.0 EUL assuming the EUL resides on an Oracle9i database and you are using a machine on which you have installed Oracle Developer Suite, follow
the steps described in How to export an EUL using the standard database export
utility .
Upgrade step 2: Upgrade the Version 5.0 EUL
After backing up the EUL, you can upgrade it. To upgrade an EUL, you simply open the EUL in the latest version of Discoverer Administrator by following the instructions
in this section.
Note that after you have upgraded the EUL, users of Discoverer Version 9.0.x will not be able to use the upgraded EUL.
To upgrade a Version 5.0 EUL to Version 5.1:
1. From the Windows Start menu, choose Programs | Oracle Business Intelligence
Tools - BI TOOLS HOME NAME | Discoverer Administrator to display the Connect to Oracle Business Intelligence Discoverer Administrator dialog.
2. Enter the database user name and password of the owner of the EUL that you
want to upgrade.
3. Click OK.
The EUL upgrade required dialog is displayed.
Figure 24–8 Discoverer Administrator upgrade dialog
Notes:
■
If you have not already exported the EUL, then click Cancel and export the EUL for more information, see
Upgrade step 1: Back up the Version 5.0 EUL
.
■
If the EUL upgrade required dialog is not displayed, then the Version 5.0 EUL has already been upgraded. You do not need to upgrade the EUL again, so go
straight to Upgrade step 4: Migrate users to Discoverer Version 10.1.2
.
Upgrading the EUL from Earlier Versions of Discoverer 24-15
4.
Click Continue to display the EUL Upgrade dialog.
Figure 24–9 EUL Upgrade dialog
5. Select the Yes, I have completed a database export and am ready to upgrade the
EUL option to confirm that you have exported the Discoverer Release 5.0 EUL.
6.
Click Proceed with Upgrade to upgrade the Version 5.0 EUL. The EUL Upgrade progress window displays the status of the upgrade.
Any messages that are output during the upgrade process are shown in the End User Layer Upgrade Log dialog, which is displayed at the end of the process. For
more information about messages that refer to invalid characters in identifiers, see Notes about upgrading identifiers that contain invalid characters for Discoverer
Version 10.1.2 .
If there are summary folders in the upgraded EUL, then the following message dialog is displayed, indicating that the summary folders are invalid and must be
refreshed.
Figure 24–10 Invalid summaries warning message dialog
7. If the message dialog in
Figure 24–10 is displayed, then click OK.
The Load Wizard is displayed.
8. Click Cancel to close the Load Wizard.
The EUL upgrade is complete. You can use this EUL to connect to the database using Discoverer Administrator Version 10.1.2.
Upgrade step 3: Refresh summary folders
If there are summary folders in the EUL that you have upgraded, then you must refresh the summary folders.
The definitions of any Release 9.0.x summary folders are copied into the new Version 5.1 EUL and the status of any upgraded summary folders is changed to “Refresh
Required”. The database tables or materialized views on which the upgraded
