Alberto, December 04, 2023 - 3:51 pm UTC
Thank you very much for your answer, Connor.
The bigger block size is because we expect the data will increase even more. With current block size we can "only" have a tablespace of 32 TB and we plan to move to a tablespace with 32K block to be able to grow until 128 TB.
We also plan to compress data in the movement.
This database is for a product not developed by my company, so it's not easy for us to know if we can move the data in parts. At this moment, the requirement is to move everything keeping the application up.
December 07, 2023 - 6:24 am UTC
I would checkout BIGFILE tablespaces.
A reader, December 07, 2023 - 9:23 am UTC
Hi Connor,
Yes, we're using BIGFILE tablespaces. According to oracle documentation:
A bigfile tablespace contains only one datafile or tempfile, which can contain up to approximately 4 billion ( 232 ) blocks. The maximum size of the single datafile or tempfile is 128 terabytes (TB) for a tablespace with 32 K blocks and 32 TB for a tablespace with 8 K blocks.
We want to move the table to a larger block size tablespace so it can grow to 128 TB, as currently this table is using 25 TB and growing. In our current tablespace with blocksize of 8K it only can grow to 32 TB.
December 17, 2023 - 11:43 pm UTC
Surely this table is partitioned?
(Because you get a tablespace per partition)