When Library is loaded after setting DBFIPS_140
(Doc ID 2191845.1)
Last updated on JANUARY 03, 2020
Applies to:
Oracle Database - Enterprise Edition - Version 12.1.0.2 and laterOracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
Goal
The Goal is to make aware of when the underlying library is loaded after setting DBFIPS_140 in the database to comply with FIPS.
Setting the database complaint to DBFIPS_140 can be done from the below document
From notes:
https://docs.oracle.com/database/121/DBSEG/asoappe.htm#DBSEG1041
"Be aware that setting DBFIPS_140 to TRUE and thus using the underlying library in FIPS mode incurs a certain amount of overhead when the library is first loaded. This is due to the verification of the signature and the execution of the self tests on the library. Once the library is loaded, then there is no other impact on performance."
From above note it is unclear as to when the library is loaded.
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |
| References |