X-Received: by 10.224.217.195 with SMTP id hn3mr27838954qab.5.1367740951790;
        Sun, 05 May 2013 01:02:31 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.49.85.106 with SMTP id g10mr1371331qez.13.1367740951747;
 Sun, 05 May 2013 01:02:31 -0700 (PDT)
Path: news.cambrium.nl!textnews.cambrium.nl!feeder2.cambriumusenet.nl!feed.tweaknews.nl!209.197.12.246.MISMATCH!nx02.iad01.newshosting.com!newshosting.com!news-out.readnews.com!transit3.readnews.com!209.85.216.88.MISMATCH!m7no2273211qam.0!news-out.google.com!y6ni0qax.0!nntp.google.com!m7no2273207qam.0!postnews.google.com!g7g2000vbv.googlegroups.com!not-for-mail
Newsgroups: comp.databases.oracle.server
Date: Sun, 5 May 2013 01:02:31 -0700 (PDT)
Complaints-To: groups-abuse@google.com
Injection-Info: g7g2000vbv.googlegroups.com; posting-host=109.153.226.240; posting-account=QmaZSQoAAAAI-CJPxUT4uCrHrztSMCGs
NNTP-Posting-Host: 109.153.226.240
References: <a5d85760-f1ae-48d8-8481-f3bd0d76fa4f@r4g2000vbf.googlegroups.com>
 <5184be23$0$2574$426a74cc@news.free.fr> <b54c5b1a-0aa2-450d-9043-ee29fd07b31c@q8g2000vbl.googlegroups.com>
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1;
 Trident/4.0; GTB7.4; .NET CLR 2.0.50727; InfoPath.2; .NET CLR 3.0.04506.30;
 .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; MS-RTC LM 8),gzip(gfe)
Message-ID: <f288971c-c492-42eb-8b5e-c5e8f8e50115@g7g2000vbv.googlegroups.com>
Subject: Re: Weird procedure access problem (ORA-00942)
From: neilsolent <n@solenttechnology.co.uk>
Injection-Date: Sun, 05 May 2013 08:02:31 +0000
Content-Type: text/plain; charset=ISO-8859-1
Xref:  news.cambrium.nl

. and thanks for all the other replies - appreciated.

Basically, an old session had hung which was causing my "drop user ssf
cascade;" command to fail when running a script to delete and recreate
the database. Hence the stored procedure was not being modified as I
expected.
Guilty of getting tired and failing to read the errors on the screen!

The procedure itself referenced tables in SSF schema but had AUTHID
CURRENT_USER set - hence the potential for this kind of error ..

Oh well - we move on ...