Steadybit logoResilience Hub
Try SteadybitGitHub icon
Steadybit logoResilience Hub

Verify System Unavailability Status when Oracle Database Can't Be Reached

An unavailable Oracle database might be too severe for suitable fallbacks and requires your system to indicate unavailability appropriately.
Targets:

Containers

Download now

Verify System Unavailability Status when Oracle Database Can't Be Reached

An unavailable Oracle database might be too severe for suitable fallbacks and requires your system to indicate unavailability appropriately.
Targets:

Containers

Download now

Verify System Unavailability Status when Oracle Database Can't Be Reached

An unavailable Oracle database might be too severe for suitable fallbacks and requires your system to indicate unavailability appropriately.
Targets:

Containers

Download now

Verify System Unavailability Status when Oracle Database Can't Be Reached

An unavailable Oracle database might be too severe for suitable fallbacks and requires your system to indicate unavailability appropriately.
Targets:

Containers

Download now
Go back to list
The experiment editor showing the visual structure of the experiment.The experiment editor showing the visual structure of the experiment.

Intent

An unavailable Oracle database might be too severe for suitable fallbacks and requires your system to indicate unavailability appropriately

Motivation

Depending on your context, an unavailable Oracle database may be considered so severe that there are no suitable fallbacks. In this case, ensuring that your system is indicating an appropriate error message is essential. After the Oracle database is back again, your system should recover automatically.

Structure

We ensure that a load-balanced user-facing endpoint fully works while having all pods ready. As soon as we simulate an unavailable Oracle database, we expect the user-facing endpoint to indicate unavailability by responding with a "Service unavailable" status. To simulate the unavailability, we can blackhole the Oracle database client connection using the hostname db.internal.steadybit.com so that no incoming or outgoing traffic is going through. The endpoint should recover automatically once the Oracle database is reachable again.


Download now

.yaml (3 kB)

It's quick and easy

  1. 1.

    Download .yaml file
  2. 2.

    Upload it inside Steadybit
  3. 3.

    Start your experiment!
Screenshot showing the Steadybit UI elements to import the experiment.yaml file into the Steadybit platform.
Tags
Oracle
recoverability

Used Actions

See all
Blackhole

Drops network traffic (incoming and outgoing).

Attack

Attack

Containers

Start using Steadybit for free

Steadybit is free for personal use. Start your journey towards reliability!

Are you unsure where to begin?

No worries, our reliability experts are here to help: book a demo with them!

Steadybit logoResilience Hub
Try Steadybit
HubActionsTargetsExtensionsRecipes
© 2023 Steadybit GmbH. All rights reserved.
Twitter iconLinkedIn iconGitHub icon