Use Fast Ingest on Autonomous Database
The intent of fast-ingest is to support applications that generate lots of informational data that has important value in the aggregate but that doesn't necessarily require full ACID guarantees. Many applications in the Internet of Things (IoT) have a rapid "fire and forget" type workload, such as sensor data, smart meter data or even traffic cameras. For these applications, data might be collected and written to the database in high volumes for later analysis.
Fast ingest is very different from normal Oracle Database transaction processing where data is logged and never lost once "written" to the database (that is, committed). In order to achieve the maximum ingest throughput, the normal Oracle transaction mechanisms are bypassed, and it is the responsibility of the application to check to see that all data was indeed written to the database. Special APIs have been added that can be called to check if the data has been written to the database.
For information on fast ingest and the steps involved in using this feature, refer to Using Fast Ingest in Database Performance Tuning Guide.
In addition, the following are required to use Fast Ingest on Autonomous Database:
- Enable the Optimizer to Use Hints:
To use fast ingest with Autonomous Database, you must enable the optimizer to use hints by setting the
optimizer_ignore_hints
parameter toFALSE
at the session or system level, as appropriate.Depending on your Autonomous Database workload type, by default
optimizer_ignore_hints
may be set toFALSE
at the system level. See Manage Optimizer Statistics on Autonomous Database for more information. - Create a Table for Fast Ingest:
Prerequisites for Fast Ingest Table contains the limitations for tables to be eligible for Fast Ingest (tables with the specified characteristics cannot use fast ingest).
Parent topic: Monitor and Manage Performance