Skip to Main Content
Forums

Oracle Database Discussions

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

ORA-29013: SSL MAC verification failure

Paul JorstadMar 16 2021

I'm trying to call a REST endpoint from the database. It is https and I've configured a wallet for such, and it works for many servers, but not one particular, I get ORA-29013: SSL MAC verification failure, but not 100% of the calls. Suddenly it works and then fails again. When searching for that error message, it says I have to open a SR, which I've done. But after over a week, I have still no soultion. So - is there other who have got this error and found a reason and a soultion for it?
Version 19.8, StandardEdtion, Windows 2016 server

Comments

Smuckers

"...and PDF printing using ORDS still works"

In part it depends on exactly what you mean by 'PDF Printing'.  The release notes are referring specifically to Apache FOP PDF Support.  If you create a Report Layout in Apex with an XSL-FO file, it is (or was) possible to use built-in Apache FOP support in ORDS to apply that layout to the PDF document that gets generated. The XSL-FO layout can do things like setting margins, adding headers/footers, changing fonts, etc.  This capability is what is disappearing from ORDS.

If you are creating PDF files from Apex without the use of the Apache FOP functionality, then this release note has no impact to you. I create lots of PDF files from Apex using various methods -- normally via the pdf package created by Anton Scheffer.  I've looked into using XSL-FO and Apache FOP because I'd *like* to add some formatting, but never taken the time to get into the nuts & bolts of actually doing so. I'm looking forward to seeing what they replace the capability with because I've always felt that the current method was simply too much work (and too skimpily documented).  Judging by the scarcity of articles/blogs/etc. online of people using Apex Report Layouts, I think I'm not alone in my opinion.

1 - 1

Post Details

Added on Mar 16 2021
#general-database-discussions
28 comments
2,208 views
2 mentions