nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Oracle Communities

Oracle Analytics and AI

Child Item

Ability to see the server log files in OAC for analytics

User_CR2OC

The ability to see the same log files in OAC as we can see in the back end of OAS, that is, the bi server log, presentation services log etc. for use with analytics reports Alternatively, if the developer option in DV can be added to analytics then that would be very useful.

We are in the process of migrating from OAS to OAC and the lack of visibility of the log files means it is taking a long time to resolve issues. Having to raise a SR to get details of the error for minor issues is taking a long time and we are not always being given the error message or the right cause. I have an issue with writeback but I have no way to see what the error is or been able to get the actual error from Oracle support. If a report failed to run overnight but worked the following day, I would also have no visibility of the error unless I raised an SR.

This must have been raised already as this is a serious omission from OAC that must be causing a large number of SRs to be raised. The existing OCI logging doesn't really log anything that is useful when there is an issue.

Find more posts tagged with

Under Review

Status: Under Review

Comments

Bret Grinslade - Oracle Analytics-Oracle

The OCI audit and diagnostic logs have essentially the same information as the OAS logs. The format is a bit different.

Is there some specific information you are not able to find for auditing or troubleshooting?

User_CR2OC

Hi Bret,

The main information I am looking for is visibility of the logs for writeback. Since I raised the idea, I am now able to see the logs for the initialisation of the repository / session variables and more in OCI, although I don't know why this didn't come through originally.

In the case of writeback, the templates we had were erroring but we had no sight of the code being executed and so couldn't resolve these without raising an SR. If we could have seen the error raised and the actual code being run then this would have helped identify the cause a lot quicker.

In the case of the variables, it would be good if we could see the code being run for the variables with any dependent variables populated (as per the obis1-diagnostic log files) instead of the RPD code (obis1-query log files). In addition, if there was a way to identify if the initialisation code had errored when it ran , that would also be useful.