On AWS RDS for Oracle, while using SQL*Plus (or SQLcl) connected as ADMIN, the installation of translated version doesn't work getting
ORA-20001: Package variable g_security_group_id must be set errors. But we found out that if you use Oracle SQL Developer connected as ADMIN and that you File>Open>load_xx.sql and execute the script with the Run Script (F5) option, the installation is completing successfully without error.
Why is SQL Developer able to execute the installation script of a translated version of Apex successfully while SQL*Plus or SQLcl are getting
ORA-20001: Package variable g_security_group_id must be set. errors on AWS RDS for Oracle ?
From ->
https://repost.aws/questions/QURvmr-gACSxGA0PtHK_CfFg#ANz_huWBqGRQazqsRkY2gzQw
SQL Dev and SQLcl do not do anything magical with APEX scripts (they don't know its an APEX script).
If they are working, then most likely they are doing so because you are connecting as a schema that the workspace is bound to.
For example, if I want to import an APEX app into my WS_ASKTOM workspace, then I must as user ASKTOM.
I can't speak for how RDS manages this - that would need to be a question for the RDS folks at AWS.
If you want to set the security ID before import, the following shoudl work
exec apex_24xxxxx.wwv_flow_api.set_security_group_id(apex_util.find_security_group_id('MY_WORKSPACE_NAME'));