12c bug - PDB spfile parameter showing into v$spparameter with wrong con_id

When changing a parameter in spfile of a pluggable database, the change is visible in V$spparameter view for PDB con_id (5), but with wrong con_id (0). This is a known bug:

Bug 16682595  SPFILE / V$SPPARAMETER problems with PDB

SQL> show con_name

CON_NAME
------------------------------
PDB3 

SQL> alter system set ddl_lock_timeout=30 scope=both;

SQL> select con_id, name, value from v$spparameter where name='ddl_lock_timeout' ;

    CON_ID 
----------
NAME
-----------------------------
VALUE
-----------------------------
         0
ddl_lock_timeout
30

Connected to the PDB we check the value of the parameter and the con_id from v$parameter view: 

SQL> show parameter ddl_lock_timeout;

NAME                                 TYPE        VALUE
------------------------------------ ----------- ----------------------
ddl_lock_timeout                     integer     30

SQL> select con_id, name, value from v$parameter where name='ddl_lock_timeout';

    CON_ID
----------
NAME
----------------------------
VALUE
----------------------------
         5
ddl_lock_timeout
30

12c - Operation 227 succeeded.

C:\Users\oracle12c>sqlplus / as sysdba

SQL*Plus: Release 11.2.0.4.0 Production on Mon Apr 27 18:59:36 2015

Copyright (c) 1982, 2013, Oracle.  All rights reserved.


Connected to:
Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production
With the Partitioning, OLAP, Advanced Analytics and Real Application Testing opt
ions

SQL>
SQL>
SQL>
SQL> select name, open_mode from v$pdbs;

NAME                           OPEN_MODE
------------------------------ ----------
PDB$SEED                       READ ONLY
PDB1                           MOUNTED
PDB2                           MOUNTED
PDB3                           MOUNTED

SQL> alter pluggable database all open;

Operation 227 succeeded.

SQL> alter pluggable database pdb1 save state;

Operation 227 succeeded.

SQL> alter pluggable database pdb3 close;

Operation 227 succeeded.

This issue is generated by the client I used (11.2.0.4) to connect to database (12.1.0.2)