SQL Developer Web in Autonomous Database relies on Oracle REST Data Services (ORDS) for access.
The correct package is:
ORDS_ADMIN.ENABLE_SCHEMA (B): To allow a non-admin user (e.g., ANALYST1) to use SQL
Developer Web, the ADMIN user executes ORDS_ADMIN.ENABLE_SCHEMA to enable the schema for
ORDS access. This procedure activates the schema for RESTful services, granting privileges like
CONNECT and SELECT implicitly for web-based SQL execution. Example:
BEGIN
ORDS_ADMIN.ENABLE_SCHEMA(p_schema => 'ANALYST1');
END;
After this, the user accesses SQL Developer Web via a URL (e.g., https:///ords/analyst1/_sdw), logging in with their database credentials. This is necessary because SQL
Developer Web runs on ORDS, and only enabled schemas can interact with it. For instance, an
analyst might query SELECT * FROM sales in the web interface post-enablement, without needing
full admin rights.
The incorrect options are:
ORDS_ADMIN.GRANT_SCHEMA (A): No such procedure exists in ORDS_ADMIN. Granting is handled
via database roles/privileges (e.g., GRANT CONNECT), not a specific ORDS grant function.
ORDS_PRIV.ENABLE_SCHEMA (C): There’s no ORDS_PRIV package; this might confuse with
ORDS_ADMIN. The correct package is ORDS_ADMIN for schema enablement.
SQLDEV_ADMIN.GRANT_SCHEMA (D): No SQLDEV_ADMIN package exists. SQL Developer Web
access is managed through ORDS, not a separate SQL Developer-specific package.
ORDS_ADMIN.ENABLE_SCHEMA is the standard, secure way to enable non-admin access to this tool
in ADB.
Reference: Oracle Cloud Infrastructure Documentation - SQL Developer Web Setup
