ORACLE 11g Database Control hugs CPU 100%

Hello,

11g, Win XP 2G SP2

after installing 11g EE and starting Database Control (emctl start dbconsole and
login sys pass sysdba) task manager reports oracle.exe is 100 % busy.
Without doing anything, cpu remains 100%, entering emctl stop dbconsole all
is fine.

has sombody seen this strange behaviour as well?

Manfis

"manfis" schreef in bericht
news:g920b0$mjf$02$1-at-news.t-online.com...
> Hello,
>
> 11g, Win XP 2G SP2
>
> after installing 11g EE and starting Database Control (emctl start dbconsole and
> login sys pass sysdba) task manager reports oracle.exe is 100 % busy.
> Without doing anything, cpu remains 100%, entering emctl stop dbconsole
> all is fine.
>
> has sombody seen this strange behaviour as well?
>
> Manfis
>

Did you reboot between installing and starting?

Shakespeare

"manfis" schreef in bericht
news:g920b0$mjf$02$1-at-news.t-online.com...
> Hello,
>
> 11g, Win XP 2G SP2
>
> after installing 11g EE and starting Database Control (emctl start dbconsole and
> login sys pass sysdba) task manager reports oracle.exe is 100 % busy.
> Without doing anything, cpu remains 100%, entering emctl stop dbconsole
> all is fine.
>
> has sombody seen this strange behaviour as well?
>
> Manfis
>

Do you have XP Professional Edition?

Shakespeare

"manfis" schreef in bericht
news:g920b0$mjf$02$1-at-news.t-online.com...
> Hello,
>
> 11g, Win XP 2G SP2
>
> after installing 11g EE and starting Database Control (emctl start dbconsole and
> login sys pass sysdba) task manager reports oracle.exe is 100 % busy.
> Without doing anything, cpu remains 100%, entering emctl stop dbconsole
> all is fine.
>
> has sombody seen this strange behaviour as well?
>
> Manfis
>

Windows Firewall active? Read the notes on Metalink under tab "Certify."

Shalespeare

On Wed, 27 Aug 2008 21:03:03 +0200, "Shakespeare"
wrote:

>
>"manfis" schreef in bericht
>news:g920b0$mjf$02$1-at-news.t-online.com...
>> Hello,
>>
>> 11g, Win XP 2G SP2
>>
>> after installing 11g EE and starting Database Control (emctl start dbconsole and
>> login sys pass sysdba) task manager reports oracle.exe is 100 % busy.
>> Without doing anything, cpu remains 100%, entering emctl stop dbconsole
>> all is fine.
>>
>> has sombody seen this strange behaviour as well?
>>
>> Manfis
>>
>
>Windows Firewall active? Read the notes on Metalink under tab "Certify."
>
>Shalespeare
>

Did you have to reboot your Windows system, so you couldn't post this
as one response? (grin

--
Sybrand Bakker
Senior Oracle DBA

schreef in bericht
news:brabb452acd53rrppelbloioormn0llk5l-at-4ax.com...
> On Wed, 27 Aug 2008 21:03:03 +0200, "Shakespeare"
> wrote:
>
>>
>>"manfis" schreef in bericht
>>news:g920b0$mjf$02$1-at-news.t-online.com...
>>> Hello,
>>>
>>> 11g, Win XP 2G SP2
>>>
>>> after installing 11g EE and starting Database Control (emctl start dbconsole
>>> and
>>> login sys pass sysdba) task manager reports oracle.exe is 100 % busy.
>>> Without doing anything, cpu remains 100%, entering emctl stop dbconsole
>>> all is fine.
>>>
>>> has sombody seen this strange behaviour as well?
>>>
>>> Manfis
>>>
>>
>>Windows Firewall active? Read the notes on Metalink under tab "Certify."
>>
>>Shalespeare
>>
>
> Did you have to reboot your Windows system, so you couldn't post this
> as one response? (grin
>
> --
> Sybrand Bakker
> Senior Oracle DBA

Trying to get my post activity counter up ......

Shakespeare

manfis wrote:
> Hello,
>
> 11g, Win XP 2G SP2
>
> after installing 11g EE and starting Database Control (emctl start dbconsole and
> login sys pass sysdba) task manager reports oracle.exe is 100 % busy.
> Without doing anything, cpu remains 100%, entering emctl stop dbconsole all
> is fine.
>
> has sombody seen this strange behaviour as well?
>
> Manfis
>
>

I can't unravel this mystery, but I got a similar behavior.
I started Database control at about 8:30 this morning because of your request.
This is also Oracle 11g but on Solaris SPARC 10 on an Sun Blade 2000
with 2 1.2 GHz CPUs.
The system was busy for about 10 hours with an average of 50%.
On Solaris I have one oracle process per connect, and this process has
consumed more than 630 minutes of CPU time now.

So there seems to be some big work to be done after init.
Wait and see, if your system calms down after a while.

Yes Win XP Professional and Rebooted.
Next what I did, I implemented 11g under Win Vista Ultimate, quite another
machine, same effect!

"Shakespeare" schrieb im Newsbeitrag
news:48b59510$0$196$e4fe514c-at-news.xs4all.nl...
>
> "manfis" schreef in bericht
> news:g920b0$mjf$02$1-at-news.t-online.com...
>> Hello,
>>
>> 11g, Win XP 2G SP2
>>
>> after installing 11g EE and starting Database Control (emctl start dbconsole
>> and login sys pass sysdba) task manager reports oracle.exe is 100 %
>> busy. Without doing anything, cpu remains 100%, entering emctl stop
>> dbconsole all is fine.
>>
>> has sombody seen this strange behaviour as well?
>>
>> Manfis
>>
>
> Did you reboot between installing and starting?
>
> Shakespeare
>

"manfis" schreef in bericht
news:g920b0$mjf$02$1-at-news.t-online.com...
> Hello,
>
> 11g, Win XP 2G SP2
>
> after installing 11g EE and starting Database Control (emctl start dbconsole and
> login sys pass sysdba) task manager reports oracle.exe is 100 % busy.
> Without doing anything, cpu remains 100%, entering emctl stop dbconsole
> all is fine.
>
> has sombody seen this strange behaviour as well?
>
> Manfis
>

I checked this with an Oracle DBA consultant and it seems it is known
behaviour. It does happen in the case you install a pre seeded database (but
can happen in other cases as well). The moment you start Database Control, it
decides it has a lot of jobs to run and starts firing them (the seeded data
is from 2004 or so, so it is 4 years behind with the jobs and tries to catch
up!)

Killing the eunning jobs will do the trick.

Shakespeare

Try the following

cd $ORACLE_HOME
../bin/emctl stop dbconsole
../bin/pafctl stop
../bin/pafctl start
../bin/emctl start dbconsole

Enter the SYSMAN password during pafctl. During "start", accept the
default interval.

The above would reset one of the job such that it would take off the
high CPU load.