---
title: "Discussion on \"Move Large Volumes of Data Over REST with APEX & ORDS\" | Hashnode"
description: "Discussion on \"Move Large Volumes of Data Over REST with APEX & ORDS\". In this post, I will discuss three ways to transport large volumes of data between two databases over REST using Oracle APEX and Oracle ORDS."
url: "https://hashnode.com/posts/apex-ords-large-volumes-rest/6363b7f609fb89ffe67cc70b"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Move Large Volumes of Data Over REST with APEX & ORDS](https://blog.cloudnueva.com/apex-ords-large-volumes-rest?utm_source=hashnode&utm_medium=feed)

In this post, I will discuss three ways to transport large volumes of data between two databases over REST using Oracle APEX and Oracle ORDS.

Nov 3, 2022 · 8 min read · blog.cloudnueva.com  
Read the article

-   [#orclords](https://hashnode.com/tag/orclords)
-   [#orclapex](https://hashnode.com/tag/orclapex)
-   [#oracle](https://hashnode.com/tag/oracle)

## Written by

[Jon Dixon](https://hashnode.com/@orclapex)

@orclapex · San Diego, CA

  
[View profile](https://hashnode.com/@orclapex)

APEX, ORDS & the Oracle Database

I’m Jon Dixon, an Oracle APEX developer and consultant at Cloud Nueva. I write about APEX, ORDS, the Oracle Database, and how AI is changing the way we build software. This blog is where I share practical examples, lessons learned, and ideas from my work.

## Responses 6

Markdown supported · ⌘↵ to post

[Norman Castelino](https://hashnode.com/@normanalwyn)

[Jan 9, 2025](https://hashnode.com/posts/apex-ords-large-volumes-rest/6363b7f609fb89ffe67cc70b/comment/677f2b97354730e47ad0c8c4)

Hi,

This blog was really helped me to achieve our requirement; The exact same code is throwing error: Error at line 5/38: ORA-20987: APEX - End-of-central-directory signature not found. This file is not a ZIP file. ORA-06512: at "APEX\_240100.WWV\_FLOW\_ERROR", line 1123 ORA-06512: at "APEX\_240100.WWV\_FLOW\_ERROR", line 1581 ORA-06512: at "APEX\_240100.WWV\_FLOW\_ZIP", line 141 ORA-06512: at "APEX\_240100.WWV\_FLOW\_ZIP", line 212 ORA-06512: at line 13 3.

[Awais](https://hashnode.com/@syedawaisamjad)

[Nov 6, 2024](https://hashnode.com/posts/apex-ords-large-volumes-rest/6363b7f609fb89ffe67cc70b/comment/672b7668132a933f20d4480f)

What if we were dealing with blobs alongside json/ data. How would that impact performance and what would be a way to make that exchange efficient and robust?

[João Coimbra](https://hashnode.com/@coimbraj)

[Oct 9, 2024](https://hashnode.com/posts/apex-ords-large-volumes-rest/6363b7f609fb89ffe67cc70b/comment/6705c9cc5ab82b864967a47b)

I like very much, I have been really enjoying your articles

[João Coimbra](https://hashnode.com/@coimbraj)

[Oct 9, 2024](https://hashnode.com/posts/apex-ords-large-volumes-rest/6363b7f609fb89ffe67cc70b/comment/6705c90d5ab82b864967a47a)

Is it possible to make a for loop for adding 700 pairs of lt\_parm\_names(i loop) and lt\_parm\_values(i loop) to a apex\_web\_service.make\_rest\_request? How many "parms" can I add to it?

[João Coimbra](https://hashnode.com/@coimbraj)

[Oct 9, 2024](https://hashnode.com/posts/apex-ords-large-volumes-rest/6363b7f609fb89ffe67cc70b/comment/6705c844159354d66cca3049)

I would like to send 700 ids to an API and get the same 700 back paired with another id crucial to my app?

[Roger Scroce](https://hashnode.com/@RogerScroce)

[Jul 28, 2023](https://hashnode.com/posts/apex-ords-large-volumes-rest/6363b7f609fb89ffe67cc70b/comment/64c312fe3510fc491e1a9fe9)

Hi Jon, Just read your article. My preferred approach to this use case is PL/SQL.

To avoid the sequential approach and the need to parse the response twice to test for the next page of data, I use a 2 step approach:

1) call the rest api for a SINGLErecord to get the total record count.

2) build and execute ALL the api calls for individual pages in parallel. Parameterise the maximum concurrency in light of vendor rate limiting.

For my use case, Oracle CX implementations, this routinely achieves a 10X to 20X overall throughput.

100% Oracle and 100% free with Oracle ADB !

[Jonathan Kearney](https://hashnode.com/@JonathanKearney)

[Nov 4, 2022](https://hashnode.com/posts/apex-ords-large-volumes-rest/6363b7f609fb89ffe67cc70b/comment/6364d6c9c8e1079692e67a1c)

Another great article, all very useful techniques to know from a practical point of view and a good lesson in theory too. Clearly explained as always, excellent

[Jon Dixon](https://hashnode.com/@orclapex)

[Nov 5, 2022](https://hashnode.com/posts/apex-ords-large-volumes-rest/6363b7f609fb89ffe67cc70b/comment/6364d6c9c8e1079692e67a1c#reply-6365cc8e5efad7ad599cb77b)

Thanks Jonathan

[Plamen Mushkov](https://hashnode.com/@plamen9)

[Nov 3, 2022](https://hashnode.com/posts/apex-ords-large-volumes-rest/6363b7f609fb89ffe67cc70b/comment/6363ecaebb0b328aa172520b)

Great article! Really enjoyed it. Really impressive performance improvement with the last method.

Speaking about other methods, it could be again any of the current ones, but fetching only the deltas - records updated/inserted after the last sync. I have always used to have a specific package and table to keep the delta information (like last sync date, latest id, etc.). And then my query would only return the needed records which are then transferred using any of the methods you mention. Or directly in bulk using a DBLink if available.

[Jon Dixon](https://hashnode.com/@orclapex)

[Nov 5, 2022](https://hashnode.com/posts/apex-ords-large-volumes-rest/6363b7f609fb89ffe67cc70b/comment/6363ecaebb0b328aa172520b#reply-6365cc775efad7ad599cb774)

I completely agree bringing just changed data is definitely the way to go for overall performance. This was more of a discussion on throughput. Thanks for your comment and idea.
