AWS RDS Testing

-

 

RDS Failover

Test Scenario
Date

Result

Details
Database Reboot17 Dec 2019(tick)Standard Reboot of the Database via AWS Console.  Several errors observed in the Fusion logs around connection timeouts.  Datasource monitor in Fusion console observed several connection changed state from "Running" to "Suspended".  All recovered within 2m45s mins of the database coming back up.  Elapsed time for overall test was approx 15 minutes.  Validation with Oracle Enterprise Manager Web Console set to refresh every 15s.
Database Reboot with Failover18 Dec 2019(tick)Reboot with Failover between AZ via AWS Console (35s).  Several errors observed in the Fusion logs around connection timeouts.  Datasource monitor in Fusion console observed several connection changed state from "Running" to "Suspended".  All recovered within 2m30s of the database coming back up.  Validation with Oracle Enterprise Manager Web Console set to refresh every 15s.
Database Reboot with Failback18 Dec 2019(tick)Reboot with Failback to original DB between AZ via AWS Console (43s).  Several errors observed in the Fusion logs around connection timeouts.  Datasource monitor in Fusion console observed several connection changed state from "Running" to "Suspended".  All recovered within 2m30s of the database coming back up.  Validation with Oracle Enterprise Manager Web Console set to refresh every 15s.
Database Reboot with Failover 218 Dec 2019(tick)2nd  Reboot with Failover between AZ via AWS Console (38s). Several errors observed in the Fusion logs around connection timeouts.  Datasource monitor in Fusion console observed several connection changed state from "Running" to "Suspended".   All recovered within 2m48s of the database coming back up.  Validation with Oracle Enterprise Manager Web Console set to refresh every 15s.

Comments

Post a Comment

Popular posts from this blog

SQL SERVER – Event ID 107- Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database.

-
SQL SERVER – Event ID 107- Report Server Windows Service cannot connect to the report server database. Error with Report Server One of my clients reported an error which is the subject of the blog. In the event viewer they were seeing below error:     Event Type: Error Event Source: Report Server Windows Service (MSSQLSERVER) Event Category: Management Event ID: 107 Computer: SQLSERVER Description: Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database The error is generic because it doesn’t tell the exact error which is causing a connectivity error. My immediate question was that, are there any more errors? So, I asked them to look at Reporting Service Log file. Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database. The application domain WindowsService_17 failed to initialize. Error: Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerDatabaseUnavailableException: The report se
Read more

SQL Server Builds Information

-
Image
Very Useful information about SQL Server Builds .  It is nicely presented in the blog . Please see  below for our reference . Microsoft SQL Server Version List What version of SQL Server do I have? This unofficial build chart lists all of the known Service Packs ( SP ), Cumulative Updates ( CU ), patches, hotfixes and other builds of MS SQL Server 2017, 2016, 2014, 2012, 2008 R2, 2008, 2005, 2000, 7.0, 6.5 and 6.0 that have been released. Useful articles: How to identify your SQL Server version and edition SQL Server Internal Database Versions Microsoft SQL Server Support Lifecycle Microsoft SQL Server Home Microsoft SQL Server Developer Center Microsoft TechNet: Microsoft SQL Server Microsoft Knowledge Base Sqlservr.exe versions   Quick summary:   RTM (no SP ) SP1 SP2 SP3 SP4   SQL Server 2017      codename vNext 14.0.1000.169 *new           SQL Server 2016 13.0.1601.5 13.0.4001.0 or 13.1.4001.0 13.0.5026.0 or 13.2.5026.0   S
Read more

Using DBCA silent install and disabling automatic memory management

-
Image
Avoid issue [DBT-11211] /app/oracle/product/12.2.0/dbhome_1/bin=> dbca -silent -createDatabase -templateName db_kp_template.dbt -gdbname dgtest1 -sid dgtest1 -responseFile NO_VALUE -characterSet AL32UTF8 -memoryPercentage 20 -emConfiguration NONE [FATAL] [DBT-11211] The Automatic Memory Management option is not allowed when the total physical memory is greater than 4GB.    CAUSE: The current total physical memory is 11GB. Solution : disable automatic memory management with in the response file and you will be fine :) .  /app/oracle/product/12.2.0/dbhome_1/assistants/dbca/templates=> dbca -silent -createDatabase -templateName db_kp_template.dbt -gdbname dgtest1 -sid dgtest1 -responseFile NO_VALUE -characterSet AL32UTF8 -automaticMemoryManagement FALSE -memoryPercentage 20 -emConfiguration NONE Enter SYS user password: Enter SYSTEM user password: [WARNING] [DBT-06208] The 'SYS' password entered does not conform to the Oracle recommended standards.    CAUS
Read more