-
We did changed nothing. How to set up AES encrypted username password in DB2 client?
It all started with the connections from Goldengate to DB2 not working anymore: The DB2 administrators say “We changed nothing. Maybe you changed something? And the DB2 documentation says nothing for this error. Next email from DB2 admins “well, we did activated the option TCPALVER=SERVER_ENCRYPT and maybe that is the problem” Indeed, that was the…
-
Get history of Switchover and Failover of an Oracle database
For physical standbys, there is no DBA_* view that I know which tracks the history of switchover and failover. For Logical standby there is DBA_LOGSTDBY_HISTORY. Ways to find the information are the Dataguard Broker log – when Broker is in use -, or using the database alert log and the following grep command:
-
Goldengate 21 for DB2 on z/OS and segmentation fault
These days I’ve been trying Goldengate 21 for DB2 on z/OS (Extract). And still surprises! Last year, with Goldengate 21.6, it would simply corrupt trailfiles if the extract abended. This year, with Goldengate 21.10, After adding a new extract,the extract abends without any error or explanation. The report file would remain with this: Only in…
-
My ARDCI cheatsheet
Check last problems Create Package Purge Value for control is hours Value for purge is minutes Fix “No ADR base is set” Sometimes also “DIA-48494: ADR home is not set” Create a ${ORACLE_HOME}/log/diag/adrci_dir.mif file with: DIA-48448: This command does not support multiple ADR homes Use set home diag/xxxxx (remove the ORACLE_BASE path)
-
Opatch now obfuscates its own backups – the new “opatch util Obfuscate” option explained
With OPatch version 12.2.0.1.36 for databases (and version 13.9.4.2.11 for Middleware), a new utility was included: obfuscate. This utility was released to workaround the increased security needed around databases servers. We cannot escape having vulnerability scanners to run there. These vulnerability scanners sometimes do not distinguish between used and unused files. When patching a database,…
-
New “OPatch util DeleteInactivePatches” tool for reducing the $ORACLE_HOME size
When you are a sensible person, you patch regularly your Oracle database. After a few years, maybe you noticed that the $ORACLE_HOME increased size from new ~7 GB to …. 26 GB! Looking better, you find the culprit is the hidden directory $ORACLE_HOME/.patch_storage : Today I show how a new option from OPatch allowed me…
