You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
title: "Assessing Oracle Schemas for Conversion (OracleToSQL)"
3
-
description: "Assessing Oracle Schemas for Conversion (OracleToSQL)"
2
+
title: "Assess Oracle Schemas for Conversion (OracleToSQL)"
3
+
description: Learn how to assess Oracle schemas for conversion.
4
4
author: nilabjaball
5
5
ms.author: niball
6
-
ms.date: "01/19/2017"
6
+
ms.reviewer: randolphwest
7
+
ms.date: 06/03/2025
7
8
ms.service: sql
8
9
ms.subservice: ssma
9
10
ms.topic: conceptual
@@ -14,69 +15,66 @@ f1_keywords:
14
15
helpviewer_keywords:
15
16
- "Analyzing Conversion Problems"
16
17
---
17
-
# Assessing Oracle Schemas for Conversion (OracleToSQL)
18
-
Before you load objects and migrate data to [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)], you should determine how complex the migration will be and how much time the migration will take. SSMA can create an assessment report that shows the percentage of objects that will be successfully converted. SSMA also lets you view the specific issues that cause conversion failures.
19
-
20
-
## Creating Assessment Reports
21
-
When it creates this assessment report, SSMA converts the selected Oracle database objects to [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] syntax, and then shows the results.
22
-
23
-
**To create an assessment report**
24
-
25
-
1. In Oracle Metadata Explorer, select the schemas to assess.
26
-
27
-
2. To omit individual objects, clear the check boxes next to those.
28
-
29
-
3. Right-click **Schemas**, and then select **Create Report**.
30
-
31
-
You can also analyze individual objects by right-clicking an object, and then selecting **Create Report**.
32
-
33
-
SSMA will show progress in the status bar at the bottom of the window. If the Output pane is visible, you will also see messages in the Output pane.
34
-
35
-
When the assessment is complete, the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Migration Assistant for Oracle: Assessment Report window will appear.
36
-
37
-
## Using Assessment Reports
38
-
The Assessment Report window contains three panes:
39
-
40
-
- The left pane contains the hierarchy of objects that are included in the assessment report. You can browse the hierarchy, and select objects and categories of objects to view conversion statistics and code.
41
-
42
-
- The contents of the right pane depends on the item that is selected in the left pane.
43
-
44
-
If a group of objects is selected, such a schema, or if a table is selected, the right pane contains a Conversion statistics pane and an Objects by Categories pane. The Conversion Statistics pane shows the conversion statistics for the selected objects. The Objects by Categories pane shows the conversion statistics for the object or categories of objects.
45
-
46
-
If a function, package, procedure, sequence, or view is selected, the right pane contains statistics, source code, and target code.
47
-
48
-
- The top area shows the overall statistics for the object. You might have to expand **Statistics** to view this information.
49
-
50
-
- The Source area shows the source code of the object that is selected in the left pane. The highlighted areas show problematic source code.
51
-
52
-
- The Target area shows the converted code. Red text shows problematic code and error messages.
53
-
54
-
- The bottom pane shows conversion messages, grouped by message number. You can click **Errors**, **Warnings**, or **Info** to view categories of messages, and then expand a group of messages. Click an individual message to select the object in the left pane and display the details in the right pane.
55
-
56
-
## Analyzing Conversion Problems By Using the Assessment Report
57
-
The Conversion Statistics pane shows the conversion statistics. If the percentage for any category is less than 100 percent, you should determine why the conversion was not successful.
58
-
59
-
**To view conversion problems**
60
-
61
-
1. Create the assessment report by using the instructions in the previous procedure.
62
-
63
-
2. In the left pane, expand schemas or folders that have a red error icon. Continue expanding items until you select an individual item that failed conversion.
64
-
65
-
3. At the top of the Source pane, click **Next Problem**.
66
-
67
-
The problematic code is highlighted, as is the related code in the Target Navigation pane.
68
-
69
-
4. Review any error messages, and then determine what you want to do with the object that caused the conversion problem:
70
-
71
-
- Update the Oracle syntax in SSMA. You can update the syntax for procedures, functions, triggers, packaged functions and packaged procedures. To update the syntax, select the object in the Oracle Metadata Explorer pane, click the **SQL** tab, and then modify the SQL code. When you navigate away from the item, you will be prompted to save the updated syntax. You can view the reported errors for the object on the **Report** tab.
72
-
73
-
- In Oracle, you can modify the Oracle object to remove or revise problematic code. To load the updated code into SSMA, you will have to update the metadata. For more information, see [Connecting to Oracle Database (OracleToSQL)](../../ssma/oracle/connecting-to-oracle-database-oracletosql.md).
74
-
75
-
- You can exclude the object from migration. In [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Metadata Explorer and Oracle Metadata Explorer, clear the check box next to the item before you load the objects into [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] and migrate data from Oracle.
[Migrating Oracle Databases to SQL Server (OracleToSQL)](../../ssma/oracle/migrating-oracle-databases-to-sql-server-oracletosql.md)
82
-
18
+
19
+
# Assess Oracle schemas for conversion (OracleToSQL)
20
+
21
+
Before you load objects and migrate data to [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)], you should determine how complex the migration will be and how much time the migration will take. Microsoft SQL Server Migration Assistant (SSMA) for Oracle can create an assessment report that shows the percentage of objects that will be successfully converted. With SSMA, you can also view the specific issues that cause conversion failures.
22
+
23
+
## Create assessment reports
24
+
25
+
When SSMA creates an assessment report, it converts the selected Oracle database objects to [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] syntax, and then shows the results.
26
+
27
+
To create an assessment report:
28
+
29
+
1. In Oracle Metadata Explorer, select the schemas that you want to assess.
30
+
31
+
1. Clear the checkboxes next to any individual objects you want to exclude.
32
+
33
+
1. Right-click **Schemas**, and then select **Create Report**. You can also analyze individual objects by right-clicking an object, and then selecting **Create Report**.
34
+
35
+
SSMA shows progress in the status bar at the bottom of the window. If the **Output** pane is visible, you also see messages there. When the assessment is complete, the **[!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] Migration Assistant for Oracle: Assessment Report** window appears.
36
+
37
+
## Use assessment reports
38
+
39
+
The **Assessment Report** window contains two panes:
40
+
41
+
- The left pane contains the hierarchy of objects that are included in the assessment report. To view conversion statistics and code, you can browse the hierarchy and select objects and categories of objects.
42
+
- The contents of the right pane correlate to the item you selected on the left pane.
43
+
44
+
If a group of objects is selected, such as a schema, or if a table is selected, the right pane contains a **Conversion Statistics** pane and an **Objects by Categories** pane. The **Conversion Statistics** pane shows the conversion statistics for the selected objects. The **Objects by Categories** pane shows the conversion statistics for the object or the categories of objects.
45
+
46
+
If a function, package, procedure, sequence, or view is selected, the right pane contains statistics, source code, and target code.
47
+
48
+
- The top area shows the overall statistics for the object. You might have to expand **Statistics** to view this information.
49
+
- The **Source** area shows the source code of the object you selected on the left pane. The highlighted areas show problematic source code.
50
+
- The **Target** area shows the converted code. Problematic code and error messages are displayed in red text.
51
+
- The bottom pane shows conversion messages, grouped by message number. You can select **Errors**, **Warnings**, or **Info** to view categories of messages, and then expand a group of messages. Select an individual message. Then select the object on the left pane and display the details on the right pane.
52
+
53
+
## Analyze conversion problems by using the assessment report
54
+
55
+
The **Conversion Statistics** pane shows the conversion statistics. If the percentage for any category is less than 100 percent, you should determine why the conversion wasn't successful.
56
+
57
+
### View conversion problems
58
+
59
+
1. Create the assessment report by using the instructions in the previous procedure.
60
+
61
+
1. On the left pane, expand schemas or folders that have a red error icon. Continue expanding items until you select an individual item that failed conversion.
62
+
63
+
1. At the top of the **Source** pane, select **Next Problem**.
64
+
65
+
The problematic code is highlighted. The related code is also highlighted on the **Target Navigation** pane.
66
+
67
+
1. Review any error messages, and then determine what you want to do with the object that caused the conversion problem. You can:
68
+
69
+
- Update the Oracle syntax in SSMA. You can update the syntax for procedures, functions, triggers, packaged functions, and packaged procedures.
70
+
71
+
To update the syntax, select the object on the Oracle Metadata Explorer pane, select the **SQL** tab, and then modify the SQL code. When you navigate away from the item, you're prompted to save the updated syntax. You can view the reported errors for the object on the **Report** tab.
72
+
73
+
- In Oracle, you can modify the Oracle object to remove or revise problematic code. To load the updated code into SSMA, you have to update the metadata. For more information, see [Connecting to Oracle Database](connecting-to-oracle-database-oracletosql.md).
74
+
75
+
- You can exclude the object from migration. In [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] Metadata Explorer and Oracle Metadata Explorer, clear the checkbox next to the item. Then load the objects into [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] and migrate data from Oracle.
0 commit comments