Questions tagged with Database
Content language: English
Sort by most recent
Hi, having an issue with incorrect results returned from a dynamodb scan, either from the console or programatically. First image shows the correct result for a query (5 rows returned): https://www.dropbox.com/s/7x6s9q89q7gd5go/dunamodb1.png?dl=0 Second image shows same results from a scan - either in the console or through node.js code (4 rows returned) https://www.dropbox.com/s/kpk3wus2vlf1ywz/dynamodb2.png?dl=0 There are actually 840 rows in this table if i just move through 50 rows at a time by viewing table details, but a scan only returns 813 rows. Thx
I have an RDS instance using MySQL engine version 5.7.36. RDS recommends updating to a newer minor 5.7 engine version, but no versions are available to choose when modifying the instance. describe-db-engine-versions doesn't list 5.7.36, but does list 5.7.34 and 5.7.37, and newer versions after that. Snapshots taken from the instance cannot be restored, because creating a new instance using the version the snapshots specify is not allowed. 5.7.36 is still documented on https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/MySQL.Concepts.VersionMgmt.html as supported until April 2023. As far as I can see there are no notifications that it's deprecated. There was a Health notification in January of impending end of support but no indication of this behavior: > Starting March 20, 2023 00:00:01 AM UTC, you will not be able to create new RDS instances with MySQL minor versions 8.0.27, 8.0.26, 8.0.25, 8.0.23, 5.7.36, 5.7.34 and 5.7.33 from either the AWS Console or the CLI. We recommend you to upgrade your databases before April 20, 2023. RDS will upgrade your MySQL databases running minor versions 8.0.27, 8.0.26, 8.0.25, 8.0.23, 5.7.36, 5.7.34 and 5.7.33 as well as any instances restored from the snapshots of these versions to the latest minor version during a scheduled maintenance window between April 20, 2023 00:00:01 UTC and May 20, 2023 00:00:01 UTC. On May 20, 2023 00:00:01 AM UTC, any MySQL databases running minor versions 8.0.27, 8.0.26, 8.0.25, 8.0.23, 5.7.36, 5.7.34 and 5.7.33 that remain will be automatically upgraded to the latest minor version by RDS regardless of instances’ scheduled maintenance window. So, upgrades should be available until April 20, and even today new instances should still be able to be created with these versions. Every other version listed in the notification is still currently available, except 5.7.36. To me this indicates an error or mistake on the part of AWS. What are my options here?
Is there a way we can refresh a limited set of data from Prod AWS account to Dev AWS account PostgreSQL database? For e.g., I have to refresh few rows from couple of tables of Prod to Dev DB. I don't want to do a full refresh of the data using snapshots. Database: AWS Aurora PostgreSQL
Hi, I need to migrate PostgreSQL DB in AWS. Is it possible to have an estimate migration's time? Thanks in advance for your help.
I've configured the Athena connection to a RDS SQL Server database using a JDBC driver. After choosing the Data Source the Database does not load and there is a "Network Failure" shown without any information. What might be the cause of such error or where I can find more information on how to solve such case? ![Enter image description here](/media/postImages/original/IMQajw0sQHTgyDgntZCvLPJg)
Im trying to follow this guide https://workmarket.tech/zero-downtime-maintenances-on-mysql-rds-ba13b51103c2 , for \*active\*-\*active\* replication. But on command `CHANGE *active* TO *active*_HOST=....` i get error: `ERROR 1227 (42000): Access denied; you need (at least one of) the SUPER or REPLICATION_*secondary*_ADMIN privilege(s) for this operation` As i understood AWS forbids this kind of access via command line access. So, how do i then do this change? i assume via `parameters group`... but how? \*active\* = some non inclusive word \*secondary\* = some other non inclusive word
We using RDS Read replica For Production DB. RDS Read Replica taken more Storage than main DB . Prod Storage : 81 GB Read Replica: 1000GB Even now we are getting the recommendation to increase the storage even more . Why does it take more storage? How to reduce the storage size without affecting read replica. It also afflicted our prod DR process and cost wise. confirm we promote the Read Replica DB to Main DB it take same amount of storage.
Hi, I'm trying to create a copy of an Aurora PostgreSQL cluster snapshot in a different region using the aws cli, I was able to do it five times, but now I'm getting the error message **Cannot copy more than 5 snapshots concurrently to the same region**. I suspect that the problem was that I deleted those snapshots while they were being copied and for some reason the status was never updated. ##### Question: do I have to contact the technical support so that they can update the status of the snapshots in the region or is there a way to clean up the snapshots that were deleted before copy them?
current scenario 1 MysqlRDS with 8TB of an instance. After migrating some application log tables, it was found that: - We are allocating an unnecessary 6TB, as the total size of the database is approx. 2TB AWS does not yet provide means to downsize allocated storage. what is the need - migrates the database to another instance in the same region with the storage already adjusted and thus freeing us from paying for an unnecessary 6TB of storage, What is the best strategy for a bank with this volume, operating with 2 read replicas, 24 hours a day, 365 days a year.
Hello there, I'm trying to drop a DB on the Aurora, but the requests just hangs. I've tried several times and the last attempt has been runnning for 600 seconds. it's a tiny DB of 20MB gzipped. * running `show databases;` returns the borken_db in the list. * running `use broken_db;`now hangs too. * running `show processlist`returns the following: | Id | User | Host | db | Command | Time | State | Info | |----|-----------------|-----------------|-------------|---------|------|----------------------------------|-----------------------------| | 5 | event_scheduler | localhost | | Daemon | 8310 | Waiting on empty queue | | | 19 | rdsadmin | localhost | | Sleep | 0 | | | | 21 | rdsadmin | localhost | | Sleep | 1 | | | | 22 | rdsadmin | localhost | | Sleep | 1 | | | | 25 | rdsadmin | localhost | | Sleep | 252 | | | | 36 | root_user | 10.0.0.48:36768 | broken_db | Sleep | 2404 | | | | 38 | root_user | 10.0.0.48:36788 | mysql | Query | 2736 | Waiting for schema metadata lock | DROP DATABASE `broken_db` | | 47 | root_user | 10.0.0.48:36826 | mysql | Query | 2346 | Waiting for schema metadata lock | drop DATABASE broken_db | | 50 | root_user | 10.0.0.48:36854 | | Query | 1990 | Waiting for schema metadata lock | USE `broken_db` | | 51 | root_user | 10.0.0.48:36874 | mysql | Query | 0 | init | show processlist | | 52 | root_user | 10.0.0.48:36894 | mysql | Query | 1042 | Waiting for schema metadata lock | use broken_db | | 58 | root_user | 10.0.0.48:36922 | | Query | 178 | Waiting for schema metadata lock | use broken_db | | 59 | rdsadmin | localhost | | Sleep | 7 | | | where do I go from there?
For the last few days, I am trying to upgrade an RDS SQL Server web-edition instance from db.t2.small to db.t3.small. but every time i receive the following error. *We're sorry, your request to modify DB instance xxx has failed. Cannot modify the instance class because there are no instances of the requested class available in the current instance's availability zone. Please try your request again at a later time.* I have also used AWS CLI to check the orderable db-instances describe-orderable-db-instance-options This returns command also shows that orderable instances are available in us-east-1 with instance type as db.t3.small , but still i am unable to change the instance type. Is anyone facing the same issue or has a solution to this ?
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