> For the complete documentation index, see [llms.txt](https://docs.tessell.com/tessell/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tessell.com/tessell/database-engines/tessell-for-oracle/db-services/my-services/database-service-home-page.md).

# Database Service home page

The database service home page is the central control plane for a single Oracle database service. It displays the service status, provides quick-access action buttons, and organises management capabilities across tabs: Overview, Monitoring, Logs, Instances, Maintenance Window, PDBs (Databases), Integrations, Events, Schedules, Sharing, and Settings.

***

## What status indicators appear next to the service name?

| Indicator                      | When it appears                                      | What to do                                                                                                                 |
| ------------------------------ | ---------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
| **Snapshot icon**              | A manual or automatic snapshot is in progress        | Click the icon to see snapshot details                                                                                     |
| **Patch Available**            | A higher Oracle quarterly patch version is available | Click to start patching — see [Patching](/tessell/database-engines/tessell-for-oracle/db-services/my-services/patching.md) |
| **Parameter Update available** | A new version of the parameter profile is available  | Hover to see which profiles are available; use [Change Parameter Profile](#how-do-i-change-the-parameter-profile) to apply |
| **Upcoming schedules**         | A start, stop, or delete schedule is approaching     | Hover to view the scheduled action and timing                                                                              |

***

## What details does the More Info panel show?

Click the **More Info** icon (ⓘ) to see a full summary of the service, grouped into four categories:

**Cloud details**

| Field                | Description                                             |
| -------------------- | ------------------------------------------------------- |
| Cloud                | Cloud provider (AWS, Azure, GCP)                        |
| Region               | Cloud region                                            |
| Availability Zone(s) | AZ(s) used; shows Availability Set if AZ is unavailable |
| Subscription         | The Tessell subscription associated with the service    |
| VPC / VNet           | Virtual network the service is attached to              |

**Storage details**

| Field            | Description                          |
| ---------------- | ------------------------------------ |
| Storage Provider | Storage type for your cloud provider |
| Volume Size      | Storage size in GiB                  |
| Max throughput   | Maximum throughput in MiB/s          |
| IOPS             | Provisioned IOPS value               |

**Compute details**

| Field              | Description                                                       |
| ------------------ | ----------------------------------------------------------------- |
| Compute            | Selected compute shape (click the tooltip for shape specs)        |
| vCPUs              | Number of vCPUs allocated                                         |
| Memory             | Amount of memory allocated                                        |
| Storage            | Storage space allocated                                           |
| Storage Encryption | Encryption key name, or "disabled" if not enabled at provisioning |

**Software details**

| Field                  | Description                                                     |
| ---------------------- | --------------------------------------------------------------- |
| Software version       | Database engine version                                         |
| Parameter Profile      | Parameter profile name (click tooltip for all parameter values) |
| Character Set          | Oracle character set                                            |
| National Character Set | Oracle national character set                                   |
| Maintenance            | Scheduled maintenance day and time                              |
| Edition                | Oracle edition (Standard/Enterprise)                            |

**Owner**

| Field         | Description                                                                 |
| ------------- | --------------------------------------------------------------------------- |
| Owner         | Username of the service owner                                               |
| My Role       | Your role: Owner, Co-owner, or Read-only                                    |
| Date created  | Date and time the service was created                                       |
| Running since | Date and time the database has been continuously running                    |
| Stopped at    | Date and time the database was last stopped                                 |
| TRN           | Tessell Resource Name — a globally unique ID for use with Tessell REST APIs |

***

## What actions are available from the top-right buttons?

| Button                   | Action                                                                                                                                                                    |
| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Availability Machine** | Opens the Availability Machine home page for this service. See [Availability Machine](/tessell/database-engines/tessell-for-oracle/db-services/availability-machines.md). |
| **Dataflix**             | Opens the Dataflix home page for this service. See [Dataflix](/tessell/database-engines/tessell-for-oracle/db-services/dataflix.md).                                      |
| **Start Service**        | Starts the service (visible only when the service is stopped).                                                                                                            |
| **Stop Service**         | Stops the service (visible only when the service is running).                                                                                                             |

***

## What is the Refresh Data feature and when should I use it?

Refresh Data is available only on cloned services. It updates the clone with the most recent snapshot from the source, without creating a new clone. This is designed for development and testing environments that need periodic data currency.

Key capabilities:

* Refresh from **snapshot** or **PITR** (Point-in-Time Recovery).
* Supports **pre- and post-scripts** to automate validation and configuration tasks after refresh.
* Supports **cross-region refresh** when a DAP policy is configured in the [Availability Machines app](/tessell/database-engines/tessell-for-oracle/db-services/availability-machines.md).
* A single source can have multiple clones; refresh flows only from source → clone. Refresh between clones is not supported.

## Can I refresh a clone that is on a different Oracle patch version?

Yes — you can refresh a clone at a higher Oracle patch version from a source at a lower version. For example:

1. Clone production (Oracle 19.26) into a test environment.
2. Patch the clone to a higher version (Oracle 19.30).
3. Continue refreshing the clone from production (still on 19.26) during testing.
4. Patch production once tests pass.

> **Note:**
>
> * Only **minor higher versions** on the clone are supported. Refresh to a major higher version or a lower version than the source is not supported.
> * If the source is later patched beyond the clone's version, refreshing the clone from the updated source is blocked.

### Steps to refresh a cloned service

1. Click **Refresh Data** on the service home page.

   > **Note:** The refresh wizard shows the source and target Oracle versions so you can see version differences before proceeding.
2. Select the recovery date from the **Recovery Date** box.

   > The calendar shows only dates that have data available based on the source instance's RPO policy.
3. Select the recovery mode in the **Recovery Mode** panel:
   * **Available Snapshots** — choose a specific snapshot.
   * **PITR** — use the clock to select an exact recovery time.
4. (Optional) In the **Custom Scripts** panel, select pre and post scripts from the dropdowns.

   > Scripts must be uploaded to the [Script Library](/tessell/database-engines/tessell-for-oracle/db-services/script-library.md) under **DB Services** before they appear here.
5. Click **Submit**.

***

## How do I restore a database service?

| Restore type             | Description                                                                              | Availability           |
| ------------------------ | ---------------------------------------------------------------------------------------- | ---------------------- |
| **In-place restore**     | Restores the database to the selected recovery point in the same DB service.             | Oracle on Exadata only |
| **Out-of-place restore** | Restores the database to the selected recovery point in a new VM (same shape as source). | All Oracle services    |

### Restore from a snapshot

1. Click the ellipsis icon (︙) → **Restore** → select **Snapshot** → **Next**.
2. In the Dataflix application, browse and select a snapshot.
3. Review the snapshot details (creation timestamp, size, number of databases, cloud details).
4. Click **Select to Restore**.
5. Choose your database, compute shape (new or existing server), master username, and password.
6. Click **Restore**. Tessell automatically:
   * Submits the restore request
   * Creates compute instance(s)
   * Configures the database
   * Sets up the Availability Machine
   * Triggers the first snapshot

### Restore using PITR

1. Click the ellipsis icon (︙) → **Restore** → select **PITR** → **Next**.
2. In the Dataflix application, pick an exact time in the available continuous data region.
3. Click **Select to Restore**.
4. Specify master username and password.
5. Click **Restore**. The same automatic steps as snapshot restore are performed.

### Restore to Maximum Recoverability

Select this option to restore to the last committed transaction. Tessell uses redo logs from the source VM if they are available and accessible.

***

## How do I resize compute or storage?

| Resize type        | Downtime impact                                                             | Notes                                                                                                   |
| ------------------ | --------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------- |
| **Compute resize** | Downtime required; HA services use rollover approach for near-zero downtime | For multi-service setups, compute resize is on the server page — it affects all services on that server |
| **Storage resize** | No downtime                                                                 | Storage can only be increased; shrinking is not supported                                               |

> **Note:** Tessell highly recommends taking a snapshot before resizing.

### Steps to resize compute

1. Click the ellipsis icon (︙) → **Resize** → **Resize compute** tab.
2. For multi-instance services, select which instances to modify (primary and HA are always modified together).
3. Drag the vCPU slider or choose a compute shape from the **Select compute shape** dropdown.
4. Optionally change the parameter profile in the same dialog.
5. Select the **I understand the consequences, resize the compute** checkbox.
6. Tessell automatically stops the database, applies the new settings, and restarts it.

### Steps to resize storage

1. Click the ellipsis icon (︙) → **Resize** → **Resize storage** tab.
2. Specify the new total **Storage**, **IOPS**, and **Throughput** values.

   > The value you enter is the total storage you need (not the additional amount).
3. For multi-instance services, specify IOPS and Throughput per instance (storage resize applies to all instances).
4. Select the **I understand the consequences, resize the storage** checkbox.
5. Tessell applies the new settings non-disruptively.

***

## How do I change the parameter profile?

Use the timing option that matches your urgency:

| Timing option                   | Behaviour                                                                                                                                                            |
| ------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Apply in maintenance window** | Changes are applied in the next scheduled maintenance window                                                                                                         |
| **Apply later**                 | Creates a one-time custom maintenance window at your chosen time                                                                                                     |
| **Apply immediately**           | Applies all pending changes asynchronously right now, regardless of the maintenance window. May cause service downtime for static parameters that require a restart. |

> **Note:** Tessell highly recommends taking a snapshot before changing the parameter profile.

### Steps to change the parameter profile

1. Click the ellipsis icon (︙) → **Change Parameter Profile**.
2. Choose a new parameter profile from the dropdown, or apply updates from the existing profile (if parameters are out of sync due to Governance changes).
3. Select a timing option.
4. Select the **I understand the consequences, apply changes immediately** checkbox.
5. Click **Apply**.

***

## How do I use the Code button for programmatic access?

The **Code** button is available for Restore, Resize, Refresh Data, and Change Parameter Profile. It generates ready-to-run code in: **Shell, Python, Go, Java, JavaScript,** and **PowerShell**.

1. Click **Code** in the wizard dialog.
2. Copy or download the generated code using the buttons in the top-right corner.
3. Click **Close** to return to the main window.

***

## What tabs are available on the database service home page?

The following tabs provide detailed management capabilities:

| Tab                                                                                                                                         | Purpose                                                           |
| ------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------- |
| [Overview](/tessell/database-engines/tessell-for-oracle/db-services/my-services/database-service-home-page/overview.md)                     | Connection details, SSL, VM access, private links, allowed IPs    |
| [Monitoring](/tessell/database-engines/tessell-for-oracle/db-services/my-services/database-service-home-page/monitoring.md)                 | OS metrics, DB metrics, Performance Insights                      |
| [Logs](/tessell/database-engines/tessell-for-oracle/db-services/my-services/database-service-home-page/logs.md)                             | Oracle alert, listener, and DBCA trace logs                       |
| [Instances](/tessell/database-engines/tessell-for-oracle/db-services/my-services/database-service-home-page/instances.md)                   | Instance topology, switchover, DR drills, add replica             |
| [Maintenance Window](/tessell/database-engines/tessell-for-oracle/db-services/my-services/database-service-home-page/maintenance-window.md) | Schedule and view maintenance activities                          |
| [PDBs (Databases)](/tessell/database-engines/tessell-for-oracle/db-services/my-services/database-service-home-page/pdbs-databases.md)       | Create, open, close, and drop PDBs in a CDB service               |
| [Integrations](/tessell/database-engines/tessell-for-oracle/db-services/my-services/database-service-home-page/integrations.md)             | Datadog, Qualys, OEM, Splunk integrations                         |
| [Events](/tessell/database-engines/tessell-for-oracle/db-services/my-services/database-service-home-page/events.md)                         | Full audit log of service actions                                 |
| [Schedules](/tessell/database-engines/tessell-for-oracle/db-services/my-services/database-service-home-page/schedules.md)                   | Start/stop/delete schedules                                       |
| [Sharing](/tessell/database-engines/tessell-for-oracle/db-services/my-services/database-service-home-page/sharing.md)                       | Share the service with other users                                |
| [Settings](/tessell/database-engines/tessell-for-oracle/db-services/my-services/database-service-home-page/settings.md)                     | Timezone, maintenance window, performance insights, observability |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.tessell.com/tessell/database-engines/tessell-for-oracle/db-services/my-services/database-service-home-page.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.