My Oracle Support Banner

OAC-Essbase: Essbase MaxL Script Job Log Files Not Visible (Doc ID 2432384.1)

Last updated on AUGUST 09, 2018

Applies to:

Oracle Analytics Cloud Service - Version 18.2.1 and later
Information in this document applies to any platform.

Symptoms

When running Jobs to call MaxL scripts, the output log file is not retrieved when using the Classic OAC-Essbase Analytics URL: https://OAC-Essbase-Server/essbase/ui. It shows up empty.

In the u01/data/logs/essbase/platform.log, see below error:

[2018-08-09T06:45:38.599+00:00] [ess_server1] [ERROR] [] [oracle.essbase.admin.jobs.types.MaxLJob] [tid: 114] [userId: username] [ecid: 45127007-9114-44ac-aa02-6e8e350f7875-00000412,0:5] [APP: ESSBASE] [partition-name: DOMAIN] [tenant-name: GLOBAL] /users/<username>/<MaxlOuptutFile>.out[[
java.nio.file.NoSuchFileException: /users/<username>/<MaxlOuptutFile>.out
        at sun.nio.fs.UnixException.translateToIOException(UnixException.java:86)
        at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
        at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)
        at sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:214)
        at java.nio.file.Files.newByteChannel(Files.java:361)
        at java.nio.file.Files.newByteChannel(Files.java:407)
        at java.nio.file.spi.FileSystemProvider.newInputStream(FileSystemProvider.java:384)
        at java.nio.file.Files.newInputStream(Files.java:152)
        at java.nio.file.Files.newBufferedReader(Files.java:2784)
        at java.nio.file.Files.lines(Files.java:3744)
        at java.nio.file.Files.lines(Files.java:3785)
        at oracle.essbase.admin.jobs.types.MaxLJob.searchFor(MaxLJob.java:152)
        at oracle.essbase.admin.jobs.types.MaxLJob.run(MaxLJob.java:110)
        at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:209)
        at weblogic.invocation.ComponentInvocationContextManager._runAs(ComponentInvocationContextManager.java:348)
        at weblogic.invocation.ComponentInvocationContextManager.runAs(ComponentInvocationContextManager.java:333)
        at weblogic.work.LivePartitionUtility.doRunWorkUnderContext(LivePartitionUtility.java:54)
        at weblogic.work.PartitionUtility.runWorkUnderContext(PartitionUtility.java:41)
        at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:640)
        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:406)
        at weblogic.work.ExecuteThread.run(ExecuteThread.java:346)

]]

 

Changes

 

Cause

To view full details, 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 a vibrant support community of peers and Oracle experts.