19c: Possible ORA-00700: [PITL6] Error After Installing the 19.4 RU
(Doc ID 2675136.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 19.4.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
ORA-700: soft internal error, arguments: [PITL6] still occurs in 19.6 with Patch 29782211 applied.
The error occurs in the following scenario:
- database was upgraded from 12.2 to 19.3 and ORA-700[PITL6] appeared
- patch 29782211 was installed + db_block_checking=MEDIUM and problem disappeared
- database was upgraded from 19.3 to 19.6 to fix another issue. Fix for unpublished Bug 29782211 is already included in 19.6, but ORA-700[PITL6] appeared again.
Using the above scenario, below is what has been tested and seen in Oracle internal environment:
- first apply 19.3 RU :
$ cksum kdt.o.193
3035696456 325744 kdt.o.193
Next, apply one-off patch for 29782211 on top of 19.3 RU :
$ cksum kdt.o.29782211
3597994365 326560 kdt.o.29782211
Then, apply the patch for 19.6 RU ( which already has the fix for Bug 29782211 included) :
$ cksum kdt.o.196
3912492417 326632 kdt.o.196
==> Opatch at this point shows that both the patches for 19.6 RU and one-off for 29782211 are applied :
$ OPatch/opatch lspatches
30557433;Database Release Update : 19.6.0.0.200114 (30557433)
29782211;ORA-00700 SHOULD ONLY BE REPORTED WHEN BLOCK_CHECKING SET then explicitly rollback one-off patch for 29782211, This leaves the env with kdt.o from 19.3 RU! :
$ cksum kdt.o
3035696456 325744 kdt.o
==> Opatch should have rolled back the one-off for 29782211 before applying the 19.6 RU, but the rollback operation was skipped by the tool.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |