Registering JOBS in OEM

Hello everybody !
I4m writing because I4m having problems when
I try to execute a JOB in OEM that I registered
with OWB. If I run this script(OWB MAP) from OWB it works
and populate the table perfectly.
But when I try to run this same thing, but now like a JOB
in OEM(that I registered with OWB too), it fails !
Somebody could give some information about it ?
Thanks !
Renato

Are you using OWB from 9iDS? I had the same problem, and it was solved a follows:
To avoid the error, edit the file setowbenv.bat in ORACLE_HOME/owb/bin/win32 so that all instances of oembase-9_0_1.jar are changed to oembase-9_0_2_.jar. Also change all instances of oemtools-9_0_1.jar to oemtools-9_0_2.jar.
A patch will be released on Metalink at the earliest opportunity.

Similar Messages

Problem in running job from OEM

I have registered JOB with OEM using TCL script from warehouse builder. I login to OEM and it shows me one job in JOB library. Now i submit this job. It keeps on showing status submitting on the Active jobs tab. It does not do anything
Thanks in advance.

Hi Garcia,
Thanks a lot for this help. Acutally "select count(1) from dual" was returning 3 initally so i have used delete statement twice and now its returning only one value. Though problem is solved but still i couldn't understand the cause of this.
Thanks a lot again.
Regards,
Ashish.

Fail to register the jobs with OEM

I have done following steps in developing a data warehouse project but im still in problum to load data from source to target:
Create a source object with thier tables
create a target object a dimension
create a mapping
create to operator one for source table and other for dimension
linked colum by column
validate this mapping
genrate this mapping
deployed this mapping
but i am facing problum while i am goining to register the TCL with OEM. I am unable to register this and following error occures
Faild to register the jobs with OEM:OEM registration Faild: OEM client not installed in Oracle_Home.
java.lang.NoClassDefFoundError.
Oracle/sysman/enSDK/client/omsClient/BadAttributeException
Exception in thread "main"
Plz help me to solve this problum.
Plz give me exact solution.
Plz give me steps from start to end of a data warehouse project.Steps involves in design ,validate and genrate and loading phase plz give me list of these steps.

This combination is not certified. Please upgrade OWB to the latest available version (9.0.3.35) that is certified on the 9.2.0.1 database.
Regards:
Igor

Authentication Error when I execute JOBS in OEM registered by OWB !!

Hi !
As I saw in the last question JOBS with
authentication error it's a commum problem ....
So follow I will detail what's happening with me:
I4m using the OWB and I did a map to extract data from two tables
on my source database and populate a destination dimension table, in my destination database.
I deploy this map, it4s sucesfull;
I run the map from OWB and it populates the destination dimension table perfectly;
I saved the TCL file and it4s OK;
I choose "Register in OEM" option and it register sucesfull;
but ... when I open the OEM and run the job from OEM, it fails !
It give this error:
VNI-2015 : Authentication error
Even when I try do it with "sysman" user
Could you help me ?
Thanks,
Renato

Hi,
Please check whether you have carried out these steps. Because I had the same problem and I resolved it.
1. I reckon you would have installed OWB and OEM.
2. In OEM if you are using the default SYSMAN user for running jobs, you should create the user SYSMAN in the OWB schema and assign the role SYSDBA, DBA AND OEM_MONITOR.
3. If you created a new user in OEM to run the jobs, you should create the user in OWB schema and assign the roles SYSDBA, DBA & OEM_MONITOR.
4. Then under your Windows NT/2000, create the OEM user and assign the user the rights "Logon as Batch Job to Run" previlege.
5. Configur OEM preferred credintials for NODE, DATABASE with proper values. The NODE user/password must be the one you have created under step 4.
6. Configur OWB with the OEM user. This can be done under Projects/Preferences, selecting OEM tab. The user/password must be thesame as under step 4.
If you do these things, not necessarily in the order mentioned, you should be able to run the jobs.
Best of luck.

Registering OWB jobs with OEM

We are facing the problem of OWB job registration in OEM. The error message that we are getting is
" Failed to register the jobs with OEM: OEM Registration Failed. Please make sure you have OEM client Installed locally, thee Oracle Management Server is running, and you have entered correct connection information and OEM information under 'Preferences'.
Error in initializing the service. Please enter correct OMS domain name in the configuration parameter and make sure that the OMS is running.
Oracle.sysman.emSDK.client.omsclientVersionMismatchException: Unable to connect to the Management server ind-spz7w2s0055.com. The management server version 9.2.0.1.0 Production is incompatible with this client 9.0
Job object failed to create, check to see if user has credentials."
The above mentioned paragraph is a single error message that we are getting.
We have referred to following documents at Metalink site:
Doc ID : Note 1081184.6
Doc ID : Note 124011.1
Doc ID : Note 169922.1
. We have also installed the patch 9.0.2.66.0. but problem continues.
Please help.

Lucas,
Your first issue is regarding the control file not being passed. In order to fix that you have to specify the control file in the mapping configuration. Beware that this control file is being read through utl_file, i.e. you will have to set the utl_file_dir in the init parameters of your database to the correct directory in order for the database to be able to read it. Basically, the control file is being read in order to fill the audit tables with the correct data.
Your second issue is regarding the type of job. As you may know OWB 'integrates' with Oracle Workflow (OWF) as well. The OWF solution also relies on the use of OEM for job execution. All of that is currently managed by Workflow Queue Listener. In order for Workflow Queue listener to be able to correctly handle the OEM jobs (defined as external functions in OWF) the job has to be defined as is. Besides, with the current way of registering the jobs all jobs (PL/SQL, ABAP or SQL Loader) are registered in the same way and directed by parameters.
Hope this helps,
Mark.

How to register job on local server with oem

Hi All,
I scheduled cron for expdp on sun server(using telnet) and its going on successfully and i dont want to disturb it.
can i register this job with EM so that just view this job status thru oem-->job section.
Thanks

Dear User,
You can't attach the crontab job in OEM. AFAIK, or use the dbms_job or dbms_scheduler job to achieve the same.
Thanks
Regards,
Taj.

Schedule FTP Job with OEM 9i

Hi All,
Does anyone have experience of setting schedule ftp job with OEM and could give me some hints or an example, thank you very much. I am now using Oracle 9i.
Rds,
CH

Lucas,
Your first issue is regarding the control file not being passed. In order to fix that you have to specify the control file in the mapping configuration. Beware that this control file is being read through utl_file, i.e. you will have to set the utl_file_dir in the init parameters of your database to the correct directory in order for the database to be able to read it. Basically, the control file is being read in order to fill the audit tables with the correct data.
Your second issue is regarding the type of job. As you may know OWB 'integrates' with Oracle Workflow (OWF) as well. The OWF solution also relies on the use of OEM for job execution. All of that is currently managed by Workflow Queue Listener. In order for Workflow Queue listener to be able to correctly handle the OEM jobs (defined as external functions in OWF) the job has to be defined as is. Besides, with the current way of registering the jobs all jobs (PL/SQL, ABAP or SQL Loader) are registered in the same way and directed by parameters.
Hope this helps,
Mark.

Using &variables in a SQL Script scheduled job within OEM

Hi...I've been searching through the forum looking for any examples of setting up a job within OEM, using the SQL Script job type, where I can basically use a WHERE clause that says 'where column_name = &variable_name' and somehow provide that at run time, as if I were in a SQL*Plus session and using a PROMPT and ACCEPT command. I thought there might be a way to emulate that situation by placing the value I'd like to qualify on within some placeholder in the Parameter section of the job. We have a few users who have limited access to OEM and need to run queries on GRANTS and ROLES for various users etc. I realize there are other ways to do this, however I'm wondering if OEM has a capability like this. Any info is appreciated! Tks!

Looks like you're missing the schema name and you'll want to use QUOTENAME to add delimiters to the objects
e.g.
DECLARE @DATABASE AS VARCHAR(50)
DECLARE @SchemaName as SYSNAME;
DECLARE @TABLE AS VARCHAR(50)
DECLARE @QUERY AS VARCHAR(MAX)
SELECT @DATABASE = '602'
SELECT @SchemaName = 'dbo' --change as appropriate
SELECT @TABLE = 'Items'
SET @QUERY = 'SELECT TOP 10 * FROM ' + QUOTENAME(@DATABASE)+'.' + QUOTENAME(@SchemaName) + '.'+QUOTENAME(@TABLE)
print @query
EXEC( @QUERY)

Which are the required roles/privs for viewing all scheduler jobs in OEM?

Platform: Oracle 11.1.0.6 Enterprise Edition (64) Windows 2008 R2 Server
- I've created a new Admin user in "OEM>Setup>Adminstrators>Create"
- I checked the user in "OEM>Server>Users":
CREATE USER "SA_ADMIN"
PROFILE "DEFAULT"
INDENTIFIED BY "saadminsa"
DEFAULT TABLESPACE "SYSAUX"
TEMPORARY TABLESPACE "TEMP"
ACCOUNT UNLOCK;
GRANT SELECT ANY DICTIONARY TO "SA_ADMIN";
GRANT "MGMT_USER" TO "SA_ADMIN"
- "SA_ADMIN" was granted only the permissions above.
- I can log in OEM as "SA_ADMIN"
- I can see OEM backup jobs and the history
- But I cannot see any "scheduler" jobs in "OEM>Server>Jobs"
- I get a lists of the jobs in "OEM>Scheduler Central" but I cannot display any more information of "scheduler jobs"
- I logged off from OEM
- I granted SCHEDULER_ADMIN role to "SA_ADMIN"
GRANT SCHEDULER_ADMIN TO "SA_ADMIN";
- I logged back in OEM as "SA_ADMIN
- I can now see some scheduler jobs, but not all of the jobs, I still cannot see any of the new jobs I created logged in OEM as SYS.
Which are the required roles/privs for viewing all scheduler jobs in OEM?

if you grant "SYSDBA" to the new Admin user then you can see the "scheduler" jobs.
GRANT SYSDBA TO "SA_ADMIN";
I wanted to grant "read" access in OEM for the new user.
This behaviour is strange.
Without the "SYSDBA" role the new user can see the OEM backup jobs that were create in as SYS, but it cannot see the "scheduler" jobs.

Required roles/privs for viewing all scheduler jobs in OEM 10g

Hello,
I would like to know wchich role/priv schould have user to view all scheduler jobs
in OEM console 10g. My user can see only few jobs in Scheduler jobs part of OEM 10g. User sys see all scheduler jobs.
Thank you for reply

Hi,
If this is a highly privileged user you can consider the CREATE ANY JOB privilege. But this privilege allows a user to run code as any other user so it should only be granted very carefully.
A user can also view any job he is granted ALTER privileges on directly.
Hope this helps,
Ravi.

Unable to launch jobs in OEM under Windows XP

I have not found a way to successfully launch a job in OEM 2.2 (Oracle 8i) under Windows XP. All jobs fail with a VNI-2015 authentication error. According to the Oracle documentation, this is because the preferred credentials have not been correctly set up. In fact, I have set up both the database and the node preferred credentials, specifying my Windows username and password for the latter, but it still doesn't work. The Oracle documentation states that the user has to be granted the "login as batch" privilege - but I can see nowhere in Windows XP where this can be done. In any case, I would have thought that, as administrator, I have all the necessary privileges (including "login as batch").
Can anyone help ?

Hi, had similar problem on Windows 2000. Under Admin tools I selected Local Security Policy, Local Policies, User Rights Assignment and then added NT user to Logon as Batch. However, not sure whether these options are available under XP?

Moving Jobs from OEM 9.2 to 10.2

We have a ton of jobs in OEM 9.2 (set up suing the old Java-based GUI).
We would like to install OEM 10g R2 Grid Control, but I can't find any documentation about moving these jobs from 9.2 to 10.2.
Does anybody know if this is even possible?

Oracle should have some migration tool for jobs from 9.2 to 10g since they changed the tables completely. Let say we have migrated the jobs to 10g this time manually.They may comeup with different tables design again in next version 11i.So we need to keep on creating new jobs on new version since they desupport the old version ..we have no other option..

Cancelling job using OEM

1)If a OWB process is run as a job using OEM and if it is interrupted or aborted due to database shutdown or I try to remove job using OEM, I run into a problem.
When the database was disconnected, the job that was running (and associated with a OWB process package) leaves something like a lock on the package. I am not able to recompile that package.
2) When I removed a job using OEM, it shows the status as deleting, but that never completes.
How do I identify and remove the locks if any and clean it up?
Thanks,
Tapas

Tapas,
Your questions are really about OEM/Intelligent Agent rather than OWB. The OEM forum is here Enterprise Manager
Regarding #1, from OEM doc: "If the Agent goes down for any period of time while the job is running, the Agent will return a job status message "Agent was down." This does not affect job operation, but merely indicates that the repeating job did not run as scheduled during the period the Agent/node was down." Could this be your case?
Regarding #2, I found this thread "Pending Deletion (job)" on OEM Forum, please see if it helps you Pending Deletion (job)
Nikolai

Submitting job in OEM

Hi,
When I am submit job from OEM it directly moves to History
section and displays the status "Failed".
If I do not use the parameter 'job_queue_processes' the
submitted jobs are directly move to active section. But they are
never executed.
Thanks,
Tarek

hello
here are some steps if u want to run a job in console for
Oracle8.1.7 on Windows2000
1 Set The KEY
set the registry value OSAUTH_PREFIX_DOMAIN in
HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\HOMEID to FALSE.
If there is no specified key there, create one.
2 . Using Oracle Administration Assistant for Windows NT
Use this tool to add a user on machine which u’ll login
as when doing any job like backup,exp,imp.(i've used internal)
now u’ll login as internal on windows .
3. GIVE RIGHT – Logon as a Batch Job
To give the windows user the right – logon as a batch job ,
use control panel->administrative tools->local security
Now, the internal user must be given the right specified.
4. Set Preferred Credentials
Set the preferred credentials in the Console for
the node as with any user with sysdba privileges like
internal/oracle.(when u've given internal the logon as a batch
job
set preferred credentials to internal .
5. Log in as internal on windows and take backup.
for backup,u need internal as either backup operator
or administrator
still if u've some problem,
mail me at [email protected]
regards.

Registering LOAD job with OEM fails

I tried to register a Mapping from a flat file to a table (SQL*Loader job) from OWB 9i (9.0.3) to OEM (9.2). This worked fine. However, the job failed to run because as the output states: the controlfile is not passed. And I can see that it is not among the job parameters.
How can it be that the standard job registering process does not include that essential parameter?
Is there a way to get a data load job properly defined in OEM?
Why is this job scheduled as a TCL job and not as a LOAD job?
thanks very much for any input!
Lucas

Lucas,
Your first issue is regarding the control file not being passed. In order to fix that you have to specify the control file in the mapping configuration. Beware that this control file is being read through utl_file, i.e. you will have to set the utl_file_dir in the init parameters of your database to the correct directory in order for the database to be able to read it. Basically, the control file is being read in order to fill the audit tables with the correct data.
Your second issue is regarding the type of job. As you may know OWB 'integrates' with Oracle Workflow (OWF) as well. The OWF solution also relies on the use of OEM for job execution. All of that is currently managed by Workflow Queue Listener. In order for Workflow Queue listener to be able to correctly handle the OEM jobs (defined as external functions in OWF) the job has to be defined as is. Besides, with the current way of registering the jobs all jobs (PL/SQL, ABAP or SQL Loader) are registered in the same way and directed by parameters.
Hope this helps,
Mark.

Registering JOBS in OEM

Similar Messages

Maybe you are looking for