Questions tagged with Amazon Relational Database Service
Content language: English
Sort by most recent
I can see there are 4 pages (1 2 3 4) of Recent events for an RDS instance (MySQL) but clcking on them doesn't change the page and also changing page size in the settings to 25 doesn't take effect - it only shows 5 recent events.
Hi,
I am hoping to start using RDS Oracle with Multi-Tenant support(CBD), but I am struggling to create another PDB (a clone of the first PDB ORCL) using the master user "admin".
CREATE PLUGGABLE DATABASE ORCL1 FROM ORCL
Error report -
ORA-65040: operation not allowed from within a pluggable database
65040. 00000 - "operation not allowed from within a pluggable database"
*Cause: An operation was attempted that can only be performed in the root
or application root container.
If I try to switch to root
alter session set container=CDB$ROOT
Error report -
ORA-01031: insufficient privileges
01031. 00000 - "insufficient privileges"
*Cause: An attempt was made to perform a database operation without
the necessary privileges.
*Action: Ask your database administrator or designated security
administrator to grant you the necessary privileges
I have also tried another user and tried to assign the privileges for both of the above but I get a permission denied. Has anyone done similar?
Thanks
The MySQL 8.0.30 community version introduced innodb_redo_log_capacity and deprecates innodb_log_file_size & innodb_log_files_in_group.
Problem is RDS parameter groups do not allow you to modify the new parameter and it defaults to 100M, which for a large production system is 10x too small.
```
+------------------------------+-----------+
| Variable_name | Value |
+------------------------------+-----------+
| innodb_redo_log_archive_dirs | |
| innodb_redo_log_capacity | 104857600 |
| innodb_redo_log_encrypt | OFF |
+------------------------------+-----------+
3 rows in set (0.00 sec)
16:44:56 (8.0.31) [(none)] > select 104857600/1024/1024;
+---------------------+
| 104857600/1024/1024 |
+---------------------+
| 100.00000000 |
+---------------------+
1 row in set (0.00 sec)
```
I have not see anybody ask it here, so has anybody else observed the situation?
From the release Notes:
InnoDB: InnoDB now supports dynamic configuration of redo log capacity. The innodb_redo_log_capacity system variable can be set at runtime to increase or decrease the total amount of disk space occupied by redo log files.
With this change, the number of redo log files and their default location has also changed. From MySQL 8.0.30, InnoDB maintains 32 redo log files in the #innodb_redo directory in the data directory. Previously, InnoDB created two redo log files in the data directory by default, and the number and size of redo log files were controlled by the innodb_log_files_in_group and innodb_log_file_size variables. These two variables are now deprecated.
When the innodb_redo_log_capacity setting is defined, innodb_log_files_in_group and innodb_log_file_size settings are ignored; otherwise, those settings are used to compute the innodb_redo_log_capacity setting (innodb_log_files_in_group * innodb_log_file_size = innodb_redo_log_capacity). If none of those variables are set, redo log capacity is set to the innodb_redo_log_capacity default value, which is 104857600 bytes (100MB).
Several status variables are provided for monitoring the redo log and redo log capacity resize operations.
[1] https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-30.html
Currently, the Create RDS read replica screen doesn't allow choosing a custom parameter group (and option group) on creation so
a new read replica with a smaller instance class ends up getting stuck in "incompatible-parameters" mode because of high values of buffer related parameters in the original primary instance's parameter group, so I have to create the new replica first with the original instance class of the primary instance, change the parameter group and then resize the replica to a smaller instance class.
Also, replication errors can occur while the primary parameter group is applied on the read replica because of MEMORY engine tables which have out of sync rows between the instances, which were meant to be excluded from replication using the read replica custom parameter group.
How can we run sql on mysql RDS and get the output on SNS?
How to setup alert for Blocking Locks in mysql RDS instance?
Hi,
I want to setup an alarm for AWS RDS mysql database. Whenever there is blocking in database sent a mail notification. I set-up it like below. But the alarm is always in INSUFFICIENT DATA state. i simulated blocking in database but no effect.
Does anyone know what this BlockedTransaction metrics is evaluating?
Hi Team,
After you create the blue/green deployment, the DB instance in the green environment is read-only by default.
Can anyone help How to enable write operations on Mysql RDS green environment.
I'm trying to connect to a postgresql RDS database using Datagrip and the AWS Toolkit plugin with IAM Authentication. The instructions on the subject are confusing and inconsistent and it's very unclear to me what I'm doing wrong. Here's what I did:
- enabled IAM Auth on the RDS instance.
- installed the AWS Toolkit and configured the access keys (I can access most services just fine, including viewing files on S3 through Datagrip. So that part is functional)
- I created a policy that allows `rds-db:connect` action and assigned it to my user
- I used the AWS explorer in Datagrip, selected the DB instance, clicked "connect with IAM auth"
- when I run "test connection" I get this:
The details that the toolkit inserts are correct as far as I can tell. I've been googling, and asking, and trying different things. Some places suggest creating a role to connect through an EC2 instance which I completely don't understand (why would I need a complete instance? Why wouldn't I just connect directly?) It's very confusing, incredibly frustrating and I'm stumped. What am I missing?
We are planning on exploring MyRocks database engine of MySQL.
I am aware that AWS RDS MariaDB supports it but haven't found any article if it's not supported by Aurora MySQL Compatible.
Is this available and will it be available in the future?
Thanks!
I've been leveraging the pg_cron extension to run scheduled precompute jobs within the Postgres DB for over a year now, and have never had this issue.
This extension comes with a table that logs the jobs that need to be run, as well as a function that allows you to easily create new jobs and insert them into the table. Today, when trying to schedule a new cron job in the Postgres DB, the DB crashed - terminating all existing connection to the DB.
We haven't changed anything in the DB since yesterday, so it is confusing as to why this extension may be related to the crash. I'm hoping someone can help provide some insight.
Is AWS RDS for MS SQL (non RDS Proxy) a SaaS or PaaS service