Oracle Business Intelligence Applications Upgrade Guide for Informatica PowerCenter Users, Release 7.9.6.4

Release 7.9.6.4

E35270-01

Contents

List of Figures

List of Tables

Title and Copyright Information

Preface

- Audience

- Documentation Accessibility

- Related Documents

- Conventions

1 What's New in This Release

- 1.1 What's New in Oracle BI Applications Release 7.9.6.4

2 Overview of Oracle BI Applications Upgrade

- 2.1 Supported Upgrade Paths

- 2.2 Why Upgrade to Oracle BI Applications Release 7.9.6.4?

- 2.2.1 Upgrade Options

- 2.3 Considerations About Upgrading to Oracle BI Enterprise Edition 11g

- 2.4 Considerations About Upgrading Oracle BI Applications

- 2.5 Best Practices for Preparing to Upgrade

- 2.6 Major Stages of Oracle BI Applications Upgrade

- 2.6.1 Sequence of Upgrade Stages

- 2.6.2 Documentation Related to the Major Stages of the Upgrade Process

Part I Upgrading When Your Source System is Siebel CRM

3 Upgrading Siebel Analytics 7.5.x

- 3.1 Prerequisites for Upgrading Oracle BI Applications

- 3.2 Upgrading Oracle BI Infrastructure to Version 11g

- 3.3 Upgrading Oracle BI Applications

- 3.4 Upgrading to Informatica PowerCenter Version 9.0.1 Hotfix 2

- 3.5 Upgrading the Informatica Repository

- 3.6 Upgrading the Informatica Repository When You Are Already Running Informatica PowerCenter 9.1

- 3.7 Verifying Configurations for Informatica PowerCenter Version 9.0.1 Hotfix 2 to Work With Oracle BI Applications and DAC

- 3.8 Installing and Configuring DAC 11g

- 3.9 Overview of Upgrading the Data Warehouse Schema and Migrating Data

- 3.10 Upgrading the Data Warehouse Schema to Version 7.7 and Migrating Data

- 3.11 Upgrading the Data Warehouse Schema to Version 7.9.0

- 3.12 Importing New Schema Definitions into the Siebel Transactional Database

- 3.12.1 Verifying the Siebel Transactional Database Upgrade

- 3.13 Migrating Data into the Data Warehouse Upgraded to Version 7.9.0

- 3.14 Upgrading the Data Warehouse Schema to Version 7.9.4 and Migrating Data

- 3.15 Upgrading the Data Warehouse Schema to Version 7.9.5 and Migrating Data

- 3.16 Upgrading the Data Warehouse Schema to Version 7.9.5.1

- 3.17 Upgrading the Data Warehouse Schema From Version 7.9.5.1 to 7.9.6.1 and Migrating Data

- 3.17.1 Upgrading the Data Warehouse Schema From Version 7.9.5.1 to 7.9.6.1

- 3.17.2 Migrating Data Into the Upgraded Data Warehouse

- 3.17.3 Verifying the Data Migrated Successfully

- 3.18 Upgrading the Data Warehouse Schema From Version 7.9.6 to 7.9.6.1

- 3.18.1 Upgrading the Data Warehouse Schema to Version 7.9.6.1

- 3.18.2 Migrating Data into the Upgraded Data Warehouse

- 3.18.3 Verifying the Data Migrated Successfully

- 3.19 Upgrading the Data Warehouse Schema From Version 7.9.6.1 to 7.9.6.2 and Migrating Data

- 3.19.1 Upgrading the Data Warehouse Schema to Version 7.9.6.2

- 3.19.2 Migrating Data into the Upgraded Data Warehouse

- 3.19.3 Verifying the Data Migrated Successfully

- 3.20 Upgrading the Data Warehouse Schema From Version 7.9.6.2 to 7.9.6.3 and Migrating Data

- 3.20.1 Upgrading the Data Warehouse Schema to Version 7.9.6.3

- 3.20.2 Migrating Data Into the Upgraded Data Warehouse

- 3.20.3 Verifying the Data Migrated Successfully

- 3.21 Upgrading the Data Warehouse Schema From Version 7.9.6.3 to 7.9.6.4 and Migrating Data

- 3.21.1 Upgrading the Data Warehouse Schema to Version 7.9.6.4

- 3.21.2 Migrating Data into the Upgraded Data Warehouse

- 3.21.3 Verifying the Data Migrated Successfully

- 3.22 Localizing the Policy Store

- 3.23 Importing the Oracle BI Applications Version 7.9.6.4 LDIF File Into the Embedded LDAP Server

- 3.24 Upgrading the Siebel Analytics Repository and Web Catalog to the Oracle BI Enterprise Edition 11g Version

- 3.25 Merging Oracle BI Applications Version 7.9.6.4 Repository With Customer Repository

- 3.25.1 Preparing for the Oracle BI Repository Upgrade

- 3.25.2 Equalizing the Oracle BI Repositories

- 3.25.3 Comparing the Oracle BI Repositories

- 3.25.4 Merging the Oracle BI Repositories

- 3.26 Merging Oracle BI Applications Version 7.9.6.4 Presentation Catalog With Current (Custom) Catalog

- 3.26.1 Trimming the Input Presentation Catalog

- 3.26.2 Merging the Oracle BI Applications Version 7.9.6.4 Presentation Catalog With Current (Custom) Catalog

- 3.26.3 Testing the Results of the Presentation Catalog Upgrade

- 3.27 Regression Testing the Oracle BI Repository Merge

4 Upgrading Siebel Business Analytics 7.7, 7.7.x and 7.8.x

- 4.1 Prerequisites for Upgrading Oracle BI Applications

- 4.2 Upgrading Oracle BI Infrastructure to Version 11g

- 4.3 Upgrading Oracle BI Applications

- 4.4 Upgrading to Informatica PowerCenter Version 9.0.1 Hotfix 2

- 4.5 Upgrading the Informatica Repository

- 4.6 Upgrading the Informatica Repository When You Are Already Running Informatica PowerCenter 9.1

- 4.7 Verifying Configurations for Informatica PowerCenter Version 9.0.1 Hotfix 2 to Work With Oracle BI Applications and DAC

- 4.8 Upgrading to and Configuring DAC Version 11g

- 4.8.1 Installing the DAC Platform and Oracle BI Applications Metadata Repository Files

- 4.8.2 Configuring the DAC Client and Server to Work With Oracle BI Applications and Informatica

- 4.8.3 Upgrading the DAC Repository

- 4.9 Overview of Upgrading the Data Warehouse Schema and Migrating Data for Non-Teradata Databases

- 4.10 Upgrading the Data Warehouse Schema to Version 7.9.0 for Non-Teradata Databases

- 4.11 Importing New Schema Definitions Into the Siebel Transactional Database

- 4.11.1 Verifying the Siebel Transactional Database Upgrade

- 4.12 Migrating Data into the Data Warehouse Upgraded to Version 7.9.0 for Non-Teradata Databases

- 4.13 Upgrading the Data Warehouse Schema to Version 7.9.4 and Migrating Data for Non-Teradata Databases

- 4.14 Upgrading the Data Warehouse Schema to Version 7.9.5 and Migrating Data for Non-Teradata Databases

- 4.15 Upgrading the Data Warehouse Schema to Version 7.9.5.1 for Non-Teradata Databases

- 4.16 Upgrading the Data Warehouse Schema From Version 7.9.5.1 to 7.9.6.1 and Migrating Data for Non-Teradata Databases

- 4.16.1 Upgrading the Data Warehouse Schema From Version 7.9.5.1 to 7.9.6.1

- 4.16.2 Migrating Data Into the Upgraded Data Warehouse

- 4.16.3 Verifying the Data Migrated Successfully

- 4.17 Upgrading the Data Warehouse Schema From Version 7.9.6 to 7.9.6.1 and Migrating Data for Non-Teradata Databases

- 4.17.1 Upgrading the Data Warehouse Schema to Version 7.9.6.1

- 4.17.2 Migrating Data into the Upgraded Data Warehouse

- 4.17.3 Verifying the Data Migrated Successfully

- 4.18 Upgrading the Data Warehouse Schema From Version 7.9.6.1 to 7.9.6.2 and Migrating Data for Non-Teradata Databases

- 4.18.1 Upgrading the Data Warehouse Schema to Version 7.9.6.2

- 4.18.2 Migrating Data into the Upgraded Data Warehouse

- 4.18.3 Verifying the Data Migrated Successfully

- 4.19 Upgrading the Data Warehouse Schema From Version 7.9.6.2 to 7.9.6.3 and Migrating Data for Non-Teradata Databases

- 4.19.1 Upgrading the Data Warehouse Schema to Version 7.9.6.3

- 4.19.2 Migrating Data Into the Upgraded Data Warehouse

- 4.19.3 Verifying the Data Migrated Successfully

- 4.20 Upgrading the Data Warehouse Schema From Version 7.9.6.3 to 7.9.6.4 and Migrating Data

- 4.20.1 Upgrading the Data Warehouse Schema to Version 7.9.6.4

- 4.20.2 Migrating Data into the Upgraded Data Warehouse

- 4.20.3 Verifying the Data Migrated Successfully

- 4.21 Upgrading the Data Warehouse Schema and Migrating Data for Teradata Databases

- 4.21.1 Upgrading Oracle BI Applications From Version 7.9.0 to 7.9.6.4

- 4.21.2 Upgrading Oracle BI Applications From Version 7.9.4 to 7.9.6.4

- 4.21.3 Upgrading Oracle BI Applications From Version 7.9.5 to 7.9.6.4

- 4.21.4 Upgrading Oracle BI Applications From Version 7.9.5.1 to 7.9.6.4

- 4.21.5 Upgrading Oracle BI Applications From Version 7.9.6.1 to 7.9.6.4

- 4.21.6 Upgrading Oracle BI Applications From Version 7.9.6.2 to 7.9.6.4

- 4.21.7 Upgrading Oracle BI Applications From Version 7.9.6.3 to 7.9.6.4

- 4.22 Localizing the Policy Store

- 4.23 Importing the Oracle BI Applications Version 7.9.6.4 LDIF File Into the Embedded LDAP Server

- 4.24 Upgrading the Siebel Analytics Repository and the Web Catalog to the Oracle BI Enterprise Edition 11g Version

- 4.25 Merging Oracle BI Applications Version 7.9.6.4 Repository With Customer Repository

- 4.25.1 Preparing for the Oracle BI Repository Upgrade

- 4.25.2 Equalizing the Oracle BI Repositories

- 4.25.3 Comparing the Oracle BI Repositories

- 4.25.4 Merging the Oracle BI Repositories

- 4.26 Merging Oracle BI Applications Version 7.9.6.4 Presentation Catalog With Current (Custom) Catalog

- 4.26.1 Trimming the Input Presentation Catalog

- 4.26.2 Merging the Oracle BI Applications Version 7.9.6.4 Presentation Catalog With Current (Custom) Catalog

- 4.26.3 Testing the Results of the Presentation Catalog Upgrade

- 4.27 Regression Testing the Oracle BI Repository Merge

5 Upgrading Oracle BI Applications 7.9.x for Siebel Source Systems

- 5.1 Prerequisites for Upgrading Oracle BI Applications

- 5.2 Upgrading Oracle BI Infrastructure to Version 11g

- 5.3 Upgrading Oracle BI Applications

- 5.4 Upgrading to Informatica PowerCenter Version 9.0.1 Hotfix 2

- 5.5 Upgrading the Informatica Repository

- 5.6 Upgrading the Informatica Repository When You Are Already Running Informatica PowerCenter 9.1

- 5.7 Verifying Configurations for Informatica PowerCenter Version 9.0.1 Hotfix 2 to Work With Oracle BI Applications and DAC

- 5.8 Upgrading to and Configuring DAC Version 11g

- 5.8.1 Installing the DAC Platform and Oracle BI Applications Metadata Repository Files

- 5.8.2 Configuring the DAC Client and Server to Work With Oracle BI Applications and Informatica

- 5.8.3 Upgrading the DAC Repository

- 5.9 Importing New Schema Definitions Into the Siebel Transactional Database

- 5.9.1 Verifying the Siebel Transactional Database Upgrade

- 5.10 Upgrading the Data Warehouse Schema and Migrating Data for Non-Teradata Databases

- 5.10.1 Upgrading the Data Warehouse Schema From Version 7.9.0 to 7.9.4 and Migrating Data

- 5.10.2 Upgrading the Data Warehouse Schema From Version 7.9.4 to 7.9.5 and Migrating Data

- 5.10.3 Upgrading the Data Warehouse Schema From Version 7.9.5 to 7.9.5.1

- 5.10.4 Upgrading the Data Warehouse Schema From Version 7.9.5.1 to 7.9.6.1 and Migrating Data

- 5.10.4.1 Upgrading the Data Warehouse Schema to Version 7.9.6.1

- 5.10.4.2 Migrating Data Into the Upgraded Data Warehouse

- 5.10.4.3 Verifying the Data Migrated Successfully

- 5.10.5 Upgrading the Data Warehouse Schema From Version 7.9.6 to 7.9.6.1 and Migrating Data

- 5.10.5.1 Upgrading the Data Warehouse Schema to Version 7.9.6.1

- 5.10.5.2 Migrating Data Into the Upgraded Data Warehouse

- 5.10.5.3 Verifying the Data Migrated Successfully

- 5.10.6 Upgrading the Data Warehouse Schema From Version 7.9.6.1 to 7.9.6.2 and Migrating Data

- 5.10.6.1 Upgrading the Data Warehouse Schema to Version 7.9.6.2

- 5.10.6.2 Migrating Data Into the Upgraded Data Warehouse

- 5.10.6.3 Verifying the Data Migrated Successfully

- 5.10.7 Upgrading the Data Warehouse Schema From Version 7.9.6.2 to 7.9.6.3 and Migrating Data

- 5.10.7.1 Upgrading the Data Warehouse Schema to Version 7.9.6.3

- 5.10.7.2 Migrating Data Into the Upgraded Data Warehouse

- 5.10.7.3 Verifying the Data Migrated Successfully

- 5.10.8 Upgrading the Data Warehouse Schema From Version 7.9.6.3 to 7.9.6.4 and Migrating Data

- 5.10.8.1 Upgrading the Data Warehouse Schema to Version 7.9.6.4

- 5.10.8.2 Migrating Data into the Upgraded Data Warehouse

- 5.10.8.3 Verifying the Data Migrated Successfully

- 5.11 Upgrading the Data Warehouse Schema and Migrating Data for Teradata Databases

- 5.11.1 Upgrading Oracle BI Applications From Version 7.9.0 to 7.9.6.4

- 5.11.2 Upgrading Oracle BI Applications From Version 7.9.4 to 7.9.6.4

- 5.11.3 Upgrading Oracle BI Applications From Version 7.9.5 to 7.9.6.4

- 5.11.4 Upgrading Oracle BI Applications From Version 7.9.5.1 to 7.9.6.4

- 5.11.5 Upgrading Oracle BI Applications From Version 7.9.6.1 to 7.9.6.4

- 5.11.6 Upgrading Oracle BI Applications From Version 7.9.6.2 to 7.9.6.4

- 5.11.7 Upgrading Oracle BI Applications From Version 7.9.6.3 to 7.9.6.4

- 5.12 Localizing the Policy Store

- 5.13 Importing the Oracle BI Applications Version 7.9.6.4 LDIF File Into the Embedded LDAP Server

- 5.14 Upgrading the Oracle BI Repository and Presentation Catalog to the Oracle BI Enterprise Edition 11g Version

- 5.15 Merging Oracle BI Applications Version 7.9.6.4 Repository With Customer Repository

- 5.15.1 Preparing for the Oracle BI Repository Upgrade

- 5.15.2 Equalizing the Oracle BI Repositories

- 5.15.3 Comparing the Oracle BI Repositories

- 5.15.4 Merging the Oracle BI Repositories

- 5.16 Merging Oracle BI Applications Version 7.9.6.4 Presentation Catalog With Current (Custom) Catalog

- 5.16.1 Trimming the Input Presentation Catalog

- 5.16.2 Merging the Oracle BI Applications Version 7.9.6.4 Presentation Catalog With Current (Custom) Catalog

- 5.16.3 Testing the Results of the Presentation Catalog Upgrade

- 5.17 Regression Testing the Oracle BI Repository Merge

Part II Upgrading When Your Source System Is Oracle EBS

6 Upgrading Oracle BI Applications for Oracle Source Systems

- 6.1 Prerequisites for Upgrading Oracle BI Applications

- 6.2 Upgrading Oracle BI Infrastructure to Version 11g

- 6.3 Upgrading Oracle BI Applications

- 6.4 Upgrading to Informatica PowerCenter Version 9.0.1 Hotfix 2

- 6.5 Upgrading the Informatica Repository

- 6.6 Upgrading the Informatica Repository When You Are Already Running Informatica PowerCenter 9.1

- 6.7 Verifying Configurations for Informatica PowerCenter Version 9.0.1 Hotfix 2 to Work With Oracle BI Applications and DAC

- 6.8 Upgrading to and Configuring DAC Version 11g

- 6.8.1 Installing the DAC Platform and Oracle BI Applications Metadata Repository Files

- 6.8.2 Configuring the DAC Client and Server to Work With Oracle BI Applications and Informatica

- 6.8.3 Upgrading the DAC Repository

- 6.9 Upgrading the Data Warehouse Schema and Migrating Data for Non-Teradata Databases

- 6.9.1 Performing Data Warehouse Schema Upgrade Steps Common to All Previous Releases

- 6.9.2 Upgrading the Data Warehouse Schema From Version 7.9.x to 7.9.3 and Migrating Data

- 6.9.3 Upgrading the Data Warehouse Schema From Version 7.9.3 to 7.9.4 and Migrating Data

- 6.9.4 Upgrading the Data Warehouse Schema From Version 7.9.4 to 7.9.5. and Migrating Data

- 6.9.5 Upgrading the Data Warehouse Schema From Version 7.9.5 to 7.9.5.1 and Migrating Data

- 6.9.6 Upgrading the Data Warehouse Schema From Version 7.9.5.1 to 7.9.6.1 and Migrating Data

- 6.9.6.1 Upgrading the Data Warehouse Schema to Version 7.9.6.1

- 6.9.6.2 Migrating Data into the Upgraded Data Warehouse

- 6.9.6.3 Verifying the Data Migrated Successfully

- 6.9.6.4 Resetting Refresh Dates

- 6.9.7 Upgrading the Data Warehouse Schema From Version 7.9.6 to 7.9.6.1 and Migrating Data

- 6.9.7.1 Upgrading the Data Warehouse Schema to Version 7.9.6.1

- 6.9.7.2 Migrating Data into the Upgraded Data Warehouse

- 6.9.7.3 Verifying the Data Migrated Successfully

- 6.9.8 Upgrading the Data Warehouse Schema From Version 7.9.6.1 to 7.9.6.2 and Migrating Data

- 6.9.8.1 Upgrading the Data Warehouse Schema to Version 7.9.6.2

- 6.9.8.2 Migrating Data into the Upgraded Data Warehouse

- 6.9.8.3 Verifying the Data Migrated Successfully

- 6.9.9 Upgrading the Data Warehouse Schema From Version 7.9.6.2 to 7.9.6.3 and Migrating Data

- 6.9.9.1 Upgrading the Data Warehouse Schema to Version 7.9.6.3

- 6.9.9.2 Migrating Data into the Upgraded Data Warehouse

- 6.9.9.3 Verifying the Data Migrated Successfully

- 6.9.10 Upgrading the Data Warehouse Schema From Version 7.9.6.3 to 7.9.6.4 and Migrating Data

- 6.9.10.1 Upgrading the Data Warehouse Schema to Version 7.9.6.4

- 6.9.10.2 Migrating Data into the Upgraded Data Warehouse

- 6.9.10.3 Verifying the Data Migrated Successfully

- 6.10 Upgrading the Data Warehouse Schema and Migrating Data for Teradata Databases

- 6.10.1 Upgrading Oracle BI Applications From Version 7.9.0 to 7.9.6.4

- 6.10.2 Upgrading Oracle BI Applications From Version 7.9.3 to 7.9.6.4

- 6.10.3 Upgrading Oracle BI Applications From Version 7.9.4 to 7.9.6.4

- 6.10.4 Upgrading Oracle BI Applications From Version 7.9.5 to 7.9.6.4

- 6.10.5 Upgrading Oracle BI Applications From Version 7.9.5.1 to 7.9.6.4

- 6.10.6 Upgrading Oracle BI Applications From Version 7.9.6.1 to 7.9.6.4

- 6.10.7 Upgrading Oracle BI Applications From Version 7.9.6.2 to 7.9.6.4

- 6.10.8 Upgrading Oracle BI Applications From Version 7.9.6.3 to 7.9.6.4

- 6.11 Localizing the Policy Store

- 6.12 Importing the Oracle BI Applications Version 7.9.6.4 LDIF File Into the Embedded LDAP Server

- 6.13 Upgrading the Oracle BI Repository and Presentation Catalog to the Oracle BI Enterprise Edition 11g Version

- 6.14 Merging Oracle BI Applications Version 7.9.6.4 Repository With Customer Repository

- 6.14.1 Preparing for the Oracle BI Repository Upgrade

- 6.14.2 Equalizing the Oracle BI Repositories

- 6.14.3 Comparing the Oracle BI Repositories

- 6.14.4 Merging the Oracle BI Repositories

- 6.15 Merging Oracle BI Applications Version 7.9.6.4 Presentation Catalog With Current (Custom) Catalog

- 6.15.1 Trimming the Input Presentation Catalog

- 6.15.2 Merging the Oracle BI Applications Version 7.9.6.4 Presentation Catalog With Current (Custom) Catalog

- 6.15.3 Testing the Results of the Presentation Catalog Upgrade

- 6.16 Regression Testing the Oracle BI Repository Merge

Part III Upgrading When Your Source System is PeopleSoft

7 Upgrading Oracle BI Applications for PeopleSoft Source Systems

- 7.1 Prerequisites for Upgrading Oracle BI Applications

- 7.2 Upgrading Oracle BI Infrastructure to Version 11g

- 7.3 Upgrading Oracle BI Applications

- 7.4 Upgrading to Informatica PowerCenter Version 9.0.1 Hotfix 2

- 7.5 Upgrading the Informatica Repository

- 7.6 Upgrading the Informatica Repository When You Are Already Running Informatica PowerCenter 9.1

- 7.7 Verifying Configurations for Informatica PowerCenter Version 9.0.1 Hotfix 2 to Work With Oracle BI Applications and DAC

- 7.8 Upgrading to and Configuring DAC Version 11g

- 7.8.1 Installing the DAC Platform and Oracle BI Applications Metadata Repository Files

- 7.8.2 Configuring the DAC Client and Server to Work With Oracle BI Applications and Informatica

- 7.8.3 Upgrading the DAC Repository

- 7.9 Upgrading the Data Warehouse Schema and Migrating Data for Non-Teradata Databases

- 7.9.1 Performing Data Warehouse Schema Upgrade Steps Common to All Previous Releases

- 7.9.2 Upgrading the Data Warehouse Schema From Version 7.9.3 to 7.9.4 and Migrating Data

- 7.9.3 Upgrading the Data Warehouse Schema From Version 7.9.4 to 7.9.5 and Migrating Data

- 7.9.4 Upgrading the Data Warehouse Schema From Version 7.9.5 to 7.9.5.1 and Migrating Data

- 7.9.5 Upgrading the Data Warehouse Schema From Version 7.9.5.1 to 7.9.6.1 and Migrating Data

- 7.9.5.1 Upgrading the Data Warehouse Schema to Version 7.9.6.1

- 7.9.5.2 Migrating Data into the Upgraded Data Warehouse

- 7.9.5.3 Verifying the Data Migrated Successfully

- 7.9.6 Upgrading the Data Warehouse Schema From Version 7.9.6 to 7.9.6.1 and Migrating Data

- 7.9.6.1 Upgrading the Data Warehouse Schema to Version 7.9.6.1

- 7.9.6.2 Migrating Data into the Upgraded Data Warehouse

- 7.9.6.3 Verifying the Data Migrated Successfully

- 7.9.7 Upgrading the Data Warehouse Schema From Version 7.9.6.1 to 7.9.6.2 and Migrating Data

- 7.9.7.1 Upgrading the Data Warehouse Schema to Version 7.9.6.2

- 7.9.7.2 Migrating Data into the Upgraded Data Warehouse

- 7.9.7.3 Verifying the Data Migrated Successfully

- 7.9.8 Upgrading the Data Warehouse Schema From Version 7.9.6.2 to 7.9.6.3 and Migrating Data

- 7.9.8.1 Upgrading the Data Warehouse Schema to Version 7.9.6.3

- 7.9.8.2 Migrating Data into the Upgraded Data Warehouse

- 7.9.8.3 Verifying the Data Migrated Successfully

- 7.9.9 Upgrading the Data Warehouse Schema From Version 7.9.6.3 to 7.9.6.4 and Migrating Data

- 7.9.9.1 Upgrading the Data Warehouse Schema to Version 7.9.6.4

- 7.9.9.2 Migrating Data into the Upgraded Data Warehouse

- 7.9.9.3 Verifying the Data Migrated Successfully

- 7.10 Upgrading the Data Warehouse Schema and Migrating Data for Teradata Databases

- 7.10.1 Upgrading Oracle BI Applications From Version 7.9.3 to 7.9.6.4

- 7.10.2 Upgrading Oracle BI Applications From Version 7.9.4 to 7.9.6.4

- 7.10.3 Upgrading Oracle BI Applications From Version 7.9.5 to 7.9.6.4

- 7.10.4 Upgrading Oracle BI Applications From Version 7.9.5.1 to 7.9.6.4

- 7.10.5 Upgrading Oracle BI Applications From Version 7.9.6.1 to 7.9.6.4

- 7.10.6 Upgrading Oracle BI Applications From Version 7.9.6.2 to 7.9.6.4

- 7.10.7 Upgrading Oracle BI Applications From Version 7.9.6.3 to 7.9.6.4

- 7.11 Localizing the Policy Store

- 7.12 Importing the Oracle BI Applications Version 7.9.6.4 LDIF File Into the Embedded LDAP Server

- 7.13 Upgrading the Oracle BI Repository and Presentation Catalog to the Oracle BI Enterprise Edition 11g Version

- 7.14 Merging Oracle BI Applications Version 7.9.6.4 Repository With Customer Repository

- 7.14.1 Preparing for the Oracle BI Repository Upgrade

- 7.14.2 Equalizing the Oracle BI Repositories

- 7.14.3 Comparing the Oracle BI Repositories

- 7.14.4 Merging the Oracle BI Repositories

- 7.15 Merging Oracle BI Applications Version 7.9.6.4 Presentation Catalog With Current (Custom) Catalog

- 7.15.1 Trimming the Input Presentation Catalog

- 7.15.2 Merging the Oracle BI Applications Version 7.9.6.4 Presentation Catalog With Current (Custom) Catalog

- 7.15.3 Testing the Results of the Presentation Catalog Upgrade

- 7.16 Regression Testing the Oracle BI Repository Merge

Part IV Upgrading When Your Source System is JD Edwards

8 Upgrading Oracle BI Applications for JD Edwards Source Systems

- 8.1 Prerequisites for Upgrading Oracle BI Applications

- 8.2 Upgrading Oracle BI Infrastructure to Version 11g

- 8.3 Upgrading Oracle BI Applications

- 8.4 Upgrading to Informatica PowerCenter Version 9.0.1 Hotfix 2

- 8.5 Upgrading the Informatica Repository

- 8.6 Upgrading the Informatica Repository When You Are Already Running Informatica PowerCenter 9.1

- 8.7 Verifying Configurations for Informatica PowerCenter Version 9.0.1 Hotfix 2 to Work With Oracle BI Applications and DAC

- 8.8 Upgrading to and Configuring DAC Version 11g

- 8.8.1 Installing the DAC Platform and Oracle BI Applications Metadata Repository Files

- 8.8.2 Configuring the DAC Client and Server to Work With Oracle BI Applications and Informatica

- 8.8.3 Upgrading the DAC Repository

- 8.9 Upgrading the Data Warehouse Schema and Migrating Data for Non-Teradata Databases

- 8.9.1 Upgrading the Data Warehouse Schema From Version 7.9.6 to 7.9.6.1 and Migrating Data for Non-Teradata Databases

- 8.9.1.1 Upgrading the Data Warehouse Schema From Version 7.9.6 to 7.9.6.1

- 8.9.1.2 Migrating Data into the Upgraded Data Warehouse

- 8.9.1.3 Verifying the Data Migrated Successfully

- 8.9.2 Upgrading the Data Warehouse Schema From Version 7.9.6.1 to 7.9.6.2 and Migrating Data for Non-Teradata Databases

- 8.9.2.1 Upgrading the Data Warehouse Schema to Version 7.9.6.2

- 8.9.2.2 Migrating Data into the Upgraded Data Warehouse

- 8.9.2.3 Verifying the Data Migrated Successfully

- 8.9.2.4 Resetting Refresh Dates

- 8.9.3 Upgrading the Data Warehouse Schema From Version 7.9.6.2 to 7.9.6.3 and Migrating Data for Non-Teradata Databases

- 8.9.3.1 Upgrading the Data Warehouse Schema to Version 7.9.6.3

- 8.9.3.2 Migrating Data into the Upgraded Data Warehouse

- 8.9.3.3 Verifying the Data Migrated Successfully

- 8.9.4 Upgrading the Data Warehouse Schema From Version 7.9.6.3 to 7.9.6.4 and Migrating Data for Non-Teradata Databases

- 8.9.4.1 Upgrading the Data Warehouse Schema to Version 7.9.6.4

- 8.9.4.2 Migrating Data into the Upgraded Data Warehouse

- 8.9.4.3 Verifying the Data Migrated Successfully

- 8.10 Upgrading the Data Warehouse Schema and Migrating Data for Teradata Databases

- 8.10.1 Upgrading Oracle BI Applications From Version 7.9.6.1 to 7.9.6.4

- 8.10.2 Upgrading Oracle BI Applications From Version 7.9.6.2 to 7.9.6.4

- 8.10.3 Upgrading Oracle BI Applications From Version 7.9.6.3 to 7.9.6.4

- 8.11 Localizing the Policy Store

- 8.12 Importing the Oracle BI Applications Version 7.9.6.4 LDIF File Into the Embedded LDAP Server

- 8.13 Upgrading the Oracle BI Repository and Presentation Catalog to the Oracle BI Enterprise Edition 11g Version

- 8.14 Merging Oracle BI Applications Version 7.9.6.4 Repository With Customer Repository

- 8.14.1 Preparing for the Oracle BI Repository Upgrade

- 8.14.2 Equalizing the Oracle BI Repositories

- 8.14.3 Comparing the Oracle BI Repositories

- 8.14.4 Merging the Oracle BI Repositories

- 8.15 Merging Oracle BI Applications Version 7.9.6.4 Presentation Catalog With Current (Custom) Catalog

- 8.15.1 Trimming the Input Presentation Catalog

- 8.15.2 Merging the Oracle BI Applications Version 7.9.6.4 Presentation Catalog With Current (Custom) Catalog

- 8.15.3 Testing the Results of the Presentation Catalog Upgrade

- 8.16 Regression Testing the Oracle BI Repository Merge

Part V Appendixes

A Setting Parameters in Informatica Parameter Files

- A.1 Setting Common Parameters in Informatica Parameter Files

- A.1.1 Setting Parameters in 793_UPG_PARAMS.txt

- A.1.2 Setting Parameters in 794_UPG_PARAMS.txt

- A.1.3 Setting Parameters in 795_UPG_PARAMS.txt

- A.1.4 Setting Parameters in 7951_UPG_PARAMS.txt

- A.1.5 Setting Parameters in 796_UPG_PARAMS.txt

- A.1.6 Setting Parameters in 7961_UPG_PARAMS.txt

- A.1.7 Setting Parameters in 7962_UPG_PARAMS.txt

- A.1.8 Setting Parameters in 7963_UPG_PARAMS.txt

- A.1.9 Setting Parameters in 7964_UPG_PARAMS.txt

- A.2 Setting Source System-Specific Parameters in Informatica Parameter Files

- A.2.1 Setting Parameters in 796_UPG_PARAMS.txt for Oracle EBS 11i Source Systems

- A.2.2 Setting Parameters in 796_UPG_PARAMS.txt for Siebel Source Systems

- A.2.3 Setting Parameters in 7962_UPG_PARAMS.txt for PeopleSoft Source Systems

- A.2.4 Setting Parameters in 7963_UPG_PARAMS.txt for Siebel Industry Applications Source Systems

- A.3 Setting Application-Specific Parameters in Informatica Parameter Files

- A.3.1 Setting Parameters and Mappings in 796_UPG_PARAMS.txt for Oracle Financial Analytics

- A.3.1.1 Setting Parameters for Value Set Hierarchies and FSG Hierarchies

- A.3.1.2 Setting Parameters for GL Data Extraction

- A.3.1.3 Setting the COGS Fact Mapping for Oracle EBS R12

- A.3.1.4 Setting the $$Hint1 Parameter for Oracle Databases

- A.3.2 Setting Parameters in 796_UPG_PARAMS.txt for Oracle Project Analytics

- A.3.3 Setting Parameters in 796_UPG_PARAMS.txt for Oracle Supply Chain and Order Management Analytics

- A.3.3.1 Setting the TIME_GRAIN Parameter for Sales Order Lines Aggregate Fact and Invoice Lines Aggregate Fact Tables

- A.3.3.2 Setting the $$PERIOD Parameter for the Customer Status History Fact Table

- A.3.4 Setting Parameters and Mappings in 7962_UPG_PARAMS.txt for Oracle Financial Analytics

- A.3.4.1 Setting GL Data Extraction Parameters for Oracle EBS 11i Sources

- A.3.4.2 Setting GL Data Extraction Parameters for Oracle EBS 12 Sources

- A.3.4.3 Setting GL Data Extraction Parameters for PeopleSoft Sources

- A.3.4.4 Setting the COGS Fact Mapping for Oracle EBS R12

- A.3.5 Setting Parameters in 7963_UPG_PARAMS.txt for Oracle Financial Analytics

- A.3.5.1 Setting Parameters for All Source Systems

- A.3.5.2 Setting Parameters Specific to PeopleSoft

- A.3.5.3 Setting Parameters Specific to Oracle EBS 11.5.10 Family Pack OIE.I and OIE.J

- A.3.6 Setting Parameters in 7963_UPG_PARAMS.txt for Oracle Human Resources Analytics

- A.3.7 Setting Parameters in 7963_UPG_PARAMS.txt for Oracle Procurement and Spend Analytics on PeopleSoft Source System

- A.3.8 Setting Parameters in 7963_UPG_PARAMS.txt for Oracle Procurement and Spend Analytics on Oracle EBS 11i and 12 Source Systems

B Generating and Running Scripts to Drop and Create Indexes

- B.1 Generating Scripts to Drop and Create Indexes for Upgrading to Release 7.9.6.2

- B.2 Running the Script to Drop All Indexes for Upgrading to Release 7.9.6.2

- B.3 Running the Scripts to Create ETL and Query Indexes for Upgrading to Release 7.9.6.2

- B.4 Generating Scripts to Drop and Create Query Indexes for Upgrading to Release 7.9.6.3

- B.5 Running the Scripts to Drop and Create Query Indexes for Upgrading to Release 7.9.6.3

- B.6 Generating Scripts to Drop and Create Query and ETL Indexes for Upgrading to Release 7.9.6.4

- B.7 Running the Scripts to Drop and Create Query Indexes for Upgrading to Release 7.9.6.4

- B.8 Running the Scripts to Drop and Create ETL Indexes for Upgrading to Release 7.9.6.4

C Creating Indexes for Oracle Financial Analytics

- C.1 Indexes for SIL_PositionDimension_UPD7962 Mapping

- C.2 Indexes for SIL_PositionDimensionHierarchy_UPD7962 Mapping

D Setting Database-Specific Parameters for the reset_infa_seq_gen.bat File

- D.1 Running reset_infa_seq_gen.bat on Base Informatica Repository

- D.1.1 Entering Values for the reset_infa_seq_gen.bat File on the Base Informatica Repository

- D.1.2 Obtaining ROW_WID from W_ORG_D and W_PRD_OF_WRK_BAND_D

- D.1.3 Obtaining ROW_WID from W_PARTY_D and W_PRD_OF_WRK_BAND_D

- D.2 Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle

- D.2.1 Entering Values for the reset_infa_seq_gen_ORA.bat File on the Base Informatica Repository

- D.2.2 Obtaining ROW_WID from W_ORG_D and W_PRD_OF_WRK_BAND_D

- D.2.3 Obtaining ROW_WID from W_PARTY_D and W_PRD_OF_WRK_BAND_D

- D.3 Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server

- D.3.1 Entering Values for the reset_infa_seq_gen_MSSQL.bat File on the Base Informatica Repository

- D.3.2 Obtaining ROW_WID from W_ORG_D and W_PRD_OF_WRK_BAND_D

- D.3.3 Obtaining ROW_WID from W_PARTY_D and W_PRD_OF_WRK_BAND_D

- D.4 Running reset_infa_seq_gen.bat on Upgrade Informatica Repository

- D.4.1 Entering Values for the reset_infa_seq_gen.bat File on the Upgrade Informatica Repository

- D.4.2 Obtaining ROW_WID from W_ORG_D and W_PRD_OF_WRK_BAND_D

- D.4.3 Obtaining ROW_WID from W_PARTY_D and W_PRD_OF_WRK_BAND_D

- D.5 Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle

- D.5.1 Entering Values for the reset_infa_seq_gen_ORA.bat File on the Upgrade Informatica Repository

- D.5.2 Obtaining ROW_WID from W_ORG_D and W_PRD_OF_WRK_BAND_D

- D.5.3 Obtaining ROW_WID from W_PARTY_D and W_PRD_OF_WRK_BAND_D

- D.6 Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server

- D.6.1 Entering Values for the reset_infa_seq_gen_MSSQL.bat File on the Upgrade Informatica Repository

- D.6.2 Obtaining ROW_WID from W_ORG_D and W_PRD_OF_WRK_BAND_D

- D.6.3 Obtaining ROW_WID from W_PARTY_D and W_PRD_OF_WRK_BAND_D

E Using the DDLimp Utility

- E.1 Using the DDLimp Utility to Run CTL Files

- E.2 Additional DDLimp Commands

F Creating ODBC Database Connections for DAC

- F.1 Creating ODBC Connections for Oracle Databases

- F.2 Creating ODBC Connections for DB2 Databases

- F.3 Creating ODBC Connections for SQL Server Databases

- F.4 Creating ODBC Connections for Teradata Databases

G Upgrading the Oracle BI Repository for Industry-Specific Analytics Applications

- G.1 Common Dimensions

- G.2 Merging Siebel Analytics and Oracle BI Repositories

- G.2.1 Creating Working Folders

- G.2.2 Trimming Repository Files

- G.2.2.1 Trimming the Original Base Repository Files

- G.2.2.2 Trimming the New Base Repository File

- G.2.2.3 Trimming the Custom Repository Files

- G.2.3 Renaming Objects in the Original Pharma Base Repository File

- G.2.4 Equalizing the Oracle BI Repositories

- G.2.5 Merging the Core Repository Files

- G.2.6 Merging the Pharma Repository Files

- G.2.7 Making Merge Decisions in the Administration Tool

- G.3 Replacing Common Dimensions After the Repository Merge

Index

List of Figures

- 2-1 Oracle BI Applications Upgrade Flow

- G-1 Phases of Repository Merge for Pharma Analytics

List of Tables

- 2-1 Major Stages of the Oracle BI Applications Upgrade and Related Documentation

- 3-1 Names of Analytics Repositories used in Examples

- 3-2 Rename MAP Files to Be Used for Various Releases

- 4-1 Names of Analytics Repositories used in Examples

- 4-2 Rename MAP Files to Be Used for Various Releases

- 5-1 Names of Analytics Repositories used in Examples

- 5-2 Rename MAP Files to Be Used for Various Releases

- 6-1 Names of Analytics Repositories used in Examples

- 6-2 Rename MAP Files to Be Used for Various Releases

- 7-1 Names of Analytics Repositories used in Examples

- 7-2 Rename MAP Files to Be Used for Various Releases

- 8-1 Names of Analytics Repositories used in Examples

- 8-2 Rename MAP Files to Be Used for Various Releases

- D-1 Oracle Database Parameter Settings for reset_infa_seq_gen.bat

- D-2 SQL Server Database Parameter Settings for reset_infa_seq_gen.bat

- D-3 IBM DB2 Database Parameter Settings for reset_infa_seq_gen.bat

- D-4 Teradata Database Parameter Settings for reset_infa_seq_gen_ORA.bat

- D-5 Teradata Database Parameter Settings for reset_infa_seq_gen_MSSQL.bat

- D-6 Oracle Database Parameter Settings for reset_infa_seq_gen.bat

- D-7 SQL Server Database Parameter Settings for reset_infa_seq_gen.bat

- D-8 IBM DB2 Database Parameter Settings for reset_infa_seq_gen.bat

- D-9 Teradata Database Parameter Settings for reset_infa_seq_gen_ORA.bat

- D-10 Teradata Database Parameter Settings for reset_infa_seq_gen_MSSQL.bat

- G-1 Common Pharma Analytics Dimensions

- G-2 Common Consumer Sector Analytics Dimensions

- G-3 Common Vehicle Sales Analytics Dimensions

- G-4 Phase 1 Repository Files

- G-5 Phase 2 Repository Files

- G-6 Rename MAP Files to Be Used for Various Releases

- G-7 Names for Pharma Analytics Common Dimensions in Pre-7.9.4 Releases

- G-8 Names for Consumer Sector Analytics Common Dimensions in Pre-7.9.5 Releases

- G-9 Names for Vehicle Sales Analytics Common Dimensions in Pre-7.9.5 Releases

Oracle® Business Intelligence Applications

Upgrade Guide for Informatica PowerCenter Users

Release 7.9.6.4

E35270-01

November 2012

Explains how to upgrade Oracle Business Intelligence Applications.

Oracle Business Intelligence Applications Upgrade Guide for Informatica PowerCenter Users, Release 7.9.6.4

E35270-01

Copyright © 2010, 2012, Oracle and/or its affiliates. All rights reserved.

Primary Author:  Jill Arehart

Contributors: Oracle Business Intelligence development, product management, and quality assurance teams.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Preface

Oracle Business Intelligence Applications are comprehensive prebuilt solutions that deliver pervasive intelligence across an organization, empowering users at all levels — from front line operational users to senior management — with the key information they need to maximize effectiveness. Intuitive and role-based, these solutions transform and integrate data from a range of enterprise sources, including Siebel, Oracle, PeopleSoft, JD Edwards, and corporate data warehouses — into actionable insight that enables more effective actions, decisions, and processes.

Oracle BI Applications are built on Oracle Business Intelligence Suite Enterprise Edition, a comprehensive next-generation BI and analytics platform.

Oracle BI Applications includes the following:

- Oracle Contact Center Telephony Analytics

- Oracle Financial Analytics

- Oracle Manufacturing Analytics

- Oracle Enterprise Asset Management Analytics

- Oracle Human Resources Analytics

- Oracle Loyalty Analytics

- Oracle Marketing Analytics

- Oracle Pharma Marketing Analytics

- Oracle Pharma Sales Analytics

- Oracle Price Analytics

- Oracle Procurement and Spend Analytics

- Oracle Project Analytics

- Oracle Sales Analytics

- Oracle Service Analytics

- Oracle Supply Chain and Order Management Analytics

For more details on the applications included in this release of Oracle BI Applications, see the Oracle Business Intelligence Applications Licensing and Packaging Guide. This guide is included in the Oracle Business Intelligence Media Pack. Also, see the System Requirements and Supported Platforms for Oracle Business Intelligence Applications, available at available at http://www.oracle.com/technetwork/middleware/bi-foundation/documentation/bi-apps-098545.html.

Oracle recommends reading the Oracle Business Intelligence Applications Release Notes before installing, using, or upgrading Oracle BI Applications. The most current version of the Oracle Business Intelligence Applications Release Notes is available on the Oracle Technology Network at http://www.oracle.com/technetwork/middleware/bi-foundation/documentation/bi-apps-098545.html. To register for a free account on the Oracle Technology Network, go to http://www.oracle.com/technetwork/index.html.

Audience

This document is intended for BI managers and implementors of Oracle BI Applications.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Related Documents

For more information, see the following Oracle BI Applications documentation set, available at http://www.oracle.com/technetwork/middleware/bi-foundation/documentation/bi-apps-098545.html:

- Oracle Business Intelligence Applications Release Notes

- System Requirements and Supported Platforms for Oracle Business Intelligence Applications

- Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users

- Oracle Business Intelligence Applications Configuration Guide for Informatica PowerCenter Users

- Oracle Business Analytics Warehouse Data Model Reference

- Oracle Business Intelligence Applications Security Guide

Also see the Oracle Business Intelligence Data Warehouse Administration Console documentation set, available at http://www.oracle.com/technetwork/middleware/bi-foundation/documentation/index.html:

- Oracle Business Intelligence Data Warehouse Administration Console Release Notes

- System Requirements and Supported Platforms for Oracle Business Intelligence Data Warehouse Administration Console

- Oracle Business Intelligence Data Warehouse Administration Console User's Guide

Conventions

The following text conventions are used in this document:

Convention

Meaning

boldface

Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.

italic

Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.

monospace

Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

1 What's New in This Release

This chapter lists changes described in this version of the documentation to support release 7.9.6.4 of the software.

This chapter contains the following topics:

- Section 1.1, "What's New in Oracle BI Applications Release 7.9.6.4"

1.1 What's New in Oracle BI Applications Release 7.9.6.4

Upgrade Guide for Informatica PowerCenter Users includes the following changes:

- This guide has been updated to include instructions for upgrading to Oracle BI Applications release 7.9.6.4 for all source systems.

2 Overview of Oracle BI Applications Upgrade

This chapter provides an overview of the Oracle Business Intelligence Applications upgrade process.

This chapter contains the following topics:

- Section 2.1, "Supported Upgrade Paths"

- Section 2.2, "Why Upgrade to Oracle BI Applications Release 7.9.6.4?"

- Section 2.3, "Considerations About Upgrading to Oracle BI Enterprise Edition 11g"

- Section 2.4, "Considerations About Upgrading Oracle BI Applications"

- Section 2.5, "Best Practices for Preparing to Upgrade"

- Section 2.6, "Major Stages of Oracle BI Applications Upgrade"

Note:

Upgrading Oracle BI Applications requires careful planning and testing. You must allocate sufficient time for implementing the upgrade. It is highly recommended that customers consider obtaining support from Oracle Consulting Services to assist with an applications upgrade.

Also note that the process of upgrading to Oracle BI Applications release 7.9.6.4 includes an upgrade of the Oracle Business Intelligence platform to Oracle Business Intelligence Enterprise Edition 11g (11.1.1.6.4)

2.1 Supported Upgrade Paths

The Oracle Business Intelligence Applications Upgrade Guide for Informatica PowerCenter Users provides instructions for upgrading to the current release of Oracle BI Applications from the previous releases listed below:

- Siebel Analytics 7.5.3
For instructions, see Chapter 3, "Upgrading Siebel Analytics 7.5.x."

- Siebel Business Analytics 7.7, 7.7.x and 7.8.x
For instructions, see Chapter 4, "Upgrading Siebel Business Analytics 7.7, 7.7.x and 7.8.x."

- Siebel Business Analytics for Life Sciences 7.8.0, 7.8.1 and 7.8.2
For instructions, see Chapter 4, "Upgrading Siebel Business Analytics 7.7, 7.7.x and 7.8.x."

- Oracle Business Intelligence Applications 7.9.0 through 7.9.6.3
For instructions, see one of the following chapters, depending on your source system:

- Chapter 5, "Upgrading Oracle BI Applications 7.9.x for Siebel Source Systems"

- Chapter 6, "Upgrading Oracle BI Applications for Oracle Source Systems"

- Chapter 7, "Upgrading Oracle BI Applications for PeopleSoft Source Systems"

- Chapter 8, "Upgrading Oracle BI Applications for JD Edwards Source Systems"

2.2 Why Upgrade to Oracle BI Applications Release 7.9.6.4?

There can be many reasons your organization would consider upgrading to Oracle BI Applications release 7.9.6.4, including, but not limited to, the following:

- An upgrade of the transactional applications can trigger a need to upgrade Oracle BI Applications to the latest release. However, it is not always necessary to upgrade Oracle BI Applications if you upgrade the transactional applications. For example, if both the version of transactional applications from which you are upgrading and to which you are upgrading are supported by the release of Oracle BI Applications you are using, you do not need to upgrade Oracle BI Applications to the latest release.

- A strong need to leverage new features and enhancements offered by Oracle BI Enterprise Edition 11g (11.1.1.6.4), including support for newer versions of databases.

- New features and enhancements offered by Oracle BI Applications, including new application content, support for newer versions of source systems, support for new versions of databases, and language support.

- Potential cost savings on additional maintenance costs in the event that support is no longer available for the transactional applications, the database version, or the Informatica version.

- Business requirements.

2.2.1 Upgrade Options

The most common triggers for upgrading Oracle BI Applications are an upgrade of the underlying transactional source system or systems, the need to take advantage of new content in the latest version of Oracle BI Applications, and support for new database platforms or operating systems.

While upgrading only the Oracle Business Intelligence Foundation to leverage several enhancements offered in Oracle BI Enterprise Edition 11g (11.1.1.6.4) is a supported option, note that only Oracle BI Applications release 7.9.6.4 is certified on Oracle BI Enterprise Edition 11g (11.1.1.6.4). Previous releases of Oracle BI Applications are not certified on Oracle BI Enterprise Edition 11g. Unless you have a compelling need to leverage the enhancements offered in Oracle BI Enterprise Edition 11g (11.1.1.6.4), suitable options worth considering are 1) staying on Oracle BI Enterprise Edition 10g, or 2) upgrading Oracle BI Enterprise Edition as part of an integral upgrade along with Oracle BI Applications.

As with any upgrade, Oracle recommends that Oracle BI Applications customers who currently use Oracle BI Enterprise Edition 10g do a thorough cost-benefit analysis before considering an upgrade to Oracle BI Enterprise Edition 11g (11.1.1.6.4).

2.3 Considerations About Upgrading to Oracle BI Enterprise Edition 11g

Upgrading to Oracle BI Applications release 7.9.6.4 requires an upgrade of the Oracle Business Intelligence Foundation to Oracle BI Enterprise Edition 11g (11.1.1.6.4).

Upgrading Oracle Business Intelligence from 10g to 11g is a substantial project, requiring the need to budget sufficient time and resources for analysis, implementation, and verification of the upgrade. Oracle provides tools and technology to automate much of the upgrade process. However, the precise strategy that you will want to adopt will depend both on the configuration of the existing 10g system, and on the required configuration of the upgraded 11g system. Before performing the platform upgrade, you should thoroughly review Oracle Fusion Middleware Upgrade Guide for Oracle Business Intelligence 11g Release 1 (11.1.1), and carefully read the chapter titled, "Planning to Upgrade from Oracle BI 10g to BI 11g."

Oracle BI Applications customers upgrading to the Oracle Business Intelligence Foundation to Oracle BI Enterprise Edition 11g (11.1.1.6.4) should note that the BI Server in Oracle BI Enterprise Edition 11g (11.1.1.6.4) is more stringent in its metadata validation checks and produces a number of warnings on the repositories that are upgraded from earlier Oracle BI Applications releases. These warnings can be fixed manually. For more information about these warning and for the workarounds to fix the issues, see Oracle Business Intelligence Applications Release Notes.

In addition, Oracle BI Enterprise Edition 11g (11.1.1.6.4) includes changes and enhancements that affect the look, feel, and behavior of dashboards and reports. For a description of these changes, see the section titled "Appendix B: Possible Changes in Oracle BI Enterprise Edition Appearance and Behavior After Upgrade," in Oracle Fusion Middleware Upgrade Guide for Oracle Business Intelligence 11g Release 1 (11.1.1).

You should also be aware of the following security-related changes in Oracle BI Enterprise Edition 11g (11.1.1.6.4):

- Repositories now have repository-specific passwords that are used to encrypt the repository contents. The repository password is stored in an external credential store when you publish a repository in Fusion Middleware Control, so that the Oracle BI Server can retrieve the password to load the repository.

- Groups no longer exist in the repository as objects. Instead, you implement data access security based on the application roles to which a user belongs.

- Application roles are managed in an external policy store. Application role objects exist in the repository, but these objects are pointers (references) to the externally managed roles.

- Users are managed in an external authentication provider and are no longer managed in the repository. User objects exist in the repository, but these objects are pointers (references) to the externally managed users.

See Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition for more information about these and other security-related changes.

2.4 Considerations About Upgrading Oracle BI Applications

You should consider the following points before you begin your upgrade:

- Review the System Requirements and Supported Platforms for Oracle Business Intelligence Applications to make sure your database platform versions are supported.

- The upgrade process is not only a technical process. It requires significant planning and involvement from many teams, including development, database administrators, business analysts, QA, and so on.

- You should determine what customizations were made to your existing application before you begin the upgrade process. It is recommended that you budget sufficient time (in the upgrade project) for detailed review of current customizations and relevance of the customizations for the new version of the application to which you plan to upgrade.

- You will also need to analyze the impact of the schema changes on your current custom implementation. The extent of your customizations will have an impact on the length of time required for the upgrade.

- At different stages of the upgrade you will also need to analyze your organization's business requirements. For example, at the stage in which you are upgrading the Oracle Business Intelligence repository, you will need to know which repository objects are not in use so that they can be trimmed from the repository. To determine this information, you will need to know what reports are in use.

- Depending on the release from which you are upgrading, moving the customizations in your existing repositories, reports, and dashboards to the new version may require a multi-step process and may involve manual processes at some stages.

- It is highly recommended that you use side-by-side environments when performing each stage of the upgrade process. Enabling side-by-side-instances of the entire Oracle BI Applications environment is a critical success factor for upgrade.
For some stages of the upgrade, you can upgrade your environments in place. However, for comparison and benchmarking purposes, it is recommended that you upgrade using side-by-side environments.

- For each stage of the upgrade process, you need to allocate a reasonable amount of time to validate the results of that stage and address any problems. In addition, final user acceptance testing must confirm that the entire upgrade process was successful.

- When you move from a development environment to test or production environments, you must perform the following stages of the upgrade process for each environment:

- Upgrade the Oracle Business Intelligence platform

- Upgrade Oracle BI Applications

- Migrate the data

- You can migrate the DAC, Informatica, and Oracle BI repositories, and the presentation catalogs into the production environment after you merge and test them.

2.5 Best Practices for Preparing to Upgrade

This section provides best practice steps you need to perform before you begin the upgrade process.

- Review this guide, Oracle Business Intelligence Applications Upgrade Guide for Informatica PowerCenter Users, in its entirety.

- Rename and copy into a different location your current repositories, presentation catalog (formerly known as the Web Catalog), and DAC installation folder from your existing environment. The file names and locations listed below represent the standard names and locations of files that shipped with previous versions of Siebel Business Analytics Applications and Oracle BI Applications.
When you back up the DAC Repository, you export the DAC metadata, in XML format (using the DAC's Export tool), into a different database, which can be used later as a reference. For instructions, see the Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Data Warehouse Administration Console.

Type

File or Folder

Default BI 10g Location

DAC metadata repository

*.xml

OracleBI\dac\export

Note: This is the directory into which you copied the DAC metadata files after you installed DAC.

Oracle BI Repository (formerly called Siebel Analytics Repository)

Oracle BI Repository (or Siebel Analytics Repository) you are currently using

OracleBI\server\Repository

Informatica Repository

Informatica Repository file (for example, Oracle_BI_DW_Base.rep)

OracleBI\dwrep\Informatica\Repository

Presentation Catalog (formerly called Web Catalog)

Presentation Catalog (or Web Catalog) you are currently using

OracleBIData\web\catalog

DAC installation folder

dac

OracleBI\dac

- Gather information that describes the current implementation, including the following:

- Version of the transactional database to which you upgraded.

- Version of the Oracle BI Enterprise Edition (platform) or Siebel Business Analytics platform from which you are upgrading.
To determine the platform version from which you are upgrading, launch the Administration Tool, and click Help, and then click Administration Tool in the toolbar. A message box provides the platform version.

- Version of Siebel Business Analytics Applications or Oracle BI Applications from which you are upgrading.
To determine the version of Siebel Business Analytics Applications or Oracle BI Applications from which you are upgrading, launch the Data Warehouse Administration Console (DAC), and click Help, and then click About DAC.

Note:

If DAC is not a component of your Analytics installation, you are running Siebel Analytics 7.5.x.

2.6 Major Stages of Oracle BI Applications Upgrade

This section describes the major stages of the Oracle BI Applications upgrade process and includes the following topics:

- Section 2.6.1, "Sequence of Upgrade Stages"

- Section 2.6.2, "Documentation Related to the Major Stages of the Upgrade Process"

Note:

iBots (agents) are not included in the standard (out-of-the-box) Oracle BI Applications product. However, you can upgrade a 10g Scheduler schema to 11g. For more information, see Oracle Fusion Middleware Upgrade Guide for Oracle Business Intelligence 11g Release 1 (11.1.1).

2.6.1 Sequence of Upgrade Stages

Figure 2-1 shows the upgrade flow for the major stages of the Siebel Business Analytics and Oracle BI Applications upgrade process. Depending on the prior release from which you are upgrading, you may find minor changes in the process shown in Figure 2-1.

Figure 2-1 Oracle BI Applications Upgrade Flow

In general, you must complete stages one through five sequentially, in the following order:

- Stage 1: Upgrade the Siebel Business Analytics platform or Oracle BI platform to Oracle Business Intelligence Enterprise Edition 11g (11.1.1.6.4). See Section 2.3, "Considerations About Upgrading to Oracle BI Enterprise Edition 11g" for important information about this upgrade process.

- Stage 2: Upgrade the following:

- Siebel Business Analytics Applications or Oracle BI Applications to the current release of Oracle BI Applications

- Informatica PowerCenter to version 9.01 Hotfix 2

- DAC platform to release 11g (11.1.1.6.4)

- Stage 3: Upgrade the metadata in the DAC and Informatica repositories.

- Stage 4: Upgrade the data warehouse schema.

- Stage 5: (For Siebel source systems) upgrade the Siebel transactional database schema.

After completing stage 4 or stage 5 for Siebel source systems, you can then perform the next three stages simultaneously:

- Stage 6: Migrate data into the upgraded data warehouse. Note that for testing purposes, you can migrate a subset of data and study the results before migrating all of the data.

- Stage 7: Import the Oracle BI Applications release 7.9.6.4 LDIF file into the embedded LDAP Server.

- Stage 8: Use the Oracle BI Enterprise Edition 11g Upgrade Assistant to upgrade the following repositories and presentation catalog (or Siebel Analytics Web catalog) from the 10g format to the 11g format:

- The Oracle BI repository you are currently using (the repository that includes your customizations).

- The standard (out-of-the-box) Oracle BI repository version 7.9.x (the version from which you are upgrading).

- The presentation catalog you are currently using.

Note: Your current policy store will be merged with the Oracle BI Applications release 7.9.6.4 policy store while upgrading the Oracle BI repository from the 10g format to the 11g format. The final policy store will be the super set of Oracle BI Applications release 7.9.6.4 policy store and the custom and current policy information from the 10g repository.

Also, your current users and groups from the repository will be merged with the Oracle BI Applications release 7.9.6.4 identity store while upgrading the Oracle BI repository from the 10g format to the 11g format. The final identity store will be the super set of the Oracle BI Applications release 7.9.6.4 identity store and the identity store information (users and groups) from the 10g repository.

After you complete stage 8, you can perform stages 9 and 10 simultaneously:

- Stage 9: Merge your customizations of a prior release of the Oracle BI repository with the new release of the Oracle BI repository.
See the section titled "Understanding the Upgrade of Repository Metadata," in the Oracle Fusion Middleware Upgrade Guide for Oracle Business Intelligence 11g Release 1 (11.1.1) for information about Oracle BI Enterprise Edition platform behavior related to the upgrade of the Oracle BI repository.

- Stage 10: Merge your customizations of a prior release of the presentation catalog with the new release of the presentation catalog.
See the section titled "Understanding Oracle BI Presentation Catalog Upgrade," in the Oracle Fusion Middleware Upgrade Guide for Oracle Business Intelligence 11g Release 1 (11.1.1) for information about Oracle BI Enterprise Edition platform behavior related to the upgrade of the Siebel Analytics Web Catalog and the Oracle BI Presentation Catalog.

Note:

Depending on the prior release from which you are upgrading, you may find minor changes in the process described in this section.

Note:

The schema and data are upgraded in place and affect only the preconfigured (out-of-the-box) content. Customizations to the schema are not affected by the upgrade process.

2.6.2 Documentation Related to the Major Stages of the Upgrade Process

Table 2-1 provides the documentation you should refer to for each stage of the upgrade.

Table 2-1 Major Stages of the Oracle BI Applications Upgrade and Related Documentation

Stage

Documentation Related to Stage

Stage 1: Upgrade the Siebel Business Analytics platform or Oracle BI Enterprise Edition platform to Oracle BI Enterprise Edition 11g (11.1.1.6.4).

- Oracle Fusion Middleware Upgrade Guide for Oracle Business Intelligence

Note: You should carefully review the chapter titled, "Planning to Upgrade from Oracle BI 10g to BI 11g" before beginning the upgrade process.

Stage 2: Upgrade the following:

- Siebel Business Analytics Applications or Oracle BI Applications to the current release of the Oracle BI Applications

- Informatica PowerCenter

- DAC platform

- Oracle Business Intelligence Applications Upgrade Guide for Informatica PowerCenter Users
This guide (the guide you are currently reading) provides instructions for the upgrade based on the source system. Follow the steps described in the appropriate chapter for your source system:

Stage 3: Upgrade the metadata in the DAC and Informatica repositories.

- Oracle Business Intelligence Applications Upgrade Guide for Informatica PowerCenter Users

- Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Data Warehouse Administration Console

Stage 4: Upgrade the data warehouse schema.

- Oracle Business Intelligence Applications Upgrade Guide for Informatica PowerCenter Users

Stage 5: (For Siebel source systems only) Upgrade the Siebel transactional database schema.

- Oracle Business Intelligence Applications Upgrade Guide for Informatica PowerCenter Users

Stage 6: Migrate data into the upgraded data warehouse.

- Oracle Business Intelligence Applications Upgrade Guide for Informatica PowerCenter Users

Stage 7: Import the Oracle BI Applications release 7.9.6.4 LDIF file into the embedded LDAP Server.

- Oracle Business Intelligence Applications Upgrade Guide for Informatica PowerCenter Users

Stage 8: Upgrade the Oracle BI repositories and presentation catalog from the 10g format to the 11g format.

- Oracle Business Intelligence Applications Upgrade Guide for Informatica PowerCenter Users

Stage 9: Merge the Siebel Analytics repository or Oracle BI repository with the new version installed with the current release.

- Oracle Business Intelligence Applications Upgrade Guide for Informatica PowerCenter Users

- Oracle Fusion Middleware Upgrade Guide for Oracle Business Intelligence

Stage 10: Merge the Siebel Business Analytics Web Catalog or Oracle BI presentation catalog with the new version installed with the current release.

- Oracle Business Intelligence Applications Upgrade Guide for Informatica PowerCenter Users

- Oracle Fusion Middleware Upgrade Guide for Oracle Business Intelligence

Part I

Upgrading When Your Source System is Siebel CRM

Part I contains instructions for upgrading to the current release of Oracle BI Applications from previous releases of Oracle BI Applications, Siebel Business Analytics, and Siebel Analytics.

Part I contains the following sections:

- Chapter 3, "Upgrading Siebel Analytics 7.5.x"
Follow the instructions in this section for upgrading to the current release of Oracle BI Applications from Siebel Analytics 7.5.x.

- Chapter 4, "Upgrading Siebel Business Analytics 7.7, 7.7.x and 7.8.x"
Follow the instructions in this section for upgrading to the current release of Oracle BI Applications from Siebel Business Analytics 7.7, 7.7.x, and 7.8.x.

- Chapter 5, "Upgrading Oracle BI Applications 7.9.x for Siebel Source Systems"
Follow the instructions in this section for upgrading to the current release from previous releases of Oracle BI Applications if your source system is Siebel CRM.

3 Upgrading Siebel Analytics 7.5.x

This chapter contains instructions for upgrading Oracle's Siebel Analytics release 7.5.x.

This chapter contains the following topics:

- Section 3.1, "Prerequisites for Upgrading Oracle BI Applications"

- Section 3.2, "Upgrading Oracle BI Infrastructure to Version 11g"

- Section 3.3, "Upgrading Oracle BI Applications"

- Section 3.4, "Upgrading to Informatica PowerCenter Version 9.0.1 Hotfix 2"

- Section 3.5, "Upgrading the Informatica Repository"

- Section 3.6, "Upgrading the Informatica Repository When You Are Already Running Informatica PowerCenter 9.1"

- Section 3.7, "Verifying Configurations for Informatica PowerCenter Version 9.0.1 Hotfix 2 to Work With Oracle BI Applications and DAC"

- Section 3.8, "Installing and Configuring DAC 11g"

- Section 3.9, "Overview of Upgrading the Data Warehouse Schema and Migrating Data"

- Section 3.10, "Upgrading the Data Warehouse Schema to Version 7.7 and Migrating Data"

- Section 3.11, "Upgrading the Data Warehouse Schema to Version 7.9.0"

- Section 3.12, "Importing New Schema Definitions into the Siebel Transactional Database"

- Section 3.13, "Migrating Data into the Data Warehouse Upgraded to Version 7.9.0"

- Section 3.14, "Upgrading the Data Warehouse Schema to Version 7.9.4 and Migrating Data"

- Section 3.15, "Upgrading the Data Warehouse Schema to Version 7.9.5 and Migrating Data"

- Section 3.16, "Upgrading the Data Warehouse Schema to Version 7.9.5.1"

- Section 3.17, "Upgrading the Data Warehouse Schema From Version 7.9.5.1 to 7.9.6.1 and Migrating Data"

- Section 3.18, "Upgrading the Data Warehouse Schema From Version 7.9.6 to 7.9.6.1"

- Section 3.19, "Upgrading the Data Warehouse Schema From Version 7.9.6.1 to 7.9.6.2 and Migrating Data"

- Section 3.20, "Upgrading the Data Warehouse Schema From Version 7.9.6.2 to 7.9.6.3 and Migrating Data"

- Section 3.21, "Upgrading the Data Warehouse Schema From Version 7.9.6.3 to 7.9.6.4 and Migrating Data"

- Section 3.22, "Localizing the Policy Store"

- Section 3.23, "Importing the Oracle BI Applications Version 7.9.6.4 LDIF File Into the Embedded LDAP Server"

- Section 3.24, "Upgrading the Siebel Analytics Repository and Web Catalog to the Oracle BI Enterprise Edition 11g Version"

- Section 3.25, "Merging Oracle BI Applications Version 7.9.6.4 Repository With Customer Repository"

- Section 3.26, "Merging Oracle BI Applications Version 7.9.6.4 Presentation Catalog With Current (Custom) Catalog"

- Section 3.27, "Regression Testing the Oracle BI Repository Merge"

3.1 Prerequisites for Upgrading Oracle BI Applications

Complete the following prerequisites before upgrading to Oracle BI Applications release 7.9.6.4:

- The DAC Client requires an ODBC connection to the Oracle Business Analytics Warehouse when the database type is Oracle, SQL Server, DB2, and DB2-390 in order to upgrade the data warehouse schema using the DDL Import Utility.
Additionally, Siebel CRM source systems require an ODBC connection to the OLTP (source) database on the machine where Oracle BI Applications software is installed. This ODBC connection will be used by the DDLIMP utility.

Before you upgrade to Oracle BI Applications verify whether you have the appropriate ODBC connections set. If you do not, see Appendix F, "Creating ODBC Database Connections for DAC."

3.2 Upgrading Oracle BI Infrastructure to Version 11g

You must upgrade Oracle BI Infrastructure to version 11g. For the specific release of Oracle BI Infrastructure 11g that is supported for this release of Oracle BI Applications, see the System Requirements and Supported Platforms for Oracle Business Intelligence Applications. For information on installing the supported version of Oracle BI Infrastructure, see the Oracle Fusion Middleware Upgrade Guide for Oracle Business Intelligence.

3.3 Upgrading Oracle BI Applications

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 Guide for Informatica PowerCenter Users.

Note the following points:

- Review "Chapter 3: Preinstallation and Predeployment Requirements for Oracle BI Applications," in the Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users. You must satisfy these requirements in order to upgrade to the current version of Oracle BI Applications.

- Perform only the step that addresses the running of the installer. Do not perform the configuration instructions that follow the running of the installer.

- If you have a previous release of Oracle BI Applications installed, you must uninstall it before you run the installer for the current release. If you do not uninstall the old release, some folders from the current release will not be correctly installed. (Make a back-up of your DAC folder before you uninstall the old release. This will be the backup of your DAC Client and Server and the DAC metadata files.)

3.4 Upgrading to Informatica PowerCenter Version 9.0.1 Hotfix 2

You must install Informatica PowerCenter 9.0.1 Hotfix 2 to run the current version of Oracle BI Applications. See the System Requirements and Supported Platforms for Oracle Business Intelligence Applications for information about additional hotfixes or emergency bug fixes that may be required to support the current version of Informatica.

Note:

Oracle BI Applications release 7.9.6.4 is also certified to run with Informatica PowerCenter version 9.1 Hotfix 2. For instructions on upgrading the Informatica Repository if you have previously upgraded to Informatica PowerCenter 9.1 Hotfix 2, see Section 3.6, "Upgrading the Informatica Repository When You Are Already Running Informatica PowerCenter 9.1."

The components and architecture for Informatica PowerCenter 9.x differ significantly from Informatica PowerCenter 7.x and 8.x. Oracle recommends that you carefully review the Informatica PowerCenter 9.0.1 documentation.

For a summary of installation instructions for installing Informatica PowerCenter 9.0.1 on a single machine in an Oracle BI Applications deployment, see the Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users.

For detailed information about deploying Informatica PowerCenter 9.0.1, refer to the Informatica PowerCenter Installation and Configuration Guide, Informatica Upgrade Guide for PowerCenter 8.1.x, Informatica Upgrade Guide for PowerCenter 8.5.x and 8.6.x, Informatica Administrator Guide, and related documentation. See the Oracle Business Intelligence Applications Release Notes, available on the Oracle Technology Network, for information about how to locate the Informatica documentation.

To upgrade to Informatica PowerCenter 9.0.1 Hotfix 2:

- Perform the pre-upgrade, upgrade, and post-upgrade steps documented in Informatica Upgrade Guide for PowerCenter 8.1.x or Informatica Upgrade Guide for PowerCenter 8.5.x and 8.6.x, depending on which version of Informatica PowerCenter you are upgrading from.

Note the following points:

- The Informatica PowerCenter 9.0.1 installation process includes upgrading your current Informatica Repository to the version 9.0.1 format. This process is necessary so that you will be able to access your current repository using the version 9.0.1 client tools and so that you can perform the procedure Section 3.5, "Upgrading the Informatica Repository."
In Section 3.5, "Upgrading the Informatica Repository," you back up and rename your current repository and then restore the Informatica Repository that is installed during the Oracle BI Applications installation (for example, Oracle_BI_DW_Base.rep). You then copy the folders containing the Oracle BI Applications content for release 7.9.6.4 to your existing repository.

- If you install Informatica PowerCenter 9.0.1 using the installer Upgrade option rather than the Install option, the property $PMRootDir is not updated to the upgraded service version installation directory. You need to configure this property to specify the upgraded service installation directory in order for DAC to be able to locate the Informatica source files.
To configure the $PMRootDir property: launch Informatica Administrator, select the Integration Service from the Navigator, click the Processes tab, and click Edit. Then, enter the appropriate value for $PMRootDir.

3.5 Upgrading the Informatica Repository

Follow this procedure to upgrade the Informatica Repository when you are upgrading the Informatica PowerCenter platform from version 7.x or 8.x to 9.0.1 Hotfix 2. If you have already upgraded to Informatica PowerCenter 9.1, follow the procedure in Section 3.6, "Upgrading the Informatica Repository When You Are Already Running Informatica PowerCenter 9.1."

In this procedure, you will copy the folders containing the Oracle BI Applications 7.9.6.4 content into your current, existing Informatica Repository. The result of this action is an Informatica Repository that contains your customizations along with the new Oracle BI Applications 7.9.6.4 content.

For detailed instructions on backing up and restoring the Informatica Repository, see the topic titled, "Backing Up and Restoring the PowerCenter Repository," in "Chapter 15: PowerCenter Repository Management," in the Informatica PowerCenter Administrator Guide. See the Oracle Business Intelligence Applications Release Notes, available on the Oracle Technology Network, for information about how to locate the Informatica documentation.

To upgrade the Informatica Repository:

1. Make sure you have backed up and renamed your current, existing Informatica Repository.

2. Copy the Oracle_BI_DW_Base.rep file (or Oracle_BI_DW_Teradata.rep for repositories on Teradata databases) from the folder OracleBI\dwrep\Informatica\Repository into the folder <INFA_HOME>\server\infa_shared\Backup.

Note:

The Oracle_BI_DW_Base.rep file is installed in the OracleBI root directory when you run the Oracle BI Applications installer, as described in Section 3.3, "Upgrading Oracle BI Applications."

3. Using Informatica PowerCenter Administrator, create a new Repository Service for the Oracle_BI_DW_Base.rep repository. See "Setup Step: Creating the Informatica Repository Service," in Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users for instructions.

4. Using the Repository Service you created in the step above, restore the Oracle_BI_DW_Base.rep repository into an empty schema. See "Restoring the Prebuilt Informatica Repository for Environments in English" or "Restoring the Prebuilt Informatica Repository on a Non-English Operating System" in Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users for instructions.
This step gives you the Oracle BI Applications 7.9.6.4 Informatica Repository in the Informatica 9.0.1 format.

5. Launch the Informatica PowerCenter Repository Manager, and connect to the repository you restored in step 4 (for example, Oracle_BI_DW_Base.rep), and connect to your current, existing Informatica Repository.
Note: Your current, existing repository should have been updated to the version 9.0.1 format during the Informatica PowerCenter 9.0.1 installation process.

6. In your current, existing repository, make sure all of your customizations are in a "Custom" folder.

7. In your current, existing repository, delete the following folders:

- PLP

- All folders with the prefix SDE_

- SILOS

- SIL_VERT

- UA_SDE

- UA_SIL

Make sure you do not delete the "Custom" folder.

8. Copy the following folders containing the Oracle BI Applications content for release 7.9.6.4 from the newly restored repository (Oracle_BI_DW_Base.rep) into your current, existing repository.

- PLP

- All folders with the prefix SDE_

- SILOS

- SIL_VERT

- UA_SDE

- UA_SIL

This action updates your current, existing repository with the Oracle BI Applications 7.9.6.4 content; this is the repository you will use to run ETL in Oracle BI Applications 7.9.6.4.

The version 7.9.6.4 repository (Oracle_BI_DW_Base.rep) and the Repository Service for this repository are no longer needed.

3.6 Upgrading the Informatica Repository When You Are Already Running Informatica PowerCenter 9.1

If you are upgrading to Oracle BI Applications 7.9.6.4 and previously upgraded Informatica PowerCenter to version 9.1 Hotfix 2, you must first restore the Oracle BI Applications version 7.9.6.4 Informatica Repository using Informatica PowerCenter 9.0.1 Hotfix 2. Then, you can upgrade this repository to the Informatica 9.1 format by pointing to it using Informatica 9.1 client tools. After the Oracle BI Applications 7.9.6.4 Informatica Repository has been upgraded to the Informatica 9.1 format, you can then copy the folders containing the Oracle BI Applications 7.9.6.4 content into your current, existing Informatica Repository. The result of this action is an Informatica Repository that contains your customizations along with the new Oracle BI Applications 7.9.6.4 content.

For detailed instructions on backing up and restoring the Informatica Repository, see the topic titled, "Backing Up and Restoring the PowerCenter Repository," in "Chapter 15: PowerCenter Repository Management," in the Informatica PowerCenter Administrator Guide. See the Oracle Business Intelligence Applications Release Notes, available on the Oracle Technology Network, for information about how to locate the Informatica documentation.

To upgrade the Informatica Repository when already running Informatica PowerCenter 9.1:

1. Make sure you have backed up and renamed your current, existing Informatica Repository.

2. Install Informatica PowerCenter Services version 9.0.1 Hotfix 2. You do not need to install the Informatica PowerCenter Client Tools. See Section 3.4, "Upgrading to Informatica PowerCenter Version 9.0.1 Hotfix 2" for instructions.

3. Copy the Oracle_BI_DW_Base.rep file (or Oracle_BI_DW_Teradata.rep for repositories on Teradata databases) from the folder OracleBI\dwrep\Informatica\Repository into the Informatica PowerCenter 9.0.1 folder <INFA_HOME>\server\infa_shared\Backup.

Note:

The Oracle_BI_DW_Base.rep file is installed in the OracleBI root directory when you run the Oracle BI Applications installer, as described in Section 3.3, "Upgrading Oracle BI Applications."

4. Using Informatica PowerCenter Administrator, create a new Repository Service for the Oracle_BI_DW_Base.rep repository. See "Setup Step: Creating the Informatica Repository Service," in Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users for instructions.

5. Using the Repository Service you created in the step above, restore the Oracle_BI_DW_Base.rep repository into an empty schema. See "Restoring the Prebuilt Informatica Repository for Environments in English" or "Restoring the Prebuilt Informatica Repository on a Non-English Operating System" in Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users for instructions.
This step gives you the Oracle BI Applications 7.9.6.4 Informatica Repository in Informatica 9.0.1 format.

6. Launch the Informatica PowerCenter Repository Manager, and connect to the repository you restored in step 5. When prompted to upgrade the repository to the 9.1 format, do so.

7. In Repository Manger, connect to your current, existing Informatica Repository.

8. In your current, existing repository, make sure all of your customizations are in a "Custom" folder.

9. In your current, existing repository, delete the following folders:

- PLP

- All folders with the prefix SDE_

- SILOS

- SIL_VERT

- UA_SDE

- UA_SIL

Make sure you do not delete the "Custom" folder.

10. Copy the following folders containing the Oracle BI Applications content for release 7.9.6.4 from the newly restored repository (Oracle_BI_DW_Base.rep) into your current, existing repository.

- PLP

- All folders with the prefix SDE_

- SILOS

- SIL_VERT

- UA_SDE

- UA_SIL

This action updates your current, existing repository with the Oracle BI Applications 7.9.6.4 content; this is the repository you will use to run ETL in Oracle BI Applications 7.9.6.4.

The version 7.9.6.4 repository (Oracle_BI_DW_Base.rep) and the Repository Service for this repository are no longer needed.

3.7 Verifying Configurations for Informatica PowerCenter Version 9.0.1 Hotfix 2 to Work With Oracle BI Applications and DAC

Informatica PowerCenter version 9.0.1 Hotfix 2 requires configuration for it to work with Oracle BI Applications and DAC. The configuration settings from your earlier Informatica environment may have been retained when you upgraded to Version 9.0.1 Hotfix 2. Verify or perform the procedures listed below, as documented in the Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users:

- Copying Source Files and Lookup Files

- Setting PowerCenter Integration Services Relaxed Code Page Validation

- Setting PowerCenter Integration Services Custom Properties

- Creating the Repository Administrator User in the Native Security Domain

3.8 Installing and Configuring DAC 11g

Siebel Analytics release 7.5.x does not include the Data Warehouse Administration Console (DAC). In the current release of Oracle BI Applications, you will use the 11g version of the DAC Client and Server and the DAC Repository. For information about the specific release of the DAC platform supported with the current release of Oracle BI Applications, see System Requirements and Supported Platforms for Oracle Business Intelligence Applications.

To install and configure DAC 11g, follow the instructions in the Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users. Make sure you perform the tasks in the following sections of the Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users:

- Preinstallation Tasks

- Installing and Setting Up the DAC Platform

- Installing DAC Metadata Files

- Logging into DAC for the First Time and Importing Metadata into the DAC Repository
Note: After you complete this procedure, you will have the default DAC Repository for Oracle BI Applications release 7.9.6.4.

- Configuring the DAC Server

- Configuring DAC Integration Settings

- Configuring Relational Connections in Informatica Workflow Manager

- Configuring the SiebelUnicodeDB Custom Property

- Setting Up DAC to Receive Email Notification

- Additional Configuration Tasks
In this section, perform only the tasks that apply to your environment.

3.9 Overview of Upgrading the Data Warehouse Schema and Migrating Data

The process for upgrading the data warehouse schema and migrating data for Siebel Business Analytics releases 7.5.x involves multiple phases, as described below.

Note:

The Oracle BI Applications upgrade logic is coded such that you must complete each of the phases listed below. To upgrade to the current release of Oracle BI Applications, you cannot skip any of the phases.

- Phase 1
In phase 1, you will upgrade the data warehouse schema to version 7.7 and migrate data into the upgraded data warehouse. For instructions, see Section 3.10.

- Phase 2
In phase 2, you will perform the following steps:

1. Upgrade the data warehouse schema to version 7.9.0. For instructions, see Section 3.11.

2. Import new schema definitions into the Siebel transactional database. For instructions, see Section 3.12.

3. Migrate data into the data warehouse upgraded to version 7.9.0. For instructions, see Section 3.13.

- Phase 3
In phase 3, you will upgrade your data warehouse schema to version 7.9.4 and migrate data into the upgraded data warehouse. For instructions, see Section 3.14.

- Phase 4
In phase 4, you will upgrade your data warehouse schema to version 7.9.5 and migrate data into the upgraded data warehouse. For instructions, see Section 3.15.

- Phase 5
In phase 5, you will upgrade your data warehouse schema to version 7.9.5.1. For instructions, see Section 3.16.

- Phase 6
In phase 6, you will do one of the following:

- Upgrade your data warehouse schema from version 7.9.5.1 to version 7.9.6.1 and migrate data. For instructions, see Section 3.17.

- If you are currently running Oracle BI Applications version 7.9.6 and using an Oracle database, you can upgrade your data warehouse schema to version 7.9.6.1 and migrate data. For instructions, see Section 3.18.

- Phase 7
In phase 7, you will upgrade your data warehouse schema to version 7.9.6.2 and migrate data into the upgraded data warehouse. For instructions, see Section 3.19.

- Phase 8
In phase 8, you will upgrade your data warehouse schema to version 7.9.6.3 and migrate data into the upgraded data warehouse. For instructions, see Section 3.20.

- Phase 9
In phase 9, you will upgrade your data warehouse schema to version 7.9.6.4 and migrate data into the upgraded data warehouse. For instructions, see Section 3.21.

3.10 Upgrading the Data Warehouse Schema to Version 7.7 and Migrating Data

Follow this procedure to upgrade the data warehouse schema to version 7.7 and migrate data.

To upgrade the data warehouse schema:

1. Run the schema upgrade script.
This script adds new tables, columns, and indexes to the existing data warehouse schema. It also modifies the existing data warehouse schema objects.

1. Navigate to the folder OracleBI\dwrep\Upgrade\CTLFiles, and locate the ddlsme_HOR_77.ctl file (Horizontal) or ddlsme_SIA_77.ctl file (Vertical).

2. If you changed any of the preconfigured column definitions in the CTL file for your implementation, you need to edit the CTL file to reflect the change. For example, if you renamed or resized an existing column in W_DAY_D, you need to make the same change in the CTL file. If you do not make the change in the CTL file, when the CTL file is run, the column definition will revert to the preconfigured definition. (As a customization, if a column size was changed from VARCHAR(50) to VARCHAR(100), and the same change was not made in the CTL file before running, the column will revert to the preconfigured value of VARCHAR(50), which could cause data to be truncated in some databases.)

3. 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\Upgrade\CTLFiles\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\Upgrade\CTLFiles\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.

2. Copy the file Upgrade.rep from the folder OracleBI\dwrep\Upgrade\Informatica\Repository into the folder <INFA_HOME>\server\infa_shared\Backup.

3. Launch the Informatica Administrator and restore Upgrade.rep (located in <INFA_HOME>\server\infa_shared\Backup) into a database other than the database in which you restored Oracle_BI_DW_Base.rep.

4. 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, <INFA_HOME>\server\infa_shared\SrcFiles.

5. Rename 753_TENERIFE_UPG_PARAMS.txt to TENERIFE_UPG_PARAMS.txt.

6. In the Informatica Workflow Manager, open the Relational Connection Browser (in the menu bar, select Connections, and then select Relational), and edit the connect string, user and password for the relational connections as follows:

1. Edit the PARAM_OLTP_SIEBEL connection to point to the Siebel transactional database.

2. Edit the DataWarehouse connection to point to the newly upgraded data warehouse database.

3. Create or edit the PARAM_DAC_OLD connection to point to the previous DAC Repository database (the version from which you are upgrading).

4. Create or edit the PARAM_DAC_NEW connection to point to the DAC Repository database.

Note:

If you are connected to an Oracle database, use the 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.

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

1. Upgrade_R_Image

2. Upgrade_Unspecifieds

3. Upgrade_Agree

4. Upgrade_Asset

5. Upgrade_Opty

6. Upgrade_Order

7. Upgrade_Quote

8. Upgrade_Response

9. Upgrade_ServiceRequest

10. Upgrade_Others

11. Upgrade_Visibility

12. UpgradeSlowlyChangingDimensionStartDates

13. DAC_Metadata_Upgrade_Workflow

8. 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

1. Upgrade_R_Image

2. Upgrade_Unspecifieds

3. Upgrade_Agree

4. Upgrade_Asset

5. Upgrade_Opty

6. Upgrade_Order

7. Upgrade_Quote

8. Upgrade_Response

9. Upgrade_ServiceRequest

10. Upgrade_Others

11. Upgrade_Visibility

12. UpgradeSlowlyChangingDimensionStartDates

13. Upgrade_Industry_R_Image

14. Upgrade_Industry_Unspecified

15. Upgrade_LS_ActivityProduct

16. Upgrade_LS_Others

17. Upgrade_Industry_Household

18. Upgrade_FINS_Visibility

19. UpgradeSlowlyChangingDimensionStartDates_Industry

20. DAC_Metadata_Upgrade_Workflow

3.11 Upgrading the Data Warehouse Schema to Version 7.9.0

This procedure adds new tables, columns, and indexes to the existing data warehouse schema. It also modifies the existing data warehouse schema objects.

To upgrade the data warehouse schema:

1. Run the UPGRADE.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

2. Run the 790_UPGRADE_PRE_CTL_SCRIPT.sql script.

1. Open the SQL client for your database type.

2. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\<database type>.

3. Open the 790_UPGRADE_PRE_CTL_SCRIPT.sql file, and copy the contents into the SQL client.

4. Execute the script.

3. Run the DW.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

4. Run the 790_UPGRADE_PRE_DIMENSION_SCRIPT.sql script. This file is located in the folder OracleBI\dwrep\Upgrade\DbScripts\<database type>.

3.12 Importing New Schema Definitions into the Siebel Transactional Database

This procedure upgrades transactional database objects that relate to Oracle Business Intelligence Applications. It does not upgrade transactional database objects for Siebel CRM applications.

To import new schema definitions into the Siebel transactional database:

1. Import schema definitions for non-image tables:

1. Access the DDLimp utility.

2. Run the DDL_OLTP.ctl script that is located in the OracleBI\dwrep\Upgrade\CTLFiles folder.
Note: If you receive an error message stating a particular object already exists in the database, use the DDLimp Merge argument (/M Y) in the DDLimp command to resolve the error.

2. Import schema definitions for image tables:

1. In DAC, go to the Design view, and select your custom container from the drop-down list to the right of the Execute button.

2. Click the Tables tab.

3. Query for all tables for which the image suffix is not null.

4. Right-click in the list of tables returned by the query, and select Change Capture Scripts, and then Generate Image and Trigger Scripts.

5. In the Triggers and Image Tables dialog box, do the following:
- Select the option All Tables in the List.

- Select the option Generate Image Table Scripts.

- Select the appropriate database type for the source system.

- Click OK.

6. Open the SQL client for the source system database type, for example, SQL Plus for Oracle, Query Analyzer for SQL Server, or a command window for DB2.
The script may contain many lines; therefore, you can save the script file as a SQL file and execute it in a SQL client.

7. Copy the scripts generated by DAC into the SQL client and execute them.

3.12.1 Verifying the Siebel Transactional Database Upgrade

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_xxx

- S_ETL_I_IMG_xxx

- S_ETL_D_IMG_xxx

- S_ETL_PARAM

- S_ETL_PRD_ATTR

- S_ETL_PRD_REL

3.13 Migrating Data into the Data Warehouse Upgraded to Version 7.9.0

Follow this procedure to migrate data into the data warehouse upgraded to version 7.9.0.

To migrate data into the upgraded data warehouse:

1. 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, <INFA_HOME>\server\infa_shared\SrcFiles.

2. 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, <INFA_HOME>\server\infa_shared\SrcFiles.

3. Rename 770_TENERIFE_UPG_PARAMS.txt to TENERIFE_UPG_PARAMS.txt.

4. In the file TENERIFE_UPG_PARAMS.txt:

1. Search for the parameter $$SourceConnection.

2. 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 (use this value for OLTP versions 8.x and 8.1.1)

- SEBL_VERT_753

- SEBL_VERT_771

- SEBL_VERT_78

- SEBL_VERT_80 (use this value for OLTP versions 8.x and 8.1.1)

For example, if your Siebel applications (OLTP) version is Siebel Industry Applications 7.5.x, the parameter should appear as:

$$SourceConnection=SEBL_VERT_753

5. In the file TENERIFE_UPG_PARAMS.txt:

1. Search for the parameter $$Source_Container.

2. 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 (use this value for OLTP versions 8.x and 8.1.1)

- Siebel 8.0 Vertical (use this value for OLTP versions 8.x and 8.1.1)

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

6. 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.

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

8. For Siebel Industry Applications (Vertical), define the alignment rule to be used for ETL loads.

1. 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, <INFA_HOME>\server\infa_shared\SrcFiles.

2. Rename the file AlignmentType_LS_782.csv to AlignmentType.csv.

3. Open the file AlignmentType.csv, and enter one of the following alignment item types under the ALIGN_TYPE field:

- Zipcode

- Account/Contact

- Brick

4. Save the file.

The Oracle Business Analytics Warehouse allows only one alignment type to be used for ETL loads during upgrade.

9. In Informatica Workflow Manager, navigate to the folder UPGRADE_770_to_79, and execute the following workflows in the order indicated:

1. MARKETING_LOAD

2. Upgrade_Dimensions_Industry

3. Update_Dimensions

4. Update_Dimension_Unspecified

5. Update_Facts

6. (For Siebel Industry Applications only) Upgrade_LS_Dimensions

7. (For Siebel Industry Applications only) Upgrade_LS_Facts

8. SIL_PositionDimensionHierarchy_Full

9. Load_INT_ORG_DH

10. 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.

11. DIMENSION_UNSPECIFIED_UPDATE

12. FACT_UPDATE

13. DAC_Metadata_Upgrade_Workflow

Note:

You need to run this workflow for upgrading to the data warehouse schema version 7.9.0 even though you ran a workflow with the same name during the upgrade to version 7.7.

10. If you upgraded your transactional database to Siebel Applications 8.x or 8.1.1, navigate to the folder UPGRADE_790_to_791_SBL80UPG and run the following workflows in the order indicated:

1. UPGRADE_DIMENSIONS

2. UPGRADE_FACTS

11. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep). For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Base Informatica Repository."

12. To verify the data migrated successfully:

1. Validate the data in the upgraded data warehouse.

2. Check whether any of the Informatica mapping log files stored in the directory \Informatica PowerCenter 9.0.1\Server\SessLogs indicates errors or failures.

3. 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.

4. 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.

Note:

Ignore any error messages that indicate tables or indexes could not be dropped from the database. These error messages are displayed when the specified objects do not exist in the database. This can occur because each source system container holds a subset of all data warehouse tables.

13. 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.

3.14 Upgrading the Data Warehouse Schema to Version 7.9.4 and Migrating Data

Follow this procedure to upgrade the data warehouse schema to version 7.9.4 and migrate data.

This procedure adds new tables, columns, and indexes to the existing data warehouse schema. It also modifies the existing data warehouse schema objects.

To upgrade the data warehouse schema to version 7.9.4 and migrate data:

1. Run the 792_UPGRADE_PRE_CTL_SCRIPT.sql script.

1. Open the SQL client for your database type, for example, SQLPLUS for Oracle, Query Analyzer for SQL Server, or a command window for DB2.

2. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\<database type>.

3. Open the 792_UPGRADE_PRE_CTL_SCRIPT.sql file, and copy the contents into the SQL client.

4. Execute the script.

2. Run the ddl_794.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

3. Run the 792_UPGRADE_PRE_DIMENSION_SCRIPT.sql script. This file is located in the folder OracleBI\dwrep\Upgrade\DbScripts\<database type>.

4. If you upgraded your transactional database to Siebel Applications 8.x or 8.1.1, run the workflows to migrate your data into the upgraded data warehouse.

1. In Informatica Workflow Manager, navigate to the folder UPGRADE_790_TO_791_SBL80UPG.

2. Run the following workflows in the order indicated:
UPGRADE_DIMENSIONS

UPGRADE_FACTS

5. Verify the data migrated successfully by checking whether any of the Informatica mapping log files stored in the <INFA_HOME>\server\infa_shared\SessLogs directory indicate errors or failures. Also, validate the data in the upgraded data warehouse.

6. If the data migration was successful, drop the tables that were created during the upgrade process, such as, W_xxxx_x_79x tables, LKP_xxxx_x and 79x_XXXX_TMP.
This step frees the space occupied by these backup tables.

7. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep). For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Base Informatica Repository."

3.15 Upgrading the Data Warehouse Schema to Version 7.9.5 and Migrating Data

Follow this procedure to upgrade the data warehouse schema to version 7.9.5 and migrate data.

This procedure adds new tables, columns, and indexes to the existing data warehouse schema. It also modifies the existing data warehouse schema objects.

To upgrade the data warehouse schema to version 7.9.5 and migrate data:

1. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade repository. For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Upgrade Informatica Repository."

2. Run the 795_UPGRADE_PRE_CTL_SCRIPT.sql script. This file is located in the folder OracleBI\dwrep\Upgrade\DbScripts\<database type>.

3. Run the UPGRADE_795.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

4. Run the ddl_795.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

5. Run the 795_UPGRADE_PRE_DIMENSION_SCRIPT.sql script. This file is located in the folder OracleBI\dwrep\Upgrade\DbScripts\<database type>.

6. Copy all of the domain value files in the folder \OracleBI\dwrep\Informatica\LkpFiles into the folder <INFA_HOME>\server\infa_shared\LkpFiles.

7. Migrate data into the upgraded data warehouse.

1. Copy the file Upgrade.rep from the folder OracleBI\dwrep\Upgrade\Informatica\Repository into the folder <INFA_HOME>\server\infa_shared\Backup.

2. Launch the Informatica Administrator and restore Upgrade.rep (located in <INFA_HOME>\server\infa_shared\Backup).

3. Configure the Informatica parameter file 795_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 795_UPG_PARAMS.txt."

4. In Informatica Workflow Manager, open the Relational Connection Browser (in the menu bar, select Connections, and then select Relational), and edit the connect string, user and password for the relational connections as follows: create one relational connection based on the appropriate database platform for your OLTP database. Create the connection with the name PARAM_OLTP.
Edit the PARAM_OLTP connection to match your OLTP environment.

Edit the PARAM_OLAP connection to match your OLAP environment.

Note:

If you are connected to an Oracle database, use the 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.

5. In Informatica Workflow Manager, navigate to the folder UPGRADE_794_to_795_SBL and execute the UPGRADE_DIMENSIONS workflow.

8. Verify the data migrated successfully.

1. Validate the data in the upgraded data warehouse.

2. Check whether any of the Informatica mapping log files stored in the <INFA_HOME>\server\infa_shared\Sesslogs directory indicates errors or failures.

3. Check whether the script 795_UPGRADE_PRE_DIMENSION_SCRIPT.sql that you ran in the SQL client of the database failed or errored out while executing.

4. Check the log file for the ddl_795.ctl. and Upgrade_795.ctl, which 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.

Note:

Ignore any error messages that indicate tables or indexes could not be dropped from the database. These error messages are displayed when the specified objects do not exist in the database. This can occur because each source system container holds a subset of all data warehouse tables

9. If the data migration was successful, drop the tables that were created during the upgrade process, such as W_xxxx_x_79x, LKP_xxxx_x and 79x_xxxx_TMP.
This step frees the space occupied by these backup tables.

10. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep). For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Base Informatica Repository."

3.16 Upgrading the Data Warehouse Schema to Version 7.9.5.1

Follow this procedure to upgrade the data warehouse schema to version 7.9.5.1.

To upgrade the data warehouse schema:

- Use the DDLimp utility to run the ddl_7951.ctl script, which is located in the OracleBI\dwrep\Upgrade\CTLFiles folder. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

3.17 Upgrading the Data Warehouse Schema From Version 7.9.5.1 to 7.9.6.1 and Migrating Data

You need to perform this procedure if you are upgrading from Oracle BI Applications releases 7.9.0, 7.9.1, 7.9.2, 7.9.3, 7.9.4, 7.9.5, or 7.9.5.1.

This procedure adds new tables, columns, and indexes to the existing data warehouse schema. It also modifies the existing data warehouse schema objects.

This section includes the following procedures:

- Section 3.17.1, "Upgrading the Data Warehouse Schema From Version 7.9.5.1 to 7.9.6.1"

- Section 3.17.2, "Migrating Data Into the Upgraded Data Warehouse"

- Section 3.17.3, "Verifying the Data Migrated Successfully"

3.17.1 Upgrading the Data Warehouse Schema From Version 7.9.5.1 to 7.9.6.1

Follow this procedure to upgrade the data warehouse schema to version 7.9.6.1.

Note: Upgrading to version 7.9.6.1 may involve running scripts that have a "796_" prefix.

To upgrade the data warehouse schema to version 7.9.6.1 and migrate data:

1. If you are using an Oracle database, run the 796_UPGRADE_DROP_INDEXES.sql script.

1. Open the SQL client for your database type.

2. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Oracle.

3. Open the 796_UPGRADE_DROP_INDEXES. sql file, and copy the contents into the SQL client.

4. Execute the script.

2. If you are using a SQL Server or DB2 database, run the 7961_UPGRADE_DROP_INDEXES.sql script.

1. Open the SQL client for your database type.

2. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\<database type>.

3. Open the 7961_UPGRADE_DROP_INDEXES. sql file, and copy the contents into the SQL client.

4. Execute the script.

3. If you are using a SQL Server database, run the 7961_UPGRADE_PRE_UPG_CTL_SCRIPT.sql file. This file is located in OracleBI\dwrep\Upgrade\DbScripts\SQLServer.

4. Run the UPGRADE_796.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

5. Run the 7961_UPGRADE_PRE_CTL_SCRIPT.sql:

1. Go to OracleBI\dwrep\Upgrade\DbScripts\<database type> folder, and open the 7961_UPGRADE_PRE_CTL_SCRIPT.sql file.

2. Search for the Datasource_Num_ID parameter, and make sure the value is correct for your existing implementation.

3. If you are using a DB2 database, search for the text "TBS_32K," and replace it with the appropriate 32K table space name that you have configured.

4. Execute the script.

6. Run the ddl_7961.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

7. Run the 796_UPGRADE_PRE_DIMENSION_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

8. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository. For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Upgrade Informatica Repository."

9. Copy all of the domain value files in the folder \OracleBI\dwrep\Informatica\LkpFiles into the folder <INFA_HOME>\server\infa_shared\LkpFiles.

3.17.2 Migrating Data Into the Upgraded Data Warehouse

Follow this procedure to migrate data into the upgraded data warehouse.

To migrate data into the upgraded data warehouse:

1. Copy the file Upgrade.rep from the folder OracleBI\dwrep\Upgrade\Informatica\Repository into the folder <INFA_HOME>\server\infa_shared\Backup.

2. Launch the Informatica Administrator and restore Upgrade.rep (located in <INFA_HOME>\server\infa_shared\Backup).

3. Configure the Informatica parameter file 796_UPG_PARAMS.txt file. For instructions, see Appendix A, "Setting Parameters in 796_UPG_PARAMS.txt."

4. Configure parameters specific to Siebel source systems. For instructions, see Appendix A, "Setting Parameters in 796_UPG_PARAMS.txt for Siebel Source Systems."

5. In Informatica Workflow Manager, open the Relational Connection Browser (in the menu bar, select Connections, and then select Relational), and edit the connect string, user and password for the relational connections as follows:

1. Edit the connection PARAM_OLTP_SIEBEL to match your OLTP environment.

2. Edit the connection PARAM_OLAP to match your OLAP environment.

3. Edit the connection PARAM_DAC to match your DAC database.

Note:

If you are connected to an Oracle database, use the 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.

6. Back up and truncate the table W_POSITION_DH.

7. In Informatica Workflow Manager, navigate to the folder UPGRADE_7951_to_796_SBL and execute the following workflows in the order indicated:

- UPGRADE_DIMENSIONS

- UPGRADE_FACTS

- RESET_DAC_REFRESH_DATES

8. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep). For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Base Informatica Repository."

9. Run the 7961_UPGRADE_PRE_DIMENSION_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

10. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository. For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Upgrade Informatica Repository."

11. Configure the Informatica parameter file 7961_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7961_UPG_PARAMS.txt."

12. In Informatica Workflow Manager, navigate to the folder UPGRADE_796_to_7961_SBL and execute the first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

13. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep). For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Base Informatica Repository."

14. Run the 7961_UPGRADE_POST_SCRIPT.sql. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

3.17.3 Verifying the Data Migrated Successfully

Follow this procedure to verify that the data was migrated successfully into the upgraded data warehouse.

To verify the data migrated successfully:

1. Validate the data in the upgraded data warehouse.

2. Check whether any of the Informatica mapping log files stored in the <INFA_HOME>\server\infa_shared\Sesslogs directory indicates errors or failures.

3. Check whether the following scripts that you ran in the SQL client of the database failed or errored out while executing:
7961_UPGRADE_DROP_INDEXES.sql

7961_UPGRADE_PRE_CTL_SCRIPT.sql

7961_UPGRADE_PRE_DIMENSION.sql

7961_UPGRADE_POST_SCRIPT.sql

4. Check the log files for the ddl_7961.ctl and Upgrade_7961.ctl scripts 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.

Note:

Ignore any error messages that indicate tables or indexes could not be dropped from the database. These error messages are displayed when the specified objects do not exist in the database. This can occur because each source system container holds a subset of all data warehouse tables

5. If the data migration was successful, drop the tables that were created during the upgrade process, such as W_xxxx_x_79x, LKP_xxxx_x, 79x_xxxx_TMP, and TMP_xxxx_79x.
This step frees the space occupied by these backup tables.

3.18 Upgrading the Data Warehouse Schema From Version 7.9.6 to 7.9.6.1

Perform the procedures in this section if you are upgrading from Oracle BI Applications release 7.9.6 to release 7.9.6.1.

Note:

This procedure is applicable only if you are using an Oracle database for your data warehouse database.

This section includes the following procedures:

- Section 3.18.1, "Upgrading the Data Warehouse Schema to Version 7.9.6.1"

- Section 3.18.2, "Migrating Data into the Upgraded Data Warehouse"

- Section 3.18.3, "Verifying the Data Migrated Successfully"

3.18.1 Upgrading the Data Warehouse Schema to Version 7.9.6.1

Follow this procedure to upgrade the data warehouse schema to version 7.9.6.1.

To upgrade the data warehouse schema to version 7.9.6.1:

1. Run the UPGRADE_7961.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

2. Run the 796ORA_TO_7961ORA_UPGRADE_PRE_CTL_SCRIPT.sql. This file is located in the folder OracleBI\dwrep\Upgrade\DbScripts\Oracle.

3. Run the ddl_7961.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

3.18.2 Migrating Data into the Upgraded Data Warehouse

Follow this procedure to migrate data into the upgraded data warehouse.

To migrate data into the upgraded data warehouse:

1. Run the 7961_UPGRADE_PRE_DIMENSION_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Oracle.

2. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade repository. For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Upgrade Informatica Repository."

3. Configure the Informatica parameter file 7961_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7961_UPG_PARAMS.txt."

4. In Informatica Workflow Manager, navigate to the folder UPGRADE_796_to_7961_SBL and execute the first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

5. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep). For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Base Informatica Repository."

6. Run the 7961_UPGRADE_POST_SCRIPT.sql. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Oracle.

3.18.3 Verifying the Data Migrated Successfully

Follow this procedure to verify that the data was migrated successfully into the upgraded data warehouse.

To verify the data migrated successfully:

1. Validate the data in the upgraded data warehouse.

2. Check whether any of the Informatica mapping log files stored in the <INFA_HOME>\server\infa_shared\Sesslogs directory indicates errors or failures.

3. Check whether the following scripts that you ran in the SQL client of the database failed or errored out while executing:
7961_UPGRADE_DROP_INDEXES.sql

7961_UPGRADE_PRE_CTL_SCRIPT.sql

7961_UPGRADE_PRE_DIMENSION.sql

7961_UPGRADE_POST_SCRIPT.sql

4. Check the log files for the ddl_7961.ctl and Upgrade_7961.ctl scripts, which 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.

Note:

Ignore any error messages that indicate tables or indexes could not be dropped from the database. These error messages are displayed when the specified objects do not exist in the database. This can occur because each source system container holds a subset of all data warehouse tables

3.19 Upgrading the Data Warehouse Schema From Version 7.9.6.1 to 7.9.6.2 and Migrating Data

This section contains the following procedures:

- Section 3.19.1, "Upgrading the Data Warehouse Schema to Version 7.9.6.2"

- Section 3.19.2, "Migrating Data into the Upgraded Data Warehouse"

- Section 3.19.3, "Verifying the Data Migrated Successfully"

3.19.1 Upgrading the Data Warehouse Schema to Version 7.9.6.2

Follow this procedure to upgrade the data warehouse schema to version 7.9.6.2.

To upgrade the data warehouse schema to version 7.9.6.2:

1. Generate the scripts to drop and create indexes. For instructions, see Section B.1, "Generating Scripts to Drop and Create Indexes for Upgrading to Release 7.9.6.2."

2. Run the script to drop all indexes. For instructions, see Section B.2, "Running the Script to Drop All Indexes for Upgrading to Release 7.9.6.2."

3. If you are using a SQL Server database, run the 7962_UPGRADE_PRE_UPG_CTL_SCRIPT.sql file. This file is located in OracleBI\dwrep\Upgrade\DbScripts\SQLServer.

4. Run the UPGRADE_7962.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

5. Run the 7962_UPGRADE_PRE_CTL_SCRIPT.sql. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

6. Run the ddl_7962.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

3.19.2 Migrating Data into the Upgraded Data Warehouse

Follow this procedure to migrate data into the upgraded data warehouse.

To migrate data into the upgraded data warehouse:

1. Run the 7962_UPGRADE_PRE_DIMENSION_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

2. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade repository. For instructions, see Section D.4, "Running reset_infa_seq_gen.bat on Upgrade Informatica Repository."

3. Configure the Informatica parameter file 7962_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7962_UPG_PARAMS.txt."

4. Run the script to create ETL indexes. For instructions, see Section B.3, "Running the Scripts to Create ETL and Query Indexes for Upgrading to Release 7.9.6.2."

5. In Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_SBL and execute the UPGRADE_DIMENSIONS workflow.

6. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep). For instructions, see Section D.1, "Running reset_infa_seq_gen.bat on Base Informatica Repository."

7. Run the script to create Query indexes. For instructions, see Section B.3, "Running the Scripts to Create ETL and Query Indexes for Upgrading to Release 7.9.6.2."

3.19.3 Verifying the Data Migrated Successfully

Follow this procedure to verify that the data was migrated successfully into the upgraded data warehouse.

To verify the data migrated successfully:

1. Validate the data in the upgraded data warehouse.

2. Check whether any of the Informatica mapping log files stored in the <INFA_HOME>\server\infa_shared\Sesslogs directory indicates errors or failures.

3. Check whether the following scripts that you ran in the SQL client of the database failed or errored out while executing:
dropallindexes.sql

7962_UPGRADE_PRE_CTL_SCRIPT.sql

7962_UPGRADE_PRE_DIMENSION.sql

createETLIndexes.sql

createQueryIndexes.sql

4. Check the log files for the ddl_7962.ctl and Upgrade_7962.ctl scripts, which 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.

Note:

Ignore any error messages that indicate tables or indexes could not be dropped from the database. These error messages are displayed when the specified objects do not exist in the database. This can occur because each source system container holds a subset of all data warehouse tables.

5. If the data migration was successful, drop the tables that were created during the upgrade process, such as W_xxxx_x_79x, LKP_xxxx_x and 79x_xxxx_TMP.
This step frees the space occupied by these backup tables.

6. Once the data migration steps above are complete, you can delete the Upgrade repository to avoid any accidental use or confusion.

1. In the Informatica Administrator, select the Upgrade repository service.

2. In the General Properties area of the Properties tab, click Edit.

3. Make sure the operating mode of the repository service is set to Exclusive.

4. Click OK.

5. Choose Actions, and then click Delete Contents.

6. In the Delete contents for <repository name> dialog, enter the repository username and password, then click OK.

3.20 Upgrading the Data Warehouse Schema From Version 7.9.6.2 to 7.9.6.3 and Migrating Data

Perform the procedures in this section to upgrade from Oracle BI Applications release 7.9.6.2 to 7.9.6.3.

This section contains the following procedures:

- Section 3.20.1, "Upgrading the Data Warehouse Schema to Version 7.9.6.3"

- Section 3.20.2, "Migrating Data Into the Upgraded Data Warehouse"

- Section 3.20.3, "Verifying the Data Migrated Successfully"

3.20.1 Upgrading the Data Warehouse Schema to Version 7.9.6.3

Follow this procedure to upgrade the data warehouse schema to version 7.9.6.3.

To upgrade the data warehouse schema to version 7.9.6.3:

1. Generate the scripts to drop and create query indexes. For instructions, see Section B.4, "Generating Scripts to Drop and Create Query Indexes for Upgrading to Release 7.9.6.3."

2. Run the script to drop query indexes. For instructions, see Section B.5, "Running the Scripts to Drop and Create Query Indexes for Upgrading to Release 7.9.6.3."

3. If you are using a SQL Server database, run the 7963_UPGRADE_PRE_UPG_CTL_SCRIPT.sql file. This file is located in OracleBI\dwrep\Upgrade\DbScripts\SQLServer.

4. Run the UPGRADE_7963.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

5. Run the 7963_UPGRADE_PRE_CTL_SCRIPT.sql. This file is located in the folder OracleBI\dwrep\Upgrade\DbScripts\<database type>.

6. Run the DDL_7963.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files.".

3.20.2 Migrating Data Into the Upgraded Data Warehouse

Follow this procedure to migrate data into the upgraded data warehouse.

To migrate data into the upgraded data warehouse:

1. Run the 7963_UPGRADE_PRE_DIMENSION_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

2. Run the 7963_UPGRADE_DROP_ETLINDICES.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

3. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade repository. For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Upgrade Informatica Repository."

4. Configure the Informatica parameter file 7963_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt."

5. If you are using Siebel Industry Applications, you need to set an additional parameter in 7963_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt for Siebel Industry Applications Source Systems."

6. In Informatica Workflow Manager, navigate to the folder UPGRADE_7962_to_7963_SBL and execute the first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

7. Upgrade geography-related attributes if necessary for your environment:

1. Determine whether a geography-related upgrade is necessary by executing the following query:

SELECT COUNT(1) as row_count,'0' as X_CUSTOM FROM W_GEO_D_7963 WHERE COUNTRY LIKE '% 'OR COUNTRY LIKE ' %'OR STATE_PROV LIKE '% 'OR STATE_PROV LIKE ' %'OR CITY LIKE '% 'OR CITY LIKE ' %'OR ZIPCODE LIKE '% 'OR ZIPCODE LIKE ' %'

2. If the query returns a count greater than zero, run the 7963_UPGRADE_POST_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.
If the query returns a count of zero, you do not need to run the 7963_UPGRADE_POST_SCRIPT.sql script.

8. Run the 7963_UPGRADE_CREATE_ETLINDICES.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

9. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep). For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Base Informatica Repository."

10. Run the createQueryIndices.sql script. For instructions, see Section B.5, "Running the Scripts to Drop and Create Query Indexes for Upgrading to Release 7.9.6.3."

3.20.3 Verifying the Data Migrated Successfully

Follow this procedure to verify that the data was migrated successfully into the upgraded data warehouse.

To verify the data migrated successfully:

1. Validate the data in the upgraded data warehouse.

2. Check whether any of the Informatica mapping log files stored in the <INFA_HOME>\server\infa_shared\Sesslogs directory indicates errors or failures.

3. Check whether the following scripts that you ran in the SQL client of the database failed or errored out while executing:
7963_UPGRADE_PRE_CTL_SCRIPT.sql

7963_UPGRADE_PRE_DIMENSION.sql

7963_UPGRADE_DROP_ETLINDICES.sql

7963_UPGRADE CREATE_ETLINDICES.sql

dropQueryIndices.sql

createQueryIndices.sql

4. Check the log files for the ddl_7963.ctl and Upgrade_7963.ctl scripts, which 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.

Note:

Ignore any error messages that indicate tables or indexes could not be dropped from the database. These error messages are displayed when the specified objects do not exist in the database. This can occur because each source system container holds a subset of all data warehouse tables

5. If the data migration was successful, drop the tables that were created during the upgrade process, such as W_xxxx_x_79x, LKP_xxxx_x and 79x_xxxx_TMP.
This step frees the space occupied by these backup tables.

6. Once the data migration steps above are complete, you can delete the Upgrade repository to avoid any accidental use or confusion.

1. In the Informatica Administrator, select the Upgrade repository service.

2. In the General Properties area of the Properties tab, click Edit.

3. Make sure the operating mode of the repository service is set to Exclusive.

4. Click OK.

5. Choose Actions, and then click Delete Contents.

6. In the Delete contents for <repository name> dialog, enter the repository username and password, and then click OK.

3.21 Upgrading the Data Warehouse Schema From Version 7.9.6.3 to 7.9.6.4 and Migrating Data

Perform the procedures in this section to upgrade from Oracle BI Applications release 7.9.6.3 to 7.9.6.4.

This section contains the following procedures:

- Section 3.21.1, "Upgrading the Data Warehouse Schema to Version 7.9.6.4"

- Section 3.21.2, "Migrating Data into the Upgraded Data Warehouse"

- Section 3.21.3, "Verifying the Data Migrated Successfully"

3.21.1 Upgrading the Data Warehouse Schema to Version 7.9.6.4

Follow this procedure to upgrade the data warehouse schema to version 7.9.6.4.

To upgrade the data warehouse schema to version 7.9.6.4:

1. If you are using a DB2 database, run siebproc.sql. This file is located in OracleBI\dwrep\siebproc\db2udb.

2. Generate the scripts to drop and create query indexes. For instructions, see Section B.6, "Generating Scripts to Drop and Create Query and ETL Indexes for Upgrading to Release 7.9.6.4."

3. Run the script to drop query indexes. For instructions, see Section B.7, "Running the Scripts to Drop and Create Query Indexes for Upgrading to Release 7.9.6.4."
Note: You must drop the query indexes before running the scripts to upgrade the schema.

4. If you are using a SQL Server database, run the 7964_UPGRADE_PRE_UPG_CTL_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\SQLServer.

5. Run the UPGRADE_7964.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

6. Run the 7964_UPGRADE_PRE_CTL_SCRIPT.sql script. This file is located in the folder OracleBI\dwrep\Upgrade\DbScripts\<database type>.

7. Run the DDL_7964.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

3.21.2 Migrating Data into the Upgraded Data Warehouse

Follow this procedure to migrate data into the upgraded data warehouse.

To migrate data into the upgraded data warehouse:

1. Run the 7964_UPGRADE_PRE_DIMENSION_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

2. Run the script to drop ETL indexes. For instructions, see Section B.8, "Running the Scripts to Drop and Create ETL Indexes for Upgrading to Release 7.9.6.4."

3. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade repository. For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Upgrade Informatica Repository."

4. Configure the Informatica parameter file 7964_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7964_UPG_PARAMS.txt."

5. In Informatica Workflow Manager, navigate to the folder UPGRADE_7963_to_7964_SBL and execute the first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

6. Run the 7964_UPGRADE_POST_SCRIPT.sql. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

7. Run the script to create ETL indexes. For instructions, see Section B.8, "Running the Scripts to Drop and Create ETL Indexes for Upgrading to Release 7.9.6.4."

8. OracleBI\dwrep\Upgrade\DbScripts\<database type>.

9. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep). For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Base Informatica Repository."

3.21.3 Verifying the Data Migrated Successfully

Follow this procedure to verify that the data was migrated successfully into the upgraded data warehouse.

To verify the data migrated successfully:

1. Validate the data in the upgraded data warehouse.

2. Check whether any of the Informatica mapping log files stored in the <INFA_HOME>\server\infa_shared\Sesslogs directory indicates errors or failures.

3. Check whether the following scripts that you ran in the SQL client of the database failed or errored out while executing:
7964_UPGRADE_PRE_CTL_SCRIPT.sql

7964_UPGRADE_PRE_DIMENSION.sql

dropEtlIndices.sql

createEtlIndices.sql

dropQueryIndices.sql

createQueryIndices.sql

4. Check the log files for the ddl_7964.ctl and Upgrade_7964.ctl scripts, which 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.

Note:

Ignore any error messages that indicate tables or indexes could not be dropped from the database. These error messages are displayed when the specified objects do not exist in the database. This can occur because each source system container holds a subset of all data warehouse tables

5. If the data migration was successful, drop the tables that were created during the upgrade process, such as W_xxxx_x_79x, LKP_xxxx_x and 79x_xxxx_TMP.
This step frees the space occupied by these backup tables.

6. Once the data migration steps above are complete, you can delete the Upgrade repository to avoid any accidental use or confusion.

1. In the Informatica Administrator, select the Upgrade repository service.

2. In the General Properties area of the Properties tab, click Edit.

3. Make sure the operating mode of the repository service is set to Exclusive.

4. Click OK.

5. Choose Actions, and then click Delete Contents.

6. In the Delete contents for <repository name> dialog, enter the repository username and password, and then click OK.

3.22 Localizing the Policy Store

The Oracle BI Applications 7.9.6.4 installer contains different policy stores for different languages. The default policy store that is deployed during the installation is in English. If you want to configure the policy store for any of the other available languages, perform the procedure below.

To configure the policy store for languages other than English:

1. Stop the Oracle BI Services.

2. Copy the system-jazn-data_<LN>.xml file from $ORACLE_BI_HOME\biapps\admin\provisioning\localization\ to $DOMAIN_HOME\config\fmwconfig\.
For example, to implement the policy store for French, you would copy the file system-jazn-data_fr.xml into the \fmwconfig directory.

3. Back up the existing system-jazn-data.xml file in $DOMAIN_HOME\config\fmwconfig\.

4. Rename $DOMAIN_HOME\config\fmwconfig\system-jazn-data_<LN>.xml to system-jazn-data.xml.

5. Start Oracle BI Services.

3.23 Importing the Oracle BI Applications Version 7.9.6.4 LDIF File Into the Embedded LDAP Server

In this procedure, you will import the standard (out-of-the-box) Oracle BI Applications version 7.9.6.4 LDIF file into the WebLogic Server (embedded LDAP server).

To import the Oracle BI Applications version 7.9.6.4 LDIF file:

1. Log in to the WebLogic Server Administration Console using the URL http://<host name>:7001/console.

2. Select the name of the security realm into which the LDIF file is to be imported (for example, myrealm).

3. Select Providers and then the type of provider into which the LDIF file is to be imported (for example, Providers, and then Authentication).

4. Select the security provider in which the LDIF file is to be imported and select Migration, and then select Import.

5. Click Save.

3.24 Upgrading the Siebel Analytics Repository and Web Catalog to the Oracle BI Enterprise Edition 11g Version

Use the Oracle BI Enterprise Edition Upgrade Assistant to upgrade the following repositories and web catalog from the Oracle BI Enterprise Edition 10g format to the 11g format:

- The standard (out-of-the-box) Siebel Analytics Repository version 7.5.x. This repository is the one that you originally received from Oracle as part of your current Siebel Analytics 7.5.x installation. Standard repositories from previous releases are available in the installation folder $ORACLE_BI_HOME\biapps\upgrade.

- The Siebel Analytics Repository you are currently using (the repository deployed in production).

- The Web Catalog you are currently using (the Web Catalog deployed in production).

For instructions on using the Upgrade Assistant, see Oracle Fusion Middleware Upgrade Guide for Oracle Business Intelligence.

Note:

If your Siebel Analytics Repository and Web Catalog are in a Siebel Analytics format, you must first upgrade them to the Oracle BI Enterprise Edition 10g format before you can upgrade them to the 11g format. For more information, see the Oracle Business Intelligence Infrastructure Upgrade Guide Version 10.1.3.2, which is located on the Oracle Technology Network in the Oracle Business Intelligence Suite Enterprise Edition Documentation Library Version 10.1.3.4.1.

Note:

Your current policy store will be merged with the Oracle BI Applications release 7.9.6.4 policy store while upgrading the Oracle BI repository from the 10g format to the 11g format. The final policy store will be the super set of Oracle BI Applications release 7.9.6.4 policy store and the custom and current policy information from the 10g repository.

Also, your current users and groups from the repository will be merged with the Oracle BI Applications release 7.9.6.4 identity store while upgrading the Oracle BI repository from the 10g format to the 11g format. The final identity store will be the super set of the Oracle BI Applications release 7.9.6.4 identity store and the identity store information (users and groups) from the 10g repository.

If you require the policy store to be in a language other than English, perform the steps in Section 3.22, "Localizing the Policy Store."

3.25 Merging Oracle BI Applications Version 7.9.6.4 Repository With Customer Repository

Note:

Before you begin this procedure, you must have already upgraded your Siebel Analytics repository to the Oracle BI Enterprise Edition 11g format. For more information, see Section 3.24, "Upgrading the Siebel Analytics Repository and Web Catalog to the Oracle BI Enterprise Edition 11g Version."

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.25.1, "Preparing for the Oracle BI Repository Upgrade"

- Section 3.25.2, "Equalizing the Oracle BI Repositories"

- Section 3.25.3, "Comparing the Oracle BI Repositories"

- Section 3.25.4, "Merging the Oracle BI Repositories"

The tasks in this section refer to multiple releases of the Oracle BI repository. 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.

Note: Standard repositories from previous releases are available in the folder $ORACLE_BI_HOME\biapps\upgrade.

OracleBIAnalyticsApps.rpd

The standard Oracle BI repository for the version you are upgrading to.

Customer_SiebelAnalyticsApps.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.

3.25.1 Preparing for the Oracle BI Repository Upgrade

Follow this procedure to prepare for the repository upgrade.

To prepare for the Analytics repository upgrade:

1. Set up a directory for the merge process, such as \OracleBIUpgrade, and create the following subfolders:

- Original

- AfterEqualize

- AfterMerge

- AfterManualWork

- AfterRegressions

2. Copy the following repositories to the folder \OracleBIUpgrade\Original:

- The standard (original) repository that you upgraded to the 11g format in Section 3.24, "Upgrading the Siebel Analytics Repository and Web Catalog to the Oracle BI Enterprise Edition 11g Version" (for example, SiebelAnalytics.rpd).

- The production repository that you also upgraded to the 11g format in Section 3.24 (for example, Customer_SiebelAnalyticsApps.rpd.

- The Oracle BI repository from the latest installation (for example, OracleBIAnalyticsApps.rpd)

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 original 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.

3.25.2 Equalizing the Oracle BI Repositories

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, siebelAnalyticsApps_79x.rpd, OracleBIAnalyticsApps.rpd, and Customer_SiebelAnalyticsApps.rpd) are equivalent.

The point of this step is to determine for every object in the OracleBIAnalyticsApps.rpd and the Customer_SiebelAnalyticsApps.rpd whether it is coming from the SiebelAnalyticsApps_79x.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 $ORACLE_BI_HOME\biapps\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.
Table 3-2 provides a list of the available MAP files and the Siebel Analytics or Oracle BI Applications release version associated with the file.

Table 3-2 Rename MAP Files to Be Used for Various Releases

Siebel Analytics / Oracle Business Intelligence Applications Release Version (Upgrading from DW Version)

Rename MAP File to Be Used

Siebel Business Analytics Applications 7.0.x

Not available

Siebel Business Analytics Applications 7.5.x

Not available

Siebel Business Analytics Applications 7.7.x (with Siebel CRM OLTP Pre-7.7.0)

rename77-7964.map

Siebel Business Analytics Applications 7.7.x (with Siebel CRM OLTP 7.7.0)

rename771-7964.map

Siebel Business Analytics Applications 7.8.2 and all 7.8.x versions before this release

rename782-7964.map

Siebel Business Analytics Applications 7.8.3 and all 7.8.x versions after this release

rename783-7964.map

Oracle BI Applications 7.9.0

rename79x-7964.map

Oracle BI Applications 7.9.1

rename79x-7964.map

Oracle BI Applications 7.9.2

rename79x-7964.map

Oracle BI Applications 7.9.3

rename793to7964.map

Oracle BI Applications 7.9.4

rename794to7964.map

Oracle BI Applications 7.9.5

rename79x-7964.map

Oracle BI Applications 7.9.5.1

rename7951to7964.map

Oracle BI Applications 7.9.5.2

rename7951to7964.map

Oracle BI Applications 7.9.6

rename79x-7964.map

Oracle BI Applications 7.9.6.2

rename7963to7964.map

Not required for upgrades from 7.9.6.2 to 7.9.6.3.

Oracle BI Applications 7.9.6.3

rename7963to7964.map

The syntax of the equalizerpds command is as follows:

equalizerpds.exe  [-B [password1]] -C base_repository_name [-E [password2]] -F repository2_name [-J udml_utf8_file_name_equalization] [-O ouput_repository_name] [-Y equalStringSet]
-Y          Treat the characters as equals.
/?          Display this usage information and exit.

To equalize a repository:

1. Copy the appropriate MAP file from the $ORACLE_BI_HOME\biapps\upgrade folder into the folder where you will execute equalizerpds.exe, for example, \OracleBIUpgrade\Original.

2. Run equalizerpds.exe to equalize the repository from the latest installation (for example, OracleBIAnalyticsApps.rpd) with the original repository (for example, SiebelAnalyticsAppss_7x.rpd). An example of the equalizerpds command is as follows:

equalizerpds -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 $ORACLE_BI_HOME\biapps\upgrade folder.

If the equalizerpds.exe executable file runs correctly, no errors are returned.

3. Run equalizerpds.exe to equalize your customized repository (for example, Customer_SiebelAnalytics.rpd) with the original repository (for example, SiebelAnalytics_79x.rpd). An example of the equalizerpds command is as follows:

equalizerpds -B SADMIN
-C \\OracleBIUpgrade\Original\SiebelAnalytics_7x.rpd
-E SADMIN
-F \\OracleBIUpgrade\Original\Customer_SiebelAnalytics.rpd
-O \\OracleBIUpgrade\AfterEqualize\Customer_SiebelAnalytics.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.

4. 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).

3.25.3 Comparing the Oracle BI Repositories

Follow this procedure to compare your existing repository with the new version to which you are upgrading.

To compare the Oracle BI 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 Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition.

3.25.4 Merging the Oracle BI Repositories

In this procedure, you execute the main algorithm to upgrade the repository. For more information on merging the repositories, see Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition.

To merge versions of the Oracle BI repositories:

1. Copy the three repositories (for example, SiebelAnalytics_7x.rpd, OracleBIAnalyticsApps.rpd, and Customer_SiebelAnalytics.rpd) to the AfterMerge folder.

2. Open the repository from the latest installation (for example, OracleBIAnalyticsApps.rpd) in the \OracleBIUpgrade\AfterMerge folder.

3. From the Administration Tool menu bar, select File, then select Merge.

4. Select the Merge Type option Full Repository Merge.

5. In the Select Original Repository dialog box, select the original repository (for example, SiebelAnalytics_7x.rpd).

6. Enter the password for the original repository.

7. In the Select Modified Repository dialog box, select the repository that contains the customizations you made to the previous version of the Analytics repository.

8. Enter the password for the modified repository.

9. In the Saved Merged Repository as dialog box, enter the name for the merged repository, for example, Merged_Repository_OracleBIAnalyticsApps.rpd.
The new repository will contain the final results of the merge.

10. Select the Equalize during merge check box.

11. Click Next.

12. In the Decision drop-down list, select the action you want to take regarding the repository change, or accept the default action.

13. To locate subsequent rows with empty Decision fields, click the Decision header cell.
When all rows have a value in the Decision field, the Finish button is enabled.

14. Select the Check consistency of the merged RPD check box.

15. Click Finish.
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.

16. 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'

17. Copy the repository to the folder \OracleBIUpgrade\AfterManualWork.

3.26 Merging Oracle BI Applications Version 7.9.6.4 Presentation Catalog With Current (Custom) Catalog

Note:

Before you begin this procedure, you must have already upgraded your current (custom) catalog to the Oracle BI Enterprise Edition 11g format. For more information, see Section 3.24, "Upgrading the Siebel Analytics Repository and Web Catalog to the Oracle BI Enterprise Edition 11g Version."

You need to perform the following tasks to complete the presentation merge process.

- Section 3.26.1, "Trimming the Input Presentation Catalog"

- Section 3.26.2, "Merging the Oracle BI Applications Version 7.9.6.4 Presentation Catalog With Current (Custom) Catalog"

- Section 3.26.3, "Testing the Results of the Presentation Catalog Upgrade"

These procedures use the following terminology to identify the various presentation catalogs you will use in the merge process:

- 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 standard Oracle BI Applications 7.9.6.4 presentation catalog that is installed with Oracle BI Applications.

- The current presentation catalog. This is the presentation catalog currently in use at your organization.

Caution:

In releases of Oracle BI Applications previous to 7.9, the Oracle BI 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 Fusion Middleware Upgrade Guide for Oracle Business Intelligence

3.26.1 Trimming the Input Presentation Catalog

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.

3.26.2 Merging the Oracle BI Applications Version 7.9.6.4 Presentation Catalog With Current (Custom) Catalog

Note:

Before you begin this procedure, you must have already upgraded your current (custom) catalog to the Oracle BI Enterprise Edition 11g format. For more information, see Section 3.24, "Upgrading the Siebel Analytics Repository and Web Catalog to the Oracle BI Enterprise Edition 11g Version."

Follow the instructions in this section to merge the Oracle BI Applications version 7.9.6.4 presentation catalog with the catalog you are currently using. This procedure uses the Oracle BI Enterprise Edition Catalog Manager. High-level steps for the merge process are provided in this section. For detailed instructions on using the Catalog Manager, see the chapter "Configuring and Managing the Oracle BI Presentation Catalog," in the Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition 11g Release 1 (11.1.1).

To merge the Oracle BI Applications version 7.9.6.4 presentation catalog with the current (custom) catalog:

1. Start the Catalog Manager, and open your current (custom) presentation catalog in offline mode.
For instructions, see "Starting Catalog Manager and Opening Catalogs," in the Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition 11g Release 1 (11.1.1).

2. Start another instance of the Catalog Manager, and open the Oracle BI Applications version 7.9.6.4 (out-of-the-box) presentation catalog in offline mode.

3. Copy and paste the custom objects from your current presentation catalog into the Oracle BI Applications version 7.9.6.4 (out-of-the-box) presentation catalog.
For instructions, see "Working with Objects in Catalog Manager," in the Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition 11g Release 1 (11.1.1).

4. If you created custom catalog groups that are not in the version 7.9.6.4 presentation catalog, you need to convert the custom catalog groups to application roles in order to maintain consistency with the version 7.9.6.4 presentation catalog.
To convert custom catalog groups to application roles, run the following command:

runcat.cmd/runcat.sh -cmd replaceAccountInPermissions -old <Catalog Group Name> -oldType group -new <App Role Name> -newType role -offline  <catalog path>

For example:

runcat.cmd -cmd replaceAccountInPermissions -old "AP Analyst" -oldType group -new "AP Analyst" -newType role -offline  c:/SampleWebcat

This command replaces a specified account with another in all catalog object ACLs and privileges in the presentation catalog, entirely in the offline mode. If an entirely new application role is specified as the replacement account, then it is necessary to refresh the GUIDs in the presentation catalog before it can be used.

Note: If the specified replacement user or group is not already present in the presentation catalog 11g Release 1 (11.1.1) already, then this operation will fail.

For more information, see the Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition 11g Release 1 (11.1.1).

3.26.3 Testing the Results of the Presentation Catalog Upgrade

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.

3.27 Regression Testing the Oracle BI Repository Merge

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:

1. 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.

2. 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 Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition.

3. Execute the logical SQL against the old repository using the command line utility nQCmd.exe located in $ORACLE_BI_HOME\bifoundation\server\bin, and save the results to a file.
For information about the nQCmd.exe utility, see Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition.

4. Edit the logical SQL test scripts to account for the name changes or modifications resulting from the upgrade.

5. Execute the edited logical SQL against the merged repository, and save the results.

6. 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.

4 Upgrading Siebel Business Analytics 7.7, 7.7.x and 7.8.x

This section contains instructions for upgrading Oracle's Siebel Business Analytics releases 7.7, 7.7.x, and 7.8.x.

This section includes the following topics:

- Section 4.1, "Prerequisites for Upgrading Oracle BI Applications"

- Section 4.2, "Upgrading Oracle BI Infrastructure to Version 11g"

- Section 4.3, "Upgrading Oracle BI Applications"

- Section 4.4, "Upgrading to Informatica PowerCenter Version 9.0.1 Hotfix 2"

- Section 4.5, "Upgrading the Informatica Repository"

- Section 4.6, "Upgrading the Informatica Repository When You Are Already Running Informatica PowerCenter 9.1"

- Section 4.7, "Verifying Configurations for Informatica PowerCenter Version 9.0.1 Hotfix 2 to Work With Oracle BI Applications and DAC"

- Section 4.8, "Upgrading to and Configuring DAC Version 11g"

- Section 4.9, "Overview of Upgrading the Data Warehouse Schema and Migrating Data for Non-Teradata Databases"

- Section 4.10, "Upgrading the Data Warehouse Schema to Version 7.9.0 for Non-Teradata Databases"

- Section 4.11, "Importing New Schema Definitions Into the Siebel Transactional Database"

- Section 4.12, "Migrating Data into the Data Warehouse Upgraded to Version 7.9.0 for Non-Teradata Databases"

- Section 4.13, "Upgrading the Data Warehouse Schema to Version 7.9.4 and Migrating Data for Non-Teradata Databases"

- Section 4.14, "Upgrading the Data Warehouse Schema to Version 7.9.5 and Migrating Data for Non-Teradata Databases"

- Section 4.15, "Upgrading the Data Warehouse Schema to Version 7.9.5.1 for Non-Teradata Databases"

- Section 4.16, "Upgrading the Data Warehouse Schema From Version 7.9.5.1 to 7.9.6.1 and Migrating Data for Non-Teradata Databases"

- Section 4.17, "Upgrading the Data Warehouse Schema From Version 7.9.6 to 7.9.6.1 and Migrating Data for Non-Teradata Databases"

- Section 4.18, "Upgrading the Data Warehouse Schema From Version 7.9.6.1 to 7.9.6.2 and Migrating Data for Non-Teradata Databases"

- Section 4.19, "Upgrading the Data Warehouse Schema From Version 7.9.6.2 to 7.9.6.3 and Migrating Data for Non-Teradata Databases"

- Section 4.20, "Upgrading the Data Warehouse Schema From Version 7.9.6.3 to 7.9.6.4 and Migrating Data"

- Section 4.21, "Upgrading the Data Warehouse Schema and Migrating Data for Teradata Databases"

- Section 4.22, "Localizing the Policy Store"

- Section 4.23, "Importing the Oracle BI Applications Version 7.9.6.4 LDIF File Into the Embedded LDAP Server"

- Section 4.24, "Upgrading the Siebel Analytics Repository and the Web Catalog to the Oracle BI Enterprise Edition 11g Version"

- Section 4.25, "Merging Oracle BI Applications Version 7.9.6.4 Repository With Customer Repository"

- Section 4.26, "Merging Oracle BI Applications Version 7.9.6.4 Presentation Catalog With Current (Custom) Catalog"

- Section 4.27, "Regression Testing the Oracle BI Repository Merge"

4.1 Prerequisites for Upgrading Oracle BI Applications

Complete the following prerequisites before upgrading to Oracle BI Applications release 7.9.6.4:

- The DAC Client requires an ODBC connection to the Oracle Business Analytics Warehouse when the database type is Oracle, SQL Server, DB2, and DB2-390 in order to upgrade the data warehouse schema using the DDL Import Utility.
Additionally, Siebel CRM source systems require an ODBC connection to the OLTP (source) database on the machine where Oracle BI Applications software is installed. This ODBC connection will be used by the DDLIMP utility.

Before you upgrade to Oracle BI Applications verify whether you have the appropriate ODBC connections set. If you do not, see Appendix F, "Creating ODBC Database Connections for DAC."

4.2 Upgrading Oracle BI Infrastructure to Version 11g

You must upgrade Oracle BI Infrastructure to version 11g. For the specific release of Oracle BI Infrastructure 11g that is supported for this release of Oracle BI Applications, see the System Requirements and Supported Platforms for Oracle Business Intelligence Applications. For information on installing the supported version of Oracle BI Infrastructure, see the Oracle Fusion Middleware Upgrade Guide for Oracle Business Intelligence.

4.3 Upgrading Oracle BI Applications

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 Guide for Informatica PowerCenter Users.

Note the following points:

- Review "Chapter 3: Preinstallation and Predeployment Requirements for Oracle BI Applications," in the Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users. You must satisfy these requirements in order to upgrade to the current version of Oracle BI Applications.

- Perform only the step that addresses the running of the installer. Do not perform the configuration instructions that follow the running of the installer.

- If you have a previous release of Oracle BI Applications installed, you must uninstall it before you run the installer for the current release. If you do not uninstall the old release, some folders from the current release will not be correctly installed. (Make a back-up of your DAC folder before you uninstall the old release. This will be the backup of your DAC Client and Server and the DAC metadata files.)

4.4 Upgrading to Informatica PowerCenter Version 9.0.1 Hotfix 2

You must install Informatica PowerCenter 9.0.1 Hotfix 2 to run the current version of Oracle BI Applications. See the System Requirements and Supported Platforms for Oracle Business Intelligence Applications for information about additional hotfixes or emergency bug fixes that may be required to support the current version of Informatica.

Note:

Oracle BI Applications release 7.9.6.4 is also certified to run with Informatica PowerCenter version 9.1 Hotfix 2. For instructions on upgrading the Informatica Repository if you have previously upgraded to Informatica PowerCenter 9.1 Hotfix 2, see Section 4.6, "Upgrading the Informatica Repository When You Are Already Running Informatica PowerCenter 9.1."

The components and architecture for Informatica PowerCenter 9.x differ significantly from Informatica PowerCenter 7.x and 8.x. Oracle recommends that you carefully review the Informatica PowerCenter 9.0.1 documentation.

For a summary of installation instructions for installing Informatica PowerCenter 9.0.1 on a single machine in an Oracle BI Applications deployment, see the Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users.

For detailed information about deploying Informatica PowerCenter 9.0.1, refer to the Informatica PowerCenter Installation and Configuration Guide, Informatica Upgrade Guide for PowerCenter 8.1.x, Informatica Upgrade Guide for PowerCenter 8.5.x and 8.6.x, Informatica Administrator Guide, and related documentation. See the Oracle Business Intelligence Applications Release Notes, available on the Oracle Technology Network, for information about how to locate the Informatica documentation.

To upgrade to Informatica PowerCenter 9.0.1 Hotfix 2:

- Perform the pre-upgrade, upgrade, and post-upgrade steps documented in Informatica Upgrade Guide for PowerCenter 8.1.x or Informatica Upgrade Guide for PowerCenter 8.5.x and 8.6.x, depending on which version of Informatica PowerCenter you are upgrading from.

Note the following points:

- The Informatica PowerCenter 9.0.1 installation process includes upgrading your current Informatica Repository to the version 9.0.1 format. This process is necessary so that you will be able to access your current repository using the version 9.0.1 client tools and so that you can perform the procedure Section 4.5, "Upgrading the Informatica Repository."
In Section 4.5, "Upgrading the Informatica Repository," you back up and rename your current repository and then restore the Informatica Repository that is installed during the Oracle BI Applications installation (for example, Oracle_BI_DW_Base.rep). You then copy the folders containing the Oracle BI Applications content for release 7.9.6.4 to your existing repository.

- If you install Informatica PowerCenter 9.0.1 using the installer Upgrade option rather than the Install option, the property $PMRootDir is not updated to the upgraded service version installation directory. You need to configure this property to specify the upgraded service installation directory in order for DAC to be able to locate the Informatica source files.
To configure the $PMRootDir property: launch Informatica Administrator, select the Integration Service from the Navigator, click the Processes tab, and click Edit. Then, enter the appropriate value for $PMRootDir.

4.5 Upgrading the Informatica Repository

Follow this procedure to upgrade the Informatica Repository when you are upgrading the Informatica PowerCenter platform from version 7.x or 8.x to 9.0.1 Hotfix 2. If you have already upgraded to Informatica PowerCenter 9.1, follow the procedure in Section 4.6, "Upgrading the Informatica Repository When You Are Already Running Informatica PowerCenter 9.1."

In this procedure, you will copy the folders containing the Oracle BI Applications 7.9.6.4 content into your current, existing Informatica Repository. The result of this action is an Informatica Repository that contains your customizations along with the new Oracle BI Applications 7.9.6.4 content.

For detailed instructions on backing up and restoring the Informatica Repository, see the topic titled, "Backing Up and Restoring the PowerCenter Repository," in "Chapter 15: PowerCenter Repository Management," in the Informatica PowerCenter Administrator Guide. See the Oracle Business Intelligence Applications Release Notes, available on the Oracle Technology Network, for information about how to locate the Informatica documentation.

To upgrade the Informatica Repository:

1. Make sure you have backed up and renamed your current, existing Informatica Repository.

2. Copy the Oracle_BI_DW_Base.rep file (or Oracle_BI_DW_Teradata.rep for repositories on Teradata databases) from the folder OracleBI\dwrep\Informatica\Repository into the folder <INFA_HOME>\server\infa_shared\Backup.

Note:

The Oracle_BI_DW_Base.rep file is installed in the OracleBI root directory when you run the Oracle BI Applications installer, as described in Section 4.3, "Upgrading Oracle BI Applications."

3. Using Informatica PowerCenter Administrator, create a new Repository Service for the Oracle_BI_DW_Base.rep repository. See "Setup Step: Creating the Informatica Repository Service," in Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users for instructions.

4. Using the Repository Service you created in the step above, restore the Oracle_BI_DW_Base.rep repository into an empty schema. See "Restoring the Prebuilt Informatica Repository for Environments in English" or "Restoring the Prebuilt Informatica Repository on a Non-English Operating System" in Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users for instructions.
This step gives you the Oracle BI Applications 7.9.6.4 Informatica Repository in the Informatica 9.0.1 format.

5. Launch the Informatica PowerCenter Repository Manager, and connect to the repository you restored in step 4 (for example, Oracle_BI_DW_Base.rep), and connect to your current, existing Informatica Repository.
Note: Your current, existing repository should have been updated to the version 9.0.1 format during the Informatica PowerCenter 9.0.1 installation process.

6. In your current, existing repository, make sure all of your customizations are in a "Custom" folder.

7. In your current, existing repository, delete the following folders:

- PLP

- All folders with the prefix SDE_

- SILOS

- SIL_VERT

- UA_SDE

- UA_SIL

Make sure you do not delete the "Custom" folder.

8. Copy the following folders containing the Oracle BI Applications content for release 7.9.6.4 from the newly restored repository (Oracle_BI_DW_Base.rep) into your current, existing repository.

- PLP

- All folders with the prefix SDE_

- SILOS

- SIL_VERT

- UA_SDE

- UA_SIL

This action updates your current, existing repository with the Oracle BI Applications 7.9.6.4 content; this is the repository you will use to run ETL in Oracle BI Applications 7.9.6.4.

The version 7.9.6.4 repository (Oracle_BI_DW_Base.rep) and the Repository Service for this repository are no longer needed.

4.6 Upgrading the Informatica Repository When You Are Already Running Informatica PowerCenter 9.1

If you are upgrading to Oracle BI Applications 7.9.6.4 and previously upgraded Informatica PowerCenter to version 9.1 Hotfix 2, you must first restore the Oracle BI Applications version 7.9.6.4 Informatica Repository using Informatica PowerCenter 9.0.1 Hotfix 2. Then, you can upgrade this repository to the Informatica 9.1 format by pointing to it using Informatica 9.1 client tools. After the Oracle BI Applications 7.9.6.4 Informatica Repository has been upgraded to the Informatica 9.1 format, you can then copy the folders containing the Oracle BI Applications 7.9.6.4 content into your current, existing Informatica Repository. The result of this action is an Informatica Repository that contains your customizations along with the new Oracle BI Applications 7.9.6.4 content.

For detailed instructions on backing up and restoring the Informatica Repository, see the topic titled, "Backing Up and Restoring the PowerCenter Repository," in "Chapter 15: PowerCenter Repository Management," in the Informatica PowerCenter Administrator Guide. See the Oracle Business Intelligence Applications Release Notes, available on the Oracle Technology Network, for information about how to locate the Informatica documentation.

To upgrade the Informatica Repository when already running Informatica PowerCenter 9.1:

1. Make sure you have backed up and renamed your current, existing Informatica Repository.

2. Install Informatica PowerCenter Services version 9.0.1 Hotfix 2. You do not need to install the Informatica PowerCenter Client Tools. See Section 4.4, "Upgrading to Informatica PowerCenter Version 9.0.1 Hotfix 2" for instructions.

3. Copy the Oracle_BI_DW_Base.rep file (or Oracle_BI_DW_Teradata.rep for repositories on Teradata databases) from the folder OracleBI\dwrep\Informatica\Repository into the Informatica PowerCenter 9.0.1 folder <INFA_HOME>\server\infa_shared\Backup.

Note:

The Oracle_BI_DW_Base.rep file is installed in the OracleBI root directory when you run the Oracle BI Applications installer, as described in Section 4.3, "Upgrading Oracle BI Applications."

4. Using Informatica PowerCenter Administrator, create a new Repository Service for the Oracle_BI_DW_Base.rep repository. See "Setup Step: Creating the Informatica Repository Service," in Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users for instructions.

5. Using the Repository Service you created in the step above, restore the Oracle_BI_DW_Base.rep repository into an empty schema. See "Restoring the Prebuilt Informatica Repository for Environments in English" or "Restoring the Prebuilt Informatica Repository on a Non-English Operating System" in Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users for instructions.
This step gives you the Oracle BI Applications 7.9.6.4 Informatica Repository in Informatica 9.0.1 format.

6. Launch the Informatica PowerCenter Repository Manager, and connect to the repository you restored in step 5. When prompted to upgrade the repository to the 9.1 format, do so.

7. In Repository Manger, connect to your current, existing Informatica Repository.

8. In your current, existing repository, make sure all of your customizations are in a "Custom" folder.

9. In your current, existing repository, delete the following folders:

- PLP

- All folders with the prefix SDE_

- SILOS

- SIL_VERT

- UA_SDE

- UA_SIL

Make sure you do not delete the "Custom" folder.

10. Copy the following folders containing the Oracle BI Applications content for release 7.9.6.4 from the newly restored repository (Oracle_BI_DW_Base.rep) into your current, existing repository.

- PLP

- All folders with the prefix SDE_

- SILOS

- SIL_VERT

- UA_SDE

- UA_SIL

This action updates your current, existing repository with the Oracle BI Applications 7.9.6.4 content; this is the repository you will use to run ETL in Oracle BI Applications 7.9.6.4.

The version 7.9.6.4 repository (Oracle_BI_DW_Base.rep) and the Repository Service for this repository are no longer needed.

4.7 Verifying Configurations for Informatica PowerCenter Version 9.0.1 Hotfix 2 to Work With Oracle BI Applications and DAC

Informatica PowerCenter version 9.0.1 Hotfix 2 requires configuration for it to work with Oracle BI Applications and DAC. The configuration settings from your earlier Informatica environment may have been retained when you upgraded to Version 9.0.1 Hotfix 2. Verify or perform the procedures listed below, as documented in the Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users:

- Copying Source Files and Lookup Files

- Setting PowerCenter Integration Services Relaxed Code Page Validation

- Setting PowerCenter Integration Services Custom Properties

- Creating the Repository Administrator User in the Native Security Domain

4.8 Upgrading to and Configuring DAC Version 11g

This section includes instructions for upgrading the DAC platform and repository to version 11g as well as information about configurations you must set or verify.

This section includes the following topics:

- Section 4.8.1, "Installing the DAC Platform and Oracle BI Applications Metadata Repository Files"

- Section 4.8.2, "Configuring the DAC Client and Server to Work With Oracle BI Applications and Informatica"

- Section 4.8.3, "Upgrading the DAC Repository"

4.8.1 Installing the DAC Platform and Oracle BI Applications Metadata Repository Files

The current release of DAC 11g is installed by its own installer and not the Oracle BI Applications installer. For information about the specific release of DAC 11g that is supported for this release of Oracle BI Applications, see System Requirements and Supported Platforms for Oracle Business Intelligence Applications.

After you install DAC 11g, you then need to copy metadata files from the machine hosting Oracle BI Applications to the machines hosting the DAC Client and Server. You then need to import the new metadata into the DAC Repository. For instructions on performing these tasks, see the following sections in the Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users:

- Installing and Setting Up the DAC Platform

Note:

You must perform all of the procedures in this section, including installing JDBC drivers, creating ODBC database connections, and installing pmrep and pmcmd command line programs.

- Installing DAC Metadata Files

- Logging into DAC for the First Time and Importing Metadata into the DAC Repository

Note:

When you perform this step, DAC will prompt you to upgrade the repository. Click Yes. This action will upgrade your repository in the 10g format to the 11g format.

After you complete this procedure, you will have the default DAC Repository for Oracle BI Applications release 7.9.6.4.

4.8.2 Configuring the DAC Client and Server to Work With Oracle BI Applications and Informatica

The DAC Client and Server require configuration to work with Oracle BI Applications and Informatica PowerCenter. The configuration settings from your earlier DAC environment may have been retained when you upgraded to version 11g. Verify or perform the procedures listed below, as documented in the Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users:

- Configuring the DAC Server

- Configuring DAC Integration Settings

- Configuring the SiebelUnicodeDB Custom Property

Note:

This procedure is required only if your source to target data movement configuration is Unicode to Unicode.

- Setting Up DAC to Receive Email Notification

- Additional Configuration Tasks
In this section, perform only the tasks that apply to your environment.

4.8.3 Upgrading the DAC Repository

To upgrade the DAC Repository, you perform a two-step process:

1. You first upgrade the existing DAC Repository from the 10g format to the 11g format. When you log into DAC 11g for the first time, DAC will prompt you to upgrade your repository. Click Yes.
For more information, see "Upgrading to DAC 11g" in Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Data Warehouse Administration Console and "Logging Into DAC for the First Time and Importing Metadata into the DAC Repository" in Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users.

2. You then use the DAC's Upgrade/Merge Wizard to complete the upgrade of your existing DAC Repository.

- If you are upgrading to Oracle BI Applications release 7.9.6.4, and you are remaining on the same version of the transactional source system, you would use the Refresh Base option of the DAC Upgrade/Merge Wizard to complete the upgrade of your existing DAC Repository. For information about how to use the Refresh Base option, see the topic titled, "About the Refresh Base Option," in the chapter "Upgrading, Comparing and Merging DAC Repositories," in the Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Data Warehouse Administration Console.

- If you are upgrading your transactional system, for example, from Oracle EBS release 12 to release 12.2, you would use the Replace Base option of the DAC Upgrade/Merge Wizard to complete the upgrade of your existing DAC Repository. For information about how to use the Replace Base option, see the topic titled, "About the Replace Base Option," in "Upgrading, Comparing and Merging DAC Repositories," in the Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Data Warehouse Administration Console.

The Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Data Warehouse Administration Console is available in the Oracle Business Intelligence Data Warehouse Administration Console Documentation Library on the Oracle Technology Network.

4.9 Overview of Upgrading the Data Warehouse Schema and Migrating Data for Non-Teradata Databases

The process for upgrading the data warehouse schema and migrating data for Siebel Business Analytics releases 7.7, 7.7.x, and 7.8.x involves multiple phases, as described below.

Note:

The Oracle BI Applications upgrade logic is coded such that you must complete each of the phases listed below. To upgrade to the current release of Oracle BI Applications, you cannot skip any of the phases.

- Phase 1
In phase 1, you will perform the following steps:

1. Upgrade the data warehouse schema to version 7.9.0. For instructions, see Section 4.10.

2. Import new schema definitions into the Siebel transactional database. For instructions, see Section 4.11.

3. Migrate data into the data warehouse upgraded to version 7.9.0. For instructions, see Section 4.12.

- Phase 2
In phase 2, you will upgrade your data warehouse schema to version 7.9.4 and migrate data into the upgraded data warehouse. For instructions, see Section 4.13.

- Phase 3
In phase 3, you will upgrade your data warehouse schema to version 7.9.5 and migrate data into the upgraded data warehouse. For instructions, see Section 4.14.

- Phase 4
In phase 4, you will upgrade your data warehouse schema to version 7.9.5.1. For instructions, see Section 4.15.

- Phase 5
In phase 5, you will do one of the following:

- Upgrade your data warehouse schema from version 7.9.5.1 to version 7.9.6.1 and migrate data. For instructions, see Section 4.16.

- If you are currently running Oracle BI Applications version 7.9.6 and using an Oracle database, you can upgrade your data warehouse schema to version 7.9.6.1 and migrate data. For instructions, see Section 4.17.

- Phase 6
In phase 6, you will upgrade your data warehouse schema to version 7.9.6.2 and migrate data. For instructions, see Section 4.18.

- Phase 7
In phase 7, you will upgrade your data warehouse schema to version 7.9.6.3 and migrate data. For instructions, see Section 4.19.

- Phase 8
In phase 8, you will upgrade your data warehouse schema to version 7.9.6.4 and migrate data. For instructions, see Section 4.20.

4.10 Upgrading the Data Warehouse Schema to Version 7.9.0 for Non-Teradata Databases

This procedure adds new tables, columns, and indexes to the existing data warehouse schema. It also modifies the existing data warehouse schema objects.

To upgrade the data warehouse schema:

1. Run the UPGRADE.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

2. Run the 790_UPGRADE_PRE_CTL_SCRIPT.sql script.

1. Open the SQL client for your database type.

2. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\<database type>.

3. Open the 790_UPGRADE_PRE_CTL_SCRIPT.sql file, and copy the contents into the SQL client.

4. Execute the script.

3. Run the DW.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

4. Run the 790_UPGRADE_PRE_DIMENSION_SCRIPT.sql script. This file is located in the folder OracleBI\dwrep\Upgrade\DbScripts\<database type>.

4.11 Importing New Schema Definitions Into the Siebel Transactional Database

This procedure upgrades transactional database objects that relate to Oracle Business Intelligence Applications. It does not upgrade transactional database objects for Siebel CRM applications.

To import new schema definitions into the Siebel transactional database:

1. Import schema definitions for non-image tables:

1. Access the DDLimp utility.

2. Run the DDL_OLTP.ctl script that is located in the OracleBI\dwrep\Upgrade\CTLFiles folder.
Note: If you receive an error message stating a particular object already exists in the database, use the DDLimp Merge argument (/M Y) in the DDLimp command to resolve the error.

2. Import schema definitions for image tables:

1. In DAC, go to the Design view, and select your custom container from the drop-down list to the right of the Execute button.

2. Click the Tables tab.

3. Query for all tables for which the image suffix is not null.

4. Right-click in the list of tables returned by the query, and select Change Capture Scripts, and then Generate Image and Trigger Scripts.

5. In the Triggers and Image Tables dialog box, do the following:
- Select the option All Tables in the List.

- Select the option Generate Image Table Scripts.

- Select the appropriate database type for the source system.

- Click OK.

6. Open the SQL client for the source system database type, for example, SQL Plus for Oracle, Query Analyzer for SQL Server, or a command window for DB2.
The script may contain many lines; therefore, you can save the script file as a SQL file and execute it in a SQL client.

7. Copy the scripts generated by DAC into the SQL client and execute them.

4.11.1 Verifying the Siebel Transactional Database Upgrade

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_xxx

- S_ETL_I_IMG_xxx

- S_ETL_D_IMG_xxx

- S_ETL_PARAM

- S_ETL_PRD_ATTR

- S_ETL_PRD_REL

4.12 Migrating Data into the Data Warehouse Upgraded to Version 7.9.0 for Non-Teradata Databases

Follow this procedure to migrate data into the upgraded data warehouse.

To migrate data into the upgraded data warehouse:

1. Copy the file Upgrade.rep from the folder OracleBI\dwrep\Upgrade\Informatica\Repository into the folder <INFA_HOME>\server\infa_shared\Backup.

2. Launch the Informatica Administrator, and restore Upgrade.rep (located in <INFA_HOME>\server\infa_shared\Backup) into a database other than the database in which you restored Oracle_BI_DW_Base.rep.

3. 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, <INFA_HOME>\server\infa_shared\SrcFiles.

4. Navigate to the folder OracleBI\dwrep\Upgrade\Informatica\ParameterFiles and copy the file <previous version of Siebel Analytics>_TENERIFE_UPG_PARAMS.txt into the SrcFiles folder on the Informatica Server machine, for example, <INFA_HOME>\server\infa_shared\SrcFiles.

5. Rename the file <previous version of Siebel Analytics>_TENERIFE_UPG_PARAMS.txt to TENERIFE_UPG_PARAMS.txt.

6. In the file TENERIFE_UPG_PARAMS.txt:

1. Search for the parameter $$SourceConnection.

2. Set the value to match your Siebel applications (OLTP) version:

- SEBL_63

- SEBL_753

- SEBL_771

- SEBL_78

- SEBL_80 (use this value for OLTP versions 8.x and 8.1.1)

- SEBL_VERT_753

- SEBL_VERT_771

- SEBL_VERT_78

- SEBL_VERT_80 (use this value for OLTP versions 8.x and 8.1.1)

For example, if your Siebel applications (OLTP) version is Siebel Industry Applications 7.8, the parameter should appear as:

$$SourceConnection=SEBL_VERT_78

7. In the file TENERIFE_UPG_PARAMS.txt:

1. Search for the parameter $$Source_Container.

2. Set the value to match your Siebel applications (OLTP) version:

- Siebel 6.3

- Siebel 7.5.3

- Siebel 7.7.1

- Siebel 7.8

- Siebel 8.0 (use this value for OLTP versions 8.x and 8.1.1)

- Siebel 7.5.3 Vertical

- Siebel 7.7.1 Vertical

- Siebel 7.8 Vertical

- Siebel 8.0 Vertical (use this value for OLTP versions 8.x and 8.1.1)

For example, if your Siebel applications (OLTP) version is Siebel Industry Applications 7.8, the parameter should appear as:

$$Source_Container=Siebel 7.8 Vertical

8. 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.

9. 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

10. In the Informatica Workflow Manager, open the Relational Connection Browser (in the menu bar, select Connections, and then select Relational), and edit the connect string, user and password for the relational connections as follows:

1. Edit the PARAM_OLTP_SIEBEL connection to point to the Siebel transactional database.

2. Edit the DataWarehouse connection to point to the newly upgraded data warehouse database.

3. Create or edit the PARAM_DAC_OLD connection to point to the previous DAC Repository database (the version from which you are upgrading).

4. Create or edit the PARAM_DAC_NEW connection to point to the DAC Repository database.

Note:

If you are connected to an Oracle database, use the 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.

11. If you are upgrading from Siebel Industry Applications (Vertical), define the alignment rule to be used for ETL loads.

1. 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, <INFA_HOME>\server\infa_shared\SrcFiles.

2. Rename the file AlignmentType_LS_782.csv to AlignmentType.csv.

3. Open the file AlignmentType.csv, and enter one of the following alignment item types under the ALIGN_TYPE field:

- Zipcode

- Account/Contact

- Brick

4. Save the file.

The Oracle Business Analytics Warehouse allows only one alignment type to be used for ETL loads during upgrade.

12. In Informatica Workflow Manager, navigate to the appropriate folder and execute the workflows in the order specified:

Application Version

Folder Name

Workflow

7.7 to 7.9

UPGRADE_770_to_79

- 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

7.7.1.x to 7.9

UPGRADE_771_to_79

- 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

7.8 to 7.9

UPGRADE_78_to_79

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

13. If you upgraded your transactional database to Siebel Applications 8.x or 8.1.1, navigate to the folder UPGRADE_790_to_791_SBL80UPG and run the following workflows in the order specified:

1. UPGRADE_DIMENSIONS

2. UPGRADE_FACTS

14. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep). For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Base Informatica Repository."

15. To verify the data migrated successfully:

1. Validate the data in the upgraded data warehouse.

2. Check whether any of the Informatica mapping log files stored in the directory <INFA_HOME>\server\infa_shared\SessLogs indicates errors or failures.

3. 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.

4. 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.

Note:

Ignore any error messages that indicate tables or indexes could not be dropped from the database. These error messages are displayed when the specified objects do not exist in the database. This can occur because each source system container holds a subset of all data warehouse tables.

16. 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.

4.13 Upgrading the Data Warehouse Schema to Version 7.9.4 and Migrating Data for Non-Teradata Databases

Follow this procedure to upgrade the data warehouse schema to version 7.9.4 and migrate data.

To upgrade the data warehouse schema and migrate data:

1. Run the 792_UPGRADE_PRE_CTL_SCRIPT.sql script. This file is located in the folder OracleBI\dwrep\Upgrade\DbScripts\<database type>.

2. Run the ddl_794.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

3. Run the 792_UPGRADE_PRE_DIMENSION_SCRIPT.sql script. This file is located in the folder OracleBI\dwrep\Upgrade\DbScripts\<database type>.

4. If you upgraded your transactional database to Siebel Applications 8.x or 8.1.1, run the workflows to migrate your data into the upgraded data warehouse.

1. In Informatica Workflow Manager, navigate to the folder UPGRADE_790_TO_791_SBL80UPG.

2. Run the following workflows in the order specified:
UPGRADE_DIMENSIONS

UPGRADE_FACTS

5. Verify the data migrated successfully by checking whether any of the Informatica mapping log files stored in the <INFA_HOME>\server\infa_shared\SessLogs directory indicate errors or failures. Also, validate the data in the upgraded data warehouse.

6. If the data migration was successful, drop the tables that were created during the upgrade process, such as, W_xxxx_x_79x tables, LKP_xxxx_x and 79x_XXXX_TMP.
This step frees the space occupied by these backup tables.

7. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep). For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Base Informatica Repository."

4.14 Upgrading the Data Warehouse Schema to Version 7.9.5 and Migrating Data for Non-Teradata Databases

Follow this procedure to upgrade the data warehouse schema to version 7.9.5 and migrate data.

To upgrade the data warehouse schema and migrate data:

1. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade repository. For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Upgrade Informatica Repository."

2. Run the 795_UPGRADE_PRE_CTL_SCRIPT.sql script. This file is located in the folder OracleBI\dwrep\Upgrade\DbScripts\<database type>.

3. Run the UPGRADE_795.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

4. Run the ddl_795.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

5. Run the 795_UPGRADE_PRE_DIMENSION_SCRIPT.sql script. This file is located in the folder OracleBI\dwrep\Upgrade\DbScripts\<database type>.

6. Copy all of the domain value files in the folder \OracleBI\dwrep\Informatica\LkpFiles into the folder <INFA_HOME>\server\infa_shared\LkpFiles.

7. Migrate data into the upgraded data warehouse.

1. Copy the file Upgrade.rep from the folder OracleBI\dwrep\Upgrade\Informatica\Repository into the folder <INFA_HOME>\server\infa_shared\Backup.

2. Launch the Informatica Administrator, and restore Upgrade.rep (located in <INFA_HOME>\server\infa_shared\Backup).

3. Configure the Informatica parameter file 795_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 795_UPG_PARAMS.txt."

4. In Informatica Workflow Manager, open the Relational Connection Browser (in the menu bar, select Connections, and then select Relational), and edit the connect string, user and password for the relational connections as follows: create one relational connection based on the appropriate database platform for your OLTP database. Create the connection with the name PARAM_OLTP.
Edit PARAM_OLTP connection to match your OLTP environment.

Edit the PARAM_OLAP connection to match your OLAP environment.

Note:

If you are connected to an Oracle database, use the 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.

5. In Informatica Workflow Manager, navigate to the folder UPGRADE_794_to_795_SBL and execute the UPGRADE_DIMENSIONS workflow.

8. Verify the data migrated successfully.

1. Validate the data in the upgraded data warehouse.

2. Check whether any of the Informatica mapping log files stored in the <INFA_HOME>\server\infa_shared\Sesslogs directory indicates errors or failures.

3. Check whether the script 795_UPGRADE_PRE_DIMENSION_SCRIPT.sql that you ran in the SQL client of the database failed or errored out while executing.

4. Check the log file for ddl_795 and script Upgrade_795.ctl scripts, which 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.

Note:

Ignore any error messages that indicate tables or indexes could not be dropped from the database. These error messages are displayed when the specified objects do not exist in the database. This can occur because each source system container holds a subset of all data warehouse tables

9. If the data migration was successful, drop the tables that were created during the upgrade process, such as W_xxxx_x_79x, LKP_xxxx_x and 79x_xxxx_TMP.
This step frees the space occupied by these backup tables.

10. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep). For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Base Informatica Repository."

4.15 Upgrading the Data Warehouse Schema to Version 7.9.5.1 for Non-Teradata Databases

Follow this procedure to upgrade the data warehouse schema to version 7.9.5.1.

To upgrade the data warehouse schema:

- Use the DDLimp utility to run the ddl_7951.ctl script, which is located in the OracleBI\dwrep\Upgrade\CTLFiles folder. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

4.16 Upgrading the Data Warehouse Schema From Version 7.9.5.1 to 7.9.6.1 and Migrating Data for Non-Teradata Databases

This procedure adds new tables, columns, and indexes to the existing data warehouse schema. It also modifies the existing data warehouse schema objects.

Note: You can upgrade directly from version 7.9.5.1 to 7.9.6.1.

This section includes the following procedures:

- Section 4.16.1, "Upgrading the Data Warehouse Schema From Version 7.9.5.1 to 7.9.6.1"

- Section 4.16.2, "Migrating Data Into the Upgraded Data Warehouse"

- Section 4.16.3, "Verifying the Data Migrated Successfully"

4.16.1 Upgrading the Data Warehouse Schema From Version 7.9.5.1 to 7.9.6.1

Follow this procedure to upgrade the data warehouse schema to version 7.9.6.1.

Note: Upgrading to version 7.9.6.1 may involve running scripts that have a "796_" prefix.

To upgrade the data warehouse schema to version 7.9.6.1 and migrate data:

1. If you are using an Oracle database, run the 796_UPGRADE_DROP_INDEXES.sql script.

1. Open the SQL client for your database type.

2. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Oracle.

3. Open the 796_UPGRADE_DROP_INDEXES. sql file, and copy the contents into the SQL client.

4. Execute the script.

2. If you are using a SQL Server or DB2 database, run the 7961_UPGRADE_DROP_INDEXES.sql script.

1. Open the SQL client for your database type.

2. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\<database type>.

3. Open the 7961_UPGRADE_DROP_INDEXES. sql file, and copy the contents into the SQL client.

4. Execute the script.

3. If you are using a SQL Server database, run the 7961_UPGRADE_PRE_UPG_CTL_SCRIPT.sql file. This file is located in OracleBI\dwrep\Upgrade\DbScripts\SQLServer.

4. Run the UPGRADE_796.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

5. Run the 7961_UPGRADE_PRE_CTL_SCRIPT.sql:

1. Go to OracleBI\dwrep\Upgrade\DbScripts\<database type> folder, and open the 7961_UPGRADE_PRE_CTL_SCRIPT.sql file.

2. Search for the Datasource_Num_ID parameter, and make sure the value is correct for your existing implementation.

3. If you are using a DB2 database, search for the text "TBS_32K," and replace it with the appropriate 32K table space name that you have configured.

4. Execute the script.

6. Run the ddl_7961.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

7. Run the 796_UPGRADE_PRE_DIMENSION_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

8. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository. For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Upgrade Informatica Repository."

9. Copy all of the domain value files in the folder \OracleBI\dwrep\Informatica\LkpFiles into the folder <INFA_HOME>\server\infa_shared\LkpFiles.

4.16.2 Migrating Data Into the Upgraded Data Warehouse

Follow this procedure to migrate data into the upgraded data warehouse.

To migrate data into the upgraded data warehouse:

1. Copy the file Upgrade.rep from the folder OracleBI\dwrep\Upgrade\Informatica\Repository into the folder <INFA_HOME>\server\infa_shared\Backup.

2. Launch the Informatica Administrator, and restore Upgrade.rep (located in <INFA_HOME>\server\infa_shared\Backup).

3. Configure the Informatica parameter file 796_UPG_PARAMS.txt file. For instructions, see Appendix A, "Setting Parameters in 796_UPG_PARAMS.txt."

4. Configure parameters specific to Siebel source systems. For instructions, see Appendix A, "Setting Parameters in 796_UPG_PARAMS.txt for Siebel Source Systems."

5. In Informatica Workflow Manager, open the Relational Connection Browser (in the menu bar, select Connections, and then select Relational), and edit the connect string, user and password for the relational connections as follows:

1. Edit the connection PARAM_OLTP_SIEBEL to match your OLTP environment.

2. Edit the connection PARAM_OLAP to match your OLAP environment.

3. Edit the connection PARAM_DAC to match your DAC database.

Note:

If you are connected to an Oracle database, use the 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.

6. Back up and truncate the table W_POSITION_DH.

7. In Informatica Workflow Manager, navigate to the folder UPGRADE_7951_to_796_SBL and execute the following workflows in the order specified:

- UPGRADE_DIMENSIONS

- UPGRADE_FACTS

- RESET_DAC_REFRESH_DATES

8. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep). For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Base Informatica Repository."

9. Run the 7961_UPGRADE_PRE_DIMENSION_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

10. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository. For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Upgrade Informatica Repository."

11. Configure the Informatica parameter file 7961_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7961_UPG_PARAMS.txt."

12. In Informatica Workflow Manager, navigate to the folder UPGRADE_796_to_7961_SBL and execute the first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

13. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep). For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Base Informatica Repository."

14. Run the 7961_UPGRADE_POST_SCRIPT.sql. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

4.16.3 Verifying the Data Migrated Successfully

Follow this procedure to verify that the data was migrated successfully into the upgraded data warehouse.

To verify the data migrated successfully:

1. Validate the data in the upgraded data warehouse.

2. Check whether any of the Informatica mapping log files stored in the <INFA_HOME>\server\infa_shared\Sesslogs directory indicates errors or failures.

3. Check whether the following scripts that you ran in the SQL client of the database failed or errored out while executing:
7961_UPGRADE_DROP_INDEXES.sql

7961_UPGRADE_PRE_CTL_SCRIPT.sql

7961_UPGRADE_PRE_DIMENSION.sql

7961_UPGRADE_POST_SCRIPT.sql

4. Check the log files for the ddl_7961.ctl and Upgrade_7961.ctl scripts 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.

Note:

Ignore any error messages that indicate tables or indexes could not be dropped from the database. These error messages are displayed when the specified objects do not exist in the database. This can occur because each source system container holds a subset of all data warehouse tables

5. If the data migration was successful, drop the tables that were created during the upgrade process, such as W_xxxx_x_79x, LKP_xxxx_x, 79x_xxxx_TMP, and TMP_xxxx_79x.
This step frees the space occupied by these backup tables.

4.17 Upgrading the Data Warehouse Schema From Version 7.9.6 to 7.9.6.1 and Migrating Data for Non-Teradata Databases

Perform the procedures in this section to upgrade from Oracle BI Applications release 7.9.6 to release 7.9.6.1.

Note:

This procedure is applicable only if you are using an Oracle database for your data warehouse database.

This section includes the following procedures:

- Section 4.17.1, "Upgrading the Data Warehouse Schema to Version 7.9.6.1"

- Section 4.17.2, "Migrating Data into the Upgraded Data Warehouse"

- Section 4.17.3, "Verifying the Data Migrated Successfully"

4.17.1 Upgrading the Data Warehouse Schema to Version 7.9.6.1

Follow this procedure to upgrade the data warehouse schema to version 7.9.6.1.

To upgrade the data warehouse schema to version 7.9.6.1:

1. Run the UPGRADE_7961.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

2. Run the 796ORA_TO_7961ORA_UPGRADE_PRE_CTL_SCRIPT.sql. This file is located in the folder OracleBI\dwrep\Upgrade\DbScripts\Oracle.

3. Run the ddl_7961.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

4.17.2 Migrating Data into the Upgraded Data Warehouse

Follow this procedure to migrate data into the upgraded data warehouse.

To migrate data into the upgraded data warehouse:

1. Run the 7961_UPGRADE_PRE_DIMENSION_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Oracle.

2. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade repository. For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Upgrade Informatica Repository."

3. Configure the Informatica parameter file 7961_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7961_UPG_PARAMS.txt."

4. In Informatica Workflow Manager, navigate to the folder UPGRADE_796_to_7961_SBL and execute the first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

5. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep). For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Base Informatica Repository."

6. Run the 7961_UPGRADE_POST_SCRIPT.sql. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Oracle.

4.17.3 Verifying the Data Migrated Successfully

Follow this procedure to verify that the data was migrated successfully into the upgraded data warehouse.

To verify the data migrated successfully:

1. Validate the data in the upgraded data warehouse.

2. Check whether any of the Informatica mapping log files stored in the <INFA_HOME>\server\infa_shared\Sesslogs directory indicates errors or failures.

3. Check whether the following scripts that you ran in the SQL client of the database failed or errored out while executing:
7961_UPGRADE_DROP_INDEXES.sql

7961_UPGRADE_PRE_CTL_SCRIPT.sql

7961_UPGRADE_PRE_DIMENSION.sql

7961_UPGRADE_POST_SCRIPT.sql

4. Check the log files for the ddl_7961.ctl and Upgrade_7961.ctl scripts, which 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.

Note:

Ignore any error messages that indicate tables or indexes could not be dropped from the database. These error messages are displayed when the specified objects do not exist in the database. This can occur because each source system container holds a subset of all data warehouse tables

4.18 Upgrading the Data Warehouse Schema From Version 7.9.6.1 to 7.9.6.2 and Migrating Data for Non-Teradata Databases

This section contains the following procedures:

- Section 4.18.1, "Upgrading the Data Warehouse Schema to Version 7.9.6.2"

- Section 4.18.2, "Migrating Data into the Upgraded Data Warehouse"

- Section 4.18.3, "Verifying the Data Migrated Successfully"

4.18.1 Upgrading the Data Warehouse Schema to Version 7.9.6.2

Follow this procedure to upgrade the data warehouse schema to version 7.9.6.2.

To upgrade the data warehouse schema to version 7.9.6.2:

1. Generate the scripts to drop and create indexes. For instructions, see Section B.1, "Generating Scripts to Drop and Create Indexes for Upgrading to Release 7.9.6.2."

2. Run the script to drop all indexes. For instructions, see Section B.2, "Running the Script to Drop All Indexes for Upgrading to Release 7.9.6.2."

3. If you are using a SQL Server database, run the 7962_UPGRADE_PRE_UPG_CTL_SCRIPT.sql file. This file is located in OracleBI\dwrep\Upgrade\DbScripts\SQLServer.

4. Run the UPGRADE_7962.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

5. Run the 7962_UPGRADE_PRE_CTL_SCRIPT.sql. This file is located in the folder OracleBI\dwrep\Upgrade\DbScripts\<database type>.

6. Run the ddl_7962.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

4.18.2 Migrating Data into the Upgraded Data Warehouse

Follow this procedure to migrate data into the upgraded data warehouse.

To migrate data into the upgraded data warehouse:

1. Run the 7962_UPGRADE_PRE_DIMENSION_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

2. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade repository. For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Upgrade Informatica Repository."

3. Configure the Informatica parameter file 7962_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7962_UPG_PARAMS.txt."

4. Run the script to create ETL indexes. For instructions, see Section B.3, "Running the Scripts to Create ETL and Query Indexes for Upgrading to Release 7.9.6.2."

5. In Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_SBL and execute the UPGRADE_DIMENSIONS workflow.

6. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep). For instructions, see Section D.1, "Running reset_infa_seq_gen.bat on Base Informatica Repository."

7. Run the script to create Query indexes. For instructions, see Section B.3, "Running the Scripts to Create ETL and Query Indexes for Upgrading to Release 7.9.6.2."

4.18.3 Verifying the Data Migrated Successfully

Follow this procedure to verify that the data was migrated successfully into the upgraded data warehouse.

To verify the data migrated successfully:

1. Validate the data in the upgraded data warehouse.

2. Check whether any of the Informatica mapping log files stored in the <INFA_HOME>\server\infa_shared\Sesslogs directory indicates errors or failures.

3. Check whether the following scripts that you ran in the SQL client of the database failed or errored out while executing:
dropallindexes.sql

7962_UPGRADE_PRE_CTL_SCRIPT.sql

7962_UPGRADE_PRE_DIMENSION.sql

createETLIndexes.sql

createQueryIndexes.sql

4. Check the log files for the ddl_7962.ctl and Upgrade_7962.ctl scripts, which 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.

Note:

Ignore any error messages that indicate tables or indexes could not be dropped from the database. These error messages are displayed when the specified objects do not exist in the database. This can occur because each source system container holds a subset of all data warehouse tables.

5. If the data migration was successful, drop the tables that were created during the upgrade process, such as W_xxxx_x_79x, LKP_xxxx_x and 79x_xxxx_TMP.
This step frees the space occupied by these backup tables.

6. Once the data migration steps above are complete, you can delete the Upgrade repository to avoid any accidental use or confusion.

1. In the Informatica Administrator, select the Upgrade repository service.

2. In the General Properties area of the Properties tab, click Edit.

3. Make sure the operating mode of the repository service is set to Exclusive.

4. Click OK.

5. Choose Actions, and then click Delete Contents.

6. In the Delete contents for <repository name> dialog, enter the repository username and password, then click OK.

4.19 Upgrading the Data Warehouse Schema From Version 7.9.6.2 to 7.9.6.3 and Migrating Data for Non-Teradata Databases

Perform the procedures in this section to upgrade from Oracle BI Applications release 7.9.6.2 to 7.9.6.3.

This section contains the following procedures:

- Section 4.19.1, "Upgrading the Data Warehouse Schema to Version 7.9.6.3"

- Section 4.19.2, "Migrating Data Into the Upgraded Data Warehouse"

- Section 4.19.3, "Verifying the Data Migrated Successfully"

4.19.1 Upgrading the Data Warehouse Schema to Version 7.9.6.3

Follow this procedure to upgrade the data warehouse schema to version 7.9.6.3.

To upgrade the data warehouse schema to version 7.9.6.3:

1. Generate the scripts to drop and create query indexes. For instructions, see Section B.4, "Generating Scripts to Drop and Create Query Indexes for Upgrading to Release 7.9.6.3."

2. Run the script to drop query indexes. For instructions, see Section B.5, "Running the Scripts to Drop and Create Query Indexes for Upgrading to Release 7.9.6.3."
Note: You must drop the query indexes before running the scripts to upgrade the schema.

3. If you are using a SQL Server database, run the 7963_UPGRADE_PRE_UPG_CTL_SCRIPT.sql file. This file is located in OracleBI\dwrep\Upgrade\DbScripts\SQLServer.

4. Run the UPGRADE_7963.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

5. Run the 7963_UPGRADE_PRE_CTL_SCRIPT.sql. This file is located in the folder OracleBI\dwrep\Upgrade\DbScripts\<database type>.

6. Run the DDL_7963.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files.".

4.19.2 Migrating Data Into the Upgraded Data Warehouse

Follow this procedure to migrate data into the upgraded data warehouse.

To migrate data into the upgraded data warehouse:

1. Run the 7963_UPGRADE_PRE_DIMENSION_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

2. Run the 7963_UPGRADE_DROP_ETLINDICES.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

3. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade repository. For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Upgrade Informatica Repository."

4. Configure the Informatica parameter file 7963_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt."

5. If you are using Siebel Industry Applications, you need to set an additional parameter in 7963_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt for Siebel Industry Applications Source Systems."

6. In Informatica Workflow Manager, navigate to the folder UPGRADE_7962_to_7963_SBL and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

7. Upgrade geography-related attributes if necessary for your environment:

1. Determine whether a geography-related upgrade is necessary by executing the following query:

SELECT COUNT(1) as row_count,'0' as X_CUSTOM FROM W_GEO_D_7963 WHERE COUNTRY LIKE '% 'OR COUNTRY LIKE ' %'OR STATE_PROV LIKE '% 'OR STATE_PROV LIKE ' %'OR CITY LIKE '% 'OR CITY LIKE ' %'OR ZIPCODE LIKE '% 'OR ZIPCODE LIKE ' %'

2. If the query returns a count greater than zero, run the 7963_UPGRADE_POST_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.
If the query returns a count of zero, you do not need to run the 7963_UPGRADE_POST_SCRIPT.sql script.

8. Run the 7963_UPGRADE_CREATE_ETLINDICES.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

9. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep). For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Base Informatica Repository."

10. Run the createQueryIndices script. For instructions, see Section B.5, "Running the Scripts to Drop and Create Query Indexes for Upgrading to Release 7.9.6.3."

4.19.3 Verifying the Data Migrated Successfully

Follow this procedure to verify that the data was migrated successfully into the upgraded data warehouse.

To verify the data migrated successfully:

1. Validate the data in the upgraded data warehouse.

2. Check whether any of the Informatica mapping log files stored in the <INFA_HOME>\server\infa_shared\Sesslogs directory indicates errors or failures.

3. Check whether the following scripts that you ran in the SQL client of the database failed or errored out while executing:
7963_UPGRADE_PRE_CTL_SCRIPT.sql

7963_UPGRADE_PRE_DIMENSION.sql

7963_UPGRADE_DROP_ETLINDICES.sql

7963_UPGRADE CREATE_ETLINDICES.sql

dropQueryIndices.sql

createQueryIndices.sql

4. Check the log files for the ddl_7963.ctl and Upgrade_7963.ctl scripts, which 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.

Note:

Ignore any error messages that indicate tables or indexes could not be dropped from the database. These error messages are displayed when the specified objects do not exist in the database. This can occur because each source system container holds a subset of all data warehouse tables

5. If the data migration was successful, drop the tables that were created during the upgrade process, such as W_xxxx_x_79x, LKP_xxxx_x and 79x_xxxx_TMP.
This step frees the space occupied by these backup tables.

6. Once the data migration steps above are complete, you can delete the Upgrade repository to avoid any accidental use or confusion.

1. In the Informatica Administrator, select the Upgrade repository service.

2. In the General Properties area of the Properties tab, click Edit.

3. Make sure the operating mode of the repository service is set to Exclusive.

4. Click OK.

5. Choose Actions, and then click Delete Contents.

6. In the Delete contents for <repository name> dialog, enter the repository username and password, and then click OK.

4.20 Upgrading the Data Warehouse Schema From Version 7.9.6.3 to 7.9.6.4 and Migrating Data

Perform the procedures in this section to upgrade from Oracle BI Applications release 7.9.6.3 to 7.9.6.4.

This section contains the following procedures:

- Section 4.20.1, "Upgrading the Data Warehouse Schema to Version 7.9.6.4"

- Section 4.20.2, "Migrating Data into the Upgraded Data Warehouse"

- Section 4.20.3, "Verifying the Data Migrated Successfully"

4.20.1 Upgrading the Data Warehouse Schema to Version 7.9.6.4

Follow this procedure to upgrade the data warehouse schema to version 7.9.6.4.

To upgrade the data warehouse schema to version 7.9.6.4:

1. If you are using a DB2 database, run siebproc.sql. This file is located in OracleBI\dwrep\siebproc\db2udb.

2. Generate the scripts to drop and create query indexes. For instructions, see Section B.6, "Generating Scripts to Drop and Create Query and ETL Indexes for Upgrading to Release 7.9.6.4."

3. Run the script to drop query indexes. For instructions, see Section B.7, "Running the Scripts to Drop and Create Query Indexes for Upgrading to Release 7.9.6.4."
Note: You must drop the query indexes before running the scripts to upgrade the schema.

4. If you are using a SQL Server database, run the 7964_UPGRADE_PRE_UPG_CTL_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\SQLServer.

5. Run the UPGRADE_7964.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

6. Run the 7964_UPGRADE_PRE_CTL_SCRIPT.sql script. This file is located in the folder OracleBI\dwrep\Upgrade\DbScripts\<database type>.

7. Run the DDL_7964.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

4.20.2 Migrating Data into the Upgraded Data Warehouse

Follow this procedure to migrate data into the upgraded data warehouse.

To migrate data into the upgraded data warehouse:

1. Run the 7964_UPGRADE_PRE_DIMENSION_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

2. Run the script to drop ETL indexes. For instructions, see Section B.8, "Running the Scripts to Drop and Create ETL Indexes for Upgrading to Release 7.9.6.4."

3. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade repository. For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Upgrade Informatica Repository."

4. Configure the Informatica parameter file 7964_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7964_UPG_PARAMS.txt."

5. In Informatica Workflow Manager, navigate to the folder UPGRADE_7963_to_7964_SBL and execute the first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

6. Run the 7964_UPGRADE_POST_SCRIPT.sql. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

7. Run the script to create ETL indexes. For instructions, see Section B.8, "Running the Scripts to Drop and Create ETL Indexes for Upgrading to Release 7.9.6.4."

8. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep). For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Base Informatica Repository."

4.20.3 Verifying the Data Migrated Successfully

Follow this procedure to verify that the data was migrated successfully into the upgraded data warehouse.

To verify the data migrated successfully:

1. Validate the data in the upgraded data warehouse.

2. Check whether any of the Informatica mapping log files stored in the <INFA_HOME>\server\infa_shared\Sesslogs directory indicates errors or failures.

3. Check whether the following scripts that you ran in the SQL client of the database failed or errored out while executing:
7964_UPGRADE_PRE_CTL_SCRIPT.sql

7964_UPGRADE_PRE_DIMENSION.sql

dropEtlIndices.sql

createEtlIndices.sql

dropQueryIndices.sql

createQueryIndices.sql

4. Check the log files for the ddl_7964.ctl and Upgrade_7964.ctl scripts, which 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.

Note:

Ignore any error messages that indicate tables or indexes could not be dropped from the database. These error messages are displayed when the specified objects do not exist in the database. This can occur because each source system container holds a subset of all data warehouse tables

5. If the data migration was successful, drop the tables that were created during the upgrade process, such as W_xxxx_x_79x, LKP_xxxx_x and 79x_xxxx_TMP.
This step frees the space occupied by these backup tables.

6. Once the data migration steps above are complete, you can delete the Upgrade repository to avoid any accidental use or confusion.

1. In the Informatica Administrator, select the Upgrade repository service.

2. In the General Properties area of the Properties tab, click Edit.

3. Make sure the operating mode of the repository service is set to Exclusive.

4. Click OK.

5. Choose Actions, and then click Delete Contents.

6. In the Delete contents for <repository name> dialog, enter the repository username and password, and then click OK.

4.21 Upgrading the Data Warehouse Schema and Migrating Data for Teradata Databases

If your data warehouse database platform is Teradata, you can upgrade to Oracle BI Applications version 7.9.6.4 from Oracle BI Applications 7.9.x.

This section includes the following topics:

- Section 4.21.1, "Upgrading Oracle BI Applications From Version 7.9.0 to 7.9.6.4"

- Section 4.21.2, "Upgrading Oracle BI Applications From Version 7.9.4 to 7.9.6.4"

- Section 4.21.3, "Upgrading Oracle BI Applications From Version 7.9.5 to 7.9.6.4"

- Section 4.21.4, "Upgrading Oracle BI Applications From Version 7.9.5.1 to 7.9.6.4"

- Section 4.21.5, "Upgrading Oracle BI Applications From Version 7.9.6.1 to 7.9.6.4"

- Section 4.21.6, "Upgrading Oracle BI Applications From Version 7.9.6.2 to 7.9.6.4"

- Section 4.21.7, "Upgrading Oracle BI Applications From Version 7.9.6.3 to 7.9.6.4"

4.21.1 Upgrading Oracle BI Applications From Version 7.9.0 to 7.9.6.4

Follow this procedure to upgrade from Oracle Business Applications version 7.9.0 to version 7.9.6.4 if your data warehouse database platform is Teradata.

To upgrade the data warehouse schema and migrate data for a Teradata database:

1. Execute the following scripts:

- 795_UPGRADE_TMP_TABLES.sql

- 7951_UPGRADE_TMP_TABLES.sql

- 7961_UPGRADE_TMP_TABLES.sql

- 7962_UPGRADE_TMP_TABLES.sql

- 7963_UPGRADE_TMP_TABLES.sql

- 7964_UPGRADE_TMP_TABLES.sql

1. Open the SQL client for your database type.

2. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.

3. Open the <version>_UPGRADE_TMP_TABLES.sql file, and copy the contents into the SQL client.

4. Execute the script.

2. Edit and execute the 794_RENAME_AND_EXCEPTIONS.sql script.

1. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.

2. Open the 794_RENAME_AND_EXCEPTIONS.sql script.

3. Search for the following statements to locate columns with RENAME commands.
ALTER TABLE <Table_Name> RENAME <Column Name> TO <New Column Name>;

4. For all columns with RENAME commands, check to see whether any COLUMN STATISTICS are defined on them.

5. For all columns that have STATISTICS defined on them, back up the COLUMN STATISTICS definition and then drop them.

6. Execute the 794_RENAME_AND_EXCEPTIONS.sql script.

7. Recreate STATISTICS on any column on which they were dropped.

3. The teradata.missing.defaults.properties file contains global default column values for data warehouse tables with NOT NULL columns for which default values are not specified in DAC. You can change the default values specified in the teradata.missing.defaults.properties file to match your environment. The file is located in \bifoundation\dac\conf\sqlgen\sql\teradata.

4. Generate upgrade scripts from DAC.

1. Log into DAC.

2. From the menu bar, select Tools, then ETL Management, and then Configure.

3. In the Sources dialog box, select Teradata as the target data warehouse database platform, and select the appropriate source data warehouse database platform.
The Configuration tab of the Data Warehouse Configuration Wizard is active.

4. Select "Generate upgrade statements for Data Warehouse Tables," and click Next.
The Data Warehouse SQL tab is active.

5. Do the following:
- Select the appropriate physical data source name for the Teradata database.

- In the container field, enter a custom container name for which you want to generate upgrade scripts. Alternatively, leave the field blank to generate upgrade scripts for all containers.

The Data Warehouse Configuration Wizard generates the following files and stores them in \bifoundation\DAC\conf\sqlgen\sql\teradata:

upgrade-regular.sql. This file contains scripts that DAC has verified are necessary to upgrade the data warehouse schema. The scripts handle new or altered tables and columns. For example, they may increase the size of simple data types or change a column from null to not null.

upgrade-questionable.sql. This file contains scripts that DAC suggests may be required to upgrade the data warehouse schema. These scripts are intended to be an aid in determining upgrade requirements and must be reviewed by a Teradata DBA and corrected if necessary.

upgradedwtables_sql.log. This file is the log file that corresponds to the upgrade-regular.sql file. It is for information purposes only.

upgrade-issues.log. This file is the log file that corresponds to the file upgrade-questionable.sql. It is for information purposes only.

6. Open the upgrade-regular.sql and upgrade-questionable.sql files, and search for the following statement to locate columns that have been added or changed.
ALTER TABLE <Table Name> ADD <Column Name><attributes>;

7. For all columns with the ADD command, check to see whether any columns exist already, and if they do, check whether they have STATISTICS defined on them.

8. For all columns that have STATISTICS defined on them, back up the column definition and then drop the STATISTICS.

9. Execute the scripts in the upgrade-regular.sql file.

10. Review the scripts in the upgrade-questionable.sql file. Edit the scripts as needed, and execute them.

11. Recreate STATISTICS on any column on which they were dropped.

5. Execute the following scripts:

- 795_UPDATE_DEFAULTS.sql

- 7951_UPDATE_DEFAULTS.sql

- 7961_UPDATE_DEFAULTS.sql

- 7962_UPDATE_DEFAULTS.sql

- 7963_UPDATE_DEFAULTS.sql

- 7964_UPDATE_DEFAULTS.sql

6. Execute the 795_Backup Tables.sql script.

7. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

8. Configure the Informatica parameter file 795_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 795_UPG_PARAMS.txt."

9. If you upgraded your transactional database to Siebel Applications 8.x or 8.1.1, run the workflows to migrate your data into the upgraded data warehouse.

1. In Informatica Workflow Manager, navigate to the folder UPGRADE_790_TO_791_SBL80UPG.

2. Run the following workflows in the order specified:
UPGRADE_DIMENSIONS

UPGRADE_FACTS

10. In Informatica Workflow Manager, navigate to the folder UPGRADE_794_to_795_SBL and execute the UPGRADE_DIMENSIONS workflow.

11. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

12. Execute the 7951_Backup Tables.sql script.

13. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade repository. For instructions, see Section D.4, "Running reset_infa_seq_gen.bat on Upgrade Informatica Repository."

14. Configure the Informatica parameter file 7951_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7951_UPG_PARAMS.txt."

15. In Informatica Workflow Manager, navigate to the folder UPGRADE_795_to_7951_SBL and execute the UPGRADE_DIMENSIONS workflow.

16. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

17. Execute the 796_Backup Tables.sql script.

18. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

19. Configure the Informatica parameter file 796_UPG_PARAMS.txt file. For instructions, see Appendix A, "Setting Parameters in 796_UPG_PARAMS.txt."

20. Configure parameters specific to Siebel source systems. For instructions, see Appendix A, "Setting Parameters in 796_UPG_PARAMS.txt for Siebel Source Systems."

21. Back up and truncate the table W_POSITION_DH.

22. In Informatica Workflow Manager, navigate to the folder UPGRADE_7951_to_796_SBL and execute the following workflows in the order specified:

- UPGRADE_DIMENSIONS

- UPGRADE_FACTS

- RESET_DAC_REFRESH_DATES

23. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

24. Execute the 7961_Backup Tables.sql script.

25. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

26. Configure the Informatica parameter file 7961_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7961_UPG_PARAMS.txt."

27. In Informatica Workflow Manager, navigate to the folder UPGRADE_796_to_7961_SBL and execute the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

28. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

29. Execute the 7962_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

30. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

31. Configure the Informatica parameter file 7962_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7962_UPG_PARAMS.txt."

32. In Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_SBL and execute the UPGRADE_DIMENSIONS workflow.

33. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

34. Execute the 7963_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

35. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

36. Configure the Informatica parameter file 7963_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt."

37. If you are using Siebel Industry Applications, you need to set an additional parameter in 7963_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt for Siebel Industry Applications Source Systems."

38. In Informatica Workflow Manager, navigate to the folder UPGRADE_7962_to_7963_SBL and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

39. Upgrade geography-related attributes if necessary for your environment:

1. Determine whether a geography-related upgrade is necessary by executing the following query:

SELECT COUNT(1) as row_count,'0' as X_CUSTOM FROM W_GEO_D_7963 WHERE COUNTRY LIKE '% 'OR COUNTRY LIKE ' %'OR STATE_PROV LIKE '% 'OR STATE_PROV LIKE ' %'OR CITY LIKE '% 'OR CITY LIKE ' %'OR ZIPCODE LIKE '% 'OR ZIPCODE LIKE ' %'

2. If the query returns a count greater than zero, run the 7963_UPGRADE_POST_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.
If the query returns a count of zero, you do not need to run the 7963_UPGRADE_POST_SCRIPT.sql script.

40. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

41. Execute the 7964_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

42. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

43. Configure the Informatica parameter file 7964_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7964_UPG_PARAMS.txt."

44. In Informatica Workflow Manager, navigate to the folder UPGRADE_7963_to_7964_SBL and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.

45. Run the 7964_UPGRADE_POST_SCRIPT.sql. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

46. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

47. Once the data migration steps above are complete, you can delete the Upgrade repository to avoid any accidental use or confusion.

1. In the Informatica Administrator, select the Upgrade repository service.

2. In the General Properties area of the Properties tab, click Edit.

3. Make sure the operating mode of the repository service is set to Exclusive.

4. Click OK.

5. Choose Actions, and then click Delete Contents.

6. In the Delete contents for <repository name> dialog, enter the repository username and password, then click OK.

4.21.2 Upgrading Oracle BI Applications From Version 7.9.4 to 7.9.6.4

Follow this procedure to upgrade from Oracle Business Applications version 7.9.4 to version 7.9.6.4 if your data warehouse database platform is Teradata.

To upgrade the data warehouse schema and migrate data for a Teradata database:

1. Execute the following scripts:

- 795_UPGRADE_TMP_TABLES.sql

- 7951_UPGRADE_TMP_TABLES.sql

- 7961_UPGRADE_TMP_TABLES.sql

- 7962_UPGRADE_TMP_TABLES.sql

- 7963_UPGRADE_TMP_TABLESsql

- 7964_UPGRADE_TMP_TABLES.sql

1. Open the SQL client for your database type.

2. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.

3. Open the <version>_UPGRADE_TMP_TABLES.sql file, and copy the contents into the SQL client.

4. Execute the script.

2. Edit and execute the 795_RENAME_AND_EXCEPTIONS.sql script.

1. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.

2. Open the 795_RENAME_AND_EXCEPTIONS.sql script.

3. Search for the following statements to locate columns with RENAME commands.
ALTER TABLE <Table_Name> RENAME <Column Name> TO <New Column Name>;

4. For all columns with RENAME commands, check to see whether any COLUMN STATISTICS are defined on them.

5. For all columns that have STATISTICS defined on them, back up the COLUMN STATISTICS definition and then drop them.

6. Execute the 795_RENAME_AND_EXCEPTIONS.sql script.

7. Recreate STATISTICS on any column on which they were dropped.

3. The teradata.missing.defaults.properties file contains global default column values for data warehouse tables with NOT NULL columns for which default values are not specified in DAC. You can change the default values specified in the teradata.missing.defaults.properties file to match your environment. The file is located in \bifoundation\dac\conf\sqlgen\sql\teradata.

4. Generate upgrade scripts from DAC.

1. Log into DAC.

2. From the menu bar, select Tools, then ETL Management, and then Configure.

3. In the Sources dialog box, select Teradata as the target data warehouse database platform, and select the appropriate source data warehouse database platform.
The Configuration tab of the Data Warehouse Configuration Wizard is active.

4. Select "Generate upgrade statements for Data Warehouse Tables," and click Next.
The Data Warehouse SQL tab is active.

5. Do the following:
- Select the appropriate physical data source name for the Teradata database.

- In the container field, enter a custom container name for which you want to generate upgrade scripts. Alternatively, leave the field blank to generate upgrade scripts for all containers.

The Data Warehouse Configuration Wizard generates the following files and stores them in \bifoundation\DAC\conf\sqlgen\sql\teradata:

upgrade-regular.sql. This file contains scripts that DAC has verified are necessary to upgrade the data warehouse schema. The scripts handle new or altered tables and columns. For example, they may increase the size of simple data types or change a column from null to not null.

upgrade-questionable.sql. This file contains scripts that DAC suggests may be required to upgrade the data warehouse schema. These scripts are intended to be an aid in determining upgrade requirements and must be reviewed by a Teradata DBA and corrected if necessary.

upgradedwtables_sql.log. This file is the log file that corresponds to the upgrade-regular.sql file. It is for information purposes only.

upgrade-issues.log. This file is the log file that corresponds to the file upgrade-questionable.sql. It is for information purposes only.

6. Open the upgrade-regular.sql and upgrade-questionable.sql files, and search for the following statement to locate columns that have been added or changed.
ALTER TABLE <Table Name> ADD <Column Name><attributes>;

7. For all columns with the ADD command, check to see whether any columns exist already, and if they do, check whether they have STATISTICS defined on them.

8. For all columns that have STATISTICS defined on them, back up the column definition and then drop the STATISTICS.

9. Execute the scripts in the upgrade-regular.sql file.

10. Review the scripts in the upgrade-questionable.sql file. Edit the scripts as needed, and execute them.

11. Recreate STATISTICS on any column on which they were dropped.

5. Execute the following scripts:

- 795_UPDATE_DEFAULTS.sql

- 7951_UPDATE_DEFAULTS.sql

- 7961_UPDATE_DEFAULTS.sql

- 7962_UPDATE_DEFAULTS.sql

- 7963_UPDATE_DEFAULTS.sql

- 7964_UPDATE_DEFAULTS.sql

6. Execute the 795_Backup Tables.sql script.

7. Configure the Informatica parameter file 795_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 795_UPG_PARAMS.txt."

8. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

9. If you upgraded your transactional database to Siebel Applications 8.x or 8.1.1, run the workflows to migrate your data into the upgraded data warehouse.

1. In Informatica Workflow Manager, navigate to the folder UPGRADE_790_TO_791_SBL80UPG.

2. Run the following workflows in the order specified:
UPGRADE_DIMENSIONS

UPGRADE_FACTS

10. In Informatica Workflow Manager, navigate to the folder UPGRADE_794_to_795_SBL and execute the UPGRADE_DIMENSIONS workflow.

11. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

12. Execute the 7951_Backup Tables.sql script.

13. Configure the Informatica parameter file 7951_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7951_UPG_PARAMS.txt."

14. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

15. In Informatica Workflow Manager, navigate to the folder UPGRADE_795_to_7951_SBL and execute the UPGRADE_DIMENSIONS workflow.

16. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

17. Execute the 796_Backup Tables.sql script.

18. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

19. Configure the Informatica parameter file 796_UPG_PARAMS.txt file. For instructions, see Appendix A, "Setting Parameters in 796_UPG_PARAMS.txt."

20. Configure parameters specific to Siebel source systems. For instructions, see Appendix A, "Setting Parameters in 796_UPG_PARAMS.txt for Siebel Source Systems."

21. Back up and truncate the table W_POSITION_DH.

22. In Informatica Workflow Manager, navigate to the folder UPGRADE_7951_to_796_SBL and execute the following workflows in the order specified:

- UPGRADE_DIMENSIONS

- UPGRADE_FACTS

- RESET_DAC_REFRESH_DATES

23. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

24. Execute the 7961_Backup Tables.sql script.

25. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

26. Configure the Informatica parameter file 7961_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7961_UPG_PARAMS.txt."

27. In Informatica Workflow Manager, navigate to the folder UPGRADE_796_to_7961_SBL and execute the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

28. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

29. Execute the 7962_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

30. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

31. Configure the Informatica parameter file 7962_UPG_PARAMS.txt. For instructions, see Section A.1.7, "Setting Parameters in 7962_UPG_PARAMS.txt."

32. In Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_SBL and execute the UPGRADE_DIMENSIONS workflow.

33. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

34. Execute the 7963_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

35. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

36. Configure the Informatica parameter file 7963_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt."

37. If you are using Siebel Industry Applications, you need to set an additional parameter in 7963_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt for Siebel Industry Applications Source Systems."

38. In Informatica Workflow Manager, navigate to the folder UPGRADE_7962_to_7963_SBL and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

39. Upgrade geography-related attributes if necessary for your environment:

1. Determine whether a geography-related upgrade is necessary by executing the following query:

SELECT COUNT(1) as row_count,'0' as X_CUSTOM FROM W_GEO_D_7963 WHERE COUNTRY LIKE '% 'OR COUNTRY LIKE ' %'OR STATE_PROV LIKE '% 'OR STATE_PROV LIKE ' %'OR CITY LIKE '% 'OR CITY LIKE ' %'OR ZIPCODE LIKE '% 'OR ZIPCODE LIKE ' %'

2. If the query returns a count greater than zero, run the 7963_UPGRADE_POST_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.
If the query returns a count of zero, you do not need to run the 7963_UPGRADE_POST_SCRIPT.sql script.

40. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

41. Execute the 7964_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

42. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

43. Configure the Informatica parameter file 7964_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7964_UPG_PARAMS.txt."

44. In Informatica Workflow Manager, navigate to the folder UPGRADE_7963_to_7964_SBL and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.

45. Run the 7964_UPGRADE_POST_SCRIPT.sql. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

46. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

47. Once the data migration steps above are complete, you can delete the Upgrade repository to avoid any accidental use or confusion.

1. In the Informatica Administrator, select the Upgrade repository service.

2. In the General Properties area of the Properties tab, click Edit.

3. Make sure the operating mode of the repository service is set to Exclusive.

4. Click OK.

5. Choose Actions, and then click Delete Contents.

6. In the Delete contents for <repository name> dialog, enter the repository username and password, and then click OK.

4.21.3 Upgrading Oracle BI Applications From Version 7.9.5 to 7.9.6.4

Follow this procedure to upgrade from Oracle Business Applications version 7.9.5 to version 7.9.6.4 if your data warehouse database platform is Teradata.

To upgrade the data warehouse schema and migrate data for a Teradata database:

1. Execute the following scripts:

- 7951_UPGRADE_TMP_TABLES.sql

- 7961_UPGRADE_TMP_TABLES.sql

- 7962_UPGRADE_TMP_TABLES.sql

- 7963_UPGRADE_TMP_TABLES.sql

- 7964_UPGRADE_TMP_TABLES.sql

1. Open the SQL client for your database type.

2. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.

3. Open the <version>_UPGRADE_TMP_TABLES.sql file, and copy the contents into the SQL client.

4. Execute the script.

2. Edit and execute the 7951_RENAME_AND_EXCEPTIONS.sql script.

1. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.

2. Open the 7951_RENAME_AND_EXCEPTIONS.sql script.

3. Search for the following statements to locate columns with RENAME commands.
ALTER TABLE <Table_Name> RENAME <Column Name> TO <New Column Name>;

4. For all columns with RENAME commands, check to see whether any COLUMN STATISTICS are defined on them.

5. For all columns that have STATISTICS defined on them, back up the COLUMN STATISTICS definition and then drop them.

6. Execute the 7951_RENAME_AND_EXCEPTIONS.sql script.

7. Recreate STATISTICS on any column on which they were dropped.

3. The teradata.missing.defaults.properties file contains global default column values for data warehouse tables with NOT NULL columns for which default values are not specified in DAC. You can change the default values specified in the teradata.missing.defaults.properties file to match your environment. The file is located in \bifoundation\dac\conf\sqlgen\sql\teradata.

4. Generate upgrade scripts from DAC.

1. Log into DAC.

2. From the menu bar, select Tools, then ETL Management, and then Configure.

3. In the Sources dialog box, select Teradata as the target data warehouse database platform, and select the appropriate source data warehouse database platform.
The Configuration tab of the Data Warehouse Configuration Wizard is active.

4. Select "Generate upgrade statements for Data Warehouse Tables," and click Next.
The Data Warehouse SQL tab is active.

5. Do the following:
- Select the appropriate physical data source name for the Teradata database.

- In the container field, enter a custom container name for which you want to generate upgrade scripts. Alternatively, leave the field blank to generate upgrade scripts for all containers.

The Data Warehouse Configuration Wizard generates the following files and stores them in \bifoundation\DAC\conf\sqlgen\sql\teradata:

upgrade-regular.sql. This file contains scripts that DAC has verified are necessary to upgrade the data warehouse schema. The scripts handle new or altered tables and columns. For example, they may increase the size of simple data types or change a column from null to not null.

upgrade-questionable.sql. This file contains scripts that DAC suggests may be required to upgrade the data warehouse schema. These scripts are intended to be an aid in determining upgrade requirements and must be reviewed by a Teradata DBA and corrected if necessary.

upgradedwtables_sql.log. This file is the log file that corresponds to the upgrade-regular.sql file. It is for information purposes only.

upgrade-issues.log. This file is the log file that corresponds to the file upgrade-questionable.sql. It is for information purposes only.

6. Open the upgrade-regular.sql and upgrade-questionable.sql files, and search for the following statement to locate columns that have been added or changed.
ALTER TABLE <Table Name> ADD <Column Name><attributes>;

7. For all columns with the ADD command, check to see whether any columns exist already, and if they do, check whether they have STATISTICS defined on them.

8. For all columns that have STATISTICS defined on them, back up the column definition and then drop the STATISTICS.

9. Execute the scripts in the upgrade-regular.sql file.

10. Review the scripts in the upgrade-questionable.sql file. Edit the scripts as needed, and execute them.

11. Recreate STATISTICS on any column on which they were dropped.

5. Execute the following scripts:

- 7951_UPDATE_DEFAULTS.sql

- 7961_UPDATE_DEFAULTS.sql

- 7962_UPDATE_DEFAULTS.sql

- 7963_UPDATE_DEFAULTS.sql

- 7964_UPDATE_DEFAULTS.sql

6. Execute the 7951_Backup Tables.sql script.

7. Configure the Informatica parameter file 7951_UPG_PARAMStxt. For instructions, see Appendix A, "Setting Parameters in 7951_UPG_PARAMS.txt."

8. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

9. If you upgraded your transactional database to Siebel Applications 8.x or 8.1.1, run the workflows to migrate your data into the upgraded data warehouse.

1. In Informatica Workflow Manager, navigate to the folder UPGRADE_790_TO_791_SBL80UPG.

2. Run the following workflows in the order specified:
UPGRADE_DIMENSIONS

UPGRADE_FACTS

10. In Informatica Workflow Manager, navigate to the folder UPGRADE_795_to_7951_SBL and execute the UPGRADE_DIMENSIONS workflow.

11. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

12. Execute the 796_Backup Tables.sql script.

13. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

14. Configure the Informatica parameter file 796_UPG_PARAMS.txt file. For instructions, see Appendix A, "Setting Parameters in 796_UPG_PARAMS.txt."

15. Configure parameters specific to Siebel source systems. For instructions, see Appendix A, "Setting Parameters in 796_UPG_PARAMS.txt for Siebel Source Systems."

16. Back up and truncate the table W_POSITION_DH.

17. In Informatica Workflow Manager, navigate to the folder UPGRADE_7951_to_796_SBL and execute the following workflows in the order specified:

- UPGRADE_DIMENSIONS

- UPGRADE_FACTS

- RESET_DAC_REFRESH_DATES

18. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

19. Execute the 7961_Backup Tables.sql script.

20. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

21. Configure the Informatica parameter file 7961_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7961_UPG_PARAMS.txt."

22. In Informatica Workflow Manager, navigate to the folder UPGRADE_796_to_7961_SBL and execute the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

23. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

24. Execute the 7962_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

25. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

26. Configure the Informatica parameter file 7962_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7962_UPG_PARAMS.txt."

27. In Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_SBL and execute the UPGRADE_DIMENSIONS workflow.

28. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

29. Execute the 7963_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

30. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

31. Configure the Informatica parameter file 7963_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt."

32. If you are using Siebel Industry Applications, you need to set an additional parameter in 7963_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt for Siebel Industry Applications Source Systems."

33. In Informatica Workflow Manager, navigate to the folder UPGRADE_7962_to_7963_SBL and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

34. Upgrade geography-related attributes if necessary for your environment:

1. Determine whether a geography-related upgrade is necessary by executing the following query:

SELECT COUNT(1) as row_count,'0' as X_CUSTOM FROM W_GEO_D_7963 WHERE COUNTRY LIKE '% 'OR COUNTRY LIKE ' %'OR STATE_PROV LIKE '% 'OR STATE_PROV LIKE ' %'OR CITY LIKE '% 'OR CITY LIKE ' %'OR ZIPCODE LIKE '% 'OR ZIPCODE LIKE ' %'

2. If the query returns a count greater than zero, run the 7963_UPGRADE_POST_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.
If the query returns a count of zero, you do not need to run the 7963_UPGRADE_POST_SCRIPT.sql script.

35. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

36. Execute the 7964_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

37. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

38. Configure the Informatica parameter file 7964_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7964_UPG_PARAMS.txt."

39. In Informatica Workflow Manager, navigate to the folder UPGRADE_7963_to_7964_SBL and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.

40. Run the 7964_UPGRADE_POST_SCRIPT.sql. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

41. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

42. Once the data migration steps above are complete, you can delete the Upgrade repository to avoid any accidental use or confusion.

1. In the Informatica Administrator, select the Upgrade repository service.

2. In the General Properties area of the Properties tab, click Edit.

3. Make sure the operating mode of the repository service is set to Exclusive.

4. Click OK.

5. Choose Actions, and then click Delete Contents.

6. In the Delete contents for <repository name> dialog, enter the repository username and password, and then click OK.

4.21.4 Upgrading Oracle BI Applications From Version 7.9.5.1 to 7.9.6.4

Follow this procedure to upgrade from Oracle Business Applications version 7.9.5.1 to version 7.9.6.4 if your data warehouse database platform is Teradata.

To upgrade the data warehouse schema and migrate data for a Teradata database:

1. Execute the following scripts:

- 7961_UPGRADE_TMP_TABLES.sql

- 7962_UPGRADE_TMP_TABLES.sql

- 7963_UPGRADE_TMP_TABLES.sql

- 7964_UPGRADE_TMP_TABLES.sql

1. Open the SQL client for your database type.

2. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.

3. Open the <version>_UPGRADE_TMP_TABLES.sql file, and copy the contents into the SQL client.

4. Execute the script.

2. Edit and execute the 7961_RENAME_AND_EXCEPTIONS.sql script.

1. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.

2. Open the 7961_RENAME_AND_EXCEPTIONS.sql script.

3. Search for the following statements to locate columns with RENAME commands.
ALTER TABLE <Table_Name> RENAME <Column Name> TO <New Column Name>;

4. For all columns with RENAME commands, check to see whether any COLUMN STATISTICS are defined on them.

5. For all columns that have STATISTICS defined on them, back up the COLUMN STATISTICS definition and then drop them.

6. Execute the 7961_RENAME_AND_EXCEPTIONS.sql script.

7. Recreate STATISTICS on any column on which they were dropped.

3. The teradata.missing.defaults.properties file contains global default column values for data warehouse tables with NOT NULL columns for which default values are not specified in DAC. You can change the default values specified in the teradata.missing.defaults.properties file to match your environment. The file is located in \bifoundation\dac\conf\sqlgen\sql\teradata.

4. Generate upgrade scripts from DAC.

1. Log into DAC.

2. From the menu bar, select Tools, then ETL Management, and then Configure.

3. In the Sources dialog box, select Teradata as the target data warehouse database platform, and select the appropriate source data warehouse database platform.
The Configuration tab of the Data Warehouse Configuration Wizard is active.

4. Select "Generate upgrade statements for Data Warehouse Tables," and click Next.
The Data Warehouse SQL tab is active.

5. Do the following:
- Select the appropriate physical data source name for the Teradata database.

- In the container field, enter a custom container name for which you want to generate upgrade scripts. Alternatively, leave the field blank to generate upgrade scripts for all containers.

The Data Warehouse Configuration Wizard generates the following files and stores them in \bifoundation\DAC\conf\sqlgen\sql\teradata:

upgrade-regular.sql. This file contains scripts that DAC has verified are necessary to upgrade the data warehouse schema. The scripts handle new or altered tables and columns. For example, they may increase the size of simple data types or change a column from null to not null.

upgrade-questionable.sql. This file contains scripts that DAC suggests may be required to upgrade the data warehouse schema. These scripts are intended to be an aid in determining upgrade requirements and must be reviewed by a Teradata DBA and corrected if necessary.

upgradedwtables_sql.log. This file is the log file that corresponds to the upgrade-regular.sql file. It is for information purposes only.

upgrade-issues.log. This file is the log file that corresponds to the file upgrade-questionable.sql. It is for information purposes only.

6. Open the upgrade-regular.sql and upgrade-questionable.sql files, and search for the following statement to locate columns that have been added or changed.
ALTER TABLE <Table Name> ADD <Column Name><attributes>;

7. For all columns with the ADD command, check to see whether any columns exist already, and if they do, check whether they have STATISTICS defined on them.

8. For all columns that have STATISTICS defined on them, back up the column definition and then drop the STATISTICS.

9. Execute the scripts in the upgrade-regular.sql file.

10. Review the scripts in the upgrade-questionable.sql file. Edit the scripts as needed, and execute them.

11. Recreate STATISTICS on any column on which they were dropped.

5. Execute the following scripts:

- 7961_UPDATE_DEFAULTS.sql

- 7962_UPDATE_DEFAULTS.sql

- 7963_UPDATE_DEFAULTS.sql

- 7964_UPDATE_DEFAULTS.sql

6. Execute the 796_Backup Tables.sql script.

7. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

8. Configure the Informatica parameter file 796_UPG_PARAMS.txt file. For instructions, see Appendix A, "Setting Parameters in 796_UPG_PARAMS.txt."

9. Configure parameters specific to Siebel source systems. For instructions, see Appendix A, "Setting Parameters in 796_UPG_PARAMS.txt for Siebel Source Systems."

10. If you upgraded your transactional database to Siebel Applications 8.x or 8.1.1, run the workflows to migrate your data into the upgraded data warehouse.

1. In Informatica Workflow Manager, navigate to the folder UPGRADE_790_TO_791_SBL80UPG.

2. Run the following workflows in the order specified:
UPGRADE_DIMENSIONS

UPGRADE_FACTS

11. Back up and truncate the table W_POSITION_DH.

12. In Informatica Workflow Manager, navigate to the folder UPGRADE_7951_to_796_SBL and execute the following workflows in the order specified:

- UPGRADE_DIMENSIONS

- UPGRADE_FACTS

- RESET_DAC_REFRESH_DATES

13. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

14. Execute the 7961_Backup Tables.sql script.

15. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

16. Configure the Informatica parameter file 7961_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7961_UPG_PARAMS.txt."

17. In Informatica Workflow Manager, navigate to the folder UPGRADE_796_to_7961_SBL and execute the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

18. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

19. Execute the 7962_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

20. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

21. Configure the Informatica parameter file 7962_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7962_UPG_PARAMS.txt."

22. In Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_SBL and execute the UPGRADE_DIMENSIONS workflow.

23. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

24. Execute the 7963_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

25. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

26. Configure the Informatica parameter file 7963_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt."

27. If you are using Siebel Industry Applications, you need to set an additional parameter in 7963_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt for Siebel Industry Applications Source Systems."

28. In Informatica Workflow Manager, navigate to the folder UPGRADE_7962_to_7963_SBL and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

29. Upgrade geography-related attributes if necessary for your environment:

1. Determine whether a geography-related upgrade is necessary by executing the following query:

SELECT COUNT(1) as row_count,'0' as X_CUSTOM FROM W_GEO_D_7963 WHERE COUNTRY LIKE '% 'OR COUNTRY LIKE ' %'OR STATE_PROV LIKE '% 'OR STATE_PROV LIKE ' %'OR CITY LIKE '% 'OR CITY LIKE ' %'OR ZIPCODE LIKE '% 'OR ZIPCODE LIKE ' %'

2. If the query returns a count greater than zero, run the 7963_UPGRADE_POST_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.
If the query returns a count of zero, you do not need to run the 7963_UPGRADE_POST_SCRIPT.sql script.

30. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

31. Execute the 7964_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

32. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

33. Configure the Informatica parameter file 7964_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7964_UPG_PARAMS.txt."

34. In Informatica Workflow Manager, navigate to the folder UPGRADE_7963_to_7964_SBL and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.

35. Run the 7964_UPGRADE_POST_SCRIPT.sql. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

36. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

37. Once the data migration steps above are complete, you can delete the Upgrade repository to avoid any accidental use or confusion.

1. In the Informatica Administrator, select the Upgrade repository service.

2. In the General Properties area of the Properties tab, click Edit.

3. Make sure the operating mode of the repository service is set to Exclusive.

4. Click OK.

5. Choose Actions, and then click Delete Contents.

6. In the Delete contents for <repository name> dialog, enter the repository username and password, and then click OK.

4.21.5 Upgrading Oracle BI Applications From Version 7.9.6.1 to 7.9.6.4

Follow this procedure to upgrade from Oracle Business Applications version 7.9.6.1 to version 7.9.6.4 if your data warehouse database platform is Teradata.

To upgrade the data warehouse schema and migrate data for a Teradata database:

1. Execute the following scripts:

- 7962_UPGRDE_TMP_TABLES.sql

- 7963_UPGRADE_TMP_TABLES.sql

- 7964_UPGRADE_TMP_TABLES.sql

1. Open the SQL client for your database type.

2. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.

3. Open the <version>_UPGRADE_TMP_TABLES.sql file, and copy the contents into the SQL client.

4. Execute the script.

2. Edit and execute the 7961_RENAME_AND_EXCEPTIONS.sql script.

1. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.

2. Open the 7961_RENAME_AND_EXCEPTIONS.sql script.

3. Search for the following statements to locate columns with RENAME commands.
ALTER TABLE <Table_Name> RENAME <Column Name> TO <New Column Name>;

4. For all columns with RENAME commands, check to see whether any COLUMN STATISTICS are defined on them.

5. For all columns that have STATISTICS defined on them, back up the COLUMN STATISTICS definition and then drop them.

6. Execute the 7961_RENAME_AND_EXCEPTIONS.sql script.

7. Recreate STATISTICS on any column on which they were dropped.

3. The teradata.missing.defaults.properties file contains global default column values for data warehouse tables with NOT NULL columns for which default values are not specified in DAC. You can change the default values specified in the teradata.missing.defaults.properties file to match your environment. The file is located in \bifoundation\dac\conf\sqlgen\sql\teradata.

4. Generate upgrade scripts from DAC.

1. Log into DAC.

2. From the menu bar, select Tools, then ETL Management, and then Configure.

3. In the Sources dialog box, select Teradata as the target data warehouse database platform, and select the appropriate source data warehouse database platform.
The Configuration tab of the Data Warehouse Configuration Wizard is active.

4. Select "Generate upgrade statements for Data Warehouse Tables," and click Next.
The Data Warehouse SQL tab is active.

5. Do the following:
- Select the appropriate physical data source name for the Teradata database.

- In the container field, enter a custom container name for which you want to generate upgrade scripts. Alternatively, leave the field blank to generate upgrade scripts for all containers.

The Data Warehouse Configuration Wizard generates the following files and stores them in \bifoundation\DAC\conf\sqlgen\sql\teradata:

upgrade-regular.sql. This file contains scripts that DAC has verified are necessary to upgrade the data warehouse schema. The scripts handle new or altered tables and columns. For example, they may increase the size of simple data types or change a column from null to not null.

upgrade-questionable.sql. This file contains scripts that DAC suggests may be required to upgrade the data warehouse schema. These scripts are intended to be an aid in determining upgrade requirements and must be reviewed by a Teradata DBA and corrected if necessary.

upgradedwtables_sql.log. This file is the log file that corresponds to the upgrade-regular.sql file. It is for information purposes only.

upgrade-issues.log. This file is the log file that corresponds to the file upgrade-questionable.sql. It is for information purposes only.

6. Open the upgrade-regular.sql and upgrade-questionable.sql files, and search for the following statement to locate columns that have been added or changed.
ALTER TABLE <Table Name> ADD <Column Name><attributes>;

7. For all columns with the ADD command, check to see whether any columns exist already, and if they do, check whether they have STATISTICS defined on them.

8. For all columns that have STATISTICS defined on them, back up the column definition and then drop the STATISTICS.

9. Execute the scripts in the upgrade-regular.sql file.

10. Review the scripts in the upgrade-questionable.sql file. Edit the scripts as needed, and execute them.

11. Recreate STATISTICS on any column on which they were dropped.

5. Execute the following scripts:

- 7962_UPDATE_DEFAULTS.sql

- 7963_UPDATE_DEFAULTS.sql

- 7964_UPDATE_DEFAULTS.sql

6. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

7. Execute the 7962_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

8. Configure the Informatica parameter file 7962_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7962_UPG_PARAMS.txt."

9. In Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_SBL and execute the UPGRADE_DIMENSIONS workflow.

10. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

11. Execute the 7963_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

12. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

13. Configure the Informatica parameter file 7963_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt."

14. If you are using Siebel Industry Applications, you need to set an additional parameter in 7963_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt for Siebel Industry Applications Source Systems."

15. In Informatica Workflow Manager, navigate to the folder UPGRADE_7962_to_7963_SBL and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

16. Upgrade geography-related attributes if necessary for your environment:

1. Determine whether a geography-related upgrade is necessary by executing the following query:

SELECT COUNT(1) as row_count,'0' as X_CUSTOM FROM W_GEO_D_7963 WHERE COUNTRY LIKE '% 'OR COUNTRY LIKE ' %'OR STATE_PROV LIKE '% 'OR STATE_PROV LIKE ' %'OR CITY LIKE '% 'OR CITY LIKE ' %'OR ZIPCODE LIKE '% 'OR ZIPCODE LIKE ' %'

2. If the query returns a count greater than zero, run the 7963_UPGRADE_POST_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.
If the query returns a count of zero, you do not need to run the 7963_UPGRADE_POST_SCRIPT.sql script.

17. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

18. Execute the 7964_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

19. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

20. Configure the Informatica parameter file 7964_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7964_UPG_PARAMS.txt."

21. In Informatica Workflow Manager, navigate to the folder UPGRADE_7963_to_7964_SBL and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.

22. Run the 7964_UPGRADE_POST_SCRIPT.sql. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

23. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

24. Once the data migration steps above are complete, you can delete the Upgrade repository to avoid any accidental use or confusion.

1. In the Informatica Administrator, select the Upgrade repository service.

2. In the General Properties area of the Properties tab, click Edit.

3. Make sure the operating mode of the repository service is set to Exclusive.

4. Click OK.

5. Choose Actions, and then click Delete Contents.

6. In the Delete contents for <repository name> dialog, enter the repository username and password, and then click OK.

4.21.6 Upgrading Oracle BI Applications From Version 7.9.6.2 to 7.9.6.4

Follow this procedure to upgrade from Oracle Business Applications version 7.9.6.2 to version 7.9.6.4 if your data warehouse database platform is Teradata.

To upgrade the data warehouse schema and migrate data for a Teradata database:

1. Execute the following scripts:

- 7963_UPGRADE_TMP_TABLES.sql

- 7964_UPGRADE_TMP_TABLES.sql

1. Open the SQL client for your database type.

2. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.

3. Open the <version>_UPGRADE_TMP_TABLES.sql file, and copy the contents into the SQL client.

4. Execute the script.

2. The teradata.missing.defaults.properties file contains global default column values for data warehouse tables with NOT NULL columns for which default values are not specified in DAC. You can change the default values specified in the teradata.missing.defaults.properties file to match your environment. The file is located in \bifoundation\dac\conf\sqlgen\sql\teradata.

3. Generate upgrade scripts from DAC.

1. Log into DAC.

2. From the menu bar, select Tools, then ETL Management, and then Configure.

3. In the Sources dialog box, select Teradata as the target data warehouse database platform, and select the appropriate source data warehouse database platform.
The Configuration tab of the Data Warehouse Configuration Wizard is active.

4. Select "Generate upgrade statements for Data Warehouse Tables," and click Next.
The Data Warehouse SQL tab is active.

5. Do the following:
- Select the appropriate physical data source name for the Teradata database.

- In the container field, enter a custom container name for which you want to generate upgrade scripts. Alternatively, leave the field blank to generate upgrade scripts for all containers.

The Data Warehouse Configuration Wizard generates the following files and stores them in \bifoundation\DAC\conf\sqlgen\sql\teradata:

upgrade-regular.sql. This file contains scripts that DAC has verified are necessary to upgrade the data warehouse schema. The scripts handle new or altered tables and columns. For example, they may increase the size of simple data types or change a column from null to not null.

upgrade-questionable.sql. This file contains scripts that DAC suggests may be required to upgrade the data warehouse schema. These scripts are intended to be an aid in determining upgrade requirements and must be reviewed by a Teradata DBA and corrected if necessary.

upgradedwtables_sql.log. This file is the log file that corresponds to the upgrade-regular.sql file. It is for information purposes only.

upgrade-issues.log. This file is the log file that corresponds to the file upgrade-questionable.sql. It is for information purposes only.

6. Open the upgrade-regular.sql and upgrade-questionable.sql files, and search for the following statement to locate columns that have been added or changed.
ALTER TABLE <Table Name> ADD <Column Name><attributes>;

7. For all columns with the ADD command, check to see whether any columns exist already, and if they do, check whether they have STATISTICS defined on them.

8. For all columns that have STATISTICS defined on them, back up the column definition and then drop the STATISTICS.

9. Execute the scripts in the upgrade-regular.sql file.

10. Review the scripts in the upgrade-questionable.sql file. Edit the scripts as needed, and execute them.

11. Recreate STATISTICS on any column on which they were dropped.

4. Execute the 7963_UPDATE_DEFAULTS.sql script.

5. Execute the 7964_UPDATE_DEFAULTS.sql script.

6. Execute the 7963_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

7. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

8. Configure the Informatica parameter file 7963_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt."

9. If you are using Siebel Industry Applications, you need to set an additional parameter in 7963_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt for Siebel Industry Applications Source Systems."

10. In Informatica Workflow Manager, navigate to the folder UPGRADE_7962_to_7963_SBL and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

11. Upgrade geography-related attributes if necessary for your environment:

1. Determine whether a geography-related upgrade is necessary by executing the following query:

SELECT COUNT(1) as row_count,'0' as X_CUSTOM FROM W_GEO_D_7963 WHERE COUNTRY LIKE '% 'OR COUNTRY LIKE ' %'OR STATE_PROV LIKE '% 'OR STATE_PROV LIKE ' %'OR CITY LIKE '% 'OR CITY LIKE ' %'OR ZIPCODE LIKE '% 'OR ZIPCODE LIKE ' %'

2. If the query returns a count greater than zero, run the 7963_UPGRADE_POST_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.
If the query returns a count of zero, you do not need to run the 7963_UPGRADE_POST_SCRIPT.sql script.

12. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

13. Execute the 7964_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

14. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

15. Configure the Informatica parameter file 7964_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7964_UPG_PARAMS.txt."

16. In Informatica Workflow Manager, navigate to the folder UPGRADE_7963_to_7964_SBL and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.

17. Run the 7964_UPGRADE_POST_SCRIPT.sql. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

18. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

19. Once the data migration steps above are complete, you can delete the Upgrade repository to avoid any accidental use or confusion.

1. In the Informatica Administrator, select the Upgrade repository service.

2. In the General Properties area of the Properties tab, click Edit.

3. Make sure the operating mode of the repository service is set to Exclusive.

4. Click OK.

5. Choose Actions, and then click Delete Contents.

6. In the Delete contents for <repository name> dialog, enter the repository username and password, and then click OK.

4.21.7 Upgrading Oracle BI Applications From Version 7.9.6.3 to 7.9.6.4

Follow this procedure to upgrade from Oracle Business Applications version 7.9.6.3 to version 7.9.6.4 if your data warehouse database platform is Teradata.

To upgrade the data warehouse schema and migrate data for a Teradata database:

1. Execute the 7964_UPGRADE_TMP_TABLES.sql script.

1. Open the SQL client for your database type.

2. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.

3. Open the 7964_UPGRADE_TMP_TABLES.sql file, and copy the contents into the SQL client.

4. Execute the script.

2. The teradata.missing.defaults.properties file contains global default column values for data warehouse tables with NOT NULL columns for which default values are not specified in DAC. You can change the default values specified in the teradata.missing.defaults.properties file to match your environment. The file is located in \bifoundation\dac\conf\sqlgen\sql\teradata.

3. Generate upgrade scripts from DAC.

1. Log into DAC.

2. From the menu bar, select Tools, then ETL Management, and then Configure.

3. In the Sources dialog box, select Teradata as the target data warehouse database platform, and select the appropriate source data warehouse database platform.
The Configuration tab of the Data Warehouse Configuration Wizard is active.

4. Select "Generate upgrade statements for Data Warehouse Tables," and click Next.
The Data Warehouse SQL tab is active.

5. Do the following:
- Select the appropriate physical data source name for the Teradata database.

- In the container field, enter a custom container name for which you want to generate upgrade scripts. Alternatively, leave the field blank to generate upgrade scripts for all containers.

The Data Warehouse Configuration Wizard generates the following files and stores them in \bifoundation\DAC\conf\sqlgen\sql\teradata:

upgrade-regular.sql. This file contains scripts that DAC has verified are necessary to upgrade the data warehouse schema. The scripts handle new or altered tables and columns. For example, they may increase the size of simple data types or change a column from null to not null.

upgrade-questionable.sql. This file contains scripts that DAC suggests may be required to upgrade the data warehouse schema. These scripts are intended to be an aid in determining upgrade requirements and must be reviewed by a Teradata DBA and corrected if necessary.

upgradedwtables_sql.log. This file is the log file that corresponds to the upgrade-regular.sql file. It is for information purposes only.

upgrade-issues.log. This file is the log file that corresponds to the file upgrade-questionable.sql. It is for information purposes only.

6. Open the upgrade-regular.sql and upgrade-questionable.sql files, and search for the following statement to locate columns that have been added or changed.
ALTER TABLE <Table Name> ADD <Column Name><attributes>;

7. For all columns with the ADD command, check to see whether any columns exist already, and if they do, check whether they have STATISTICS defined on them.

8. For all columns that have STATISTICS defined on them, back up the column definition and then drop the STATISTICS.

9. Execute the scripts in the upgrade-regular.sql file.

10. Review the scripts in the upgrade-questionable.sql file. Edit the scripts as needed, and execute them.

11. Recreate STATISTICS on any column on which they were dropped.

4. Execute the 7964_UPDATE_DEFAULTS.sql scripts.

5. Execute the 7964_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

6. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

7. Configure the Informatica parameter file 7964_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7964_UPG_PARAMS.txt."

8. In Informatica Workflow Manager, navigate to the folder UPGRADE_7963_to_7964_SBL and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.

9. Run the 7964_UPGRADE_POST_SCRIPT.sql. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

10. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

11. Once the data migration steps above are complete, you can delete the Upgrade repository to avoid any accidental use or confusion.

1. In the Informatica Administrator, select the Upgrade repository service.

2. In the General Properties area of the Properties tab, click Edit.

3. Make sure the operating mode of the repository service is set to Exclusive.

4. Click OK.

5. Choose Actions, and then click Delete Contents.

6. In the Delete contents for <repository name> dialog, enter the repository username and password, and then click OK.

4.22 Localizing the Policy Store

The Oracle BI Applications 7.9.6.4 installer contains different policy stores for different languages. The default policy store that is deployed during the installation is in English. If you want to configure the policy store for any of the other available languages, perform the procedure below.

To configure the policy store for languages other than English:

1. Stop the Oracle BI Services.

2. Copy the system-jazn-data_<LN>.xml file from $ORACLE_BI_HOME\biapps\admin\provisioning\localization\ to $DOMAIN_HOME\config\fmwconfig\.
For example, to implement the policy store for French, you would copy the file system-jazn-data_fr.xml into the \fmwconfig directory.

3. Back up the existing system-jazn-data.xml file in $DOMAIN_HOME\config\fmwconfig\.

4. Rename $DOMAIN_HOME\config\fmwconfig\system-jazn-data_<LN>.xml to system-jazn-data.xml.

5. Start Oracle BI Services.

4.23 Importing the Oracle BI Applications Version 7.9.6.4 LDIF File Into the Embedded LDAP Server

In this procedure, you will import the standard (out-of-the-box) Oracle BI Applications version 7.9.6.4 LDIF file into the WebLogic Server embedded LDAP server.

To import the Oracle BI Applications version 7.9.6.4 LDIF file:

1. Log in to the WebLogic Server Administration Console using the URL http://<host name>:7001/console.

2. Select the name of the security realm into which the LDIF file is to be imported (for example, myrealm).

3. Select Providers and then the type of provider into which the LDIF file is to be imported (for example, Providers, and then Authentication).

4. Select the security provider in which the LDIF file is to be imported and select Migration, and then select Import.

5. Click Save.

4.24 Upgrading the Siebel Analytics Repository and the Web Catalog to the Oracle BI Enterprise Edition 11g Version

Use the Oracle BI Enterprise Edition Upgrade Assistant to upgrade the following repositories and web catalog from the Oracle BI Enterprise Edition 10g format to the 11g format:

- The standard (out-of-the-box) Siebel Analytics Repository version 7.7, 7.7.x, or 7.8.x. This repository is the one that you originally received from Oracle as part of your current Siebel Analytics 7.7, 7.7.x, or 7.8.x installation. Standard repositories from previous releases are available in the installation folder $ORACLE_BI_HOME\biapps\upgrade.

- The Siebel Analytics Repository you are currently using (the repository deployed in production).

- The Web Catalog you are currently using (the Web Catalog deployed in production).

For instructions on using the Upgrade Assistant, see Oracle Fusion Middleware Upgrade Guide for Oracle Business Intelligence.

Note:

If your Siebel Analytics Repository and Web Catalog are in a Siebel Analytics format, you must first upgrade them to the Oracle BI Enterprise Edition 10g format before you can upgrade them to the 11g format. For more information, see the Oracle Business Intelligence Infrastructure Upgrade Guide Version 10.1.3.2, which is located on the Oracle Technology Network in the Oracle Business Intelligence Suite Enterprise Edition Documentation Library Version 10.1.3.4.1.

Note:

Your current policy store will be merged with the Oracle BI Applications release 7.9.6.4 policy store while upgrading the Oracle BI repository from the 10g format to the 11g format. The final policy store will be the super set of Oracle BI Applications release 7.9.6.4 policy store and the custom and current policy information from the 10g repository.

Also, your current users and groups from the repository will be merged with the Oracle BI Applications release 7.9.6.4 identity store while upgrading the Oracle BI repository from the 10g format to the 11g format. The final identity store will be the super set of the Oracle BI Applications release 7.9.6.4 identity store and the identity store information (users and groups) from the 10g repository.

If you require the policy store to be in a language other than English, perform the steps in Section 4.22, "Localizing the Policy Store."

4.25 Merging Oracle BI Applications Version 7.9.6.4 Repository With Customer Repository

Note:

Before you begin this procedure, you must have already upgraded your Siebel Analytics repository to the Oracle BI Enterprise Edition 11g format. For more information, see Section 4.24, "Upgrading the Siebel Analytics Repository and the Web Catalog to the Oracle BI Enterprise Edition 11g Version."

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 4.25.1, "Preparing for the Oracle BI Repository Upgrade"

- Section 4.25.2, "Equalizing the Oracle BI Repositories"

- Section 4.25.3, "Comparing the Oracle BI Repositories"

- Section 4.25.4, "Merging the Oracle BI Repositories"

The tasks in this section refer to multiple releases of the Oracle BI repository. Table 4-1 provides the names and descriptions of the repositories used in the examples in this section.

Table 4-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.

Note: Standard repositories from previous releases are available in the folder $ORACLE_BI_HOME\biapps\upgrade.

OracleBIAnalyticsApps.rpd

The standard Oracle BI repository for the version you are upgrading to.

Customer_SiebelAnalyticsApps.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.

4.25.1 Preparing for the Oracle BI Repository Upgrade

Follow this procedure to prepare for the repository upgrade.

To prepare for the Analytics repository upgrade:

1. Set up a directory for the merge process, such as \OracleBIUpgrade, and create the following subfolders:

- Original

- AfterEqualize

- AfterMerge

- AfterManualWork

- AfterRegressions

2. Copy the following repositories to the folder \OracleBIUpgrade\Original:

- The standard (original) repository that you upgraded to the 11g format in Section 4.24, "Upgrading the Siebel Analytics Repository and the Web Catalog to the Oracle BI Enterprise Edition 11g Version" (for example, SiebelAnalytics.rpd).

- The production repository that you also upgraded to the 11g format in Section 4.24 (for example, Customer_SiebelAnalyticsApps.rpd.

- The Oracle BI repository from the latest installation (for example, OracleBIAnalyticsApps.rpd)

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 original 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.

4.25.2 Equalizing the Oracle BI Repositories

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, siebelAnalyticsApps_79x.rpd, OracleBIAnalyticsApps.rpd, and Customer_SiebelAnalyticsApps.rpd) are equivalent.

The point of this step is to determine for every object in the OracleBIAnalyticsApps.rpd and the Customer_SiebelAnalyticsApps.rpd whether it is coming from the SiebelAnalyticsApps_79x.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 $ORACLE_BI_HOME\biapps\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.
Table 4-2 provides a list of the available MAP files and the Siebel Analytics or Oracle BI Applications release version associated with the file.

Table 4-2 Rename MAP Files to Be Used for Various Releases

Siebel Analytics / Oracle Business Intelligence Applications Release Version (Upgrading from DW Version)

Rename MAP File to Be Used

Siebel Business Analytics Applications 7.0.x

Not available

Siebel Business Analytics Applications 7.5.x

Not available

Siebel Business Analytics Applications 7.7.x (with Siebel CRM OLTP Pre-7.7.0)

Rename77-7963.map

Siebel Business Analytics Applications 7.7.x (with Siebel CRM OLTP 7.7.0)

Rename771-7963.map

Siebel Business Analytics Applications 7.8.2 and all 7.8.x versions before this release

Rename782-7963.map

Siebel Business Analytics Applications 7.8.3 and all 7.8.x versions after this release

Rename783-7963.map

Oracle BI Applications 7.9.0

Rename79x-7963.map

Oracle BI Applications 7.9.1

Rename79x-7963.map

Oracle BI Applications 7.9.2

Rename79x-7963.map

Oracle BI Applications 7.9.3

Rename793to7963.map

Oracle BI Applications 7.9.4

Rename794to7963.map

Oracle BI Applications 7.9.5

Rename79x-7963.map

Oracle BI Applications 7.9.5.1

Rename7951to7963.map

Oracle BI Applications 7.9.5.2

Rename7951to7963.map

Oracle BI Applications 7.9.6

Rename79x-7963.map

Oracle BI Applications 7.9.6.2

rename7963to7964.map

Not required for upgrades from 7.9.6.2 to 7.9.6.3.

Oracle BI Applications 7.9.6.3

rename7963to7964.map

The syntax of the equalizerpds command is as follows:

equalizerpds.exe  [-B [password1]] -C base_repository_name [-E [password2]] -F repository2_name [-J udml_utf8_file_name_equalization] [-O ouput_repository_name] [-Y equalStringSet]
-Y          Treat the characters as equals.
/?          Display this usage information and exit.

To equalize a repository:

1. Copy the appropriate MAP file from the $ORACLE_BI_HOME\biapps\upgrade folder into the folder where you will execute equalizerpds.exe, for example, \OracleBIUpgrade\Original.

2. Run equalizerpds.exe to equalize the repository from the latest installation (for example, OracleBIAnalyticsApps.rpd) with the original repository (for example, SiebelAnalyticsAppss_7x.rpd). An example of the equalizerpds command is as follows:

equalizerpds -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 $ORACLE_BI_HOME\biapps\upgrade folder.

If the equalizerpds.exe executable file runs correctly, no errors are returned.

3. Run equalizerpds.exe to equalize your customized repository (for example, Customer_SiebelAnalytics.rpd) with the original repository (for example, SiebelAnalytics_79x.rpd). An example of the equalizerpds command is as follows:

equalizerpds -B SADMIN
-C \\OracleBIUpgrade\Original\SiebelAnalytics_7x.rpd
-E SADMIN
-F \\OracleBIUpgrade\Original\Customer_SiebelAnalytics.rpd
-O \\OracleBIUpgrade\AfterEqualize\Customer_SiebelAnalytics.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.

4. 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).

4.25.3 Comparing the Oracle BI Repositories

Follow this procedure to compare your existing repository with the new version to which you are upgrading.

To compare the Oracle BI 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 Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition.

4.25.4 Merging the Oracle BI Repositories

In this procedure, you execute the main algorithm to upgrade the repository. For more information on merging the repositories, see Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition.

To merge versions of the Oracle BI repositories:

1. Copy the three repositories (for example, SiebelAnalytics_7x.rpd, OracleBIAnalyticsApps.rpd, and Customer_SiebelAnalytics.rpd) to the AfterMerge folder.

2. Open the repository from the latest installation (for example, OracleBIAnalyticsApps.rpd) in the \OracleBIUpgrade\AfterMerge folder.

3. From the Administration Tool menu bar, select File, then select Merge.

4. Select the Merge Type option Full Repository Merge.

5. In the Select Original Repository dialog box, select the original repository (for example, SiebelAnalytics_7x.rpd).

6. Enter the password for the original repository.

7. In the Select Modified Repository dialog box, select the repository that contains the customizations you made to the previous version of the Analytics repository.

8. Enter the password for the modified repository.

9. In the Saved Merged Repository as dialog box, enter the name for the merged repository, for example, Merged_Repository_OracleBIAnalyticsApps.rpd.
The new repository will contain the final results of the merge.

10. Select the Equalize during merge check box.

11. Click Next.

12. In the Decision drop-down list, select the action you want to take regarding the repository change, or accept the default action.

13. To locate subsequent rows with empty Decision fields, click the Decision header cell.
When all rows have a value in the Decision field, the Finish button is enabled.

14. Select the Check consistency of the merged RPD check box.

15. Click Finish.
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.

16. 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'

17. Copy the repository to the folder \OracleBIUpgrade\AfterManualWork.

4.26 Merging Oracle BI Applications Version 7.9.6.4 Presentation Catalog With Current (Custom) Catalog

Note:

Before you begin this procedure, you must have already upgraded your current (custom) catalog to the Oracle BI Enterprise Edition 11g format. For more information, see Section 4.24, "Upgrading the Siebel Analytics Repository and the Web Catalog to the Oracle BI Enterprise Edition 11g Version."

You need to perform the following tasks to complete the presentation catalog merge process.

- Section 4.26.1, "Trimming the Input Presentation Catalog"

- Section 4.26.2, "Merging the Oracle BI Applications Version 7.9.6.4 Presentation Catalog With Current (Custom) Catalog"

- Section 4.26.3, "Testing the Results of the Presentation Catalog Upgrade"

These procedures use the following terminology to identify the various presentation catalogs you will use in the merge process:

- 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 standard Oracle BI Applications 7.9.6.4 presentation catalog that is installed with Oracle BI Applications.

- The current presentation catalog. This is the presentation catalog currently in use at your organization.

4.26.1 Trimming the Input Presentation Catalog

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.

4.26.2 Merging the Oracle BI Applications Version 7.9.6.4 Presentation Catalog With Current (Custom) Catalog

Note:

Before you begin this procedure, you must have already upgraded your current (custom) catalog to the Oracle BI Enterprise Edition 11g format. For more information, see Section 4.24, "Upgrading the Siebel Analytics Repository and the Web Catalog to the Oracle BI Enterprise Edition 11g Version."

Follow the instructions in this section to merge the Oracle BI Applications version 7.9.6.4 presentation catalog with the catalog you are currently using. This procedure uses the Oracle BI Enterprise Edition Catalog Manager. High-level steps for the merge process are provided in this section. For detailed instructions on using the Catalog Manager, see the chapter "Configuring and Managing the Oracle BI Presentation Catalog," in the Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition 11g Release 1 (11.1.1).

To merge the Oracle BI Applications version 7.9.6.4 presentation catalog with the current (custom) catalog:

1. Start the Catalog Manager, and open your current (custom) presentation catalog in offline mode.
For instructions, see the section "Starting Catalog Manager and Opening Catalogs," in the Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition 11g Release 1 (11.1.1).

2. Start another instance of the Catalog Manager, and open the Oracle BI Applications version 7.9.6.4 (out-of-the-box) presentation catalog in offline mode.

3. Copy and paste the custom objects from your current presentation catalog into the Oracle BI Applications version 7.9.6.4 (out-of-the-box) presentation catalog.
For instructions, see section "Working with Objects in Catalog Manager," in the Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition 11g Release 1 (11.1.1).

4. If you created custom catalog groups that are not in the version 7.9.6.4 presentation catalog, you need to convert the custom catalog groups to application roles in order to maintain consistency with the version 7.9.6.4 presentation catalog.
To convert custom catalog groups to application roles, run the following command:

runcat.cmd/runcat.sh -cmd replaceAccountInPermissions -old <Catalog Group Name> -oldType group -new <App Role Name> -newType role -offline  <catalog path>

For example:

runcat.cmd -cmd replaceAccountInPermissions -old "AP Analyst" -oldType group -new "AP Analyst" -newType role -offline  c:/SampleWebcat

This command replaces a specified account with another in all catalog object ACLs and privileges in the presentation catalog, entirely in the offline mode. If an entirely new application role is specified as the replacement account, then it is necessary to refresh the GUIDs in the presentation catalog before it can be used.

Note: If the specified replacement user or group is not already present in the presentation catalog 11g Release 1 (11.1.1) already, then this operation will fail.

For more information, see the Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition 11g Release 1 (11.1.1).

4.26.3 Testing the Results of the Presentation Catalog Upgrade

Note:

Before you perform this step, you must have already migrated 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.

4.27 Regression Testing the Oracle BI Repository Merge

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:

1. 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.

2. 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 Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition.

3. Execute the logical SQL against the old repository using the command line utility nQCmd.exe located in $ORACLE_BI_HOME\bifoundation\server\bin, and save the results to a file.
For information about the nQCmd.exe utility, see Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition.

4. Edit the logical SQL test scripts to account for the name changes or modifications resulting from the upgrade.

5. Execute the edited logical SQL against the merged repository, and save the results.

6. 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.

5 Upgrading Oracle BI Applications 7.9.x for Siebel Source Systems

This section contains instructions for upgrading Oracle BI Applications releases when you are running Siebel CRM Applications as your source system.

This section includes the following topics:

- Section 5.1, "Prerequisites for Upgrading Oracle BI Applications"

- Section 5.2, "Upgrading Oracle BI Infrastructure to Version 11g"

- Section 5.3, "Upgrading Oracle BI Applications"

- Section 5.4, "Upgrading to Informatica PowerCenter Version 9.0.1 Hotfix 2"

- Section 5.5, "Upgrading the Informatica Repository"

- Section 5.6, "Upgrading the Informatica Repository When You Are Already Running Informatica PowerCenter 9.1"

- Section 5.7, "Verifying Configurations for Informatica PowerCenter Version 9.0.1 Hotfix 2 to Work With Oracle BI Applications and DAC"

- Section 5.8, "Upgrading to and Configuring DAC Version 11g"

- Section 5.9, "Importing New Schema Definitions Into the Siebel Transactional Database"

- Section 5.10, "Upgrading the Data Warehouse Schema and Migrating Data for Non-Teradata Databases"

- Section 5.11, "Upgrading the Data Warehouse Schema and Migrating Data for Teradata Databases"

- Section 5.12, "Localizing the Policy Store"

- Section 5.13, "Importing the Oracle BI Applications Version 7.9.6.4 LDIF File Into the Embedded LDAP Server"

- Section 5.14, "Upgrading the Oracle BI Repository and Presentation Catalog to the Oracle BI Enterprise Edition 11g Version"

- Section 5.15, "Merging Oracle BI Applications Version 7.9.6.4 Repository With Customer Repository"

- Section 5.16, "Merging Oracle BI Applications Version 7.9.6.4 Presentation Catalog With Current (Custom) Catalog"

- Section 5.17, "Regression Testing the Oracle BI Repository Merge"

5.1 Prerequisites for Upgrading Oracle BI Applications

Complete the following prerequisites before upgrading to Oracle BI Applications release 7.9.6.4:

- The DAC Client requires an ODBC connection to the Oracle Business Analytics Warehouse when the database type is Oracle, SQL Server, DB2, and DB2-390 in order to upgrade the data warehouse schema using the DDL Import Utility.
Additionally, Siebel CRM source systems require an ODBC connection to the OLTP (source) database on the machine where Oracle BI Applications software is installed. This ODBC connection will be used by the DDLIMP utility.

Before you upgrade to Oracle BI Applications verify whether you have the appropriate ODBC connections set. If you do not, see Appendix F, "Creating ODBC Database Connections for DAC."

5.2 Upgrading Oracle BI Infrastructure to Version 11g

You must upgrade Oracle BI Infrastructure to version 11g. For the specific release of Oracle BI Infrastructure 11g that is supported for this release of Oracle BI Applications, see the System Requirements and Supported Platforms for Oracle Business Intelligence Applications. For information on installing the supported version of Oracle BI Infrastructure, see the Oracle Fusion Middleware Upgrade Guide for Oracle Business Intelligence.

5.3 Upgrading Oracle BI Applications

Run the Oracle BI Applications installer to upgrade your Oracle BI Applications environment to the current version. For instructions on running the installer, see the Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users.

Note the following points:

- Review "Chapter 3: Preinstallation and Predeployment Requirements for Oracle BI Applications," in the Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users. You must satisfy these requirements in order to upgrade to the current version of Oracle BI Applications.

- Perform only the step that addresses the running of the installer. Do not perform the configuration instructions that follow the running of the installer.

- If you have a previous release of Oracle BI Applications installed, you must uninstall it before you run the installer for the current release. If you do not uninstall the old release, some folders from the current release will not be correctly installed. (Make a back-up of your DAC folder before you uninstall the old release. This will be the backup of your DAC Client and Server and the DAC metadata files.)

5.4 Upgrading to Informatica PowerCenter Version 9.0.1 Hotfix 2

You must install Informatica PowerCenter 9.0.1 Hotfix 2 to run the current version of Oracle BI Applications. See the System Requirements and Supported Platforms for Oracle Business Intelligence Applications for information about additional hotfixes or emergency bug fixes that may be required to support the current version of Informatica.

Note:

Oracle BI Applications release 7.9.6.4 is also certified to run with Informatica PowerCenter version 9.1 Hotfix 2. For instructions on upgrading the Informatica Repository if you have previously upgraded to Informatica PowerCenter 9.1 Hotfix 2, see Section 5.6, "Upgrading the Informatica Repository When You Are Already Running Informatica PowerCenter 9.1."

The components and architecture for Informatica PowerCenter 9.x differ significantly from Informatica PowerCenter 7.x and 8.x. Oracle recommends that you carefully review the Informatica PowerCenter 9.0.1 documentation.

For a summary of installation instructions for installing Informatica PowerCenter 9.0.1 on a single machine in an Oracle BI Applications deployment, see the Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users.

For detailed information about deploying Informatica PowerCenter 9.0.1, refer to the Informatica PowerCenter Installation and Configuration Guide, Informatica Upgrade Guide for PowerCenter 8.1.x, Informatica Upgrade Guide for PowerCenter 8.5.x and 8.6.x, Informatica Administrator Guide, and related documentation. See the Oracle Business Intelligence Applications Release Notes, available on the Oracle Technology Network, for information about how to locate the Informatica documentation.

To upgrade to Informatica PowerCenter 9.0.1 Hotfix 2:

- Perform the pre-upgrade, upgrade, and post-upgrade steps documented in Informatica Upgrade Guide for PowerCenter 8.1.x or Informatica Upgrade Guide for PowerCenter 8.5.x and 8.6.x, depending on which version of Informatica PowerCenter you are upgrading from.

Note the following points:

- The Informatica PowerCenter 9.0.1 installation process includes upgrading your current Informatica Repository to the version 9.0.1 format. This process is necessary so that you will be able to access your current repository using the version 9.0.1 client tools and so that you can perform the procedure Section 5.5, "Upgrading the Informatica Repository."
In Section 5.5, "Upgrading the Informatica Repository," you back up and rename your current repository and then restore the Informatica Repository that is installed during the Oracle BI Applications installation (for example, Oracle_BI_DW_Base.rep). You then copy the folders containing the Oracle BI Applications content for release 7.9.6.4 to your existing repository.

- If you install Informatica PowerCenter 9.0.1 using the installer Upgrade option rather than the Install option, the property $PMRootDir is not updated to the upgraded service version installation directory. You need to configure this property to specify the upgraded service installation directory in order for DAC to be able to locate the Informatica source files.
To configure the $PMRootDir property: launch Informatica Administrator, select the Integration Service from the Navigator, click the Processes tab, and click Edit. Then, enter the appropriate value for $PMRootDir.

5.5 Upgrading the Informatica Repository

Follow this procedure to upgrade the Informatica Repository when you are upgrading the Informatica PowerCenter platform from version 7.x or 8.x to 9.0.1 Hotfix 2. If you have already upgraded to Informatica PowerCenter 9.1, follow the procedure in Section 5.6, "Upgrading the Informatica Repository When You Are Already Running Informatica PowerCenter 9.1."

In this procedure, you will copy the folders containing the Oracle BI Applications 7.9.6.4 content into your current, existing Informatica Repository. The result of this action is an Informatica Repository that contains your customizations along with the new Oracle BI Applications 7.9.6.4 content.

For detailed instructions on backing up and restoring the Informatica Repository, see the topic titled, "Backing Up and Restoring the PowerCenter Repository," in "Chapter 15: PowerCenter Repository Management," in the Informatica PowerCenter Administrator Guide. See the Oracle Business Intelligence Applications Release Notes, available on the Oracle Technology Network, for information about how to locate the Informatica documentation.

To upgrade the Informatica Repository:

1. Make sure you have backed up and renamed your current, existing Informatica Repository.

2. Copy the Oracle_BI_DW_Base.rep file (or Oracle_BI_DW_Teradata.rep for repositories on Teradata databases) from the folder OracleBI\dwrep\Informatica\Repository into the folder <INFA_HOME>\server\infa_shared\Backup.

Note:

The Oracle_BI_DW_Base.rep file is installed in the OracleBI root directory when you run the Oracle BI Applications installer, as described in Section 5.3, "Upgrading Oracle BI Applications."

3. Using Informatica PowerCenter Administrator, create a new Repository Service for the Oracle_BI_DW_Base.rep repository. See "Setup Step: Creating the Informatica Repository Service," in Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users for instructions.

4. Using the Repository Service you created in the step above, restore the Oracle_BI_DW_Base.rep repository into an empty schema. See "Restoring the Prebuilt Informatica Repository for Environments in English" or "Restoring the Prebuilt Informatica Repository on a Non-English Operating System" in Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users for instructions.
This step gives you the Oracle BI Applications 7.9.6.4 Informatica Repository in the Informatica 9.0.1 format.

5. Launch the Informatica PowerCenter Repository Manager, and connect to the repository you restored in step 4 (for example, Oracle_BI_DW_Base.rep), and connect to your current, existing Informatica Repository.
Note: Your current, existing repository should have been updated to the version 9.0.1 format during the Informatica PowerCenter 9.0.1 installation process.

6. In your current, existing repository, make sure all of your customizations are in a "Custom" folder.

7. In your current, existing repository, delete the following folders:

- PLP

- All folders with the prefix SDE_

- SILOS

- SIL_VERT

- UA_SDE

- UA_SIL

Make sure you do not delete the "Custom" folder.

8. Copy the following folders containing the Oracle BI Applications content for release 7.9.6.4 from the newly restored repository (Oracle_BI_DW_Base.rep) into your current, existing repository.

- PLP

- All folders with the prefix SDE_

- SILOS

- SIL_VERT

- UA_SDE

- UA_SIL

This action updates your current, existing repository with the Oracle BI Applications 7.9.6.4 content; this is the repository you will use to run ETL in Oracle BI Applications 7.9.6.4.

The version 7.9.6.4 repository (Oracle_BI_DW_Base.rep) and the Repository Service for this repository are no longer needed.

5.6 Upgrading the Informatica Repository When You Are Already Running Informatica PowerCenter 9.1

If you are upgrading to Oracle BI Applications 7.9.6.4 and previously upgraded Informatica PowerCenter to version 9.1 Hotfix 2, you must first restore the Oracle BI Applications version 7.9.6.4 Informatica Repository using Informatica PowerCenter 9.0.1 Hotfix 2. Then, you can upgrade this repository to the Informatica 9.1 format by pointing to it using Informatica 9.1 client tools. After the Oracle BI Applications 7.9.6.4 Informatica Repository has been upgraded to the Informatica 9.1 format, you can then copy the folders containing the Oracle BI Applications 7.9.6.4 content into your current, existing Informatica Repository. The result of this action is an Informatica Repository that contains your customizations along with the new Oracle BI Applications 7.9.6.4 content.

For detailed instructions on backing up and restoring the Informatica Repository, see the topic titled, "Backing Up and Restoring the PowerCenter Repository," in "Chapter 15: PowerCenter Repository Management," in the Informatica PowerCenter Administrator Guide. See the Oracle Business Intelligence Applications Release Notes, available on the Oracle Technology Network, for information about how to locate the Informatica documentation.

To upgrade the Informatica Repository when already running Informatica PowerCenter 9.1:

1. Make sure you have backed up and renamed your current, existing Informatica Repository.

2. Install Informatica PowerCenter Services version 9.0.1 Hotfix 2. You do not need to install the Informatica PowerCenter Client Tools. See Section 5.4, "Upgrading to Informatica PowerCenter Version 9.0.1 Hotfix 2" for instructions.

3. Copy the Oracle_BI_DW_Base.rep file (or Oracle_BI_DW_Teradata.rep for repositories on Teradata databases) from the folder OracleBI\dwrep\Informatica\Repository into the Informatica PowerCenter 9.0.1 folder <INFA_HOME>\server\infa_shared\Backup.

Note:

The Oracle_BI_DW_Base.rep file is installed in the OracleBI root directory when you run the Oracle BI Applications installer, as described in Section 5.3, "Upgrading Oracle BI Applications."

4. Using Informatica PowerCenter Administrator, create a new Repository Service for the Oracle_BI_DW_Base.rep repository. See "Setup Step: Creating the Informatica Repository Service," in Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users for instructions.

5. Using the Repository Service you created in the step above, restore the Oracle_BI_DW_Base.rep repository into an empty schema. See "Restoring the Prebuilt Informatica Repository for Environments in English" or "Restoring the Prebuilt Informatica Repository on a Non-English Operating System" in Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users for instructions.
This step gives you the Oracle BI Applications 7.9.6.4 Informatica Repository in Informatica 9.0.1 format.

6. Launch the Informatica PowerCenter Repository Manager, and connect to the repository you restored in step 5. When prompted to upgrade the repository to the 9.1 format, do so.

7. In Repository Manger, connect to your current, existing Informatica Repository.

8. In your current, existing repository, make sure all of your customizations are in a "Custom" folder.

9. In your current, existing repository, delete the following folders:

- PLP

- All folders with the prefix SDE_

- SILOS

- SIL_VERT

- UA_SDE

- UA_SIL

Make sure you do not delete the "Custom" folder.

10. Copy the following folders containing the Oracle BI Applications content for release 7.9.6.4 from the newly restored repository (Oracle_BI_DW_Base.rep) into your current, existing repository.

- PLP

- All folders with the prefix SDE_

- SILOS

- SIL_VERT

- UA_SDE

- UA_SIL

This action updates your current, existing repository with the Oracle BI Applications 7.9.6.4 content; this is the repository you will use to run ETL in Oracle BI Applications 7.9.6.4.

The version 7.9.6.4 repository (Oracle_BI_DW_Base.rep) and the Repository Service for this repository are no longer needed.

5.7 Verifying Configurations for Informatica PowerCenter Version 9.0.1 Hotfix 2 to Work With Oracle BI Applications and DAC

Informatica PowerCenter version 9.0.1 Hotfix 2 requires configuration for it to work with Oracle BI Applications and DAC. The configuration settings from your earlier Informatica environment may have been retained when you upgraded to Version 9.0.1 Hotfix 2. Verify or perform the procedures listed below, as documented in the Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users:

- Copying Source Files and Lookup Files

- Setting PowerCenter Integration Services Relaxed Code Page Validation

- Setting PowerCenter Integration Services Custom Properties

- Creating the Repository Administrator User in the Native Security Domain

5.8 Upgrading to and Configuring DAC Version 11g

This section includes instructions for upgrading the DAC platform and repository to version 11g as well as information about configurations you must set or verify.

This section includes the following topics:

- Section 5.8.1, "Installing the DAC Platform and Oracle BI Applications Metadata Repository Files"

- Section 5.8.2, "Configuring the DAC Client and Server to Work With Oracle BI Applications and Informatica"

- Section 5.8.3, "Upgrading the DAC Repository"

5.8.1 Installing the DAC Platform and Oracle BI Applications Metadata Repository Files

The current release of DAC 11g is installed by its own installer and not the Oracle BI Applications installer. For information about the specific release of DAC 11g that is supported for this release of Oracle BI Applications, see System Requirements and Supported Platforms for Oracle Business Intelligence Applications.

After you install DAC 11g, you then need to copy metadata files from the machine hosting Oracle BI Applications to the machines hosting the DAC Client and Server. You then need to import the new metatdata into the DAC Repository. For instructions on performing these tasks, see the following sections in the Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users:

- Installing and Setting Up the DAC Platform

Note:

You must perform all of the procedures in this section, including installing JDBC drivers, creating ODBC database connections, and installing pmrep and pmcmd command line programs.

- Installing DAC Metadata Files

- Logging into DAC for the First Time and Importing Metadata into the DAC Repository

Note:

When you perform this step, DAC will prompt you to upgrade the repository. Click Yes. This action will upgrade your repository in the 10g format to the 11g format.

After you complete this procedure, you will have the default DAC Repository for Oracle BI Applications release 7.9.6.4.

5.8.2 Configuring the DAC Client and Server to Work With Oracle BI Applications and Informatica

The DAC Client and Server require configuration to work with Oracle BI Applications and Informatica PowerCenter. The configuration settings from your earlier DAC environment may have been retained when you upgraded to version 11g. Verify or perform the procedures listed below, as documented in the Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users:

- Configuring the DAC Server

- Configuring DAC Integration Settings

- Configuring the SiebelUnicodeDB Custom Property

Note:

This procedure is required only if your source to target data movement configuration is Unicode to Unicode.

- Setting Up DAC to Receive Email Notification

- Additional Configuration Tasks
In this section, perform only the tasks that apply to your environment.

5.8.3 Upgrading the DAC Repository

To upgrade the DAC Repository, you perform a two-step process:

1. You first upgrade the existing DAC Repository from the 10g format to the 11g format. When you log into DAC 11g for the first time, DAC will prompt you to upgrade your repository. Click Yes.
For more information, see "Upgrading to DAC 11g" in Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Data Warehouse Administration Console and "Logging Into DAC for the First Time and Importing Metadata into the DAC Repository" in Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users.

2. You then use the DAC's Upgrade/Merge Wizard to complete the upgrade of your existing DAC Repository.

- If you are upgrading to Oracle BI Applications release 7.9.6.4, and you are remaining on the same version of the transactional source system, you would use the Refresh Base option of the DAC Upgrade/Merge Wizard to complete the upgrade of your existing DAC Repository. For information about how to use the Refresh Base option, see the topic titled, "About the Refresh Base Option," in the chapter "Upgrading, Comparing and Merging DAC Repositories," in the Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Data Warehouse Administration Console.

- If you are upgrading your transactional system, for example, from Oracle EBS release 12 to release 12.2, you would use the Replace Base option of the DAC Upgrade/Merge Wizard to complete the upgrade of your existing DAC Repository. For information about how to use the Replace Base option, see the topic titled, "About the Replace Base Option," in "Upgrading, Comparing and Merging DAC Repositories," in the Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Data Warehouse Administration Console.

The Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Data Warehouse Administration Console is available in the Oracle Business Intelligence Data Warehouse Administration Console Documentation Library on the Oracle Technology Network.

5.9 Importing New Schema Definitions Into the Siebel Transactional Database

This procedure upgrades transactional database objects that relate to Oracle Business Intelligence Applications. It does not upgrade transactional database objects for Siebel CRM applications.

To import new schema definitions into the Siebel transactional database:

1. Import schema definitions for non-image tables:

1. Access the DDLimp utility.

2. Run the DDL_OLTP.ctl script that is located in the OracleBI\dwrep\Upgrade\CTLFiles folder.
Note: If you receive an error message stating a particular object already exists in the database, use the DDLimp Merge argument (/M Y) in the DDLimp command to resolve the error.

2. Import schema definitions for image tables:

1. In DAC, go to the Design view, and select your custom container from the drop-down list to the right of the Execute button.

2. Click the Tables tab.

3. Query for all tables for which the image suffix is not null.

4. Right-click in the list of tables returned by the query, and select Change Capture Scripts, and then Generate Image and Trigger Scripts.

5. In the Triggers and Image Tables dialog box, do the following:
- Select the option All Tables in the List.

- Select the option Generate Image Table Scripts.

- Select the appropriate database type for the source system.

- Click OK.

6. Open the SQL client for the source system database type, for example, SQL Plus for Oracle, Query Analyzer for SQL Server, or a command window for DB2.
The script may contain many lines; therefore, you can save the script file as a SQL file and execute it in a SQL client.

7. Copy the scripts generated by DAC into the SQL client and execute them.

5.9.1 Verifying the Siebel Transactional Database Upgrade

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_xxx

- S_ETL_I_IMG_xxx

- S_ETL_D_IMG_xxx

- S_ETL_PARAM

- S_ETL_PRD_ATTR

- S_ETL_PRD_REL

5.10 Upgrading the Data Warehouse Schema and Migrating Data for Non-Teradata Databases

This section contains the following topics:

- Section 5.10.1, "Upgrading the Data Warehouse Schema From Version 7.9.0 to 7.9.4 and Migrating Data"

- Section 5.10.2, "Upgrading the Data Warehouse Schema From Version 7.9.4 to 7.9.5 and Migrating Data"

- Section 5.10.3, "Upgrading the Data Warehouse Schema From Version 7.9.5 to 7.9.5.1"

- Section 5.10.4, "Upgrading the Data Warehouse Schema From Version 7.9.5.1 to 7.9.6.1 and Migrating Data"

- Section 5.10.5, "Upgrading the Data Warehouse Schema From Version 7.9.6 to 7.9.6.1 and Migrating Data" (Applicable only if you are using an Oracle database as your data warehouse database.)

- Section 5.10.6, "Upgrading the Data Warehouse Schema From Version 7.9.6.1 to 7.9.6.2 and Migrating Data"

- Section 5.10.7, "Upgrading the Data Warehouse Schema From Version 7.9.6.2 to 7.9.6.3 and Migrating Data"

- Section 5.10.8, "Upgrading the Data Warehouse Schema From Version 7.9.6.3 to 7.9.6.4 and Migrating Data"

If you are currently running Oracle BI Applications release 7.9.0, 7.9.1, 7.9.2 or 7.9.3, you need to perform the procedures in Section 5.10.1, Section 5.10.2, Section 5.10.3, Section 5.10.4, Section 5.10.6, Section 5.10.7, and Section 5.10.8.

If you are currently running Oracle BI Applications release 7.9.4, you need to perform the procedures in Section 5.10.2, Section 5.10.3, Section 5.10.4, Section 5.10.6, Section 5.10.7, and Section 5.10.8.

If you are currently running Oracle BI Applications release 7.9.5, you need to perform the procedures in Section 5.10.3, Section 5.10.4, Section 5.10.6, Section 5.10.7, and Section 5.10.8

If you are currently running Oracle BI Applications release 7.9.5.1, you need to perform the procedures in Section 5.10.4, Section 5.10.6, Section 5.10.7, and Section 5.10.8.

If you are currently running Oracle BI Applications release 7.9.6, you need to perform the procedures in Section 5.10.5, Section 5.10.6, Section 5.10.7, and Section 5.10.8.

If you are currently running Oracle BI Applications release 7.9.6.1, you need to perform the procedures in Section 5.10.6, Section 5.10.7, and Section 5.10.8.

If you are currently running Oracle BI Applications release 7.9.6.2, you need to perform the procedures in Section 5.10.7 and Section 5.10.8.

If you are currently running Oracle BI Applications release 7.9.6.3, you need to perform the procedures in Section 5.10.8.

These procedures add new tables, columns, and indexes to the existing data warehouse schema. They also modify the existing data warehouse schema objects.

5.10.1 Upgrading the Data Warehouse Schema From Version 7.9.0 to 7.9.4 and Migrating Data

You need to perform this procedure if you are upgrading from Oracle BI Applications releases 7.9.0, 7.9.1, 7.9.2 or 7.9.3.

To upgrade the data warehouse schema to version 7.9.4 and migrate data:

1. Run the 792_UPGRADE_PRE_CTL_SCRIPT.sql script.

1. Open the SQL client for your database type.

2. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\<database type>.

3. Open the 792_UPGRADE_PRE_CTL_SCRIPT.sql file, and copy the contents into the SQL client.

4. Execute the script.

2. Run the ddl_794.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

3. Run the 792_UPGRADE_PRE_DIMENSION_SCRIPT.sql script. This file is located in the OracleBI\dwrep\Upgrade\DbScripts\<database type> folder.

4. If you upgraded your transactional database to Siebel Applications 8.x or 8.1.1, run the workflows to migrate your data into the upgraded data warehouse.

1. In Informatica Workflow Manager, navigate to the folder UPGRADE_790_TO_791_SBL80UPG.

2. Run the following workflows in the order specified below:
UPGRADE_DIMENSIONS

UPGRADE_FACTS

5. Verify the data migrated successfully by checking whether any of the Informatica mapping log files stored in the <INFA_HOME>\server\infa_shared\SessLogs directory indicate errors or failures. Also, validate the data in the upgraded data warehouse.

6. If the data migration was successful, drop the tables that were created during the upgrade process, such as, W_xxxx_x_79x tables, LKP_xxxx_x and 79x_XXXX_TMP.
This step frees the space occupied by these backup tables.

7. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep). For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Base Informatica Repository."

5.10.2 Upgrading the Data Warehouse Schema From Version 7.9.4 to 7.9.5 and Migrating Data

You need to perform this procedure if you are upgrading from Oracle BI Applications releases 7.9.0, 7.9.1, 7.9.2, 7.9.3 or 7.9.4.

To upgrade the data warehouse schema to version 7.9.5 and migrate data:

1. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade repository. For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Upgrade Informatica Repository."

2. Run the 795_UPGRADE_PRE_CTL_SCRIPT.sql script. This file is located in the OracleBI\dwrep\Upgrade\DbScripts\<database type> folder.

3. Run the UPGRADE_795.ctl script. For instructions, seeAppendix E, "Using the DDLimp Utility to Run CTL Files."

4. Run the ddl_795.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

5. Run the 795_UPGRADE_PRE_DIMENSION_SCRIPT.sql script. This file is located in the OracleBI\dwrep\Upgrade\DbScripts\<database type> folder.

6. Copy all of the domain value files in the folder \OracleBI\dwrep\Informatica\LkpFiles into the folder <INFA_HOME>\server\infa_shared\LkpFiles.

7. Migrate data into the upgraded data warehouse.

1. Copy the file Upgrade.rep file from the folder OracleBI\dwrep\Upgrade\Informatica\Repository into the folder <INFA_HOME>\server\infa_shared\Backup.

2. Launch the Informatica Administrator, and restore Upgrade.rep (located in <INFA_HOME>\server\infa_shared\Backup).

3. Configure the Informatica parameter file 795_UPG_PARAMS.txt. For instructions, Appendix A, "Setting Parameters in 795_UPG_PARAMS.txt."

4. In Informatica Workflow Manager, open the Relational Connection Browser (in the menu bar, select Connections, and then select Relational), and edit the connect string, user and password for the relational connections as follows:
Edit the PARAM_OLTP connection to match your OLTP environment.

Edit the PARAM_OLAP connection to match your OLAP environment.

Note:

If you are connected to an Oracle database, use the 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.

5. In Informatica Workflow Manager, navigate to the folder UPGRADE_794_to_795_SBL and execute the UPGRADE_DIMENSIONS workflow.

8. Verify the data migrated successfully.

1. Validate the data in the upgraded data warehouse.

2. Check whether any of the Informatica mapping log files stored in the <INFA_HOME>\server\infa_shared\Sesslogs directory indicates errors or failures.

3. Check whether the script 795_UPGRADE_PRE_DIMENSION_SCRIPT.sql that you ran in the SQL client of the database failed or errored out while executing.

4. Check the log files for DDL_795.ctl and Upgrade_795.ctl, which 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.

Note:

Ignore any error messages that indicate tables or indexes could not be dropped from the database. These error messages are displayed when the specified objects do not exist in the database. This can occur because each source system container holds a subset of all data warehouse tables

9. If the data migration was successful, drop the tables that were created during the upgrade process, such as W_xxxx_x_79x, LKP_xxxx_x and 79x_xxxx_TMP.
This step frees the space occupied by these backup tables.

10. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep). For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Base Informatica Repository."

5.10.3 Upgrading the Data Warehouse Schema From Version 7.9.5 to 7.9.5.1

You need to perform this procedure if you are upgrading from Oracle BI Applications releases 7.9.0, 7.9.1, 7.9.2, 7.9.3, 7.9.4 or 7.9.5.

To upgrade the data warehouse schema to version 7.9.5.1:

- Use the DDLimp utility to run the ddl_7951.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

5.10.4 Upgrading the Data Warehouse Schema From Version 7.9.5.1 to 7.9.6.1 and Migrating Data

You need to perform this procedure if you are upgrading from Oracle BI Applications releases 7.9.0, 7.9.1, 7.9.2, 7.9.3, 7.9.4, 7.9.5 or 7.9.5.1.

This procedure adds new tables, columns, and indexes to the existing data warehouse schema. It also modifies the existing data warehouse schema objects.

This section includes the following procedures:

- Section 5.10.4.1, "Upgrading the Data Warehouse Schema to Version 7.9.6.1"

- Section 5.10.4.2, "Migrating Data Into the Upgraded Data Warehouse"

- Section 5.10.4.3, "Verifying the Data Migrated Successfully"

5.10.4.1 Upgrading the Data Warehouse Schema to Version 7.9.6.1

Follow this procedure to upgrade the data warehouse schema to version 7.9.6.1.

Note: Upgrading to version 7.9.6.1 may involve running scripts that have a "796_" prefix.

To upgrade the data warehouse schema to version 7.9.6.1 and migrate data:

1. If you are using an Oracle database, run the 796_UPGRADE_DROP_INDEXES.sql script.

1. Open the SQL client for your database type.

2. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Oracle.

3. Open the 796_UPGRADE_DROP_INDEXES. sql file, and copy the contents into the SQL client.

4. Execute the script.

2. If you are using a SQL Server or DB2 database, run the 7961_UPGRADE_DROP_INDEXES.sql script.

1. Open the SQL client for your database type.

2. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\<database type>.

3. Open the 7961_UPGRADE_DROP_INDEXES. sql file, and copy the contents into the SQL client.

4. Execute the script.

3. If you are using a SQL Server database, run the 7961_UPGRADE_PRE_UPG_CTL_SCRIPT.sql file. This file is located in OracleBI\dwrep\Upgrade\DbScripts\SQLServer.

4. Run the UPGRADE_796.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

5. Run the 7961_UPGRADE_PRE_CTL_SCRIPT.sql:

1. Go to OracleBI\dwrep\Upgrade\DbScripts\<database type> folder, and open the 7961_UPGRADE_PRE_CTL_SCRIPT.sql file.

2. Search for the Datasource_Num_ID parameter, and make sure the value is correct for your existing implementation.

3. If you are using a DB2 database, search for the text "TBS_32K," and replace it with the appropriate 32K table space name that you have configured.

4. Execute the script.

6. Run the ddl_7961.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

7. Run the 796_UPGRADE_PRE_DIMENSION_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

8. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository. For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Upgrade Informatica Repository."

9. Copy all of the domain value files in the folder \OracleBI\dwrep\Informatica\LkpFiles into the folder <INFA_HOME>\server\infa_shared\LkpFiles.

5.10.4.2 Migrating Data Into the Upgraded Data Warehouse

Follow this procedure to migrate data into the upgraded data warehouse.

To migrate data into the upgraded data warehouse:

1. Copy the file Upgrade.rep from the folder OracleBI\dwrep\Upgrade\Informatica\Repository into the folder <INFA_HOME>\server\infa_shared\Backup.

2. Launch the Informatica Administrator, and restore Upgrade.rep (located in <INFA_HOME>\server\infa_shared\Backup).

3. Configure the Informatica parameter file 796_UPG_PARAMS.txt file. For instructions, see Appendix A, "Setting Parameters in 796_UPG_PARAMS.txt."

4. Configure parameters specific to Siebel source systems. For instructions, see Appendix A, "Setting Parameters in 796_UPG_PARAMS.txt for Siebel Source Systems."

5. In Informatica Workflow Manager, open the Relational Connection Browser (in the menu bar, select Connections, and then select Relational), and edit the connect string, user and password for the relational connections as follows:

1. Edit the connection PARAM_OLTP_SIEBEL to match your OLTP environment.

2. Edit the connection PARAM_OLAP to match your OLAP environment.

3. Edit the connection PARAM_DAC to match your DAC database.

Note:

If you are connected to an Oracle database, use the 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.

6. Back up and truncate the table W_POSITION_DH.

7. In Informatica Workflow Manager, navigate to the folder UPGRADE_7951_to_796_SBL and execute the following workflows in the order specified:

- UPGRADE_DIMENSIONS

- UPGRADE_FACTS

- RESET_DAC_REFRESH_DATES

8. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep). For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Base Informatica Repository."

9. Run the 7961_UPGRADE_PRE_DIMENSION_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

10. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository. For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Upgrade Informatica Repository."

11. Configure the Informatica parameter file 7961_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7961_UPG_PARAMS.txt."

12. In Informatica Workflow Manager, navigate to the folder UPGRADE_796_to_7961_SBL and execute the first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

13. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep). For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Base Informatica Repository."

14. Run the 7961_UPGRADE_POST_SCRIPT.sql. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

5.10.4.3 Verifying the Data Migrated Successfully

Follow this procedure to verify that the data was migrated successfully into the upgraded data warehouse.

To verify the data migrated successfully:

1. Validate the data in the upgraded data warehouse.

2. Check whether any of the Informatica mapping log files stored in the <INFA_HOME>\server\infa_shared\Sesslogs directory indicates errors or failures.

3. Check whether the following scripts that you ran in the SQL client of the database failed or errored out while executing:
7961_UPGRADE_DROP_INDEXES.sql

7961_UPGRADE_PRE_CTL_SCRIPT.sql

796 UPGRADE_PRE_DIMENSION.sql

7961_UPGRADE_PRE_DIMENSION.sql

7961_UPGRADE_POST_SCRIPT.sql

4. Check the log files for the ddl_7961.ctl and Upgrade_796.ctl scripts 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.

Note:

Ignore any error messages that indicate tables or indexes could not be dropped from the database. These error messages are displayed when the specified objects do not exist in the database. This can occur because each source system container holds a subset of all data warehouse tables

5. If the data migration was successful, drop the tables that were created during the upgrade process, such as W_xxxx_x_79x, LKP_xxxx_x, 79x_xxxx_TMP, and TMP_xxxx_79x.
This step frees the space occupied by these backup tables.

5.10.5 Upgrading the Data Warehouse Schema From Version 7.9.6 to 7.9.6.1 and Migrating Data

Perform the procedures in this section if you are upgrading from Oracle BI Applications release 7.9.6 to release 7.9.6.1.

Note:

This procedure is applicable only if you are using an Oracle database for your data warehouse database.

This section includes the following procedures:

- Section 5.10.5.1, "Upgrading the Data Warehouse Schema to Version 7.9.6.1"

- Section 5.10.5.2, "Migrating Data Into the Upgraded Data Warehouse"

- Section 5.10.5.3, "Verifying the Data Migrated Successfully"

5.10.5.1 Upgrading the Data Warehouse Schema to Version 7.9.6.1

Follow this procedure to upgrade the data warehouse schema to version 7.9.6.1.

To upgrade the data warehouse schema to version 7.9.6.1:

1. Run the UPGRADE_7961.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

2. Run the 796ORA_TO_7961ORA_UPGRADE_PRE_CTL_SCRIPT.sql. This file is located in the folder OracleBI\dwrep\Upgrade\DbScripts\Oracle.

3. Run the ddl_7961.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

5.10.5.2 Migrating Data Into the Upgraded Data Warehouse

Follow this procedure to migrate data into the upgraded data warehouse.

To migrate data into the upgraded data warehouse:

1. Run the 7961_UPGRADE_PRE_DIMENSION_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Oracle.

2. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade repository. For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Upgrade Informatica Repository."

3. Configure the Informatica parameter file 7961_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7961_UPG_PARAMS.txt."

4. In Informatica Workflow Manager, navigate to the folder UPGRADE_796_to_7961_SBL and execute the first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

5. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep). For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Base Informatica Repository."

6. Run the 7961_UPGRADE_POST_SCRIPT.sql. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Oracle.

5.10.5.3 Verifying the Data Migrated Successfully

Follow this procedure to verify that the data was migrated successfully into the upgraded data warehouse.

To verify the data migrated successfully:

1. Validate the data in the upgraded data warehouse.

2. Check whether any of the Informatica mapping log files stored in the <INFA_HOME>\server\infa_shared\Sesslogs directory indicates errors or failures.

3. Check whether the following scripts that you ran in the SQL client of the database failed or errored out while executing:
7961_UPGRADE_DROP_INDEXES.sql

7961_UPGRADE_PRE_CTL_SCRIPT.sql

7961_UPGRADE_PRE_DIMENSION.sql

7961_UPGRADE_POST_SCRIPT.sql

4. Check the log files for the ddl_7961.ctl and Upgrade_7961.ctl scripts, which 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.

Note:

Ignore any error messages that indicate tables or indexes could not be dropped from the database. These error messages are displayed when the specified objects do not exist in the database. This can occur because each source system container holds a subset of all data warehouse tables

5. If the data migration was successful, drop the tables that were created during the upgrade process, such as W_xxxx_x_79x, LKP_xxxx_x and 79x_xxxx_TMP.
This step frees the space occupied by these backup tables.

6. Once the data migration steps above are complete, you can delete the Upgrade repository to avoid any accidental use or confusion.

1. In the Informatica Administrator, select the Upgrade repository service.

2. In the General Properties area of the Properties tab, click Edit.

3. Make sure the operating mode of the repository service is set to Exclusive.

4. Click OK.

5. Choose Actions, and then click Delete Contents.

6. In the Delete contents for <repository name> dialog, enter the repository username and password, and then click OK.

5.10.6 Upgrading the Data Warehouse Schema From Version 7.9.6.1 to 7.9.6.2 and Migrating Data

This section contains the following procedures:

- Section 5.10.6.1, "Upgrading the Data Warehouse Schema to Version 7.9.6.2"

- Section 5.10.6.2, "Migrating Data Into the Upgraded Data Warehouse"

- Section 5.10.6.3, "Verifying the Data Migrated Successfully"

You need to complete each of these procedures in order to upgrade the data warehouse schema to version 7.9.6.2 and migrate data.

5.10.6.1 Upgrading the Data Warehouse Schema to Version 7.9.6.2

Follow this procedure to upgrade the data warehouse schema to version 7.9.6.2.

To upgrade the data warehouse schema to version 7.9.6.2:

1. Generate the scripts to drop and create indexes. For instructions, see Section B.1, "Generating Scripts to Drop and Create Indexes for Upgrading to Release 7.9.6.2."

2. Run the script to drop all indexes. For instructions, see Section B.2, "Running the Script to Drop All Indexes for Upgrading to Release 7.9.6.2."

3. If you are using a SQL Server database, run the 7962_UPGRADE_PRE_UPG_CTL_SCRIPT.sql file. This file is located in OracleBI\dwrep\Upgrade\DbScripts\SQLServer.

4. Run the UPGRADE_7962.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

5. Run the 7962_UPGRADE_PRE_CTL_SCRIPT.sql. This file is located in the folder OracleBI\dwrep\Upgrade\DbScripts\<database type>.

6. Run the ddl_7962.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

5.10.6.2 Migrating Data Into the Upgraded Data Warehouse

Follow this procedure to migrate data into the upgraded data warehouse.

To migrate data into the upgraded data warehouse:

1. Run the 7962_UPGRADE_PRE_DIMENSION_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

2. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade repository.

3. Configure the Informatica parameter file 7962_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7962_UPG_PARAMS.txt."

4. Run the script to create ETL indexes. For instructions, see Section B.3, "Running the Scripts to Create ETL and Query Indexes for Upgrading to Release 7.9.6.2."

5. In Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_SBL and execute the UPGRADE_DIMENSIONS workflow.

6. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep). For instructions, seeAppendix D, "Running reset_infa_seq_gen.bat on Base Informatica Repository."

7. Run the script to create Query indexes. For instructions, see Section B.3, "Running the Scripts to Create ETL and Query Indexes for Upgrading to Release 7.9.6.2."

5.10.6.3 Verifying the Data Migrated Successfully

Follow this procedure to verify that the data was migrated successfully into the upgraded data warehouse.

To verify the data migrated successfully:

1. Validate the data in the upgraded data warehouse.

2. Check whether any of the Informatica mapping log files stored in the <INFA_HOME>\server\infa_shared\Sesslogs directory indicates errors or failures.

3. Check whether the following scripts that you ran in the SQL client of the database failed or errored out while executing:
dropallindexes.sql

7962_UPGRADE_PRE_CTL_SCRIPT.sql

7962_UPGRADE_PRE_DIMENSION.sql

createETLIndexes.sql

createQueryIndexes.sql

4. Check the log files for the ddl_7962.ctl and Upgrade_7962.ctl scripts, which 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.

Note:

Ignore any error messages that indicate tables or indexes could not be dropped from the database. These error messages are displayed when the specified objects do not exist in the database. This can occur because each source system container holds a subset of all data warehouse tables.

5. If the data migration was successful, drop the tables that were created during the upgrade process, such as W_xxxx_x_79x, LKP_xxxx_x and 79x_xxxx_TMP.
This step frees the space occupied by these backup tables.

6. Once the data migration steps above are complete, you can delete the Upgrade repository to avoid any accidental use or confusion.

1. In the Informatica Administrator, select the Upgrade repository service.

2. In the General Properties area of the Properties tab, click Edit.

3. Make sure the operating mode of the repository service is set to Exclusive.

4. Click OK.

5. Choose Actions, and then click Delete Contents.

6. In the Delete contents for <repository name> dialog, enter the repository username and password, and then click OK.

5.10.7 Upgrading the Data Warehouse Schema From Version 7.9.6.2 to 7.9.6.3 and Migrating Data

Perform the procedures in this section to upgrade from Oracle BI Applications release 7.9.6.2 to 7.9.6.3.

This section contains the following procedures:

- Section 5.10.7.1, "Upgrading the Data Warehouse Schema to Version 7.9.6.3"

- Section 5.10.7.2, "Migrating Data Into the Upgraded Data Warehouse"

- Section 5.10.7.3, "Verifying the Data Migrated Successfully"

5.10.7.1 Upgrading the Data Warehouse Schema to Version 7.9.6.3

Follow this procedure to upgrade the data warehouse schema to version 7.9.6.3.

To upgrade the data warehouse schema to version 7.9.6.3:

1. Generate the scripts to drop and create query indexes. For instructions, see Section B.4, "Generating Scripts to Drop and Create Query Indexes for Upgrading to Release 7.9.6.3."

2. Run the script to drop query indexes. For instructions, see Section B.5, "Running the Scripts to Drop and Create Query Indexes for Upgrading to Release 7.9.6.3."
Note: You must drop the query indexes before running the scripts to upgrade the schema.

3. If you are using a SQL Server database, run the 7963_UPGRADE_PRE_UPG_CTL_SCRIPT.sql file. This file is located in OracleBI\dwrep\Upgrade\DbScripts\SQLServer.

4. Run the UPGRADE_7963.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

5. Run the 7963_UPGRADE_PRE_CTL_SCRIPT.sql. This file is located in the folder OracleBI\dwrep\Upgrade\DbScripts\<database type>.

6. Run the DDL_7963.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files.".

5.10.7.2 Migrating Data Into the Upgraded Data Warehouse

Follow this procedure to migrate data into the upgraded data warehouse.

To migrate data into the upgraded data warehouse:

1. Run the 7963_UPGRADE_PRE_DIMENSION_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

2. Run the 7963_UPGRADE_DROP_ETLINDICES.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

3. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade repository. For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Upgrade Informatica Repository."

4. Configure the Informatica parameter file 7963_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt."

5. If you are using Siebel Industry Applications, you need to set an additional parameter in 7963_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt for Siebel Industry Applications Source Systems."

6. In Informatica Workflow Manager, navigate to the folder UPGRADE_7962_to_7963_SBL and execute the first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

7. Upgrade geography-related attributes if necessary for your environment:

1. Determine whether a geography-related upgrade is necessary by executing the following query:

SELECT COUNT(1) as row_count,'0' as X_CUSTOM FROM W_GEO_D_7963 WHERE COUNTRY LIKE '% 'OR COUNTRY LIKE ' %'OR STATE_PROV LIKE '% 'OR STATE_PROV LIKE ' %'OR CITY LIKE '% 'OR CITY LIKE ' %'OR ZIPCODE LIKE '% 'OR ZIPCODE LIKE ' %'

2. If the query returns a count greater than zero, run the 7963_UPGRADE_POST_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.
If the query returns a count of zero, you do not need to run the 7963_UPGRADE_POST_SCRIPT.sql script.

8. Run the 7963_UPGRADE_CREATE_ETLINDICES.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

9. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep). For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Base Informatica Repository."

10. Run the createQueryIndices.sql script. For instructions, see Section B.5, "Running the Scripts to Drop and Create Query Indexes for Upgrading to Release 7.9.6.3."

5.10.7.3 Verifying the Data Migrated Successfully

Follow this procedure to verify that the data was migrated successfully into the upgraded data warehouse.

To verify the data migrated successfully:

1. Validate the data in the upgraded data warehouse.

2. Check whether any of the Informatica mapping log files stored in the <INFA_HOME>\server\infa_shared\Sesslogs directory indicates errors or failures.

3. Check whether the following scripts that you ran in the SQL client of the database failed or errored out while executing:
7963_UPGRADE_PRE_CTL_SCRIPT.sql

7963_UPGRADE_PRE_DIMENSION.sql

7963_UPGRADE_DROP_ETLINDICES.sql

7963_UPGRADE CREATE_ETLINDICES.sql

dropQueryIndices.sql

createQueryIndices.sql

4. Check the log files for the ddl_7963.ctl and Upgrade_7963.ctl scripts, which 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.

Note:

Ignore any error messages that indicate tables or indexes could not be dropped from the database. These error messages are displayed when the specified objects do not exist in the database. This can occur because each source system container holds a subset of all data warehouse tables

5. If the data migration was successful, drop the tables that were created during the upgrade process, such as W_xxxx_x_79x, LKP_xxxx_x and 79x_xxxx_TMP.
This step frees the space occupied by these backup tables.

6. Once the data migration steps above are complete, you can delete the Upgrade repository to avoid any accidental use or confusion.

1. In the Informatica Administrator, select the Upgrade repository service.

2. In the General Properties area of the Properties tab, click Edit.

3. Make sure the operating mode of the repository service is set to Exclusive.

4. Click OK.

5. Choose Actions, and then click Delete Contents.

6. In the Delete contents for <repository name> dialog, enter the repository username and password, and then click OK.

5.10.8 Upgrading the Data Warehouse Schema From Version 7.9.6.3 to 7.9.6.4 and Migrating Data

Perform the procedures in this section to upgrade from Oracle BI Applications release 7.9.6.3 to 7.9.6.4.

This section contains the following procedures:

- Section 5.10.8.1, "Upgrading the Data Warehouse Schema to Version 7.9.6.4"

- Section 5.10.8.2, "Migrating Data into the Upgraded Data Warehouse"

- Section 5.10.8.3, "Verifying the Data Migrated Successfully"

5.10.8.1 Upgrading the Data Warehouse Schema to Version 7.9.6.4

Follow this procedure to upgrade the data warehouse schema to version 7.9.6.4.

To upgrade the data warehouse schema to version 7.9.6.4:

1. If you are using a DB2 database, run siebproc.sql. This file is located in OracleBI\dwrep\siebproc\db2udb.

2. Generate the scripts to drop and create query indexes. For instructions, see Section B.6, "Generating Scripts to Drop and Create Query and ETL Indexes for Upgrading to Release 7.9.6.4."

3. Run the script to drop query indexes. For instructions, see Section B.7, "Running the Scripts to Drop and Create Query Indexes for Upgrading to Release 7.9.6.4."
Note: You must drop the query indexes before running the scripts to upgrade the schema.

4. If you are using a SQL Server database, run the 7964_UPGRADE_PRE_UPG_CTL_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\SQLServer.

5. Run the UPGRADE_7964.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

6. Run the 7964_UPGRADE_PRE_CTL_SCRIPT.sql script. This file is located in the folder OracleBI\dwrep\Upgrade\DbScripts\<database type>.

7. Run the DDL_7964.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

5.10.8.2 Migrating Data into the Upgraded Data Warehouse

Follow this procedure to migrate data into the upgraded data warehouse.

To migrate data into the upgraded data warehouse:

1. Run the 7964_UPGRADE_PRE_DIMENSION_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

2. Run the script to drop ETL indexes. For instructions, see Section B.8, "Running the Scripts to Drop and Create ETL Indexes for Upgrading to Release 7.9.6.4."

3. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade repository. For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Upgrade Informatica Repository."

4. Configure the Informatica parameter file 7964_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7964_UPG_PARAMS.txt."

5. In Informatica Workflow Manager, navigate to the folder UPGRADE_7963_to_7964_SBL and execute the first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

6. Run the 7964_UPGRADE_POST_SCRIPT.sql. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

7. Run the script to create ETL indexes. For instructions, see Section B.8, "Running the Scripts to Drop and Create ETL Indexes for Upgrading to Release 7.9.6.4."

8. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep). For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Base Informatica Repository."

5.10.8.3 Verifying the Data Migrated Successfully

Follow this procedure to verify that the data was migrated successfully into the upgraded data warehouse.

To verify the data migrated successfully:

1. Validate the data in the upgraded data warehouse.

2. Check whether any of the Informatica mapping log files stored in the <INFA_HOME>\server\infa_shared\Sesslogs directory indicates errors or failures.

3. Check whether the following scripts that you ran in the SQL client of the database failed or errored out while executing:
7964_UPGRADE_PRE_CTL_SCRIPT.sql

7964_UPGRADE_PRE_DIMENSION.sql

dropEtlIndices.sql

createEtlIndices.sql

dropQueryIndices.sql

createQueryIndices.sql

4. Check the log files for the ddl_7964.ctl and Upgrade_7964.ctl scripts, which 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.

Note:

Ignore any error messages that indicate tables or indexes could not be dropped from the database. These error messages are displayed when the specified objects do not exist in the database. This can occur because each source system container holds a subset of all data warehouse tables

5. If the data migration was successful, drop the tables that were created during the upgrade process, such as W_xxxx_x_79x, LKP_xxxx_x and 79x_xxxx_TMP.
This step frees the space occupied by these backup tables.

6. Once the data migration steps above are complete, you can delete the Upgrade repository to avoid any accidental use or confusion.

1. In the Informatica Administrator, select the Upgrade repository service.

2. In the General Properties area of the Properties tab, click Edit.

3. Make sure the operating mode of the repository service is set to Exclusive.

4. Click OK.

5. Choose Actions, and then click Delete Contents.

6. In the Delete contents for <repository name> dialog, enter the repository username and password, and then click OK.

5.11 Upgrading the Data Warehouse Schema and Migrating Data for Teradata Databases

If your data warehouse database platform is Teradata, you can upgrade to Oracle Business Intelligence Applications version 7.9.6.4 from Oracle Business Intelligence Applications 7.9.x.

This section includes the following topics:

- Section 5.11.1, "Upgrading Oracle BI Applications From Version 7.9.0 to 7.9.6.4"

- Section 5.11.2, "Upgrading Oracle BI Applications From Version 7.9.4 to 7.9.6.4"

- Section 5.11.3, "Upgrading Oracle BI Applications From Version 7.9.5 to 7.9.6.4"

- Section 5.11.4, "Upgrading Oracle BI Applications From Version 7.9.5.1 to 7.9.6.4"

- Section 5.11.5, "Upgrading Oracle BI Applications From Version 7.9.6.1 to 7.9.6.4"

- Section 5.11.6, "Upgrading Oracle BI Applications From Version 7.9.6.2 to 7.9.6.4"

- Section 5.11.7, "Upgrading Oracle BI Applications From Version 7.9.6.3 to 7.9.6.4"

5.11.1 Upgrading Oracle BI Applications From Version 7.9.0 to 7.9.6.4

Follow this procedure to upgrade from Oracle Business Applications version 7.9.0 to version 7.9.6.4 if your data warehouse database platform is Teradata.

To upgrade the data warehouse schema and migrate data for a Teradata database:

1. Execute the following scripts:

- 795_UPGRADE_TMP_TABLES.sql

- 7951_UPGRADE_TMP_TABLES.sql

- 7961_UPGRADE_TMP_TABLES.sql

- 7962_UPGRADE_TMP_TABLES.sql

- 7963_UPGRADE_TMP_TABLES.sql

- 7964_UPGRADE_TMP_TABLES.sql

1. Open the SQL client for your database type.

2. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.

3. Open the <version>_UPGRADE_TMP_TABLES.sql file, and copy the contents into the SQL client.

4. Execute the script.

2. Edit and execute the 794_RENAME_AND_EXCEPTIONS.sql script.

1. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.

2. Open the 794_RENAME_AND_EXCEPTIONS.sql script.

3. Search for the following statements to locate columns with RENAME commands.
ALTER TABLE <Table_Name> RENAME <Column Name> TO <New Column Name>;

4. For all columns with RENAME commands, check to see whether any COLUMN STATISTICS are defined on them.

5. For all columns that have STATISTICS defined on them, back up the COLUMN STATISTICS definition and then drop them.

6. Execute the 794_RENAME_AND_EXCEPTIONS.sql script.

7. Recreate STATISTICS on any column on which they were dropped.

3. The teradata.missing.defaults.properties file contains global default column values for data warehouse tables with NOT NULL columns for which default values are not specified in DAC. You can change the default values specified in the teradata.missing.defaults.properties file to match your environment. The file is located in \bifoundation\dac\conf\sqlgen\sql\teradata.

4. Generate upgrade scripts from DAC.

1. Log into DAC.

2. From the menu bar, select Tools, then ETL Management, and then Configure.

3. In the Sources dialog box, select Teradata as the target data warehouse database platform, and select the appropriate source data warehouse database platform.
The Configuration tab of the Data Warehouse Configuration Wizard is active.

4. Select "Generate upgrade statements for Data Warehouse Tables," and click Next.
The Data Warehouse SQL tab is active.

5. Do the following:
- Select the appropriate physical data source name for the Teradata database.

- In the container field, enter a custom container name for which you want to generate upgrade scripts. Alternatively, leave the field blank to generate upgrade scripts for all containers.

The Data Warehouse Configuration Wizard generates the following files and stores them in \bifoundation\DAC\conf\sqlgen\sql\teradata:

upgrade-regular.sql. This file contains scripts that DAC has verified are necessary to upgrade the data warehouse schema. The scripts handle new or altered tables and columns. For example, they may increase the size of simple data types or change a column from null to not null.

upgrade-questionable.sql. This file contains scripts that DAC suggests may be required to upgrade the data warehouse schema. These scripts are intended to be an aid in determining upgrade requirements and must be reviewed by a Teradata DBA and corrected if necessary.

upgradedwtables_sql.log. This file is the log file that corresponds to the upgrade-regular.sql file. It is for information purposes only.

upgrade-issues.log. This file is the log file that corresponds to the file upgrade-questionable.sql. It is for information purposes only.

6. Open the upgrade-regular.sql and upgrade-questionable.sql files, and search for the following statement to locate columns that have been added or changed.
ALTER TABLE <Table Name> ADD <Column Name><attributes>;

7. For all columns with the ADD command, check to see whether any columns exist already, and if they do, check whether they have STATISTICS defined on them.

8. For all columns that have STATISTICS defined on them, back up the column definition and then drop the STATISTICS.

9. Execute the scripts in the upgrade-regular.sql file.

10. Review the scripts in the upgrade-questionable.sql file. Edit the scripts as needed, and execute them.

11. Recreate STATISTICS on any column on which they were dropped.

5. Execute the following scripts:

- 795_UPDATE_DEFAULTS.sql

- 7951_UPDATE_DEFAULTS.sql

- 7961_UPDATE_DEFAULTS.sql

- 7962_UPDATE_DEFAULTS.sql

- 7963_UPDATE_DEFAULTS.sql

- 7964_UPDATE_DEFAULTS.sql

6. Execute the 795_Backup Tables.sql script.

7. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

8. Configure the Informatica parameter file 795_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 795_UPG_PARAMS.txt."

9. If you upgraded your transactional database to Siebel Applications 8.x or 8.1.1, run the workflows to migrate your data into the upgraded data warehouse.

1. In Informatica Workflow Manager, navigate to the folder UPGRADE_790_TO_791_SBL80UPG.

2. Run the following workflows in the order specified:
UPGRADE_DIMENSIONS

UPGRADE_FACTS

10. In Informatica Workflow Manager, navigate to the folder UPGRADE_794_to_795_SBL and execute the UPGRADE_DIMENSIONS workflow.

11. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

12. Execute the 7951_Backup Tables.sql script.

13. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade repository.

14. Configure the Informatica parameter file 7951_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7951_UPG_PARAMS.txt."

15. In Informatica Workflow Manager, navigate to the folder UPGRADE_795_to_7951_SBL and execute the UPGRADE_DIMENSIONS workflow.

16. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

17. Execute the 796_Backup Tables.sql script.

18. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

19. Configure the Informatica parameter file 796_UPG_PARAMS.txt file. For instructions, see Appendix A, "Setting Parameters in 796_UPG_PARAMS.txt."

20. Configure parameters specific to Siebel source systems. For instructions, see Appendix A, "Setting Parameters in 796_UPG_PARAMS.txt for Siebel Source Systems."

21. Back up and truncate the table W_POSITION_DH.

22. In Informatica Workflow Manager, navigate to the folder UPGRADE_7951_to_796_SBL and execute the following workflows in the order specified:

- UPGRADE_DIMENSIONS

- UPGRADE_FACTS

- RESET_DAC_REFRESH_DATES

23. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

24. Execute the 7961_Backup_Tables.sql script.

25. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

26. Configure the Informatica parameter file 7961_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7961_UPG_PARAMS.txt."

27. In Informatica Workflow Manager, navigate to the folder UPGRADE_796_to_7961_SBL and execute the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

28. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

29. Execute the 7962_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

30. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

31. Configure the Informatica parameter file 7962_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7962_UPG_PARAMS.txt."

32. In Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_SBL and execute the UPGRADE_DIMENSIONS workflow.

33. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

34. Execute the 7963_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

35. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

36. Configure the Informatica parameter file 7963_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt."

37. If you are using Siebel Industry Applications, you need to set an additional parameter in 7963_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt for Siebel Industry Applications Source Systems."

38. In Informatica Workflow Manager, navigate to the folder UPGRADE_7962_to_7963_SBL and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.

39. Upgrade geography-related attributes if necessary for your environment:

1. Determine whether a geography-related upgrade is necessary by executing the following query:

SELECT COUNT(1) as row_count,'0' as X_CUSTOM FROM W_GEO_D_7963 WHERE COUNTRY LIKE '% 'OR COUNTRY LIKE ' %'OR STATE_PROV LIKE '% 'OR STATE_PROV LIKE ' %'OR CITY LIKE '% 'OR CITY LIKE ' %'OR ZIPCODE LIKE '% 'OR ZIPCODE LIKE ' %'

2. If the query returns a count greater than zero, run the 7963_UPGRADE_POST_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.
If the query returns a count of zero, you do not need to run the 7963_UPGRADE_POST_SCRIPT.sql script.

40. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

41. Execute the 7964_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

42. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

43. Configure the Informatica parameter file 7964_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7964_UPG_PARAMS.txt."

44. In Informatica Workflow Manager, navigate to the folder UPGRADE_7963_to_7964_SBL and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.

45. Run the 7964_UPGRADE_POST_SCRIPT.sql. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

46. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

47. Once the data migration steps above are complete, you can delete the Upgrade repository to avoid any accidental use or confusion.

1. In the Informatica Administrator, select the Upgrade repository service.

2. In the General Properties area of the Properties tab, click Edit.

3. Make sure the operating mode of the repository service is set to Exclusive.

4. Click OK.

5. Choose Actions, and then click Delete Contents.

6. In the Delete contents for <repository name> dialog, enter the repository username and password, and then click OK.

5.11.2 Upgrading Oracle BI Applications From Version 7.9.4 to 7.9.6.4

Follow this procedure to upgrade from Oracle Business Applications version 7.9.4 to version 7.9.6.4 if your data warehouse database platform is Teradata.

To upgrade the data warehouse schema and migrate data for a Teradata database:

1. Execute the following scripts:

- 795_UPGRADE_TMP_TABLES.sql

- 7951_UPGRADE_TMP_TABLES.sql

- 7961_UPGRADE_TMP_TABLES.sql

- 7962_UPGRADE_TMP_TABLES.sql

- 7963_UPGRADE_TMP_TABLES.sql

- 7964_UPGRADE_TMP_TABLES.sql

1. Open the SQL client for your database type.

2. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.

3. Open the <version>_UPGRADE_TMP_TABLES.sql file, and copy the contents into the SQL client.

4. Execute the script.

2. Edit and execute the 795_RENAME_AND_EXCEPTIONS.sql script.

1. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.

2. Open the 795_RENAME_AND_EXCEPTIONS.sql script.

3. Search for the following statements to locate columns with RENAME commands.
ALTER TABLE <Table_Name> RENAME <Column Name> TO <New Column Name>;

4. For all columns with RENAME commands, check to see whether any COLUMN STATISTICS are defined on them.

5. For all columns that have STATISTICS defined on them, back up the COLUMN STATISTICS definition and then drop them.

6. Execute the 795_RENAME_AND_EXCEPTIONS.sql script.

7. Recreate STATISTICS on any column on which they were dropped.

3. The teradata.missing.defaults.properties file contains global default column values for data warehouse tables with NOT NULL columns for which default values are not specified in DAC. You can change the default values specified in the teradata.missing.defaults.properties file to match your environment. The file is located in \bifoundation\dac\conf\sqlgen\sql\teradata.

4. Generate upgrade scripts from DAC.

1. Log into DAC.

2. From the menu bar, select Tools, then ETL Management, and then Configure.

3. In the Sources dialog box, select Teradata as the target data warehouse database platform, and select the appropriate source data warehouse database platform.
The Configuration tab of the Data Warehouse Configuration Wizard is active.

4. Select "Generate upgrade statements for Data Warehouse Tables," and click Next.
The Data Warehouse SQL tab is active.

5. Do the following:
- Select the appropriate physical data source name for the Teradata database.

- In the container field, enter a custom container name for which you want to generate upgrade scripts. Alternatively, leave the field blank to generate upgrade scripts for all containers.

The Data Warehouse Configuration Wizard generates the following files and stores them in \bifoundation\DAC\conf\sqlgen\sql\teradata:

upgrade-regular.sql. This file contains scripts that DAC has verified are necessary to upgrade the data warehouse schema. The scripts handle new or altered tables and columns. For example, they may increase the size of simple data types or change a column from null to not null.

upgrade-questionable.sql. This file contains scripts that DAC suggests may be required to upgrade the data warehouse schema. These scripts are intended to be an aid in determining upgrade requirements and must be reviewed by a Teradata DBA and corrected if necessary.

upgradedwtables_sql.log. This file is the log file that corresponds to the upgrade-regular.sql file. It is for information purposes only.

upgrade-issues.log. This file is the log file that corresponds to the file upgrade-questionable.sql. It is for information purposes only.

6. Open the upgrade-regular.sql and upgrade-questionable.sql files, and search for the following statement to locate columns that have been added or changed.
ALTER TABLE <Table Name> ADD <Column Name><attributes>;

7. For all columns with the ADD command, check to see whether any columns exist already, and if they do, check whether they have STATISTICS defined on them.

8. For all columns that have STATISTICS defined on them, back up the column definition and then drop the STATISTICS.

9. Execute the scripts in the upgrade-regular.sql file.

10. Review the scripts in the upgrade-questionable.sql file. Edit the scripts as needed, and execute them.

11. Recreate STATISTICS on any column on which they were dropped.

5. Execute the following scripts:

- 795_UPDATE_DEFAULTS.sql

- 7951_UPDATE_DEFAULTS.sql

- 7961_UPDATE_DEFAULTS.sql

- 7962_UPDATE_DEFAULTS.sql

- 7963_UPDATE_DEFAULTS.sql

- 7964_UPDATE_DEFAULTS.sql

6. Execute the 795_Backup Tables.sql script.

7. Configure the Informatica parameter file 795_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 795_UPG_PARAMS.txt."

8. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade repository. For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Upgrade Informatica Repository."

9. If you upgraded your transactional database to Siebel Applications 8.x or 8.1.1, run the workflows to migrate your data into the upgraded data warehouse.

1. In Informatica Workflow Manager, navigate to the folder UPGRADE_790_TO_791_SBL80UPG.

2. Run the following workflows in the order specified:
UPGRADE_DIMENSIONS

UPGRADE_FACTS

10. In Informatica Workflow Manager, navigate to the folder UPGRADE_794_to_795_SBL and execute the UPGRADE_DIMENSIONS workflow.

11. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

12. Execute the 7951_Backup Tables.sql script.

13. Configure the Informatica parameter file 7951_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7951_UPG_PARAMS.txt."

14. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

15. In Informatica Workflow Manager, navigate to the folder UPGRADE_795_to_7951_SBL and execute the UPGRADE_DIMENSIONS workflow.

16. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

17. Execute the 796_Backup Tables.sql script.

18. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

19. Configure the Informatica parameter file 796_UPG_PARAMS.txt file. For instructions, see Appendix A, "Setting Parameters in 796_UPG_PARAMS.txt."

20. Configure parameters specific to Siebel source systems. For instructions, see Appendix A, "Setting Parameters in 796_UPG_PARAMS.txt for Siebel Source Systems."

21. Back up and truncate the table W_POSITION_DH.

22. In Informatica Workflow Manager, navigate to the folder UPGRADE_7951_to_796_SBL and execute the following workflows in the order specified:

- UPGRADE_DIMENSIONS

- UPGRADE_FACTS

- RESET_DAC_REFRESH_DATES

23. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

24. Execute the 7961_Backup Tables.sql script.

25. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

26. Configure the Informatica parameter file 7961_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7961_UPG_PARAMS.txt."

27. In Informatica Workflow Manager, navigate to the folder UPGRADE_796_to_7961_SBL and execute the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

28. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

29. Execute the 7962_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

30. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

31. Configure the Informatica parameter file 7962_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7962_UPG_PARAMS.txt."

32. In Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_SBL and execute the UPGRADE_DIMENSIONS workflow.

33. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

34. Execute the 7963_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

35. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

36. Configure the Informatica parameter file 7963_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt."

37. If you are using Siebel Industry Applications, you need to set an additional parameter in 7963_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt for Siebel Industry Applications Source Systems."

38. In Informatica Workflow Manager, navigate to the folder UPGRADE_7962_to_7963_SBL and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.

39. Upgrade geography-related attributes if necessary for your environment:

1. Determine whether a geography-related upgrade is necessary by executing the following query:

SELECT COUNT(1) as row_count,'0' as X_CUSTOM FROM W_GEO_D_7963 WHERE COUNTRY LIKE '% 'OR COUNTRY LIKE ' %'OR STATE_PROV LIKE '% 'OR STATE_PROV LIKE ' %'OR CITY LIKE '% 'OR CITY LIKE ' %'OR ZIPCODE LIKE '% 'OR ZIPCODE LIKE ' %'

2. If the query returns a count greater than zero, run the 7963_UPGRADE_POST_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.
If the query returns a count of zero, you do not need to run the 7963_UPGRADE_POST_SCRIPT.sql script.

40. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

41. Execute the 7964_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

42. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

43. Configure the Informatica parameter file 7964_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7964_UPG_PARAMS.txt."

44. In Informatica Workflow Manager, navigate to the folder UPGRADE_7963_to_7964_SBL and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.

45. Run the 7964_UPGRADE_POST_SCRIPT.sql. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

46. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

47. Once the data migration steps above are complete, you can delete the Upgrade repository to avoid any accidental use or confusion.

1. In the Informatica Administrator, select the Upgrade repository service.

2. In the General Properties area of the Properties tab, click Edit.

3. Make sure the operating mode of the repository service is set to Exclusive.

4. Click OK.

5. Choose Actions, and then click Delete Contents.

6. In the Delete contents for <repository name> dialog, enter the repository username and password, and then click OK.

5.11.3 Upgrading Oracle BI Applications From Version 7.9.5 to 7.9.6.4

Follow this procedure to upgrade from Oracle Business Applications version 7.9.5 to version 7.9.6.4 if your data warehouse database platform is Teradata.

To upgrade the data warehouse schema and migrate data for a Teradata database:

1. Execute the following scripts:

- 7951_UPGRADE_TMP_TABLES.sql

- 7961_UPGRADE_TMP_TABLES.sql

- 7962_UPGRADE_TMP_TABLES.sql

- 7963_UPGRADE_TMP_TABLES.sql

- 7964_UPGRADE_TMP_TABLES.sql

1. Open the SQL client for your database type.

2. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.

3. Open the <version>_UPGRADE_TMP_TABLES.sql file, and copy the contents into the SQL client.

4. Execute the script.

2. Edit and execute the 7951_RENAME_AND_EXCEPTIONS.sql script.

1. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.

2. Open the 7951_RENAME_AND_EXCEPTIONS.sql script.

3. Search for the following statements to locate columns with RENAME commands.
ALTER TABLE <Table_Name> RENAME <Column Name> TO <New Column Name>;

4. For all columns with RENAME commands, check to see whether any COLUMN STATISTICS are defined on them.

5. For all columns that have STATISTICS defined on them, back up the COLUMN STATISTICS definition and then drop them.

6. Execute the 7951_RENAME_AND_EXCEPTIONS.sql script.

7. Recreate STATISTICS on any column on which they were dropped.

3. The teradata.missing.defaults.properties file contains global default column values for data warehouse tables with NOT NULL columns for which default values are not specified in DAC. You can change the default values specified in the teradata.missing.defaults.properties file to match your environment. The file is located in \bifoundation\dac\conf\sqlgen\sql\teradata.

4. Generate upgrade scripts from DAC.

1. Log into DAC.

2. From the menu bar, select Tools, then ETL Management, and then Configure.

3. In the Sources dialog box, select Teradata as the target data warehouse database platform, and select the appropriate source data warehouse database platform.
The Configuration tab of the Data Warehouse Configuration Wizard is active.

4. Select "Generate upgrade statements for Data Warehouse Tables," and click Next.
The Data Warehouse SQL tab is active.

5. Do the following:
- Select the appropriate physical data source name for the Teradata database.

- In the container field, enter a custom container name for which you want to generate upgrade scripts. Alternatively, leave the field blank to generate upgrade scripts for all containers.

The Data Warehouse Configuration Wizard generates the following files and stores them in \bifoundation\DAC\conf\sqlgen\sql\teradata:

upgrade-regular.sql. This file contains scripts that DAC has verified are necessary to upgrade the data warehouse schema. The scripts handle new or altered tables and columns. For example, they may increase the size of simple data types or change a column from null to not null.

upgrade-questionable.sql. This file contains scripts that DAC suggests may be required to upgrade the data warehouse schema. These scripts are intended to be an aid in determining upgrade requirements and must be reviewed by a Teradata DBA and corrected if necessary.

upgradedwtables_sql.log. This file is the log file that corresponds to the upgrade-regular.sql file. It is for information purposes only.

upgrade-issues.log. This file is the log file that corresponds to the file upgrade-questionable.sql. It is for information purposes only.

6. Open the upgrade-regular.sql and upgrade-questionable.sql files, and search for the following statement to locate columns that have been added or changed.
ALTER TABLE <Table Name> ADD <Column Name><attributes>;

7. For all columns with the ADD command, check to see whether any columns exist already, and if they do, check whether they have STATISTICS defined on them.

8. For all columns that have STATISTICS defined on them, back up the column definition and then drop the STATISTICS.

9. Execute the scripts in the upgrade-regular.sql file.

10. Review the scripts in the upgrade-questionable.sql file. Edit the scripts as needed, and execute them.

11. Recreate STATISTICS on any column on which they were dropped.

5. Execute the following scripts:

- 7951_UPDATE_DEFAULTS.sql

- 7961_UPDATE_DEFAULTS.sql

- 7962_UPDATE_DEFAULTS.sql

- 7963_UPDATE_DEFAULTS.sql

- 7964_UPDATE_DEFAULTS.sql

6. Execute the 7951_Backup Tables.sql script.

7. Configure the Informatica parameter file 7951_UPG_PARAMStxt. For instructions, see Appendix A, "Setting Parameters in 7951_UPG_PARAMS.txt."

8. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

9. If you upgraded your transactional database to Siebel Applications 8.x or 8.1.1, run the workflows to migrate your data into the upgraded data warehouse.

1. In Informatica Workflow Manager, navigate to the folder UPGRADE_790_TO_791_SBL80UPG.

2. Run the following workflows in the order specified:
UPGRADE_DIMENSIONS

UPGRADE_FACTS

10. In Informatica Workflow Manager, navigate to the folder UPGRADE_795_to_7951_SBL and execute the UPGRADE_DIMENSIONS workflow.

11. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

12. Execute the 796_Backup Tables.sql script.

13. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

14. Configure the Informatica parameter file 796_UPG_PARAMS.txt file. For instructions, see Appendix A, "Setting Parameters in 796_UPG_PARAMS.txt."

15. Configure parameters specific to Siebel source systems. For instructions, see Appendix A, "Setting Parameters in 796_UPG_PARAMS.txt for Siebel Source Systems."

16. Back up and truncate the table W_POSITION_DH.

17. In Informatica Workflow Manager, navigate to the folder UPGRADE_7951_to_796_SBL and execute the following workflows in the order specified:

- UPGRADE_DIMENSIONS

- UPGRADE_FACTS

- RESET_DAC_REFRESH_DATES

18. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

19. Execute the 7961_Backup Tables.sql script.

20. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

21. Configure the Informatica parameter file 7961_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7961_UPG_PARAMS.txt."

22. Back up and truncate the table W_POSITION_DH.

23. In Informatica Workflow Manager, navigate to the folder UPGRADE_796_to_7961_SBL and execute the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

24. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

25. Execute the 7962_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

26. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

27. Configure the Informatica parameter file 7962_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7962_UPG_PARAMS.txt."

28. In Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_SBL and execute the UPGRADE_DIMENSIONS workflow.

29. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

30. Execute the 7963_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

31. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

32. Configure the Informatica parameter file 7963_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt."

33. If you are using Siebel Industry Applications, you need to set an additional parameter in 7963_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt for Siebel Industry Applications Source Systems."

34. In Informatica Workflow Manager, navigate to the folder UPGRADE_7962_to_7963_SBL and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.

35. Upgrade geography-related attributes if necessary for your environment:

1. Determine whether a geography-related upgrade is necessary by executing the following query:

SELECT COUNT(1) as row_count,'0' as X_CUSTOM FROM W_GEO_D_7963 WHERE COUNTRY LIKE '% 'OR COUNTRY LIKE ' %'OR STATE_PROV LIKE '% 'OR STATE_PROV LIKE ' %'OR CITY LIKE '% 'OR CITY LIKE ' %'OR ZIPCODE LIKE '% 'OR ZIPCODE LIKE ' %'

2. If the query returns a count greater than zero, run the 7963_UPGRADE_POST_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.
If the query returns a count of zero, you do not need to run the 7963_UPGRADE_POST_SCRIPT.sql script.

36. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

37. Execute the 7964_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

38. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

39. Configure the Informatica parameter file 7964_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7964_UPG_PARAMS.txt."

40. In Informatica Workflow Manager, navigate to the folder UPGRADE_7963_to_7964_SBL and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.

41. Run the 7964_UPGRADE_POST_SCRIPT.sql. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

42. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

43. Once the data migration steps above are complete, you can delete the Upgrade repository to avoid any accidental use or confusion.

1. In the Informatica Administrator, select the Upgrade repository service.

2. In the General Properties area of the Properties tab, click Edit.

3. Make sure the operating mode of the repository service is set to Exclusive.

4. Click OK.

5. Choose Actions, and then click Delete Contents.

6. In the Delete contents for <repository name> dialog, enter the repository username and password, and then click OK.

5.11.4 Upgrading Oracle BI Applications From Version 7.9.5.1 to 7.9.6.4

Follow this procedure to upgrade from Oracle Business Applications version 7.9.5.1 to version 7.9.6.4 if your data warehouse database platform is Teradata.

To upgrade the data warehouse schema and migrate data for a Teradata database:

1. Execute the following scripts:

- 7961_UPGRADE_TMP_TABLES.sql

- 7962_UPGRADE_TMP_TABLES.sql

- 7963_UPGRADE_TMP_TABLES.sql

- 7964_UPGRADE_TMP_TABLES.sql

1. Open the SQL client for your database type.

2. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.

3. Open the <version>_UPGRADE_TMP_TABLES.sql file, and copy the contents into the SQL client.

4. Execute the script.

2. Edit and execute the 7961_RENAME_AND_EXCEPTIONS.sql script.

1. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.

2. Open the 7961_RENAME_AND_EXCEPTIONS.sql script.

3. Search for the following statements to locate columns with RENAME commands.
ALTER TABLE <Table_Name> RENAME <Column Name> TO <New Column Name>;

4. For all columns with RENAME commands, check to see whether any COLUMN STATISTICS are defined on them.

5. For all columns that have STATISTICS defined on them, back up the COLUMN STATISTICS definition and then drop them.

6. Execute the 7961_RENAME_AND_EXCEPTIONS.sql script.

7. Recreate STATISTICS on any column on which they were dropped.

3. The teradata.missing.defaults.properties file contains global default column values for data warehouse tables with NOT NULL columns for which default values are not specified in DAC. You can change the default values specified in the teradata.missing.defaults.properties file to match your environment. The file is located in \bifoundation\dac\conf\sqlgen\sql\teradata.

4. Generate upgrade scripts from DAC.

1. Log into DAC.

2. From the menu bar, select Tools, then ETL Management, and then Configure.

3. In the Sources dialog box, select Teradata as the target data warehouse database platform, and select the appropriate source data warehouse database platform.
The Configuration tab of the Data Warehouse Configuration Wizard is active.

4. Select "Generate upgrade statements for Data Warehouse Tables," and click Next.
The Data Warehouse SQL tab is active.

5. Do the following:
- Select the appropriate physical data source name for the Teradata database.

- In the container field, enter a custom container name for which you want to generate upgrade scripts. Alternatively, leave the field blank to generate upgrade scripts for all containers.

The Data Warehouse Configuration Wizard generates the following files and stores them in \bifoundation\DAC\conf\sqlgen\sql\teradata:

upgrade-regular.sql. This file contains scripts that DAC has verified are necessary to upgrade the data warehouse schema. The scripts handle new or altered tables and columns. For example, they may increase the size of simple data types or change a column from null to not null.

upgrade-questionable.sql. This file contains scripts that DAC suggests may be required to upgrade the data warehouse schema. These scripts are intended to be an aid in determining upgrade requirements and must be reviewed by a Teradata DBA and corrected if necessary.

upgradedwtables_sql.log. This file is the log file that corresponds to the upgrade-regular.sql file. It is for information purposes only.

upgrade-issues.log. This file is the log file that corresponds to the file upgrade-questionable.sql. It is for information purposes only.

6. Open the upgrade-regular.sql and upgrade-questionable.sql files, and search for the following statement to locate columns that have been added or changed.
ALTER TABLE <Table Name> ADD <Column Name><attributes>;

7. For all columns with the ADD command, check to see whether any columns exist already, and if they do, check whether they have STATISTICS defined on them.

8. For all columns that have STATISTICS defined on them, back up the column definition and then drop the STATISTICS.

9. Execute the scripts in the upgrade-regular.sql file.

10. Review the scripts in the upgrade-questionable.sql file. Edit the scripts as needed, and execute them.

11. Recreate STATISTICS on any column on which they were dropped.

5. Execute the following scripts:

- 7961_UPDATE_DEFAULTS.sql

- 7962_UPDATE_DEFAULTS.sql

- 7963_UPDATE_DEFAULTS.sql

- 7964_UPDATE_DEFAULTS.sql

6. Execute the 796_Backup Tables.sql script.

7. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

8. Configure the Informatica parameter file 796_UPG_PARAMS.txt file. For instructions, see Appendix A, "Setting Parameters in 796_UPG_PARAMS.txt."

9. Configure parameters specific to Siebel source systems. For instructions, see Appendix A, "Setting Parameters in 796_UPG_PARAMS.txt for Siebel Source Systems."

10. If you upgraded your transactional database to Siebel Applications 8.x or 8.1.1, run the workflows to migrate your data into the upgraded data warehouse.

1. In Informatica Workflow Manager, navigate to the folder UPGRADE_790_TO_791_SBL80UPG.

2. Run the following workflows in the order specified:
UPGRADE_DIMENSIONS

UPGRADE_FACTS

11. Back up and truncate the table W_POSITION_DH.

12. In Informatica Workflow Manager, navigate to the folder UPGRADE_7951_to_796_SBL and execute the following workflows in the order specified:

- UPGRADE_DIMENSIONS

- UPGRADE_FACTS

- RESET_DAC_REFRESH_DATES

13. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

14. Execute the 7961_Backup Tables.sql script.

15. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

16. Configure the Informatica parameter file 7961_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7961_UPG_PARAMS.txt."

17. In Informatica Workflow Manager, navigate to the folder UPGRADE_796_to_7961_SBL and execute the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

18. Execute the 7962_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

19. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

20. Configure the Informatica parameter file 7962_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7962_UPG_PARAMS.txt."

21. In Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_SBL and execute the UPGRADE_DIMENSIONS workflow.

22. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

23. Execute the 7963_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

24. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

25. Configure the Informatica parameter file 7963_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt."

26. If you are using Siebel Industry Applications, you need to set an additional parameter in 7963_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt for Siebel Industry Applications Source Systems."

27. In Informatica Workflow Manager, navigate to the folder UPGRADE_7962_to_7963_SBL and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.

28. Upgrade geography-related attributes if necessary for your environment:

1. Determine whether a geography-related upgrade is necessary by executing the following query:

SELECT COUNT(1) as row_count,'0' as X_CUSTOM FROM W_GEO_D_7963 WHERE COUNTRY LIKE '% 'OR COUNTRY LIKE ' %'OR STATE_PROV LIKE '% 'OR STATE_PROV LIKE ' %'OR CITY LIKE '% 'OR CITY LIKE ' %'OR ZIPCODE LIKE '% 'OR ZIPCODE LIKE ' %'

2. If the query returns a count greater than zero, run the 7963_UPGRADE_POST_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.
If the query returns a count of zero, you do not need to run the 7963_UPGRADE_POST_SCRIPT.sql script.

29. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

30. Execute the 7964_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

31. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

32. Configure the Informatica parameter file 7964_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7964_UPG_PARAMS.txt."

33. In Informatica Workflow Manager, navigate to the folder UPGRADE_7963_to_7964_SBL and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.

34. Run the 7964_UPGRADE_POST_SCRIPT.sql. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

35. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

36. Once the data migration steps above are complete, you can delete the Upgrade repository to avoid any accidental use or confusion.

1. In the Informatica Administrator, select the Upgrade repository service.

2. In the General Properties area of the Properties tab, click Edit.

3. Make sure the operating mode of the repository service is set to Exclusive.

4. Click OK.

5. Choose Actions, and then click Delete Contents.

6. In the Delete contents for <repository name> dialog, enter the repository username and password, and then click OK.

5.11.5 Upgrading Oracle BI Applications From Version 7.9.6.1 to 7.9.6.4

Follow this procedure to upgrade from Oracle Business Applications version 7.9.6.1 to version 7.9.6.4 if your data warehouse database platform is Teradata.

To upgrade the data warehouse schema and migrate data for a Teradata database:

1. Execute the following scripts:

- 7962_UPGRDE_TMP_TABLES.sql

- 7963_UPGRADE_TMP_TABLES.sql

- 7964_UPGRADE_TMP_TABLES.sql

1. Open the SQL client for your database type.

2. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.

3. Open the <version>_UPGRADE_TMP_TABLES.sql file, and copy the contents into the SQL client.

4. Execute the script.

2. The teradata.missing.defaults.properties file contains global default column values for data warehouse tables with NOT NULL columns for which default values are not specified in DAC. You can change the default values specified in the teradata.missing.defaults.properties file to match your environment. The file is located in \bifoundation\dac\conf\sqlgen\sql\teradata.

3. Generate upgrade scripts from DAC.

1. Log into DAC.

2. From the menu bar, select Tools, then ETL Management, and then Configure.

3. In the Sources dialog box, select Teradata as the target data warehouse database platform, and select the appropriate source data warehouse database platform.
The Configuration tab of the Data Warehouse Configuration Wizard is active.

4. Select "Generate upgrade statements for Data Warehouse Tables," and click Next.
The Data Warehouse SQL tab is active.

5. Do the following:
- Select the appropriate physical data source name for the Teradata database.

- In the container field, enter a custom container name for which you want to generate upgrade scripts. Alternatively, leave the field blank to generate upgrade scripts for all containers.

The Data Warehouse Configuration Wizard generates the following files and stores them in \bifoundation\DAC\conf\sqlgen\sql\teradata:

upgrade-regular.sql. This file contains scripts that DAC has verified are necessary to upgrade the data warehouse schema. The scripts handle new or altered tables and columns. For example, they may increase the size of simple data types or change a column from null to not null.

upgrade-questionable.sql. This file contains scripts that DAC suggests may be required to upgrade the data warehouse schema. These scripts are intended to be an aid in determining upgrade requirements and must be reviewed by a Teradata DBA and corrected if necessary.

upgradedwtables_sql.log. This file is the log file that corresponds to the upgrade-regular.sql file. It is for information purposes only.

upgrade-issues.log. This file is the log file that corresponds to the file upgrade-questionable.sql. It is for information purposes only.

6. Open the upgrade-regular.sql and upgrade-questionable.sql files, and search for the following statement to locate columns that have been added or changed.
ALTER TABLE <Table Name> ADD <Column Name><attributes>;

7. For all columns with the ADD command, check to see whether any columns exist already, and if they do, check whether they have STATISTICS defined on them.

8. For all columns that have STATISTICS defined on them, back up the column definition and then drop the STATISTICS.

9. Execute the scripts in the upgrade-regular.sql file.

10. Review the scripts in the upgrade-questionable.sql file. Edit the scripts as needed, and execute them.

11. Recreate STATISTICS on any column on which they were dropped.

4. Execute the following scripts:

- 7962_UPDATE_DEFAULTS.sql

- 7963_UPDATE_DEFAULTS.sql

- 7964_UPDATE_DEFAULTS.sql

5. Execute the 7962_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

6. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

7. Configure the Informatica parameter file 7962_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7962_UPG_PARAMS.txt."

8. In Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_SBL and execute the UPGRADE_DIMENSIONS workflow.

9. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

10. Execute the 7963_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

11. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

12. Configure the Informatica parameter file 7963_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt."

13. If you are using Siebel Industry Applications, you need to set an additional parameter in 7963_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt for Siebel Industry Applications Source Systems."

14. In Informatica Workflow Manager, navigate to the folder UPGRADE_7962_to_7963_SBL and execute the UPGRADE_DIMENSIONS workflow.

15. Upgrade geography-related attributes if necessary for your environment:

1. Determine whether a geography-related upgrade is necessary by executing the following query:

SELECT COUNT(1) as row_count,'0' as X_CUSTOM FROM W_GEO_D_7963 WHERE COUNTRY LIKE '% 'OR COUNTRY LIKE ' %'OR STATE_PROV LIKE '% 'OR STATE_PROV LIKE ' %'OR CITY LIKE '% 'OR CITY LIKE ' %'OR ZIPCODE LIKE '% 'OR ZIPCODE LIKE ' %'

2. If the query returns a count greater than zero, run the 7963_UPGRADE_POST_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.
If the query returns a count of zero, you do not need to run the 7963_UPGRADE_POST_SCRIPT.sql script.

16. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

17. Execute the 7964_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

18. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

19. Configure the Informatica parameter file 7964_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7964_UPG_PARAMS.txt."

20. In Informatica Workflow Manager, navigate to the folder UPGRADE_7963_to_7964_SBL and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.

21. Run the 7964_UPGRADE_POST_SCRIPT.sql. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

22. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

23. Once the data migration steps above are complete, you can delete the Upgrade repository to avoid any accidental use or confusion.

1. In the Informatica Administrator, select the Upgrade repository service.

2. In the General Properties area of the Properties tab, click Edit.

3. Make sure the operating mode of the repository service is set to Exclusive.

4. Click OK.

5. Choose Actions, and then click Delete Contents.

6. In the Delete contents for <repository name> dialog, enter the repository username and password, and then click OK.

5.11.6 Upgrading Oracle BI Applications From Version 7.9.6.2 to 7.9.6.4

Follow this procedure to upgrade from Oracle Business Applications version 7.9.6.2 to version 7.9.6.4 if your data warehouse database platform is Teradata.

To upgrade the data warehouse schema and migrate data for a Teradata database:

1. Execute the following scripts:

- 7963_UPGRADE_TMP_TABLES.sql

- 7964_UPGRADE_TMP_TABLES.sql

1. Open the SQL client for your database type.

2. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.

3. Open the <version>_UPGRADE_TMP_TABLES.sql file, and copy the contents into the SQL client.

4. Execute the script.

2. The teradata.missing.defaults.properties file contains global default column values for data warehouse tables with NOT NULL columns for which default values are not specified in DAC. You can change the default values specified in the teradata.missing.defaults.properties file to match your environment. The file is located in \bifoundation\dac\conf\sqlgen\sql\teradata.

3. Generate upgrade scripts from DAC.

1. Log into DAC.

2. From the menu bar, select Tools, then ETL Management, and then Configure.

3. In the Sources dialog box, select Teradata as the target data warehouse database platform, and select the appropriate source data warehouse database platform.
The Configuration tab of the Data Warehouse Configuration Wizard is active.

4. Select "Generate upgrade statements for Data Warehouse Tables," and click Next.
The Data Warehouse SQL tab is active.

5. Do the following:
- Select the appropriate physical data source name for the Teradata database.

- In the container field, enter a custom container name for which you want to generate upgrade scripts. Alternatively, leave the field blank to generate upgrade scripts for all containers.

The Data Warehouse Configuration Wizard generates the following files and stores them in \bifoundation\DAC\conf\sqlgen\sql\teradata:

upgrade-regular.sql. This file contains scripts that DAC has verified are necessary to upgrade the data warehouse schema. The scripts handle new or altered tables and columns. For example, they may increase the size of simple data types or change a column from null to not null.

upgrade-questionable.sql. This file contains scripts that DAC suggests may be required to upgrade the data warehouse schema. These scripts are intended to be an aid in determining upgrade requirements and must be reviewed by a Teradata DBA and corrected if necessary.

upgradedwtables_sql.log. This file is the log file that corresponds to the upgrade-regular.sql file. It is for information purposes only.

upgrade-issues.log. This file is the log file that corresponds to the file upgrade-questionable.sql. It is for information purposes only.

6. Open the upgrade-regular.sql and upgrade-questionable.sql files, and search for the following statement to locate columns that have been added or changed.
ALTER TABLE <Table Name> ADD <Column Name><attributes>;

7. For all columns with the ADD command, check to see whether any columns exist already, and if they do, check whether they have STATISTICS defined on them.

8. For all columns that have STATISTICS defined on them, back up the column definition and then drop the STATISTICS.

9. Execute the scripts in the upgrade-regular.sql file.

10. Review the scripts in the upgrade-questionable.sql file. Edit the scripts as needed, and execute them.

11. Recreate STATISTICS on any column on which they were dropped.

4. Execute the 7963_UPDATE_DEFAULTS.sql script.

5. Execute the 7964_UPDATE_DEFAULTS.sql script.

6. Execute the 7963_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

7. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

8. Configure the Informatica parameter file 7963_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt."

9. If you are using Siebel Industry Applications, you need to set an additional parameter in 7963_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt for Siebel Industry Applications Source Systems."

10. In Informatica Workflow Manager, navigate to the folder UPGRADE_7962_to_7963_SBL and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

11. Upgrade geography-related attributes if necessary for your environment:

1. Determine whether a geography-related upgrade is necessary by executing the following query:

SELECT COUNT(1) as row_count,'0' as X_CUSTOM FROM W_GEO_D_7963 WHERE COUNTRY LIKE '% 'OR COUNTRY LIKE ' %'OR STATE_PROV LIKE '% 'OR STATE_PROV LIKE ' %'OR CITY LIKE '% 'OR CITY LIKE ' %'OR ZIPCODE LIKE '% 'OR ZIPCODE LIKE ' %'

2. If the query returns a count greater than zero, run the 7963_UPGRADE_POST_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.
If the query returns a count of zero, you do not need to run the 7963_UPGRADE_POST_SCRIPT.sql script.

12. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

13. Execute the 7964_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

14. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

15. Configure the Informatica parameter file 7964_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7964_UPG_PARAMS.txt."

16. In Informatica Workflow Manager, navigate to the folder UPGRADE_7963_to_7964_SBL and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.

17. Run the 7964_UPGRADE_POST_SCRIPT.sql. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

18. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

19. Once the data migration steps above are complete, you can delete the Upgrade repository to avoid any accidental use or confusion.

1. In the Informatica Administrator, select the Upgrade repository service.

2. In the General Properties area of the Properties tab, click Edit.

3. Make sure the operating mode of the repository service is set to Exclusive.

4. Click OK.

5. Choose Actions, and then click Delete Contents.

6. In the Delete contents for <repository name> dialog, enter the repository username and password, and then click OK.

5.11.7 Upgrading Oracle BI Applications From Version 7.9.6.3 to 7.9.6.4

Follow this procedure to upgrade from Oracle Business Applications version 7.9.6.3 to version 7.9.6.4 if your data warehouse database platform is Teradata.

To upgrade the data warehouse schema and migrate data for a Teradata database:

1. Execute the 7964_UPGRADE_TMP_TABLES.sql script.

1. Open the SQL client for your database type.

2. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.

3. Open the 7964_UPGRADE_TMP_TABLES.sql file, and copy the contents into the SQL client.

4. Execute the script.

2. The teradata.missing.defaults.properties file contains global default column values for data warehouse tables with NOT NULL columns for which default values are not specified in DAC. You can change the default values specified in the teradata.missing.defaults.properties file to match your environment. The file is located in \bifoundation\dac\conf\sqlgen\sql\teradata.

3. Generate upgrade scripts from DAC.

1. Log into DAC.

2. From the menu bar, select Tools, then ETL Management, and then Configure.

3. In the Sources dialog box, select Teradata as the target data warehouse database platform, and select the appropriate source data warehouse database platform.
The Configuration tab of the Data Warehouse Configuration Wizard is active.

4. Select "Generate upgrade statements for Data Warehouse Tables," and click Next.
The Data Warehouse SQL tab is active.

5. Do the following:
- Select the appropriate physical data source name for the Teradata database.

- In the container field, enter a custom container name for which you want to generate upgrade scripts. Alternatively, leave the field blank to generate upgrade scripts for all containers.

The Data Warehouse Configuration Wizard generates the following files and stores them in \bifoundation\DAC\conf\sqlgen\sql\teradata:

upgrade-regular.sql. This file contains scripts that DAC has verified are necessary to upgrade the data warehouse schema. The scripts handle new or altered tables and columns. For example, they may increase the size of simple data types or change a column from null to not null.

upgrade-questionable.sql. This file contains scripts that DAC suggests may be required to upgrade the data warehouse schema. These scripts are intended to be an aid in determining upgrade requirements and must be reviewed by a Teradata DBA and corrected if necessary.

upgradedwtables_sql.log. This file is the log file that corresponds to the upgrade-regular.sql file. It is for information purposes only.

upgrade-issues.log. This file is the log file that corresponds to the file upgrade-questionable.sql. It is for information purposes only.

6. Open the upgrade-regular.sql and upgrade-questionable.sql files, and search for the following statement to locate columns that have been added or changed.
ALTER TABLE <Table Name> ADD <Column Name><attributes>;

7. For all columns with the ADD command, check to see whether any columns exist already, and if they do, check whether they have STATISTICS defined on them.

8. For all columns that have STATISTICS defined on them, back up the column definition and then drop the STATISTICS.

9. Execute the scripts in the upgrade-regular.sql file.

10. Review the scripts in the upgrade-questionable.sql file. Edit the scripts as needed, and execute them.

11. Recreate STATISTICS on any column on which they were dropped.

4. Execute the 7964_UPDATE_DEFAULTS.sql scripts.

5. Execute the 7964_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

6. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

7. Configure the Informatica parameter file 7964_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7964_UPG_PARAMS.txt."

8. In Informatica Workflow Manager, navigate to the folder UPGRADE_7963_to_7964_SBL and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.

9. Run the 7964_UPGRADE_POST_SCRIPT.sql. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

10. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

11. Once the data migration steps above are complete, you can delete the Upgrade repository to avoid any accidental use or confusion.

1. In the Informatica Administrator, select the Upgrade repository service.

2. In the General Properties area of the Properties tab, click Edit.

3. Make sure the operating mode of the repository service is set to Exclusive.

4. Click OK.

5. Choose Actions, and then click Delete Contents.

6. In the Delete contents for <repository name> dialog, enter the repository username and password, and then click OK.

5.12 Localizing the Policy Store

The Oracle BI Applications 7.9.6.4 installer contains different policy stores for different languages. The default policy store that is deployed during the installation is in English. If you want to configure the policy store for any of the other available languages, perform the procedure below.

To configure the policy store for languages other than English:

1. Stop the Oracle BI Services.

2. Copy the system-jazn-data_<LN>.xml file from $ORACLE_BI_HOME\biapps\admin\provisioning\localization\ to $DOMAIN_HOME\config\fmwconfig\.
For example, to implement the policy store for French, you would copy the file system-jazn-data_fr.xml into the \fmwconfig directory.

3. Back up the existing system-jazn-data.xml file in $DOMAIN_HOME\config\fmwconfig\.

4. Rename $DOMAIN_HOME\config\fmwconfig\system-jazn-data_<LN>.xml to system-jazn-data.xml.

5. Start Oracle BI Services.

5.13 Importing the Oracle BI Applications Version 7.9.6.4 LDIF File Into the Embedded LDAP Server

In this procedure, you will import the standard (out-of-the-box) Oracle BI Applications version 7.9.6.4 LDIF file into the WebLogic Server embedded LDAP server.

To import the Oracle BI Applications version 7.9.6.4 LDIF file:

1. Log in to the WebLogic Server Administration Console using the URL http://<host name>:7001/console.

2. Select the name of the security realm into which the LDIF file is to be imported (for example, myrealm).

3. Select Providers and then the type of provider into which the LDIF file is to be imported (for example, Providers, and then Authentication).

4. Select the security provider in which the LDIF file is to be imported and select Migration, and then select Import.

5. Click Save.

5.14 Upgrading the Oracle BI Repository and Presentation Catalog to the Oracle BI Enterprise Edition 11g Version

Use the Oracle BI Enterprise Edition Upgrade Assistant to upgrade the following repositories and web catalog from the Oracle BI Enterprise Edition 10g format to the 11g format:

- The standard (out-of-the-box) Oracle BI Repository. This repository is the one that you originally received from Oracle as part of your current Oracle BI Applications installation (the version from which you are upgrading). Standard repositories from previous releases are available in the installation folder $ORACLE_BI_HOME\biapps\upgrade.

- The Oracle BI Repository you are currently using (the repository deployed in production).

- The Presentation Catalog you are currently using (the catalog deployed in production).

For instructions on using the Upgrade Assistant, see Oracle Fusion Middleware Upgrade Guide for Oracle Business Intelligence.

Note:

Your current policy store will be merged with the Oracle BI Applications release 7.9.6.4 policy store while upgrading the Oracle BI repository from the 10g format to the 11g format. The final policy store will be the super set of Oracle BI Applications release 7.9.6.4 policy store and the custom and current policy information from the 10g repository.

Also, your current users and groups from the repository will be merged with the Oracle BI Applications release 7.9.6.4 identity store while upgrading the Oracle BI repository from the 10g format to the 11g format. The final identity store will be the super set of the Oracle BI Applications release 7.9.6.4 identity store and the identity store information (users and groups) from the 10g repository.

If you require the policy store to be in a language other than English, perform the steps in Section 5.12, "Localizing the Policy Store."

5.15 Merging Oracle BI Applications Version 7.9.6.4 Repository With Customer Repository

Note:

Before you begin this procedure, you must have already upgraded the Oracle BI repository you are currently using and the standard (out-of-the-box) Oracle BI repository version 7.9.x (the version from which you are upgrading) to the Oracle BI Enterprise Edition 11g format. For more information, see Section 5.14, "Upgrading the Oracle BI Repository and Presentation Catalog to the Oracle BI Enterprise Edition 11g Version."

This process merges your customizations of a prior release of the Oracle BI repository with the new release 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 5.15.1, "Preparing for the Oracle BI Repository Upgrade"

- Section 5.15.2, "Equalizing the Oracle BI Repositories"

- Section 5.15.3, "Comparing the Oracle BI Repositories"

- Section 5.15.4, "Merging the Oracle BI Repositories"

The tasks in this section refer to multiple releases of the Oracle BI repository. Table 5-1 provides the names and descriptions of the repositories used in the examples in this section.

Table 5-1 Names of Analytics Repositories used in Examples

Name of Repository

Description

OracleBIAnalyticsApps_79x.rpd

The standard Oracle BI repository for the version you are upgrading from.

Note: Standard repositories from previous releases are available in the folder $ORACLE_BI_HOME\biapps\upgrade.

OracleBIAnalyticsApps.rpd

The standard Oracle BI repository for the version you are upgrading to.

Customer_OracleBIAnalyticsApps.rpd

The Oracle BI 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.

5.15.1 Preparing for the Oracle BI Repository Upgrade

Follow this procedure to prepare for the repository upgrade.

To prepare for the Analytics repository upgrade:

1. Set up a directory for the merge process, such as \OracleBIUpgrade, and create the following subfolders:

- Original

- AfterEqualize

- AfterMerge

- AfterManualWork

- AfterRegressions

2. Copy the following repositories to the folder \OracleBIUpgrade\Original:

- The standard repository that you upgraded to the 11g format in Section 5.14, "Upgrading the Oracle BI Repository and Presentation Catalog to the Oracle BI Enterprise Edition 11g Version" (for example, OracleBIAnalyticsApps_79x.rpd).

- The production repository that you also upgraded to the 11g format in Section 5.14 (for example, Customer_OracleBIAnalyticsApps.rpd.

- The Oracle BI repository from the latest installation (for example, OracleBIAnalyticsApps.rpd)

If, in your current environment, you are running Oracle BI Applications for one or more modules using a Oracle BI repository in which you extracted the corresponding projects for the modules from the standard Oracle BI repository file you received from the previous release, you need to extract the same projects from the OracleBIAnalyticsApps_79x.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 Oracle BI 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 OracleBIAnalyticsApps_79x.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.

5.15.2 Equalizing the Oracle BI Repositories

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, OracleBIAnalyticsApps_79x.rpd, OracleBIAnalyticsApps.rpd, and Customer_OracleBIAnalyticsApps.rpd) are equivalent.

The point of this step is to determine for every object in the OracleBIAnalyticsApps.rpd and the Customer_OracleBIAnalyticsApps.rpd whether it is coming from the OracleBIAnalyticsApps_79x.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 $ORACLE_BI_HOME\biapps\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.
Table 5-2 provides a list of the available MAP files and the Siebel Analytics or Oracle BI Applications release version associated with the file.

Table 5-2 Rename MAP Files to Be Used for Various Releases

Siebel Analytics / Oracle Business Intelligence Applications Release Version (Upgrading from DW Version)

Rename MAP File to Be Used

Siebel Business Analytics Applications 7.0.x

Not available

Siebel Business Analytics Applications 7.5.x

Not available

Siebel Business Analytics Applications 7.7.x (with Siebel CRM OLTP Pre-7.7.0)

Rename77-7963.map

Siebel Business Analytics Applications 7.7.x (with Siebel CRM OLTP 7.7.0)

Rename771-7963.map

Siebel Business Analytics Applications 7.8.2 and all 7.8.x versions before this release

Rename782-7963.map

Siebel Business Analytics Applications 7.8.3 and all 7.8.x versions after this release

Rename783-7963.map

Oracle BI Applications 7.9.0

Rename79x-7963.map

Oracle BI Applications 7.9.1

Rename79x-7963.map

Oracle BI Applications 7.9.2

Rename79x-7963.map

Oracle BI Applications 7.9.3

Rename793to7963.map

Oracle BI Applications 7.9.4

Rename794to7963.map

Oracle BI Applications 7.9.5

Rename79x-7963.map

Oracle BI Applications 7.9.5.1

Rename7951to7963.map

Oracle BI Applications 7.9.5.2

Rename7951to7963.map

Oracle BI Applications 7.9.6

Rename79x-7963.map

Oracle BI Applications 7.9.6.2

rename7963to7964.map

Not required for upgrades from 7.9.6.2 to 7.9.6.3.

Oracle BI Applications 7.9.6.3

rename7963to7964.map

The syntax of the equalizerpds command is as follows:

equalizerpds.exe  [-B [password1]] -C base_repository_name [-E [password2]] -F repository2_name [-J udml_utf8_file_name_equalization] [-O ouput_repository_name] [-Y equalStringSet]
-Y          Treat the characters as equals.
/?          Display this usage information and exit.

To equalize a repository:

1. Copy the appropriate MAP file from the $ORACLE_BI_HOME\biapps\upgrade folder into the folder where you will execute equalizerpds.exe, for example, \OracleBIUpgrade\Original.

2. Run equalizerpds.exe to equalize the repository from the latest installation (for example, OracleBIAnalyticsApps.rpd) with the original repository (for example, OracleBIAnalyticsApps_794.rpd). An example of the equalizerpds command is as follows:

equalizerpds -B SADMIN
-C \\OracleBIUpgrade\Original\OracleBIAnalyticsApps_791.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 $ORACLE_BI_HOME\biapps\upgrade folder.

If the equalizerpds.exe executable file runs correctly, no errors are returned.

3. Run equalizerpds.exe to equalize your customized repository (for example, Customer_OracleBIAnalyticsApps.rpd) with the original repository (for example, OracleBIAnalyticsApps_79x.rpd). An example of the equalizerpds command is as follows:

equalizerpds -B SADMIN
-C \\OracleBIUpgrade\Original\OracleBIAnalyticsApps_791.rpd
-E SADMIN
-F \\OracleBIUpgrade\Original\Customer_OracleBIAnalyticsApps.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.

4. 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).

5.15.3 Comparing the Oracle BI Repositories

Follow this procedure to compare your existing repository with the new version to which you are upgrading.

To compare the Oracle BI 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 Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition.

5.15.4 Merging the Oracle BI Repositories

In this procedure, you execute the main algorithm to upgrade the repository. For more information on merging the repositories, see Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition.

To merge versions of the Oracle BI repositories:

1. Copy the three repositories (for example, OracleBIAnalyticsApps_79x.rpd, OracleBIAnalyticsApps.rpd, and Customer_OracleBIAnalyticsApps.rpd) to the AfterMerge folder.

2. Open the repository from the latest installation (for example, OracleBIAnalyticsApps.rpd) in the \OracleBIUpgrade\AfterMerge folder.

3. From the Administration Tool menu bar, select File, then select Merge.

4. Select the Merge Type option Full Repository Merge.

5. In the Select Original Repository dialog box, select the original repository (for example, OracleBIAnalyticsApps_79x.rpd).

6. Enter the password for the original repository.

7. In the Select Modified Repository dialog box, select the repository that contains the customizations you made to the previous version of the Analytics repository.

8. Enter the password for the modified repository.

9. In the Saved Merged Repository as dialog box, enter the name for the merged repository, for example, Merged_Repository_OracleBIAnalyticsApps.rpd.
The new repository will contain the final results of the merge.

10. Select the Equalize during merge check box.

11. Click Next.

12. In the Decision drop-down list, select the action you want to take regarding the repository change, or accept the default action.

13. To locate subsequent rows with empty Decision fields, click the Decision header cell.
When all rows have a value in the Decision field, the Finish button is enabled.

14. Select the Check consistency of the merged RPD check box.

15. Click Finish.
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.

16. 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'

17. Copy the repository to the folder \OracleBIUpgrade\AfterManualWork.

5.16 Merging Oracle BI Applications Version 7.9.6.4 Presentation Catalog With Current (Custom) Catalog

Note:

Before you begin this procedure, you must have already upgraded your current (custom) catalog to the Oracle BI Enterprise Edition 11g format. For more information, see Section 5.14, "Upgrading the Oracle BI Repository and Presentation Catalog to the Oracle BI Enterprise Edition 11g Version."

You need to perform the following tasks to complete the presentation merge process.

- Section 5.16.1, "Trimming the Input Presentation Catalog"

- Section 5.16.2, "Merging the Oracle BI Applications Version 7.9.6.4 Presentation Catalog With Current (Custom) Catalog"

- Section 5.16.3, "Testing the Results of the Presentation Catalog Upgrade"

These procedures use the following terminology to identify the various presentation catalogs you will use in the merge process:

- The original presentation catalog. This catalog is the output from the step you performed in Section 5.14, "Upgrading the Oracle BI Repository and Presentation Catalog to the Oracle BI Enterprise Edition 11g Version." It is the version of the unmodified presentation catalog you received with the Oracle BI Applications release you are upgrading from that you upgraded to the 11g format.

- The new presentation catalog. This is the standard Oracle BI Applications 7.9.6.4 presentation catalog that is installed with Oracle BI Applications.

- The current presentation catalog. This catalog is the output from the step you performed in Section 5.14, "Upgrading the Oracle BI Repository and Presentation Catalog to the Oracle BI Enterprise Edition 11g Version." It is the presentation catalog currently in use at your organization that you upgraded to the 11g format.

5.16.1 Trimming the Input Presentation Catalog

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.

5.16.2 Merging the Oracle BI Applications Version 7.9.6.4 Presentation Catalog With Current (Custom) Catalog

Note:

Before you begin this procedure, you must have already upgraded your current (custom) catalog to the Oracle BI Enterprise Edition 11g format. For more information, see Section 5.14, "Upgrading the Oracle BI Repository and Presentation Catalog to the Oracle BI Enterprise Edition 11g Version."

Follow the instructions in this section to merge the Oracle BI Applications version 7.9.6.4 presentation catalog with the catalog you are currently using. This procedure uses the Oracle BI Enterprise Edition Catalog Manager. High-level steps for the merge process are provided in this section. For detailed instructions on using the Catalog Manager, see the chapter "Configuring and Managing the Oracle BI Presentation Catalog," in the Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition 11g Release 1 (11.1.1).

To merge the Oracle BI Applications version 7.9.6.4 presentation catalog with the current (custom) catalog:

1. Start the Catalog Manager, and open your current (custom) presentation catalog in offline mode.
For instructions, see the section "Starting Catalog Manager and Opening Catalogs," in the Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition 11g Release 1 (11.1.1).

2. Start another instance of the Catalog Manager, and open the Oracle BI Applications version 7.9.6.4 (out-of-the-box) presentation catalog in offline mode.

3. Copy and paste the custom objects from your current presentation catalog into the Oracle BI Applications version 7.9.6.4 (out-of-the-box) presentation catalog.
For instructions, see the section "Working with Objects in Catalog Manager," in the Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition 11g Release 1 (11.1.1).

4. If you created custom catalog groups that are not in the version 7.9.6.4 presentation catalog, you need to convert the custom catalog groups to application roles in order to maintain consistency with the version 7.9.6.4 presentation catalog.
To convert custom catalog groups to application roles, run the following command:

runcat.cmd/runcat.sh -cmd replaceAccountInPermissions -old <Catalog Group Name> -oldType group -new <App Role Name> -newType role -offline  <catalog path>

For example:

runcat.cmd -cmd replaceAccountInPermissions -old "AP Analyst" -oldType group -new "AP Analyst" -newType role -offline  c:/SampleWebcat

This command replaces a specified account with another in all catalog object ACLs and privileges in the presentation catalog, entirely in the offline mode. If an entirely new application role is specified as the replacement account, then it is necessary to refresh the GUIDs in the presentation catalog before it can be used.

Note: If the specified replacement user or group is not already present in the presentation catalog 11g Release 1 (11.1.1) already, then this operation will fail.

For more information, see the Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition 11g Release 1 (11.1.1).

5.16.3 Testing the Results of the Presentation Catalog Upgrade

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.

5.17 Regression Testing the Oracle BI Repository Merge

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:

1. 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.

2. 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 Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition.

3. Execute the logical SQL against the old repository using the command line utility nQCmd.exe located in $ORACLE_BI_HOME\bifoundation\server\bin, and save the results to a file.
For information about the nQCmd.exe utility, see Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition.

4. Edit the logical SQL test scripts to account for the name changes or modifications resulting from the upgrade.

5. Execute the edited logical SQL against the merged repository, and save the results.

6. 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.

Part II

Upgrading When Your Source System Is Oracle EBS

Part II contains instructions for upgrading to the current release of Oracle BI Applications from previous releases when you are running Oracle EBS as your source system.

Part II contains Chapter 6, "Upgrading Oracle BI Applications for Oracle Source Systems."

6 Upgrading Oracle BI Applications for Oracle Source Systems

This section contains instructions for upgrading Oracle BI Applications when you are running Oracle EBS as your source system.

This section includes the following topics:

- Section 6.1, "Prerequisites for Upgrading Oracle BI Applications"

- Section 6.2, "Upgrading Oracle BI Infrastructure to Version 11g"

- Section 6.3, "Upgrading Oracle BI Applications"

- Section 6.4, "Upgrading to Informatica PowerCenter Version 9.0.1 Hotfix 2"

- Section 6.5, "Upgrading the Informatica Repository"

- Section 6.6, "Upgrading the Informatica Repository When You Are Already Running Informatica PowerCenter 9.1"

- Section 6.7, "Verifying Configurations for Informatica PowerCenter Version 9.0.1 Hotfix 2 to Work With Oracle BI Applications and DAC"

- Section 6.8, "Upgrading to and Configuring DAC Version 11g"

- Section 6.9, "Upgrading the Data Warehouse Schema and Migrating Data for Non-Teradata Databases"

- Section 6.10, "Upgrading the Data Warehouse Schema and Migrating Data for Teradata Databases"

- Section 6.11, "Localizing the Policy Store"

- Section 6.12, "Importing the Oracle BI Applications Version 7.9.6.4 LDIF File Into the Embedded LDAP Server"

- Section 6.13, "Upgrading the Oracle BI Repository and Presentation Catalog to the Oracle BI Enterprise Edition 11g Version"

- Section 6.14, "Merging Oracle BI Applications Version 7.9.6.4 Repository With Customer Repository"

- Section 6.15, "Merging Oracle BI Applications Version 7.9.6.4 Presentation Catalog With Current (Custom) Catalog"

- Section 6.16, "Regression Testing the Oracle BI Repository Merge"

6.1 Prerequisites for Upgrading Oracle BI Applications

Complete the following prerequisites before upgrading to Oracle BI Applications release 7.9.6.4:

- The DAC Client requires an ODBC connection to the Oracle Business Analytics Warehouse when the database type is Oracle, SQL Server, DB2, and DB2-390 in order to upgrade the data warehouse schema using the DDL Import Utility.
Before you upgrade to Oracle BI Applications verify whether you have the appropriate ODBC connection set. If you do not, see Appendix F, "Creating ODBC Database Connections for DAC."

6.2 Upgrading Oracle BI Infrastructure to Version 11g

You must upgrade Oracle BI Infrastructure to version 11g. For the specific release of Oracle BI Infrastructure 11g that is supported for this release of Oracle BI Applications, see the System Requirements and Supported Platforms for Oracle Business Intelligence Applications. For information on installing the supported version of Oracle BI Infrastructure, see the Oracle Fusion Middleware Upgrade Guide for Oracle Business Intelligence.

6.3 Upgrading Oracle BI Applications

Run the Oracle BI Applications installer to upgrade your Oracle BI Applications environment to the current version. For instructions on running the installer, see the Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users.

Note the following points:

- Review "Chapter 3: Preinstallation and Predeployment Requirements for Oracle BI Applications," in the Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users. You must satisfy these requirements in order to upgrade to the current version of Oracle BI Applications.

- Perform only the step that addresses the running of the installer. Do not perform the configuration instructions that follow the running of the installer.

- If you have a previous release of Oracle BI Applications installed, you must uninstall it before you run the installer for the current release. If you do not uninstall the old release, some folders from the current release will not be correctly installed. (Make a back-up of your DAC folder before you uninstall the old release. This will be the backup of your DAC Client and Server and the DAC metadata files.)

6.4 Upgrading to Informatica PowerCenter Version 9.0.1 Hotfix 2

You must install Informatica PowerCenter 9.0.1 Hotfix 2 to run the current version of Oracle BI Applications. See the System Requirements and Supported Platforms for Oracle Business Intelligence Applications for information about additional hotfixes or emergency bug fixes that may be required to support the current version of Informatica.

Note:

Oracle BI Applications release 7.9.6.4 is also certified to run with Informatica PowerCenter version 9.1 Hotfix 2. For instructions on upgrading the Informatica Repository if you have previously upgraded to Informatica PowerCenter 9.1 Hotfix 2, see Section 6.6, "Upgrading the Informatica Repository When You Are Already Running Informatica PowerCenter 9.1."

The components and architecture for Informatica PowerCenter 9.x differ significantly from Informatica PowerCenter 7.x and 8.x. Oracle recommends that you carefully review the Informatica PowerCenter 9.0.1 documentation.

For a summary of installation instructions for installing Informatica PowerCenter 9.0.1 on a single machine in an Oracle BI Applications deployment, see the Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users.

For detailed information about deploying Informatica PowerCenter 9.0.1, refer to the Informatica PowerCenter Installation and Configuration Guide, Informatica Upgrade Guide for PowerCenter 8.1.x, Informatica Upgrade Guide for PowerCenter 8.5.x and 8.6.x, Informatica Administrator Guide, and related documentation. See the Oracle Business Intelligence Applications Release Notes, available on the Oracle Technology Network, for information about how to locate the Informatica documentation.

To upgrade to Informatica PowerCenter 9.0.1 Hotfix 2:

- Perform the pre-upgrade, upgrade, and post-upgrade steps documented in Informatica Upgrade Guide for PowerCenter 8.1.x or Informatica Upgrade Guide for PowerCenter 8.5.x and 8.6.x, depending on which version of Informatica PowerCenter you are upgrading from.

Note the following points:

- The Informatica PowerCenter 9.0.1 installation process includes upgrading your current Informatica Repository to the version 9.0.1 format. This process is necessary so that you will be able to access your current repository using the version 9.0.1 client tools and so that you can perform the procedure Section 6.5, "Upgrading the Informatica Repository."
In Section 6.5, "Upgrading the Informatica Repository," you back up and rename your current repository and then restore the Informatica Repository that is installed during the Oracle BI Applications installation (for example, Oracle_BI_DW_Base.rep). You then copy the folders containing the Oracle BI Applications content for release 7.9.6.4 to your existing repository.

- If you install Informatica PowerCenter 9.0.1 using the installer Upgrade option rather than the Install option, the property $PMRootDir is not updated to the upgraded service version installation directory. You need to configure this property to specify the upgraded service installation directory in order for DAC to be able to locate the Informatica source files.
To configure the $PMRootDir property: launch Informatica Administrator, select the Integration Service from the Navigator, click the Processes tab, and click Edit. Then, enter the appropriate value for $PMRootDir.

6.5 Upgrading the Informatica Repository

Follow this procedure to upgrade the Informatica Repository when you are upgrading the Informatica PowerCenter platform from version 7.x or 8.x to 9.0.1 Hotfix 2. If you have already upgraded to Informatica PowerCenter 9.1, follow the procedure in Section 6.6, "Upgrading the Informatica Repository When You Are Already Running Informatica PowerCenter 9.1."

In this procedure, you will copy the folders containing the Oracle BI Applications 7.9.6.4 content into your current, existing Informatica Repository. The result of this action is an Informatica Repository that contains your customizations along with the new Oracle BI Applications 7.9.6.4 content.

For detailed instructions on backing up and restoring the Informatica Repository, see the topic titled, "Backing Up and Restoring the PowerCenter Repository," in "Chapter 15: PowerCenter Repository Management," in the Informatica PowerCenter Administrator Guide. See the Oracle Business Intelligence Applications Release Notes, available on the Oracle Technology Network, for information about how to locate the Informatica documentation.

To upgrade the Informatica Repository:

1. Make sure you have backed up and renamed your current, existing Informatica Repository.

2. Copy the Oracle_BI_DW_Base.rep file (or Oracle_BI_DW_Teradata.rep for repositories on Teradata databases) from the folder OracleBI\dwrep\Informatica\Repository into the folder <INFA_HOME>\server\infa_shared\Backup.

Note:

The Oracle_BI_DW_Base.rep file is installed in the OracleBI root directory when you run the Oracle BI Applications installer, as described in Section 6.3, "Upgrading Oracle BI Applications."

3. Using Informatica PowerCenter Administrator, create a new Repository Service for the Oracle_BI_DW_Base.rep repository. See "Setup Step: Creating the Informatica Repository Service," in Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users for instructions.

4. Using the Repository Service you created in the step above, restore the Oracle_BI_DW_Base.rep repository into an empty schema. See "Restoring the Prebuilt Informatica Repository for Environments in English" or "Restoring the Prebuilt Informatica Repository on a Non-English Operating System" in Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users for instructions.
This step gives you the Oracle BI Applications 7.9.6.4 Informatica Repository in the Informatica 9.0.1 format.

5. Launch the Informatica PowerCenter Repository Manager, and connect to the repository you restored in step 4 (for example, Oracle_BI_DW_Base.rep), and connect to your current, existing Informatica Repository.
Note: Your current, existing repository should have been updated to the version 9.0.1 format during the Informatica PowerCenter 9.0.1 installation process.

6. In your current, existing repository, make sure all of your customizations are in a "Custom" folder.

7. In your current, existing repository, delete the following folders:

- PLP

- All folders with the prefix SDE_

- SILOS

- SIL_VERT

- UA_SDE

- UA_SIL

Make sure you do not delete the "Custom" folder.

8. Copy the following folders containing the Oracle BI Applications content for release 7.9.6.4 from the newly restored repository (Oracle_BI_DW_Base.rep) into your current, existing repository.

- PLP

- All folders with the prefix SDE_

- SILOS

- SIL_VERT

- UA_SDE

- UA_SIL

This action updates your current, existing repository with the Oracle BI Applications 7.9.6.4 content; this is the repository you will use to run ETL in Oracle BI Applications 7.9.6.4.

The version 7.9.6.4 repository (Oracle_BI_DW_Base.rep) and the Repository Service for this repository are no longer needed.

6.6 Upgrading the Informatica Repository When You Are Already Running Informatica PowerCenter 9.1

If you are upgrading to Oracle BI Applications 7.9.6.4 and previously upgraded Informatica PowerCenter to version 9.1 Hotfix 2, you must first restore the Oracle BI Applications version 7.9.6.4 Informatica Repository using Informatica PowerCenter 9.0.1 Hotfix 2. Then, you can upgrade this repository to the Informatica 9.1 format by pointing to it using Informatica 9.1 client tools. After the Oracle BI Applications 7.9.6.4 Informatica Repository has been upgraded to the Informatica 9.1 format, you can then copy the folders containing the Oracle BI Applications 7.9.6.4 content into your current, existing Informatica Repository. The result of this action is an Informatica Repository that contains your customizations along with the new Oracle BI Applications 7.9.6.4 content.

For detailed instructions on backing up and restoring the Informatica Repository, see the topic titled, "Backing Up and Restoring the PowerCenter Repository," in "Chapter 15: PowerCenter Repository Management," in the Informatica PowerCenter Administrator Guide. See the Oracle Business Intelligence Applications Release Notes, available on the Oracle Technology Network, for information about how to locate the Informatica documentation.

To upgrade the Informatica Repository when already running Informatica PowerCenter 9.1:

1. Make sure you have backed up and renamed your current, existing Informatica Repository.

2. Install Informatica PowerCenter Services version 9.0.1 Hotfix 2. You do not need to install the Informatica PowerCenter Client Tools. See Section 6.4, "Upgrading to Informatica PowerCenter Version 9.0.1 Hotfix 2" for instructions.

3. Copy the Oracle_BI_DW_Base.rep file (or Oracle_BI_DW_Teradata.rep for repositories on Teradata databases) from the folder OracleBI\dwrep\Informatica\Repository into the Informatica PowerCenter 9.0.1 folder <INFA_HOME>\server\infa_shared\Backup.

Note:

The Oracle_BI_DW_Base.rep file is installed in the OracleBI root directory when you run the Oracle BI Applications installer, as described in Section 6.3, "Upgrading Oracle BI Applications."

4. Using Informatica PowerCenter Administrator, create a new Repository Service for the Oracle_BI_DW_Base.rep repository. See "Setup Step: Creating the Informatica Repository Service," in Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users for instructions.

5. Using the Repository Service you created in the step above, restore the Oracle_BI_DW_Base.rep repository into an empty schema. See "Restoring the Prebuilt Informatica Repository for Environments in English" or "Restoring the Prebuilt Informatica Repository on a Non-English Operating System" in Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users for instructions.
This step gives you the Oracle BI Applications 7.9.6.4 Informatica Repository in Informatica 9.0.1 format.

6. Launch the Informatica PowerCenter Repository Manager, and connect to the repository you restored in step 5. When prompted to upgrade the repository to the 9.1 format, do so.

7. In Repository Manger, connect to your current, existing Informatica Repository.

8. In your current, existing repository, make sure all of your customizations are in a "Custom" folder.

9. In your current, existing repository, delete the following folders:

- PLP

- All folders with the prefix SDE_

- SILOS

- SIL_VERT

- UA_SDE

- UA_SIL

Make sure you do not delete the "Custom" folder.

10. Copy the following folders containing the Oracle BI Applications content for release 7.9.6.4 from the newly restored repository (Oracle_BI_DW_Base.rep) into your current, existing repository.

- PLP

- All folders with the prefix SDE_

- SILOS

- SIL_VERT

- UA_SDE

- UA_SIL

This action updates your current, existing repository with the Oracle BI Applications 7.9.6.4 content; this is the repository you will use to run ETL in Oracle BI Applications 7.9.6.4.

The version 7.9.6.4 repository (Oracle_BI_DW_Base.rep) and the Repository Service for this repository are no longer needed.

6.7 Verifying Configurations for Informatica PowerCenter Version 9.0.1 Hotfix 2 to Work With Oracle BI Applications and DAC

Informatica PowerCenter version 9.0.1 Hotfix 2 requires configuration for it to work with Oracle BI Applications and DAC. The configuration settings from your earlier Informatica environment may have been retained when you upgraded to Version 9.0.1 Hotfix 2. Verify or perform the procedures listed below, as documented in the Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users:

- Copying Source Files and Lookup Files

- Setting PowerCenter Integration Services Relaxed Code Page Validation

- Setting PowerCenter Integration Services Custom Properties

- Creating the Repository Administrator User in the Native Security Domain

6.8 Upgrading to and Configuring DAC Version 11g

This section includes instructions for upgrading the DAC platform and repository to version 11g as well as information about configurations you must set or verify.

This section includes the following topics:

- Section 6.8.1, "Installing the DAC Platform and Oracle BI Applications Metadata Repository Files"

- Section 6.8.2, "Configuring the DAC Client and Server to Work With Oracle BI Applications and Informatica"

- Section 6.8.3, "Upgrading the DAC Repository"

6.8.1 Installing the DAC Platform and Oracle BI Applications Metadata Repository Files

The current release of DAC 11g is installed by its own installer and not the Oracle BI Applications installer. For information about the specific release of DAC 11g that is supported for this release of Oracle BI Applications, see System Requirements and Supported Platforms for Oracle Business Intelligence Applications.

After you install DAC 11g, you then need to copy metadata files from the machine hosting Oracle BI Applications to the machines hosting the DAC Client and Server. You then need to import the new metatdata into the DAC Repository. For instructions on performing these tasks, see the following sections in the Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users:

- Installing and Setting Up the DAC Platform

Note:

You must perform all of the procedures in this section, including installing JDBC drivers, creating ODBC database connections, and installing pmrep and pmcmd command line programs.

- Installing DAC Metadata Files

- Logging into DAC for the First Time and Importing Metadata into the DAC Repository

Note:

When you perform this step, DAC will prompt you to upgrade the repository. Click Yes. This action will upgrade your repository in the 10g format to the 11g format.

After you complete this procedure, you will have the default DAC Repository for Oracle BI Applications release 7.9.6.4.

6.8.2 Configuring the DAC Client and Server to Work With Oracle BI Applications and Informatica

The DAC Client and Server require configuration to work with Oracle BI Applications and Informatica PowerCenter. The configuration settings from your earlier DAC environment may have been retained when you upgraded to version 11g. Verify or perform the procedures listed below, as documented in the Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users:

- Configuring the DAC Server

- Configuring DAC Integration Settings

- Configuring the SiebelUnicodeDB Custom Property

Note:

This procedure is required only if your source to target data movement configuration is Unicode to Unicode.

- Setting Up DAC to Receive Email Notification

- Additional Configuration Tasks
In this section, perform only the tasks that apply to your environment.

6.8.3 Upgrading the DAC Repository

To upgrade the DAC Repository, you perform a two-step process:

1. You first upgrade the existing DAC Repository from the 10g format to the 11g format. When you log into DAC 11g for the first time, DAC will prompt you to upgrade your repository. Click Yes.
For more information, see "Upgrading to DAC 11g" in Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Data Warehouse Administration Console and "Logging Into DAC for the First Time and Importing Metadata into the DAC Repository" in Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users.

2. You then use the DAC's Upgrade/Merge Wizard to complete the upgrade of your existing DAC Repository.

- If you are upgrading to Oracle BI Applications release 7.9.6.4, and you are remaining on the same version of the transactional source system, you would use the Refresh Base option of the DAC Upgrade/Merge Wizard to complete the upgrade of your existing DAC Repository. For information about how to use the Refresh Base option, see the topic titled, "About the Refresh Base Option," in the chapter "Upgrading, Comparing and Merging DAC Repositories," in the Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Data Warehouse Administration Console.

- If you are upgrading your transactional system, for example, from Oracle EBS release 12 to release 12.2, you would use the Replace Base option of the DAC Upgrade/Merge Wizard to complete the upgrade of your existing DAC Repository. For information about how to use the Replace Base option, see the topic titled, "About the Replace Base Option," in "Upgrading, Comparing and Merging DAC Repositories," in the Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Data Warehouse Administration Console.

The Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Data Warehouse Administration Console is available in the Oracle Business Intelligence Data Warehouse Administration Console Documentation Library on the Oracle Technology Network.

6.9 Upgrading the Data Warehouse Schema and Migrating Data for Non-Teradata Databases

This section contains the following topics:

- Section 6.9.1, "Performing Data Warehouse Schema Upgrade Steps Common to All Previous Releases"

- Section 6.9.2, "Upgrading the Data Warehouse Schema From Version 7.9.x to 7.9.3 and Migrating Data"

- Section 6.9.3, "Upgrading the Data Warehouse Schema From Version 7.9.3 to 7.9.4 and Migrating Data"

- Section 6.9.4, "Upgrading the Data Warehouse Schema From Version 7.9.4 to 7.9.5. and Migrating Data"

- Section 6.9.5, "Upgrading the Data Warehouse Schema From Version 7.9.5 to 7.9.5.1 and Migrating Data"

- Section 6.9.6, "Upgrading the Data Warehouse Schema From Version 7.9.5.1 to 7.9.6.1 and Migrating Data"

- Section 6.9.7, "Upgrading the Data Warehouse Schema From Version 7.9.6 to 7.9.6.1 and Migrating Data" (Applicable only if you are using an Oracle database as your data warehouse database.)

- Section 6.9.8, "Upgrading the Data Warehouse Schema From Version 7.9.6.1 to 7.9.6.2 and Migrating Data"

- Section 6.9.9, "Upgrading the Data Warehouse Schema From Version 7.9.6.2 to 7.9.6.3 and Migrating Data"

- Section 6.9.10, "Upgrading the Data Warehouse Schema From Version 7.9.6.3 to 7.9.6.4 and Migrating Data"

If you are currently running Oracle BI Applications release 7.9.0, 7.9.1 or 7.9.2, you need to perform the procedures in Section 6.9.1, Section 6.9.2, Section 6.9.3, Section 6.9.4, Section 6.9.5, Section 6.9.6, Section 6.9.8, Section 6.9.9, and Section 6.9.10.

If you are currently running Oracle BI Applications release 7.9.3, you need to perform the procedures in Section 6.9.1, Section 6.9.3, Section 6.9.4, Section 6.9.5, Section 6.9.6, Section 6.9.8, Section 6.9.9, and Section 6.9.10.

If you are currently running Oracle BI Applications release 7.9.4, you need to perform the procedures in Section 6.9.1, Section 6.9.4, Section 6.9.5, and Section 6.9.6, Section 6.9.8, Section 6.9.9, and Section 6.9.10.

If you are currently running Oracle BI Applications release 7.9.5, you need to perform the procedures in Section 6.9.1 and Section 6.9.5, and Section 6.9.6, Section 6.9.8, Section 6.9.9, and Section 6.9.10.

If you are currently running Oracle BI Applications release 7.9.5.1, you need to perform the procedures in Section 6.9.1 and Section 6.9.6, Section 6.9.8, Section 6.9.9, and Section 6.9.10.

If you are currently running Oracle BI Applications release 7.9.6, you need to perform the procedures in Section 6.9.1, Section 6.9.7, Section 6.9.8, Section 6.9.9, and Section 6.9.10.

If you are currently running Oracle BI Applications release 7.9.6.1, you need to perform the procedures in Section 6.9.1, Section 6.9.8, Section 6.9.9, and Section 6.9.10.

If you are currently running Oracle BI Applications release 7.9.6.2, you need to perform the procedures in Section 6.9.1, Section 6.9.9, and Section 6.9.10.

If you are currently running Oracle BI Applications release 7.9.6.3, you need to perform the procedures in Section 6.9.1 and Section 6.9.10.

These procedures add new tables, columns, and indexes to the existing data warehouse schema. They also modify the existing data warehouse schema objects.

6.9.1 Performing Data Warehouse Schema Upgrade Steps Common to All Previous Releases

The steps in this procedure are required for upgrading to Oracle BI Applications release 7.9.6.4 from all previous releases.

To perform common data warehouse upgrade steps:

1. If you are using a DB2 database, you need to execute the stored procedure siebproc.sql, which creates procedures and functions needed by the DDLimp utility. This file is located in \dwrep\siebproc\db2udb.

2. Copy all of the domain value files in the folder \OracleBI\dwrep\Informatica\LkpFiles into the folder <INFA_HOME>\server\infa_shared\LkpFiles.

3. Restore the Upgrade repository:

1. Copy the file Upgrade.rep from the folder OracleBI\dwrep\Upgrade\Informatica\Repository into the folder <INFA_HOME>\server\infa_shared\Backup.

2. Launch the Informatica Administrator, and restore Upgrade.rep (located in <INFA_HOME>\server\infa_shared\Backup).

4. In Informatica Workflow Manager, open the Relational Connection Browser (in the menu bar, select Connections, and then select Relational), and edit the connect string, user and password for the relational connections as follows:

1. For the OLTP connection:
If you are using the Oracle EBS 11i source system, edit the connection PARAM_OLTP_ORA11i.

If you are using Oracle EBS R12, source system, edit the connection PARAM_OLTP_ORAR12.

2. For the OLAP connection, edit the connection PARAM_OLAP.

3. For the DAC database connection, edit the connection PARAM_DAC.

Note:

If you are connected to an Oracle database, use the 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.

6.9.2 Upgrading the Data Warehouse Schema From Version 7.9.x to 7.9.3 and Migrating Data

Perform this procedure if you are upgrading from Oracle BI Applications releases 7.9.0, 7.9.1 or 7.9.2.

To upgrade the data warehouse schema and migrate data into the upgraded data warehouse:

1. Run the UPGRADE_793.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

2. Run the ddl_793.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

3. Run the 793_UPGRADE_PRE_DIMENSION_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

4. Migrate data into the upgraded data warehouse.

1. Configure the Informatica parameter file 793_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 793_UPG_PARAMS.txt."

2. In Informatica Workflow Manager, navigate to the folder UPGRADE_790_to_793 and run the Update_Dimensions workflow, and then run the Update_Facts workflow.

3. If you are using the Oracle EBS 11.5.10 source system, navigate to the folder UPGRADE_790_to_793_ORA11510, and run the SIL_PurchaseAmount_Patch workflow.

5. Verify the data migrated successfully.

1. Validate the data in the upgraded data warehouse.

2. Check whether any of the Informatica mapping log files stored in the <INFA_HOME>\server\infa_shared\SessLogs directory indicate errors or failures.

3. Check whether the script 793_UPGRADE_PRE_DIMENSION_SCRIPT.sql that you ran in the SQL client of the database failed or errored out while executing.

4. Check the log file for the scripts ddl_793.ctl and UPGRADE_793.ctl, which 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.

Note:

Ignore any error messages that indicate tables or indexes could not be dropped from the database. These error messages are displayed when the specified objects do not exist in the database. This can occur because each source system container holds a subset of all data warehouse tables

6. If the data migration was successful, drop the tables that were created during the upgrade process, such as, W_xxxx_x_79x tables, LKP_xxxx_x and 79x_XXXX_TMP.
This step frees the space occupied by these backup tables.

6.9.3 Upgrading the Data Warehouse Schema From Version 7.9.3 to 7.9.4 and Migrating Data

Perform the procedure in this section to upgrade from Oracle BI Applications release 7.9.3 to 7.9.4.

To upgrade the data warehouse schema and migrate data into the upgraded data warehouse:

1. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade repository. For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Upgrade Informatica Repository."

2. Run the 794_UPGRADE_PRE_CTL_SCRIPT.sql. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

3. Run the UPGRADE_794.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

4. Run the ddl_794.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

5. Run the 794_UPGRADE_PRE_DIMENSION_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

6. Migrate data into the upgraded data warehouse.

1. Configure the Informatica parameter file 794_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 794_UPG_PARAMS.txt.".

2. In Informatica Workflow Manager, navigate to the folder UPGRADE_793_to_794_ORA11i and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

7. Verify the data migrated successfully.

1. Validate the data in the upgraded data warehouse.

2. Check whether any of the Informatica mapping log files stored in the <INFA_HOME>\server\infa_shared\SessLogs directory indicate errors or failures.

3. Check whether the script 794_UPGRADE_PRE_DIMENSION_SCRIPT.sql that you ran in the SQL client of the database failed or errored out while executing.

4. Check the log file for the scripts ddl_794 and UpgradPGRADE_794.ctl, which 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.

Note:

Ignore any error messages that indicate tables or indexes could not be dropped from the database. These error messages are displayed when the specified objects do not exist in the database. This can occur because each source system container holds a subset of all data warehouse tables

8. If the data migration was successful, drop the tables that were created during the upgrade process, such as, W_xxxx_x_79x tables, LKP_xxxx_x and 79x_XXXX_TMP.
This step frees the space occupied by these backup tables.

9. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep). For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Base Informatica Repository."

6.9.4 Upgrading the Data Warehouse Schema From Version 7.9.4 to 7.9.5. and Migrating Data

Perform the procedures in this section to upgrade from Oracle BI Applications release 7.9.4 to 7.9.5.

To upgrade the data warehouse schema and migrate data into the upgraded data warehouse:

1. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade repository. For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Upgrade Informatica Repository."

2. Run the 795_UPGRADE_PRE_CTL_SCRIPT.sql. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

3. Run the UPGRADE_795.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

4. Run the ddl_795.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

5. Run the 795_UPGRADE_PRE_DIMENSION_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

6. Migrate data into the upgraded data warehouse.

1. Configure the Informatica parameter file 795_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 795_UPG_PARAMS.txt."

2. If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_794_to_795_ORA11i and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_794_to_795_ORAR12 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

7. Verify the data migrated successfully.

1. Validate the data in the upgraded data warehouse.

2. Check whether any of the Informatica mapping log files stored in the <INFA_HOME>\server\infa_shared\Sesslogs directory indicates errors or failures.

3. Check whether the script 795_UPGRADE_PRE_DIMENSION_SCRIPT.sql that you ran in the SQL client of the database failed or errored out while executing.

4. Check the log file for the scripts ddl_795.ctl and UPGRADE_795.ctl, which 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.

Note:

Ignore any error messages that indicate tables or indexes could not be dropped from the database. These error messages are displayed when the specified objects do not exist in the database. This can occur because each source system container holds a subset of all data warehouse tables

8. If the data migration was successful, drop the tables that were created during the upgrade process, such as W_xxxx_x_79x, LKP_xxxx_x and 79x_xxxx_TMP.
This step frees the space occupied by these backup tables.

9. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep). For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Base Informatica Repository."

6.9.5 Upgrading the Data Warehouse Schema From Version 7.9.5 to 7.9.5.1 and Migrating Data

Perform the procedures in this section to upgrade from Oracle BI Applications release 7.9.5 to 7.9.5.1.

To upgrade the data warehouse schema and migrate data into the upgraded data warehouse:

1. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade repository. For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Upgrade Informatica Repository."

2. Run the 7951_UPGRADE_PRE_CTL_SCRIPT.sql. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

3. Run the UPGRADE_7951.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

4. Run the ddl_7951.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

5. Run the 7951_UPGRADE_PRE_DIMENSION_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

6. Migrate data into the upgraded data warehouse:

1. Configure the Informatica parameter file 7951_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7951_UPG_PARAMS.txt."

2. If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_794_to_7951_ORA11i and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_794_to_7951_ORAR12 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

7. Verify the data migrated successfully.

1. Validate the data in the upgraded data warehouse.

2. Check whether any of the Informatica mapping log files stored in the <INFA_HOME>\server\infa_shared\Sesslogs directory indicates errors or failures.

3. Check whether the script 7951_UPGRADE_PRE_DIMENSION_SCRIPT.sql that you ran in the SQL client of the database failed or errored out while executing.

4. Check the log file for the scripts ddl_7951.ctl and Upgrade_7951.ctl, which 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.

Note:

Ignore any error messages that indicate tables or indexes could not be dropped from the database. These error messages are displayed when the specified objects do not exist in the database. This can occur because each source system container holds a subset of all data warehouse tables

8. If the data migration was successful, drop the tables that were created during the upgrade process, such as W_xxxx_x_79x, LKP_xxxx_x and 79x_xxxx_TMP.
This step frees the space occupied by these backup tables.

9. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep). For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Base Informatica Repository."

6.9.6 Upgrading the Data Warehouse Schema From Version 7.9.5.1 to 7.9.6.1 and Migrating Data

Perform the procedures in this section to upgrade from Oracle BI Applications release 7.9.5.1 to 7.9.6.1.

This section includes the following procedures:

- Section 6.9.6.1, "Upgrading the Data Warehouse Schema to Version 7.9.6.1"

- Section 6.9.6.2, "Migrating Data into the Upgraded Data Warehouse"

- Section 6.9.6.3, "Verifying the Data Migrated Successfully"

- Section 6.9.6.4, "Resetting Refresh Dates"

6.9.6.1 Upgrading the Data Warehouse Schema to Version 7.9.6.1

Follow this procedure to upgrade the data warehouse schema to version 7.9.6.1.

Note: Upgrading to version 7.9.6.1 may involve running scripts that have a "796_" prefix.

To upgrade the data warehouse schema to version 7.9.6.1:

1. If you are using an Oracle database, run the 796_UPGRADE_DROP_INDEXES.sql script.

1. Open the SQL client for your database type.

2. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Oracle.

3. Open the 796_UPGRADE_DROP_INDEXES. sql file, and copy the contents into the SQL client.

4. Execute the script.

2. If you are using a SQL Server or DB2 database, run the 7961_UPGRADE_DROP_INDEXES.sql script.

1. Open the SQL client for your database type.

2. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\<database type>.

3. Open the 7961_UPGRADE_DROP_INDEXES. sql file, and copy the contents into the SQL client.

4. Execute the script.

3. If you are using a SQL Server database, run the 7961_UPGRADE_PRE_UPG_CTL_SCRIPT.sql file. This file is located in OracleBI\dwrep\Upgrade\DbScripts\SQLServer.

4. Run the UPGRADE_796.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

5. Run the 7961_UPGRADE_PRE_CTL_SCRIPT.sql:

1. Go to OracleBI\dwrep\Upgrade\DbScripts\<database type> folder, and open the 7961_UPGRADE_PRE_CTL_SCRIPT.sql file.

2. Search for the Datasource_Num_ID parameter, and make sure the value is correct for your existing implementation.

3. If you are using a DB2 database, search for the text "TBS_32K," and replace it with the appropriate 32K table space name that you have configured.

4. Execute the script.

6. Run the ddl_7961.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

6.9.6.2 Migrating Data into the Upgraded Data Warehouse

Follow this procedure to migrate data into the upgraded data warehouse.

To migrate data into the upgraded data warehouse:

1. Run the 796_UPGRADE_PRE_DIMENSION_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

2. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade repository. For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Upgrade Informatica Repository."

3. Configure the Informatica parameter file 796_UPG_PARAMS.txt file. For instructions, see Appendix A, "Setting Parameters in 796_UPG_PARAMS.txt."

4. If you are using Oracle EBS 11i, configure parameters specific to Oracle 11i source systems. For instructions, see Appendix A, "Setting Parameters in 796_UPG_PARAMS.txt for Oracle EBS 11i Source Systems."

5. If you are upgrading Oracle Financial Analytics, you need to configure specific parameters and update mappings. For more information, see Appendix A, "Setting Parameters and Mappings in 796_UPG_PARAMS.txt for Oracle Financial Analytics."

6. If you are upgrading Oracle Supply Chain and Order Management Analytics, you need to configure specific parameters. For more information, see Appendix A, "Setting Parameters in 796_UPG_PARAMS.txt for Oracle Supply Chain and Order Management Analytics."

7. If you are deploying Oracle Project Analytics, you need to configure specific parameters. For more information, see Appendix A, "Setting Parameters in 796_UPG_PARAMS.txt for Oracle Project Analytics."

8. Back up and truncate the table W_POSITION_DH.

9. If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_7951_to_796_ORA11i and execute the following workflows in the order they appear:

- UPGRADE_DIMENSIONS

- UPGRADE_FACTS

If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_ORAR12 and execute the following workflows in the order they appear:

- UPGRADE_DIMENSIONS

- UPGRADE_FACTS

10. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep). For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Base Informatica Repository."

11. Run the 7961_UPGRADE_PRE_DIMENSION_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

12. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade repository. For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Upgrade Informatica Repository."

13. Configure the Informatica parameter file 7961_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7961_UPG_PARAMS.txt."

14. If you are upgrading Oracle Financial Analytics, you need to configure specific parameters and update mappings. For more information, see Section A.3.1, "Setting Parameters and Mappings in 796_UPG_PARAMS.txt for Oracle Financial Analytics."

15. If you are upgrading Oracle Supply Chain and Order Management Analytics, you need to configure specific parameters. For more information, see Section A.3.3, "Setting Parameters in 796_UPG_PARAMS.txt for Oracle Supply Chain and Order Management Analytics."

16. If you are deploying Oracle Project Analytics, you need to configure specific parameters. For more information, see Section A.3.2, "Setting Parameters in 796_UPG_PARAMS.txt for Oracle Project Analytics."

17. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade repository. For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Upgrade Informatica Repository."

18. If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_796_to_7961_ORA11i and execute the first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_796_to_7961_ORAR12 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

19. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep). For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Base Informatica Repository."

20. Run the 7961_UPGRADE_POST_SCRIPT.sql. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

6.9.6.3 Verifying the Data Migrated Successfully

Follow this procedure to verify that the data was migrated successfully into the upgraded data warehouse.

To verify the data migrated successfully:

1. Validate the data in the upgraded data warehouse.

2. Check whether any of the Informatica mapping log files stored in the <INFA_HOME>\server\infa_shared\Sesslogs directory indicates errors or failures.

3. Check whether the following scripts that you ran in the SQL client of the database failed or errored out while executing:
7961_UPGRADE_DROP_INDEXES.sql

7961_UPGRADE_PRE_CTL_SCRIPT.sql

796_UPGRADE_PRE_DIMENSION.sql

796_UPGRADE_POST_SCRIPT.sql

7961_UPGRADE_POST_SCRIPT.sq

4. Check the log files for the ddl_7961.ctl and Upgrade_796.ctl scripts 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.

Note:

Ignore any error messages that indicate tables or indexes could not be dropped from the database. These error messages are displayed when the specified objects do not exist in the database. This can occur because each source system container holds a subset of all data warehouse tables

5. If the data migration was successful, drop the tables that were created during the upgrade process, such as W_xxxx_x_79x, LKP_xxxx_x and 79x_xxxx_TMP.
This step frees the space occupied by these backup tables.

6.9.6.4 Resetting Refresh Dates

After verifying the data was migrated successfully into the upgraded data warehouse, follow this procedure to reset refresh dates.

1. If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_7951_TO_796_ORA11i and execute the RESET_DAC_REFRESH_DATES workflow.

2. If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_7951_TO_796_ORAR12 and execute the RESET_DAC_REFRESH_DATES workflow.

3. In DAC, do the following:

1. Navigate to the Setup view, and click the Physical Data Sources tab.

2. In the top pane list, select DataWarehouse. (If you customized the name of the connection for the data warehouse, select the appropriate connection for the data warehouse database.)

3. Click the Refresh Dates subtab (in the lower pane).

4. Query for the table FND_LOOKUP_VALUES, and set the value in the Refresh Date column to NULL.

4. Once the data migration steps above are complete, you can delete the Upgrade repository to avoid any accidental use or confusion.

1. In the Informatica Administrator, select the Upgrade repository service.

2. In the General Properties area of the Properties tab, click Edit.

3. Make sure the operating mode of the repository service is set to Exclusive.

4. Click OK.

5. Choose Actions, and then click Delete Contents.

6. In the Delete contents for <repository name> dialog, enter the repository username and password, and then click OK.

6.9.7 Upgrading the Data Warehouse Schema From Version 7.9.6 to 7.9.6.1 and Migrating Data

Perform the procedures in this section to upgrade from Oracle BI Applications release 7.9.6 to release 7.9.6.1.

Note:

This procedure is applicable only if you are using an Oracle database for your data warehouse database.

This section includes the following procedures:

- Section 6.9.7.1, "Upgrading the Data Warehouse Schema to Version 7.9.6.1"

- Section 6.9.7.2, "Migrating Data into the Upgraded Data Warehouse"

- Section 6.9.7.3, "Verifying the Data Migrated Successfully"

6.9.7.1 Upgrading the Data Warehouse Schema to Version 7.9.6.1

Follow this procedure to upgrade the data warehouse schema to version 7.9.6.1.

To upgrade the data warehouse schema to version 7.9.6.1:

1. Run the UPGRADE_7961.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

2. Run the 796ORA_TO_7961ORA_UPGRADE_PRE_CTL_SCRIPT.sql. This file is located in the folder OracleBI\dwrep\Upgrade\DbScripts\Oracle.

3. Run the ddl_7961.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

6.9.7.2 Migrating Data into the Upgraded Data Warehouse

Follow this procedure to migrate data into the upgraded data warehouse.

To migrate data into the upgraded data warehouse:

1. Run the 7961_UPGRADE_PRE_DIMENSION_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Oracle.

2. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade repository. For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Upgrade Informatica Repository."

3. Configure the Informatica parameter file 7961_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7961_UPG_PARAMS.txt."

4. If you are upgrading Oracle Financial Analytics, you need to configure specific parameters and update mappings. For more information, see Section A.3.1, "Setting Parameters and Mappings in 796_UPG_PARAMS.txt for Oracle Financial Analytics."

5. If you are upgrading Oracle Supply Chain and Order Management Analytics, you need to configure specific parameters. For more information, see Section A.3.3, "Setting Parameters in 796_UPG_PARAMS.txt for Oracle Supply Chain and Order Management Analytics."

6. If you are deploying Oracle Project Analytics, you need to configure specific parameters. For more information, see Section A.3.2, "Setting Parameters in 796_UPG_PARAMS.txt for Oracle Project Analytics."

7. If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_796_to_7961_ORA11i and execute the first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_796_to_7961_ORAR12 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

8. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep). For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Base Informatica Repository."

9. Run the 7961_UPGRADE_POST_SCRIPT.sql. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Oracle.

6.9.7.3 Verifying the Data Migrated Successfully

Follow this procedure to verify that the data was migrated successfully into the upgraded data warehouse.

To verify the data migrated successfully:

1. Validate the data in the upgraded data warehouse.

2. Check whether any of the Informatica mapping log files stored in the <INFA_HOME>\server\infa_shared\Sesslogs directory indicates errors or failures.

3. Check whether the following scripts that you ran in the SQL client of the database failed or errored out while executing:
7961_UPGRADE_DROP_INDEXES.sql

7961_UPGRADE_PRE_CTL_SCRIPT.sql

7961_UPGRADE_PRE_DIMENSION.sql

7961_UPGRADE_POST_SCRIPT.sql

4. Check the log files for the ddl_7961.ctl and Upgrade_7961.ctl scripts, which 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.

Note:

Ignore any error messages that indicate tables or indexes could not be dropped from the database. These error messages are displayed when the specified objects do not exist in the database. This can occur because each source system container holds a subset of all data warehouse tables

5. If the data migration was successful, drop the tables that were created during the upgrade process, such as W_xxxx_x_79x, LKP_xxxx_x and 79x_xxxx_TMP.
This step frees the space occupied by these backup tables.

6.9.8 Upgrading the Data Warehouse Schema From Version 7.9.6.1 to 7.9.6.2 and Migrating Data

Perform the procedures in this section to upgrade from Oracle BI Applications release 7.9.6.1 to 7.9.6.2.

This section contains the following procedures:

- Section 6.9.8.1, "Upgrading the Data Warehouse Schema to Version 7.9.6.2"

- Section 6.9.8.2, "Migrating Data into the Upgraded Data Warehouse"

- Section 6.9.8.3, "Verifying the Data Migrated Successfully"

6.9.8.1 Upgrading the Data Warehouse Schema to Version 7.9.6.2

Follow this procedure to upgrade the data warehouse schema to version 7.9.6.2.

To upgrade the data warehouse schema to version 7.9.6.2:

1. Generate the scripts to drop and create indexes. For instructions, see Section B.1, "Generating Scripts to Drop and Create Indexes for Upgrading to Release 7.9.6.2."

2. Run the script to drop all indexes. For instructions, see Section B.2, "Running the Script to Drop All Indexes for Upgrading to Release 7.9.6.2."

3. If you are using a SQL Server database, run the 7962_UPGRADE_PRE_UPG_CTL_SCRIPT.sql file. This file is located in OracleBI\dwrep\Upgrade\DbScripts\SQLServer.

4. Run the UPGRADE_7962.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

5. Run the 7962_UPGRADE_PRE_CTL_SCRIPT.sql. This file is located in the folder OracleBI\dwrep\Upgrade\DbScripts\<database type>.

6. Run the DDL_7962.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files.".

6.9.8.2 Migrating Data into the Upgraded Data Warehouse

Follow this procedure to migrate data into the upgraded data warehouse.

To migrate data into the upgraded data warehouse:

1. Run the 7962_UPGRADE_PRE_DIMENSION_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

2. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade repository. For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Upgrade Informatica Repository."

3. Configure the Informatica parameter file 7962_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7962_UPG_PARAMS.txt."

4. If you are upgrading Oracle Financial Analytics, do the following:

1. Configure application-specific parameters and update mappings. For instructions, see Section A.3.4, "Setting Parameters and Mappings in 7962_UPG_PARAMS.txt for Oracle Financial Analytics."

2. Make sure specific indexes are created. For instructions, see Appendix C, "Creating Indexes for Oracle Financial Analytics."

5. If you are using Oracle EBS R12, you need to configure specific parameters and update mappings for COGS. For instructions, see Appendix A, "Setting the COGS Fact Mapping for Oracle EBS R12."

6. Run the script to create ETL indexes. For instructions, see Section B.3, "Running the Scripts to Create ETL and Query Indexes for Upgrading to Release 7.9.6.2."

7. If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_ORA11i and execute the first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_ORAR12 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

8. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep). For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Base Informatica Repository."

9. Run the script to create Query indexes. For instructions, see Section B.3, "Running the Scripts to Create ETL and Query Indexes for Upgrading to Release 7.9.6.2."

6.9.8.3 Verifying the Data Migrated Successfully

Follow this procedure to verify that the data was migrated successfully into the upgraded data warehouse.

To verify the data migrated successfully:

1. Validate the data in the upgraded data warehouse.

2. Check whether any of the Informatica mapping log files stored in the <INFA_HOME>\server\infa_shared\Sesslogs directory indicates errors or failures.

3. Check whether the following scripts that you ran in the SQL client of the database failed or errored out while executing:
dropallindexes.sql

7962_UPGRADE_PRE_CTL_SCRIPT.sql

7962_UPGRADE_PRE_DIMENSION.sql

createETLIndexes.sql

createQueryIndexes.sql

4. Check the log files for the ddl_7962.ctl and Upgrade_7962.ctl scripts, which 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.

Note:

Ignore any error messages that indicate tables or indexes could not be dropped from the database. These error messages are displayed when the specified objects do not exist in the database. This can occur because each source system container holds a subset of all data warehouse tables

5. If the data migration was successful, drop the tables that were created during the upgrade process, such as W_xxxx_x_79x, LKP_xxxx_x and 79x_xxxx_TMP.
This step frees the space occupied by these backup tables.

6. Once the data migration steps above are complete, you can delete the Upgrade repository to avoid any accidental use or confusion.

1. In the Informatica Administrator, select the Upgrade repository service.

2. In the General Properties area of the Properties tab, click Edit.

3. Make sure the operating mode of the repository service is set to Exclusive.

4. Click OK.

5. Choose Actions, and then click Delete Contents.

6. In the Delete contents for <repository name> dialog, enter the repository username and password, and then click OK.

6.9.9 Upgrading the Data Warehouse Schema From Version 7.9.6.2 to 7.9.6.3 and Migrating Data

Perform the procedures in this section to upgrade from Oracle BI Applications release 7.9.6.2 to 7.9.6.3.

This section contains the following procedures:

- Section 6.9.9.1, "Upgrading the Data Warehouse Schema to Version 7.9.6.3"

- Section 6.9.9.2, "Migrating Data into the Upgraded Data Warehouse"

- Section 6.9.9.3, "Verifying the Data Migrated Successfully"

6.9.9.1 Upgrading the Data Warehouse Schema to Version 7.9.6.3

Follow this procedure to upgrade the data warehouse schema to version 7.9.6.3.

To upgrade the data warehouse schema to version 7.9.6.3

1. Generate the scripts to drop and create query indexes. For instructions, see Section B.4, "Generating Scripts to Drop and Create Query Indexes for Upgrading to Release 7.9.6.3."

2. Run the script to drop query indexes. For instructions, see Section B.5, "Running the Scripts to Drop and Create Query Indexes for Upgrading to Release 7.9.6.3."
Note: You must drop the query indexes before running the scripts to upgrade the schema.

3. If you are using a SQL Server database, run the 7963_UPGRADE_PRE_UPG_CTL_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\SQLServer.

4. Run the UPGRADE_7963.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

5. Run the 7963_UPGRADE_PRE_CTL_SCRIPT.sql script. This file is located in the folder OracleBI\dwrep\Upgrade\DbScripts\<database type>.

6. Run the DDL_7963.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

6.9.9.2 Migrating Data into the Upgraded Data Warehouse

Follow this procedure to migrate data into the upgraded data warehouse.

To migrate data into the upgraded data warehouse:

1. Run the 7963_UPGRADE_PRE_DIMENSION_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

2. Run the 7963_UPGRADE_DROP_ETLINDICES.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

3. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade repository. For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Upgrade Informatica Repository."

4. Configure the Informatica parameter file 7963_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt."

5. If you are upgrading Oracle Financial Analytics, do the following:

1. Set the parameters as specified in Appendix A, "Setting Parameters for All Source Systems."

2. If you are using Oracle EBS 11.5.10 family pack OIE.I or OIE.J, set the parameters as specified in Appendix A, "Setting Parameters Specific to Oracle EBS 11.5.10 Family Pack OIE.I and OIE.J."

6. If you are upgrading Oracle Human Resources Analytics, set the parameters as specified in Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt for Oracle Human Resources Analytics."

7. If you are upgrading Oracle Procurement and Spend Analytics, set the parameters as specified in Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt for Oracle Procurement and Spend Analytics on Oracle EBS 11i and 12 Source Systems."

8. If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_7962_to_7963_ORA11i and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using Oracle EBS R12x, in Informatica Workflow Manager, navigate to the folder UPGRADE_7962_to_7963_ORAR12 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

9. Upgrade geography-related attributes if necessary for your environment:

1. Determine whether a geography-related upgrade is necessary by executing the following query:

SELECT COUNT(1) as row_count,'0' as X_CUSTOM FROM W_GEO_D_7963 WHERE COUNTRY LIKE '% 'OR COUNTRY LIKE ' %'OR STATE_PROV LIKE '% 'OR STATE_PROV LIKE ' %'OR CITY LIKE '% 'OR CITY LIKE ' %'OR ZIPCODE LIKE '% 'OR ZIPCODE LIKE ' %'

2. If the query returns a count greater than zero, run the 7963_UPGRADE_POST_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.
If the query returns a count of zero, you do not need to run the 7963_UPGRADE_POST_SCRIPT.sql script.

10. Run the 7963_UPGRADE_CREATE_ETLINDICES.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

11. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep). For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Base Informatica Repository."

12. Run the createQueryIndices.sql script. For instructions, see Section B.5, "Running the Scripts to Drop and Create Query Indexes for Upgrading to Release 7.9.6.3."

6.9.9.3 Verifying the Data Migrated Successfully

Follow this procedure to verify that the data was migrated successfully into the upgraded data warehouse.

To verify the data migrated successfully:

1. Validate the data in the upgraded data warehouse.

2. Check whether any of the Informatica mapping log files stored in the <INFA_HOME>\server\infa_shared\Sesslogs directory indicates errors or failures.

3. Check whether the following scripts that you ran in the SQL client of the database failed or errored out while executing:
7963_UPGRADE_PRE_CTL_SCRIPT.sql

7963_UPGRADE_PRE_DIMENSION.sql

7963_UPGRADE_DROP_ETLINDICES.sql

7963_UPGRADE CREATE_ETLINDICES.sql

dropQueryIndices.sql

createQueryIndices.sql

4. Check the log files for the ddl_7963.ctl and Upgrade_7963.ctl scripts, which 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.

Note:

Ignore any error messages that indicate tables or indexes could not be dropped from the database. These error messages are displayed when the specified objects do not exist in the database. This can occur because each source system container holds a subset of all data warehouse tables

5. If the data migration was successful, drop the tables that were created during the upgrade process, such as W_xxxx_x_79x, LKP_xxxx_x and 79x_xxxx_TMP.
This step frees the space occupied by these backup tables.

6. Once the data migration steps above are complete, you can delete the Upgrade repository to avoid any accidental use or confusion.

1. In the Informatica Administrator, select the Upgrade repository service.

2. In the General Properties area of the Properties tab, click Edit.

3. Make sure the operating mode of the repository service is set to Exclusive.

4. Click OK.

5. Choose Actions, and then click Delete Contents.

6. In the Delete contents for <repository name> dialog, enter the repository username and password, and then click OK.

6.9.10 Upgrading the Data Warehouse Schema From Version 7.9.6.3 to 7.9.6.4 and Migrating Data

Perform the procedures in this section to upgrade from Oracle BI Applications release 7.9.6.3 to 7.9.6.4.

This section contains the following procedures:

- Section 6.9.10.1, "Upgrading the Data Warehouse Schema to Version 7.9.6.4"

- Section 6.9.10.2, "Migrating Data into the Upgraded Data Warehouse"

- Section 6.9.10.3, "Verifying the Data Migrated Successfully"

6.9.10.1 Upgrading the Data Warehouse Schema to Version 7.9.6.4

Follow this procedure to upgrade the data warehouse schema to version 7.9.6.4.

To upgrade the data warehouse schema to version 7.9.6.4:

1. If you are using a DB2 database, run siebproc.sql. This file is located in OracleBI\dwrep\siebproc\db2udb.

2. Generate the scripts to drop and create query indexes. For instructions, see Section B.6, "Generating Scripts to Drop and Create Query and ETL Indexes for Upgrading to Release 7.9.6.4."

3. Run the script to drop query indexes. For instructions, see Section B.7, "Running the Scripts to Drop and Create Query Indexes for Upgrading to Release 7.9.6.4."
Note: You must drop the query indexes before running the scripts to upgrade the schema.

4. If you are using a SQL Server database, run the 7964_UPGRADE_PRE_UPG_CTL_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\SQLServer.

5. Run the UPGRADE_7964.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

6. Run the 7964_UPGRADE_PRE_CTL_SCRIPT.sql script. This file is located in the folder OracleBI\dwrep\Upgrade\DbScripts\<database type>.

7. Run the DDL_7964.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

6.9.10.2 Migrating Data into the Upgraded Data Warehouse

Follow this procedure to migrate data into the upgraded data warehouse.

To migrate data into the upgraded data warehouse:

1. Run the 7964_UPGRADE_PRE_DIMENSION_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

2. Run the script to drop ETL indexes. For instructions, see Section B.8, "Running the Scripts to Drop and Create ETL Indexes for Upgrading to Release 7.9.6.4."

3. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade repository. For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Upgrade Informatica Repository."

4. Configure the Informatica parameter file 7964_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7964_UPG_PARAMS.txt."

5. If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_7963_to_7964_ORA11i and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using Oracle EBS R12x, in Informatica Workflow Manager, navigate to the folder UPGRADE_7963_to_7964_ORAR12 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

6. If you are upgrading the Oracle Human Resource Analytics Workforce module, you must perform a full load of data. To complete this step you will set the refresh dates to NULL for the Workforce-related tables.

1. Log into DAC.

2. Go to the Physical Data Sources tab in the Setup view.

3. In the top pane window, select the appropriate data warehouse connection.

4. Go to the Refresh Dates subtab.

5. Reset the refresh date to Null for the following tables by clicking in the Refresh Date column, displaying the Date dialog, and clicking Null. Click Save for each record.
W_ORA_SUPV_STATUS_PS

W_ORA_WEVT_ASG_PS

W_ORA_WEVT_FTE_PS

W_ORA_WEVT_HDC_PS

W_ORA_WEVT_PERF_PS

W_ORA_WEVT_PTYP_PS

W_ORA_WEVT_SAL_PS

W_PSFT_POSN_HLDR_PS

W_PSFT_POSN_WRKR_PS

W_PSFT_SUPV_STATUS_PS

W_PSFT_SUPV_WRKR_PS

W_PSFT_WEVT_AGE_PS

W_PSFT_WEVT_IASG_PS

W_PSFT_WEVT_JOB_PS

W_PSFT_WEVT_PERF_PS

W_WRKFC_EVT_FS

W_WRKFC_EVT_F

W_WRKFC_EVT_MERGE_F

W_WRKFC_EVT_MONTH_F

W_WRKFC_EVT_POW_F

W_WRKFC_EVT_AGE_F

W_WRKFC_EVT_A

W_WRKFC_BAL_A

W_WRKFC_EVENT_GROUP_D

W_WRKFC_EVENT_TYPE_D

7. If you are upgrading the Oracle Human Resource Analytics Recruitment module, do the following:

1. Execute the following SQL statement to clean the data:

DELETE FROM W_RCRTMNT_EVENT_F
WHERE RCRTMNT_EVENT_CLASS = 'JOB_RQSTN'
AND DATASOURCE_NUM_ID IN <>

2. Run the following upgrade map worklet:

HumanResourceAnalytics_Recruitment_JobRequisitions_UPG7964

8. Run the 7964_UPGRADE_POST_SCRIPT.sql. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

9. Run the script to create ETL indexes. For instructions, see Section B.8, "Running the Scripts to Drop and Create ETL Indexes for Upgrading to Release 7.9.6.4."

10. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep). For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Base Informatica Repository."

6.9.10.3 Verifying the Data Migrated Successfully

Follow this procedure to verify that the data was migrated successfully into the upgraded data warehouse.

To verify the data migrated successfully:

1. Validate the data in the upgraded data warehouse.

2. Check whether any of the Informatica mapping log files stored in the <INFA_HOME>\server\infa_shared\Sesslogs directory indicates errors or failures.

3. Check whether the following scripts that you ran in the SQL client of the database failed or errored out while executing:
7964_UPGRADE_PRE_CTL_SCRIPT.sql

7964_UPGRADE_PRE_DIMENSION.sql

dropEtlIndices.sql

createEtlIndices.sql

dropQueryIndices.sql

createQueryIndices.sql

4. Check the log files for the ddl_7964.ctl and Upgrade_7964.ctl scripts, which 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.

Note:

Ignore any error messages that indicate tables or indexes could not be dropped from the database. These error messages are displayed when the specified objects do not exist in the database. This can occur because each source system container holds a subset of all data warehouse tables

5. If the data migration was successful, drop the tables that were created during the upgrade process, such as W_xxxx_x_79x, LKP_xxxx_x and 79x_xxxx_TMP.
This step frees the space occupied by these backup tables.

6. Once the data migration steps above are complete, you can delete the Upgrade repository to avoid any accidental use or confusion.

1. In the Informatica Administrator, select the Upgrade repository service.

2. In the General Properties area of the Properties tab, click Edit.

3. Make sure the operating mode of the repository service is set to Exclusive.

4. Click OK.

5. Choose Actions, and then click Delete Contents.

6. In the Delete contents for <repository name> dialog, enter the repository username and password, and then click OK.

6.10 Upgrading the Data Warehouse Schema and Migrating Data for Teradata Databases

If your data warehouse database platform is Teradata, you can upgrade to Oracle BI Applications version 7.9.6.4 from Oracle BI Applications 7.9.x.

This section includes the following topics:

- Section 6.10.1, "Upgrading Oracle BI Applications From Version 7.9.0 to 7.9.6.4"

- Section 6.10.2, "Upgrading Oracle BI Applications From Version 7.9.3 to 7.9.6.4"

- Section 6.10.3, "Upgrading Oracle BI Applications From Version 7.9.4 to 7.9.6.4"

- Section 6.10.4, "Upgrading Oracle BI Applications From Version 7.9.5 to 7.9.6.4"

- Section 6.10.5, "Upgrading Oracle BI Applications From Version 7.9.5.1 to 7.9.6.4"

- Section 6.10.6, "Upgrading Oracle BI Applications From Version 7.9.6.1 to 7.9.6.4"

- Section 6.10.7, "Upgrading Oracle BI Applications From Version 7.9.6.2 to 7.9.6.4"

- Section 6.10.8, "Upgrading Oracle BI Applications From Version 7.9.6.3 to 7.9.6.4"

6.10.1 Upgrading Oracle BI Applications From Version 7.9.0 to 7.9.6.4

Follow this procedure to upgrade from Oracle BI Applications version 7.9.0 to version 7.9.6.4 if your data warehouse database platform is Teradata.

To upgrade the data warehouse schema and migrate data for a Teradata database:

1. Execute the following scripts:

- 793_UPGRADE_TMP_TABLES.sql

- 794_UPGRADE_TMP_TABLES.sql

- 795_UPGRADE_TMP_TABLES.sql

- 7951_UPGRADE_TMP_TABLES.sql

- 7961_UPGRADE_TMP_TABLES.sql

- 7962_UPGRADE_TMP_TABLES.sql

- 7963_UPGRADE_TMP_TABLES.sql

- 7964_UPGRADE_TMP_TABLES.sql

1. Open the SQL client for your database type.

2. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.

3. Open the <version>_UPGRADE_TMP_TABLES.sql file, and copy the contents into the SQL client.

4. Execute the script.

2. Edit and execute the 793_RENAME_AND_EXCEPTIONS.sql script.

1. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.

2. Open the 793_RENAME_AND_EXCEPTIONS.sql script.

3. Search for the following statements to locate columns with RENAME commands.
ALTER TABLE <Table_Name> RENAME <Column Name> TO <New Column Name>;

4. For all columns with RENAME commands, check to see whether any COLUMN STATISTICS are defined on them.

5. For all columns that have STATISTICS defined on them, back up the COLUMN STATISTICS definition and then drop them.

6. Execute the 793_RENAME_AND_EXCEPTIONS.sql script.

7. Recreate STATISTICS on any column on which they were dropped.

3. The teradata.missing.defaults.properties file contains global default column values for data warehouse tables with NOT NULL columns for which default values are not specified in DAC. You can change the default values specified in the teradata.missing.defaults.properties file to match your environment. The file is located in \bifoundation\dac\conf\sqlgen\sql\teradata.

4. Generate upgrade scripts from DAC.

1. Log into DAC.

2. From the menu bar, select Tools, then ETL Management, and then Configure.

3. In the Sources dialog box, select Teradata as the target data warehouse database platform, and select the appropriate source data warehouse database platform.
The Configuration tab of the Data Warehouse Configuration Wizard is active.

4. Select "Generate upgrade statements for Data Warehouse Tables," and click Next.
The Data Warehouse SQL tab is active.

5. Do the following:
- Select the appropriate physical data source name for the Teradata database.

- In the container field, enter a custom container name for which you want to generate upgrade scripts. Alternatively, leave the field blank to generate upgrade scripts for all containers.

The Data Warehouse Configuration Wizard generates the following files and stores them in \bifoundation\DAC\conf\sqlgen\sql\teradata:

upgrade-regular.sql. This file contains scripts that DAC has verified are necessary to upgrade the data warehouse schema. The scripts handle new or altered tables and columns. For example, they may increase the size of simple data types or change a column from null to not null.

upgrade-questionable.sql. This file contains scripts that DAC suggests may be required to upgrade the data warehouse schema. These scripts are intended to be an aid in determining upgrade requirements and must be reviewed by a Teradata DBA and corrected if necessary.

upgradedwtables_sql.log. This file is the log file that corresponds to the upgrade-regular.sql file. It is for information purposes only.

upgrade-issues.log. This file is the log file that corresponds to the file upgrade-questionable.sql. It is for information purposes only.

6. Open the upgrade-regular.sql and upgrade-questionable.sql files, and search for the following statement to locate columns that have been added or changed.
ALTER TABLE <Table Name> ADD <Column Name><attributes>;

7. For all columns with the ADD command, check to see whether any columns exist already, and if they do, check whether they have STATISTICS defined on them.

8. For all columns that have STATISTICS defined on them, back up the column definition and then drop the STATISTICS.

9. Execute the scripts in the upgrade-regular.sql file.

10. Review the scripts in the upgrade-questionable.sql file. Edit the scripts as needed, and execute them.

11. Recreate STATISTICS on any column on which they were dropped.

5. Execute the following scripts:

- 794_UPDATE_DEFAULTS.sql

- 795_UPDATE_DEFAULTS.sql

- 7951_UPDATE_DEFAULTS.sql

- 7961_UPDATE_DEFAULTS.sql

- 7962_UPDATE_DEFAULTS.sql

- 7963_UPDATE_DEFAULTS.sql

- 7964_UPDATE_DEFAULTS.sql

6. Execute the 793_Backup Tables.sql script.

7. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

8. Configure the Informatica parameter file 793_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 793_UPG_PARAMS.txt."

9. In Informatica Workflow Manager, navigate to the folder UPGRADE_790_to_793 and run the Update_Dimensions workflow, and then run the Update_Facts workflow.

10. If you are using the Oracle EBS 11.5.10 source system, navigate to the folder UPGRADE_790_to_793_ORA11510, and run the SIL_PurchaseAmount_Patch workflow.

11. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

12. Execute the 794_Backup Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

13. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

14. Configure the Informatica parameter file 794_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 794_UPG_PARAMS.txt."

15. In Informatica Workflow Manager, navigate to the folder UPGRADE_793_to_794_ORA11i and execute the UPGRADE_DIMENSIONS and UPGRADE_FACTS workflows.

16. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

17. Execute the 795_Backup Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata

18. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

19. Configure the Informatica parameter file 795_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 795_UPG_PARAMS.txt."

20. If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_794_to_795_ORA11i and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_794_to_795_ORAR12 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

21. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

22. Execute the 7951_Backup Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

23. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade repository. For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Upgrade Informatica Repository."

24. Configure the Informatica parameter file 7951_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7951_UPG_PARAMS.txt."

25. If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_795_to_7951_ORA11i and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_795_to_7951_ORAR12 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

26. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

27. Execute the 796_Backup Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

28. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

29. Configure the Informatica parameter file 796_UPG_PARAMS.txt file. For instructions, see Appendix A, "Setting Parameters in 796_UPG_PARAMS.txt."

30. If you are using Oracle EBS 11i, configure parameters specific to Oracle 11i source systems. For instructions, see Appendix A, "Setting Parameters in 796_UPG_PARAMS.txt for Oracle EBS 11i Source Systems."

31. If you are upgrading Oracle Financial Analytics, you need to configure specific parameters and update mappings. For more information, see Appendix A, "Setting Parameters and Mappings in 796_UPG_PARAMS.txt for Oracle Financial Analytics."

32. If you are upgrading Oracle Supply Chain and Order Management Analytics, you need to configure specific parameters. For more information, see Appendix A, "Setting Parameters in 796_UPG_PARAMS.txt for Oracle Supply Chain and Order Management Analytics."

33. If you are deploying Oracle Project Analytics, you need to configure specific parameters. For more information, see Appendix A, "Setting Parameters in 796_UPG_PARAMS.txt for Oracle Project Analytics."

34. Back up and truncate the table W_POSITION_DH.

35. If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_7951_to_796_ORA11i and execute the following workflows in the order specified below:

- UPGRADE_DIMENSIONS

- UPGRADE_FACTS

- RESET_DAC_REFRESH_DATES

36. If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_7951_to_796_ORAR12 and execute the following workflows in the order specified below:

- UPGRADE_DIMENSIONS

- UPGRADE_FACTS

- RESET_DAC_REFRESH_DATES

37. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

38. Execute the 7961_Backup Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

39. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

40. Configure the Informatica parameter file 7961_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7961_UPG_PARAMS.txt."

41. If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_796_to_7961_ORA11i and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_796_to_7961_ORAR12 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

42. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

43. Execute the 7962_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

44. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

45. Configure the Informatica parameter file 7962_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7962_UPG_PARAMS.txt."

46. If you are upgrading Oracle Financial Analytics, do the following:

1. Configure application-specific parameters and update mappings. For instructions, see Section A.3.4, "Setting Parameters and Mappings in 7962_UPG_PARAMS.txt for Oracle Financial Analytics."

2. Make sure specific indexes are created. For instructions, see Appendix C, "Creating Indexes for Oracle Financial Analytics."

47. If you are using Oracle EBS R12, you need to configure specific parameters and update mappings for COGS. For instructions, see Section A.3.4.4, "Setting the COGS Fact Mapping for Oracle EBS R12."

48. If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_ORA11i and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_ORAR12 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

49. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

50. Execute the 7963_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

51. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

52. Configure the Informatica parameter file 7963_UPG_PARAMS.txt. For instructions, see Section A.1.8, "Setting Parameters in 7963_UPG_PARAMS.txt."

53. If you are upgrading Oracle Financial Analytics, do the following:

1. Set the parameters as specified in Appendix A, "Setting Parameters for All Source Systems."

2. If you are using Oracle EBS 11.5.10 family pack OIE.I or OIE.J, set the parameters as specified in Appendix A, "Setting Parameters Specific to Oracle EBS 11.5.10 Family Pack OIE.I and OIE.J."

54. If you are upgrading Oracle Human Resources Analytics, set the parameters as specified in Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt for Oracle Human Resources Analytics."

55. If you are upgrading Oracle Procurement and Spend Analytics, set the parameters as specified in Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt for Oracle Procurement and Spend Analytics on Oracle EBS 11i and 12 Source Systems."

56. If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_7962_to_7963_ORA11i and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_7962_to_7963_ORAR12 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

57. Upgrade geography-related attributes if necessary for your environment:

1. Determine whether a geography-related upgrade is necessary by executing the following query:

SELECT COUNT(1) as row_count,'0' as X_CUSTOM FROM W_GEO_D_7963 WHERE COUNTRY LIKE '% 'OR COUNTRY LIKE ' %'OR STATE_PROV LIKE '% 'OR STATE_PROV LIKE ' %'OR CITY LIKE '% 'OR CITY LIKE ' %'OR ZIPCODE LIKE '% 'OR ZIPCODE LIKE ' %'

2. If the query returns a count greater than zero, run the 7963_UPGRADE_POST_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.
If the query returns a count of zero, you do not need to run the 7963_UPGRADE_POST_SCRIPT.sql script.

58. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

59. Execute the 7964_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

60. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

61. Configure the Informatica parameter file 7964_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7964_UPG_PARAMS.txt."

62. If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_7963_to_7964_ORA11i and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_7963_to_7964_ORAR12 and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.

63. Run the 7964_UPGRADE_POST_SCRIPT.sql. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

64. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

65. In DAC, do the following:

1. Navigate to the Setup view, and click the Physical Data Sources tab.

2. In the top pane list, select DataWarehouse. (If you customized the name of the connection for the data warehouse, select the appropriate connection for the data warehouse database.)

3. Click the Refresh Dates subtab (in the lower pane).

4. Query for the FND_LOOKUP_VALUES table, and set the value in the Refresh Date column to NULL.

66. Once the data migration steps above are complete, you can delete the Upgrade repository to avoid any accidental use or confusion.

1. In the Informatica Administrator, select the Upgrade repository service.

2. In the General Properties area of the Properties tab, click Edit.

3. Make sure the operating mode of the repository service is set to Exclusive.

4. Click OK.

5. Choose Actions, and then click Delete Contents.

6. In the Delete contents for <repository name> dialog, enter the repository username and password, and then click OK.

6.10.2 Upgrading Oracle BI Applications From Version 7.9.3 to 7.9.6.4

Follow this procedure to upgrade from Oracle BI Applications version 7.9.3 to version 7.9.6.4 if your data warehouse database platform is Teradata.

To upgrade the data warehouse schema and migrate data for a Teradata database:

1. Execute the following scripts:

- 794_UPGRADE_TMP_TABLES.sql

- 795_UPGRADE_TMP_TABLES.sql

- 7951_UPGRADE_TMP_TABLES.sql

- 7961_UPGRADE_TMP_TABLES.sql

- 7962_UPGRADE_TMP_TABLES.sql

- 7963_UPGRADE_TMP_TABLES.sql

- 7964_UPGRADE_TMP_TABLES.sql

1. Open the SQL client for your database type.

2. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.

3. Open the <version>_UPGRADE_TMP_TABLES.sql file, and copy the contents into the SQL client.

4. Execute the script.

2. Edit and execute the 794_RENAME_AND_EXCEPTIONS.sql script.

1. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.

2. Open the 794_RENAME_AND_EXCEPTIONS.sql script.

3. Search for the following statements to locate columns with RENAME commands.
ALTER TABLE <Table_Name> RENAME <Column Name> TO <New Column Name>;

4. For all columns with RENAME commands, check to see whether any COLUMN STATISTICS are defined on them.

5. For all columns that have STATISTICS defined on them, back up the COLUMN STATISTICS definition and then drop them.

6. Execute the 794_RENAME_AND_EXCEPTIONS.sql script.

7. Recreate STATISTICS on any column on which they were dropped.

3. The teradata.missing.defaults.properties file contains global default column values for data warehouse tables with NOT NULL columns for which default values are not specified in DAC. You can change the default values specified in the teradata.missing.defaults.properties file to match your environment. The file is located in \bifoundation\dac\conf\sqlgen\sql\teradata.

4. Generate upgrade scripts from DAC.

1. Log into DAC.

2. From the menu bar, select Tools, then ETL Management, and then Configure.

3. In the Sources dialog box, select Teradata as the target data warehouse database platform, and select the appropriate source data warehouse database platform.
The Configuration tab of the Data Warehouse Configuration Wizard is active.

4. Select "Generate upgrade statements for Data Warehouse Tables," and click Next.
The Data Warehouse SQL tab is active.

5. Do the following:
- Select the appropriate physical data source name for the Teradata database.

- In the container field, enter a custom container name for which you want to generate upgrade scripts. Alternatively, leave the field blank to generate upgrade scripts for all containers.

The Data Warehouse Configuration Wizard generates the following files and stores them in \bifoundation\DAC\conf\sqlgen\sql\teradata:

upgrade-regular.sql. This file contains scripts that DAC has verified are necessary to upgrade the data warehouse schema. The scripts handle new or altered tables and columns. For example, they may increase the size of simple data types or change a column from null to not null.

upgrade-questionable.sql. This file contains scripts that DAC suggests may be required to upgrade the data warehouse schema. These scripts are intended to be an aid in determining upgrade requirements and must be reviewed by a Teradata DBA and corrected if necessary.

upgradedwtables_sql.log. This file is the log file that corresponds to the upgrade-regular.sql file. It is for information purposes only.

upgrade-issues.log. This file is the log file that corresponds to the file upgrade-questionable.sql. It is for information purposes only.

6. Open the upgrade-regular.sql and upgrade-questionable.sql files, and search for the following statement to locate columns that have been added or changed.
ALTER TABLE <Table Name> ADD <Column Name><attributes>;

7. For all columns with the ADD command, check to see whether any columns exist already, and if they do, check whether they have STATISTICS defined on them.

8. For all columns that have STATISTICS defined on them, back up the column definition and then drop the STATISTICS.

9. Execute the scripts in the upgrade-regular.sql file.

10. Review the scripts in the upgrade-questionable.sql file. Edit the scripts as needed, and execute them.

11. Recreate STATISTICS on any column on which they were dropped.

5. Execute the following scripts:

- 794_UPDATE_DEFAULTS.sql

- 795_UPDATE_DEFAULTS.sql

- 7951_UPDATE_DEFAULTS.sql

- 7961_UPDATE_DEFAULTS.sql

- 7962_UPDATE_DEFAULTS.sql

- 7963_UPDATE_DEFAULTS.sql

- 7964_UPDATE_DEFAULTS.sql

6. Execute the 794_Backup Tables.sql script.

7. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

8. Configure the Informatica parameter file 794_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 794_UPG_PARAMS.txt."

9. In Informatica Workflow Manager, navigate to the folder UPGRADE_793_to_794_ORA11i and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

10. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

11. Execute the 795_Backup Tables.sql script.

12. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

13. Configure the Informatica parameter file 795_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 795_UPG_PARAMS.txt."

14. If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_794_to_795_ORA11i and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_794_to_795_ORAR12 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

15. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

16. Execute the 7951_Backup Tables.sql script.

17. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

18. Configure the Informatica parameter file 7951_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7951_UPG_PARAMS.txt."

19. If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_795_to_7951_ORA11i and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_795_to_7951_ORAR12 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

20. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

21. Execute the 796_Backup Tables.sql script.

22. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

23. Configure the Informatica parameter file 796_UPG_PARAMS.txt file. For instructions, see Appendix A, "Setting Parameters in 796_UPG_PARAMS.txt."

24. If you are using Oracle EBS 11i, configure parameters specific to Oracle 11i source systems. For instructions, see Appendix A, "Setting Parameters in 796_UPG_PARAMS.txt for Oracle EBS 11i Source Systems."

25. If you are upgrading Oracle Financial Analytics, you need to configure specific parameters and update mappings. For more information, see Appendix A, "Setting Parameters and Mappings in 796_UPG_PARAMS.txt for Oracle Financial Analytics."

26. If you are upgrading Oracle Supply Chain and Order Management Analytics, you need to configure specific parameters. For more information, see Appendix A, "Setting Parameters in 796_UPG_PARAMS.txt for Oracle Supply Chain and Order Management Analytics."

27. If you are deploying Oracle Project Analytics, you need to configure specific parameters. For more information, see Appendix A, "Setting Parameters in 796_UPG_PARAMS.txt for Oracle Project Analytics."

28. Back up and truncate the table W_POSITION_DH.

29. If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_7951_to_796_ORA11i and execute the following workflows in the order specified below:

- UPGRADE_DIMENSIONS

- UPGRADE_FACTS

- RESET_DAC_REFRESH_DATES

30. If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_7951_to_796_ORAR12 and execute the following workflows in the order specified below:

- UPGRADE_DIMENSIONS

- UPGRADE_FACTS

- RESET_DAC_REFRESH_DATES

31. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

32. Execute the 7961_Backup Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

33. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

34. Configure the Informatica parameter file 7961_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7961_UPG_PARAMS.txt."

35. If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_796_to_7961_ORA11i and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_796_to_7961_ORAR12 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

36. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

37. Execute the 7962_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

38. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade repository.

39. Configure the Informatica parameter file 7962_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7962_UPG_PARAMS.txt."

40. If you are upgrading Oracle Financial Analytics, do the following:

1. Configure application-specific parameters and update mappings. For instructions, see Section A.3.4, "Setting Parameters and Mappings in 7962_UPG_PARAMS.txt for Oracle Financial Analytics."

2. Make sure specific indexes are created. For instructions, see Appendix C, "Creating Indexes for Oracle Financial Analytics."

41. If you are using Oracle EBS R12, you need to configure specific parameters and update mappings for COGS. For instructions, see Section A.3.4.4, "Setting the COGS Fact Mapping for Oracle EBS R12."

42. If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_ORA11i and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_ORAR12 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

43. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

44. Execute the 7963_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

45. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

46. Configure the Informatica parameter file 7963_UPG_PARAMS.txt. For instructions, see Section A.1.8, "Setting Parameters in 7963_UPG_PARAMS.txt."

47. If you are upgrading Oracle Financial Analytics, do the following:

1. Set the parameters as specified in Appendix A, "Setting Parameters for All Source Systems."

2. If you are using Oracle EBS 11.5.10 family pack OIE.I or OIE.J, set the parameters as specified in Appendix A, "Setting Parameters Specific to Oracle EBS 11.5.10 Family Pack OIE.I and OIE.J."

48. If you are upgrading Oracle Human Resources Analytics, set the parameters as specified in Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt for Oracle Human Resources Analytics."

49. If you are upgrading Oracle Procurement and Spend Analytics, set the parameters as specified in Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt for Oracle Procurement and Spend Analytics on Oracle EBS 11i and 12 Source Systems."

50. If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_7962_to_7963_ORA11i and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_7962_to_7963_ORAR12 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

51. Upgrade geography-related attributes if necessary for your environment:

1. Determine whether a geography-related upgrade is necessary by executing the following query:

SELECT COUNT(1) as row_count,'0' as X_CUSTOM FROM W_GEO_D_7963 WHERE COUNTRY LIKE '% 'OR COUNTRY LIKE ' %'OR STATE_PROV LIKE '% 'OR STATE_PROV LIKE ' %'OR CITY LIKE '% 'OR CITY LIKE ' %'OR ZIPCODE LIKE '% 'OR ZIPCODE LIKE ' %'

2. If the query returns a count greater than zero, run the 7963_UPGRADE_POST_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.
If the query returns a count of zero, you do not need to run the 7963_UPGRADE_POST_SCRIPT.sql script.

52. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

53. Execute the 7964_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

54. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

55. Configure the Informatica parameter file 7964_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7964_UPG_PARAMS.txt."

56. If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_7963_to_7964_ORA11i and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_7963_to_7964_ORAR12 and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.

57. Run the 7964_UPGRADE_POST_SCRIPT.sql. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

58. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

59. In DAC, do the following:

1. Navigate to the Setup view, and click the Physical Data Sources tab.

2. In the top pane list, select DataWarehouse. (If you customized the name of the connection for the data warehouse, select the appropriate connection for the data warehouse database.)

3. Click the Refresh Dates subtab (in the lower pane).

4. Query for the FND_LOOKUP_VALUES table, and set the value in the Refresh Date column to NULL.

60. Once the data migration steps above are complete, you can delete the Upgrade repository to avoid any accidental use or confusion.

1. In the Informatica Administrator, select the Upgrade repository service.

2. In the General Properties area of the Properties tab, click Edit.

3. Make sure the operating mode of the repository service is set to Exclusive.

4. Click OK.

5. Choose Actions, and then click Delete Contents.

6. In the Delete contents for <repository name> dialog, enter the repository username and password, and then click OK.

6.10.3 Upgrading Oracle BI Applications From Version 7.9.4 to 7.9.6.4

Follow this procedure to upgrade from Oracle BI Applications version 7.9.4 to version 7.9.6.4 if your data warehouse database platform is Teradata.

To upgrade the data warehouse schema and migrate data for a Teradata database:

1. Execute the following scripts:

- 795_UPGRADE_TMP_TABLES.sql

- 7951_UPGRADE_TMP_TABLES.sql

- 7961_UPGRADE_TMP_TABLES.sql

- 7962_UPGRADE_TMP_TABLES.sql

- 7963_UPGRADE_TMP_TABLES.sql

- 7964_UPGRADE_TMP_TABLES.sql

1. Open the SQL client for your database type.

2. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.

3. Open the <version>_UPGRADE_TMP_TABLES.sql file, and copy the contents into the SQL client.

4. Execute the script.

2. Edit and execute the 795_RENAME_AND_EXCEPTIONS.sql script.

1. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.

2. Open the 795_RENAME_AND_EXCEPTIONS.sql script.

3. Search for the following statements to locate columns with RENAME commands.
ALTER TABLE <Table_Name> RENAME <Column Name> TO <New Column Name>;

4. For all columns with RENAME commands, check to see whether any COLUMN STATISTICS are defined on them.

5. For all columns that have STATISTICS defined on them, back up the COLUMN STATISTICS definition and then drop them.

6. Execute the 795_RENAME_AND_EXCEPTIONS.sql script.

7. Recreate STATISTICS on any column on which they were dropped.

3. The teradata.missing.defaults.properties file contains global default column values for data warehouse tables with NOT NULL columns for which default values are not specified in DAC. You can change the default values specified in the teradata.missing.defaults.properties file to match your environment. The file is located in \bifoundation\dac\conf\sqlgen\sql\teradata.

4. Generate upgrade scripts from DAC.

1. Log into DAC.

2. From the menu bar, select Tools, then ETL Management, and then Configure.

3. In the Sources dialog box, select Teradata as the target data warehouse database platform, and select the appropriate source data warehouse database platform.
The Configuration tab of the Data Warehouse Configuration Wizard is active.

4. Select "Generate upgrade statements for Data Warehouse Tables," and click Next.
The Data Warehouse SQL tab is active.

5. Do the following:
- Select the appropriate physical data source name for the Teradata database.

- In the container field, enter a custom container name for which you want to generate upgrade scripts. Alternatively, leave the field blank to generate upgrade scripts for all containers.

The Data Warehouse Configuration Wizard generates the following files and stores them in \bifoundation\DAC\conf\sqlgen\sql\teradata:

upgrade-regular.sql. This file contains scripts that DAC has verified are necessary to upgrade the data warehouse schema. The scripts handle new or altered tables and columns. For example, they may increase the size of simple data types or change a column from null to not null.

upgrade-questionable.sql. This file contains scripts that DAC suggests may be required to upgrade the data warehouse schema. These scripts are intended to be an aid in determining upgrade requirements and must be reviewed by a Teradata DBA and corrected if necessary.

upgradedwtables_sql.log. This file is the log file that corresponds to the upgrade-regular.sql file. It is for information purposes only.

upgrade-issues.log. This file is the log file that corresponds to the file upgrade-questionable.sql. It is for information purposes only.

6. Open the upgrade-regular.sql and upgrade-questionable.sql files, and search for the following statement to locate columns that have been added or changed.
ALTER TABLE <Table Name> ADD <Column Name><attributes>;

7. For all columns with the ADD command, check to see whether any columns exist already, and if they do, check whether they have STATISTICS defined on them.

8. For all columns that have STATISTICS defined on them, back up the column definition and then drop the STATISTICS.

9. Execute the scripts in the upgrade-regular.sql file.

10. Review the scripts in the upgrade-questionable.sql file. Edit the scripts as needed, and execute them.

11. Recreate STATISTICS on any column on which they were dropped.

5. Execute the following scripts:

- 795_UPDATE_DEFAULTS.sql

- 7951_UPDATE_DEFAULTS.sql

- 7961_UPDATE_DEFAULTS.sql

- 7962_UPDATE_DEFAULTS.sql

- 7963_UPDATE_DEFAULTS.sql

- 7964_UPDATE_DEFAULTS.sql

6. Execute the 795_Backup Tables.sql script.

7. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

8. Configure the Informatica parameter file 795_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 795_UPG_PARAMS.txt."

9. If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_794_to_795_ORA11i and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_794_to_795_ORAR12 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

10. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

11. Execute the 7951_Backup Tables.sql script.

12. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

13. Configure the Informatica parameter file 7951_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7951_UPG_PARAMS.txt."

14. If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_795_to_7951_ORA11i and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_795_to_7951_ORAR12 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

15. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

16. Execute the 796_Backup Tables.sql script.

17. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

18. Configure the Informatica parameter file 796_UPG_PARAMS.txt file. For instructions, see Appendix A, "Setting Parameters in 796_UPG_PARAMS.txt."

19. If you are using Oracle EBS 11i, configure parameters specific to Oracle 11i source systems. For instructions, see Appendix A, "Setting Parameters in 796_UPG_PARAMS.txt for Oracle EBS 11i Source Systems."

20. If you are upgrading Oracle Financial Analytics, you need to configure specific parameters and update mappings. For more information, see Appendix A, "Setting Parameters and Mappings in 796_UPG_PARAMS.txt for Oracle Financial Analytics."

21. If you are upgrading Oracle Supply Chain and Order Management Analytics, you need to configure specific parameters. For more information, see Section A.3.3, "Setting Parameters in 796_UPG_PARAMS.txt for Oracle Supply Chain and Order Management Analytics."

22. If you are deploying Oracle Project Analytics, you need to configure specific parameters. For more information, see Section A.3.2, "Setting Parameters in 796_UPG_PARAMS.txt for Oracle Project Analytics."

23. Back up and truncate the table W_POSITION_DH.

24. If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_7951_to_796_ORA11i and execute the following workflows in the order specified below:

- UPGRADE_DIMENSIONS

- UPGRADE_FACTS

- RESET_DAC_REFRESH_DATES

25. If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_7951_to_796_ORAR12 and execute the following workflows in the order specified below:

- UPGRADE_DIMENSIONS

- UPGRADE_FACTS

- RESET_DAC_REFRESH_DATES

26. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

27. Execute the 7961_Backup Tables.sql script.

28. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

29. Configure the Informatica parameter file 7961_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7961_UPG_PARAMS.txt."

30. If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_796_to_7961_ORA11i and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_796_to_7961_ORAR12 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

31. Execute the 7962_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

32. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

33. Configure the Informatica parameter file 7962_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7962_UPG_PARAMS.txt."

34. If you are upgrading Oracle Financial Analytics, do the following:

1. Configure application-specific parameters and update mappings. For instructions, see Section A.3.4, "Setting Parameters and Mappings in 7962_UPG_PARAMS.txt for Oracle Financial Analytics."

2. Make sure specific indexes are created. For instructions, see Appendix C, "Creating Indexes for Oracle Financial Analytics."

35. If you are using Oracle EBS R12, you need to configure specific parameters and update mappings for COGS. For instructions, see Section A.3.4.4, "Setting the COGS Fact Mapping for Oracle EBS R12."

36. If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_ORA11i and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_ORAR12 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

37. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

38. Execute the 7963_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

39. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

40. Configure the Informatica parameter file 7963_UPG_PARAMS.txt. For instructions, see Section A.1.8, "Setting Parameters in 7963_UPG_PARAMS.txt."

41. If you are upgrading Oracle Financial Analytics, do the following:

1. Set the parameters as specified in Appendix A, "Setting Parameters for All Source Systems."

2. If you are using Oracle EBS 11.5.10 family pack OIE.I or OIE.J, set the parameters as specified in Appendix A, "Setting Parameters Specific to Oracle EBS 11.5.10 Family Pack OIE.I and OIE.J."

42. If you are upgrading Oracle Human Resources Analytics, set the parameters as specified in Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt for Oracle Human Resources Analytics."

43. If you are upgrading Oracle Procurement and Spend Analytics, set the parameters as specified in Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt for Oracle Procurement and Spend Analytics on Oracle EBS 11i and 12 Source Systems."

44. If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_7962_to_7963_ORA11i and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_7962_to_7963_ORAR12 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

45. Upgrade geography-related attributes if necessary for your environment:

1. Determine whether a geography-related upgrade is necessary by executing the following query:

SELECT COUNT(1) as row_count,'0' as X_CUSTOM FROM W_GEO_D_7963 WHERE COUNTRY LIKE '% 'OR COUNTRY LIKE ' %'OR STATE_PROV LIKE '% 'OR STATE_PROV LIKE ' %'OR CITY LIKE '% 'OR CITY LIKE ' %'OR ZIPCODE LIKE '% 'OR ZIPCODE LIKE ' %'

2. If the query returns a count greater than zero, run the 7963_UPGRADE_POST_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.
If the query returns a count of zero, you do not need to run the 7963_UPGRADE_POST_SCRIPT.sql script.

46. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

47. Execute the 7964_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

48. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

49. Configure the Informatica parameter file 7964_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7964_UPG_PARAMS.txt."

50. If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_7963_to_7964_ORA11i and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_7963_to_7964_ORAR12 and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.

51. Run the 7964_UPGRADE_POST_SCRIPT.sql. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

52. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

53. In DAC, do the following:

1. Navigate to the Setup view, and click the Physical Data Sources tab.

2. In the top pane list, select DataWarehouse. (If you customized the name of the connection for the data warehouse, select the appropriate connection for the data warehouse database.)

3. Click the Refresh Dates subtab (in the lower pane).

4. Query for the table FND_LOOKUP_VALUES, and set the value in the Refresh Date column to NULL.

54. Once the data migration steps above are complete, you can delete the Upgrade repository to avoid any accidental use or confusion.

1. In the Informatica Administrator, select the Upgrade repository service.

2. In the General Properties area of the Properties tab, click Edit.

3. Make sure the operating mode of the repository service is set to Exclusive.

4. Click OK.

5. Choose Actions, and then click Delete Contents.

6. In the Delete contents for <repository name> dialog, enter the repository username and password, and then click OK.

6.10.4 Upgrading Oracle BI Applications From Version 7.9.5 to 7.9.6.4

Follow this procedure to upgrade from Oracle BI Applications version 7.9.5 to version 7.9.6.4 if your data warehouse database platform is Teradata.

To upgrade the data warehouse schema and migrate data for a Teradata database:

1. Execute the following scripts:

- 7951_UPGRADE_TMP_TABLES.sql

- 7961_UPGRADE_TMP_TABLES.sql

- 7962_UPGRADE_TMP_TABLES.sql

- 7963_UPGRADE_TMP_TABLES.sql

- 7964_UPGRADE_TMP_TABLES.sql

1. Open the SQL client for your database type.

2. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.

3. Open the <version>_UPGRADE_TMP_TABLES.sql file, and copy the contents into the SQL client.

4. Execute the script.

2. Edit and execute the 7951_RENAME_AND_EXCEPTIONS.sql script.

1. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.

2. Open the 7951_RENAME_AND_EXCEPTIONS.sql script.

3. Search for the following statements to locate columns with RENAME commands.
ALTER TABLE <Table_Name> RENAME <Column Name> TO <New Column Name>;

4. For all columns with RENAME commands, check to see whether any COLUMN STATISTICS are defined on them.

5. For all columns that have STATISTICS defined on them, back up the COLUMN STATISTICS definition and then drop them.

6. Execute the 7951_RENAME_AND_EXCEPTIONS.sql script.

7. Recreate STATISTICS on any column on which they were dropped.

3. The teradata.missing.defaults.properties file contains global default column values for data warehouse tables with NOT NULL columns for which default values are not specified in DAC. You can change the default values specified in the teradata.missing.defaults.properties file to match your environment. The file is located in \bifoundation\dac\conf\sqlgen\sql\teradata.

4. Generate upgrade scripts from DAC.

1. Log into DAC.

2. From the menu bar, select Tools, then ETL Management, and then Configure.

3. In the Sources dialog box, select Teradata as the target data warehouse database platform, and select the appropriate source data warehouse database platform.
The Configuration tab of the Data Warehouse Configuration Wizard is active.

4. Select "Generate upgrade statements for Data Warehouse Tables," and click Next.
The Data Warehouse SQL tab is active.

5. Do the following:
- Select the appropriate physical data source name for the Teradata database.

- In the container field, enter a custom container name for which you want to generate upgrade scripts. Alternatively, leave the field blank to generate upgrade scripts for all containers.

The Data Warehouse Configuration Wizard generates the following files and stores them in \bifoundation\DAC\conf\sqlgen\sql\teradata:

upgrade-regular.sql. This file contains scripts that DAC has verified are necessary to upgrade the data warehouse schema. The scripts handle new or altered tables and columns. For example, they may increase the size of simple data types or change a column from null to not null.

upgrade-questionable.sql. This file contains scripts that DAC suggests may be required to upgrade the data warehouse schema. These scripts are intended to be an aid in determining upgrade requirements and must be reviewed by a Teradata DBA and corrected if necessary.

upgradedwtables_sql.log. This file is the log file that corresponds to the upgrade-regular.sql file. It is for information purposes only.

upgrade-issues.log. This file is the log file that corresponds to the file upgrade-questionable.sql. It is for information purposes only.

6. Open the upgrade-regular.sql and upgrade-questionable.sql files, and search for the following statement to locate columns that have been added or changed.
ALTER TABLE <Table Name> ADD <Column Name><attributes>;

7. For all columns with the ADD command, check to see whether any columns exist already, and if they do, check whether they have STATISTICS defined on them.

8. For all columns that have STATISTICS defined on them, back up the column definition and then drop the STATISTICS.

9. Execute the scripts in the upgrade-regular.sql file.

10. Review the scripts in the upgrade-questionable.sql file. Edit the scripts as needed, and execute them.

11. Recreate STATISTICS on any column on which they were dropped.

5. Execute the following scripts:

- 7951_UPDATE_DEFAULTS.sql

- 7961_UPDATE_DEFAULTS.sql

- 7962_UPDATE_DEFAULTS.sql

- 7963_UPDATE_DEFAULTS.sql

- 7964_UPDATE_DEFAULTS.sql

6. Execute the 7951_Backup Tables.sql script.

7. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

8. Configure the Informatica parameter file 7951_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7951_UPG_PARAMS.txt."

9. If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_795_to_7951_ORA11i and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_795_to_7951_ORAR12 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

10. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

11. Execute the 796_Backup Tables.sql script.

12. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

13. Configure the Informatica parameter file 796_UPG_PARAMS.txt file. For instructions, see Appendix A, "Setting Parameters in 796_UPG_PARAMS.txt."

14. If you are using Oracle EBS 11i, configure parameters specific to Oracle 11i source systems. For instructions, see Appendix A, "Setting Parameters in 796_UPG_PARAMS.txt for Oracle EBS 11i Source Systems."

15. If you are upgrading Oracle Financial Analytics, you need to configure specific parameters and update mappings. For more information, see Appendix A, "Setting Parameters and Mappings in 796_UPG_PARAMS.txt for Oracle Financial Analytics."

16. If you are upgrading Oracle Supply Chain and Order Management Analytics, you need to configure specific parameters. For more information, see Appendix A, "Setting Parameters in 796_UPG_PARAMS.txt for Oracle Supply Chain and Order Management Analytics."

17. If you are deploying Oracle Project Analytics, you need to configure specific parameters. For more information, see Appendix A, "Setting Parameters in 796_UPG_PARAMS.txt for Oracle Project Analytics."

18. Back up and truncate the table W_POSITION_DH.

19. If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_7951_to_796_ORA11i and execute the following workflows in the order specified below:

- UPGRADE_DIMENSIONS

- UPGRADE_FACTS

- RESET_DAC_REFRESH_DATES

20. If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_7951_to_796_ORAR12 and execute the following workflows in the order specified below:

- UPGRADE_DIMENSIONS

- UPGRADE_FACTS

- RESET_DAC_REFRESH_DATES

21. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

22. Execute the 7961_Backup Tables.sql script.

23. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

24. Configure the Informatica parameter file 7961_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7961_UPG_PARAMS.txt."

25. If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_796_to_7961_ORA11i and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_796_to_7961_ORAR12 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

26. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

27. Execute the 7962_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

28. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

29. Configure the Informatica parameter file 7962_UPG_PARAMS.txt.

30. If you are upgrading Oracle Financial Analytics, do the following:

1. Configure application-specific parameters and update mappings. For instructions, see Section A.3.4, "Setting Parameters and Mappings in 7962_UPG_PARAMS.txt for Oracle Financial Analytics."

2. Make sure specific indexes are created. For instructions, see Appendix C, "Creating Indexes for Oracle Financial Analytics."

31. If you are using Oracle EBS R12, you need to configure specific parameters and update mappings for COGS. For instructions, see Section A.3.4.4, "Setting the COGS Fact Mapping for Oracle EBS R12."

32. If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_ORA11i and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_ORAR12 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

33. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

34. Execute the 7963_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

35. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

36. Configure the Informatica parameter file 7963_UPG_PARAMS.txt. For instructions, see Section A.1.8, "Setting Parameters in 7963_UPG_PARAMS.txt."

37. If you are upgrading Oracle Financial Analytics, do the following:

1. Set the parameters as specified in Appendix A, "Setting Parameters for All Source Systems."

2. If you are using Oracle EBS 11.5.10 family pack OIE.I or OIE.J, set the parameters as specified in Appendix A, "Setting Parameters Specific to Oracle EBS 11.5.10 Family Pack OIE.I and OIE.J."

38. If you are upgrading Oracle Human Resources Analytics, set the parameters as specified in Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt for Oracle Human Resources Analytics."

39. If you are upgrading Oracle Procurement and Spend Analytics, set the parameters as specified in Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt for Oracle Procurement and Spend Analytics on Oracle EBS 11i and 12 Source Systems."

40. If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_7962_to_7963_ORA11i and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_7962_to_7963_ORAR12 and execute execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

41. Upgrade geography-related attributes if necessary for your environment:

1. Determine whether a geography-related upgrade is necessary by executing the following query:

SELECT COUNT(1) as row_count,'0' as X_CUSTOM FROM W_GEO_D_7963 WHERE COUNTRY LIKE '% 'OR COUNTRY LIKE ' %'OR STATE_PROV LIKE '% 'OR STATE_PROV LIKE ' %'OR CITY LIKE '% 'OR CITY LIKE ' %'OR ZIPCODE LIKE '% 'OR ZIPCODE LIKE ' %'

2. If the query returns a count greater than zero, run the 7963_UPGRADE_POST_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.
If the query returns a count of zero, you do not need to run the 7963_UPGRADE_POST_SCRIPT.sql script.

42. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

43. Execute the 7964_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

44. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

45. Configure the Informatica parameter file 7964_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7964_UPG_PARAMS.txt."

46. If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_7963_to_7964_ORA11i and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_7963_to_7964_ORAR12 and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.

47. Run the 7964_UPGRADE_POST_SCRIPT.sql. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

48. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

49. In DAC, do the following:

1. Navigate to the Setup view, and click the Physical Data Sources tab.

2. In the top pane list, select DataWarehouse. (If you customized the name of the connection for the data warehouse, select the appropriate connection for the data warehouse database.)

3. Click the Refresh Dates subtab (in the lower pane).

4. Query for the table FND_LOOKUP_VALUES, and set the value in the Refresh Date column to NULL.

50. Once the data migration steps above are complete, you can delete the Upgrade repository to avoid any accidental use or confusion.

1. In the Informatica Administrator, select the Upgrade repository service.

2. In the General Properties area of the Properties tab, click Edit.

3. Make sure the operating mode of the repository service is set to Exclusive.

4. Click OK.

5. Choose Actions, and then click Delete Contents.

6. In the Delete contents for <repository name> dialog, enter the repository username and password, and then click OK.

6.10.5 Upgrading Oracle BI Applications From Version 7.9.5.1 to 7.9.6.4

Follow this procedure to upgrade from Oracle BI Applications version 7.9.5.1 to version 7.9.6.4 if your data warehouse database platform is Teradata.

To upgrade the data warehouse schema and migrate data for a Teradata database:

1. Execute the following scripts:

- 7961_UPGRADE_TMP_TABLES.sql

- 7962_UPGRADE_TMP_TABLES.sql

- 7963_UPGRADE_TMP_TABLES.sql

- 7964_UPGRADE_TMP_TABLES.sql

1. Open the SQL client for your database type.

2. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.

3. Open the <version>_UPGRADE_TMP_TABLES.sql file, and copy the contents into the SQL client.

4. Execute the script.

2. Edit and execute the 7961_RENAME_AND_EXCEPTIONS.sql script.

1. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.

2. Open the 7961_RENAME_AND_EXCEPTIONS.sql script.

3. Search for the following statements to locate columns with RENAME commands.
ALTER TABLE <Table_Name> RENAME <Column Name> TO <New Column Name>;

4. For all columns with RENAME commands, check to see whether any COLUMN STATISTICS are defined on them.

5. For all columns that have STATISTICS defined on them, back up the COLUMN STATISTICS definition and then drop them.

6. Execute the 7961_RENAME_AND_EXCEPTIONS.sql script.

7. Recreate STATISTICS on any column on which they were dropped.

3. The teradata.missing.defaults.properties file contains global default column values for data warehouse tables with NOT NULL columns for which default values are not specified in DAC. You can change the default values specified in the teradata.missing.defaults.properties file to match your environment. The file is located in \bifoundation\dac\conf\sqlgen\sql\teradata.

4. Generate upgrade scripts from DAC.

1. Log into DAC.

2. From the menu bar, select Tools, then ETL Management, and then Configure.

3. In the Sources dialog box, select Teradata as the target data warehouse database platform, and select the appropriate source data warehouse database platform.
The Configuration tab of the Data Warehouse Configuration Wizard is active.

4. Select "Generate upgrade statements for Data Warehouse Tables," and click Next.
The Data Warehouse SQL tab is active.

5. Do the following:
- Select the appropriate physical data source name for the Teradata database.

- In the container field, enter a custom container name for which you want to generate upgrade scripts. Alternatively, leave the field blank to generate upgrade scripts for all containers.

The Data Warehouse Configuration Wizard generates the following files and stores them in \bifoundation\DAC\conf\sqlgen\sql\teradata:

upgrade-regular.sql. This file contains scripts that DAC has verified are necessary to upgrade the data warehouse schema. The scripts handle new or altered tables and columns. For example, they may increase the size of simple data types or change a column from null to not null.

upgrade-questionable.sql. This file contains scripts that DAC suggests may be required to upgrade the data warehouse schema. These scripts are intended to be an aid in determining upgrade requirements and must be reviewed by a Teradata DBA and corrected if necessary.

upgradedwtables_sql.log. This file is the log file that corresponds to the upgrade-regular.sql file. It is for information purposes only.

upgrade-issues.log. This file is the log file that corresponds to the file upgrade-questionable.sql. It is for information purposes only.

6. Open the upgrade-regular.sql and upgrade-questionable.sql files, and search for the following statement to locate columns that have been added or changed.
ALTER TABLE <Table Name> ADD <Column Name><attributes>;

7. For all columns with the ADD command, check to see whether any columns exist already, and if they do, check whether they have STATISTICS defined on them.

8. For all columns that have STATISTICS defined on them, back up the column definition and then drop the STATISTICS.

9. Execute the scripts in the upgrade-regular.sql file.

10. Review the scripts in the upgrade-questionable.sql file. Edit the scripts as needed, and execute them.

11. Recreate STATISTICS on any column on which they were dropped.

5. Execute the following scripts:

- 7961_UPDATE_DEFAULTS.sql

- 7962_UPDATE_DEFAULTS.sql

- 7963_UPDATE_DEFAULTS.sql

- 7964_UPDATE_DEFAULTS.sql

6. Execute the 796_Backup Tables.sql script.

7. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

8. Configure the Informatica parameter file 796_UPG_PARAMS.txt file. For instructions, see Appendix A, "Setting Parameters in 796_UPG_PARAMS.txt."

9. If you are using Oracle EBS 11i, configure parameters specific to Oracle 11i source systems. For instructions, see Appendix A, "Setting Parameters in 796_UPG_PARAMS.txt for Oracle EBS 11i Source Systems."

10. If you are upgrading Oracle Financial Analytics, you need to configure specific parameters and update mappings. For more information, see Appendix A, "Setting Parameters and Mappings in 796_UPG_PARAMS.txt for Oracle Financial Analytics."

11. If you are upgrading Oracle Supply Chain and Order Management Analytics, you need to configure specific parameters. For more information, see Appendix A, "Setting Parameters in 796_UPG_PARAMS.txt for Oracle Supply Chain and Order Management Analytics."

12. If you are deploying Oracle Project Analytics, you need to configure specific parameters. For more information, see Appendix A, "Setting Parameters in 796_UPG_PARAMS.txt for Oracle Project Analytics."

13. Back up and truncate the table W_POSITION_DH.

14. If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_7951_to_796_ORA11i and execute the following workflows in the order specified below:

- UPGRADE_DIMENSIONS

- UPGRADE_FACTS

- RESET_DAC_REFRESH_DATES

15. If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_7951_to_796_ORAR12 and execute the following workflows in the order specified below:

- UPGRADE_DIMENSIONS

- UPGRADE_FACTS

- RESET_DAC_REFRESH_DATES

16. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

17. Execute the 7961_Backup Tables.sql script.

18. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

19. Configure the Informatica parameter file 7961_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7961_UPG_PARAMS.txt."

20. If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_796_to_7961_ORA11i and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_796_to_7961_ORAR12 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

21. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

22. Execute the 7962_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

23. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

24. Configure the Informatica parameter file 7962_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7962_UPG_PARAMS.txt."

25. If you are upgrading Oracle Financial Analytics, do the following:

1. Configure application-specific parameters and update mappings. For instructions, see Section A.3.4, "Setting Parameters and Mappings in 7962_UPG_PARAMS.txt for Oracle Financial Analytics."

2. Make sure specific indexes are created. For instructions, see Appendix C, "Creating Indexes for Oracle Financial Analytics."

26. If you are using Oracle EBS R12, you need to configure specific parameters and update mappings for COGS. For instructions, see Section A.3.4.4, "Setting the COGS Fact Mapping for Oracle EBS R12."

27. If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_ORA11i and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_ORAR12 and execute execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

28. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

29. Execute the 7963_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

30. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

31. Configure the Informatica parameter file 7963_UPG_PARAMS.txt. For instructions, see Section A.1.8, "Setting Parameters in 7963_UPG_PARAMS.txt."

32. If you are upgrading Oracle Financial Analytics, do the following:

1. Set the parameters as specified in Appendix A, "Setting Parameters for All Source Systems."

2. If you are using Oracle EBS 11.5.10 family pack OIE.I or OIE.J, set the parameters as specified in Appendix A, "Setting Parameters Specific to Oracle EBS 11.5.10 Family Pack OIE.I and OIE.J."

33. If you are upgrading Oracle Human Resources Analytics, set the parameters as specified in Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt for Oracle Human Resources Analytics."

34. If you are upgrading Oracle Procurement and Spend Analytics, set the parameters as specified in Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt for Oracle Procurement and Spend Analytics on Oracle EBS 11i and 12 Source Systems."

35. If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_7962_to_7963_ORA11i and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_7962_to_7963_ORAR12 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

36. Upgrade geography-related attributes if necessary for your environment:

1. Determine whether a geography-related upgrade is necessary by executing the following query:

SELECT COUNT(1) as row_count,'0' as X_CUSTOM FROM W_GEO_D_7963 WHERE COUNTRY LIKE '% 'OR COUNTRY LIKE ' %'OR STATE_PROV LIKE '% 'OR STATE_PROV LIKE ' %'OR CITY LIKE '% 'OR CITY LIKE ' %'OR ZIPCODE LIKE '% 'OR ZIPCODE LIKE ' %'

2. If the query returns a count greater than zero, run the 7963_UPGRADE_POST_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.
If the query returns a count of zero, you do not need to run the 7963_UPGRADE_POST_SCRIPT.sql script.

37. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

38. Execute the 7964_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

39. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

40. Configure the Informatica parameter file 7964_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7964_UPG_PARAMS.txt."

41. If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_7963_to_7964_ORA11i and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_7963_to_7964_ORAR12 and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.

42. Run the 7964_UPGRADE_POST_SCRIPT.sql. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

43. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

44. In DAC, do the following:

1. Navigate to the Setup view, and click the Physical Data Sources tab.

2. In the top pane list, select DataWarehouse. (If you customized the name of the connection for the data warehouse, select the appropriate connection for the data warehouse database.)

3. Click the Refresh Dates subtab (in the lower pane).

4. Query for the table FND_LOOKUP_VALUES, and set the value in the Refresh Date column to NULL.

45. Once the data migration steps above are complete, you can delete the Upgrade repository to avoid any accidental use or confusion.

1. In the Informatica Administrator, select the Upgrade repository service.

2. In the General Properties area of the Properties tab, click Edit.

3. Make sure the operating mode of the repository service is set to Exclusive.

4. Click OK.

5. Choose Actions, and then click Delete Contents.

6. In the Delete contents for <repository name> dialog, enter the repository username and password, and then click OK.

6.10.6 Upgrading Oracle BI Applications From Version 7.9.6.1 to 7.9.6.4

Follow this procedure to upgrade from Oracle Business Applications version 7.9.6.1 to version 7.9.6.4 if your data warehouse database platform is Teradata.

To upgrade the data warehouse schema and migrate data for a Teradata database:

1. Execute the 7962_UPGRADE_TMP_TABLES.sql, 7963_UPGRADE_TMP_TABLES.sql, and 7964__UPGRADE_TMP_TABLES.sql scripts.

1. Open the SQL client for your database type.

2. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.

3. Open the <version>_UPGRADE_TMP_TABLES.sql file, and copy the contents into the SQL client.

4. Execute the script.

2. The teradata.missing.defaults.properties file contains global default column values for data warehouse tables with NOT NULL columns for which default values are not specified in DAC. You can change the default values specified in the teradata.missing.defaults.properties file to match your environment. The file is located in \bifoundation\dac\conf\sqlgen\sql\teradata.

3. Generate upgrade scripts from DAC.

1. Log into DAC.

2. From the menu bar, select Tools, then ETL Management, and then Configure.

3. In the Sources dialog box, select Teradata as the target data warehouse database platform, and select the appropriate source data warehouse database platform.
The Configuration tab of the Data Warehouse Configuration Wizard is active.

4. Select "Generate upgrade statements for Data Warehouse Tables," and click Next.
The Data Warehouse SQL tab is active.

5. Do the following:
- Select the appropriate physical data source name for the Teradata database.

- In the container field, enter a custom container name for which you want to generate upgrade scripts. Alternatively, leave the field blank to generate upgrade scripts for all containers.

The Data Warehouse Configuration Wizard generates the following files and stores them in \bifoundation\DAC\conf\sqlgen\sql\teradata:

upgrade-regular.sql. This file contains scripts that DAC has verified are necessary to upgrade the data warehouse schema. The scripts handle new or altered tables and columns. For example, they may increase the size of simple data types or change a column from null to not null.

upgrade-questionable.sql. This file contains scripts that DAC suggests may be required to upgrade the data warehouse schema. These scripts are intended to be an aid in determining upgrade requirements and must be reviewed by a Teradata DBA and corrected if necessary.

upgradedwtables_sql.log. This file is the log file that corresponds to the upgrade-regular.sql file. It is for information purposes only.

upgrade-issues.log. This file is the log file that corresponds to the file upgrade-questionable.sql. It is for information purposes only.

6. Open the upgrade-regular.sql and upgrade-questionable.sql files, and search for the following statement to locate columns that have been added or changed.
ALTER TABLE <Table Name> ADD <Column Name><attributes>;

7. For all columns with the ADD command, check to see whether any columns exist already, and if they do, check whether they have STATISTICS defined on them.

8. For all columns that have STATISTICS defined on them, back up the column definition and then drop the STATISTICS.

9. Execute the scripts in the upgrade-regular.sql file.

10. Review the scripts in the upgrade-questionable.sql file. Edit the scripts as needed, and execute them.

11. Recreate STATISTICS on any column on which they were dropped.

4. Execute the 7962_UPDATE_DEFAULTS.sql, 7963_UPDATE_DEFAULTS.sql, and 7964_UPDATE_DEFAULTS.sql scripts.

5. Execute the 7962_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

6. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

7. Configure the Informatica parameter file 7962_UPG_PARAMS.txt. Appendix A, "Setting Parameters in 7962_UPG_PARAMS.txt."

8. If you are upgrading Oracle Financial Analytics, do the following:

1. Configure application-specific parameters and update mappings. For instructions, see Section A.3.4, "Setting Parameters and Mappings in 7962_UPG_PARAMS.txt for Oracle Financial Analytics."

2. Make sure specific indexes are created. For instructions, see Appendix C, "Creating Indexes for Oracle Financial Analytics."

9. If you are using Oracle EBS R12, you need to configure specific parameters and update mappings for COGS. For instructions, see Section A.3.4.4, "Setting the COGS Fact Mapping for Oracle EBS R12."

10. If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_ORA11i and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_ORAR12 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

11. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

12. Execute the 7963_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

13. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

14. Configure the Informatica parameter file 7963_UPG_PARAMS.txt. For instructions, see Section A.1.8, "Setting Parameters in 7963_UPG_PARAMS.txt."

15. If you are upgrading Oracle Financial Analytics, do the following:

1. Set the parameters as specified in Appendix A, "Setting Parameters for All Source Systems."

2. If you are using Oracle EBS 11.5.10 family pack OIE.I or OIE.J, set the parameters as specified in Appendix A, "Setting Parameters Specific to Oracle EBS 11.5.10 Family Pack OIE.I and OIE.J."

16. If you are upgrading Oracle Human Resources Analytics, set the parameters as specified in Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt for Oracle Human Resources Analytics."

17. If you are upgrading Oracle Procurement and Spend Analytics, set the parameters as specified in Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt for Oracle Procurement and Spend Analytics on Oracle EBS 11i and 12 Source Systems."

18. If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_7962_to_7963_ORA11i and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_7962_to_7963_ORAR12 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

19. Upgrade geography-related attributes if necessary for your environment:

1. Determine whether a geography-related upgrade is necessary by executing the following query:

SELECT COUNT(1) as row_count,'0' as X_CUSTOM FROM W_GEO_D_7963 WHERE COUNTRY LIKE '% 'OR COUNTRY LIKE ' %'OR STATE_PROV LIKE '% 'OR STATE_PROV LIKE ' %'OR CITY LIKE '% 'OR CITY LIKE ' %'OR ZIPCODE LIKE '% 'OR ZIPCODE LIKE ' %'

2. If the query returns a count greater than zero, run the 7963_UPGRADE_POST_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.
If the query returns a count of zero, you do not need to run the 7963_UPGRADE_POST_SCRIPT.sql script.

20. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

21. Execute the 7964_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

22. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

23. Configure the Informatica parameter file 7964_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7964_UPG_PARAMS.txt."

24. If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_7963_to_7964_ORA11i and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_7963_to_7964_ORAR12 and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.

25. Run the 7964_UPGRADE_POST_SCRIPT.sql. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

26. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

27. In DAC, do the following:

1. Navigate to the Setup view, and click the Physical Data Sources tab.

2. In the top pane list, select DataWarehouse. (If you customized the name of the connection for the data warehouse, select the appropriate connection for the data warehouse database.)

3. Click the Refresh Dates subtab (in the lower pane).

4. Query for the table FND_LOOKUP_VALUES, and set the value in the Refresh Date column to NULL.

28. Once the data migration steps above are complete, you can delete the Upgrade repository to avoid any accidental use or confusion.

1. In the Informatica Administrator, select the Upgrade repository service.

2. In the General Properties area of the Properties tab, click Edit.

3. Make sure the operating mode of the repository service is set to Exclusive.

4. Click OK.

5. Choose Actions, and then click Delete Contents.

6. In the Delete contents for <repository name> dialog, enter the repository username and password, and then click OK.

6.10.7 Upgrading Oracle BI Applications From Version 7.9.6.2 to 7.9.6.4

Follow this procedure to upgrade from Oracle Business Applications version 7.9.6.2 to version 7.9.6.4 if your data warehouse database platform is Teradata.

To upgrade the data warehouse schema and migrate data for a Teradata database:

1. Execute the 7963_UPGRADE_TMP_TABLES.sql and 7964_UPGRADE_TMP_TABLES.sql script.

1. Open the SQL client for your database type.

2. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.

3. Open the <version>_UPGRADE_TMP_TABLES.sql file, and copy the contents into the SQL client.

4. Execute the script.

2. The teradata.missing.defaults.properties file contains global default column values for data warehouse tables with NOT NULL columns for which default values are not specified in DAC. You can change the default values specified in the teradata.missing.defaults.properties file to match your environment. The file is located in \bifoundation\dac\conf\sqlgen\sql\teradata.

3. Generate upgrade scripts from DAC.

1. Log into DAC.

2. From the menu bar, select Tools, then ETL Management, and then Configure.

3. In the Sources dialog box, select Teradata as the target data warehouse database platform, and select the appropriate source data warehouse database platform.
The Configuration tab of the Data Warehouse Configuration Wizard is active.

4. Select "Generate upgrade statements for Data Warehouse Tables," and click Next.
The Data Warehouse SQL tab is active.

5. Do the following:
- Select the appropriate physical data source name for the Teradata database.

- In the container field, enter a custom container name for which you want to generate upgrade scripts. Alternatively, leave the field blank to generate upgrade scripts for all containers.

The Data Warehouse Configuration Wizard generates the following files and stores them in \bifoundation\DAC\conf\sqlgen\sql\teradata:

upgrade-regular.sql. This file contains scripts that DAC has verified are necessary to upgrade the data warehouse schema. The scripts handle new or altered tables and columns. For example, they may increase the size of simple data types or change a column from null to not null.

upgrade-questionable.sql. This file contains scripts that DAC suggests may be required to upgrade the data warehouse schema. These scripts are intended to be an aid in determining upgrade requirements and must be reviewed by a Teradata DBA and corrected if necessary.

upgradedwtables_sql.log. This file is the log file that corresponds to the upgrade-regular.sql file. It is for information purposes only.

upgrade-issues.log. This file is the log file that corresponds to the file upgrade-questionable.sql. It is for information purposes only.

6. Open the upgrade-regular.sql and upgrade-questionable.sql files, and search for the following statement to locate columns that have been added or changed.
ALTER TABLE <Table Name> ADD <Column Name><attributes>;

7. For all columns with the ADD command, check to see whether any columns exist already, and if they do, check whether they have STATISTICS defined on them.

8. For all columns that have STATISTICS defined on them, back up the column definition and then drop the STATISTICS.

9. Execute the scripts in the upgrade-regular.sql file.

10. Review the scripts in the upgrade-questionable.sql file. Edit the scripts as needed, and execute them.

11. Recreate STATISTICS on any column on which they were dropped.

4. Execute the 7963_UPDATE_DEFAULTS.sql and 7964_UPDATE_DEFAULTS.sql scripts.

5. Execute the 7963_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

6. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

7. If you are upgrading Oracle Financial Analytics, do the following:

1. Set the parameters as specified in Appendix A, "Setting Parameters for All Source Systems."

2. If you are using Oracle EBS 11.5.10 family pack OIE.I or OIE.J, set the parameters as specified in Appendix A, "Setting Parameters Specific to Oracle EBS 11.5.10 Family Pack OIE.I and OIE.J."

8. If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_7962_to_7963_ORA11i and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_7962_to_7963_ORAR12 and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.

9. Upgrade geography-related attributes if necessary for your environment:

1. Determine whether a geography-related upgrade is necessary by executing the following query:

SELECT COUNT(1) as row_count,'0' as X_CUSTOM FROM W_GEO_D_7963 WHERE COUNTRY LIKE '% 'OR COUNTRY LIKE ' %'OR STATE_PROV LIKE '% 'OR STATE_PROV LIKE ' %'OR CITY LIKE '% 'OR CITY LIKE ' %'OR ZIPCODE LIKE '% 'OR ZIPCODE LIKE ' %'

2. If the query returns a count greater than zero, run the 7963_UPGRADE_POST_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.
If the query returns a count of zero, you do not need to run the 7963_UPGRADE_POST_SCRIPT.sql script.

10. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

11. Execute the 7964_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

12. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

13. Configure the Informatica parameter file 7964_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7964_UPG_PARAMS.txt."

14. If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_7963_to_7964_ORA11i and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_7963_to_7964_ORAR12 and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.

15. Run the 7964_UPGRADE_POST_SCRIPT.sql. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

16. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

17. Once the data migration steps above are complete, you can delete the Upgrade repository to avoid any accidental use or confusion.

1. In the Informatica Administrator, select the Upgrade repository service.

2. In the General Properties area of the Properties tab, click Edit.

3. Make sure the operating mode of the repository service is set to Exclusive.

4. Click OK.

5. Choose Actions, and then click Delete Contents.

6. In the Delete contents for <repository name> dialog, enter the repository username and password, and then click OK.

6.10.8 Upgrading Oracle BI Applications From Version 7.9.6.3 to 7.9.6.4

Follow this procedure to upgrade from Oracle Business Applications version 7.9.6.3 to version 7.9.6.4 if your data warehouse database platform is Teradata.

To upgrade the data warehouse schema and migrate data for a Teradata database:

1. Execute the 7964_UPGRADE_TMP_TABLES.sql script.

1. Open the SQL client for your database type.

2. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.

3. Open the 7964_UPGRADE_TMP_TABLES.sql file, and copy the contents into the SQL client.

4. Execute the script.

2. The teradata.missing.defaults.properties file contains global default column values for data warehouse tables with NOT NULL columns for which default values are not specified in DAC. You can change the default values specified in the teradata.missing.defaults.properties file to match your environment. The file is located in \bifoundation\dac\conf\sqlgen\sql\teradata.

3. Generate upgrade scripts from DAC.

1. Log into DAC.

2. From the menu bar, select Tools, then ETL Management, and then Configure.

3. In the Sources dialog box, select Teradata as the target data warehouse database platform, and select the appropriate source data warehouse database platform.
The Configuration tab of the Data Warehouse Configuration Wizard is active.

4. Select "Generate upgrade statements for Data Warehouse Tables," and click Next.
The Data Warehouse SQL tab is active.

5. Do the following:
- Select the appropriate physical data source name for the Teradata database.

- In the container field, enter a custom container name for which you want to generate upgrade scripts. Alternatively, leave the field blank to generate upgrade scripts for all containers.

The Data Warehouse Configuration Wizard generates the following files and stores them in \bifoundation\DAC\conf\sqlgen\sql\teradata:

upgrade-regular.sql. This file contains scripts that DAC has verified are necessary to upgrade the data warehouse schema. The scripts handle new or altered tables and columns. For example, they may increase the size of simple data types or change a column from null to not null.

upgrade-questionable.sql. This file contains scripts that DAC suggests may be required to upgrade the data warehouse schema. These scripts are intended to be an aid in determining upgrade requirements and must be reviewed by a Teradata DBA and corrected if necessary.

upgradedwtables_sql.log. This file is the log file that corresponds to the upgrade-regular.sql file. It is for information purposes only.

upgrade-issues.log. This file is the log file that corresponds to the file upgrade-questionable.sql. It is for information purposes only.

6. Open the upgrade-regular.sql and upgrade-questionable.sql files, and search for the following statement to locate columns that have been added or changed.
ALTER TABLE <Table Name> ADD <Column Name><attributes>;

7. For all columns with the ADD command, check to see whether any columns exist already, and if they do, check whether they have STATISTICS defined on them.

8. For all columns that have STATISTICS defined on them, back up the column definition and then drop the STATISTICS.

9. Execute the scripts in the upgrade-regular.sql file.

10. Review the scripts in the upgrade-questionable.sql file. Edit the scripts as needed, and execute them.

11. Recreate STATISTICS on any column on which they were dropped.

4. Execute the 7964_UPDATE_DEFAULTS.sql scripts.

5. Execute the 7964_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

6. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

7. Configure the Informatica parameter file 7964_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7964_UPG_PARAMS.txt."

8. If you are using Oracle EBS 11i, in Informatica Workflow Manager, navigate to the folder UPGRADE_7963_to_7964_ORA11i and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.
If you are using Oracle EBS R12, R12.1.1, or R12.1.2, in Informatica Workflow Manager, navigate to the folder UPGRADE_7963_to_7964_ORAR12 and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.

9. Run the 7964_UPGRADE_POST_SCRIPT.sql. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

10. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

11. Once the data migration steps above are complete, you can delete the Upgrade repository to avoid any accidental use or confusion.

1. In the Informatica Administrator, select the Upgrade repository service.

2. In the General Properties area of the Properties tab, click Edit.

3. Make sure the operating mode of the repository service is set to Exclusive.

4. Click OK.

5. Choose Actions, and then click Delete Contents.

6. In the Delete contents for <repository name> dialog, enter the repository username and password, and then click OK.

6.11 Localizing the Policy Store

The Oracle BI Applications 7.9.6.4 installer contains different policy stores for different languages. The default policy store that is deployed during the installation is in English. If you want to configure the policy store for any of the other available languages, perform the procedure below.

To configure the policy store for languages other than English:

1. Stop the Oracle BI Services.

2. Copy the system-jazn-data_<LN>.xml file from $ORACLE_BI_HOME\biapps\admin\provisioning\localization\ to $DOMAIN_HOME\config\fmwconfig\.
For example, to implement the policy store for French, you would copy the file system-jazn-data_fr.xml into the \fmwconfig directory.

3. Back up the existing system-jazn-data.xml file in $DOMAIN_HOME\config\fmwconfig\.

4. Rename $DOMAIN_HOME\config\fmwconfig\system-jazn-data_<LN>.xml to system-jazn-data.xml.

5. Start Oracle BI Services.

6.12 Importing the Oracle BI Applications Version 7.9.6.4 LDIF File Into the Embedded LDAP Server

In this procedure, you will import the standard (out-of-the-box) Oracle BI Applications version 7.9.6.4 LDIF file into the WebLogic Server embedded LDAP server.

To import the Oracle BI Applications version 7.9.6.4 LDIF file:

1. Log in to the WebLogic Server Administration Console using the URL http://<host name>:7001/console.

2. Select the name of the security realm into which the LDIF file is to be imported (for example, myrealm).

3. Select Providers and then the type of provider into which the LDIF file is to be imported (for example, Providers, and then Authentication).

4. Select the security provider in which the LDIF file is to be imported and select Migration, and then select Import.

5. Click Save.

6.13 Upgrading the Oracle BI Repository and Presentation Catalog to the Oracle BI Enterprise Edition 11g Version

Use the Oracle BI Enterprise Edition Upgrade Assistant to upgrade the following repositories and web catalog from the Oracle BI Enterprise Edition 10g format to the 11g format:

- The standard (out-of-the-box) Oracle BI Repository. This repository is the one that you originally received from Oracle as part of your current Oracle BI Applications installation (the version from which you are upgrading). Standard repositories from previous releases are available in the installation folder $ORACLE_BI_HOME\biapps\upgrade.

- The Oracle BI Repository you are currently using (the repository deployed in production).

- The Presentation Catalog you are currently using (the catalog deployed in production).

For instructions on using the Upgrade Assistant, see Oracle Fusion Middleware Upgrade Guide for Oracle Business Intelligence.

Note:

Your current policy store will be merged with the Oracle BI Applications release 7.9.6.4 policy store while upgrading the Oracle BI repository from the 10g format to the 11g format. The final policy store will be the super set of Oracle BI Applications release 7.9.6.4 policy store and the custom and current policy information from the 10g repository.

Also, your current users and groups from the repository will be merged with the Oracle BI Applications release 7.9.6.4 identity store while upgrading the Oracle BI repository from the 10g format to the 11g format. The final identity store will be the super set of the Oracle BI Applications release 7.9.6.4 identity store and the identity store information (users and groups) from the 10g repository.

If you require the policy store to be in a language other than English, perform the steps in Section 6.11, "Localizing the Policy Store."

6.14 Merging Oracle BI Applications Version 7.9.6.4 Repository With Customer Repository

Note:

Before you begin this procedure, you must have already upgraded the Oracle BI repository you are currently using and the standard (out-of-the-box) Oracle BI repository version 7.9.x (the version from which you are upgrading) to the Oracle BI Enterprise Edition 11g format. For more information, see Section 6.13, "Upgrading the Oracle BI Repository and Presentation Catalog to the Oracle BI Enterprise Edition 11g Version."

This process merges your customizations of a prior release of the Oracle BI repository with the new release 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 6.14.1, "Preparing for the Oracle BI Repository Upgrade"

- Section 6.14.2, "Equalizing the Oracle BI Repositories"

- Section 6.14.3, "Comparing the Oracle BI Repositories"

- Section 6.14.4, "Merging the Oracle BI Repositories"

The tasks in this section refer to multiple releases of the Oracle BI repository. Table 6-1 provides the names and descriptions of the repositories used in the examples in this section.

Table 6-1 Names of Analytics Repositories used in Examples

Name of Repository

Description

OracleBIAnalyticsApps_79x.rpd

The standard Oracle BI repository for the version you are upgrading from.

Note: Standard repositories from previous releases are available in the folder $ORACLE_BI_HOME\biapps\upgrade.

OracleBIAnalyticsApps.rpd

The standard Oracle BI repository for the version you are upgrading to.

Customer_OracleBIAnalyticsApps.rpd

The Oracle BI 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.

6.14.1 Preparing for the Oracle BI Repository Upgrade

Follow this procedure to prepare for the repository upgrade.

To prepare for the Analytics repository upgrade:

1. Set up a directory for the merge process, such as \OracleBIUpgrade, and create the following subfolders:

- Original

- AfterEqualize

- AfterMerge

- AfterManualWork

- AfterRegressions

2. Copy the following repositories to the folder \OracleBIUpgrade\Original:

- The standard repository that you upgraded to the 11g format in Section 6.13, "Upgrading the Oracle BI Repository and Presentation Catalog to the Oracle BI Enterprise Edition 11g Version" (for example, OracleBIAnalyticsApps_79x.rpd).

- The production repository that you also upgraded to the 11g format in Section 6.13 (for example, Customer_OracleBIAnalyticsApps.rpd.

- The Oracle BI repository from the latest installation (for example, OracleBIAnalyticsApps.rpd)

If, in your current environment, you are running Oracle BI Applications for one or more modules using a Oracle BI repository in which you extracted the corresponding projects for the modules from the standard Oracle BI repository file you received from the previous release, you need to extract the same projects from the OracleBIAnalyticsApps_79x.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 Oracle BI 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 OracleBIAnalyticsApps_79x.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.

6.14.2 Equalizing the Oracle BI Repositories

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, OracleBIAnalyticsApps_79x.rpd, OracleBIAnalyticsApps.rpd, and Customer_OracleBIAnalyticsApps.rpd) are equivalent.

The point of this step is to determine for every object in the OracleBIAnalyticsApps.rpd and the Customer_OracleBIAnalyticsApps.rpd whether it is coming from the OracleBIAnalyticsApps_79x.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 $ORACLE_BI_HOME\biapps\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.
Table 6-2 provides a list of the available MAP files and the Siebel Analytics or Oracle BI Applications release version associated with the file.

Table 6-2 Rename MAP Files to Be Used for Various Releases

Siebel Analytics / Oracle Business Intelligence Applications Release Version (Upgrading from DW Version)

Rename MAP File to Be Used

Siebel Business Analytics Applications 7.0.x

Not available

Siebel Business Analytics Applications 7.5.x

Not available

Siebel Business Analytics Applications 7.7.x (with Siebel CRM OLTP Pre-7.7.0)

Rename77-7963.map

Siebel Business Analytics Applications 7.7.x (with Siebel CRM OLTP 7.7.0)

Rename771-7963.map

Siebel Business Analytics Applications 7.8.2 and all 7.8.x versions before this release

Rename782-7963.map

Siebel Business Analytics Applications 7.8.3 and all 7.8.x versions after this release

Rename783-7963.map

Oracle BI Applications 7.9.0

Rename79x-7963.map

Oracle BI Applications 7.9.1

Rename79x-7963.map

Oracle BI Applications 7.9.2

Rename79x-7963.map

Oracle BI Applications 7.9.3

Rename793to7963.map

Oracle BI Applications 7.9.4

Rename794to7963.map

Oracle BI Applications 7.9.5

Rename79x-7963.map

Oracle BI Applications 7.9.5.1

Rename7951to7963.map

Oracle BI Applications 7.9.5.2

Rename7951to7963.map

Oracle BI Applications 7.9.6

Rename79x-7963.map

Oracle BI Applications 7.9.6.2

rename7963to7964.map

Not required for upgrades from 7.9.6.2 to 7.9.6.3.

Oracle BI Applications 7.9.6.3

rename7963to7964.map

The syntax of the equalizerpds command is as follows:

equalizerpds.exe  [-B [password1]] -C base_repository_name [-E [password2]] -F repository2_name [-J udml_utf8_file_name_equalization] [-O ouput_repository_name] [-Y equalStringSet]
-Y          Treat the characters as equals.
/?          Display this usage information and exit.

To equalize a repository:

1. Copy the appropriate MAP file from the $ORACLE_BI_HOME\biapps\upgrade folder into the folder where you will execute equalizerpds.exe, for example, \OracleBIUpgrade\Original.

2. Run equalizerpds.exe to equalize the repository from the latest installation (for example, OracleBIAnalyticsApps.rpd) with the original repository (for example, OracleBIAnalyticsAppss_793.rpd). An example of the equalizerpds command is as follows:

equalizerpds -B SADMIN
-C \\OracleBIUpgrade\Original\OracleBIAnalyticsApps_791.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 $ORACLE_BI_HOME\biapps\upgrade folder.

If the equalizerpds.exe executable file runs correctly, no errors are returned.

3. Run equalizerpds.exe to equalize your customized repository (for example, Customer_OracleBIAnalyticsApps.rpd) with the original repository (for example, OracleBIAnalyticsApps_79x.rpd). An example of the equalizerpds command is as follows:

equalizerpds -B SADMIN
-C \\OracleBIUpgrade\Original\OracleBIAnalyticsApps_791.rpd
-E SADMIN
-F \\OracleBIUpgrade\Original\Customer_OracleBIAnalyticsApps.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.

4. 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).

6.14.3 Comparing the Oracle BI Repositories

Follow this procedure to compare your existing repository with the new version to which you are upgrading.

To compare the Oracle BI 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 Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition.

6.14.4 Merging the Oracle BI Repositories

In this procedure, you execute the main algorithm to upgrade the repository. For more information on merging the repositories, see Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition.

To merge versions of the Oracle BI repositories:

1. Copy the three repositories (for example, OracleBIAnalyticsApps_79x.rpd, OracleBIAnalyticsApps.rpd, and Customer_OracleBIAnalyticsApps.rpd) to the AfterMerge folder.

2. Open the repository from the latest installation (for example, OracleBIAnalyticsApps.rpd) in the \OracleBIUpgrade\AfterMerge folder.

3. From the Administration Tool menu bar, select File, then select Merge.

4. Select the Merge Type option Full Repository Merge.

5. In the Select Original Repository dialog box, select the original repository (for example, OracleBIAnalyticsApps_79x.rpd).

6. Enter the password for the original repository.

7. In the Select Modified Repository dialog box, select the repository that contains the customizations you made to the previous version of the Analytics repository.

8. Enter the password for the modified repository.

9. In the Saved Merged Repository as dialog box, enter the name for the merged repository, for example, Merged_Repository_OracleBIAnalyticsApps.rpd.
The new repository will contain the final results of the merge.

10. Select the Equalize during merge check box.

11. Click Next.

12. In the Decision drop-down list, select the action you want to take regarding the repository change, or accept the default action.

13. To locate subsequent rows with empty Decision fields, click the Decision header cell.
When all rows have a value in the Decision field, the Finish button is enabled.

14. Select the Check consistency of the merged RPD check box.

15. Click Finish.
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.

16. 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'

17. Copy the repository to the folder \OracleBIUpgrade\AfterManualWork.

6.15 Merging Oracle BI Applications Version 7.9.6.4 Presentation Catalog With Current (Custom) Catalog

Note:

Before you begin this procedure, you must have already upgraded your current (custom) catalog to the Oracle BI Enterprise Edition 11g format. For more information, see Section 6.13, "Upgrading the Oracle BI Repository and Presentation Catalog to the Oracle BI Enterprise Edition 11g Version."

You need to perform the following tasks to complete the presentation merge process.

- Section 6.15.1, "Trimming the Input Presentation Catalog"

- Section 6.15.2, "Merging the Oracle BI Applications Version 7.9.6.4 Presentation Catalog With Current (Custom) Catalog"

- Section 6.15.3, "Testing the Results of the Presentation Catalog Upgrade"

These procedures use the following terminology to identify the various presentation catalogs you will use in the merge process:

- The original presentation catalog. This catalog is the output from the step you performed in Section 6.13, "Upgrading the Oracle BI Repository and Presentation Catalog to the Oracle BI Enterprise Edition 11g Version." It is the version of the unmodified presentation catalog you received with the Oracle BI Applications release you are upgrading from that you upgraded to the 11g format.

- The new presentation catalog. This is the standard Oracle BI Applications 7.9.6.4 presentation catalog that is installed with Oracle BI Applications.

- The current presentation catalog. This catalog is the output from the step you performed in Section 6.13, "Upgrading the Oracle BI Repository and Presentation Catalog to the Oracle BI Enterprise Edition 11g Version." It is the presentation catalog currently in use at your organization that you upgraded to the 11g format.

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 Fusion Middleware Upgrade Guide for Oracle Business Intelligence

6.15.1 Trimming the Input Presentation Catalog

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.

6.15.2 Merging the Oracle BI Applications Version 7.9.6.4 Presentation Catalog With Current (Custom) Catalog

Note:

Before you begin this procedure, you must have already upgraded your current (custom) catalog to the Oracle BI Enterprise Edition 11g format. For more information, see Section 6.13, "Upgrading the Oracle BI Repository and Presentation Catalog to the Oracle BI Enterprise Edition 11g Version."

Follow the instructions in this section to merge the Oracle BI Applications version 7.9.6.4 presentation catalog with the catalog you are currently using. This procedure uses the Oracle BI Enterprise Edition Catalog Manager. High-level steps for the merge process are provided in this section. For detailed instructions on using the Catalog Manager, see the chapter "Configuring and Managing the Oracle BI Presentation Catalog," in the Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition 11g Release 1 (11.1.1).

To merge the Oracle BI Applications version 7.9.6.4 presentation catalog with the current (custom) catalog:

1. Start the Catalog Manager, and open your current (custom) presentation catalog in offline mode.
For instructions, see the section "Starting Catalog Manager and Opening Catalogs," in the Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition 11g Release 1 (11.1.1).

2. Start another instance of the Catalog Manager, and open the Oracle BI Applications version 7.9.6.4 (out-of-the-box) presentation catalog in offline mode.

3. Copy and paste the custom objects from your current presentation catalog into the Oracle BI Applications version 7.9.6.4 (out-of-the-box) presentation catalog.
For instructions, see the section "Working with Objects in Catalog Manager," in the Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition 11g Release 1 (11.1.1).

4. If you created custom catalog groups that are not in the version 7.9.6.4 presentation catalog, you need to convert the custom catalog groups to application roles in order to maintain consistency with the version 7.9.6.4 presentation catalog.
To convert custom catalog groups to application roles, run the following command:

runcat.cmd/runcat.sh -cmd replaceAccountInPermissions -old <Catalog Group Name> -oldType group -new <App Role Name> -newType role -offline  <catalog path>

For example:

runcat.cmd -cmd replaceAccountInPermissions -old "AP Analyst" -oldType group -new "AP Analyst" -newType role -offline  c:/SampleWebcat

This command replaces a specified account with another in all catalog object ACLs and privileges in the presentation catalog, entirely in the offline mode. If an entirely new application role is specified as the replacement account, then it is necessary to refresh the GUIDs in the presentation catalog before it can be used.

Note: If the specified replacement user or group is not already present in the presentation catalog 11g Release 1 (11.1.1) already, then this operation will fail.

For more information, see the Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition 11g Release 1 (11.1.1).

6.15.3 Testing the Results of the Presentation Catalog Upgrade

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.

6.16 Regression Testing the Oracle BI Repository Merge

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:

1. 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.

2. 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 Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition.

3. Execute the logical SQL against the old repository using the command line utility nQCmd.exe located in $ORACLE_BI_HOME\bifoundation\server\bin, and save the results to a file.
For information about the nQCmd.exe utility, see Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition.

4. Edit the logical SQL test scripts to account for the name changes or modifications resulting from the upgrade.

5. Execute the edited logical SQL against the merged repository, and save the results.

6. 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.

Part III

Upgrading When Your Source System is PeopleSoft

Part III contains instructions for upgrading to the current release of Oracle BI Applications when you are running PeopleSoft Enterprise Applications as your source system.

Part III contains Chapter 7, "Upgrading Oracle BI Applications for PeopleSoft Source Systems."

7 Upgrading Oracle BI Applications for PeopleSoft Source Systems

This section contains instructions for upgrading Oracle BI Applications when you are running PeopleSoft Enterprise Applications as your source system.

This section includes the following topics:

- Section 7.1, "Prerequisites for Upgrading Oracle BI Applications"

- Section 7.2, "Upgrading Oracle BI Infrastructure to Version 11g"

- Section 7.3, "Upgrading Oracle BI Applications"

- Section 7.4, "Upgrading to Informatica PowerCenter Version 9.0.1 Hotfix 2"

- Section 7.5, "Upgrading the Informatica Repository"

- Section 7.6, "Upgrading the Informatica Repository When You Are Already Running Informatica PowerCenter 9.1"

- Section 7.7, "Verifying Configurations for Informatica PowerCenter Version 9.0.1 Hotfix 2 to Work With Oracle BI Applications and DAC"

- Section 7.8, "Upgrading to and Configuring DAC Version 11g"

- Section 7.9, "Upgrading the Data Warehouse Schema and Migrating Data for Non-Teradata Databases"

- Section 7.10, "Upgrading the Data Warehouse Schema and Migrating Data for Teradata Databases"

- Section 7.11, "Localizing the Policy Store"

- Section 7.12, "Importing the Oracle BI Applications Version 7.9.6.4 LDIF File Into the Embedded LDAP Server"

- Section 7.13, "Upgrading the Oracle BI Repository and Presentation Catalog to the Oracle BI Enterprise Edition 11g Version"

- Section 7.14, "Merging Oracle BI Applications Version 7.9.6.4 Repository With Customer Repository"

- Section 7.15, "Merging Oracle BI Applications Version 7.9.6.4 Presentation Catalog With Current (Custom) Catalog"

- Section 7.16, "Regression Testing the Oracle BI Repository Merge"

7.1 Prerequisites for Upgrading Oracle BI Applications

Complete the following prerequisites before upgrading to Oracle BI Applications release 7.9.6.4:

- The DAC Client requires an ODBC connection to the Oracle Business Analytics Warehouse when the database type is Oracle, SQL Server, DB2, and DB2-390 in order to upgrade the data warehouse schema using the DDL Import Utility.
Before you upgrade to Oracle BI Applications verify whether you have the appropriate ODBC connections set. If you do not, see Appendix F, "Creating ODBC Database Connections for DAC."

7.2 Upgrading Oracle BI Infrastructure to Version 11g

You must upgrade Oracle BI Infrastructure to version 11g. For the specific release of Oracle BI Infrastructure 11g that is supported for this release of Oracle BI Applications, see the System Requirements and Supported Platforms for Oracle Business Intelligence Applications. For information on installing the supported version of Oracle BI Infrastructure, see the Oracle Fusion Middleware Upgrade Guide for Oracle Business Intelligence.

7.3 Upgrading Oracle BI Applications

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 Guide for Informatica PowerCenter Users.

Note the following points:

- Review "Chapter 3: Preinstallation and Predeployment Requirements for Oracle BI Applications," in the Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users. You must satisfy these requirements in order to upgrade to the current version of Oracle BI Applications.

- Perform only the step that addresses the running of the installer. Do not perform the configuration instructions that follow the running of the installer.

- If you have a previous release of Oracle BI Applications installed, you must uninstall it before you run the installer for the current release. If you do not uninstall the old release, some folders from the current release will not be correctly installed. (Make a back-up of your DAC folder before you uninstall the old release. This will be the backup of your DAC Client and Server and the DAC metadata files.)

7.4 Upgrading to Informatica PowerCenter Version 9.0.1 Hotfix 2

You must install Informatica PowerCenter 9.0.1 Hotfix 2 to run the current version of Oracle BI Applications. See the System Requirements and Supported Platforms for Oracle Business Intelligence Applications for information about additional hotfixes or emergency bug fixes that may be required to support the current version of Informatica.

Note:

Oracle BI Applications release 7.9.6.4 is also certified to run with Informatica PowerCenter version 9.1 Hotfix 2. For instructions on upgrading the Informatica Repository if you have previously upgraded to Informatica PowerCenter 9.1 Hotfix 2, see Section 7.6, "Upgrading the Informatica Repository When You Are Already Running Informatica PowerCenter 9.1."

The components and architecture for Informatica PowerCenter 9.x differ significantly from Informatica PowerCenter 7.x and 8.x. Oracle recommends that you carefully review the Informatica PowerCenter 9.0.1 documentation.

For a summary of installation instructions for installing Informatica PowerCenter 9.0.1 on a single machine in an Oracle BI Applications deployment, see the Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users.

For detailed information about deploying Informatica PowerCenter 9.0.1, refer to the Informatica PowerCenter Installation and Configuration Guide, Informatica Upgrade Guide for PowerCenter 8.1.x, Informatica Upgrade Guide for PowerCenter 8.5.x and 8.6.x, Informatica Administrator Guide, and related documentation. See the Oracle Business Intelligence Applications Release Notes, available on the Oracle Technology Network, for information about how to locate the Informatica documentation.

To upgrade to Informatica PowerCenter 9.0.1 Hotfix 2:

- Perform the pre-upgrade, upgrade, and post-upgrade steps documented in Informatica Upgrade Guide for PowerCenter 8.1.x or Informatica Upgrade Guide for PowerCenter 8.5.x and 8.6.x, depending on which version of Informatica PowerCenter you are upgrading from.

Note the following points:

- The Informatica PowerCenter 9.0.1 installation process includes upgrading your current Informatica Repository to the version 9.0.1 format. This process is necessary so that you will be able to access your current repository using the version 9.0.1 client tools and so that you can perform the procedure Section 7.5, "Upgrading the Informatica Repository."
In Section 7.5, "Upgrading the Informatica Repository," you back up and rename your current repository and then restore the Informatica Repository that is installed during the Oracle BI Applications installation (for example, Oracle_BI_DW_Base.rep). You then copy the folders containing the Oracle BI Applications content for release 7.9.6.4 to your existing repository.

- If you install Informatica PowerCenter 9.0.1 using the installer Upgrade option rather than the Install option, the property $PMRootDir is not updated to the upgraded service version installation directory. You need to configure this property to specify the upgraded service installation directory in order for DAC to be able to locate the Informatica source files.
To configure the $PMRootDir property: launch Informatica Administrator, select the Integration Service from the Navigator, click the Processes tab, and click Edit. Then, enter the appropriate value for $PMRootDir.

7.5 Upgrading the Informatica Repository

Follow this procedure to upgrade the Informatica Repository when you are upgrading the Informatica PowerCenter platform from version 7.x or 8.x to 9.0.1 Hotfix 2. If you have already upgraded to Informatica PowerCenter 9.1, follow the procedure in Section 7.6, "Upgrading the Informatica Repository When You Are Already Running Informatica PowerCenter 9.1."

In this procedure, you will copy the folders containing the Oracle BI Applications 7.9.6.4 content into your current, existing Informatica Repository. The result of this action is an Informatica Repository that contains your customizations along with the new Oracle BI Applications 7.9.6.4 content.

For detailed instructions on backing up and restoring the Informatica Repository, see the topic titled, "Backing Up and Restoring the PowerCenter Repository," in "Chapter 15: PowerCenter Repository Management," in the Informatica PowerCenter Administrator Guide. See the Oracle Business Intelligence Applications Release Notes, available on the Oracle Technology Network, for information about how to locate the Informatica documentation.

To upgrade the Informatica Repository:

1. Make sure you have backed up and renamed your current, existing Informatica Repository.

2. Copy the Oracle_BI_DW_Base.rep file (or Oracle_BI_DW_Teradata.rep for repositories on Teradata databases) from the folder OracleBI\dwrep\Informatica\Repository into the folder <INFA_HOME>\server\infa_shared\Backup.

Note:

The Oracle_BI_DW_Base.rep file is installed in the OracleBI root directory when you run the Oracle BI Applications installer, as described in Section 7.3, "Upgrading Oracle BI Applications."

3. Using Informatica PowerCenter Administrator, create a new Repository Service for the Oracle_BI_DW_Base.rep repository. See "Setup Step: Creating the Informatica Repository Service," in Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users for instructions.

4. Using the Repository Service you created in the step above, restore the Oracle_BI_DW_Base.rep repository into an empty schema. See "Restoring the Prebuilt Informatica Repository for Environments in English" or "Restoring the Prebuilt Informatica Repository on a Non-English Operating System" in Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users for instructions.
This step gives you the Oracle BI Applications 7.9.6.4 Informatica Repository in the Informatica 9.0.1 format.

5. Launch the Informatica PowerCenter Repository Manager, and connect to the repository you restored in step 4 (for example, Oracle_BI_DW_Base.rep), and connect to your current, existing Informatica Repository.
Note: Your current, existing repository should have been updated to the version 9.0.1 format during the Informatica PowerCenter 9.0.1 installation process.

6. In your current, existing repository, make sure all of your customizations are in a "Custom" folder.

7. In your current, existing repository, delete the following folders:

- PLP

- All folders with the prefix SDE_

- SILOS

- SIL_VERT

- UA_SDE

- UA_SIL

Make sure you do not delete the "Custom" folder.

8. Copy the following folders containing the Oracle BI Applications content for release 7.9.6.4 from the newly restored repository (Oracle_BI_DW_Base.rep) into your current, existing repository.

- PLP

- All folders with the prefix SDE_

- SILOS

- SIL_VERT

- UA_SDE

- UA_SIL

This action updates your current, existing repository with the Oracle BI Applications 7.9.6.4 content; this is the repository you will use to run ETL in Oracle BI Applications 7.9.6.4.

The version 7.9.6.4 repository (Oracle_BI_DW_Base.rep) and the Repository Service for this repository are no longer needed.

7.6 Upgrading the Informatica Repository When You Are Already Running Informatica PowerCenter 9.1

If you are upgrading to Oracle BI Applications 7.9.6.4 and previously upgraded Informatica PowerCenter to version 9.1 Hotfix 2, you must first restore the Oracle BI Applications version 7.9.6.4 Informatica Repository using Informatica PowerCenter 9.0.1 Hotfix 2. Then, you can upgrade this repository to the Informatica 9.1 format by pointing to it using Informatica 9.1 client tools. After the Oracle BI Applications 7.9.6.4 Informatica Repository has been upgraded to the Informatica 9.1 format, you can then copy the folders containing the Oracle BI Applications 7.9.6.4 content into your current, existing Informatica Repository. The result of this action is an Informatica Repository that contains your customizations along with the new Oracle BI Applications 7.9.6.4 content.

For detailed instructions on backing up and restoring the Informatica Repository, see the topic titled, "Backing Up and Restoring the PowerCenter Repository," in "Chapter 15: PowerCenter Repository Management," in the Informatica PowerCenter Administrator Guide. See the Oracle Business Intelligence Applications Release Notes, available on the Oracle Technology Network, for information about how to locate the Informatica documentation.

To upgrade the Informatica Repository when already running Informatica PowerCenter 9.1:

1. Make sure you have backed up and renamed your current, existing Informatica Repository.

2. Install Informatica PowerCenter Services version 9.0.1 Hotfix 2. You do not need to install the Informatica PowerCenter Client Tools. See Section 7.4, "Upgrading to Informatica PowerCenter Version 9.0.1 Hotfix 2" for instructions.

3. Copy the Oracle_BI_DW_Base.rep file (or Oracle_BI_DW_Teradata.rep for repositories on Teradata databases) from the folder OracleBI\dwrep\Informatica\Repository into the Informatica PowerCenter 9.0.1 folder <INFA_HOME>\server\infa_shared\Backup.

Note:

The Oracle_BI_DW_Base.rep file is installed in the OracleBI root directory when you run the Oracle BI Applications installer, as described in Section 7.3, "Upgrading Oracle BI Applications."

4. Using Informatica PowerCenter Administrator, create a new Repository Service for the Oracle_BI_DW_Base.rep repository. See "Setup Step: Creating the Informatica Repository Service," in Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users for instructions.

5. Using the Repository Service you created in the step above, restore the Oracle_BI_DW_Base.rep repository into an empty schema. See "Restoring the Prebuilt Informatica Repository for Environments in English" or "Restoring the Prebuilt Informatica Repository on a Non-English Operating System" in Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users for instructions.
This step gives you the Oracle BI Applications 7.9.6.4 Informatica Repository in Informatica 9.0.1 format.

6. Launch the Informatica PowerCenter Repository Manager, and connect to the repository you restored in step 5. When prompted to upgrade the repository to the 9.1 format, do so.

7. In Repository Manger, connect to your current, existing Informatica Repository.

8. In your current, existing repository, make sure all of your customizations are in a "Custom" folder.

9. In your current, existing repository, delete the following folders:

- PLP

- All folders with the prefix SDE_

- SILOS

- SIL_VERT

- UA_SDE

- UA_SIL

Make sure you do not delete the "Custom" folder.

10. Copy the following folders containing the Oracle BI Applications content for release 7.9.6.4 from the newly restored repository (Oracle_BI_DW_Base.rep) into your current, existing repository.

- PLP

- All folders with the prefix SDE_

- SILOS

- SIL_VERT

- UA_SDE

- UA_SIL

This action updates your current, existing repository with the Oracle BI Applications 7.9.6.4 content; this is the repository you will use to run ETL in Oracle BI Applications 7.9.6.4.

The version 7.9.6.4 repository (Oracle_BI_DW_Base.rep) and the Repository Service for this repository are no longer needed.

7.7 Verifying Configurations for Informatica PowerCenter Version 9.0.1 Hotfix 2 to Work With Oracle BI Applications and DAC

Informatica PowerCenter version 9.0.1 Hotfix 2 requires configuration for it to work with Oracle BI Applications and DAC. The configuration settings from your earlier Informatica environment may have been retained when you upgraded to Version 9.0.1 Hotfix 2. Verify or perform the procedures listed below, as documented in the Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users:

- Copying Source Files and Lookup Files

- Setting PowerCenter Integration Services Relaxed Code Page Validation

- Setting PowerCenter Integration Services Custom Properties

- Creating the Repository Administrator User in the Native Security Domain

7.8 Upgrading to and Configuring DAC Version 11g

This section includes instructions for upgrading the DAC platform and repository to version 11g as well as information about configurations you must set or verify.

This section includes the following topics:

- Section 7.8.1, "Installing the DAC Platform and Oracle BI Applications Metadata Repository Files"

- Section 7.8.2, "Configuring the DAC Client and Server to Work With Oracle BI Applications and Informatica"

- Section 7.8.3, "Upgrading the DAC Repository"

7.8.1 Installing the DAC Platform and Oracle BI Applications Metadata Repository Files

The current release of DAC 11g is installed by its own installer and not the Oracle BI Applications installer. For information about the specific release of DAC 11g that is supported for this release of Oracle BI Applications, see System Requirements and Supported Platforms for Oracle Business Intelligence Applications.

After you install DAC 11g, you then need to copy metadata files from the machine hosting Oracle BI Applications to the machines hosting the DAC Client and Server. You then need to import the new metadata into the DAC Repository. For instructions on performing these tasks, see the following sections in the Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users:

- Installing and Setting Up the DAC Platform

Note:

You must perform all of the procedures in this section, including installing JDBC drivers, creating ODBC database connections, and installing pmrep and pmcmd command line programs.

- Installing DAC Metadata Files

- Logging into DAC for the First Time and Importing Metadata into the DAC Repository

Note:

When you perform this step, DAC will prompt you to upgrade the repository. Click Yes. This action will upgrade your repository in the 10g format to the 11g format.

After you complete this procedure, you will have the default DAC Repository for Oracle BI Applications release 7.9.6.4.

7.8.2 Configuring the DAC Client and Server to Work With Oracle BI Applications and Informatica

The DAC Client and Server require configuration to work with Oracle BI Applications and Informatica PowerCenter. The configuration settings from your earlier DAC environment may have been retained when you upgraded to version 11g. Verify or perform the procedures listed below, as documented in the Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users:

- Configuring the DAC Server

- Configuring DAC Integration Settings

- Configuring the SiebelUnicodeDB Custom Property

Note:

This procedure is required only if your source to target data movement configuration is Unicode to Unicode.

- Setting Up DAC to Receive Email Notification

- Additional Configuration Tasks
In this section, perform only the tasks that apply to your environment.

7.8.3 Upgrading the DAC Repository

To upgrade the DAC Repository, you perform a two-step process:

1. You first upgrade the existing DAC Repository from the 10g format to the 11g format. When you log into DAC 11g for the first time, DAC will prompt you to upgrade your repository. Click Yes.
For more information, see "Upgrading to DAC 11g" in Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Data Warehouse Administration Console and "Logging Into DAC for the First Time and Importing Metadata into the DAC Repository" in Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users.

2. You then use the DAC's Upgrade/Merge Wizard to complete the upgrade of your existing DAC Repository.

- If you are upgrading to Oracle BI Applications release 7.9.6.4, and you are remaining on the same version of the transactional source system, you would use the Refresh Base option of the DAC Upgrade/Merge Wizard to complete the upgrade of your existing DAC Repository. For information about how to use the Refresh Base option, see the topic titled, "About the Refresh Base Option," in the chapter "Upgrading, Comparing and Merging DAC Repositories," in the Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Data Warehouse Administration Console.

- If you are upgrading your transactional system, for example, from Oracle EBS release 12 to release 12.2, you would use the Replace Base option of the DAC Upgrade/Merge Wizard to complete the upgrade of your existing DAC Repository. For information about how to use the Replace Base option, see the topic titled, "About the Replace Base Option," in "Upgrading, Comparing and Merging DAC Repositories," in the Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Data Warehouse Administration Console.

The Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Data Warehouse Administration Console is available in the Oracle Business Intelligence Data Warehouse Administration Console Documentation Library on the Oracle Technology Network.

7.9 Upgrading the Data Warehouse Schema and Migrating Data for Non-Teradata Databases

This section contains the following topics:

- Section 7.9.1, "Performing Data Warehouse Schema Upgrade Steps Common to All Previous Releases"

- Section 7.9.2, "Upgrading the Data Warehouse Schema From Version 7.9.3 to 7.9.4 and Migrating Data"

- Section 7.9.3, "Upgrading the Data Warehouse Schema From Version 7.9.4 to 7.9.5 and Migrating Data"

- Section 7.9.4, "Upgrading the Data Warehouse Schema From Version 7.9.5 to 7.9.5.1 and Migrating Data"

- Section 7.9.5, "Upgrading the Data Warehouse Schema From Version 7.9.5.1 to 7.9.6.1 and Migrating Data"

- Section 7.9.6, "Upgrading the Data Warehouse Schema From Version 7.9.6 to 7.9.6.1 and Migrating Data" (Applicable only if you are using an Oracle database as your data warehouse database.)

- Section 7.9.7, "Upgrading the Data Warehouse Schema From Version 7.9.6.1 to 7.9.6.2 and Migrating Data"

- Section 7.9.8, "Upgrading the Data Warehouse Schema From Version 7.9.6.2 to 7.9.6.3 and Migrating Data"

- Section 7.9.9, "Upgrading the Data Warehouse Schema From Version 7.9.6.3 to 7.9.6.4 and Migrating Data"

If you are currently running Oracle BI Applications version 7.9.3, you need to perform the procedures in Section 7.9.1, Section 7.9.2, Section 7.9.3, Section 7.9.4, Section 7.9.5, Section 7.9.7, Section 7.9.8, and Section 7.9.9.

If you are currently running Oracle BI Applications version 7.9.4, you need to perform the procedures in Section 7.9.1, Section 7.9.3, Section 7.9.4 and Section 7.9.5, Section 7.9.7, Section 7.9.8, and Section 7.9.9.

If you are currently running Oracle BI Applications version 7.9.5, you need to perform the procedures in Section 7.9.1, Section 7.9.4 and Section 7.9.5, Section 7.9.7, Section 7.9.8, and Section 7.9.9.

If you are currently running Oracle BI Applications version 7.9.5.1, you need to perform the procedures in Section 7.9.1, Section 7.9.5, Section 7.9.7, Section 7.9.8, and Section 7.9.9.

If you are currently running Oracle BI Applications version 7.9.6, you need to perform the procedures in Section 7.9.1, Section 7.9.6, Section 7.9.7, Section 7.9.8, and Section 7.9.9.

If you are currently running Oracle BI Applications version 7.9.6.1, you need to perform the procedures in Section 7.9.1, Section 7.9.7, Section 7.9.8, and Section 7.9.9

If you are currently running Oracle BI Applications version 7.9.6.2, you need to perform the procedures in Section 7.9.1, Section 7.9.8, and Section 7.9.9.

If you are currently running Oracle BI Applications version 7.9.6.3, you need to perform the procedures in Section 7.9.1 and Section 7.9.9.

These procedures add new tables, columns, and indexes to the existing data warehouse schema. They also modify the existing data warehouse schema objects.

7.9.1 Performing Data Warehouse Schema Upgrade Steps Common to All Previous Releases

The steps in this procedure are required for upgrading to Oracle BI Applications release 7.9.6.4 from all previous releases.

To perform common data warehouse upgrade steps:

1. Copy all of the domain value files in the folder \OracleBI\dwrep\Informatica\LkpFiles into the folder <INFA_HOME>\server\infa_shared\LkpFiles.

2. Restore the Upgrade repository:

1. Copy the file Upgrade.rep from the folder OracleBI\dwrep\Upgrade\Informatica\Repository into the folder <INFA_HOME>\server\infa_shared\Backup.

2. Launch the Informatica Administrator, and restore Upgrade.rep (located in <INFA_HOME>\server\infa_shared\Backup).

3. Configure connections for the OLAP and OLTP databases.

Note:

Make sure all the PeopleSoft source (OLTP) connections are created as Application connections and the OLAP connections are created as Relational connections.

1. In Informatica Workflow Manager, open the Application Connection Browser (in the menu bar, select Connections, and then select Application), and configure the parameter PARAM_OLTP to match your OLTP environment.

2. Open the Relational Connection Browser (in the menu bar, select Connections, and then select Relational), and configure the parameter PARAM_OLAP to match your OLAP environment.

3. If you are upgrading Oracle Financial Analytics, configure PARAM_OLTP_PFST_FIN to point to the PeopleSoft Financials Pillar database.
Note: This connection is present as both an Application connection and Relational connection. You must configure both of them to point to the PeopleSoft Financial Pillar database.

4. If you are upgrading Oracle Human Resources Analytics, configure PARAM_OLTP_PSFT_HR to point to the PeopleSoft HRMS Pillar database.
Note: This connection is present as an Application connection only.

5. Configure the Relational connection PARAM_DAC to match your DAC database connection.

6. Configure a Relational connection with the same name defined in the DAC Physical Data Sources tab for the OLAP connection. The Type specified in DAC is "Warehouse." The default name for this connection is "Datawarehouse."

7. Configure an Application connection with the same name defined in the DAC Physical Data Sources tab for the OLTP connection. The Type specified in DAC is "Source."

Note:

If you are connected to an Oracle database, use the 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.

4. Make sure all the date parameters are set up with an appropriate format.
For example, the format for $$LOW_DATE is as follows:

SIL_EmployeeDimension_Full]
$$TYPE2_FLG=Y
$DBConnection_OLAP=adevuni_fl1
MPLT_GET_ETL_PROC_WID.$$ETL_PROC_WID=1
$$LOW_DATE=to_date('01/01/1970','MM/DD/YYYY')
mplt_SIL_EmployeeDimension.$$LANGUAGE_CODE=E
mplt_SIL_EmployeeDimension.$$MASTER_CODE_NOT_FOUND=NA
mplt_SIL_EmployeeDimension.$$SOURCE_CODE_NOT_SUPPLIED=NA

7.9.2 Upgrading the Data Warehouse Schema From Version 7.9.3 to 7.9.4 and Migrating Data

Follow this procedure to upgrade from Oracle BI Applications release 7.9.3 to 7.9.4.

To upgrade the data warehouse schema and migrate data into the upgraded data warehouse:

1. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade repository. For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Upgrade Informatica Repository."

2. Run the 794_UPGRADE_PRE_CTL_SCRIPT.sql. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

3. Run the UPGRADE_794.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

4. Run ddl_794.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

5. Run the 794_UPGRADE_PRE_DIMENSION_SCRIPT.sql script. This file is located in the OracleBI\dwrep\Upgrade\DbScripts\<database type> folder.

6. Migrate data into the upgraded data warehouse.

1. Configure the Informatica parameter file 794_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 794_UPG_PARAMS.txt."

2. In Informatica Workflow Manager, navigate to the folder UPGRADE_793_to_794_PSFT88, and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

7. Verify the data migrated successfully.

1. Validate the data in the upgraded data warehouse.

2. Check whether any of the Informatica mapping log files stored in the <INFA_HOME>\server\infa_shared\SessLogs directory indicate errors or failures.

3. Check whether the script 794_UPGRADE_PRE_DIMENSION_SCRIPT.sql that you ran in the SQL client of the database failed or errored out while executing.

4. Check the log file for the ddl_794.ctl and Upgrade_794.ctl scripts, which 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.

Note:

Ignore any error messages that indicate tables or indexes could not be dropped from the database. These error messages are displayed when the specified objects do not exist in the database. This can occur because each source system container holds a subset of all data warehouse tables

8. If the data migration was successful, drop the tables that were created during the upgrade process, such as, W_xxxx_x_79x tables, LKP_xxxx_x and 79x_XXXX_TMP.
This step frees the space occupied by these backup tables.

9. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep). For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Base Informatica Repository."

7.9.3 Upgrading the Data Warehouse Schema From Version 7.9.4 to 7.9.5 and Migrating Data

Follow this procedure to upgrade from Oracle BI Applications release 7.9.4 to 7.9.5.

To upgrade the data warehouse schema and migrate data into the upgraded data warehouse:

1. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade repository. For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Upgrade Informatica Repository."

2. Run the 795_UPGRADE_PRE_CTL_SCRIPT.sql. This file is located in the OracleBI\dwrep\Upgrade\DbScripts\<database type> folder.

3. Run the UPGRADE_795.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

4. Run the ddl_795.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

5. Run the 795_UPGRADE_PRE_DIMENSION_SCRIPT.sql script. This file is located in the folder OracleBI\dwrep\Upgrade\DbScripts\<database type>.

6. Migrate data into the upgraded data warehouse.

1. Configure the Informatica parameter file 795_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 795_UPG_PARAMS.txt."

2. In Informatica Workflow Manager, navigate to the folder UPGRADE_794_to_795_PSFT88 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

7. Verify the data migrated successfully.

1. Validate the data in the upgraded data warehouse.

2. Check whether any of the Informatica mapping log files stored in the <INFA_HOME>\server\infa_shared\Sesslogs directory indicates errors or failures.

3. Check whether the script 795_UPGRADE_PRE_DIMENSION_SCRIPT.sql that you ran in the SQL client of the database failed or errored out while executing.

4. Check the log file for the ddl_795.ctl and Upgrade_795.ctl scripts, which 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.

8. If the data migration was successful, drop the tables that were created during the upgrade process, such as W_xxxx_x_79x, LKP_xxxx_x and 79x_xxxx_TMP.
This step frees the space occupied by these backup tables.

9. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep). For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Base Informatica Repository."

7.9.4 Upgrading the Data Warehouse Schema From Version 7.9.5 to 7.9.5.1 and Migrating Data

Follow this procedure to upgrade from Oracle BI Applications release 7.9.5 to 7.9.5.1.

To upgrade the data warehouse schema and migrate data:

1. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade repository. For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Upgrade Informatica Repository."

2. Run the 7951_UPGRADE_PRE_CTL_SCRIPT.sql. This file is located in the folder OracleBI\dwrep\Upgrade\DbScripts\<database type>.

3. Run the UPGRADE_7951.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

4. Run the ddl_7951.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

5. Run the 7951_UPGRADE_PRE_DIMENSION_SCRIPT.sql script. This file is located in the folder OracleBI\dwrep\Upgrade\DbScripts\<database type>.

6. Migrate data into the upgraded data warehouse.

1. Configure the Informatica parameter file 7951_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7951_UPG_PARAMS.txt."

2. In Informatica Workflow Manager, navigate to the folder UPGRADE_795_to_7951_PSFT and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

7. Verify the data migrated successfully.

1. Validate the data in the upgraded data warehouse.

2. Check whether any of the Informatica mapping log files stored in the <INFA_HOME>\server\infa_shared\Sesslogs directory indicates errors or failures.

3. Check whether the script 7951_UPGRADE_PRE_DIMENSION_SCRIPT.sql that you ran in the SQL client of the database failed or errored out while executing.

4. Check the log file for the ddl_7951.ctl and Upgrade_7951.ctl scripts, which 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.

Note:

Ignore any error messages that indicate tables or indexes could not be dropped from the database. These error messages are displayed when the specified objects do not exist in the database. This can occur because each source system container holds a subset of all data warehouse tables

8. If the data migration was successful, drop the tables that were created during the upgrade process, such as W_xxxx_x_79x, LKP_xxxx_x and 79x_xxxx_TMP.
This step frees the space occupied by these backup tables.

9. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep). For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Base Informatica Repository."

7.9.5 Upgrading the Data Warehouse Schema From Version 7.9.5.1 to 7.9.6.1 and Migrating Data

Follow this procedure to upgrade from Oracle BI Applications release 7.9.5.1 to 7.9.6.1.

This section includes the following topics:

- Section 7.9.5.1, "Upgrading the Data Warehouse Schema to Version 7.9.6.1"

- Section 7.9.5.2, "Migrating Data into the Upgraded Data Warehouse"

- Section 7.9.5.3, "Verifying the Data Migrated Successfully"

7.9.5.1 Upgrading the Data Warehouse Schema to Version 7.9.6.1

Follow this procedure to upgrade the data warehouse schema to version 7.9.6.1.

Note: Upgrading to version 7.9.6.1 may involve running scripts that have a "796_" prefix.

To upgrade the data warehouse schema to version 7.9.6.1:

1. If you are using an Oracle database, run the 796_UPGRADE_DROP_INDEXES.sql script.

1. Open the SQL client for your database type.

2. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Oracle.

3. Open the 796_UPGRADE_DROP_INDEXES. sql file, and copy the contents into the SQL client.

4. Execute the script.

2. If you are using a SQL Server or DB2 database, run the 7961_UPGRADE_DROP_INDEXES.sql script.

1. Open the SQL client for your database type.

2. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\<database type>.

3. Open the 7961_UPGRADE_DROP_INDEXES. sql file, and copy the contents into the SQL client.

4. Execute the script.

3. If you are using a SQL Server database, run the 7961_UPGRADE_PRE_UPG_CTL_SCRIPT.sql file. This file is located in OracleBI\dwrep\Upgrade\DbScripts\SQLServer.

4. Run the UPGRADE_796.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

5. Run the 7961_UPGRADE_PRE_CTL_SCRIPT.sql:

1. Go to OracleBI\dwrep\Upgrade\DbScripts\<database type> folder, and open the 7961_UPGRADE_PRE_CTL_SCRIPT.sql file.

2. Search for the Datasource_Num_ID parameter, and make sure the value is correct for your existing implementation.

3. If you are using a DB2 database, search for the text "TBS_32K," and replace it with the appropriate 32K table space name that you have configured.

4. Execute the script.

6. Run the ddl_7961.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

7. Run the 796_UPGRADE_PRE_DIMENSION_SCRIPT.sql script. This file is located in the folder OracleBI\dwrep\Upgrade\DbScripts\<database type>.

7.9.5.2 Migrating Data into the Upgraded Data Warehouse

Follow this procedure to migrate data into the upgraded data warehouse.

To migrate data into the upgraded data warehouse:

1. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository. For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Upgrade Informatica Repository."

2. Configure the Informatica parameter file 796_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 796_UPG_PARAMS.txt."

3. If you are upgrading Oracle Financial Analytics, you need to configure specific parameters and update mappings. For more information, see Section A.3.1, "Setting Parameters and Mappings in 796_UPG_PARAMS.txt for Oracle Financial Analytics."

4. If you are upgrading Oracle Project Analytics, you need to configure specific parameters. For more information, see Section A.3.2, "Setting Parameters in 796_UPG_PARAMS.txt for Oracle Project Analytics."

5. Back up and truncate table W_POSITION_DH.

6. If you are using PeopleSoft version 8.8, in Informatica Workflow Manager, navigate to the folder UPGRADE_7951_to_796_PSFT88 and execute the following workflows in the order as they appear:

- UPGRADE_DIMENSIONS

- UPGRADE_FACTS

- RESET_DAC_REFRESH_DATES

If you are using PeopleSoft version 8.9 or 9.0, in Informatica Workflow Manager, navigate to the folder UPGRADE_7951_to_796_PSFT90 and execute the following workflows in the order as they appear:

- UPGRADE_DIMENSIONS

- UPGRADE_FACTS

- RESET_DAC_REFRESH_DATES

7. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep). For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Base Informatica Repository."

8. Run the 7961_UPGRADE_PRE_DIMENSION_SCRIPT.sql script. This file is located in the folder OracleBI\dwrep\Upgrade\DbScripts\<database type>.

9. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository. For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Upgrade Informatica Repository."

10. Configure the Informatica parameter file 7961_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7961_UPG_PARAMS.txt."

11. If you are using PeopleSoft version 8.8, in Informatica Workflow Manager, navigate to the folder UPGRADE_796_to_7961_PSFT88 and execute the first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using PeopleSoft versions 8.9 or 9.0, in Informatica Workflow Manager, navigate to the folder UPGRADE_796_to_7961_PSFT90 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

12. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep). For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Base Informatica Repository."

13. Run the 7961_UPGRADE_POST_SCRIPT.sql. This file is located in the folder OracleBI\dwrep\Upgrade\DbScripts\<database type>.

7.9.5.3 Verifying the Data Migrated Successfully

Follow this procedure to verify that the data was migrated successfully into the upgraded data warehouse.

To verify the data migrated successfully:

1. Validate the data in the upgraded data warehouse.

2. Check whether any of the Informatica mapping log files stored in the <INFA_HOME>\server\infa_shared\Sesslogs directory indicates errors or failures.

3. Check whether the following scripts that you ran in the SQL client of the database failed or errored out while executing:
7961_UPGRADE_DROP_INDEXES.sql

7961_UPGRADE_PRE_CTL_SCRIPT.sql

7961_UPGRADE_PRE_DIMENSION.sql

7961_UPGRADE_POST_SCRIPT.sql

4. Check the log files for the ddl_7961.ctl and Upgrade_7961.ctl scripts, which 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.

Note:

Ignore any error messages that indicate tables or indexes could not be dropped from the database. These error messages are displayed when the specified objects do not exist in the database. This can occur because each source system container holds a subset of all data warehouse tables

5. If the data migration was successful, drop the tables that were created during the upgrade process, such as W_xxxx_x_79x, LKP_xxxx_x and 79x_xxxx_TMP.
This step frees the space occupied by these backup tables.

6. Once the data migration steps above are complete, you can delete the Upgrade repository to avoid any accidental use or confusion.

1. In the Informatica Administrator, select the Upgrade repository service.

2. In the General Properties area of the Properties tab, click Edit.

3. Make sure the operating mode of the repository service is set to Exclusive.

4. Click OK.

5. Choose Actions, and then click Delete Contents.

6. In the Delete contents for <repository name> dialog, enter the repository username and password, then click OK.

7.9.6 Upgrading the Data Warehouse Schema From Version 7.9.6 to 7.9.6.1 and Migrating Data

Perform the procedures in this section if you are upgrading from Oracle BI Applications release 7.9.6 to release 7.9.6.1.

Note:

This procedure is applicable only if you are using an Oracle database for your data warehouse database.

This section includes the following procedures:

- Section 7.9.6.1, "Upgrading the Data Warehouse Schema to Version 7.9.6.1"

- Section 7.9.6.2, "Migrating Data into the Upgraded Data Warehouse"

- Section 7.9.6.3, "Verifying the Data Migrated Successfully"

7.9.6.1 Upgrading the Data Warehouse Schema to Version 7.9.6.1

Follow this procedure to upgrade the data warehouse schema to version 7.9.6.1.

To upgrade the data warehouse schema to version 7.9.6.1:

1. Run the UPGRADE_7961.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

2. Run the 796ORA_TO_7961ORA_UPGRADE_PRE_CTL_SCRIPT.sql. This file is located in the folder OracleBI\dwrep\Upgrade\DbScripts\Oracle.

3. Run the ddl_7961.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

7.9.6.2 Migrating Data into the Upgraded Data Warehouse

Follow this procedure to migrate data into the upgraded data warehouse.

To migrate data into the upgraded data warehouse:

1. Run the 7961_UPGRADE_PRE_DIMENSION_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Oracle.

2. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade repository. For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Upgrade Informatica Repository."

3. Configure the Informatica parameter file 7961_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7961_UPG_PARAMS.txt."

4. If you are using PeopleSoft version 8.8, in Informatica Workflow Manager, navigate to the folder UPGRADE_796_to_7961_PSFT88 and execute the first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using PeopleSoft version 8.9 or 9.0, in Informatica Workflow Manager, navigate to the folder UPGRADE_796_to_7961_PSFT90 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

5. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep). For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Base Informatica Repository."

6. Run the 7961_UPGRADE_POST_SCRIPT.sql. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Oracle.

7.9.6.3 Verifying the Data Migrated Successfully

Follow this procedure to verify that the data was migrated successfully into the upgraded data warehouse.

To verify the data migrated successfully:

1. Validate the data in the upgraded data warehouse.

2. Check whether any of the Informatica mapping log files stored in the <INFA_HOME>\server\infa_shared\Sesslogs directory indicates errors or failures.

3. Check whether the following scripts that you ran in the SQL client of the database failed or errored out while executing:
7961_UPGRADE_DROP_INDEXES.sql

7961_UPGRADE_PRE_CTL_SCRIPT.sql

7961_UPGRADE_PRE_DIMENSION.sql

7961_UPGRADE_POST_SCRIPT.sql

4. Check the log files for the ddl_7961.ctl and Upgrade_7961.ctl scripts, which 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.

Note:

Ignore any error messages that indicate tables or indexes could not be dropped from the database. These error messages are displayed when the specified objects do not exist in the database. This can occur because each source system container holds a subset of all data warehouse tables

5. If the data migration was successful, drop the tables that were created during the upgrade process, such as W_xxxx_x_79x, LKP_xxxx_x and 79x_xxxx_TMP.
This step frees the space occupied by these backup tables.

6. Once the data migration steps above are complete, you can delete the Upgrade repository to avoid any accidental use or confusion.

1. In the Informatica Administrator, select the Upgrade repository service.

2. In the General Properties area of the Properties tab, click Edit.

3. Make sure the operating mode of the repository service is set to Exclusive.

4. Click OK.

5. Choose Actions, and then click Delete Contents.

6. In the Delete contents for <repository name> dialog, enter the repository username and password, and then click OK.

7.9.7 Upgrading the Data Warehouse Schema From Version 7.9.6.1 to 7.9.6.2 and Migrating Data

Perform the procedures in this section to upgrade from Oracle BI Applications release 7.9.6.1 to 7.9.6.2.

This section contains the following procedures:

- Section 7.9.7.1, "Upgrading the Data Warehouse Schema to Version 7.9.6.2"

- Section 7.9.7.2, "Migrating Data into the Upgraded Data Warehouse"

- Section 7.9.7.3, "Verifying the Data Migrated Successfully"

7.9.7.1 Upgrading the Data Warehouse Schema to Version 7.9.6.2

Follow this procedure to upgrade the data warehouse schema to version 7.9.6.2.

To upgrade the data warehouse schema to version 7.9.6.2:

1. Generate the scripts to drop and create indexes. For instructions, see Section B.1, "Generating Scripts to Drop and Create Indexes for Upgrading to Release 7.9.6.2."

2. Run the script to drop all indexes. For instructions, see Section B.2, "Running the Script to Drop All Indexes for Upgrading to Release 7.9.6.2."

3. If you are using a SQL Server database, run the 7962_UPGRADE_PRE_UPG_CTL_SCRIPT.sql file. This file is located in OracleBI\dwrep\Upgrade\DbScripts\SQLServer.

4. Run the UPGRADE_7962.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

5. Run the 7962_UPGRADE_PRE_CTL_SCRIPT.sql. This file is located in the folder OracleBI\dwrep\Upgrade\DbScripts\<database type>.

6. Run the DDL_7962.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

7.9.7.2 Migrating Data into the Upgraded Data Warehouse

Follow this procedure to migrate data into the upgraded data warehouse.

To migrate data into the upgraded data warehouse:

1. Run the 7962_UPGRADE_PRE_DIMENSION_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

2. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade repository. For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Upgrade Informatica Repository."

3. Configure the Informatica parameter file 7962_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7962_UPG_PARAMS.txt."

4. Configure additional parameters specific to PeopleSoft source systems. For instructions, see Section A.2.3, "Setting Parameters in 7962_UPG_PARAMS.txt for PeopleSoft Source Systems."

5. If you are upgrading Oracle Financial Analytics, you need to configure specific parameters and update mappings. For instructions, see Section A.3.4, "Setting Parameters and Mappings in 7962_UPG_PARAMS.txt for Oracle Financial Analytics."

6. If you are upgrading Oracle Financial Analytics, you need to make sure specific indexes are created. For instructions, see Appendix C, "Creating Indexes for Oracle Financial Analytics."

7. Run the script to create ETL indexes. For instructions, see Section B.3, "Running the Scripts to Create ETL and Query Indexes for Upgrading to Release 7.9.6.2."

8. If you are using PeopleSoft version 8.8, in Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_PSFT88 and execute the first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using PeopleSoft version 8.9 or 9.0, in Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_PSFT90 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

9. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep). For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Base Informatica Repository."

10. Run the script to create Query indexes. For instructions, see Section B.3, "Running the Scripts to Create ETL and Query Indexes for Upgrading to Release 7.9.6.2."

7.9.7.3 Verifying the Data Migrated Successfully

Follow this procedure to verify that the data was migrated successfully into the upgraded data warehouse.

To verify the data migrated successfully:

1. Validate the data in the upgraded data warehouse.

2. Check whether any of the Informatica mapping log files stored in the <INFA_HOME>\server\infa_shared\Sesslogs directory indicates errors or failures.

3. Check whether the following scripts that you ran in the SQL client of the database failed or errored out while executing:
dropallindexes.sql

7962_UPGRADE_PRE_CTL_SCRIPT.sql

7962_UPGRADE_PRE_DIMENSION.sql

createETLIndexes.sql

createQueryIndexes.sql

4. Check the log files for the DDL_7962.ctl and Upgrade_7962.ctl scripts, which 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.

Note:

Ignore any error messages that indicate tables or indexes could not be dropped from the database. These error messages are displayed when the specified objects do not exist in the database. This can occur because each source system container holds a subset of all data warehouse tables

5. If the data migration was successful, drop the tables that were created during the upgrade process, such as W_xxxx_x_79x, LKP_xxxx_x and 79x_xxxx_TMP.
This step frees the space occupied by these backup tables.

6. Once the data migration steps above are complete, you can delete the Upgrade repository to avoid any accidental use or confusion.

1. In the Informatica Administrator, select the Upgrade repository service.

2. In the General Properties area of the Properties tab, click Edit.

3. Make sure the operating mode of the repository service is set to Exclusive.

4. Click OK.

5. Choose Actions, and then click Delete Contents.

6. In the Delete contents for <repository name> dialog, enter the repository username and password, and then click OK.

7.9.8 Upgrading the Data Warehouse Schema From Version 7.9.6.2 to 7.9.6.3 and Migrating Data

Perform the procedures in this section to upgrade from Oracle BI Applications release 7.9.6.2 to 7.9.6.3.

This section contains the following procedures:

- Upgrading the Data Warehouse Schema to Version 7.9.6.3

- Migrating Data into the Upgraded Data Warehouse

- Verifying the Data Migrated Successfully

7.9.8.1 Upgrading the Data Warehouse Schema to Version 7.9.6.3

Follow this procedure to upgrade the data warehouse schema to version 7.9.6.3.

To upgrade the data warehouse schema to version 7.9.6.3:

1. Generate the scripts to drop and create query indexes. For instructions, see Section B.4, "Generating Scripts to Drop and Create Query Indexes for Upgrading to Release 7.9.6.3."

2. Run the script to drop query indexes. For instructions, see Section B.5, "Running the Scripts to Drop and Create Query Indexes for Upgrading to Release 7.9.6.3."
Note: You must drop the query indexes before running the scripts to upgrade the schema.

3. If you are using a SQL Server database, run the 7963_UPGRADE_PRE_UPG_CTL_SCRIPT.sql file. This file is located in OracleBI\dwrep\Upgrade\DbScripts\SQLServer.

4. Run the UPGRADE_7963.ctl script. For instructions, see Section E.1, "Using the DDLimp Utility to Run CTL Files."

5. Run the 7963_UPGRADE_PRE_CTL_SCRIPT.sql. This file is located in the folder OracleBI\dwrep\Upgrade\DbScripts\<database type>.

6. Run the DDL_7963.ctl script. For instructions, see Section E.1, "Using the DDLimp Utility to Run CTL Files.".

7.9.8.2 Migrating Data into the Upgraded Data Warehouse

Follow this procedure to migrate data into the upgraded data warehouse.

To migrate data into the upgraded data warehouse:

1. Run the 7963_UPGRADE_PRE_DIMENSION_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

2. Run the 7963_UPGRADE_DROP_ETLINDICES.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

3. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade repository. For instructions, see Section D.4, "Running reset_infa_seq_gen.bat on Upgrade Informatica Repository."

4. Configure the Informatica parameter file 7963_UPG_PARAMS.txt. For instructions, see Section A.1.8, "Setting Parameters in 7963_UPG_PARAMS.txt."

5. If you are upgrading Oracle Financial Analytics, do the following:

1. Set the parameters as specified in Appendix A, "Setting Parameters for All Source Systems."

2. Set the parameters as specified in Appendix A, "Setting Parameters Specific to PeopleSoft."

6. If you are upgrading Oracle Human Resources, set parameters as specified in Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt for Oracle Human Resources Analytics."

7. If your source system is PeopleSoft version 9.0 and you are upgrading Oracle Procurement and Spend Analytics, set the parameter as specified in Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt for Oracle Procurement and Spend Analytics on PeopleSoft Source System."

8. If you are using PeopleSoft 8.8, in Informatica Workflow Manager, navigate to the folder UPGRADE_7962_to_7963_PSFT88 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using PeopleSoft 8.9 or 9.0, in Informatica Workflow Manager, navigate to the folder UPGRADE_7962_to_7963_90 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

9. Upgrade geography-related attributes if necessary for your environment:

1. Determine whether a geography-related upgrade is necessary by executing the following query:

SELECT COUNT(1) as row_count,'0' as X_CUSTOM FROM W_GEO_D_7963 WHERE COUNTRY LIKE '% 'OR COUNTRY LIKE ' %'OR STATE_PROV LIKE '% 'OR STATE_PROV LIKE ' %'OR CITY LIKE '% 'OR CITY LIKE ' %'OR ZIPCODE LIKE '% 'OR ZIPCODE LIKE ' %'

2. If the query returns a count greater than zero, run the 7963_UPGRADE_POST_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.
If the query returns a count of zero, you do not need to run the 7963_UPGRADE_POST_SCRIPT.sql script.

10. Run the 7963_UPGRADE_CREATE_ETLINDICES.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

11. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep). For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Base Informatica Repository."

12. Run the createQueryIndices.sql script. For instructions, see Section B.5, "Running the Scripts to Drop and Create Query Indexes for Upgrading to Release 7.9.6.3."

7.9.8.3 Verifying the Data Migrated Successfully

Follow this procedure to verify that the data was migrated successfully into the upgraded data warehouse.

To verify the data migrated successfully:

1. Validate the data in the upgraded data warehouse.

2. Check whether any of the Informatica mapping log files stored in the <INFA_HOME>\server\infa_shared\Sesslogs directory indicates errors or failures.

3. Check whether the following scripts that you ran in the SQL client of the database failed or errored out while executing:
7963_UPGRADE_PRE_CTL_SCRIPT.sql

7963_UPGRADE_PRE_DIMENSION.sql

7963_UPGRADE_DROP_ETLINDICES.sql

7963_UPGRADE CREATE_ETLINDICES.sql

dropQueryIndices.sql

createQueryIndices.sql

4. Check the log files for the ddl_7963.ctl and Upgrade_7963.ctl scripts, which 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.

Note:

Ignore any error messages that indicate tables or indexes could not be dropped from the database. These error messages are displayed when the specified objects do not exist in the database. This can occur because each source system container holds a subset of all data warehouse tables

5. If the data migration was successful, drop the tables that were created during the upgrade process, such as W_xxxx_x_79x, LKP_xxxx_x and 79x_xxxx_TMP.
This step frees the space occupied by these backup tables.

6. Once the data migration steps above are complete, you can delete the Upgrade repository to avoid any accidental use or confusion.

1. In the Informatica Administrator, select the Upgrade repository service.

2. In the General Properties area of the Properties tab, click Edit.

3. Make sure the operating mode of the repository service is set to Exclusive.

4. Click OK.

5. Choose Actions, and then click Delete Contents.

6. In the Delete contents for <repository name> dialog, enter the repository username and password, and then click OK.

7.9.9 Upgrading the Data Warehouse Schema From Version 7.9.6.3 to 7.9.6.4 and Migrating Data

Perform the procedures in this section to upgrade from Oracle BI Applications release 7.9.6.3 to 7.9.6.4.

This section contains the following procedures:

- Section 7.9.9.1, "Upgrading the Data Warehouse Schema to Version 7.9.6.4"

- Section 7.9.9.2, "Migrating Data into the Upgraded Data Warehouse"

- Section 7.9.9.3, "Verifying the Data Migrated Successfully"

7.9.9.1 Upgrading the Data Warehouse Schema to Version 7.9.6.4

Follow this procedure to upgrade the data warehouse schema to version 7.9.6.4.

To upgrade the data warehouse schema to version 7.9.6.4:

1. If you are using a DB2 database, run siebproc.sql. This file is located in OracleBI\dwrep\siebproc\db2udb.

2. Generate the scripts to drop and create query indexes. For instructions, see Section B.6, "Generating Scripts to Drop and Create Query and ETL Indexes for Upgrading to Release 7.9.6.4."

3. Run the script to drop query indexes. For instructions, see Section B.7, "Running the Scripts to Drop and Create Query Indexes for Upgrading to Release 7.9.6.4."
Note: You must drop the query indexes before running the scripts to upgrade the schema.

4. If you are using a SQL Server database, run the 7964_UPGRADE_PRE_UPG_CTL_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\SQLServer.

5. Run the UPGRADE_7964.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

6. Run the 7964_UPGRADE_PRE_CTL_SCRIPT.sql script. This file is located in the folder OracleBI\dwrep\Upgrade\DbScripts\<database type>.

7. Run the DDL_7964.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

7.9.9.2 Migrating Data into the Upgraded Data Warehouse

Follow this procedure to migrate data into the upgraded data warehouse.

To migrate data into the upgraded data warehouse:

1. Run the 7964_UPGRADE_PRE_DIMENSION_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

2. Run the script to drop ETL indexes. For instructions, see Section B.8, "Running the Scripts to Drop and Create ETL Indexes for Upgrading to Release 7.9.6.4."

3. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade repository. For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Upgrade Informatica Repository."

4. Configure the Informatica parameter file 7964_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7964_UPG_PARAMS.txt."

5. If you are using PeopleSoft 8.8, in Informatica Workflow Manager, navigate to the folder UPGRADE_7963_to_7964_PSFT88 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using PeopleSoft 8.9 or 9.0, in Informatica Workflow Manager, navigate to the folder UPGRADE_7963_to_7964_90 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

6. If you are upgrading the Oracle Human Resource Analytics Workforce module, you must perform a full load of data. To complete this step you will set the refresh dates to NULL for the Workforce-related tables.

1. Log into DAC.

2. Go to the Physical Data Sources tab in the Setup view.

3. In the top pane window, select the appropriate data warehouse connection.

4. Go to the Refresh Dates subtab.

5. Reset the refresh date to Null for the following tables by clicking in the Refresh Date column, displaying the Date dialog, and clicking Null. Click Save for each record.
W_ORA_SUPV_STATUS_PS

W_ORA_WEVT_ASG_PS

W_ORA_WEVT_FTE_PS

W_ORA_WEVT_HDC_PS

W_ORA_WEVT_PERF_PS

W_ORA_WEVT_PTYP_PS

W_ORA_WEVT_SAL_PS

W_PSFT_POSN_HLDR_PS

W_PSFT_POSN_WRKR_PS

W_PSFT_SUPV_STATUS_PS

W_PSFT_SUPV_WRKR_PS

W_PSFT_WEVT_AGE_PS

W_PSFT_WEVT_IASG_PS

W_PSFT_WEVT_JOB_PS

W_PSFT_WEVT_PERF_PS

W_WRKFC_EVT_FS

W_WRKFC_EVT_F

W_WRKFC_EVT_MERGE_F

W_WRKFC_EVT_MONTH_F

W_WRKFC_EVT_POW_F

W_WRKFC_EVT_AGE_F

W_WRKFC_EVT_A

W_WRKFC_BAL_A

W_WRKFC_EVENT_GROUP_D

W_WRKFC_EVENT_TYPE_D

7. If you are upgrading the Oracle Human Resource Analytics Recruitment module, do the following:

1. Execute the following SQL statement to clean the data:

DELETE FROM W_RCRTMNT_EVENT_F
WHERE RCRTMNT_EVENT_CLASS = 'JOB_RQSTN'
AND DATASOURCE_NUM_ID IN <>

2. Run the following upgrade map worklet:

HumanResourceAnalytics_Recruitment_JobRequisitions_UPG7964

8. Run the 7964_UPGRADE_POST_SCRIPT.sql. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

9. Run the script to create ETL indexes. For instructions, see Section B.8, "Running the Scripts to Drop and Create ETL Indexes for Upgrading to Release 7.9.6.4."

10. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep). For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Base Informatica Repository."

7.9.9.3 Verifying the Data Migrated Successfully

Follow this procedure to verify that the data was migrated successfully into the upgraded data warehouse.

To verify the data migrated successfully:

1. Validate the data in the upgraded data warehouse.

2. Check whether any of the Informatica mapping log files stored in the <INFA_HOME>\server\infa_shared\Sesslogs directory indicates errors or failures.

3. Check whether the following scripts that you ran in the SQL client of the database failed or errored out while executing:
7964_UPGRADE_PRE_CTL_SCRIPT.sql

7964_UPGRADE_PRE_DIMENSION.sql

dropEtlIndices.sql

createEtlIndices.sql

dropQueryIndices.sql

createQueryIndices.sql

4. Check the log files for the ddl_7964.ctl and Upgrade_7964.ctl scripts, which 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.

Note:

Ignore any error messages that indicate tables or indexes could not be dropped from the database. These error messages are displayed when the specified objects do not exist in the database. This can occur because each source system container holds a subset of all data warehouse tables

5. If the data migration was successful, drop the tables that were created during the upgrade process, such as W_xxxx_x_79x, LKP_xxxx_x and 79x_xxxx_TMP.
This step frees the space occupied by these backup tables.

6. Once the data migration steps above are complete, you can delete the Upgrade repository to avoid any accidental use or confusion.

1. In the Informatica Administrator, select the Upgrade repository service.

2. In the General Properties area of the Properties tab, click Edit.

3. Make sure the operating mode of the repository service is set to Exclusive.

4. Click OK.

5. Choose Actions, and then click Delete Contents.

6. In the Delete contents for <repository name> dialog, enter the repository username and password, and then click OK.

7.10 Upgrading the Data Warehouse Schema and Migrating Data for Teradata Databases

If your data warehouse database platform is Teradata, you can upgrade to Oracle BI Applications version 7.9.6.4 from Oracle BI Applications 7.9.x.

This section includes the following topics:

- Section 7.10.1, "Upgrading Oracle BI Applications From Version 7.9.3 to 7.9.6.4"

- Section 7.10.2, "Upgrading Oracle BI Applications From Version 7.9.4 to 7.9.6.4"

- Section 7.10.3, "Upgrading Oracle BI Applications From Version 7.9.5 to 7.9.6.4"

- Section 7.10.4, "Upgrading Oracle BI Applications From Version 7.9.5.1 to 7.9.6.4"

- Section 7.10.5, "Upgrading Oracle BI Applications From Version 7.9.6.1 to 7.9.6.4"

- Section 7.10.6, "Upgrading Oracle BI Applications From Version 7.9.6.2 to 7.9.6.4"

- Section 7.10.7, "Upgrading Oracle BI Applications From Version 7.9.6.3 to 7.9.6.4"

7.10.1 Upgrading Oracle BI Applications From Version 7.9.3 to 7.9.6.4

Follow this procedure to upgrade from Oracle BI Applications version 7.9.3 to version 7.9.6.4 if your data warehouse database platform is Teradata.

To upgrade the data warehouse schema and migrate data for a Teradata database:

1. Execute the following scripts:

- 794_UPGRADE_TMP_TABLES.sql

- 795_UPGRADE_TMP_TABLES.sql

- 7951_UPGRADE_TMP_TABLES.sql

- 7961_UPGRADE_TMP_TABLES.sql

- 7962_UPGRADE_TMP_TABLES.sql

- 7963_UPGRADE_TMP_TABLES.sql

- 7964_UPGRADE_TMP_TABLES.sql

1. Open the SQL client for your database type.

2. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.

3. Open the <version>_UPGRADE_TMP_TABLES.sql file, and copy the contents into the SQL client.

4. Execute the script.

2. Edit and execute the 794_RENAME_AND_EXCEPTIONS.sql script.

1. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.

2. Open the 794_RENAME_AND_EXCEPTIONS.sql script.

3. Search for the following statements to locate columns with RENAME commands.
ALTER TABLE <Table_Name> RENAME <Column Name> TO <New Column Name>;

4. For all columns with RENAME commands, check to see whether any COLUMN STATISTICS are defined on them.

5. For all columns that have STATISTICS defined on them, back up the COLUMN STATISTICS definition and then drop them.

6. Execute the 794_RENAME_AND_EXCEPTIONS.sql script.

7. Recreate STATISTICS on any column on which they were dropped.

3. The teradata.missing.defaults.properties file contains global default column values for data warehouse tables with NOT NULL columns for which default values are not specified in DAC. You can change the default values specified in the teradata.missing.defaults.properties file to match your environment. The file is located in \bifoundation\dac\conf\sqlgen\sql\teradata.

4. Generate upgrade scripts from DAC.

1. Log into DAC.

2. From the menu bar, select Tools, then ETL Management, and then Configure.

3. In the Sources dialog box, select Teradata as the target data warehouse database platform, and select the appropriate source data warehouse database platform.
The Configuration tab of the Data Warehouse Configuration Wizard is active.

4. Select "Generate upgrade statements for Data Warehouse Tables," and click Next.
The Data Warehouse SQL tab is active.

5. Do the following:
- Select the appropriate physical data source name for the Teradata database.

- In the container field, enter a custom container name for which you want to generate upgrade scripts. Alternatively, leave the field blank to generate upgrade scripts for all containers.

The Data Warehouse Configuration Wizard generates the following files and stores them in \bifoundation\DAC\conf\sqlgen\sql\teradata:

upgrade-regular.sql. This file contains scripts that DAC has verified are necessary to upgrade the data warehouse schema. The scripts handle new or altered tables and columns. For example, they may increase the size of simple data types or change a column from null to not null.

upgrade-questionable.sql. This file contains scripts that DAC suggests may be required to upgrade the data warehouse schema. These scripts are intended to be an aid in determining upgrade requirements and must be reviewed by a Teradata DBA and corrected if necessary.

upgradedwtables_sql.log. This file is the log file that corresponds to the upgrade-regular.sql file. It is for information purposes only.

upgrade-issues.log. This file is the log file that corresponds to the file upgrade-questionable.sql. It is for information purposes only.

6. Open the upgrade-regular.sql and upgrade-questionable.sql files, and search for the following statement to locate columns that have been added or changed.
ALTER TABLE <Table Name> ADD <Column Name><attributes>;

7. For all columns with the ADD command, check to see whether any columns exist already, and if they do, check whether they have STATISTICS defined on them.

8. For all columns that have STATISTICS defined on them, back up the column definition and then drop the STATISTICS.

9. Execute the scripts in the upgrade-regular.sql file.

10. Review the scripts in the upgrade-questionable.sql file. Edit the scripts as needed, and execute them.

11. Recreate STATISTICS on any column on which they were dropped.

5. Execute the following scripts:

- 794_UPDATE_DEFAULTS.sql

- 795_UPDATE_DEFAULTS.sql

- 7951_UPDATE_DEFAULTS.sql

- 7961_UPDATE_DEFAULTS.sql

- 7962_UPDATE_DEFAULTS.sql

- 7963_UPDATE_DEFAULTS.sql

- 7964_UPDATE_DEFAULTS.sql

6. Execute the 794_Backup Tables.sql script.

7. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

8. Configure the Informatica parameter file 794_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 794_UPG_PARAMS.txt."

9. In Informatica Workflow Manager, navigate to the folder UPGRADE_793_to_794_PSFT88 and execute the UPGRADE_DIMENSIONS and UPGRADE_FACTS workflows.

10. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

11. Execute the 795_Backup Tables.sql script.

12. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

13. Configure the Informatica parameter file 795_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 795_UPG_PARAMS.txt."

14. In Informatica Workflow Manager, navigate to the folder UPGRADE_794_to_795_PSFT88 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

15. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

16. Execute the 7951_Backup Tables.sql script.

17. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

18. Configure the Informatica parameter file 7951_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7951_UPG_PARAMS.txt."

19. In Informatica Workflow Manager, navigate to the folder UPGRADE_795_to_7951_PSFT and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

20. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

21. Execute the 796_Backup Tables.sql script.

22. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

23. Configure the Informatica parameter file 796_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 796_UPG_PARAMS.txt."

24. If you are upgrading Oracle Financial Analytics, you need to configure specific parameters and update mappings. For more information, see Section A.3.1, "Setting Parameters and Mappings in 796_UPG_PARAMS.txt for Oracle Financial Analytics."

25. If you are upgrading Oracle Project Analytics, you need to configure specific parameters. For more information, see Section A.3.1, "Setting Parameters and Mappings in 796_UPG_PARAMS.txt for Oracle Financial Analytics."

26. Back up and truncate the table W_POSITION_DH.

27. If you are using PeopleSoft version 8.8, in Informatica Workflow Manager, navigate to the folder UPGRADE_7951_to_796_PSFT88 and execute the following workflows in the order as they appear: UPGRADE_DIMENSIONS, UPGRADE_FACTS, and RESET_DAC_REFRESH_DATES.
If you are using PeopleSoft version 8.9 or 9.0, in Informatica Workflow Manager, navigate to the folder UPGRADE_7951_to_796_PSFT90 and execute the following workflows in the order as they appear: UPGRADE_DIMENSIONS, UPGRADE_FACTS, and RESET_DAC_REFRESH_DATES.

28. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

29. Execute the 7961_Backup Tables.sql script.

30. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

31. Configure the Informatica parameter file 7961_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7961_UPG_PARAMS.txt."

32. If you are using PeopleSoft version 8.8, in Informatica Workflow Manager, navigate to the folder UPGRADE_796_to_7961_PSFT88 and execute and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using PeopleSoft version 8.9 or 9.0, in Informatica Workflow Manager, navigate to the folder UPGRADE_796_to_7961_PSFT90 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

33. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

34. Execute the 7962_Backup_Tables.sql script.

35. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade repository. For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Upgrade Informatica Repository."

36. Configure the Informatica parameter file 7962_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7962_UPG_PARAMS.txt."

37. Configure additional parameters specific to PeopleSoft source systems. For instructions, see Section A.2.3, "Setting Parameters in 7962_UPG_PARAMS.txt for PeopleSoft Source Systems."

38. If you are upgrading Oracle Financial Analytics, you need to configure specific parameters and update mappings. For instructions, see Section A.3.4, "Setting Parameters and Mappings in 7962_UPG_PARAMS.txt for Oracle Financial Analytics."

39. If you are upgrading Oracle Financial Analytics, you need to make sure specific indexes are created. For instructions, see Appendix C, "Creating Indexes for Oracle Financial Analytics."

40. If you are using PeopleSoft version 8.8, in Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_PSFT88 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using PeopleSoft version 8.9 or 9.0, in Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_PSFT90 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

41. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

42. Execute the 7963_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

43. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

44. Configure the Informatica parameter file 7963_UPG_PARAMS.txt. For instructions, see Section A.1.8, "Setting Parameters in 7963_UPG_PARAMS.txt."

45. If you are upgrading Oracle Financial Analytics, do the following:

1. Set the parameters as specified in Appendix A, "Setting Parameters for All Source Systems."

2. Set the parameters as specified in Appendix A, "Setting Parameters Specific to PeopleSoft."

46. If you are upgrading Oracle Human Resources, set parameters as specified in Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt for Oracle Human Resources Analytics."

47. If your source system is PeopleSoft version 9.0 and you are upgrading Oracle Procurement and Spend Analytics, set the parameter as specified in Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt for Oracle Procurement and Spend Analytics on PeopleSoft Source System."

48. If you are using PeopleSoft 8.8, in Informatica Workflow Manager, navigate to the folder UPGRADE_7962_to_7963_PSFT88 and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.
If you are using PeopleSoft 8.9 or 9.0, in Informatica Workflow Manager, navigate to the folder UPGRADE_7962_to_7963_PSFT90 and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.

49. Upgrade geography-related attributes if necessary for your environment:

1. Determine whether a geography-related upgrade is necessary by executing the following query:

SELECT COUNT(1) as row_count,'0' as X_CUSTOM FROM W_GEO_D_7963 WHERE COUNTRY LIKE '% 'OR COUNTRY LIKE ' %'OR STATE_PROV LIKE '% 'OR STATE_PROV LIKE ' %'OR CITY LIKE '% 'OR CITY LIKE ' %'OR ZIPCODE LIKE '% 'OR ZIPCODE LIKE ' %'

2. If the query returns a count greater than zero, run the 7963_UPGRADE_POST_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.
If the query returns a count of zero, you do not need to run the 7963_UPGRADE_POST_SCRIPT.sql script.

50. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

51. Execute the 7964_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

52. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

53. Configure the Informatica parameter file 7964_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7964_UPG_PARAMS.txt."

54. If you are using PeopleSoft 8.8, in Informatica Workflow Manager, navigate to the folder UPGRADE_7963_to_7964_PSFT88 and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.
If you are using PeopleSoft 8.9 or 9.0, in Informatica Workflow Manager, navigate to the folder UPGRADE_7963_to_7964_PSFT90 and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.

55. Run the 7964_UPGRADE_POST_SCRIPT.sql. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

56. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

57. Once the data migration steps above are complete, you can delete the Upgrade repository to avoid any accidental use or confusion.

1. In the Informatica Administrator, select the Upgrade repository service.

2. In the General Properties area of the Properties tab, click Edit.

3. Make sure the operating mode of the repository service is set to Exclusive.

4. Click OK.

5. Choose Actions, and then click Delete Contents.

6. In the Delete contents for <repository name> dialog, enter the repository username and password, and then click OK.

7.10.2 Upgrading Oracle BI Applications From Version 7.9.4 to 7.9.6.4

Follow this procedure to upgrade from Oracle BI Applications version 7.9.4 to version 7.9.6.4 if your data warehouse database platform is Teradata.

To upgrade the data warehouse schema and migrate data for a Teradata database:

1. Execute the following scripts:

- 795_UPGRADE_TMP_TABLES.sql

- 7951_UPGRADE_TMP_TABLES.sql

- 7961_UPGRADE_TMP_TABLES.sql

- 7962_UPGRADE_TMP_TABLES.sql

- 7963_UPGRADE_TMP_TABLES.sql

- 7964_UPGRADE_TMP_TABLES.sql

1. Open the SQL client for your database type.

2. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.

3. Open the <version>_UPGRADE_TMP_TABLES.sql file, and copy the contents into the SQL client.

4. Execute the script.

2. Edit and execute the 795_RENAME_AND_EXCEPTIONS.sql script.

1. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.

2. Open the 795_RENAME_AND_EXCEPTIONS.sql script.

3. Search for the following statements to locate columns with RENAME commands.
ALTER TABLE <Table_Name> RENAME <Column Name> TO <New Column Name>;

4. For all columns with RENAME commands, check to see whether any COLUMN STATISTICS are defined on them.

5. For all columns that have STATISTICS defined on them, back up the COLUMN STATISTICS definition and then drop them.

6. Execute the 795_RENAME_AND_EXCEPTIONS.sql script.

7. Recreate STATISTICS on any column on which they were dropped.

3. The teradata.missing.defaults.properties file contains global default column values for data warehouse tables with NOT NULL columns for which default values are not specified in DAC. You can change the default values specified in the teradata.missing.defaults.properties file to match your environment. The file is located in \bifoundation\dac\conf\sqlgen\sql\teradata.

4. Generate upgrade scripts from DAC.

1. Log into DAC.

2. From the menu bar, select Tools, then ETL Management, and then Configure.

3. In the Sources dialog box, select Teradata as the target data warehouse database platform, and select the appropriate source data warehouse database platform.
The Configuration tab of the Data Warehouse Configuration Wizard is active.

4. Select "Generate upgrade statements for Data Warehouse Tables," and click Next.
The Data Warehouse SQL tab is active.

5. Do the following:
- Select the appropriate physical data source name for the Teradata database.

- In the container field, enter a custom container name for which you want to generate upgrade scripts. Alternatively, leave the field blank to generate upgrade scripts for all containers.

The Data Warehouse Configuration Wizard generates the following files and stores them in \bifoundation\DAC\conf\sqlgen\sql\teradata:

upgrade-regular.sql. This file contains scripts that DAC has verified are necessary to upgrade the data warehouse schema. The scripts handle new or altered tables and columns. For example, they may increase the size of simple data types or change a column from null to not null.

upgrade-questionable.sql. This file contains scripts that DAC suggests may be required to upgrade the data warehouse schema. These scripts are intended to be an aid in determining upgrade requirements and must be reviewed by a Teradata DBA and corrected if necessary.

upgradedwtables_sql.log. This file is the log file that corresponds to the upgrade-regular.sql file. It is for information purposes only.

upgrade-issues.log. This file is the log file that corresponds to the file upgrade-questionable.sql. It is for information purposes only.

6. Open the upgrade-regular.sql and upgrade-questionable.sql files, and search for the following statement to locate columns that have been added or changed.
ALTER TABLE <Table Name> ADD <Column Name><attributes>;

7. For all columns with the ADD command, check to see whether any columns exist already, and if they do, check whether they have STATISTICS defined on them.

8. For all columns that have STATISTICS defined on them, back up the column definition and then drop the STATISTICS.

9. Execute the scripts in the upgrade-regular.sql file.

10. Review the scripts in the upgrade-questionable.sql file. Edit the scripts as needed, and execute them.

11. Recreate STATISTICS on any column on which they were dropped.

5. Execute the following scripts:

- 795_UPDATE_DEFAULTS.sql

- 7951_UPDATE_DEFAULTS.sql

- 7961_UPDATE_DEFAULTS.sql

- 7962_UPDATE_DEFAULTS.sql

- 7963_UPDATE_DEFAULTS.sql

- 7964_UPDATE_DEFAULTS.sql

6. Execute the 795_Backup Tables.sql script.

7. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

8. Configure the Informatica parameter file 795_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 795_UPG_PARAMS.txt."

9. In Informatica Workflow Manager, navigate to the folder UPGRADE_794_to_795_PSFT88 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

10. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

11. Execute the 7951_Backup Tables.sql script.

12. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

13. Configure the Informatica parameter file 7951_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7951_UPG_PARAMS.txt."

14. In Informatica Workflow Manager, navigate to the folder UPGRADE_795_to_7951_PSFT and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

15. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

16. Execute the 796_Backup Tables.sql script.

17. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

18. Configure the Informatica parameter file 796_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 796_UPG_PARAMS.txt."

19. If you are upgrading Oracle Financial Analytics, you need to configure specific parameters and update mappings. For more information, see Section A.3.1, "Setting Parameters and Mappings in 796_UPG_PARAMS.txt for Oracle Financial Analytics."

20. If you are upgrading Oracle Project Analytics, you need to configure specific parameters. For more information, see Section A.3.2, "Setting Parameters in 796_UPG_PARAMS.txt for Oracle Project Analytics."

21. Back up and truncate the table W_POSITION_DH.

22. If you are using PeopleSoft version 8.8, in Informatica Workflow Manager, navigate to the folder UPGRADE_7951_to_796_PSFT88 and execute the following workflows in the order as they appear: UPGRADE_DIMENSIONS, UPGRADE_FACTS, and RESET_DAC_REFRESH_DATES.
If you are using PeopleSoft version 8.9 or 9.0, in Informatica Workflow Manager, navigate to the folder UPGRADE_7951_to_796_PSFT90 and execute the following workflows in the order as they appear: UPGRADE_DIMENSIONS, UPGRADE_FACTS, and RESET_DAC_REFRESH_DATES.

23. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

24. Execute the 7961_Backup Tables.sql script.

25. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

26. Configure the Informatica parameter file 7961_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7961_UPG_PARAMS.txt."

27. If you are using PeopleSoft version 8.8, in Informatica Workflow Manager, navigate to the folder UPGRADE_796_to_7961_PSFT88 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using PeopleSoft version 8.9 or 9.0, in Informatica Workflow Manager, navigate to the folder UPGRADE_796_to_7961_PSFT90 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

28. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

29. Execute the 7962_Backup_Tables.sql script.

30. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

31. Configure the Informatica parameter file 7962_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7962_UPG_PARAMS.txt."

32. Configure additional parameters specific to PeopleSoft source systems. For instructions, see Section A.2.3, "Setting Parameters in 7962_UPG_PARAMS.txt for PeopleSoft Source Systems."

33. If you are upgrading Oracle Financial Analytics, you need to configure specific parameters and update mappings. For instructions, see Section A.3.4, "Setting Parameters and Mappings in 7962_UPG_PARAMS.txt for Oracle Financial Analytics."

34. If you are upgrading Oracle Financial Analytics, you need to make sure specific indexes are created. For instructions, see Appendix C, "Creating Indexes for Oracle Financial Analytics."

35. If you are using PeopleSoft version 8.8, in Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_PSFT88 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using PeopleSoft version 8.9 or 9.0, in Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_PSFT90 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

36. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

37. Execute the 7963_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

38. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

39. Configure the Informatica parameter file 7963_UPG_PARAMS.txt. For instructions, see Section A.1.8, "Setting Parameters in 7963_UPG_PARAMS.txt."

40. If you are upgrading Oracle Financial Analytics, do the following:

1. Set the parameters as specified in Appendix A, "Setting Parameters for All Source Systems."

2. Set the parameters as specified in Appendix A, "Setting Parameters Specific to PeopleSoft."

41. If you are upgrading Oracle Human Resources, set parameters as specified in Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt for Oracle Human Resources Analytics."

42. If your source system is PeopleSoft version 9.0 and you are upgrading Oracle Procurement and Spend Analytics, set the parameter as specified in Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt for Oracle Procurement and Spend Analytics on PeopleSoft Source System."

43. If you are using PeopleSoft 8.8, in Informatica Workflow Manager, navigate to the folder UPGRADE_7962_to_7963_PSFT88 and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.
If you are using PeopleSoft 8.9 or 9.0, in Informatica Workflow Manager, navigate to the folder UPGRADE_7962_to_7963_PSFT90 and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.

44. Upgrade geography-related attributes if necessary for your environment:

1. Determine whether a geography-related upgrade is necessary by executing the following query:

SELECT COUNT(1) as row_count,'0' as X_CUSTOM FROM W_GEO_D_7963 WHERE COUNTRY LIKE '% 'OR COUNTRY LIKE ' %'OR STATE_PROV LIKE '% 'OR STATE_PROV LIKE ' %'OR CITY LIKE '% 'OR CITY LIKE ' %'OR ZIPCODE LIKE '% 'OR ZIPCODE LIKE ' %'

2. If the query returns a count greater than zero, run the 7963_UPGRADE_POST_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.
If the query returns a count of zero, you do not need to run the 7963_UPGRADE_POST_SCRIPT.sql script.

45. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

46. Execute the 7964_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

47. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

48. Configure the Informatica parameter file 7964_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7964_UPG_PARAMS.txt."

49. If you are using PeopleSoft 8.8, in Informatica Workflow Manager, navigate to the folder UPGRADE_7963_to_7964_PSFT88 and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.
If you are using PeopleSoft 8.9 or 9.0, in Informatica Workflow Manager, navigate to the folder UPGRADE_7963_to_7964_PSFT90 and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.

50. Run the 7964_UPGRADE_POST_SCRIPT.sql. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

51. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

52. Once the data migration steps above are complete, you can delete the Upgrade repository to avoid any accidental use or confusion.

1. In the Informatica Administrator, select the Upgrade repository service.

2. In the General Properties area of the Properties tab, click Edit.

3. Make sure the operating mode of the repository service is set to Exclusive.

4. Click OK.

5. Choose Actions, and then click Delete Contents.

6. In the Delete contents for <repository name> dialog, enter the repository username and password, and then click OK.

7.10.3 Upgrading Oracle BI Applications From Version 7.9.5 to 7.9.6.4

Follow this procedure to upgrade from Oracle BI Applications version 7.9.5 to version 7.9.6.4 if your data warehouse database platform is Teradata.

To upgrade the data warehouse schema and migrate data for a Teradata database:

1. Execute the following scripts:

- 7951_UPGRADE_TMP_TABLES.sql

- 7961_UPGRADE_TMP_TABLES.sql

- 7962_UPGRADE_TMP_TABLES.sql

- 7963_UPGRADE_TMP_TABLES.sql

- 7964_UPGRADE_TMP_TABLES.sql

1. Open the SQL client for your database type.

2. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.

3. Open the <version>_UPGRADE_TMP_TABLES.sql file, and copy the contents into the SQL client.

4. Execute the script.

2. Edit and execute the 7951_RENAME_AND_EXCEPTIONS.sql script.

1. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.

2. Open the 7951_RENAME_AND_EXCEPTIONS.sql script.

3. Search for the following statements to locate columns with RENAME commands.
ALTER TABLE <Table_Name> RENAME <Column Name> TO <New Column Name>;

4. For all columns with RENAME commands, check to see whether any COLUMN STATISTICS are defined on them.

5. For all columns that have STATISTICS defined on them, back up the COLUMN STATISTICS definition and then drop them.

6. Execute the 7951_RENAME_AND_EXCEPTIONS.sql script.

7. Recreate STATISTICS on any column on which they were dropped.

3. The teradata.missing.defaults.properties file contains global default column values for data warehouse tables with NOT NULL columns for which default values are not specified in DAC. You can change the default values specified in the teradata.missing.defaults.properties file to match your environment. The file is located in \bifoundation\dac\conf\sqlgen\sql\teradata.

4. Generate upgrade scripts from DAC.

1. Log into DAC.

2. From the menu bar, select Tools, then ETL Management, and then Configure.

3. In the Sources dialog box, select Teradata as the target data warehouse database platform, and select the appropriate source data warehouse database platform.
The Configuration tab of the Data Warehouse Configuration Wizard is active.

4. Select "Generate upgrade statements for Data Warehouse Tables," and click Next.
The Data Warehouse SQL tab is active.

5. Do the following:
- Select the appropriate physical data source name for the Teradata database.

- In the container field, enter a custom container name for which you want to generate upgrade scripts. Alternatively, leave the field blank to generate upgrade scripts for all containers.

The Data Warehouse Configuration Wizard generates the following files and stores them in \bifoundation\DAC\conf\sqlgen\sql\teradata:

upgrade-regular.sql. This file contains scripts that DAC has verified are necessary to upgrade the data warehouse schema. The scripts handle new or altered tables and columns. For example, they may increase the size of simple data types or change a column from null to not null.

upgrade-questionable.sql. This file contains scripts that DAC suggests may be required to upgrade the data warehouse schema. These scripts are intended to be an aid in determining upgrade requirements and must be reviewed by a Teradata DBA and corrected if necessary.

upgradedwtables_sql.log. This file is the log file that corresponds to the upgrade-regular.sql file. It is for information purposes only.

upgrade-issues.log. This file is the log file that corresponds to the file upgrade-questionable.sql. It is for information purposes only.

6. Open the upgrade-regular.sql and upgrade-questionable.sql files, and search for the following statement to locate columns that have been added or changed.
ALTER TABLE <Table Name> ADD <Column Name><attributes>;

7. For all columns with the ADD command, check to see whether any columns exist already, and if they do, check whether they have STATISTICS defined on them.

8. For all columns that have STATISTICS defined on them, back up the column definition and then drop the STATISTICS.

9. Execute the scripts in the upgrade-regular.sql file.

10. Review the scripts in the upgrade-questionable.sql file. Edit the scripts as needed, and execute them.

11. Recreate STATISTICS on any column on which they were dropped.

5. Execute the following scripts:

- 7951_UPDATE_DEFAULTS.sql

- 7961_UPDATE_DEFAULTS.sql

- 7962_UPDATE_DEFAULTS.sql

- 7963_UPDATE_DEFAULTS.sql

- 7964_UPDATE_DEFAULTS.sql

6. Execute the 7951_Backup Tables.sql script.

7. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

8. Configure the Informatica parameter file 7951_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7951_UPG_PARAMS.txt."

9. In Informatica Workflow Manager, navigate to the folder UPGRADE_795_to_7951_PSFT and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

10. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

11. Execute the 796_Backup Tables.sql script.

12. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

13. Configure the Informatica parameter file 796_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 796_UPG_PARAMS.txt."

14. If you are upgrading Oracle Financial Analytics, you need to configure specific parameters and update mappings. For more information, see Section A.3.1, "Setting Parameters and Mappings in 796_UPG_PARAMS.txt for Oracle Financial Analytics."

15. If you are upgrading Oracle Project Analytics, you need to configure specific parameters. For more information, see Section A.3.2, "Setting Parameters in 796_UPG_PARAMS.txt for Oracle Project Analytics."

16. Back up and truncate the table W_POSITION_DH.

17. If you are using PeopleSoft version 8.8, in Informatica Workflow Manager, navigate to the folder UPGRADE_7951_to_796_PSFT88 and execute the following workflows in the order as they appear: UPGRADE_DIMENSIONS, UPGRADE_FACTS, and RESET_DAC_REFRESH_DATES.
If you are using PeopleSoft version 8.9 or 9.0, in Informatica Workflow Manager, navigate to the folder UPGRADE_7951_to_796_PSFT90 and execute the following workflows in the order as they appear: UPGRADE_DIMENSIONS, UPGRADE_FACTS, and RESET_DAC_REFRESH_DATES.

18. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

19. Execute the 7961_Backup_Tables.sql script.

20. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

21. Configure the Informatica parameter file 7961_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7961_UPG_PARAMS.txt."

22. If you are using PeopleSoft version 8.8, in Informatica Workflow Manager, navigate to the folder UPGRADE_796_to_7961_PSFT88 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using PeopleSoft version 8.9 or 9.0, in Informatica Workflow Manager, navigate to the folder UPGRADE_796_to_7961_PSFT90 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

23. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

24. Execute 7962_Backup_Tables.sql script.

25. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

26. Configure the Informatica parameter file 7962_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7962_UPG_PARAMS.txt."

27. Configure additional parameters specific to PeopleSoft source systems. For instructions, see Section A.2.3, "Setting Parameters in 7962_UPG_PARAMS.txt for PeopleSoft Source Systems."

28. If you are upgrading Oracle Financial Analytics, you need to configure specific parameters and update mappings. For instructions, see Section A.3.4, "Setting Parameters and Mappings in 7962_UPG_PARAMS.txt for Oracle Financial Analytics."

29. If you are upgrading Oracle Financial Analytics, you need to make sure specific indexes are created. For instructions, see Appendix C, "Creating Indexes for Oracle Financial Analytics."

30. If you are using PeopleSoft version 8.8, in Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_PSFT88 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using PeopleSoft version 8.9 or 9.0, in Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_PSFT90 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

31. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

32. Execute the 7963_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

33. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

34. Configure the Informatica parameter file 7963_UPG_PARAMS.txt. For instructions, see Section A.1.8, "Setting Parameters in 7963_UPG_PARAMS.txt."

35. If you are upgrading Oracle Financial Analytics, do the following:

1. Set the parameters as specified in Appendix A, "Setting Parameters for All Source Systems."

2. Set the parameters as specified in Appendix A, "Setting Parameters Specific to PeopleSoft."

36. If you are upgrading Oracle Human Resources, set parameters as specified in Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt for Oracle Human Resources Analytics."

37. If your source system is PeopleSoft version 9.0 and you are upgrading Oracle Procurement and Spend Analytics, set the parameter as specified in Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt for Oracle Procurement and Spend Analytics on PeopleSoft Source System."

38. If you are using PeopleSoft 8.8, in Informatica Workflow Manager, navigate to the folder UPGRADE_7962_to_7963_PSFT88 and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.
If you are using PeopleSoft 8.9 or 9.0, in Informatica Workflow Manager, navigate to the folder UPGRADE_7962_to_7963_PSFT90 and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.

39. Upgrade geography-related attributes if necessary for your environment:

1. Determine whether a geography-related upgrade is necessary by executing the following query:

SELECT COUNT(1) as row_count,'0' as X_CUSTOM FROM W_GEO_D_7963 WHERE COUNTRY LIKE '% 'OR COUNTRY LIKE ' %'OR STATE_PROV LIKE '% 'OR STATE_PROV LIKE ' %'OR CITY LIKE '% 'OR CITY LIKE ' %'OR ZIPCODE LIKE '% 'OR ZIPCODE LIKE ' %'

2. If the query returns a count greater than zero, run the 7963_UPGRADE_POST_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.
If the query returns a count of zero, you do not need to run the 7963_UPGRADE_POST_SCRIPT.sql script.

40. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

41. Execute the 7964_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

42. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

43. Configure the Informatica parameter file 7964_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7964_UPG_PARAMS.txt."

44. If you are using PeopleSoft 8.8, in Informatica Workflow Manager, navigate to the folder UPGRADE_7963_to_7964_PSFT88 and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.
If you are using PeopleSoft 8.9 or 9.0, in Informatica Workflow Manager, navigate to the folder UPGRADE_7963_to_7964_PSFT90 and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.

45. Run the 7964_UPGRADE_POST_SCRIPT.sql. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

46. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

47. Once the data migration steps above are complete, you can delete the Upgrade repository to avoid any accidental use or confusion.

1. In the Informatica Administrator, select the Upgrade repository service.

2. In the General Properties area of the Properties tab, click Edit.

3. Make sure the operating mode of the repository service is set to Exclusive.

4. Click OK.

5. Choose Actions, and then click Delete Contents.

6. In the Delete contents for <repository name> dialog, enter the repository username and password, and then click OK.

7.10.4 Upgrading Oracle BI Applications From Version 7.9.5.1 to 7.9.6.4

Follow this procedure to upgrade from Oracle BI Applications version 7.9.5.1 to version 7.9.6.4 if your data warehouse database platform is Teradata.

To upgrade the data warehouse schema and migrate data for a Teradata database:

1. Execute the following scripts:

- 7961_UPGRADE_TMP_TABLES.sql

- 7962_UPGRADE_TMP_TABLES.sql

- 7963_UPGRADE_TMP_TABLES.sql

- 7964_UPGRADE_TMP_TABLES.sql

1. Open the SQL client for your database type.

2. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.

3. Open the <version>_UPGRADE_TMP_TABLES.sql file, and copy the contents into the SQL client.

4. Execute the script.

2. Edit and execute the 7961_RENAME_AND_EXCEPTIONS.sql script.

1. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.

2. Open the 7961_RENAME_AND_EXCEPTIONS.sql script.

3. Search for the following statements to locate columns with RENAME commands.
ALTER TABLE <Table_Name> RENAME <Column Name> TO <New Column Name>;

4. For all columns with RENAME commands, check to see whether any COLUMN STATISTICS are defined on them.

5. For all columns that have STATISTICS defined on them, back up the COLUMN STATISTICS definition and then drop them.

6. Execute the 7961_RENAME_AND_EXCEPTIONS.sql script.

7. Recreate STATISTICS on any column on which they were dropped.

3. The teradata.missing.defaults.properties file contains global default column values for data warehouse tables with NOT NULL columns for which default values are not specified in DAC. You can change the default values specified in the teradata.missing.defaults.properties file to match your environment. The file is located in \bifoundation\dac\conf\sqlgen\sql\teradata.

4. Generate upgrade scripts from DAC.

1. Log into DAC.

2. From the menu bar, select Tools, then ETL Management, and then Configure.

3. In the Sources dialog box, select Teradata as the target data warehouse database platform, and select the appropriate source data warehouse database platform.
The Configuration tab of the Data Warehouse Configuration Wizard is active.

4. Select "Generate upgrade statements for Data Warehouse Tables," and click Next.
The Data Warehouse SQL tab is active.

5. Do the following:
- Select the appropriate physical data source name for the Teradata database.

- In the container field, enter a custom container name for which you want to generate upgrade scripts. Alternatively, leave the field blank to generate upgrade scripts for all containers.

The Data Warehouse Configuration Wizard generates the following files and stores them in \bifoundation\DAC\conf\sqlgen\sql\teradata:

upgrade-regular.sql. This file contains scripts that DAC has verified are necessary to upgrade the data warehouse schema. The scripts handle new or altered tables and columns. For example, they may increase the size of simple data types or change a column from null to not null.

upgrade-questionable.sql. This file contains scripts that DAC suggests may be required to upgrade the data warehouse schema. These scripts are intended to be an aid in determining upgrade requirements and must be reviewed by a Teradata DBA and corrected if necessary.

upgradedwtables_sql.log. This file is the log file that corresponds to the upgrade-regular.sql file. It is for information purposes only.

upgrade-issues.log. This file is the log file that corresponds to the file upgrade-questionable.sql. It is for information purposes only.

6. Open the upgrade-regular.sql and upgrade-questionable.sql files, and search for the following statement to locate columns that have been added or changed.
ALTER TABLE <Table Name> ADD <Column Name><attributes>;

7. For all columns with the ADD command, check to see whether any columns exist already, and if they do, check whether they have STATISTICS defined on them.

8. For all columns that have STATISTICS defined on them, back up the column definition and then drop the STATISTICS.

9. Execute the scripts in the upgrade-regular.sql file.

10. Review the scripts in the upgrade-questionable.sql file. Edit the scripts as needed, and execute them.

11. Recreate STATISTICS on any column on which they were dropped.

5. Execute the following scripts:

- 7961_UPDATE_DEFAULTS.sql

- 7962_UPDATE_DEFAULTS.sql

- 7963_UPDATE_DEFAULTS.sql

- 7964_UPDATE_DEFAULTS.sql

6. Execute the 796_Backup Tables.sql script.

7. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

8. Configure the Informatica parameter file 796_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 796_UPG_PARAMS.txt."

9. If you are upgrading Oracle Financial Analytics, you need to configure specific parameters and update mappings. For more information, see Section A.3.1, "Setting Parameters and Mappings in 796_UPG_PARAMS.txt for Oracle Financial Analytics."

10. If you are upgrading Oracle Project Analytics, you need to configure specific parameters. For more information, see Section A.3.2, "Setting Parameters in 796_UPG_PARAMS.txt for Oracle Project Analytics."

11. Back up and truncate the table W_POSITION_DH.

12. If you are using PeopleSoft version 8.8, in Informatica Workflow Manager, navigate to the folder UPGRADE_7951_to_796_PSFT88 and execute the following workflows in the order as they appear: UPGRADE_DIMENSIONS, UPGRADE_FACTS, and RESET_DAC_REFRESH_DATES.
If you are using PeopleSoft version 8.9 or 9.0, in Informatica Workflow Manager, navigate to the folder UPGRADE_7951_to_796_PSFT90 and execute the following workflows in the order as they appear: UPGRADE_DIMENSIONS, UPGRADE_FACTS, and RESET_DAC_REFRESH_DATES.

13. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

14. Execute the 7961_Backup Tables.sql script.

15. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

16. Configure the Informatica parameter file 7961_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7961_UPG_PARAMS.txt."

17. If you are using PeopleSoft version 8.8, in Informatica Workflow Manager, navigate to the folder UPGRADE_796_to_7961_PSFT88 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using PeopleSoft version 8.9 or 9.0, in Informatica Workflow Manager, navigate to the folder UPGRADE_796_to_7961_PSFT90 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

18. Execute the 7962_Backup_Tables.sql script.

19. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

20. Configure the Informatica parameter file 7962_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7962_UPG_PARAMS.txt."

21. Configure additional parameters specific to PeopleSoft source systems. For instructions, see Section A.2.3, "Setting Parameters in 7962_UPG_PARAMS.txt for PeopleSoft Source Systems."

22. If you are upgrading Oracle Financial Analytics, you need to configure specific parameters and update mappings. For instructions, see Section A.3.4, "Setting Parameters and Mappings in 7962_UPG_PARAMS.txt for Oracle Financial Analytics."

23. If you are upgrading Oracle Financial Analytics, you need to make sure specific indexes are created. For instructions, see Appendix C, "Creating Indexes for Oracle Financial Analytics."

24. If you are using PeopleSoft version 8.8, in Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_PSFT88 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using PeopleSoft version 8.9 or 9.0, in Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_PSFT90 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

25. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

26. Execute the 7963_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

27. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

28. Configure the Informatica parameter file 7963_UPG_PARAMS.txt. For instructions, see Section A.1.8, "Setting Parameters in 7963_UPG_PARAMS.txt."

29. If you are upgrading Oracle Financial Analytics, do the following:

1. Set the parameters as specified in Appendix A, "Setting Parameters for All Source Systems."

2. Set the parameters as specified in Appendix A, "Setting Parameters Specific to PeopleSoft."

30. If you are upgrading Oracle Human Resources, set parameters as specified in Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt for Oracle Human Resources Analytics."

31. If your source system is PeopleSoft version 9.0 and you are upgrading Oracle Procurement and Spend Analytics, set the parameter as specified in Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt for Oracle Procurement and Spend Analytics on PeopleSoft Source System."

32. If you are using PeopleSoft 8.8, in Informatica Workflow Manager, navigate to the folder UPGRADE_7962_to_7963_PSFT88 and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.
If you are using PeopleSoft 8.9 or 9.0, in Informatica Workflow Manager, navigate to the folder UPGRADE_7962_to_7963_PSFT90 and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.

33. Upgrade geography-related attributes if necessary for your environment:

1. Determine whether a geography-related upgrade is necessary by executing the following query:

SELECT COUNT(1) as row_count,'0' as X_CUSTOM FROM W_GEO_D_7963 WHERE COUNTRY LIKE '% 'OR COUNTRY LIKE ' %'OR STATE_PROV LIKE '% 'OR STATE_PROV LIKE ' %'OR CITY LIKE '% 'OR CITY LIKE ' %'OR ZIPCODE LIKE '% 'OR ZIPCODE LIKE ' %'

2. If the query returns a count greater than zero, run the 7963_UPGRADE_POST_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.
If the query returns a count of zero, you do not need to run the 7963_UPGRADE_POST_SCRIPT.sql script.

34. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

35. Execute the 7964_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

36. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

37. Configure the Informatica parameter file 7964_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7964_UPG_PARAMS.txt."

38. If you are using PeopleSoft 8.8, in Informatica Workflow Manager, navigate to the folder UPGRADE_7963_to_7964_PSFT88 and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.
If you are using PeopleSoft 8.9 or 9.0, in Informatica Workflow Manager, navigate to the folder UPGRADE_7963_to_7964_PSFT90 and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.

39. Run the 7964_UPGRADE_POST_SCRIPT.sql. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

40. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

41. Once the data migration steps above are complete, you can delete the Upgrade repository to avoid any accidental use or confusion.

1. In the Informatica Administrator, select the Upgrade repository service.

2. In the General Properties area of the Properties tab, click Edit.

3. Make sure the operating mode of the repository service is set to Exclusive.

4. Click OK.

5. Choose Actions, and then click Delete Contents.

6. In the Delete contents for <repository name> dialog, enter the repository username and password, and then click OK.

7.10.5 Upgrading Oracle BI Applications From Version 7.9.6.1 to 7.9.6.4

Follow this procedure to upgrade from Oracle Business Applications version 7.9.6.1 to version 7.9.6.4 if your data warehouse database platform is Teradata.

To upgrade the data warehouse schema and migrate data for a Teradata database:

1. Execute the following scripts:

- 7962_UPGRADE_TMP_TABLES.sql

- 7963_UPGRADE_TMP_TABLES.sql

- 7964_UPGRADE_TMP_TABLES.sql

1. Open the SQL client for your database type.

2. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.

3. Open the <version>_UPGRADE_TMP_TABLES.sql file, and copy the contents into the SQL client.

4. Execute the script.

2. The teradata.missing.defaults.properties file contains global default column values for data warehouse tables with NOT NULL columns for which default values are not specified in DAC. You can change the default values specified in the teradata.missing.defaults.properties file to match your environment. The file is located in \bifoundation\dac\conf\sqlgen\sql\teradata.

3. Generate upgrade scripts from DAC.

1. Log into DAC.

2. From the menu bar, select Tools, then ETL Management, and then Configure.

3. In the Sources dialog box, select Teradata as the target data warehouse database platform, and select the appropriate source data warehouse database platform.
The Configuration tab of the Data Warehouse Configuration Wizard is active.

4. Select "Generate upgrade statements for Data Warehouse Tables," and click Next.
The Data Warehouse SQL tab is active.

5. Do the following:
- Select the appropriate physical data source name for the Teradata database.

- In the container field, enter a custom container name for which you want to generate upgrade scripts. Alternatively, leave the field blank to generate upgrade scripts for all containers.

The Data Warehouse Configuration Wizard generates the following files and stores them in \bifoundation\DAC\conf\sqlgen\sql\teradata:

upgrade-regular.sql. This file contains scripts that DAC has verified are necessary to upgrade the data warehouse schema. The scripts handle new or altered tables and columns. For example, they may increase the size of simple data types or change a column from null to not null.

upgrade-questionable.sql. This file contains scripts that DAC suggests may be required to upgrade the data warehouse schema. These scripts are intended to be an aid in determining upgrade requirements and must be reviewed by a Teradata DBA and corrected if necessary.

upgradedwtables_sql.log. This file is the log file that corresponds to the upgrade-regular.sql file. It is for information purposes only.

upgrade-issues.log. This file is the log file that corresponds to the file upgrade-questionable.sql. It is for information purposes only.

6. Open the upgrade-regular.sql and upgrade-questionable.sql files, and search for the following statement to locate columns that have been added or changed.
ALTER TABLE <Table Name> ADD <Column Name><attributes>;

7. For all columns with the ADD command, check to see whether any columns exist already, and if they do, check whether they have STATISTICS defined on them.

8. For all columns that have STATISTICS defined on them, back up the column definition and then drop the STATISTICS.

9. Execute the scripts in the upgrade-regular.sql file.

10. Review the scripts in the upgrade-questionable.sql file. Edit the scripts as needed, and execute them.

11. Recreate STATISTICS on any column on which they were dropped.

4. Execute the following scripts:

- 7962_UPDATE_DEFAULTS.sql

- 7963_UPDATE_DEFAULTS.sql

- 7964_UPDATE_DEFAULTS.sql

5. Execute the 7962_Backup_Tables.sql script.

6. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

7. Configure the Informatica parameter file 7962_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7962_UPG_PARAMS.txt."

8. Configure additional parameters specific to PeopleSoft source systems. For instructions, see Section A.2.3, "Setting Parameters in 7962_UPG_PARAMS.txt for PeopleSoft Source Systems."

9. If you are upgrading Oracle Financial Analytics, you need to configure specific parameters and update mappings. For instructions, see Section A.3.4, "Setting Parameters and Mappings in 7962_UPG_PARAMS.txt for Oracle Financial Analytics."

10. If you are upgrading Oracle Financial Analytics, you need to make sure specific indexes are created. For instructions, see Appendix C, "Creating Indexes for Oracle Financial Analytics."

11. If you are using PeopleSoft version 8.8, in Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_PSFT88 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using PeopleSoft version 8.9 or 9.0, in Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_PSFT90 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

12. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

13. Execute the 7963_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

14. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

15. Configure the Informatica parameter file 7963_UPG_PARAMS.txt. For instructions, see Section A.1.8, "Setting Parameters in 7963_UPG_PARAMS.txt."

16. If you are upgrading Oracle Financial Analytics, do the following:

1. Set the parameters as specified in Appendix A, "Setting Parameters for All Source Systems."

2. Set the parameters as specified in Appendix A, "Setting Parameters Specific to PeopleSoft."

17. If you are upgrading Oracle Human Resources, set parameters as specified in Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt for Oracle Human Resources Analytics."

18. If your source system is PeopleSoft version 9.0 and you are upgrading Oracle Procurement and Spend Analytics, set the parameter as specified in Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt for Oracle Procurement and Spend Analytics on PeopleSoft Source System."

19. If you are using PeopleSoft 8.8, in Informatica Workflow Manager, navigate to the folder UPGRADE_7962_to_7963_PSFT88 and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.
If you are using PeopleSoft 8.9 or 9.0, in Informatica Workflow Manager, navigate to the folder UPGRADE_7962_to_7963_PSFT90 and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.

20. Upgrade geography-related attributes if necessary for your environment:

1. Determine whether a geography-related upgrade is necessary by executing the following query:

SELECT COUNT(1) as row_count,'0' as X_CUSTOM FROM W_GEO_D_7963 WHERE COUNTRY LIKE '% 'OR COUNTRY LIKE ' %'OR STATE_PROV LIKE '% 'OR STATE_PROV LIKE ' %'OR CITY LIKE '% 'OR CITY LIKE ' %'OR ZIPCODE LIKE '% 'OR ZIPCODE LIKE ' %'

2. If the query returns a count greater than zero, run the 7963_UPGRADE_POST_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.
If the query returns a count of zero, you do not need to run the 7963_UPGRADE_POST_SCRIPT.sql script.

21. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

22. Execute the 7964_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

23. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

24. Configure the Informatica parameter file 7964_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7964_UPG_PARAMS.txt."

25. If you are using PeopleSoft 8.8, in Informatica Workflow Manager, navigate to the folder UPGRADE_7963_to_7964_PSFT88 and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.
If you are using PeopleSoft 8.9 or 9.0, in Informatica Workflow Manager, navigate to the folder UPGRADE_7963_to_7964_PSFT90 and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.

26. Run the 7964_UPGRADE_POST_SCRIPT.sql. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

27. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

28. Once the data migration steps above are complete, you can delete the Upgrade repository to avoid any accidental use or confusion.

1. In the Informatica Administrator, select the Upgrade repository service.

2. In the General Properties area of the Properties tab, click Edit.

3. Make sure the operating mode of the repository service is set to Exclusive.

4. Click OK.

5. Choose Actions, and then click Delete Contents.

6. In the Delete contents for <repository name> dialog, enter the repository username and password, then click OK.

7.10.6 Upgrading Oracle BI Applications From Version 7.9.6.2 to 7.9.6.4

Follow this procedure to upgrade from Oracle Business Applications version 7.9.6.2 to version 7.9.6.4 if your data warehouse database platform is Teradata.

To upgrade the data warehouse schema and migrate data for a Teradata database:

1. Execute the 7963_UPGRADE_TMP_TABLES.sql and 7964_UPGRADE_TMP_TABLES.sql script.

1. Open the SQL client for your database type.

2. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.

3. Open the <version>_UPGRADE_TMP_TABLES.sql file, and copy the contents into the SQL client.

4. Execute the script.

2. The teradata.missing.defaults.properties file contains global default column values for data warehouse tables with NOT NULL columns for which default values are not specified in DAC. You can change the default values specified in the teradata.missing.defaults.properties file to match your environment. The file is located in \bifoundation\dac\conf\sqlgen\sql\teradata.

3. Generate upgrade scripts from DAC.

1. Log into DAC.

2. From the menu bar, select Tools, then ETL Management, and then Configure.

3. In the Sources dialog box, select Teradata as the target data warehouse database platform, and select the appropriate source data warehouse database platform.
The Configuration tab of the Data Warehouse Configuration Wizard is active.

4. Select "Generate upgrade statements for Data Warehouse Tables," and click Next.
The Data Warehouse SQL tab is active.

5. Do the following:
- Select the appropriate physical data source name for the Teradata database.

- In the container field, enter a custom container name for which you want to generate upgrade scripts. Alternatively, leave the field blank to generate upgrade scripts for all containers.

The Data Warehouse Configuration Wizard generates the following files and stores them in \bifoundation\DAC\conf\sqlgen\sql\teradata:

upgrade-regular.sql. This file contains scripts that DAC has verified are necessary to upgrade the data warehouse schema. The scripts handle new or altered tables and columns. For example, they may increase the size of simple data types or change a column from null to not null.

upgrade-questionable.sql. This file contains scripts that DAC suggests may be required to upgrade the data warehouse schema. These scripts are intended to be an aid in determining upgrade requirements and must be reviewed by a Teradata DBA and corrected if necessary.

upgradedwtables_sql.log. This file is the log file that corresponds to the upgrade-regular.sql file. It is for information purposes only.

upgrade-issues.log. This file is the log file that corresponds to the file upgrade-questionable.sql. It is for information purposes only.

6. Open the upgrade-regular.sql and upgrade-questionable.sql files, and search for the following statement to locate columns that have been added or changed.
ALTER TABLE <Table Name> ADD <Column Name><attributes>;

7. For all columns with the ADD command, check to see whether any columns exist already, and if they do, check whether they have STATISTICS defined on them.

8. For all columns that have STATISTICS defined on them, back up the column definition and then drop the STATISTICS.

9. Execute the scripts in the upgrade-regular.sql file.

10. Review the scripts in the upgrade-questionable.sql file. Edit the scripts as needed, and execute them.

11. Recreate STATISTICS on any column on which they were dropped.

4. Execute the 7963_UPDATE_DEFAULTS.sql and 7964_UPDATE_DEFAULTS.sql scripts.

5. Execute the 7963_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

6. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

7. Configure the Informatica parameter file 7963_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt."

8. If you are upgrading Oracle Financial Analytics, do the following:

1. Set the parameters as specified in Appendix A, "Setting Parameters for All Source Systems."

2. Set the parameters as specified in Appendix A, "Setting Parameters Specific to PeopleSoft."

9. If you are upgrading Oracle Human Resources, set parameters as specified in Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt for Oracle Human Resources Analytics."

10. If your source system is PeopleSoft version 9.0 and you are upgrading Oracle Procurement and Spend Analytics, set the parameter as specified in Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt for Oracle Procurement and Spend Analytics on PeopleSoft Source System."

11. If you are using PeopleSoft 8.8, in Informatica Workflow Manager, navigate to the folder UPGRADE_7962_to_7963_PSFT88 and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.
If you are using PeopleSoft 8.9 or 9.0, in Informatica Workflow Manager, navigate to the folder UPGRADE_7962_to_7963_PSFT90 and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.

12. Upgrade geography-related attributes if necessary for your environment:

1. Determine whether a geography-related upgrade is necessary by executing the following query:

SELECT COUNT(1) as row_count,'0' as X_CUSTOM FROM W_GEO_D_7963 WHERE COUNTRY LIKE '% 'OR COUNTRY LIKE ' %'OR STATE_PROV LIKE '% 'OR STATE_PROV LIKE ' %'OR CITY LIKE '% 'OR CITY LIKE ' %'OR ZIPCODE LIKE '% 'OR ZIPCODE LIKE ' %'

2. If the query returns a count greater than zero, run the 7963_UPGRADE_POST_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.
If the query returns a count of zero, you do not need to run the 7963_UPGRADE_POST_SCRIPT.sql script.

13. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

14. Execute the 7964_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

15. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

16. Configure the Informatica parameter file 7964_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7964_UPG_PARAMS.txt."

17. If you are using PeopleSoft 8.8, in Informatica Workflow Manager, navigate to the folder UPGRADE_7963_to_7964_PSFT88 and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.
If you are using PeopleSoft 8.9 or 9.0, in Informatica Workflow Manager, navigate to the folder UPGRADE_7963_to_7964_PSFT90 and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.

18. Run the 7964_UPGRADE_POST_SCRIPT.sql. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

19. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

20. Once the data migration steps above are complete, you can delete the Upgrade repository to avoid any accidental use or confusion.

1. In the Informatica Administrator, select the Upgrade repository service.

2. In the General Properties area of the Properties tab, click Edit.

3. Make sure the operating mode of the repository service is set to Exclusive.

4. Click OK.

5. Choose Actions, and then click Delete Contents.

6. In the Delete contents for <repository name> dialog, enter the repository username and password, and then click OK.

7.10.7 Upgrading Oracle BI Applications From Version 7.9.6.3 to 7.9.6.4

Follow this procedure to upgrade from Oracle Business Applications version 7.9.6.3 to version 7.9.6.4 if your data warehouse database platform is Teradata.

To upgrade the data warehouse schema and migrate data for a Teradata database:

1. Execute the 7964_UPGRADE_TMP_TABLES.sql script.

1. Open the SQL client for your database type.

2. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.

3. Open the 7964_UPGRADE_TMP_TABLES.sql file, and copy the contents into the SQL client.

4. Execute the script.

2. The teradata.missing.defaults.properties file contains global default column values for data warehouse tables with NOT NULL columns for which default values are not specified in DAC. You can change the default values specified in the teradata.missing.defaults.properties file to match your environment. The file is located in \bifoundation\dac\conf\sqlgen\sql\teradata.

3. Generate upgrade scripts from DAC.

1. Log into DAC.

2. From the menu bar, select Tools, then ETL Management, and then Configure.

3. In the Sources dialog box, select Teradata as the target data warehouse database platform, and select the appropriate source data warehouse database platform.
The Configuration tab of the Data Warehouse Configuration Wizard is active.

4. Select "Generate upgrade statements for Data Warehouse Tables," and click Next.
The Data Warehouse SQL tab is active.

5. Do the following:
- Select the appropriate physical data source name for the Teradata database.

- In the container field, enter a custom container name for which you want to generate upgrade scripts. Alternatively, leave the field blank to generate upgrade scripts for all containers.

The Data Warehouse Configuration Wizard generates the following files and stores them in \bifoundation\DAC\conf\sqlgen\sql\teradata:

upgrade-regular.sql. This file contains scripts that DAC has verified are necessary to upgrade the data warehouse schema. The scripts handle new or altered tables and columns. For example, they may increase the size of simple data types or change a column from null to not null.

upgrade-questionable.sql. This file contains scripts that DAC suggests may be required to upgrade the data warehouse schema. These scripts are intended to be an aid in determining upgrade requirements and must be reviewed by a Teradata DBA and corrected if necessary.

upgradedwtables_sql.log. This file is the log file that corresponds to the upgrade-regular.sql file. It is for information purposes only.

upgrade-issues.log. This file is the log file that corresponds to the file upgrade-questionable.sql. It is for information purposes only.

6. Open the upgrade-regular.sql and upgrade-questionable.sql files, and search for the following statement to locate columns that have been added or changed.
ALTER TABLE <Table Name> ADD <Column Name><attributes>;

7. For all columns with the ADD command, check to see whether any columns exist already, and if they do, check whether they have STATISTICS defined on them.

8. For all columns that have STATISTICS defined on them, back up the column definition and then drop the STATISTICS.

9. Execute the scripts in the upgrade-regular.sql file.

10. Review the scripts in the upgrade-questionable.sql file. Edit the scripts as needed, and execute them.

11. Recreate STATISTICS on any column on which they were dropped.

4. Execute the 7964_UPDATE_DEFAULTS.sql scripts.

5. Execute the 7964_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

6. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

7. Configure the Informatica parameter file 7964_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7964_UPG_PARAMS.txt."

8. If you are using PeopleSoft 8.8, in Informatica Workflow Manager, navigate to the folder UPGRADE_7963_to_7964_PSFT88 and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.
If you are using PeopleSoft 8.9 or 9.0, in Informatica Workflow Manager, navigate to the folder UPGRADE_7963_to_7964_PSFT90 and execute first the UPGRADE_DIMENSIONS workflow, and then the UPGRADE_FACTS workflow.

9. Run the 7964_UPGRADE_POST_SCRIPT.sql. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

10. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

11. Once the data migration steps above are complete, you can delete the Upgrade repository to avoid any accidental use or confusion.

1. In the Informatica Administrator, select the Upgrade repository service.

2. In the General Properties area of the Properties tab, click Edit.

3. Make sure the operating mode of the repository service is set to Exclusive.

4. Click OK.

5. Choose Actions, and then click Delete Contents.

6. In the Delete contents for <repository name> dialog, enter the repository username and password, and then click OK.

7.11 Localizing the Policy Store

The Oracle BI Applications 7.9.6.4 installer contains different policy stores for different languages. The default policy store that is deployed during the installation is in English. If you want to configure the policy store for any of the other available languages, perform the procedure below.

To configure the policy store for languages other than English:

1. Stop the Oracle BI Services.

2. Copy the system-jazn-data_<LN>.xml file from $ORACLE_BI_HOME\biapps\admin\provisioning\localization\ to $DOMAIN_HOME\config\fmwconfig\.
For example, to implement the policy store for French, you would copy the file system-jazn-data_fr.xml into the \fmwconfig directory.

3. Back up the existing system-jazn-data.xml file in $DOMAIN_HOME\config\fmwconfig\.

4. Rename $DOMAIN_HOME\config\fmwconfig\system-jazn-data_<LN>.xml to system-jazn-data.xml.

5. Start Oracle BI Services.

7.12 Importing the Oracle BI Applications Version 7.9.6.4 LDIF File Into the Embedded LDAP Server

In this procedure, you will import the standard (out-of-the-box) Oracle BI Applications version 7.9.6.4 LDIF file into the WebLogic Server embedded LDAP server.

To import the Oracle BI Applications version 7.9.6.4 LDIF file:

1. Log in to the WebLogic Server Administration Console using the URL http://<host name>:7001/console.

2. Select the name of the security realm into which the LDIF file is to be imported (for example, myrealm).

3. Select Providers and then the type of provider into which the LDIF file is to be imported (for example, Providers, and then Authentication).

4. Select the security provider in which the LDIF file is to be imported and select Migration, and then select Import.

5. Click Save.

7.13 Upgrading the Oracle BI Repository and Presentation Catalog to the Oracle BI Enterprise Edition 11g Version

Use the Oracle BI Enterprise Edition Upgrade Assistant to upgrade the following repositories and web catalog from the Oracle BI Enterprise Edition 10g format to the 11g format:

- The standard (out-of-the-box) Oracle BI Repository. This repository is the one that you originally received from Oracle as part of your current Oracle BI Applications installation (the version from which you are upgrading). Standard repositories from previous releases are available in the installation folder $ORACLE_BI_HOME\biapps\upgrade.

- The Oracle BI Repository you are currently using (the repository deployed in production).

- The Presentation Catalog you are currently using (the catalog deployed in production).

For instructions on using the Upgrade Assistant, see Oracle Fusion Middleware Upgrade Guide for Oracle Business Intelligence.

Note:

Your current policy store will be merged with the Oracle BI Applications release 7.9.6.4 policy store while upgrading the Oracle BI repository from the 10g format to the 11g format. The final policy store will be the super set of Oracle BI Applications release 7.9.6.4 policy store and the custom and current policy information from the 10g repository.

Also, your current users and groups from the repository will be merged with the Oracle BI Applications release 7.9.6.4 identity store while upgrading the Oracle BI repository from the 10g format to the 11g format. The final identity store will be the super set of the Oracle BI Applications release 7.9.6.4 identity store and the identity store information (users and groups) from the 10g repository.

If you require the policy store to be in a language other than English, perform the steps in Section 7.11, "Localizing the Policy Store."

7.14 Merging Oracle BI Applications Version 7.9.6.4 Repository With Customer Repository

Note:

Before you begin this procedure, you must have already upgraded the Oracle BI repository you are currently using and the standard (out-of-the-box) Oracle BI repository version 7.9.x (the version from which you are upgrading) to the Oracle BI Enterprise Edition 11g format. For more information, see Section 7.13, "Upgrading the Oracle BI Repository and Presentation Catalog to the Oracle BI Enterprise Edition 11g Version."

This process merges your customizations of a prior release of the Oracle BI repository with the new release 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 7.14.1, "Preparing for the Oracle BI Repository Upgrade"

- Section 7.14.2, "Equalizing the Oracle BI Repositories"

- Section 7.14.3, "Comparing the Oracle BI Repositories"

- Section 7.14.4, "Merging the Oracle BI Repositories"

The tasks in this section refer to multiple releases of the Oracle BI repository. Table 7-1 provides the names and descriptions of the repositories used in the examples in this section.

Table 7-1 Names of Analytics Repositories used in Examples

Name of Repository

Description

OracleBIAnalyticsApps_79x.rpd

The standard Oracle BI repository for the version you are upgrading from.

Note: Standard repositories from previous releases are available in the folder $ORACLE_BI_HOME\biapps\upgrade.

OracleBIAnalyticsApps.rpd

The standard Oracle BI repository for the version you are upgrading to.

Customer_OracleBIAnalyticsApps.rpd

The Oracle BI 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.

7.14.1 Preparing for the Oracle BI Repository Upgrade

Follow this procedure to prepare for the repository upgrade.

To prepare for the Analytics repository upgrade:

1. Set up a directory for the merge process, such as \OracleBIUpgrade, and create the following subfolders:

- Original

- AfterEqualize

- AfterMerge

- AfterManualWork

- AfterRegressions

2. Copy the following repositories to the folder \OracleBIUpgrade\Original:

- The standard repository that you upgraded to the 11g format in Section 7.13, "Upgrading the Oracle BI Repository and Presentation Catalog to the Oracle BI Enterprise Edition 11g Version" (for example, OracleBIAnalyticsApps_79x.rpd).

- The production repository that you also upgraded to the 11g format in Section 7.13 (for example, Customer_OracleBIAnalyticsApps.rpd.

- The Oracle BI repository from the latest installation (for example, OracleBIAnalyticsApps.rpd)

If, in your current environment, you are running Oracle BI Applications for one or more modules using a Oracle BI repository in which you extracted the corresponding projects for the modules from the standard Oracle BI repository file you received from the previous release, you need to extract the same projects from the OracleBIAnalyticsApps_79x.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 Oracle BI 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 OracleBIAnalyticsApps_79x.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.

7.14.2 Equalizing the Oracle BI Repositories

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, OracleBIAnalyticsApps_79x.rpd, OracleBIAnalyticsApps.rpd, and Customer_OracleBIAnalyticsApps.rpd) are equivalent.

The point of this step is to determine for every object in the OracleBIAnalyticsApps.rpd and the Customer_OracleBIAnalyticsApps.rpd whether it is coming from the OracleBIAnalyticsApps_79x.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 $ORACLE_BI_HOME\biapps\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.
Table 7-2 provides a list of the available MAP files and the Siebel Analytics or Oracle BI Applications release version associated with the file.

Table 7-2 Rename MAP Files to Be Used for Various Releases

Siebel Analytics / Oracle Business Intelligence Applications Release Version (Upgrading from DW Version)

Rename MAP File to Be Used

Siebel Business Analytics Applications 7.0.x

Not available

Siebel Business Analytics Applications 7.5.x

Not available

Siebel Business Analytics Applications 7.7.x (with Siebel CRM OLTP Pre-7.7.0)

Rename77-7963.map

Siebel Business Analytics Applications 7.7.x (with Siebel CRM OLTP 7.7.0)

Rename771-7963.map

Siebel Business Analytics Applications 7.8.2 and all 7.8.x versions before this release

Rename782-7963.map

Siebel Business Analytics Applications 7.8.3 and all 7.8.x versions after this release

Rename783-7963.map

Oracle BI Applications 7.9.0

Rename79x-7963.map

Oracle BI Applications 7.9.1

Rename79x-7963.map

Oracle BI Applications 7.9.2

Rename79x-7963.map

Oracle BI Applications 7.9.3

Rename793to7963.map

Oracle BI Applications 7.9.4

Rename794to7963.map

Oracle BI Applications 7.9.5

Rename79x-7963.map

Oracle BI Applications 7.9.5.1

Rename7951to7963.map

Oracle BI Applications 7.9.5.2

Rename7951to7963.map

Oracle BI Applications 7.9.6

Rename79x-7963.map

Oracle BI Applications 7.9.6.2

rename7963to7964.map

Not required for upgrades from 7.9.6.2 to 7.9.6.3.

Oracle BI Applications 7.9.6.3

rename7963to7964.map

The syntax of the equalizerpds command is as follows:

equalizerpds.exe  [-B [password1]] -C base_repository_name [-E [password2]] -F repository2_name [-J udml_utf8_file_name_equalization] [-O ouput_repository_name] [-Y equalStringSet]
-Y          Treat the characters as equals.
/?          Display this usage information and exit.

To equalize a repository:

1. Copy the appropriate MAP file from the $ORACLE_BI_HOME\biapps\upgrade folder into the folder where you will execute equalizerpds.exe, for example, \OracleBIUpgrade\Original.

2. Run equalizerpds.exe to equalize the repository from the latest installation (for example, OracleBIAnalyticsApps.rpd) with the original repository (for example, OracleBIAnalyticsAppss_793.rpd). An example of the equalizerpds command is as follows:

equalizerpds -B SADMIN
-C \\OracleBIUpgrade\Original\OracleBIAnalyticsApps_791.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 $ORACLE_BI_HOME\biapps\upgrade folder.

If the equalizerpds.exe executable file runs correctly, no errors are returned.

3. Run equalizerpds.exe to equalize your customized repository (for example, Customer_OracleBIAnalyticsApps.rpd) with the original repository (for example, OracleBIAnalyticsApps_79x.rpd). An example of the equalizerpds command is as follows:

equalizerpds -B SADMIN
-C \\OracleBIUpgrade\Original\OracleBIAnalyticsApps_791.rpd
-E SADMIN
-F \\OracleBIUpgrade\Original\Customer_OracleBIAnalyticsApps.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.

4. 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).

7.14.3 Comparing the Oracle BI Repositories

Follow this procedure to compare your existing repository with the new version to which you are upgrading.

To compare the Oracle BI 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 Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition.

7.14.4 Merging the Oracle BI Repositories

In this procedure, you execute the main algorithm to upgrade the repository. For more information on merging the repositories, see Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition.

To merge versions of the Oracle BI repositories:

1. Copy the three repositories (for example, OracleBIAnalyticsApps_79x.rpd, OracleBIAnalyticsApps.rpd, and Customer_OracleBIAnalyticsApps.rpd) to the AfterMerge folder.

2. Open the repository from the latest installation (for example, OracleBIAnalyticsApps.rpd) in the \OracleBIUpgrade\AfterMerge folder.

3. From the Administration Tool menu bar, select File, then select Merge.

4. Select the Merge Type option Full Repository Merge.

5. In the Select Original Repository dialog box, select the original repository (for example, OracleBIAnalyticsApps_79x.rpd).

6. Enter the password for the original repository.

7. In the Select Modified Repository dialog box, select the repository that contains the customizations you made to the previous version of the Analytics repository.

8. Enter the password for the modified repository.

9. In the Saved Merged Repository as dialog box, enter the name for the merged repository, for example, Merged_Repository_OracleBIAnalyticsApps.rpd.
The new repository will contain the final results of the merge.

10. Select the Equalize during merge check box.

11. Click Next.

12. In the Decision drop-down list, select the action you want to take regarding the repository change, or accept the default action.

13. To locate subsequent rows with empty Decision fields, click the Decision header cell.
When all rows have a value in the Decision field, the Finish button is enabled.

14. Select the Check consistency of the merged RPD check box.

15. Click Finish.
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.

16. 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'

17. Copy the repository to the folder \OracleBIUpgrade\AfterManualWork.

7.15 Merging Oracle BI Applications Version 7.9.6.4 Presentation Catalog With Current (Custom) Catalog

Note:

Before you begin this procedure, you must have already upgraded your current (custom) catalog to the Oracle BI Enterprise Edition 11g format. For more information, see Section 7.13, "Upgrading the Oracle BI Repository and Presentation Catalog to the Oracle BI Enterprise Edition 11g Version."

You need to perform the following tasks to complete the presentation merge process.

- Section 7.15.1, "Trimming the Input Presentation Catalog"

- Section 7.15.2, "Merging the Oracle BI Applications Version 7.9.6.4 Presentation Catalog With Current (Custom) Catalog"

- Section 7.15.3, "Testing the Results of the Presentation Catalog Upgrade"

These procedures use the following terminology to identify the various presentation catalogs you will use in the merge process:

- The original presentation catalog. This catalog is the output from the step you performed in Section 7.13, "Upgrading the Oracle BI Repository and Presentation Catalog to the Oracle BI Enterprise Edition 11g Version." It is the version of the unmodified presentation catalog you received with the Oracle BI Applications release you are upgrading from that you upgraded to the 11g format.

- The new presentation catalog. This is the standard Oracle BI Applications 7.9.6.4 presentation catalog that is installed with Oracle BI Applications.

- The current presentation catalog. This catalog is the output from the step you performed in Section 7.13, "Upgrading the Oracle BI Repository and Presentation Catalog to the Oracle BI Enterprise Edition 11g Version." It is the presentation catalog currently in use at your organization that you upgraded to the 11g format.

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 Fusion Middleware Upgrade Guide for Oracle Business Intelligence

7.15.1 Trimming the Input Presentation Catalog

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.

7.15.2 Merging the Oracle BI Applications Version 7.9.6.4 Presentation Catalog With Current (Custom) Catalog

Note:

Before you begin this procedure, you must have already upgraded your current (custom) catalog to the Oracle BI Enterprise Edition 11g format. For more information, see Section 7.13, "Upgrading the Oracle BI Repository and Presentation Catalog to the Oracle BI Enterprise Edition 11g Version."

Follow the instructions in this section to merge the Oracle BI Applications version 7.9.6.4 presentation catalog with the catalog you are currently using. This procedure uses the Oracle BI Enterprise Edition Catalog Manager. High-level steps for the merge process are provided in this section. For detailed instructions on using the Catalog Manager, see the chapter "Configuring and Managing the Oracle BI Presentation Catalog," in the Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition 11g Release 1 (11.1.1).

To merge the Oracle BI Applications version 7.9.6.4 presentation catalog with the current (custom) catalog:

1. Start the Catalog Manager, and open your current (custom) presentation catalog in offline mode.
For instructions, see the section "Starting Catalog Manager and Opening Catalogs," in the Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition 11g Release 1 (11.1.1).

2. Start another instance of the Catalog Manager, and open the Oracle BI Applications version 7.9.6.4 (out-of-the-box) presentation catalog in offline mode.

3. Copy and paste the custom objects from your current presentation catalog into the Oracle BI Applications version 7.9.6.4 (out-of-the-box) presentation catalog.
For instructions, see the section "Working with Objects in Catalog Manager," in the Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition 11g Release 1 (11.1.1).

4. If you created custom catalog groups that are not in the version 7.9.6.4 presentation catalog, you need to convert the custom catalog groups to application roles in order to maintain consistency with the version 7.9.6.4 presentation catalog.
To convert custom catalog groups to application roles, run the following command:

runcat.cmd/runcat.sh -cmd replaceAccountInPermissions -old <Catalog Group Name> -oldType group -new <App Role Name> -newType role -offline  <catalog path>

For example:

runcat.cmd -cmd replaceAccountInPermissions -old "AP Analyst" -oldType group -new "AP Analyst" -newType role -offline  c:/SampleWebcat

This command replaces a specified account with another in all catalog object ACLs and privileges in the presentation catalog, entirely in the offline mode. If an entirely new application role is specified as the replacement account, then it is necessary to refresh the GUIDs in the presentation catalog before it can be used.

Note: If the specified replacement user or group is not already present in the presentation catalog 11g Release 1 (11.1.1) already, then this operation will fail.

For more information, see the Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition 11g Release 1 (11.1.1).

7.15.3 Testing the Results of the Presentation Catalog Upgrade

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.

7.16 Regression Testing the Oracle BI Repository Merge

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:

1. 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.

2. 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 Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition.

3. Execute the logical SQL against the old repository using the command line utility nQCmd.exe located in $ORACLE_BI_HOME\bifoundation\server\bin, and save the results to a file.
For information about the nQCmd.exe utility, see Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition.

4. Edit the logical SQL test scripts to account for the name changes or modifications resulting from the upgrade.

5. Execute the edited logical SQL against the merged repository, and save the results.

6. 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.

Part IV

Upgrading When Your Source System is JD Edwards

Part IV contains instructions for upgrading to the current release of Oracle BI Applications when you are running JD Edwards Enterprise as your source system.

Part IV contains Chapter 8, "Upgrading Oracle BI Applications for JD Edwards Source Systems."

8 Upgrading Oracle BI Applications for JD Edwards Source Systems

This section contains instructions for upgrading Oracle BI Applications when you are running JD Edwards Enterprise Applications as your source system.

This section contains the following topics:

- Section 8.1, "Prerequisites for Upgrading Oracle BI Applications"

- Section 8.2, "Upgrading Oracle BI Infrastructure to Version 11g"

- Section 8.3, "Upgrading Oracle BI Applications"

- Section 8.4, "Upgrading to Informatica PowerCenter Version 9.0.1 Hotfix 2"

- Section 8.5, "Upgrading the Informatica Repository"

- Section 8.6, "Upgrading the Informatica Repository When You Are Already Running Informatica PowerCenter 9.1"

- Section 8.7, "Verifying Configurations for Informatica PowerCenter Version 9.0.1 Hotfix 2 to Work With Oracle BI Applications and DAC"

- Section 8.8, "Upgrading to and Configuring DAC Version 11g"

- Section 8.9, "Upgrading the Data Warehouse Schema and Migrating Data for Non-Teradata Databases"

- Section 8.10, "Upgrading the Data Warehouse Schema and Migrating Data for Teradata Databases"

- Section 8.11, "Localizing the Policy Store"

- Section 8.12, "Importing the Oracle BI Applications Version 7.9.6.4 LDIF File Into the Embedded LDAP Server"

- Section 8.13, "Upgrading the Oracle BI Repository and Presentation Catalog to the Oracle BI Enterprise Edition 11g Version"

- Section 8.14, "Merging Oracle BI Applications Version 7.9.6.4 Repository With Customer Repository"

- Section 8.15, "Merging Oracle BI Applications Version 7.9.6.4 Presentation Catalog With Current (Custom) Catalog"

- Section 8.16, "Regression Testing the Oracle BI Repository Merge"

8.1 Prerequisites for Upgrading Oracle BI Applications

Complete the following prerequisites before upgrading to Oracle BI Applications release 7.9.6.4:

- The DAC Client requires an ODBC connection to the Oracle Business Analytics Warehouse when the database type is Oracle, SQL Server, DB2, and DB2-390 in order to upgrade the data warehouse schema using the DDL Import Utility.
Before you upgrade to Oracle BI Applications verify whether you have the appropriate ODBC connections set. If you do not, see Appendix F, "Creating ODBC Database Connections for DAC."

8.2 Upgrading Oracle BI Infrastructure to Version 11g

You must upgrade Oracle BI Infrastructure to version 11g. For the specific release of Oracle BI Infrastructure 11g that is supported for this release of Oracle BI Applications, see the System Requirements and Supported Platforms for Oracle Business Intelligence Applications. For information on installing the supported version of Oracle BI Infrastructure, see the Oracle Fusion Middleware Upgrade Guide for Oracle Business Intelligence.

8.3 Upgrading Oracle BI Applications

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 Guide for Informatica PowerCenter Users.

Note the following points:

- Review "Chapter 3: Preinstallation and Predeployment Requirements for Oracle BI Applications," in the Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users. You must satisfy these requirements in order to upgrade to the current version of Oracle BI Applications.

- Perform only the step that addresses the running of the installer. Do not perform the configuration instructions that follow the running of the installer.

- If you have a previous release of Oracle BI Applications installed, you must uninstall it before you run the installer for the current release. If you do not uninstall the old release, some folders from the current release will not be correctly installed. (Make a back-up of your DAC folder before you uninstall the old release. This will be the backup of your DAC Client and Server and the DAC metadata files.)

8.4 Upgrading to Informatica PowerCenter Version 9.0.1 Hotfix 2

You must install Informatica PowerCenter 9.0.1 Hotfix 2 to run the current version of Oracle BI Applications. See the System Requirements and Supported Platforms for Oracle Business Intelligence Applications for information about additional hotfixes or emergency bug fixes that may be required to support the current version of Informatica.

Note:

Oracle BI Applications release 7.9.6.4 is also certified to run with Informatica PowerCenter version 9.1 Hotfix 2. For instructions on upgrading the Informatica Repository if you have previously upgraded to Informatica PowerCenter 9.1 Hotfix 2, see Section 8.6, "Upgrading the Informatica Repository When You Are Already Running Informatica PowerCenter 9.1."

The components and architecture for Informatica PowerCenter 9.x differ significantly from Informatica PowerCenter 7.x and 8.x. Oracle recommends that you carefully review the Informatica PowerCenter 9.0.1 documentation.

For a summary of installation instructions for installing Informatica PowerCenter 9.0.1 on a single machine in an Oracle BI Applications deployment, see the Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users.

For detailed information about deploying Informatica PowerCenter 9.0.1, refer to the Informatica PowerCenter Installation and Configuration Guide, Informatica Upgrade Guide for PowerCenter 8.1.x, Informatica Upgrade Guide for PowerCenter 8.5.x and 8.6.x, Informatica Administrator Guide, and related documentation. See the Oracle Business Intelligence Applications Release Notes, available on the Oracle Technology Network, for information about how to locate the Informatica documentation.

To upgrade to Informatica PowerCenter 9.0.1 Hotfix 2:

- Perform the pre-upgrade, upgrade, and post-upgrade steps documented in Informatica Upgrade Guide for PowerCenter 8.1.x or Informatica Upgrade Guide for PowerCenter 8.5.x and 8.6.x, depending on which version of Informatica PowerCenter you are upgrading from.

Note the following points:

- The Informatica PowerCenter 9.0.1 installation process includes upgrading your current Informatica Repository to the version 9.0.1 format. This process is necessary so that you will be able to access your current repository using the version 9.0.1 client tools and so that you can perform the procedure Section 8.5, "Upgrading the Informatica Repository."
In Section 8.5, "Upgrading the Informatica Repository," you back up and rename your current repository and then restore the Informatica Repository that is installed during the Oracle BI Applications installation (for example, Oracle_BI_DW_Base.rep). You then copy the folders containing the Oracle BI Applications content for release 7.9.6.4 to your existing repository.

- If you install Informatica PowerCenter 9.0.1 using the installer Upgrade option rather than the Install option, the property $PMRootDir is not updated to the upgraded service version installation directory. You need to configure this property to specify the upgraded service installation directory in order for DAC to be able to locate the Informatica source files.
To configure the $PMRootDir property: launch Informatica Administrator, select the Integration Service from the Navigator, click the Processes tab, and click Edit. Then, enter the appropriate value for $PMRootDir.

8.5 Upgrading the Informatica Repository

Follow this procedure to upgrade the Informatica Repository when you are upgrading the Informatica PowerCenter platform from version 7.x or 8.x to 9.0.1 Hotfix 2. If you have already upgraded to Informatica PowerCenter 9.1, follow the procedure in Section 8.6, "Upgrading the Informatica Repository When You Are Already Running Informatica PowerCenter 9.1."

In this procedure, you will copy the folders containing the Oracle BI Applications 7.9.6.4 content into your current, existing Informatica Repository. The result of this action is an Informatica Repository that contains your customizations along with the new Oracle BI Applications 7.9.6.4 content.

For detailed instructions on backing up and restoring the Informatica Repository, see the topic titled, "Backing Up and Restoring the PowerCenter Repository," in "Chapter 15: PowerCenter Repository Management," in the Informatica PowerCenter Administrator Guide. See the Oracle Business Intelligence Applications Release Notes, available on the Oracle Technology Network, for information about how to locate the Informatica documentation.

To upgrade the Informatica Repository:

1. Make sure you have backed up and renamed your current, existing Informatica Repository.

2. Copy the Oracle_BI_DW_Base.rep file (or Oracle_BI_DW_Teradata.rep for repositories on Teradata databases) from the folder OracleBI\dwrep\Informatica\Repository into the folder <INFA_HOME>\server\infa_shared\Backup.

Note:

The Oracle_BI_DW_Base.rep file is installed in the OracleBI root directory when you run the Oracle BI Applications installer, as described in Section 8.3, "Upgrading Oracle BI Applications."

3. Using Informatica PowerCenter Administrator, create a new Repository Service for the Oracle_BI_DW_Base.rep repository. See "Setup Step: Creating the Informatica Repository Service," in Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users for instructions.

4. Using the Repository Service you created in the step above, restore the Oracle_BI_DW_Base.rep repository into an empty schema. See "Restoring the Prebuilt Informatica Repository for Environments in English" or "Restoring the Prebuilt Informatica Repository on a Non-English Operating System" in Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users for instructions.
This step gives you the Oracle BI Applications 7.9.6.4 Informatica Repository in the Informatica 9.0.1 format.

5. Launch the Informatica PowerCenter Repository Manager, and connect to the repository you restored in step 4 (for example, Oracle_BI_DW_Base.rep), and connect to your current, existing Informatica Repository.
Note: Your current, existing repository should have been updated to the version 9.0.1 format during the Informatica PowerCenter 9.0.1 installation process.

6. In your current, existing repository, make sure all of your customizations are in a "Custom" folder.

7. In your current, existing repository, delete the following folders:

- PLP

- All folders with the prefix SDE_

- SILOS

- SIL_VERT

- UA_SDE

- UA_SIL

Make sure you do not delete the "Custom" folder.

8. Copy the following folders containing the Oracle BI Applications content for release 7.9.6.4 from the newly restored repository (Oracle_BI_DW_Base.rep) into your current, existing repository.

- PLP

- All folders with the prefix SDE_

- SILOS

- SIL_VERT

- UA_SDE

- UA_SIL

This action updates your current, existing repository with the Oracle BI Applications 7.9.6.4 content; this is the repository you will use to run ETL in Oracle BI Applications 7.9.6.4.

The version 7.9.6.4 repository (Oracle_BI_DW_Base.rep) and the Repository Service for this repository are no longer needed.

8.6 Upgrading the Informatica Repository When You Are Already Running Informatica PowerCenter 9.1

If you are upgrading to Oracle BI Applications 7.9.6.4 and previously upgraded Informatica PowerCenter to version 9.1 Hotfix 2, you must first restore the Oracle BI Applications version 7.9.6.4 Informatica Repository using Informatica PowerCenter 9.0.1 Hotfix 2. Then, you can upgrade this repository to the Informatica 9.1 format by pointing to it using Informatica 9.1 client tools. After the Oracle BI Applications 7.9.6.4 Informatica Repository has been upgraded to the Informatica 9.1 format, you can then copy the folders containing the Oracle BI Applications 7.9.6.4 content into your current, existing Informatica Repository. The result of this action is an Informatica Repository that contains your customizations along with the new Oracle BI Applications 7.9.6.4 content.

For detailed instructions on backing up and restoring the Informatica Repository, see the topic titled, "Backing Up and Restoring the PowerCenter Repository," in "Chapter 15: PowerCenter Repository Management," in the Informatica PowerCenter Administrator Guide. See the Oracle Business Intelligence Applications Release Notes, available on the Oracle Technology Network, for information about how to locate the Informatica documentation.

To upgrade the Informatica Repository when already running Informatica PowerCenter 9.1:

1. Make sure you have backed up and renamed your current, existing Informatica Repository.

2. Install Informatica PowerCenter Services version 9.0.1 Hotfix 2. You do not need to install the Informatica PowerCenter Client Tools. See Section 8.4, "Upgrading to Informatica PowerCenter Version 9.0.1 Hotfix 2" for instructions.

3. Copy the Oracle_BI_DW_Base.rep file (or Oracle_BI_DW_Teradata.rep for repositories on Teradata databases) from the folder OracleBI\dwrep\Informatica\Repository into the Informatica PowerCenter 9.0.1 folder <INFA_HOME>\server\infa_shared\Backup.

Note:

The Oracle_BI_DW_Base.rep file is installed in the OracleBI root directory when you run the Oracle BI Applications installer, as described in Section 8.3, "Upgrading Oracle BI Applications."

4. Using Informatica PowerCenter Administrator, create a new Repository Service for the Oracle_BI_DW_Base.rep repository. See "Setup Step: Creating the Informatica Repository Service," in Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users for instructions.

5. Using the Repository Service you created in the step above, restore the Oracle_BI_DW_Base.rep repository into an empty schema. See "Restoring the Prebuilt Informatica Repository for Environments in English" or "Restoring the Prebuilt Informatica Repository on a Non-English Operating System" in Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users for instructions.
This step gives you the Oracle BI Applications 7.9.6.4 Informatica Repository in Informatica 9.0.1 format.

6. Launch the Informatica PowerCenter Repository Manager, and connect to the repository you restored in step 5. When prompted to upgrade the repository to the 9.1 format, do so.

7. In Repository Manger, connect to your current, existing Informatica Repository.

8. In your current, existing repository, make sure all of your customizations are in a "Custom" folder.

9. In your current, existing repository, delete the following folders:

- PLP

- All folders with the prefix SDE_

- SILOS

- SIL_VERT

- UA_SDE

- UA_SIL

Make sure you do not delete the "Custom" folder.

10. Copy the following folders containing the Oracle BI Applications content for release 7.9.6.4 from the newly restored repository (Oracle_BI_DW_Base.rep) into your current, existing repository.

- PLP

- All folders with the prefix SDE_

- SILOS

- SIL_VERT

- UA_SDE

- UA_SIL

This action updates your current, existing repository with the Oracle BI Applications 7.9.6.4 content; this is the repository you will use to run ETL in Oracle BI Applications 7.9.6.4.

The version 7.9.6.4 repository (Oracle_BI_DW_Base.rep) and the Repository Service for this repository are no longer needed.

8.7 Verifying Configurations for Informatica PowerCenter Version 9.0.1 Hotfix 2 to Work With Oracle BI Applications and DAC

Informatica PowerCenter version 9.0.1 Hotfix 2 requires configuration for it to work with Oracle BI Applications and DAC. The configuration settings from your earlier Informatica environment may have been retained when you upgraded to Version 9.0.1 Hotfix 2. Verify or perform the procedures listed below, as documented in the Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users:

- Copying Source Files and Lookup Files

- Setting PowerCenter Integration Services Relaxed Code Page Validation

- Setting PowerCenter Integration Services Custom Properties

- Creating the Repository Administrator User in the Native Security Domain

8.8 Upgrading to and Configuring DAC Version 11g

This section includes instructions for upgrading the DAC platform and repository to version 11g as well as information about configurations you must set or verify.

This section includes the following topics:

- Section 8.8.1, "Installing the DAC Platform and Oracle BI Applications Metadata Repository Files"

- Section 8.8.2, "Configuring the DAC Client and Server to Work With Oracle BI Applications and Informatica"

- Section 8.8.3, "Upgrading the DAC Repository"

8.8.1 Installing the DAC Platform and Oracle BI Applications Metadata Repository Files

The current release of DAC 11g is installed by its own installer and not the Oracle BI Applications installer. For information about the specific release of DAC 11g that is supported for this release of Oracle BI Applications, see System Requirements and Supported Platforms for Oracle Business Intelligence Applications.

After you install DAC 11g, you then need to copy metadata files from the machine hosting Oracle BI Applications to the machines hosting the DAC Client and Server. You then need to import the new metadata into the DAC Repository. For instructions on performing these tasks, see the following sections in the Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users:

- Installing and Setting Up the DAC Platform

Note:

You must perform all of the procedures in this section, including installing JDBC drivers, creating ODBC database connections, and installing pmrep and pmcmd command line programs.

- Installing DAC Metadata Files

- Logging into DAC for the First Time and Importing Metadata into the DAC Repository

Note:

When you perform this step, DAC will prompt you to upgrade the repository. Click Yes. This action will upgrade your repository in the 10g format to the 11g format.

After you complete this procedure, you will have the default DAC Repository for Oracle BI Applications release 7.9.6.4.

8.8.2 Configuring the DAC Client and Server to Work With Oracle BI Applications and Informatica

The DAC Client and Server require configuration to work with Oracle BI Applications and Informatica PowerCenter. The configuration settings from your earlier DAC environment may have been retained when you upgraded to version 11g. Verify or perform the procedures listed below, as documented in the Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users:

- Configuring the DAC Server

- Configuring DAC Integration Settings

- Configuring the SiebelUnicodeDB Custom Property

Note:

This procedure is required only if your source to target data movement configuration is Unicode to Unicode.

- Setting Up DAC to Receive Email Notification

- Additional Configuration Tasks
In this section, perform only the tasks that apply to your environment.

8.8.3 Upgrading the DAC Repository

To upgrade the DAC Repository, you perform a two-step process:

1. You first upgrade the existing DAC Repository from the 10g format to the 11g format. When you log into DAC 11g for the first time, DAC will prompt you to upgrade your repository. Click Yes.
For more information, see "Upgrading to DAC 11g" in Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Data Warehouse Administration Console and "Logging Into DAC for the First Time and Importing Metadata into the DAC Repository" in Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users.

2. You then use the DAC's Upgrade/Merge Wizard to complete the upgrade of your existing DAC Repository.

- If you are upgrading to Oracle BI Applications release 7.9.6.4, and you are remaining on the same version of the transactional source system, you would use the Refresh Base option of the DAC Upgrade/Merge Wizard to complete the upgrade of your existing DAC Repository. For information about how to use the Refresh Base option, see the topic titled, "About the Refresh Base Option," in the chapter "Upgrading, Comparing and Merging DAC Repositories," in the Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Data Warehouse Administration Console.

- If you are upgrading your transactional system, for example, from Oracle EBS release 12 to release 12.2, you would use the Replace Base option of the DAC Upgrade/Merge Wizard to complete the upgrade of your existing DAC Repository. For information about how to use the Replace Base option, see the topic titled, "About the Replace Base Option," in "Upgrading, Comparing and Merging DAC Repositories," in the Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Data Warehouse Administration Console.

The Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Data Warehouse Administration Console is available in the Oracle Business Intelligence Data Warehouse Administration Console Documentation Library on the Oracle Technology Network.

8.9 Upgrading the Data Warehouse Schema and Migrating Data for Non-Teradata Databases

Perform the procedures in this section if you are upgrading from Oracle BI Applications release 7.9.6, 7.9.6.1, 7.9.6.2, or 7.9.6.3 to release 7.9.6.4.

This section includes the following procedures:

- Section 8.9.1, "Upgrading the Data Warehouse Schema From Version 7.9.6 to 7.9.6.1 and Migrating Data for Non-Teradata Databases" (Applicable only if you are using an Oracle database as your data warehouse database.)

- Section 8.9.2, "Upgrading the Data Warehouse Schema From Version 7.9.6.1 to 7.9.6.2 and Migrating Data for Non-Teradata Databases"

- Section 8.9.3, "Upgrading the Data Warehouse Schema From Version 7.9.6.2 to 7.9.6.3 and Migrating Data for Non-Teradata Databases"

- Section 8.9.4, "Upgrading the Data Warehouse Schema From Version 7.9.6.3 to 7.9.6.4 and Migrating Data for Non-Teradata Databases"

If you are currently running Oracle BI Applications release 7.9.6, you need to perform the procedures in Section 8.9.1, Section 8.9.2, Section 8.9.3, and Section 8.9.4.

If you are currently running Oracle BI Applications release 7.9.6.1, you need to perform the procedures in Section 8.9.2, Section 8.9.3, and Section 8.9.4.

If you are currently running Oracle BI Applications release 7.9.6.2, you need to perform the procedures in Section 8.9.3 and Section 8.9.4.

If you are currently running Oracle BI Applications release 7.9.6.3, you need to perform the procedures in Section 8.9.4.

8.9.1 Upgrading the Data Warehouse Schema From Version 7.9.6 to 7.9.6.1 and Migrating Data for Non-Teradata Databases

Follow the procedures in this section to upgrade the data warehouse schema to version 7.9.6.1 and migrate data.

Note:

This procedure is applicable only if you are using an Oracle database for your data warehouse database.

This section includes the following topics:

- Section 8.9.1.1, "Upgrading the Data Warehouse Schema From Version 7.9.6 to 7.9.6.1"

- Section 8.9.1.2, "Migrating Data into the Upgraded Data Warehouse"

- Section 8.9.1.3, "Verifying the Data Migrated Successfully"

8.9.1.1 Upgrading the Data Warehouse Schema From Version 7.9.6 to 7.9.6.1

Follow this procedure to upgrade the data warehouse schema to version 7.9.6.1.

To upgrade the data warehouse schema to version 7.9.6.1:

1. Run the UPGRADE_7961.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

2. Run the 796ORA_TO_7961ORA_UPGRADE_PRE_CTL_SCRIPT.sql. This file is located in the folder OracleBI\dwrep\Upgrade\DbScripts\Oracle.

3. Run the ddl_7961.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

8.9.1.2 Migrating Data into the Upgraded Data Warehouse

Follow this procedure to migrate data into the upgraded data warehouse.

To migrate data into the upgraded data warehouse:

1. Run the 7961_UPGRADE_PRE_DIMENSION_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Oracle.

2. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade repository. For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Upgrade Informatica Repository."

3. Configure the Informatica parameter file 7961_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7961_UPG_PARAMS.txt."

4. If you are upgrading Oracle Financial Analytics, you need to configure specific parameters and update mappings. For more information, see Section A.3.1, "Setting Parameters and Mappings in 796_UPG_PARAMS.txt for Oracle Financial Analytics."

5. If you are using JD Edwards version 8.11 or 8.12, in Informatica Workflow Manager, navigate to the folder UPGRADE_796_to_7961_JDE_811SP1_812 and execute the first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.
If you are using JD Edwards version 9, in Informatica Workflow Manager, navigate to the folder UPGRADE_796_to_7961_JDE_90 and execute first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

6. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep). For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Base Informatica Repository."

7. Run the 7961_UPGRADE_POST_SCRIPT.sql. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Oracle.

8.9.1.3 Verifying the Data Migrated Successfully

Follow this procedure to verify that the data was migrated successfully into the upgraded data warehouse.

To verify the data migrated successfully:

1. Validate the data in the upgraded data warehouse.

2. Check whether any of the Informatica mapping log files stored in the <INFA_HOME>\server\infa_shared\Sesslogs directory indicates errors or failures.

3. Check whether the following scripts that you ran in the SQL client of the database failed or errored out while executing:
7961_UPGRADE_DROP_INDEXES.sql

796ORA_TO_7961ORA_UPGRADE_PRE_CTL_SCRIPT.sql

7961_UPGRADE_PRE_DIMENSION.sql

7961_UPGRADE_POST_SCRIPT.sql

4. Check the log files for the ddl_7961.ctl and Upgrade_7961.ctl scripts, which 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.

Note:

Ignore any error messages that indicate tables or indexes could not be dropped from the database. These error messages are displayed when the specified objects do not exist in the database. This can occur because each source system container holds a subset of all data warehouse tables

5. If the data migration was successful, drop the tables that were created during the upgrade process, such as W_xxxx_x_79x, LKP_xxxx_x and 79x_xxxx_TMP.
This step frees the space occupied by these backup tables.

8.9.2 Upgrading the Data Warehouse Schema From Version 7.9.6.1 to 7.9.6.2 and Migrating Data for Non-Teradata Databases

This section contains the following procedures:

- Section 8.9.2.1, "Upgrading the Data Warehouse Schema to Version 7.9.6.2"

- Section 8.9.2.2, "Migrating Data into the Upgraded Data Warehouse"

- Section 8.9.2.3, "Verifying the Data Migrated Successfully"

- Section 8.9.2.4, "Resetting Refresh Dates"

8.9.2.1 Upgrading the Data Warehouse Schema to Version 7.9.6.2

Follow this procedure to upgrade the data warehouse schema to version 7.9.6.2.

To upgrade the data warehouse schema to version 7.9.6.2:

1. Generate the scripts to drop and create indexes. For instructions, see Section B.1, "Generating Scripts to Drop and Create Indexes for Upgrading to Release 7.9.6.2."

2. Run the script to drop all indexes. For instructions, see Section B.2, "Running the Script to Drop All Indexes for Upgrading to Release 7.9.6.2."

3. If you are using a SQL Server database, run the 7962_UPGRADE_PRE_UPG_CTL_SCRIPT.sql file. This file is located in OracleBI\dwrep\Upgrade\DbScripts\SQLServer.

4. Run the UPGRADE_7962.ctl script. Appendix E, "Using the DDLimp Utility to Run CTL Files."

5. Run the 7962_UPGRADE_PRE_CTL_SCRIPT.sql. This file is located in the folder OracleBI\dwrep\Upgrade\DbScripts\<database type>.

6. Run the DDL_7962.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

8.9.2.2 Migrating Data into the Upgraded Data Warehouse

Follow this procedure to migrate data into the upgraded data warehouse.

To migrate data into the upgraded data warehouse:

1. Run the 7962_UPGRADE_PRE_DIMENSION_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

2. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade repository. For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Upgrade Informatica Repository."

3. Configure the Informatica parameter file 7962_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7962_UPG_PARAMS.txt."

4. Run the script to create ETL indexes. For instructions, see Section B.3, "Running the Scripts to Create ETL and Query Indexes for Upgrading to Release 7.9.6.2."

5. In Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_JDE and execute the first the UPGRADE_DIMENSIONS workflow and then the UPGRADE_FACTS workflow.

6. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep). For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Base Informatica Repository."

7. Run the script to create Query indexes. For instructions, see Section B.3, "Running the Scripts to Create ETL and Query Indexes for Upgrading to Release 7.9.6.2."

8.9.2.3 Verifying the Data Migrated Successfully

Follow this procedure to verify that the data was migrated successfully into the upgraded data warehouse.

To verify the data migrated successfully:

1. Validate the data in the upgraded data warehouse.

2. Check whether any of the Informatica mapping log files stored in the <INFA_HOME>\server\infa_shared\Sesslogs directory indicates errors or failures.

3. Check whether the following scripts that you ran in the SQL client of the database failed or errored out while executing:
dropallindexes.sql

7962_UPGRADE_PRE_CTL_SCRIPT.sql

7962_UPGRADE_PRE_DIMENSION.sql

createETLIndexes.sql

createQueryIndexes.sql

4. Check the log files for the ddl_7962.ctl and Upgrade_7962.ctl scripts, which 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.

Note:

Ignore any error messages that indicate tables or indexes could not be dropped from the database. These error messages are displayed when the specified objects do not exist in the database. This can occur because each source system container holds a subset of all data warehouse tables

5. If the data migration was successful, drop the tables that were created during the upgrade process, such as W_xxxx_x_79x, LKP_xxxx_x and 79x_xxxx_TMP.
This step frees the space occupied by these backup tables.

8.9.2.4 Resetting Refresh Dates

After verifying the data was migrated successfully into the upgraded data warehouse, follow this procedure to reset refresh dates.

1. If you are using JD Edwards version 8.11 or 8.12, in Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_JDE_811SP1_812 and execute the RESET_DAC_REFRESH_DATES workflow.
If you are using JD Edwards version 9, in Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_JDE90 and execute the RESET_DAC_REFRESH_DATES workflow.

2. Locate the 7962_RESET_REFRESH_DATES.txt file in the folder OracleBI\dwrep\Upgrade\Informatica\SrcFiles.
In the next step, you will reset the refresh dates to NULL for the tables listed in 7962_RESET_REFRESH_DATES.txt.

3. In DAC, do the following:

1. Navigate to the Setup view, and click the Physical Data Sources tab.

2. In the top pane list, select DataWarehouse. (If you customized the name of the connection for the data warehouse, select the appropriate connection for the data warehouse database.)

3. Click the Refresh Dates subtab (in the lower pane).

4. Query for the tables listed in the 7962_RESET_REFRESH_DATES.txt file, and, for each table, set the value in the Refresh Date column to NULL

4. Once the data migration steps above are complete, you can delete the Upgrade repository to avoid any accidental use or confusion.

1. In the Informatica Administrator, select the Upgrade repository service.

2. In the General Properties area of the Properties tab, click Edit.

3. Make sure the operating mode of the repository service is set to Exclusive.

4. Click OK.

5. Choose Actions, and then click Delete Contents.

6. In the Delete contents for <repository name> dialog, enter the repository username and password, and then click OK.

8.9.3 Upgrading the Data Warehouse Schema From Version 7.9.6.2 to 7.9.6.3 and Migrating Data for Non-Teradata Databases

Perform the procedures in this section to upgrade from Oracle BI Applications release 7.9.6.2 to 7.9.6.3.

This section contains the following procedures:

- Section 8.9.3.1, "Upgrading the Data Warehouse Schema to Version 7.9.6.3"

- Section 8.9.3.2, "Migrating Data into the Upgraded Data Warehouse"

- Section 8.9.3.3, "Verifying the Data Migrated Successfully"

8.9.3.1 Upgrading the Data Warehouse Schema to Version 7.9.6.3

Follow this procedure to upgrade the data warehouse schema to version 7.9.6.3.

To upgrade the data warehouse schema to version 7.9.6.3:

1. Generate the scripts to drop and create query indexes. For instructions, see Section B.4, "Generating Scripts to Drop and Create Query Indexes for Upgrading to Release 7.9.6.3."

2. Run the script to drop query indexes. For instructions, see Section B.5, "Running the Scripts to Drop and Create Query Indexes for Upgrading to Release 7.9.6.3."
Note: You must drop the query indexes before running the scripts to upgrade the schema.

3. If you are using a SQL Server database, run the 7963_UPGRADE_PRE_UPG_CTL_SCRIPT.sql file. This file is located in OracleBI\dwrep\Upgrade\DbScripts\SQLServer.

4. Run the UPGRADE_7963.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

5. Run the 7963_UPGRADE_PRE_CTL_SCRIPT.sql. This file is located in the folder OracleBI\dwrep\Upgrade\DbScripts\<database type>.

6. Run the DDL_7963.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files.".

8.9.3.2 Migrating Data into the Upgraded Data Warehouse

Follow this procedure to migrate data into the upgraded data warehouse.

To migrate data into the upgraded data warehouse:

1. Run the 7963_UPGRADE_PRE_DIMENSION_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

2. Run the 7963_UPGRADE_DROP_ETLINDICES.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

3. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade repository. For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Upgrade Informatica Repository."

4. Configure the Informatica parameter file 7963_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7963_UPG_PARAMS.txt."

5. If you are upgrading Oracle Financial Analytics, set the parameters as specified in Appendix A, "Setting Parameters for All Source Systems."

6. If you are using JD Edwards 8.11 or 8.12, in Informatica Workflow Manager, navigate to the folder UPGRADE_7962_to_7963_JDE_811SP1_812 and execute the UPGRADE_FACTS workflow.
If you are using JD Edwards 9, in Informatica Workflow Manager, navigate to the folder UPGRADE_7962_to_7963_JDE90 and execute the UPGRADE_FACTS workflow.

7. Upgrade geography-related attributes if necessary for your environment:

1. Determine whether a geography-related upgrade is necessary by executing the following query:

SELECT COUNT(1) as row_count,'0' as X_CUSTOM FROM W_GEO_D_7963 WHERE COUNTRY LIKE '% 'OR COUNTRY LIKE ' %'OR STATE_PROV LIKE '% 'OR STATE_PROV LIKE ' %'OR CITY LIKE '% 'OR CITY LIKE ' %'OR ZIPCODE LIKE '% 'OR ZIPCODE LIKE ' %'

2. If the query returns a count greater than zero, run the 7963_UPGRADE_POST_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.
If the query returns a count of zero, you do not need to run the 7963_UPGRADE_POST_SCRIPT.sql script.

8. Run the 7963_UPGRADE_CREATE_ETLINDICES.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

9. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep). For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Base Informatica Repository."

10. Run the createQueryIndices script. For instructions, see Section B.5, "Running the Scripts to Drop and Create Query Indexes for Upgrading to Release 7.9.6.3."

8.9.3.3 Verifying the Data Migrated Successfully

Follow this procedure to verify that the data was migrated successfully into the upgraded data warehouse.

To verify the data migrated successfully:

1. Validate the data in the upgraded data warehouse.

2. Check whether any of the Informatica mapping log files stored in the <INFA_HOME>\server\infa_shared\Sesslogs directory indicates errors or failures.

3. Check whether the following scripts that you ran in the SQL client of the database failed or errored out while executing:
7963_UPGRADE_PRE_CTL_SCRIPT.sql

7963_UPGRADE_PRE_DIMENSION.sql

7963_UPGRADE_DROP_ETLINDICES.sql

7963_UPGRADE CREATE_ETLINDICES.sql

dropQueryIndices.sql

createQueryIndices.sql

4. Check the log files for the ddl_7963.ctl and Upgrade_7963.ctl scripts, which 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.

Note:

Ignore any error messages that indicate tables or indexes could not be dropped from the database. These error messages are displayed when the specified objects do not exist in the database. This can occur because each source system container holds a subset of all data warehouse tables

5. If the data migration was successful, drop the tables that were created during the upgrade process, such as W_xxxx_x_79x, LKP_xxxx_x and 79x_xxxx_TMP.
This step frees the space occupied by these backup tables.

6. Once the data migration steps above are complete, you can delete the Upgrade repository to avoid any accidental use or confusion.

1. In the Informatica Administrator, select the Upgrade repository service.

2. In the General Properties area of the Properties tab, click Edit.

3. Make sure the operating mode of the repository service is set to Exclusive.

4. Click OK.

5. Choose Actions, and then click Delete Contents.

6. In the Delete contents for <repository name> dialog, enter the repository username and password, and then click OK.

8.9.4 Upgrading the Data Warehouse Schema From Version 7.9.6.3 to 7.9.6.4 and Migrating Data for Non-Teradata Databases

Perform the procedures in this section to upgrade from Oracle BI Applications release 7.9.6.3 to 7.9.6.4.

This section contains the following procedures:

- Section 8.9.4.1, "Upgrading the Data Warehouse Schema to Version 7.9.6.4"

- Section 8.9.4.2, "Migrating Data into the Upgraded Data Warehouse"

- Section 8.9.4.3, "Verifying the Data Migrated Successfully"

8.9.4.1 Upgrading the Data Warehouse Schema to Version 7.9.6.4

Follow this procedure to upgrade the data warehouse schema to version 7.9.6.4.

To upgrade the data warehouse schema to version 7.9.6.4:

1. If you are using a DB2 database, run siebproc.sql. This file is located in OracleBI\dwrep\siebproc\db2udb.

2. Generate the scripts to drop and create query indexes. For instructions, see Section B.6, "Generating Scripts to Drop and Create Query and ETL Indexes for Upgrading to Release 7.9.6.4."

3. Run the script to drop query indexes. For instructions, see Section B.7, "Running the Scripts to Drop and Create Query Indexes for Upgrading to Release 7.9.6.4."
Note: You must drop the query indexes before running the scripts to upgrade the schema.

4. If you are using a SQL Server database, run the 7964_UPGRADE_PRE_UPG_CTL_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\SQLServer.

5. Run the UPGRADE_7964.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

6. Run the 7964_UPGRADE_PRE_CTL_SCRIPT.sql script. This file is located in the folder OracleBI\dwrep\Upgrade\DbScripts\<database type>.

7. Run the DDL_7964.ctl script. For instructions, see Appendix E, "Using the DDLimp Utility to Run CTL Files."

8.9.4.2 Migrating Data into the Upgraded Data Warehouse

Follow this procedure to migrate data into the upgraded data warehouse.

To migrate data into the upgraded data warehouse:

1. Run the 7964_UPGRADE_PRE_DIMENSION_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

2. Run the script to drop ETL indexes. For instructions, see Section B.8, "Running the Scripts to Drop and Create ETL Indexes for Upgrading to Release 7.9.6.4."

3. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade repository. For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Upgrade Informatica Repository."

4. Configure the Informatica parameter file 7964_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7964_UPG_PARAMS.txt."

5. If you are using JD Edwards 8.11 or 8.12, in Informatica Workflow Manager, navigate to the folder UPGRADE_7963_to_7964_JDE_811SP1_812 and execute the UPGRADE_FACTS workflow.
If you are using JD Edwards 9, in Informatica Workflow Manager, navigate to the folder UPGRADE_7963_to_7964_JDE90 and execute the UPGRADE_FACTS workflow.

6. Run the 7964_UPGRADE_POST_SCRIPT.sql. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

7. Run the script to drop ETL indexes. For instructions, see Section B.8, "Running the Scripts to Drop and Create ETL Indexes for Upgrading to Release 7.9.6.4."

8. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep). For instructions, see Appendix D, "Running reset_infa_seq_gen.bat on Base Informatica Repository."

8.9.4.3 Verifying the Data Migrated Successfully

Follow this procedure to verify that the data was migrated successfully into the upgraded data warehouse.

To verify the data migrated successfully:

1. Validate the data in the upgraded data warehouse.

2. Check whether any of the Informatica mapping log files stored in the <INFA_HOME>\server\infa_shared\Sesslogs directory indicates errors or failures.

3. Check whether the following scripts that you ran in the SQL client of the database failed or errored out while executing:
7964_UPGRADE_PRE_CTL_SCRIPT.sql

7964_UPGRADE_PRE_DIMENSION.sql

dropEtlIndices.sql

createEtlIndices.sql

dropQueryIndices.sql

createQueryIndices.sql

4. Check the log files for the ddl_7964.ctl and Upgrade_7964.ctl scripts, which 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.

Note:

Ignore any error messages that indicate tables or indexes could not be dropped from the database. These error messages are displayed when the specified objects do not exist in the database. This can occur because each source system container holds a subset of all data warehouse tables

5. If the data migration was successful, drop the tables that were created during the upgrade process, such as W_xxxx_x_79x, LKP_xxxx_x and 79x_xxxx_TMP.
This step frees the space occupied by these backup tables.

6. Once the data migration steps above are complete, you can delete the Upgrade repository to avoid any accidental use or confusion.

1. In the Informatica Administrator, select the Upgrade repository service.

2. In the General Properties area of the Properties tab, click Edit.

3. Make sure the operating mode of the repository service is set to Exclusive.

4. Click OK.

5. Choose Actions, and then click Delete Contents.

6. In the Delete contents for <repository name> dialog, enter the repository username and password, and then click OK.

8.10 Upgrading the Data Warehouse Schema and Migrating Data for Teradata Databases

If your data warehouse database platform is Teradata, follow the procedures in this section to upgrade from Oracle BI Applications version 7.9.6.1, 7.9.6.2, and 7.9.6.3 to version 7.9.6.4.

This section includes the following topics:

- Section 8.10.1, "Upgrading Oracle BI Applications From Version 7.9.6.1 to 7.9.6.4"

- Section 8.10.2, "Upgrading Oracle BI Applications From Version 7.9.6.2 to 7.9.6.4"

- Section 8.10.3, "Upgrading Oracle BI Applications From Version 7.9.6.3 to 7.9.6.4"

8.10.1 Upgrading Oracle BI Applications From Version 7.9.6.1 to 7.9.6.4

Follow this procedure to upgrade from Oracle BI Applications version 7.9.6.1 to version 7.9.6.2 if your data warehouse database platform is Teradata.

To upgrade the data warehouse schema and migrate data for a Teradata database:

1. Execute the following scripts:

- 7962_UPGRADE_TMP_TABLES.sql

- 7963_UPGRADE_TMP_TABLES.sql

- 7963_UPGRADE_TMP_TABLES.sql

- 7964_UPGRADE_TMP_TABLES.sql

1. Open the SQL client for your database type.

2. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.

3. Open the <version>_UPGRADE_TMP_TABLES.sql file, and copy the contents into the SQL client.

4. Execute the script.

2. The teradata.missing.defaults.properties file contains global default column values for data warehouse tables with NOT NULL columns for which default values are not specified in DAC. You can change the default values specified in the teradata.missing.defaults.properties file to match your environment. The file is located in \bifoundation\dac\conf\sqlgen\sql\teradata.

3. Generate upgrade scripts from DAC.

1. Log into DAC.

2. From the menu bar, select Tools, then ETL Management, and then Configure.

3. In the Sources dialog box, select Teradata as the target data warehouse database platform, and select the appropriate source data warehouse database platform.
The Configuration tab of the Data Warehouse Configuration Wizard is active.

4. Select "Generate upgrade statements for Data Warehouse Tables," and click Next.
The Data Warehouse SQL tab is active.

5. Do the following:
- Select the appropriate physical data source name for the Teradata database.

- In the container field, enter a custom container name for which you want to generate upgrade scripts. Alternatively, leave the field blank to generate upgrade scripts for all containers.

The Data Warehouse Configuration Wizard generates the following files and stores them in \bifoundation\DAC\conf\sqlgen\sql\teradata:

upgrade-regular.sql. This file contains scripts that DAC has verified are necessary to upgrade the data warehouse schema. The scripts handle new or altered tables and columns. For example, they may increase the size of simple data types or change a column from null to not null.

upgrade-questionable.sql. This file contains scripts that DAC suggests may be required to upgrade the data warehouse schema. These scripts are intended to be an aid in determining upgrade requirements and must be reviewed by a Teradata DBA and corrected if necessary.

upgradedwtables_sql.log. This file is the log file that corresponds to the upgrade-regular.sql file. It is for information purposes only.

upgrade-issues.log. This file is the log file that corresponds to the file upgrade-questionable.sql. It is for information purposes only.

6. Open the upgrade-regular.sql and upgrade-questionable.sql files, and search for the following statement to locate columns that have been added or changed.
ALTER TABLE <Table Name> ADD <Column Name><attributes>;

7. For all columns with the ADD command, check to see whether any columns exist already, and if they do, check whether they have STATISTICS defined on them.

8. For all columns that have STATISTICS defined on them, back up the column definition and then drop the STATISTICS.

9. Execute the scripts in the upgrade-regular.sql file.

10. Review the scripts in the upgrade-questionable.sql file. Edit the scripts as needed, and execute them.

11. Recreate STATISTICS on any column on which they were dropped.

4. Execute the following scripts:

- 7962_UPDATE_DEFAULTS.sql

- 7963_UPDATE_DEFAULTS.sql

- 7964_UPDATE_DEFAULTS.sql

5. Execute the 7962_Backup_Tables.sql script.

6. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

7. Configure the Informatica parameter file 7962_UPG_PARAMStxt. For instructions, see Appendix A, "Setting Parameters in 7962_UPG_PARAMS.txt."

8. If you are using JD Edwards version 8.11 or 8.12, in Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_JDE_811SP1_812 and execute the following workflows in the order specified:

- UPGRADE_DIMENSIONS

- UPGRADE_FACTS

- RESET_DAC_REFRESH_DATES

9. If you are using JD Edwards version 9, in Informatica Workflow Manager, navigate to the folder UPGRADE_7961_to_7962_JDE90 and execute the following workflows in the order specified:

- UPGRADE_DIMENSIONS

- UPGRADE_FACTS

- RESET_DAC_REFRESH_DATES

10. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

11. Locate the 7962_RESET_REFRESH_DATES.txt file in the folder OracleBI\dwrep\Upgrade\Informatica\SrcFiles.
In the next step, you will reset the refresh dates to NULL for the tables listed in 7962_RESET_REFRESH_DATES.txt.

12. In DAC, do the following:

1. Navigate to the Setup view, and click the Physical Data Sources tab.

2. In the top pane list, select DataWarehouse. (If you customized the name of the connection for the data warehouse, select the appropriate connection for the data warehouse database.)

3. Click the Refresh Dates subtab (in the lower pane).

4. Query for the tables listed in the 7962_RESET_REFRESH_DATES.txt file, and, for each table, set the value in the Refresh Date column to NULL

13. Execute the 7963_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

14. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

15. Configure the Informatica parameter file 7963_UPG_PARAMS.txt. For instructions, see Section A.1.8, "Setting Parameters in 7963_UPG_PARAMS.txt."

16. If you are upgrading Oracle Financial Analytics, set the parameters as specified in Appendix A, "Setting Parameters for All Source Systems."

17. If you are using JD Edwards 8.11 or 8.12, in Informatica Workflow Manager, navigate to the folder UPGRADE_7962_to_7963_JDE_811SP1_812 and execute the UPGRADE_FACTS workflow.
If you are using JD Edwards 9, in Informatica Workflow Manager, navigate to the folder UPGRADE_7962_to_7963_JDE90 and execute the UPGRADE_FACTS workflow.

18. Upgrade geography-related attributes if necessary for your environment:

1. Determine whether a geography-related upgrade is necessary by executing the following query:

SELECT COUNT(1) as row_count,'0' as X_CUSTOM FROM W_GEO_D_7963 WHERE COUNTRY LIKE '% 'OR COUNTRY LIKE ' %'OR STATE_PROV LIKE '% 'OR STATE_PROV LIKE ' %'OR CITY LIKE '% 'OR CITY LIKE ' %'OR ZIPCODE LIKE '% 'OR ZIPCODE LIKE ' %'

2. If the query returns a count greater than zero, run the 7963_UPGRADE_POST_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.
If the query returns a count of zero, you do not need to run the 7963_UPGRADE_POST_SCRIPT.sql script.

19. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

20. Execute the 7964_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

21. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

22. Configure the Informatica parameter file 7964_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7964_UPG_PARAMS.txt."

23. If you are using JD Edwards 8.11 or 8.12, in Informatica Workflow Manager, navigate to the folder UPGRADE_7963_to_7964_JDE_811SP1_812 and execute the UPGRADE_FACTS workflow.
If you are using JD Edwards 9, in Informatica Workflow Manager, navigate to the folder UPGRADE_7963_to_7964_JDE90 and execute the UPGRADE_FACTS workflow.

24. Run the 7964_UPGRADE_POST_SCRIPT.sql. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

25. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

26. Once the data migration steps above are complete, you can delete the Upgrade repository to avoid any accidental use or confusion.

1. In the Informatica Administrator, select the Upgrade repository service.

2. In the General Properties area of the Properties tab, click Edit.

3. Make sure the operating mode of the repository service is set to Exclusive.

4. Click OK.

5. Choose Actions, and then click Delete Contents.

6. In the Delete contents for <repository name> dialog, enter the repository username and password, and then click OK.

8.10.2 Upgrading Oracle BI Applications From Version 7.9.6.2 to 7.9.6.4

Follow this procedure to upgrade from Oracle BI Applications version 7.9.6.2 to version 7.9.6.3 if your data warehouse database platform is Teradata.

To upgrade the data warehouse schema and migrate data for a Teradata database:

1. Execute the following scripts:

- 7963_UPGRADE_TMP_TABLES.sql

- 7964_UPGRADE_TMP_TABLES.sql

1. Open the SQL client for your database type.

2. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.

3. Open the <version>_UPGRADE_TMP_TABLES.sql file, and copy the contents into the SQL client.

4. Execute the script.

2. The teradata.missing.defaults.properties file contains global default column values for data warehouse tables with NOT NULL columns for which default values are not specified in DAC. You can change the default values specified in the teradata.missing.defaults.properties file to match your environment. The file is located in \bifoundation\dac\conf\sqlgen\sql\teradata.

3. Generate upgrade scripts from DAC.

1. Log into DAC.

2. From the menu bar, select Tools, then ETL Management, and then Configure.

3. In the Sources dialog box, select Teradata as the target data warehouse database platform, and select the appropriate source data warehouse database platform.
The Configuration tab of the Data Warehouse Configuration Wizard is active.

4. Select "Generate upgrade statements for Data Warehouse Tables," and click Next.
The Data Warehouse SQL tab is active.

5. Do the following:
- Select the appropriate physical data source name for the Teradata database.

- In the container field, enter a custom container name for which you want to generate upgrade scripts. Alternatively, leave the field blank to generate upgrade scripts for all containers.

The Data Warehouse Configuration Wizard generates the following files and stores them in \bifoundation\DAC\conf\sqlgen\sql\teradata:

upgrade-regular.sql. This file contains scripts that DAC has verified are necessary to upgrade the data warehouse schema. The scripts handle new or altered tables and columns. For example, they may increase the size of simple data types or change a column from null to not null.

upgrade-questionable.sql. This file contains scripts that DAC suggests may be required to upgrade the data warehouse schema. These scripts are intended to be an aid in determining upgrade requirements and must be reviewed by a Teradata DBA and corrected if necessary.

upgradedwtables_sql.log. This file is the log file that corresponds to the upgrade-regular.sql file. It is for information purposes only.

upgrade-issues.log. This file is the log file that corresponds to the file upgrade-questionable.sql. It is for information purposes only.

6. Open the upgrade-regular.sql and upgrade-questionable.sql files, and search for the following statement to locate columns that have been added or changed.
ALTER TABLE <Table Name> ADD <Column Name><attributes>;

7. For all columns with the ADD command, check to see whether any columns exist already, and if they do, check whether they have STATISTICS defined on them.

8. For all columns that have STATISTICS defined on them, back up the column definition and then drop the STATISTICS.

9. Execute the scripts in the upgrade-regular.sql file.

10. Review the scripts in the upgrade-questionable.sql file. Edit the scripts as needed, and execute them.

11. Recreate STATISTICS on any column on which they were dropped.

4. Execute the following scripts:

- 7963_UPDATE_DEFAULTS.sql

- 7964_UPDATE_DEFAULTS.sql

5. Execute the 7963_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

6. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

7. Configure the Informatica parameter file 7963_UPG_PARAMS.txt. For instructions, see Section A.1.8, "Setting Parameters in 7963_UPG_PARAMS.txt."

8. If you are upgrading Oracle Financial Analytics, set the parameters as specified in Appendix A, "Setting Parameters for All Source Systems."

9. If you are using JD Edwards 8.11 or 8.12, in Informatica Workflow Manager, navigate to the folder UPGRADE_7962_to_7963_JDE_811SP1_812 and execute the UPGRADE_FACTS workflow.
If you are using JD Edwards 9, in Informatica Workflow Manager, navigate to the folder UPGRADE_7962_to_7963_JDE90 and execute the UPGRADE_FACTS workflow.

10. Upgrade geography-related attributes if necessary for your environment:

1. Determine whether a geography-related upgrade is necessary by executing the following query:

SELECT COUNT(1) as row_count,'0' as X_CUSTOM FROM W_GEO_D_7963 WHERE COUNTRY LIKE '% 'OR COUNTRY LIKE ' %'OR STATE_PROV LIKE '% 'OR STATE_PROV LIKE ' %'OR CITY LIKE '% 'OR CITY LIKE ' %'OR ZIPCODE LIKE '% 'OR ZIPCODE LIKE ' %'

2. If the query returns a count greater than zero, run the 7963_UPGRADE_POST_SCRIPT.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.
If the query returns a count of zero, you do not need to run the 7963_UPGRADE_POST_SCRIPT.sql script.

11. Locate the 7962_RESET_REFRESH_DATES.txt file in the folder OracleBI\dwrep\Upgrade\Informatica\SrcFiles.
In the next step, you will reset the refresh dates to NULL for the tables listed in 7962_RESET_REFRESH_DATES.txt.

12. In DAC, do the following:

1. Navigate to the Setup view, and click the Physical Data Sources tab.

2. In the top pane list, select DataWarehouse. (If you customized the name of the connection for the data warehouse, select the appropriate connection for the data warehouse database.)

3. Click the Refresh Dates subtab (in the lower pane).

4. Query for the tables listed in the 7962_RESET_REFRESH_DATES.txt file, and, for each table, set the value in the Refresh Date column to NULL

13. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

14. Execute the 7964_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

15. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

16. Configure the Informatica parameter file 7964_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7964_UPG_PARAMS.txt."

17. If you are using JD Edwards 8.11 or 8.12, in Informatica Workflow Manager, navigate to the folder UPGRADE_7963_to_7964_JDE_811SP1_812 and execute the UPGRADE_FACTS workflow.
If you are using JD Edwards 9, in Informatica Workflow Manager, navigate to the folder UPGRADE_7963_to_7964_JDE90 and execute the UPGRADE_FACTS workflow.

18. Run the 7964_UPGRADE_POST_SCRIPT.sql. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

19. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

20. Once the data migration steps above are complete, you can delete the Upgrade repository to avoid any accidental use or confusion.

1. In the Informatica Administrator, select the Upgrade repository service.

2. In the General Properties area of the Properties tab, click Edit.

3. Make sure the operating mode of the repository service is set to Exclusive.

4. Click OK.

5. Choose Actions, and then click Delete Contents.

6. In the Delete contents for <repository name> dialog, enter the repository username and password, and then click OK.

8.10.3 Upgrading Oracle BI Applications From Version 7.9.6.3 to 7.9.6.4

Follow this procedure to upgrade from Oracle Business Applications version 7.9.6.3 to version 7.9.6.4 if your data warehouse database platform is Teradata.

To upgrade the data warehouse schema and migrate data for a Teradata database:

1. Execute the 7964_UPGRADE_TMP_TABLES.sql script.

1. Open the SQL client for your database type.

2. Navigate to the folder OracleBI\dwrep\Upgrade\DbScripts\Teradata.

3. Open the 7964_UPGRADE_TMP_TABLES.sql file, and copy the contents into the SQL client.

4. Execute the script.

2. The teradata.missing.defaults.properties file contains global default column values for data warehouse tables with NOT NULL columns for which default values are not specified in DAC. You can change the default values specified in the teradata.missing.defaults.properties file to match your environment. The file is located in \bifoundation\dac\conf\sqlgen\sql\teradata.

3. Generate upgrade scripts from DAC.

1. Log into DAC.

2. From the menu bar, select Tools, then ETL Management, and then Configure.

3. In the Sources dialog box, select Teradata as the target data warehouse database platform, and select the appropriate source data warehouse database platform.
The Configuration tab of the Data Warehouse Configuration Wizard is active.

4. Select "Generate upgrade statements for Data Warehouse Tables," and click Next.
The Data Warehouse SQL tab is active.

5. Do the following:
- Select the appropriate physical data source name for the Teradata database.

- In the container field, enter a custom container name for which you want to generate upgrade scripts. Alternatively, leave the field blank to generate upgrade scripts for all containers.

The Data Warehouse Configuration Wizard generates the following files and stores them in \bifoundation\DAC\conf\sqlgen\sql\teradata:

upgrade-regular.sql. This file contains scripts that DAC has verified are necessary to upgrade the data warehouse schema. The scripts handle new or altered tables and columns. For example, they may increase the size of simple data types or change a column from null to not null.

upgrade-questionable.sql. This file contains scripts that DAC suggests may be required to upgrade the data warehouse schema. These scripts are intended to be an aid in determining upgrade requirements and must be reviewed by a Teradata DBA and corrected if necessary.

upgradedwtables_sql.log. This file is the log file that corresponds to the upgrade-regular.sql file. It is for information purposes only.

upgrade-issues.log. This file is the log file that corresponds to the file upgrade-questionable.sql. It is for information purposes only.

6. Open the upgrade-regular.sql and upgrade-questionable.sql files, and search for the following statement to locate columns that have been added or changed.
ALTER TABLE <Table Name> ADD <Column Name><attributes>;

7. For all columns with the ADD command, check to see whether any columns exist already, and if they do, check whether they have STATISTICS defined on them.

8. For all columns that have STATISTICS defined on them, back up the column definition and then drop the STATISTICS.

9. Execute the scripts in the upgrade-regular.sql file.

10. Review the scripts in the upgrade-questionable.sql file. Edit the scripts as needed, and execute them.

11. Recreate STATISTICS on any column on which they were dropped.

4. Execute the 7964_UPDATE_DEFAULTS.sql scripts.

5. Execute the 7964_Backup_Tables.sql script. This file is located in OracleBI\dwrep\Upgrade\DbScripts\Teradata.

6. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server."

7. Configure the Informatica parameter file 7964_UPG_PARAMS.txt. For instructions, see Appendix A, "Setting Parameters in 7964_UPG_PARAMS.txt."

8. If you are using JD Edwards 8.11 or 8.12, in Informatica Workflow Manager, navigate to the folder UPGRADE_7963_to_7964_JDE_811SP1_812 and execute the UPGRADE_FACTS workflow.
If you are using JD Edwards 9, in Informatica Workflow Manager, navigate to the folder UPGRADE_7963_to_7964_JDE90 and execute the UPGRADE_FACTS workflow.

9. Run the 7964_UPGRADE_POST_SCRIPT.sql. This file is located in OracleBI\dwrep\Upgrade\DbScripts\<database type>.

10. Use the reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

- If your Informatica Repository runs on an Oracle database, for instructions, see Appendix D, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle."

- If your Informatica Repository runs on an MSSQL Server database, for instructions, see Appendix D, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server."

11. Once the data migration steps above are complete, you can delete the Upgrade repository to avoid any accidental use or confusion.

1. In the Informatica Administrator, select the Upgrade repository service.

2. In the General Properties area of the Properties tab, click Edit.

3. Make sure the operating mode of the repository service is set to Exclusive.

4. Click OK.

5. Choose Actions, and then click Delete Contents.

6. In the Delete contents for <repository name> dialog, enter the repository username and password, and then click OK.

8.11 Localizing the Policy Store

The Oracle BI Applications 7.9.6.4 installer contains different policy stores for different languages. The default policy store that is deployed during the installation is in English. If you want to configure the policy store for any of the other available languages, perform the procedure below.

To configure the policy store for languages other than English:

1. Stop the Oracle BI Services.

2. Copy the system-jazn-data_<LN>.xml file from $ORACLE_BI_HOME\biapps\admin\provisioning\localization\ to $DOMAIN_HOME\config\fmwconfig\.
For example, to implement the policy store for French, you would copy the file system-jazn-data_fr.xml into the \fmwconfig directory.

3. Back up the existing system-jazn-data.xml file in $DOMAIN_HOME\config\fmwconfig\.

4. Rename $DOMAIN_HOME\config\fmwconfig\system-jazn-data_<LN>.xml to system-jazn-data.xml.

5. Start Oracle BI Services.

8.12 Importing the Oracle BI Applications Version 7.9.6.4 LDIF File Into the Embedded LDAP Server

In this procedure, you will import the standard (out-of-the-box) Oracle BI Applications version 7.9.6.4 LDIF file into the WebLogic Server embedded LDAP server.

To import the Oracle BI Applications version 7.9.6.4 LDIF file:

1. Log in to the WebLogic Server Administration Console using the URL http://<host name>:7001/console.

2. Select the name of the security realm into which the LDIF file is to be imported (for example, myrealm).

3. Select Providers and then the type of provider into which the LDIF file is to be imported (for example, Providers, and then Authentication).

4. Select the security provider in which the LDIF file is to be imported and select Migration, and then select Import.

5. Click Save.

8.13 Upgrading the Oracle BI Repository and Presentation Catalog to the Oracle BI Enterprise Edition 11g Version

Use the Oracle BI Enterprise Edition Upgrade Assistant to upgrade the following repositories and presentation catalog from the Oracle BI Enterprise Edition 10g format to the 11g format:

- The standard (out-of-the-box) Oracle BI Repository. This repository is the one that you originally received from Oracle as part of your current Oracle BI Applications installation (the version from which you are upgrading). Standard repositories from previous releases are available in the installation folder $ORACLE_BI_HOME\biapps\upgrade.

- The Oracle BI Repository you are currently using (the repository deployed in production).

- The Presentation Catalog you are currently using (the catalog deployed in production).

For instructions on using the Upgrade Assistant, see Oracle Fusion Middleware Upgrade Guide for Oracle Business Intelligence.

Note:

Your current policy store will be merged with the Oracle BI Applications release 7.9.6.4 policy store while upgrading the Oracle BI repository from the 10g format to the 11g format. The final policy store will be the super set of Oracle BI Applications release 7.9.6.4 policy store and the custom and current policy information from the 10g repository.

Also, your current users and groups from the repository will be merged with the Oracle BI Applications release 7.9.6.4 identity store while upgrading the Oracle BI repository from the 10g format to the 11g format. The final identity store will be the super set of the Oracle BI Applications release 7.9.6.4 identity store and the identity store information (users and groups) from the 10g repository.

If you require the policy store to be in a language other than English, perform the steps in Section 8.11, "Localizing the Policy Store."

8.14 Merging Oracle BI Applications Version 7.9.6.4 Repository With Customer Repository

Note:

Before you begin this procedure, you must have already upgraded the Oracle BI repository you are currently using and the standard (out-of-the-box) Oracle BI repository version 7.9.x (the version from which you are upgrading) to the Oracle BI Enterprise Edition 11g format. For more information, see Section 8.13, "Upgrading the Oracle BI Repository and Presentation Catalog to the Oracle BI Enterprise Edition 11g Version."

This process merges your customizations of a prior release of the Oracle BI repository with the new release 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 8.14.1, "Preparing for the Oracle BI Repository Upgrade"

- Section 8.14.2, "Equalizing the Oracle BI Repositories"

- Section 8.14.3, "Comparing the Oracle BI Repositories"

- Section 8.14.4, "Merging the Oracle BI Repositories"

The tasks in this section refer to multiple releases of the Oracle BI repository. Table 8-1 provides the names and descriptions of the repositories used in the examples in this section.

Table 8-1 Names of Analytics Repositories used in Examples

Name of Repository

Description

OracleBIAnalyticsApps_79x.rpd

The standard Oracle BI repository for the version you are upgrading from.

Note: Standard repositories from previous releases are available in the folder $ORACLE_BI_HOME\biapps\upgrade.

OracleBIAnalyticsApps.rpd

The standard Oracle BI repository for the version you are upgrading to.

Customer_OracleBIAnalyticsApps.rpd

The Oracle BI 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.

8.14.1 Preparing for the Oracle BI Repository Upgrade

Follow this procedure to prepare for the repository upgrade.

To prepare for the Analytics repository upgrade:

1. Set up a directory for the merge process, such as \OracleBIUpgrade, and create the following subfolders:

- Original

- AfterEqualize

- AfterMerge

- AfterManualWork

- AfterRegressions

2. Copy the following repositories to the folder \OracleBIUpgrade\Original:

- The standard repository that you upgraded to the 11g format in Section 8.13, "Upgrading the Oracle BI Repository and Presentation Catalog to the Oracle BI Enterprise Edition 11g Version" (for example, OracleBIAnalyticsApps_79x.rpd).

- The production repository that you also upgraded to the 11g format in Section 8.13 (for example, Customer_OracleBIAnalyticsApps.rpd.

- The Oracle BI repository from the latest installation (for example, OracleBIAnalyticsApps.rpd)

If, in your current environment, you are running Oracle BI Applications for one or more modules using a Oracle BI repository in which you extracted the corresponding projects for the modules from the standard Oracle BI repository file you received from the previous release, you need to extract the same projects from the OracleBIAnalyticsApps_79x.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 Oracle BI 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 OracleBIAnalyticsApps_79x.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.

8.14.2 Equalizing the Oracle BI Repositories

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, OracleBIAnalyticsApps_79x.rpd, OracleBIAnalyticsApps.rpd, and Customer_OracleBIAnalyticsApps.rpd) are equivalent.

The point of this step is to determine for every object in the OracleBIAnalyticsApps.rpd and the Customer_OracleBIAnalyticsApps.rpd whether it is coming from the OracleBIAnalyticsApps_79x.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 $ORACLE_BI_HOME\biapps\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.
Table 8-2 provides a list of the available MAP files and the Siebel Analytics or Oracle BI Applications release version associated with the file.

Table 8-2 Rename MAP Files to Be Used for Various Releases

Siebel Analytics / Oracle Business Intelligence Applications Release Version (Upgrading from DW Version)

Rename MAP File to Be Used

Siebel Business Analytics Applications 7.0.x

Not available

Siebel Business Analytics Applications 7.5.x

Not available

Siebel Business Analytics Applications 7.7.x (with Siebel CRM OLTP Pre-7.7.0)

Rename77-7963.map

Siebel Business Analytics Applications 7.7.x (with Siebel CRM OLTP 7.7.0)

Rename771-7963.map

Siebel Business Analytics Applications 7.8.2 and all 7.8.x versions before this release

Rename782-7963.map

Siebel Business Analytics Applications 7.8.3 and all 7.8.x versions after this release

Rename783-7963.map

Oracle BI Applications 7.9.0

Rename79x-7963.map

Oracle BI Applications 7.9.1

Rename79x-7963.map

Oracle BI Applications 7.9.2

Rename79x-7963.map

Oracle BI Applications 7.9.3

Rename793to7963.map

Oracle BI Applications 7.9.4

Rename794to7963.map

Oracle BI Applications 7.9.5

Rename79x-7963.map

Oracle BI Applications 7.9.5.1

Rename7951to7963.map

Oracle BI Applications 7.9.5.2

Rename7951to7963.map

Oracle BI Applications 7.9.6

Rename79x-7963.map

Oracle BI Applications 7.9.6.2

rename7963to7964.map

Not required for upgrades from 7.9.6.2 to 7.9.6.3.

Oracle BI Applications 7.9.6.3

rename7963to7964.map

The syntax of the equalizerpds command is as follows:

equalizerpds.exe  [-B [password1]] -C base_repository_name [-E [password2]] -F repository2_name [-J udml_utf8_file_name_equalization] [-O ouput_repository_name] [-Y equalStringSet]
-Y          Treat the characters as equals.
/?          Display this usage information and exit.

To equalize a repository:

1. Copy the appropriate MAP file from the $ORACLE_BI_HOME\biapps\upgrade folder into the folder where you will execute equalizerpds.exe, for example, \OracleBIUpgrade\Original.

2. Run equalizerpds.exe to equalize the repository from the latest installation (for example, OracleBIAnalyticsApps.rpd) with the original repository (for example, OracleBIAnalyticsAppss_793.rpd). An example of the equalizerpds command is as follows:

equalizerpds -B SADMIN
-C \\OracleBIUpgrade\Original\OracleBIAnalyticsApps_791.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 $ORACLE_BI_HOME\biapps\upgrade folder.

If the equalizerpds.exe executable file runs correctly, no errors are returned.

3. Run equalizerpds.exe to equalize your customized repository (for example, Customer_OracleBIAnalyticsApps.rpd) with the original repository (for example, OracleBIAnalyticsApps_79x.rpd). An example of the equalizerpds command is as follows:

equalizerpds -B SADMIN
-C \\OracleBIUpgrade\Original\OracleBIAnalyticsApps_791.rpd
-E SADMIN
-F \\OracleBIUpgrade\Original\Customer_OracleBIAnalyticsApps.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.

4. 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).

8.14.3 Comparing the Oracle BI Repositories

Follow this procedure to compare your existing repository with the new version to which you are upgrading.

To compare the Oracle BI 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 Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition.

8.14.4 Merging the Oracle BI Repositories

In this procedure, you execute the main algorithm to upgrade the repository. For more information on merging the repositories, see Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition.

To merge versions of the Oracle BI repositories:

1. Copy the three repositories (for example, OracleBIAnalyticsApps_79x.rpd, OracleBIAnalyticsApps.rpd, and Customer_OracleBIAnalyticsApps.rpd) to the AfterMerge folder.

2. Open the repository from the latest installation (for example, OracleBIAnalyticsApps.rpd) in the \OracleBIUpgrade\AfterMerge folder.

3. From the Administration Tool menu bar, select File, then select Merge.

4. Select the Merge Type option Full Repository Merge.

5. In the Select Original Repository dialog box, select the original repository (for example, OracleBIAnalyticsApps_79x.rpd).

6. Enter the password for the original repository.

7. In the Select Modified Repository dialog box, select the repository that contains the customizations you made to the previous version of the Analytics repository.

8. Enter the password for the modified repository.

9. In the Saved Merged Repository as dialog box, enter the name for the merged repository, for example, Merged_Repository_OracleBIAnalyticsApps.rpd.
The new repository will contain the final results of the merge.

10. Select the Equalize during merge check box.

11. Click Next.

12. In the Decision drop-down list, select the action you want to take regarding the repository change, or accept the default action.

13. To locate subsequent rows with empty Decision fields, click the Decision header cell.
When all rows have a value in the Decision field, the Finish button is enabled.

14. Select the Check consistency of the merged RPD check box.

15. Click Finish.
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.

16. 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'

17. Copy the repository to the folder \OracleBIUpgrade\AfterManualWork.

8.15 Merging Oracle BI Applications Version 7.9.6.4 Presentation Catalog With Current (Custom) Catalog

Note:

Before you begin this procedure, you must have already upgraded your current (custom) catalog to the Oracle BI Enterprise Edition 11g format. For more information, see Section 8.13, "Upgrading the Oracle BI Repository and Presentation Catalog to the Oracle BI Enterprise Edition 11g Version."

You need to perform the following tasks to complete the presentation merge process.

- Section 8.15.1, "Trimming the Input Presentation Catalog"

- Section 8.15.2, "Merging the Oracle BI Applications Version 7.9.6.4 Presentation Catalog With Current (Custom) Catalog"

- Section 8.15.3, "Testing the Results of the Presentation Catalog Upgrade"

These procedures use the following terminology to identify the various presentation catalogs you will use in the merge process:

- The original presentation catalog. This catalog is the output from the step you performed in Section 8.13, "Upgrading the Oracle BI Repository and Presentation Catalog to the Oracle BI Enterprise Edition 11g Version." It is the version of the unmodified presentation catalog you received with the Oracle BI Applications release you are upgrading from that you upgraded to the 11g format.

- The new presentation catalog. This is the standard Oracle BI Applications 7.9.6.4 presentation catalog that is installed with Oracle BI Applications.

- The current presentation catalog. This catalog is the output from the step you performed in Section 8.13, "Upgrading the Oracle BI Repository and Presentation Catalog to the Oracle BI Enterprise Edition 11g Version." It is the presentation catalog currently in use at your organization that you upgraded to the 11g format.

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 Fusion Middleware Upgrade Guide for Oracle Business Intelligence

8.15.1 Trimming the Input Presentation Catalog

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.

8.15.2 Merging the Oracle BI Applications Version 7.9.6.4 Presentation Catalog With Current (Custom) Catalog

Note:

Before you begin this procedure, you must have already upgraded your current (custom) catalog to the Oracle BI Enterprise Edition 11g format. For more information, see Section 8.13, "Upgrading the Oracle BI Repository and Presentation Catalog to the Oracle BI Enterprise Edition 11g Version."

Follow the instructions in this section to merge the Oracle BI Applications version 7.9.6.4 presentation catalog with the catalog you are currently using. This procedure uses the Oracle BI Enterprise Edition Catalog Manager. High-level steps for the merge process are provided in this section. For detailed instructions on using the Catalog Manager, see the chapter "Configuring and Managing the Oracle BI Presentation Catalog," in the Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition 11g Release 1 (11.1.1).

To merge the Oracle BI Applications version 7.9.6.4 presentation catalog with the current (custom) catalog:

1. Start the Catalog Manager, and open your current (custom) presentation catalog in offline mode.
For instructions, see the section "Starting Catalog Manager and Opening Catalogs," in the Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition 11g Release 1 (11.1.1).

2. Start another instance of the Catalog Manager, and open the Oracle BI Applications version 7.9.6.4 (out-of-the-box) presentation catalog in offline mode.

3. Copy and paste the custom objects from your current presentation catalog into the Oracle BI Applications version 7.9.6.4 (out-of-the-box) presentation catalog.
For instructions, see the section "Working with Objects in Catalog Manager," in the Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition 11g Release 1 (11.1.1).

4. If you created custom catalog groups that are not in the version 7.9.6.4 presentation catalog, you need to convert the custom catalog groups to application roles in order to maintain consistency with the version 7.9.6.4 presentation catalog.
To convert custom catalog groups to application roles, run the following command:

runcat.cmd/runcat.sh -cmd replaceAccountInPermissions -old <Catalog Group Name> -oldType group -new <App Role Name> -newType role -offline  <catalog path>

For example:

runcat.cmd -cmd replaceAccountInPermissions -old "AP Analyst" -oldType group -new "AP Analyst" -newType role -offline  c:/SampleWebcat

This command replaces a specified account with another in all catalog object ACLs and privileges in the presentation catalog, entirely in the offline mode. If an entirely new application role is specified as the replacement account, then it is necessary to refresh the GUIDs in the presentation catalog before it can be used.

Note: If the specified replacement user or group is not already present in the presentation catalog 11g Release 1 (11.1.1) already, then this operation will fail.

For more information, see the Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition 11g Release 1 (11.1.1).

8.15.3 Testing the Results of the Presentation Catalog Upgrade

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.

8.16 Regression Testing the Oracle BI Repository Merge

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:

1. 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.

2. 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 Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition.

3. Execute the logical SQL against the old repository using the command line utility nQCmd.exe located in $ORACLE_BI_HOME\bifoundation\server\bin, and save the results to a file.
For information about the nQCmd.exe utility, see Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition.

4. Edit the logical SQL test scripts to account for the name changes or modifications resulting from the upgrade.

5. Execute the edited logical SQL against the merged repository, and save the results.

6. 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.

Part V

Appendixes

Part V contains the following appendixes:

- Appendix A, "Setting Parameters in Informatica Parameter Files"

- Appendix B, "Generating and Running Scripts to Drop and Create Indexes"

- Appendix C, "Creating Indexes for Oracle Financial Analytics"

- Appendix D, "Setting Database-Specific Parameters for the reset_infa_seq_gen.bat File"

- Appendix E, "Using the DDLimp Utility"

- Appendix F, "Creating ODBC Database Connections for DAC"

- Appendix G, "Upgrading the Oracle BI Repository for Industry-Specific Analytics Applications"

A Setting Parameters in Informatica Parameter Files

This appendix provides instructions for setting parameters in the Informatica parameter files. It contains the following topics:

- Section A.1, "Setting Common Parameters in Informatica Parameter Files"

- Section A.2, "Setting Source System-Specific Parameters in Informatica Parameter Files"

- Section A.3, "Setting Application-Specific Parameters in Informatica Parameter Files"

A.1 Setting Common Parameters in Informatica Parameter Files

This section provides instructions for configuring the <Oracle BI Applications version>_UPG_PARAMS.txt file. You need to configure these files for each version of Oracle BI Applications to which you are upgrading.

This section contains the following topics:

- Section A.1.1, "Setting Parameters in 793_UPG_PARAMS.txt"

- Section A.1.2, "Setting Parameters in 794_UPG_PARAMS.txt"

- Section A.1.3, "Setting Parameters in 795_UPG_PARAMS.txt"

- Section A.1.4, "Setting Parameters in 7951_UPG_PARAMS.txt"

- Section A.1.5, "Setting Parameters in 796_UPG_PARAMS.txt"

- Section A.1.6, "Setting Parameters in 7961_UPG_PARAMS.txt"

- Section A.1.7, "Setting Parameters in 7962_UPG_PARAMS.txt"

- Section A.1.8, "Setting Parameters in 7963_UPG_PARAMS.txt"

- Section A.1.9, "Setting Parameters in 7964_UPG_PARAMS.txt"

A.1.1 Setting Parameters in 793_UPG_PARAMS.txt

Follow this procedure to set parameters in the 793_UPG_PARAMS.txt file. This procedure is applicable for upgrades to Oracle BI Applications release 7.9.3.

To set parameters in the 793_UPG_PARAMS.txt file

1. Navigate to the folder OracleBI\dwrep\Upgrade\Informatica\ParameterFiles and copy the file 793_UPG_PARAMS.txt into the SrcFiles folder on the Informatica Server machine, for example, <INFA_HOME>\server\infa_shared\SrcFiles.

2. Set the parameter $$ETL_PROC_WID to the latest ETL_PROC_WID value from the database. You can get this value from W_PARAM_G.ETL_PROC_WID.

3. Set the parameter $$DATASOURCE_NUM_ID to the relevant value from the source system setup.

4. Search for parameter values defined with the "TO_DATE" function. Edit the function to use the appropriate function for data conversion based on the database type:
- For Oracle databases, use "TO_DATE('1899-01-01 00:00:00', 'YYYY-MM-DD HH24:MI:SS')"

- For SQL Server databases, use "CONVERT(datetime,'1899-01-01')"

- For DB2 databases, use "TO_DATE('1899-01-01 00:00:00', 'YYYY-MM-DD HH24:MI:SS')"

- For Teradata databases, use "cast('1899-01-01' as timestamp format 'YYYY-MM-DD')"

A.1.2 Setting Parameters in 794_UPG_PARAMS.txt

Follow this procedure to set parameters in the 794_UPG_PARAMS.txt file. This procedure is applicable for upgrades to Oracle BI Applications release 7.9.4.

To set parameters in the 794_UPG_PARAMS.txt file

1. Navigate to the folder OracleBI\dwrep\Upgrade\Informatica\ParameterFiles and copy the file 794_UPG_PARAMS.txt into the SrcFiles folder on the Informatica Server machine, for example, <INFA_HOME>\server\infa_shared\SrcFiles.

2. Set the parameter $$ETL_PROC_WID to the latest ETL_PROC_WID value from the database. You can get this value from W_PARAM_G.ETL_PROC_WID.

3. Set the parameter $$DATASOURCE_NUM_ID to the relevant value from the source system setup.

4. Search for parameter values defined with the "TO_DATE" function. Edit the function to use the appropriate function for data conversion based on the database type:
- For Oracle databases, use "TO_DATE('1899-01-01 00:00:00', 'YYYY-MM-DD HH24:MI:SS')"

- For SQL Server databases, use "CONVERT(datetime,'1899-01-01')"

- For DB2 databases, use "TO_DATE('1899-01-01 00:00:00', 'YYYY-MM-DD HH24:MI:SS')"

- For Teradata databases, use "cast('1899-01-01' as timestamp format 'YYYY-MM-DD')"

A.1.3 Setting Parameters in 795_UPG_PARAMS.txt

Follow this procedure to set parameters in the 795_UPG_PARAMS.txt file. This procedure is applicable for upgrades to Oracle BI Applications release 7.9.5.

To set parameters in the 795_UPG_PARAMS.txt file

1. Navigate to the folder OracleBI\dwrep\Upgrade\Informatica\ParameterFiles and copy the file 795_UPG_PARAMS.txt into the SrcFiles folder on the Informatica Server machine, for example, <INFA_HOME>\server\infa_shared\SrcFiles.

2. Set the parameter $$ETL_PROC_WID to the latest ETL_PROC_WID value from the database. You can get this value from W_PARAM_G.ETL_PROC_WID.

3. Set the parameter $$DATASOURCE_NUM_ID to the relevant value from the source system setup.

4. Search for parameter values defined with the "TO_DATE" function. Edit the function to use the appropriate function for data conversion based on the database type:
- For Oracle databases, use "TO_DATE('1899-01-01 00:00:00', 'YYYY-MM-DD HH24:MI:SS')"

- For SQL Server databases, use "CONVERT(datetime,'1899-01-01')"

- For DB2 databases, use "TO_DATE('1899-01-01 00:00:00', 'YYYY-MM-DD HH24:MI:SS')"

- For Teradata databases, use "cast('1899-01-01' as timestamp format 'YYYY-MM-DD')"

A.1.4 Setting Parameters in 7951_UPG_PARAMS.txt

Follow this procedure to set parameters in the 7951_UPG_PARAMS.txt file. This procedure is applicable for upgrades to Oracle BI Applications release 7.9.5.1.

To set parameters in the 7951_UPG_PARAMS.txt file

1. Navigate to the folder OracleBI\dwrep\Upgrade\Informatica\ParameterFiles and copy the file 7951_UPG_PARAMS.txt into the SrcFiles folder on the Informatica Server machine, for example, <INFA_HOME>\server\infa_shared\SrcFiles.

2. Set the parameter $$ETL_PROC_WID to the latest ETL_PROC_WID value from the database. You can get this value from W_PARAM_G.ETL_PROC_WID.

3. Set the parameter $$DATASOURCE_NUM_ID to the relevant value from the source system setup.

4. Search for parameter values defined with the "TO_DATE" function. Edit the function to use the appropriate function for data conversion based on the database type:
- For Oracle databases, use "TO_DATE('1899-01-01 00:00:00', 'YYYY-MM-DD HH24:MI:SS')"

- For SQL Server databases, use "CONVERT(datetime,'1899-01-01')"

- For DB2 databases, use "TO_DATE('1899-01-01 00:00:00', 'YYYY-MM-DD HH24:MI:SS')"

- For Teradata databases, use "cast('1899-01-01' as timestamp format 'YYYY-MM-DD')"

A.1.5 Setting Parameters in 796_UPG_PARAMS.txt

Follow this procedure to set parameters in the 796_UPG_PARAMS.txt file. This procedure is applicable for upgrades to Oracle BI Applications release 7.9.6.

To set parameters in the 796_UPG_PARAMS.txt file

1. Navigate to the folder OracleBI\dwrep\Upgrade\Informatica\ParameterFiles and copy the file 796_UPG_PARAMS.txt into the SrcFiles folder on the Informatica Server machine, for example, <INFA_HOME>\server\infa_shared\SrcFiles.

2. In the 796_UPG_PARAMS.txt file, set the following parameters:

1. $$ETL_PROC_WID. Set this parameter to the relevant value from the source system setup. You can get this value from W_PARAM_G.ETL_PROC_WID

2. $$DATASOURCE_NUM_ID. Set this parameter to the relevant value from the source system setup.

3. $$INITIAL_EXTRACT_DATE. Set this parameter to the initial extraction data of the data warehouse.

4. $$WH_DATASOURCE_NUM_ID. Set this parameter to the data source number ID you have set up for the data warehouse. This value should be the same data source number ID in the warehouse table W_DAY_D. If this is not set up correctly, the upgrade maps will fail with a NULL ROW_WID. Make sure this parameter is setup appropriately for your environment.

5. $$START_DATE. Get this value from the Source System Parameters tab in DAC.

6. $$END_DATE. Get this value from the Source System Parameters tab in DAC.

7. $$MASTER_ORG. Get this value from the Source System Parameters tab in DAC.

8. $$INV_PROD_CAT_SET_ID1. Get this value from the Source System Parameters tab in DAC.

9. $$PROD_CAT_SET_ID1. Get this value from the Source System Parameters tab in DAC.

10. Set the parameter $$IS_SOURCE_PRE_80 to Y if your source OLTP application was on a version prior to Siebel 8.0 before you began the upgrade process. Otherwise, set this parameter to N.

11. Search for parameter values defined with the "TO_DATE" function. Edit the function to use the appropriate function for data conversion based on the database type:
- For Oracle databases, use "TO_DATE('1899-01-01 00:00:00', 'YYYY-MM-DD HH24:MI:SS')"

- For SQL Server databases, use "CONVERT(datetime,'1899-01-01')"

- For DB2 databases, use "TO_DATE('1899-01-01 00:00:00', 'YYYY-MM-DD HH24:MI:SS')"

- For Teradata databases, use "cast('1899-01-01' as timestamp format 'YYYY-MM-DD')"

A.1.6 Setting Parameters in 7961_UPG_PARAMS.txt

Follow this procedure to set parameters in the 7961_UPG_PARAMS.txt file. This procedure is applicable for upgrades to Oracle BI Applications release 7.9.6.1.

To set parameters in the 7961_UPG_PARAMS.txt file

1. Navigate to the folder OracleBI\dwrep\Upgrade\Informatica\ParameterFiles and copy the file 7961_UPG_PARAMS.txt into the SrcFiles folder on the Informatica Server machine, for example, <INFA_HOME>\server\infa_shared\SrcFiles.

2. In the 7961_UPG_PARAMS.txt file, set the following parameters:

1. $$ETL_PROC_WID. Set this parameter to the relevant value from the source system setup. You can get this value from W_PARAM_G.ETL_PROC_WID

2. $$DATASOURCE_NUM_ID. Set this parameter to the relevant value from the source system setup.

3. $$INITIAL_EXTRACT_DATE. Set this parameter to the initial extraction data of the data warehouse.

4. $$WH_DATASOURCE_NUM_ID. Set this parameter to the data source number ID you have set up for the data warehouse.

5. Search for parameter values defined with the "TO_DATE" function. Edit the function to use the appropriate function for data conversion based on the database type:
- For Oracle databases, use "TO_DATE('1899-01-01 00:00:00', 'YYYY-MM-DD HH24:MI:SS')"

- For SQL Server databases, use "CONVERT(datetime,'1899-01-01')"

- For DB2 databases, use "TO_DATE('1899-01-01 00:00:00', 'YYYY-MM-DD HH24:MI:SS')"

- For Teradata databases, use "cast('1899-01-01' as timestamp format 'YYYY-MM-DD')"

A.1.7 Setting Parameters in 7962_UPG_PARAMS.txt

Follow this procedure to set parameters in the 7962_UPG_PARAMS.txt file. This procedure is applicable for upgrades to Oracle BI Applications release 7.9.6.2.

Note: If your source system is PeopleSoft, you must also set the parameters in Section A.2.3, "Setting Parameters in 7962_UPG_PARAMS.txt for PeopleSoft Source Systems."

To set parameters in the 7962_UPG_PARAMS.txt file

1. Navigate to the folder OracleBI\dwrep\Upgrade\Informatica\ParameterFiles and copy the file 7962_UPG_PARAMS.txt into the SrcFiles folder on the Informatica Server machine, for example, <INFA_HOME>\server\infa_shared\SrcFiles.

2. In the 7962_UPG_PARAMS.txt file, set the following parameters:

1. $$ETL_PROC_WID. Set this parameter to the relevant value from the source system setup. You can get this value from W_PARAM_G.ETL_PROC_WID

2. $$DATASOURCE_NUM_ID. Set this parameter to the relevant value from the source system setup.

3. $$INITIAL_EXTRACT_DATE. Set this parameter to the initial extraction data of the data warehouse.

4. $$WH_DATASOURCE_NUM_ID. Set this parameter to the data source number ID you have set up for the data warehouse.

5. Search for parameter values defined with the "TO_DATE" function. Edit the function to use the appropriate function for data conversion based on the database type:
- For Oracle databases, use "TO_DATE('1899-01-01 00:00:00', 'YYYY-MM-DD HH24:MI:SS')"

- For SQL Server databases, use "CONVERT(datetime,'1899-01-01')"

- For DB2 databases, use "TO_DATE('1899-01-01 00:00:00', 'YYYY-MM-DD HH24:MI:SS')"

- For Teradata databases, use "cast('1899-01-01' as timestamp format 'YYYY-MM-DD')"

A.1.8 Setting Parameters in 7963_UPG_PARAMS.txt

Follow this procedure to set parameters in the 7963_UPG_PARAMS.txt file. This procedure is applicable for upgrades to Oracle BI Applications release 7.9.6.3.

To set parameters in the 7963_UPG_PARAMS.txt file

1. Navigate to the folder OracleBI\dwrep\Upgrade\Informatica\ParameterFiles and copy the file 7963_UPG_PARAMS.txt into the SrcFiles folder on the Informatica Server machine, for example, <INFA_HOME>\server\infa_shared\SrcFiles.

2. In the 7963_UPG_PARAMS.txt file, set the following global parameters:

1. $$ETL_PROC_WID. Set this parameter to the relevant value from the source system setup. You can get this value from W_PARAM_G.ETL_PROC_WID

2. $$WH_DATASOURCE_NUM_ID. Set this parameter to the data source number ID you have set up for the data warehouse.

3. In the 7963_UPG_PARAMS.txt file, set the following common dimension parameters:

1. Locate the section in the file that lists common dimension parameters for your source system, and set the following parameters.

2. $$DATASOURCE_NUM_ID. Set this parameter to the relevant value from the source system setup.

3. $$INITIAL_EXTRACT_DATE. Set this parameter to the initial extraction data of the data warehouse.

4. $$DFLT_LANG. The default value for this parameter is $$DFLT_LANG=US. This value is appropriate for Oracle source systems when the transactional database language is English (US).
For Siebel and JD Edwards source systems with the transactional database language as English (US), set the value for the parameter to $$DFLT_LANG=ENU.

If the default language of your transactional database is not English (US), you need to set the DFLT_LANG parameter to the appropriate language for your data source database. To find the value to specify, execute the following query against the transactional database.

select VAL from S_SYS_PREF where SYS_PREF_CD='ETL Default Language';

Note: PeopleSoft source systems do not use the $$DFLT_LANG parameter.

A.1.9 Setting Parameters in 7964_UPG_PARAMS.txt

Follow this procedure to set parameters in the 7964_UPG_PARAMS.txt file. This procedure is applicable for upgrades to Oracle BI Applications release 7.9.6.1.

To set parameters in the 7964_UPG_PARAMS.txt file

1. Navigate to the folder OracleBI\dwrep\Upgrade\Informatica\ParameterFiles and copy the file 7964_UPG_PARAMS.txt into the SrcFiles folder on the Informatica Server machine, for example, <INFA_HOME>\server\infa_shared\SrcFiles.

2. In the 7964_UPG_PARAMS.txt file, set the following parameters:

1. $$ETL_PROC_WID. Set this parameter to the relevant value from the source system setup. You can get this value from W_PARAM_G.ETL_PROC_WID

2. $$DATASOURCE_NUM_ID. Set this parameter to the relevant value from the source system setup.

3. $$INITIAL_EXTRACT_DATE. Set this parameter to the initial extraction data of the data warehouse.

4. $$WH_DATASOURCE_NUM_ID. Set this parameter to the data source number ID you have set up for the data warehouse.

5. Search for parameter values defined with the "TO_DATE" function. Edit the function to use the appropriate function for data conversion based on the database type:
- For Oracle databases, use "TO_DATE('1899-01-01 00:00:00', 'YYYY-MM-DD HH24:MI:SS')"

- For SQL Server databases, use "CONVERT(datetime,'1899-01-01')"

- For DB2 databases, use "TO_DATE('1899-01-01 00:00:00', 'YYYY-MM-DD HH24:MI:SS')"

- For Teradata databases, use "cast('1899-01-01' as timestamp format 'YYYY-MM-DD')"

A.2 Setting Source System-Specific Parameters in Informatica Parameter Files

This section provides instructions for setting parameters in the Informatica parameter files that are specific to various source systems. You may need to set or update these parameters depending on your environment. The topic headings below indicate the source system and version of the parameter file that require configuration.

This section includes the following topics:

- Section A.2.1, "Setting Parameters in 796_UPG_PARAMS.txt for Oracle EBS 11i Source Systems"

- Section A.2.2, "Setting Parameters in 796_UPG_PARAMS.txt for Siebel Source Systems"

- Section A.2.3, "Setting Parameters in 7962_UPG_PARAMS.txt for PeopleSoft Source Systems"

- Section A.2.4, "Setting Parameters in 7963_UPG_PARAMS.txt for Siebel Industry Applications Source Systems"

Note: If you are using Oracle Financial Analytics and your source system is either PeopleSoft or Oracle EBS 11.5.10 family pack OIE.I and OIE.J, there are additional parameters you must set. For instructions, see Section A.3.5, "Setting Parameters in 7963_UPG_PARAMS.txt for Oracle Financial Analytics."

A.2.1 Setting Parameters in 796_UPG_PARAMS.txt for Oracle EBS 11i Source Systems

This procedure is only applicable to Oracle EBS 11i source systems and for upgrades to Oracle BI Applications release 7.9.6.

To set parameters in the 796_UPG_PARAMS.txt file for Oracle EBS 11i source systems

1. Navigate to the SrcFiles folder on the Informatica Server machine, for example, <INFA_HOME>\server\infa_shared\SrcFiles.

2. Open the file 796_UPG_PARAMS.txt.

3. Note the values for the following parameters:

- $$ORA_DATASOURCE_NUM_ID_LIST

- $$GRAIN

- $$GBL_DATASOURCE_NUM_ID

- $$QUALIFICATION_CATEGORY_LIST

4. In DAC, go to the Design view, and select the appropriate custom container.

5. Select the Source System Parameters tab.

6. Query for the parameters listed in Step 3, and compare the values.

7. If necessary, change the values for the parameters in the 796_UPG_PARAMS.txt file to match the values for the parameters in the DAC Source System Parameters tab.

8. Save the 796_UPG_PARAMS.txt file.

A.2.2 Setting Parameters in 796_UPG_PARAMS.txt for Siebel Source Systems

This procedure is only applicable to Siebel source systems and for upgrades to Oracle BI Applications release 7.9.6.

To set parameters in the 796_UPG_PARAMS.txt file for Siebel source systems

1. Navigate to the SrcFiles folder on the Informatica Server machine, for example, <INFA_HOME>\server\infa_shared\SrcFiles.

2. Open the file 796_UPG_PARAMS.txt.

3. Note the values for the following parameters:

- $$HI_DT

- $$LOW_DT

- $$NAME_ORDER_WITH_FIRSTNAME

4. In DAC, go the Design view, and select the appropriate custom container.

5. Select the Source System Parameters tab.

6. Query for the parameters listed in Step 3, and compare the values.

7. If necessary, change the values for the parameters in the 796_UPG_PARAMS.txt file to match the values for the parameters in the DAC Source System Parameters tab.

8. Save the 796_UPG_PARAMS.txt file.

A.2.3 Setting Parameters in 7962_UPG_PARAMS.txt for PeopleSoft Source Systems

If your source system is PeopleSoft, you must follow the instructions in this section after completing the instructions in Section A.1.7, "Setting Parameters in 7962_UPG_PARAMS.txt." This procedure is applicable for upgrades to Oracle BI Applications release 7.9.6.2.

To set parameters in the 7962_UPG_PARAMS.txt file for PeopleSoft source systems

1. Open the 7962_UPG_PARAMS.txt file.
Note: Make sure you perform the procedure in Section A.1.7, "Setting Parameters in 7962_UPG_PARAMS.txt" before you begin this procedure.

2. If you are using PeopleSoft version 8.9 or higher, set the following parameters in the 7962_UPG_PARAMS.txt file specific to multiple product category enhancement:

1. For the $$TREE_NAME1 parameter, set the value to a tree name for which you want to include the product categories. Generally, this value is ALL_PURCHASE_ITEMS. You can use the following SQL to obtain the TREE_NAMES:

SELECT * FROM PSTREEDEFN WHERE TREE_STRCT_ID = 'ITEMS'

2. The TREE_STRUCT in the PeopleSoft Tree that defines the Item Category Tree generally has the value ITEMS. If you changed this value, you must update the parameter $$TREE_STRUCT_ID_LIST with the appropriate value.

3. Verify the value for the PSFT_OLTP_VER parameter matches the version of PeopleSoft you are using.

PeopleSoft Version

Enter Parameter Value

PeopleSoft version 8.9

PSFT_OLTP_VER=90

PeopleSoft version 9.0

PSFT_OLTP_VER=90

PeopleSoft version 9.1

PSFT_OLTP_VER=91

The default value for this parameter is PSFT_OLTP_VER=91.

Caution:

You must enter the correct value for this parameter or else the upgrade process will fail.

A.2.4 Setting Parameters in 7963_UPG_PARAMS.txt for Siebel Industry Applications Source Systems

This procedure is applicable when you are upgrading to Oracle BI Applications release 7.9.6.3 and the source system is Siebel Industry Applications.

To set parameters in the 7963_UPG_PARAMS.txt file for Siebel Industry Applications source systems

1. Navigate to the SrcFiles folder on the Informatica Server machine, for example, <INFA_HOME>\server\infa_shared\SrcFiles.

2. Open the file 7963_UPG_PARAMS.txt.

3. Search for the parameter $$VERTICAL_UPGRADE.

4. If you are using Siebel Industry Applications, set the value to 1.
For example: $$VERTICAL_UPGRADE=1

If you are not using Siebel Industry Applications, leave the default value (0).

5. Save the 7963_UPG_PARAMS.txt file.

A.3 Setting Application-Specific Parameters in Informatica Parameter Files

This section provides information about setting parameters in the Informatica parameter files that are specific to an Oracle BI Applications application. You may need to set or update these parameters depending on your environment. The topic headings below indicate the application and version of the parameter file that require configuration.

This appendix includes the following topics:

- Section A.3.1, "Setting Parameters and Mappings in 796_UPG_PARAMS.txt for Oracle Financial Analytics"

- Section A.3.2, "Setting Parameters in 796_UPG_PARAMS.txt for Oracle Project Analytics"

- Section A.3.3, "Setting Parameters in 796_UPG_PARAMS.txt for Oracle Supply Chain and Order Management Analytics"

- Section A.3.4, "Setting Parameters and Mappings in 7962_UPG_PARAMS.txt for Oracle Financial Analytics"

- Section A.3.5, "Setting Parameters in 7963_UPG_PARAMS.txt for Oracle Financial Analytics"

- Section A.3.6, "Setting Parameters in 7963_UPG_PARAMS.txt for Oracle Human Resources Analytics"

- Section A.3.7, "Setting Parameters in 7963_UPG_PARAMS.txt for Oracle Procurement and Spend Analytics on PeopleSoft Source System"

A.3.1 Setting Parameters and Mappings in 796_UPG_PARAMS.txt for Oracle Financial Analytics

This section provides information about parameters and mappings specific to Oracle Financial Analytics that you may need to configure or update depending on your environment. The procedures in this section are applicable for upgrades to Oracle BI Applications release 7.9.6.

This section includes the following topics:

- Section A.3.1.1, "Setting Parameters for Value Set Hierarchies and FSG Hierarchies"

- Section A.3.1.2, "Setting Parameters for GL Data Extraction"

- Section A.3.1.3, "Setting the COGS Fact Mapping for Oracle EBS R12"

- Section A.3.1.4, "Setting the $$Hint1 Parameter for Oracle Databases"

A.3.1.1 Setting Parameters for Value Set Hierarchies and FSG Hierarchies

In Oracle Financial Analytics, the default behavior is for Value Set Hierarchies to be enabled and Financial Statement Generator (FSG) Hierarchies to be disabled.

If you have changed this behavior by disabling Value Set Hierarchies and enabling FSG Hierarchies, then you need to set the parameters that control this behavior in the 796_UPG_PARAMS.txt file and the DAC configuration tags.

To set the FSG Hierarchies and Value Set Hierarchies parameters

1. Navigate to the SrcFiles folder on the Informatica Server machine, for example, <INFA_HOME>\server\infa_shared\SrcFiles.

2. Open the 796_UPG_PARAMS.txt file.

3. Search for the parameter $$IS_FSGHIERARCHY_INSTALLED, and set the value to Y.
For example:

$$IS_FSGHIERARCHY_INSTALLED=Y

4. Search for the parameter $$IS_VALUESETHIERARCHY_INSTALLED, and set the value to N.
For example:

$$IS_VALUESETHIERARCHY_INSTALLED=N

A.3.1.2 Setting Parameters for GL Data Extraction

If you have configured your GL data extraction to limit the set of books or ledgers extracted, you need to set the appropriate parameters in the 796_UPG_PARAMS.txt file to match the same parameters in the DAC source system parameters.

This section includes the following topics:

- Section A.3.1.2.1, "Setting GL Data Extraction Parameters for Oracle EBS 11i Sources"

- Section A.3.1.2.2, "Setting GL Data Extraction Parameters for Oracle EBS R12 Sources"

A.3.1.2.1 Setting GL Data Extraction Parameters for Oracle EBS 11i Sources

Follow this procedure to set GL data extraction parameters for Oracle EBS 11i sources.

To set GL data extraction parameters

1. Navigate to the SrcFiles folder on the Informatica Server machine, for example, <INFA_HOME>\server\infa_shared\SrcFiles.

2. Open the 796_UPG_PARAMS.txt file.

3. Note the values for the following parameters:

- $$FILTER_BY_SET_OF_BOOKS_ID

- $$FILTER_BY_SET_OF_BOOKS_TYPE

- $$SET_OF_BOOKS_ID_LIST

- $$SET_OF_BOOKS_TYPE_LIST

4. In DAC, go to the Design view, and select the appropriate custom container.

5. Select the Source System Parameters tab.

6. Query for the parameters listed in Step 3, and compare the values.

7. If necessary, change the values for the parameters in the 796_UPG_PARAMS.txt file to match the values for the parameters in the DAC Source System Parameters tab.

8. Save the 796_UPG_PARAMS.txt file.

A.3.1.2.2 Setting GL Data Extraction Parameters for Oracle EBS R12 Sources

Follow this procedure to configure GL data extraction parameters for Oracle EBS R12 sources.

To set GL data extraction parameters

1. Navigate to the SrcFiles folder on the Informatica Server machine, for example, <INFA_HOME>\server\infa_shared\SrcFiles.

2. Open the 796_UPG_PARAMS.txt file.

3. Note the values for the following parameters:

- $$FILTER_BY_LEDGER_ID

- $$FILTER_BY_LEDGER_TYPE

- $$LEDGER_ID_LIST

- $$LEDGER_TYPE_LIST

4. In DAC, go to the Design view, and select the appropriate custom container.

5. Select the Source System Parameters tab.

6. Query for the parameters listed in Step 3, and compare the values.

7. If necessary, change the values for the parameters in the 796_UPG_PARAMS.txt file to match the values for the parameters in the DAC Source System Parameters tab.

8. Save the 796_UPG_PARAMS.txt file.

A.3.1.3 Setting the COGS Fact Mapping for Oracle EBS R12

For Oracle EBS R12 sources, follow this procedure to update the COGS fact mapping.

To set the COGS fact mapping

1. Launch Informatica PowerCenter Designer.

2. Navigate to the folder UPGRADE_7951_TO_796_ORA12.

3. Open the mapping SDE_ORA_GLCOGSFact_UPG796.

4. Open the mapplet mplt_BC_ORA_GLCOGSFact.

5. Open the Source Qualifier Transformation, do the following:

1. Open the SQL Query property.

2. In the WHERE clause of the query locate the hard-coded filter on the Transaction Type ID and Transaction Action ID.
For example:

MMT.TRANSACTION_TYPE_ID IN (15, 33, 10008) AND (MMT.TRANSACTION_ACTION_ID,MTA.ACCOUNTING_LINE_TYPE) IN ((27, 2), (1, 36), (36, 35))

6. Change the values to the actual values you used in the SDE_ORA_GLCOGSFact mapping in the base Informatica Repository code.

A.3.1.4 Setting the $$Hint1 Parameter for Oracle Databases

If your target data warehouse is an Oracle database server, follow this procedure to set the $$Hint1 parameter.

To set the $$Hint1 parameter

1. Navigate to the SrcFiles folder on the Informatica Server machine, for example, <INFA_HOME>\server\infa_shared\SrcFiles.

2. Open the 796_UPG_PARAMS.txt file.

3. Locate the $$Hint1 parameter for the appropriate version of the Oracle database, and enter the following value:
/*+ USE_HASH(W_GL_BALANCE_F, W_GL_ACCOUNT_D, W_GLACCT_SEG_CONFIG_TMP) */

For example:

mplt_GLBalanceAggrByAcctSegCodes.$$Hint1=/*+ USE_HASH(W_GL_BALANCE_F, W_GL_ACCOUNT_D, W_GLACCT_SEG_CONFIG_TMP) */

4. Save the 796_UPG_PARAMS.txt file.

A.3.2 Setting Parameters in 796_UPG_PARAMS.txt for Oracle Project Analytics

If you are deploying Oracle Project Analytics and you are upgrading to Oracle BI Applications release 7.9.6, follow the procedure in this section to configure the IS_PROJECTS_INSTALLED parameter.

To set the IS_PROJECTS_INSTALLED parameter

1. Navigate to the SrcFiles folder on the Informatica Server machine, for example, <INFA_HOME>\server\infa_shared\SrcFiles.

2. Open the 796_UPG_PARAMS.txt file.

3. Search for the parameter $$IS_PROJECTS_INSTALLED, and set the value to Y.
For example:

$$IS_PROJECTS_INSTALLED=Y

4. Save the 796_UPG_PARAMS.txt file.

A.3.3 Setting Parameters in 796_UPG_PARAMS.txt for Oracle Supply Chain and Order Management Analytics

If you are deploying Oracle Supply Chain and Order Management Analytics and you are upgrading to Oracle BI Applications release 7.9.6, follow the procedures in this section to set parameters in 796_UPG_PARAM.txt.

This section includes the following topics:

- Section A.3.3.1, "Setting the TIME_GRAIN Parameter for Sales Order Lines Aggregate Fact and Invoice Lines Aggregate Fact Tables"

- Section A.3.3.2, "Setting the $$PERIOD Parameter for the Customer Status History Fact Table"

A.3.3.1 Setting the TIME_GRAIN Parameter for Sales Order Lines Aggregate Fact and Invoice Lines Aggregate Fact Tables

If you are deploying Oracle Supply Chain and Order Management Analytics, you need to configure the TIME_GRAIN parameter for the Sales Order Lines Aggregate Fact table and for the Invoice Lines Aggregate Fact table. For instructions, see the section titled, "Process of Aggregating Oracle Supply Chain and Order Management," in Oracle Business Intelligence Applications Configuration Guide for Informatica PowerCenter Users.

A.3.3.2 Setting the $$PERIOD Parameter for the Customer Status History Fact Table

If you are deploying Oracle Supply Chain and Order Management Analytics, you need to configure the $$PERIOD parameter for the Customer Status History Fact table. For instructions, see the section titled, "How to Configure the Customer Status History Fact Table," in Oracle Business Intelligence Applications Configuration Guide for Informatica PowerCenter Users.

A.3.4 Setting Parameters and Mappings in 7962_UPG_PARAMS.txt for Oracle Financial Analytics

If you are deploying Oracle Financial Analytics and you are upgrading to Oracle BI Applications release 7.9.6.2, follow the procedures in this section for your particular source system to set parameters in 7962_UPG_PARAM.txt.

This section includes the following topics:

- Section A.3.4.1, "Setting GL Data Extraction Parameters for Oracle EBS 11i Sources"

- Section A.3.4.2, "Setting GL Data Extraction Parameters for Oracle EBS 12 Sources"

- Section A.3.4.3, "Setting GL Data Extraction Parameters for PeopleSoft Sources"

- Section A.3.4.4, "Setting the COGS Fact Mapping for Oracle EBS R12"

A.3.4.1 Setting GL Data Extraction Parameters for Oracle EBS 11i Sources

Follow this procedure to configure GL data extraction parameters for Oracle EBS 11i sources.

To set GL data extraction parameters

1. Navigate to the SrcFiles folder on the Informatica Server machine, for example, <INFA_HOME>\server\infa_shared\SrcFiles.

2. Open the 7962_UPG_PARAMS.txt file.

3. Note the values for the following parameters:

- mplt_BC_ORA_GL_Balance_Fact.$$FILTER_BY_SET_OF_BOOKS_ID

- mplt_BC_ORA_GL_Balance_Fact.$$FILTER_BY_SET_OF_BOOKS_TYPE

- mplt_BC_ORA_GL_Balance_Fact.$$SET_OF_BOOKS_ID_LIST

- mplt_BC_ORA_GL_Balance_Fact.$$SET_OF_BOOKS_TYPE_LIST

4. In DAC, go to the Design view, and select the appropriate custom container.

5. Select the Source System Parameters tab.

6. Query for the parameters listed in Step 3, and compare the values.

7. If necessary, change the values for the parameters in the 7962_UPG_PARAMS.txt file to match the values for the parameters in the DAC Source System Parameters tab.

8. Save the 7962_UPG_PARAMS.txt file.

A.3.4.2 Setting GL Data Extraction Parameters for Oracle EBS 12 Sources

Follow this procedure to configure GL data extraction parameters for Oracle EBS 12 sources.

To set GL data extraction parameters

1. Navigate to the SrcFiles folder on the Informatica Server machine, for example, <INFA_HOME>\server\infa_shared\SrcFiles.

2. Open the 7962_UPG_PARAMS.txt file.

3. Note the values for the following parameters:

- mplt_BC_ORA_GL_Balance_Fact.$$FILTER_BY_LEDGER_ID

- mplt_BC_ORA_GL_Balance_Fact.$$FILTER_BY_LEDGER_TYPE

- mplt_BC_ORA_GL_Balance_Fact.$$LEDGER_ID_LIST

- mplt_BC_ORA_GL_Balance_Fact.$$LEDGER_TYPE_LIST

4. In DAC, go to the Design view, and select the appropriate custom container.

5. Select the Source System Parameters tab.

6. Query for the parameters listed in Step 3, and compare the values.

7. If necessary, change the values for the parameters in the 7962_UPG_PARAMS.txt file to match the values for the parameters in the DAC Source System Parameters tab.

8. Save the 7962_UPG_PARAMS.txt file.

A.3.4.3 Setting GL Data Extraction Parameters for PeopleSoft Sources

Follow this procedure to configure GL data extraction parameters for PeopleSoft 8.8, 8.9, and 9.0 sources.

To set GL data extraction parameters

1. Navigate to the SrcFiles folder on the Informatica Server machine, for example, <INFA_HOME>\server\infa_shared\SrcFiles.

2. Open the 7962_UPG_PARAMS.txt file.

3. Note the values for the following parameters:

- mplt_BC_PSFT_GLBalanceFact.$$FISCAL_YEAR

- $$LOW_DATE

4. In DAC, go to the Design view, and select the appropriate custom container.

5. Select the Source System Parameters tab.

6. Query for the parameters listed in Step 3, and compare the values.

7. If necessary, change the values for the parameters in the 7962_UPG_PARAMS.txt file to match the values for the parameters in the DAC Source System Parameters tab.

Note:

The parameter $$FISCAL_YEAR is fiscal year from which you want to extract the GL Balances into the data warehouse. GL Balances from PS_LEDGER will be extracted from this year forward into the data warehouse. All balances prior to this year will not be extracted.

8. Save the 7962_UPG_PARAMS.txt file.

A.3.4.4 Setting the COGS Fact Mapping for Oracle EBS R12

For Oracle EBS R12 sources, follow this procedure to update the COGS fact mapping.

To set the COGS fact mapping

1. Launch Informatica PowerCenter Designer.

2. Navigate to the folder UPGRADE_7961_to_7962_ORAR12.

3. Open the mapping SDE_ORA_GLCOGSFact_UPG7962.

4. Open the mapplet mplt_BC_ORA_GLCOGSFact.

5. Open the Source Qualifier Transformation, and do the following:

1. Open the SQL Query property.

2. In the WHERE clause of the query, locate the hard-coded filter on the Transaction Type ID and Transaction Action ID.
For example:

MMT.TRANSACTION_TYPE_ID IN (15, 33, 10008) AND
(MMT.TRANSACTION_ACTION_ID,MTA.ACCOUNTING_LINE_TYPE) IN
((27,2),(1,36),(36,35))

6. Change the values to the actual values you used in the SDE_ORA_GLCOGSFact mapping in the main Informatica Repository code.

A.3.5 Setting Parameters in 7963_UPG_PARAMS.txt for Oracle Financial Analytics

If you are deploying Oracle Financial Analytics and you are upgrading to Oracle BI Applications release 7.9.6.3, follow the procedures in this section for your particular source system to set parameters in 7963_UPG_PARAM.txt.

This section includes the following topics:

- Section A.3.5.1, "Setting Parameters for All Source Systems"

- Section A.3.5.2, "Setting Parameters Specific to PeopleSoft"

- Section A.3.5.3, "Setting Parameters Specific to Oracle EBS 11.5.10 Family Pack OIE.I and OIE.J"

A.3.5.1 Setting Parameters for All Source Systems

This section provides instructions for setting parameters in the 7963_UPG_PARAMS.txt file for Oracle Financial Analytics for all source systems, including Oracle EBS 11i, Oracle EBS 12, PeopleSoft, and JD Edwards.

To set the soft delete parameter

1. Navigate to the SrcFiles folder on the Informatica Server machine, for example, <INFA_HOME>\server\infa_shared\SrcFiles.

2. Open the 7963_UPG_PARAMS.txt file.

3. Note the value for the parameter $$IS_SOFT_DELETE_IMPLEMENTED.
The default value for this parameter is $$IS_SOFT_DELETE_IMPLEMENTED=N.

If the Soft Delete parameter is implemented for any of the Oracle Financial Analytics modules, for example, GL, AP, AR, and Profitability (COGS/Revenue), you must change the parameter value to $$IS_SOFT_DELETE_IMPLEMENTED=Y for the appropriate module for which it is implemented.

4. Save the 7963_UPG_PARAMS.txt file.

A.3.5.2 Setting Parameters Specific to PeopleSoft

This section provides instructions for setting a parameter for Oracle Financial Analytics in the 7963_UPG_PARAMS.txt file that is specific to PeopleSoft source systems.

To set the parameter specific to PeopleSoft source systems

1. Navigate to the SrcFiles folder on the Informatica Server machine, for example, <INFA_HOME>\server\infa_shared\SrcFiles.

2. Open the 7963_UPG_PARAMS.txt file.

3. The parameter $$PSFT_OLTP_VER specifies the version of the PeopleSoft OLTP. The default value for this parameter is $$PSFT_OLTP_VER=90.
Change the parameter value to match the appropriate version of the PeopleSoft OLTP. For example:

- For PeopleSoft version 8.9, enter $$PSFT_OLTP_VER=89.

- For PeopleSoft version 9.0, enter $$PSFT_OLTP_VER=90.

- For PeopleSoft version 9.1, enter $$PSFT_OLTP_VER=91.

Note: This parameter is needed to run the Transaction type dimension maps, which are missing in the PeopleSoft 8.9 source system. Therefore, setting this parameter is particularly important if you are using PeopleSoft 8.9.

4. Save the 7963_UPG_PARAMS.txt file.

A.3.5.3 Setting Parameters Specific to Oracle EBS 11.5.10 Family Pack OIE.I and OIE.J

This section provides instructions for setting a parameter for Oracle Financial Analytics in the 7963_UPG_PARAMS.txt file that is specific to Oracle EBS 11.5.10 family pack OIE.I and OIE.J.

To set the parameter specific to Oracle EBS 11.5.10 OIE.I or OIE.J

1. Navigate to the SrcFiles folder on the Informatica Server machine, for example, <INFA_HOME>\server\infa_shared\SrcFiles.

2. Open the 7963_UPG_PARAMS.txt file.

3. The parameter $$ORA_OLTP_VER specifies the version of the Oracle EBS OLTP.
Change the parameter value to match the appropriate version of the family pack for your Oracle EBS 11.5.10 environment.

- For Oracle EBS 11.5.10 family pack OIE.I, enter $$ORA_OLTP_VER=OIEI.

- For Oracle EBS 11.5.10 family pack OIE.J, enter $$ORA_OLTP_VER=OIEJ.

4. Save the 7963_UPG_PARAMS.txt file.

A.3.6 Setting Parameters in 7963_UPG_PARAMS.txt for Oracle Human Resources Analytics

If you are deploying Oracle Human Resources Analytics and you are upgrading to Oracle BI Applications release 7.9.6.3, follow the procedure in this section to set parameters in 7963_UPG_PARAM.txt.

To set the parameter for Oracle Human Resources

1. Navigate to the SrcFiles folder on the Informatica Server machine, for example, <INFA_HOME>\server\infa_shared\SrcFiles.

2. Open the 7963_UPG_PARAMS.txt file.

3. Search for the parameter $$HR_WRKFC_EXTRACT_DATE.
The parameter value is defined with the "TO_DATE" function.

4. Edit the function to use the appropriate function for data conversion based on the database type:
- For Oracle databases, use "TO_DATE('1899-01-01 00:00:00', 'YYYY-MM-DD HH24:MI:SS')"

- For SQL Server databases, use "CONVERT(datetime,'1899-01-01')"

- For DB2 databases, use "TO_DATE('1899-01-01 00:00:00', 'YYYY-MM-DD HH24:MI:SS')"

- For Teradata databases, use "cast('1899-01-01' as timestamp format 'YYYY-MM-DD')"

5. Save the 7963_UPG_PARAMS.txt file.

A.3.7 Setting Parameters in 7963_UPG_PARAMS.txt for Oracle Procurement and Spend Analytics on PeopleSoft Source System

Follow the procedure in this section if you are deploying Oracle Procurement and Spend Analytics on a PeopleSoft 9.0 source system.

To set the parameters for Oracle Procurement and Spend Analytics

1. Navigate to the SrcFiles folder on the Informatica Server machine, for example, <INFA_HOME>\server\infa_shared\SrcFiles.

2. Open the 7963_UPG_PARAMS.txt file.

3. Set the parameter $$PSFT_DATASOURCE_NUM_ID to the relevant value from the source system setup.

4. Save the 7963_UPG_PARAMS.txt file.

A.3.8 Setting Parameters in 7963_UPG_PARAMS.txt for Oracle Procurement and Spend Analytics on Oracle EBS 11i and 12 Source Systems

Follow the procedure in this section if you are deploying Oracle Procurement and Spend Analytics on a Oracle EBS 11i and 12 source systems.

To set the parameters for Oracle Procurement and Spend Analytics

1. Navigate to the SrcFiles folder on the Informatica Server machine, for example, <INFA_HOME>\server\infa_shared\SrcFiles.

2. Open the 7963_UPG_PARAMS.txt file.

3. Search for the entry:

[UPGRADE_7962_to_7963_ORA<version>.SIL_PurchaseCycleLinesFact_UPG7963]

4. Set the parameter $$ORA_DATASOURCE_NUM_ID to the relevant value from the source system setup.
The default value for Oracle EBS 11i is

$$ORA_DATASOURCE_NUM_ID_LIST=(4)

The default value for Oracle EBS 12is

$$ORA_DATASOURCE_NUM_ID_LIST=(9)

5. Save the 7963_UPG_PARAMS.txt file.

B Generating and Running Scripts to Drop and Create Indexes

This appendix provides instructions for generating and running scripts to drop and create indexes while upgrading to releases 7.9.6.2 and 7.9.6.3.

This appendix contains the following topics:

- Section B.1, "Generating Scripts to Drop and Create Indexes for Upgrading to Release 7.9.6.2"

- Section B.2, "Running the Script to Drop All Indexes for Upgrading to Release 7.9.6.2"

- Section B.3, "Running the Scripts to Create ETL and Query Indexes for Upgrading to Release 7.9.6.2"

- Section B.4, "Generating Scripts to Drop and Create Query Indexes for Upgrading to Release 7.9.6.3"

- Section B.5, "Running the Scripts to Drop and Create Query Indexes for Upgrading to Release 7.9.6.3"

- Section B.6, "Generating Scripts to Drop and Create Query and ETL Indexes for Upgrading to Release 7.9.6.4"

- Section B.7, "Running the Scripts to Drop and Create Query Indexes for Upgrading to Release 7.9.6.4"

- Section B.8, "Running the Scripts to Drop and Create ETL Indexes for Upgrading to Release 7.9.6.4"

B.1 Generating Scripts to Drop and Create Indexes for Upgrading to Release 7.9.6.2

This section provides instructions for generating a script to drop indexes as well as scripts to create ETL indexes and query indexes. This procedure is applicable when you are upgrading to release 7.9.6.2.

To generate a script to drop indexes and a script to create indexes

1. Go to the folder OracleBI\dwrep\Upgrade\CTLFiles.

2. Open the UPGRADE_7961_to_7962_<source system>.txt file.
This file contains a list of data warehouse tables that were upgraded for this release.

3. Open a text editor, and copy and paste the contents of UPGRADE_7961_to_7962_<source system>.txt into a new file.
Note that table names are separated by a comma (,).

4. Find and replace the comma (,) with OR.
Make sure there is only one space before and after OR. The format of the text string should appear as follows:

table_1 OR table_2 OR table_3 OR table_4

For example:

W_POSITION_D OR W_PURCH_COST_F OR W_EXPENSE_F OR W_PURCH_CYCLE_LINE_A OR W_ORA_GL_LINKAGE_INFO_REVN_TMP OR W_POSITION_DH

5. Open the DAC repository for the release from which you are upgrading. For example, if you are upgrading from release 7.9.6.1 to 7.9.6.2, you would open the release 7.9.6.1 DAC repository

6. From the DAC toolbar, select the appropriate source system container from the drop-down list.

7. In the Design view, click the Indices tab.

8. In the top pane toolbar, click Query.
The top pane window now displays Query mode.

9. Copy the text string from the text file you created in step 5 into the Table Name field.

10. Click Go.

11. In the list of query results, right-click, and then select Generate Index Scripts.

12. Select "All records in the list."

13. In the Generate Index Scripts dialog box, do one of the following:

- To generate index scripts based on a physical data source connection that you previously set up, select the "Use source information" check box, and then select the appropriate physical data source connection from the drop-down list.

- To generate index scripts based on the data warehouse database type, deselect the "Use source information" check box, and then select the appropriate database type.
If the database type is Oracle, enter a table owner, and optionally enter a tablespace in which the indexes will be dropped and created.

If the database type is SQL Server, DB2 or Teradata, enter a table owner.

14. Click OK.
A message box states whether the scripts were successfully generated. The following scripts are saved in the folder \bifoundation\dac\log\scripts:

- dropAllIndexes.sql

- createETLIndexes.sql

- createQueryIndexes.sql

B.2 Running the Script to Drop All Indexes for Upgrading to Release 7.9.6.2

This section provides instructions for running the dropAllIndexes.sql script to drop all indexes during the upgrade to release 7.9.6.2. Before you perform this procedure, you must first generate the script, as described in Section B.1, "Generating Scripts to Drop and Create Indexes for Upgrading to Release 7.9.6.2."

To run the script to drop all indexes

1. Open the SQL client for your database type.

2. Navigate to the folder \bifoundation\dac\log\scripts.

3. Open the dropAllIndexes.sql file, and copy the contents into the SQL client.

4. Execute the script.

B.3 Running the Scripts to Create ETL and Query Indexes for Upgrading to Release 7.9.6.2

This section provides instructions for running the createETLIndexes.sql and createQueryIndexes.sql scripts to create indexes during the upgrade to release 7.9.6.2. Before you perform this procedure, you must first generate the scripts, as described in Section B.1, "Generating Scripts to Drop and Create Indexes for Upgrading to Release 7.9.6.2."

To run the script to create ETL and Query indexes

1. Open the SQL client for your database type.

2. Navigate to the folder \bifoundation\dac\log\scripts.

3. Open either the createETLIndexes.sql script or the createQueryIndexes.sql script, depending on the upgrade step you are on.
Note: You must run the createETLIndexes.sql script before you run the Informatica workflows and the createQueryindexes.script after you run the Informatica workflows.

4. Copy the contents of the SQL script into the SQL client.

5. Execute the script.

B.4 Generating Scripts to Drop and Create Query Indexes for Upgrading to Release 7.9.6.3

This section provides instructions for generating scripts to drop and create query indexes. This procedure is applicable when you are upgrading to release 7.9.6.3.

To generate a scripts to drop and create query indexes

1. Go to the folder OracleBI\dwrep\Upgrade\CTLFiles.

2. Open the UPGRADE_7962_to_7963_<source system>.txt file.
This file contains a list of data warehouse tables that were upgraded for this release.

3. Open a text editor, and copy and paste the contents of UPGRADE_7962_to_7963_<source system>.txt into a new file.
Note that table names are separated by a comma (,).

4. Find and replace the comma (,) with OR.
Make sure there is only one space before and after OR. The format of the text string should appear as follows:

table_1 OR table_2 OR table_3 OR table_4

For example:

W_POSITION_D OR W_PURCH_COST_F OR W_EXPENSE_F OR W_PURCH_CYCLE_LINE_A OR W_ORA_GL_LINKAGE_INFO_REVN_TMP OR W_POSITION_DH

5. Open the DAC repository for the release from which you are upgrading. For example, if you are upgrading from release 7.9.6.2 to 7.9.6.3, you would open the release 7.9.6.2 DAC repository

6. From the DAC toolbar, select the appropriate source system container from the drop-down list.

7. In the Design view, click the Indices tab.

8. In the top pane toolbar, click Query.
The top pane window now displays Query mode.

9. Copy the text string from the text file you created in step 5 into the Table Name field.

10. Click Go.

11. In the list of query results, right-click, and then select Generate Index Scripts.

12. Select "All records in the list."

13. In the Generate Index Scripts dialog box, do one of the following:

- To generate index scripts based on a physical data source connection that you previously set up, select the "Use source information" check box, and then select the appropriate physical data source connection from the drop-down list.

- To generate index scripts based on the data warehouse database type, deselect the "Use source information" check box, and then select the appropriate database type.
If the database type is Oracle, enter a table owner, and optionally enter a tablespace in which the indexes will be dropped and created.

If the database type is SQL Server, DB2 or Teradata, enter a table owner.

14. Click OK.
A message box states whether the scripts were successfully generated. The following scripts are saved in the folder \bifoundation\dac\log\scripts:

- dropQueryIndices.sql

- createQueryIndices.sql
Note: Additional files may be generated; however, you will not need to run them.

B.5 Running the Scripts to Drop and Create Query Indexes for Upgrading to Release 7.9.6.3

This section provides instructions for running the dropQueryIndices.sql and createQueryIndices.sql scripts when upgrading to release 7.9.6.3. Before you perform this procedure, you must first generate the scripts, as described in Section B.4, "Generating Scripts to Drop and Create Query Indexes for Upgrading to Release 7.9.6.3."

To run the script to drop or create query indexes

1. Open the SQL client for your database type.

2. Navigate to the folder \bifoundation\dac\log\scripts.

3. Open either the dropQueryIndices.sql script or the createQueryIndices.sql script, depending on the upgrade step you are on.

4. Copy the contents of the SQL script into the SQL client.

5. Execute the script.

B.6 Generating Scripts to Drop and Create Query and ETL Indexes for Upgrading to Release 7.9.6.4

This section provides instructions for generating scripts to drop and create query and ETL indexes for upgrading to release 7.9.6.4.

To generate a scripts to drop and create query and ETL indexes

1. Go to the folder OracleBI\dwrep\Upgrade\CTLFiles.

2. Open the UPGRADE_7963_to_7964_<source system>.txt file.
This file contains a list of data warehouse tables that were upgraded for this release.

3. Open a text editor, and copy and paste the contents of UPGRADE_7963_to_7964_<source system>.txt into a new file.
Note that table names are separated by a comma (,).

4. Find and replace the comma (,) with OR.
Make sure there is only one space before and after OR. The format of the text string should appear as follows:

table_1 OR table_2 OR table_3 OR table_4

For example:

W_POSITION_D OR W_PURCH_COST_F OR W_EXPENSE_F OR W_PURCH_CYCLE_LINE_A OR W_ORA_GL_LINKAGE_INFO_REVN_TMP OR W_POSITION_DH

5. Open the DAC repository for the release from which you are upgrading. For example, if you are upgrading from release 7.9.6.3 to 7.9.6.4, you would open the release 7.9.6.3 DAC repository

6. From the DAC toolbar, select the appropriate source system container from the drop-down list.

7. In the Design view, click the Indices tab.

8. In the top pane toolbar, click Query.
The top pane window now displays Query mode.

9. Copy the text string from the text file you created in step 5 into the Table Name field.

10. Click Go.

11. In the list of query results, right-click, and then select Generate Index Scripts.

12. Select "All records in the list."

13. In the Generate Index Scripts dialog box, do one of the following:

- To generate index scripts based on a physical data source connection that you previously set up, select the "Use source information" check box, and then select the appropriate physical data source connection from the drop-down list.

- To generate index scripts based on the data warehouse database type, deselect the "Use source information" check box, and then select the appropriate database type.
If the database type is Oracle, enter a table owner, and optionally enter a tablespace in which the indexes will be dropped and created.

If the database type is SQL Server, DB2 or Teradata, enter a table owner.

14. Click OK.
A message box states whether the scripts were successfully generated. The following scripts are saved in the folder \bifoundation\dac\log\scripts:

- dropQueryIndices.sql

- createQueryIndices.sql

- dropEtlIndices.sql

- createEtlIndices.sql
Note: Additional files may be generated; however, you will not need to run them.

B.7 Running the Scripts to Drop and Create Query Indexes for Upgrading to Release 7.9.6.4

This section provides instructions for running the dropQueryIndices.sql and createQueryIndices.sql scripts when upgrading to release 7.9.6.4. Before you perform this procedure, you must first generate the scripts, as described in Section B.6, "Generating Scripts to Drop and Create Query and ETL Indexes for Upgrading to Release 7.9.6.4."

To run the script to drop or create query indexes

1. Open the SQL client for your database type.

2. Navigate to the folder \bifoundation\dac\log\scripts.

3. Open either the dropQueryIndices.sql script or the createQueryIndices.sql script, depending on the upgrade step you are on.

4. Copy the contents of the SQL script into the SQL client.

5. Execute the script.

B.8 Running the Scripts to Drop and Create ETL Indexes for Upgrading to Release 7.9.6.4

This section provides instructions for running the dropEtlIndices.sql and createEtlIndices.sql scripts when upgrading to release 7.9.6.4. Before you perform this procedure, you must first generate the scripts, as described in Section B.6, "Generating Scripts to Drop and Create Query and ETL Indexes for Upgrading to Release 7.9.6.4."

Before running the scripts, you need to remove the drop/create statements for certain indexes from the script files (createEtlIndices.sql and dropEtlIndices.sql). These indexes need to be present in the data warehouse during the data upgrade to improve Informatica upgrade map performance. Details of indexes that need to be retained are available in 7964_UPGRADE_IDX_PRESERV.txt. This file is located in the folder OracleBI\dwrep\Upgrade\DbScripts.

To remove the create/drop statements for indexes that need to be retained

1. Open file 7964_UPGRADE_IDX_PRESERV.txt, which is located in the folder OracleBI\dwrep\Upgrade\DbScripts.

2. Navigate to the folder \bifoundation\dac\log\scripts.

3. Back up the file createEtlIndices.sql.

4. Open the file createEtlIndices.sql, and remove the create index statements for the indexes referred to in the file 7964_UPGRADE_IDX_PRESERV.txt.

5. Back up the file dropEtlIndices.sql.

6. Open the file dropEtlIndices.sql, and remove the drop index statements for the indexes referred to in the file 7964_UPGRADE_IDX_PRESERV.txt.

To run the script to drop or create ETL indexes

1. Open the SQL client for your database type.

2. Navigate to the folder \bifoundation\dac\log\scripts.

3. Open either the dropEtlIndices.sql script or the createETLIndices.sql script, depending on the upgrade step you are on.

4. Copy the contents of the SQL script into the SQL client.

5. Execute the script.

C Creating Indexes for Oracle Financial Analytics

This appendix provides information about indexes that should be created to improve performance when using Oracle Financial Analytics. The indexes discussed in this appendix are applicable to Oracle BI Applications release 7.9.6.2.

Note:

After a successful data upgrade, you can drop the indexes referred to in this appendix, except for the ones that already existed in the DAC metadata.

This appendix includes the following topics:

- Section C.1, "Indexes for SIL_PositionDimension_UPD7962 Mapping"

- Section C.2, "Indexes for SIL_PositionDimensionHierarchy_UPD7962 Mapping"

C.1 Indexes for SIL_PositionDimension_UPD7962 Mapping

Make sure the following indexes are created for the SIL_PositionDimension_UPD7962 mapping:

- Primary key index on the ROW_WID column on table W_POSITION_D

- Normal index on the INTEGRATION_ID and DATASOURCE_NUM_ID columns on table W_POSITION_D_7962

C.2 Indexes for SIL_PositionDimensionHierarchy_UPD7962 Mapping

Make sure the following indexes are created for the SIL_PositionDimensionHierarchy_UPD7962 mapping:

- Primary key index on ROW_WID column on table W_POSITION_D

- Primary key index on ROW_WID column on table W_POSITION_DH

- Primary key index on ROW_WID column on table W_POSITION_DH_7962

- Unique index on INTEGRATION_ID, DATASOURCE_NUM_ID, and EFFECTIVE_FROM_DT columns on table W_POSITION_D

- Unique index on BASE_POSTN_ID, DATASOURCE_NUM_ID, and EFFECTIVE_FROM_DT columns on table W_POSITION_DH_7962

D Setting Database-Specific Parameters for the reset_infa_seq_gen.bat File

This appendix contains the following topics:

- Section D.1, "Running reset_infa_seq_gen.bat on Base Informatica Repository"

- Section D.2, "Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle"

- Section D.3, "Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server"

- Section D.4, "Running reset_infa_seq_gen.bat on Upgrade Informatica Repository"

- Section D.5, "Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle"

- Section D.6, "Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server"

D.1 Running reset_infa_seq_gen.bat on Base Informatica Repository

Follow this procedure to run the reset_infa_seq_gen.bat file on the Base informatica Repository if your Oracle Business Analytics Warehouse runs on an Oracle, DB2, or MSSQL Server database.

This section contains the following topics:

- Section D.1.1, "Entering Values for the reset_infa_seq_gen.bat File on the Base Informatica Repository"

- Section D.1.2, "Obtaining ROW_WID from W_ORG_D and W_PRD_OF_WRK_BAND_D"

- Section D.1.3, "Obtaining ROW_WID from W_PARTY_D and W_PRD_OF_WRK_BAND_D"

D.1.1 Entering Values for the reset_infa_seq_gen.bat File on the Base Informatica Repository

Follow this procedure to enter values for the reset_infa_seq_gen.bat file to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

1. Navigate to OracleBI\dwrep\Upgrade\DbScripts\<database type>.

2. Open the reset_infa_seq_gen.bat file.

3. Enter the appropriate parameter values to reflect your environment (the parameters are database specific). See one of the following tables:

- Table D-1, "Oracle Database Parameter Settings for reset_infa_seq_gen.bat"

- Table D-2, "SQL Server Database Parameter Settings for reset_infa_seq_gen.bat"

- Table D-3, "IBM DB2 Database Parameter Settings for reset_infa_seq_gen.bat"

After you complete this step, proceed to one of the following sections:

- Follow the steps in Section D.1.2, "Obtaining ROW_WID from W_ORG_D and W_PRD_OF_WRK_BAND_D" if you are in an upgrade phase in which you are upgrading to Oracle BI Applications version 7.9.0, 7.9.1, 7.9.2, 7.9.3, 7.9.4, 7.9.5, 7.9.5.1, or 7.9.6.

- Follow the steps in Section D.1.3, "Obtaining ROW_WID from W_PARTY_D and W_PRD_OF_WRK_BAND_D" if you are in an upgrade phase in which you are upgrading to Oracle BI Applications version 7.9.6.1, 7.9.6.2, or 7.9.6.3.

Do not execute reset_infa_seq_gen.bat until you have completed the procedures in either Section D.1.2 or Section D.1.3.

Oracle Database Parameter Settings for the Base Informatica Repository

Table D-1 Oracle Database Parameter Settings for reset_infa_seq_gen.bat

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.

OLAP TNS ENTRY

Enter the TNS entry for the data warehouse database.

INFORMATICA SERVER ADDRESS

Enter the host address for the Informatica Service.

INFORMATICA REPOSITORY  DATABASE TNSENTRY

Enter the TNS entry for the Informatica Repository database.

INFORMATICA REPOSITORY DB USERNAME

Enter the user ID of the base Informatica Repository database.

INFORMATICA REPOSITORY DB PASSWORD

Enter the password@connection string of the base InformaticaRepository database.

INFORMATICA REPOSITORY

Enter the name of the base Informatica Repository.

INFORMATICA REPOSITORY USERNAME

Enter the user ID of the base Informatica Repository.

INFORMATICA REPOSITORY PASSWORD

Enter the password for the base Informatica Repository.

INFORMATICA FODLER

For all source systems except Siebel Industry Applications, enter the value HOR.

For Siebel Industry Applications, you need to run reset_infa_seq_gen.bat twice. For the first execution, enter the value VERT. For the second execution, enter the value HOR.

INFORMATICA PORT

Enter the port number for the Repository Service. The default is 6001.

SQL Server Database Parameter Settings for the Base Informatica Repository

Table D-2 SQL Server Database Parameter Settings for reset_infa_seq_gen.bat

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 REPOSITORY DB SERVER ADDRESS

Enter the Informatica Server host address.

INFORMATICA DATABASE

Enter the name of the database in which the base Informatica Repository metadata is available.

INFORMATICA DB USERNAME

Enter the user ID of the base Informatica Repository database.

INFORMATICA DB PASSWORD

Enter the password @connection string of the base Informatica Repository database.

INFORMATICA REPOSITORY SERVER ADDRESS

Enter the name of the machine that runs the Repository Service for the base Repository.

INFORMATICA REPOSITORY USERNAME

Enter the user ID of the base Informatica Repository.

INFORMATICA REPOSITORY PASSWORD

Enter the password of the base Informatica Repository.

INFORMATAICA FOLDER

For all source systems except Siebel Industry Applications, enter the value HOR.

For Siebel Industry Applications, you need to run reset_infa_seq_gen.bat twice. For the first execution, enter the value VERT. For the second execution, enter the value HOR.

INFORMATICA PORT

Enter the port number for the Repository Service. The default is 6001.

IBM DB2 Database Parameter Settings for the Base Informatica Repository

Table D-3 IBM DB2 Database Parameter Settings for reset_infa_seq_gen.bat

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.

INFA DATABASE ALIAS

Enter the name of the database in which Informatica Repository metadata is available.

INFORMATICA DB USERNAME

Enter the user ID of the base Informatica Repository database.

INFORMATICA DB PASSWORD

Enter the password @connection string of the base Informatica Repository database.

INFORMATICA REPOSITORY

Enter the name of the base Informatica Repository.

INFORMATICA REPOSITORY USERNAME

Enter the user ID of the base Informatica Repository.

INFORMATICA REPOSITORY PASSWORD

Enter the password for the base Informatica Repository.

INFORMATICA SERVER ADDRESS

Enter the Informatica Server host address.

INFORMATICA FOLDER

For all source systems except Siebel Industry Applications, enter the value HOR.

For Siebel Industry Applications, you need to run reset_infa_seq_gen.bat twice. For the first execution, enter the value VERT. For the second execution, enter the value HOR.

INFORMATICA PORT

Enter the port number for the Repository Service. The default is 6001.

D.1.2 Obtaining ROW_WID from W_ORG_D and W_PRD_OF_WRK_BAND_D

Follow this procedure to obtain the maximum ROW_WID value from W_ORG_D and from W_PRD_OF_WRK_BAND_D if you are in an upgrade phase in which you are upgrading to Oracle BI Applications version 7.9.0, 7.9.1, 7.9.2, 7.9.3, 7.9.4, 7.9.5, 7.9.5.1, or 7.9.6.

Note: If you are in an upgrade phase in which you are upgrading to Oracle BI Applications version 7.9.6.1, 7.9.6.2, or 7.9.6.3, follow the steps in Section D.1.3, "Obtaining ROW_WID from W_PARTY_D and W_PRD_OF_WRK_BAND_D."

1. Obtain the maximum ROW_WID value from W_ORG_D:

1. In the reset_infa_seq_gen.bat file, go to the end of the file and locate the section similar to

IF %INFA_REP%==UPGRADE echo pmrep Updateseqgenvals -f"UPGRADE_7951_to_796_SBL" -t Seq_W_PARTY_D_Wid -c 1234567 >>sequence_gen_update.bat.

2. In the code example, note the value 1234567. You will replace this value in a following step.

3. On the data warehouse, run the following SQL statement:

SELECT MAX(ROW_WID)+1 FROM W_ORG_D

4. In the reset_infa_seq_gen.bat file, replace the value 1234567 with the value that was returned by the SQL statement.

2. Obtain the maximum ROW_WID value from W_PRD_OF_WRK_BAND_D:

1. In the reset_infa_seq_gen.bat file, go to the end of the file and locate the section similar to:

IF %INFA_REP%==UPGRADE echo pmrep Updateseqgenvals -f"UPGRADE_7951_to_796_SBL" -t Seq_W_PARTY_D_Wid -c 1234567 >>sequence_gen_update.bat.

2. Add the following lines after the section referred to in step a:

IF %INFA_FOLDER%==HOR echo pmrep Updateseqgenvals -f "SILOS" -m SIL_PeriodOfWorkBandDimension -t Seq_3000_Plus_Sequence_Prd_Of_Wrk_Band -c MAX1 >>sequence_gen_update.bat

IF %INFA_FOLDER%==HOR echo pmrep Updateseqgenvals -f "SILOS" -m SIL_PeriodOfWorkBandDimension -t Seq_4000_Plus_Sequence_Prd_Of_Wrk_Band -c MAX2 >>sequence_gen_update.bat

3. In the code example, note the values MAX1 and MAX2. You will replace these values in a following step.

4. On the data warehouse, run the following SQL statements:

select max(ROW_WID)+1 from W_PRD_OF_WRK_BAND_D where level_id = 'POW_BAND_EMP'

The value returned from the SQL statement above corresponds to MAX1.

select max(ROW_WID)+1 from W_PRD_OF_WRK_BAND_D where level_id = 'POW_BAND_CWK'

The value returned from the SQL statement above corresponds to MAX2.

5. In the reset_infa_seq_gen.bat file, replace the values MAX1 and MAX2 with the values returned by the SQL statements.

3. Execute reset_infa_seq_gen.bat.

D.1.3 Obtaining ROW_WID from W_PARTY_D and W_PRD_OF_WRK_BAND_D

Follow this procedure to obtain the maximum ROW_WID value from W_PARTY_D and from W_PRD_OF_WRK_BAND_D if you are in an upgrade phase in which you are upgrading to Oracle BI Applications version 7.9.6.1, 7.9.6.2, or 7.9.6.3.

Note: If you are in an upgrade phase in which you are upgrading to Oracle BI Applications version 7.9.0, 7.9.1, 7.9.2, 7.9.3, 7.9.4, 7.9.5, 7.9.5.1, or 7.9.6, follow the steps in Section D.1.2, "Obtaining ROW_WID from W_ORG_D and W_PRD_OF_WRK_BAND_D."

1. Obtain the maximum ROW_WID value from W_ORG_D:

1. In the reset_infa_seq_gen.bat file, go to the end of the file and locate the section similar to

IF %INFA_REP%==UPGRADE echo pmrep Updateseqgenvals -f"UPGRADE_7951_to_796_SBL" -t Seq_W_PARTY_D_Wid -c 1234567 >>sequence_gen_update.bat.

2. In the code example, note the value 1234567. You will replace this value in a following step.

3. On the data warehouse, run the following SQL statement:

SELECT MAX(ROW_WID)+1 FROM W_PARTY_D

4. In the reset_infa_seq_gen.bat file, replace the value 1234567 with the value that was returned by the SQL statement.

2. Obtain the maximum ROW_WID value from W_PRD_OF_WRK_BAND_D:

1. In the reset_infa_seq_gen.bat file, go to the end of the file and locate the section similar to:

IF %INFA_REP%==UPGRADE echo pmrep Updateseqgenvals -f"UPGRADE_7951_to_796_SBL" -t Seq_W_PARTY_D_Wid -c 1234567 >>sequence_gen_update.bat.

2. Add the following lines after the section referred to in step a:

IF %INFA_FOLDER%==HOR echo pmrep Updateseqgenvals -f "SILOS" -m SIL_PeriodOfWorkBandDimension -t Seq_3000_Plus_Sequence_Prd_Of_Wrk_Band -c MAX1 >>sequence_gen_update.bat

IF %INFA_FOLDER%==HOR echo pmrep Updateseqgenvals -f "SILOS" -m SIL_PeriodOfWorkBandDimension -t Seq_4000_Plus_Sequence_Prd_Of_Wrk_Band -c MAX2 >>sequence_gen_update.bat

3. In the code example, note the values MAX1 and MAX2. You will replace these values in a following step.

4. On the data warehouse, run the following SQL statements:

select max(ROW_WID)+1 from W_PRD_OF_WRK_BAND_D where level_id = 'POW_BAND_EMP'

The value returned from the SQL statement above corresponds to MAX1.

select max(ROW_WID)+1 from W_PRD_OF_WRK_BAND_D where level_id = 'POW_BAND_CWK'

The value returned from the SQL statement above corresponds to MAX2.

5. In the reset_infa_seq_gen.bat file, replace the values MAX1 and MAX2 with the values returned by the SQL statements.

3. Execute reset_infa_seq_gen.bat.

D.2 Running reset_infa_seq_gen_ORA.bat on Base Repository for DW on Teradata and Repository on Oracle

Follow this procedure if your Oracle Business Analytics Warehouse is on a Teradata database and your Informatica Repository is on an Oracle database.

This section contains the following topics:

- Section D.2.1, "Entering Values for the reset_infa_seq_gen_ORA.bat File on the Base Informatica Repository"

- Section D.2.2, "Obtaining ROW_WID from W_ORG_D and W_PRD_OF_WRK_BAND_D"

- Section D.2.3, "Obtaining ROW_WID from W_PARTY_D and W_PRD_OF_WRK_BAND_D"

D.2.1 Entering Values for the reset_infa_seq_gen_ORA.bat File on the Base Informatica Repository

Follow this procedure to enter values for the reset_infa_seq_gen_ORA.bat file to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

1. Navigate to OracleBI\dwrep\Upgrade\DbScripts\Teradata.

2. Open the reset_infa_seq_gen_ORA.bat file.

3. Enter the appropriate parameter values to reflect your environment (the parameters are database specific).

Table D-4 Teradata Database Parameter Settings for reset_infa_seq_gen_ORA.bat

Parameter

Setting

OLAP_SERVER

Enter the name of the Teradata Server for the data warehouse 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 password of the data warehouse database.

INFORMATICA SERVER ADDRESS

Enter the Informatica Server host address.

INFORMATICA REPOSITORY DB USERNAME

Enter the user ID of the base Informatica Repository database.

INFORMATICA REPOSITORY DB PASSWORD

Enter the password @connection string of the base Informatica Repository database.

INFORMATICA REPOSITORY

Enter the name of the base Informatica Repository.

INFORMATICA REPOSITORY USERNAME

Enter the user ID of the base Informatica Repository.

INFORMATICA REPOSITORY PASSWORD

Enter the password for the base Informatica Repository.

INFORMATICA FOLDER

For all source systems except Siebel Industry Applications, enter the value HOR.

For Siebel Industry Applications, you need to run reset_infa_seq_gen_ORA.bat twice. For the first execution, enter the value VERT. For the second execution, enter the value HOR.

INFORMATICA PORT

Enter the port number for the Repository Service. The default is 6001.

After you complete this step, proceed to one of the following sections:

- Follow the steps in Section D.2.2, "Obtaining ROW_WID from W_ORG_D and W_PRD_OF_WRK_BAND_D" if you are in an upgrade phase in which you are upgrading to Oracle BI Applications version 7.9.0, 7.9.1, 7.9.2, 7.9.3, 7.9.4, 7.9.5, 7.9.5.1, or 7.9.6.

- Follow the steps in Section D.2.3, "Obtaining ROW_WID from W_PARTY_D and W_PRD_OF_WRK_BAND_D" if you are in an upgrade phase in which you are upgrading to Oracle BI Applications version 7.9.6.1, 7.9.6.2, or 7.9.6.3.

Do not execute reset_infa_seq_gen_ORA.bat until you have completed the procedures in either Section D.2.2 or Section D.2.3.

D.2.2 Obtaining ROW_WID from W_ORG_D and W_PRD_OF_WRK_BAND_D

Follow this procedure to obtain the maximum ROW_WID value from W_ORG_D and from W_PRD_OF_WRK_BAND_D if you are in an upgrade phase in which you are upgrading to Oracle BI Applications version 7.9.0, 7.9.1, 7.9.2, 7.9.3, 7.9.4, 7.9.5, 7.9.5.1, or 7.9.6.

Note: If you are in an upgrade phase in which you are upgrading to Oracle BI Applications version 7.9.6.1, 7.9.6.2, or 7.9.6.3, follow the steps in Section D.2.3, "Obtaining ROW_WID from W_PARTY_D and W_PRD_OF_WRK_BAND_D."

1. Obtain the maximum ROW_WID value from W_ORG_D:

1. In the reset_infa_seq_gen_ORA.bat file, go to the end of the file and locate the section similar to

IF %INFA_REP%==UPGRADE echo pmrep Updateseqgenvals -f"UPGRADE_7951_to_796_SBL" -t Seq_W_PARTY_D_Wid -c 1234567 >>sequence_gen_update.bat.

2. In the code example, note the value 1234567. You will replace this value in a following step.

3. On the data warehouse, run the following SQL statement:

SELECT MAX(ROW_WID)+1 FROM W_ORG_D

4. In the reset_infa_seq_gen_ORA.bat file, replace the value 1234567 with the value that was returned by the SQL statement.

2. Obtain the maximum ROW_WID value from W_PRD_OF_WRK_BAND_D:

1. In the reset_infa_seq_gen_ORA.bat file, go to the end of the file and locate the section similar to:

IF %INFA_REP%==UPGRADE echo pmrep Updateseqgenvals -f"UPGRADE_7951_to_796_SBL" -t Seq_W_PARTY_D_Wid -c 1234567 >>sequence_gen_update.bat.

2. Add the following lines after the section referred to in step a:

IF %INFA_FOLDER%==HOR echo pmrep Updateseqgenvals -f "SILOS" -m SIL_PeriodOfWorkBandDimension -t Seq_3000_Plus_Sequence_Prd_Of_Wrk_Band -c MAX1 >>sequence_gen_update.bat

IF %INFA_FOLDER%==HOR echo pmrep Updateseqgenvals -f "SILOS" -m SIL_PeriodOfWorkBandDimension -t Seq_4000_Plus_Sequence_Prd_Of_Wrk_Band -c MAX2 >>sequence_gen_update.bat

3. In the code example, note the values MAX1 and MAX2. You will replace these values in a following step.

4. On the data warehouse, run the following SQL statements:

select max(ROW_WID)+1 from W_PRD_OF_WRK_BAND_D where level_id = 'POW_BAND_EMP'

The value returned from the SQL statement above corresponds to MAX1.

select max(ROW_WID)+1 from W_PRD_OF_WRK_BAND_D where level_id = 'POW_BAND_CWK'

The value returned from the SQL statement above corresponds to MAX2.

5. In the reset_infa_seq_gen_ORA.bat file, replace the values MAX1 and MAX2 with the values returned by the SQL statements.

3. Execute reset_infa_seq_gen_ORA.bat.

D.2.3 Obtaining ROW_WID from W_PARTY_D and W_PRD_OF_WRK_BAND_D

Follow this procedure to obtain the maximum ROW_WID value from W_PARTY_D and from W_PRD_OF_WRK_BAND_D if you are in an upgrade phase in which you are upgrading to Oracle BI Applications version 7.9.6.1, 7.9.6.2, or 7.9.6.3.

Note: If you are in an upgrade phase in which you are upgrading to Oracle BI Applications version 7.9.0, 7.9.1, 7.9.2, 7.9.3, 7.9.4, 7.9.5, 7.9.5.1, or 7.9.6, follow the steps in Section D.2.2, "Obtaining ROW_WID from W_ORG_D and W_PRD_OF_WRK_BAND_D."

1. Obtain the maximum ROW_WID value from W_ORG_D:

1. In the reset_infa_seq_gen_ORA.bat file, go to the end of the file and locate the section similar to

IF %INFA_REP%==UPGRADE echo pmrep Updateseqgenvals -f"UPGRADE_7951_to_796_SBL" -t Seq_W_PARTY_D_Wid -c 1234567 >>sequence_gen_update.bat.

2. In the code example, note the value 1234567. You will replace this value in a following step.

3. On the data warehouse, run the following SQL statement:

SELECT MAX(ROW_WID)+1 FROM W_PARTY_D

4. In the reset_infa_seq_gen_ORA.bat file, replace the value 1234567 with the value that was returned by the SQL statement.

2. Obtain the maximum ROW_WID value from W_PRD_OF_WRK_BAND_D:

1. In the reset_infa_seq_gen_ORA.bat file, go to the end of the file and locate the section similar to:

IF %INFA_REP%==UPGRADE echo pmrep Updateseqgenvals -f"UPGRADE_7951_to_796_SBL" -t Seq_W_PARTY_D_Wid -c 1234567 >>sequence_gen_update.bat.

2. Add the following lines after the section referred to in step a:

IF %INFA_FOLDER%==HOR echo pmrep Updateseqgenvals -f "SILOS" -m SIL_PeriodOfWorkBandDimension -t Seq_3000_Plus_Sequence_Prd_Of_Wrk_Band -c MAX1 >>sequence_gen_update.bat

IF %INFA_FOLDER%==HOR echo pmrep Updateseqgenvals -f "SILOS" -m SIL_PeriodOfWorkBandDimension -t Seq_4000_Plus_Sequence_Prd_Of_Wrk_Band -c MAX2 >>sequence_gen_update.bat

3. In the code example, note the values MAX1 and MAX2. You will replace these values in a following step.

4. On the data warehouse, run the following SQL statements:

select max(ROW_WID)+1 from W_PRD_OF_WRK_BAND_D where level_id = 'POW_BAND_EMP'

The value returned from the SQL statement above corresponds to MAX1.

select max(ROW_WID)+1 from W_PRD_OF_WRK_BAND_D where level_id = 'POW_BAND_CWK'

The value returned from the SQL statement above corresponds to MAX2.

5. In the reset_infa_seq_gen_ORA.bat file, replace the values MAX1 and MAX2 with the values returned by the SQL statements.

3. Execute reset_infa_seq_gen_ORA.bat.

D.3 Running reset_infa_seq_gen_MSSQL.bat on Base Repository for DW on Teradata and Repository on MSSQL Server

Follow this procedure if your Oracle Business Analytics Warehouse is on a Teradata database and your Informatica Repository is on an MSSQL Server database.

This section contains the following topics:

- Section D.3.1, "Entering Values for the reset_infa_seq_gen_MSSQL.bat File on the Base Informatica Repository"

- Section D.3.2, "Obtaining ROW_WID from W_ORG_D and W_PRD_OF_WRK_BAND_D"

- Section D.3.3, "Obtaining ROW_WID from W_PARTY_D and W_PRD_OF_WRK_BAND_D"

D.3.1 Entering Values for the reset_infa_seq_gen_MSSQL.bat File on the Base Informatica Repository

Follow this procedure to enter values for the reset_infa_seq_gen_MSSQL.bat file to initialize the Informatica sequence generator for incremental runs on the base Informatica Repository (for example, Oracle_BI_DW_Base.rep).

1. Navigate to OracleBI\dwrep\Upgrade\DbScripts\Teradata.

2. Open the reset_infa_seq_gen_MSSQL.bat file.

3. Enter the appropriate parameter values to reflect your environment (the parameters are database specific).

Table D-5 Teradata Database Parameter Settings for reset_infa_seq_gen_MSSQL.bat

Parameter

Setting

OLAP_SERVER

Enter the name of the Teradata 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 password of the data warehouse database.

INFORMATICA REPOSITORY SERVER ADDRESS

Enter the Informatica Repository Service host address.

INFORMATICA REPOSITORY DB SERVER ADDRESS

Enter the database address for the Informatica Repository database server in the format <MSSQL Server address>,<port number>

For example: tcp:192.168.01.2,20100

or tcp:MSSQL2005DBA,20100

INFORMATICA REPOSITORY DATABASE

Name of the Informatica Repository database.

INFORMATICA REPOSITORY DB USERNAME

Enter the user ID of the base Informatica Repository database.

INFORMATICA REPOSITORY DB PASSWORD

Enter the password @connection string of the base Informatica Repository database.

INFORMATICA REPOSITORY

Enter the name of the base Informatica Repository.

INFORMATICA REPOSITORY USERNAME

Enter the user ID of the base Informatica Repository.

INFORMATICA REPOSITORY PASSWORD

Enter the password for the base Informatica Repository.

INFORMATICA FOLDER

For all source systems except Siebel Industry Applications, enter the value HOR.

For Siebel Industry Applications, you need to run reset_infa_seq_gen_MSSQL.bat twice. For the first execution, enter the value VERT. For the second execution, enter the value HOR.

INFORMATICA PORT

Enter the port number for the Repository Service. The default is 6001.

After you complete this step, proceed to one of the following sections:

- Follow the steps in Section D.3.2, "Obtaining ROW_WID from W_ORG_D and W_PRD_OF_WRK_BAND_D" if you are in an upgrade phase in which you are upgrading to Oracle BI Applications version 7.9.0, 7.9.1, 7.9.2, 7.9.3, 7.9.4, 7.9.5, 7.9.5.1, or 7.9.6.

- Follow the steps in Section D.3.3, "Obtaining ROW_WID from W_PARTY_D and W_PRD_OF_WRK_BAND_D" if you are in an upgrade phase in which you are upgrading to Oracle BI Applications version 7.9.6.1, 7.9.6.2, or 7.9.6.3.

Do not execute reset_infa_seq_gen_MSSQL.bat until you have completed the procedures in either Section D.3.2 or Section D.3.3.

D.3.2 Obtaining ROW_WID from W_ORG_D and W_PRD_OF_WRK_BAND_D

Follow this procedure to obtain the maximum ROW_WID value from W_ORG_D and from W_PRD_OF_WRK_BAND_D if you are in an upgrade phase in which you are upgrading to Oracle BI Applications version 7.9.0, 7.9.1, 7.9.2, 7.9.3, 7.9.4, 7.9.5, 7.9.5.1, or 7.9.6.

Note: If you are in an upgrade phase in which you are upgrading to Oracle BI Applications version 7.9.6.1, 7.9.6.2, or 7.9.6.3, follow the steps in Section D.3.3, "Obtaining ROW_WID from W_PARTY_D and W_PRD_OF_WRK_BAND_D."

1. Obtain the maximum ROW_WID value from W_ORG_D:

1. In the reset_infa_seq_gen_MSSQL.bat file, go to the end of the file and locate the section similar to

IF %INFA_REP%==UPGRADE echo pmrep Updateseqgenvals -f"UPGRADE_7951_to_796_SBL" -t Seq_W_PARTY_D_Wid -c 1234567 >>sequence_gen_update.bat.

2. In the code example, note the value 1234567. You will replace this value in a following step.

3. On the data warehouse, run the following SQL statement:

SELECT MAX(ROW_WID)+1 FROM W_ORG_D

4. In the reset_infa_seq_gen_MSSQL.bat file, replace the value 1234567 with the value that was returned by the SQL statement.

2. Obtain the maximum ROW_WID value from W_PRD_OF_WRK_BAND_D:

1. In the reset_infa_seq_gen_MSSQL.bat file, go to the end of the file and locate the section similar to:

IF %INFA_REP%==UPGRADE echo pmrep Updateseqgenvals -f"UPGRADE_7951_to_796_SBL" -t Seq_W_PARTY_D_Wid -c 1234567 >>sequence_gen_update.bat.

2. Add the following lines after the section referred to in step a:

IF %INFA_FOLDER%==HOR echo pmrep Updateseqgenvals -f "SILOS" -m SIL_PeriodOfWorkBandDimension -t Seq_3000_Plus_Sequence_Prd_Of_Wrk_Band -c MAX1 >>sequence_gen_update.bat

IF %INFA_FOLDER%==HOR echo pmrep Updateseqgenvals -f "SILOS" -m SIL_PeriodOfWorkBandDimension -t Seq_4000_Plus_Sequence_Prd_Of_Wrk_Band -c MAX2 >>sequence_gen_update.bat

3. In the code example, note the values MAX1 and MAX2. You will replace these values in a following step.

4. On the data warehouse, run the following SQL statements:

select max(ROW_WID)+1 from W_PRD_OF_WRK_BAND_D where level_id = 'POW_BAND_EMP'

The value returned from the SQL statement above corresponds to MAX1.

select max(ROW_WID)+1 from W_PRD_OF_WRK_BAND_D where level_id = 'POW_BAND_CWK'

The value returned from the SQL statement above corresponds to MAX2.

5. In the reset_infa_seq_gen_MSSQL.bat file, replace the values MAX1 and MAX2 with the values returned by the SQL statements.

3. Execute reset_infa_seq_gen_MSSQL.bat.

D.3.3 Obtaining ROW_WID from W_PARTY_D and W_PRD_OF_WRK_BAND_D

Follow this procedure to obtain the maximum ROW_WID value from W_PARTY_D and from W_PRD_OF_WRK_BAND_D if you are in an upgrade phase in which you are upgrading to Oracle BI Applications version 7.9.6.1, 7.9.6.2, or 7.9.6.3.

Note: If you are in an upgrade phase in which you are upgrading to Oracle BI Applications version 7.9.0, 7.9.1, 7.9.2, 7.9.3, 7.9.4, 7.9.5, 7.9.5.1, or 7.9.6, follow the steps in Section D.3.2, "Obtaining ROW_WID from W_ORG_D and W_PRD_OF_WRK_BAND_D."

1. Obtain the maximum ROW_WID value from W_ORG_D:

1. In the reset_infa_seq_gen_MSSQL.bat file, go to the end of the file and locate the section similar to

IF %INFA_REP%==UPGRADE echo pmrep Updateseqgenvals -f"UPGRADE_7951_to_796_SBL" -t Seq_W_PARTY_D_Wid -c 1234567 >>sequence_gen_update.bat.

2. In the code example, note the value 1234567. You will replace this value in a following step.

3. On the data warehouse, run the following SQL statement:

SELECT MAX(ROW_WID)+1 FROM W_PARTY_D

4. In the reset_infa_seq_gen_MSSQL.bat file, replace the value 1234567 with the value that was returned by the SQL statement.

2. Obtain the maximum ROW_WID value from W_PRD_OF_WRK_BAND_D:

1. In the reset_infa_seq_gen_MSSQL.bat file, go to the end of the file and locate the section similar to:

IF %INFA_REP%==UPGRADE echo pmrep Updateseqgenvals -f"UPGRADE_7951_to_796_SBL" -t Seq_W_PARTY_D_Wid -c 1234567 >>sequence_gen_update.bat.

2. Add the following lines after the section referred to in step a:

IF %INFA_FOLDER%==HOR echo pmrep Updateseqgenvals -f "SILOS" -m SIL_PeriodOfWorkBandDimension -t Seq_3000_Plus_Sequence_Prd_Of_Wrk_Band -c MAX1 >>sequence_gen_update.bat

IF %INFA_FOLDER%==HOR echo pmrep Updateseqgenvals -f "SILOS" -m SIL_PeriodOfWorkBandDimension -t Seq_4000_Plus_Sequence_Prd_Of_Wrk_Band -c MAX2 >>sequence_gen_update.bat

3. In the code example, note the values MAX1 and MAX2. You will replace these values in a following step.

4. On the data warehouse, run the following SQL statements:

select max(ROW_WID)+1 from W_PRD_OF_WRK_BAND_D where level_id = 'POW_BAND_EMP'

The value returned from the SQL statement above corresponds to MAX1.

select max(ROW_WID)+1 from W_PRD_OF_WRK_BAND_D where level_id = 'POW_BAND_CWK'

The value returned from the SQL statement above corresponds to MAX2.

5. In the reset_infa_seq_gen_MSSQL.bat file, replace the values MAX1 and MAX2 with the values returned by the SQL statements.

3. Execute reset_infa_seq_gen_MSSQL.bat.

D.4 Running reset_infa_seq_gen.bat on Upgrade Informatica Repository

Follow this procedure to run the reset_infa_seq_gen.bat file on the Base informatica Repository if your Oracle Business Analytics Warehouse runs on an Oracle, DB2, or MSSQL Server database.

This section contains the following topics:

- Section D.4.1, "Entering Values for the reset_infa_seq_gen.bat File on the Upgrade Informatica Repository"

- Section D.4.2, "Obtaining ROW_WID from W_ORG_D and W_PRD_OF_WRK_BAND_D"

- Section D.4.3, "Obtaining ROW_WID from W_PARTY_D and W_PRD_OF_WRK_BAND_D"

D.4.1 Entering Values for the reset_infa_seq_gen.bat File on the Upgrade Informatica Repository

Follow this procedure to run the reset_infa_seq_gen.bat file to initialize the Informatica sequence generator for incremental runs on the Upgrade repository if your Oracle Business Analytics Warehouse runs on an Oracle, DB2, or MSSQL Server database.

1. Navigate to OracleBI\dwrep\Upgrade\DbScripts\<database type>.

2. Open the reset_infa_seq_gen.bat file.

3. Enter the appropriate parameter values to reflect your environment (the parameters are database specific). See one of the following tables:

- Table D-6, "Oracle Database Parameter Settings for reset_infa_seq_gen.bat"

- Table D-7, "SQL Server Database Parameter Settings for reset_infa_seq_gen.bat"

- Table D-8, "IBM DB2 Database Parameter Settings for reset_infa_seq_gen.bat"

After you complete this step, proceed to one of the following sections:

- Follow the steps in Section D.4.2, "Obtaining ROW_WID from W_ORG_D and W_PRD_OF_WRK_BAND_D" if you are in an upgrade phase in which you are upgrading to Oracle BI Applications version 7.9.0, 7.9.1, 7.9.2, 7.9.3, 7.9.4, 7.9.5, 7.9.5.1, or 7.9.6.

- Follow the steps in Section D.4.3, "Obtaining ROW_WID from W_PARTY_D and W_PRD_OF_WRK_BAND_D" if you are in an upgrade phase in which you are upgrading to Oracle BI Applications version 7.9.6.1, 7.9.6.2, or 7.9.6.3.

Do not execute reset_infa_seq_gen.bat until you have completed the procedures in either Section D.4.2 or Section D.4.3.

Oracle Database Parameter Settings for the Upgrade Informatica Repository

Table D-6 Oracle Database Parameter Settings for reset_infa_seq_gen.bat

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 SERVER ADDRESS

Enter the Informatica Server host address.

INFORMATICA DATABASE TNSENTRY

Enter the TNS entry for the Informatica Server database.

INFORMATICA DB USERNAME

Enter the user ID of the upgrade Informatica Repository database.

INFORMATICA DB PASSWORD

Enter the password@connection string of the upgrade InformaticaRepository database.

INFORMATICA REPOSITORY

Enter the name of the upgrade Informatica Repository.

INFORMATICA REPOSITORY USERNAME

Enter the user ID of the upgrade Informatica Repository.

INFORMATICA REPOSITORY PASSWORD

Enter the password for the upgrade Informatica Repository.

INFORMATICA FODLER

Enter the value UPGRADE

INFORMATICA PORT

Enter the port number for the Repository Service. The default is 6001.

SQL Server Database Parameter Settings for the Upgrade Informatica Repository

Table D-7 SQL Server Database Parameter Settings for reset_infa_seq_gen.bat

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 DB SERVER ADDRESS

Enter the Informatica Server host address.

INFORMATICA DATABASE

Enter the name of the database in which the upgrade Informatica Repository metadata is available.

INFORMATICA DB USERNAME

Enter the user ID of the upgrade Informatica Repository database.

INFORMATICA DB PASSWORD

Enter the password @connection string of the upgrade Informatica Repository database.

INFORMATICA REPOSITORY SERVER ADDRESS

Enter the name of the machine that runs the Repository Service for the upgrade Repository.

INFORMATICA REPOSITORY USERNAME

Enter the user ID of the upgrade Informatica Repository.

INFORMATICA REPOSITORY PASSWORD

Enter the password of the upgrade Informatica Repository.

INFORMATAICA FOLDER

Enter the value UPGRADE

INFORMATICA PORT

Enter the port number for the Repository Service. The default is 6001.

IBM DB2 Database Parameter Settings for the Upgrade Informatica Repository

Table D-8 IBM DB2 Database Parameter Settings for reset_infa_seq_gen.bat

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.

INFA DATABASE ALIAS

Enter the name of the database in which Informatica Repository metadata is available.

INFORMATICA DB USERNAME

Enter the user ID of the upgrade Informatica Repository database.

INFORMATICA DB PASSWORD

Enter the password @connection string of the upgrade Informatica Repository database.

INFORMATICA REPOSITORY

Enter the name of the upgrade Informatica Repository.

INFORMATICA REPOSITORY USERNAME

Enter the user ID of the upgrade Informatica Repository.

INFORMATICA REPOSITORY PASSWORD

Enter the password for the upgrade Informatica Repository.

INFORMATICA SERVER ADDRESS

Enter the Informatica Server host address.

INFORMATICA FOLDER

Enter the value UPGRADE

INFORMATICA PORT

Enter the port number for the Repository Service. The default is 6001.

D.4.2 Obtaining ROW_WID from W_ORG_D and W_PRD_OF_WRK_BAND_D

Follow this procedure to obtain the maximum ROW_WID value from W_ORG_D and from W_PRD_OF_WRK_BAND_D if you are in an upgrade phase in which you are upgrading to Oracle BI Applications version 7.9.0, 7.9.1, 7.9.2, 7.9.3, 7.9.4, 7.9.5, 7.9.5.1, or 7.9.6.

Note: If you are in an upgrade phase in which you are upgrading to Oracle BI Applications version 7.9.6.1, 7.9.6.2, or 7.9.6.3, follow the steps in Section D.4.3, "Obtaining ROW_WID from W_PARTY_D and W_PRD_OF_WRK_BAND_D."

1. Obtain the maximum ROW_WID value from W_ORG_D:

1. In the reset_infa_seq_gen.bat file, go to the end of the file and locate the section similar to

IF %INFA_REP%==UPGRADE echo pmrep Updateseqgenvals -f"UPGRADE_7951_to_796_SBL" -t Seq_W_PARTY_D_Wid -c 1234567 >>sequence_gen_update.bat.

2. In the code example, note the value 1234567. You will replace this value in a following step.

3. On the data warehouse, run the following SQL statement:

SELECT MAX(ROW_WID)+1 FROM W_ORG_D

4. In the reset_infa_seq_gen.bat file, replace the value 1234567 with the value that was returned by the SQL statement.

2. Obtain the maximum ROW_WID value from W_PRD_OF_WRK_BAND_D:

1. In the reset_infa_seq_gen.bat file, go to the end of the file and locate the section similar to:

IF %INFA_REP%==UPGRADE echo pmrep Updateseqgenvals -f"UPGRADE_7951_to_796_SBL" -t Seq_W_PARTY_D_Wid -c 1234567 >>sequence_gen_update.bat.

2. Add the following lines after the section referred to in step a:

IF %INFA_FOLDER%==HOR echo pmrep Updateseqgenvals -f "SILOS" -m SIL_PeriodOfWorkBandDimension -t Seq_3000_Plus_Sequence_Prd_Of_Wrk_Band -c MAX1 >>sequence_gen_update.bat

IF %INFA_FOLDER%==HOR echo pmrep Updateseqgenvals -f "SILOS" -m SIL_PeriodOfWorkBandDimension -t Seq_4000_Plus_Sequence_Prd_Of_Wrk_Band -c MAX2 >>sequence_gen_update.bat

3. In the code example, note the values MAX1 and MAX2. You will replace these values in a following step.

4. On the data warehouse, run the following SQL statements:

select max(ROW_WID)+1 from W_PRD_OF_WRK_BAND_D where level_id = 'POW_BAND_EMP'

The value returned from the SQL statement above corresponds to MAX1.

select max(ROW_WID)+1 from W_PRD_OF_WRK_BAND_D where level_id = 'POW_BAND_CWK'

The value returned from the SQL statement above corresponds to MAX2.

5. In the reset_infa_seq_gen.bat file, replace the values MAX1 and MAX2 with the values returned by the SQL statements.

3. Execute reset_infa_seq_gen.bat.

D.4.3 Obtaining ROW_WID from W_PARTY_D and W_PRD_OF_WRK_BAND_D

Follow this procedure to obtain the maximum ROW_WID value from W_PARTY_D and from W_PRD_OF_WRK_BAND_D if you are in an upgrade phase in which you are upgrading to Oracle BI Applications version 7.9.6.1, 7.9.6.2, or 7.9.6.3.

Note: If you are in an upgrade phase in which you are upgrading to Oracle BI Applications version 7.9.0, 7.9.1, 7.9.2, 7.9.3, 7.9.4, 7.9.5, 7.9.5.1, or 7.9.6, follow the steps in Section D.4.2, "Obtaining ROW_WID from W_ORG_D and W_PRD_OF_WRK_BAND_D."

1. Obtain the maximum ROW_WID value from W_ORG_D:

1. In the reset_infa_seq_gen.bat file, go to the end of the file and locate the section similar to

IF %INFA_REP%==UPGRADE echo pmrep Updateseqgenvals -f"UPGRADE_7951_to_796_SBL" -t Seq_W_PARTY_D_Wid -c 1234567 >>sequence_gen_update.bat.

2. In the code example, note the value 1234567. You will replace this value in a following step.

3. On the data warehouse, run the following SQL statement:

SELECT MAX(ROW_WID)+1 FROM W_PARTY_D

4. In the reset_infa_seq_gen.bat file, replace the value 1234567 with the value that was returned by the SQL statement.

2. Obtain the maximum ROW_WID value from W_PRD_OF_WRK_BAND_D:

1. In the reset_infa_seq_gen.bat file, go to the end of the file and locate the section similar to:

IF %INFA_REP%==UPGRADE echo pmrep Updateseqgenvals -f"UPGRADE_7951_to_796_SBL" -t Seq_W_PARTY_D_Wid -c 1234567 >>sequence_gen_update.bat.

2. Add the following lines after the section referred to in step a:

IF %INFA_FOLDER%==HOR echo pmrep Updateseqgenvals -f "SILOS" -m SIL_PeriodOfWorkBandDimension -t Seq_3000_Plus_Sequence_Prd_Of_Wrk_Band -c MAX1 >>sequence_gen_update.bat

IF %INFA_FOLDER%==HOR echo pmrep Updateseqgenvals -f "SILOS" -m SIL_PeriodOfWorkBandDimension -t Seq_4000_Plus_Sequence_Prd_Of_Wrk_Band -c MAX2 >>sequence_gen_update.bat

3. In the code example, note the values MAX1 and MAX2. You will replace these values in a following step.

4. On the data warehouse, run the following SQL statements:

select max(ROW_WID)+1 from W_PRD_OF_WRK_BAND_D where level_id = 'POW_BAND_EMP'

The value returned from the SQL statement above corresponds to MAX1.

select max(ROW_WID)+1 from W_PRD_OF_WRK_BAND_D where level_id = 'POW_BAND_CWK'

The value returned from the SQL statement above corresponds to MAX2.

5. In the reset_infa_seq_gen.bat file, replace the values MAX1 and MAX2 with the values returned by the SQL statements.

3. Execute reset_infa_seq_gen.bat.

D.5 Running reset_infa_seq_gen_ORA.bat on Upgrade Repository for DW on Teradata and Repository on Oracle

Follow this procedure if your Oracle Business Analytics Warehouse is on a Teradata database and your Informatica Repository is on an Oracle database.

This section contains the following topics:

- Section D.5.1, "Entering Values for the reset_infa_seq_gen_ORA.bat File on the Upgrade Informatica Repository"

- Section D.5.2, "Obtaining ROW_WID from W_ORG_D and W_PRD_OF_WRK_BAND_D"

- Section D.5.3, "Obtaining ROW_WID from W_PARTY_D and W_PRD_OF_WRK_BAND_D"

D.5.1 Entering Values for the reset_infa_seq_gen_ORA.bat File on the Upgrade Informatica Repository

Follow this procedure to enter values for the reset_infa_seq_gen_ORA.bat file to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

1. Navigate to OracleBI\dwrep\Upgrade\DbScripts\Teradata.

2. Open the reset_infa_seq_gen_ORA.bat file.

3. Enter the appropriate parameter values to reflect your environment (the parameters are database specific).

Table D-9 Teradata Database Parameter Settings for reset_infa_seq_gen_ORA.bat

Parameter

Setting

OLAP_SERVER

Enter the name of the Teradata 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 password of the data warehouse database.

INFORMATICA SERVER ADDRESS

Enter the Informatica Server host address.

INFORMATICA REPOSITORY DB USERNAME

Enter the user ID of the Upgrade Informatica Repository database.

INFORMATICA REPOSITORY DB PASSWORD

Enter the password @connection string of the Upgrade Informatica Repository database.

INFORMATICA REPOSITORY

Enter the name of the Upgrade Informatica Repository.

INFORMATICA REPOSITORY USERNAME

Enter the user ID of the Upgrade Informatica Repository.

INFORMATICA REPOSITORY PASSWORD

Enter the password for the Upgrade Informatica Repository.

INFORMATICA FOLDER

For all source systems except Siebel Industry Applications, enter the value HOR.

For Siebel Industry Applications, you need to run reset_infa_seq_gen_ORA.bat twice. For the first execution, enter the value VERT. For the second execution, enter the value HOR.

INFORMATICA PORT

Enter the port number for the Repository Service. The default is 6001.

After you complete this step, proceed to one of the following sections:

- Follow the steps in Section D.5.2, "Obtaining ROW_WID from W_ORG_D and W_PRD_OF_WRK_BAND_D" if you are in an upgrade phase in which you are upgrading to Oracle BI Applications version 7.9.0, 7.9.1, 7.9.2, 7.9.3, 7.9.4, 7.9.5, 7.9.5.1, or 7.9.6.

- Follow the steps in Section D.5.3, "Obtaining ROW_WID from W_PARTY_D and W_PRD_OF_WRK_BAND_D" if you are in an upgrade phase in which you are upgrading to Oracle BI Applications version 7.9.6.1, 7.9.6.2, or 7.9.6.3.

Do not execute reset_infa_seq_gen_ORA.bat until you have completed the procedures in either Section D.5.2 or Section D.5.3.

D.5.2 Obtaining ROW_WID from W_ORG_D and W_PRD_OF_WRK_BAND_D

Follow this procedure to obtain the maximum ROW_WID value from W_ORG_D and from W_PRD_OF_WRK_BAND_D if you are in an upgrade phase in which you are upgrading to Oracle BI Applications version 7.9.0, 7.9.1, 7.9.2, 7.9.3, 7.9.4, 7.9.5, 7.9.5.1, or 7.9.6.

Note: If you are in an upgrade phase in which you are upgrading to Oracle BI Applications version 7.9.6.1, 7.9.6.2, or 7.9.6.3, follow the steps in Section D.5.3, "Obtaining ROW_WID from W_PARTY_D and W_PRD_OF_WRK_BAND_D."

1. Obtain the maximum ROW_WID value from W_ORG_D:

1. In the reset_infa_seq_gen_ORA.bat file, go to the end of the file and locate the section similar to

IF %INFA_REP%==UPGRADE echo pmrep Updateseqgenvals -f"UPGRADE_7951_to_796_SBL" -t Seq_W_PARTY_D_Wid -c 1234567 >>sequence_gen_update.bat.

2. In the code example, note the value 1234567. You will replace this value in a following step.

3. On the data warehouse, run the following SQL statement:

SELECT MAX(ROW_WID)+1 FROM W_ORG_D

4. In the reset_infa_seq_gen_ORA.bat file, replace the value 1234567 with the value that was returned by the SQL statement.

2. Obtain the maximum ROW_WID value from W_PRD_OF_WRK_BAND_D:

1. In the reset_infa_seq_gen_ORA.bat file, go to the end of the file and locate the section similar to:

IF %INFA_REP%==UPGRADE echo pmrep Updateseqgenvals -f"UPGRADE_7951_to_796_SBL" -t Seq_W_PARTY_D_Wid -c 1234567 >>sequence_gen_update.bat.

2. Add the following lines after the section referred to in step a:

IF %INFA_FOLDER%==HOR echo pmrep Updateseqgenvals -f "SILOS" -m SIL_PeriodOfWorkBandDimension -t Seq_3000_Plus_Sequence_Prd_Of_Wrk_Band -c MAX1 >>sequence_gen_update.bat

IF %INFA_FOLDER%==HOR echo pmrep Updateseqgenvals -f "SILOS" -m SIL_PeriodOfWorkBandDimension -t Seq_4000_Plus_Sequence_Prd_Of_Wrk_Band -c MAX2 >>sequence_gen_update.bat

3. In the code example, note the values MAX1 and MAX2. You will replace these values in a following step.

4. On the data warehouse, run the following SQL statements:

select max(ROW_WID)+1 from W_PRD_OF_WRK_BAND_D where level_id = 'POW_BAND_EMP'

The value returned from the SQL statement above corresponds to MAX1.

select max(ROW_WID)+1 from W_PRD_OF_WRK_BAND_D where level_id = 'POW_BAND_CWK'

The value returned from the SQL statement above corresponds to MAX2.

5. In the reset_infa_seq_gen_ORA.bat file, replace the values MAX1 and MAX2 with the values returned by the SQL statements.

3. Execute reset_infa_seq_gen_ORA.bat.

D.5.3 Obtaining ROW_WID from W_PARTY_D and W_PRD_OF_WRK_BAND_D

Follow this procedure to obtain the maximum ROW_WID value from W_PARTY_D and from W_PRD_OF_WRK_BAND_D if you are in an upgrade phase in which you are upgrading to Oracle BI Applications version 7.9.6.1, 7.9.6.2, or 7.9.6.3.

Note: If you are in an upgrade phase in which you are upgrading to Oracle BI Applications version 7.9.0, 7.9.1, 7.9.2, 7.9.3, 7.9.4, 7.9.5, 7.9.5.1, or 7.9.6, follow the steps in Section D.5.2, "Obtaining ROW_WID from W_ORG_D and W_PRD_OF_WRK_BAND_D."

1. Obtain the maximum ROW_WID value from W_ORG_D:

1. In the reset_infa_seq_gen_ORA.bat file, go to the end of the file and locate the section similar to

IF %INFA_REP%==UPGRADE echo pmrep Updateseqgenvals -f"UPGRADE_7951_to_796_SBL" -t Seq_W_PARTY_D_Wid -c 1234567 >>sequence_gen_update.bat.

2. In the code example, note the value 1234567. You will replace this value in a following step.

3. On the data warehouse, run the following SQL statement:

SELECT MAX(ROW_WID)+1 FROM W_PARTY_D

4. In the reset_infa_seq_gen_ORA.bat file, replace the value 1234567 with the value that was returned by the SQL statement.

2. Obtain the maximum ROW_WID value from W_PRD_OF_WRK_BAND_D:

1. In the reset_infa_seq_gen_ORA.bat file, go to the end of the file and locate the section similar to:

IF %INFA_REP%==UPGRADE echo pmrep Updateseqgenvals -f"UPGRADE_7951_to_796_SBL" -t Seq_W_PARTY_D_Wid -c 1234567 >>sequence_gen_update.bat.

2. Add the following lines after the section referred to in step a:

IF %INFA_FOLDER%==HOR echo pmrep Updateseqgenvals -f "SILOS" -m SIL_PeriodOfWorkBandDimension -t Seq_3000_Plus_Sequence_Prd_Of_Wrk_Band -c MAX1 >>sequence_gen_update.bat

IF %INFA_FOLDER%==HOR echo pmrep Updateseqgenvals -f "SILOS" -m SIL_PeriodOfWorkBandDimension -t Seq_4000_Plus_Sequence_Prd_Of_Wrk_Band -c MAX2 >>sequence_gen_update.bat

3. In the code example, note the values MAX1 and MAX2. You will replace these values in a following step.

4. On the data warehouse, run the following SQL statements:

select max(ROW_WID)+1 from W_PRD_OF_WRK_BAND_D where level_id = 'POW_BAND_EMP'

The value returned from the SQL statement above corresponds to MAX1.

select max(ROW_WID)+1 from W_PRD_OF_WRK_BAND_D where level_id = 'POW_BAND_CWK'

The value returned from the SQL statement above corresponds to MAX2.

5. In the reset_infa_seq_gen_ORA.bat file, replace the values MAX1 and MAX2 with the values returned by the SQL statements.

3. Execute reset_infa_seq_gen_ORA.bat.

D.6 Running reset_infa_seq_gen_MSSQL.bat on Upgrade Repository for DW on Teradata and Repository on MSSQL Server

Follow this procedure if your Oracle Business Analytics Warehouse is on a Teradata database and your Informatica Repository is on an MSSQL Server database.

This section contains the following topics:

- Section D.6.1, "Entering Values for the reset_infa_seq_gen_MSSQL.bat File on the Upgrade Informatica Repository"

- Section D.6.2, "Obtaining ROW_WID from W_ORG_D and W_PRD_OF_WRK_BAND_D"

- Section D.6.3, "Obtaining ROW_WID from W_PARTY_D and W_PRD_OF_WRK_BAND_D"

D.6.1 Entering Values for the reset_infa_seq_gen_MSSQL.bat File on the Upgrade Informatica Repository

Follow this procedure to enter values for the reset_infa_seq_gen_MSSQL.bat file to initialize the Informatica sequence generator for incremental runs on the Upgrade Informatica Repository.

1. Navigate to OracleBI\dwrep\Upgrade\DbScripts\Teradata.

2. Open the reset_infa_seq_gen_MSSQL.bat file.

3. Enter the appropriate parameter values to reflect your environment (the parameters are database specific).

Table D-10 Teradata Database Parameter Settings for reset_infa_seq_gen_MSSQL.bat

Parameter

Setting

OLAP_SERVER

Enter the name of the Teradata 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 password of the data warehouse database.

INFORMATICA REPOSITORY SERVER ADDRESS

Enter the UPgrade Informatica Repository Service host address.

INFORMATICA REPOSITORY DB SERVER ADDRESS

Enter the database address for the Upgrade Informatica Repository database server in the format <MSSQL Server addres>,<port number>

For example: tcp:192.168.01.2,20100

or tcp:MSSQL2005DBA,20100

INFORMATICA REPOSITORY DATABASE

Name of the UPgrade Informatica Repository database.

INFORMATICA REPOSITORY DB USERNAME

Enter the user ID of the Upgrade Informatica Repository database.

INFORMATICA REPOSITORY DB PASSWORD

Enter the password @connection string of the Upgrade Informatica Repository database.

INFORMATICA REPOSITORY

Enter the name of the Upgrade Informatica Repository.

INFORMATICA REPOSITORY USERNAME

Enter the user ID of the Upgrade Informatica Repository.

INFORMATICA REPOSITORY PASSWORD

Enter the password for the Upgrade Informatica Repository.

INFORMATICA FOLDER

For all source systems except Siebel Industry Applications, enter the value HOR.

For Siebel Industry Applications, you need to run reset_infa_seq_gen_MSSQL.bat twice. For the first execution, enter the value VERT. For the second execution, enter the value HOR.

INFORMATICA PORT

Enter the port number for the Repository Service. The default is 6001.

After you complete this step, proceed to one of the following sections:

- Follow the steps in Section D.6.2, "Obtaining ROW_WID from W_ORG_D and W_PRD_OF_WRK_BAND_D" if you are in an upgrade phase in which you are upgrading to Oracle BI Applications version 7.9.0, 7.9.1, 7.9.2, 7.9.3, 7.9.4, 7.9.5, or 7.9.5.1, or 7.9.6.

- Follow the steps in Section D.6.3, "Obtaining ROW_WID from W_PARTY_D and W_PRD_OF_WRK_BAND_D" if you are in an upgrade phase in which you are upgrading to Oracle BI Applications version 7.9.6.1, 7.9.6.2, or 7.9.6.3.

Do not execute reset_infa_seq_gen_MSSQL.bat until you have completed the procedures in either Section D.6.2 or Section D.6.3.

D.6.2 Obtaining ROW_WID from W_ORG_D and W_PRD_OF_WRK_BAND_D

Follow this procedure to obtain the maximum ROW_WID value from W_ORG_D and from W_PRD_OF_WRK_BAND_D if you are in an upgrade phase in which you are upgrading to Oracle BI Applications version 7.9.0, 7.9.1, 7.9.2, 7.9.3, 7.9.4, 7.9.5, 7.9.5.1, or 7.9.6.

Note: If you are in an upgrade phase in which you are upgrading to Oracle BI Applications version 7.9.6.1, 7.9.6.2, or 7.9.6.3, follow the steps in Section D.6.3, "Obtaining ROW_WID from W_PARTY_D and W_PRD_OF_WRK_BAND_D."

1. Obtain the maximum ROW_WID value from W_ORG_D:

1. In the reset_infa_seq_gen_MSSQL.bat file, go to the end of the file and locate the section similar to

IF %INFA_REP%==UPGRADE echo pmrep Updateseqgenvals -f"UPGRADE_7951_to_796_SBL" -t Seq_W_PARTY_D_Wid -c 1234567 >>sequence_gen_update.bat.

2. In the code example, note the value 1234567. You will replace this value in a following step.

3. On the data warehouse, run the following SQL statement:

SELECT MAX(ROW_WID)+1 FROM W_ORG_D

4. In the reset_infa_seq_gen_MSSQL.bat file, replace the value 1234567 with the value that was returned by the SQL statement.

2. Obtain the maximum ROW_WID value from W_PRD_OF_WRK_BAND_D:

1. In the reset_infa_seq_gen_MSSQL.bat file, go to the end of the file and locate the section similar to:

IF %INFA_REP%==UPGRADE echo pmrep Updateseqgenvals -f"UPGRADE_7951_to_796_SBL" -t Seq_W_PARTY_D_Wid -c 1234567 >>sequence_gen_update.bat.

2. Add the following lines after the section referred to in step a:

IF %INFA_FOLDER%==HOR echo pmrep Updateseqgenvals -f "SILOS" -m SIL_PeriodOfWorkBandDimension -t Seq_3000_Plus_Sequence_Prd_Of_Wrk_Band -c MAX1 >>sequence_gen_update.bat

IF %INFA_FOLDER%==HOR echo pmrep Updateseqgenvals -f "SILOS" -m SIL_PeriodOfWorkBandDimension -t Seq_4000_Plus_Sequence_Prd_Of_Wrk_Band -c MAX2 >>sequence_gen_update.bat

3. In the code example, note the values MAX1 and MAX2. You will replace these values in a following step.

4. On the data warehouse, run the following SQL statements:

select max(ROW_WID)+1 from W_PRD_OF_WRK_BAND_D where level_id = 'POW_BAND_EMP'

The value returned from the SQL statement above corresponds to MAX1.

select max(ROW_WID)+1 from W_PRD_OF_WRK_BAND_D where level_id = 'POW_BAND_CWK'

The value returned from the SQL statement above corresponds to MAX2.

5. In the reset_infa_seq_gen_MSSQL.bat file, replace the values MAX1 and MAX2 with the values returned by the SQL statements.

3. Execute reset_infa_seq_gen_MSSQL.bat.

D.6.3 Obtaining ROW_WID from W_PARTY_D and W_PRD_OF_WRK_BAND_D

Follow this procedure to obtain the maximum ROW_WID value from W_PARTY_D and from W_PRD_OF_WRK_BAND_D if you are in an upgrade phase in which you are upgrading to Oracle BI Applications version 7.9.6.1, 7.9.6.2, or 7.9.6.3.

Note: If you are in an upgrade phase in which you are upgrading to Oracle BI Applications version 7.9.0, 7.9.1, 7.9.2, 7.9.3, 7.9.4, 7.9.5, 7.9.5.1, or 7.9.6, follow the steps in Section D.6.2, "Obtaining ROW_WID from W_ORG_D and W_PRD_OF_WRK_BAND_D."

1. Obtain the maximum ROW_WID value from W_ORG_D:

1. In the reset_infa_seq_gen_MSSQL.bat file, go to the end of the file and locate the section similar to

IF %INFA_REP%==UPGRADE echo pmrep Updateseqgenvals -f"UPGRADE_7951_to_796_SBL" -t Seq_W_PARTY_D_Wid -c 1234567 >>sequence_gen_update.bat.

2. In the code example, note the value 1234567. You will replace this value in a following step.

3. On the data warehouse, run the following SQL statement:

SELECT MAX(ROW_WID)+1 FROM W_PARTY_D

4. In the reset_infa_seq_gen_MSSQL.bat file, replace the value 1234567 with the value that was returned by the SQL statement.

2. Obtain the maximum ROW_WID value from W_PRD_OF_WRK_BAND_D:

1. In the reset_infa_seq_gen_MSSQL.bat file, go to the end of the file and locate the section similar to:

IF %INFA_REP%==UPGRADE echo pmrep Updateseqgenvals -f"UPGRADE_7951_to_796_SBL" -t Seq_W_PARTY_D_Wid -c 1234567 >>sequence_gen_update.bat.

2. Add the following lines after the section referred to in step a:

IF %INFA_FOLDER%==HOR echo pmrep Updateseqgenvals -f "SILOS" -m SIL_PeriodOfWorkBandDimension -t Seq_3000_Plus_Sequence_Prd_Of_Wrk_Band -c MAX1 >>sequence_gen_update.bat

IF %INFA_FOLDER%==HOR echo pmrep Updateseqgenvals -f "SILOS" -m SIL_PeriodOfWorkBandDimension -t Seq_4000_Plus_Sequence_Prd_Of_Wrk_Band -c MAX2 >>sequence_gen_update.bat

3. In the code example, note the values MAX1 and MAX2. You will replace these values in a following step.

4. On the data warehouse, run the following SQL statements:

select max(ROW_WID)+1 from W_PRD_OF_WRK_BAND_D where level_id = 'POW_BAND_EMP'

The value returned from the SQL statement above corresponds to MAX1.

select max(ROW_WID)+1 from W_PRD_OF_WRK_BAND_D where level_id = 'POW_BAND_CWK'

The value returned from the SQL statement above corresponds to MAX2.

5. In the reset_infa_seq_gen_MSSQL.bat file, replace the values MAX1 and MAX2 with the values returned by the SQL statements.

3. Execute reset_infa_seq_gen_MSSQL.bat.

E Using the DDLimp Utility

This appendix contains instructions for using the DDLimp utility. It contains the following topic:

- Section E.1, "Using the DDLimp Utility to Run CTL Files"

E.1 Using the DDLimp Utility to Run CTL Files

Follow this procedure to use the DDLimp utility to run CTL files.

To use the DDLimp utility

1. Navigate to the folder OracleBI\dwrep\Upgrade\CTLFiles, and locate the specified CTL file.

2. If you changed any of the preconfigured column definitions in the CTL file for your implementation, you need to edit the CTL file to reflect the change. For example, if you renamed or resized an existing column in W_DAY_D, you need to make the same change in the CTL file. If you do not make the change in the CTL file, when the CTL file is run, the column definition will revert to the preconfigured definition. (As a customization, if a column size was changed from VARCHAR(50) to VARCHAR(100), and the same change was not made in the CTL file before running, the column will revert to the preconfigured value of VARCHAR(50), which could cause data to be truncated in some databases.)

3. For non-Teradata databases, use the DDLimp utility to run the <file_name>.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\CTLFiles\<FILE_NAME>.CTL>
/L <..\oracleBI\dwrep\<FILE_NAME>.log>

For example:

DDLIMP /U SADMIN /P SADMIN /C OBIA /G SSE_ROLE
/I N /R Y /F C:\OracleBI\dwrep\Upgrade\CTLFiles\UPGRADE_7962.CTL /L C:\OracleBI\dwrep\UPGRADE.log

4. For Teradata databases, use the DDLimp utility to run the <file_name>.ctl script. Use the following command:

..\OracleBI\dwrep\bin\DDLIMP /U <USER> /P <PASSWORD> /C <ODBC connect string>
/G SSE_ROLE /F <..\OracleBI\dwrep\Upgrade\CTLFiles\<FILE_NAME>.CTL>
/s N /L <..\oracleBI\dwrep\<FILE_NAME>.log>

For example:

DDLIMP /U SADMIN /P SADMIN /C OBIA /G SSE_ROLE
/F C:\OracleBI\dwrep\Upgrade\CTLFiles\UPGRADE_7962.CTL /s N /L C:\OracleBI\dwrep\UPGRADE.log

E.2 Additional DDLimp Commands

The following DDLimp commands are also available:

- /P <PASSWORD> - The password for the data warehouse.

- For Oracle databases, use the Data Direct drivers.

- /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.

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

F Creating ODBC Database Connections for DAC

This appendix provides instructions for creating ODBC database connections for DAC.

The DAC Client requires an ODBC connection to the Oracle Business Analytics Warehouse when the database type is Oracle, SQL Server, DB2, and DB2-390 in order to upgrade the data warehouse schema using the DDL Import Utility.

Additionally, Siebel CRM source systems require an ODBC connection to the OLTP (source) database on the machine where Oracle BI Applications software is installed. This ODBC connection will be used by the DDLIMP utility.

For the ODBC connections to Oracle databases, you must use the Oracle Merant ODBC Driver that is installed with the DAC platform installation. For all other databases, you should use ODBC drivers supplied by your database vendor.

Note:

On Windows Vista, the Oracle Merant Driver is not successfully installed by the DAC installer. Use Microsoft ODBC Administrator to configure an ODBC connection with the native ODBC driver instead. Use this ODBC when upgrading tables in the Oracle Business Analytics Warehouse using the DAC Client.

Refer to the appropriate instructions for your database type:

- Section F.1, "Creating ODBC Connections for Oracle Databases"

- Section F.2, "Creating ODBC Connections for DB2 Databases"

- Section F.3, "Creating ODBC Connections for SQL Server Databases"

- Section F.4, "Creating ODBC Connections for Teradata Databases"

F.1 Creating ODBC Connections for Oracle Databases

Follow these instructions for creating ODBC connections for Oracle databases on Windows. For instructions on creating ODBC connections for Oracle databases on UNIX or Linux, see the documentation provided with your database.

Note: You must use the Oracle Merant ODBC driver to create the ODBC connections. The Oracle Merant ODBC driver is installed by the Oracle BI Applications installer. Therefore, you will need to create the ODBC connections after you have run the Oracle BI Applications installer and have installed the DAC Client.

To create ODBC connections for Oracle databases

1. On the Windows machine that will host the DAC Client, navigate to the ODBC Data Source Administrator.
Use the System DSN tab of the ODBC Data Source Administrator to create an ODBC connection to the Oracle Business Analytics Warehouse database using the Oracle Merant ODBC driver that is supplied with Oracle BI Applications.

For example, you might create a database connection called Connect_to_OLAP.

2. Click the System DSN tab.

3. Click Add.

4. In the list of drivers, select the Oracle Merant ODBC driver that is installed with DAC, for example, Oracle Merant ODBC Driver in DAC 10g_Oracle - OH1.

5. In the ODBC Oracle Driver Setup dialog, enter or select the following:

Field

Description

Data Source Name

Enter any meaningful name.

Server Name

Enter the tnsname for the database.

Client Version

Select 10gR1 for 10g and 11g databases.

6. Click Test Connect to make sure the connection works.

7. (If your source system is Siebel CRM) In Windows, in the System DSN tab of the ODBC Data Source Administrator, create an ODBC connection to the Siebel transactional database using the Oracle Merant Closed driver.

F.2 Creating ODBC Connections for DB2 Databases

Follow these instructions for creating ODBC connections for DB2 databases on Windows. For instructions on creating ODBC connections for DB2 databases on UNIX or Linux, see the documentation provided with your database.

To create ODBC connections for DB2 databases

1. Using the DB2 Client Configuration Assistant, create a database connection to the Oracle Business Analytics Warehouse database on the machine that will host the DAC Client. If your source system is Siebel CRM, also create an ODBC connection to the transactional database on the machine where you will run the Oracle BI Applications installer.
Note: If you use the DB2 Client Configuration Assistant to create database connections, you can omit step 2, because the DB2 Client Configuration Assistant automatically creates System DSNs (default behavior).

2. If necessary, on Windows, in the System DSN tab of the ODBC Data Source Administrator, create an ODBC connection to the Oracle Business Analytics Warehouse (and, if your source system is Siebel CRM, to the transactional database) using an ODBC driver.

3. Test the connections to make sure they work.

F.3 Creating ODBC Connections for SQL Server Databases

Follow these instructions for creating ODBC connections for SQL Server databases on Windows.

To create ODBC connections for SQL Server databases

1. In Windows, in the System DSN tab of the ODBC Data Source Administrator, create the following:

- An ODBC connection to the Oracle Business Analytics Warehouse database on the machine that will host the DAC Client.

- (If your source system is Siebel CRM) An ODBC connection to the transactional database on the machine where you will run the Oracle BI Applications installer.

Note: Select SQL Server as the ODBC driver.

2. Test the connections to make sure they work.

Note: When you use the ODBC Data Source Administrator to create a database connection, make sure that you select the SQL Server authentication option using a login ID and password entered by the user.

F.4 Creating ODBC Connections for Teradata Databases

Follow these instructions for creating ODBC connections for Teradata databases.

To create ODBC connections for Teradata databases on Windows

1. On the Windows machine that will host the DAC Client, in the System DSN tab of the ODBC Data Source Administrator, create an ODBC connection to the Oracle Business Analytics Warehouse Teradata database.

2. Set the following parameters:
Field=Enter

DateFormat=AAA

SessionMode=ANSI

NoScan=Yes

3. For Unicode environments, in the Teradata ODBC Driver Advanced Options dialog, set the Character Set parameter to UTF8.

To create ODBC connections for Teradata databases on UNIX

1. Using the Teradata ODBC driver, create an ODBC connection for the Teradata database.

2. Set the following variables in the ODBC.INI file:

- DateFormat=AAA

- SessionMode=ANSI

- NoScan=Yes

3. For UNICODE environments, in the Teradata ODBC Driver Advanced Options dialog, add the following:

- CharacterSet=UTF8

G Upgrading the Oracle BI Repository for Industry-Specific Analytics Applications

This appendix contains instructions for upgrading the Oracle BI repository for Pharma Analytics, Consumer Sector, and Vehicle Sales.

In Oracle BI Applications release 7.9.4, the Pharma Analytics business model and Core business model were merged. In Oracle BI Applications release 7.9.5, the Consumer Sector and Vehicle Sales Analytics business models and Core business model were merged. Because of this merge, the process of upgrading the Oracle BI repository has some steps that differ from the standard Oracle BI repository upgrade process.

This section includes the following topics:

- Section G.1, "Common Dimensions"

- Section G.2, "Merging Siebel Analytics and Oracle BI Repositories"

- Section G.3, "Replacing Common Dimensions After the Repository Merge"

G.1 Common Dimensions

Table G-1, Table G-2, and Table G-3 list the common dimensions of Pharma, Consumer Sector, and Vehicle Sales Analytics and their statuses. Some of the dimensions are not shared with other Core modules because of specific requirements.

Table G-1 Common Pharma Analytics Dimensions

Dimensions in Pre-7.9.4 Releases

Dimensions in Release 7.9.4

Status

Comments

Dim - Accounts

Dim - Customer

Shared

None

Dim - Contacts

Dim - Contact

Shared

New name is singular

Dim - Security Dimension

Dim - Position Security

Shared

None

Dim - Time Period

Dim - Date

Shared

None

Dim - Geography

Dim - Pharma Geography

Not shared

Use Pharma-specific dimension in Core

Dim - Geography_Account

Dim - Pharma Geography_Account

Not shared

Use Pharma-specific dimension in Core

Dim - Geography_Contact

Dim - Pharma Geography_Contact

Not shared

Use Pharma-specific dimension in Core

Dim - Products

Dim - Pharma Products

Not shared

Use Pharma-specific dimension in Core

Table G-2 Common Consumer Sector Analytics Dimensions

Dimensions in Pre-7.9.5 Releases

Dimensions in Release 7.9.5

Status

Comments

Dim - Account Geography

Dim - Account Geography

Shared

None

Dim - Accounts

Dim - Customer

Shared

None

Dim - Accounts Hierarchy

Dim - Accounts Hierarchy

Shared

None

Dim - Employees

Dim - Employees

Shared

None

Dim - End Date

Dim - End Date

Shared

None

Dim - Position Hierarchies

Dim - Position

Shared

Dim - Position in 7.9.5 combines both Position and Position Hierarchy

Dim - Positions

Dim - Position

Shared

Dim - Position in 7.9.5 combines both Position and Position Hierarchy

Dim - Product Categories Hierarchy

Dim - CS Product Category Hierarchy

Not shared

Use CS-specific dimension in Core

Dim - Products

Dim - CS Product

Not shared

Use CS-specific dimension in Core

Dim - Start Date/Date

Dim - Start Date

Shared

None

Table G-3 Common Vehicle Sales Analytics Dimensions

Dimensions in Pre-7.9.5 Releases

Dimensions in Release 7.9.5

Status

Comments

Dim - Accounts

Dim - Customer

Shared

None

Dim - Accounts Geography

Dim - Account Geography

Shared

None

Dim - Contacts Geography

Dim - Person Geography

Shared

None

Dim - Date

Dim - Date

Shared

None

Dim - Households

Dim - Households

Shared

None

Dim - Individuals

Dim - Contact

Shared

None

Dim - Lease/Loan Expiry

Dim - End Date

Shared

None

Dim - Product Hierarchy

Dim - Product Hierarchy

Shared

None

Dim - Products

Dim - Product

Shared

None

Dim - Vehicle

Dim - Asset

Shared

None

G.2 Merging Siebel Analytics and Oracle BI Repositories

The Pharma, Consumer Sector, and Vehicle Sales Analytics upgrade process involves merging customizations of prior releases of the Siebel Analytics or Oracle BI repositories into the current version of the Oracle BI repository. This process follows the same principle as the Core upgrade process but includes some additional steps.

In this section, the upgrade process for Pharma Analytics from pre-7.9.4 releases to release 7.9.4 and higher will be used as an example. The upgrade process for Consumer Sector and Vehicle Sales Analytics from pre-7.9.5 releases to release 7.9.5 and higher are the same as that for the upgrade to Pharma Analytics release 7.9.4 and higher.

As shown in Figure G-1, there are two phases to the Pharma Analytics upgrade process.

Figure G-1 Phases of Repository Merge for Pharma Analytics

Phase 1

As shown in Figure G-1, there are two phases in the Pharma Analytics upgrade process. Phase 1 involves merging the 7.x original Core base repository (the repository that shipped with the release of Siebel Analytics or Oracle BI you are currently running), the 7.x custom Core repository, and the new base repository into one output repository.

Phase 2

Phase 2 involves merging the output repository of Phase 1 with the 7.x original Pharma Analytics base repository and the 7.x custom Pharma Analytics repository. The output repository of Phase 2 is a merged Pharma and Core repository that includes your customizations from prior releases and the new data model.

Note:

You need to perform both phases of the upgrade process if your current, customized repository has both Core and Pharma models and the Core model is customized.

If your current, customized repository does not include the Core model or includes the Core model but the Core model is not customized, you only need to perform Phase 2.

If you only perform Phase 2, then you will not have a new Core merged RPD (as shown in Figure G-1). Instead, you will use the new base RPD in place of the new Core merged RPD.

See Table G-4 and Table G-5 for a description of the different RPD file names.

The tasks in this section refer to multiple versions of the Siebel Analytics or Oracle BI repository. Table G-4 provides the names and descriptions of the repositories used in Phase 1. Table G-5 provides the names and descriptions of the repositories used in Phase 2.

Table G-4 Phase 1 Repository Files

Repository File

Description

7x_original_Core_base.rpd

The trimmed, original (standard) repository for the version you are upgrading from.

7x_custom_Core.rpd

The trimmed, custom 7.x repository that includes the Core model customizations.

New_base.rpd

The trimmed, new repository that includes related Core and Pharma modules in one Core model (logical folder).

Table G-5 Phase 2 Repository Files

Repository File

Description

New_Core_merged.rpd

The output repository from Phase 1.

If you do not perform Phase 1, then use the new base RPD in place of the new Core merged RPD.

7x_original_Pharma_base.rpd

The trimmed, original 7.x repository that includes the Pharma model, which was not customized.

7x_custom_Pharma.rpd

The trimmed, customized repository that includes a customized Pharma model.

New_Core_Pharma_merged.rpd

The final, merged new repository that includes a single Core model (logical folder), including all the customized content.

G.2.1 Creating Working Folders

You will use the working folders to hold the repository files after the different stages of the merge process.

Create a folder for the merge process, such as \OracleBIPharmaUpgrade, and then create the following subfolders:

- Original

- AfterTrimDown

- AfterEqualize

- AfterMerge

- AfterManualWork

- AfterRegressions

G.2.2 Trimming Repository Files

Trimming the repositories so that you upgrade only the content that is in use can narrow the upgrade scope and eliminate unnecessary complexities during the merge process.

You can trim down repository files by extracting projects or manually trimming down repository objects.

Note:

The Security Group property controls the presentation catalogs that will be extracted. If a presentation catalog is added to a project for extract but none of the groups in the project has visibility to see the catalog, it will not show up in the extracted repository file.

G.2.2.1 Trimming the Original Base Repository Files

You should trim the original base repository file to meet your business requirements.

To trim the original base repository files

1. If you are performing Phase 1 of the upgrade process, trim the original Core base repository file.

2. Save the file as 7x_original_Core_base.rpd (where 7x represents the release of Siebel Analytics or Oracle BI) in the AfterTrimDown subfolder.

3. Trim the original Pharma base repository file.

4. Save the file as 7x_original_Pharma _base.rpd in the AfterTrimDown subfolder.

G.2.2.2 Trimming the New Base Repository File

The new base repository file that you received with the current Oracle BI Applications release, contains one Core model (logical folder), which holds Pharma and Core repository objects.

To trim the new base repository file

1. Trim the new base repository file.

2. Save the file as New_base.rpd in the AfterTrimDown subfolder.

G.2.2.3 Trimming the Custom Repository Files

If you are performing Phase 1 of the upgrade process, you will have a 7x custom Core repository file (7x_custom_core.rpd) that contains the 7x original Core base contents and your customizations.

You will also have a 7x custom Pharma repository file (7x_custom_Pharma.rpd) that contains the 7x original Pharma base contents and your customizations.

Save these files in the AfterTrimDown subfolder.

G.2.3 Renaming Objects in the Original Pharma Base Repository File

In the 7x original Pharma base repository file and the 7x custom Pharma repository file, you need to rename some repository objects to be compatible with the new data model.

To rename objects in the Pharma repository files

1. In the Server Administration Tool, open the 7x _original_Pharma_base.rpd file.

2. In the Business Model and Mapping layer, rename Business Model Pharma to Core.

3. In the Physical layer, do the following:

1. Rename Database Pharma Data Warehouse to Oracle Data Warehouse.

2. Make sure the Connection Pool is named as Oracle Data Warehouse Connection Pool.

3. Make sure the Catalog entry (below the Connection Pool entry) is named as Catalog.

4. Make sure the Schema entry (below the Catalog entry) is named as dbo.

4. Repeat Steps 1 through 3 using the 7x_custom_Pharma.rpd file.

G.2.4 Equalizing the Oracle BI Repositories

The equalization process in the standard Oracle BI repository upgrade uses the original base repository from a previous release as a starting point. This type of equalization is referred to as "backward" equalization. The Pharma upgrade uses what is called "forward" equalization, in which you use the repository file from the current release as a starting point and equalize the 7x base repository file and the 7x custom repository file to it.

You will first need to prepare the MAP file for "forward" equalization before you execute the equalization.

Table G-6 provides a list of the available MAP files and the Siebel Analytics or Oracle BI Applications release version associated with the file.

Table G-6 Rename MAP Files to Be Used for Various Releases

Siebel Analytics / Oracle Business Intelligence Applications Release Version (Upgrading from DW Version)

Rename MAP File to Be Used

Siebel Business Analytics Applications 7.0.x

Not available

Siebel Business Analytics Applications 7.5.x

Not available

Siebel Business Analytics Applications 7.7.x (with Siebel CRM OLTP Pre-7.7.0)

Rename77-7963.map

Siebel Business Analytics Applications 7.7.x (with Siebel CRM OLTP 7.7.0)

Rename771-7963.map

Siebel Business Analytics Applications 7.8.2 and all 7.8.x versions before this release

Rename782-7963.map

Siebel Business Analytics Applications 7.8.3 and all 7.8.x versions after this release

Rename783-7963.map

Oracle BI Applications 7.9.0

Rename79x-7963.map

Oracle BI Applications 7.9.1

Rename79x-7963.map

Oracle BI Applications 7.9.2

Rename79x-7963.map

Oracle BI Applications 7.9.3

Rename793to7963.map

Oracle BI Applications 7.9.4

Rename794to7963.map

Oracle BI Applications 7.9.5

Rename79x-7963.map

Oracle BI Applications 7.9.5.1

Rename7951to7963.map

Oracle BI Applications 7.9.5.2

Rename7951to7963.map

Oracle BI Applications 7.9.6

Rename79x-7963.map

Oracle BI Applications 7.9.6.2

rename7963to7964.map

Not required for upgrades from 7.9.6.2 to 7.9.6.3.

Oracle BI Applications 7.9.6.3

rename7963to7964.map

To prepare the MAP file for "forward" equalization

1. Copy the appropriate MAP file from the \OracleBI\Upgrade folder into the folder where you will execute equalizerpds.exe.

Note:

The naming convention of the MAP files is rename<release from which you are upgrading>-<release to which you are upgrading>.map.

For example if you are upgrading from release 7.8.4 to release 7.9.5, you should use the file rename784_795.map.

2. Open the MAP file in Excel.

3. In the Text Import Wizard, accept the default in the Step 1 dialog by clicking Next.

4. In the Step 2 dialog of the Text Import Wizard, do the following:

1. Make sure the Tab check box is selected in the Delimiters region.

2. In the Text qualifier list, select None.

3. Click Next.

5. In the Step 3 dialog, click Finish.
The file opens in an Excel spreadsheet window and contains three columns.

6. Switch the order of the second and third columns by cutting the third column and inserting it as the second column.

7. Save the file.

8. Check to make sure the string format is correct.

To equalize the repository files

1. Run equalizerpds.exe.
An example of the equalizerpds command is as follows:

equalizerpds -A Administrator -B SADMIN
-C \OracleBIPharmaUpgrade\AfterTrimDown\New_base.rpd
-D Administrator -E SADMIN
-F \OracleBIPharmaUpgrade\AfterTrimDown\7x_custom_Pharma.rpd
-O \OracleBIPharmaUpgrade\AfterEqualize\7x_custom_Pharma.rpd
-X -J rename784-795.map

If the equalizerpds.exe executable file runs correctly, no errors are returned.

2. Repeat Step 1 to equalize each of the files in AfterTrimDown to New_base.rpd.

3. 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).

G.2.5 Merging the Core Repository Files

Note:

You need to perform this procedure if your customized repository has both Core and Pharma models and the Core model is customized. If the customized repository does not include the Core model or includes the Core model but the Core model is not customized, you do not need to perform this step.

This step involves a three-way merge on the Core repository. For a description of the files that will be merged in this procedure, see Section G.2, "Merging Siebel Analytics and Oracle BI Repositories."

To merge the core repository files

1. Copy 7x_original_Core_base.rpd, 7x_custom_Core.rpd, and New_base.rpd to the AfterMerge folder.

2. In the Server Administration Tool, open the New_base.rpd file.

3. From the Administration Tool menu bar, select File, then select Merge.

4. In the Select Original Repository dialog, select 7x_original_Core_base.

5. Enter the password, and click OK.

6. Click Select for the Modified Repository field.

7. In the Select Modified Repository dialog, select 7x_custom_Core.rpd.

8. Click Open, type the password, and then click OK.

9. In the Decision list, select the action you want to take regarding the repository change, or accept the default action.
For information about making decisions, see Section G.2.7, "Making Merge Decisions in the Administration Tool."

10. 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.

11. 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.

12. 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 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'

13. Save the merged repository as New_Core_merged.rpd.

G.2.6 Merging the Pharma Repository Files

This step involves a three-way merge on the Pharma repository. For a description of the files that will be merged in this procedure, see Section G.2, "Merging Siebel Analytics and Oracle BI Repositories."

Note:

If you did not perform Phase 1 of the upgrade process you will not have a New_Core_merged.rpd file. In place of the New_Core_merged.rpd file, you should use the New_new_base.rpd file.

To merge the Pharma repository files

1. Copy New_Core_merged.rpd, 7x_original_Pharma_base.rpd, and 7x_custom_Pharma.rpd to the AfterMerge folder.

2. In the Server Administration Tool, open the New_Core_merged.rpd file.

3. From the Administration Tool menu bar, select File, then select Merge.

4. In the Select Original Repository dialog, select 7x_original_Pharma_base.

5. Enter the password, and click OK.

6. Click Select for the Modified Repository field.

7. In the Select Modified Repository dialog, select 7x_custom_Pharma.rpd.

8. Click Open, type the password, and then click OK.

9. In the Decision list, select the action you want to take regarding the repository change, or accept the default action.
For information about making decisions, see Section G.2.7, "Making Merge Decisions in the Administration Tool."

10. 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.

11. 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.

12. 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 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'

13. Save the merged repository as New_Core_Pharma_merged.rpd.

G.2.7 Making Merge Decisions in the Administration Tool

When making decisions about merging repository objects in the Administration Tool, you should consider the following points:

- For objects that do not appear in the new base repository, you should normally choose "current," which will incorporate the changes into the new base repository.

- For objects added to the new base repository, you should normally choose "current," which will keep the changes.

- For objects in the original repository that were replaced with new objects, you may see decisions for removing the old objects from the current repository and adding the new objects. Choosing "current" will replace the old objects.

- For new customizations that you added to a repository, choose "modified" to keep the changes.

- If an object is changed in both the customized repository and the new base repository, the description "changed in both," may appear. In such cases, choose "current" to keep the object as it is in the new base repository, or choose "modified," to keep the object as it is in the customized repository.

G.3 Replacing Common Dimensions After the Repository Merge

After the repository file merge, all preconfigured presentation dimension tables and columns should be merged properly and sourcing from the new logical dimensions in the Core model. For example, Account Name in the Account presentation table should source from "Core"."Dim - Customer"."Account Name," and Gross Margin in the Product presentation table should source from "Core"."Dim - Pharma Products"."Gross Margin."

However, customized presentation tables and columns may still source from old dimensions. Table G-7, Table G-8, and Table G-9 list the common dimensions that have new names in the new release. If you customized presentation tables or columns from the old dimensions listed in Table G-7, Table G-8, and Table G-9 you need to replace the old logical source tables or table columns with the new ones.

A way to quickly allocate these problematic presentation tables or columns would be to do the following:

1. In the Core logical folder in the Server Administration Tool, find the old dimension name as listed in Table G-7, Table G-8, or Table G-9, for example, "Dim - Accounts."

2. Right-click the old dimension name, then click Display Related, and then click Presentation Column.

3. Replace the presentation columns with the same columns from the new logical dimension, for example, "Dim - Customer"

4. To verify you replaced the presentation columns correctly, search for presentation columns on the Core logical dimension, such as "Core - Accounts". If the return is empty, then it is safe to delete the old dimension, for example, "Dim - Accounts"

The following common dimensions in 7.x need to be reviewed and removed.

Table G-7 Names for Pharma Analytics Common Dimensions in Pre-7.9.4 Releases

Name of Dimension in Pre-7.9.4 Releases

Name of Dimension in Release 7.9.4

Status

Comments

Dim - Accounts

Dim - Customer

Shared

None

Dim - Contacts

Dim - Contact

Shared

New name is singular

Dim - Time Period

Dim - Date

Shared

None

Table G-8 Names for Consumer Sector Analytics Common Dimensions in Pre-7.9.5 Releases

Name of Dimension in Pre-7.9.5 Releases

Name of Dimension in Release 7.9.5

Status

Comments

Dim - Accounts

Dim - Customer

Shared

None

Dim - Position Hierarchies

Not applicable

Shared

Merged into Dim - Position in Core

Dim - Positions

Dim - Position

Shared

Dim - Position combines both Position and Position Hierarchy

Dim - Start Date/Date

Dim - Start Date

Shared

None

Table G-9 Names for Vehicle Sales Analytics Common Dimensions in Pre-7.9.5 Releases

Name of Dimension in Pre-7.9.5 Releases

Name of Dimension in Release 7.9.5

Status

Comments

Dim - Accounts

Dim - Customer

Shared

None

Dim - Accounts Geography

Dim - Account Geography

Shared

None

Dim - Contacts Geography

Dim - Person Geography

Shared

None

Dim - Individuals

Dim - Contact

Shared

None

Dim - Lease/Loan Expiry

Dim - End Date

Shared

None

Dim - Products

Dim - Product

Shared

None

Dim - Vehicle

Dim - Asset

Shared

None

Index

A  B  C  D  F  G  I  J  L  O  P  R  S  T  U  V

Symbols

$$Hint1 parameter for Oracle databases

configuring, A.3.1.4

$$PERIOD parameter

configuring for Oracle Supply Chain and Order Management Analytics, A.3.3.2

A

Application-specific parameters for Oracle Financial Analytics

configuring in 796_UPG_PARAMS.txt, A.3.1

B

best practices

preparing to upgrade, 2.5

C

COGS fact mapping

configuring 7962_UPG_PARAMS.txt for Oracle EBS R12, A.3.4.4

COGS fact mapping for Oracle EBS R12

configuring 796_UPG_PARAMS.txt, A.3.1.3

Consumer Sector

upgrading Oracle BI repository, G

D

DAC

installing for Siebel Analytics 7.5.x, 3.8

data warehouse schema

upgrading for JD Edwards source systems, 8.9

upgrading for Oracle EBS source systems, 6.9

upgrading for PeopleSoft source systems, 7.9

upgrading for Siebel Analytics 7.5.x, 3.9

upgrading for Siebel Business Analytics 7.7, 7.7.x, 7.8.x, 4.9

upgrading for Siebel Business Analytics on Teradata database, 4.21

upgrading for Siebel sources, 5.10

DDLimp utility

using to run CTL files, E.1

F

FSG Hierarchies, A.3.1.1

G

GL Data Extraction

configuring parameter in 796_UPG_PARAMS.txt, A.3.1.2

configuring parameter in 7962_UPG_PARAMS.txt for PeopleSoft sources, A.3.4.3

I

indexes

generating and running scripts for dropping and creating, B

Informatica

parameter files, configuring, A.1

upgrading for Siebel Analytics 7.5.x, 3.4, 4.4, 5.4, 6.4, 7.4, 8.4

Informatica parameter file 793_UPG_PARAMS.txt

configuring, A.1.1

Informatica parameter file 794_UPG_PARAMS.txt

configuring, A.1.2

Informatica parameter file 795_UPG_PARAMS.txt

configuring, A.1.3

Informatica parameter file 7951_UPG_PARAMS.txt

configuring, A.1.4

Informatica parameter file 796_UPG_PARAMS.txt

configuring, A.1.5, A.2.1

Informatica parameter file 7961_UPG_PARAMS.txt

configuring, A.1.6, A.1.9

Informatica parameter file 7962_UPG_PARAMS.txt

configuring, A.1.7

Informatica parameter file 7963_UPG_PARAMS.txt

configuring, A.1.8

Informatica Repository

upgrading for Siebel Analytics 7.5.x, 3.5, 4.5, 5.5, 6.5, 7.5, 8.5

Informatica sequence generator

setting parameters, D

J

JD Edwards

upgrading, 8

L

LDIF file

importing into embedded LDAP Server for JD Edwards sources, 8.12

importing into embedded LDAP Server for Oracle EBS sources, 6.12

importing into embedded LDAP Server for PeopleSoft sources, 7.12

importing into embedded LDAP Server for Siebel Analytics 7.5.x, 3.23

importing into embedded LDAP Server for Siebel Business Analytics, 4.23

importing into embedded LDAP Server for Siebel sources, 5.13

O

Oracle BI Applications

upgrading for JD Edwards source systems, 8.3

upgrading for Oracle EBS source systems, 6.3

upgrading for PeopleSoft source systems, 7.3

upgrading for Siebel Analytics 7.5.x, 3.3

upgrading for Siebel Business Analytics 7.7, 7.7.x, 7.8.x, 4.3

upgrading for Siebel sources, 5.3

Oracle BI Enterprise Edition

considerations for upgrading to 11g, 2.3

Oracle BI Infrastructure

upgrading for JD Edwards source systems, 8.2

upgrading for Oracle EBS source systems, 6.2

upgrading for PeopleSoft source systems, 7.2

upgrading Oracle BI Applications 7.9.x for Siebel Source Systems, 5.2

upgrading Siebel Analytics 7.5.3, 3.2

upgrading Siebel Business Analytics 7.7, 7.7..x and 7.8.x, 4.2

Oracle BI Repository

merging for Oracle EBS sources, 6.14

merging for Siebel Analytics 7.5.x, 3.25

merging for Siebel Business Analytics, 4.25

merging for Siebel sources, 5.15

upgrading for JD Edwards sources, 8.13

upgrading for Oracle EBS sources, 6.13

upgrading for PeopleSoft sources, 7.13

upgrading for Siebel sources, 5.14

Oracle EBS

upgrading, 7

Oracle Financial Analytics

configuring GL Data Extraction in 796_UPG_PARAMS.txt, A.3.1.2

configuring parameters, A.3.1.1

creating indexes for, C

FSG Hierarchies, A.3.1.1

setting parameters, A.3.4

setting parameters for Oracle BI Applications release 7.9.6.3, A.3.5

Value Set Hierarchies, A.3.1.1

Oracle Human Resources Analytics

setting parameters for Oracle BI Applications release 7.9.6.3, A.3.6

Oracle Procurement and Spend Analytics

setting parameters for Oracle BI Applications release 7.9.6.3, A.3.7, A.3.8

Oracle Project Analytics

configuring parameters in 796_UPG_PARAMS.txt, A.3.2

Oracle Supply Chain and Order Management Analytics

configuring $$PERIOD parameter, A.3.3.2

configuring TIME_GRAIN parameter, A.3.3.1

setting parameters, A.3.3

P

PeopleSoft

upgrading, 7

PeopleSoft source systems

upgrading, 7

Pharma Analytics

upgrading Oracle BI repository, G

policy store

localizing for JD Edwards sources, 8.11

localizing for Oracle EBS sources, 6.11

localizing for PeopleSoft sources, 7.11

localizing for Siebel Analytics 7.5.x, 3.22

localizing for Siebel Business Analytics, 4.22

localizing for Siebel sources, 5.12

presentation catalog

merging for JD Edwards sources, 8.14

merging for Oracle EBS sources, 6.15

merging for PeopleSoft sources, 7.14

merging for Siebel Analytics 7.5.x, 3.26

merging for Siebel Business Analytics, 4.26

merging for Siebel sources, 5.16, 5.16.2

upgrading for JD Edwards sources, 8.13

upgrading for Oracle EBS sources, 6.13

upgrading for PeopleSoft sources, 7.13

upgrading for Siebel sources, 5.14

preupgrade

best practices, 2.5

process flow, 2.6

R

reset_infa_seq_gen.bat

setting database-specific parameters, D

S

Siebel Analytics

upgrading release 7.5.x, 3

Siebel Analytics Repository

upgrading for Siebel Analytics 7.5.x, 3.24

Siebel Analytics Web Catalog

upgrading for Siebel Analytics 7.5.x, 3.24

Siebel Business Analytics

upgrading release 7.7, 7.7.x, 7.8.x, 4

upgrading releases 7.7, 7.7.x and 7.8.x, 4

Siebel Business Analytics Repository

upgrading for Siebel Business Analytics, 4.24

Siebel Business Analytics Web Catalog

upgrading for Siebel Business Analytics, 4.24

stages of upgrade

process flow, 2.6

sequence of stages, 2.6.1

supported upgrade paths, 2.1, 2.1

T

Teradata database

upgrading data warehouse schema for Oracle EBS source systems, 6.10

upgrading data warehouse schema for PeopleSoft source systems, 7.10

upgrading data warehouse schema for Siebel Analytics 7.7, 7.7.x, 7.8.x, 4.21

upgrading data warehouse schema for Siebel sources, 5.11

TIME_GRAIN parameter

configuring for Oracle Supply Chain and Order Management Analytics, A.3.3.1

U

upgrade

best practices, 2.5

considerations for upgrading Oracle BI Applications, 2.4

considerations for upgrading to Oracle BI Enterprise Edition 11g, 2.3

major stages, 2.6.1

overview, 2

preparing, 2.5

preupgrade considerations, 2.4

process flow, 2.6

reasons to upgrade, 2.2

sequence of steps, 2.6.1

supported paths, 2.1

upgrading JD Edwards source systems, 8

upgrading older releases of Oracle BI for Oracle EBS, 6

upgrading Oracle BI Applications 7.9.x for Siebel Sources, 5

upgrading PeopleSoft source systems, 7

upgrading Siebel Analytics 7.5.x, 3

upgrading Siebel Business Analytics 7.7, 7.7.x, 7.8.x, 4

upgrade considerations

points to consider, 2.4

V

Vehicle Sales

upgrading Oracle BI repository, G

Copyright © 2010, 2012, Oracle and/or its affiliates. All rights reserved.