call vs execute - stored procedures

From: Glenn Stauffer <stauffer_at_swarthmore.edu>
Date: Wed, 16 Jan 2002 10:10:16 -0800
Message-ID: <F001.003F18B5.20020116085524@fatcity.com>

I am working up a script to run the dbms_stats.gather_database_stats() procedure and have run into something for which I haven't yet found an explanation.

Maybe someone here can tell me why I can run dbms_stats.gather_database_stats from Python like this (Perl would be similar, I believe, since I found the fix in a Perl list archive)

        cursor.execute("BEGIN dbms_stats.gather_database_stats(); END; ")

but not like this:

        cursor.execute("call dbms_stats.gather_database_stats()")

"Call" works for other stored procedures, dbms_utility.analyze_schema() for instance, but not for dbms_stats.

So, what's the difference?

Thanks, Glenn
--

Please see the official ORACLE-L FAQ: http://www.orafaq.com
--

Author: Glenn Stauffer
  INET: stauffer_at_swarthmore.edu

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------

To REMOVE yourself from this mailing list, send an E-Mail message to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). Received on Wed Jan 16 2002 - 12:10:16 CST