Automic Workload Automation

 View Only
Expand all | Collapse all

Problems with Package.UTF8.DB.Migration v1.0.2

  • 1.  Problems with Package.UTF8.DB.Migration v1.0.2

    Posted Feb 26, 2024 05:44 AM
    Edited by Michael A. Lowry Feb 27, 2024 04:01 AM

    Automic Automation v24.0.0 was released a bit over a week ago. Version 24 adds support for UTF-8, and Broadcom helpfully provided a migration tool, Package.UTF8.DB.Migration, to help migrate AE databases that use other character sets to the UTF-8 character set.

    I'd like to advise anyone contemplating such a migration to wait until an update for the tool is released. The tool (v1.0.2) currently has bugs that can prevent a successful DB migration.

    During the weekend, we tried to use Package.UTF8.DB.Migration v1.0.2 to complete migration of a database to UTF-8. The online portion of the migration completed successfully, but the offline portion of that finalizes the migration did not go so well. Among other problems, we found that all of the ALTER TABLE … ADD CONSTRAINT statements in the 1st generated SQL script were invalid and could not be executed without modification/correction.

    We opened a support ticket with Broadcom.



  • 2.  RE: Problems with Package.UTF8.DB.Migration v1.0.2

    Posted Feb 27, 2024 05:35 AM

    Hi Michael. Thanks for the information. Bye. Donato



    ------------------------------
    Donato Faggella
    DevOps Engineer III
    Swisscom (Suisse) SA
    ------------------------------



  • 3.  RE: Problems with Package.UTF8.DB.Migration v1.0.2

    Posted Mar 26, 2024 10:54 AM

    Hi Michael,

    which database are you using? I'm currently struggling with MSSQL because of a prerequisite (a required command does not run on MSSQL 2022).

    regards,
    Peter



    ------------------------------
    Automic Certified Professional/Expert & Broadcom Knight

    For AUTOMIC trainings please check https://www.qskills.de/qs/workshops/automic/
    ------------------------------



  • 4.  RE: Problems with Package.UTF8.DB.Migration v1.0.2

    Posted Mar 26, 2024 11:49 AM
    Edited by Michael A. Lowry Mar 26, 2024 11:51 AM

    We use Oracle.  We ran into different problems than the one you describe.



  • 5.  RE: Problems with Package.UTF8.DB.Migration v1.0.2

    Broadcom Employee
    Posted Mar 27, 2024 03:48 AM

    Hi @Peter Grundler

    what is the command you are struggling with?

    Regards, Markus




  • 6.  RE: Problems with Package.UTF8.DB.Migration v1.0.2

    Posted Mar 27, 2024 08:15 AM

    Servus Markus,

    It's GRANT CREATE PUBLIC DATABASE LINK TO <destination DB user>

    Best regards,

    Peter 



    ------------------------------
    Automic Certified Professional/Expert & Broadcom Knight

    For AUTOMIC trainings please check https://www.qskills.de/qs/workshops/automic/
    ------------------------------



  • 7.  RE: Problems with Package.UTF8.DB.Migration v1.0.2

    Broadcom Employee
    Posted Mar 27, 2024 08:21 AM

    Servus Peter :-)

    What exactly is the issue with that command? Any error messages?

    thank you!

    Regards, Markus




  • 8.  RE: Problems with Package.UTF8.DB.Migration v1.0.2

    Posted Mar 27, 2024 10:07 AM

    Hi Markus,

    the error message is

    Msg 102, Level 15, State 1, Line 1
    Incorrect syntax near 'PUBLIC'.
     
    I have checked the Microsoft documentation (https://learn.microsoft.com/en-us/sql/t-sql/statements/grant-database-permissions-transact-sql?view=sql-server-ver16) and in fact, this command is not listed/supported.
    best regards,
    Peter


    ------------------------------
    Automic Certified Professional/Expert & Broadcom Knight

    For AUTOMIC trainings please check https://www.qskills.de/qs/workshops/automic/
    ------------------------------



  • 9.  RE: Problems with Package.UTF8.DB.Migration v1.0.2

    Broadcom Employee
    Posted Mar 27, 2024 10:30 AM

    Hi Peter,

    this is the command for Oracle. Let me find out the correct commands for MS-SQL and get back to you.

    Regards, Markus




  • 10.  RE: Problems with Package.UTF8.DB.Migration v1.0.2

    Posted Mar 27, 2024 10:46 AM

    Thank you Markus!

    It would be helpful - if possible - to discuss a correct and working procedure regarding MSSQL. Following the steps described in the documentation is currently not working.

    best regards,
    Peter



    ------------------------------
    Automic Certified Professional/Expert & Broadcom Knight

    For AUTOMIC trainings please check https://www.qskills.de/qs/workshops/automic/
    ------------------------------



  • 11.  RE: Problems with Package.UTF8.DB.Migration v1.0.2

    Broadcom Employee
    Posted Mar 27, 2024 11:40 AM
    Edited by Markus Embacher 30 days ago

    Hi Peter,

    here is an example for MS-SQL:

    USE [master]
    EXEC sp_addlinkedserver 
        @server=N'UC4_SOURCE', 
        @srvproduct=N'', 
        @provider=N'MSOLEDBSQL', 
        @datasrc=N'<datasource>',
        @catalog='ae';
    GO

    Pls have a look at sp_addlinkedserver (Transact-SQL) - SQL Server for the details. The above is just an example.

    After defining the link please test the connection before you try to run the migration:
    select count(*) from from UC4_SOURCE.ae.dbo.OH

    I'll address your feedback internally.

    Regards, Markus




  • 12.  RE: Problems with Package.UTF8.DB.Migration v1.0.2

    Posted Mar 27, 2024 08:59 AM
    Edited by Michael A. Lowry Mar 27, 2024 09:10 AM

    We initially ran into a similar problem. The schema user had neither the right to create a DB link nor the right to grant this authorization. We had to ask our DBA to create the DB link for us.



  • 13.  RE: Problems with Package.UTF8.DB.Migration v1.0.2

    Posted Mar 27, 2024 08:56 AM
    Edited by Michael A. Lowry Mar 27, 2024 08:56 AM

    Broadcom opened bug ID PCK_UTF8_DB-1 for the problems we reported. An update will be released soon. See AE v24 problems.