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.

Similar Messages

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

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.

Not able to deploy to register my mapping with OEM

I am new to data ware housing.Iam using oracle9i warehouse builder.I created a source,target and mapping between these two using mapping editor.Then I have generated scripts bot not able to make OEM register.When I click the button "OEM register", it give 2 error messages.
1. Specified Connection is not a valid Run time schema
2. Please Make sure OEM Client installed locally or enter correct OMS domain domain in the configuration parameter.
I know that some parameter should be set in preference dialog box but no idea how to set that.
Can anyone help regarding this.
Thanks

created a project with following structure
MyProject
----MySource (FlatFile)
----MyTarget
Created a map between these 2 and named it "MyMapping".After successfully generating code for the map, "GenerationReults[succeed]" Dialog box opened.But Deploy and Run button are disabled so I tried clicking OEM Register button to get the following error message even after setting preference values.
Please tell me how to make those buttons enabled.Is there another way.
Error--
Failed to register the jobs with OEM.: OEM Registration Failed. Please make sure you have OEM client installed locally, the Oracle Management Server is running, and you have entered correct connection information and OEM information under 'Preferences'.
Incorrect domain entered or node not discovered. Please enter correct OMS domain name in the configuration parameter and make sure that the OMS is running.
oracle.sysman.emSDK.client.omsClient.NoDomainException: singapore
Job object failed to create, check to see if user has credentials.

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.

Owb job (import) scheduling with oem 2.2

Hi all,
System config :
oracle 8.1.7 enterprise, oem 2.2.0.0.0 and owb 3i. on
windows nt workstation.
I created necessary source and target module and mapping is
completed in owb. When I generated scripts on mapped objects,
it created a ctl script and tcl scripts. when I try to register
with OEM register it is giving following error message
"failed to register the jobs with oem. oem registratrion failed.
please make sure you have oem client installed locally. the oem
is running and you have enter informationa oem inforamtion under
preferences".
But actually oem is running on my system, oracle8ihomeagent
is running and other things are also fine.
Can any one help me in addressing the problem.
Thanks a lot.
with regards
sreenivas

As bazzza mentioned, try a simple SQL script with say "select 1 from dual".
What is the RMAN Script doing? A big Backup? If it has not failed with an error, then check from the database to see if the session is doing something.

OWB Job Registration with OEM

We are new users of OWB 2.0. OWB and OEM are installed in the same machine,platform is NT.
We can not register the job with Enterprise Manager successfully and it has not any error message. Once we click the "OEM Register" button,the application will not work.
We try to run the deployed .bat file in DOS mode, it pops up the following message:
Exception in thread "main" java.lang.NoClassDefFoundError: oracle/sysman/emSDK/c
ommon/registry/RegistryImplementationOperations
at
at oracle.sysman.emSDK.client.omsClient.Client.doLogon(Client.java:1192)
at oracle.sysman.emSDK.client.omsClient.Client.silentLogin(Client.java:761)
at oracle.wh.generator.common.WBOEMDeployJobs.doCreateNewJob(WBOEMDeployJobs.java:200)
at oracle.wh.generator.common.WBOEMDeployJobs.main(WBOEMDeployJobs.java:468)
Could you please tell us the reason of it? Thank you.
null

Hi,
I assume you are using OWB 2.0.4.78.
If you are getting a progress box which does move beyond 0% then this is due to a bug in this release.
I suggest that you apply the patch and upgrade to 2.0.5. The patch file available for download from metalink site is some 44Mb in size.
This should solve your problem.
regards,
Shekaran

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.

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.

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 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.

Pb with agent Jobs on OEM

Hi.
I try to do Exports with OEM 2.1.0.1.0 Server Management configuration.
1 - I complete the Export Wizard, valid it.
2 - The OEM Agent create a job, program it, start it and finish it with status 'FAILED'
3 - I can see that the job failed because it can not open the Export log choosen in the wizard.
4 - Indeed, there is no Export file and no Export log created !
5 - I try the same Export directly with the exp command and that succeeds
information 1 : I think of having changed correctly
the Prefereed Credentials with an correct NT User (set up to "Logon as a batch agent") and a SysDBA database usr.
information 2 : when i use OEM Agent to execute a windows batch in which are the Exp command and the necessary parameters, that succeeds
So i have the problem only when the OEM Agent try to do himself this export
thank you to help me
(Sorry. English is not my native language !)

Hi.
I try to do Exports with OEM 2.1.0.1.0 Server Management configuration.
1 - I complete the Export Wizard, valid it.
2 - The OEM Agent create a job, program it, start it and finish it with status 'FAILED'
3 - I can see that the job failed because it can not open the Export log choosen in the wizard.
4 - Indeed, there is no Export file and no Export log created !
5 - I try the same Export directly with the exp command and that succeeds
information 1 : I think of having changed correctly
the Prefereed Credentials with an correct NT User (set up to "Logon as a batch agent") and a SysDBA database usr.
information 2 : when i use OEM Agent to execute a windows batch in which are the Exp command and the necessary parameters, that succeeds
So i have the problem only when the OEM Agent try to do himself this export
thank you to help me
(Sorry. English is not my native language !)

WorkFlow OWB Jobs

Is there a way to run the Workflow jobs independent of Oracle clients (OWB and OEM)? We currently have OWB client for windows installed on our machine and cannot use windows to run our jobs in our production environment. Is there a way to run OWB jobs in unix?

Hi,
Assuming the 3 users/schemas after the OWB installations are owb,owbuser,owbrun(runtime)
Login with Owbuser ID/pwd to Unix sqlplus
then execute the following line (all in one line)
@/build/owb92/owb/rtp/sql/oem_exec_template.sql owbrun CDS_TXN_LOAD_PROCESS_FLOW_LOC PROCESS CDS_TXN_LOAD_PROCESS_FLOW_01 "," ","
where
@/build/owb92/owb/rtp/sql/oem_exec_template.sql - complete path of oem_exec_template.sql file
CDS_TXN_LOAD_PROCESS_FLOW_LOC - process flow location
CDS_TXN_LOAD_PROCESS_FLOW_01 - process flow name
PROCESS - keyword to run workflow process
Cheers
Ranjeesh

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

How to register a Location with database link in Ombplus?

Hello,
what's the detailed syntax in owb 10.2 to register a location with a database link?

Hi,
thanks that helps.
Now i found out that after an import of the location the field "from Location" is not set. I need to set it to OWB_REPOSITORY_LOCATION.
How can i do it?
OMBALTER LOCATION 'Locname' SET PROPERTIES (FROM_LOCATION) VALUES ('OWB_REPOSITORY_OWNER') does not work
-> Property FROM_LOCATION is not defined in class ORACLE_GATEWAY_LOCATION
Cann you help me again?
Thanks
Helga

Registering OWB jobs with OEM

Similar Messages

Maybe you are looking for