Using Oracle Data Guard with Oracle Data Guard Broker? Disable your LOG_ARCHIVE_n parameters and reconfigure your Oracle Data Guard Broker settings

When configuring Oracle Data Guard Broker to be used in your Oracle Data Guard configuration, you must disable the parameter log_archive_dest_n to Null at Primary and Standby before starting your setup. Otherwise, you are going to receive the following error on your Data Guard configuration: “Error: ORA-16698: LOG_ARCHIVE_DEST_n parameter set for object to be added”. It’s effortless to modify this parameter, and an example on an Oracle RAC database it is as it is below on the Primary and Standby databases: #Primary: #Standby: The idea is the Broker control LOG_ARCHIVE_*…

Services Summary…Service “86b637b62fdf7a65e053f706e80a27ca” has 1 instance(s). Don’t freak out!

Those who install and create a database running in the Oracle release 12.2.0.3 launched by Oracle Corporation in February 2019 might get surprised about the unknown hash services shown in the listener due to the PDB databases. I must say that my first thought was, “What?????”. Write in the comments how was yours. My first information is: don’t freak out! This service was introduced by the Oracle Database release 12cR2 due to the possibility of creating a PDB as a Proxy PDB. Thus, what you can see of new in…

Unexpected ‘supportedOSCheck’ while installing Oracle database 19c in silent mode on Oracle Linux 8.2 64-bit (x86-64)

As usual, I checked all the pre-requisites for the installation of Oracle Database 19c on Oracle Linux 8.2. However, I didn’t expect to be surprised with the below error at the very beginning: I thought:” Did I miss Oracle Linux 8 isn’t supported with Oracle 19c?”. I was sure that I checked this before so I started googling around again and then I found that this error has happened in previous releases as 12.1 due to the fact that it does not contain Pre-req checks specific to OL /RHEL 8…

Oracle Database 19c doesn’t support OL6 – /lib64/libc.so.6: version `GLIBC_2.14′ not

One of the pre-requisite before installing any database software is to check if the platform that you are going to install your database in is supported by that platform. For instance, if you are going to install Oracle database on Linux, it is recommended to check the “Database Installation Guide for Linux” and check the operating system checklist. On April 25th 2019, Oracle database 19c became available to downloaded from Oracle.com. Regardless of the new features, software libraries and so on one difference from the previous release made me think…

Warning: PDB altered with errors. How PDB_PLUG_IN_VIOLATIONS view can help you?

I was cloning a PDB from another PDB when I faced this error: Then I was wondering what shall I do now once the command is “show errors” but replied “No errors.”, and it didn’t give any clear message that was different from “Warning: PDB altered with errors.”. I came to a realization after doing some research and I found that the view pdb_plug_in_violations and found out the reason of the warning and it was because my database has Transparent Data Encryption configured and was missing the keys from the…

“ORA-65011: Pluggable database does not exist” while cloning a NON-CDB into a PDB

I was cloning an Oracle NON-CDB database to a PDB when I get the following error: I checked and the connection to the DB_LINK created to access the NON-CDB was OK: This error happens because you are probably trying to clone a CDB database to a PDB and this can be queried using SQL below: When a database is created as a CDB it can not be a PDB and vice versa. So, I suggest creating a new database, really a NON-CDB, and do the operation again. Eu estava clonando…

ORA-65093: multitenant container database not set up properly

I was creating a CDB database when I got the following error: Why did I get this error? Because I forgot to add the enable_pluggable_database parameter with the value to TRUE in the parameter file. Therefore, Oracle understood that I was creating a NON-CDB database instead of a CDB. After I added the parameter in the parameter file, it was possible to continue with the creation of the CDB database. enable_pluggable_database parameter with the value to TRUE Restating the instance with the new parameter:   Creating the CDB database again:…

Fixing PRVF-0002 : Could not retrieve local node name

I was installing Oracle stand alone 12c while during the installation I got the following error: This error occurs because Oracle did not find the server name during the lookup operation. So how to solve this? The answer is simple. Just add the server name in the /etc/ hosts (as the example in the picture below: 192.168.56.71 dbdg.localdomain dbdg) file with the root user and then proceed with the installation:   Estava instalando o Oracle stand alone 12c quando durante a instalação obtive o seguinte erro: Este erro acontece porque…

ORA-12528: TNS:listener: all appropriate instances are blocking new connections

If you are doing a duplicate (except an Active duplication) to create a Standby database and received the following error below: You should add the entry “(UR = A)” in tnsnames.ora for the target and source database. (Feature of Oracle 10g). As the example below in the tnsnames.ora: Se você estiver fazendo um duplicate (exceto um Active duplication) para criar um banco de dados do tipo Standby e recebeu o seguinte erro abaixo: Você deverá adicionar a entrada “(UR = A)” no tnsnames.ora para o aliás dos bancos de dados…

Inventory load failed… OPatch cannot load inventory for the given Oracle Home.

                Por alguma razão quando o $ORACLE_HOME é removido do inventário, o DBA irá encontrar o erro “Inventory load failed… OPatch cannot load inventory for the given Oracle Home” quando se tentar executar o utilitário do opatch (localizado em $ORACLE_HOME/OPatch/opatch) para verificar os patches aplicados no ambiente de banco de dados Oracle. Com isso, neste post estarei exemplificando como resolver este problema. Causa raíz: Por alguma razão o $ORACLE_HOME foi removido do inventário. Solucao: Simplesmente adicione novamente o ORACLE_HOME ao inventário do banco…