{"id":8559,"date":"2016-07-13T18:20:46","date_gmt":"2016-07-13T16:20:46","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/oracle-public-cloud-patch-conflict\/"},"modified":"2016-07-13T18:20:46","modified_gmt":"2016-07-13T16:20:46","slug":"oracle-public-cloud-patch-conflict","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/oracle-public-cloud-patch-conflict\/","title":{"rendered":"Oracle Public Cloud patch conflict"},"content":{"rendered":"<h2>By Franck Pachot<\/h2>\n<p>.<br \/>\nThis morning I wanted to test a patch (18633374) in the Oracle Cloud Service. The DBaaS was created as an &#8216;Enterprise Edition Extreme Performance&#8217; which comes with all options, including multitenant option. I applied my patch. My test required to create a new tablespace but it failed with: ORA-65010: maximum number of pluggable databases created<br \/>\n<!--more--><br \/>\nThis is the kind of message we get when we try to use a feature that is not allowed in Standard Edition. But I was in Enterprise Edition here:<br \/>\nFirst thing I did was to tweet a screenshot, in case someone encountered the issue already:<\/p>\n<blockquote class=\"twitter-tweet\" data-width=\"500\" data-dnt=\"true\">\n<p lang=\"en\" dir=\"ltr\">This is not exactly my definition of &#39;EE Extreme Perf&#39;. WTF did I do? <a href=\"https:\/\/t.co\/y34JoX9mY3\">pic.twitter.com\/y34JoX9mY3<\/a><\/p>\n<p>&mdash; Franck Pachot (@FranckPachot) <a href=\"https:\/\/twitter.com\/FranckPachot\/status\/753172873708179457?ref_src=twsrc%5Etfw\">July 13, 2016<\/a><\/p><\/blockquote>\n<p><script async src=\"https:\/\/platform.twitter.com\/widgets.js\" charset=\"utf-8\"><\/script><br \/>\nAnd second thing was to try to reproduce the issue because it&#8217;s a test environment where I did things quickly and I don&#8217;t remember all what was done.<br \/>\nI create a new service in EE Extreme Performance:<\/p>\n<pre><code>\nConnected to:\nOracle Database 12c EE Extreme Perf Release 12.1.0.2.0 - 64bit Production\nWith the Partitioning, Oracle Label Security, OLAP, Advanced Analytics\nand Real Application Testing options\n<\/code><\/pre>\n<p>check that I can create additional pluggable databases<\/p>\n<pre><code>\nSQL&gt; show pdbs\n&nbsp;\n    CON_ID CON_NAME                       OPEN MODE  RESTRICTED\n---------- ------------------------------ ---------- ----------\n         2 PDB$SEED                       READ ONLY  NO\n         3 PDB                            READ WRITE NO\n         4 DEMOS                          READ WRITE NO\nSQL&gt; create pluggable database PDBNEW admin user admin identified by admin;\nPluggable database created.\nSQL&gt; create pluggable database PDBNEW1 admin user admin identified by admin;\nPluggable database created.\n<\/code><\/pre>\n<p>I tried to do the same as I did (apply patch 18633374)<\/p>\n<pre><code>[oracle@CDBA 18633374]$ dbshut $ORACLE_HOME\nProcessing Database instance \"CDB\": log file \/u01\/app\/oracle\/product\/12.1.0\/dbhome_1\/shutdown.log\n$ORACLE_HOME\/OPatch\/opatch apply\n[oracle@CDBA 18633374]$ $ORACLE_HOME\/OPatch\/opatch apply\nOracle Interim Patch Installer version 12.1.0.1.10\nCopyright (c) 2016, Oracle Corporation.  All rights reserved.\n&nbsp;\nOracle Home       : \/u01\/app\/oracle\/product\/12.1.0\/dbhome_1\nCentral Inventory : \/u01\/app\/oraInventory\n   from           : \/u01\/app\/oracle\/product\/12.1.0\/dbhome_1\/oraInst.loc\nOPatch version    : 12.1.0.1.10\nOUI version       : 12.1.0.2.0\nLog file location : \/u01\/app\/oracle\/product\/12.1.0\/dbhome_1\/cfgtoollogs\/opatch\/18633374_Jul_13_2016_11_23_28\/apply2016-07-13_11-23-28AM_1.log\n&nbsp;\nVerifying environment and performing prerequisite checks...\n&nbsp;\nConflicts\/Supersets for each patch are:\n&nbsp;\nPatch : 18633374\n&nbsp;\n        Conflict with 23192060\n        Conflict details:\n        \/u01\/app\/oracle\/product\/12.1.0\/dbhome_1\/lib\/libserver12.a:kpdbc.o\n        \/u01\/app\/oracle\/product\/12.1.0\/dbhome_1\/lib\/libserver12.a:krb.o\n        \/u01\/app\/oracle\/product\/12.1.0\/dbhome_1\/lib\/libserver12.a:krbb.o\n        \/u01\/app\/oracle\/product\/12.1.0\/dbhome_1\/lib\/libserver12.a:krbi.o\n        \/u01\/app\/oracle\/product\/12.1.0\/dbhome_1\/lib\/libserver12.a:krbabr.o\n&nbsp;\nFollowing patches have conflicts: [   18633374   23192060 ]<\/code><\/pre>\n<p><\/code><\/p>\n<p>Yes, I remember that I had to de-install an interim patch that was there in my newly created DBaaS:<\/p>\n<pre><code>\n[oracle@CDBA 18633374]$ $ORACLE_HOME\/OPatch\/opatch lspatches\n23192060;\n22674709;Database PSU 12.1.0.2.160419, Oracle JavaVM Component (Apr2016)\n22291127;Database Patch Set Update : 12.1.0.2.160419 (22291127)\n<\/code><\/pre>\n<p>Let&#8217;s do it:<\/p>\n<pre><code>\n[oracle@CDBA 18633374]$ $ORACLE_HOME\/OPatch\/opatch rollback -id 23192060\nOracle Interim Patch Installer version 12.1.0.1.10\nCopyright (c) 2016, Oracle Corporation.  All rights reserved.\n&nbsp;\nOracle Home       : \/u01\/app\/oracle\/product\/12.1.0\/dbhome_1\nCentral Inventory : \/u01\/app\/oraInventory\n   from           : \/u01\/app\/oracle\/product\/12.1.0\/dbhome_1\/oraInst.loc\nOPatch version    : 12.1.0.1.10\nOUI version       : 12.1.0.2.0\nLog file location : \/u01\/app\/oracle\/product\/12.1.0\/dbhome_1\/cfgtoollogs\/opatch\/23192060_Jul_13_2016_11_24_49\/rollback2016-07-13_11-24-49AM_1.log\n&nbsp;\nRollbackSession rolling back interim patch '23192060' from OH '\/u01\/app\/oracle\/product\/12.1.0\/dbhome_1'\n&nbsp;\nPlease shutdown Oracle instances running out of this ORACLE_HOME on the local system.\n(Oracle Home = '\/u01\/app\/oracle\/product\/12.1.0\/dbhome_1')\n&nbsp;\nIs the local system ready for patching? [y|n]\ny\nUser Responded with: Y\n&nbsp;\nPatching component oracle.oracore.rsf, 12.1.0.2.0...\n&nbsp;\nPatching component oracle.rdbms.rsf, 12.1.0.2.0...\n&nbsp;\nPatching component oracle.rdbms, 12.1.0.2.0...\nDeleting \"kscs.o\" from archive \"\/u01\/app\/oracle\/product\/12.1.0\/dbhome_1\/lib\/libserver12.a\"\nDeleting \"kststqae.o\" from archive \"\/u01\/app\/oracle\/product\/12.1.0\/dbhome_1\/lib\/libserver12.a\"\n&nbsp;\nPatching component oracle.rdbms.dbscripts, 12.1.0.2.0...\nRollbackSession removing interim patch '23192060' from inventory\nLog file location: \/u01\/app\/oracle\/product\/12.1.0\/dbhome_1\/cfgtoollogs\/opatch\/23192060_Jul_13_2016_11_24_49\/rollback2016-07-13_11-24-49AM_1.log\n&nbsp;\nOPatch succeeded.\n<\/code><\/pre>\n<p>Then I check if I&#8217;m still able to create a new PDB:<\/p>\n<pre><code>\n[oracle@CDBA 18633374]$ dbstart $ORACLE_HOME\nProcessing Database instance \"CDB\": log file \/u01\/app\/oracle\/product\/12.1.0\/dbhome_1\/startup.log\n<\/code><\/pre>\n<p>Ok, I&#8217;ll not detail the following problem for the moment:<\/p>\n<pre><code>ORA-01078: failure in processing system parameters\nLRM-00101: unknown parameter name 'encrypt_new_tablespaces'<\/code><\/pre>\n<p>During my tests I removed that encrypt_new_tablespaces parameter from the spfile to continue.<\/p>\n<pre><code>\n[oracle@CDBA 18633374]$ sqlplus \/ as sysdba\n&nbsp;\nSQL*Plus: Release 12.1.0.2.0 Production on Wed Jul 13 11:34:57 2016\n&nbsp;\nCopyright (c) 1982, 2014, Oracle.  All rights reserved.\n&nbsp;\nConnected to:\nOracle Database 12c EE Extreme Perf Release 12.1.0.2.0 - 64bit Production\n&nbsp;\nSQL&gt; create pluggable database PDBNEW2 admin user admin identified by admin;\ncreate pluggable database PDBNEW2 admin user admin identified by admin\n&nbsp;                    *\nERROR at line 1:\nORA-65010: maximum number of pluggable databases created\n<\/code><\/pre>\n<p>Ok, issue reproduced. Interim patch 23192060 is required to be able to have EE Extreme Perf able to act as an Enterprise Edition.<\/p>\n<p>No description, but from alert.log the list of bugs bundled there:<\/p>\n<pre><code>Patch Id: 23192060\nPatch Description:\nPatch Apply Time:\nBugs Fixed: 19366375,19665921,19770063,21281607,21470120,21923026,23072137<\/code><\/pre>\n<p>A lookup in MOS gives:<\/p>\n<p>19366375 &#8211; CORRECT ELAPSED TIME CALCULATION AND ADD DIAGNOSTIC FOR BUG 18920073<br \/>\n19665921 &#8211; ENABLE HCC FOR DBCS REGARDLESS OF EXTREME PERFORMANCE OPTION OR OTHER OPTIONS<br \/>\n19770063 &#8211; GET INFO ABOUT CLOUD BUNDLE INTO V$INSTANCE TABLE<br \/>\n21281607 &#8211; TRANSPARENTLY ENCRYPT TABLESPACE AT CREATION IN CLOUD<br \/>\n21470120 &#8211; CLOUD BACKPORT FOR HCC AND VERSION CHANGES<br \/>\n21923026 &#8211; ORA-600 [OLTP COMPRESSION SANITY CHECK]<br \/>\n23072137 &#8211; TDE OFFLINE ENCRYPTION SHOULD NOT BE ALLOWED CONCURRENTLY DURING MRP<\/p>\n<p>Several Oracle Public Cloud specifics here. The &#8216;encrypt_new_tablespaces&#8217; to do TDE for all new user tablespace, the HCC which is possible in any EE on the Cloud, and info about cloud edition in v$instance&#8230;<\/p>\n<p>Let&#8217;s check the edition now that I&#8217;ve de-installed the patch 19770063:<\/p>\n<pre><code>SQL&gt; select edition from v$instance;\n&nbsp;\nEDITION\n-------\nUNKNOWN<\/code><\/pre>\n<p>This value comes from x$ksuxsinst.ksuxsedition which is 0 there and the view knows only the value 8 for Enterprise Edition:<\/p>\n<pre><code>SQL&gt; select ksuxsedition from x$ksuxsinst;\n&nbsp;\nKSUXSEDITION\n------------\n           0\n&nbsp;\nSQL&gt; select view_definition from v$fixed_view_definition where view_name='GV$INSTANCE';\n&nbsp;\nVIEW_DEFINITION\n---------------\nselect ks.inst_id,ksuxsins,ksuxssid,ksuxshst,ksuxsver,ksuxstim,decode(ksuxssts,0,'STARTED',1,'MOUNTED',2,'OPEN',3,'OPEN MIGRATE','UNKNOWN'),decode(ksuxsshr,0,'NO',1,'YES',2,NULL),ksuxsthr,decode(ksuxsarc,0,'STOPPED',1,'STARTED','FAILED'),decode(ksuxslsw,0,NULL,2,'ARCHIVE LOG',3,'CLEAR LOG',4,'CHECKPOINT',         5,'REDO GENERATION'),decode(ksuxsdba,0,'ALLOWED','RESTRICTED'),decode(ksuxsshp,0,'NO','YES'),decode(kvitval,0,'ACTIVE',2147483647,'SUSPENDED','INSTANCE RECOVERY'),decode(ksuxsrol,1,'PRIMARY_INSTANCE',2,'SECONDARY_INSTANCE','UNKNOWN'), decode(qui_state,0,'NORMAL',1,'QUIESCING',2,'QUIESCED','UNKNOWN'), decode(bitand(ksuxsdst, 1), 0, 'NO', 1, 'YES', 'NO'), ks.con_id, decode(ksuxsmode,2,'READ MOSTLY','REGULAR'), \ndecode(ksuxsedition, 2, 'PO', 4, 'SE', 8, 'EE', 16, 'XE', 32, 'CS',    40, 'CE', 'UNKNOWN'), ksuxsfam from x$ksuxsinst ks, x$kvit kv, x$quiesce qu where kvittag = 'kcbwst'<\/code><\/pre>\n<p>No doubt, this meay lead to inaccesible EE features.<\/p>\n<p>When you create a DBaaS in, wich includes the patch 2319206, you get the following for EE Extreme Performance:<\/p>\n<pre><code>\nSQL&gt; host $ORACLE_HOME\/OPatch\/opatch lspatches\n23192060;\n22674709;Database PSU 12.1.0.2.160419, Oracle JavaVM Component (Apr2016)\n22291127;Database Patch Set Update : 12.1.0.2.160419 (22291127)\n&nbsp;\nSQL&gt; select edition from v$instance;\n&nbsp;\nEDITION\n-------\nXP\n&nbsp;\nSQL&gt; select ksuxsedition from x$ksuxsinst;\n&nbsp;\nKSUXSEDITION\n------------\n         256\n&nbsp;\nSQL&gt; select view_definition from v$fixed_view_definition where view_name='GV$INSTANCE';\n&nbsp;\nVIEW_DEFINITION\n---------------\nselect ks.inst_id,ksuxsins,ksuxssid,ksuxshst,ksuxsver,ksuxstim,decode(ksuxssts,0,'STARTED',1,'MOUNTED',2,'OPEN',3,'OPEN MIGRATE','UNKNOWN'),decode(ksuxsshr,0,'NO',1,'YES',2,NULL),ksuxsthr,decode(ksuxsarc,0,'STOPPED',1,'STARTED','FAILED'),decode(ksuxslsw,0,NULL,2,'ARCHIVE LOG',3,'CLEAR LOG',4,'CHECKPOINT',       5,'REDO GENERATION'),decode(ksuxsdba,0,'ALLOWED','RESTRICTED'),decode(ksuxsshp,0,'NO','YES'),decode(kvitval,0,'ACTIVE',2147483647,'SUSPENDED','INSTANCE RECOVERY'),decode(ksuxsrol,1,'PRIMARY_INSTANCE',2,'SECONDARY_INSTANCE','UNKNOWN'), decode(qui_state,0,'NORMAL',1,'QUIESCING',2,'QUIESCED','UNKNOWN'), decode(bitand(ksuxsdst, 1), 0, 'NO', 1, 'YES', 'NO'), ks.con_id, decode(ksuxsmode,1,'REGULAR',2,'READ MOSTLY','READ ONLY'), \ndecode(ksuxsedition, 2, 'PO', 4, 'SE', 8, 'EE', 16, 'XE', 32, 'CS',        64, 'CE', 128, 'HP', 256, 'XP', 'UNKNOWN'), ksuxsfam, kjidtv from x$ksuxsinst ks, x$kvit kv, x$quiesce qu, x$kjidt where kvittag = 'kcbwst'\n<\/code><\/pre>\n<h3>So what?<\/h3>\n<p>The Oracle Public Cloud is a strange PaaS: database is provisioned automatically but you can break everything you want later: you are DBA, SYSDBA and even root, as in IaaS. But it&#8217;s not because you can do everything that you should do everything. The Oracle Database software has been adapted for the Cloud and requires specific patches. After each PSU, those patches are merged to be applied over the PSU. And if you need to apply a new patch which conflicts with one of them, then you should request a merge that includes the Cloud fixes.<\/p>\n<p>Having different patches for Cloud and for on-premises is not very nice. If the goal is to have dev and test in the public cloud and prod on-premises, then we want the same software and the same patching procedures. But don&#8217;t worry, this is because the cloud arrived after 12.1.0.2 release. Next generation will be stabilized on the cloud first. We complains about &#8216;cloud-first&#8217;?<\/p>\n","protected":false},"excerpt":{"rendered":"<p>By Franck Pachot . This morning I wanted to test a patch (18633374) in the Oracle Cloud Service. The DBaaS was created as an &#8216;Enterprise Edition Extreme Performance&#8217; which comes with all options, including multitenant option. I applied my patch. My test required to create a new tablespace but it failed with: ORA-65010: maximum number [&hellip;]<\/p>\n","protected":false},"author":27,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[229],"tags":[220,135,64,96,66,223],"type_dbi":[],"class_list":["post-8559","post","type-post","status-publish","format-standard","hentry","category-database-administration-monitoring","tag-cdb","tag-cloud","tag-multitenant","tag-oracle","tag-pdb","tag-pluggable-databases"],"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>Oracle Public Cloud patch conflict - 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\/oracle-public-cloud-patch-conflict\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Oracle Public Cloud patch conflict\" \/>\n<meta property=\"og:description\" content=\"By Franck Pachot . This morning I wanted to test a patch (18633374) in the Oracle Cloud Service. The DBaaS was created as an &#8216;Enterprise Edition Extreme Performance&#8217; which comes with all options, including multitenant option. I applied my patch. My test required to create a new tablespace but it failed with: ORA-65010: maximum number [&hellip;]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/oracle-public-cloud-patch-conflict\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2016-07-13T16:20:46+00:00\" \/>\n<meta name=\"author\" content=\"Oracle Team\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Oracle Team\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"7 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\/oracle-public-cloud-patch-conflict\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/oracle-public-cloud-patch-conflict\/\"},\"author\":{\"name\":\"Oracle Team\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee\"},\"headline\":\"Oracle Public Cloud patch conflict\",\"datePublished\":\"2016-07-13T16:20:46+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/oracle-public-cloud-patch-conflict\/\"},\"wordCount\":596,\"commentCount\":0,\"keywords\":[\"CDB\",\"Cloud\",\"multitenant\",\"Oracle\",\"PDB\",\"Pluggable Databases\"],\"articleSection\":[\"Database Administration &amp; Monitoring\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/oracle-public-cloud-patch-conflict\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/oracle-public-cloud-patch-conflict\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/oracle-public-cloud-patch-conflict\/\",\"name\":\"Oracle Public Cloud patch conflict - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"datePublished\":\"2016-07-13T16:20:46+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/oracle-public-cloud-patch-conflict\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/oracle-public-cloud-patch-conflict\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/oracle-public-cloud-patch-conflict\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Oracle Public Cloud patch conflict\"}]},{\"@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\/66ab87129f2d357f09971bc7936a77ee\",\"name\":\"Oracle Team\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g\",\"caption\":\"Oracle Team\"},\"url\":\"https:\/\/www.dbi-services.com\/blog\/author\/oracle-team\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Oracle Public Cloud patch conflict - 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\/oracle-public-cloud-patch-conflict\/","og_locale":"en_US","og_type":"article","og_title":"Oracle Public Cloud patch conflict","og_description":"By Franck Pachot . This morning I wanted to test a patch (18633374) in the Oracle Cloud Service. The DBaaS was created as an &#8216;Enterprise Edition Extreme Performance&#8217; which comes with all options, including multitenant option. I applied my patch. My test required to create a new tablespace but it failed with: ORA-65010: maximum number [&hellip;]","og_url":"https:\/\/www.dbi-services.com\/blog\/oracle-public-cloud-patch-conflict\/","og_site_name":"dbi Blog","article_published_time":"2016-07-13T16:20:46+00:00","author":"Oracle Team","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Oracle Team","Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/oracle-public-cloud-patch-conflict\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/oracle-public-cloud-patch-conflict\/"},"author":{"name":"Oracle Team","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee"},"headline":"Oracle Public Cloud patch conflict","datePublished":"2016-07-13T16:20:46+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/oracle-public-cloud-patch-conflict\/"},"wordCount":596,"commentCount":0,"keywords":["CDB","Cloud","multitenant","Oracle","PDB","Pluggable Databases"],"articleSection":["Database Administration &amp; Monitoring"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/oracle-public-cloud-patch-conflict\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/oracle-public-cloud-patch-conflict\/","url":"https:\/\/www.dbi-services.com\/blog\/oracle-public-cloud-patch-conflict\/","name":"Oracle Public Cloud patch conflict - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2016-07-13T16:20:46+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/oracle-public-cloud-patch-conflict\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/oracle-public-cloud-patch-conflict\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/oracle-public-cloud-patch-conflict\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Oracle Public Cloud patch conflict"}]},{"@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\/66ab87129f2d357f09971bc7936a77ee","name":"Oracle Team","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g","caption":"Oracle Team"},"url":"https:\/\/www.dbi-services.com\/blog\/author\/oracle-team\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/8559","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\/27"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=8559"}],"version-history":[{"count":0,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/8559\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=8559"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=8559"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=8559"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=8559"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}