I have not yet had time to build a test case and prove this out, but I wanted to document one last bug that we found so far in our 126.96.36.199 to 19c upgrade. We tried copying a bunch of partitioned tables on our source database to the new one using Datapump Import (impdp) over a database link. We got a boatload of errors like this:
ORA-00600: internal error code, arguments: [qesmaGetPamR-NullCtx],
There are many Oracle bugs like this, but they seem to have been fixed in 188.8.131.52. For example:
Bug 12591399 – ORA-600[qesmagetpamr-nullctx] / ORA-14091 with distributed query with local partition table (Doc ID 12591399.8)
Puzzling. We ended up just exporting to disk and that has worked well so no big deal, but I wonder if this is some sort of recession of a fixed bug.
Anyway, I am off for the rest of the year. This should be my last post unless I mess with Nethack over vacation and post something about that. I hope everyone out there has a good new year.
P.S. Created a simple partitioned table with 2 partitions and 100 rows in each one. I got the error importing over a link from 184.108.40.206 to 19c. It worked perfectly going from 220.127.116.11 to 18.104.22.168. Same source table. Parfile:
$ cat bobby_link_test.par userid=MYUSER/MYPASSWORD JOB_NAME=BOBBY_TEST DIRECTORY=BOBBY_DIR NETWORK_LINK=MYLINK LOGFILE=bobby_link_test.log tables=TEST
CREATE TABLE test ( PART_COL NUMBER, data NUMBER ) PARTITION BY RANGE (PART_COL) ( PARTITION PART_COL_1 VALUES LESS THAN (100), PARTITION PART_COL_2 VALUES LESS THAN (200) ) ;
PPS. Works fine going from 22.214.171.124 to 18c. Going to try a different 19c database just to be sure it isn’t the one that has the problem.
PPPS. Definitely a 19c bug. It fails on two different 19c databases but not on 18c. In every case source is same 126.96.36.199 database and same small partitioned table.
1/6/2020 update – created SR. Trying to be a good Oracle community citizen.
Bug is already fixed. Patch 30321076. Oracle is way ahead of me!