I 'm java system designer. As we have large project to do tightly,
Those projects are java api without webpage.

I design to create general flow engine to support all project.
This idea use 1 oracle schema , having general transaction table . And others control routing table.

They all nearly complete. But DBA Team concern that he is suffered to maintain very large request to 1 schema.

1 reason is if there are problem is some table. He must offline tablespace to fix. This is problem because all project will be affected.

I try to convince by split data of each table to partition by project_code & "month number to delete" .

Eaxmple partition:

PROJ1_05 PROJ1_06 PROJ1_07
PROJ2_05 PROJ2_06 PROJ2_07

and all transaction table will store on its partition.

So, If there are problem on any part of tablespace then he should offline some partition and another project with use same table should able to service

Transaction per day should around 10Meg Record per day.

Is this a good idea?
If I must use 1 schema, what is strategy to do?
Do you have any comment?