I was creating an Oracle Data Guard environment when I got the following error while I was creating the password file: And the reason behind this error is that Oracle Corporation has been working hard to ensure more security in their database releases. Therefore, from the Oracle database release version 12.2, Oracle has changed some policies within passwords, and due to it, no longer weak passwords are allowed unless you want to. The new requirements about passwords that are allowed can be found in the chapter “3 Configuring Authentication” of…
Year: 2021
Implementing Oracle Data Guard Broker 19c in an Oracle Standby RAC Database
Before I start, I would like to do a disclaimer and say that this is a procedure that might help you. However, I do not recommend you test it in a production environment before reading Oracle documentation and notes to understand the concepts that I will write here. Oracle Data Guard Broker is a utility that can help you manage your Oracle Data Guard. Among many benefits of using this utility, I highlight that while using it, it will not need manual intervention to recover the databases or eventually a…
Oracle Data Guard 19c: rfs (PID:11969): Possible network disconnect with primary database
One of the essential things in the configuration of Oracle Data Guard and Oracle Data Guard Broker is where the file tnsnames.ora is placed, which by default, from some other early releases of 19c it has been defined at $ORACLE_HOME/network/admin. However, in one of the environments that I was providing some job as a consultant, I could see the following outputs from the Oracle Data Guard broker utility : Just a brief explanation on the output above to make it easier to understand from now on: Standby database has db_unique_name…
Active Data Guard feature: since 11g keeping your Oracle Data Guard open in read-only mode, and still applying redo information
The active Data Guard feature is not something new. It has been on since Oracle Database version 11g, but it is the first time I am writing about it on my blog (I think so!), and I think it is always nice not to miss anything on our career path. So here we go! Before Oracle Database version 11g, it was already possible to open Oracle Data Guard in open mode. Still, there were some complications, e.g., when it was needed to recover the standby database. Thinking on that, Oracle…
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_*…
Oracle Enterprise Manager 13c release 4- How to add a target host and agent manually
Enterprise Manager tool in its release 13.4 has been up since January 2020 (ORACLE1) and its current release 13.5 since April 2021 (ORACLE2). Currently, I have been involved in a project where I had to install both Oracle Management Repository (Management Repository) (ORACLE3) following by the installations of the agents in several servers. Therefore, in this post, I will show how you can deploy an agent release 13.4 in a server that runs Oracle Database after configuring an Oracle Management Repository in another server. Thus, one of the primary steps…
PLS-00201: identifier ‘DBMS_JAVA.GRANT_PERMISSION’ must be declared
I was doing the deployment of data in one database when I got the following error message: After some researches, I found that the Oracle Database Java Packages component was invalid in the database as below: And the documentation that helped to find out it was (Doc ID 397770.1) and (Doc ID 2314363.1). This documentation helps you identify invalid components in the registry of your database and recreate this component in case one of them is with the INVALID status. After the procedure of creating any invalid features again, the…
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!…
DB_UNKNOWN directory created after an attempt of copying a pwfile to ASM
I was trying to copy a password file from a file system to the ASM. Every time I tried to copy this file, I noticed that the directory named “DB_UNKNOWN” was created. This error usually happens when the database unique_name (resource) is not configured into the CRS and the output can be seen as below: To fix this issue, you must use the “–dbuniquename” clause while copying a file from disk to the ASM: I hope that this post helps you! brunorsHi! I am Bruno, a Brazilian born and bred.…
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…