| Table of Contents |
|---|
General
A source host is a server that hosts the source databases. A test data environment includes access definition to one source database and a GI. This section describes how to create and manage a Source Host and a Test Data Environment.
A Golden Image (GI) refers to a pre-configured template of a database environment. This template encapsulates a snapshot of the database including its schema, data, configurations, and associated applications. It serves as a master copy from which multiple instances of the database can be rapidly deployed, ensuring consistency, reliability, and quick scalability across different virtual environments.
Supported types of Golden Images for Oracle database
Each type of Golden Image for Oracle databases serves a specific set of needs, from real-time replication to disaster recovery and cloud-based management. The choice of GI should align with the operational objectives and the specific environment, whether it’s on-premises or cloud-based like AWS RDS.
1. Live Golden Image (Live GI)
A Live GI is a real-time replica of a production database, mirroring its current state including data and configurations.
2. RMAN Golden Image (RMAN GI)
An RMAN GI is a backup-based image created using Oracle Recovery Manager (RMAN). It includes all critical components of the database, such as data files, control files, and archived redo logs, captured at a specific point in time.
3. RMAN Standby Golden Image (RMAN Standby GI)
This GI is a variant of the RMAN GI, specifically designed for setting up Oracle standby databases. While it also uses RMAN, it includes additional elements necessary for creating and managing a standby database environment, such as standby redo logs and specific configurations for data guard.
4. RDS AWS RMAN Golden Image
The RDS AWS RMAN GI is exclusively for Oracle databases hosted on Amazon RDS. It combines the features of RMAN with optimizations for AWS cloud infrastructure.
To open the Source work area:
...
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
You can quickly locate a source host by typing its letters on the Search bar. The list updates promptly. |
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
To add a source host, see https://accelario.atlassian.net/wiki/spaces/DVPD/pages/2176975966/21%3AOracle+Initial+Setup#To-add-a-source-host%3A |
To modify a source host:
Select the source host.
Click Modify source host.
Modify the source host as required.
...
To create a Live GI:
Click Create LIVE GI.
Enter a Name.
Click Create.
After the GI is created, the following message appears: Golden Image (live) has been created.The VDB Management window displays the GI that was created.
The GI icon appears on the left.. Click the info icon, next to the GI. It will show the newly created directory on the source server. (The directory was created automatically by Accelario)
You can verify the directory by running
df -hcommand on source. E.g. :
You will need to create your oracle instance on this directory, so all datafiles, controlfiles, redo, archives , dump and audit will point to this path
E.g. spfile parameters:
*.audit_file_dest='/main_pool/00000046/adump'*.control_files='/main_pool/00000046/control01.ctl'*.db_create_file_dest='/main_pool/00000046'*.db_create_online_log_dest_1='/main_pool/00000046'*.db_recovery_file_dest='/main_pool/00000046'*.diagnostic_dest='/main_pool/00000046'*.log_archive_dest_1='location=/main_pool/00000046'The spfile itself should also be placed on the same directory
Once the database is up and running , proceed to activate the GI. Click the Activate icon net to the GI. The Activation verifies that the new database is fully located in the required directory.
Once the activation is completed, a first snapshot is created and you can proceed with VDB creation.
.
To modify a Live GI:
Modify the Golden Image Parameters as required.
...
Click Next to go to the next Modify Test Data Environment window.
Modify the Source DB Parameters as required.
...
To save your changes, click Modify.
RMAN GI
To create a RMAN GI:
...
3. Click Next to go to the next Modify Test Data Environment window.
To modify a
...
RMAN GI:
Modify the Golden Image Parameters as required.
...
4. To save your changes, click Modify.
RMAN STANDBY GI
To modify a RMAN STANDBY GI:
Modify the Golden Image Parameters as required.
...
4. To save your changes, click Modify.
...
AWS RDS RMAN
...
Modify the Golden Image Parameters as required.
...
2. Click Next to go to the next Modify Test Data Environment window.
3. Modify the Source DB Parameters as required.
...
4. To save your changes, click Modify.
GI
First configuration screen
On the first configuration screen choose AWS RDS Oracle and the source server (it should have Oracle Database software installed - same version as the RDS database)
...
Second configuration screen
On the second configuration screen enter AWS parameters
...
AWS authentication
The AWS authentication can be either via access key or via IAM role.
AWS Credentials
Use this mode in case you have prepared a dedicated user in AWS and generated access key for it. How to do it
Access Key ID:
This is a unique identifier provided by AWS, for accessing all AWS services. It's used for authentication. Obtain it from the IAM settings in your AWS account.
Secret Access Key:
A secret key that pairs with your Access Key ID for request authentication and authorization. This key should be generated when creating a new Access Key ID and kept confidential.
IAM role
Use this mode if you have applied an IAM role to the source server. How to do it
AWS Backup Details
Backup Directory Name:
Specify the Oracle directory on the RDS Oracle instance.
E.g.: DATA_PUMP_DIR
Compress Backup (Y/N):
Option to compress backup files, which helps in reducing storage space. Choose 'Y' to enable compression, reducing backup size, or 'N' to store backups in their original size.
AWS S3 Bucket Parameters
Name:
Provide the S3 bucket name that will be used to copy of Oracle backups between RDS and the source server. How to create it
E.g. : rds-ora19
Local Mount Path:
The designated path for mounting the S3 bucket on the source server. This allows to access the backups that are stored on the S3 bucket. The path should reference an existing, empty directory.
E.g. : /home/oracle/s3_backups
S3 Bucket Prefix (Subfolder).
Subfolder within the S3 bucket where the RDS backups will be stored. Do not use any slashes.
E.g. : ora19-folder
Third configuration screen
On the third configuration screen enter the connection details to the RDS Oracle database
...
Make sure that the RDS Oracle user will have the following permissions:
| Code Block |
|---|
GRANT dba TO acc_rman_user;
GRANT EXECUTE ON RDSADMIN.RDSADMIN_UTIL TO acc_rman_user;
GRANT EXECUTE ON RDSADMIN.RDSADMIN_RMAN_UTIL TO acc_rman_user;
GRANT EXECUTE ON RDSADMIN.RDSADMIN_MASTER_UTIL TO acc_rman_user;
GRANT EXECUTE ON RDSADMIN.RDSADMIN_S3_TASKS TO acc_rman_user;
GRANT EXECUTE ON rdsadmin.rds_file_util TO acc_rman_user;
GRANT READ, WRITE ON DIRECTORY DATA_PUMP_DIR TO acc_rman_user; |
Forth configuration screen
On the forth configuration screen enter details of the staging database on the source server (beware that it is different from the RDS Oracle)
...
Some of the fields are not required, since they are derived automatically from previous screens
Test Data Environment (TDE)
To see information about a test data environment:
...