My Oracle Support Banner

OBIEE 12c: FMW Log Viewer Returns No Results When OBIS Logs Are Searched By Username (Doc ID 2654017.1)

Last updated on APRIL 03, 2020

Applies to:

Enterprise Manager for Fusion Middleware - Version 12.2.1.3.0 and later
Business Intelligence Suite Enterprise Edition - Version 12.2.1.3.0 and later
Information in this document applies to any platform.

Symptoms

When a user reports a problem / issue, the OBIEE Administrator wants to review all log entries related to that user around the reported time frame, especially from the OBIS (-query, -diagnostic) and OBIPS (sawlog) logs.

When using the Log Viewer in EM, or the WLST displayLogs command to search the OBIS logs by user name ... no results are returned. For example:-

1. Login to /analytics, say as the "testuser1" user
    Run an analysis (with loglevel of 2 or higher enabled, so entries are written to the obis query log)

2. Open the OBIS -diagnostic and -query log files in <DOMAIN_HOME>/servers/obis#/logs, and see entries with [username: testuser1]
    Open the OBIPS sawlog log file in <DOMAIN_HOME>/servers/obips#/logs, and see entries with [userID: testuser1]

3. Login to FMW Console (/em)
    3.1 Navigate to biinstance > Overview tab > Click on View / Search Log Files link
    3.2 In the Log Messages page:
    3.3 Click on View > Columns. Select the User column.
              >> It is observed that the User column is empty for any entries from an OBIS log, but is populated for entries from WLS and OBIPS logs
    3.4 Click on the Search button. Set the Date Range (for example, Most Recent: 2 Hours). Select all Message Types. Click Add Fields button > Check on User > Click Add > Enter the user name (for example: testuser1). Click the Search button.
              >> See results are returned for obips (with "testuser1" in the User column populated), but there are none for obis1

4. On the OBIEE server:
    4.1 Launch WLST.  For example: <ORACLE_HOME>/oracle_common/common/bin/wlst.sh
    4.2 Connect to the domain. For example: connect('<WLS Admin User>','<WLS Admin Password>','t3://<Server>:<Admin Server Port>')
    4.3 Query the OBIPS logs via the displayLogs command. For example: displayLogs(query='user eq testuser1',target=['obips1'], last='2h', type=['ERROR','INCIDENT_ERROR','WARNING','NOTIFICATION','TRACE'])
              >> See results returned.
    4.4 Query the OBIS logs via the displayLogs command. For example: displayLogs(query='user eq testuser1',target=['obis1'], last='2h', type=['ERROR','INCIDENT_ERROR','WARNING','NOTIFICATION','TRACE'])
              >> See "No messages found. Try using different options"

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!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.