To resolve this issue, get correct values of ASO related parameters and provide them in the JDBC connection string (You can get the exact values of these parameters from sqlnet.ora file, which is present in Oracle server machine).
Example: Below are the contents of sqlnet.ora file:
SQLNET.ENCRYPTION_CLIENT = REQUIRED
SQLNET.ENCRYPTION_TYPES_CLIENT = (RC4_256) SQLNET.CRYPTO_CHECKSUM_CLIENT = REQUIRED SQLNET.CRYPTO_CHECKSUM_TYPES_CLIENT = (MD5)
Since you mentioned a specific ticket ID related to the outage, it would be beneficial to follow up with Microsoft support. Provide them with the error details and the timeline of when the issue started to see if there are any known issues or fixes from their end.
https://knowledge.informatica.com/s/article/498384?language=en_US