Habib's Byte Hub

                 The SYS.ALL_SYNONYMS view is used to get all the details of existing synonyms accessible to the current user. However, SYS.ALL_SYNONYMS has some known performance issues — and at the time I'm writing this blog,   hey still haven’t been resolved.   This becomes an issue if your database has a huge number of synonyms . (Yeah, sounds like a long shot, but believe me, speaking from experience — it can definitely happen.) So, if your application has a PL/SQL block that's querying this view, you might want to consider updating your code to avoid referencing it altogether. So the question is What's the alternative? I had the same question! And then a smart teammate of mine suggested using DBMS_UTILITY.NAME_RESOLVE. (s/o to Gerardo!) What is DBMS_UTILITY.NAME_RESOLVE? This is a built-in Oracle procedure that helps you resolve the components of a name in the database — things like the object name, schema, dblink, and t...

             Non-Interactive ORDS Installation process   This blog will provide some examples for non-interactive install/upgrade, it covers multiple scenarios specially if you want to install ORDS with a custom database XOR PL/SQL gateway user.  Note: During installation, ORDS_PUBLIC_USER will always be created, you can define its password via --proxy-user sub-command, or otherwise a random password will be generated.  Install/Upgrade ORDS with default user  1.1.  Install:  The runtime and database user is defaulted in this case to ORDS_PUBLIC_USER. Within the configuration file, the db.username will be set to ORDS_PUBLIC_USER, and its password will be stored within the wallet. Consider using  "--proxy-user" sub-command if you want to define a password for ORDS_PUBLIC_USER. Secret file contains the password for the admin user (SYS in this case).   ords --config  /path/to/config  install   ...