sybperl-l Archive

From: Michael Peppler <mpeppler at peppler dot org>
Subject: Re: perl scripted killed
Date: Jul 27 2004 12:03PM

On Tue, 2004-07-27 at 13:52, David VanEmden wrote:
> Michael,
>  Here is the section of the log for the failure.    I can run the
> stored procedure from a stand alone script and it succeeds every time. 
> Sometimes it even works in the main script I have.  It is an
> intermittant problem.
> 
> Here is the output for the call and part of the previous call...
> 
>  syb_st_fetch() -> st_next_results() == 4046
>     syb_st_fetch() -> resetting ACTIVE, moreResults, dyn_execed
>     syb_st_finish() -> resetting ACTIVE, moreResults, dyn_execed
>     <- finish= 1 at GARS_Actlog_Email.pl line 174 via
> /local/www/htdocs/scripts/
> gars/actlog/SCHEDULER/GARS_Actlog_Email.pl line 828
>     <> DESTROY(DBI::st=HASH(0x19037c)) ignored for outer handle (inner
> DBI::st=H
> ASH(0x1903d0) has ref cnt 1)
>     -> DESTROY for DBD::Sybase::st (DBI::st=HASH(0x1903d0)~INNER)
>     syb_st_destroy: called on 508bf8...
>     syb_st_destroy(): freeing imp_sth->statement
>     syb_st_destroy(): cmd dropped: 1
>     <- DESTROY= undef at GARS_Actlog_Email.pl line 828
>     -> prepare for DBD::Sybase::db (DBI::db=HASH(0x18fb60)~0x1901cc
> 'exec Determ
> ineEmail1')
>     New DBI::st (for DBD::Sybase::st, parent=DBI::db=HASH(0x1901cc),
> id=)
>     dbih_setup_handle(DBI::st=HASH(0x1902bc)=>DBI::st=HASH(0x1903b8),
> DBD::Sybas
> e::st, 19040c, Null!)
>     dbih_make_com(DBI::db=HASH(0x1901cc), 190a58, DBD::Sybase::st, 396,
> 0) thr#0
>     <- prepare= DBI::st=HASH(0x1902bc) at GARS_Actlog_Email.pl line 206
> via /loc
> al/www/htdocs/scripts/gars/actlog/SCHEDULER/GARS_Actlog_Email.pl line
> 830
>     -> execute for DBD::Sybase::st (DBI::st=HASH(0x1902bc)~0x1903b8)
>     syb_st_execute() -> ct_command() OK
>     syb_st_execute() -> ct_send() OK

Weird.

Does the script *exit* at that point, or does it simply hang?

Have you looked at the DB server error log to see if there is anything
there?

Michael


> >>> Michael Peppler  7/27/2004 1:45:58 AM >>>
> On Mon, 2004-07-26 at 22:56, David VanEmden wrote:
> > I have a script which makes use of the DBD interface.  I am
> > intermittantly getting a situation where the script stops and all I
> see
> > is the messaged killed.  I have set the dbtrace to level 2 and the
> last
> > things in the trace file are...
> > 
> >   syb_st_execute() -> ct_command() OK
> >     syb_st_execute() -> ct_send() OK
> > 
> > The command to be executed is a stored procedure.  It never returns.
> 
> > Any thoughts as to what might be the problem?
> 
> The most likely problem is that the stored proc dies on the server.
> Check the server's error log.
> 
> Also, run the script with trace level 3, and then post the entire
> section of the trace file that relates to this stored proc execution.
> 
> Michael
-- 
Michael Peppler                              Data Migrations, Inc.
mpeppler@peppler.org                       http://www.peppler.org/
Sybase T-SQL/OpenClient/OpenServer/C/Perl developer available for short
or long term contract positions - http://www.peppler.org/resume.html