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…
Author: brunors
*The views expressed here are my own and do not represent those of my employer.*
Hello, I’m Bruno — a dual citizen of Brazil and Sweden. I bring a global perspective shaped by experiences in both South America and Europe, with a strong focus on collaboration and innovation across cultures. I am a Computer Scientist, PhD Candidate in Information and Communication Technologies, focusing on Data Science and Artificial Intelligence, and hold dual Master’s degrees in Data Science and Cybersecurity. With over fifteen years of international experience spanning Brazil, Hungary, and Sweden, I have collaborated with global organizations such as IBM, Playtech, and Oracle, as well as contributed remotely to projects across multiple regions. My professional interests include Databases, Cybersecurity, Cloud Computing, Data Science, Data Engineering, Big Data, Artificial Intelligence, Programming, and Software Engineering, all driven by a deep passion for transforming data into strategic business value.
12C : A simple approach to index monitoring
Index tracking is useful to know if the index is being used or not and then delete it. In this post I’ll be creating a table called techdatabasket_customers, an index called techdatabasket_index and later activating index monitoring through the command “ALTER INDEX <index_name> MONITORING USAGE;” to finally use the view dba_object_usage (In previous versions of 12.1, the view was called V$OBJECT_USAGE) to get the information in the USED field with the value “YES” meaning that the index is being used and “NO” meaning that the index is not being…
Creating a CDB Without Using Oracle Managed Files
The following procedure below aims to create an Oracle 12c database by command line with only the CDB by enabling the ENABLE_PLUGGABLE_DATABASE = TRUE parameter for a possible creation of PDBs in the future. Therefore, it follows the procedures: Creating database directories and granting permissions to the oracle user: Creating the database pfile with the ENABLE_PLUGGABLE_DATABASE parameter set to TRUE, this way it will be possible to create PDBs in the future: Setting the environment variable and initializing the database in NOMOUNT status: Creation of the database: …
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…
AWARDS: “Top 60 Oracle Blogs post” AND ” Oracle ACE Associate “
02/06/2011, esta foi a data que iniciei minha carreira como Administrador de Banco de Dados Oracle. 18 anos. Primeiro emprego e extramamente motivado para crescer profissionalmente e ajudar minha família. Em 2012, criei um blog motivado pelas postagens dos meus estudos diários e também pela motivação de ser cada vez melhor. Agora, praticamente 6 anos depois, especificamente em 14 de Outubro, o meu blog recebeu o reconhecimento ” Top 60 Oracle Blogs post” da empresa Feedspot pelo próprio fundador da empresa, Mr. Anuj Agarwal e, no dia 30 de Outubro,…
‘Oracle XML Database’ package needs to be properly re-created
O Oracle XML DB é uma feature que possui várias tecnologias que pode auxiliar o DBA quando o assunto é high-performance. No entanto, em alguns casos, seja por um mal upgrade executado anteriormente ou por qualquer outra atividade esta feature se torna inválida e para isso necessitamos executar os seguintes comandos: Oracle XML DB is a feature that has several technologies that can help the DBA to improve high performance. However, in some cases, due to an incorrectly updated executed or any other activity, this resource becomes invalid and…
ORA-28040: NO MATCHING AUTHENTICATION PROTOCOL EXCEPTION AFTER UPGRADE FROM 11G TO 12C
After upgraded an Oracle database from 11.2.0.4 to 12.2.0.1 I receive the error “ORA-28040: No matching authentication protocol exception” during one of our applications tried to connect to this database. This is due to the fact that in version 11G the parameter SQLNET.ALLOWED_LOGON_VERSION_SERVER had the default value 8 while in version 12c it is 11. Knowing this, after changing the value of the parameter in the sqlnet.ora file the problem has been solved. Portuguse / Português Depois de atualizar um banco de dados Oracle 11.2.0.4 para 12.2.0.1 eu recebir o…