Writing 2 TB a month will require a good enough file system to handle the I/O needs for your online redo logs, your undo tablespace, your archived redo logs and your tablespace(s) holding the table and indexes. You might need to ensure you have enough disk spindles to be able to handle this type of I/O volume.
The other thing I would recommend is to look at partitioning. You may have to partition this table to get the desired performance out of it. Partitioning is an extra cost option, but it may be just what you need.
Dig Deeper on Oracle database design and architecture
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.