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_*…

ORA-01261: Parameter db_recovery_file_dest destination string cannot be translate

I was configuring an Oracle Data Guard 19c database, and when I tried to start the database, I received the following error: After some analysis, I concluded that the error was the “*.db_recovery_file_dest” parameter configured in the database. When you use a location on ASM, it is only necessary to specify the name of the disk group and not the directories inside the disk group. Knowing that I configured the parameter from : To: After the modification the pfile had the output below: Consequently, the startup worked after that: brunorsHi!…

Oracle Data Guard 19c: Fetch Archive Log FAL: Error 12154 connecting to DB_TECH1,DB_TECH2 for fetching gap sequence

I was managing and configuration an Active-Standby database running in an Oracle RAC that has two nodes when I found the following output from the alert.log: After some research, I found that the parameter FAL_SERVER was not configured right in both Primary and Standby databases. The parameter was fixed on both sides. The main issue to cause this to happen is because the multiple service names in the FAL_SERVER parameter on the Standby database were not configured correctly. The issue was that the parameter was configured as below: Instead of…

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…

Enabling Block Change Tracking in Oracle Database 12c

Post originally written at April 2, 2017 updated at October 19, 2019.   One of the possible ways of configuring to reduce costs while performing any incremental backup of a database is to enable the Block Change Tracking feature. Thus, when there is the execution of this type of backup the RMAN uses the file that was created when this feature is enabled only to save the blocks that have been changing in the database and then increasing the performance saving costs during the execution. Therefore, in this post, I…

RMAN-06217: not connected to auxiliary database with a net service name

Estava executando um duplicate para criar um Oracle Standby quando foi reportado o seguinte erro: Neste caso, como é um Duplicate from Active Database é necessário a adição de uma entrada estática no arquivo Listener.ora do banco de dados auxiliar, além de utilizar a string de conexão na execução do Duplicate tanto para o banco de dados Auxiliar como para o target. Depois reexecutei o duplicate e finalizou com sucesso: brunorsHi! I am Bruno, a Brazilian born and bred. Former Oracle ACE, Computer Scientist, MSc in Data Science, over ten…

Set Flashback Database parameters

Habilitar a funcionalide de Flashback no banco de dados é uma tarefa simples que envolve o parâmetro DB_FLASHBACK_RETENTION_TARGET e a ativação do Flashback na base de dados. Sendo assim, neste post estarei abordando a ativação desta funcionalidade . Segue abaixo o exemplo: Configuração do parâmetro DB_FLASHBACK_RETENTION_TARGET para definir o tempo de retenção a cada snapshot do Flashback: Ativação do Flashback na base de dados: Validação das configurações definidas através das views V$FLASHBACK_DATABASE_STAT e V$DATABASE:   Caso decida desabilitar o Flahsback, segue o exemplo:     brunorsHi! I am Bruno, a Brazilian born…

Configure a Fast Recovery Area

Configurar a Fast Recovery Area é uma tarefa que envolve dois parâmetros: DB_RECOVERY_FILE_DEST_SIZE e DB_RECOVERY_FILE_DEST. O primeiro basicamente determina o tamanho da Fast Recovery Area e o segundo o diretório onde os arquivos  serão gerados. Sendo isso, neste post irei mostrar a configuração desta área em um ambiente Single instance. Uma vez que, a configuração em um ambiente com Oracle Real Application Clusters (RAC) deve ser a mesma em todas as instâncias do ambiente, além de especificar a cláusula SID=’*’ . Configuração do DB_RECOVERY_FILE_DEST_SIZE: Configuração do DB_RECOVERY_FILE_DEST: brunorsHi! I am Bruno, a…

Qual o percentual da flash recovery area que está em uso no banco de dados Oracle?

É comum verificar o percentual de uso da flash recovery area (FRA) quando a mesma se encontra configurada na base de dados. Para verificar o percentual de uso da mesma, pode-se usar a V$FLASH_RECOVERY_AREA_USAGE. Com isso, segue um exemplo neste post: Verificando se a flash recovery area se encontra configurada: Note que está configurado a flash recovery area para utilizar o disk group DG_FRA e com o valor máximo de uso para 800G. Outro ponto interessante, que o valor máximo é diferente do valor total do disk group, que pode…

RMAN-05001: auxiliary filename “filename” conflicts with a file used by the target database

  I was trying to do a duplicate database with the same SID to another hostname. Then, during my action I got the error “RMAN-05001: auxiliary “filename” conflicts with a file used by the target database”. To solve this problem I added the sintax “NOFILENAMECHECK” after the “duplicate target database to” command. Below, it is showed the script that I used:   run { # Perform allocate channel allocate auxiliary channel t1 type ‘sbt_tape’    parms ‘ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)’; allocate auxiliary channel t2 type ‘sbt_tape’    parms ‘ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)’; allocate auxiliary channel t3…