Re: DBA Information question...

My answer is not directly related to your question ... but rather to issues you haven't considered. I would strongly urge you to not let your customers build their own instances and databases for your product based on written text. There are considerations with respect to an Oracle installation that go well beyond what can be communicated in that manner.

I would suggest that you supply your customers with an initSID.ora and a series of build scripts (starting with create database, followed by creation of temp, rollback, data, and index tablespaces, etc.). Add instructions on which parameters they can modify and which they can not. And what considerations relate to how it is modified.

I've done this for more than a few customers. And every time they are left to create their own my clients have ended up sending in support personnel to clean up the mess. Seemingly small things like block size and character set can make a huge difference.

Daniel Morgan

ARP wrote:

> We have a database-bound application under development which is soon going
> to be sold commercially. I need to communicate to Oracle (and other) DBAs
> the kind of information about the application database that would be helpful
> to them in planning to create their own instances of the database for use in
> their various companies. Two questions:
>
> 1. Apart from the obvious object descriptions, constraints, indexes, etc.;
> is there anything that an Oracle DBA would be particularly interested in
> with regard to the database structural and meta-data details that would be
> helpful in planning for the database?
>
> 2. Are there any known methods including readily available tools (esp.
> shareware or freeware) that would assist me in determining the average
> record-size in each table (and other similar metrics) from a sample database
> that I have been using for testing?
>
> Thanks in advance for your assistance.
Received on Tue Apr 16 2002 - 09:53:10 CDT