locked
Failure of SSMA for Oracle v7.3.0 in server side mode data migration, cannot load assembly RRS feed

  • Question

  • Ran SSMA for Oracle v7.3.0. Instance - Microsoft SQL Server Enterprise (64-bit) 2016. Version - 13.0.4422.0.8, 8 cores, 16Gb RAM.

    Schema converted OK, Runs OK in Client Side Data Migration mode. Tried to run in Server Side Data Migration mode, got exception below, captured with Profiler:

    ----------------------------------------------------------------------------------------------------------------------------------------------

    exec sp_executesql N'EXECUTE [msdb].[dbo].[sp_agent_log_job_history] @job_id = @P1, @is_system = @P2, @step_id = @P3, @sql_message_id = @P4, @sql_severity = @P5, @run_status = @P6, @run_date = @P7, @run_time = @P8, @run_duration = @P9, @operator_id_emailed = @P10, @operator_id_netsent = @P11, @operator_id_paged = @P12, @retries_attempted = @P13, @session_id  = @P14, @message = @P15',N'@P1 uniqueidentifier,@P2 int,@P3 int,@P4 int,@P5 int,@P6 int,@P7 int,@P8 int,@P9 int,@P10 int,@P11 int,@P12 int,@P13 int,@P14 int,@P15 nvarchar(4000)','EEC40C9F-51B8-48B0-8F26-1E606AF73484',0,1,0,0,0,20170427,151137,1,0,0,0,0,6033,N'Executed as user: DOMAIN\account. Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly ''Microsoft.SSMA.Framework.Generic.AbstractTelemetryProvider, Version=7.3.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'' or one of its dependencies. The system cannot find the file specified.     at Microsoft.SSMA.Framework.SqlServer.DataMigration.Default.BCPDataMigration.DefaultBCPDataMigrationTool.MainImpl(String[] args)     at Microsoft.SSMA.Framework.Oracle.SqlServer.DataMigration.BCPDataMigration.BCPDataMigrationTool.Main(String[] args).  Process Exit Code 255.  The step failed.'

    ----------------------------------------------------------------------------------------------------------------------------------------------

    Checked assembly is deployed, see below from sys.assemblies:

    name principal_id assembly_id clr_name permission_set permission_set_desc is_visible create_date modify_date is_user_defined
    Microsoft.SSMA.Framework.Generic.AbstractTelemetryProvider 1 65549 microsoft.ssma.framework.generic.abstracttelemetryprovider, version=7.3.0.0, culture=neutral, publickeytoken=31bf3856ad364e35, processorarchitecture=msil 3 UNSAFE_ACCESS 0 2017-04-27 15:07:13.660 2017-04-27 15:07:13.660 1

    ----------------------------------------------------------------------------------------------------------------------------------------------

    Uninstalled/reinstalled SSMA, same error.

    Please advise what can be the cause.

    Regards

    Pavlo Khytko

    Thursday, April 27, 2017 5:46 AM

Answers

  • Hey Pavlo

    Did you ever find a fix for this?  I am encountering the same issue.

    Regards

    Steve

    • Marked as answer by pkhytko Tuesday, May 9, 2017 11:06 PM
    Monday, May 8, 2017 6:55 AM

All replies

  • Hey Pavlo

    Did you ever find a fix for this?  I am encountering the same issue.

    Regards

    Steve

    • Marked as answer by pkhytko Tuesday, May 9, 2017 11:06 PM
    Monday, May 8, 2017 6:55 AM
  • Hi Steve

    Please find below MS support replay, works OK for me.

    Solution

    ====================

    Involved SSMA group and we suggested below:

    SSMA comes in two pieces: client tool and extension pack, which should be installed on the target server. Our external BCP tool failed, that is being executed as part of the agent job. In this case it looks for the dll in the SQL Server instance bin folder, for example: C:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\Binn\Microsoft SQL Server Migration Assistant for Oracle Extension Pack\bin. We need to verify if required dll is available there. And if not, we need to copy it over from the C:\Microsoft SQL Server Migration Assistant for Oracle Extension Pack\bin and try doing the server-side migration again.

    In addition, Product Group was able to reproduce the issue this issue will be fixed in the next release.

    Again, thanks for your time and patience in this matter, and thank you for choosing Microsoft!

     

    Have a great day!

    • Proposed as answer by Davy_Wang Tuesday, May 9, 2017 10:04 AM
    Monday, May 8, 2017 10:33 PM
  • Hi pkhytko,

    Glad to hear that you have resolved the issue. Please make corresponding replies as answer as it would benefit others when they are reading this thread. 

    If you have any other questions, please let me know.

    Regards,
    Davy

    MSDN Community Support<br/> Please remember to click &quot;Mark as Answer&quot; the responses that resolved your issue, and to click &quot;Unmark as Answer&quot; if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact <a href="mailto:MSDNFSF@microsoft.com">MSDNFSF@microsoft.com</a>.

    Tuesday, May 9, 2017 10:05 AM
  • Thanks Pavlo,

    Hit the nail on the head.  Problem solved.  Now I just need to let it run for a week to migrate a 1.5Billion row table.  :)

    Thanks again

    Steve

    Tuesday, May 16, 2017 5:38 AM