Reason for moving the function outside DB1
A reader, October 01, 2021 - 5:12 am UTC
Thank you for the response Chris.
The function invokes a C lib via External Procedure call. The lib do some processing and returns the result back to the function.
The function has to be moved to DB2 (a non-ExaCC DB) because DB1 is in ExaCC and we are not allowed to put the C lib in ExaCC.
Also, due to some security restrictions, we can not move logic from the C lib in DB.
October 04, 2021 - 4:47 am UTC
I spoke to some of our Exa CC people - they replied
While we recommend to not install additional software on servers (as especially additional RPMs will affect OS patching/upgrade), it never says anywhere you are not allowed to install additional software….
One option you could consider is using a docker container for additional software, as this does not interfere with the OS updates then… See: Decoupling RPM Dependencies, running Oracle R Distribution (ORD) on Exadata Database Nodes in Docker (Doc ID 2257680.1)
If this is the case, you may want to put the software onto an ACFS folder, to have a common location across the cluster (and not to worry to have to update each node individually).