system user locked after crash

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

fp - 28 Sep 2007 14:04 GMT

Hi, we have an application running with OracleXE 10g on Windows.
It's not unusual that the application runs in the same pc which host the db
server.
It happened that, after a sudden crash of the system and after the windows
reboot, the Oracle system user was locked.

Ok, now i've unlocked the user but still don't know why this happened.
I can only imagine a series of wrong user/pwd connections, but it seems this
isn't the case.

Thanks in advance for any answer to my doubt

--
francesco pighi

Reply to this Message

fitzjarrell@cox.net - 28 Sep 2007 15:50 GMT

Comments embedded.

> Hi, we have an application running with OracleXE 10g on Windows.

Interesting. Which release of Windows? What sort of application
would this be? I suspect it's a fairly small application given that
you're using XE and there are database size limitations.

> It's not unusual that the application runs in the same pc which host the db
> server.

It may not be unusual in your shop but I certainly wouldn't recommend
such a practice.

> It happened that, after a sudden crash of the system and after the windows
> reboot, the Oracle system user was locked.

You're assuming the SYSTEM user account was unlocked prior to the
crash, and that may not be the case. The SYSTEM user may have been
locked prior to the crash and you only discovered this after the
system was restarted. Do you possess logs from any scheduled tasks
which could prove otherwise? We really need more information than you
have currently provided.

> Ok, now i've unlocked the user but still don't know why this happened.
> I can only imagine a series of wrong user/pwd connections,

As I would also suspect.

> but it seems this isn't the case.

What evidence do you have to support this claim? Read no more into
that question than what is written, as I am merely asking for further
proof of your assertion. We certainly cannot infer from your
description what may have happened apart from that which would appear
obvious. If you have information which could suggest otherwise please
post it.

> Thanks in advance for any answer to my doubt
>
> --
> francesco pighi

David Fitzjarrell

Reply to this Message

fp - 28 Sep 2007 16:43 GMT

>> Hi, we have an application running with OracleXE 10g on Windows.
>
> Interesting. Which release of Windows? What sort of application
> would this be? I suspect it's a fairly small application given that
> you're using XE and there are database size limitations.

It's a desktop app written in .Net which uses Oracle ODP.Net. The lock of
the system user was found on a Win Xp Pro SP2 machine. It's worth noting
that this is the first case in 200+ installations.

>> It's not unusual that the application runs in the same pc which host the
>> db
>> server.
>
> It may not be unusual in your shop but I certainly wouldn't recommend
> such a practice.

Me too... in fact we are pushing our customer to adopt Oracle STD and buy a
dedicated Oracle server for each office (which has from 1 to 6 or 7
clients). They were used in this way because of the previous application
that is going to be replaced by ours.

>> It happened that, after a sudden crash of the system and after the
>> windows
[quoted text clipped - 6 lines]
> which could prove otherwise? We really need more information than you
> have currently provided.

I haven't logs which could prove my statement, and in fact it was just an
assumption based on the fact that the system password is the same in all the
installations and it has never changed from our first installation up til
now. We have a bunch of functions in a windows service which, periodically,
uses the system user to perform database specific tasks (gather stats,
unlock users, etc), but the pwd is embedded (crypted) in the c# code, so, i
presume (but at this point I'm not so sure), it can't be wrong.

Unfortunately this office is assisted by an external IT service and they
called us just to fix the problem, they only said me that none of them tried
to connect manually as system (in sqlplus for example).

Thank you very much anyway, and sorry for my italenglish :-)
I presume this matter will remain unknown.

--
francesco pighi

Reply to this Message

fitzjarrell@cox.net - 28 Sep 2007 17:30 GMT

> <fitzjarr...@cox.net> ha scritto nel messaggionews:1190991043.869175.213700@r29g2000hsg.googlegroups.com...
>
[quoted text clipped - 48 lines]
> --
> francesco pighi

A corrupted source file or memory problems could well be the cause of
this account locking; the system crashed due to some problem, was
there any indication of why this machine suddenly decided to die? Any
information is better than no information.

David Fitzjarrell

Reply to this Message

fp - 28 Sep 2007 17:52 GMT

> A corrupted source file or memory problems could well be the cause of
> this account locking; the system crashed due to some problem, was
> there any indication of why this machine suddenly decided to die? Any
> information is better than no information.

The application was in the middle of a time-consuming query to elaborate an
data analysis report. And then (unfortunately i couldn't verify this myself)
the system rebooted. Probably it was a memory or disk problem of some kind
because this pc previously had a system.dbf file corrupted and then oracle
was re-installed from scratch and the app was restored with our backup and
restore utility which in essence is an interface to exp and imp.

> David Fitzjarrell

--
francesco pighi

Reply to this Message