Skip to content

Commit 690a475

Browse files
authored
Merge branch 'main' into NicolaCimitile-patch-7
2 parents 85e0ddb + 6664854 commit 690a475

File tree

7 files changed

+710
-9
lines changed

7 files changed

+710
-9
lines changed

data-platform/exadata-cloud-at-customer/exacc-infra/single-node-vm-cluster/README.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -16,11 +16,11 @@ Run each single instance database as a two–node cluster, but shut down unneces
1616

1717
# Useful Links
1818

19-
- [About Single-Node VM Cluster](https://docs.oracle.com/en-us/iaas/exadata/doc/ecc-manage-vm-clusters.html#GUID-F528AA9C-2130-4E15-B8DE-DF65FD580789)
19+
* [About Single-Node VM Cluster](https://docs.oracle.com/en-us/iaas/exadata/doc/ecc-manage-vm-clusters.html#GUID-F528AA9C-2130-4E15-B8DE-DF65FD580789)
2020

21-
- [Using the Console to Create a Single-Node VM Cluster](https://docs.oracle.com/en-us/iaas/exadata/doc/ecc-manage-vm-clusters.html#GUID-6F475E61-176B-481D-92B9-5FD93326C7AA)
21+
* [Using the Console to Create a Single-Node VM Cluster](https://docs.oracle.com/en-us/iaas/exadata/doc/ecc-manage-vm-clusters.html#GUID-6F475E61-176B-481D-92B9-5FD93326C7AA)
2222

23-
- [Using the Console to View Single-Node VM Cluster Details](https://docs.oracle.com/en-us/iaas/exadata/doc/ecc-manage-vm-clusters.html#GUID-CEDD32D1-3309-4ED3-BB28-335348CDE790)
23+
* [Using the Console to View Single-Node VM Cluster Details](https://docs.oracle.com/en-us/iaas/exadata/doc/ecc-manage-vm-clusters.html#GUID-CEDD32D1-3309-4ED3-BB28-335348CDE790)
2424

2525

2626
# License
@@ -31,4 +31,4 @@ Licensed under the Universal Permissive License (UPL), Version 1.0.
3131

3232
See [LICENSE](https://github.com/oracle-devrel/technology-engineering/blob/main/LICENSE) for more details.
3333

34-
Reviewed 28/06/2024
34+
Reviewed 30/10/2024
Lines changed: 49 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,49 @@
1+
# Exadata Cloud@Customer - Health Check
2+
3+
## Introduction
4+
5+
The Health Check is an assessment that can be requested by the Customers to review the ExaDB-C@C deployments.
6+
7+
The main reasons that may motivate the request of an ExaDB-C@C Health Check are:
8+
9+
* Check ExaDB-C@C deployment best-practices application, to verify any drift in the configurations that may lead to unexpected behaviours.
10+
* Verify if the implemented Architecture matches with the requirements defined by the customer during the solution definition. Each solution has its own requirements in terms of High Availability, SLAs, Backup Policies, Patching Policies, and Disaster Recovery. Verifying that the running services match all the prerequisites, help in the definition of a robust and well-defined solution, reducing the risks to expose the customer to unexpected issues that are often caused by misconfigured systems are all amongst the objectives.
11+
* Assess the infrastructure after experiencing any unexpected behavior. Even if the Health Check is not a reactive measure, getting the possibility to assess the entire infrastructure after the immediate resolution of disruptive events, may help in preventing further faults: a critical issue can be the consequence of misconfigured systems, where identifying any discrepancies at an early stage from the best practices will help in avoiding escalations for certain situations.
12+
13+
## Goals
14+
15+
The goals of the Health Check are the following:
16+
17+
* Verify the architecture, identify any logical discrepancies between the requirements and the defined configurations
18+
* Verify the ExaDB-C@C configurations, identify any issues that may be caused by non compliant systems
19+
* Offer the customer the possibility to get a consolidated report of the health of its overall infrastructure
20+
21+
## How-To
22+
23+
To request the ExaDB-C@C Health Check, Please reach out to your Oracle Account Team.
24+
25+
The assessment will be led by the EMEA Exadata Cloud@Customer Specialist Team.
26+
27+
To proceed with the analysis, the initiator will be asked to provide:
28+
* Compiling detailed information to a questionnaire on the overall deployment
29+
* Architecture References, documenting the solution requirements and the implemented configuration
30+
* Compliance Reports & Configuration Details
31+
32+
Once the Health Check is completed, the initiator will receive a commprehensive report detailing all findings of the analysis.
33+
34+
## Customer Guidelines
35+
36+
Below is a list with the instructions on how to retrieve the solution data useful for the analysis:
37+
38+
* [AHF Reports](https://github.com/oracle-devrel/technology-engineering/tree/main/data-platform/exadata-cloud-at-customer/exacc-value/exacc-healthcheck/healthcheck-ahf-report)
39+
* [AWR Dumps](https://github.com/oracle-devrel/technology-engineering/tree/main/data-platform/exadata-cloud-at-customer/exacc-value/exacc-healthcheck/healthcheck-awr-dump)
40+
41+
## License
42+
43+
Copyright (c) 2024 Oracle and/or its affiliates.
44+
45+
Licensed under the Universal Permissive License (UPL), Version 1.0.
46+
47+
See [LICENSE](https://github.com/oracle-devrel/technology-engineering/blob/main/LICENSE) for more details.
48+
49+
Reviewed 30/10/2024

0 commit comments

Comments
 (0)