Document requirements / setup for Amazon AWS [DBZ-5391]
- Dominant language
- HTML
- Stars
- 6
- Forks
- 8
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 1
Description
Migrated from [DBZ-5391](https://issues.redhat.com/browse/DBZ-5391)
In order to deploy the Oracle connector on Amazon AWS, a specific set of requirements must be met. Much like other RDS databases, Amazon does not give full SYSDBA rights but does offer equivalent permissions and/or database APIs that must be used rather than the default ones exposed directly by Oracle. The following shows the set ups required for AWS and we should find some way to integrate this into the documentation:
Grants
{noformat}
--GRANT EXECUTE ON DBMS_LOGMNR TO dbzuser;
exec rdsadmin.rdsadmin_util.grant_sys_object('DBMS_LOGMNR','DBZUSER','EXECUTE');
--GRANT EXECUTE ON DBMS_LOGMNR_D TO dbzuser;
exec rdsadmin.rdsadmin_util.grant_sys_object('DBMS_LOGMNR_D','DBZUSER','EXECUTE');
--GRANT SELECT on V_$LOGMNR_LOGS to db_user
exec rdsadmin.rdsadmin_util.grant_sys_object('V_$LOGMNR_LOGS','DBZUSER','SELECT');
--GRANT SELECT on V_$LOGMNR_CONTENTS to db_user
exec rdsadmin.rdsadmin_util.grant_sys_object('V_$LOGMNR_CONTENTS','DBZUSER','SELECT');
GRANT LOGMINING to dbzuser; -– Required only if the Oracle version is 12c or later.
{noformat}
Logging:
{noformat}
--- Supplemental Logging
SELECT supplemental_log_data_min FROM v$database;
--ALTER DATABASE ADD SUPPLEMENTAL LOG DATA;
begin
rdsadmin.rdsadmin_util.alter_supplemental_logging(
p_action => 'ADD');
end;
/
-- Archive Retention
begin
rdsadmin.rdsadmin_util.set_configuration(
name => 'archivelog retention hours',
value => '24');
end;
/
commit;
{noformat}
More grants
{noformat}
-- Grants
exec rdsadmin.rdsadmin_util.grant_sys_object('V_$LOG','DBZUSER','SELECT');
exec rdsadmin.rdsadmin_util.grant_sys_object('V_$LOG_HISTORY','DBZUSER','SELECT');
exec rdsadmin.rdsadmin_util.grant_sys_object('V_$LOGMNR_LOGS','DBZUSER','SELECT');
exec rdsadmin.rdsadmin_util.grant_sys_object('V_$LOGMNR_CONTENTS','DBZUSER','SELECT');
exec rdsadmin.rdsadmin_util.grant_sys_object('V_$LOGMNR_PARAMETERS','DBZUSER','SELECT');
exec rdsadmin.rdsadmin_util.grant_sys_object('V_$LOGFILE','DBZUSER','SELECT');
exec rdsadmin.rdsadmin_util.grant_sys_object('V_$ARCHIVED_LOG','DBZUSER','SELECT');
exec rdsadmin.rdsadmin_util.grant_sys_object('V_$ARCHIVE_DEST_STATUS','DBZUSER','SELECT');
exec rdsadmin.rdsadmin_util.grant_sys_object('V_$TRANSACTION','DBZUSER','SELECT');
{noformat}
Contributor guide
Research direction
Start by locating the Oracle connector setup documentation and any existing RDS guidance; compare them with the AWS grants and logging steps listed here. Done means the AWS-specific requirements are integrated into the documentation in a clear setup section.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, sql
- Domain
- cloud, databases, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100