Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: sqlplus : 100% CPU usage while connecting to remote DB

Re: sqlplus : 100% CPU usage while connecting to remote DB

From: Ana C. Dent <anacedent_at_hotmail.com>
Date: Tue, 26 Jun 2007 03:32:51 GMT
Message-ID: <DN%fi.8429$oh3.2577@newsfe03.phx>


Krivenok Dmitry <krivenok.dmitry_at_gmail.com> wrote in news:1182778236.430452.74910_at_q69g2000hsb.googlegroups.com:

> Hello!
> I am trying to connect to the remote DB using the following command:
>
> sqlplus dimas/pass_at_MTT
>
> Note, that MTT is accessible, I've tested it using tnsping.
>
> But sqlplus hangs and eats 100% of CPU.
> Look at top's output:
> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
> 12767 voteuser 22 0 19752 4764 3364 R 100 0.2 0:03.34 sqlplus
>
> I'm just trying to connect to remote DB.
> What's wrong?
>
> I've traced sqlplus process via strace utility.
> It doesn't attempt to connect (doesn't call connect system call).
> Looks like an infinite loop:
>
> ...
> ...
> ...
> 13100 open("/usr/local/oracle/app/oracle/product/10.2.0/rdbms/mesg/
> ocius.msb", O_RDONLY) = 6
> 13100 fcntl64(6, F_SETFD, FD_CLOEXEC) = 0
> 13100 lseek(6, 0, SEEK_SET) = 0
> 13100 read(6, "\25\23\"\1\23\3\t\t
> \0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 256) = 256
> 13100 lseek(6, 512, SEEK_SET) = 512
> 13100 read(6, "\337y
> \0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 512) = 512
> 13100 lseek(6, 1024, SEEK_SET) = 1024
> 13100 read(6, "\25\7\'\0072\7>\7j\7\276\17$\'\6K5S\24TfT\307T(VsV
> \222"..., 86) = 86
> 13100 brk(0x80af000) = 0x80af000
> 13100 times(NULL) = -2058704771
> 13100 times(NULL) = -2058704771
> 13100 times(NULL) = -2058704771
> 13100 times(NULL) = -2058704771
> 13100 times(NULL) = -2058704771
> 13100 times(NULL) = -2058704771
> ...
> ...
> ...
>
> That is sqlplus process calls only "times" system call in a loop (in
> fact, infinite loop).
>
> P.S.
> Remote connect to the MTT DB from another host is successful.
>

OO OO I've seen this before.

Linux V10.0.2.1 right?

What is uptime on this server?

If so you have two choices.
1) Upgrade to V10.2.0.2
or revert to the Micro$oft school of s/w engineering by 2) Reboot server

If uptime is around 200 day you've hit known bug in V10.2.0.1

HTH & YMMV Received on Mon Jun 25 2007 - 22:32:51 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US