ick Denoire < XXXX@XXXXX.COM > wrote in message news:< XXXX@XXXXX.COM >...
assume that they have none.
publish an app so that it appears to be an app, nothing more.
if the database is read only, maintenance will be minimal.
you will still need to configure parameters related to
tns_alias, service_name, host
(127.0.0.1 is not real effective in multi-user environments)
per CPU pricing under 10g standard edition is relatively simple.
yes, oracle has a packager, and you can use OUI to deploy your own
provided database that you have "jarred". you can use reponse files to
drive the install of the oracle server software + patchsets. response
files can chain to other response files. This is covered in the docs
for the Oracle Universal Installer. I've supplied response files to
client sites that when coupled with a batch file, covered deploying an
Oracle Client + config files, plus application runtime environment off
of a unc share.
aim for having everything OFA, with a known:
and a single db_file_create_dest
(although no new datafiles, logfiles will be created with a db open
If you must be flexible regarding datafile location, you might want to
use symbolic links from under the ORACLE_BASE to the real location.
I'm assuming that the read-only database will be NOARCHIVELOG
(attempt at a cheap laugh).
I would recommend that you dig up several docs by Thomas Cox:
- low administration oracle server (LAOS)
- dba checklist v1.5
- O'Reilly Oracle DBA Checklists
For a canned app that you know very well that is frozen, if you're
running a database in noarchivelog, its not that difficult to set it
up for minimal maintenance. Oversize the hardware. Schedule OS jobs to
create logical and physical backup sets on disk (compress afterwards)
and have the client site pickup the backup sets as part of their
network backups. for Bonus points (and revenue) have the backup jobs
send an email report of free space, success of backups, invalid
objects, errors from the alert log, etc. AND CHARGE FOR IT.
Also - consider partnering with a 3rd party provider of Remote DBA
expect advocates of PostGRES and MySQL to chime in here.
this might be an option that you should consider.
sure - but I've only heard of mounting datafiles for read only
tablespaces via CD-ROM, not an entire database.
Perhaps DVD-ROM would be better, if a 700MB cd won't do.
I'd hate to have to add compression to the mix.
Do you intend to allow them to produce sorts, hash_joins, use global
If so, you're going to have to mount temp files.
This can be done with a database opened read only (e.g. standby
database opened read only for verification purposes).
I think that the controlfiles and system tablespace would have to be
read/write in order for the location of the tempfiles to be recorded.
You could ship temp files on the CDROM and locate them in a well known
location during install, turn them read/write and this would be a
but I still don't know about atempting to open an entire database read
you're still going to need to groom files
- alert log (bdump)
- listener log(s)
- core dumps
- process crashes (udump)
and they might need t