Autonomous Transaction Processing

Get Involved. Join the Conversation.


    Peter Schneider
    Oracle Cloud Free Tier - Autonomous DB - ORDS 503 error,...
    Topic posted September 30, 2019 by Peter SchneiderGreen Ribbon: 100+ Points, tagged Apex, Provisioning, SQL Dev Web, Transaction Processing 
    101 Views, 11 Comments
    Oracle Cloud Free Tier - Autonomous DB - ORDS 503 error, cannot connect
    ATP - Neither APEX Link, nor SQL Dev Web Link, nor connect using local SQL Dev 19.2 works

    Hi all,

    I alrready posted this yesterday in the general Infrastructure forum, but as per Richard Garsthagen's suggestion, I'm reposting this here as well.

    I just wanted to give Oracle Cloud a test drive using the newly announced Always Free tier. But sadly, after provisioning ATP DB instance (serverless), I found that I cannot use it at all.

    In the service console (Development), neither of the APEX link nor the SQL Developer Web links work. Both give the below error message (see image)

    Furthermore, when I try to connect with a locally installed SQL Developer 19.2 using the connect option "Cloud Wallet" and specifying the download, SQL Developer displays the error message (in german): "Status: Nicht erfolgreich - Test nicht erfolgreich: I/O Fehler: Remote host closed connection during handshake".

    Now lastly, when I try to use a locally installed client (I merged sqlnet.ora and tnsnames.ora from with my already present files residing in my TNS_ADMIN directory, I have unzipped, and in sqlnet.ora I have modified: "WALLET_LOCATION = (SOURCE = (METHOD = file) (METHOD_DATA = (DIRECTORY="D:\\Oracle\\tnsadmin\\Wallet_PS1")))"...

    Now when I tnsping my instance, it gives:

    d:\Users\Peter>tnsping ps1_high

    TNS Ping Utility for 64-bit Windows: Version - Production on 29-SEP-2019 17:36:50

    Copyright (c) 1997, 2013, Oracle.  All rights reserved.

    Used parameter files:

    Used TNSNAMES adapter to resolve the alias
    Attempting to contact (description= (address=(protocol=tcps)(port=1522)(,OU=Oracle BMCS FRANKFURT,O=Oracle Corporation,L=Redwood City,ST=California,C=US)))
    TNS-12560: TNS:protocol adapter error


    So, nothing seems to work at all, and I'm completey lost. Stopping and restarting did not help.

    Can anyone help, please?

    Thanks and regards,





    • Rahul Bhinde


      I am also facing same error '503 Service Unavailable' where i am unable to access Oracle Apex and SQL Developer web after the Always Free ATP instance is created. I am able to connect to database using SQL Developer remotely.

      I have verified multiple options of restarting ATP instance, re-creating the instance but no luck.

      Assistance related to this issue will be of great help as I also need to deploy and test my Oracle Apex application on ATP.

      Thank You.

      • Peter Schneider

        Hi Rahul,

        for me, the remote connection with SQL Developer 19.2 didn't work either. Which version do you use? Which connect options worked for you?

        Thanks for any insight,


        • Rahul Bhinde

          Hi Peter,

          I have used same version of SQL Developer 19.2 and selected Cloud Wallet option where the path of the zip file (wallet) was provided. Also verify whether the port 1521 is allowed in Ingress rule; i am not sure if this will help or not but it is just a thought which is worth a try.




    • Geert Jansen

      Same here,

      ATP instance running normal (as usual), I can still connect to this instance from local SQL developer.

      But apex is not working. "The connection pool named: |ocid1.tenancy.oc1..aaaaaaaa6ietk4rti2zggx7del55hqxb34iecqe54hvmqrio36kenpzdq2ea-xxxx|re| is not correctly configured, due to the following error(s): No more data to read from socket" 

      It worked fine a few days ago. 

      I'm kind of amazed that such an service outage goes unnoticed by Oracle. I was just testing the cloud and considering migrating some of my personal APEX apps, I normally host on my own server.  But it appears my server has a better uptime than oracle cloud crying

    • Maria Colgan

      Thanks for reporting this. 

      Oracle Cloud Operations is aware of this problem and are working to resolve it.



      • Peter Schneider

        Thanks Maria!

        Now, I get a new, different error message:


      • Rahul Bhinde

        Hi Maria,

        Thank You for addressing this issue. It would be helpful if you can share tentatively by when these issues will be resolved for
        ATP Always Free services and we will be able to access Oracle Apex !!!




    • Maria Colgan


      The Ops team are rolling out a fix now to address this problem and you should be able to access Oracle Apex.



      • Peter Schneider

        Still no good news - now after provisioning, I get a plain 500 with no additional information from ORDS.

        Central Europe, Germany, Frankfurt region.

        I dont really mean to complain about a freebie, BUT: how on earth could this be announced to the public, when clearly, this it not finished yet, and is not working at all?

        Oracle, aren't you testing this? I mean - this DOES NOT WORK at all...


      • Rahul Bhinde
        Hi Maria, Unfortunately i am still facing the same error. I am located in the India (West) region. Would also like to know do we need to re-create the instance or just resarting will work? Thank You for all the support. Regards, Rahul
      • Andre Souza

        I have one ATP running APEX just fine but when I try to get a new one (dev and prod) I keep getting the 503 service error message... Sao Paulo servers.

        Any news on this problem?