Database Service home page
At the top of the database service home page, the status of the database service is displayed below the service name. Next to status, you can view:
Snapshot
When a manual or automatic snapshot of the database service is in progress, a snapshot icon appears next to the status. Clicking this icon displays the details of the ongoing snapshot.
Patching
If a higher Oracle quarterly patch version is available from Tessell, Patch Available appears next to the status. To view the new versions available for your DB Service, hover over Patch Available and then click Patch Now.
Note:
Tessell highly recommends taking a snapshot of the database before patching to prevent any data loss.
Tessell releases new Oracle PSUs to the platform within 2 weeks of release from Oracle.
Tessell also supports publishing one-off Oracle patches to the platform.
A Patch Database Engine Version window pops up where you can:
Choose a version of the database engine available from the dropdown list.
Optionally, edit the number of instances to patch if the service has more than one instance. By default, all the instances are patched. The primary and HA instance update together, you cannot deselect HA instance from the primary.
An estimated service downtime is displayed for patching.
Select the Patch Database Engine Version check box.
Click Start Patch.
The request to apply the patch is updated and following steps takes place automatically:
Request is submitted to patch the software for DB service instances from older version to new version.
Installs the new version of Oracle binaries.
Note: For a multi-service deployment, this step is performed only for patching the first service.
Patches the DB Service Instance(s).
Service is ready and updates the Tessell metadata.
For HA Services, Tessell follows Standby-First patching with rollover mode, minimizing the downtime only for the “Switchover”. By default, there is one switchover during patching operation and the roles of instances are changed at the end of patching. If the customer intends to have the primary and standby instances as-is role post patching, please ask Tessell support to enable this feature flag. If this feature flag is turned on, another switchover is triggered at the end of patching.
Parameter Update
If a new version of parameter profile is available for the database service, it displays Parameter Update available. Hover over the parameter update to see which new parameter profiles are available for the DB service. For more information, see change parameter profile.
Upcoming schedules
Upcoming schedules, such as start, stop, or delete are displayed next to the status. Hover over a schedule to view its details, including the scheduled actions.
More info
The more information icon gives a summary of the database service. Following details are displayed:
Cloud details
Cloud
Region
Availability Zone(s)
Subscription
VPC or VNet
Storage details
Storage Provider - Displays the storage type selected as per your cloud provider.
Volume Size - Displays the storage size in GiB.
Max throughput - Displays the maximum throughput value in MiB/s.
IOPS - Displays the IOPS value specified for your storage.
Compute details
Compute - Displays the selected compute shape for your database service. Click the tooltip next to the shape to view the information about the compute shape.
vCPUs - Displays the number of vCPUs allocated for your database service.
Memory - Displays the amount of memory allocated for your database service.
Storage - Displays the amount of storage space allocated for your database service.
Storage Encryption - Displays the name of the encryption key assigned to your database service. It displays disabled if it was not enabled during the provisioning process.
Software details
Software version - Displays the version of the database engine you selected for your database service.
Parameter Profile - Displays the name of the parameter profile selected for your database service. Click the tooltip next to the profile name to view the complete information about all the parameters and their values for the assigned profile.
Character Set - Displays the character set selected for your Oracle database service.
National Character Set - Displays the national character set selected for your Oracle database service.
Maintenance - Displays the day and time scheduled for the maintenance of your database service.
Edition - Displays the edition of the selected database engine for your database service.
Owner
Owner - Displays the username of the owner.
My Role - Displays your role for the database service. The possible values are Owner, Co-owner, or Read-only.
Date created - Displays the date and time when the database service was created.
Running since - Displays the date and time since your database is up and running.
Stopped at - Displays the date and time when your database was stopped.
TRN - Displays the Tessell resource name. The TRN is a global unique id and can be used in operating database services through Tessell Rest APIs.
At the top right-side of the database service home page, you see the following options:
Availability Machine
Click to access the Availability Machine home page for the database service. For more information, see Availability Machine home page.
Dataflix
Click to access the Dataflix home page for the database service. For more information, see Dataflix home page.
Start Service
Click to start the database service. This option is available if the database service is stopped.
Stop Service
Click to stop the database service. This option is available if the database service is up and running.
Refresh Data
This option is available only if the database service is cloned.
The refresh feature from Tessell offers a flexible solution for development and testing environments by enabling you to update database clones with the most recent snapshot, eliminating the need to create entirely new database service clones. This feature maintains data consistency and security and can be initiated either manually or automatically.
To ensure the cloned environment functions correctly, tasks such as data validation, configuration adjustments, and other custom operations are crucial. By enabling pre- and post-scripts during the refresh process, you can automate these essential tasks, thereby seamlessly meeting their specific requirements.
To perform cross-region database refreshes, you must first configure the DAP policy in the Availability Machines app. This policy is necessary for replicating snapshots and PITR data to the desired region. A single source can have multiple clones and refresh can only happen from source to destination. Refresh between clones is not supported.
Click this option to refresh the cloned service data.
Select the date to which you wish to refresh from the Recovery Date box.
Note: The calendar shows only the dates that have data available based on the source instance’s RPO policy.
Select whether to recover from snapshots or PITR in the Recovery Mode panel.
Available Snapshots panel displays available snapshots for the selected data.
PITR invokes a clock that allows you to select the exact time to recover.
Optionally, in the Custom Scripts panel you can select pre and post scripts from the respective dropdown list.
To use a custom script, ensure that you have uploaded scripts in the Script Library application under DB Services app family.
Click Submit to initiate the refresh.
Click the ellipsis icon (︙) for following actions:
Restore
Restore functionality is designed to restore a copy of the data from a chosen time into a new VM of the same shape as source. Most of the configurations are kept unchangeable in the restore operation.
Select this option to restore the database service.
Following options are displayed:
In-place restore: Restore the database to the selected recovery point in the same DB service.
Note: In-place restore is available only for Oracle database on Exadata system.
Out-of-place restore: Restore the database to the selected recovery point in a new VM.
For restore, the possible options are:
Snapshot
Select snapshot option to restore the database service to automated or manual snapshots and click Next.
This opens the Dataflix application, you can view a list of available snapshots, each with its corresponding timestamp, storage size, and number of regions.
Select the snapshot, review the details of the selected snapshot like creation timestamp, size, number of databases, and the cloud details.
Click the Select to Restore button at the bottom.
Choose your database and its compute shape for either a new or existing server.
Specify the master username and master password of the database service.
Select the Restore button from the bottom to restore the database service up to the selected snapshot time. The following steps are performed automatically:
Request is submitted to restore the database service up to given snapshot time
Creates compute instance(s)
Configures the database
Availability Machine is setup
Triggers first snapshot
PITR
Select the PITR option to restore to a particular point in time from the available continuous data region and click Next.
This opens the Dataflix application.
Pick a time to restore your service on the Regions and Availability Zones.
Click the Select to Restore button at the bottom.
Specify the master username and master password of the database service
Select the Restore button from the bottom to restore the database service up to the selected timestamp. The following steps are performed automatically:
Request is submitted to restore the database service up to given snapshot time
Creates compute instance(s)
Configures the database
Availability Machine is setup
Triggers first snapshot
Maximum Recoverability
Select to restore the database service to the last committed transaction. This option ensures the usage of redo logs from the source VM if they are available and accessible.
Edit Service
Select Edit Service option to rename the database service, update the description of the database service, enable delete/stop protection or enable auto minor version update.
For more information, see Edit the Service.
Resize
Tessell supports resizing of the compute and storage for database services.
Note: Tessell highly recommends taking a snapshot of the database before resizing.
Select Resize to update the compute shape or storage.
Compute resize:
Compute resize is a downtime operation. For HA database services, this is done in a rollover approach to keep near zero downtime.
For multi-instance databases, select the desired instance to modify under MODIFY COMPUTE on the Resize compute page.
By default, all the instances are selected to modify. The primary and HA instance are modified together, you cannot deselect HA instance from the primary.
Note: For multi-service setups, the resize compute option is located on the specific server's page. This is because resizing the compute affects all database services running on that server.
Drag the slider to select the No. of vCPUs, see the respective change in Select compute shape dropdown list.
Choose a compute shape from the Select compute shape dropdown list.
When modifying compute shapes, you can also modify the parameter profile. Choose a parameter profile from the dropdown list.
Select the “I understand the consequences, resize the compute” check box.
Automatically the following steps are taken:
Submits the request with new settings
Stops the databases
Applies the new settings to the database
Starts the database
Resize storage:
This is a non-downtime operation. Storage can only be increased, shrinking or reducing the storage is not supported.
Specify Storage, IOPS, and Throughput values under MODIFY STORAGE on the Resize storage page.
By default, all the instances are selected to modify.
Resize storage value you specify here is the total storage value you need, that is existing storage value plus the additional storage value you need.
For multi-instance databases, specify the IOPS and Throughput value for each instance.
Storage resizing applies to all instances, you cannot modify storage for individual instances.
Select the “I understand the consequences, resize the storage” check box.
Automatically the following steps are taken:
Submits the request with new settings
Applies the new settings to the database
Change Parameter Profile
Note: Tessell highly recommends taking a snapshot of the database before changing parameter profile to prevent any data loss.
Using this flow, you can either:
Apply a new parameter profile to the database service.
Apply changes from the existing parameter profile.
If any parameters are altered in Governance > DB Governance > Parameters, and those service parameters are out of sync with the existing profile, this option enables users to synchronize the database and restarts it. This occurs if the altered parameters are "static” in nature, requiring a database restart to be applied.
Select Change Parameter Profile option to update the parameter profile for the database service.
Change Parameter Profile window opens.
Choose a new parameter profile from the dropdown list.
Select when to apply the changes.
Three options are available:
Apply in maintenance window - Select this option to update the parameter profile in the upcoming scheduled maintenance window.
Apply later - Select this option to schedule your updates at a convenient time.
This creates a custom, one-time maintenance window that can also be used for scheduling other tasks.
Apply immediately - Select this option to apply the changes immediately.
Note: These changes, including any other pending modifications, are applied asynchronously and immediately, regardless of the scheduled maintenance window. This immediate application, due to the inclusion of pending changes, may lead to service downtime.
Select the “I understand the consequences, apply changes immediately” check box.
Select the Apply button to apply the changes.
Delete
Select to delete the service. For more information, see Delete the service.
Using the code for operations like Restore, Resize, Refresh Data and Change parameter profile:
Use the Code button to view the code in different languages like Shell, Python, Go, Java, Javascript, and PowerShell.
You can copy or download the code using the respective buttons in the top-right corner.
Use the Close button at the bottom left corner to return back to the main window.
When you click a database service, various tabs are displayed on the Database service home page that includes, Overview, Monitoring, Logs, Instances, Maintenance window, Databases, Integrations, Events, Schedules, Sharing, and Settings. Let us discuss each of these tabs in the next steps.
Figure 2: Database Service home page
Last updated
Was this helpful?