drop/truncate table partition and constraints
Hello Folks,
Whilst dropping/truncating a table partition one must not have any active referential constraints on it. Either disable them or drop them and enable and later create/enable them after the partition operation is complete. However, this will leave the table in an inconsistent state until partition operation is complete. Which means I must have some amount of maintenance window for such partition operation.
So is there any alternate to perform partition maintenance with no downtime of the upstream layer above the database in an application architecture?
Thanks in advance for your response.
Best,
Girish