You have a lot on your plate, so database patches tend to have a low-priority on your to-do list. After all, there are only so many hours in the day. However, you’re not going to be able to wait on patching your Oracle databases that are 184.108.40.206 or 220.127.116.11 and older (Oracle 10.2 and older are unpatched for this issue).
Why This Patch is Important
This patch impacts the System Change Number, or SCN, that Oracle calculates by looking at the number of seconds since 1988. It increases the maximum SCN limit for that database, which becomes relevant when you use database links.
A database link syncs the SCN between each database. If you have a database that is not patched, then the SCN will not go up high enough to sync with the patched database. You end up with a database link connection that fails in this situation, which is represented through run-time errors. After you patch, the databases sync and you have a higher transaction rate for these databases.
Even if your current transaction rate doesn’t get close to the unpatched max, it’s better to update the databases now so you don’t run into problems when you have greater demands in the future.
Put June 23rd, 2019 on Your Calendar
This is the deadline for applying the patch to your Oracle database before you could start running into problems with the SCN.
If you don’t use database links, you won’t be impacted by this issue but it might be time to consider upgrading your older Oracle databases. Data breaches happen far too often to have your data stored in a vulnerable location that’s no longer receiving security updates. You also miss out on new bug fixes, features and other perks.
When you upgrade your Oracle databases, you’re improving security for all of the systems that rely on those resources, as well as bringing in performance improvements that were implemented in recent Oracle database versions.
Get help with Oracle database patching, upgrading and migration with Datavail’s data and technology experts who deliver the services and support you need to get more out of your databases.
Subscribe to Our Blog
Never miss a post! Stay up to date with the latest database, application and analytics tips and news. Delivered in a handy bi-weekly update straight to your inbox. You can unsubscribe at any time.
Most people will encounter this error when their application tries to connect to an Oracle database service, but it can also be raised by one database instance trying to connect to another database service via a database link.
Imagine over 100 logins on the source server, you need to migrate them to the destination server. Wouldn’t it be awesome if we could automate the process?