OEM Scheduled Jobs

Can anyone answer this question?
Thanks,
John
Is OEM set up to run UNIX command scripts or is OEM schedule just a way to manage the DBMS_Job queue?

In 10g, it uses DBMS_SCHEDULER instead of dbms_job

Similar Messages

  • OEM Scheduled Job Not Assuming OS User File Permissions

    I have defined and scheduled a job using OEM Grid Control that executes an OS level command which is a script containing the HP-UX find command. When I run the script at the OS level the script completes successfully. When the job scheduler runs the job it fails because the find command doesn't have permission to recursively traverse the subdirectories even though the subdirectories are owned by the process executing the find command. The preferred credentials for the job are set to the same user that I used to run the job manually. Why would this be happening?
    We're using OEM Grid Control 10.2.0.3.0 running on Linux used to manage Oracle 10G on HP-UX. Please help.

    Please paste the script and error

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

  • Scheduling jobs in OEM

    Hi,
    I get the following error-message:
    VNI-2015 : The Node preferred credentials for the target node are either invalid or do not have sufficient privileges to complete the operation.
    On Windows platforms, the Node credentials specified for the Windows target should have the "Logon as a batch job" privilege.
    Logon as batch job right has been given to the administrator-user. Node credentials have been set. I am trying to execute the OEM_EXEC_TEMPLATE. The used parameters: RUNTIME_OWNER LOC_STAG PLSQL MAP_CREDIT_LIMITS "," ","
    I have selected the Run SQLplus script option. Another question is where to find the deployed process scripts to execute.
    Hope you can help. Thankz in advance.
    Eric

    Eric,
    The preference is all about being able to logon as a background user and execute a batch job. If you are on Windows 2000, you would find this setting under your control panel, administrative tools, local security policy, local policies, user rights assignments, for the user you have selected to be your default logon credential. The 'Log on as batch job' privileges is by default not available for anyone, and you have to explicitly grant it in order for the OEM scheduling piece to work. This is documented in the installation and configuration guide.
    Hope this helps,
    Mark.

  • Monitor Scheduled Jobs in OEM

    Does anyone use OEM to monitor the success or failure of Scheduled Jobs?
    Can somebody point me in the right direction, either documentation or how you do this at your place of work.
    Documentation out there seems to be a little scarce with regards to this.
    Thanks!

    I should make myself a little clearer. I would like a job failure to automatically notify me - whether by email or any other means.
    The small bit of documentation that I find is in the OEM Advanced Configuratin Guide (B16242-01) section: 12.4 Passing Job Execution Status Information
    Thanks.

  • OEM tables for scheduled jobs

    Hi,
    What are the DB tables in which OEM is saving scheduled jobs that one can add inside the OEM web interface?
    I have more than 100 jobs scheduled inside OEM and I want to get a report with job name, what that job is doing, etc. The kind of info that I can find in DBA_SCHEDULE% tables inside a DB.
    I tried to get the info from DBA_SCHEDULER_JOBS but the jobs in this view are for DB only, and not the jobs that OEM is running against the databases registered with OEM.
    Thanks,
    Daniel

    See if you find the information you want in the MGMT$JOB* views.
    Eric

  • Scheduling jobs in OWB 10.2

    I'm busy with a migration of OWB 10.1 to 10.2 and I had almost everything up and running
    except
    the scheduled jobs.
    In 10.1 my predecessors made scheduled jobs which started in their turn a procedure which then started the process flow with wb_rt_api_exec.
    After migration I could not get those jobs going anymore.
    After investigation I could see that the procedures (starting the proess flows) ran when started with the runtime rrepository owner as launcher.
    Even te jobs ran when they were started with the session credentials (iow the credentials from the logged on user being the runtime repository owner).
    I've seen the atricles telling that you need to set the preferred credentials to the runtime repository owner in oem if you want to get it running from there.
    Anyhow I could start it by recreating the jobs with the runtime repository owner as the creator.
    Doens anybody know why it could run in owb 10.1 with sys as creator and why it nn longer works in 10.2.
    I checked the 10.1 installation and I haven't found any priviileges granted to sys that where not granted in the 10.2 installation, so there is no diff.
    Any help would be welcome.

    Hi,
    You cannot schedule direct mapping. You need create Process flow then u need to attach calendar for that. Go to Control Centre Deploy process flow and schedule and further click on start.
    Regards,
    Ava

  • Scheduling Jobs

    I have tried to create scheduling jobs and schedule them. But the error message is 'Server throws in an exception'. My server is O8.0.5. Hope someone can enlighten me.

    <BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Justin Cave ([email protected]):
    Are you using an ODBC client to schedule these jobs? I'm not clear what you're trying to do.
    Justin Cave
    ODBC Development<HR></BLOCKQUOTE>
    I used the OEM on my server. It is used also for my routine exporting of tables from my databases. I tried both ways, creating scheduling job on the OEM console, and scheduling on the export dialog box, but the same error message came. Then, it exited my OEM console/data manager, depending on the active window.
    null

  • OEM - Active job details

    I've 2 Production Servers with Prodction Databases which runs 24/7 basis. and One Test Server with Test Database, I was configured my test database with OEM (oracle 8i), and Scheduled jobs to take daily backup of my Production databases. It was working fine and mean while my Test database is CRASHED.
    Try to recover my test database, but failed, then I reinstalled oracle 8i in my Test database and Re-created database, and also reconfigured my OEM in Test database, and again I scheduled a job (different) to take backup of my Production database.
    When I observed in my production Database, i found that, earlier backup schedule is still running and it takes backup at a perticular time. Now, at present I want to stop that job schedule(before crash - earlier), but could not find where the earlier information is stored, I can see the present configured job schedules in my Test Database.
    Now I want to know that when I schedule a job from my Test database, where this information is stored in my Production database, and how to stop perticular jobs in production database (without using my test database OEM).
    Thanks
    Shafi

    Thank you Rajiv,
    I check both and obectGUID exist in both places (Resource Object and Process Definitions).
    For the job here are the values of the fields:
    Batch Size
    Batch Start
    Filter     Filter
    Incremental Recon Attribute: uSNChanged
    IT Resource Name: Active Directory     
    Latest Token     
    Maintain Hierarchy: no     
    Manager Id     Manager Id
    Number of Batches: All     
    Object Type: User     
    OIM Employee Type     
    OIM Organization Name: Xellerate Users     
    OIM User Type: End-User     
    Resource Object Name: AD User Trusted     
    Scheduled Task Name: Active Directory User Trusted Recon     
    Search Base: OU=....,O=....,DC=...,DC=.....     
    Search Scope: subtree     
    Sort By: samAccountName     
    Sort Direction: asc
    I'm guessing I'm doing something wrong, I just need to know what LOL

  • Database shutdown and scheduled jobs

    Hi:
    We are planning to shut down our server for two days, and would like to know following.
    1. We have about 100 jobs scheduled throughout the day. We will shut down the server for two days. What will happen when we restart the server, will same daily scheudle job will execute twice ?
    2. Is there any place in OEM where you select all schedule jobs and suspend all ?
    3. Is there any place in OEM where you select all suspended jobs and resume all ?
    Thanks

    Hi,
    If all your jobs are running from OEM, then simple solution will be to define blackout period for the duration your server will be out, so when the server comes up then jobs will be started except for the jobs to be run during black out period.
    Regards

  • Launchd and scheduled jobs

    From what I've read, you can't rely on launchd for scheduled jobs - in my case I want to back up at 3am in the morning - upon it being woken by another application.
    Now that cron is disabled - how can I achieve this scheduled tasks?
    I cannot believe that Apple have released into production a component that simply does not work ( that relies on the machine being on 100% without sleeping etc ).

    Hi Stewart:
    I can't speak to 10.4.3, but in 10.4.2, I just rebuilt my /etc/crontab file the way I wanted it, because cron still is a part of 10.4.2, and my Mac stays on 24x7.
    Looking at the "OEM" version of Tiger's crontab, it appears that what they did was basically make a crontab file full of comment lines, so I guess when cron parsed it, there was nothing there telling cron that it had to launch something.
    So, if you make a bonafide crontab file, I think (in 10.4.3) you'll be okay. If you don't recall the format for the crontab file, or don't have access to an old legacy one from 10.2 or so (I never had 10.3 so don't know whether they used cron or launchd), I can post mine here, if you'd like, that you could use as a model. I'll check back sometime later this week and see if you'd like me to post it here.
    Anyhow, after I made a new crontab file, I had asked on this forum how to disable the launchd daily/weekly/monthly stuff. Although it isn't important to do so, I figured, why run it more often than once daily/weekly/monthly, at what I understood would be random times of day, if the jobs would even be run at all, based on all the reports about undesired behavior caused by reboot, sleep, etc.?
    Some smart person on this forum told me that I could take the three com.apple.periodic-daily/weekly/monthly.plist files and save them off somewhere else other than in /System/Library/LaunchDaemons. So I just tarballed 'em (tar -cvvvzf com.apple.periodic-\*.plist.tgz com.apple.periodic-monthly.plist com.apple.periodic-weekly.plist com.apple.periodic-daily.plist) and left the tarball right there in /System/Library/LaunchDaemons, then deleted the originals. If I ever need 'em again I can just "tar -xvvvzf com.apple.periodic-\*.plist.tgz".
    So as near as I can tell, I don't even have to fuss about whether the daily/weekly/monthly jobs are being launched by launchd, and as near as I can tell, the daily/weekly/monthly jobs are being run daily, weekly, and monthly, as appropriate, and at the desired times of day, by cron and crontab.
    Quicksilver G4   Mac OS X (10.4.2)  
    Quicksilver G4    
    Quicksilver G4    

  • Empty "scheduled jobs" list in control center

    Hi all,
    due to a move to a new data warehouse environment i added a new configuration
    to my OWB project with new locations, control center etc.
    I was able to deploy and run all of the owb stuff into the new environment except all
    the scheduled jobs to deploy into OEM,
    which owb generates for all the process flows that have a schedule assigned ("Referred Calendar" in Configuration).
    The list of "Scheduled Jobs" in control center for the target location just appears empty.
    Are there any additional settings or privileges missings,
    i.e. for target location, owb repository owner, configuration, location, ...?
    Old env is Oracle DB 10.2.0.2 on Win Server 2003 32 bit, Workflow Server 2.6.4, OWB Client 10.2.0.1.31, OWB-Repository 10.2.0.1.0.
    New env is Oracle DB 10.2.0.2 on Redhat 64 bit, Workflow Server 2.6.4, OWB Client 10.2.0.1.31, OWB-Repository 10.2.0.1.0.
    Any hints would be appreciated.
    Thanks,
    Matthias

    Hi,
    I found out that I have to create a new schedule module.
    In the create module wizard you'll have to define a location where schedules
    are deployed to and there I defined the new target location.
    It is not possible to assign different deployment locations for same schedule
    module in each configuration.
    I don't know if it is a bug or a feature, but with the new seperate schedule module
    it works.
    Just to let you know,
    Matthias

  • ADF_FACES-60097 error while opening a random schedule job

    Hello,
    recently i'm facing a error in oim while i open the schedule job
    When i logeed in with xelsysadm
    click on advanced.then click on System management
    search all the scehdule jobs
    open a random schedule job
    error occured!!
    Error: An error Occurred while retrieving trigger for the schedule job.
    ADF_FACES-60097
    please help
    regards
    tp

    Hi Frank,
    Thanks for the reply. I am using it as an inline popup. I am trying to create command links dynamically in an iterator. When a link is clicked a popup window opens. The text of the link is passed to the popup window by creating a variable in the session scope ( I even tried request scope) by an action listener in the backing bean.
    I tried to create another simple application with a static command button which passes its text to popup window through a session scope variable. It worked fine. I am not sure why the same procedure is not working in my original application. Can you give me a hint what could possibly go wrong according the exception stack trace ?
    Thanks,
    KK

  • Error while creating a Scheduled job in OIM 11g

    While creating a scheduled job, if i click on the Task and search to select the value, i get the following error.
    <Nov 14, 2011 5:10:24 PM IST> <Error> <oracle.adfinternal.view.faces.config.rich
    .RegistrationConfigurator> <BEA-000000> <ADF_FACES-60096:Server Exception during
    PPR, #1
    javax.servlet.ServletException: java.lang.AssertionError
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.jav
    a:341)
    at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:27)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.ja
    va:57)
    at oracle.help.web.rich.OHWFilter.doFilter(Unknown Source)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.ja
    va:57)
    at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.j
    ava:205)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.ja
    va:57)
    at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter
    (RegistrationFilter.java:106)
    at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterL
    istChain.doFilter(TrinidadFilterImpl.java:447)
    at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter
    .java:60)
    at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterL
    istChain.doFilter(TrinidadFilterImpl.java:447)
    at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilt
    erImpl(TrinidadFilterImpl.java:271)
    at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilte
    r(TrinidadFilterImpl.java:177)
    at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFi
    lter.java:92)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.ja
    va:57)
    at oracle.iam.platform.auth.web.PwdMgmtNavigationFilter.doFilter(PwdMgmt
    NavigationFilter.java:122)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.ja
    va:57)
    at oracle.iam.platform.auth.web.OIMAuthContextFilter.doFilter(OIMAuthCon
    textFilter.java:108)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.ja
    va:57)
    at oracle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:1
    76)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.ja
    va:57)
    at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111)
    at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:31
    3)
    at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUt
    il.java:413)
    at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.jav
    a:94)
    at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:1
    61)
    at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.ja
    va:57)
    at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:13
    6)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.ja
    va:57)
    at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsF
    ilter.java:27)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.ja
    va:57)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationActio
    n.wrapRun(WebAppServletContext.java:3715)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationActio
    n.run(WebAppServletContext.java:3681)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
    dSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
    120)
    at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppS
    ervletContext.java:2277)
    at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletC
    ontext.java:2183)
    at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.j
    ava:1454)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    Caused By: java.lang.AssertionError
    at org.apache.myfaces.trinidad.component.ChildArrayList.__removeFromPare
    nt(ChildArrayList.java:191)
    at org.apache.myfaces.trinidad.component.ChildArrayList.add(ChildArrayLi
    st.java:53)
    at org.apache.myfaces.trinidad.component.ChildArrayList.add(ChildArrayLi
    st.java:69)
    at org.apache.myfaces.trinidad.component.ChildArrayList.add(ChildArrayLi
    st.java:33)
    at oracle.iam.consoles.faces.render.canonic.UIValue$UIEntitySelector.sea
    rch(UIValue.java:1670)
    at oracle.iam.consoles.faces.render.canonic.UIValue$UIEntitySelector.acc
    ess$2400(UIValue.java:1467)
    at oracle.iam.consoles.faces.render.canonic.UIValue$EntitySelectorQueryL
    istener.processQuery(UIValue.java:1787)
    at oracle.adf.view.rich.event.QueryEvent.processListener(QueryEvent.java
    :67)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.broadcast(UIXC
    omponentBase.java:675)
    at oracle.adf.view.rich.component.UIXQuery.broadcast(UIXQuery.java:108)
    at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent$1.r
    un(ContextSwitchingComponent.java:92)
    at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent._pr
    ocessPhase(ContextSwitchingComponent.java:361)
    at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.bro
    adcast(ContextSwitchingComponent.java:96)
    at oracle.adf.view.rich.component.fragment.UIXInclude.broadcast(UIXInclu
    de.java:102)
    at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent$1.r
    un(ContextSwitchingComponent.java:93)
    at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent._pr
    ocessPhase(ContextSwitchingComponent.java:361)
    at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.bro
    adcast(ContextSwitchingComponent.java:96)
    at oracle.adf.view.rich.component.fragment.UIXInclude.broadcast(UIXInclu
    de.java:96)
    at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.broadcastEvents
    (LifecycleImpl.java:902)
    at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(L
    ifecycleImpl.java:313)
    at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.execute(Lifecyc
    leImpl.java:186)
    at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265)
    at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run
    (StubSecurityHelper.java:227)
    at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecuri
    tyHelper.java:125)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.jav
    a:300)
    at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:27)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.ja
    va:57)
    at oracle.help.web.rich.OHWFilter.doFilter(Unknown Source)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.ja
    va:57)
    at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.j
    ava:205)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.ja
    va:57)
    at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter
    (RegistrationFilter.java:106)
    at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterL
    istChain.doFilter(TrinidadFilterImpl.java:447)
    at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter
    .java:60)
    at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterL
    istChain.doFilter(TrinidadFilterImpl.java:447)
    at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilt
    erImpl(TrinidadFilterImpl.java:271)
    at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilte
    r(TrinidadFilterImpl.java:177)
    at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFi
    lter.java:92)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.ja
    va:57)
    at oracle.iam.platform.auth.web.PwdMgmtNavigationFilter.doFilter(PwdMgmt
    NavigationFilter.java:122)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.ja
    va:57)
    at oracle.iam.platform.auth.web.OIMAuthContextFilter.doFilter(OIMAuthCon
    textFilter.java:108)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.ja
    va:57)
    at oracle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:1
    76)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.ja
    va:57)
    at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111)
    at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:31
    3)
    at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUt
    il.java:413)
    at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.jav
    a:94)
    at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:1
    61)
    at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.ja
    va:57)
    at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:13
    6)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.ja
    va:57)
    at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsF
    ilter.java:27)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.ja
    va:57)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationActio
    n.wrapRun(WebAppServletContext.java:3715)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationActio
    n.run(WebAppServletContext.java:3681)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
    dSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
    120)
    at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppS
    ervletContext.java:2277)
    at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletC
    ontext.java:2183)
    at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.j
    ava:1454)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    >
    This behavior is seen in most of the lookups when we try to search for value.
    Please let me know for any configuration steps for the same issue.

    Have you tried restarting the db and the server? I have seen this on user search and a db restart along with server restart solved it for me. Also note that this error in my case was due to wrong mds file. so for you also check ur tasks and any custom xml which might have some errors into it.
    HTH,
    BB

Maybe you are looking for