Locator

Contact

Locator

Vet Centers

Regional Benefits Offices

Regional Loan Centers

Cemetery Locations

VA Technical Reference Model v 25.7

Oracle Database

General Information

Technologies must be operated and maintained in accordance with Federal and Department security and privacy policies and guidelines. More information on the proper use of the TRM can be found on the TRM Proper Use Tab/Section.

Website:	Go to site
Description:	Oracle Database, also known as Oracle relational database management system (RDBMS) or Oracle Enterprise Database, is an object-relational database management system that includes Extensible Markup Language (XML) capabilities. There are many implementations of this product. There is a personal and express edition of this software that can be run on a local laptop or desktop. The standard or enterprise editions run on servers. This product can also be run in a cloud instance, on-premises, in a co-located environment or as a hybrid solution. This entry is specific to the enterprise editions. The TRM decisions in this entry only apply to technologies and versions owned, operated, managed, patched, and version-controlled by VA. This includes technologies deployed as software installations on VMs within VA-controlled cloud environments (e.g., VA Enterprise Cloud (VAEC)). Cloud services provided by the VAEC, which are listed in the VAEC Service Catalog, and those controlled and managed by an external Cloud Service Provider (i.e., SaaS) are not in the purview of the TRM. For more information on the use of cloud services and cloud-based products within VA, including VA private clouds, please see the Enterprise Cloud Solutions Office (ECSO) Portal at: https://dvagov.sharepoint.com/sites/OITECSO
Technology/Standard Usage Requirements:	Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information System Security Officer (ISSO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.
Section 508 Information:	This technology has not been assessed by the Section 508 Office. The Implementer of this technology has the responsibility to ensure the version deployed is 508-compliant. Section 508 compliance may be reviewed by the Section 508 Office and appropriate remedial action required if necessary. For additional information or assistance regarding Section 508, please contact the Section 508 Office at Section508@va.gov.
Decision:	View Decisions

Decision Source:	TRM Mgmt Group
Decision Process:	One-VA TRM v25.5
Decision Date:	05/15/2025 at 16:30:13 UTC
Aliases:	Oracle RDBMS, Oracle Enterprise Database
Introduced By:	Extended Tool List (ETL)
Vendor Name:	Oracle

Vendor Release Information

The Vendor Release table provides the known releases for the TRM Technology, obtained from the vendor (or from the release source).

You must be logged into the RSAA website prior to clicking the Attestation URLs or the URLs won't open.

Major versions and minor versions of that Major released on or after 09/14/2022 are NOT EXEMPT. Major Versions released before 09/14/2022 are EXEMPT as well as minor versions of that Major regardless of release date.

Version	Release Date	Vendor End of Life Date	Vendor Desupport Date
10.2.x	09/01/2005		07/13/2013
11.1.x	07/11/2007		08/30/2015
11.2.x	09/01/2009		12/31/2020
12.1.x	06/30/2013		07/31/2021
12.2.0.1.x	03/01/2017	11/30/2020	11/30/2020
18.x (12.2.0.2.x)	04/30/2018	06/08/2021	06/08/2021
19.x (12.2.0.3.x)	02/04/2019	04/30/2024	04/30/2027
21c (21.x)	12/01/2020	04/30/2024	04/30/2024
23c (23.x)	09/19/2023
23ai (23.x)	05/02/2024

Current Decision Matrix (04/22/2025)

Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information System Security Officer (ISSO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.

The VA Decision Matrix displays the current and future VAIT position regarding different releases of a TRM entry. These decisions are based upon the best information available as of the most current date. The consumer of this information has the responsibility to consult the organizations responsible for the desktop, testing, and/or production environments to ensure that the target version of the technology will be supported.

Legend:

White	Authorized: The technology/standard has been authorized for use.
Yellow	Authorized w/ Constraints: The technology/standard can be used within the specified constraints located below the decision matrix in the footnote[1] and on the General tab.
Gray	Authorized w/ Constraints (POA&M): This technology or standard can be used only if a POA&M review is conducted and signed by the Authorizing Official Designated Representative (AODR) as designated by the Authorizing Official (AO) or designee and based upon a recommendation from the POA&M Compliance Enforcement, has been granted to the project team or organization that wishes to use the technology.
Orange	Authorized w/ Constraints (DIVEST): VA has decided to divest itself on the use of the technology/standard. As a result, all projects currently utilizing the technology/standard must plan to eliminate their use of the technology/standard. Additional information on when the entry is projected to become unauthorized may be found on the Decision tab for the specific entry.
Black	Unauthorized: The technology/standard is not (currently) permitted to be used under any circumstances.
Blue	Authorized w/ Constraints (PLANNING/EVALUATION): The period of time this technology is currently being evaluated, reviewed, and tested in controlled environments. Use of this technology is strictly controlled and not available for use within the general population. If a customer would like to use this technology, please work with your local or Regional OI&T office and contact the appropriate evaluation office displayed in the notes below the decision matrix. The Local or Regional OI&T office should submit an inquiry to the TRM if they require further assistance or if the evaluating office is not listed in the notes below.

Release/Version Information:

VA decisions for specific versions may include a ‘.x’ wildcard, which denotes a decision that pertains to a range of multiple versions.

For example, a technology authorized with a decision for 7.x would cover any version of 7.(Anything) - 7.(Anything). However, a 7.4.x decision would cover any version of 7.4.(Anything), but would not cover any version of 7.5.x or 7.6.x on the TRM.

VA decisions for specific versions may include ‘+’ symbols; which denotes that the decision for the version specified also includes versions greater than what is specified but is not to exceed or affect previous decimal places.

For example, a technology authorized with a decision for 12.6.4+ would cover any version that is greater than 12.6.4, but would not exceed the .6 decimal ie: 12.6.401 is ok, 12.6.5 is ok, 12.6.9 is ok, however 12.7.0 or 13.0 is not.

Any major.minor version that is not listed in the VA Decision Matrix is considered Authorized w/ Constraints (POA&M).

<Past

CY2024

CY2025

CY2026

Future>

Release

10.2.x

Unapproved

Authorized w/ Constraints (POA&M)

11.1.x

Unapproved

Authorized w/ Constraints (POA&M)

11.2.x

Unapproved

Authorized w/ Constraints (POA&M)

12.1.x

Unapproved

Authorized w/ Constraints (POA&M)

12.2.0.1.x

Unapproved

Authorized w/ Constraints (POA&M)

18.x (12.2.0.2.x)

Unapproved

Authorized w/ Constraints (POA&M)

19.x (12.2.0.3.x)

Approved w/Constraints
[28, 31, 33, 34, 35, 36, 37]

Authorized w/ Constraints
[28, 31, 33, 34, 35, 36, 37]

Authorized w/ Constraints
[28, 31, 33, 35, 36, 37, 38]

21c (21.x)

Unapproved

Authorized w/ Constraints (POA&M)

23c (23.x)

Unapproved

Authorized w/ Constraints (POA&M)

23ai (23.x)

Unapproved

Authorized w/ Constraints (POA&M)

Note:

In 2018, Oracle changed their version number scheme. Version 18c (18.x aka 12.2.0.2) and 19c (19.x aka 12.2.0.3) are later updates to the original 12.2.x version line. The VA baselines for 12.2.x apply to version 19.x.

The latest version of this technology released is version 23ai (23.4.0). However, at the time of writing, version 19.x is still supported by the vendor and the current VA-baselined version. Version 23ai is not an extended support release and is unapproved for use until a baseline configuration has been developed.

Decision Constraints


[28]	This technology has received one or more VA security bulletins that provide specific guidance on vulnerability patching and mitigation. It is the responsibility of VA system owners to ensure that the appropriate mitigations are taken to address all known and future discovered vulnerabilities with this product. See the Reference tab for more information on security bulletins related to this product.

[31]	Due to National Institute of Standards and Technology (NIST) identified security vulnerabilities, extra vigilance should be applied to ensure the versions remain properly patched to mitigate known and future vulnerabilities. The local ISSO (Information System Security Officer) can provide assistance in reviewing the NIST vulnerabilities.

[33]	In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004 , VA Directive 6517, and VA Directive 6513. The local ISSO (Information System Security Officer) can advise on the ESCCB review process.

[34]	Configuration and deployment standards for Oracle Databases and their host Server images are defined and maintained by the Core Systems Engineering organization within VA Solution Delivery (SD) and must be followed and adhered to unless an appropriate waiver is granted. Detailed information can be found at the following location: https://vaww.vashare.oit.va.gov/sites/itops/svcs/sma/BCM/Pages/BCM.aspx Users must not utilize Oracle Load Testing (OLT), as it is at the time of writing, unapproved in the TRM.

[35]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISSO (Information System Security Officer) to ensure compliance with both VA Handbook 6500 and VA Directive 6500.

[36]	Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request, visit the Product Marketplace. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[37]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 or its successor to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 or 140-3 compliant full disk encryption (FOE) must be implemented on the storage device where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information System Security Officer (ISSO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP). By September 22, 2026, all FIPS 140-2 certificate validations will be placed on the Historical List, please refer to FIPS Transition Effort for further guidance and timeline of changes.

[38]	Configuration and deployment standards for Oracle Databases and their host Server images are defined and maintained by the Core Systems Engineering organization within VA Solution Delivery (SD) and must be followed and adhered to unless an appropriate waiver is granted. Users must not utilize Oracle Load Testing (OLT), as it, at the time of writing, requires a POA&M.

Technology Components

Note: This list may not be complete. No component, listed or unlisted, may be used outside of the technology in which it is released. The usage decision for a component is found in the Decision and Decision Constraints.

Name	Description
Oracle Active Data Guard	Oracle Active Data Guard, as an option to Oracle Database Enterprise Edition, offloads resource intensive activities from a production database to one or more synchronized standby databases.
Oracle Advanced Compression	Oracle Advanced Compression provides for storing and auditing of historical data. It delivers compression rates of two to four times across all types of data and applications improving query performance.
Oracle Advanced Security	Oracle Advanced Security is an option for Oracle Database Enterprise Edition. Oracle Advanced Security provides three main features: Transparent Data Encryption, Network encryption, and Strong authentication.
Oracle Application Express (APEX)	Oracle Application Express (abbreviated APEX, previously named Oracle HTML DB) is a web-based software development environment that runs on an Oracle database. It is fully supported and comes standard (at no additional cost) with all Oracle Database editions and, starting with Oracle 11g, is installed by default as part of the core database install.
Oracle Automatic Storage Management (ASM)	ASM is a volume manager and a file system for Oracle database files that supports single-instance Oracle Database and Oracle Real Application Clusters (Oracle RAC) configurations. ASM is Oracle's recommended storage management solution that provides an alternative to conventional volume managers, file systems, and raw devices.
Oracle Database Vault	Oracle Database Vault helps increase the security of existing applications and address regulatory mandates that call for separation-of-duties, least privilege and other preventive controls.
Oracle Label Security	Oracle Label Security is a technology for classifying data and mediating access to data based on its classification.
Oracle Machine Learning (formerly Advanced Analytics)	Oracle Machine Learning extends the Oracle database into an analytics platform through two major components: Oracle R Enterprise and Oracle Data Mining.
Oracle Multitenant	Oracle Multitenant is a new option for Oracle Database 12c Enterprise Edition. The multitenant architecture enables an Oracle database to function as a multitenant container database (CDB) that includes zero, one, or many customer-created pluggable databases (PDBs).
Oracle Partitioning	Oracle Partitioning, as an option to Oracle Database Enterprise Edition, allows tables, indexes, and index-organized tables to be subdivided into smaller pieces, enabling these database objects to be managed and accessed at a finer level of granularity.
Oracle Real Application Clusters (RAC)	Oracle Real Application Clusters (RAC) supports the deployment of a single database across a cluster of servers, providing fault tolerance from hardware failures or planned outages.
Oracle Real Application Testing	Oracle Real Application Testing database option includes two solutions to test the effect of system changes on real-world applications: Database Replay and SQL Performance Analyzer (SPA).
Oracle SQL Plus	Oracle SQL Plus is a general purpose utility used for running SQL commands and PL/SQL blocks and performing database administration. This component is integrated with the core Oracle Database installation, but can also be installed remotely as part of the Oracle Client product. The Oracle Client product has a separate TRM entry and constrained approval that should be referenced for that product.
Oracle TimesTen (formerly In-Memory Database Cache)	Oracle TimesTen is an Oracle Database product option that enables database applications to selectively cache performance-critical subsets of the Oracle Database tables into the TimesTen In-Memory Database to improve application response time. This Oracle Database Cache component is included as part of this TRM entry. NOTE: The Oracle TimesTen In-Memory Database, which is a standalone product from Oracle Database, is listed under a separate TRM entry. Please refer to the TRM entry and approval for the Oracle TimesTen In-Memory Database standalone product.
Pro*C/C++	ProC (also known as ProC/C++) is an embedded SQL programming language used by Oracle Database database management systems. ProC uses either C or C++ as its host language. During compilation, the embedded SQL statements are interpreted by a precompiler and replaced by C or C++ function calls to their respective SQL library. The output from the ProC precompiler is standard C or C++ code that is then compiled by any one of several C or C++ compilers into an executable.


Information Management Technologies Data Management	Object-Oriented DBMS
Information Management Technologies Data Management	Relational DBMS	Microsoft SQL Server and Oracle DB are the preferred Relational DBMS platforms in VA. Per ELT decision, all future requests for Relational DBMS technologies will be Unapproved.	1/13/2015 12:00:00 AM

General Analysis

Adoption Benefits

The vendor of this technology is an industry leader in the subject matter.
This technology is Federal Information Processing (FIPS) 140-2 compliant.
This is a well-documented technology.

Adoption Risks

This technology may utilize external data connections.
This technology can potentially use Oracle Load Testing (OLT) which requires a POA&M for use on the VA network.
This technology can integrate with and alter database technologies.
Due to the rapid release schedule of this technology, the VA may be unable to update to the most recent patch and may require a deployment model requiring the use of specific versions.
The potential exists to store Personally Identifiable Information (PII), Protected Health Information (PHI) and/or VA Sensitive data and proper security standards must be followed in these cases.
There are known Common Vulnerabilities and Exposures (CVEs) associated with this technology. Please see https://nvd.NIST.gov/vuln/search for more details.
This technology may utilize external data connections.
There are other authorized solutions that provide similar functionality available on the TRM. The use of several similar solutions may increase organization requirements for support and maintenance.
The technology requires the purchase of licenses from vendor, which could potentially lead to vendor lock-in.
The potential of vendor lock exists when utilizing proprietary vendor technology.

Architectural Benefits

This technology can use a VA-preferred database.
This technology is compatible with virtual machines, therefore consistent with the enterprise Server Virtualize First Policy (VAIQ 7266972 08-27-2012).
This technology is portable as it runs on multiple TRM-authorized operating systems.

Architectural Risks

This technology includes cloud-based functionality which has potential information security risks.

- The information contained on this page is accurate as of the Decision Date (05/15/2025 at 16:30:13 UTC).

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 25.7

General Information

Vendor Release Information

Current Decision Matrix (04/22/2025)

Decision Constraints

References

Technology Components

VA Categories

View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Optional Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 25.7

General Information

Vendor Release Information

Current Decision Matrix (04/22/2025)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Optional Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

EMAIL UPDATES

VA Categories

View the VA Categorization Framework