Table of Contents
- Title and Copyright Information
- Preface
-
1
Overview of Migrating Databases to Unicode
- 1.1 What Is a Database Character Set?
- 1.2 Introduction to Character Set Migration
- 1.3 Why Unicode Is the Right Choice
-
1.4
About Character Set Migration Tools
- 1.4.1 Identification of Migration Issues with the Database Character Set Scanner (CSSCAN)
- 1.4.2 Changing Character Set Metadata Using the CSALTER Script
- 1.4.3 Converting Character Data Using the Export/Import and Data Pump Utilities
- 1.4.4 Migrating a Database Using the Database Migration Assistant for Unicode
- 1.5 Overview of Character Set Migration Considerations
-
2
Getting Started with the DMU
- 2.1 Using the Database Migration Assistant for Unicode: A Roadmap
- 2.2 Introduction to the DMU Interface and Navigation
- 2.3 Overview of Requirements and Security Considerations
- 2.4 Performing First Tasks with the DMU
- 2.5 Introduction to the DMU User Interface
- 2.6 Overview of Data Preparation
- 2.7 Overview of Data Conversion
- 3 Viewing and Setting Object Properties in the DMU
-
4
Performing Basic DMU Tasks
- 4.1 Initializing the Database
- 4.2 Refreshing, Reinstalling, Upgrading, and Uninstalling the DMU Repository
-
4.3
Scanning the Database
- 4.3.1 Setting Database Properties
- 4.3.2 Scanning the Database with the Scan Wizard
- 4.3.3 Monitoring the Progress of a Scan
- 4.3.4 Viewing the Database Scan Report
- 4.3.5 Overview of the Database Scan Report
- 4.3.6 Generating the Problem Data Report
- 4.3.7 Scanning the PL/SQL Code
-
4.3.8
Scanning the Database with the DMU Command-Line Scanner (DMU-CLS)
- 4.3.8.1 Prerequisites for Using the DMU-CLS
- 4.3.8.2 Starting the DMU-CLS
- 4.3.8.3 DMU-CLS Parameters
- 4.3.8.4 DMU-CLS Scopes for Database Scan and Report Generation
- 4.3.8.5 DMU-CLS Scan Modes
- 4.3.8.6 DMU-CLS Execution Statuses
- 4.3.8.7 DMU-CLS Operations Examples
- 4.3.8.8 DMU-CLS Parameter File
- 4.3.8.9 Managing a DMU Repository Using the DMU-CLS
- 4.3.8.10 DMU-CLS Scan Report
- 4.3.8.11 DMU-CLS Problem Data Report
- 4.3.8.12 DMU-CLS Error Messages
- 4.4 Cleansing the Data
- 4.5 Converting the Database
- 4.6 Validating Data as Unicode
- 4.7 Creating a Diagnostic Package
-
5
Advanced Topics in the DMU
- 5.1 Excluding Columns and Tables From Migration
-
5.2
Handling Non-Accessible Data
- 5.2.1 Read-Only Tables Considerations
- 5.2.2 Read-Only Tablespaces Considerations
- 5.2.3 Offline Tablespaces and Data Files Considerations
-
5.2.4
Working With External Tables
- 5.2.4.1 Cleansing External Tables
- 5.2.4.2 Cleansing Length Issues
- 5.2.4.3 Correcting Character Set Declaration of ORACLE_LOADER Files
- 5.2.4.4 Correcting Character Set Declaration of ORACLE_DATAPUMP Files
- 5.2.4.5 Fixing Corrupted Character Codes
- 5.2.4.6 Handling Binary Data
- 5.2.4.7 Performance Considerations for ORACLE_LOADER Files
- 5.3 Migrating Data Dictionary Contents
- 5.4 Working with Multilingual Columns
- 5.5 Advanced Convertibility Issues
- 5.6 Adapting Applications for Unicode Migration
- 5.7 Exporting and Importing Migration Profile
- 5.8 Near-Zero Downtime Database Migration to Unicode
- 5.9 Repairing Database Character Set Metadata
- 5.10 DMU Accessibility Information
-
6
Using the DMU to Cleanse Data
- 6.1 Cleansing Data
- 6.2 Viewing Data
- 6.3 Editing Data
- 6.4 Displaying Data
- 6.5 Modifying Columns
- 6.6 Scheduling Column Modification
- 6.7 Modifying Attributes
- 6.8 Scheduling Attribute Modification
- 6.9 Ignoring Convertibility Issues
- 6.10 Bulk Cleansing
- 6.11 Cleansing Scenario 1: A Database with No Issues
- 6.12 Cleansing Scenario 2: Cleansing Expansion Issues
- 6.13 Cleansing Scenario 3: Cleansing Invalid Representation Issues
- A Third-Party License Information
- Glossary
- Index