Skip to main content

Invisible Column feature in Oracle 12c

Invisible Column feature in Oracle 12c


Oracle 12c allows a coulnm to be invisible. Invisible coulnm are considered only when they are explicitly referred, otherwise they are ignored for queries and DML operations. Sometimes it requires to hide particualr column from developers thus they can not include these data in reports.
You can make a column visible or invisible whenever required using ALTER TABLE command:

CREATE TABLE INV_EMP (EMP# NUMBER(4), SALARY NUMBER(8,2) INVISIBLE)
INSERT INTO INV_EMP (EMP#,SALARY) VALUES (101, 6000);
INSERT INTO INV_EMP VALUES(102);
SQL> select * from INV_EMP;
      EMP#
-----------
      101
      102
SQL> select EMP#,SALARY from INV_EMP;
      EMP#       SALARY
----------       -------------
      101        6000
      102
SQL> ALTER TABLE INV_EMP MODIFY (SALARY  VISIBLE);
SQL> select * from INV_EMP;
      EMP#      SALARY
----------      -------------
      101       6000
      102
You can do same for view as you are doing for table column:
SQL> create or replace view INV_EMP_VIEW (EMP#, SALARY INVISIBLE) as select EMP#, SALARY from INV_EMP;

You can not make a table or its whole column invisible. For Example the above table having two column one hidden one visible.
If you try to invisible both then you will get the error:

SQL> alter table INV_EMP (salary invisible);
alter table inv_emp (salary invisible)
            *
ERROR at line 1:
ORA-54039: table must have at least one column that is not invisible.

Note: *. INVISIBLE columns are not supported in external tables, cluster tables, or temporary tables.
          *. You cannot make a system-generated hidden column visible.

Comments

Popular posts from this blog

Tablespace Management using Toad

You can view all of your tablespace information using toad tablespace screen from Database –> Administer –> Tablespaces Here each table describes different detailed information across all the tablespaces in database. If you open this screen from the toad DBA module then you are also able to see the “space history” and “IO history” tab along with Files, Free space, object, Fragmentation. With these tab you are able to able perform space monitoring and planning steps. These tab permits you check graphically space and IO usage over time. Through this way DBA are also able to estimate ‘Object size’ based on this estimation. From the below “alter tablespace” tab you can §          Modify the tablespace and datafile size. §          Add new datafile to the tablespace.

Import Excel Data into Oracle using Oracle form Button

Import Excel Data into Oracle using Oracle form Button 1. Create a button on the form with the name "IMPORT_EXCEL" and write a pl/sql on "WHEN BUTTON PRESSED" trigger. BEGIN IF :System.Cursor_Block<>'GL_DAILY_COMPOUND_HEADER' THEN   Go_Item('GL_DAILY_COMPOUND_HEADER.V_DATE'); END IF; IF :System.Mode = 'NORMAL' AND :System.Record_Status IN ('NEW','INSERT') THEN   IMPORT_EXCEL_PROC;   ---Form procedure ELSE  MESSAGE('Import allowed only for new entry!!!');  MESSAGE('Import allowed only for new entry!!!'); END IF; END; 2. Now write the procedure "IMPORT_EXCEL_PROC" into the program unit. Don't forget to create required table and folder for procedure IMPORT_EXCEL_PROC PROCEDURE IMPORT_EXCEL_PROC IS application    OLE2.Obj_Type; workbooks      OLE2.Obj_Type; workbook       OLE2.Obj_Type; worksheets      OLE2.Obj_Type; worksheet       OLE2.Obj_Type; cell      

Changing National Character Set AL16UTF16 to UTF8

Changing National Character Set AL16UTF16 to UTF8 The national character set is used for data that is stored in table columns of the types NCHAR, NVARCHAR2, and NCLOB.  In contrast, the database character set is used for data stored in table columns of the types CHAR, VARCHAR2 and CLOB. Like the database character set, the national character set is defined when the database is initially created and can usually no longer be changed, at least not easily or without involving quite a lot of work (export, recreate database, import). Except when creating the database, where the national character set is defined explicitly, it can change implicitly even when upgrading the database from Oracle8i to Oracle9i (or Oracle10g). You require SYSDBA authorization to change the national character set. Changing the national character set means changing an Oracle Dictionary entry, but no data is changed.  $sqlplus /nolog SQL> CONNECT / AS SYSDBA SQL> Select property_value fro