Recently, I undertook the task of upgrading an Oracle database from version 19.10 to 19.18. As the process progressed, I began to encounter a series of errors that were consistently appearing in the alert log. After diving deep into the issue, it was discovered that running a series of scripts after the upgrade would effectively solve the problem. Furthermore, it was necessary to recompile the invalid packages. Without any delay, I proceeded to execute the specified scripts and recompile the invalid objects. And voila, problem solved! I hope this post…
Category: Oracle Database Errors
Enable online status for all Oracle database datafiles
I have executed a database migration by transitioning from a physical active data guard to a primary database. Subsequent to the migration, I observed that several data files were offline, as evidenced below: Modifying the status of each individual data file would require a substantial amount of time. To provide an illustrative example: In order to streamline the operation, I devised a PL/SQL procedure that effectively places all data files offline across all tablespaces within the database, subsequently modifying their statuses to online, as illustrated below: I hope this post…
Index WRH$_SYSMETRIC_HISTORY_INDEX Status Unusable After Database Upgrade From 12c To 19c
Upgrading Oracle database 12.2 to 19.10 came with some surprises, and one of them was the invalid status of the index WRH$_SYSMETRIC_HISTORY_INDEX owned by the user SYS. Rebuilding the index helped only temporarily, so I decided to recreate the index by following the procedure below: — Confirmation of the invalid index: — Action plan: For more information, please check the following MOS notes below: Index WRH$_SYSMETRIC_HISTORY_INDEX Status Unusable (Doc ID 2426391.1)WRH$_SYSMETRIC_HISTORY_INDEX Index Does Not Get Partitioned After Database Upgrade From 12c To 19c (Doc ID 2777641.1)Index WRH$_SYSMETRIC_HISTORY_INDEX Status Unusable (Doc…
Bug ORA-38881 during “drop tablespace” even though there is NO Guaranteed Restore Point (GRP) – Fixed in version 19.17
I just upgraded one Oracle Database system from 12.2 to 19.10. I was happy with the result until one database procedure started to fail with the message “ORA-38881: Kan inte radera tabellutrymmet TECH_29102_9292 i den primära databasen pga. garanterade återställningspunkter.” . For those unfamiliar with the Swedish language, this is the same error message as “Oracle Error ORA-38881: Cannot drop tablespace string on primary database due to guaranteed restore points.”. I started doing some investigation until I found that there is a BUG:14163359 fixed on version 19.17 of the Oracle databases. And…
Rebuilding Oracle Partitioned Index- Solving “ORA-14086: a partitioned index may not be rebuilt as a whole”
It is known that Oracle has two types of partitioned Indexes: Local and Global Partitioned Index. I will only cover some of the specifications that explain their differences. However, according to the VLDB and Partitioning Guide release 21c, “Partitioning is possible on both regular (heap organized) tables and index-organized tables, except for those containing LONG or LONG RAW columns. You can create nonpartitioned global indexes, range or hash partitioned global indexes, and local indexes on partitioned tables.”. Furthermore, while creating a local index, the database constructs the index, which is…
RMAN-04006: error from auxiliary database: ORA-01017: invalid username/password; logon denied when Primary and Standby have the same password for the password file
“Opinions expressed are solely my own and do not express the views or opinions of my employer.” I was creating a standby database and had the intention of using an active duplicate to copy the data from the primary database to the standby when I had the following error: I did all the ordinary checklist by checking if the password file on the standby file had the same password as the primary database and also by checking if the “Password file:” option configured on the srvctl “srvctl config database -d…
19c datapatch hangs on “Installing patches…”
“Opinions expressed are solely my own and do not express the views or opinions of my employer.” I upgraded a database from 12.1 to 12.2, from 12.2 to 19.3, and then from 19.3 to 19.15 on an environment with Oracle Restart (HAS). However, after successfully applying the patch and the environment running 19.15, the datapath hanged on the “Installing patches…” part of the script followed by the error ” Died at $ORACLE_HOME/rdbms/admin/catcon.pm line 18217″ after a while. Follow below an example of the description above: The solution to it was…
ORA-00609: could not attach to incoming connection ORA-12637: Packet receive failed
I upgraded an Oracle RAC database from 12c to 19c. After a while, I identified that some jobs were having problems running. Therefore, I investigated and found out about the new default feature on the 19c client database that requires tests if Out of Bound breaks are allowed. Thus. Follow below the steps to handle this: The first step was to check the alert.log, and the errors messages were as below: I have also checked traces to understand more about the error, and this is what looked like: From now,…
Oracle Data Guard 12c: ORA-01110: data file 0000: ‘$ORACLE_HOME/dbs/UNNAMED0ZZZ’
“Opinions expressed are solely my own and do not express the views or opinions of my employer.” Oracle Data Guard is a great Oracle product that ensures high availability, data protection, and disaster recovery for enterprise data. However, as with any other product, sometimes there are some issues that appear and it is needed to be solved. Therefore, the post today will be about the error “ORA-01110: data file 0000: ‘$ORACLE_HOME/dbs/UNNAMED0ZZZ’”. Many causes can lead to this error but one that I can point out is when the primary database…
ORAPWD : Password complexity failed for SYS user
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…