24.1 About Discoverer versions and EUL versions

Specific versions of Discoverer are compatible with particular EUL versions.

Discoverer end users will be unable to connect to an EUL that is not compatible with the version of the Discoverer product that they are using.

The following table provides Discoverer release and version numbers and the EUL version numbers to which they correspond.

Discoverer Release/Version Number

EUL Version Number

Version 11.1.1.1.0

Version 5.1.x.x

Version 10.1.2.x

Version 5.1.x.x

Version 9.0.4.x

Version 5.0.2.x

Version 9.0.2.53 and later

Version 5.0.2.x

Version 9.0.2.52 and earlier

Version 5.0.0.x

Release 4.1.x

Release 4.1.x

Release 3.1.x/3.3.x

Release 3.1.x

24.1.1 About upgrading from Discoverer Version 10.1.2 to Version 11.1.1.1.0

Discoverer Version 11.1.1.1.0 uses the same EUL version as Discoverer 10.1.2; therefore, no EUL upgrade is required. If you are using a version of Discoverer earlier than 10.1.2, then use the information in this chapter to upgrade to 10.1.2.

For information about upgrading Discoverer Version 10.1.2 to Version 11.1.1.1.0, see the Oracle Fusion Middleware Upgrade Guide for Oracle Portal, Forms, Reports, and Discoverer.

24.2 Upgrading from earlier versions to Discoverer 10.1.2

This section describes how to upgrade the End User Layer for use with Discoverer 10.1.2. After you upgrade the EUL for use with Discoverer 10.1.2, you can also it with with Discoverer 11.1.1.1.0.

If you attempt to connect to a Release 4.1.x EUL or a Version 5.0.x.x EUL (Discoverer Version 9.0.2 or 9.0.4) using Discoverer Administrator Version 10.1.2, then you will be prompted to upgrade the EUL to Version 5.1.x.x. Note that this EUL upgrade option is destructive.

Throughout this chapter, references to Discoverer Version 10.1.2 apply to all 10.1.2.x versions including 10.1.2.0.0, 10.1.2.1, and 10.1.2.2

24.2.1 Which upgrade path to take for Discoverer Version 10.1.2

The appropriate upgrade path depends on the version of Discoverer from which you are upgrading, as described in the following list:

24.2.2 What are the prerequisites for upgrading from earlier versions to Discoverer Version 10.1.2?

Before you can upgrade to Discoverer Version 10.1.2, Discoverer Administrator Version 10.1.2 must already be installed.

In addition, to upgrade End User Layers, the EUL owners must have the following database privileges:

CREATE PROCEDURE

CREATE SESSION

CREATE TABLE

CREATE VIEW

CREATE SEQUENCE

If upgrading Discoverer to an Oracle9i (or later) Enterprise Edition database, summaries are implemented as materialized views and the EUL owners therefore require the following privileges:

CREATE ANY MATERIALIZED VIEW

DROP ANY MATERIALIZED VIEW

ALTER ANY MATERIALIZED VIEW

GLOBAL QUERY REWRITE

Important: To maintain the consistency of data transferred to upgraded EULs, it is very important that no Discoverer Administrator sessions are opened on the earlier version of the EUL while the upgrade is in progress.

24.2.3 An overview of the upgrade process for Discoverer Version 10.1.2

During the upgrade process, you perform numerous steps. Some of these steps depend on the version of Discoverer from which you are upgrading.

The following list provides an overview of the steps that you follow:

Use the database export utility to take a backup of each EUL that you must upgrade. Ensure that you take a database export instead of an EUL export to include the EUL tables themselves (including workbook definitions that are saved to the database and query statistics) and the EUL metadata.

Upgrade EULs by opening each EUL in the version of Discoverer Administrator to which you are upgrading. When you log on to Discoverer Administrator as the owner of a Release 4.1 or Version 5.0.x.x EUL, Discoverer Administrator automatically prompts you to upgrade the EUL to Version 5.1.x.x.

Refresh summary folders.

Migrate users to the new version of Discoverer. Users of older versions of Discoverer will not be able to access upgraded EULs. Note that:

users of Discoverer Release 4.1 will still be able to access an original Release 4.1 EUL, but any changes that they make will not be visible in the upgraded Version 5.1.x.x EUL.

users of Discoverer Version 9.0.2 and Version 9.0.4 who accessed a Version 5.0.x.x EUL will not be able to access that EUL when the EUL has been upgraded to Version 5.1.x.x.

Remove the old EULs from the database (not required when upgrading from Version 9.0.x). Initially you will probably want to just prevent access to the original EULs and allow users to access only the upgraded EULs. When you are confident that all users are successfully accessing the upgraded EULs, you will remove the old EULs.

Remove old versions of Discoverer from client machines. When you are confident that all users are successfully accessing the upgraded EULs with the latest version of Discoverer, you will typically want to remove old versions of Discoverer.

The steps that are described in the previous list are depicted visually in the flowchart in Figure 24-2.

24.2.5.1 About upgrading from Discoverer Release 4.1 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). If users have been using a Discoverer Release 4.1 EUL, that EUL must be upgraded before the users can access it using Discoverer Version 10.1.2.

The EUL upgrade process creates new Version 5.1 EUL tables and copies metadata from the Release 4.1 EUL tables into the new tables. Existing users can continue working with Discoverer Release 4.1 during the upgrade process, because the upgrade process is nondestructive (that is, the Release 4.1 EUL tables are not deleted).

Follow the upgrade steps below to upgrade the EUL using Discoverer Administrator:

24.2.5.2 Upgrade step 1: Back up the Release 4.1 EUL

Before you can upgrade a Discoverer Release 4.1 EUL to a Discoverer Version 5.1 EUL, 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 Release 4.1 EUL resides

The version of the Oracle database and the version of the Oracle database client software that is 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 Oracle10g client software is installed on the machine), then you might not be able to follow the instructions in this chapter. If you cannot export the EUL, contact the database administrator who can export the EUL for you.

24.2.5.3 Upgrade step 2: Upgrade the Release 4.1 EUL

After you back up the Release 4.1 EUL, you can upgrade it to Version 5.1. To upgrade an EUL, you simply open the EUL in the newer version of Discoverer Administrator by following the instructions in this section. The same database user that owned the Release 4.1 EUL will own the Version 5.1 EUL.

Note that Release 4.1 end users are not affected by the upgrade and can continue using the Release 4.1 EUL. However, any changes (for example, modifications to workbooks) that end users make in the Release 4.1 EUL after the upgrade process has started will not be present in the Version 5.1 EUL.

Important: To maintain the consistency of data that is transferred to the Version 5.1 EUL, ensure that no Discoverer Administrator sessions are opened on the Release 4.1 EUL while the upgrade is in progress.

The EUL upgrade is complete. You can use this EUL to connect to the database using Discoverer Administrator Version 10.1.2.

24.2.5.4 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 4.1 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 summary folders are based are not actually created until the summary folders are refreshed.

Open the business area that contains the summary folders that you want to refresh.

Display the Summaries tab of the Workarea.

Select the summary folders that you want to refresh.

You must refresh all of the summary folders before Discoverer can use them. However, depending on the amount of data, you might not want to refresh all the summary folders at the same time.

Select Tools | Refresh Summaries.

For any summary folders that are not based on external summary tables, the Refresh Summaries dialog is displayed.

Figure 24-7 Refresh Summaries dialog

Specify refresh options as required.

You can refresh summary folders immediately or specify a time for the refresh. Depending on the amount of data, you might want to schedule the refresh for an off-peak time.

Click OK to refresh the summary folders.

Notes

If an upgraded EUL contains summary folders that are based on external summary tables, you must also refresh those summary folders. During the refresh, Discoverer updates EUL metadata for summary folders based on external summary tables. If you are using Oracle9i (or later) Enterprise Edition databases, Discoverer creates a materialized view that references the external summary table.

24.2.5.5 Upgrade step 4: Migrate users to Discoverer Version 10.1.2

When you have upgraded all Release 4.1 EULs and you are satisfied that the upgraded EULs are ready for use, migrate Discoverer users to Discoverer Version 10.1.2.

While you are rolling out the migration across the organization, users can continue to work with Discoverer Release 4.1 (accessing the original EUL) or with Discoverer Version 10.1.2 (accessing the upgraded EUL). However, note that any changes that 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

Install Oracle Business Intelligence Discoverer.

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:

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.

24.2.5.6 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 tables/materialized 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.

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:

Choose ORACLE | Application Development | SQL*Plus from the Windows Start menu to display the SQL*Plus Log On dialog.

Enter the database user name, password, and database for the owner of the Discoverer Release 4.1 EUL that you want to remove.

Type the following at the command prompt to start the Release 4.1 EUL deinstallation script:

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.

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.

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 <today's 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.

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.

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:

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: Scott's Summary
User: FRED, Summary: Fred's 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.

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.

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:

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.

Note that any workbooks that were created in Discoverer Release 4.1 and saved in the <ORACLE_HOME>\discvr4 directory will not be deleted.

(optional) To retain workbooks from the <ORACLE_HOME>\discvr4 directory for future use, follow these steps:

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.

Delete the \discvr4 directory.

24.2.6 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:

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:

24.2.6.2 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

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.

The EUL upgrade is complete. You can use this EUL to connect to the database using Discoverer Administrator Version 10.1.2.

24.2.6.4 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 summary folders are based are not actually created until the summary folders are refreshed.

Open the business area that contains the summary folders that you want to refresh.

Display the Summaries tab of the Workarea.

Select the summary folders that you want to refresh.

You must refresh all of the summary folders before Discoverer can use them. However, depending on the amount of data, you might not want to refresh all the summary folders at the same time.

Select Tools | Refresh Summaries.

For any summary folders that are not based on external summary tables, the Refresh Summaries dialog is displayed.

Figure 24-11 Refresh Summaries dialog

Specify refresh options as required.

You can refresh summary folders immediately or specify a time for the refresh. Depending on the amount of data, you might want to schedule the refresh for an off-peak time.

Click OK to refresh the summary folders.

Notes

If an upgraded EUL contains summary folders that are based on external summary tables, then you must also refresh those summary folders. During the refresh, Discoverer updates EUL metadata for summary folders based on external summary tables. If you are using an Oracle9i (or later) Enterprise Edition database, then Discoverer creates a materialized view that references the external summary table.

24.2.6.5 Upgrade step 4: Migrate users to Discoverer Version 10.1.2

When you have upgraded all Version 5.0 EULs and you are satisfied that the upgraded EULs are ready to use, migrate Discoverer users to Discoverer Version 10.1.2.

Until you have migrated users to Discoverer Version 10.1.2, they will not be able to access upgraded EULs.

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:

Install Oracle Business Intelligence Discoverer.

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:

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 9.0.x.

Notes

When a user logs into Discoverer Version 10.1.2 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 Version 9.0.x against a non-upgraded EUL.

After Discoverer Version 10.1.2 is installed and a connection to the database has been established successfully through a Version 5.1 EUL, you can remove Discoverer Version 9.0.x products (that is, Discoverer Desktop and Discoverer Administrator) from client machines.

When you and your users have connected successfully to Version 5.1 EULs using Discoverer Version 10.1.2, you can remove Discoverer Version 9.0.x products (that is, Discoverer Administrator, Discoverer Desktop) from client machines.

To remove Discoverer Version 9.0.x products from client machines:

Insert the CD from which you installed Discoverer Version 9.0.x products into your 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.

Use the Oracle Installer dialogs to remove Discoverer Version 9.0.x products.

Note that any workbooks that were created in Discoverer Version 9.0.x and saved in the <ORACLE_HOME>\discoverer902 directory (Version 9.0.2) or the <ORACLE_HOME>\discoverer directory (Version 9.0.4) will not be deleted.

(optional) To retain Discoverer Version 9.0.x workbooks for future use with Discoverer Version 10.1.2:

Move the Discoverer Version 9.0.x workbooks to a new directory.

Delete the original directory.

24.2.7 Notes about upgrading to Discoverer Version 10.1.2

This section contains the following notes about upgrading to Discoverer Version 10.1.2:

When upgrading an Oracle Applications EUL, be aware that the MAXEXTENTS storage property of the EUL tables might have been increased to a value greater than the MAXEXTENTS storage property of the tablespace in which the EUL was created. If this situation exists, then any attempt to upgrade the EUL will fail (for example, with an ORA01631 error) because:

the upgrade process uses the original EUL tablespace's MAXEXTENTS value when creating the new EUL tables

the new EUL tables will therefore not be large enough to contain the data from the original EUL tables

If the MAXEXTENTS value of the EUL tables is greater than the MAXEXTENTS value of the EUL's tablespace, then ask the database administrator to increase the MAXEXTENTS value of the original EUL's tablespace before attempting to upgrade the EUL. The new EUL tablespace and the new EUL tables will be created with the larger MAXEXTENTS value.

24.2.7.2 Notes about upgrading EULs that contain analytic functions for Discoverer Version 10.1.2

When you upgrade a Discoverer Release 4.1 EUL to a Discoverer Version 5.1 EUL, new Oracle9i analytic functions are added to EUL tables.

Where existing user-defined functions have the same name (or the same unique identifier) as the new functions, Discoverer does the following:

renames the existing user-defined function

displays a log message at the end of the upgrade process

gives you the option to save the messages to a log file

Note: Discoverer's internal reference system ensures that Discoverer end users can still open workbooks that contain renamed user-defined functions.

24.2.7.3 Notes about upgrading the Video Stores tutorial for Discoverer Version 10.1.2

The Video Stores tutorials are specific to particular Discoverer releases.

When you upgrade to a new version of Discoverer, install the Video Stores sample data using the appropriate version of Discoverer Administrator instead of upgrading the tutorial.

24.2.7.4 Notes about upgrading scheduled workbooks for Discoverer Version 10.1.2

When you upgrade a Release 3.1 EUL to a Release 4.1 EUL, you must run a separate executable (called dis4sch.exe) to upgrade scheduled workbooks (for more information, see the Discoverer 4.1 Release Notes).

When you upgrade a Release 4.1 EUL to a Version 5.1 EUL, scheduled workbooks are automatically upgraded. However, scheduled workbook results are not copied to the Version 5.1 EUL. The results for an upgraded scheduled workbook will be available only after the scheduled workbook has next run.

24.2.7.5 Notes about upgrading workbooks saved in .dis files for Discoverer Version 10.1.2

If Discoverer Desktop users save workbooks to the file system in .dis files, then the .dis files must be upgraded before they can be used with the latest version of Discoverer.

To upgrade the .dis files, users simply open the .dis files in the latest version of Discoverer and save the files back to the file system, or to the database (to open them in Discoverer Plus and Discoverer Viewer). Note that when a .dis file has been upgraded, users of earlier versions of Discoverer Desktop will not be able to open the file.

24.2.7.6 Notes about upgrading Discoverer systems that use the EUL Gateway for Discoverer Version 10.1.2

A Discoverer system might use the EUL Gateway to populate EULs with metadata from a source other than the database's on-line dictionary (for example, from Oracle Designer).

If you upgrade such a system, then you must re-install and reconfigure the EUL Gateway after the upgrade process is complete. For more information about installing and configuring the EUL Gateway, see the eulgatew.doc document located in the <ORACLE_HOME>\discoverer\kits directory.

24.2.7.7 Notes about upgrading summary folders that contain SET operators for Discoverer Version 10.1.2

When you upgrade a Release 3.1 EUL to a Release 4.1 EUL on an Oracle9i (or later) Enterprise Edition database, be aware that summary folders based on SET operators (for example, UNION, UNION ALL, MINUS, INTERSECT) might be invalidated.

During the upgrade process, summary folders are converted to materialized views. However, the Oracle9i (or later) Enterprise Edition database imposes restrictions on the use of SET operators (for example, UNION, UNION ALL, MINUS, INTERSECT) in materialized views.

Note that the restrictions on the use of SET operators in materialized views have been removed in Oracle databases (9.2(or later).

24.2.7.8 Notes about upgrading identifiers that contain invalid characters for Discoverer Version 10.1.2

In a future release of Discoverer, there may be a change to the valid characters that can be used in identifiers and some characters may be de-supported (for more information, see "What are identifiers?"). If any characters become de-supported, then Discoverer will automatically modify the invalid characters in the release where such modification is required.

Note: During a 9.0.2 to 9.0.4 upgrade, Discoverer detects invalid characters in identifiers and warns that you will have to modify the characters in a future release. In fact, Discoverer will modify the invalid characters automatically in the release where such modification becomes required.

24.2.8 About scheduled workbooks and compatibility between Discoverer 10.1.2 and pre-Oracle9i database releases

New version of the batch PL/SQL package is installed into the user's schema

When you upgrade an EUL on a pre-Oracle9i database to Discoverer 10.1.2, a new version of the batch PL/SQL package is installed into the user's schema alongside the existing package. Preserving the existing PL/SQL package prevents any existing scheduled workbook batch jobs from being destroyed. Function names in the new batch PL/SQL package however, remain the same as the existing batch PL/SQL package.

Run a script to specify that a scheduled workbook results schema is to own the results tables

When you upgrade the EUL to Discoverer 10.1.2 from a pre-Oracle9i database release, check whether the following conditions are true:

the database user that schedules a workbook does not own the database tables that contain the workbook results

you want a different database user (a scheduled workbook results schema) to own the database tables that contain the workbook results