Oracle backend testing: TNS:no appropriate service handler found?
Leo Soto M.
suite with the oracle backend[1]. And it is not because oracle is
down: it happens after a while (34 minutes!), and looks like it is
caused by too many connections to the oracle server[2]. The
listener.log file confirms it[3].
Is anyone else experimenting this? Any idea on what test(s) may be
causing the problem?
[1] http://certenium.ingenium.cl:8080/hudson/job/django-trunk/SETTINGS_MODULE=settings_oracle/22/console
[2] http://www.orafaq.com/usenet/comp.databases.oracle.server/2006/02/27/1877.htm
[3] http://dpaste.com/68676/
--
Leo Soto M.
http://blog.leosoto.com
Leo Soto M.
Yeah, I know it is not polite to bump an old post without a good reason.
Well, my good reason is that Django is approaching the beta period and
seems like oracle testing is not being covered by the buildbots. So, I
think I can help this a bit with my hudson setup (kindly hosted by the
company where I work), if someone in the Oracle crew can give me a
hand with the observed problems.
Regards,
Matt Boersma
executing this:
SQL> show parameters processes;
NAME TYPE VALUE
------------------------------------ -----------
------------------------------
processes integer 50
If "processes" is less than 100, bump it up:
SQL> alter system set processes = 100 scope=spfile;
System altered.
Then you'll have to restart Oracle, since this change can be made only
to the SPFILE startup configuration, not to the running server
instance.
As they mentioned on the forums you linked to, this is just a
workaround for Oracle being slow to recognize when connections are
freed, but it might help the test suite to complete. There are some
other parameters that might be relevant, but try this first.
Matt
On Aug 9, 6:33 pm, "Leo Soto M." <leo.s...@gmail.com> wrote:
>
> > I'm getting the error mentioned on the subject when running the test
> > suite with the oracle backend[1]. And it is not because oracle is
> > down: it happens after a while (34 minutes!), and looks like it is
> > caused by too many connections to the oracle server[2]. The
> > listener.log file confirms it[3].
>
> > Is anyone else experimenting this? Any idea on what test(s) may be
> > causing the problem?
>
> > [2]http://www.orafaq.com/usenet/comp.databases.oracle.server/2006/02/27/...
Leo Soto M.
>
> Leo, try logging in to the Oracle server as sys with sqlplus and
> executing this:
>
> SQL> show parameters processes;
> NAME TYPE VALUE
> ------------------------------------ -----------
> ------------------------------
> processes integer 50
>
> If "processes" is less than 100, bump it up:
>
> SQL> alter system set processes = 100 scope=spfile;
> System altered.
>
Exelent, it worked! Thanks you.
So, from now on, django developers can check the status of the test
suite with the oracle backend here: