|
| 1 | +# SQL Developer Web - Oracle Database Actions Access |
| 2 | + |
| 3 | +Oracle Database Actions is formerly known as SQL Developer Web and is a web-based interface that uses Oracle REST Data Services to provide development, data studio, administration and monitoring features for Oracle Autonomous Database, Oracle Database Cloud Services and on-premises Oracle Database. Database Actions comes already configured, via ORDS, on Autonomous Database. |
| 4 | + |
| 5 | +Reviewed: 10.06.2026 |
| 6 | + |
| 7 | +Database Actions, (here also abbreviated as DB Actions), runs in Oracle REST Data Services and access to it is provided through schema-based authentication. To access Database Actions, you must sign in as a database user whose schema has been enabled for Database Actions. |
| 8 | + |
| 9 | +## User Authentication - prerequisites |
| 10 | + |
| 11 | +User access to Database Actions is described as follows |
| 12 | +- In Oracle Autonomous AI Database databases, the ADMIN user is pre-enabled; |
| 13 | +- To enable another database user's schema it has to be [REST-enabled first](https://docs.oracle.com/en/database/oracle/sql-developer-web/sdwad/accessing-sql-developer-web.html#GUID-63D265FC-7500-4F88-8870-1C60E0A286FF). |
| 14 | + |
| 15 | +Key important information, when REST-enabling a schema user to authenticate via DB Actions are: |
| 16 | +- <i><b>schema_name</i></b> : database Schema name (in uppercase) |
| 17 | +- <i><b>schema_alias</i></b>: alias for the schema name which will appear in the URL the user will make use when authenticating to database via DB Actions. |
| 18 | + |
| 19 | +<b>Note</b>: as a best practice, it is not recommended to name the schema alias as the schema name itself: this, as a security measure to avoid schema name exposure. |
| 20 | + |
| 21 | +When signing in to Database Actions you can connect via ORDS Schema alias defined in the REST-enabling schema configuration as follows: |
| 22 | +- <b>Database Actions Sign-in</b> page --> <b>Advanced</b> in the Path Field enter: <schema_alias>, then login and password of the database schema when <i>schema_name</i> and <i>schema_alias</i> differ (as recommended). |
| 23 | + |
| 24 | +To connect to a given database in a multiple database pool scenario, when Database Actions is configured via an ORDS-Standalone, (or together with Tomcat/WebLogic), in a non-Autonomous AI Database (or ADB customer-managed configuration) the steps are as follows: |
| 25 | +- <b>Database Actions Sign-in page</b> --> <b>Advanced</b> in the Path Field enter: |
| 26 | + |
| 27 | + <i><database_pool_name>/<schema_name></i> |
| 28 | + |
| 29 | + then schema name and password in the login-password portion. |
| 30 | +<br> |
| 31 | +<br> |
| 32 | + |
| 33 | +# Useful Links |
| 34 | +- [Signing-in to Database Actions](https://docs.oracle.com/en/database/oracle/sql-developer-web/25.4/sdweb/signing-database-actions.html) |
| 35 | +- [Jeff Smith PM's Blog - SQL Developer Web](https://www.thatjeffsmith.com/sql-developer-web/) |
| 36 | +<br> |
| 37 | +<br> |
| 38 | + |
| 39 | +# License |
| 40 | + |
| 41 | +Copyright (c) 2026 Oracle and/or its affiliates. |
| 42 | + |
| 43 | +Licensed under the Universal Permissive License (UPL), Version 1.0. |
| 44 | + |
| 45 | +See [LICENSE](https://github.com/oracle-devrel/technology-engineering/blob/main/LICENSE) for more details. |
| 46 | + |
0 commit comments