You need to add new partitions and drop old ones as time moves on. Oracle can't just suddenly shift rows from one partition to another just because the system clock has advanced to the next day. We have a table that is partitioned into months. At the end of each month, we drop the oldest partition, then add the partition for the next month. Jay -----Original Message----- From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of John Dunn Sent: Wednesday, January 19, 2005 8:32 AM To: Oracle-L@xxxxxxxxxxxxx Subject: Question re range partioning tables I have a table which has a date column I would like to use for range partitioning. However, looking at the documentation examples it appears necessary to specify specific ranges when creating the table e.g. PARTITION part1 VALUES LESS THAN TO_DATE (01-APR-1994, DD-MON-YYYY), PARTITION part1 VALUES GREATER THAN TO_DATE (01-APR-1994, DD-MON-YYYY), Is it always necessary to provide specific range values? What happens at time moves on. Is it necessary to repartition the table to add new time periods? Or is it possible to specify ranges relative to SYSDATE e.g SYSDATE - 30, SYSDATE - 60 etc John -- //www.freelists.org/webpage/oracle-l **DISCLAIMER This e-mail message and any files transmitted with it are intended for the = use of the individual or entity to which they are addressed and may contain= information that is privileged, proprietary and confidential. If you are n= ot the intended recipient, you may not use, copy or disclose to anyone the = message or any information contained in the message. If you have received t= his communication in error, please notify the sender and delete this e-mail= message. The contents do not represent the opinion of D&E except to the ex= tent that it relates to their official business. -- //www.freelists.org/webpage/oracle-l