In June 2016 I posted the following BUG: Bug on Oracle 12c Multitenant & PDB Clone as Snapshot Copy, promising to post an update once the version 12cR2 is available, because in the service request, originally opened with the version 188.8.131.52 Oracle stated that the bug would be fixed in 12cR2.
I was so impatient, that just few hours after the general availability of the Oracle Database 12c Release 2 I created a new cluster and tested the resolution.
For the record, it states that the resolution of this bug is important for one of my clients, where we have implemented the snapshot PDB on the application development lifecycle.
So let’s see if the bug has been fixed!
SQL*Plus: Release 184.108.40.206.0 Production on Wed Mar 1 21:06:54 2017 Copyright (c) 1982, 2016, Oracle. All rights reserved. Connected to: Oracle Database 12c Enterprise Edition Release 220.127.116.11.0 - 64bit Production SQL> CREATE PLUGGABLE DATABASE PDBACFS1_SNAP1 from PDBACFS1 SNAPSHOT COPY; Pluggable database created. SQL> ALTER PLUGGABLE DATABASE PDBACFS1_SNAP1 OPEN instances=all; Pluggable database altered. SQL> select CON_ID, NAME, OPEN_MODE, SNAPSHOT_PARENT_CON_ID from v$pdbs where NAME in ('PDBACFS1','PDBACFS1_SNAP1'); CON_ID NAME OPEN_MODE SNAPSHOT_PARENT_CON_ID ---------- ------------------- ---------- ---------------------- 5 PDBACFS1 READ WRITE 6 PDBACFS1_SNAP1 READ WRITE <-- This should be 5 but is NULL 2 rows selected.
To a certain point of view progress has been made, in version 18.104.22.168 the column SNAPSHOT_PARENT_CON_ID was always zero (0) now is null!
I’m sorry for my customer, I’ll keep
testing hoping …
2 thoughts on “New Oracle version (22.214.171.124) old BUG!”
hello, have you had any updates on this bug? do you know if this has been resolved?
Sorry, no update on the subject!