Re: instance stuck in initialization

From: Leng Kaing <mylengdotkaing_at_hancorp.com.au>
Date: Tue, 05 Sep 2000 18:47:39 +1000
Message-ID: <39B4B32A.F2177635@hancorp.com.au>

catalog.sql is one of the most important scripts that must be run after creating the database. This sets up your dictionary tables! You also need catproc.sql to setup the procedural option. Use svrmgrl and connect as INTERNAL. oratune_at_aol.com wrote:

> In article <8ols46$jri$1_at_nnrp1.deja.com>,
> pjohns23_at_my-deja.com wrote:
> > Barnel, I think we're on to something. My database was also manually
> > created.
> >
> > When I initially installed (ok the 4th time), the software got
 installed
> > cleanly, but the script to build the initial database bombed out. I
> > figured that was probably ok and proceeded to build a database by
 hand.
> > Along the way, I discovered that catalog.sql had never been executed,
 so
> > I ran it to build the dba_ tables. There must be another key script
 that
> > needs to be executed.
> >
> > Peggy
> >
> > In article <39ADD737.E4AB304C_at_ottawa.com>,
> > Barnel <barnel_at_ottawa.com> wrote:
> > > Funny you should also have this problem. I am in the same situation
 as you
> > > are. The last thing (ok the last foolish thing) I remember doing
 was
> > > setting a my temporary tablespace to the permanent option and then
 back to
> > > temporary using Oracle's Storage Manager Utility. The thing is that
 when I
> > > was flickered the radio button between the 2 options and hitting the
 apply
> > > button. I don't remember seeing the "You were successful in doing
 what
 you
> > > were doing dialog box".
> > >
> > > The other thing that I see going against me is the fact that I
 manually
> > > created my database. Meaning I could not get dbassist to create my
 database
> > > or generate my db creation script (that another long story) so I
 found
> > > myself creating, altering and running the scripts from the
> > > $ORACLE_HOME/rdbms directory by myself. So I'm wondering if there
 is
 script
> > > or a procedure that I may have forgotten?
> > >
> > > Any suggestion (hopefully not involving having to re-create this God
> > > forsaking database) ?
> > >
> > > Thanks
> > >
> > > pjohns23_at_my-deja.com wrote:
> > >
> > > > I have a new installation of 8.1.5 on Solaris 7 that seems to be
 getting
> > > > hung up in an initialization mode.
> > > >
> > > > When I bring up the instance this happens:
> > > > SVRMGR> connect internal
> > > > Connected
> > > > SVRMGR> startup open dev1
> > > > ORACLE instance started.
> > > > Total System Global Area 37182864 bytes
> > > > Fixed Size 64912 bytes
> > > > Variable Size 10723328 bytes
> > > > Database Buffers 26214400 bytes
> > > > Redo Buffers 180224 bytes
> > > > Database mounted.
> > > > ORA-01403: no data found
> > > > SVRMGR>
> > > >
> > > > As long as I remain connected as internal, I can do whatever I
 want
> > > > (create a database, create/drop tablespaces, create/drop tables,
 ...).
> > > > However, when I try to connect as another user, this happens:
> > > > SVRMGR> connect dbauser/xxxxxxx
> > > > ORA-01033: ORACLE initialization or shutdown in progress
> > > > SVRMGR>
> > > >
> > > > This same ORA-01033 error occurs in sqlplus, imp, and every
 utility
 I've
> > > > tried, as well.
> > > >
> > > > Any ideas are greatly appreciated.
> > > > --
> > > > Thanks,
> > > > Peggy D. Johnson
> > > >
> > > > Sent via Deja.com http://www.deja.com/
> > > > Before you buy.
> > >
> > >
> >
> > --
> > Thanks,
> > Peggy D. Johnson
> >
> > Sent via Deja.com http://www.deja.com/
> > Before you buy.
> >

>

> The catalog.sql script must be run as either SYS or INTERNAL; I choose
> to run it from the Server Manager prompt:

>

> SVRMGR> @catalog

>

> Try this: from Server Manager connect as INTERNAL, set echo on, spool
> output to a file (/tmp/catalog would work) then execute the catalog.sql
> script. The spool file should list all of the various and sundry
> commands submitted to Server Manager and also the generated output. You
> may find that there were some errors executing catalog.sql that passed
> by you the last time you ran it. The catalog.sql script first calls
> standard.sql, then generates the catalog views, then calls the following
> scripts in the listed order:

>


> cataudit.sql             Auditing views

> catexp.sql               IMP/EXP views

> catldr.sql               SQL*Loader views

> catsvrmg.sql             Server Manager views

> catpart.sql              Partitioning views

> catadt.sql               Object views

>

> Errors in any one of these scripts could cause the error you encounter.
> --
> David Fitzjarrell
> Oracle Certified DBA

>

> Sent via Deja.com http://www.deja.com/
> Before you buy.
Received on Tue Sep 05 2000 - 03:47:39 CDT