Oracle Analytics Cloud and Server

Welcome to the Oracle Analytics Community: Please complete your User Profile and upload your Profile Picture

Dashboard Graphs issue in some browsers

Received Response
103
Views
20
Comments
2»

Answers

  • Rai Qaiser Hussain
    Rai Qaiser Hussain Rank 5 - Community Champion

    @Charles M

    I have copied instanceconfig.xml file below there is no such entry exists

    <?xml version="1.0" encoding="UTF-8" standalone="no"?>

    <!-- Oracle Business Intelligence Presentation Services Configuration File -->

    <WebConfig xmlns="oracle.bi.presentation.services/config/v1.1">

        <ServerInstance>

            <DSN>AnalyticsWeb</DSN>

            <Logging>

                <Writers>

                    <Writer implementation="FileLogWriter" name="Global File Logger" writerClassId="1" dir="{%ORACLE_BIPS_INSTANCE_LOGDIR%}" filePrefix="sawlog" maxFileSizeKb="10240" filesN="10" fmtName="ODL-Text"/>

                    <Writer implementation="CoutWriter" name="Console Logger" writerClassId="2" maxFileSizeKb="10240"/>

                    <Writer implementation="EventLogWriter" name="System Event Logger" writerClassId="3" maxFileSizeKb="10240"/>

                    <Writer implementation="FileLogWriter" name="Webcat Upgrade Logger" disableCentralControl="true" writerClassId="5" dir="{%ORACLE_BIPS_INSTANCE_LOGDIR%}" filePrefix="webcatupgrade" maxFileSizeKb="2147483647" filesN="1" fmtName="ODL-Text"/>

                </Writers>

                <WriterClassGroups>

                    <WriterClassGroup name="All">1,2,3,5,6</WriterClassGroup>

                    <WriterClassGroup name="File">1</WriterClassGroup>

                    <WriterClassGroup name="Console">2</WriterClassGroup>

                    <WriterClassGroup name="EventLog">3</WriterClassGroup>

                    <WriterClassGroup name="UpgradeLogFile">5</WriterClassGroup>

                </WriterClassGroups>

                <Filters>

                    <FilterRecord writerClassGroup="File" path="saw" information="1" warning="31" error="31" trace="0" incident_error="1"/>

                    <FilterRecord writerClassGroup="File" path="saw.mktgsqlsubsystem.joblog" information="1" warning="31" error="31" trace="0" incident_error="1"/>

                    <FilterRecord writerClassGroup="UpgradeLogFile" disableCentralControl="true" path="saw.subsystem.catalog.initialize.upgrade" information="1" warning="32" error="32" trace="1" incident_error="32"/>

                    <FilterRecord writerClassGroup="UpgradeLogFile" disableCentralControl="true" path="saw.subsystem.catalog.upgrade" information="1" warning="32" error="32" trace="1" incident_error="32"/>

                </Filters>

            </Logging>

            <Views>

                <Pivot>

                    <DefaultRowsDisplayedInDelivery>75</DefaultRowsDisplayedInDelivery>

                    <DefaultRowsDisplayedInDownload>2500</DefaultRowsDisplayedInDownload>

                    <DisableAutoPreview>false</DisableAutoPreview>

                </Pivot>

                <Table>

                    <DefaultRowsDisplayedInDelivery>75</DefaultRowsDisplayedInDelivery>

                    <DefaultRowsDisplayedInDownload>2500</DefaultRowsDisplayedInDownload>

                </Table>

            </Views>

            <UI>

    <DefaultSkin>Alta</DefaultSkin>

    <DefaultStyle>Alta</DefaultStyle>

    <SkinMappings>

    <skinMapping>

    <biadfSkinFamily>bi-alta</biadfSkinFamily>

    <biSkin>AltaBitech</biSkin>

    </skinMapping>

    </SkinMappings>

    </UI>

            <Catalog>

                <UpgradeAndExit>false</UpgradeAndExit>

                <EnableMultiTenancy>false</EnableMultiTenancy>

            </Catalog>

            <!-- TODO - many of the following entries need removing once OBIPS uses the Endpoint API -->

            <Listener port="9710" ssl="false"/>

            <Alerts>

                <ScheduleServer ssl="false">localhost:9705</ScheduleServer>

                <OfflinePresentationServicesURL>http://10.232.18.95:9704/analytics/saw.dll</OfflinePresentationServicesURL>

            </Alerts>

            <ActionFramework>

                <WorkflowServer>http://10.232.18.95:9704</WorkflowServer>

                <WorkflowService>ANALYTICS</WorkflowService>

                <WorkflowSystem>obiaftests</WorkflowSystem>

            </ActionFramework>

            <Security>

                <ClientSessionExpireMinutes>210</ClientSessionExpireMinutes>

            </Security>

            <ODBC>

                <ResultRowLimit>65000</ResultRowLimit>

            </ODBC>

            <Dashboard>

                <ShowPageTabsAlways>false</ShowPageTabsAlways>

                <ShowSectionHeadingsDefault>false</ShowSectionHeadingsDefault>

                <CollapsibleSectionsDefault>true</CollapsibleSectionsDefault>

            </Dashboard>

            <BIComposer>

                <Enabled>true</Enabled>

            </BIComposer>

            <DeploymentProfile>

                <DeploymentMode>onsite</DeploymentMode>

            </DeploymentProfile>

            <AsyncLogon>

                <NewLogonWaitSeconds>30</NewLogonWaitSeconds>

                <NewSyncLogonWaitSeconds>900</NewSyncLogonWaitSeconds>

            </AsyncLogon>

            <Marketing>

                <ContentServer>

                    <URL>http://localhost:8765</URL>

                </ContentServer>

            </Marketing>

            <Authentication>

                <EnabledSchemas>UidPwd,Impersonate,UidPwd-soap,Impersonate-soap</EnabledSchemas>

            </Authentication>

        </ServerInstance>

    </WebConfig>

  • Charles M
    Charles M Rank 6 - Analytics Lead

    Thanks Rai. At this time, I am not sure what is causing this issue. If I come across anything, I will reply back.

    Regards,

    Charles

  • Charles M
    Charles M Rank 6 - Analytics Lead

    Hi Rai,

    If you wanted to try something, and have a development instance that you could access, you could make some changes to that instanceconfig file to see if it makes a difference. I am not recommending that you do this. Simply offering a possibility. It is up to you and your client to determine if it is appropriate. I haven't tested this, nor has it been recommended/tested by Oracle. And, I'm making some assumptions based on information I've seen ...

    All that said, you could do the following, after taking a backup of the instanceconfig file:

    1) Add the following to the 'Views' section

    <Charts>
    <DefaultWebImageType>flash</DefaultWebImageType>
    </Charts>

    2) Try changing those "skin" values to all 'Alta'

    e.g.

    <biadfSkinFamily>bi-alta</biadfSkinFamily> --> change to Alta

    <biSkin>AltaBitech</biSkin> --> change to Alta

    You can try these one-at-a-time, or both together. Just backup the file each/every time. If anything adverse happens, revert back to the original file.

    FYI - After any changes to that file, you'll need to bounce the presentation server/services.

    Regards,

    Charles

  • Rai Qaiser Hussain
    Rai Qaiser Hussain Rank 5 - Community Champion

    thanks

  • Chris Arnold
    Chris Arnold Rank 5 - Community Champion

    We ran into this issue in 12c.

    We went into the dashboard properties and changed the Style to be 'SkyrosCloud' and that fixed the issue. Now the users are able to see the graphs using IE.

    Give this a try and see if it helps.

  • Rai Qaiser Hussain
    Rai Qaiser Hussain Rank 5 - Community Champion

    We are  using OBIEE 12,  Surprisingly, I tried style "FusionFX" and it is working fine from few days but I was not sure either it is a permanent solution or just the solution for this dashboard graph only.

  • [Deleted User]
    [Deleted User] Rank 10 - Analytics Guru
    Rai Qaiser Hussain wrote:We are using OBIEE 12     

    There were 23 "12c" which all behave differently as software versions do. Please do always provide a precise version:

    12.2.1.4.181016

    12.2.1.4                

    12.2.1.3.181016

    12.2.1.3.180717

    12.2.1.3.180116

    12.2.1.3                 

    12.2.1.2.180717

    12.2.1.2.180116

    12.2.1.2.171017

    12.2.1.2.170718

    12.2.1.2.170418

    12.2.1.2                 

    12.2.1.1.171017

    12.2.1.1.170718

    12.2.1.1.170418

    12.2.1.1.161018

    12.2.1.1

    12.2.1.0.170418

    12.2.1.0.161018

    12.2.1.0.160719

    12.2.1.0.160419

    12.2.1.0.160119

    12.2.1.0

  • Rai Qaiser Hussain
    Rai Qaiser Hussain Rank 5 - Community Champion

    We are using OBIEE 12.2.1.3.0 version.

  • [Deleted User]
    [Deleted User] Rank 10 - Analytics Guru

    I probably have posted this about 10 time sin the last 12 weeks, but let me be clear once more - and I will probably add this to every reply now.

    1.) 12.2.1.3.0 is an unpatched "dot zero" release and as such not recommendable as soon as the first bundle patch has been released. After three bundle patches over a timeframe of 16 months no one should be using the basic dot zero release anymore.

    2.) 12.2.1.3 is about to reach the end of its supported lifecycle in terms of error correction - which stops April 2019:

    https://support.oracle.com/epmos/faces/DocContentDisplay?id=1664916.1

    This error correction support document should be known and understood by anyone working with the product.

    3.) The required and recommended bundle patches for all OBI version are noted in this document:

    https://support.oracle.com/epmos/faces/DocContentDisplay?id=2070465.1

    Likewise, this document should be known and understood by anyone working with the product.

  • Rai Qaiser Hussain
    Rai Qaiser Hussain Rank 5 - Community Champion

    thanks for the detailed information