100 levels deep in subroutine calls!



Hello Everyone,

I have a large program that loops through approximately 150 rows of data
from an Oracle database using Perl DBI. Within each row of data the
program performs further actions like logging on to a different database
(Netezza using ODBC driver) to gather further information then writing
to yet another database. I am making sure that $sth->finish() and
$dbh->disconnect are being used appropriately where necessary.
Everything seem to be checking out, but at this very same row of data, I
always get a core dump while attempting to logon to the same database to
which I was connecting and disconnecting in the previous steps. So I
turned on the Perl debug to step through the each row. At the very same
row, I get the following error from Perl.

DB<19> c
main::sub_exit(/usr/local/apps/common/devl/bin/GlobalRoutines.pm:551):
551: print STDERR "***** sub_exit() begins. *****\n\n";
100 levels deep in subroutine calls!

Is this strictly a Perl debug error message or is this a generic Perl
error message? Is there a way around this limitation? I saw something
while searching on the Internet about setting the $DB::deep to a higher
number.

I hope you can shed some light for me.

Thanks.

Peter



Relevant Pages

  • PostgreSQL and Customer Database
    ... I've been working on both SQL and Perl for a while now, ... get them all onto an SQL database, and be able to keep track of sales, as ... the database available to customers and potential customers, ...
    (perl.beginners)
  • Ways of ensuring integers in the database are seen as numbers in perl?
    ... I'd like my database returned integers to look like integers to Perl but they currently don't until I add 0 to them. ... The reason for this is that adding 0 to a Perl scalar seems to persuade Perl the scalar is an integer. ... $num as returned from database: ...
    (perl.dbi.users)
  • Re: How to access MS Access from Perl?
    ... if you were to later migrate to MS SQL Server or Oracle ... minimize your load on the database server's compiled procedure cache. ... On the other hand, if startup time for your perl script is an issue, and ... slightly preferable to the bulkier DBI + DBD::ODBC. ...
    (comp.lang.perl)
  • Re: LAMP - Program Design with Perl
    ... > information and queries the MySQL database. ... > Maybe there are Perl modules to faciliate this kind of task? ... so I think it worthwhile to second Anno's suggestion on this method (eg. ... Aside from the hint about dispatch tables, ...
    (comp.lang.perl.misc)
  • Re: Attempted Simultaneous Access causes "Could not lock file"
    ... storing it in my MSAccess database. ... I just wrote another test perl program and pasted in the massive SELECT ... >> I can have multiple perl programs writing to the database, ... > It probably needs exclusive access to the entire Table if it's modifying ...
    (microsoft.public.access.tablesdbdesign)