Null values in not null columns on compressed partitioned table
(Doc ID 1201263.1)
Last updated on OCTOBER 17, 2019
Applies to:
Oracle Database - Enterprise Edition - Version 10.2.0.4 to 10.2.0.4 [Release 10.2]Information in this document applies to any platform.
Symptoms
On a partitioned database in a partitioned compressed table wrong values are seen:
SQL> select rowid, COL1
2 from securitydbo.T1
3 where COL1 =
4 (
5 select min(COL1)
6 from XYZ.T1
7* )
ROWID COL1
------------------ ------------------
AABBQHABKAAAOKtAAB -8.95E-116
SQL> select nvl(COL1,-999)
2 from XYZ.T1
3 where rowid='AABBQHABKAAAOKtAAB';
NVL(COL1,-999)
----------------------------
-999
or null is seen in not null column
It was detected that moving the data "fixes" the issue.
For example moving the partition or creating a table based on the partition.
created a table t1 as select * from the partition.
SQL> select COL2, COL3
2 from XYZ.T1 h
3 where COL4 = 110766
4 and COL5 in (40)
5 order by COL2
6 /
EFFECTIVE COL3
--------- -----------------
12-JAN-09 ------------>here is null
SQL>
SQL> select COL2, COL3
2 from t1 h
3 where COL4 = 110766
4 and COL5 in (40)
5 order by COL2
6 /
EFFECTIVE COL3
--------- -----------------
12-JAN-09 100
2 from XYZ.T1 h
3 where COL4 = 110766
4 and COL5 in (40)
5 order by COL2
6 /
EFFECTIVE COL3
--------- -----------------
12-JAN-09 ------------>here is null
SQL>
SQL> select COL2, COL3
2 from t1 h
3 where COL4 = 110766
4 and COL5 in (40)
5 order by COL2
6 /
EFFECTIVE COL3
--------- -----------------
12-JAN-09 100
Changes
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 |
| Changes |
| Cause |
| Solution |
| References |