Request context not set properly error when initiating a dataload in ARM (Doc ID 1625992.1)

Last updated on MARCH 30, 2017

Applies to:

Hyperion Financial Close Management - Version 11.1.2.3.000 and later
Information in this document applies to any platform.

Symptoms

When attempting to start a data load from an existing ARM definition, it errors out immediatly with the following error

 

[ErpIntegrator0] [ERROR] []
[oracle.odi.repex.view.main.auth.AuthMustFilter] [tid: 11] [userId:
<anonymous>] [ecid: 0000KGbp^9UAhKT5uBO5yX1IyuL4000058,0] [APP:
odiconsole] Request context not set properly[[
oracle.odi.repex.model.contexts.RequestContext$RequestContextNotInitializedException: Request context not set properly
at oracle.odi.repex.model.contexts.SessionContext.getOdiInstance(SessionContext.java:46)
at oracle.odi.repex.model.contexts.RequestContext.getLocalOdiInstance(RequestContext.java:38)
at oracle.odi.repex.view.main.auth.AuthMustFilter.doFilterInternal(AuthMustFilter.java:37)
at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
at oracle.odi.repex.view.main.auth.ThreadAuthFilter.doFilterInternal(ThreadAuthFilter.java:38)
at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:324)
at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:460)
at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:163)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3730)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2273)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)

 

Changes

 Two things:

1) The period was locked in ARM

2) The 'Global POV' in ERPi is set to Y

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms