Recent Discussions
Oracle 2.0 Upgrade Woes with Self-Hosted Integration Runtime
This past weekend my ADF instance finally got the prompt to upgrade linked services that use the Oracle 1.0 connector, so I thought, "no problem!" and got to work upgrading my self-hosted integration runtime to 5.50.9171.1 Most of my connection use service_name during authentication, so https://learn.microsoft.com/en-us/azure/data-factory/connector-oracle?tabs=data-factory, I should be able to connect using the Easy Connect (Plus) Naming convention. When I do, I encounter this error: Test connection operation failed. Failed to open the Oracle database connection. ORA-50201: Oracle Communication: Failed to connect to server or failed to parse connect string ORA-12650: No common encryption or data integrity algorithm https://docs.oracle.com/error-help/db/ora-12650/ I did some digging on this error code, and the troubleshooting doc suggests that I reach out to my Oracle DBA to update Oracle server settings. Which, I did, but I have zero confidence the DBA will take any action. https://learn.microsoft.com/en-us/azure/data-factory/connector-troubleshoot-oracle Then I happened across this documentation about the upgraded connector. https://learn.microsoft.com/en-us/azure/data-factory/connector-oracle?tabs=data-factory#upgrade-the-oracle-connector Is this for real? ADF won't be able to connect to old versions of Oracle? If so I'm effed because my company is so so legacy and all of our Oracle servers at 11g. I also tried adding additional connection properties in my linked service connection like this, but I have honestly no idea what I'm doing: Encryption client: accepted Encryption types client: AES128, AES192, AES256, 3DES112, 3DES168 Crypto checksum client: accepted Crypto checksum types client: SHA1, SHA256, SHA384, SHA512 But no matter what, the issue persists. :( Am I missing something stupid? Are there ways to handle the encryption type mismatch client-side from the VM that runs the self-hosted integration runtime? I would hate to be in the business of managing an Oracle environment and tsanames.ora files, but I also don't want to re-engineer almost 100 pipelines because of a connector incompatability.
Log Reader Agent throwing errors on Azure SQL Managed Instance
I configured Azure SQL Managed Instance for transactional replication, it is a publisher with local distributor. I got it set up and the snapshot agent runs successfully, but the log reader agent is throwing errors: The last step did not log any message! (Source: MSSQL_REPL, Error number: MSSQL_REPL22037) Get help: http://help/MSSQL_REPL22037 I tried setting up with TSQL script as well as via replication wizard. Still no luck with the logreader agent. Note - this instance of MI was migrated from on-premise. I verified that the replAgentUser was created and does exist. USE master GO EXEC sp_adddistributor = @@SERVERNAME, @password = NULL GO EXEC sp_adddistributiondb @database = N'distribution' , @min_distretention = 0 , _distretention = 72 , @history_retention = 48 , @deletebatchsize_xact = 5000 , @deletebatchsize_cmd = 2000 , @security_mode = 1 GO EXEC sp_adddistpublisher @publisher = @@SERVERNAME , @distribution_db = N'distribution' , @security_mode = 0 , @login = '<login>' , @password = '<password>' , @working_directory = N'\\<name>.file.core.windows.net\replshare' , @storage_connection_string = N'DefaultEndpointsProtocol=https;AccountName=<name>;AccountKey=<key>;EndpointSuffix=core.windows.net' GO EXEC sp_replicationdboption @dbname = N'db1' , @optname = N'publish' , @value = N'true' GO USE [db1] GO -- Adding the transactional publication EXEC sp_addpublication @publication = N'pub1' , @description = N'Transactional publication' , @sync_method = N'concurrent' , @retention = 0 , @allow_push = N'true' , @allow_pull = N'true' , @allow_anonymous = N'true' , @enabled_for_internet = N'false' , _in_defaultfolder = N'true' , @compress_snapshot = N'false' , @ftp_port = 21 , @ftp_login = N'anonymous' , @allow_subscription_copy = N'false' , @add_to_active_directory = N'false' , @repl_freq = N'continuous' , @status = N'active' , @independent_agent = N'true' , _sync = N'true' , @allow_sync_tran = N'false' , @autogen_sync_procs = N'false' , @allow_queued_tran = N'false' , @allow_dts = N'false' , @replicate_ddl = 1 , @allow_initialize_from_backup = N'false' , @enabled_for_p2p = N'false' , @enabled_for_het_sub = N'false' GO EXEC sys.sp_changelogreader_agent @job_login = '<login>' , @job_password = '<password>' , @publisher_security_mode = 0 , @publisher_login = N'<login>' , @publisher_password = '<password>' GO EXEC sp_addpublication_snapshot @publication = N'pub1' , @frequency_type = 1 , @frequency_interval = 0 , @frequency_relative_interval = 0 , @frequency_recurrence_factor = 0 , @frequency_subday = 0 , @frequency_subday_interval = 0 , @active_start_time_of_day = 0 , @active_end_time_of_day = 235959 , @active_start_date = 0 , @active_end_date = 0 , @job_login = '<login>' , @job_password = '<password>' , @publisher_security_mode = 0 , @publisher_login = N'<login>' , @publisher_password = '<password>' GO EXEC sp_addarticle @publication = N'pub1' , @article = N'table1' , @source_owner = N'dbo' , @source_object = N'table1' , @type = N'logbased' , @description = N'' , @creation_script = N'' , @pre_creation_cmd = N'drop' , @schema_option = 0x00000000080350DF , @identityrangemanagementoption = N'none' , @destination_table = N'table1' , @destination_owner = N'dbo' , @status = 24 , @vertical_partition = N'false' , @ins_cmd = N'CALL [sp_MSins_dbotable1]' , @del_cmd = N'CALL [sp_MSdel_dbotable1]' , @upd_cmd = N'SCALL [sp_MSupd_dbotable1]' GO EXEC sp_startpublication_snapshot @publication = N'pub1'; GO Looking at the results of MSlogreader_history table, all changes are being replicated, however there are many runstatus = 6, which means failure.
Azure data factory nested statements displaying as closed by default
Whenever I open an azure data factory pipeline now all nested activities such as foreach loops and if statements are closed so I can't see what's inside them without clicking the expand button. But then clicking the expand button often moves all other activities around the page. Is there a way to have these activities expanded by default? They used to be expanded by default but this stopped happening yesterday afternoon.
Recent Blogs
- Authors: Johannes Schuetzner, Software Engineer at Mercedes-Benz & Nacho Alonso Portillo, Principal Program Manager at Microsoft When you think of Mercedes-Benz, you think of innovation, precision...Sep 24, 2025
- At the heart of every digital transformation is data. This year’s Migrate and Modernize Summit was more than a showcase of new features—it was a demonstration of how Microsoft Azure is reimagining th...Sep 23, 2025
