You can create an export from Oracle Autonomous Database (ADB) in either of these ways:
-
as part of a flow while designing or building your flow (Flow builder > Add source app)
– or –
-
as a resource that you can later attach to a flow (Resources > Exports)
Tip
The navigation paths differ, but the exporting task is the same.
Creating an export from Oracle ADB consists of the following two logical parts: providing general details and configuring the export.
You can start creating an export from Oracle ADB and provide essential/general details in either of these ways:
-
From the main menu, select Tools> Flow builder.
-
In the Flow builder, click the plus sign () next to Source.
-
In Create source, for Application, select Oracle Autonomous Database.
-
For What would you like to do?, the default is Export records from source application.
-
For Connection, select a previously created Oracle ADB connection from the drop-down menu, or you can click Create connection and create one if you haven't done so already.
-
Click Next.
– or –
-
From the main menu, select Resources >Exports.
-
Click + New export.
-
In Create export, for Application, select Oracle Autonomous Database.
-
For Connection, select a previously created Oracle ADB connection from the drop-down menu, or you can click Create connection and create one if you haven't done so already.
-
For Name, enter a meaningful name based on the purpose, function, or any other aspect.
-
For Description, optionally provide details that will help in understanding your export.
-
Click Next.
Note
You've completed providing the general details. Next, you must configure the required settings in the export.
You can use standard SQL queries to export and modify data. If your flow requires multiple SQL queries, you must create one export for each query. You can't use multiple SQL queries on a single export.
For Oracle ADB, you must configure the required settings in General, What would you like to export? and Configure export type sections for data to be exported successfully. (You can configure the optional settings as required for any customization.)
-
In Name your export, enter a meaningful name for your export based on the purpose, function, or any other aspect.
Note
If you've used the Resources > Exports path to create an export, then this value is automatically filled in.
-
For SQL query, click the Edit icon () and enter your SQL statement based on what you want to export from Oracle ADB.
-
For Export type, select an option based on how you want to export records. See Four different export types to retrieve data . If you're using Delta as the Export type, for the date, you must provide the data type explicitly. For example,
SELECT * FROM TableName WHERE joining IS NOT NULL AND joining TO_TIMESTAMP({{lastExportDateTime}},'YYYY-MM-DD"T"HH24:mi:SS.FF3"Z"') ORDER BY id
-
Click Preview to check the export to see sample JSON-formatted data. If the SQL query is not executed successfully, revise the Query or Export type values.
-
Click Save.
When an export is saved,
-
if you've created it in a flow, the export is added to your flow in Flow builder.
-
if you've created it as a resource, then it is added under Resources > Exports.
Optional sections/settings |
Instructions |
---|---|
Would you like to group records? |
|
Group records by fields |
|
Mock output |
|
Mock output |
|
Advanced |
|
Page size |
|
Data URI template |
|
Do not store retry data |
Check this box if you do NOT want integrator.io to store retry data for records that fail in your flow. Storing retry data can slow down your flow's overall performance if you are processing very large numbers of records that are failing. |
Override trace key template |
Comments
Please sign in to leave a comment.