{"id":12802,"date":"2019-09-13T08:27:43","date_gmt":"2019-09-13T06:27:43","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/moving-oracle-database-to-new-home-on-oda\/"},"modified":"2019-09-13T08:27:43","modified_gmt":"2019-09-13T06:27:43","slug":"moving-oracle-database-to-new-home-on-oda","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/moving-oracle-database-to-new-home-on-oda\/","title":{"rendered":"Moving oracle database to new home on ODA"},"content":{"rendered":"<p>Moving database to new ORACLE_HOME is a common dba task. Performing this task on an ODA will need an additional step knowing ODA Lite is using an internal Derby database for the metadata. ODA HA will not be a problem here, knowing we do not have any Derby database. Through this blog I would like to give you some guidance and work around to move database to a new home (of same major release). In this example we will move a database named mydb, with db_unique_name set to mydb_site1 from OraDB11204_home1 to OraDB11204_home2.<\/p>\n<p>I would like to highlight that the following blog is showing the procedure to move a database between ORACLE_HOME of same major release. The new ORACLE_HOME would for example run additionnal patches. An upgrade between Oracle major release is not possible following this procedure, and you would need to use the appropriate odacli commands (odacli upgrade-database) in that case.<br \/>\nLast but not least, I also would like to strongly advise that updating manually the ODA repository should only be peformed after getting Oracle support guidance and agreement to do so. Neither the author (that&#8217;s me \ud83d\ude42 ) nor dbi services \ud83d\ude09 would be responsible for any issue or consequence following commands described in this blog. This would be your own responsability. \ud83d\ude09<\/p>\n<p>I&#8217;m running ODA release 12.2.1.3. The database version used in this exemple is an Oracle 11g, but would work exactly the same for any other version like Oracle 12c databases.<\/p>\n<p><!--more--><\/p>\n<h3>Curent database information<\/h3>\n<p>Let&#8217;s first get information on which dbhome our mydb database is running.<\/p>\n<p>List dbhomes :<br \/>\n<code>[root@oda tmp]# odacli list-dbhomes<br \/>\nID                                       Name                 DB Version                               Home Location                                 Status<br \/>\n---------------------------------------- -------------------- ---------------------------------------- --------------------------------------------- ----------<br \/>\ned0a6667-0d70-4113-8a5e-3afaf1976fc2     OraDB12102_home1     12.1.0.2.171017 (26914423, 26717470)     \/u01\/app\/oracle\/product\/12.1.0.2\/dbhome_1     Configured<br \/>\n89f6687e-f575-45fc-91ef-5521374c54c0     OraDB11204_home1     11.2.0.4.171017 (26609929, 26392168)     \/u01\/app\/oracle\/product\/11.2.0.4\/dbhome_1     Configured<br \/>\n8c6bc663-b064-445b-8a14-b7c46df9d1da     OraDB12102_home3     12.1.0.2.171017 (26914423, 26717470)     \/u01\/app\/oracle\/product\/12.1.0.2\/dbhome_3     Configured<br \/>\n9783fd89-f035-4d1a-aaaf-f1cdb09c6ea8     OraDB11204_home2     11.2.0.4.171017 (26609929, 26392168)     \/u01\/app\/oracle\/product\/11.2.0.4\/dbhome_2     Configured<\/code><\/p>\n<p>List database information :<br \/>\n<code>[root@oda tmp]# odacli list-databases<br \/>\nID                                       DB Name    DB Type  DB Version           CDB        Class    Shape    Storage    Status        DbHomeID<br \/>\n---------------------------------------- ---------- -------- -------------------- ---------- -------- -------- ---------- ------------ ----------------------------------------<br \/>\nf38f3a6c-987c-4e11-8cfa-af5cb66ff4e3     mydb     Si       11.2.0.4             false      OLTP     Odb1     ACFS       Configured   89f6687e-f575-45fc-91ef-5521374c54c0<\/code><\/p>\n<p>Our database is running on OraDB11204_home1 Oracle home.<\/p>\n<h3>Moving database to new home<\/h3>\n<p>Let&#8217;s move mydb database on OraDB11204_home2.<\/p>\n<ol>\n<p>The process to link the database to a new home is quite simple and would just be easily done by :<\/p>\n<li>Moving the instance parameter file and password file to the new oracle home<\/li>\n<li>Updating the listener configuration by inserting the new oracle home in case static registration is used<\/li>\n<li>Changing grid cluster information using srvctl command<\/li>\n<\/ol>\n<p>First we need to stop the database :<br \/>\n<code>oracle@oda:\/u01\/app\/oracle\/product\/11.2.0.4\/dbhome_2\/dbs\/ [mydb] srvctl stop database -d mydb_site1<\/code><\/p>\n<p>We can list the current grid configuration :<br \/>\n<code>oracle@oda:\/u01\/app\/oracle\/product\/11.2.0.4\/dbhome_2\/dbs\/ [mydb] srvctl config database -d mydb_site1<br \/>\nDatabase unique name: mydb_site1<br \/>\nDatabase name: mydb<br \/>\nOracle home: \/u01\/app\/oracle\/product\/11.2.0.4\/dbhome_1<br \/>\nOracle user: oracle<br \/>\nSpfile: \/u02\/app\/oracle\/oradata\/mydb_site1\/dbs\/spfilemydb.ora<br \/>\nDomain:<br \/>\nStart options: open<br \/>\nStop options: immediate<br \/>\nDatabase role: PRIMARY<br \/>\nManagement policy: AUTOMATIC<br \/>\nServer pools: mydb_site1<br \/>\nDatabase instance: mydb<br \/>\nDisk Groups:<br \/>\nMount point paths: \/u02\/app\/oracle\/oradata\/mydb_site1,\/u03\/app\/oracle\/<br \/>\nServices:<br \/>\nType: SINGLE<br \/>\nDatabase is administrator managed<\/code><\/p>\n<p>As we can see the grid cluster database is referring the current dbhome.  Let&#8217;s update it to have it linked to new oracle home :<br \/>\n<code>oracle@oda:\/u01\/app\/oracle\/product\/11.2.0.4\/dbhome_2\/dbs\/ [mydb] srvctl modify database -d mydb_site1 -o \/u01\/app\/oracle\/product\/11.2.0.4\/dbhome_2<\/code><\/p>\n<p>Note that if you are using Oracle 12c, the srvctl command option might differ. Use :<br \/>\n-db for database name<br \/>\n-oraclehome for database oracle home<br \/>\n-pwfile for password file<\/p>\n<p>With Oracle 12c database you will have to specify the change for the password file as well in case it is stored in $ORACLE_HOME\/dbs folder.<\/p>\n<p>We can check the new grid database configuration :<br \/>\n<code>oracle@oda:\/u01\/app\/oracle\/product\/11.2.0.4\/dbhome_2\/dbs\/ [mydb] srvctl config database -d mydb_site1<br \/>\nDatabase unique name: mydb_site1<br \/>\nDatabase name: mydb<br \/>\nOracle home: \/u01\/app\/oracle\/product\/11.2.0.4\/dbhome_2<br \/>\nOracle user: oracle<br \/>\nSpfile: \/u02\/app\/oracle\/oradata\/mydb_site1\/dbs\/spfilemydb.ora<br \/>\nDomain:<br \/>\nStart options: open<br \/>\nStop options: immediate<br \/>\nDatabase role: PRIMARY<br \/>\nManagement policy: AUTOMATIC<br \/>\nServer pools: mydb_site1<br \/>\nDatabase instance: mydb<br \/>\nDisk Groups:<br \/>\nMount point paths: \/u02\/app\/oracle\/oradata\/mydb_site1,\/u03\/app\/oracle\/<br \/>\nServices:<br \/>\nType: SINGLE<br \/>\nDatabase is administrator managed<\/code><\/p>\n<p>And we can start our database again :<br \/>\n<code>oracle@oda:\/u01\/app\/oracle\/product\/11.2.0.4\/dbhome_1\/dbs\/ [mydb] srvctl start database -d mydb_site1<\/code><\/p>\n<p>Our database will now successfully be running on OraDB11204_home2.<\/p>\n<p>We can check and see that dcs agent has successfully updated the oratab file :<br \/>\n<code>oracle@oda:\/tmp\/ [mydb] grep mydb \/etc\/oratab<br \/>\nmydb:\/u01\/app\/oracle\/product\/11.2.0.4\/dbhome_2:N              # line added by Agent<\/code><\/p>\n<p>Our ORACLE_HOME env variable will now be :<br \/>\n<code>oracle@oda01-p:\/tmp\/ [mydb] echo $ORACLE_HOME<br \/>\n\/u01\/app\/oracle\/product\/11.2.0.4\/dbhome_2<\/code><\/p>\n<p>Are we done? No, let&#8217;s check how the ODA will display the new updated information.<\/p>\n<h3>Checking ODA metadata information<\/h3>\n<p>List dbhomes :<br \/>\n<code>[root@oda tmp]# odacli list-dbhomes<br \/>\nID                                       Name                 DB Version                               Home Location                                 Status<br \/>\n---------------------------------------- -------------------- ---------------------------------------- --------------------------------------------- ----------<br \/>\ned0a6667-0d70-4113-8a5e-3afaf1976fc2     OraDB12102_home1     12.1.0.2.171017 (26914423, 26717470)     \/u01\/app\/oracle\/product\/12.1.0.2\/dbhome_1     Configured<br \/>\n89f6687e-f575-45fc-91ef-5521374c54c0     OraDB11204_home1     11.2.0.4.171017 (26609929, 26392168)     \/u01\/app\/oracle\/product\/11.2.0.4\/dbhome_1     Configured<br \/>\n8c6bc663-b064-445b-8a14-b7c46df9d1da     OraDB12102_home3     12.1.0.2.171017 (26914423, 26717470)     \/u01\/app\/oracle\/product\/12.1.0.2\/dbhome_3     Configured<br \/>\n9783fd89-f035-4d1a-aaaf-f1cdb09c6ea8     OraDB11204_home2     11.2.0.4.171017 (26609929, 26392168)     \/u01\/app\/oracle\/product\/11.2.0.4\/dbhome_2     Configured<\/code><\/p>\n<p>List database information :<br \/>\n<code>[root@oda tmp]# odacli list-databases<br \/>\nID                                       DB Name    DB Type  DB Version           CDB        Class    Shape    Storage    Status        DbHomeID<br \/>\n---------------------------------------- ---------- -------- -------------------- ---------- -------- -------- ---------- ------------ ----------------------------------------<br \/>\nf38f3a6c-987c-4e11-8cfa-af5cb66ff4e3     mydb     Si       11.2.0.4             false      OLTP     Odb1     ACFS       Configured   89f6687e-f575-45fc-91ef-5521374c54c0<\/code><\/p>\n<p>As we can see, ODA metadata coming from the derby database will still show mydb database linked to OraDB11204_home1.<\/p>\n<h3>Updating ODA metadata<\/h3>\n<p>Let&#8217;s update derby database to reflect the changes.<\/p>\n<p>You can get your current appliance version by running the command :<br \/>\n<code>odacli describe-component<\/code><\/p>\n<h4>ODA version 18.3 or higher<\/h4>\n<p>If you are running ODA version 18.3 or higher you can use following command to move a database from one database home to another database home of same base version :<br \/>\n<code>odacli modify-database -i  -dh <\/code><\/p>\n<p>This command might not be successfull if your database was initially created as instance only : <\/p>\n<p><code>[root@oda tmp]# odacli modify-database -i f38f3a6c-987c-4e11-8cfa-af5cb66ff4e3 -dh 9783fd89-f035-4d1a-aaaf-f1cdb09c6ea8<br \/>\nDCS-10045:Validation error encountered: Changing the database home is not allowed for an instance only database.<\/code><\/p>\n<h4>ODA version lower than 18.3<\/h4>\n<p>If you are running a lower version of ODA, you will need to update the derby DB manually. <strong>I would strongly recommend to act carefully on the derby database to make sure not to corrupt the ODA. I would also encourage you to get Oracle support guidance in case you need to act on your production ODA.<\/strong><br \/>\nThe next steps will describe how to update the derby DB manually.<\/p>\n<h5>1) Stop the DCS Agent<\/h5>\n<p><code>[root@oda ~]# initctl stop initdcsagent<br \/>\ninitdcsagent stop\/waiting<\/p>\n<p>[root@oda ~]# ps -ef | grep dcs-agent | grep -v grep<br \/>\n[root@oda ~]#<\/code><\/p>\n<h5>2) Copy the derby Database<\/h5>\n<p>It is important to backup the repository and to apply the changes on the backup in order to keep the original version unchanged in case of trouble.<\/p>\n<p>Go in the derby db repository folder :<br \/>\n<code>[root@oda tmp]# cd \/opt\/oracle\/dcs\/repo<\/code><\/p>\n<p>List current repository folder :<br \/>\n<code>[root@oda repo]# ls -l<br \/>\ntotal 24<br \/>\n-rw-r--r-- 1 root root 1149 Aug 27 11:57 derby.log<br \/>\ndrwxr-xr-x 4 root root 4096 Aug 27 15:32 node_0<br \/>\ndrwxr-xr-x 4 root root 4096 Aug 12 16:18 node_0_orig_12082019_1619<br \/>\ndrwxr-xr-x 4 root root 4096 Aug 26 11:31 node_0_orig_26082019_1132<br \/>\ndrwxr-xr-x 4 root root 4096 Aug 26 15:27 node_0_orig_26082019_1528<br \/>\ndrwxr-xr-x 4 root root 4096 Aug 27 11:57 node_0_orig_27082019_1158<\/code><\/p>\n<p>Backup the repository (we will apply the changes on the backup repository to keep the original so far unchanged) :<br \/>\n<code>[root@oda repo]# cp -rp node_0 node_0_backup_27082019_1533<\/code><\/p>\n<p>List current repository folder :<br \/>\n<code>[root@oda repo]# ls -l<br \/>\ntotal 28<br \/>\n-rw-r--r-- 1 root root 1149 Aug 27 11:57 derby.log<br \/>\ndrwxr-xr-x 4 root root 4096 Aug 27 15:32 node_0<br \/>\ndrwxr-xr-x 4 root root 4096 Aug 27 15:32 node_0_backup_27082019_1533<br \/>\ndrwxr-xr-x 4 root root 4096 Aug 12 16:18 node_0_orig_12082019_1619<br \/>\ndrwxr-xr-x 4 root root 4096 Aug 26 11:31 node_0_orig_26082019_1132<br \/>\ndrwxr-xr-x 4 root root 4096 Aug 26 15:27 node_0_orig_26082019_1528<br \/>\ndrwxr-xr-x 4 root root 4096 Aug 27 11:57 node_0_orig_27082019_1158<\/code><\/p>\n<h5>3) Start DCS Agent<\/h5>\n<p><code>[root@oda repo]# initctl start initdcsagent<br \/>\ninitdcsagent start\/running, process 45530<\/p>\n<p>[root@oda repo]# ps -ef | grep dcs-agent | grep -v grep<br \/>\nroot     45530     1 99 15:33 ?        00:00:10 java -Xms128m -Xmx512m -XX:MetaspaceSize=128m -XX:MaxMetaspaceSize=512m -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 -jar \/opt\/oracle\/dcs\/bin\/dcs-agent-2.4.12-oda-SNAPSHOT.jar server \/opt\/oracle\/dcs\/conf\/dcs-agent.json<br \/>\n[root@oda repo]#<\/code><\/p>\n<h5>4) Update metadata information<\/h5>\n<p>We now need to connect to the Derby backup database and make home id changes for the specific database.<\/p>\n<p>Let&#8217;s connect to the derby database :<br \/>\n<code>[root@oda repo]# \/usr\/java\/jdk1.8.0_161\/db\/bin\/ij<br \/>\nij version 10.11<br \/>\nij&gt; connect 'jdbc:derby:node_0_backup_27082019_1533';<\/code><\/p>\n<p>Let&#8217;s check current metadata information :<br \/>\n<code>ij&gt; select DBHOMEID from DB where ID='f38f3a6c-987c-4e11-8cfa-af5cb66ff4e3';<br \/>\nDBHOMEID<br \/>\n--------------------------------------------------------------------------------------------------------------------------------<br \/>\n89f6687e-f575-45fc-91ef-5521374c54c0<br \/>\n1 row selected<\/code><\/p>\n<p>Let&#8217;s update metadata according the home changes :<br \/>\n<code>ij&gt; update DB set DBHOMEID='9783fd89-f035-4d1a-aaaf-f1cdb09c6ea8' where ID='f38f3a6c-987c-4e11-8cfa-af5cb66ff4e3';<br \/>\n1 row inserted\/updated\/deleted<\/code><\/p>\n<p>Let&#8217;s check the updated information :<br \/>\n<code>ij&gt; select DBHOMEID from DB where ID='f38f3a6c-987c-4e11-8cfa-af5cb66ff4e3';<br \/>\nDBHOMEID<br \/>\n--------------------------------------------------------------------------------------------------------------------------------<br \/>\n9783fd89-f035-4d1a-aaaf-f1cdb09c6ea8<br \/>\n1 row selected<\/code><\/p>\n<p>Let&#8217;s commit the changes :<br \/>\n<code>ij&gt; commit;<\/code><\/p>\n<p>And finally exit :<br \/>\n<code>ij&gt; exit;<\/code><\/p>\n<h5>5) Stop the DCS Agent<\/h5>\n<p><code>[root@oda repo]# initctl stop initdcsagent<br \/>\ninitdcsagent stop\/waiting<\/p>\n<p>[root@oda repo]# ps -ef | grep dcs-agent | grep -v grep<br \/>\n[root@oda repo]#<\/code><\/p>\n<h5>6) Apply the changes in production<\/h5>\n<p>In this step, we will rename the original repository to keep a backup and put our changes in production.<\/p>\n<p>List current repository folder :<br \/>\n<code>[root@oda repo]# ls -ltrh<br \/>\ntotal 28K<br \/>\ndrwxr-xr-x 4 root root 4.0K Aug 12 16:18 node_0_orig_12082019_1619<br \/>\ndrwxr-xr-x 4 root root 4.0K Aug 26 11:31 node_0_orig_26082019_1132<br \/>\ndrwxr-xr-x 4 root root 4.0K Aug 26 15:27 node_0_orig_26082019_1528<br \/>\ndrwxr-xr-x 4 root root 4.0K Aug 27 11:57 node_0_orig_27082019_1158<br \/>\ndrwxr-xr-x 4 root root 4.0K Aug 27 15:35 node_0_backup_27082019_1533<br \/>\n-rw-r--r-- 1 root root 1.2K Aug 27 15:35 derby.log<br \/>\ndrwxr-xr-x 4 root root 4.0K Aug 27 15:36 node_0<\/code><\/p>\n<p>Backup the original database :<br \/>\n<code>[root@oda repo]# mv node_0 node_0_orig_27082019_1536<\/code><\/p>\n<p>Put our changes in production :<br \/>\n<code>[root@oda repo]# mv node_0_backup_27082019_1533 node_0<\/code><\/p>\n<p>Check the repository folder :<br \/>\n<code>[root@oda repo]# ls -ltrh<br \/>\ntotal 28K<br \/>\ndrwxr-xr-x 4 root root 4.0K Aug 12 16:18 node_0_orig_12082019_1619<br \/>\ndrwxr-xr-x 4 root root 4.0K Aug 26 11:31 node_0_orig_26082019_1132<br \/>\ndrwxr-xr-x 4 root root 4.0K Aug 26 15:27 node_0_orig_26082019_1528<br \/>\ndrwxr-xr-x 4 root root 4.0K Aug 27 11:57 node_0_orig_27082019_1158<br \/>\ndrwxr-xr-x 4 root root 4.0K Aug 27 15:35 node_0<br \/>\n-rw-r--r-- 1 root root 1.2K Aug 27 15:35 derby.log<br \/>\ndrwxr-xr-x 4 root root 4.0K Aug 27 15:36 node_0_orig_27082019_1536<\/code><\/p>\n<h5>7) Start the DCS Agent<\/h5>\n<p><code>[root@oda repo]# initctl start initdcsagent<br \/>\ninitdcsagent start\/running, process 59703<\/p>\n<p>[root@oda repo]# ps -ef | grep dcs-agent | grep -v grep<br \/>\nroot     59703     1 99 15:37 ?        00:00:11 java -Xms128m -Xmx512m -XX:MetaspaceSize=128m -XX:MaxMetaspaceSize=512m -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 -jar \/opt\/oracle\/dcs\/bin\/dcs-agent-2.4.12-oda-SNAPSHOT.jar server \/opt\/oracle\/dcs\/conf\/dcs-agent.json<br \/>\n[root@oda repo]#<\/code><\/p>\n<h5>8) Check ODA metadata<\/h5>\n<p>Now we can check and see that derby database is showing correct metadata information.<\/p>\n<p>Lsit dbhomes :<br \/>\n<code>[root@oda repo]# odacli list-dbhomes<br \/>\nID                                       Name                 DB Version                               Home Location                                 Status<br \/>\n---------------------------------------- -------------------- ---------------------------------------- --------------------------------------------- ----------<br \/>\ned0a6667-0d70-4113-8a5e-3afaf1976fc2     OraDB12102_home1     12.1.0.2.171017 (26914423, 26717470)     \/u01\/app\/oracle\/product\/12.1.0.2\/dbhome_1     Configured<br \/>\n89f6687e-f575-45fc-91ef-5521374c54c0     OraDB11204_home1     11.2.0.4.171017 (26609929, 26392168)     \/u01\/app\/oracle\/product\/11.2.0.4\/dbhome_1     Configured<br \/>\n8c6bc663-b064-445b-8a14-b7c46df9d1da     OraDB12102_home3     12.1.0.2.171017 (26914423, 26717470)     \/u01\/app\/oracle\/product\/12.1.0.2\/dbhome_3     Configured<br \/>\n9783fd89-f035-4d1a-aaaf-f1cdb09c6ea8     OraDB11204_home2     11.2.0.4.171017 (26609929, 26392168)     \/u01\/app\/oracle\/product\/11.2.0.4\/dbhome_2     Configured<\/code><\/p>\n<p>Check new medata database information :<br \/>\n<code>[root@oda repo]# odacli list-databases<br \/>\nID                                       DB Name    DB Type  DB Version           CDB        Class    Shape    Storage    Status        DbHomeID<br \/>\n---------------------------------------- ---------- -------- -------------------- ---------- -------- -------- ---------- ------------ ----------------------------------------<br \/>\nf38f3a6c-987c-4e11-8cfa-af5cb66ff4e3     mydb     Si       11.2.0.4             false      OLTP     Odb1     ACFS       Configured   9783fd89-f035-4d1a-aaaf-f1cdb09c6ea8<\/p>\n<p>[root@oda repo]# odacli describe-database -i f38f3a6c-987c-4e11-8cfa-af5cb66ff4e3<br \/>\nDatabase details<br \/>\n----------------------------------------------------------------<br \/>\n                     ID: f38f3a6c-987c-4e11-8cfa-af5cb66ff4e3<br \/>\n            Description: mydb<br \/>\n                DB Name: mydb<br \/>\n             DB Version: 11.2.0.4<br \/>\n                DB Type: Si<br \/>\n             DB Edition: EE<br \/>\n                   DBID:<br \/>\n Instance Only Database: true<br \/>\n                    CDB: false<br \/>\n               PDB Name:<br \/>\n    PDB Admin User Name:<br \/>\n                  Class: OLTP<br \/>\n                  Shape: Odb1<br \/>\n                Storage: ACFS<br \/>\n           CharacterSet: AL32UTF8<br \/>\n  National CharacterSet: AL16UTF16<br \/>\n               Language: AMERICAN<br \/>\n              Territory: AMERICA<br \/>\n                Home ID: 9783fd89-f035-4d1a-aaaf-f1cdb09c6ea8<br \/>\n        Console Enabled: false<br \/>\n     Level 0 Backup Day: Sunday<br \/>\n    AutoBackup Disabled: false<br \/>\n                Created: June 11, 2019 2:46:35 PM CEST<br \/>\n         DB Domain Name: in-kon.ch<\/code><\/p>\n<h3>Conclusion<\/h3>\n<p>Database is now running on new oracle home and ODA metadata information are up to date. Updating metada might be very important for further database upgrade or further database deletion that will be performed with odacli commands. Otherwise next commands might failed.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Moving database to new ORACLE_HOME is a common dba task. Performing this task on an ODA will need an additional step knowing ODA Lite is using an internal Derby database for the metadata. ODA HA will not be a problem here, knowing we do not have any Derby database. Through this blog I would like [&hellip;]<\/p>\n","protected":false},"author":48,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[229,59],"tags":[280,23,79,96],"type_dbi":[],"class_list":["post-12802","post","type-post","status-publish","format-standard","hentry","category-database-administration-monitoring","category-oracle","tag-database","tag-dba","tag-oda","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>Moving oracle database to new home on 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\/moving-oracle-database-to-new-home-on-oda\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Moving oracle database to new home on ODA\" \/>\n<meta property=\"og:description\" content=\"Moving database to new ORACLE_HOME is a common dba task. Performing this task on an ODA will need an additional step knowing ODA Lite is using an internal Derby database for the metadata. ODA HA will not be a problem here, knowing we do not have any Derby database. Through this blog I would like [&hellip;]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/moving-oracle-database-to-new-home-on-oda\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2019-09-13T06:27:43+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=\"12 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\/moving-oracle-database-to-new-home-on-oda\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/moving-oracle-database-to-new-home-on-oda\/\"},\"author\":{\"name\":\"Marc Wagner\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/225d9884b8467ead9a872823acb14628\"},\"headline\":\"Moving oracle database to new home on ODA\",\"datePublished\":\"2019-09-13T06:27:43+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/moving-oracle-database-to-new-home-on-oda\/\"},\"wordCount\":935,\"commentCount\":0,\"keywords\":[\"database\",\"DBA\",\"ODA\",\"Oracle\"],\"articleSection\":[\"Database Administration &amp; Monitoring\",\"Oracle\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/moving-oracle-database-to-new-home-on-oda\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/moving-oracle-database-to-new-home-on-oda\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/moving-oracle-database-to-new-home-on-oda\/\",\"name\":\"Moving oracle database to new home on ODA - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"datePublished\":\"2019-09-13T06:27:43+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/225d9884b8467ead9a872823acb14628\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/moving-oracle-database-to-new-home-on-oda\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/moving-oracle-database-to-new-home-on-oda\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/moving-oracle-database-to-new-home-on-oda\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Moving oracle database to new home on 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":"Moving oracle database to new home on 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\/moving-oracle-database-to-new-home-on-oda\/","og_locale":"en_US","og_type":"article","og_title":"Moving oracle database to new home on ODA","og_description":"Moving database to new ORACLE_HOME is a common dba task. Performing this task on an ODA will need an additional step knowing ODA Lite is using an internal Derby database for the metadata. ODA HA will not be a problem here, knowing we do not have any Derby database. Through this blog I would like [&hellip;]","og_url":"https:\/\/www.dbi-services.com\/blog\/moving-oracle-database-to-new-home-on-oda\/","og_site_name":"dbi Blog","article_published_time":"2019-09-13T06:27:43+00:00","author":"Marc Wagner","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Marc Wagner","Est. reading time":"12 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/moving-oracle-database-to-new-home-on-oda\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/moving-oracle-database-to-new-home-on-oda\/"},"author":{"name":"Marc Wagner","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/225d9884b8467ead9a872823acb14628"},"headline":"Moving oracle database to new home on ODA","datePublished":"2019-09-13T06:27:43+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/moving-oracle-database-to-new-home-on-oda\/"},"wordCount":935,"commentCount":0,"keywords":["database","DBA","ODA","Oracle"],"articleSection":["Database Administration &amp; Monitoring","Oracle"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/moving-oracle-database-to-new-home-on-oda\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/moving-oracle-database-to-new-home-on-oda\/","url":"https:\/\/www.dbi-services.com\/blog\/moving-oracle-database-to-new-home-on-oda\/","name":"Moving oracle database to new home on ODA - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2019-09-13T06:27:43+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/225d9884b8467ead9a872823acb14628"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/moving-oracle-database-to-new-home-on-oda\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/moving-oracle-database-to-new-home-on-oda\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/moving-oracle-database-to-new-home-on-oda\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Moving oracle database to new home on 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\/12802","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=12802"}],"version-history":[{"count":0,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/12802\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=12802"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=12802"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=12802"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=12802"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}