Skip Headers
Oracle® Application Server Release Notes
10g Release 3 (10.1.3.1.0) for Microsoft Windows
B31012-02
  Go To Documentation Library
Home		 Go To Table Of Contents
Contents
Previous
Previous 		 Next
Next		  

10 Oracle Business Activity Monitoring

This chapter describes issues associated with Oracle Business Activity Monitoring. It includes the following topics:

10.1 General Issues and Workarounds

This section describes general Oracle Business Activity Monitoring issues and, where applicable, their workarounds. It includes the following topics:

10.1.1 Some Product Features Previews Only

Preview features are for evaluation only.

ICommand Web Service is a preview feature.

Saving reports in MHT format is a preview feature. Save Offline, emailing rendered reports, and emailing a report in Alerts save the report in the MHT format.

The following report views are preview versions: Funnel Chart, P-Chart, R-Chart, S-Chart, Columnar, Crosstab, Summary Crosstab, Matrix, Excel, Column Group, and Row Group.

10.1.2 Some Product Features Not Supported

Active Messenger and Collaboration Server are not supported as of 10g Release 2 (10.1.2), and they will be removed in future releases. Instead, use email accounts for alerting.

The Spreadsheet view is not supported, and it will be removed from future releases.

Enterprise Link VBA is not supported.

Enterprise Link Repositories are only supported on Oracle databases. All other database types for Enterprise Link Repositories are not supported.

Enterprise Link integrates with all enterprise message sources that adhere to the JMS 1.1 specification. Enterprise Link does not support the following enterprise message sources that appear in the Architect user interface: See Beyond JMS Intelligent Queue, Sonic MQ, Tibco Rendezvous, and WebMethods.

10.1.3 DateAdd Function in Filters Can Produce Incorrect Active Data

The DateAdd() function in filters produces incorrect active data with the last day of the month.

10.1.4 Report Cache Service May Not Restart Immediately

After viewing a report and leaving the report open, sometimes the Report Cache service may not restart. Wait 30-60 seconds before restarting the service, or end the ASP.NET process in the Task Manager and then restart.

10.1.5 Logging In Using "Run as" Not Supported

Logging into an Oracle Business Activity Monitoring application using "Run as" with a different user name than the currently logged-on user is not supported.

10.1.6 Install Complete IIS When MS Cluster Service Installed

If MS Cluster service is installed on a system some components of IIS get installed with it, this makes the BAM installer give a false result on IIS prerequisite check, that is it will say PASSED, even though IIS is not fully installed. Before installing Oracle Business Activity Monitoring, make sure to install IIS as detailed in section 2.2.2 "Installing Microsoft Internet Information Services" of the Oracle Business Activity Monitoring Installation Guide.

10.1.7 The Oracle BAM Active Data Cache Service May Fail to Start

You may encounter the following error when starting the Active Data Cache:


The Oracle BAM Active Data Cache service failed to start. Oracle.BAM.ActiveDataCache.Common.Exceptions.CacheException: ADC Data Object could not be loaded ---> System.NullReferenceException: Object reference not set to an instance of an object.

If you have some rows of data in a data object, then attempt to change one of the populated fields to a non-nullable datatype (auto-incrementing or timestamp), it will throw an error saying "table must be empty."At that point, you will not be able to restart the ADC. If you do not restart the ADC everything continues to work without the changes to the data object. If you restart the ADC, it will not work, and there is no way to recover except to re-create the ADC or bring back the BAM schema from a database backup.

10.1.8 Testing a BAM Server Connection in JDeveloper

When creating an Oracle BAM Server connection in JDeveloper, select Use secure HTTP protocol check box only if you want to use secure HTTP (HTTPS) to connect to the Oracle BAM Server running on HTTPS. If this box is selected by mistake when Oracle Business Activity Monitoring is running on HTTP on port 80, Test Connection hangs.

When creating an Oracle BAM Server connection in JDeveloper on Windows XP, a message "Basic realm does not match with 'host.domain.com'" can occur when you use Test Connection. There are domain and Realm options under Basic Authentication under Directory Security tab on IIS. When Oracle Business Activity Monitoring is installed, by default Realm is set to the domain name of the administrator who installed Oracle Business Activity Monitoring. To work around this issue, set Realm to an empty string.

10.1.9 ICommand: Exporting Reports with Background Images

Exporting reports with background images exports the name of the internal images file, and also imports it. If the original report still exists, then both reports are cross-linked to the same image. If the original report is not there, then the image is lost.

10.1.10 ICommand: Special Character in Parameter Value Causes Export Failure

ICommand export fails when exporting a parameterized alert with a special character in the parameter value.

10.1.11 Restricting BAM Web Services to BAM Users

Disable Automatic Addition of Users in order to prevent any authenticated user from invoking BAM web services. See "Disabling the Automatic Addition of Users" in Chapter 3 of the Oracle Business Activity Monitoring Installation Guide for more information.

10.1.12 Web Service Calls May Not Be Logged

Web service log entries are missing from WebApps.txt under certain scenarios. To enable logging do the following steps:

  1. Exit all Oracle BAM browser windows, and stop all of the Oracle BAM services.

  2. Optionally, edit web.config and set log level to debug: <priority value="DEBUG" />

  3. Run iisreset / kill aspnet_wp.exe.

  4. Do not open any Oracle BAM browser windows.

  5. Invoke the Web services code.

  6. Now open the Oracle BAM start page and any other browser windows.

It is very important to do step 5 before step 6, otherwise you will only see the Web applications entries in WebApps.txt, and the Web services entries never appear.

10.1.13 Globalization and Localization Support Limitations

Full globalization support of Oracle Business Activity Monitoring is not available in this release.

  • All servers and clients running Oracle Business Activity Monitoring components should be set to the same locale.

  • The Oracle Business Activity Monitoring applications will obey the globalization culture setting from the web.config file on the server, but not the client browser locale.

  • This version of Oracle Business Activity Monitoring is not fully localized. Only Active Viewer is localized for the following languages: French, German, Italian, Portuguese(Brazil), Spanish, Japanese, Korean, Simplified Chinese, and Traditional Chinese.

  • Render for e-mailing uses the time zone of the Web server. If a report has time zones set to client time zone, when viewing a report from a browser, the browser time zone is sent to the Report Server and used when formatting the datetime fields. There is no equivalent for the Event Engine's render for email, so it defaults to the Web server time zone.

  • The Calculation Legend does not support multibyte characters. This field name is limited to 30 or fewer letters, numbers, and underscores. Spaces are not allowed.

  • Report fields like View Titles may not correctly display Western European multibyte characters.

  • Report names that include Western European multibyte characters may not appear correctly in the Select Report dialog. The Report may still be selected and opened in Active Viewer and Active Studio.

10.1.14 Accessibility Compliance Limitation

This version of Oracle Business Activity Monitoring does not comply with accessibility standards provided in other Oracle products. Future versions plan to comply with these standards.

10.2 General Active Studio Issues and Workarounds

This section describes general Active Studio issues and, where applicable, their workarounds. It includes the following topics:

10.2.1 Save As Dialog Box May Appear Inappropriately

An additional Save as dialog box displays after clicking Cancel on the original Save as dialog box.

10.2.2 Save Prompt Not Displayed When Closing Report After Deleting a View

Users are not prompted to save after deleting a view in a report. Save changes after deleting views.

10.2.3 ADC Exception on Adding Timestamp to a Non-Empty Data Object

Attempting to add a timestamp to a data object after a previous failure throws an Active Data Cache exception.

If you try to add timestamps when the data object is not empty and receive an error, use ICommand to export the data object, delete it, import it back in (as empty), and add the non-nullable column. Only add timestamps as non-nullable columns, and only when the data object is empty.

10.2.4 BLANK Selection Not Supported in Oracle Database

Several places in the user interface, such as the Prompt and Parameters Wizard, allow BLANK as a valid selection. Oracle databases do not support empty strings and users should not enter BLANK.

10.2.5 Drill-through Fields Grayed Out After Editing Drill-through

Drill-through fields appear disabled (grayed out) even though the Enable drill through to detail check box is selected. To remove fields or change the order of the fields, uncheck the Enable drill through to detail check box and then check it again. The fields are accessible again.

10.2.6 Rank Column Not Available in Some Views

For OpenURL, ViewReport, and Insert action types, the Rank column cannot be used in an action or be formatted as links.

10.2.7 Use Global Change Data Object to Fix Reports Using Deleted Data Objects

Reports based on a data object that has been completely deleted can no longer be used or edited. You can use the Global Change Data Object action in the View Editor to assign a new data object to the views in the report.

10.2.8 Pause/Resume Active Data Does Not Work After Viewset Expires

When viewing multiple reports, pause/resume active data after the viewset expires does not work.

10.2.9 Changing Data Types in Data Object Can Break Reports

Reports can become unusable if you change the data type of columns used by the reports.

10.2.10 Using Default Report Name Can Generate an Error

Sometimes when saving a report as the default name, a message displays that incorrectly indicates that the report already exists. Specify a different name and save the report.

10.2.11 Active Data May Fail On Simultaneous Report Loading

If two Reports are opened on the same host and they both load at the same time, Active Data may fail to work. Note that it does not matter how the two separate Reports are hosted. It can be with any combination of Active Viewer, Active Studio, or portals and custom pages that host Reports.

10.2.12 Use Field IDs Instead of Field Names in Shortcut Report URL

Copy Shortcut requires a Field ID instead of a Field Name when using Field Parameters in a Report URL. You can look up the Field ID for any field in a data object in the Layout page for data objects in Architect.

10.2.13 Active Lookups Do Not Work With Deletes

If you create a report on a data object with a lookup and clear the source data object, no active data will appear. The lookup values will not change to NULL.

10.2.14 Multi-level Calculations in Combination with Other Data Manipulation

Aggregate values used at the detail level, also known as multi-level calculations, in lists and columnar reports cannot be combined with sorting, filters, groups, or Top N. This combination can display an error or prevent active data from displaying.

10.2.15 Errors When Fields Hidden or Revealed After View Design

Issues can occur when using a view, such as a Crosstab, Range Gauge, or Updating Ordered List, that contains fields that are hidden or unhidden after the design of the view. If the user wants to hide information in the view, first remove the field from the list of fields being shown in the view and then use Architect and make the field private.

10.2.16 Error When Group-by Data Crosses Year Boundary

Error while creating a report with group by data fields and group on Week-Month and Week-Quarter and data crosses the year boundary.

10.2.17 String Parameters Not Supported in Calculator

String fields are supported in the Calculator, but string parameters are not supported in the Calculator.

10.2.18 Show Details Does Not Work with Time Groups

When using Time Groups, Show Details is not working. No data is displayed. However, Show Details does work when using Time Series.

10.2.19 Error When Changing View Type

When changing the view type of an existing view, errors can occur.

10.2.20 Save Offline Limitations

  • Users who only have Active Studio and report creation permissions assigned can also save reports offline. Only e-mailing rendered reports is managed as a separate permission.

  • Saving a report offline closes the Active Studio in some cases. This is affected by a known issue using Internet Explorer on Microsoft XP Service Pack 2. For more information, see http://support.microsoft.com/?kbid=896017.

  • When viewing saved offline reports, the report loading icon may sometimes not disappear; this can be ignored.

  • Save Offline does not work if the report name has a semicolon.

  • After you click Save Offline, a dialog box appears asking whether you want to Open, Save, or Cancel. Choose Save. When you return to the view, it appears empty. If you want to see data in the view again, close the report and reopen it.

  • When saved offline, the Range Gauge can appear small in MHT format because it has a legend, and it is rendering into a fixed area.

  • External Content views cannot always display images when saved offline or sent by email in MHT format.

  • When Oracle Business Activity Monitoring is installed on the D: drive, an error can occur when attempting to open a report in MHT format sent in an Alert email. The error does not occur if the report is sent from Active Studio using Email Report page.

10.3 List View Issues and Workarounds

This section describes List view issues and, where applicable, their workarounds. It includes the following topics:

10.3.1 Streaming List Range Buttons May Not Appear at Times

Due to an Internet Explorer issue, sometimes the range buttons in a Streaming List do not display and an error can occur. A fix for Internet Explorer is available from Microsoft by referencing the article "Internet Explorer May Appear to Stop Responding When Requesting Many Objects" at the following URL:

http://support.microsoft.com/?id=818506

10.3.2 Updating Ordered List: Cancel Button Not Functional with Top N

Updating Ordered List views require a sort if Top N is applied. If you create an Updating Ordered List and apply Top N without sorting, and then click Cancel, an error displays when you save and view the report.

10.3.3 Heading Text Cannot Be Removed

In List views, you cannot remove heading text once it was specified. You can enter new text to replace the existing text.

10.3.4 Special Characters Affect Sort Order in Updating Ordered Lists

Updating Ordered Lists are not sorted correctly when the data contains specials characters.

10.4 Chart View Issues and Workarounds

This section describes Chart view issues and, where applicable, their workarounds. Funnel Chart and SPC Chart views are previews and should only be used for evaluation. It includes the following topics:

10.4.1 Timestamp on Axis Label Causes ADC Error

An error occurs in the Active Data Cache internal data access system when timestamp is selected in the axis label.

10.4.2 Data Labels Cut Off with Active Data

In charts with all three data label types displayed, the data labels can appear cut off when viewing the report with live data.

10.4.3 Null Values Incorrect When Grouping in Charts

When grouping in Charts, null values are not represented correctly.

10.4.4 Labels May Overlap in Charts

Under certain conditions, labels can overlap in charts.

10.4.5 Charts Using Top N May Fail with Active Data

Charts using Top N may fail with an error when using Active Data.

10.4.6 Grouping Can Cause Error

When working with Charts, the message, "If you group by field, you can only choose one summary function for one chart value" can display. Remove the group manually and click Apply to continue working.

10.4.7 Time Groups in Charts Must Use Default Date Format

When using Time Groups in Charts, overriding the default formatting for the date field does not work.

10.4.8 X-Axis May Not Clear Appropriately in Continuous Time Series

When you view a continuous time series chart and clear the underlying data, there are times when the x axis should clear and times when it should not. If the left edge and right edge of the x axis values are well-defined (using filters on both edges, or Active Now, or Time Groups), the data always clears correctly. If the left and right edge of the x axis are not well-defined (no filters, left filter only, or right filter only), it may result in just the labels being removed.

10.4.9 Stacked Bar Chart Legend May Be Obscured by Negative Values

Negative values can overlap in the legend in Stacked Bar Charts.

10.4.10 Target Lines Work Only in Bar Chart

Target lines are broken with Active Data for charts other than the Bar Chart.

10.4.11 Funnel Chart Limitations

  • The Funnel Chart view is a preview feature in this release. Preview features are for evaluation only.

  • Timestamp or datetime as a group field in Funnel Charts is displayed incorrectly.

  • Funnel charts do not scale down to small screens well.

  • Funnel charts do not support adding and removing groups or clearing the data while being viewed. You can close and reopen the report after any of these data conditions.

10.4.12 SPC Chart Limitations

  • The SPC Chart views (S-Chart, R-Chart, and P-Chart) are preview features in this release. Preview features are for evaluation only.

  • A field name including spaces in a Pass Filter will not pass. For SPC Charts, you must enclose a field name that contains spaces in quotes.

  • The X-bar value for the S-Chart is calculated incorrectly.

  • In an R-Chart combined with surface prompts, Active Data may reset the value displayed in the surface prompt to its default value, even though the last value submitted through the surface prompt is still in effect.

10.5 Miscellaneous View Issues and Workarounds

This section describes miscellaneous view issues and their workarounds. It includes the following topics:

10.5.1 Active Now May Show Wrong Results with KPI View in Report

When a report with a KPI view using an Active Now filter is opened in two Active Viewer browser windows, older data is not removed from the report, and reprompting and restarting the report does not correct the view. Close both Active Viewer browser windows and start only one Active Viewer to display the correct report results.

10.5.2 Faulty View Report Hyperlink in Action Form View

The View Report hyperlink in Action Forms returns an empty report if passing a parameter value with special characters. As a workaround, use Action Buttons instead of Action Links.

10.5.3 Surface Prompts View Does Not Render for Email

For Surface Prompts, the view does not render for email.

10.5.4 Resizing Column Group Moves Entire Group View

Using the view handle to resize a Column Group view causes the view to move around in the report. In order to properly resize a column group you need to select a view that is inside the Column Group view and then attempt to resize it.

10.5.5 Crosstab, Summary Crosstab, and Matrix View Limitations

The Crosstab, Summary Crosstab, and Matrix views are preview features in this release. Preview features are for evaluation only.

  • Working with a continuous series when a category has a value of zero includes issues, such as an error if the user selects a time unit quantity other than 1, issues with the Crosstab view, and with filters. For Crosstabs, issues include continuous series handling where active data inserts, group ordering, and formatting might work incorrectly.

  • For Crosstabs, when working in the View Editor to select columns and rows, the Script error "tdAddRemoveButtons.parentElement" displays if the data object has more than one datetime field. You can ignore the error and continue working in the View Editor.

  • The Crosstab view type does not support e-mailing the report page.

  • When a Matrix conditional formatting condition is set to Is not equal to, the color display is incorrectly applied.

10.5.6 Excel View Limitations

The Excel view is a preview feature in this release. Preview features are for evaluation only.

  • Excel views do not support E-mailing and Save Offline.

  • Double-clicking an XLS file in Windows Explorer while an Excel View is open in Active Studio causes Excel to hang. Excel will start working if you close the report in Active Studio. Excel does not hang if you open Excel, then select File > Open to open the XLS file.

  • After data is in an Excel view, users can apply sorting using the Excel sorting functions. Excel does not resort data on each update. Because of this, sorted data compared between OWC Spreadsheet and Excel views will not match when data is first displayed.

  • If you want to use Save As for an Excel view in Active Studio, view the report and then select File > Save As. Using Save As while the report is being edited can cause an error to display.

10.5.7 Columnar Report and View Limitations

The Columnar report and view are preview features in this release. Preview features are for evaluation only.

10.6 Filter Issues and Workarounds

This section describes data filter issues and, where applicable, their workarounds. It includes the following topics:

10.6.1 BLANK Value in Prompt Causes Error

Creating a filter with a boolean data type and a prompt value displays an error if BLANK is allowed in the prompt and selected by the prompt user. In a filter with a datetime prompt that allows a BLANK value, clicking OK with no value displays an error. BLANK values should be disabled for all types besides strings.

10.6.2 "Is Like" Filter on Datetime Fields Does Not Work

In filters on datetime field types, you are unable to type a value for "is like" filters. You can create filters by selecting a specific date from the calendar, but you cannot type values or indicate wildcard characters.

10.6.3 Incorrect Daylight Savings Time May Be Displayed

If you are viewing filters using datetime fields, you may see discrepancies in the time selected during daylight savings changes. This can happen only if you are viewing a report when daylight savings change happens. The workaround is to reopen the report.

10.6.4 Cannot Create Filter When Field Changed to Lookup Field in Data Object

If you update a data object (change a normal field to a lookup field) which has a report based on it, you cannot create a filter that report.

10.7 Calculated Field Issues and Workarounds

This section describes calculated field issues and, where applicable, their workarounds. It includes the following topics:

10.7.1 In Some Cases Calculated Field Cannot Be Deleted

In some cases when the user has saved and edited the view, a calculated field cannot be deleted even if it is not used in the view.

10.7.2 Prompts and Parameters Wizard Does Not Include Calculated Fields

Calculated fields are not listed in the From list step in the Prompts and Parameters Wizard. However, the parameter and type in the prompt works fine with a calculated field.

10.7.3 Multi-level Calculation with Max or Min and Boolean Do Not Work

Multi-level calculated fields with Max() or Min() and Boolean do not work.

10.7.4 ADC Error on Division with Two Calculated Fields

Creating a calculated field to perform a division operation on two calculated fields, both of which use CountDistinct, can cause an Active Data Cache error.

The workaround is to create a calculated field such as:


CountDistinct({Recent Account Touch SID})/CountDistinct({Account SID})

The problem only exists when a calculated field does operations on other aggregate calculated fields.

10.8 Alert Issues and Workarounds

This section describes Alert issues and, where applicable, their workarounds. It includes the following topics:

10.8.1 Special Characters Can Cause Error When Editing Alerts

An error displays when editing an alert when a parameter value to pass to a plan has a special character.

10.8.2 Changing Event Type in Parameterized Alert Causes Exception in Event Engine

Changing to another event type does not remove the field parameters from a parameterized plan. You must manually remove the parameter if you change the event type.

10.8.3 Calculated Fields Do Not Appear in Alert Filters

You cannot create a row or group filter alert on a calculated field.

10.8.4 Filter Items May Appear Misaligned

Alignment issues occur for the Row and Group Filter tab in Alerts.

10.8.5 Alerts Not Deleted with Parent Reports

Alerts are not deleted when they are based on a report that has been deleted.

10.8.6 Cancel Does Not Work on Clear Alert History

If you click the Clear alert history link and then click Cancel, when you click the Activate checkbox for an alert, the alert history is cleared. Write alert history to the Event log to avoid mistakenly clearing it.

10.8.7 Invalid Windows File Name Characters in Report Name

Alerts do not launch if you select a report name that contains any of the invalid Windows file name characters such as \ / : * ? " < > |.

10.8.8 Alerts Still Launch After Report Is Deleted

Launched alerts that reference deleted reports behave inconsistently. Make sure the reports used by alerts still exist.

10.8.9 Orphaned Alert Not Marked

An alert is not marked as orphaned if a prompts or parameters is later created in a view other than the first view in a multi-view report.

10.8.10 Unique Naming Not Enforced on Alert Parameters

The Alert Parameter dialog incorrectly allows you to create two parameters with the same name.

10.8.11 Row-level Security Not Supported for Alerts on Data Change

Row level security is not respected for alerts on data changing in a data object. Also, the row level security of the alert owner is applied and not the message recipient.

10.8.12 Non-applicable Aggregates Included in Select Data Field Dialog

The Select Data Field dialog in Alert Rule Editor incorrectly allows users to select non-applicable aggregates. Select valid functions for data fields.

10.8.13 Duplicate Fields May Appear in Field Lists

When creating and editing alerts with groups and filters, duplicate fields may appear in the lists of fields.

10.8.14 Alerts on Aggregates May Misfire

Alerts on aggregates sometimes fire when they should not. For example, alert me when SUM(Sales) changes may fire when SUM(Sales) has not changed.

10.8.15 Calling .NET Web Service Directly Using External Action

When defining an External Action for Alerts in Architect, you can call a .NET web service if all of the following conditions are true:

  • The namespace is the same as the one used in the proxy in Event Engine code: http://mahamoti-djinn/ActionService

  • The method name is the same as execute

  • The argument to the method execute is ActionData

A BPEL service does not have tight binding with namespaces and therefore can be called with just the method name, for example, execute or initiate. As long as the signature is the same (variable name can be different), XML data will go into the BPEL process.

10.8.16 Alert Actions Ignored if Previous Action Fails

If an Alert is configured with multiple actions, and one action fails, no other actions will be executed.

10.9 Administrator and Architect Issues and Workarounds

This section describes Administrator and Architect issues and, where applicable, their workarounds. It includes the following topics:

10.9.1 Plan Setting Check May Take a Long Time

When requesting a Plan settings check in Administrator, it may take a long time to determine if the monitoring settings for Plans have been changed.

10.9.2 Plan Does Not Restart When Plan Monitor Service Loses ADC Connection

When the Plan Monitor Service loses connectivity to the Active Data Cache, a Plan does not restart. Restart the Plan Monitor Service.

10.9.3 Cannot Edit Data Objects with Some Alerts

If a data object has an alert using When this data field has a condition of x, a message displays that the data object is in use if you try to edit the data object. To edit a data object that has alerts based on it, you must stop the Oracle BAM Event Service, make the edits, and restart it.

10.9.4 Permission Changes May Not Propagate to Lookup Objects

When you change permissions on a data object that has lookups written against it, you may also need to change permissions on the other data objects that are looking up against this data object. If a user builds a lookup field against a data object where they do not have read access, data will still be returned.

10.9.5 Invalid Lookups Prevent Deletes From Being Sent to the View

The Active Data Cache only supports lookups as inner joins that only match one value. No matches are invalid, and two or more matches are invalid. Ensure that a lookup matches one and only one row in the foreign table. If this is not true, then lookups on active data can include values that should be deleted.

10.9.6 Non-administrators Cannot Clear Data Objects with Joins

Logging on as a non-administrator user and trying to clear a data object containing joins results in an error. The Administrator must log on and clear the data object.

10.9.7 Lookups That Return Multiple Rows Not Supported

Active Data Cache lookups do not support returning multiple rows. However, it is not prevented, and when it does happen, the behavior is undefined.

10.9.8 Decimal with Scale 10 Allows Seven Digits Left of Decimal Point

The default scale setting for decimals is 10 which allows seven digits to the left of the decimal point and ten to the right for a precision total of 17. To increase the number of digits allowed to the left of the decimal point, decrease the scale value. For example, if scale is 3, you will have 14 digits left of the decimal.

10.9.9 Error May Occur When Deleting Row from Lookup Table

An error can occur when deleting a row from a lookup data object (that is not an external data object) when a report using a lookup field from the lookup data object is open. Close the error and refresh the contents. The row is deleted.

10.10 Enterprise Link Issues and Workarounds

This section describes Enterprise Link issues and, where applicable, their workarounds. It includes the following topics:

10.10.1 Nonexistent Alert Does Not Cause Plan to Fail

A Plan does not fail if the Alert Transform is set to an alert that does not exist.

10.10.2 GET Method Not Working in Enterprise Link Web Service

Enterprise Link Web Service is not working with the GET method of sending data to the Enterprise Link Web service. HTTP Post and HTTP Get are disabled by default. For more information, see:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;819267

10.10.3 .NET Framework 2.0 Causes Error When Running Enterprise Link Plans

Various errors including "Unhandled Exception: System.ArgumentOutOfRangeException: Ticks must be between DateTime.MinValue.Ticks and DateTime.MaxValue.Ticks. Parameter name: ticks" can occur when .NET 2.0 is installed on an Oracle Business Activity Monitoring host. This is a known Microsoft issue and requires a Microsoft hotfix. Documentation on this issue is available at the following URL: http://support.microsoft.com/?kbid=907262

10.11 BPEL-BAM Integration Issues and Workarounds

This section describes BPEL-BAM integration issues and, where applicable, their workarounds. It includes the following topics:

10.11.1 10.1.3.1.0 BPEL and JDeveloper BPEL Plugin Must be Used

Oracle Business Activity Monitoring 10.1.3.1.0 needs to run with Oracle BPEL 10.1.3.1.0 and vice versa. Oracle JDeveloper must have the 10.1.3.1.0 BPEL plugin.

10.11.2 Unable to Flush BAM Batch

Run Orderbooking sample and create 30,000 instances. The following errors appear in BPEL opmn or domain logs:


Maximum request length exceeded

Unable to flush BAM batch

To workaround this issue, modify the IIS configuration on Oracle Business Activity Monitoring host:

C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\CONFIG\machine.config

Set maxRequestLength to 40MB from 4096(KB): maxRequestLength="40960"

10.11.3 Changing BAM Server From BPEL Console Takes No Effect at Runtime

Changing the Oracle BAM server details under the descriptor tab for deployed process through BPEL Console does not take effect at runtime, even after restarting the BPEL Server, and it continues to refer to the old Oracle BAM server at runtime. If you must modify the oracle BAM server details, you must do it at design time by loading the data object from the BAM sensor action pane, or change it manually in the bpel.xml file and deploy the process.

10.11.4 Batched Messages Lost On Restart

If you restart Oracle BPEL Server, any messages currently being batched are lost. Ensure that all messages have successfully published to Oracle Business Activity Monitoring Active Data Cache before restarting Oracle BPEL Server.

10.11.5 Data Object Read Permission Required for Updates/Upserts or Deletes

Read permission should be given with Update or Delete permissions on a data object for a given user, otherwise errors occur when attempting to update/upsert/delete into Oracle Business Activity Monitoring Active Data Cache data object using BPEL-BAM integration, and operation fails.

10.11.6 Duplicate Messages on IIS Restart

If Microsoft IIS restarts on the BAM server while messages are being published from BPEL, duplicate messages can show up in BAM. To avoid this issue, use non-batch mode for BAM sensor actions, and using Oracle BAM Architect, create an index on the BPEL InstanceID column in the database table to where messages are being written.

10.11.7 Sensor Actions Order is Not Guaranteed When Using Batch Mode

If you enabled batching on a BAM sensor action on the Create Sensor Action window, when a single BPEL process has a BAM Sensor Action with an Insert operation, followed by another BAM Sensor Action with an Update operation, Oracle Business Activity Monitoring may change the order in which these operations are executed. This can cause the updates to be lost. To work around, select only one type of sensor operation per BPEL process, such as Upsert. Also, using Oracle BAM Architect, make sure that the target data object InstanceID column is of type Integer, and create an index on the InstanceID column.

10.11.8 Western European Number Format Issue in Transforms

In many Western European locales such as German or French, the default decimal point is a comma (,) instead of the dot (.). In that case the mathematical function in a transform activity, such as ADD and SUBTRACT, will give an output using the comma as decimal point, although the input numbers of the function are using dot.

To work around this issue, add a decimal-format function to overwrite the default format. The following is an example for ADDITION.


<xsl:decimal-format name="usa" decimal-separator="."/> 

<xsl:template match="/"> 

  <tns:Root-Element> 

    <tns:Price> 

      <tns:price1> 

        <xsl:value-of select="/tns:Root-Element/tns:Price/tns:price1"/> 

      </tns:price1> 

      <tns:price2> 

        <xsl:value-of select="/tns:Root-Element/tns:Price/tns:price2"/> 

      </tns:price2> 

      <tns:price3> 

        <xsl:value-of select="format-number((/tns:Root-Element/tns:Price/tns:price1 - /tns:Root-Element/tns:Price/tns:price2), '#.00', 'usa')"/> 

      </tns:price3> 

    </tns:Price> 

  </tns:Root-Element> 

</xsl:template>
  Previous
Previous 		 Next
Next
  Go To Documentation Library
Home		 Go To Table Of Contents
Contents