| Oracle® Real-Time Decisions Release Notes Versions 3.0 and 3.0.0.1 Part Number E13857-09 |
|
|
View PDF |
| Oracle® Real-Time Decisions Release Notes Versions 3.0 and 3.0.0.1 Part Number E13857-09 |
|
|
View PDF |
This chapter describes general issues and workarounds for Oracle RTD. It contains the following topics:
For the latest certification information, which supersedes that in the Oracle RTD documentation, refer to System Requirements and Supported Platforms for Oracle Real-Time Decisions for Versions 3.0 and 3.0.0.1, available from the Oracle RTD Documentation Web site at:
http://www.oracle.com/technetwork/middleware/real-time-decisions/documentation/index.html
This section provides release notes on installing Oracle RTD. It contains the following topics:
When you follow the instructions as described in Section 3.2.3, "Creating a JDBC Provider for the Oracle RTD Database in Oracle" in Oracle Real-Time Decisions Installation and Administration Guide, you will get some errors indicating that SDDS is missing. You can safely ignore these errors, and proceed with the instructions as described in the rest of that section.
This issue applies to Version 3.0 and Version 3.0.0.1.
Client example files are not available in the .cpio installation files. They may be retrieved from the Windows installation .zip files.
This section contains the following topics:
Section 3.3.1, "Decisions May Not Contain Expected Performance Goals References"
Section 3.3.3, "Save Choice IDs in Inline Services Rather Than Choices"
Section 3.3.4, "Ensuring Unique Batch Names Across a Cluster"
Section 3.3.7, "Negative Choice and Choice Group Scores Cause Runtime Errors"
Section 3.3.8, "Model APIs Not Working Correctly With Only One Positive Event"
Section 3.3.9, "Model Quality APIs Do Not Support Partitions"
This issue applies to Version 3.0 only. It is fixed in Version 3.0.0.1.
Inline Service decisions may be ignoring performance goals and returning unexpected results. This is caused by an issue in the metadata generation within Oracle RTD Studio.
The use case is as follows:
An Inline Service is first created with choices, integration points, a decision D1, data sources, and so on, but with no performance goals initially. At this point, decision D1 does not utilize a performance goal to render results.
The user now creates one or more performance goals using the Performance Goals editor.
The decision D1, when it is re-opened in Decision Studio, will appear to now include the performance goals (and equal value weights for each goal) as part of the decision.
Although visually the goals appear to be referenced, the underlying metadata file (*.sda) does not actually contain the goals information. If no further modifications are made to decision D1 and the Inline Service is now redeployed and run, the response from the decision will be incorrect.
The workaround for the issue is to make a modification to decision D1, for example, to edit the Decision's description field, or to adjust the goal weights slightly. Saving the modified decision will then regenerate the decision's metadata with the correct goals/weights references.
This issue applies to Version 3.0 and Version 3.0.0.1.
Oracle recommends that, after installing Oracle RTD, you add extra protection to the installed files by setting up operating system specific file permissions.
Operating systems vary in how file permissions can be set up. The following recommendations use the principles and terms underlying file permissions in Unix-like systems. Administrators of other system types should use the equivalent options and facilities that are available in their systems.
This section assumes three broad user categories:
User/Owner
Group
Others
The file permissions specified in this section are:
R - Read
W - Write
X - Execute
None
The sections that follow list the recommended file permissions for each user category and specific Oracle RTD files and directories.
Note that the following directories are in the Windows RTD_HOME only:
RTD_HOME\apps\
RTD_HOME\client\
RTD_HOME\deploy\
RTD_HOME\docs\
RTD_HOME\eclipse\
RTD_HOME\examples\
RTD_HOME\help\
RTD_HOME\jdk\
RTD_HOME\log\
RTD_HOME\schemas\
RTD_HOME\scripts\
The User/Owner is responsible for installation and for patch accounts during patching. At the operating system level, this user has the equivalent of IT administrator/installer rights.
Table 3-1 shows the recommended file permissions for this user category.
The Group users are the (non-patching) administrators. These users should have the standard Oracle RTD role RTDAdminUser.
Table 3-2 shows the recommended file permissions for this user category.
Table 3-2 Group File Permissions
| File Type | Permission |
|---|---|
|
Administrative tools |
|
|
Administrative configuration files |
RW |
|
Documentation and sample files Read-only zip files |
R |
|
Editable admin tools |
RWX |
|
Other files |
None |
Footnote 1 Some operating systems require R and X to be both set for executables, in which case substitute RX for X for Administrative tools.
The specific Oracle RTD files for each general file type category in Table 3-2 are as follows:
Administrative tools
An Oracle RTD Windows client application for initializing or upgrading the Oracle RTD Database: SDDBTOOL (RTD_HOME\scripts\SDDBTool.cmd)
Command line scripts for initializing or upgrading the Oracle RTD Database (RTD_HOME\scripts\sql and its subdirectories and files)
RTD_HOME\jdk and its subdirectories and files
RTD_HOME\lib and its subdirectories and file
Administrative configuration files
Command line scripts for initializing or upgrading the Oracle RTD Database (RTD_HOME\scripts\sql)
RTD_HOME\client\*.properties
Documentation and sample files
RTD_HOME\help and its subdirectories and files
RTD_HOME\docs and its subdirectories and files
RTD_HOME\examples and its subdirectories and files
RTD_HOME\client\Client Examples and its subdirectories and files
Read-only zip files
Command Line Deployer (RTD_HOME\OracleBI\RTD\client\CommandLineDeploy and its file rtd-deploytool-3.0.0.1.xxx.zip)
Editable admin tools
RTD_HOME\scripts\SetSDParams.cmd
RTD_HOME\scripts\sdexec.cmd
The Other users are the end users. These users should have the standard Oracle RTD role RTDEndUser and, as required, other standard Oracle RTD roles that enable them to perform Inline Service development.
Table 3-3 shows the recommended file permissions for this user category.
Table 3-3 Other File Permissions
| File Type | Permission |
|---|---|
|
End user tools |
|
|
Documentation and sample files |
R |
|
Client log files |
RW |
|
Client configuration files Client owned example files |
RW |
|
Other files |
None |
Footnote 1 Some operating systems require R and X to be both set for executables, in which case substitute RX for X for End user tools.
The specific Oracle RTD files for the general file type categories in Table 3-3 are as follows:
End user tools
On Windows only, RTD Load Generator (RTD_HOME\scripts\loadgen.cmd)
Batch (RTD_HOME\client\Batch and its subdirectories and files)
DecisionService (RTD_HOME\client\DecisionService and its subdirectories and files)
On Windows only, Decision Studio (RTD_HOME\eclipse and its subdirectories and files)
Documentation and sample files
RTD_HOME\help and its subdirectories and files
RTD_HOME\docs and its subdirectories and files
RTD_HOME\examples and its subdirectories and files
RTD_HOME\client\Client Examples and its subdirectories and files
Client log files
Client log (RTD_HOME\log\client.log)
RTD_HOME\etc\ds_perf.xls
RTD_HOME\etc\lg_perf.xls
Client configuration files
RTD_HOME\eclipse\plugins\com.sigmadynamics.studio_3.0.0\etc\eclipse-log.properties
RTD_HOME\etc\log4j.xml
Client owned example files
RTD_HOME\examples and its subdirectories and files
RTD_HOME\client\Client Examples and its subdirectories and files
This issue applies to Version 3.0 and Version 3.0.0.1.
The Getting Started tutorial chapters within Oracle Real-Time Decisions Platform Developer's Guide and the sample Inline Services CrossSell and DC_Demo store choices in session-tied entities. It is recommended that configurations only save IDs of choices instead of the full choice objects.
It is a standard requirement for Inline Service names and batch names to be unique within a cluster.
After an Inline Service is copied within a cluster, batch names registered in the Inline Service can be changed manually to achieve uniqueness. This manual step is not required if the batch registration code in the Inline Service automatically generates the batch name from the new Inline Service name, as in the following generic examples:
batchAgent.registerBatch(
batchAgent.getInlineService().getName() + ".FeedBackBatchJob",
"com.<mycompany>.rtd.batch.FeedBackBatchJob",
FeedBackBatchJob.description,
FeedBackBatchJob.paramDescriptions,
FeedBackBatchJob.paramDefaults);
or
batchAgent.registerBatch(
Application.getApp().getName() + ".FeedBackBatchJob",
"com.<mycompany>.rtd.batch.FeedBackBatchJob",
FeedBackBatchJob.description,
FeedBackBatchJob.paramDescriptions,
FeedBackBatchJob.paramDefaults);
Note that all programs that may call the batch need to be made aware of the new batch name.
This issue applies to Version 3.0 and Version 3.0.0.1.
There are cases where non-mature predictive models will return an actual likelihood rather than NaN during the early life of a model. There are also some cases where mature predictive models will return NaN as opposed to actual likelihoods when the Randomize Likelihood option is enabled for a model. These situations are transient in nature and, in the latter case, do not outweigh the benefits of the Randomize Likelihood feature.
This issue applies to Version 3.0 and Version 3.0.0.1.
Delayed learning, as specified by selecting options in the Temporary Data Storage tab for a model, is the process whereby a model learns on the session attributes values of the base event when a positive event occurs in a later session; the original session in which the base event occurred has already closed. Delayed learning does not function as described in Oracle Real-Time Decisions Platform Developer's Guide.
This issue applies to Version 3.0 and Version 3.0.0.1.
If choice or choice group scores are negative, Oracle RTD generates the following runtime exception message:
Caused by: java.lang.RuntimeException: Goal Weight can not be negative
This runtime exception will prevent completion of the decision process. Add a constant value to score calculations to prevent negative scores.
This issue applies to Version 3.0 and Version 3.0.0.1.
If there is only one positive event in a choice event model, certain model APIs do not return correct results. These model APIs include getChoiceEventModelCount(), getChoiceEventLikelihood(), getChoiceEventModelQuality(), and getChoiceEventModelError().The workaround is to add a positive event , which can have any name, in the model and the corresponding choice group, and to redeploy the Inline Service in which this is defined.
This issue applies to Version 3.0 and Version 3.0.0.1.
If a choice model has partitions, do not call these methods: getChoiceModelQuality, getChoiceModelCount, getChoiceModelLift, getChoiceModelError.
If a choice event model has partitions, do not call these methods: getChoiceEventModelQuality, getChoiceEventModelCount.
This issue applies to Version 3.0 and Version 3.0.0.1.
Model snapshot values for correlation (table RTDCorrelation) and predictiveness (table RTDPredictiveness) are incorrect for completed time windows for model instances marked with state = c.
|
 Copyright © 2009, 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|