SSMA Server-seitige Datenmigrations-Engine

Benjamin Durst 0 Reputation points
2026-07-30T12:51:12.61+00:00

Problemzusammenfassung: Die Server Side Data Migration Engine in SSMA für Oracle 10.5 schlägt sofort ohne Datenmigration und ohne Erstellung eines SQL-Agent-Jobs fehl. Client-seitige Migration funktioniert erfolgreich.   

Environment 

Oracle Database 12c Enterprise Edition 12.2.0.1.0. SQL Server 2022 Standard 16.0.4265.3. SSMA 10.5 and Extension Pack 10.5. Oracle Client 19c. Migration VM: 8 vCPU, 64 GB RAM. 

Migration Settings 

Server Side Migration Engine enabled, Use 32-bit Engine=No, Batch Size=100000, Parallel Mode=Auto, Timeout=1440.

Erwartetes Verhalten 

SSMA sollte ein Migrationspaket erstellen, einen SQL-Agent-Job erstellen und Daten direkt von Oracle zu SQL Server migrieren. 

Tatsächliches Verhalten 

Die Migration stoppt nach dem Start der Datenmigrations-Engine. 0 Tabellen migriert, 1 Tabelle fehlgeschlagen. Kein detaillierter Fehler. Kein SQL-Agent-Job erstellt. 

Durchgeführte Validierung 

SQL Agent läuft. Die Oracle-Konnektivität wurde mit tnsping (30 ms) bestätigt. BCP verfügbar. Erweiterungspack installiert. CLR aktiviert. SSMA Oracle-Assemblies präsentieren. Client-seitige Migration funktioniert. 

Beobachtete Umweltergebnisse 

SQL-Agent-Konto: NT Service\SQLSERVERAGENT. Zwei Oraclehome entdeckt. bcp.exe anwesend. Oracle Parallel Query bestätigt. 

Fragen

Warum endet die Server-Side-Migration vor der Erstellung eines SQL-Agent-Jobs? Gibt es bekannte Probleme mit SSMA 10.5, Oracle Client 19c oder SQL Server 2022? Wie kann eine detaillierte Server-seitige Migrationsprotokollierung aktiviert werden? Können mehrere Oracle Homes dieses Verhalten verursachen? 

SQL Server Migration Assistant
SQL Server Migration Assistant

A Microsoft tool designed to automate database migration to SQL Server from Access, DB2, MySQL, Oracle, and SAP ASE.

1 answer

Sort by: Most helpful
Most helpful Newest Oldest

  1. AI answer

    2026-07-30T12:51:29.5766667+00:00

    English-only support.

    For the described behavior, the supported checks from the available guidance are:

    1. Verify that Server Side Data Migration Engine is selected in Tools > Project Settings > General > Migration.
    2. Confirm the prerequisites for server-side migration are all met:
      • SSMA for Oracle Extension Pack is installed on the SQL Server instance.
      • SQL Server Agent service is running.
      • Oracle providers are installed on the computer running SSMA.
    3. If server-side migration is selected and the extension pack is not installed correctly, SSMA can fail with this error: 
         SSMA Data Migration components were not found on SQL Server, server-side data migration will not be possible. Please check if Extension Pack is installed correctly.
    4. After extension pack installation, verify the server-side components exist:
      • The sysdb database is present.
      • The ssma_oracle.bcp_migration_packages table exists in sysdb.
      • SQL Server Agent jobs are created during migration with names like ssma_oracle data migration package {GUID}.
    5. Verify CLR is enabled. If CLR is not enabled, SSMA can return: 
         SSMA could not retrieve the extension pack assembly version information. Reinstall the extension pack on the database server.
    6. If the server-side engine continues to fail, the documented fallback is to use the Client Side Data Migration Engine, which does not depend on the extension pack being available.

    Supported facts about the specific questions:

    • Why should a SQL Agent job appear? Server-side migration uses the SSMA data migration engine running on the SQL Server box as a SQL Agent job.
    • Can missing server-side components prevent job creation? Yes. If the extension pack is not installed correctly, server-side migration is not possible.
    • How to enable detailed server-side migration logging? No procedure for enabling additional detailed logging is provided in the available guidance.
    • Can multiple Oracle homes cause this behavior? No supported statement is available in the provided guidance.
    • Are there known issues specific to SSMA 10.5, Oracle Client 19c, or SQL Server 2022 for this symptom? No supported statement is available in the provided guidance.

    A relevant Microsoft Q&A recommendation for server-side failures is to:

    • uninstall and reinstall the Extension Pack,
    • confirm version alignment between the SSMA client and Extension Pack,
    • verify the SQL Server Agent service account has read/execute access to the Extension Pack directory,
    • and test client-side migration with reduced batch sizes if server-side still fails.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.