Oracle WebCenter Analytics 10.3.0.1 - released November 2009

Oracle WebCenter Analytics 10.3.0 - released November 2008

These release notes cover all releases of WebCenter Analytics 10.3, including hotfixes and maintenance packs. For more information on a particular release, go to the appropriate section of these release notes.

Release notes are occasionally updated after the release date. For the most up-to-date release notes, go to http://download.oracle.com/docs/cd/E13158_01/alui/analytics/docs103/index.html.

For the latest information on supported operating systems, application servers, databases, and browsers, see the Oracle WebCenter Analytics spreadsheet under System Requirements and Supported Platforms for Oracle WebCenter Interaction & Ensemble 10gR3 on the Oracle Fusion Middleware Certification page at http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html.

Important:

• If you are running Oracle WebLogic Portal 10.3, you must install the Oracle WebLogic Portal patch. You can find the patch download tool in <install_dir>/utils/bsu. Instructions for the utility can be found here: http://download.oracle.com/docs/cd/E14759_01/doc.32/e14143/toc.htm. Follow the instructions for downloading Private Patches.
• Oracle WebCenter Analytics leverages Hibernate 3.0.5 for persistence. You must install Hibernate 3.0.5 before you install Oracle WebCenter Analytics. Hibernate 3.0.5 can be downloaded from http://sourceforge.net/project/showfiles.php?group_id=40712&package_id=127784.
• Oracle WebCenter Analytics leverages Cewolf 0.10.3 for its charting engine. You must install Cewolf 0.10.3 before you install Oracle WebCenter Analytics. Cewolf can be downloaded from https://olex.openlogic.com/package_versions/download/5428?package_version_id=218&path=openlogic%2Fcewolf%2F0.10.3%2Fcewolf-0.10.3-all-bin.zip.

At the time of release, Oracle WebCenter Analytics 10.3.x supports the following:

• Windows
  • Operating Systems:
    • Windows Server 2003 SP2 (x86)
  • Databases:
    • Microsoft SQL Server 2005 or 2005 SP2 with SQL Server 2000 Compatibility Level (32- and 64-bit in default or failover cluster configuration)
    • Oracle 10g (10.1.0.5 and above) or Oracle 10gR2 (10.2.0.2 and above) including RAC
    • Oracle 11g (11.1.0.6 and above)* including RAC
• RedHat Linux
  • Operating Systems:
    • RedHat Enterprise Linux ES 4.0 update 3 on all processors except Itanium
    • RedHat Enterprise Linux ES 5.x on all processors except Itanium
  • Databases:
    • Oracle 10g (10.1.0.5 and above) or Oracle 10gR2 (10.2.0.2 and above) including RAC
    • Oracle 11g (11.1.0.6 and above)* including RAC
• Oracle Enterprise Linux
  • Operating Systems:
    • Oracle Enterprise Linux 4.x on all processors except Itanium
    • Oracle Enterprise Linux 5.x on all processors except Itanium
  • Databases:
    • Oracle 10g (10.1.0.5 and above) or Oracle 10gR2 (10.2.0.2 and above) including RAC
    • Oracle 11g (11.1.0.6 and above)* including RAC
• Novell SuSE Linux
  • Operating Systems:
    • SuSE Enterprise Linux SLES 9 on all processors except Itanium
    • SuSE Enterprise Linux SLES 10 on all processors except Itanium
  • Databases:
    • Oracle 10g (10.1.0.5 and above) or Oracle 10gR2 (10.2.0.2 and above) including RAC
    • Oracle 11g (11.1.0.6 and above)* including RAC
• Sun Solaris
  • Operating Systems:
    • Solaris 8 on 64-bit SPARC
    • Solaris 9 on 64-bit SPARC, requires the following patch: 111711-15 (32-bit Shared library patch for C++ ) or 111712-15 (64-bit Shared library patch for C++)
    • Solaris 10 on 64-bit SPARC
  • Databases:
    • Oracle 10g (10.1.0.5 and above) or Oracle 10gR2 (10.2.0.2 and above) including RAC
    • Oracle 11g (11.1.0.6 and above)* including RAC
• IBM AIX
  • Operating Systems:
    • IBM AIX 5.3 on 64-bit POWER, requires the following patches: AIX 5.3 Service pack 5300-05–06 and July 2007 IBM C++ Runtime Environment Component for AIX
  • Databases:
    • Oracle 10g (10.1.0.5 and above) or Oracle 10gR2 (10.2.0.2 and above) including RAC
    • Oracle 11g (11.1.0.6 and above)* including RAC
• Web Browsers:
  • Microsoft Internet Explorer 6.0, 6.0 SP1, 6.0 SP2 (on XP), 7.0 (on Vista), or 7.0 SP2 (on XP SP2)
  • Safari 3.0 (Windows)
  • Firefox 2.0 or 3.0
• WebCenter Products:
  • WebCenter Interaction 10.3
  • WebCenter Collaboration 10.3
  • WebLogic Portal 10.3.2

* Note: When running Oracle 11g versions prior to 11.1.0.7.0 the Oracle system parameter _optimizer_group_by_placement must be set to false. This can either be set in the init.ora file of the respective database instance(s) or by by issuing an ALTER SYSTEM command as follows:

SQLPLUS /nolog
CONNECT / AS SYSDBA
ALTER SYSTEM SET "_optimizer_group_by_placement"=false

Note: No matter the platform, this version of Analytics is installed using the Embedded Application Server v4.0

The following product documentation is available on http://download.oracle.com/docs/cd/E13158_01/alui/analytics/docs103/index.html.

The following documentation is provided with the product distribution.

• Oracle WebCenter Analytics running on Tomcat SHOULD NOT share security database with Oracle WebCenter Ensemble 11g (running on Oracle WebLogic Server). Oracle WebCenter Analytics running on Tomcat SHOULD share security database with other BEA/BID applications running on Tomcat/EAS. That means, security database should be shared among Pathways 1.*, Pages 1.0, Oracle WebCenter Interaction 10.3, Ensemble 2.x/10g and Analytics 10g. (Issue #8673122)
• Queries that use virtual columns and cost-based query transformation might cause unexpected errors. (Issue #7336120)
  
  Workaround: Disable cost_based query transformations.
• Date/Time type user property filter does not work for some strings. (Issue #8567428)
  
  Workaround: Specify date and time using the calendar widget.

• Asian characters exported to a tsv file display as garbled question mark (?). (Issue# 7822093)

• Query API for Custom Reporting
• Support for Hot Failover and Load Balancing of the Collector
• Improved filtering with Global Filters
• Usability Improvements and Bug Fixes

• When including the My Page option in the Page Views report, some international characters may not display correctly. (Issue# 7812280)
• The exception: 'java.lang.Exception: Can't determine os. osName=AIX' may be displayed in the analyticsui.log when displaying PIE Report. This may occur on Linux as well. (Issue# 7816296)
• Choose Resources does not have JS validation when not selecting any resource within the editor. (Issue# 7816954)
• Drilling down a LINE/BAR/PIE Resource report does not retain the resource selected in the Choose Resource editor. (Issue# 7814078)
• The ALI portal diagnostic tool may fail with XPException: Fatal error loading lib file analyticstag: Unable to locate Tag Library meta data. This is a non-fatal error that can be ignored. (Issue# 7816882)
• When re-loading the Specify Desktop(s) pop-up page, the specified desktop value does not display as having been already selected. (Issue# 7817675)
• Specify date range allows dates that occur in the future. (Issue# 7818880)
• Dates specified in the Specific Date Range fields are all shortened to two digits and presumed to be in this century. (Issue# 7820826)
• When re-loading the Specify Portlet(s) page, the check box corresponding to the portlet that is being displayed in the report is not checked. (Issue# 7820827)
• The Summary Duration report will ignore filters on user properties. (Issue# 7820829)
• When using the "Specify Portlets..." feature within Portlet Metrics, it is not possible to analyze portlets that reside within a community. (Issue# 7811634)

• The Phone Home feature in the Configuration Manager is not supported for use by customers unless directed to do so by customer support. (Issue #7825327)
• Broken images get counted as portlet use events. (Issue #7797761)
• If a portlet has a gatewayed link to a CSS or JS file, that link is counted as a portlet use. (Issue #7804817)
• The uninstaller does not uninstall the Analytics Jobs component files. (Issue #7809866)
• On the Search report for a 6.0 portal, the document view details always return all document views for that search regardless of your filter criteria. (Issue #7812745)
• When exporting user details in the Content Items report, the report is blank when the top level of "Count by Subfolder" is queried. A workaround is to select a subset of the subfolders that fall under the top-level folder. (Issue #7812643)
• Document and Content Item Views reports return zero results on Oracle when there are more than 1000 subfolders selected. A workaround is to break up the report into smaller sections selecting less than 1000 subfolders. (Issue #7808189)
• When re-editing the Community Traffic Response Time Portlet Template Preferences from This Community to Top Communities or Bottom Communities or vice versa in one session, the dialog will be unresponsive. A workaround is to close the dialog and re-edit the preferences. (Issue #7808189)
• In a stand-alone portlet for the Page Views report, there is no error handling when grouping by time and user property. (Issue #7811043)
• When selecting Count by Subfolder and specifying a folder in the Other Metrics – Content Items report, the Line report shows the message "No data to display". A workaround is to use another display type: Tabular, Pie or Bar. (Issue #7808449)
• When using an Oracle database with case sensitivity turned on, search phrases may show up in the search report as case sensitive. (Issue# 7813298)
• In Content Items report with tabular view, when both views and users are queried under COUNT BY SUBFOLDER, no data is displayed in the report. (Issue# 7815517)
• With WebLogic Portal: filtering/grouping by user property is not available in the duration report. (Issue# 7812953)
• The Chinese Traditional string localizations will be displayed when using the Taiwan locale. (Issue# 7815165)
• Top/Bottom 5/10/15/20 Page Views generate 6/11/16/21 reports when Include My Pages is selected when both Hits and Users are selected. (Issue# 7815336)
• When using the Analytics Console from the WebLogic Administration Console, if the current user's session times out due to a long period of inactivity, the user may receive an error message that there is no data to display or receive a blank screen. The solution is to log off and log onto the WebLogic Administration Console. (Issue# 7818081)
• With WebLogic Portal: The Summary Traffic report Group By selections are enabled when the pie/bar report is selected. (Issue# 7816332)
• With WebLogic Portal: On the Duration tab of the Summary Metrics report, selecting any property from Group By will refresh to the Day property. (Issue# 7816356)
• Manually modifying the Start/End date will cause the date editor to refresh to its previous date or the current date. (Issue# 7817673)
• With WebLogic Portal: on the Desktop Metrics report with the Line report type, the legend at the bottom of the report may not correspond to the correct lines. (Issue# 7819624)
• When using the Portal Traffic Summary report with the Line display, the Grouping option will not behave as expected. The workaround is to use the Tabular display. (Issue# 7819276)
• In Pie/Bar display, when selecting multiple entities, the Group By options will be disabled after clicking on View Data. (Issue# 7821673)
• With WebLogic Portal: Scroll bar is not available in Show Community Pages link in Desktop metrics. (Issue# 7818734 )
• The Analytics portlets may not function properly when the 3rd party extension "Firebug" is enabled in FireFox. (Issue# 7822301)
• If you uninstall Analytics 2.5, you may need to remove these settings from the configuration file: [...]. (Issue# 7823677)
• When creating new events, a user can specify properties that violate database naming conventions (e.g. by using reserved words as property names). The resulting event won't work. Do not use property names that violate database naming conventions. (Issues #7812203, #7823085)
• For MS-SQL, install_analytics_data.sql script does not set IDENTITY_INSERT for ASDIM_GROUPS.GROUPID which causes the Groups Sync job to fail. The workaround is to set IDENTITY_INSERT on, run the Group Sync job and then set IDENTITY_INSERT off. (Issue# 7823696)
• Customers with more than approximately 25,000 logins per hour at peak load may experience high disk write utilization on the Analytics database. Isolating the disk that the Analytics database is stored on can mitigate the issue. (Issue# 7823612)
• If a document is deleted and then re-added to the directory, it will appear twice, and each view of the document will increment all instances of the document in the report. (Issue# 7824183)
• Newly-created events do not get saved for the first time. As a workaround, cancel the event registration process to exit the Event Registration page, then resubmit the events. (Issue# 7822851 )
• When a document has been copied into multiple folders in the Knowledge Directory and a report is run using more than one of those folders, the total view count will be incorrect. (Issue# 7826571 )
• The PARTITION_XACT_SIZE parameter is not included in the install_analytics_data.sql and upgrade_2.0_to_2.1.sql scripts for MS SQL Server; they are included for Oracle databases. The solution is to enable simple recovery model on the Analytics database and include the following in the MS SQL Server scripts:
  INSERT INTO ASSYS_CONFIG (CREATED, LASTMODIFIED, NAME, CONFIGTYPEID, INTVAL) VALUES (getdate(), getdate(), 'PARTITION_XACT_SIZE', '2', 1000); (Issue# 7822756)
• In Analytics Administration -> Security Settings -> Global Filters, HOST attributes are not working with respect to PortletViews and PubItemViews. (Issue# 7826380)
• In Analytics Administration -> Security Settings -> Global Filters, LINKSOURCE attributes are not working with respect to PorletViews and PubItemViews. (Issue# 7825610)
• HOSTID is not configured properly for ASFACT_PORTLETUSES and ASFACT_SEARCHES. This gives an incorrect result when global filtering is applied to the PortletUses Event. This is related to Issue# 7826380. (Issue# 7826047 )
• The Host Resolution Sync Job job locks the ASDMIN_HOSTS table, thereby preventing the Collector from persisting most events while the job is running. The workaround is to disable or appropriately schedule the Host Resolution Sync Job. (Issue# 7825855)
• The asmanagerui.log does not work. The workaround is to add log4j.jar to the WEB-INF/lib folder in the asmanager.war and make sure the log4j.properties file in WEB-INF/classes is properly configured. (Issue# 7825304)
• The RUN_AUTH_SOURCE_SYNC for AnalyticsRunJobs.bat fails if an auth source was created with an ID that is different from AUTHSOURCEID in ASDIM_AUTHSOURCES is modified after being synched to Analytics. The workaround to bring in the new auth sources is to update the lastmodified column in PTAUTHSOURCES for auth sources that have been already synched to a date and time prior to the last job run of RUN_AUTH_SOURCE_SYNC as recorded in ASSYS_JOBLOGS. (Issue #7824944 )

• The Configurator does not start automatically after running the Analytics silent installer. (Issue #7808733)
• The uninstaller does not uninstall the Analytics Jobs component files. (Issue # 7809866)
• When upgrading Analytics, the Analytics services are not shut down. The user has to manually shut down the services before the upgrade. (Issue #7809615)
• In the Configurator for the Portal Settings, the checkbox for the Portal version only indicates 5.0.4J but should also be checked if using Portal version 5.0.5J. (Issue #7810301)
• When configuring the Security Directory section under Analytics Console in the Configuration Manager: If you switch the provider to AD or LDAP, then proceed to customize all of the settings, and then switch back to ALI as the provider, the ALI provider will not work properly as the additional LDAP settings were not set back to the defaults from what the user configured when using AD LDAP as the provider. To work around, set the values back to their defaults before switching provider types. (Issue # 7826563)
• The deployment guide says to not load balance Analytics even though the Analytics 10.0.3 collector supports clustering and load balancing. In fact, this is only true for the Analytics ui and management applications. The collector in Analytics 2.5 has clustering and load balancing built into it. (Issue # 7822723)

• When loading the portal initially and browsing to the Analytics Console, an error is thrown and the Analytics_log.<date>.txt file (where <date> is the date when the file was written) shows the exception '2005-10-13 11:19:03 ApplicationDispatcher[/analytics] Servlet.service() for servlet jsp threw exception java.lang.NoClassDefFoundError: '. These errors can be ignored. (Issue #7805100 )
• You may see the following message in analyticsui.log: WARN HtmlGridRendererBase - PanelGrid reportForm307:tabularData:_id39 has not enough children. Child count should be a multiple of the columns attribute. This message is not fatal and can be ignored. (Issue #7806237)
• The events list on the Event Registration page will display identical names since the spacing is not taken into consideration. For example, if 'Test 1' is created as one event and 'Test 1' is created as another event, both events will display as 'Test 1' in the events list. However, the database will correctly show the spaces in the display name. (Issue #7812656)
• If a partitioned table currently in the view is removed, an administrator must go into Analytics Administration and click Finish in order to see data in the report (this will update the view). (Issue #7811063)
• Event Registration cannot be completed if a newly-created dimension is removed from the event parameter which uses it. (Issue #7808058)
• The following error may appear in the analyticsui.log: ERROR TabularMultipleSearchDataProvider - Exception occurred while trying to determine drillDownRow. This error is not fatal and can be ignored. (Issue #7811083)
• If the "View Portal Document Related Data" option is disabled for a role within the Security Settings, the user will still be able to see the Document report options in the Analytics Console until they log off and their session is cleared. (Issue #7808210)
• During initial creation of an Event, removing Parameters from the Event will throw a 500 error if the Event was not saved first. A workaround is to first save the Event before adding Parameters. (Issue #7809634)
• Can't register new event with property called "date" when using an Oracle database. A workaround is not to use Oracle reserved words. (Issue #7812203 )
• Can’t edit a string value for custom events when editing an existing event. The following error message appears: "An error occurred while saving event registration. Check that all required fields have valid values and dimension mappings are correct." This error does not occur when creating new custom event types.
• Changing the partition settings in the Administration UI can take a long time when you have a large number of event types and a large amount of collected ata. The WebCenter Interaction UI might display an error message if the operation takes longer than the current portlet timeout setting. However, despite the error message, the Analytics views will eventually get updated. (Issue #7826684)

• Time periods yielding no data are not displayed in any of the Analytics reports except for Summary Metrics - Users. For example, on the Community Traffic report, if the user filters by "last week", but there are only community traffic hits for Tuesday and Friday, the report will only display data for Tuesday and Friday for the selected community. (Issue #7794955 )
• In the Analytics Console Community, sometimes the console refreshes and resets to the default report settings, which clears the current report in view. (Issue #7800191 )
• In bar reports that have long names in the legend, the leftmost name gets truncated. (Issue #7795958)
• Very long object names (such as community, portlet, auth source, etc) may push the report off the screen while displaying the entire object name. (Issue #7797107)
• When viewing line reports grouped by week on systems with Monday as the first day of the week, the data points on the line chart are not aligned with the dates on the X-axis. Workaround: View the data in bar, tabular or pie form or export the data. (Issue #7797130)
• An underscore (_) cannot be entered in the filter by User Property entry box. (Issue #7797336)
• In the Portal Users report, the inactive/active users appear as inactive/active for the entire day, regardless of change of status within the day. This can be seen when the report is grouped by hour. (Issue #7797893 )
• For Line view, when Filter by This Week and Group by Week there is no text on the time axis describing the week for a single data point. (Issue #7797874)
• For portlet templates, it is possible to configure a portlet without any view options (i.e. views, users). (Issue #7803607)
• In Portlet Templates, the value set for top number of items to show may not be used if the user is also using the filter by user property feature. This results in Analytics displaying the top 5 items instead of the number set in the template. (Issue #7806415)
• In the choose project popup window of the Projects report, the personal project is displayed with its project ID and not the personal project's name. (Issue #7805726)
• In the Content Items stand-alone portlet, no radio button is selected by default when "select folder" is chosen. A folder option must be selected in order to use the "select folder" option. (Issue #7805742)
• On the Portlet Usage/View/Response Time reports, when the "select portlets" option is used, the Portlet Selection window does not display portlets that exist within Community Folders. (Issue #7809716)
• On the Search report for a 6.0 portal, the document view details always return all document views for that search regardless of your filter criteria. (Issue #7812745)
• On the exported Portal Visit Duration report, the column header becomes "Not Available" when a bar or line report is selected. (Issue #7811159)
• On the line view of the Portal Users report, although the user property dropdown is disabled, if there's a value showing from the previous report, the report displays an error "Grouping by User Property is not permitted in this line report." A workaround is to unselect the user property by using tabular view then proceed to line view. (Issue #7807684)
• In the Portal Traffic report, the grouping dropdowns are enabled upon loading the report options. Grouping will be ignored if selected for pie report. Any change to the display or time settings will correctly disable the grouping dropdown for pie. (Issue #7807685)
• In the Portal Users report line view, the grouping by error message incorrectly says user must group by time OR user property. Grouping by User Property is not allowed for the line view. (Issue #7807688)
• In the Choose Project popup window of the Projects report, an HTTP Status 500 error may be displayed after clicking OK due to a timing issue. This only occurs when using IE. (Issue #7807800)
• In the Choose Project popup window of the Projects report, any previous projects will no longer appear selected in the dialog; however, those selections still exist. (Issue #7808074)
• The Search report after upgrade shows all previous search metrics as 0% abandoned. (Issue #7810292)
• In the Search report, when the returned results are in multiples of 20, clicking last page button (>|) on the table control results in a page having a blank view. This could also show up in the Document Views report. (Issue #7807834)
• The title is missing from the exported version of the Page Views report. (Issue #7811569)
• When exporting user details in the Content Items report, the report is blank when the top level of "Count by Subfolder" is queried. A workaround is to select a subset of the subfolders that fall under the top-level folder. (Issue #7812643 )
• Document and Content Item Views reports return zero results on ORACLE when there are more than 1000 subfolders selected. A workaround is to break up the report into smaller sections selecting less than 1000 subfolders. (Issue #7808189)
• When re-editing the Community Traffic Response Time Portlet Template Preferences from "THIS COMMNUNITY" to "TOP COMMUNITIES" or "BOTTOM COMMUNITIES" or vice versa in one session, the dialog will be unresponsive. A workaround is to close the dialog and re-edit the preferences (Issue #7807698) In a stand-alone portlet for Page View, there is no error handling when grouping by time and user property. (Issue #7811043)
• Editing a role name within the Analytics Administrator - Security Settings throws a 500 error if using UNIX or Linux with Oracle. A workaround is to create a new role with the desired name and delete the existing role. (Issue # 7811460)
• When selecting Count by Subfolder and specifying a folder in the Other Metrics – Content Items report, the Line report shows the message "No data to display". A workaround is to use another display type: Tabular, Pie or Bar. (Issue #7808449)
• Line reports for Projects, Community and Portlet reports do not display the correct data; the graphs are correct but the legend and names don't match the data. A workaround is to view the data with another display type: Tabular, Pie or Bar. (Issue #7807843)
• Group by User and Filter by User properties are working only for the Administrator user. Although data for all users grouped by title should be shown, only Administrator user information is displayed. However, if you choose to view the data report with the Group By option not selected, the export user details contain all user data. (Issue #7826858, #7823416)
• The report view is not getting refreshed when selecting an empty folder from the drop down list box on the Document tab. (Issue #7825357 )
• Selecting the Analytics Console -> Summary Metrics -> Users ->Inactive/Active user option results in displaying incorrect data. Newly added-users are not being displayed under the active column in the tabular data. (Issue # 7827085 )
• Group By Week in Line reports do not display the week for which data in the report is displayed. (Issue #7824960 )

• In some cases, portlet usage counts are correct when filtered or grouped by user property, although the aggregate count is correct. The portal keeps the gatewayed URL cached and registers the user ID as the last cached user. Once it is rendered, it picks up the new user ID. To track exact portlet metrics, a workaround is to set the portlet's web service cache to zero. (Issue #7798788)
• A login event is tracked with each browser window opened in Firefox and Netscape when auto-login is enabled. (Issue #7800512)
• Portlet Usage events for gatewayed portlets are not recording cached portlet uses on the browser. To track those particular portlets, set the http headers to return "no-cache". Please visit this URL for the http header specification protocol: http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html (Issue #7799290)
• Searches within Collaboration projects or Publisher Explorer are not collected. (Issue #7796672)
• Clicking on a Collaboration project pop-up window will generate a portlet usage event under the portlet which opened the project. (Issue #7795466)
• Document View events for copies of Knowledge Directory documents are tracked under the original document. This is evident when using the "include subfolders" feature to generate the Document View report. (Issue #7799665)
• Broken images still get counted as portlet use events. (Issue #7797761)
• Document view events from within Collaboration projects are not getting captured when viewed through the WebEdit utility. (Issue #7800101)
• Not all Collaboration document view events are captured when clicked upon through search results. (Issue # 7800143)
• If you do a search on a Studio record lookup portlet the use does not get counted in portlet metrics. In order for a portlet use to get registered, you must actually click on one of the search results in the pop-up results window or refresh it. (Issue #7803353)
• If a portlet has a gatewayed link to a CSS or JS file, that link is counted as a portlet use. (Issue #7804817)
• When uploading a Web Document (such as HTML) with the images, and then generating a Collaboration Document View report, Analytics may have multiple CDV events in the Console. (Issue #7806343)
• Autorefresh page views are included in the counts, but should be ignored. (Issue #7806198)
• The document view count is incremented when a Collaboration document is published to the Knowledge irectory. (Issue #7826133)

• The number format in reports does not follow the user locale settings. (Issue #7797004)
• If the strings extracted from the portal database during the sync job contain Asian characters, and the user's locale is non-Asian, the Asian characters are not correctly displayed in the report. (Issue #7797804)
• Some European locales display the wrong date format of mm/dd/yyyy instead of dd/mm/yyyy on the report UI. (Issue #7799452)
• With the Community Traffic report's line and bar formats, the title is cut off in the Y axis on the French UI. (Issue #7803454)
• In an exported Excel file, the time format follows the remote server's system locale instead of the client's locale. (Issue #7805839)
• The font is not set to display Japanese characters in the y axis of the analytics reports.
  
  Workaround:
    1. Unpack the analytics.war file.
    2. Open the AnalyticsUIParams.properties file for editing. You can find this file in the analyticsui.jar file.
    3. Add these locale entries:
         <LocaleCode>_font_<OSName>=<LocalFont>
         <LocaleCode>_fontSize=14
         <LocaleCode>_fontSmallSize=10
    4. Save and repackage .war file.
  
  The locale entries should include these values:
    • The appropriate two letter language code
    • Your operating system: Windows, Solaris, or Linux
    • The name of the font that is appropriate to your locale and platform
  
  Windows example:
     ja_font_Windows=MS PGothic
     ja_fontSize=14
     ja_fontSmallSize=10
  (Issue #7806874)
• Export User Details - US English date format is incorrect when using non-English server (Issue #7810759)
• When creating a role in Security Settings, localized group names are displayed, but English names are displayed after it is saved. (Issue #7810988)
• The portal side Configurator changes the UI language depending on the OS language, but the remote side Configurator always shows English (EN) UI. (Issue #7810511)
• Non mm/dd/yy date formats such as dd/mm/yy and yy/mm/dd cannot be recognized by date range in the Analytics Console (Issue #7825919 )

• Reports with very large amounts of data may time out. Changing the gateway timeout in the report Web service to a higher value may solve this. (Issue #7797395)
• Reports with very large amounts of data. Querying lots of data may impact your database server and, therefore, your portal if you are sharing a database instance. In general, users need to be aware that Analytics does not save reports, and generates them on an "on-demand basis" Oracle is in the process of developing features to address this, but in the meantime, please be aware that running reports can have an impact on overall system performance if the deployment shares database resources. (Issue #7827267)
• Multi-valued user property values are not synched correctly in the ASDIM_USERPROPERTYVALUES table. Only the most recent value is synched and is overwritten when additional values are added. (Issue #7803806)