Mailing List
Home
Forum Home
Oracle List - by freelists.org
Oracle on SUSE Linux - Runing Oracle on SUSE Linux
Oracle database error code ...
www.freelists.org
Subjects
ORA 12540: TNS:internal limit restriction exceeded
ORA 12838 please : Is possible to append two times to the same table befo
ORA 12838 please : Is possible to append two times to the same table before
ora 04031
ora 12500 on windows
ORA 32004: obsolete and/or deprecated parameter(s) specified
ORA 01925: maximum of 30 enabled roles exceeded
ORA 01925: maximum of 30 enabled roles exceeded
ora 12500 on windows
ORA 01650, one idea
ORA 01650
ORA 4030
ORA 12838 please : Is possible to append two times to thesametable before do
ORA 12838 please : Is possible to append two times to thesame table before d
ORA 01536
ORA 03113 end of file on communication channel
ORA 32004: obsolete and/or deprecated parameter(s) specified
ORA 00600:
ORA 00020: maximum number of processes (%s) exceeded
ORA 01925: maximum of 30 enabled roles exceeded
ORA 3113 while creating a cluster database 9201 RAC on Linux with OCFS
ora 12500 on windows
ora 12500 on windows
ora 12500 on windows
ORA 01650, one idea
ora 12500 on windows
ora 12500 on windows
ora 12500 on windows
ORA 2000 Error Using DBMS STATS GATHER SCHEMA STATS
ORA 01650, one idea
ORA 01650, one idea
ORA 01650, one idea
ORA 01650
ORA 01650
ORA 01031
ORA 4030
ORA 4030
ORA 06502: PL/SQL: numeric or value error: Bulk Bind: Truncated Bind
ORA 01722 invalid number
 
-none-

-none-

2007-09-04       - By Powell, Mark D

 Back

Alter the table adding nullable column
Populate column
alter the table modifying column to be not null
Update statistics

-- Mark D Powell --
Phone (313) 592-5148


-- --Original Message-- --
From: oracle-l-bounce@(protected)
[mailto:oracle-l-bounce@(protected)] On Behalf Of
genegurevich@(protected)
Sent: Tuesday, September 04, 2007 2:59 PM
To: oracle-l
Subject: NOT NULL vs NULL column in a fact table

Hi all

I have several medium to large fact tables to which I need to add a NOT
NULL column. In the past I would do the following:

- copy the data from the fact table to a backup table
- truncate the fact table
- add the new column to the fact table as NOT NULL
- copy the data back from the backup table to the fact table with some
predetermined default value  (say, -9) for the new column
- rebuild indices
- reanalyze the fact table.

This time however the number of the tables and the sizes are too big and
I don't think my normal process will complete within a reasonable time.
So I am now considering just adding this column as nullable, and modify
it as not null when older partitions are dropped (in a year or two or
so) and I will ask the reporting team to run the reports for this new
column only for the months starting with the one when this column was
added.

What kind of problems am I asking for?
thank you

Gene Gurevich


--
http://www.freelists.org/webpage/oracle-l


--
http://www.freelists.org/webpage/oracle-l