EA Remote Repository for Oracle 9i

[tdrozdowski]

Been a user of EA for over a year now, and the organization I'm with upgraded to corporate edition.  So in taking advantage of the remote repository concept, I hit a few snags with the instructions for using Oracle 9i that I have some suggestions for.

1. Oracle seed script.  The necessary sequences for the repository are not in your script that you direct people to.  I've put together a script that creates them and I'd be willing to post it here for inclusion in updated scripts.

2. Oracle OLE-DB adaptor.  Found out (the hard way) that if you have the Oracle 10g client installed, putting the 9i OLE-DB adaptor seems to corrupt your Oracle installation.  A warning in the instructions would help people with this.

3. Would it be possible to update the repository schema so that it could host more than one project?  Our DBA pretty much flipped his lid when he learned he would have to create a new schema for every EA project we create (that we want in the remote repo).  I know we could put all of our org's models into one giant model, but it seems kinda messy that way and an administrative nightmare (to manage users, models, permissions, etc).

4. The MDAC requirement is outdated - if you have Windows XP sp2, you don't need to install it.  And if you don't, they're on version 2.8 now. (the links to 2.6/2.7 are dead)

[hd]

1. Oracle seed script.  The necessary sequences for the repository are not in your script that you direct people to.  I've put together a script that creates them and I'd be willing to post it here for inclusion in updated scripts.

There's no need for sequences in the script. The Data Model Transfer deletes and recreates them on the fly.

[tdrozdowski]

As of build 788, it didn't do so for me.  Once I had the sequences in the db, it did set them to the appropriate values...

[spolyak]

FWIW, our problem was that i neglected to do "grant create sequence" on the db user. had to go back and hand create the sequences (with the correct start with vals). Maybe the oracle db instructions should be more explicit about what grants to exeucte, etc.

[«Midnight»]

Perhaps so.

Still, you'd have the same problem (inability to successfully execute a script or command to create a sequence) regardless of which (or any) CASE tool you used.

Perhaps the documentation needs to remain with the Oracle user and administrator communities.

That's not to say that the situation couldn't be improved. Rather, it seems a bit to ask CASE tool developers to document the tools they address.

Just my 0.02 CAD worth.

[Gary W.]

Perhaps the documentation needs to remain with the Oracle user and administrator communities.

Well, looking at the installation docs for Oracle's *own* CASE tool (Designer), I see whole sections devoted to "DBA tasks you must do on your own prior to installation".  They explicitly list stuff like:
 GRANT EXECUTE ON sys.lt_export_pkg TO exp_full_database;
 GRANT EXECUTE ON sys.lt_export_pkg TO PUBLIC;
 GRANT EXECUTE ON sys.lt_export_pkg TO user;

I suspect there are reasons to have you manually do this (e.g. running a script while logged on as a super-user isn't a good practice), and I don't know if SQL-Server or MSSQL or PostGRES are the same, but in all my years of using Oracle, I've always found explicit instructions on how to manually prepare the database account.

gary