RE: EXTERNAL:Re: Job breaks after upgrade from 10.2.0.3 to 11.1.0.7
- From: "Schauss, Peter (IT Solutions)" <peter.schauss@xxxxxxx>
- To: <ilmar.kerm@xxxxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
- Date: Fri, 30 Jul 2010 12:03:04 -0500
Ilmar,
Thanks for the tip. Recreating the job solved the problem.
- Peter Schauss
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On
Behalf Of Ilmar Kerm
Sent: Thursday, July 29, 2010 11:03 AM
To: oracle-l@xxxxxxxxxxxxx
Subject: EXTERNAL:Re: Job breaks after upgrade from 10.2.0.3 to 11.1.0.7
On Thu, Jul 29, 2010 at 4:53 PM, Schauss, Peter (IT Solutions)
<peter.schauss@xxxxxxx> wrote:
> I upgraded an instance of 10.2.0.3 (Windows 2003 sp2) to 11.1.0.7 by
> creating a new instance, recreating users, and importing the application
> schema. Now a job which ran under 10.2.0.3 breaks.
>
> From DBA_JOBS:
> log_user= SYSTEM
> priv_user=SYSTEM
> schema_user=<application schema>
> what=<schema>.<package>.<procedure> (package is valid)
>
> The job breaks with:
>
> ORA-12012: error on auto execute of job 5
> ORA-06550: line 1, column 102:
> PLS-00904: insufficient privilege to access object <schema>.<package>
> ORA-06550: line 1, column 96:
> PL/SQL: Statement ignored
>
> The package is owned by the job's schema_user.
>
> What privilege am I missing?
DBMS_JOB jobs are imported incorrectly with data pump when running
impdp as SYSTEM. You need to recreate the jobs. I usually exclude the
jobs from export and recreate them with scripts after import.
Or if you only want to import the application schema, then run impdp
as the application user, not SYSTEM.
--
Ilmar Kerm
--
//www.freelists.org/webpage/oracle-l
Other related posts:
- » RE: EXTERNAL:Re: Job breaks after upgrade from 10.2.0.3 to 11.1.0.7 - Schauss, Peter (IT Solutions)
