Problem submitting jobs in OEM

Hi,
I've been trying to utilize backup manager inside the OEM, and finally, I am able to log into OEM, my preferred credentials are set properly to user oracle, my user has been given the logon as batch job privilage.
I've also given my user Full Control to my Oracle Home directory. Prior, I only gave it read/write privilages, and it gave me the error "operating system resource shortage". Now, after Full Control, it tells me "Access is denied".
What have I missed? Is there some addition permissions I need to assign? Please help. I feel like I'm almost there, but as a novice, am missing the last clues.
Thanks in advance,
Willis Chang
Oracle 8.1.7
Windows 2000 Professional

Hi Rajkumar,
I can definitely help you with that part. However, you may end up in the same boat as me. Or maybe you might be able to help me figure out my problem afterward.
First, you are supposed to be using an NT (2000) account as your preferred credentials. I hope you already know that.
Secondly, you need to assign that user to the Administrators group and the ORADBA group.
Thirdly, in your problem, you need to go to Control Panel > Administrative Tools > Local Security Policy
Then you navigate the following tree:
Local Policies > User Rights Management > Logon as a batch job. Assign your user that right, and it should start working. Please post again so that I know if you were successful, as it might help me figure out my problem.
Thanks,
Willis

Similar Messages

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.

Submitting jobs from OEM

Hi !
After hours of hard work, i got my agent up and running,
(fixing ownership of files etc.)and was pleased to see the auto-
discover function working properly. But... when trying to submit
a job, it failed with the message "error processing the job que".
I am using OEM 1.4.
Will it help to upgrade to OEM 1.X ?
John
null

Hi!
I'm using OEM 1.6, but I get a similar message: "error accessing
job queue"...
Using Oracle 8.0.5 (shipping), with SuSe 5.3.
Any help would be appreciate,
Thomas
John S. Henriksen (guest) wrote:
: Hi !
: After hours of hard work, i got my agent up and running,
: (fixing ownership of files etc.)and was pleased to see the
auto-
: discover function working properly. But... when trying to
submit
: a job, it failed with the message "error processing the job
que".
: I am using OEM 1.4.
: Will it help to upgrade to OEM 1.X ?
: John
null

Get back to previously submitted job in OEM

Hi all,
From Advisor Central I clicked "implement" button to shrink a table segment. I strayed away to look for something else but I don't know how to get back to the job to check the job status. I searched in the Jobs tab and Reports tab based on the job name (I gave a special name to the job) and no luck. It must have a way.
Thank you very much and have a great weekend!!
Shirley

Hi,
>>I searched in the Jobs tab and Reports tab based on the job name
You need to take a search at the Advisor Central page
Cheers
Legatti

Submitting jobs

I have problems submitting jobs, im- or export, from within the enterprise manager. (Error-Msg: VNI-2015)
This is my configuration:
* OS: W2K
* DB/EMS: 9.2.0.1
* User <Computer-Name>\OraDBA with "logon as batchjob" privilege
* User OraDBA as Administrator-account in EMS with preferred credentials set to the above mentioned OS-User and the DB-User "System"
Any idea what is wrong?

There are multiple ways to setup a virtual cluster. Some people prefer to use one less core then the total number of cores and others use half the number of cores. Either way If you only have two cores it is recommended to only use one.

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.

Problem in submitting job through Pl/sql

Hi,
I have a procedure with parameters as shown below.
Pkg1.Proc1(indate date, innum1 number, innum2 number)
I am trying to execute this procedure by submitting jobs through another procedure and passing the parameters dynamically. I found the jobs are not getting submitted. Please see the code inside the procedure as below.
dbms_job.submit(var1,'BEGIN pkg1.Proc1(''' || i_date||''','|| i_num1||','||i_num2||'); END;',SYSDATE);
I have tried as following also
dbms_job.submit(var1,'BEGIN pkg1.Proc1(''''' || i_date||''''','|| i_num1||','||i_num2||'); END;',SYSDATE);
both time the procedure is running fine but the job is not seen as submitted.
when I am executing it as follows in sql * plus, it is executing fine.
dbms_job.submit(var1,'BEGIN pkg1.Proc1(''15-aug-2007'',1,2); END;',SYSDATE);
Please let me know if I need to change anything in my code.
Regards,
Poulose

Hi Pls find the portion below.
process_id is of type number and having value 1001. v_business_dt is a date variable. and i_module is a number with value 1.
DBMS_JOB.ISUBMIT(CF_CRM.process_id,'BEGIN DBK_CRM_PROCESS_TRACKING.RUN_PROC(''' || v_business_dt||''','|| i_module||','||CF_CRM.process_id||'); END;',SYSDATE);

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.

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?

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.

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.

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

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 !)

Problem creating job steps variants

Hi Gurus!
I have a problem with job steps creation.
In my program I need to copy the exist job with some condition accords to job steps variants.
But when I create the new job and it steps and variants in SM37, I can not see the variants names, only number.
For example in template that I am copying it looks like that:
No. Program name/command      Prog. type Spool list   Parameters              User Lang.
1              RMCVNEUA                  ABAP                        BW_TEMPLATE       aaa     EN
But in job that I create it is:
Program name/command      Prog. type   Spool list   Parameters               User Lang.
RMCVNEUA                          ABAP                           &0000000000271     ddd     EN
How can I create steps with variant names instead of numbers/indexes?   BW_TEMPLATE instead of &0000000000271.
My code:
CALL FUNCTION 'JOB_OPEN'
    EXPORTING
      jobname          = lv_jobname
      sdlstrtdt        = lv_date
      sdlstrttm        = lv_time
    IMPORTING
      jobcount         = lv_jobcount
    EXCEPTIONS
      cant_create_job = 1
      invalid_job_data = 2
      jobname_missing = 3
      OTHERS           = 4.
SUBMIT (ps_tbtcp-progname) VIA JOB pv_jobname NUMBER pv_jobcount
                                 USING SELECTION-SET ls_cat-variant
                                 AND RETURN.
CALL FUNCTION 'JOB_CLOSE'
    EXPORTING
      jobcount                          = lv_jobcount
      jobname                           = lv_jobname
     direct_start                      = lv_imm_run
   EXCEPTIONS
     cant_start_immediate              = 1
     invalid_startdate                 = 2
     jobname_missing                   = 3
     job_close_failed                  = 4
     job_nosteps                       = 5
     job_notex                         = 6
     lock_failed                       = 7
     invalid_target                    = 8
     OTHERS                            = 9
Edited by: Dani_K on Oct 27, 2010 4:35 PM

No any suggestions?

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)

Problem submitting jobs in OEM

Similar Messages

Maybe you are looking for