Autonomous Transaction Processing

Get Involved. Join the Conversation.

Topic

    Gleb Otochkin
    Apex and SQL Developer Web on ATP 19c preview
    Topic posted October 15, 2019 by Gleb OtochkinGreen Ribbon: 100+ Points, tagged Apex, SQL Dev Web, Transaction Processing 
    34 Views, 6 Comments
    Title:
    Apex and SQL Developer Web on ATP 19c preview
    Summary:
    Getting error trying to start either Apex or SQL developer Web on ATP 19c preview
    Content:

    Here is the error when I try to open Apex 

    503 Service Unavailable

    • The connection pool named: |ocid1.tenancy.oc1.......-orcl|re| is not correctly configured, due to the following error(s): Exception occurred while getting connection: oracle.ucp.UniversalConnectionPoolException: Cannot get Connection from Datasource: java.sql.SQLException: Listener refused the connection with the following error: ORA-12529, TNS:connect request rejected based on current filtering rules

    And the same when I try to run SQL Dev Web (as expected)

    • The connection pool named: |ocid1.tenancy.oc1.......-orcl|re| is not correctly configured, due to the following error(s): Exception occurred while getting connection: oracle.ucp.UniversalConnectionPoolException: Cannot get Connection from Datasource: java.sql.SQLException: Listener refused the connection with the following error: ORA-12529, TNS:connect request rejected based on current filtering rules
    Version:
    19

    Comment

     

    • Keith Laker

      I just checked my "19c Preview" instance in Ashburn data center and it's working as expected. Can you try again and if it's still not working then please open a service request with support and we will be able to investigate why this is not working for you.

    • Gleb Otochkin

      It looks like the problem is in database name. If I name of the database is "oral" I am getting error either in 18c or 19c preview but it works perfectly well with any other name. Tried to find any note in documentation but couldn't, maybe I am missing it. 

    • Keith Laker

      Just tried using "oral" as the database name, created a 19c Preview instance in Ashburn and I can access both SQL Developer Web and APEX. So not sure what is happening in your environment. Which data center are you using?

    • Gleb Otochkin

      Sorry, looks like autocorrect screwed up a bit. Not "oral" but "orcl" . Toronto region. 

    • Keith Laker

      Created an 18c database in Ashburn using "orcl" as the database name and everything worked as expected.

      Created a 19c preview database in Toronto using "orcl" as the database name and again both SQL Dev Web and APEX working as expected. 

      Not sure what's happening with your cloud account. Can you open a support ticket please?

    • Gleb Otochkin

      Yes, you are right. It works alright in another tenancy. Looks like a problem for one particular environment. 

      Not sure if i will be able to follow it up with support since that one was a demo tenancy and it will be gone in a week.