My Oracle Support Banner

SCHEMA VALIDATION UTILITY (SVU) (Doc ID 286619.1)

Last updated on AUGUST 10, 2018

Applies to:

Portal - Version 9.0.4 to 11.1.1.6.0 [Release 10g to FMW11g]
Information in this document applies to any platform.

Purpose

This technical note describes the Schema Validation Utility (SVU). This utility is used to report and cleanup any data inconsistencies in the Portal schema. The utility can be used to validate some of the Page Group objects and DB Provider objects. The various types of validations performed by the SVU are described in detail in this technical note.

Last Revised: October 29, 2013

Scope

For Portal Administrator who need to run portal Export/Imports or to clean data inconsistencies identified in the Portal.

Details

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Purpose
Scope
Details
 1. When to run the Schema Validation Utility?
 2. Why run the Schema Validation Utility?
 3. How to get the Schema Validation Utility?
 4. Running the SVU
 5. What validations are performed by the Schema validation utility Validating Page Groups?
 5.1. Validating Page Groups
 5.1.1. Validate categories associated with page groups
 5.2. Validating Page and Item Attributes
 5.2.1. Validate item type - attribute associations
 5.2.2. Validate item type function - attribute associations
 5.2.3. Validate page type - attribute associations
 5.2.4. Validate the page type attributes for the default language
 5.2.5. Validate page type function - attribute associations
 5.3. Validating Pages
 5.3.1. Validate styles used by pages
 5.3.2. Validate categories used by pages
 5.3.3. Validate parent for personal pages
 5.3.4. Validate if page attributes belong to existing attributes
 5.3.5. Validate if page attributes are associated with existing page type attributes
 5.4. Validating Regions
 5.4.1. Validate if regions belong to existing pages
 5.4.2. Validate style used by regions
 5.4.3. Validate if region attributes belong to existing attributes
 5.5. Validating Styles
 5.5.1. Validate if settings are associated with existing styles
 5.6. Validating Items
 5.6.1. Validate if items are associated with existing pages
 5.6.2. Validate if items are associated with existing regions
 5.6.3. Validate if items exist in wwv_things table
 5.7. Validating Things
 5.7.1. Validate if items are associated with existing pages
 5.7.2. Validate if items are associated with Correct Region IDs
 5.7.3. Validate if items are associated with existing regions
 5.7.4. Validate if things are associated with existing items
 5.7.5. Validate if portlet instance items have corresponding instances
 5.7.6. Validate parent ID for items
 5.7.7. Validate versions for items
 5.7.8. Validate attributes associated with items
 5.7.9. Validate if item attributes are associated with existing attributes
 5.7.10. Validate if item attributes are associated with existing item type attributes
 5.7.11. Validate SUBTYPE and SUBTYPESITEID of Items
 5.7.12. Validate item metadata
 5.7.13. Validate files associated with items
 5.8. Validating Portlets
 5.8.1. Validate page portlets
 5.8.2. Validate if portlet instances belong to registered providers
 5.8.3. Validate portlet instances against the portlet metadata repository
 5.8.4. Validate portlet instances against items
 5.9. Validating Database Providers
 5.9.1. Validate version for DB PROVIDERS
 5.9.2. Validate status for DB PROVIDERS
 5.9.3. Validate components
 5.9.4. Validate version for components
 5.9.5. Validate references to LINK/LOVs
 6. Interpreting the Report
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.