SQL> connect sys/<password>@<container> as sysdba
SQL> exec dbms_xdb_config.sethttpsport(5501);
PL/SQL procedure completed
If you're using a listener TCP port other than 1521, you
will also need to set the dispatchers and local_listener
initialization parameters, just like you would in a
non-CDB system. Please see the documentation for
Tablespaces are local to a PDB, so the Tablespaces entry
is not available at the root container. To view and
manage tablespaces or datafiles on a PDB, go to the EM
Express configured on that PDB.
Yes, Common Users can be created and managed from the
At the PDB container, only the Activity and Monitored SQL
tabs are visible because these are the only tabs that
display PDB-specific data.
At the root container, all tabs are available in the
Yes, at the root container, you can see the Average Active Sessions breakdown by container using the Home Page and the Performance Hub (Summary tab or Activity tab).
This data is taken from ASH, not metrics, so you might
see a discrepancy when comparing average active sessions
per container against a different breakdown.
Although PDB$SEED is just a seed database, when queries
are issued against CDB_* views, the server internally
switches to all containers, including PDB$SEED, to
retrieve data. If there are frequent queries against
CDB_* views, this could result in activity captured
No, EM Express does not provide full CDB management
capabilities in DB 126.96.36.199.0.
You can get this information from the Status region in the home page. If you are at the root container, the type will show "CDB (# of PDBs)", and if you are at the PDB, the region will include the Container Name to which you're connected.
In addition, the blue panel at the top of the page will
have an icon on the top left that indicates if the
database is a CDB. The database name will be
displayed after the icon:
If you're connected to a PDB, the container name will be displayed after the database name: