But if we reached (80%) Type-1 area limit and we don't have downtime window for next 2-3 weeks than i think we should better do TABLEMOVE online for all the tables having size from 0-600MB.
This is getting off topic. If you have a genuine problem to be solved then I think you should open your own thread where you describe it in real detail. This thread is about the fastest way to move a table and it definitely isn't proutil tablemove, which you seem to have a fondness for.
The size limit of a Type I area depends on two things: the maximum number of blocks in the area, which is a function of area RPB, and the database block size. The product of number of blocks and block size is the theoretical limit of the area size. At a maximum, this number could be several terabytes. Even with a relatively high RPB (and thus relatively low maximum number of blocks), the maximum area size is hundreds of gigabytes.
So as Tom says, moving a few hundred megabytes of data, likely only a few percent of the total, out of that area via tablemove basically accomplishes nothing apart from huge BI growth and its attendant problems. It still contains very large and likely fast-growing tables . You are still faced with a dump and load in the short term.
I don't know what the significance of the next two to three weeks is for you. Are you projecting that you will reach maximum capacity in that time? That sounds like an explosive rate of growth if you are at 80% of maximum now. If so, you should have been doing capacity planning and projecting your growth toward the limit long before now, in plenty of time to have access to multiple downtime windows. You should also be practicing your dump and load on a non-production copy of the database so you have well-tested procedures and scripts.
@Rajat Sharma
Please start a new thread if you want to continue this conversation.