Autonomous Transaction Processing

Get Involved. Join the Conversation.

Comments

  • Subrahmanyam Vempati
    Thanks Simon, I have used same marketplace Image to create ODI instance by ATP(create new repository option).But Is it possible for me to create a new work repository without having sys login? Please help me with any references. I am not even able to connect to master/work repositories that this stack creates in ATP. Regards, Vempati
  • Simon Law

    Vempati, there is no user log in available for SYS or  SYSTEM , ADMIN is the only administrator for Autonomous DB. 

    Regarding ODI, ODI on-prem release doesn't support repository in ATP. However the ODI Market Place image does support repository in ATP.

    -Simon

  • Subrahmanyam Vempati

    Hi Simon,

    There are SYS/SYSTEM users, please find the below snapshot from SQL developer of ATP. I need sysdba user to create some repositories in ODI. Admin is not super user I guess.

    Thanks,

    Vempati

     

     

    SQL.PNG (16KB)
  • Simon Law

    There is no SYS (or SYSDBA) access with Autonomous Database, ADMIN is the superuser for managing ATP.

  • 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. 

  • 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

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

  • 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

    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. 

  • Rick Kelder

    It seems an update gave me more options in roles. It fixed some things and some other things didnt change, however, it does work now:

    - it works for manually created handlers, but only for the schema user, even when we have another DB user with roles and grants etc (and even SQLDeveloper role)

    - it doesnt work for auto-rest, unless I add SQLDeveloper to the privilege that is created with autorest, and only then again for the schema user

  • Rick Kelder

    Hi Keith,

     

    Thanks for your answer. I have looked at that post, for me it keeps giving me 401 unauthorized even when using my own account, the schema account or even admin account. Either from the browser or PostMan, where in the post he says it works with his PostMan, we get the 401.

  • 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.

  • Keith Laker

    Have you looked at this blog post by Jeff Smith: https://www.thatjeffsmith.com/archive/2019/06/rest-services-now-available-for-oracle-autonomous-database/

     

  • Keith Laker

    I just checked this in my "19c Preview" instance running in Ashburn data center and it's working fine. Can you please open a service ticket with support.

  • Peter Care

    We have the same issue, when trying to open APEX or ORDS. It was working fine until 15-Oct-19.