I really rely on people telling me about issues they saw. And in this case, it happened twice within a few days. At OOW London, a customer came after my talk and told me about invalid objects and an incredible long recompilation time. In fact, he had to apply an OJVM patch in order to solve this. When I returned home, Jure commented on the blog about a very similar issue. I spent some time on the weekend to check it out. And I realized: There are issues with prebuilt seed databases and OJVM in 19c.… Continue reading...
I did blog about several things-to-know with DBCA (Database Configuration Assistant) in the past. And one issue came up in our internal mailing list the other day. Be aware of database options selections for PDBs in DBCA. Missing one or the other “click” may bring you in trouble later on. I blogged about this already a while ago but this was only part of a larger post: Create Multitenant Databases with DBCA – Things to Know.
Be aware of database options selections for PDBs in DBCA
When you create a custom container database with DBCA you will see this …Continue reading...
Roberto Valsania asked this question once he read my blog post about whether you have to execute
datapatch after creating a new 12c database: Do you have to execute
catbundle.sql when you create a new 11g database?
I’d bet you all are aware that Oracle Database 184.108.40.206 will go out of Waived Extended Support by end of 2018. But that doesn’t answer the question. So I did a quick experiment and created a fresh 220.127.116.11 database to answer the question.
Do you have to execute catbundle.sql when you create a new 11g database?
First of all, let me clarify …Continue reading...
Interesting things happen. And I learned (credits to Arun Gupta and others) that there is a change in Oracle Database 12.2 environments I wasn’t aware: The DBCA 12.2 does not update
/etc/oratab in GI / RAC environments. Let me give you some extra information and hints on this topic as it may cause some strange situations.
DBCA 12.2 does not update /etc/oratab in GI / RAC
Arun Gupta commented on the blog:
… Continue reading...
Another case in point. DBCA fails to update the /etc/oratab file in 12.2 when a database is created. There is no documentation of this behavior. So, I opened
When you create Multitenant databases with DBCA there are some Things to Know. And in Oracle Database 18.104.22.168’s Database Creation Assistant (DBCA) there is a common pitfall in the “Options” screen. It was grayed out in the previous release but when you choose to create a “custom” database you can select the options/components now. Be careful …
I did blog several times about the DBCA already:
- Always create databases as customer databases
- Use your own templates in DBCA when you create databases
- Does DBCA execute datapatch in Oracle Database 12.2?
- Create Container databases with less options
And …Continue reading...
Another advice regarding database creation:
Use your own templates in DBCA to create databases.
This way you can configure not only the options and components to create but also redo log layout, your set of parameters and much more. And it is less error prone than a “create database” script.
Use your own template in DBCA
Creating your own template in DBCA (Database Configuration Assistant) is quite easy and straight forward. In DBCA select “Manage Templates”:
and create a new template:… Continue reading...
I’m giving this advice to customers for many years:
When you create a fresh Oracle database ALWAYS create databases as CUSTOM databases. Via template or not doesn’t matter.
In the DBCA better use your own and wisely configured template rather than the prebuilt (we used to call them: seed) databases. The seed databases for “Data Warehouse” and “General Purpose or Transaction Processing” have all options and components included. I use them for testing from time to time.
As the upgrade duration mainly depends on the number of installed components I’d recommend to choose the components to install, and …Continue reading...
Does the Database Configuration Assistant (DBCA) execute “datapatch -verbose” in Oracle 12.2 when you create a new database?
Does DBCA in Oracle 12.2 execute
datapatch when you create new database? I was curious if this misbehavior from the previous release has been fixed. Good news: It got fixed with Oracle Database 22.214.171.124. The DBCA does execute “
datapatch -verbose” automatically now when you create a new database. In the previous release this did not happen – you had to execute it manually after creating a new database.
Quick Test Scenario
I …Continue reading...
Actually, command line upgrades are affected as well, if you do not use OS authentication. Apparently, datapatch is not able to execute in non-OS authentication mode. See MOS note 1635007.1.
You are doing a command line upgrade to Oracle Database 12c with catctl.pl – and you don’t use OS authentication allowing connections with “/ as sysdba” then datapatch.pl won’t be able to execute the SPU/PSU/BP related SQL commands as it will fail to connect to your database with an ORA-1017 (invalid username/password) error.
Bug 18361221 …Continue reading...
A few weeks ago I did blog about the DBUA (Database Upgrade Assistant) not executing ‘datapatch’ (i.e. not applying the SQL changes involved with a SPU/PSU/BP) automatically:
For DBUA, please note that this behavior DOES NOT APPLY to command line upgrades done with catctl.pl – as you can see from this somewhat disturbing messages during the upgrade in phase 65 and phase 69 (which are not errors but just informational messages for datapatch’s execution):
But afterwards I have learned that things are worse.
The same behavior is true when you create
When Oracle Multitenant was launched Roy and I amongst many other people always mentioned that the requirement of having all options in a Container Database (CDB$ROOT), and therefore also for the PDB$SEED with the immediate result that all PDBs provisioned from the PDB$SEED will have all options as well, will hinder customer adoption significantly. But this has been changed now. You can create Container Databases (CDB) with less options – it’s now supported in Oracle 126.96.36.199.
Create Container Databases (CDB) with less options – it’s now supported in Oracle 188.8.131.52
Almost all customers I have talked to in the …Continue reading...