Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Multidomain MDM 10.3 HotFix 3
  • All Products

Table of Contents

Search

  1. Preface
  2. Upgrade Overview
  3. Pre-Upgrade Tasks
  4. Database Tasks
  5. Application Server Tasks
  6. Hub Store Upgrade
  7. Hub Server Upgrade (In-place Upgrade)
  8. Process Server Upgrade (In-place Upgrade)
  9. Resource Kit Upgrade (In-place Upgrade)
  10. Post-Upgrade Tasks
  11. Search Configuration Upgrade
  12. ActiveVOS Post-Installation Tasks for the Application Server
  13. ActiveVOS Post-Upgrade Tasks for Business Entity Adapter
  14. ActiveVOS Post-Upgrade Tasks for Subject Areas Adapter
  15. Appendix A: Troubleshooting the Upgrade Process
  16. Appendix B: Frequently Asked Questions
  17. Appendix C: Processing Existing ActiveVOS Tasks
  18. Appendix D: Configuring Metadata Caching

Upgrading from Version 9.0.1 or 9.1.0 for Oracle

Upgrading from Version 9.0.1 or 9.1.0 for Oracle

Back Next

The Readiness Report

The Readiness Report

The readiness report identifies the data issues that you must resolve before you migrate the schema to the new data structure. Run a script to perform a data check and create the
READINESS_REPORT<
report ID
>.CSV
 file.
The readiness report outlines the issues that you must resolve before you upgrade.
The readiness report contains the following sections:
Detailed Temporary Data Tables
Lists the names of the temporary data tables that contain a copy of the records with data issues. Refer to the information in these tables to investigate and resolve data issues.
Summary
Lists all issues found during the data check.
The following table describes the information in each column:
Column
Description
Ref. #
Row number
Check Code
Code that identifies the data issue
Description
Issue that causes the error for that particular check code
Fix Type
Issue in the
Auto Mandatory Fix
 section have a fix type of
auto
Foreign Key Name
Name of the foreign key with data issues
Original Count
Number of data issues that the initial data check found
Current Count
Number of data issues that the most recent data check found
Details of Auto Mandatory Fix Issues
Lists the issues that are fixed by running a script. You must fix these issues before you upgrade.
The following table describes the information in each column:
Column
Description
Ref. #
Row number
Check Code
Code that identifies the data issue
Description
Issue that causes the error for that particular check code
Fix Type
Issue in the
Auto Mandatory Fix
 section have a fix type of
auto
Foreign Key Name
Name of the foreign key with data issues
Original Count
Number of data issues that the initial data check found
Current Count
Number of data issues that the most recent data check found
<
base object name
>
Number of data issues for a particular base object.
Others
Number of issues not specific to a particular base object
Two rows below the details of the auto mandatory fix issues identify the base object table record count and the cross-reference table record count. These rows display the total number of base object and cross-reference tables in the schema to provide some perspective on the percentage of records that have data issues.
Details of Manual Mandatory Fix Issues
Lists the issues you cannot run a script to fix. You must fix these issues before you upgrade.
The following table describes the information in the column:
Column
Description
Ref. #
Row number
Check Code
Code that identifies the data issue
Description
Description of the issue that caused the error
Object Name
Name of the base object that the issue affects
Detail of Manual Warnings
Lists the issues that are optional to fix before upgrading. The manual warnings cannot be fixed by running a script.
The following table describes the information in the column:
Column
Description
Ref. #
Row number
Check Code
Code that identifies the data issue
Description
Description of the issue that caused the error
Object Name
Name of the base object that the issue affects
Warning of Columns Unrelated to Hierarchy Manager in Hierarchy Relationship Base Objects
Lists the base object table name, the name of the user column, and the number of records that the upgrade process merges. The upgrade process merges duplicate hierarchy manager relationship base objects records so that the MDM Hub can maintain the effective periods in the cross-reference table. Assess the impact that the merge has on the user columns.
0 COMMENTS
We’d like to hear from you!