Re: startup nomount

> You are correct again that a DBA is required for on site setup. But that
> cost is prohibitive. I'm going to try and change that with my script.

Just be aware that your clients will probably need a dba later afterwards to do routine stuff, like backups, periodic maintenance, etc...

Also, how could the cost of a dba be prohibitive, but you guys will pay the Oracle licenses? You ARE paying the licenses for each deployment, right?

Also, one last time: Oracle does not run well unsupervised. You will cause your customers grief by giving them a database that REQUIRES maintenance, and then there is no one to do that maintenance.

> My initial batch file does the following:
> My scripts modify Init., Listener and the sqlnet. ora files and put them
in
> the correct location with the Host and GlobalDatBaseName changes.. Then it
> starts the listener and runs tnsping to make sure we have made it thus
far.

Would tnsping work at this stage without a working DB created? You might save this for last...

> Then it deletes the pwdMYDB.ora file and calls the oradim statement. Even
> if these services are running already, no fatal error.
> oradim -new -sid MYDB -startmode manual -pfile
> D:\ORACLE\ora81\database\initMYDB.ora -intpwd password
> I'm not sure if deleting the password file is causing me not to be able to
> log on as sysdba. I can login SYSTEM or SYS using the normal passwords
but
> not as SYSDBA.

You got a lot to learn about this... Read up on the relationship between a password file, logging in as sysdba, and the init file...

> After the Startup Nomount, I Create and size the DB. ( I think)

Again, this is not right. Why not just create the scripts with DBCA and modify them to what you need? You're re-inventing the wheel here.

>I'm really
> not sure what the minimum requirements are to run the IMP.

You need a working database, and you need to have the schema owners (users) created before you do the imp.

>I got 3 rather
> large books on Oracle and none of them tell exactly what to expect/do
using
> IMP/EXP utilities. They do say to login as INTERNAL/ORACLE as sysdba but
> that doesn't work either. They did say that internal was for older
systems
> and change to sys.

Again, read up on imp (buy a good book that actuially talks about it). You do not need to log in as sysdba to do imp/exp.

> I could create an installation that created each object and user and then
do
> the IMP for individual tablespaces, or use the script that dbArtisan
> created..

This does not make sense. Just create the schema owners and run imp. You don't need to create objects because imp will restore them.

>I thought it might be better to try and just do IMP
> fulldatabase.

You don;t want to do this as system objects will be imprted overwriting the already-existing system objects. Just import the schemas you want to restore.

> I think I have to run the CATxxx.sql scripts first. so I have to add them
> somewhere also.

Oh god! You are playing with fire BIG TIME!

> Thanks.for the time people, Oracle has me on my knees.

If you continue down this line it will also have you in the unemployment line!

> BTW2 What is the user/password as sysdba. connection string?? I think
that

connect sys/change_on_install as sysdba;

You are going down a certified fail-proof path to self-destruction. What you are charged with doing, combined with your lack of experience will insure you'll destroy a lot of databases before you even get close to what you are trying to accomplish.

If you are serious about this task, then learn the Oracle database first, before even thinking of taking on your task.

I feel very sorry for your customers, they will be stuck with a copy of Oracle (legal?) and have no idea that they have a ticking timebomb on their server... Received on Wed Mar 05 2003 - 17:03:48 CST