|Oracle® Fusion Middleware Release Notes
11g Release 1 (11.1.1) for Microsoft Windows x64
Part Number E14774-06
This chapter describes issues associated with Oracle Business Activity Monitoring (Oracle BAM). It includes the following topics:
This section describes general issue and workarounds. It includes the following topics:
Microsoft Windows Intel x86-32:
Microsoft Windows XP Professional, Service Pack 2 or higher
Microsoft Windows Vista
Microsoft Internet Explorer 6.0, Service Pack 1 or higher
Microsoft Internet Explorer 7.0
1 CPU at 1.2 GHz or faster minimum (a faster processor may be necessary to view complex dashboards)
512 MB RAM minimum
5 MB of free disk space
Oracle BAM Active Studio requires 1024 x 768 minimum resolution
Oracle BAM Active Viewer requires 800 x 600 or higher resolution
Additional Requirements for Optional Excel View in Oracle BAM Active Viewer or Oracle BAM Active Studio:
The Oracle BAM Excel view type requires that Microsoft Excel version XP, 2003, or 2007 is installed on the client computer.
If you are using the Microsoft Windows pop-up blocker, or any other tool that blocks pop-up browser windows, you must configure it to allow pop-up windows while using the Oracle BAM Web applications. Turn off pop-up blockers in Microsoft Internet Explorer for the URL on which the Oracle BAM Web applications are hosted.
The Microsoft Internet Explorer installation on client systems must be a standard version, and it must not include customizations such as add-in tool bars or hot bars for other Web sites.
Preview features are for evaluation only.
ICommand Web Service is a preview feature.
Saving reports in MHT format is a preview feature. Save Offline, e-mailing rendered reports, and e-mailing a report in Alerts save the report in the MHT format.
The following report views are preview versions: P-Chart, R-Chart, S-Chart, Columnar, Crosstab, Summary Crosstab, Matrix, Excel, Column Group, and Row Group.
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.
For a complete list of Oracle BAM upgrade issues, see the following:
Section 3.1.1, "Patches Required to Address Specific Upgrade and Compatibility Requirements", which includes information on an Oracle Database patch that is required before you perform an Oracle BAM schema upgrade.
Section 3.1.5, "Oracle BAM Upgrade Issues", which consolidates various known issues and workarounds when upgrading Oracle BAM to 11g.
Section 3.3.1, "Documentation Errata for Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter, and ADF", which includes some documentation additions for upgrading Oracle BAM to 11g.
For single instance database installs, the statement cache size will already be set to 0 (zero) by default. Do not change this to a non-zero value.
For installs against a RAC database, the statement cache size must manually be set to 0 for each RAC data source; otherwise, data corruption may occur and the Oracle BAM Active Data Cache may need to be restored from a backup (or reinitialized if no backups are available).
Oracle BAM applications are not functional if the database on which Oracle BAM depends is started few minutes later than Oracle BAM Server.
If the Oracle BAM Web applications component is started and stopped from Oracle Enterprise Manager Fusion Middleware Control while a report is open either in Active Studio or Active Viewer, the user may find that creating a new report after this restart could cause a Null Pointer Exception such as:
If this happens, the workaround is to restart the managed server in which Oracle BAM is running.
The login prompt will appear when a user session is expired.
If a login prompt appears in the Web browser or a dialog (for example, in one of the panes of Active Studio), and the space is not able to accommodate the prompt in the pop-up, close the window, log out if necessary, and log in again.
Oracle BAM does not format numbers according to locale information set in the Web browser.
Currently Oracle BAM does the following:
Format dates as per browser locale.
Change the language as per browser locale.
Filters on datetime and timestamp data types use the Oracle BAM Server time zone for condition evaluations. Time zone personalization in user preferences has no effect on these evaluations. Also, the filters using the Active Now feature use Oracle BAM Server time zone for Now evaluations.
If the following is set, 11/26/2008T17:30:10.0000000+05:30, for a datetime or timestamp column of a data object, The Oracle BAM Active Data Cache should interpret it to be a value in IST, but the +05:30 offset is ignored and the ADC considers the value to be in the Oracle BAM Server time zone (which is PST). So, no matter what offset is used (+05:30 or any other country's offset), or what time zone notation (such as IST or PST), or GMT notation (11/26/2008T12:00:10Z), Oracle BAM Active Data Cache considers the datetime value string, ignores the time zone offset, and considers the datetime to be in PST. Thus, 11/26/2008T17:30:10.0000000 and 11/26/2008T12:00:10 are both are considered as PST values, where as they are exactly same values--one represented in IST and another one in GMT.
1stage.sh (1stage.bat) file for the Oracle BAM Portfolios demo is meant to clean up the data accumulated in the demo's data objects (such as, after a demo run), and reset it to the data originally contained in those data objects. Currently, running
1stage.sh changes the IDs of the data in the data object, which results in the
Too Many Values error in the KPI views, or one pie becoming too big in the right side pie chart.
Check the Oracle BAM page on Oracle Technology Network for the updated demo files:
An Oracle BAM sensor action cannot be notified of BPEL events, and the messages sent to Oracle BAM from the BPEL server are only stored in memory; therefore, when the BPEL server restarts, all the messages still on the BPEL side are lost.
This behavior is by design, and there is no workaround.
In some cases failover could result in faulty Oracle BAM Web application sessions. For example, you may see Page Not Found errors in any of the Oracle BAM Web application frames or dialogs. If this is encountered, close all Oracle BAM Web application browser sessions, log out of the Oracle BAM start page, and close that browser, too. Restart your sessions.
When an interface involving Oracle BAM IKM and LKM modules is in execution when either the RAC database fails over or the Oracle BAM Server undergoes whole server migration, then, at the instant that the failover starts, the Oracle Data Integrator session reports an exception for that particular step, and the execution for the entire interface is halted.
The user will have to re-execute that interface. If commit size was set to zero (for any of the IKM SQL to Oracle BAM-based interfaces), the entire transaction is rolled back. In those cases where a different commit size was used, the user will have to take adequate steps to avoid data duplication in the target data store upon re-execution.
Oracle BAM presents the following limitations because in this release Oracle BAM Web applications and Oracle BAM Server are only deployed in a single EAR, but are represented in Oracle Enterprise Manager Fusion Middleware Control using two separate targets:
Along with two custom targets, Oracle BAM Server and Oracle BAM Web applications, The Oracle BAM application also appears as a generic J2EE application in the Application Deployments list in Oracle Enterprise Manager Fusion Middleware Control navigation tree, and in the Farm home page. It is recommended that the user only use custom Oracle BAM targets (
OracleBAMWeb), the internal application target (
oracle-bam) should not be used.
Additional information about the generic
oracle-bam J2EE application target: The generic J2EE application target (oracle-bam) despite being an internal application, still appears under parent Application Deployments and not in the sub-folder Internal Applications of Application Deployments. Moving oracle-bam generic J2EE application target to Internal Applications folder has been deferred.
The Stop and Start commands in the Oracle BAM Server and Oracle BAM Web applications menus in Oracle Enterprise Manager Fusion Middleware Control pages does not stop or start the corresponding target only, it stops the entire Oracle BAM application (Oracle BAM Server and Oracle BAM Web applications).
Viewing any J2EE metrics in the context of Oracle BAM Server or Oracle BAM Web applications actually presents the view for entire J2EE application. (From performance page and WebLogic Server page the user gets access to the J2EE application metric).
WebLogic Server (Managed Server) home page shows three deployed applications for each Oracle BAM install (two custom targets and one generic J2EE application target). Corresponding to each target there are few J2EE application metrics shown. Because J2EE metrics correspond to each deployment, the metrics values get repeated for all of the Oracle BAM targets. The workaround is displaying metric values only against one target and the other two showing n/a.
The MBean browser in Oracle Enterprise Manager Fusion Middleware Control does not have any validation in place to check whether the entered value is correct or not.
When you see the
Unable to extend tablespace error message, you can do the following:
Increase the tablespace size.
If you cleared a large amount of data from a data object, and expect the tablespace to have more data, you might still see this error. The table space release is not synchronous, and you must run command
A user assigned to a non-Administrator role may be unable to create or view reports, but has the privileges to do so, and gets the following error:
Exception Message BAM-01257: Insufficient permission to perform the requested action.
This is due to the user not having at least Read permissions on the /System folder in Oracle BAM Architect.
The same user opening a report on two different computers with different language settings causes a language mix in the Oracle BAM user interface.
A single user should not log in simultaneously on different computers with two different language settings.
An external data object can be created on a table that begins with an underscore (_), but an exception occurs when checking the contents of the table in Oracle BAM Architect.
As part of an Oracle BAM alert action, Oracle BAM Event Engine can call external Web services. However, for secure Web services, Oracle BAM Event Engine supports calling only HTTP Basic authentication protected Web services in this release. Configuring an alert action to call WS-Security enabled Web services is not supported.
Using double quotation marks (") around the
file value in ICommand export does not work.
Use single quotation marks (') instead of double quotation marks to specify the
<?xml version="1.0" encoding="utf-8"?><IstanteCommands><export name='/Samples/Film Sales' file='c:\do_with_data.xml' type="dataobject"/></IstanteCommands>
When operation COUNTDISTINCT-based aggregate is chosen in Group filters in data object and report based alerts, the user might see the alert firing multiple times, even if the alert criterion was satisfied only once in the data. This behavior is seen when bulk data object operations are performed. That is, if multiple rows are inserted, deleted, updated, or upserted in the data object at one time.
Grouping by Week in a Crosstab or Chart view could cause group values for Day of Month or Day of Week to be calculated incorrectly for weeks that include the end of one month and the beginning of another.
Include Day of Year in the grouping along with Day of Month or Day of Week.
Loading to an external data object in Oracle BAM using Oracle Data Integrator (using IKM) is supposed to fail and raise error message because this scenario is not supported. However, instead of raising an error, the IKM SQL to Oracle BAM (insert) operation used to load data into an external data object in Oracle BAM reports success and displays the number of rows inserted, when no rows were actually inserted.
When you must pass a date input through an Oracle BAM alert rule invocation to an Oracle Data Integrator scenario, it is recommended that you set up the Oracle Data Integrator scenario to use an
alphanumeric datatype variable instead of
date datatype. Using a
date datatype variable may lead to a parse exception within the Oracle Data Integrator agent which results in a failure to invoke the scenario successfully.
alphanumeric datatype variable is used within the definition of the Oracle Data Integrator interface, use the
TO_DATE function along with the format in which the date is expected. For example, with a project level variable named
alphVariableName, the function usage would be:
Within the Oracle BAM alert rule definition (for the Run an ODI scenario action), pass the date to be input in the same format.
An Oracle BAM external data object can not be created based on an external database table with a multi-byte name.
Drilling down on a time or date dimension in a collapsed list view causes an exception. Use chart views only to drill down on time or date dimensions.
When there is an alert (for example, Alert B) that is created as a dependent on another alert (Alert A), as in migration or upgrade, the alerts must be imported to the target system in order of dependency (Alert B must be imported before Alert A).
This section describes documentation errata. It includes the following topics:
Two items are added to the Oracle BAM-Oracle Data Integrator manual installation instructions:
1) The environment variable
JAVA_HOME must be set to Java version 1.6.x in the environment in which an Oracle Data Integrator application will be invoked. This means that Java version 1.6.x must be installed on the machine. To set the environment variable:
On Microsoft Windows, go to the Control Panel, click on the System icon. In the System Properties, go to the Advanced tab, and then click on the Environment Variables button. In the Environment Variables window, create or modify a variable named
JAVA_HOME for the user (upper box), and set the value to the path for the Java installation (for example:
c:\PROGRA~1\Java\jdk1.6.0_12). Click OK. When you launch Oracle Data Integrator, be sure to do it from a fresh command prompt, to pick up the new environment variable.
2) In the instructions where the user is instructed to modify the
odiparams script the following must also be done:
The note in Oracle Fusion Middleware User's Guide for Oracle Business Activity Monitoring, Table 34-3 Oracle BAM Knowledge Modules, currently states:
During execution, the number of upsert operations are reported in the No. of Updates field, because the Oracle Data Integrator Operator user interface does not have a No. of Upserts field.
The following information is appended to that note:
Further, the count for all of the inserts and updates to the Oracle BAM database are reported in the Updates field, and are not reported separately.
There are several ways to run Oracle Data Integrator scenarios in which Oracle BAM functionality has been embedded. The Oracle BAM documentation provides instructions on how to install Oracle BAM integration components for Oracle Data Integrator. These instructions suffice for running Oracle BAM in Oracle Data Integrator in every circumstance except if running the Oracle Data Integrator agent as a Microsoft Windows Service. In this case, please follow these instructions:
On the Oracle BAM host, go to the
Copy the two files contained in that directory (
readme.txt) to the Microsoft Windows machine on which the Oracle Data Integrator agent will be running as a service, in the
Follow the instructions in the
readme.txt file in that directory to configure the Oracle Data Integrator agent to run with Oracle BAM.
agent.bat file (on Microsoft Windows) will pick up the same environment variables as do the other Oracle Data Integrator applications (such as Designer, Topology, Operator). This means that as long as the Oracle Data Integrator integration installation has been performed on the Oracle Data Integrator directory in which
agent.bat will run, no additional steps are needed to run the Oracle Data Integrator agent as a standalone application on Microsoft Windows (not as a service).
The following statement in Section 34.1 "Introduction to Using the Oracle Data Integrator With Oracle Business Activity Monitoring," has been updated:
Oracle Data Integrator cannot insert data into Oracle BAM read-only fields of type Lookup, Calculated, Auto-incrementing integer, and Timestamp. These fields are automatically populated.
The statement includes the following in addition to the current text:
Although Oracle Data Integrator allows you to select these fields as target fields, running Oracle Data Integrator with these fields populated will throw an exception.
If you have any long running database operations that exceed the defaults, and encounter JDBC timeouts indicated by the exception
ORA-01013 user requested cancel of current operation, you can increase the values in the following configuration properties accordingly:
These properties specify the timeout, in seconds, for JDBC Update and Query commands, respectively.
Both of these properties have default values of sixty seconds to protect the Oracle BAM Active Data Cache from deadlock situations. It is recommended that the properties are increased only as much as necessary to prevent deadlock.
The correct default port numbers are
registerusers utility: 9001
If a non-default port or protocol (like for SSL) is used, then the user must change these settings in the
The Oracle BAM
registerusers utility, used to register users in Oracle BAM, currently has the
-adminpswd parameter in which users can enter a password in clear text.
This parameter is no longer be an option for users.
The documentation in Oracle Fusion Middleware Administrator's Guide for Oracle SOA Suite, Section 22.2.2 "Monitoring the Event Engine Component," information about Active Rules currently states:
Active Rules displays the number of alert rules that are active (not expired or invalid) in Oracle BAM Event Engine. Active Rules displays the total number of alert rules in Oracle BAM Event Engine, which is the sum of alerts created for all of the Oracle BAM users.
The following information is appended to that statement:
Alerts based on reports that have multiple views will result in creation of multiple alert rules, so the number of Active Rules may be different from the overall number of alerts that are active for all users.
A single or double quotation mark in an Oracle BAM object name, such as a data object, report, or enterprise message source name, will cause a runtime error.
Do not include single or double quotation marks in an Oracle BAM object name.
In the section "To configure a drill-across target:" step 8, line 3: "the field value represented in that bar" should be "the group value represented by that bar."
When using Now Mode in prompts and parameters, the user can enter negative values for the Offset to select an interval in past. In filters, the user can select options from now and ago, which also support a negative value for offset.
Columnar reports and views support active data updates only, and only under the following conditions: the updates do not change the grouping of a record, and the report does not span multiple pages or frames.
In Oracle Fusion Middleware User's Guide for Oracle Business Activity Monitoring, Chapter 4, "Creating and Using Views," the following statement is incorrect:
"8. It is not necessary to specify the ID; the system creates it."
The following statement is correct:
"8. Specify the ID; the system requires it."
ADCServerName property is configured in the
BAMICommandConfig.xml file as well as in the
See "Configuring Server Name" in Oracle Fusion Middleware Administrator's Guide for Oracle SOA Suite for information about how to set the property.
The maximum number of rows to fetch from external data sources is controlled by
Import_MaxSize property which is defaulted to -1 (negative one). The property gets a value of 64000 from
Import_MaxSize property is set to -1, so the net default is 64000.
If you need to increase the number of rows to be fetched, you can do so in the
BAMServerConfig.xml file. Increasing this value beyond 64000 can have performance implications, so it should only be increased as much as necessary.
Normally, this increase may not be required. It may be required only in the cases where you must run a report that has an aggregate column on the external data object that has more than 64000 rows (for example, sum, count, average).
The Oracle BAM jsessionid cookie is persisted on disk on the client side. The lifetime of the cookie is one week.
The cookie is maintained on client side and is used for:
1) Authentication mechanism. The first time a user logs in, the browser keeps the login credentials. If another browser window is opened, the user does not have to log in again. As long as the browser window is open it will update the cookie every 10 seconds. When it becomes stale the user is redirected to the login page.
2) Maintaining sticky sessions. When using a pool of Oracle BAM servers, the load balancer uses the cookie to maintain sticky sessions, so that all requests go to the same Oracle BAM Server. This is required because an open report is registered for receiving active data from a particular Oracle BAM Server.
A side effect of the cookie is that it bypasses authentication, which becomes more pronounced with single-sign-on. The cookie is persisted to disk because multiple browser windows may be contained in separate processes.
If there is a security concern, contact Oracle Support Services.
The help topics for Oracle BAM Excel view Macro and Data Transfer properties are not available in the translated versions of Oracle BAM online help.
The English version includes the appropriate topics, and these features are documented in the Oracle Fusion Middleware User's Guide for Oracle Business Activity Monitoring.
Figures 5-10 and 5-11 are reversed in Oracle Fusion Middleware User's Guide for Oracle Business Activity Monitoring.
In Oracle Fusion Middleware User's Guide for Oracle Business Activity Monitoring, Chapter 5 "Manipulating Data in Views," on page 5-3, the following information is added to define time units for filter expressions on datetime fields:
Week is based on a Sunday through Saturday week, Quarter is based on the typical fiscal year January through December with Q1 starting January 1, and year is based on a January through December year.
Field Type Prompts and Parameters
In Oracle Fusion Middleware User's Guide for Oracle Business Activity Monitoring, Chapter 8 "Using Prompts and Parameters," the following information is added for further information about developing parameters using the Field type.
Field is a type that allows you to select data object fields as the values passed to the parameter, rather than values within a field. For example, choosing this type allows the user to change the field by which data is grouped in a chart while viewing a report.
While configuring the input definition for a parameter of type Field, you will choose only fields from the data object, and not values from a field.
The ALL, NULL, or BLANK values are not presented when creating parameters of prompts of type Field.
User can leave value unselected is not presented as an option when using the Field type.
When Field is chosen, and you select a field of type datetime, you are also presented with the option to create a time group. To add a time group, click Add. For more information about time groups see "Configuring Time Groups" in Oracle Fusion Middleware User's Guide for Oracle Business Activity Monitoring Chapter 4 "Creating and Using Views."
Datetime Type Prompts and Parameters
When a parameter type of datetime is chosen you can also configure a time window (that is, you can filter the data by time) within which data is to be displayed by configuring the Now Mode. See "Using Active Now" in Oracle Fusion Middleware User's Guide for Oracle Business Activity Monitoring Chapter 5 "Manipulating Data in Views" for more information.
In Oracle Fusion Middleware Administrator's Guide for Oracle SOA Suite Section 23.3.4 "Understanding Oracle BAM Application Roles," Report Viewer Permissions currently reads:
ActiveViewer: Has full access to Oracle BAM Active Studio application functionality
The corrected text reads:
ActiveViewer: Has full access to Oracle BAM Active Viewer application functionality
The following information is added to Oracle Fusion Middleware User's Guide for Oracle Business Activity Monitoring Chapter 3 "Creating and Managing Reports."
Changing the Data Object
You can edit a report and change the data object you selected for a specific view, or any occurrence of a data object used throughout the entire report. The data object you select must contain at least the same fields as the originally selected data object. The data object you choose might contain additional fields. The data objects that do not apply are disabled.
You can change the dataobject for a specific view by using the View Editor Data Objects tab, or you can replace a data object for entire report by using Global Change Data Object action.
To change all occurrences of a data object in a report:
While the report is open for editing, click Global Change Data Object in the Actions list.
In the Global Change Data Object dialog box, click Browse to select the currently used data object (the data object you want to replace).
Click Browse by the second field to select the replacement data object, and clock OK.
In section 21.8 of the Oracle Fusion Middleware Administrator's Guide for Oracle SOA Suite, the following location is given for the configuration file in which to edit Oracle BAM adapter batching properties:
The Oracle BAM adapter batching properties must be edited in the
BAMCommonConfig.xml file that is a part of
oracle-bam-adapter.rar file, not the configuration file on Oracle BAM Server as indicated in the documentation.
To edit the
Extract it from the Oracle BAM adapter RAR which is located in the
Edit the batching properties.
Repackage and redeploy the Oracle BAM adapter.
In section 21.7.1 "Configuring Oracle BAM Connection Factories," in Oracle Fusion Middleware Administrator's Guide for Oracle SOA Suite, the following note is added:
Note:If you change any property in an existing connection factory for the Oracle BAM adapter, you must restart both Oracle WebLogic Server and Oracle BAM Server for the changes to take effect.
xmlPayload(xsd:any) are replaced with
xmlPayload(xsd:string) for all Oracle BAM Web Services.