Re: startup nomount

Ok back up a step... Why are you doing this? Why startup nomount? Why shutdown/startup at all? You mention IMP, but IMP needs the database to be up and running, startups should not be involved. Also, why call oradim?

Unless you're doing cold backups, shutting down a db is NOT part of normal maintenance.

If you have as big a mess in your hands as it appears you do, it's a good thing you can't login in as sysdba!

Sorry to say that but what you say you are trying to do makes no sense at all!

"CS" <sheley_at_interaccess.com> wrote in message news:orn9a.5595$fa.2431759_at_dca1-nnrp1.news.algx.net...
> I'm a newbie to Oracle DBA chores.
> I'm trying to setup a script that installs Oracle then IMPort a database.
>
> After installing oracle, my batch file Starts the listener, then calls
> sqlmgrl.
>
> What should I connect as and what password?? I'm getting 'Insufficient
> Privilege's logging on as Sys or System when I issue the command STARTUP
> NOMOUNT
>
> I can't seem to get on using AS SYSDBA.
>
> Here is the command I issue before starting Svrmgrl
> oradim -new -sid MYDB -startmode manual -pfile
> D:\ORACLE\ora81\database\initMYDB.ora -intpwd password
>
> Once I get the command line down, I plan to put it in a SQL script
>
> Any Ideas would be really appreciated.
>
> Thanks
> CS
>
>
>
Received on Wed Mar 05 2003 - 08:34:57 CST