Re: DBMS_SCHEDULER and snapshot standby
From: rjamya <rjamya_at_gmail.com>
Date: Thu, 8 Aug 2013 09:27:05 -0400
Message-ID: <CAGurbTPR7Z7s9u-Z5upY8848kwdLs1KCEtN+y-jivOMbCXRhAA_at_mail.gmail.com>
No need to trace it, it is documented in MOS note 1551817.1, it is a known issue, there exists a patch for certain versions and doc mentions a possible workaround.
Raj
Date: Thu, 8 Aug 2013 09:27:05 -0400
Message-ID: <CAGurbTPR7Z7s9u-Z5upY8848kwdLs1KCEtN+y-jivOMbCXRhAA_at_mail.gmail.com>
No need to trace it, it is documented in MOS note 1551817.1, it is a known issue, there exists a patch for certain versions and doc mentions a possible workaround.
Raj
On Thu, Aug 8, 2013 at 9:22 AM, Stefan Knecht <knecht.stefan_at_gmail.com>wrote:
> Niall
>
> Running a 10046 before issuing calls to dbms_scheduler might reveal some
> insight as to why job creations fail. Have you tried that?
>
>
>
-- http://www.freelists.org/webpage/oracle-lReceived on Thu Aug 08 2013 - 15:27:05 CEST