How to Resolve Incorrect Time Zone Issue in MariaDB RDS Instance
Question
An RDS DBA changes the time zone of a Maria DB RDS Instance by setting the dynamic parameter time_zone in the DB Parameter Group to the local time zone of the application.
An application user is still reporting an incorrect time zone.
What actions should the DBA perform to resolve the issue (choose two)?
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D. E.Answer: A and D.
Option A is CORRECT because the custom DB Parameter Group where the time_zone parameter was set must be applied to the RDS instance.
Option B is incorrect because application code change is not necessary when the time zone on the database has been changed.
Option C is incorrect because dynamic parameters in DB parameter groups do not require RDS instance reboot.
Option D is CORRECT because the time zone change takes effect on any new sessions to the database.Any open connections to the database will use the session time zone.To resolve the issue, the user must close the current connection and open a new connection.
Option E is incorrect because the rdsadmin.rdsadmin_util.alter_db_time_zone procedure is used to set the time zone of an Oracle DB instance.
Reference:
https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_MariaDB.html#MariaDB.Concepts.LocalTimeZoneThe issue at hand is that an RDS DBA has changed the time zone of a Maria DB RDS Instance by setting the dynamic parameter time_zone in the DB Parameter Group to the local time zone of the application. However, an application user is still reporting an incorrect time zone.
To resolve this issue, the DBA should perform the following two actions:
Ensure that the DB Parameter Group is applied to the RDS instance: It is possible that the changes made by the DBA have not been applied to the RDS instance. In this case, the DBA should ensure that the DB Parameter Group is applied to the RDS instance. This can be done by navigating to the RDS instance in the AWS Management Console, selecting the instance, and then selecting the "Configuration" tab. The DB Parameter Group should be listed under the "Parameter Groups" section. If it is not listed, the DBA should apply the DB Parameter Group to the RDS instance.
Use rdsadmin.rdsadmin_util.alter_db_time_zone procedure to update the RDS instance time zone to the value set in the DB Parameter Group: It is also possible that the time zone has not been updated correctly. In this case, the DBA should use the rdsadmin.rdsadmin_util.alter_db_time_zone procedure to update the RDS instance time zone to the value set in the DB Parameter Group. This procedure can be run using the AWS Management Console or the AWS CLI. The DBA should ensure that the correct time zone value is set in the DB Parameter Group before running the procedure.
Instructing the application developers to update the application code to use the dynamic parameter type for the time_zone parameter is not a solution to this particular issue, as the DBA has already set the dynamic parameter in the DB Parameter Group. Rebooting the RDS DB instance or instructing the application user to disconnect from the database and start a new session may not resolve the issue.
