ERROR:
Format: ORA-600 [qertbGetPartitionNumber:qesma2] [a] [b] [c] [d] [e]
oracle 11g adg rac从库查询分区表bug
------------------------------------------------------------------------
SUGGESTIONS:
If the Known Issues section below does not help in terms of identifying
a solution, please submit the trace files and alert.log to Oracle
Support Services for further analysis.
Known Issues:
You can restrict the list below to issues likely to affect one of the following versions by clicking the relevant button:
NB Prob Bug Fixed Description IIII 18899974 11.2.0.4.170718, 12.1.0.2.161018, 12.2.0.1 ORA-600 [kcbgtcr_13] on ADG for SPACE metadata blocks and UNDO blocks II 13812031 11.2.0.2.BP19, 11.2.0.3.6, 11.2.0.3.BP12, 11.2.0.4, 12.1.0.1 Wrong results /ORA-600 from query/DML on partitioned table
- '*' indicates that an alert exists for that issue.
- '+' indicates a particularly notable issue / bug.
- See Note:1944526.1 for details of other symbols used
- -----------------------------------------------------------------------------
如果是已经安装了170718补丁的话，则可能是命中了Bug 19614585
根据 bug 1961458 的文档描述，受影响的版本
---
~Versions BELOW 12.2
~Active Data Guard (ADG)
~RAC (Real Application Clusters) / OPS
~Partitioned Tables
~Read Only Database
~Physical Standby Database / Dataguard
~SELECT
-----------------------------------------------
This bug is only relevant when using Real Application Clusters (RAC) and Partitioned Tables
This problem is caused by the fix of bug 15969429. If the fix of bug 15969429 is present (which is the case of 11.2.0.4.0 and 12.1.0.1) and if running a query against a PARTITION object on a RAC Active Dataguard (ADG) Physical Standby database causes Wrong Results or errors like: ORA-600 [kksgaGetNoAlloc_Int0] ORA-600 [qesmaGetIdxSeg2] ORA-600 [kdsgrp1] ORA-600 [12406] ORA-7445 [kqrLocalInvalidateByHash] ORA-7445 [kslgetl] ORA-8103 ORA-1555 and the same query runs without problems on the primary database, then it could be a case of this bug. As an example of wrong results, for a RAC ADG database with two instances, the ADG instance 1 may see a different number of rows for the PARTITION table than ADG instance 2. Note: This patch needs to be installed on both the primary and standby. It is also advised to apply the fix for similar bug 19689979 Cf. bug:28222735: If _part_access_version_by_number=FALSE then it may appear as if this fix is not working, so make sure _part_access_version_by_number=TRUE (default).
