PDBs (Databases)
The PDBs tab presents a comprehensive view of all Pluggable Databases (PDBs) within your Container Database (CDB) service. This tab is displayed only for database services deployed with CDB/PDB architecture (services selected as container databases during provisioning).
Tessell provides complete lifecycle management for PDBs, including creation, credential management, state control (open/close operations), and deletion. Each PDB operates as an isolated, portable database within the shared CDB infrastructure, allowing you to manage tenant databases independently while benefiting from consolidated resources.
The PDBs table displays all configured PDBs with the following information:
Name - Displays the name of your PDB. PDB names are unique within the database service.
Status - Displays the current runtime state of each PDB. Understanding these states helps you monitor PDB availability and troubleshoot connectivity issues.
Ready
PDB is open and available for connections. Applications can read and write data.
Open Mode: READ WRITE, READ ONLY, or MIGRATE
Restricted
PDB is open but in restricted mode. Only users with RESTRICTED SESSION privilege can connect.
Open Mode: READ WRITE, READ ONLY, or MIGRATE with Restricted: YES
Stopped
PDB is closed and not accessible. No connections are allowed.
Open Mode: MOUNTED
Creating
PDB creation is in progress.
N/A - Provisioning state
Deleting
PDB deletion is in progress.
N/A - Deletion state
Updating
PDB operation (such as credential reset or state change) is in progress.
N/A - Operation state
Failed
PDB operation failed. Check Events tab for details.
N/A - Error state
The status displayed in Tessell reflects the actual Oracle runtime state. Tessell periodically syncs with Oracle to ensure accuracy. If you change the PDB state directly in Oracle (for example, closing it via SQL), Tessell automatically detects and updates the status during the next sync cycle.
Connection Endpoint - Displays the hostname for your PDB. You can copy this hostname using the copy icon next to it.
Created - Displays the date and time when the PDB was created.
Managing Individual PDBs
Click the ellipsis icon (⋮) on the right side of any PDB row to access management options:
Edit Credentials
Reset the master password for the PDB without affecting other PDBs or the CDB.
Select Edit Credentials from the menu. The Edit Credentials dialog opens.
PDB Master Username - Displayed for reference only. This cannot be changed after PDB creation.
PDB Master Password - Specify a new password for the PDB master user.
The password must be at least 9 characters long and can include alphanumeric characters and the following special characters: !, #, $, %, ^, &, *
Click the eye icon to toggle password visibility.
Click the copy icon to copy the password to your clipboard.
Click Save to apply the password change.
Notes:
The password reset is effective immediately for new connections.
Existing active connections are not terminated but will require the new password on reconnect.
Password reset is allowed regardless of PDB state (Ready, Restricted, or Stopped), as long as the CDB service is healthy.
Only one credential update operation is allowed at a time per PDB.
Open PDB
Make a closed (stopped) PDB available for use.
Open a PDB when you need to make it accessible for application workloads, maintenance tasks, or user connections after it is closed.
Select Open PDB from the menu. A confirmation dialog appears.
Review the warning message about the operation.
Click Open to proceed.
The PDB state changes to "Updating" during the operation, then updates to "Ready" once the PDB is successfully opened. The PDB opens in READ WRITE mode by default, following Oracle's native behavior.
Notes:
This operation is only available when the PDB status is "Stopped".
For HA services, the operation is performed in a coordinated manner across all instances to maintain consistency.
The open operation typically completes within seconds to a few minutes depending on PDB size and complexity.
Close PDB
Make an open PDB unavailable by closing it.
Close a PDB when you need to perform maintenance, reduce resource consumption, or temporarily disable access for a specific tenant or workload.
Select Close PDB from the menu. A confirmation dialog appears with a warning that this will disconnect all active sessions.
Review the impact message.
Optionally, add comments to document the reason for closing the PDB.
Click Close to proceed.
The PDB state changes to "Updating" during the operation, then updates to "Stopped" once successfully closed. The PDB closes to MOUNTED state, making it unavailable for connections.
Notes:
This operation is only available when the PDB status is "Ready" or "Restricted".
All active connections to the PDB are forcefully disconnected.
For HA services, the operation is coordinated across all instances.
You can reopen the PDB at any time using the Open PDB operation.
Drop PDB
Permanently delete a PDB and all its data.
Drop a PDB when it is no longer needed and you want to reclaim storage space. This is useful for decommissioning tenant databases or removing test/development PDBs.
Select Drop PDB from the menu. A confirmation dialog appears with a critical warning.
Read the warning: "This action cannot be undone. All data in this PDB will be permanently deleted."
Optionally, add comments to document the reason for deletion.
Specify the PDB name exactly as shown to confirm deletion.
Click Drop to proceed.
Notes:
This operation permanently deletes the PDB and all its data files.
There is no way to recover a dropped PDB unless you have a snapshot or backup.
The PDB must be closed before dropping (Tessell automatically closes it if needed).
This operation cannot be cancelled once initiated.
Adding a New PDB
Create additional Pluggable Databases within your CDB service.
Click + Add Database in the top right corner. The "Create a new Pluggable Database" dialog opens.
PDB details section:
Database Name - Specify a name for the new PDB.
PDB names must begin with alphabets and can contain only alphanumerics and underscores.
Maximum length is 30 characters.
The name must be unique within the CDB service.
Description (optional) - Provide a description to identify the purpose or workload of this PDB.
Database Credentials section:
PDB Master Username - Specify the administrative username for this PDB.
You can customize this username.
Username must start with a letter or underscore, contain only alphanumerics and underscores, with a maximum length of 32 characters.
PDB Master Password - Set the password for the PDB master user.
The password must be at least 9 characters long and can include alphanumeric characters and the following special characters: !, #, $, %, ^, &, *
Click the eye icon to toggle password visibility.
Click the copy icon to copy the password for secure storage.
Custom scripts section:
Post-script - Optionally, select a SQL post-script to execute after PDB creation. Post-scripts run using the PDB master user context. Use post-scripts to automate initialization tasks such as:
Creating application schemas
Granting roles and privileges
Loading seed or reference data
Configuring PDB-specific settings
Script requirements:
Only SQL scripts (.sql) are supported for PDB-level execution.
Scripts must be pre-created and registered in the Script Library application.
Scripts run with PDB master user privileges only (no CDB-level access).
Scripts execute after the PDB is fully created and accessible.
Script failure handling follows the same rules as CDB-level post-scripts.
For HA services, scripts run only on the primary PDB; replicas inherit the state.
Review all configurations and click Create.
The PDB creation process automatically performs the following steps:
Submits the request to create a new PDB
Provisions the PDB within the CDB
Configures the PDB master user and credentials
Executes the post-script if selected
Opens the PDB in READ WRITE mode
Updates the status to "Ready"
Notes:
PDB creation typically completes within a few minutes depending on configuration complexity.
For HA services, the PDB is created on the primary instance and automatically replicated to standby instances.
The PDB inherits certain configurations from the parent CDB (such as character sets and timezone).
Created PDBs are immediately available for application connections once the status shows "Ready".
PDB State Synchronization
Tessell continuously monitors and synchronizes PDB states with Oracle to ensure accurate status reporting:
Automatic state detection: Tessell periodically queries Oracle to detect the runtime state of each PDB.
Manual state changes: If you change a PDB's state directly in Oracle (using SQL commands), Tessell automatically detects and reflects the change during the next sync cycle.
Status accuracy: The displayed status always matches the actual Oracle open_mode and restricted status.
This ensures that you have real-time visibility into PDB availability, even if changes are made outside the Tessell platform.
As an alternative method, use the code to add a database.
Use the Code button at the top-right to view the ‘Code for Create a new Pluggable Database’ window.
On the left-hand side of the window, you can view the API, its type and the payload.
On the right-hand side of the window, you can view the code to create databases in various languages like Shell, Python, Go, Java, Javascript, and Powershell that you can run independently.
You can copy or download this code using respective buttons.
Use the Close button to return back to the main window.
Last updated
Was this helpful?