While patching ODAs from 19.10 to 19.13, the update-dbhome could fail if some databases inside this dbhome are stopped or only mounted. Job would then stop with a DCS-10001:Internal error encountered: PRGH-1153 : RHPHelper call to get runing nodes failed for DB: “ARITSTDB”.<\/p>\n
How to solve this problem?<\/p>\n
My environment is composed of 3 X8-2M ODAs, 2 are dedicated for production with Data Guard, and 1 for test and development databases. Initialy deployed with 19.6, the goal was to patch to the latest 19.13. An intermediate patch was needed, so these ODAs will first be patched to 19.10 before applying 19.13 straight after.<\/p>\n
Patching from 19.6 to 19.10 was fine, but patching the only 19c dbhome to 19.13 was not. Job raised an error:<\/p>\n
odacli describe-job -i 087d618c-714c-463f-a1e8-7efcba0541fc<\/strong>\n\nJob details\n----------------------------------------------------------------\n ID: 087d618c-714c-463f-a1e8-7efcba0541fc\n Description: DB Home Patching: Home Id is 38c08a67-2730-4b76-92aa-4a47840082c5\n Status: Failure\n Created: February 23, 2022 6:02:42 PM CET\n Message: DCS-10001:Internal error encountered: PRGH-1153 : RHPHelper call to get runing nodes failed for DB: \"ARITSTDB\"..\n\nTask Name Start Time End Time Status\n---------------------------------------- ----------------------------------- ----------------------------------- ----------\nDB Home Patching February 23, 2022 6:03:02 PM CET February 23, 2022 7:02:53 PM CET Failure\nDB Home Patching February 23, 2022 6:03:03 PM CET February 23, 2022 7:02:53 PM CET Failure\nAdding USER SSH_EQUIVALENCE February 23, 2022 6:03:03 PM CET February 23, 2022 6:03:03 PM CET Success\nAdding USER SSH_EQUIVALENCE February 23, 2022 6:03:03 PM CET February 23, 2022 6:03:04 PM CET Success\ntask:TaskSequential_2030 February 23, 2022 6:03:04 PM CET February 23, 2022 7:01:55 PM CET Failure\nCreating wallet for DB Client February 23, 2022 6:03:43 PM CET February 23, 2022 6:03:43 PM CET Success\nPatch databases by RHP February 23, 2022 6:03:43 PM CET February 23, 2022 6:11:03 PM CET Success\nupdating database metadata February 23, 2022 6:11:56 PM CET February 23, 2022 6:11:56 PM CET Success\nSet log_archive_dest for Database February 23, 2022 6:11:56 PM CET February 23, 2022 6:12:01 PM CET Success\nPatch databases by RHP February 23, 2022 6:12:01 PM CET February 23, 2022 6:19:10 PM CET Success\nupdating database metadata February 23, 2022 6:20:03 PM CET February 23, 2022 6:20:03 PM CET Success\nSet log_archive_dest for Database February 23, 2022 6:20:03 PM CET February 23, 2022 6:20:08 PM CET Success\nPatch databases by RHP February 23, 2022 6:20:08 PM CET February 23, 2022 6:25:26 PM CET Success\nupdating database metadata February 23, 2022 6:26:21 PM CET February 23, 2022 6:26:21 PM CET Success\nSet log_archive_dest for Database February 23, 2022 6:26:21 PM CET February 23, 2022 6:26:26 PM CET Success\nPatch databases by RHP February 23, 2022 6:26:26 PM CET February 23, 2022 6:31:54 PM CET Success\nupdating database metadata February 23, 2022 6:32:49 PM CET February 23, 2022 6:32:49 PM CET Success\nSet log_archive_dest for Database February 23, 2022 6:32:49 PM CET February 23, 2022 6:32:53 PM CET Success\nPatch databases by RHP February 23, 2022 6:32:53 PM CET February 23, 2022 6:38:09 PM CET Success\nupdating database metadata February 23, 2022 6:39:02 PM CET February 23, 2022 6:39:03 PM CET Success\nSet log_archive_dest for Database February 23, 2022 6:39:03 PM CET February 23, 2022 6:39:07 PM CET Success\nPatch databases by RHP February 23, 2022 6:39:07 PM CET February 23, 2022 6:44:02 PM CET Success\nupdating database metadata February 23, 2022 6:44:58 PM CET February 23, 2022 6:44:58 PM CET Success\nSet log_archive_dest for Database February 23, 2022 6:44:58 PM CET February 23, 2022 6:45:03 PM CET Success\nPatch databases by RHP February 23, 2022 6:45:03 PM CET February 23, 2022 6:51:55 PM CET Success\nupdating database metadata February 23, 2022 6:52:48 PM CET February 23, 2022 6:52:48 PM CET Success\nSet log_archive_dest for Database February 23, 2022 6:52:48 PM CET February 23, 2022 6:52:52 PM CET Success\nPatch databases by RHP February 23, 2022 6:52:52 PM CET February 23, 2022 7:00:09 PM CET Success\nupdating database metadata February 23, 2022 7:01:05 PM CET February 23, 2022 7:01:05 PM CET Success\nSet log_archive_dest for Database February 23, 2022 7:01:05 PM CET February 23, 2022 7:01:10 PM CET Success\nPatch databases by RHP February 23, 2022 7:01:10 PM CET February 23, 2022 7:01:55 PM CET Failure\n<\/code><\/pre>\nStatus of databases after patching<\/h2>\n
Failure didn’t happen immediately, part of the job should have been done. Let’s check databases and version associated:<\/p>\n
odacli list-databases<\/strong>\n\nID DB Name DB Type DB Version CDB Class Shape Storage Status DbHomeID\n---------------------------------------- ---------- -------- -------------------- ---------- -------- -------- ---------- ------------ ----------------------------------------\n6e26f06c-ee16-46f2-986e-0d82602fe93a GOTTSTDB SI 19.13.0.0.211019 false OLTP odb1 ASM CONFIGURED e087a1ea-bf81-44a0-8f04-4d154c1fecc9\n17c84065-9bb9-4548-bf72-d0a02ad2213f PATSTDB SI 19.13.0.0.211019 false OLTP odb1s ASM CONFIGURED e087a1ea-bf81-44a0-8f04-4d154c1fecc9\nf34eddac-7794-47cd-9d6a-08aa3b2f90b7 PATSITDB SI 19.10.0.0.210119 false OLTP odb1s ASM CONFIGURED 38c08a67-2730-4b76-92aa-4a47840082c5\n185bc4bf-492e-4b98-9440-b24c2864f572 PATCIDB SI 19.10.0.0.210119 false OLTP odb1s ASM CONFIGURED 38c08a67-2730-4b76-92aa-4a47840082c5\nd0657336-b416-40d7-929f-8a9fe604e908 M4CTSTDB SI 19.10.0.0.210119 false OLTP odb1s ASM CONFIGURED 38c08a67-2730-4b76-92aa-4a47840082c5\n9681f86e-88b9-468f-93c6-9b2db76bede1 MINDEVDB SI 19.13.0.0.211019 false OLTP odb1s ASM CONFIGURED e087a1ea-bf81-44a0-8f04-4d154c1fecc9\na5e4f009-942a-488c-9097-6e34e6b858dd MINTSTDB SI 19.10.0.0.210119 false OLTP odb1s ASM CONFIGURED 38c08a67-2730-4b76-92aa-4a47840082c5\n62416912-551b-44cb-a23d-8f60ca7d8a37 REGNTTST SI 19.10.0.0.210119 false OLTP odb1s ASM CONFIGURED 38c08a67-2730-4b76-92aa-4a47840082c5\naf37407a-f340-43b2-bb41-7f7e1143c703 LOGMTST SI 19.10.0.0.210119 false OLTP odb1s ASM CONFIGURED 38c08a67-2730-4b76-92aa-4a47840082c5\n6ce0e7a6-7560-4b2a-b992-cf6cca7500f0 WNTVSTDB SI 19.10.0.0.210119 false OLTP odb1s ASM CONFIGURED 38c08a67-2730-4b76-92aa-4a47840082c5\n9bebb050-8090-444f-bbc7-7dcfb4bc68a1 BQ3 SI 19.13.0.0.211019 false OLTP odb1s ASM CONFIGURED e087a1ea-bf81-44a0-8f04-4d154c1fecc9\nd7da5dba-03d5-4cbd-ba7f-00aaea97c55c POQ SI 19.10.0.0.210119 false OLTP odb1s ASM CONFIGURED 38c08a67-2730-4b76-92aa-4a47840082c5\n7e396dee-e4b3-4d84-8a4e-e42b4de69884 OQ1 SI 19.13.0.0.211019 false OLTP odb1s ASM CONFIGURED e087a1ea-bf81-44a0-8f04-4d154c1fecc9\n64c248c3-aaf9-4a89-a672-f6e60e20e2aa SQ1 SI 19.10.0.0.210119 false OLTP odb1s ASM CONFIGURED 38c08a67-2730-4b76-92aa-4a47840082c5\n69b805d8-db8c-4240-aadc-e267b5c6f020 SQ2 SI 19.10.0.0.210119 false OLTP odb1s ASM CONFIGURED 38c08a67-2730-4b76-92aa-4a47840082c5\n76562430-5554-4876-967f-58bcb81e2818 OD1 SI 19.10.0.0.210119 false OLTP odb1s ASM CONFIGURED 38c08a67-2730-4b76-92aa-4a47840082c5\n4c50b2d6-0e4f-47d6-a278-5ee6bd4635d4 BD3 SI 19.10.0.0.210119 false OLTP odb1s ASM CONFIGURED 38c08a67-2730-4b76-92aa-4a47840082c5\n9c5bac01-e9a6-4345-8076-4b647fb0457e SD1 SI 19.13.0.0.211019 false OLTP odb1s ASM CONFIGURED e087a1ea-bf81-44a0-8f04-4d154c1fecc9\nb051e5be-92c1-4d85-9060-7a36bf4befd6 POD SI 19.13.0.0.211019 false OLTP odb1s ASM CONFIGURED e087a1ea-bf81-44a0-8f04-4d154c1fecc9\nefd34b41-cbda-4785-9cda-e08450203619 SD2 SI 19.13.0.0.211019 false OLTP odb1s ASM CONFIGURED e087a1ea-bf81-44a0-8f04-4d154c1fecc9\n4c679720-c577-4934-ab56-67d421538366 ARITSTDB SI 19.10.0.0.210119 false OLTP odb1s ASM CONFIGURED 38c08a67-2730-4b76-92aa-4a47840082c5\n<\/code><\/pre>\nA few databases have been migrated to the new 19.13 dhbome, then job stopped after ARITSTDB database. Actually, ARITSTDB is a decommissioned database, still existing on my ODA. On one of the other ODA, behaviour was the same, but for another reason: databases were mostly standbys. So this part of the patch is not continuing after trying on a database not in read\/write mode.<\/p>\n
Retry to apply the patch on the dbhome<\/h2>\n
Let’s retry the patch to see if it can continue:<\/p>\n
odacli update-dbhome -i 38c08a67-2730-4b76-92aa-4a47840082c5 -v 19.13.0.0.0 -f<\/strong>\n\nodacli describe-job -i 9ec82ccd-d726-4172-be80-943bafbfbd18<\/strong>\n\nJob details\n----------------------------------------------------------------\n ID: 9ec82ccd-d726-4172-be80-943bafbfbd18\n Description: DB Home Patching: Home Id is 38c08a67-2730-4b76-92aa-4a47840082c5\n Status: Failure\n Created: February 23, 2022 7:11:36 PM CET\n Message: DCS-10001:Internal error encountered: PRCT-1014 : Internal error: CmdToolUtil-execute1-error1.\n\nTask Name Start Time End Time Status\n---------------------------------------- ----------------------------------- ----------------------------------- ----------\nDB Home Patching February 23, 2022 7:11:50 PM CET February 23, 2022 7:13:29 PM CET Failure\nDB Home Patching February 23, 2022 7:11:50 PM CET February 23, 2022 7:13:29 PM CET Failure\nAdding USER SSH_EQUIVALENCE February 23, 2022 7:11:50 PM CET February 23, 2022 7:11:51 PM CET Success\nAdding USER SSH_EQUIVALENCE February 23, 2022 7:11:51 PM CET February 23, 2022 7:11:51 PM CET Success\ntask:TaskSequential_3109 February 23, 2022 7:11:51 PM CET February 23, 2022 7:12:54 PM CET Failure\nCreating wallet for DB Client February 23, 2022 7:12:30 PM CET February 23, 2022 7:12:30 PM CET Success\nPatch databases by RHP February 23, 2022 7:12:30 PM CET February 23, 2022 7:12:54 PM CET Failure\n<\/code><\/pre>\nDespite the failure status, my stopped database is now switched to its new home, but the task stopped again after this change.<\/p>\n
odacli list-databases<\/strong>\n\nID DB Name DB Type DB Version CDB Class Shape Storage Status DbHomeID\n---------------------------------------- ---------- -------- -------------------- ---------- -------- -------- ---------- ------------ ----------------------------------------\n6e26f06c-ee16-46f2-986e-0d82602fe93a GOTTSTDB SI 19.13.0.0.211019 false OLTP odb1 ASM CONFIGURED e087a1ea-bf81-44a0-8f04-4d154c1fecc9\n17c84065-9bb9-4548-bf72-d0a02ad2213f PATSTDB SI 19.13.0.0.211019 false OLTP odb1s ASM CONFIGURED e087a1ea-bf81-44a0-8f04-4d154c1fecc9\nf34eddac-7794-47cd-9d6a-08aa3b2f90b7 PATSITDB SI 19.10.0.0.210119 false OLTP odb1s ASM CONFIGURED 38c08a67-2730-4b76-92aa-4a47840082c5\n185bc4bf-492e-4b98-9440-b24c2864f572 PATCIDB SI 19.10.0.0.210119 false OLTP odb1s ASM CONFIGURED 38c08a67-2730-4b76-92aa-4a47840082c5\nd0657336-b416-40d7-929f-8a9fe604e908 M4CTSTDB SI 19.10.0.0.210119 false OLTP odb1s ASM CONFIGURED 38c08a67-2730-4b76-92aa-4a47840082c5\n9681f86e-88b9-468f-93c6-9b2db76bede1 MINDEVDB SI 19.13.0.0.211019 false OLTP odb1s ASM CONFIGURED e087a1ea-bf81-44a0-8f04-4d154c1fecc9\na5e4f009-942a-488c-9097-6e34e6b858dd MINTSTDB SI 19.10.0.0.210119 false OLTP odb1s ASM CONFIGURED 38c08a67-2730-4b76-92aa-4a47840082c5\n62416912-551b-44cb-a23d-8f60ca7d8a37 REGNTTST SI 19.10.0.0.210119 false OLTP odb1s ASM CONFIGURED 38c08a67-2730-4b76-92aa-4a47840082c5\naf37407a-f340-43b2-bb41-7f7e1143c703 LOGMTST SI 19.10.0.0.210119 false OLTP odb1s ASM CONFIGURED 38c08a67-2730-4b76-92aa-4a47840082c5\n6ce0e7a6-7560-4b2a-b992-cf6cca7500f0 WNTVSTDB SI 19.10.0.0.210119 false OLTP odb1s ASM CONFIGURED 38c08a67-2730-4b76-92aa-4a47840082c5\n9bebb050-8090-444f-bbc7-7dcfb4bc68a1 BQ3 SI 19.13.0.0.211019 false OLTP odb1s ASM CONFIGURED e087a1ea-bf81-44a0-8f04-4d154c1fecc9\nd7da5dba-03d5-4cbd-ba7f-00aaea97c55c POQ SI 19.10.0.0.210119 false OLTP odb1s ASM CONFIGURED 38c08a67-2730-4b76-92aa-4a47840082c5\n7e396dee-e4b3-4d84-8a4e-e42b4de69884 OQ1 SI 19.13.0.0.211019 false OLTP odb1s ASM CONFIGURED e087a1ea-bf81-44a0-8f04-4d154c1fecc9\n64c248c3-aaf9-4a89-a672-f6e60e20e2aa SQ1 SI 19.10.0.0.210119 false OLTP odb1s ASM CONFIGURED 38c08a67-2730-4b76-92aa-4a47840082c5\n69b805d8-db8c-4240-aadc-e267b5c6f020 SQ2 SI 19.10.0.0.210119 false OLTP odb1s ASM CONFIGURED 38c08a67-2730-4b76-92aa-4a47840082c5\n76562430-5554-4876-967f-58bcb81e2818 OD1 SI 19.10.0.0.210119 false OLTP odb1s ASM CONFIGURED 38c08a67-2730-4b76-92aa-4a47840082c5\n4c50b2d6-0e4f-47d6-a278-5ee6bd4635d4 BD3 SI 19.10.0.0.210119 false OLTP odb1s ASM CONFIGURED 38c08a67-2730-4b76-92aa-4a47840082c5\n9c5bac01-e9a6-4345-8076-4b647fb0457e SD1 SI 19.13.0.0.211019 false OLTP odb1s ASM CONFIGURED e087a1ea-bf81-44a0-8f04-4d154c1fecc9\nb051e5be-92c1-4d85-9060-7a36bf4befd6 POD SI 19.13.0.0.211019 false OLTP odb1s ASM CONFIGURED e087a1ea-bf81-44a0-8f04-4d154c1fecc9\nefd34b41-cbda-4785-9cda-e08450203619 SD2 SI 19.13.0.0.211019 false OLTP odb1s ASM CONFIGURED e087a1ea-bf81-44a0-8f04-4d154c1fecc9\n4c679720-c577-4934-ab56-67d421538366 ARITSTDB SI 19.13.0.0.210119 false OLTP odb1s ASM CONFIGURED e087a1ea-bf81-44a0-8f04-4d154c1fecc9\n<\/code><\/pre>\nLet’s start again the patching of this dbhome:<\/p>\n
odacli update-dbhome -i 38c08a67-2730-4b76-92aa-4a47840082c5 -v 19.13.0.0.0 -f<\/strong>\n\nodacli describe-job -i \"36843376-2ea3-4d17-b641-dac34270d1f2\"<\/strong>\n\n\nJob details\n----------------------------------------------------------------\n ID: 36843376-2ea3-4d17-b641-dac34270d1f2\n Description: DB Home Patching: Home Id is 38c08a67-2730-4b76-92aa-4a47840082c5\n Status: Success\n Created: February 23, 2022 7:16:42 PM CET\n Message:\n\nTask Name Start Time End Time Status\n---------------------------------------- ----------------------------------- ----------------------------------- ----------\nAdding USER SSH_EQUIVALENCE February 23, 2022 7:16:56 PM CET February 23, 2022 7:16:57 PM CET Success\nAdding USER SSH_EQUIVALENCE February 23, 2022 7:16:57 PM CET February 23, 2022 7:16:57 PM CET Success\nCreating wallet for DB Client February 23, 2022 7:17:36 PM CET February 23, 2022 7:17:36 PM CET Success\nPatch databases by RHP February 23, 2022 7:17:36 PM CET February 23, 2022 7:23:05 PM CET Success\nupdating database metadata February 23, 2022 7:23:59 PM CET February 23, 2022 7:23:59 PM CET Success\nSet log_archive_dest for Database February 23, 2022 7:23:59 PM CET February 23, 2022 7:24:03 PM CET Success\nPatch databases by RHP February 23, 2022 7:24:03 PM CET February 23, 2022 7:31:11 PM CET Success\nupdating database metadata February 23, 2022 7:32:09 PM CET February 23, 2022 7:32:09 PM CET Success\nSet log_archive_dest for Database February 23, 2022 7:32:09 PM CET February 23, 2022 7:32:13 PM CET Success\nPatch databases by RHP February 23, 2022 7:32:13 PM CET February 23, 2022 7:39:15 PM CET Success\nupdating database metadata February 23, 2022 7:40:09 PM CET February 23, 2022 7:40:09 PM CET Success\nSet log_archive_dest for Database February 23, 2022 7:40:09 PM CET February 23, 2022 7:40:14 PM CET Success\nPatch databases by RHP February 23, 2022 7:40:14 PM CET February 23, 2022 7:47:25 PM CET Success\nupdating database metadata February 23, 2022 7:48:26 PM CET February 23, 2022 7:48:26 PM CET Success\nSet log_archive_dest for Database February 23, 2022 7:48:26 PM CET February 23, 2022 7:48:29 PM CET Success\nPatch databases by RHP February 23, 2022 7:48:29 PM CET February 23, 2022 7:55:39 PM CET Success\nupdating database metadata February 23, 2022 7:56:34 PM CET February 23, 2022 7:56:34 PM CET Success\nSet log_archive_dest for Database February 23, 2022 7:56:34 PM CET February 23, 2022 7:56:39 PM CET Success\nPatch databases by RHP February 23, 2022 7:56:39 PM CET February 23, 2022 8:03:39 PM CET Success\nupdating database metadata February 23, 2022 8:04:33 PM CET February 23, 2022 8:04:33 PM CET Success\nSet log_archive_dest for Database February 23, 2022 8:04:34 PM CET February 23, 2022 8:04:37 PM CET Success\nPatch databases by RHP February 23, 2022 8:04:37 PM CET February 23, 2022 8:11:27 PM CET Success\nupdating database metadata February 23, 2022 8:12:19 PM CET February 23, 2022 8:12:19 PM CET Success\nSet log_archive_dest for Database February 23, 2022 8:12:19 PM CET February 23, 2022 8:12:23 PM CET Success\nPatch databases by RHP February 23, 2022 8:12:23 PM CET February 23, 2022 8:18:00 PM CET Success\nupdating database metadata February 23, 2022 8:18:54 PM CET February 23, 2022 8:18:54 PM CET Success\nSet log_archive_dest for Database February 23, 2022 8:18:54 PM CET February 23, 2022 8:18:58 PM CET Success\nPatch databases by RHP February 23, 2022 8:18:58 PM CET February 23, 2022 8:24:02 PM CET Success\nupdating database metadata February 23, 2022 8:24:56 PM CET February 23, 2022 8:24:56 PM CET Success\nSet log_archive_dest for Database February 23, 2022 8:24:56 PM CET February 23, 2022 8:25:00 PM CET Success\nPatch databases by RHP February 23, 2022 8:25:00 PM CET February 23, 2022 8:30:13 PM CET Success\nupdating database metadata February 23, 2022 8:31:06 PM CET February 23, 2022 8:31:06 PM CET Success\nSet log_archive_dest for Database February 23, 2022 8:31:06 PM CET February 23, 2022 8:31:13 PM CET Success\nPatch databases by RHP February 23, 2022 8:31:13 PM CET February 23, 2022 8:36:19 PM CET Success\nupdating database metadata February 23, 2022 8:37:15 PM CET February 23, 2022 8:37:15 PM CET Success\nSet log_archive_dest for Database February 23, 2022 8:37:15 PM CET February 23, 2022 8:37:19 PM CET Success\nPatch databases by RHP February 23, 2022 8:37:19 PM CET February 23, 2022 8:42:41 PM CET Success\nupdating database metadata February 23, 2022 8:43:36 PM CET February 23, 2022 8:43:36 PM CET Success\nSet log_archive_dest for Database February 23, 2022 8:43:36 PM CET February 23, 2022 8:43:39 PM CET Success\nUpdate System version February 23, 2022 8:43:39 PM CET February 23, 2022 8:43:39 PM CET Success\nTDE parameter update February 23, 2022 8:44:27 PM CET February 23, 2022 8:44:27 PM CET Success\n\nodacli list-databases<\/strong>\nID DB Name DB Type DB Version CDB Class Shape Storage Status DbHomeID\n---------------------------------------- ---------- -------- -------------------- ---------- -------- -------- ---------- ------------ ----------------------------------------\n6e26f06c-ee16-46f2-986e-0d82602fe93a GOTTSTDB SI 19.13.0.0.211019 false OLTP odb1 ASM CONFIGURED e087a1ea-bf81-44a0-8f04-4d154c1fecc9\n17c84065-9bb9-4548-bf72-d0a02ad2213f PATSTDB SI 19.13.0.0.211019 false OLTP odb1s ASM CONFIGURED e087a1ea-bf81-44a0-8f04-4d154c1fecc9\nf34eddac-7794-47cd-9d6a-08aa3b2f90b7 PATSITDB SI 19.13.0.0.211019 false OLTP odb1s ASM CONFIGURED e087a1ea-bf81-44a0-8f04-4d154c1fecc9\n185bc4bf-492e-4b98-9440-b24c2864f572 PATCIDB SI 19.13.0.0.211019 false OLTP odb1s ASM CONFIGURED e087a1ea-bf81-44a0-8f04-4d154c1fecc9\nd0657336-b416-40d7-929f-8a9fe604e908 M4CTSTDB SI 19.13.0.0.211019 false OLTP odb1s ASM CONFIGURED e087a1ea-bf81-44a0-8f04-4d154c1fecc9\n9681f86e-88b9-468f-93c6-9b2db76bede1 MINDEVDB SI 19.13.0.0.211019 false OLTP odb1s ASM CONFIGURED e087a1ea-bf81-44a0-8f04-4d154c1fecc9\na5e4f009-942a-488c-9097-6e34e6b858dd MINTSTDB SI 19.13.0.0.211019 false OLTP odb1s ASM CONFIGURED e087a1ea-bf81-44a0-8f04-4d154c1fecc9\n62416912-551b-44cb-a23d-8f60ca7d8a37 REGNTTST SI 19.13.0.0.211019 false OLTP odb1s ASM CONFIGURED e087a1ea-bf81-44a0-8f04-4d154c1fecc9\naf37407a-f340-43b2-bb41-7f7e1143c703 LOGMTST SI 19.13.0.0.211019 false OLTP odb1s ASM CONFIGURED e087a1ea-bf81-44a0-8f04-4d154c1fecc9\n6ce0e7a6-7560-4b2a-b992-cf6cca7500f0 WNTVSTDB SI 19.13.0.0.211019 false OLTP odb1s ASM CONFIGURED e087a1ea-bf81-44a0-8f04-4d154c1fecc9\n9bebb050-8090-444f-bbc7-7dcfb4bc68a1 BQ3 SI 19.13.0.0.211019 false OLTP odb1s ASM CONFIGURED e087a1ea-bf81-44a0-8f04-4d154c1fecc9\nd7da5dba-03d5-4cbd-ba7f-00aaea97c55c POQ SI 19.13.0.0.211019 false OLTP odb1s ASM CONFIGURED e087a1ea-bf81-44a0-8f04-4d154c1fecc9\n7e396dee-e4b3-4d84-8a4e-e42b4de69884 OQ1 SI 19.13.0.0.211019 false OLTP odb1s ASM CONFIGURED e087a1ea-bf81-44a0-8f04-4d154c1fecc9\n64c248c3-aaf9-4a89-a672-f6e60e20e2aa SQ1 SI 19.13.0.0.211019 false OLTP odb1s ASM CONFIGURED e087a1ea-bf81-44a0-8f04-4d154c1fecc9\n69b805d8-db8c-4240-aadc-e267b5c6f020 SQ2 SI 19.13.0.0.211019 false OLTP odb1s ASM CONFIGURED e087a1ea-bf81-44a0-8f04-4d154c1fecc9\n76562430-5554-4876-967f-58bcb81e2818 OD1 SI 19.13.0.0.211019 false OLTP odb1s ASM CONFIGURED e087a1ea-bf81-44a0-8f04-4d154c1fecc9\n4c50b2d6-0e4f-47d6-a278-5ee6bd4635d4 BD3 SI 19.13.0.0.211019 false OLTP odb1s ASM CONFIGURED e087a1ea-bf81-44a0-8f04-4d154c1fecc9\n9c5bac01-e9a6-4345-8076-4b647fb0457e SD1 SI 19.13.0.0.211019 false OLTP odb1s ASM CONFIGURED e087a1ea-bf81-44a0-8f04-4d154c1fecc9\nb051e5be-92c1-4d85-9060-7a36bf4befd6 POD SI 19.13.0.0.211019 false OLTP odb1s ASM CONFIGURED e087a1ea-bf81-44a0-8f04-4d154c1fecc9\nefd34b41-cbda-4785-9cda-e08450203619 SD2 SI 19.13.0.0.211019 false OLTP odb1s ASM CONFIGURED e087a1ea-bf81-44a0-8f04-4d154c1fecc9\n4c679720-c577-4934-ab56-67d421538366 ARITSTDB SI 19.13.0.0.211019 false OLTP odb1s ASM CONFIGURED e087a1ea-bf81-44a0-8f04-4d154c1fecc9\n<\/code><\/pre>\nodacli finally managed to patch everything, but applying multiple time the patch on this home was needed. Number of runs depends on the number of databases not being read\/write opened. As long as you have databases still pointing to the old dbhome you need to apply the patch again. <\/p>\n
Conclusion<\/h2>\n
The solution to solve this problem is to start the patching again on the same dbhome and it will continue. Keep in mind that this has to be done in a sequential mode.<\/p>\n
Patching an ODA takes time, time to prepare, time to backup prior patching, time to apply the patch, time to do the troubleshooting. But it works and everything is up to date with a single patch.<\/p>\n","protected":false},"excerpt":{"rendered":"
Introduction While patching ODAs from 19.10 to 19.13, the update-dbhome could fail if some databases inside this dbhome are stopped or only mounted. Job would then stop with a DCS-10001:Internal error encountered: PRGH-1153 : RHPHelper call to get runing nodes failed for DB: “ARITSTDB”. How to solve this problem? Environment description My environment is composed […]<\/p>\n","protected":false},"author":45,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[229,198,59],"tags":[2444,2504,2184,1631,1327,365,572,2505,2485,2506,1586],"type_dbi":[],"class_list":["post-17144","post","type-post","status-publish","format-standard","hentry","category-database-administration-monitoring","category-database-management","category-oracle","tag-19-13","tag-cmdtoolutil-execute1-error1","tag-dcs-10001","tag-failure","tag-odacli","tag-oracle-database-appliance","tag-patch","tag-patch-database-by-rhp","tag-prct-1014","tag-prgh-1153","tag-update-dbhome"],"acf":[],"yoast_head":"\n
ODA 19.13: odacli update-dbhome raises DCS-10001 and PRGH-1153 - 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\/oda-19-13-odacli-update-dbhome-raises-dcs-10001-and-prgh-1153\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"ODA 19.13: odacli update-dbhome raises DCS-10001 and PRGH-1153\" \/>\n<meta property=\"og:description\" content=\"Introduction While patching ODAs from 19.10 to 19.13, the update-dbhome could fail if some databases inside this dbhome are stopped or only mounted. Job would then stop with a DCS-10001:Internal error encountered: PRGH-1153 : RHPHelper call to get runing nodes failed for DB: “ARITSTDB”. How to solve this problem? Environment description My environment is composed […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/oda-19-13-odacli-update-dbhome-raises-dcs-10001-and-prgh-1153\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2022-02-28T14:13:23+00:00\" \/>\n<meta name=\"author\" content=\"J\u00e9r\u00f4me Dubar\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"J\u00e9r\u00f4me Dubar\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"16 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\/oda-19-13-odacli-update-dbhome-raises-dcs-10001-and-prgh-1153\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/oda-19-13-odacli-update-dbhome-raises-dcs-10001-and-prgh-1153\/\"},\"author\":{\"name\":\"J\u00e9r\u00f4me Dubar\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/0fb4bbf128b4cda2f96d662dec2baedd\"},\"headline\":\"ODA 19.13: odacli update-dbhome raises DCS-10001 and PRGH-1153\",\"datePublished\":\"2022-02-28T14:13:23+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/oda-19-13-odacli-update-dbhome-raises-dcs-10001-and-prgh-1153\/\"},\"wordCount\":383,\"commentCount\":0,\"keywords\":[\"19.13\",\"CmdToolUtil-execute1-error1\",\"DCS-10001\",\"failure\",\"odacli\",\"Oracle database appliance\",\"patch\",\"patch database by RHP\",\"PRCT-1014\",\"PRGH-1153\",\"update-dbhome\"],\"articleSection\":[\"Database Administration & Monitoring\",\"Database management\",\"Oracle\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/oda-19-13-odacli-update-dbhome-raises-dcs-10001-and-prgh-1153\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/oda-19-13-odacli-update-dbhome-raises-dcs-10001-and-prgh-1153\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/oda-19-13-odacli-update-dbhome-raises-dcs-10001-and-prgh-1153\/\",\"name\":\"ODA 19.13: odacli update-dbhome raises DCS-10001 and PRGH-1153 - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"datePublished\":\"2022-02-28T14:13:23+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/0fb4bbf128b4cda2f96d662dec2baedd\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/oda-19-13-odacli-update-dbhome-raises-dcs-10001-and-prgh-1153\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/oda-19-13-odacli-update-dbhome-raises-dcs-10001-and-prgh-1153\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/oda-19-13-odacli-update-dbhome-raises-dcs-10001-and-prgh-1153\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"ODA 19.13: odacli update-dbhome raises DCS-10001 and PRGH-1153\"}]},{\"@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\/0fb4bbf128b4cda2f96d662dec2baedd\",\"name\":\"J\u00e9r\u00f4me Dubar\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/secure.gravatar.com\/avatar\/efaa5a7def0aa4cdaf49a470fb4a7641a3ea6e378ae1455096a0933f99f46d6b?s=96&d=mm&r=g\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/efaa5a7def0aa4cdaf49a470fb4a7641a3ea6e378ae1455096a0933f99f46d6b?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/efaa5a7def0aa4cdaf49a470fb4a7641a3ea6e378ae1455096a0933f99f46d6b?s=96&d=mm&r=g\",\"caption\":\"J\u00e9r\u00f4me Dubar\"},\"description\":\"J\u00e9r\u00f4me Dubar has more than 15 years of experience in the field of Information Technology. Ten years ago, he specialized in the Oracle Database technology. His expertise is focused on database architectures, high availability (RAC), disaster recovery (DataGuard), backups (RMAN), performance analysis and tuning (AWR\/statspack), migration, consolidation and appliances, especially ODA (his main projects during the last years). Prior to joining dbi services, J\u00e9r\u00f4me Dubar worked in a Franco-Belgian IT service company as Database team manager and main consultant for 7 years. He also worked for 5 years in a software editor company as technical consultant across France. He was also teaching Oracle Database lessons for 9 years. J\u00e9r\u00f4me Dubar holds a Computer Engineering degree from the Lille Sciences and Technologies university in northern France. His branch-related experience covers the public sector, retail, industry, banking, health, e-commerce and IT sectors.\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/author\/jerome-dubar\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"ODA 19.13: odacli update-dbhome raises DCS-10001 and PRGH-1153 - 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\/oda-19-13-odacli-update-dbhome-raises-dcs-10001-and-prgh-1153\/","og_locale":"en_US","og_type":"article","og_title":"ODA 19.13: odacli update-dbhome raises DCS-10001 and PRGH-1153","og_description":"Introduction While patching ODAs from 19.10 to 19.13, the update-dbhome could fail if some databases inside this dbhome are stopped or only mounted. Job would then stop with a DCS-10001:Internal error encountered: PRGH-1153 : RHPHelper call to get runing nodes failed for DB: “ARITSTDB”. How to solve this problem? Environment description My environment is composed […]","og_url":"https:\/\/www.dbi-services.com\/blog\/oda-19-13-odacli-update-dbhome-raises-dcs-10001-and-prgh-1153\/","og_site_name":"dbi Blog","article_published_time":"2022-02-28T14:13:23+00:00","author":"J\u00e9r\u00f4me Dubar","twitter_card":"summary_large_image","twitter_misc":{"Written by":"J\u00e9r\u00f4me Dubar","Est. reading time":"16 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/oda-19-13-odacli-update-dbhome-raises-dcs-10001-and-prgh-1153\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/oda-19-13-odacli-update-dbhome-raises-dcs-10001-and-prgh-1153\/"},"author":{"name":"J\u00e9r\u00f4me Dubar","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/0fb4bbf128b4cda2f96d662dec2baedd"},"headline":"ODA 19.13: odacli update-dbhome raises DCS-10001 and PRGH-1153","datePublished":"2022-02-28T14:13:23+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/oda-19-13-odacli-update-dbhome-raises-dcs-10001-and-prgh-1153\/"},"wordCount":383,"commentCount":0,"keywords":["19.13","CmdToolUtil-execute1-error1","DCS-10001","failure","odacli","Oracle database appliance","patch","patch database by RHP","PRCT-1014","PRGH-1153","update-dbhome"],"articleSection":["Database Administration & Monitoring","Database management","Oracle"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/oda-19-13-odacli-update-dbhome-raises-dcs-10001-and-prgh-1153\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/oda-19-13-odacli-update-dbhome-raises-dcs-10001-and-prgh-1153\/","url":"https:\/\/www.dbi-services.com\/blog\/oda-19-13-odacli-update-dbhome-raises-dcs-10001-and-prgh-1153\/","name":"ODA 19.13: odacli update-dbhome raises DCS-10001 and PRGH-1153 - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2022-02-28T14:13:23+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/0fb4bbf128b4cda2f96d662dec2baedd"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/oda-19-13-odacli-update-dbhome-raises-dcs-10001-and-prgh-1153\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/oda-19-13-odacli-update-dbhome-raises-dcs-10001-and-prgh-1153\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/oda-19-13-odacli-update-dbhome-raises-dcs-10001-and-prgh-1153\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"ODA 19.13: odacli update-dbhome raises DCS-10001 and PRGH-1153"}]},{"@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\/0fb4bbf128b4cda2f96d662dec2baedd","name":"J\u00e9r\u00f4me Dubar","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/efaa5a7def0aa4cdaf49a470fb4a7641a3ea6e378ae1455096a0933f99f46d6b?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/efaa5a7def0aa4cdaf49a470fb4a7641a3ea6e378ae1455096a0933f99f46d6b?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/efaa5a7def0aa4cdaf49a470fb4a7641a3ea6e378ae1455096a0933f99f46d6b?s=96&d=mm&r=g","caption":"J\u00e9r\u00f4me Dubar"},"description":"J\u00e9r\u00f4me Dubar has more than 15 years of experience in the field of Information Technology. Ten years ago, he specialized in the Oracle Database technology. His expertise is focused on database architectures, high availability (RAC), disaster recovery (DataGuard), backups (RMAN), performance analysis and tuning (AWR\/statspack), migration, consolidation and appliances, especially ODA (his main projects during the last years). Prior to joining dbi services, J\u00e9r\u00f4me Dubar worked in a Franco-Belgian IT service company as Database team manager and main consultant for 7 years. He also worked for 5 years in a software editor company as technical consultant across France. He was also teaching Oracle Database lessons for 9 years. J\u00e9r\u00f4me Dubar holds a Computer Engineering degree from the Lille Sciences and Technologies university in northern France. His branch-related experience covers the public sector, retail, industry, banking, health, e-commerce and IT sectors.","url":"https:\/\/www.dbi-services.com\/blog\/author\/jerome-dubar\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/17144","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\/45"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=17144"}],"version-history":[{"count":0,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/17144\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=17144"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=17144"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=17144"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=17144"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}