| Oracle® Business Intelligence Applications Upgrade Guide Version 7.9.4 E10757-01 |
|
 Previous |
 Next |
| Oracle® Business Intelligence Applications Upgrade Guide Version 7.9.4 E10757-01 |
|
Previous |
Next |
This section includes the following topics:
Section 3.6, "Upgrading the Data Warehouse Schema from Release 7.5.x to 7.7 and Migrating Data"
Section 3.7, "Upgrading the Data Warehouse Schema from Release 7.7 to 7.9.4"
Section 3.8, "Importing New Schema Definitions into the Siebel Transactional Database"
Section 3.9, "Migrating Data into the Data Warehouse Upgraded to Release 7.9.4"
Section 3.11, "Upgrading the Oracle BI Presentation Catalog"
Upgrade the Oracle BI Infrastructure to the current version. For information on installing the current version, see the Oracle Business Intelligence Infrastructure Upgrade Guide.
Run the Oracle BI Applications installer to upgrade your Oracle BI Applications environment to the current version. For instructions on running the installer, see Oracle Business Intelligence Applications Installation and Configuration Guide.
|
Note: Perform only the step that addresses the running of the installer. Do not perform the configuration instructions that follow the running of the installer. |
Before you begin this procedure, do the following:
Create and configure a new DAC repository according to the instructions in Oracle Business Intelligence Applications Installation and Configuration Guide.
Make sure you have set up the DAC system properties, Informatica Server, Informatica Repository Server, and database connections according to the instructions in the Oracle Business Intelligence Applications Installation and Configuration Guide.
Make a copy of your preconfigured source system container. (You cannot change the metadata in the preconfigured container. You must make a copy of it in order to be able to modify the objects it contains.) For instructions, see the Oracle Business Intelligence Data Warehouse Administration Console Guide
To manually move your customizations to the DAC repository
Open the copy of the source system container into which you want to move your customizations.
Import the custom data warehouse tables:
Navigate to the Tables tab in the Design view.
Right-click and select Import from Database, and then click Import Database Tables.
In the Data Sources drop-down list, select DataWarehouse.
Click Read Tables.
Select the tables you want to import, and then click Import Tables.
Import the custom columns for the tables you imported in Step 2:
In the Tables tab, query for the tables you imported in Step 2.
Right-click and select Import from Database, and then click Import Database Columns.
In the Importing Columns... dialog box, select "All records in the list," and click OK.
In the Data Sources drop-down list, select DataWarehouse.
Click Read Columns.
Select the columns you want to import, and then click Import Columns.
Navigate to the Tables tab, and then click the Columns child tab, and add the Foreign Key to Table and Foreign Key to Column attributes for the newly imported columns.
Import the indices for the custom data warehouse tables.
In the Tables tab, query for the tables you imported in Step 2.
Right-click and select Import Indices.
In the Importing Indices... dialog box, select "All records in the list," and click OK.
In the Data Sources drop-down list, select DataWarehouse.
Click Read Indices.
Select the indices you want to import, and then click Import Indices.
Import the custom source tables:
Navigate to the Tables tab in the Design view.
Right-click and select Import from Database, and then click Import Database Tables.
In the Data Sources drop-down list, select the appropriate source.
Click Read Tables.
Select the tables you want to import, and then click Import Tables.
You do not have to import columns for the custom source tables. Columns for source tables are not required.
Import columns for any standard data warehouse tables that were extended, and add the appropriate attributes in the DAC.
Create new custom logical and physical task folders.
In the DAC, from the Tools menu, select Seed Data, then select Task Folders.
To create a custom logical folder, click New.
In the Name field, enter a name for the custom logical folder, for example, Custom Logical.
In the Type field, select Logical.
To create a custom physical folder, click New.
In the Name field, enter a name for the custom physical folder, for example, Custom Physical.
In the Type field, select Physical.
Register the folders you created in Step 7 in the Source System Folders tab.
In the Design view, select the Source System Folders tab.
Click New.
Enter the name of the Custom Logical folder in the Logical Folder field.
Enter the name of the Custom Physical folder in the Physical Folder field, and save the record.
Modify the task attributes for workflows in the custom folder that are modified standard mappings, that is, standard (out-of-the-box) mappings from the previous release that you copied into the Informatica custom folder.
Navigate to the Tasks tab and query for the Informatica workflow names that are in the Informatica custom folder under Command for Incremental Load or Command for Full Load.
You must review the workflows in the custom folder in Informatica Workflow Manager.
For each task, change the Folder Name (in the Edit child tab) to the Custom Logical folder name.
For each task, right-click and select Synchronize Tasks.
In the Task Synchronization dialog box, select Selected Record Only, and click OK.
This step adds source and target tables to the task.
Click Yes in the Synchronizing Task(s)... dialog box to proceed.
An informational message will indicate the results of the process.
Click OK.
Add tasks that were created as new tasks in the current implementation.
In the Design view, select the Tasks tab, and then select the Edit child tab.
For each new task, copy the names of the Informatica workflows into the fields Command for Incremental Load and Command for Full Load.
Assign the appropriate values for the remaining fields in the Edit child tab.
In the Tasks tab, query for the tasks you entered in Step b.
Right-click the list of query results, and in the Task Synchronization dialog box, select "All records in the list," and click OK.
This step adds source tables and target tables to the task.
Click Yes in the Synchronizing Task(s)... dialog box to proceed.
An informational message will indicate the results of the process.
Click OK.
|
Note: If your customizations included new fact tables, you will need to create and assemble new subject areas as well as create and build new execution plans. If your customizations included extending dimension tables, you will need to reassemble your existing subject areas and rebuild your existing execution plans. You will also need to set the appropriate execution plan attributes, such as Prune Days. For instructions, see Oracle Business Intelligence Data Warehouse Administration Console Guide. |
For information on upgrading to Informatica version 7.1.4, see the Informatica documentation, which is provided in the Third_Party_Software\Informatica\Informatica 7.1.4 PowerCenter Doc folder of the Oracle Business Intelligence Applications CD-ROM.
You do not need to uninstall the previous version of Informatica before running the installation program. However, you need to stop the Informatica service before you install the Informatica Server and stop the Repository Server service before you install the Repository Server.
After you upgrade to Informatica version 7.1.4, you need to apply the Informatica Emergency Bug Fix (EBF) 108240. The EBF product files are located in the \Third_Party_Software\Informatica\Patch2 directory on the Oracle BI Applications 7.9.4 Installation CD. For instructions on installing the EBF, refer to the file titled EBF108240.html provided in the same location as the EBF product files.
The instructions provided in the EBF108240.html file reference the regedit path for Informatica PowerCenter 7.1.4 on Windows machines as:
\hkey_local_machine\system\currentcontrolset\services\powermart\configuration
Depending on your machine and Informatica 7.1.4 installation, the path may be:
\hkey_local_machine\system\currentcontrolset\services\powermart\parameters\configuration
Follow this procedure to upgrade the Informatica repository.
To upgrade the Informatica repository
Make sure you have backed up and renamed your current Informatica repository.
For instructions, see the Informatica documentation, which is provided in the Third_Party_Software\Informatica\Informatica 7.1.4 PowerCenter Doc folder of the Oracle Business Intelligence Applications CD-ROM.
Copy the Oracle_BI_DW_Base.rep file from the folder OracleBI\dwrep\Informatica\Repository into the folder Informatica PowerCenter 7.1.4\RepositoryServer\bin\Backup.
Launch the Informatica Repository Console and restore Oracle_BI_DW_Base.rep (located in Informatica PowerCenter 7.1.4\RepositoryServer\bin\Backup).
Copy the custom folder from your previous Informatica repository to the newly created Informatica repository:
Launch the Informatica Repository Manager, and connect to both your previous and newly created Informatica repositories.
Copy the Custom folder in your previous repository into the newly created Informatica repository.
Make sure there is an individual workflow for each of the mappings in the Custom folder.
New columns were added to the Oracle Business Analytics Warehouse for Oracle BI Applications version 7.9.4. Review your custom mappings to determine whether the new columns need to be added to the mapping.
Register the mappings in the DAC.
Upgrading from release 7.5.x requires two stages. In the first stage, you upgrade the data warehouse schema and migrate the data from release 7.5.x to 7.7. In the second stage, you upgrade the data warehouse schema and migrate the data from release 7.7 to 7.9.4.
To upgrade the data warehouse schema from release 7.5.x to 7.7
Run the schema upgrade script.
Navigate to the folder OracleBI\dwrep\Upgrade\CTLFiles.
Use the DDLimp utility to run one of the following scripts:
For Siebel Applications (Horizontal), run ddlsme_HOR_77.ctl.
For Siebel Industry Applications (Vertical), run ddlsme_SIA_77.ctl.
Use the following command, substituting the correct script name where appropriate.
..\OracleBI\dwrep\bin\DDLIMP /U <USER> /P <PASSWORD> /C <ODBC connect string> /G SSE_ROLE /I N /R Y /F <..\OracleBI\dwrep\ddlsme_HOR_77.ctl> /L <..\oracleBI\dwrep\ddlsme_HOR_77.log>
For example:
DDLIMP /U SADMIN /P SADMIN /C SIEBEL_OLTP /G SSE_ROLE /I N /R Y /F C:\OracleBI\dwrep\ddlsme_HOR_77.ctl /L C:\OracleBI\dwrep\ddlsme_HOR_77.log
Notes:
/P <PASSWORD> - The password for the data warehouse.
/C <ODBC connect string> - The name of the ODBC connect string.
/I N - Tells DDLimp to ignore the indexes DDL defined in the CTL file if any exist. It does not change existing indexes. (The default is /I Y, which tells DDLimp to create and merge indexes from the CTL file with the indexes in the database.
For Oracle databases, use the Data Direct drivers.
In addition, you can use the following commands:
/W Y - If the OLAP database is Oracle and Unicode.
/Z Y - If the OLAP database is DB2 or SQL Server and Unicode.
/B <TABLE_SPACE_NAME> - If you want to create these tables in a separate table space. For DB2, This must be specified as 32K tablespace.
/X <INDEX_TABLE_SPACE_NAME> - If you want to create the indexes in a separate tablespace. For DB2, This must be specified as 32K tablespace.
/Y - Storage File for DB2/390.
/R - Regrant tables.
Copy the file Upgrade.rep file from the folder OracleBI\dwrep\Upgrade\Informatica\Repository into the folder Informatica PowerCenter 7.1.4\RepositoryServer\bin\Backup.
Launch the Informatica Repository Console and restore Upgrade.rep (located in Informatica PowerCenter 7.1.4\RepositoryServer\bin\Backup) into a database other than the database in which you restored Oracle_BI_DW_Base.rep.
Navigate to the folder OracleBI\dwrep\Upgrade\Informatica\ParameterFiles and copy the file 753_TENERIFE_UPG_PARAMS.txt into the SrcFiles folder on the Informatica Server machine, for example, C:\Program Files\Informatica PowerCenter 7.1.4\Server\SrcFiles.
Rename 753_TENERIFE_UPG_PARAMS.txt to TENERIFE_UPG_PARAMS.txt.
In the Informatica Workflow Manager, open the Relational Connection Browser by selecting Connections from the toolbar, and then selecting Relational. Do the following.
|
Note: If you are connected to an Oracle database, use Oracle Native driver instead of ODBC.If you are connected to a SQL Server database, use the ODBC driver rather than the native SQL Server driver. |
Create a relational connection with the name PARAM_OLTP_SIEBEL to point to the Siebel transactional database.
Create a relational connection with the name DataWarehouse to point to the newly upgraded data warehouse database.
Create a relational connection with the name PARAM_DAC_NEW to point to the DAC repository database.
For Siebel Applications (Horizontal), in Informatica Workflow Manager, navigate to the folder UPGRADE_753_to_770_HOR, and execute the following workflows in the order indicated:
Upgrade_R_Image
Upgrade_Unspecifieds
Upgrade_Agree
Upgrade_Asset
Upgrade_Opty
Upgrade_Order
Upgrade_Quote
Upgrade_Response
Upgrade_ServiceRequest
Upgrade_Others
Upgrade_Visibility
UpgradeSlowlyChangingDimensionStartDates
DAC_Metadata_Upgrade_Workflow
For Siebel Industry Applications (Vertical), in Informatica Workflow Manager, navigate to the folder UPGRADE_753_to_770_SIA, and execute the following workflows in the order indicated
Upgrade_R_Image
Upgrade_Unspecifieds
Upgrade_Agree
Upgrade_Asset
Upgrade_Opty
Upgrade_Order
Upgrade_Quote
Upgrade_Response
Upgrade_ServiceRequest
Upgrade_Others
Upgrade_Visibility
UpgradeSlowlyChangingDimensionStartDates
Upgrade_Industry_R_Image
Upgrade_Industry_Unspecified
Upgrade_LS_ActivityProduct
Upgrade_LS_Others
Upgrade_Industry_Household
Upgrade_FINS_Visibility
UpgradeSlowlyChangingDimensionStartDates_Industry
DAC_Metadata_Upgrade_Workflow
This procedure adds new tables, columns, and indexes to the existing data warehouse schema. It does not alter or disrupt your existing data. The scripts that you will run during this procedure are described below.
UPGRADE.ctl. This script standardizes schemas to the Siebel Industry Applications 7.8.4 release. It adds new tables and columns and modifies existing columns. It also adds lookup tables.
790_UPGRADE_PRE_CTL_SCRIPT.sql. For all database types except for DB2, this script renames columns to support Teradata databases. It also adds default values in columns in case a column changes from nullable to not null, and truncates all fact and dimension staging tables.
For DB2 databases, this script does not rename columns. Instead, the new columns are updated with the old values in the script 790_UPGRADE_PRE_DIMENSION_SCRIPT.sql.
DW.ctl. This script upgrades the schema to the Oracle BI Applications 7.9.4 release.
790_UPGRADE_PRE_DIMENSION_SCRIPT.sql. This script creates backup tables for the dimension and fact tables that are being updated during the 7.8.4 to 7.9 upgrade. The backup tables are called <table_name>_784.
This script also sets the SRC_EFF_FROM_DT and EFFECTIVE_FROM_DT to 1/1/1899 in the tables where these columns were defaulted to SYSDATE in DW.ct.
For DB2 databases, this script contains update commands to load new column names from the old column names.
To upgrade the data warehouse schema to release 7.9.4
Run the UPGRADE.ctl script.
Navigate to the folder OracleBI\dwrep\Upgrade\CTLFiles.
Use the DDLimp utility to run the UPGRADE.ctl script. Use the following command:
..\OracleBI\dwrep\bin\DDLIMP /U <USER> /P <PASSWORD> /C <ODBC connect string> /G SSE_ROLE /I N /R Y /F <..\OracleBI\dwrep\UPGRADE.CTL> /L <..\oracleBI\dwrep\UPGRADE.log>
For example:
DDLIMP /U SADMIN /P SADMIN /C SIEBEL_OLTP /G SSE_ROLE /I N /R Y /F C:\OracleBI\dwrep\UPGRADE.CTL /L C:\OracleBI\dwrep\UPGRADE.log
Notes:
/P <PASSWORD> - The password for the data warehouse.
/C <ODBC connect string> - The name of the ODBC connect string.
/I N - Tells DDLimp to ignore the indexes DDL defined in the CTL file if any exist. It does not change existing indexes. (The default is /I Y, which tells DDLimp to create and merge indexes from the CTL file with the indexes in the database.
For Oracle databases, use the Data Direct drivers.
In addition, you can use the following commands:
/W Y - If the OLAP database is Oracle and Unicode.
/Z Y - If the OLAP database is DB2 or SQL Server and Unicode.
/B <TABLE_SPACE_NAME> - If you want to create these tables in a separate table space. For DB2, This must be specified as 32K tablespace.
/X <INDEX_TABLE_SPACE_NAME> - If you want to create the indexes in a separate tablespace. For DB2, This must be specified as 32K tablespace.
/Y - Storage File for DB2/390.
/R - Regrant tables.
Run the 790_UPGRADE_PRE_CTL_SCRIPT.sql script.
Open the SQL client for your database type, for example, SQLPLUS for Oracle, Query Analyzer for SQL Server, or a command window for DB2.
Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\<database type>.
Open the 790_UPGRADE_PRE_CTL_SCRIPT.sql file, and copy the contents into the SQL client.
Execute the script.
Run the DW.ctl script.
Navigate to the folder OracleBI\dwrep\Upgrade\CTLFiles.
Use the DDLimp utility to run the DW.ctl script.
Use the command provided in Step 1, but substitute the correct script name.
Run the 790_UPGRADE_PRE_DIMENSION_SCRIPT.sql script.
Open the SQL client for your database type.
Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\<database type>.
Open the 790_UPGRADE_PRE_DIMENSION_SCRIPT.sql file, and copy the contents into the SQL client.
Execute the script.
This procedure upgrades transactional database objects that relate to Oracle Business Intelligence Applications. It does not upgrade transactional database objects for CRM applications.
|
Note: You must perform this procedure before you migrate data into the data warehouse upgraded to release 7.9.4. |
To import new schema definitions into the Siebel transactional database
Use the DDLimp utility to run the DDL_OLTP.ctl script that is located in the OracleBI\dwrep\Upgrade\CTLFiles folder.
Follow this procedure to verify the following tables were created in the Siebel transactional database.
To verify the transactional database upgrade
For all upgrade paths, verify the following tables were created in the Siebel transactional database:
S_ETL_R_IMG_1 through S_ETL_R_IMG_166
S_ETL_I_IMG_1 through S_ETL_I_IMG_166
S_ETL_D_IMG_1 through S_ETL_D_IMG_166
S_ETL_PARAM
S_ETL_PRD_ATTR
S_ETL_PRD_REL
Follow this procedure to migrate data into the data warehouse upgraded to Release 7.9.4.
To migrate data into the data warehouse upgraded to release 7.9.4
Navigate to the folder OracleBI\dwrep\Upgrade\Informatica\SrcFiles and copy the *.csv files into the SrcFiles folder on the Informatica Server machine, for example, C:\Program Files\Informatica PowerCenter 7.1.4\Server\SrcFiles.
Navigate to the folder OracleBI\dwrep\Upgrade\Informatica\ParameterFiles and copy the file 770_TENERIFE_UPG_PARAMS.txt into the SrcFiles folder on the Informatica Server machine, for example, C:\Program Files\Informatica PowerCenter 7.1.4\Server\SrcFiles.
Rename 770_TENERIFE_UPG_PARAMS.txt to TENERIFE_UPG_PARAMS.txt.
In the file TENERIFE_UPG_PARAMS.txt:
Search for the parameter $$SourceConnection.
Set the value to one of the following options, based on your Siebel applications (OLTP) version:
SEBL_63
SEBL_753
SEBL_771
SEBL_78
SEBL_80
SEBL_VERT_753
SEBL_VERT_771
SEBL_VERT_78
SEBL_VERT_80
For example, if your Siebel applications (OLTP) version is Siebel Industry Applications 7.5.x, the parameter should appear as:
$$SourceConnection=SEBL_VERT_753
In the file TENERIFE_UPG_PARAMS.txt:
Search for the parameter $$Source_Container.
Set the value to one of the following options, based on your Siebel applications (OLTP) version:
Siebel 6.3
Siebel 7.5.3
Siebel 7.5.3 Vertical
Siebel 7.7.1
Siebel 7.7.1 Vertical
Siebel 7.8
Siebel 7.8 Vertical
Siebel 8.0
Siebel 8.0 Vertical
For example, if your Siebel applications (OLTP) version is Siebel Industry Applications 7.5.x, the parameter should appear as:
$$Source_Container=Siebel 7.5.3 Vertical
In the file TENERIFE_UPG_PARAMS.txt, edit the ETL_PROC_WID parameter as follows:
MPLT_GET_ETL_PROC_WID.$$ETL_PROC_WID=<latest ETL_PROC_WID value from your database>
You can get this value from W_PARAM_G.ETL_PROC_WID.
If you are running Siebel Industry Applications (Vertical), in the file TENERIFE_UPG_PARAMS.txt, set the VERTICAL_UPGRADE parameter to 1. For example:
$$VERTICAL_UPGRADE=1
For Siebel Industry Applications (Vertical), define the alignment rule to be used for ETL loads.
Navigate to the folder OracleBI\dwrep\Upgrade\Informatica\SrcFiles and copy the file AlignmentType_LS_782.csv into the SrcFiles folder on the Informatica Server machine, for example, C:\Program Files\Informatica PowerCenter 7.1.4\Server\SrcFiles.
Rename the file AlignmentType_LS_782.csv to AlignmentType.csv.
Open the file AlignmentType.csv, and enter one of the following alignment item types under the ALIGN_TYPE field:
Zipcode
Account/Contact
Brick
Save the file.
The Oracle Business Analytics Warehouse allows only one alignment type to be used for ETL loads during upgrade.
In Informatica Workflow Manager, navigate to the folder UPGRADE_770_to_79, and execute the following workflows in the order indicated:
MARKETING_LOAD
Upgrade_Dimensions_Industry
Update_Dimensions
Update_Dimension_Unspecified
Update_Facts
Upgrade_LS_Dimensions
Upgrade_LS_Facts
SIL_PositionDimensionHierarchy_Full
Load_INT_ORG_DH
DIMENSION_LOAD
|
Note: If you are using the SCD version of the dimension, replace the corresponding TENN_UPG_W_XXX_D_784_To_W_XXX_D session with TENN_UPG_W_XXX_D_784_SCD_To_W_XXX_D. This will upgrade the data from the W_XXX_SCD version of the dimension to the new SCD-enabled W_XXX_D dimension. |
DIMENSION_UNSPECIFIED_UPDATE
FACT_UPDATE
DAC_Metadata_Upgrade_Workflow
If you upgraded your transactional database to Siebel Applications 8.0, navigate to the folder UPGRADE_790_to_791_SBL80UPG and run the following workflows in the order indicated:
UPGRADE_DIMENSIONS
UPGRADE_FACTS
Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the main Informatica repository (Oracle_BI_DW_Base.rep).
Navigate to OracleBI\dwrep\Upgrade\DbScripts\<database type>.
Open the reset_infa_seq_gen.bat file.
The file opens a command prompt, which will prompt you for the parameters listed below.
Enter the appropriate parameter values to reflect your environment (the parameters are database specific).
For Oracle databases:
| Parameter | Setting |
|---|---|
OLAP USERNAME |
Enter the data warehouse database user ID |
OLAP PASSWORD |
Enter the user ID/password@connection string of the data warehouse database |
INFORMATICA DB USERNAME |
Enter the user ID of the main Informatica Repository database |
INFORMATICA DB PASSWORD |
Enter the password@connection string of the main InformaticaRepository database |
INFORMATICA REPOSITORY |
Enter the name of the main Informatica Repository |
INFORMATICA REPOSITORY USERNAME |
Enter the user ID of the main Informatica Repository |
INFORMATICA REPOSITORY PASSWORD |
Enter the password for the main Informatica Repository |
INFORMATICA REPOSITORY SERVER ADDRESS |
Enter the main Informatica Repository Server host name |
INFA_FOLDER |
Enter the value HOR for Horizontal Applications or VERT for Vertical Applications |
For Microsoft SQL Server databases:
| Parameter | Setting |
|---|---|
OLAP_SERVER |
Enter the name of the SQL Server for the OLAP database |
OLAP DATABASE |
Enter the name of the database on which OLAP data is available |
OLAP USERNAME |
Enter the user ID of the data warehouse database |
OLAP PASSWORD |
Enter the user ID/password@connection string of the data warehouse database |
INFORMATICA SERVER ADDRESS |
Enter the name of the SQL Server for the Informatica Repository database. |
INFORMATICA DATABASE |
Enter the name of the database on which the Informatica Repository metadata is available |
INFORMATICA DB USERNAME |
Enter the user ID of the main Informatica Repository database |
INFORMATICA DB PASSWORD |
Enter the password@connection string of the main Informatica Repository database |
INFORMATICA REPOSITORY |
Enter the name of the main Informatica Repository |
INFORMATICA REPOSITORY USERNAME |
Enter the user ID of the main Informatica Repository |
INFORMATICA REPOSITORY PASSWORD |
Enter the password of the main Informatica Repository |
INFORMATICA REPOSITORY SERVER ADDRESS |
Enter the main Informatica Repository Server host name |
INFA_FOLDER |
Enter the value HOR for Horizontal Applications or VERT for Vertical Applications |
For IBM DB2 databases:
| Parameter | Setting |
|---|---|
OLAP USERNAME |
Enter the user ID of the data warehouse database |
OLAP PASSWORD |
Enter the user ID/password@connection string of the data warehouse database |
INFORMATICA DB USERNAME |
Enter the user ID of the Upgrade Informatica Repository database |
INFORMATICA DB PASSWORD |
Enter the password @connection string of the main Informatica Repository database |
INFA DATABASE ALIAS |
Enter the name of the database in which Informatica Repository metadata is available |
INFORMATICA REPOSITORY |
Enter the name of the main Informatica Repository |
INFORMATICA REPOSITORY USERNAME |
Enter the user ID of the main Informatica Repository |
INFORMATICA REPOSITORY PASSWORD |
Enter the password for the Informatica Repository |
INFORMATICA REPOSITORY SERVER ADDRESS |
Enter the Upgrade Informatica Repository Server host name |
INFA_FOLDER |
Enter the value HOR for Horizontal Applications or VERT for Vertical Applications |
To verify the data migrated successfully:
Check whether any of the Informatica mapping log files stored in the directory \Informatica PowerCenter 7.1.4\Server\SessLogs indicates errors or failures.
Check whether the SQL scripts (790_UPGRADE_PRE_CTL_SCRIPT.sql and 790_UPGRADE_PRE_DIMENSION_SCRIPT.sql) that you ran in the SQL client of the database failed or errored out while executing.
Check the log files for the CTL files (Upgrade.ctl and DW.ctl) that you ran using the DDLimp command to determine whether any of the runs failed.
If you did not detect any errors or failures in the steps above, then the data migration was successful.
(Optional) If the data migration was successful, drop the tables that were created during the upgrade process, such as, W_xxxx_x_784 tables, LKP_xxxx_x, and W_ASSET_D_TMP.
This step frees the space occupied by these backup tables.
This process merges your customizations of a prior release of the Siebel Analytics repository with the new version of the Oracle BI repository. Before you begin this process, make sure you have backed up and renamed your existing repository.
To upgrade the repository, perform the following tasks:
Section 3.10.1, "Preparing for the Oracle BI Repository Upgrade"
Section 3.10.3, "Comparing the Siebel Analytics and Oracle BI Repositories"
Section 3.10.4, "Merging the Siebel Analytics and Oracle BI Repositories"
Section 3.10.5, "Regression Testing the Oracle BI Repository Merge"
The tasks in this section refer to multiple versions of the Siebel Analytics and Oracle BI repositories. Table 3-1 provides the names and descriptions of the repositories used in the examples in this section.
Table 3-1 Names of Analytics Repositories used in Examples
| Name of Repository | Description |
|---|---|
|
SiebelAnalytics_7x.rpd |
The standard Siebel Analytics repository for the version you are upgrading from. This repository is referred to as the "original" repository in the examples in this section. Note: Standard repositories from previous releases are available in the folder \OracleBI\Upgrade. |
|
OracleBIAnalyticsApps.rpd |
The standard Oracle BI repository for the version you are upgrading to. |
|
Customer_SiebelAnalytics.rpd |
The Siebel Analytics repository that contains your customizations for the version you are upgrading from. |
|
Merged_Repository_OracleBI.rpd |
The Oracle BI repository that contains your customizations for the version you are upgrading to. |
Follow this procedure to prepare for the repository upgrade.
To prepare for the Analytics repository upgrade
Set up a directory for the merge process, such as \OracleBIUpgrade, and create the following subfolders:
Original
AfterEqualize
AfterMerge
AfterManualWork
AfterRegressions
Copy the original repository (for example, SiebelAnalytics_7x.rpd), the production repository (for example, Customer_SiebelAnalytics.rpd, and the repository from the latest installation (for example, OracleBIAnalyticsApps.rpd) into the folder \OracleBIUpgrade\Original.
If, in your current environment, you are running Siebel Analytics for one or more modules using a Siebel Analytics repository in which you extracted the corresponding projects for the modules from the standard Siebel Analytics repository file you received from the previous release, you need to extract the same projects from the SiebelAnalytics_7x.rpd file and use this as your original repository. (If you have the original repository that you extracted during the last upgrade, you can use it as the original repository file.) This will prevent you from losing any new metadata you would like to add in this upgrade.
Also, if you customized the Siebel Analytics repository by trimming a large number of objects and you would like to get those objects back during the current upgrade, you need to trim the SiebelAnalytics_7x.rpd file in the same way and use the modified version as the original repository file. This will prevent you from losing any new metadata you would like to add in this upgrade.
The Merge feature in the Administration Tool relies on a change detection algorithm to determine the changes that need to be made to upgrade repositories correctly. For the algorithm to work correctly, it has to determine which objects in the three repositories (for example, SiebelAnalytics_7x.rpd, OracleBIAnalyticsApps.rpd, and Customer_SiebelAnalytics.rpd) are equivalent.
The point of this step is to determine for every object in the OracleBIAnalyticsApps.rpd and the Customer_SiebelAnalytics.rpd whether it is coming from the SiebelAnalytics_7x.rpd.
Equivalence between objects is established using the Administration Tool's Equalize feature. The file that you specify in the Output option (-O) is the only file that is modified during the equalization process.
The Equalize feature has several mechanisms for determining whether an object in two different repositories is semantically the same:
Fully Qualified Name. If an object in one repository has the same fully qualified name as another object of the same class in another repository, then the two objects are declared equal.
Simple String Substitution. Equivalence can be declared between two objects of the same class in two repositories whose only difference is that some key characters in their names differ. The equalizerpds executable file ignores those characters while checking fully qualified names. For example, "Core"."W_DAY_D" might be considered equivalent to "Core"."W DAY D" if the characters "_" and " " have been declared as equivalent.
Rename File. When none of the preceding rules are applicable, equivalence can be manually declared using a script as input to the equalizerpds executable file. Oracle ships the rename files (MAP) for the major releases. The files are located in the OracleBI\Upgrade folder. You can also create your own rename files for customizations not covered in the files that Oracle ships. You can open and edit the rename files in Microsoft Excel.
The syntax of the equalizerpds command is as follows:
equalizerpds.exe -A userid1 [-B [password1]] -C base_repository_name -D userid2 [-E [password2]] -F repository2_name [-J udml_utf8_file_name_equalization] [-O ouput_repository_name] [-X] [-Y equalStringSet] -X Treat 'Factxxxx' as 'Fact' in Business Model. -Y Treat the characters as equals. /? Display this usage information and exit.
To equalize a repository
Copy the appropriate MAP file from the OracleBI\Upgrade folder into the folder where you will execute equalizerpds.exe, for example, \OracleBIUpgrade\Original.
Run equalizerpds.exe to equalize the repository from the latest installation (for example, OracleBIAnalyticsApps.rpd) with the original repository (for example, SiebelAnalytics_7x.rpd). An example of the equalizerpds command is as follows:
equalizerpds -A Administrator -B SADMIN -C \\OracleBIUpgrade\Original\SiebelAnalytics_7x.rpd -D Administrator -E SADMIN -F \\OracleBIUpgrade\Original\OracleBIAnalyticsApps.rpd -O \\OracleBIAnalyticsUpgrade\AfterEqualize\OracleBIAnalyticsApps.rpd -X -J rename7x-79.map
The MAP files are located in the \OracleBI\Upgrade folder.
If the equalizerpds.exe executable file runs correctly, no errors are returned.
Run equalizerpds.exe to equalize your customized repository (for example, Customer_SiebelAnalytics.rpd) with the original repository (for example, SiebelAnalytics_7x.rpd). An example of the equalizerpds command is as follows:
equalizerpds -A Administrator -B SADMIN -C \\OracleBIUpgrade\Original\SiebelAnalytics_7x.rpd -D Administrator -E SADMIN -F \\OracleBIUpgrade\Original\Customer_SiebelAnalytics.rpd -O \\OracleBIUpgrade\AfterEqualize\Customer_OracleBIAnalyticsApps.rpd
The execution of equalizerpds that equalizes the customer repository with the original repository does not use the rename file.
Make sure that the original repository is copied unchanged into its new location so that after running the script, all three repositories are contained within the \OracleBIUpgrade\AfterEqualize directory.
To verify the process completed successfully, compare the size of the repositories. The output repository (-O) should be close to the same size as the repository you equalized (-F).
Follow this procedure to compare your existing repository with the new version to which you are upgrading.
To compare the repositories
Use the Administration Tool's Compare Repositories feature to analyze the differences between your existing repository and the new version of the repository to which you are upgrading. Note where elements have been created, removed, or changed in the new version. Consider whether you can use the new metadata and retire customizations you made in the existing repository.
For instructions on how to use the Administration Tool's Compare Repositories feature, see Oracle Business Intelligence Server Administration Guide.
In this procedure, you execute the main algorithm to upgrade the repository. For more information on merging the repositories, see Oracle Business Intelligence Server Administration Guide.
To merge versions of the repositories
Copy the three repositories (for example, SiebelAnalytics_7x.rpd, OracleBIAnalyticsApps.rpd, and Customer_SiebelAnalytics.rpd) to the AfterMerge folder.
Open the repository from the latest installation (for example, OracleBIAnalyticsApps.rpd) in the \OracleBIUpgrade\AfterMerge folder.
Save the repository with a new name, for example, Merged_Repository_OracleBIAnalyticsApps.rpd.
This new repository will contain the final results of the upgrade.
From the Administration Tool menu bar, select File, then select Merge.
In the Select Original Repository dialog box, select the original repository (for example, SiebelAnalytics_7x.rpd).
Enter the password, and click OK.
Click Select for the Modified Repository field.
In the Select Modified Repository dialog box, select the repository that contains the customizations you made to the previous version of the Analytics repository.
Click Open, type the password, and then click OK.
In the Decision drop-down list, select the action you want to take regarding the repository change, or accept the default action.
To locate subsequent rows with empty Decision fields, click the Decision header cell.
When all rows have a value in the Decision field, the Merge button is enabled.
Click Merge.
This process can take up to 40 minutes, depending on the size of the repositories you are working with. A message will alert you when the merge is complete.
Click Yes when asked if you want to run a consistency check.
The number of errors returned by the consistency check is an indication of how successful the merge process was. If you receive many errors, for example, over 300, you should analyze the reason for the errors. If the merge process failed to recognize that two objects are the same, you may need to edit the rename file if the object is in the Current repository, or add your own rename file if you have renamed many of the objects and the upgrade engine failed to relate them to the original objects.
You also may need to change the actions you selected in the Decision drop-down list before rerunning the merge. This could save you time by reducing the number of errors that you will need to fix manually.
Once you are satisfied with the results of the merge, you should fix the remaining errors manually. It is important that you fix all errors before moving on to the next step. This repository serves as the input for the next stage.
You should also check that all of your customized objects are present and that no duplicate physical tables were introduced. To check for duplicate tables, search for physical tables using a query such as:
where name like '*#1'
Copy the repository to the folder \OracleBIUpgrade\AfterManualWork.
In performing a regression test for the repository merge, the objective is to collect a set of logical SQL statements that are used for reports and to verify that they continue to work with the new metadata. For this purpose, it is recommended that you perform the following procedure.
To perform regression testing
Run the reports that are necessary to include in the regression suite. These reports might be a subset of the reports in the Presentation Catalog.
Collect the logical SQL generated in the previous step. You can do this using Usage Tracking or by parsing the query log file.
For information about Usage Tracking, see Oracle Business Intelligence Server Administration Guide.
Execute the logical SQL against the old repository using the command line utility nQCmd.exe located in \OracleBI\server\bin, and save the results to a file.
For information about the nQCmd.exe utility, see Oracle Business Intelligence Server Administration Guide.
Edit the logical SQL test scripts to account for the name changes or modifications resulting from the upgrade.
Execute the edited logical SQL against the merged repository, and save the results.
Compare the results from the steps above and try to explain the differences. If it is determined that these differences are due to the upgrade process, then you have to correct them manually.
This repository now contains the merged content from the new OracleBIAnalyticsApps.rpd and the production repository.
You will need to upgrade your current Oracle BI Presentation Catalog if your organization:
Has prebuilt applications already installed, and
Has customized the current Oracle BI Presentation Catalog
If you made no changes to the previous Presentation Catalog distributed with previous versions of prebuilt applications, you do not need to upgrade the catalog. You can begin using the newer version of the catalog.
This process includes the following tasks:
Section 3.11.2, "Upgrading the Oracle BI Presentation Catalog to a Newer Version"
Section 3.11.3, "Testing the Results of the Presentation Catalog Upgrade"
|
Caution: In releases of Oracle BI Applications previous to 7.9, the Presentation Catalog (formerly known as the Siebel Analytics Web Catalog) was stored in a single file rather than in a directory structure of individual files. If you have a previous version of the Presentation Catalog, you will need to convert it to the new format. For more information about how to convert the Presentation Catalog to the new format, see the Oracle Business Intelligence Infrastructure Upgrade Guide |
Before you upgrade and merge your current Presentation Catalog with the new Presentation Catalog, determine which of the existing content you want to keep and which new content you want to incorporate. Review your existing Presentation Catalog and determine the usage patterns of reports and dashboards. Note that some of the preconfigured content in the existing catalog may appear in the new version in a redesigned format. In addition, the new version includes completely new content. After you have decided the content that is to make up your enterprise Presentation Catalog, trim the input catalogs using the Catalog Manager. For information on trimming catalogs, see Oracle Business Intelligence Presentation Services Administration Guide.
The Presentation Catalog upgrade process makes use of three catalogs:
The original Presentation Catalog. This is the unmodified Presentation Catalog that you received with the Oracle BI Applications release that you are upgrading from.
The new Presentation Catalog. This is the Presentation Catalog that is installed in the OracleBIData\web\catalog folder with the installation of Oracle BI Applications.
The current Presentation Catalog. This is the Presentation Catalog currently in use at your organization.
You use Catalog Manager for this upgrade process. Catalog Manager compares the content in both the Current Presentation Catalog and the Modified Presentation Catalog with the content in the Original Presentation Catalog, merges any changes into the Current Presentation Catalog, and produces a list of upgrade differences, which you must resolve by indicating how you want the differences handled. If the catalogs have conflicting content, you can choose which catalog the content should be taken from. The end result is a merged Presentation Catalog that contains the site-specific changes, as well as new metadata.
To upgrade your Presentation Catalog to a newer version
Make a backup copy of the current Presentation Catalog, rename the folder <catalogname>_old, and move it to a temporary location.
Copy the original Presentation Catalog into the folder that holds your current Presentation Catalog and rename it <catalogname>_Original.
Start Catalog Manager and open the new Presentation Catalog in offline mode.
Select Tools, then select Upgrade Catalog.
In the original Presentation Catalog field, browse to locate the original Presentation Catalog.
In the Current Presentation Catalog field, browse to locate your current Web Catalog, <catalogname>_old.
Click OK.
Resolve any upgrade differences as follows:
Review each unresolved difference in the Unresolved differences list.
For each unresolved difference, select the version that you want to keep.
Click OK.
The log file SiebelAnalyticsMigrationLog.txt holds information about the merge process. This log file is written to \OracleBI\web\catalogmanager. If you get an error logged in the file, this means that the path in question had a problem that did not allow the merge mechanism to resolve the merge. No action was taken. To merge that particular item, go into your original Presentation Catalog and merge it manually.
Review the upgraded Presentation Catalog, and, if necessary, set permissions for objects.
Save the new Presentation Catalog.
|
Note: Before you perform this step, you must first migrate the data into the upgraded data warehouse. |
The Presentation Catalog upgrade functionality does not automatically carry over object permissions; therefore, you should review the Presentation Catalog object permissions before you perform this step.
This step ensures that the upgraded reports and the new preconfigured reports are functional and render correct results within the new, merged Presentation Catalog. This step is typically performed by visually inspecting the final results of the complete end-to-end upgrade process.
For upgraded reports, the preferred approach for comparison purposes is to have side-by-side environments, and have users review specific dashboard content between the two environments. Examine not only the look and feel of the application but also the data contained in the reports to make sure the content remains the same. It is recommended that you request users to use various elements of the user interface to validate results, such as global prompts, column selectors, report filters, drills, and navigations, as they normally do on a day-to-day basis.
Also review the overall visibility and administrative settings in the new Presentation Catalog to ensure they are correct. Pay careful attention to the visibility rules that are established for any content that was migrated during the upgrade. You might have to manually adjust these settings.
