Re: Oracle 10g enterprise on windows xp pro - startup problems from time to time?

Incompetent regarding oracle databases? Of course, that's why I'm asking my questions here! Ignorant? If that were the case I would blame Oracle instead of myself. I'm new to oracle, and I have to get a JSF project completed in time. As this project will be running on Oracle AS and DB I tried to setup this environment here in my office. Worked perfectly in my virtual machine, on my "real" server (old desktop athlon) it doesn't work all that well. I don't know why, and I didn't find anything that would help in the documentation (I'm sure it's there, but hey, it's about 450mb of data!) - again, that's why I was asking, in a polite manner I think, what _I_ might be doing wrong and where to start _looking_ for a solution. I'm neither whining nor telling that sql servers a better product nor do I know anything about some evil empire (for real, thats childs play - expected a bit more of someone who calls himself senior something). Btw, the windows (yeah, evil os, I know, but I don't have time to learn linux atm) system is fresh & clean. It was installed on the same day as oracle, just every windows update installed.

So again, if anyone's willing to point me into a direction I would really appreciate it. :)

Sybrand Bakker schrieb:

> On 17 Aug 2006 04:36:45 -0700, "mathias.ringhof"
> <mathias.ringhof_at_googlemail.com> wrote:
>
> >Any ideas? A colleague of mine always starts and stops his instances
> >manually... somehow I start to realize why... ^_^
>
> My primary idea is your colleague probably also never read any
> documentation, and so is equally ignorant and incompetent. Just like
> you, I guess.
>
> If your registry keys have been set correctly, and you don't have a
> completely whacked system (which you probably do) then the Oracle
> service would shutdown the database for you.
> However, if the database doesn't shutdown in ora_shutdown_timeout
> seconds (defined in the registry), the database will be shutdown
> abort, causing recovery at startup .
> Also an incorrect sys password (ie the sys password in the password
> file is NOT the same as the SYS password in the database) can cause
> problems. Errors are written in oradim.log, in alert<sid>.log etc.
>
> If you for a change, would realize you come from the Evil Empire, and
> Oracle is not sqlserver from a different vendor, but actually a much
> better product, and would start reading those manuals, instead of
> whining here, you would actually learn something, and resolve the
> problem easily.
> It was introduced by not reading the manuals in the first place.
>
>
> --
> Sybrand Bakker, Senior Oracle DBA
Received on Fri Aug 18 2006 - 01:29:30 CDT