Re: Compatible parameter
- From: David Barbour <david.barbour1@xxxxxxxxx>
- To: sarah.satterthwaite@xxxxxxxxxx
- Date: Wed, 15 Jul 2009 16:06:40 -0400
The last time I saw v$compatseg and v$compatibility was in Oracle 9i. I
still have one 9.2.0.3 DB on Windows that has them. There might be some
DBMS package out there that would give you this information, but I have no
idea which one it might be.
On Wed, Jul 15, 2009 at 10:19 AM, Satterthwaite, Sarah <
sarah.satterthwaite@xxxxxxxxxx> wrote:
> My databases are version 10.2.0.4.x, but some of them still have
> compatible set to 10.2.0.3.0. I want to know what restricted features will
> become available if I raise the value of compatible.
>
> The following is probably from version 7, but I have not found a similar
> view in Oracle 10:
>
> Type ID Release Updated Description
> -------- ------------ ------------ -----------------------------------
> BOOTSTRP 7.0.10.0.0 7.0.12.0.0 bootstrap$
> COMPATSG 7.0.11.0.0 7.0.12.0.0 Compatibility segment
> DATAFILE 7.0.11.0.0 Data file structure
> KCBCICT 7.1.5.0.0 Cache cross-instance protocol
> LOGSTRUC 7.2.0.0.0 Log structure
> TRUNCFIX 7.2.0.0.0 truncate bug fix
> CONTROLF 7.3.0.0.0 Control file
> RCVREDO 7.3.0.0.0 Recovery redo
> REDODATA 7.3.0.0.0 Redo contents
> TEMPTS 7.3.0.0.0 7.3.0.0.0 Temporary tablespace
> TRUNCNT 7.3.0.0.0 7.3.0.0.0 truncation count
> UNDODATA 7.3.0.0.0 7.3.0.0.0 Undo contents
> UNLMTEXT 7.3.0.0.0 7.3.0.0.0 unlimited extents
>
> DISLOCK 0.0.0.0.0 Alter Table Disable Table Lock
> FORCEVSN 0.0.0.0.0 Force undo/redo versions to exist
> HASHEXP 0.0.0.0.0 Hash expressions in hash clusters
> IMPHSHFN 0.0.0.0.0 Improved hash function
> KDIBIX 0.0.0.0.0 bitmap indexes
> KDINFB 0.0.0.0.0 index support for freelist groups
> LOCKING 0.0.0.0.0 Instance locking protocol
> MULTTRIG 0.0.0.0.0 Multiple Triggers Per Type
> RDONLYTS 0.0.0.0.0 Read only tablespace
> REDOORDR 0.0.0.0.0 Redo order by SCN
> RESZDAFL 0.0.0.0.0 Resizable data files
> REUSEBRB 0.0.0.0.0 reuse index branch blocks
> UPDSNAP 0.0.0.0.0 Updatable Snapshots
>
> I am quite sure that it was generated using the following SQL:
>
> col type_id format a8 head 'Type ID'
> col release format a12 head 'Release'
> col description format a40 head 'Description' word
> col updated format a12 head 'Updated' word
> col implemented noprint
>
> break on implemented skip 2
>
> spool compatib.rep
>
> select decode (c.release, '0.0.0.0.0', '2,', '1') implemented,
> c.type_id, c.release, s.updated, c.description
> from v$compatibility c,
> v$compatseg s
> where c.type_id = s.type_id (+)
> and c.release = s.release (+)
> order by decode (c.release, '0.0.0.0.0', '2,', '1'),
> c.release, c.type_id, s.updated
> /
>
> Can someone point me to similar information in Oracle 10?
>
> Thanks,
>
> Sarah
>
> _______________________________
>
> *Sarah Satterthwaite
> *Database Administrator
> Loan Fulfillment Solutions
> *Fiserv*
> Fax: 617-498-0959
> *www.fiserv.com* <http://www.fiserv.com/>
> P Please consider the environment before printing this e-mail
>
>
>
>
Other related posts:
