3 General Issues and Workarounds

This chapter describes general issues and workarounds for Oracle RTD. It contains the following topics:

3.1 Certification Information

For the latest certification information, which supersedes that in the Oracle RTD documentation, see "Oracle Fusion Middleware Supported System Configurations" for Release 3.2, at:

http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html

3.2 Installation Issues

This section provides release notes on installing Oracle RTD. It contains the following topics:

3.2.1 Client Examples Available Only in Windows Installation .Zip Files, Not .CPIO

Client example files are not available in the .cpio installation files. They may be retrieved from the Windows installation .zip files.

3.3 General Issues

This section contains the following topics:

3.3.1 Ensuring Unique Batch Names Across a Cluster

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.

3.3.2 Transient Likelihood Problems

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.

3.3.3 Issue Opening .csv Files in Excel

Oracle RTD Platform .csv files use tabs as delimiter instead of comma. Some versions of MS Excel do not recognize the delimiter. To work around this, rename the file as a .txt file and open it again in MS Excel, using the import wizard to specify tab as the delimiter.Also check the formatting of columns with dates and percentages to make sure they are displayed properly.

3.3.4 Do Not Customize Study Names

When deploying an inline service, do not customize the study name. In particular, two inline services should not share the same study.

3.3.5 Use Development Deployment State Only

Deployment states will be deprecated in a future release. Avoid using any deployment state other than Development.