Exalytics and OBIEE Saw Logs Full of Errors Like "GUID 08587d778e994dacb55279a519dfef43 not found in cache or backend marking as unknown"

(Doc ID 2235568.1)

Last updated on FEBRUARY 23, 2017

Applies to:

Business Intelligence Server Enterprise Edition - Version and later
Oracle Exalytics Software - Version and later
Information in this document applies to any platform.


When using OBIEE on an Exalytics server, OBIEE users are able to login and the application is working as expected, but the sawlogs have many error messages like:

GUID 08587d778e994dacb55279a519dfef43 not found in cache or backend marking as unknown.

saw.connectionPool.getConnection] [ecid: 005Hyo1wWEM3v1jXX1V4Fb000SYc0000cy,0:1:1:1] [tid: 4180547904]
Authentication Failure.
Odbc driver returned an error (SQLDriverConnectW).
State: 08004. Code: 10018. [NQODBC] [SQL_STATE: 08004] [nQSError: 10018] Access for the requested connection is refused.
[nQSError: 43113] Message returned from OBIS.
[nQSError: 43126] Authentication failed: invalid user/password. (08004)[[
ecid: 005Hyo1wWEM3v1jXX1V4Fb000SYc0000cy,0:1:1:1
ThreadID: 4180547904

These errors may occur on any OBIEE environment and not just those on Exalytics servers.


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