This site is currently read-only as we are migrating to Oracle Forums for an improved community experience. You will not be able to initiate activity until January 30th, when you will be able to use this site as normal.

    Forum Stats

  • 3,889,956 Users
  • 2,269,775 Discussions
  • 7,916,823 Comments

Discussions

Oracle Apex - HTTP ERROR 200 Service Unavailable

Jasper Tanglib
Jasper Tanglib Member Posts: 76 Red Ribbon
edited Apr 30, 2021 7:47AM in APEX Discussions

Hi,

In Oracle 20.2, there is an upload file that ends up to this error after attempting to upload a huge file (1.8GB). This huge file was taking 1 hour to load and ends up to this error. Please refer to ss below:


I first thought it was because the default session was 1 hour, so after 1 hour I thought it would stop the session and cause that error, so I increased the sessions up to 2 days: please refer to ss below:


Tried to upload that same huge file (1.8GB) and now it gets this new error.


Any idea what is causing this? Was increasing the session just right or should I revert it back to default?


Any ideas or suggestions are appreciated!

-Jazz

Answers

  • Jasper Tanglib
    Jasper Tanglib Member Posts: 76 Red Ribbon

    Settings of the file upload has 2 processes which are as follows:

    1. Process: Process Row of FILE_TRANSFER_T

    2. Import Collection (PLSQL)

    BEGIN

        APEX_DEBUG.ENABLE(

            apex_debug.c_log_level_info);

            

        apex_debug.message('file_id : '||:P200_FILE_ID);

        EXECUTE IMMEDIATE('alter session disable parallel dml');

        collection.import_collection_from_apex(

            p_file_id => :P200_FILE_ID

        );


        apex_debug.message('Collection succeeded');

    exception

      when others then

      apex_debug.message('Collection failed with '||sqlerrm);

      raise;

    END;

  • AndyH
    AndyH Member Posts: 860 Bronze Trophy
    edited Apr 30, 2021 7:47AM

    There are also timeout settings in ORDS - maybe ORDS isn't getting the response from APEX and then decides to throw the 200?

    Maybe you can try splitting this into two actions/pages - one to upload the file and another to do the processing? I would guess that the processing is taking all the time. The processing could be kicked off in background so that there's no browser/ORDS/APEX time-outs to consider.