Installing APEX into Different PDBs
You can install different versions of Oracle APEX into different PDBs.
If APEX is not installed in the container database, you can install a local APEX within each PDB as required. When APEX is installed locally there are no APEX metadata linked objects and all packages, views, and tables are created within the APEX_260200 schema, within each PDB where APEX is installed.
Uninstalling APEX from a CDB
Learn how to uninstall Oracle APEX from a CDB.
To uninstall APEX from a CDB:
Note:
Installing or removing APEX from a CDB requires a local connection to the database.
This section describes removing APEX from a CDB.
-
Change to the
apexdirectory in the location where you unzipped the distribution. -
Start SQLcl and connect to the database where APEX is installed as
SYSspecifying theSYSDBArole. For example:-
On Windows:
<SYSTEM_DRIVE>:\ sql /nolog SQL> CONNECT SYS as SYSDBA Enter password: <SYS_password> -
On UNIX and Linux:
$ sql /nolog SQL> CONNECT SYS as SYSDBA Enter password: <SYS_password>
-
-
Run
apxremov.sql.For example:
@apxremov.sqlNote: If you run
apexremov.sqlafter PDBs have been added to the CDB, then APEX uninstalls from all of the PDBs, as well asCDB$ROOTandPDB$SEED. Any applications defined in any of the PDBs will be removed.
Installing APEX Locally in a PDB
Learn how to install Oracle APEX locally in a PDB.
Once you have removed APEX from the container database by following the instructions in Uninstalling APEX from a CDB, you can install APEX locally in a PDB.
To install APEX locally in a PDB:
-
Change the
apexdirectory in the location where you unzipped the distribution. -
Start SQLcl and connect to the database where APEX is installed as SYS specifying the SYSDBA role. For example:
-
On Windows:
<SYSTEM_DRIVE>:\ sql /nolog SQL> CONNECT SYS as SYSDBA Enter password: <SYS_password> -
On UNIX and Linux:
$ sql /nolog SQL> CONNECT SYS as SYSDBA Enter password: <SYS_password>
-
-
Set the container to the PDB you want to install APEX locally:
ALTER SESSION SET CONTAINER = <PDB_name>; -
Select the appropriate installation option.
Full development environment provides complete access to the App Builder environment to develop applications. A Runtime environment enables users to run applications that cannot be modified.
Available installation options include:
-
Full development environment - Run
apexins.sqlpassing the following four arguments in the order shown:@apexins.sql tablespace_apex tablespace_files tablespace_temp imagesWhere:
-
tablespace_apexis the name of the tablespace for the APEX platform schema. -
tablespace_filesis the name of the tablespace for the APEX files schema. -
tablespace_tempis the name of the temporary tablespace or tablespace group. -
imagesis the virtual directory for APEX images. To support future APEX upgrades, define the virtual image directory as/i/.
For example:
@apexins.sql SYSAUX SYSAUX TEMP /i/ -
-
Runtime environment - Run
apxrtins.sqlpassing the following four arguments in the order shown:@apxrtins.sql tablespace_apex tablespace_files tablespace_temp imagesWhere:
-
tablespace_apexis the name of the tablespace for the APEX platform schema. -
tablespace_filesis the name of the tablespace for the APEX files schema. -
tablespace_tempis the name of the temporary tablespace or tablespace group. -
imagesis the virtual directory for APEX images. To support future APEX upgrades, define the virtual image directory as/i/.
For example:
@apxrtins.sql SYSAUX SYSAUX TEMP /i/ -
-
-
Complete the appropriate steps in Installing and Configuring Oracle REST Data Services and Oracle APEX.
See Also:
-
Installing and Configuring Oracle REST Data Services and Oracle APEX
-
Working with SQLcl in Oracle SQLcl User’s Guide for more information about SQLcl
Installing APEX into a CDB
To install Oracle APEX into a CDB:
Note: Installing or removing APEX from a CDB requires a local connection to the database.
-
Change your working directory to the
apexdirectory in the location where you unzipped the distribution. -
Start SQLcl and connect to
CDB$ROOTof the database where APEX is installed asSYSspecifying theSYSDBArole. For example:-
On Windows:
<SYSTEM_DRIVE>:\ sql /nolog SQL> CONNECT SYS as SYSDBA Enter password: <SYS_password> -
On UNIX and Linux:
$ sql /nolog SQL> CONNECT SYS as SYSDBA Enter password: <SYS_password>
-
-
Select the appropriate installation option.
Full development environment provides complete access to the App Builder environment to develop applications. A Runtime environment enables users to run applications that cannot be modified.
Available installation options include:
-
Full development environment. Run
apexins.sqlpassing the following four arguments in the order shown:@apexins.sql tablespace_apex tablespace_files tablespace_temp imagesWhere:
-
tablespace_apexis the name of the tablespace for the APEX platform schema. -
tablespace_filesis the name of the tablespace for the APEX files schema. -
tablespace_tempis the name of the temporary tablespace or tablespace group. -
imagesis the virtual directory for APEX images. To support future APEX upgrades, define the virtual image directory as/i/.
Example:
@apexins.sql SYSAUX SYSAUX TEMP /i/ -
-
Runtime environment. Run
apxrtins.sqlpassing the following arguments in the order shown:@apxrtins.sql tablespace_apex tablespace_files tablespace_temp imagesWhere:
-
tablespace_apexis the name of the tablespace for the APEX platform schema. -
tablespace_filesis the name of the tablespace for the APEX files schema. -
tablespace_tempis the name of the temporary tablespace or tablespace group. -
imagesis the virtual directory for APEX images. To support future APEX upgrades, define the virtual image directory as/i/.
Example:
@apxrtins.sql SYSAUX SYSAUX TEMP /i/ -
-
-
Complete appropriate steps in Installing and Configuring Oracle REST Data Services and Oracle APEX.