{"id":37816,"date":"2020-09-03T05:47:00","date_gmt":"2020-09-03T12:47:00","guid":{"rendered":"https:\/\/virtual-dba.com\/?p=37816"},"modified":"2021-02-10T18:11:04","modified_gmt":"2021-02-11T01:11:04","slug":"resolving-sql0930n-memory-errors-after-upgrade","status":"publish","type":"post","link":"https:\/\/virtual-dba.com\/blog\/resolving-sql0930n-memory-errors-after-upgrade\/","title":{"rendered":"Resolving SQL0930N Memory Errors after an RHEL 7.8 Upgrade"},"content":{"rendered":"\n<p>A colleague and I were recently working on a Db2 server with a large amount of memory (512 Gb) and were supporting the system administrators in applying operating system maintenance to bring the system from RedHat Enterprise Linux (RHEL) 7.6 to RHEL 7.8.<\/p>\n\n\n\n<p>The operating system upgrade was successful, however, we found that we were unable to activate the database after the system was rebooted. We received an SQL0930N error (&#8220;There is not enough storage available to process the statement.&#8221;) in response to the ACTIVATE DATABASE command.<\/p>\n\n\n\n<p>Looking in the db2diag.log file, we found the following error message:<\/p>\n\n\n<pre><code>2020-08-10-11.58.48.813633-240 I64894E612            LEVEL: Error  \nPID     : 24888                TID : 140736762734336 PROC : db2sysc 0  \nINSTANCE: db2inst1             NODE : 000            DB   : SAMPLE  \nAPPHDL  : 0-7                  APPID: *LOCAL.db2inst1.200810155758  \nAUTHID  : DB2INST1             HOSTNAME: db2server  \nEDUID   : 48                   EDUNAME: db2agent (SAMPLE) 0  \nFUNCTION: DB2 UDB, buffer pool services, sqlbinit, probe:604  \nMESSAGE : ZRC=0x850F0005=-2062614523=SQLO_NOSEG  \n          \"No Storage Available for allocation\"  \n          DIA8305C Memory allocation failure occurred. \n<\/code><\/pre>\n\n\n<p>The <em>SQLO_NOSEG<\/em> error code pointed me to the issue that Db2 was unable to allocate enough shared memory segments to support the database&#8217;s memory requirements.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Finding the issue<\/strong><\/h3>\n\n\n\n<p>We followed <a href=\"https:\/\/www.ibm.com\/support\/knowledgecenter\/SSEPGG_11.5.0\/com.ibm.db2.luw.qb.server.doc\/doc\/t0008238.html\" target=\"_blank\" rel=\"noreferrer noopener\">IBM&#8217;s documentation<\/a> for setting the kernel parameters <strong>kernel.shmmni<\/strong> and <strong>kernel.msgmni<\/strong>, which states that you should set kernel.shmmni to 256 times the size of RAM (in GB), and kernel.msgmni to 1024 times the size of RAM (also in GB). On this server, with 512 Gb RAM, the values were set to 131072 and 524288, respectively.<\/p>\n\n\n\n<p>However, we found that upon rebooting to the new kernel version included with RHEL 7.8 (kernel version 3.10.0-1127), these values were not set as expected:<\/p>\n\n\n<pre><code>$ ipcs -l  \n  \n------ Messages Limits --------  \nmax queues system wide = 4096  \nmax size of message (bytes) = 2097152  \ndefault max size of queue (bytes) = 2097152  \n  \n------ Shared Memory Limits --------  \nmax number of segments = 4096  \nmax seg size (kbytes) = 536870912  \nmax total shared memory (kbytes) = 1073741824  \nmin seg size (bytes) = 1  \n  \n------ Semaphore Limits --------  \nmax number of arrays = 129024  \nmax semaphores per array = 250  \nmax semaphores system wide = 256000  \nmax ops per semop call = 32  \nsemaphore max value = 32767  \n<\/code><\/pre>\n\n\n<p>Furthermore, attempts to manually increase these values also failed:<\/p>\n\n\n<pre><code># sysctl -w kernel.shmmni=131072  \nsysctl: setting key \"kernel.shmmni\": Invalid argument  \nkernel.shmmni = 131072 \n<\/code><\/pre>\n\n\n<p>Experimentation revealed that we <em>were<\/em> able to increase both kernel.shmmni and kernel.msgmni to 32768, but no further. If you are following IBM&#8217;s recommendations, this means that you won&#8217;t be able to set kernel.msgmni properly if you have more than 32Gb of RAM on your server.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Thanks, RedHat?<\/strong><\/h3>\n\n\n\n<p>Fortunately, we were working with a very smart system engineer, and after scratching our heads for a while (and considering rolling the maintenance back), she found this RedHat <a href=\"https:\/\/access.redhat.com\/solutions\/4968021\" target=\"_blank\" rel=\"noreferrer noopener\">support article<\/a>.<\/p>\n\n\n\n<p>The article confirmed our suspicion that RedHat had made some changes to the kernel in RedHat 7.8, limiting the kernel.msgmni, kernel.semmni, and kernel.shmmni to 32768.<\/p>\n\n\n\n<p>To our relief, the article provides a <strong>solution<\/strong>: add the <strong>ipcmni_extend<\/strong> boot-time command-line option for the kernel. We set this parameter by adding the ipcmni_extend option to GRUB_CMDLINE_LINUX line in the \/etc\/default\/grub file and executing the grubby command. After rebooting the server, we were relieved to discover that ipcs -l was reporting the proper values for kernel.msgmni and kernel.shmmni.<\/p>\n\n\n\n<p>With these values set properly, we were able to activate our database and inform the customer that the operating system patching had been completed successfully.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>A colleague and I were recently working on a Db2 server with a large amount of memory (512 Gb) and were supporting the system administrators in applying operating system maintenance to bring the system from RedHat Enterprise Linux (RHEL) 7.6 to RHEL 7.8. The operating system upgrade was successful, however, we found that we were [&hellip;]<\/p>\n","protected":false},"author":44,"featured_media":37818,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"off","_et_pb_old_content":"","_et_gb_content_width":"","content-type":"","footnotes":""},"categories":[4166,17],"tags":[4136],"class_list":["post-37816","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog","category-db2","tag-db2-error"],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v27.1 (Yoast SEO v27.1.1) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>Resolving SQL0930N Memory Errors after an RHEL 7.8 Upgrade<\/title>\n<meta name=\"description\" content=\"After upgrading to RHEL 7.8, you may run into SQL0930N errors on systems with more than 32Gb memory. Learn how to resolve the issue and get your database running again.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/virtual-dba.com\/blog\/resolving-sql0930n-memory-errors-after-upgrade\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Resolving SQL0930N Memory Errors after an RHEL 7.8 Upgrade\" \/>\n<meta property=\"og:description\" content=\"After upgrading to RHEL 7.8, you may run into SQL0930N errors on systems with more than 32Gb memory. Learn how to resolve the issue and get your database running again.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/virtual-dba.com\/blog\/resolving-sql0930n-memory-errors-after-upgrade\/\" \/>\n<meta property=\"og:site_name\" content=\"Virtual-DBA Remote DBA Services &amp; Support - Certified Database Experts\" \/>\n<meta property=\"article:published_time\" content=\"2020-09-03T12:47:00+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2021-02-11T01:11:04+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/virtual-dba.com\/media\/Resolving-SQL0930N-Memory-Errors-after-an-RHEL-7.8-Upgrade.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"557\" \/>\n\t<meta property=\"og:image:height\" content=\"291\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Ian Bjorhovde and Marc Petros\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@virtual_dba\" \/>\n<meta name=\"twitter:site\" content=\"@virtual_dba\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Ian Bjorhovde and Marc Petros\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"3 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/virtual-dba.com\/blog\/resolving-sql0930n-memory-errors-after-upgrade\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/virtual-dba.com\/blog\/resolving-sql0930n-memory-errors-after-upgrade\/\"},\"author\":{\"name\":\"Ian Bjorhovde and Marc Petros\",\"@id\":\"https:\/\/virtual-dba.com\/#\/schema\/person\/dff93201ec19d63cda8591002c9fbd77\"},\"headline\":\"Resolving SQL0930N Memory Errors after an RHEL 7.8 Upgrade\",\"datePublished\":\"2020-09-03T12:47:00+00:00\",\"dateModified\":\"2021-02-11T01:11:04+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/virtual-dba.com\/blog\/resolving-sql0930n-memory-errors-after-upgrade\/\"},\"wordCount\":425,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/virtual-dba.com\/#organization\"},\"image\":{\"@id\":\"https:\/\/virtual-dba.com\/blog\/resolving-sql0930n-memory-errors-after-upgrade\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/virtual-dba.com\/wp-content\/uploads\/Resolving-SQL0930N-Memory-Errors-after-an-RHEL-7.8-Upgrade.jpg\",\"keywords\":[\"db2 error\"],\"articleSection\":[\"Blog\",\"Db2\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/virtual-dba.com\/blog\/resolving-sql0930n-memory-errors-after-upgrade\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/virtual-dba.com\/blog\/resolving-sql0930n-memory-errors-after-upgrade\/\",\"url\":\"https:\/\/virtual-dba.com\/blog\/resolving-sql0930n-memory-errors-after-upgrade\/\",\"name\":\"Resolving SQL0930N Memory Errors after an RHEL 7.8 Upgrade\",\"isPartOf\":{\"@id\":\"https:\/\/virtual-dba.com\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/virtual-dba.com\/blog\/resolving-sql0930n-memory-errors-after-upgrade\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/virtual-dba.com\/blog\/resolving-sql0930n-memory-errors-after-upgrade\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/virtual-dba.com\/wp-content\/uploads\/Resolving-SQL0930N-Memory-Errors-after-an-RHEL-7.8-Upgrade.jpg\",\"datePublished\":\"2020-09-03T12:47:00+00:00\",\"dateModified\":\"2021-02-11T01:11:04+00:00\",\"description\":\"After upgrading to RHEL 7.8, you may run into SQL0930N errors on systems with more than 32Gb memory. Learn how to resolve the issue and get your database running again.\",\"breadcrumb\":{\"@id\":\"https:\/\/virtual-dba.com\/blog\/resolving-sql0930n-memory-errors-after-upgrade\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/virtual-dba.com\/blog\/resolving-sql0930n-memory-errors-after-upgrade\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/virtual-dba.com\/blog\/resolving-sql0930n-memory-errors-after-upgrade\/#primaryimage\",\"url\":\"https:\/\/virtual-dba.com\/wp-content\/uploads\/Resolving-SQL0930N-Memory-Errors-after-an-RHEL-7.8-Upgrade.jpg\",\"contentUrl\":\"https:\/\/virtual-dba.com\/wp-content\/uploads\/Resolving-SQL0930N-Memory-Errors-after-an-RHEL-7.8-Upgrade.jpg\",\"width\":557,\"height\":291,\"caption\":\"Resolving SQL0930N Memory Errors after an RHEL 7.8 Upgrade\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/virtual-dba.com\/blog\/resolving-sql0930n-memory-errors-after-upgrade\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/virtual-dba.com\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Resolving SQL0930N Memory Errors after an RHEL 7.8 Upgrade\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/virtual-dba.com\/#website\",\"url\":\"https:\/\/virtual-dba.com\/\",\"name\":\"Virtual-DBA Remote DBA Services &amp; Support - Certified Database Experts\",\"description\":\"Remote Database Administration\",\"publisher\":{\"@id\":\"https:\/\/virtual-dba.com\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/virtual-dba.com\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/virtual-dba.com\/#organization\",\"name\":\"Virtual-DBA: Remote DBA | Remote Database Administration\",\"alternateName\":\"Virtual-DBA powered by XTIVIA\",\"url\":\"https:\/\/virtual-dba.com\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/virtual-dba.com\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/virtual-dba.com\/wp-content\/uploads\/V-DBA-Database-Services-and-Support-Featured-Logo.jpg\",\"contentUrl\":\"https:\/\/virtual-dba.com\/wp-content\/uploads\/V-DBA-Database-Services-and-Support-Featured-Logo.jpg\",\"width\":557,\"height\":291,\"caption\":\"Virtual-DBA: Remote DBA | Remote Database Administration\"},\"image\":{\"@id\":\"https:\/\/virtual-dba.com\/#\/schema\/logo\/image\/\"},\"sameAs\":[\"https:\/\/x.com\/virtual_dba\",\"https:\/\/www.linkedin.com\/showcase\/36220649\/\",\"https:\/\/www.youtube.com\/channel\/UCx3AIeUQ2ziTLKZSJDZ-SEg\"],\"description\":\"Eliminate database downtime and spiraling costs with XTIVIA\u2019s Virtual-DBA. In today\u2019s always-on business world, gaps in 24x7 on-call DBA support, neglected maintenance and security, or a stretched team struggling with overwhelming workloads can lead to costly disruptions and threaten business continuity. XTIVIA\u2019s Virtual-DBA provides the immediate, expert database administration you need, exactly when you need it, ensuring optimal performance, ironclad security, and significant cost savings without the burden of expanding your in-house team. The goal of Virtual-DBA is to provide a cost-effective solution for organizations seeking to optimize the security, management, maintenance, availability, and performance of their critical business systems, whether self-managed or cloud-managed (e.g., AWS RDS, Azure SQL Database). We accomplish this through a comprehensive remote DBA service offering designed specifically to meet the Oracle\u00ae, DB2\u00ae, Informix\u00ae, MySQL\u2122, PostgreSQL\u00ae, MongoDB\u00ae, MariaDB, and Microsoft SQL Server\u00ae, CockroachDB, Databricks, AWS, and Azure needs of our clients.\",\"email\":\"info@xtivia.com\",\"telephone\":\"8886853101\",\"legalName\":\"XTIVIA, Inc\",\"foundingDate\":\"1992-05-01\",\"numberOfEmployees\":{\"@type\":\"QuantitativeValue\",\"minValue\":\"201\",\"maxValue\":\"500\"}},{\"@type\":\"Person\",\"@id\":\"https:\/\/virtual-dba.com\/#\/schema\/person\/dff93201ec19d63cda8591002c9fbd77\",\"name\":\"Ian Bjorhovde and Marc Petros\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/virtual-dba.com\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/cc79247507b5b0586a5ac5b841e5c4f042b4a9067bdefcf4864cd1b7e7b92f2c?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/cc79247507b5b0586a5ac5b841e5c4f042b4a9067bdefcf4864cd1b7e7b92f2c?s=96&d=mm&r=g\",\"caption\":\"Ian Bjorhovde and Marc Petros\"},\"url\":\"https:\/\/virtual-dba.com\/author\/ian-bjorhovde-and-marc-petros\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Resolving SQL0930N Memory Errors after an RHEL 7.8 Upgrade","description":"After upgrading to RHEL 7.8, you may run into SQL0930N errors on systems with more than 32Gb memory. Learn how to resolve the issue and get your database running again.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/virtual-dba.com\/blog\/resolving-sql0930n-memory-errors-after-upgrade\/","og_locale":"en_US","og_type":"article","og_title":"Resolving SQL0930N Memory Errors after an RHEL 7.8 Upgrade","og_description":"After upgrading to RHEL 7.8, you may run into SQL0930N errors on systems with more than 32Gb memory. Learn how to resolve the issue and get your database running again.","og_url":"https:\/\/virtual-dba.com\/blog\/resolving-sql0930n-memory-errors-after-upgrade\/","og_site_name":"Virtual-DBA Remote DBA Services &amp; Support - Certified Database Experts","article_published_time":"2020-09-03T12:47:00+00:00","article_modified_time":"2021-02-11T01:11:04+00:00","og_image":[{"width":557,"height":291,"url":"https:\/\/virtual-dba.com\/media\/Resolving-SQL0930N-Memory-Errors-after-an-RHEL-7.8-Upgrade.jpg","type":"image\/jpeg"}],"author":"Ian Bjorhovde and Marc Petros","twitter_card":"summary_large_image","twitter_creator":"@virtual_dba","twitter_site":"@virtual_dba","twitter_misc":{"Written by":"Ian Bjorhovde and Marc Petros","Est. reading time":"3 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/virtual-dba.com\/blog\/resolving-sql0930n-memory-errors-after-upgrade\/#article","isPartOf":{"@id":"https:\/\/virtual-dba.com\/blog\/resolving-sql0930n-memory-errors-after-upgrade\/"},"author":{"name":"Ian Bjorhovde and Marc Petros","@id":"https:\/\/virtual-dba.com\/#\/schema\/person\/dff93201ec19d63cda8591002c9fbd77"},"headline":"Resolving SQL0930N Memory Errors after an RHEL 7.8 Upgrade","datePublished":"2020-09-03T12:47:00+00:00","dateModified":"2021-02-11T01:11:04+00:00","mainEntityOfPage":{"@id":"https:\/\/virtual-dba.com\/blog\/resolving-sql0930n-memory-errors-after-upgrade\/"},"wordCount":425,"commentCount":0,"publisher":{"@id":"https:\/\/virtual-dba.com\/#organization"},"image":{"@id":"https:\/\/virtual-dba.com\/blog\/resolving-sql0930n-memory-errors-after-upgrade\/#primaryimage"},"thumbnailUrl":"https:\/\/virtual-dba.com\/wp-content\/uploads\/Resolving-SQL0930N-Memory-Errors-after-an-RHEL-7.8-Upgrade.jpg","keywords":["db2 error"],"articleSection":["Blog","Db2"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/virtual-dba.com\/blog\/resolving-sql0930n-memory-errors-after-upgrade\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/virtual-dba.com\/blog\/resolving-sql0930n-memory-errors-after-upgrade\/","url":"https:\/\/virtual-dba.com\/blog\/resolving-sql0930n-memory-errors-after-upgrade\/","name":"Resolving SQL0930N Memory Errors after an RHEL 7.8 Upgrade","isPartOf":{"@id":"https:\/\/virtual-dba.com\/#website"},"primaryImageOfPage":{"@id":"https:\/\/virtual-dba.com\/blog\/resolving-sql0930n-memory-errors-after-upgrade\/#primaryimage"},"image":{"@id":"https:\/\/virtual-dba.com\/blog\/resolving-sql0930n-memory-errors-after-upgrade\/#primaryimage"},"thumbnailUrl":"https:\/\/virtual-dba.com\/wp-content\/uploads\/Resolving-SQL0930N-Memory-Errors-after-an-RHEL-7.8-Upgrade.jpg","datePublished":"2020-09-03T12:47:00+00:00","dateModified":"2021-02-11T01:11:04+00:00","description":"After upgrading to RHEL 7.8, you may run into SQL0930N errors on systems with more than 32Gb memory. Learn how to resolve the issue and get your database running again.","breadcrumb":{"@id":"https:\/\/virtual-dba.com\/blog\/resolving-sql0930n-memory-errors-after-upgrade\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/virtual-dba.com\/blog\/resolving-sql0930n-memory-errors-after-upgrade\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/virtual-dba.com\/blog\/resolving-sql0930n-memory-errors-after-upgrade\/#primaryimage","url":"https:\/\/virtual-dba.com\/wp-content\/uploads\/Resolving-SQL0930N-Memory-Errors-after-an-RHEL-7.8-Upgrade.jpg","contentUrl":"https:\/\/virtual-dba.com\/wp-content\/uploads\/Resolving-SQL0930N-Memory-Errors-after-an-RHEL-7.8-Upgrade.jpg","width":557,"height":291,"caption":"Resolving SQL0930N Memory Errors after an RHEL 7.8 Upgrade"},{"@type":"BreadcrumbList","@id":"https:\/\/virtual-dba.com\/blog\/resolving-sql0930n-memory-errors-after-upgrade\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/virtual-dba.com\/"},{"@type":"ListItem","position":2,"name":"Resolving SQL0930N Memory Errors after an RHEL 7.8 Upgrade"}]},{"@type":"WebSite","@id":"https:\/\/virtual-dba.com\/#website","url":"https:\/\/virtual-dba.com\/","name":"Virtual-DBA Remote DBA Services &amp; Support - Certified Database Experts","description":"Remote Database Administration","publisher":{"@id":"https:\/\/virtual-dba.com\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/virtual-dba.com\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/virtual-dba.com\/#organization","name":"Virtual-DBA: Remote DBA | Remote Database Administration","alternateName":"Virtual-DBA powered by XTIVIA","url":"https:\/\/virtual-dba.com\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/virtual-dba.com\/#\/schema\/logo\/image\/","url":"https:\/\/virtual-dba.com\/wp-content\/uploads\/V-DBA-Database-Services-and-Support-Featured-Logo.jpg","contentUrl":"https:\/\/virtual-dba.com\/wp-content\/uploads\/V-DBA-Database-Services-and-Support-Featured-Logo.jpg","width":557,"height":291,"caption":"Virtual-DBA: Remote DBA | Remote Database Administration"},"image":{"@id":"https:\/\/virtual-dba.com\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/x.com\/virtual_dba","https:\/\/www.linkedin.com\/showcase\/36220649\/","https:\/\/www.youtube.com\/channel\/UCx3AIeUQ2ziTLKZSJDZ-SEg"],"description":"Eliminate database downtime and spiraling costs with XTIVIA\u2019s Virtual-DBA. In today\u2019s always-on business world, gaps in 24x7 on-call DBA support, neglected maintenance and security, or a stretched team struggling with overwhelming workloads can lead to costly disruptions and threaten business continuity. XTIVIA\u2019s Virtual-DBA provides the immediate, expert database administration you need, exactly when you need it, ensuring optimal performance, ironclad security, and significant cost savings without the burden of expanding your in-house team. The goal of Virtual-DBA is to provide a cost-effective solution for organizations seeking to optimize the security, management, maintenance, availability, and performance of their critical business systems, whether self-managed or cloud-managed (e.g., AWS RDS, Azure SQL Database). We accomplish this through a comprehensive remote DBA service offering designed specifically to meet the Oracle\u00ae, DB2\u00ae, Informix\u00ae, MySQL\u2122, PostgreSQL\u00ae, MongoDB\u00ae, MariaDB, and Microsoft SQL Server\u00ae, CockroachDB, Databricks, AWS, and Azure needs of our clients.","email":"info@xtivia.com","telephone":"8886853101","legalName":"XTIVIA, Inc","foundingDate":"1992-05-01","numberOfEmployees":{"@type":"QuantitativeValue","minValue":"201","maxValue":"500"}},{"@type":"Person","@id":"https:\/\/virtual-dba.com\/#\/schema\/person\/dff93201ec19d63cda8591002c9fbd77","name":"Ian Bjorhovde and Marc Petros","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/virtual-dba.com\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/cc79247507b5b0586a5ac5b841e5c4f042b4a9067bdefcf4864cd1b7e7b92f2c?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/cc79247507b5b0586a5ac5b841e5c4f042b4a9067bdefcf4864cd1b7e7b92f2c?s=96&d=mm&r=g","caption":"Ian Bjorhovde and Marc Petros"},"url":"https:\/\/virtual-dba.com\/author\/ian-bjorhovde-and-marc-petros\/"}]}},"_links":{"self":[{"href":"https:\/\/virtual-dba.com\/wp-json\/wp\/v2\/posts\/37816","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/virtual-dba.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/virtual-dba.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/virtual-dba.com\/wp-json\/wp\/v2\/users\/44"}],"replies":[{"embeddable":true,"href":"https:\/\/virtual-dba.com\/wp-json\/wp\/v2\/comments?post=37816"}],"version-history":[{"count":0,"href":"https:\/\/virtual-dba.com\/wp-json\/wp\/v2\/posts\/37816\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/virtual-dba.com\/wp-json\/wp\/v2\/media\/37818"}],"wp:attachment":[{"href":"https:\/\/virtual-dba.com\/wp-json\/wp\/v2\/media?parent=37816"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/virtual-dba.com\/wp-json\/wp\/v2\/categories?post=37816"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/virtual-dba.com\/wp-json\/wp\/v2\/tags?post=37816"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}