Managing Configuration and Member Tagging

Tagging enables teams to organize configuration members according to business needs.

Oracle Data Guard 26ai introduced a flexible tagging feature that enables users to associate arbitrary key-value pairs with Oracle Data Guard broker configuration members.

These user-defined tags logically group database members based on attributes, like location, lifecycle status, organization, and other business-specific identifiers. This aids management and monitoring capabilities.

Member tagging is useful in the following situations:

Location-based Grouping: Tag members based on their geographical location for better management and monitoring of global data centers.
```
EDIT MEMBER orcl_iad_1 SET Tag region='us-ashburn-1';
EDIT MEMBER orcl_phx_1 SET Tag region='us-phoenix-1';
```
Lifecycle Status Tracking: Tag members based on their lifecycle status to facilitate operations and maintenance planning.
```
EDIT MEMBER orcl_iad_1 SET Tag lifecycle='Production';
EDIT MEMBER orcl_iad_2 SET Tag lifecycle='Development';
```
Compliance: Track compliance-related information, such as regulations (e.g., GDPR, HIPAA) that the database member needs to adhere to.
```
EDIT MEMBER orcl_fra_1 SET Tag compliance='GDPR';
EDIT MEMBER finance_iad_2 SET Tag compliance='HIPAA';
```

Note:

The tag name and value can be set at the discretion of the users with the following limitation:

Tag names starting with "ORA" are reserved and cannot not be set unless documented or instructed by Oracle Support.