Skip to Main Content

SQL & PL/SQL

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Temporal validity in OTN Developer VM

Scott WesleyJan 1 2015 — edited Jan 2 2015

Hi all,

I've been playing with 12c in the supplied "OTN Developer Day VM" and it's not filtering rows, but this is unexpected according to a brief conversation on twitter.

The documentation states

  • Temporal validity is not supported with a multitenant container database (CDB).

I interpeted this as also potentially not working within the PDBs below it (if that's an appropriate terminology). I came to this conclusion because of my (only) general understanding of the 12c architecture, so the behaviour I found on the DB I wasn't surprising, and this past forum post that didn't have a conclusion, and this past twitter conversation from JLewis.

I used Tim Hall's example and found all 12 rows kept being returned and no explain plan differences when using the PERIOD FOR syntax. This happens in both the SQL Dev version that came with the VM and SQL*Plus - I thought I'd double check since inline plsql WITH wasn't recognised in SQL Dev.

temporal.png

The connect string was pmuser@pdb1

SELECT NAME,cdb FROM v$database;

| NAME | CDB |
| ORCL | YES |

show con_name

CON_NAME

------------------------------

PDB1

select * from v$version

Oracle Database 12c Enterprise Edition Release 12.1.0.1.0 - 64bit Production

Is this expected behaviour? Is it because of the way this VM is set up?

Cheers

This post has been answered by unknown-7404 on Jan 2 2015
Jump to Answer
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Jan 30 2015
Added on Jan 1 2015
10 comments
1,775 views