We live in hope JV. That's not what you wanted to hear, I know, but it is where we are now.
But all is not lost! If you've got an Oracle set-up of that size you have also doubtless got a few Oracle wizards around, trying to fill the empty hours now that everything is working so well...
Have one of them create a wrapper for the Sparx procedure to set up a project. The wrapper should be able to take either a single project name or a set - I'll leave you and your wizard to figure out the most effective way to pass parameters. I would then create the back end, probably giving it an 'internal' name geared to EA models, run the Sparx script to set it up, and then provide whatever default user access you might define.
Once this works well, have your wizard look at how EA does its data transfer function to set up a project. Take the before and after pictures of a new, empty project in Oracle. Then have your wizard build an ETL script that does the same thing, and can be called from the above model creation script. Try setting this up with an option to import a specific file containing reference data, to allow you to set up certain classes of models with corporate standards (or whatever) reflected.
At this point you will have a tool that allows you, or your DBA, to build a new model schema on the fly, populate it with core data, and set up basic access.
Yes, it is some work, but this is something that Sparx could not do for you (we all claim our business are unique, but I think they might all be identical with the exception of the Oracle set up). It should pay off handsomely long before you reach the 100th model!
HTH,
David
PS: If you feel like giving something back, you could always publish the script (after obtaining permission of course) to the EA User Group and Wiki - see the Automation section of the forum for details.