{"id":43699,"date":"2026-03-31T22:32:30","date_gmt":"2026-03-31T20:32:30","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/?p=43699"},"modified":"2026-03-31T22:32:32","modified_gmt":"2026-03-31T20:32:32","slug":"mysql-metadata-store-service-not-able-to-start-on-an-oda","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/mysql-metadata-store-service-not-able-to-start-on-an-oda\/","title":{"rendered":"MySQL Metadata Store service not able to start on an ODA"},"content":{"rendered":"\n<p>I was recently doing some consulting on some ODA at one of our customers, and I faced an issue with the DCS Agent and the MySQL Metadata Store. In this blog, I will show you the problem and how I could resolved it.<\/p>\n\n\n\n<!--more-->\n\n\n\n<h3>Problem description<\/h3>\n\n\n\n<p>On an Oracle Database Appliance, the DCS agent is the software providing the full automation to manage the appliance. It will have no impact on the well working of the databases but is mandatory to manage the appliance (patching, create dbhome, create database and any appliance resources). The DCS agent will perform various operations on the appliance, such as provisioning, database lifecycle management, backup and recovery, and storage management. The DCS Agent will use a MySQL database to store the metadata. In order for the DCS Agent to work, the MySQL database needs to be up and running.<\/p>\n\n\n\n<p>On the node 0 of an ODA X9-2-HA, where I was preparing the next database patching operation, I wanted to run some cleanup.<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1]\">\n[root@ODA-HA_node0 ~]# odacli cleanup-patchrepo -comp DB,GI -v 19.20.0.0.0\nDCS-10009:Failed to create new service job report.\n<\/pre>\n<\/br>\n\n\n\n<p>For which I could get a DCS failure.<\/p>\n\n\n\n<p>I checked the job and realised that an ODA cleaning job where still in running status for about 3 months&#8230;<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1,10]\">\n[root@ODA-HA_node0 ~]# odacli list-jobs\n\nID                                       Description                                                                 Created                             Status\n---------------------------------------- --------------------------------------------------------------------------- ----------------------------------- ----------------\n80f2bfbc-a02e-47bb-b57c-754d3d6d3d3a     Server Patching                                                             2025-11-12 08:00:14 CET             Success\n2e36d676-f175-402d-a7e4-735b4eb965de     Patch pre-checks for [STORAGE]                                              2025-11-12 08:58:19 CET             Success\n...\nc4611880-fdc8-44fd-90a5-c2dd27d12f7c     Auto purge job data                                                         2025-12-09 03:59:48 CET             Success\ned09f270-5eff-4141-9b7b-51a2e5d30e32     Auto purge job data                                                         2025-12-10 03:59:50 CET             Success\naecd8ca5-44fb-4e2c-af2b-0e42e954381a     Auto purge job data                                                         2025-12-11 03:59:52 CET             Running\n\n[root@ODA-HA_node0 ~]#\n<\/pre>\n<\/br>\n\n\n\n<h3>Troubleshooting<\/h3>\n\n\n\n<p>I restarted the DCS agent.<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1,3,5]\">\n[root@ODA-HA_node0 ~]# systemctl stop initdcsagent\n\n[root@ODA-HA_node0 ~]# systemctl start initdcsagent\n\n[root@ODA-HA_node0 ~]# systemctl status initdcsagent\n\u25cf initdcsagent.service - Oracle dcs-agent startup\n   Loaded: loaded (\/etc\/systemd\/system\/initdcsagent.service; enabled; vendor preset: disabled)\n   Active: active (running) since Wed 2026-03-18 14:35:41 CET; 2s ago\n Main PID: 92038 (sh)\n    Tasks: 96 (limit: 79998)\n   Memory: 331.7M\n   CGroup: \/system.slice\/initdcsagent.service\n           \u251c\u250092038 \/bin\/sh -c . \/opt\/oracle\/dcs\/bin\/setupJreAgent.sh;LD_LIBRARY_PATH=\/opt\/oracle\/rhp\/lib:$JRE_HOME\/lib\/amd64:\/usr\/lib64:\/lib64:\/lib:\/usr\/lib $JAVA -Xms128m -Xmx256m -XX:MetaspaceSize=128m -XX:MaxMetaspaceSize=256m -XX:+DisableExplicitGC -XX:ParallelGCThreads=4 -XX:+PrintGCDetails -XX:+PrintHeapAtGC -XX:+PrintTenuringDistribution -XX:+PrintGCTimeStamps -XX:+PrintGCDateStamps -Xloggc:\/opt\/oracle\/dcs\/log\/gc-dcs-agent-%t-%p.log -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFi&gt;\n           \u2514\u250092039 \/opt\/oracle\/dcs\/java\/1.8.0_441\/bin\/java -Xms128m -Xmx256m -XX:MetaspaceSize=128m -XX:MaxMetaspaceSize=256m -XX:+DisableExplicitGC -XX:ParallelGCThreads=4 -XX:+PrintGCDetails -XX:+PrintHeapAtGC -XX:+PrintTenuringDistribution -XX:+PrintGCTimeStamps -XX:+PrintGCDateStamps -Xloggc:\/opt\/oracle\/dcs\/log\/gc-dcs-agent-%t-%p.log -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=10 -XX:GCLogFileSize=10M -Doracle.security.jps.config=\/opt\/oracle\/dcs\/agent\/jps-config.xml -Dio.nett&gt;\n\nMar 18 14:35:41 ODA-HA_node0 systemd[1]: Started Oracle dcs-agent startup.\n[root@ODA-HA_node0 ~]# odacli list-jobs | tail -n3\n<\/pre>\n<\/br>\n\n\n\n<p>Which did not help. In the DCS Agent log I could find some errors with HAMI. Oracle HAMI is the Oracle High Availability Metadata Infrastructure service providing distributed services required by DCS including locking and synchronizing configuration details in the cluster.<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1]\">\n[root@ODA-HA_node0 log]# view dcs-agent-infra.log\n...\n...\n...\n2026-03-18 14:59:37,776 DEBUG [DcsInfraProvisioningThread] [] c.o.d.i.h.c.CommandExecutor: Going to execute command '\/opt\/oracle\/dcs\/hami\/bin\/hamictl.sh ssh-equiv --ensemble ODA_DCS --hosts ODA-HA_node0-priv,ODA-HA_node1-priv --json'\n2026-03-18 14:59:38,014 DEBUG [DcsInfraProvisioningThread] [] c.o.d.i.h.c.CommandExecutor: Got result from execution of '\/opt\/oracle\/dcs\/hami\/bin\/hamictl.sh ssh-equiv --ensemble ODA_DCS --hosts ODA-HA_node0-priv,ODA-HA_node1-priv --json':\n - RC:     1\n - OUTPUT: \/opt\/oracle\/dcs\/oda-python3\/lib\/python3.12\/getpass.py:91: GetPassWarning: Can not control echo on the terminal.\nWarning: Password input may be echoed.\nhamictl_oda_dcs's password: *********\n{\"operation\": \"ssh-equiv\", \"result\": \"FAILED\", \"message\": \"Invalid password\"}\n\n2026-03-18 14:59:38,015 ERROR [DcsInfraProvisioningThread] [] c.o.d.a.i.DcsInfraProvisioningThread: Could not provision DCS infrastructure\ncom.oracle.dcs.infra.hams.ctl.HamiCtl$HamiCtlException: Invalid password\n<\/pre>\n<\/br>\n\n\n\n<p>I decided to restart MySQL service.<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1,3]\">\n[root@ODA-HA_node0 ~]# systemctl stop oda-mysql\n\n[root@ODA-HA_node0 ~]# systemctl start oda-mysql\nJob for oda-mysql.service failed because the control process exited with error code.\nSee \"systemctl status oda-mysql.service\" and \"journalctl -xe\" for details.\n<\/pre>\n<\/br>\n\n\n\n\n<p>Which failed&#8230;<\/p>\n\n\n\n<p>Checking the logs:<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1,4,5]\">\n[root@ODA-HA_node0 ~]# journalctl -xe\n...\n-- Unit oda-mysql.service has begun starting up.\nMar 31 09:23:10 ODA-HA_node0 systemd[90052]: oda-mysql.service: Failed to execute command: Permission denied\nMar 31 09:23:10 ODA-HA_node0 systemd[90052]: oda-mysql.service: Failed at step EXEC spawning \/opt\/oracle\/dcs\/mysql\/bin\/mysqld: Permission denied\n<\/pre>\n<\/br>\n\n\n\n<p>I could see that it was complaining about permissions.<\/p>\n\n\n\n<p>I checked the permissions on the MySQL binary:<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1]\">\n[root@ODA-HA_node0 ~]# ls -ltrh \/opt\/oracle\/dcs\/mysql\/bin\/mysqld\n-rwxr-x--- 1 odamysql odamysql 338M Mar 26 16:55 \/opt\/oracle\/dcs\/mysql\/bin\/mysqld\n[root@ODA-HA_node0 ~]#\n<\/pre>\n<\/br>\n\n\n\n<p>And that one was ok. The linux user starting MySQL, odamysql, was having the right permissions.<\/p>\n\n\n\n<p>I then checked all permissions including the directories:<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1,2]\">\n[root@ODA-HA_node0 log]# ls -ld \/opt \/opt\/oracle \/opt\/oracle\/dcs \/opt\/oracle\/dcs\/mysql \/opt\/oracle\/dcs\/mysql\/bin\ndrwxrwx---  11 root     oinstall 4096 Nov 21 13:58 \/opt\ndrwxr-xr-x.  9 root     root     4096 Nov 14 16:31 \/opt\/oracle\ndrwxr-xr-x. 30 root     root     4096 Nov 14 12:40 \/opt\/oracle\/dcs\ndrwxr-xr-x. 13 root     root     4096 Nov 14 09:10 \/opt\/oracle\/dcs\/mysql\ndrwxr-x---.  2 odamysql odamysql 4096 Mar 26 16:55 \/opt\/oracle\/dcs\/mysql\/bin\n[root@ODA-HA_node0 log]#\n<\/pre>\n<\/br>\n\n\n\n<p>And  I could see that there were wrong on the \/opt directory&#8230; The odamysql directory is not able to enter and read in the \/opt directory, as it does not belong to the group and there is no permissions on the other users&#8230;<\/p>\n\n\n\n<p>I checked on a valid ODA and as expected the permissions should be:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>drwxr-xr-x. 11 root     root     4096 Mar 18 10:02 \/opt<\/code><\/pre>\n\n\n\n<p>So this is mainly due to an human mistake&#8230;<\/p>\n\n\n\n<h3>Resolution<\/h3>\n\n\n\n<p>I first checked and could confirm the issue only affect the \/opt directory itself.<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1,4]\">\n[root@ODA-HA_node0 opt]# pwd\n\/opt\n\n[root@ODA-HA_node0 opt]# ls -ltrh\ntotal 48K\ndrwxr-xr-x.  3 root root     4.0K Sep 17  2024 lsi\ndrwxr-xr-x   2 root root     4.0K Jan 15  2025 oracle.ahf\ndrwx------.  2 root root      16K Nov 11 15:42 lost+found\ndrwxr-xr-x.  4 root root     4.0K Nov 11 16:32 MegaRAID\ndrwxr-xr-x   3 root root     4.0K Nov 12 10:20 ORCLfmap\ndrwxr-xr-x   5 root root     4.0K Nov 12 13:36 odabr\ndrwxr-xr-x.  9 root root     4.0K Nov 14 16:31 oracle\ndrwxrwx---  16 root oinstall 4.0K Feb 16 11:19 commvault\ndrwx------  11 root root     4.0K Mar 30 02:08 splunkforwarder\n[root@ODA-HA_node0 opt]#\n<\/pre>\n<\/br>\n\n\n\n<p>I change the permissions for other users.<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1,3,4]\">\n[root@ODA-HA_node0 \/]# chmod o+rx \/opt\n\n[root@ODA-HA_node0 \/]# ls -ld \/opt \/opt\/oracle \/opt\/oracle\/dcs \/opt\/oracle\/dcs\/mysql \/opt\/oracle\/dcs\/mysql\/bin\ndrwxrwxr-x  11 root     oinstall 4096 Nov 21 13:58 \/opt\ndrwxr-xr-x.  9 root     root     4096 Nov 14 16:31 \/opt\/oracle\ndrwxr-xr-x. 30 root     root     4096 Nov 14 12:40 \/opt\/oracle\/dcs\ndrwxr-xr-x. 13 root     root     4096 Nov 14 09:10 \/opt\/oracle\/dcs\/mysql\ndrwxr-x---.  2 odamysql odamysql 4096 Mar 26 16:55 \/opt\/oracle\/dcs\/mysql\/bin\n[root@ODA-HA_node0 \/]#\n<\/pre>\n<\/br>\n\n\n\n\n<p>And I could successfully start the MySQL service.<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1,3,6]\">\n[root@ODA-HA_node0 \/]# systemctl start oda-mysql\n\n[root@ODA-HA_node0 \/]# systemctl status oda-mysql\n\u25cf oda-mysql.service - MySQL Server for ODA\n   Loaded: loaded (\/etc\/systemd\/system\/oda-mysql.service; enabled; vendor preset: disabled)\n   Active: active (running) since Tue 2026-03-31 09:55:48 CEST; 6s ago\n     Docs: man:mysqld(8)\n           http:\/\/dev.mysql.com\/doc\/refman\/en\/using-systemd.html\n Main PID: 55837 (mysqld)\n   Status: \"Server is operational\"\n    Tasks: 33 (limit: 79998)\n   Memory: 423.5M\n   CGroup: \/system.slice\/oda-mysql.service\n           \u2514\u250055837 \/opt\/oracle\/dcs\/mysql\/bin\/mysqld --defaults-file=\/opt\/oracle\/dcs\/mysql\/etc\/mysqldb.cnf --skip-mysqlx\n\nMar 31 09:55:48 ODA-HA_node0 systemd[1]: Starting MySQL Server for ODA...\nMar 31 09:55:48 ODA-HA_node0 systemd[1]: Started MySQL Server for ODA.\n[root@ODA-HA_node0 \/]#\n<\/pre>\n<\/br>\n\n\n\n<p>And I could successfully start the DCS Agent.<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1,18,20,23]\">\n[root@ODA-HA_node0 \/]# systemctl status initdcsagent\n\u25cf initdcsagent.service - Oracle dcs-agent startup\n   Loaded: loaded (\/etc\/systemd\/system\/initdcsagent.service; enabled; vendor preset: disabled)\n   Active: inactive (dead) since Wed 2026-03-18 15:22:48 CET; 1 weeks 5 days ago\n Main PID: 84546 (code=killed, signal=TERM)\n\nMar 19 16:18:04 ODA-HA_node0 systemd[1]: Dependency failed for Oracle dcs-agent startup.\nMar 19 16:18:04 ODA-HA_node0 systemd[1]: initdcsagent.service: Job initdcsagent.service\/start failed with result 'dependency'.\nMar 24 13:38:38 ODA-HA_node0 systemd[1]: Dependency failed for Oracle dcs-agent startup.\nMar 24 13:38:38 ODA-HA_node0 systemd[1]: initdcsagent.service: Job initdcsagent.service\/start failed with result 'dependency'.\nMar 25 09:46:35 ODA-HA_node0 systemd[1]: Dependency failed for Oracle dcs-agent startup.\nMar 25 09:46:35 ODA-HA_node0 systemd[1]: initdcsagent.service: Job initdcsagent.service\/start failed with result 'dependency'.\nMar 26 11:06:50 ODA-HA_node0 systemd[1]: Dependency failed for Oracle dcs-agent startup.\nMar 26 11:06:50 ODA-HA_node0 systemd[1]: initdcsagent.service: Job initdcsagent.service\/start failed with result 'dependency'.\nMar 30 16:07:15 ODA-HA_node0 systemd[1]: Dependency failed for Oracle dcs-agent startup.\nMar 30 16:07:15 ODA-HA_node0 systemd[1]: initdcsagent.service: Job initdcsagent.service\/start failed with result 'dependency'.\n\n[root@ODA-HA_node0 \/]# systemctl start initdcsagent\n\n[root@ODA-HA_node0 \/]# systemctl status initdcsagent\n\u25cf initdcsagent.service - Oracle dcs-agent startup\n   Loaded: loaded (\/etc\/systemd\/system\/initdcsagent.service; enabled; vendor preset: disabled)\n   Active: active (running) since Tue 2026-03-31 09:57:34 CEST; 1s ago\n Main PID: 59253 (sh)\n    Tasks: 96 (limit: 79998)\n   Memory: 270.0M\n   CGroup: \/system.slice\/initdcsagent.service\n           \u251c\u250059253 \/bin\/sh -c . \/opt\/oracle\/dcs\/bin\/setupJreAgent.sh;LD_LIBRARY_PATH=\/opt\/oracle\/rhp\/lib:$JRE_HOME\/lib\/amd64:\/usr\/lib64:\/lib64:\/lib:\/usr\/lib $JAVA -Xms128m -Xmx256m -XX:MetaspaceSize=128m -XX:MaxMetaspaceSize=256m -XX:+DisableExplicitGC -XX:ParallelGCThreads=4 -XX:+PrintGCDetails -XX:+PrintHeapAtGC -XX:+PrintTenuringDistribution -XX:+PrintGCTimeStamps -XX:+PrintGCDateStamps -Xloggc:\/opt\/oracle\/dcs\/log\/gc-dcs-agent-%t-%p.log -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFi&gt;\n           \u2514\u250059254 \/opt\/oracle\/dcs\/java\/1.8.0_441\/bin\/java -Xms128m -Xmx256m -XX:MetaspaceSize=128m -XX:MaxMetaspaceSize=256m -XX:+DisableExplicitGC -XX:ParallelGCThreads=4 -XX:+PrintGCDetails -XX:+PrintHeapAtGC -XX:+PrintTenuringDistribution -XX:+PrintGCTimeStamps -XX:+PrintGCDateStamps -Xloggc:\/opt\/oracle\/dcs\/log\/gc-dcs-agent-%t-%p.log -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=10 -XX:GCLogFileSize=10M -Doracle.security.jps.config=\/opt\/oracle\/dcs\/agent\/jps-config.xml -Dio.nett&gt;\n\nMar 31 09:57:34 ODA-HA_node0 systemd[1]: Started Oracle dcs-agent startup.\n[root@ODA-HA_node0 \/]#\n<\/pre>\n<\/br>\n\n\n\n<p>And I could successfully run the cleanup:<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1,15,21]\">\n[root@ODA-HA_node0 ~]# odacli cleanup-patchrepo -comp DB,GI -v 19.20.0.0.0\n{\n  \"jobId\" : \"08b395be-ae5a-4d6f-8e5d-1c0fa232f672\",\n  \"status\" : \"Created\",\n  \"message\" : \"\",\n  \"reports\" : [ ],\n  \"createTimestamp\" : \"March 31, 2026 11:21:58 CEST\",\n  \"resourceList\" : [ ],\n  \"description\" : \"Cleanup patchrepos\",\n  \"updatedTime\" : \"March 31, 2026 11:21:58 CEST\",\n  \"jobType\" : null,\n  \"cpsMetadata\" : null\n}\n\n[root@ODA-HA_node0 ~]# odacli describe-job -i 08b395be-ae5a-4d6f-8e5d-1c0fa232f672\n\nJob details\n----------------------------------------------------------------\n                     ID:  08b395be-ae5a-4d6f-8e5d-1c0fa232f672\n            Description:  Cleanup patchrepos\n                 Status:  Success\n                Created:  March 31, 2026 11:21:58 CEST\n                Message:\n\nTask Name                                Node Name                 Start Time                               End Time                                 Status\n---------------------------------------- ------------------------- ---------------------------------------- ---------------------------------------- ----------------\nCleanup Repository                       ODA-HA_node1                 March 31, 2026 11:21:58 CEST             March 31, 2026 11:21:59 CEST             Success\nCleanup old ASR rpm                      ODA-HA_node0                 March 31, 2026 11:21:59 CEST             March 31, 2026 11:21:59 CEST             Success\n\n[root@ODA-HA_node0 ~]#\n<\/pre>\n<\/br>\n\n\n\n<p>Finally, I have also changed the group for \/opt accordingly to root group.<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1,3,4]\">\n[root@ODA-HA_node0 \/]# chgrp root \/opt\n\n[root@ODA-HA_node0 \/]# ls -ld \/opt \/opt\/oracle \/opt\/oracle\/dcs \/opt\/oracle\/dcs\/mysql \/opt\/oracle\/dcs\/mysql\/bin\ndrwxrwxr-x  11 root     root     4096 Nov 21 13:58 \/opt\ndrwxr-xr-x.  9 root     root     4096 Nov 14 16:31 \/opt\/oracle\ndrwxr-xr-x. 30 root     root     4096 Nov 14 12:40 \/opt\/oracle\/dcs\ndrwxr-xr-x. 13 root     root     4096 Nov 14 09:10 \/opt\/oracle\/dcs\/mysql\ndrwxr-x---.  2 odamysql odamysql 4096 Mar 26 16:55 \/opt\/oracle\/dcs\/mysql\/bin\n[root@ODA-HA_node0 \/]#\n<\/pre>\n<\/br>\n\n\n\n<h3>To wrap up&#8230;<\/h3>\n\n\n\n<p>DCS Agent and MySQL database will have no effect on the well working of your databases, but if they are not working you are not able to manage your appliance any more. Here, wrong permissions (for sure a human mistake) had sad effects on appliance software. Solving the permissions issue resolved my problem.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>I was recently doing some consulting on some ODA at one of our customers, and I faced an issue with the DCS Agent and the MySQL Metadata Store. In this blog, I will show you the problem and how I could resolved it.<\/p>\n","protected":false},"author":48,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[59],"tags":[3947,2567,96],"type_dbi":[],"class_list":["post-43699","post","type-post","status-publish","format-standard","hentry","category-oracle","tag-mysql-metadata-store","tag-oda-2","tag-oracle"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v27.2 (Yoast SEO v27.2) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>MySQL Metadata Store service not able to start on an ODA - dbi Blog<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.dbi-services.com\/blog\/mysql-metadata-store-service-not-able-to-start-on-an-oda\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"MySQL Metadata Store service not able to start on an ODA\" \/>\n<meta property=\"og:description\" content=\"I was recently doing some consulting on some ODA at one of our customers, and I faced an issue with the DCS Agent and the MySQL Metadata Store. In this blog, I will show you the problem and how I could resolved it.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/mysql-metadata-store-service-not-able-to-start-on-an-oda\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2026-03-31T20:32:30+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-03-31T20:32:32+00:00\" \/>\n<meta name=\"author\" content=\"Marc Wagner\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Marc Wagner\" \/>\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:\/\/www.dbi-services.com\/blog\/mysql-metadata-store-service-not-able-to-start-on-an-oda\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/mysql-metadata-store-service-not-able-to-start-on-an-oda\/\"},\"author\":{\"name\":\"Marc Wagner\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/225d9884b8467ead9a872823acb14628\"},\"headline\":\"MySQL Metadata Store service not able to start on an ODA\",\"datePublished\":\"2026-03-31T20:32:30+00:00\",\"dateModified\":\"2026-03-31T20:32:32+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/mysql-metadata-store-service-not-able-to-start-on-an-oda\/\"},\"wordCount\":483,\"commentCount\":0,\"keywords\":[\"MySQL Metadata Store\",\"oda\",\"Oracle\"],\"articleSection\":[\"Oracle\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/mysql-metadata-store-service-not-able-to-start-on-an-oda\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/mysql-metadata-store-service-not-able-to-start-on-an-oda\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/mysql-metadata-store-service-not-able-to-start-on-an-oda\/\",\"name\":\"MySQL Metadata Store service not able to start on an ODA - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"datePublished\":\"2026-03-31T20:32:30+00:00\",\"dateModified\":\"2026-03-31T20:32:32+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/225d9884b8467ead9a872823acb14628\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/mysql-metadata-store-service-not-able-to-start-on-an-oda\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/mysql-metadata-store-service-not-able-to-start-on-an-oda\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/mysql-metadata-store-service-not-able-to-start-on-an-oda\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"MySQL Metadata Store service not able to start on an ODA\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/\",\"name\":\"dbi Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/225d9884b8467ead9a872823acb14628\",\"name\":\"Marc Wagner\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/secure.gravatar.com\/avatar\/a873cc6e7fbdbbcbdbcaf5dbded14ad9a77b2ec2c3e03b4d724ed33d35d5f328?s=96&d=mm&r=g\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/a873cc6e7fbdbbcbdbcaf5dbded14ad9a77b2ec2c3e03b4d724ed33d35d5f328?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/a873cc6e7fbdbbcbdbcaf5dbded14ad9a77b2ec2c3e03b4d724ed33d35d5f328?s=96&d=mm&r=g\",\"caption\":\"Marc Wagner\"},\"url\":\"https:\/\/www.dbi-services.com\/blog\/author\/marc-wagner\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"MySQL Metadata Store service not able to start on an ODA - dbi Blog","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:\/\/www.dbi-services.com\/blog\/mysql-metadata-store-service-not-able-to-start-on-an-oda\/","og_locale":"en_US","og_type":"article","og_title":"MySQL Metadata Store service not able to start on an ODA","og_description":"I was recently doing some consulting on some ODA at one of our customers, and I faced an issue with the DCS Agent and the MySQL Metadata Store. In this blog, I will show you the problem and how I could resolved it.","og_url":"https:\/\/www.dbi-services.com\/blog\/mysql-metadata-store-service-not-able-to-start-on-an-oda\/","og_site_name":"dbi Blog","article_published_time":"2026-03-31T20:32:30+00:00","article_modified_time":"2026-03-31T20:32:32+00:00","author":"Marc Wagner","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Marc Wagner","Est. reading time":"3 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/mysql-metadata-store-service-not-able-to-start-on-an-oda\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/mysql-metadata-store-service-not-able-to-start-on-an-oda\/"},"author":{"name":"Marc Wagner","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/225d9884b8467ead9a872823acb14628"},"headline":"MySQL Metadata Store service not able to start on an ODA","datePublished":"2026-03-31T20:32:30+00:00","dateModified":"2026-03-31T20:32:32+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/mysql-metadata-store-service-not-able-to-start-on-an-oda\/"},"wordCount":483,"commentCount":0,"keywords":["MySQL Metadata Store","oda","Oracle"],"articleSection":["Oracle"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/mysql-metadata-store-service-not-able-to-start-on-an-oda\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/mysql-metadata-store-service-not-able-to-start-on-an-oda\/","url":"https:\/\/www.dbi-services.com\/blog\/mysql-metadata-store-service-not-able-to-start-on-an-oda\/","name":"MySQL Metadata Store service not able to start on an ODA - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2026-03-31T20:32:30+00:00","dateModified":"2026-03-31T20:32:32+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/225d9884b8467ead9a872823acb14628"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/mysql-metadata-store-service-not-able-to-start-on-an-oda\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/mysql-metadata-store-service-not-able-to-start-on-an-oda\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/mysql-metadata-store-service-not-able-to-start-on-an-oda\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"MySQL Metadata Store service not able to start on an ODA"}]},{"@type":"WebSite","@id":"https:\/\/www.dbi-services.com\/blog\/#website","url":"https:\/\/www.dbi-services.com\/blog\/","name":"dbi Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/225d9884b8467ead9a872823acb14628","name":"Marc Wagner","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/a873cc6e7fbdbbcbdbcaf5dbded14ad9a77b2ec2c3e03b4d724ed33d35d5f328?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/a873cc6e7fbdbbcbdbcaf5dbded14ad9a77b2ec2c3e03b4d724ed33d35d5f328?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/a873cc6e7fbdbbcbdbcaf5dbded14ad9a77b2ec2c3e03b4d724ed33d35d5f328?s=96&d=mm&r=g","caption":"Marc Wagner"},"url":"https:\/\/www.dbi-services.com\/blog\/author\/marc-wagner\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/43699","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/users\/48"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=43699"}],"version-history":[{"count":11,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/43699\/revisions"}],"predecessor-version":[{"id":43710,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/43699\/revisions\/43710"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=43699"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=43699"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=43699"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=43699"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}