Contents

Title and Copyright Information

Preface

• Audience
• Documentation Accessibility
• Related Documents
• Conventions

What's New in the Oracle Application Server Release Notes?

• Chapter 3, "General Management and Security Issues"
• Chapter 8, "Oracle BPEL Process Manager"
• Chapter 12, "Oracle HTTP Server"
• Chapter 13, "Oracle Containers for J2EE"

1 Introduction

• 1.1 Latest Release Information
• 1.2 Purpose of this Document
• 1.3 Operating System Requirements
• 1.4 Certification Information
• 1.5 Licensing Information

2 Installation Issues

• 2.1 Installation Issues
  • 2.1.1 Using the Unified Oracle SOA Suite Installer for the mySOACompany Topology
  • 2.1.2 IPv6 Not Supported
  • 2.1.3 Response Files Created through the Record Mode Are Not Supported
  • 2.1.4 Error Messages after Setting VIRTUAL_HOST_NAME
  • 2.1.5 Error Message in application.log File
  • 2.1.6 Middle Tier Installation Failure for Turkish Locale
  • 2.1.7 Recommended Locales for Simplified Chinese and Traditional Chinese
  • 2.1.8 Icon and URL Link Errors in Spanish and Brazilian Portuguese Language Locales
  • 2.1.9 Oracle HTTP Server Welcome Page Displays Only In English
  • 2.1.10 opmnctl Command Time Out with Old Data
  • 2.1.11 Exception in Error Log when Installing MainCD
  • 2.1.12 ONS Port Conflict When Oracle Database is Installed After Oracle Application Server
  • 2.1.13 OPMJA.MSG Message Format is Invalid
• 2.2 Documentation Errata
  • 2.2.1 Incorrect Installation Directory Path in Graphic
  • 2.2.2 ASG Standalone Kit Runinstaller Location Correction
  • 2.2.3 Incorrect Installation Requirements in the Screenshot of Select Installation Type Page
  • 2.2.4 Incorrect URL
  • 2.2.5 Additional Requirement for /etc/hosts File not Documented

3 General Management and Security Issues

• 3.1 General Issues and Workarounds
  • 3.1.1 Configuring JGroups for Minimum Thread Consumption by Adapters
  • 3.1.2 Deploying an Application Hangs During File Upload
  • 3.1.3 SOA Database Backups
  • 3.1.4 Limited Management Support for Multiple-JVM OC4J Instances
  • 3.1.5 OC4J Restart Required When Changing the Name or URL of a JDBC Data Source or Connection Pool
  • 3.1.6 Problem Removing a Property from a Native Data Source
  • 3.1.7 Use the Command-Line to Restart Standalone OC4J Instances
  • 3.1.8 TopLink Sessions Not Available in Application Server Control Console
  • 3.1.9 Unable to Receive MBean Notification Using OPMN to Start or Stop OC4J
  • 3.1.10 Using the Java Server Pages Standard Tag Libraries
  • 3.1.11 Cannot Browse System MBeans If Application Server and OC4J Instance Share the Same Name
  • 3.1.12 Considerations When Restarting Oracle Application Server After Applying the Patch Set
    • 3.1.12.1 Restarting the Application Server Instance If You Had Trouble Displaying the Application Server Control Console
    • 3.1.12.2 Displaying the Application Server Control Console After a 10g Release 3 (10.1.3.1.0) Advanced Installation
  • 3.1.13 Welcome Page Link to Application Server Control Not Working
• 3.2 Clustering and Replication Issues
  • 3.2.1 Using Oracle Universal Installer Provided Sample Cluster Discovery Address May Inadvertently Cluster Servers
• 3.3 Documentation Errata
  • 3.3.1 Valid Range of Multicast Addresses is Incorrect in the Application Server Control Online Help
  • 3.3.2 Correction About Configuring Oracle Application Server 10.1.2 with Oracle Application Server 10.1.3
  • 3.3.3 Additional Information for Changing Hostname
  • 3.3.4 Additional Information About Cloning and Oracle Enterprise Service Bus
  • 3.3.5 Additional Information About Cloning
  • 3.3.6 Online Help for the the Java SSO Session Timeout Field is Incorrect
  • 3.3.7 Incorrect Gateway Example in Oracle Process Manager and Notification Server Administrator's Guide
  • 3.3.8 Default Ping Timeout Value in OPMN Is 30 Seconds, Not 20
  • 3.3.9 Enabling and Disabling Components Is Supported
  • 3.3.10 Incorrect request Attribute Description
  • 3.3.11 Incorrect Title

4 Oracle JDeveloper

• 4.1 Introduction
• 4.2 General IDE Issues and Workarounds
  • 4.2.1 Incompatibility Between Internal CVS Client and CVSNT Server
• 4.3 Deployment Issues and Workarounds
  • 4.3.1 EJB Web Service Fails to Deploy to JDeveloper's Embedded Server
  • 4.3.2 ADF Web Application with Ejb3 Model Project Dependency Fails to Deploy
  • 4.3.3 Deploying JDeveloper Deployment Profiles to Archive Files on the File System
• 4.4 Modeling Issues and Workarounds
  • 4.4.1 Refactoring Context Menu and UML
  • 4.4.2 Java Modeler Accessibility
• 4.5 Toplink Issues and Workarounds
  • 4.5.1 Importing Tables with Multibyte Characters
• 4.6 EJB Issues and Workarounds
  • 4.6.1 EJB 3.0 Application Migration Issue (10.1.3 to 10.1.3.1)
  • 4.6.2 Running EJB 3.0 Applications
• 4.7 Web Services Issues and Workarounds
  • 4.7.1 Top-Down SOAP 1.2 Services Changed to SOAP 1.1 after Editing
  • 4.7.2 Top-Down Service with One-Way Operations Changed to Two-Way Methods after Editing
  • 4.7.3 Top-down Web Services Generated with Enumerated Types Fail Validation
  • 4.7.4 Deleting InitParam or Header in a Web Service Handler Causes an Error
  • 4.7.5 Web Service Proxy Fails when Running with Reliability Settings
  • 4.7.6 'Invoke' Button Not Present in Enterprise Manager for Testing EJB3.0 Web Service on External OC4J
  • 4.7.7 Invalid Web Service Endpoint in Generated Proxy for Multi-Port WSDLs
  • 4.7.8 Runtime Exception when More than One Web Service Exists in a Project
• 4.8 JavaServer Faces (JSF) Issues
  • 4.8.1 In JSF 1.1_02 Pages under /WEB-INF Fail to Load
• 4.9 Miscellaneous Issues and Workarounds
  • 4.9.1 Using JAZNMigrationTool with JDeveloper
  • 4.9.2 Running ADF Installer against Application Server 10.1.2 Instance
  • 4.9.3 Restore Option Does Not Restore bc4j.ear

5 Oracle Application Server Packaged-Application Adapters

• 5.1 OracleAS Adapters: General Issues and Workarounds
  • 5.1.1 Namespace Requirements
  • 5.1.2 Testing Outbound BPEL and ESB Processes
  • 5.1.3 Schema Validation
  • 5.1.4 HTTP Repository Connection
  • 5.1.5 Using Business Services Engine for Inbound Processing
  • 5.1.6 Using Business Services Engine with a File Repository
  • 5.1.7 Synchronous Events
  • 5.1.8 Ports Option for Inbound Processing
  • 5.1.9 Supported Custom Objects
  • 5.1.10 Windows Shortcuts
  • 5.1.11 OPMN and JCA Test Servlet Startup Error
  • 5.1.12 Adapter Certification
  • 5.1.13 Adapter Compatibility
  • 5.1.14 Unsupported Configuration
  • 5.1.15 Encoding Support
  • 5.1.16 New OracleAS Adapter J2CA Targets
  • 5.1.17 Invoking a Run-Time Message When BSE Is Unavailable
  • 5.1.18 Invoking Outbound BPEL Process at Run Time Using BSE
  • 5.1.19 WSIL Browser Not Working in JDeveloper
  • 5.1.20 Using the J2CA Test Tool for Outbound Only
  • 5.1.21 J2CA Test Tool Does Not Support DBCS Input
  • 5.1.22 BSE Web Services Browser Pages Do Not Support DBCS Input
  • 5.1.23 Creating an ESB Process for Web Services
  • 5.1.24 Adapter Language Certification
• 5.2 OracleAS Adapter Application Explorer
  • 5.2.1 Environment Variable and Permission Settings
  • 5.2.2 Unable to Connect to Remote Machines Using File or DB Repositories for J2CA Configurations
• 5.3 OracleAS Adapter for PeopleSoft: Issues and Workarounds
  • 5.3.1 PeopleSoft Versions and PeopleTools Release Levels Supported
  • 5.3.2 PeopleSoft LDAP Authentication Incompatible
  • 5.3.3 Automatic Reconnect to PeopleSoft
  • 5.3.4 HTTPS Protocol
  • 5.3.5 PeopleSoft Messages
  • 5.3.6 Limitation with Level 2 Scrolls
  • 5.3.7 Limitation with Level 3 Scrolls
  • 5.3.8 Limitation with Effective Dated Scrolls
  • 5.3.9 Limitation When Inserting a Second Row for Level 1, 2, or 3 Scrolls
  • 5.3.10 Limitation when Creating a Schema for Multilevel Component Interfaces
  • 5.3.11 PeopleTools Date Format
  • 5.3.12 Generating Java APIs
  • 5.3.13 Differences Between Component Interface Functionality and Adapter Functionality
  • 5.3.14 Missing Field Errors When Using a Component Interface
  • 5.3.15 Support for Related Display Fields
  • 5.3.16 Differences Between Component Interface Functionality and Adapter Functionality
  • 5.3.17 Multiple Effective Dated Scrolls
  • 5.3.18 Debug Message
  • 5.3.19 LOCATION Component Interface
  • 5.3.20 Component Interface Names
  • 5.3.21 Component Interface Java API Compilation Errors (People Tools 8.46)
• 5.4 OracleAS Adapter for MySAP ERP: Issues and Workarounds
  • 5.4.1 MySAP ERP Versions and APIs
  • 5.4.2 Intermediate Documents (IDocs) During Inbound Processing
  • 5.4.3 Unable to Connect to an SAP Target in BSE
  • 5.4.4 SAP IDoc Data with Japanese DBCS Characters Overflows and Truncates Characters
  • 5.4.5 No Values Set for Code and Details in Binding Fault
  • 5.4.6 MySAP Adapter Exceptions
• 5.5 OracleAS Adapter for Siebel: Issues and Workarounds
  • 5.5.1 Siebel Versions and APIs Supported
  • 5.5.2 Additional Configuration in the Siebel Environment
  • 5.5.3 Automatic Reconnect to Siebel
  • 5.5.4 Updating or Deleting Siebel Records Using OracleAS Adapter for Siebel
  • 5.5.5 Adapter Exception Error If Siebel Request Document Contains Japanese Characters
  • 5.5.6 HTTPS Protocol
  • 5.5.7 Multi-Value Groups
  • 5.5.8 Siebel Schema Issue When Generating Multiple WSDL Files
  • 5.5.9 Business Services in Siebel 7.8
  • 5.5.10 Siebel Connectivity Prerequisites
• 5.6 OracleAS Adapter for J.D. Edwards OneWorld: Issues and Workarounds
  • 5.6.1 J.D. Edwards OneWorld Platforms, Products, and Releases Supported
  • 5.6.2 J.D. Edwards OneWorld Inbound WSDL Generation on UNIX Platforms
  • 5.6.3 J.D. Edwards OneWorld Unit Of Work (UOW)
  • 5.6.4 J.D. Edwards OneWorld Versions and Library Files
• 5.7 Software Maintenance Notice
• 5.8 Documentation Errata
  • 5.8.1 Configuring the Database Repository for J2CA
  • 5.8.2 The Data Export Control Table and the Processing Log Table

6 Oracle Application Server Technology Adapters

• 6.1 Oracle Application Server Adapter for Files/FTP Issues and Workarounds
  • 6.1.1 Using CorrelationSets With File Adapter
  • 6.1.2 Setting up Maverick on FTP Adapter
• 6.2 Oracle Application Server Adapter for Java Message Service Issues and Workarounds
  • 6.2.1 JMS adapter in an XA scenario against AQ-JMS (OJMS)
  • 6.2.2 ESB Cannot Run JMS Adapter (OEMS JMS provider) in Non-Managed Mode
  • 6.2.3 Regression Stress - Dequeue Fails with AQJMSException in AQJMS Advanced Scenario
  • 6.2.4 When using Topics with OJMS (AQ based JMS), AQ JMS Topic Hangs, and Ceases to Dequeue
  • 6.2.5 Enabling Native Correlation in JMS Adapter
    • 6.2.5.1 Native Adapter Correlation
    • 6.2.5.2 Oracle BPEL Process Manager Correlation Sets
• 6.3 Oracle Application Server Adapter for Advanced Queuing Issues and Workarounds
  • 6.3.1 Dequeuing in the AQ Adapter is Very Slow for Large Numbers of Messages
• 6.4 Oracle Application Server Adapter for Database Issues and Workarounds
  • 6.4.1 DB Adapter Wizard Shows Empty (Blank) Page After Creating DB Connection
  • 6.4.2 Faulted DBAdapter Instances Do Not Appear in BPEL Console
• 6.5 Oracle Application Server Adapter for MQSeries Issues and Workarounds
  • 6.5.1 Mandatory Patch for Oracle Application Server Adapter for MQSeries
• 6.6 Oracle Application Server Adapter for Oracle Applications Issues and Workarounds
  • 6.6.1 Schema for Business Event Payload Cannot be Specified in the Wizard
• 6.7 Documentation Errata
  • 6.7.1 Incorrect Values of the hostOSType and Indextype Parameters
  • 6.7.2 Incorrect Segmentation Property Name
  • 6.7.3 Using Data Source While Creating a Server Connection in AQ Adapters when oc4j-ra.xml Is Not Configured
  • 6.7.4 Implication of Dequeue Condition in AQ Adapters
  • 6.7.5 XMLType Is Supported in the 10.1.3.1 Release

7 Oracle Enterprise Service Bus

• 7.1 General Issues and Workarounds
  • 7.1.1 The SOA Basic Installation Type Should be Used Instead of the ESB Standalone Developer Installation Type
  • 7.1.2 Performance Degradation of Dequeuing Operations Against AQ When Using an Oracle 10.2.0.2 Database
  • 7.1.3 Memory Usage Grows Gradually in Default Installation at High Volume
  • 7.1.4 Filter Expression Only Supports XPath Functions that are Included in the XPath 1.0 Specification
  • 7.1.5 External Dependencies Used at Design Time Must Be Available at Deployment Time
  • 7.1.6 Multibyte Characters Are Not Supported in Some ESB Component Names
• 7.2 Configuration Issues and Workarounds
  • 7.2.1 ESB Server Displays a Warning Message When Shut Down
  • 7.2.2 Oracle ESB Control Does Not Display Correctly For Some Window Sizes
  • 7.2.3 Access Problem After Logging into Oracle ESB Control Using Internet Explorer
  • 7.2.4 Timeout Exceptions When Using Oracle Enterprise Service Bus
  • 7.2.5 Missing pc.properties After Completing the ESB Standalone Installation
  • 7.2.6 An Inbound Adapter Service and its Corresponding Routing Service Should Reside in the Same ESB System
  • 7.2.7 Configuration of an Additional Design Time Instance in a High Availability Deployment Requires Additional Configuration
  • 7.2.8 New Parameters in the ESB_PARAMETER Table are Required for a Non-default OC4J JMS Setup
  • 7.2.9 Non-transactional MQ Adapter Incorrectly Configured as Transactional
• 7.3 Documentation Errata
  • 7.3.1 Some Oracle Enterprise Service Bus Features are in Preview Mode
  • 7.3.2 Oracle Enterprise Service Bus and Oracle Application Server Integration B2B
  • 7.3.3 Incorrect Account Name Mentioned in Oracle Enterprise Service Bus Installation Guide

8 Oracle BPEL Process Manager

• 8.1 Installation and Deinstallation Issues and Workarounds
  • 8.1.1 OC4J Instance Names of 14 or More Characters Cause Oracle BPEL Process Manager Installation Failure
  • 8.1.2 Use the SOA Basic Install Type Instead of the Oracle BPEL Process Manager for Developers Installation Type
  • 8.1.3 Oracle BPEL Process Manager Clusters Do Not Need to Be Part of an OPMN Cluster
  • 8.1.4 EJB URL in wf_client_config.xml Is Incorrect After Installation
  • 8.1.5 Installing BPEL on OID-Associated J2EE
  • 8.1.6 Error Message Can Be Ignored During BPEL Standalone Installation
  • 8.1.7 Deploying BPEL Processes to All Nodes in a Cluster
  • 8.1.8 Installation Impact on Adapter Endpoint Activation Topologies
  • 8.1.9 Changes to ant-orabpel.properties Required for Certain Clustering Configurations
  • 8.1.10 Surviving Nodes Do Not Automatically Continue Instance Execution After a Failover
• 8.2 Modeling and Design-Time Issues and Workarounds
  • 8.2.1 Cannot Exchange Multipart SOAP Messages Between Oracle BPEL Process Manager and a Remote Web Service
  • 8.2.2 Cannot Select Property Aliases in project_name.wsdl File
  • 8.2.3 BPEL Processes Initiated by Partner Links Referring to Adapters
  • 8.2.4 Dragging a Decision Service Icon into a BPEL Diagram Activities Area
  • 8.2.5 Decision Service Cannot Be Edited in Oracle JDeveloper
  • 8.2.6 Correlation Sets in Previously Deployed Versions May Be Overwritten
  • 8.2.7 Change in HeaderHandler from Release 10.1.2.0.2 to Release 10.1.3.1.0
  • 8.2.8 Online Help for Invocation Pattern Operations in a Decide Activity
  • 8.2.9 WSIF Bindings Generated from Oracle JDeveloper Are Not Interoperable with Oracle BPEL Process Manager
  • 8.2.10 BPEL XPath Functions File and Console Link Location
  • 8.2.11 Schema Names Do Not Support Multibyte Characters
  • 8.2.12 Creating an Application Server Connection in Oracle JDeveloper with Non-oc4jadmin Users
  • 8.2.13 Running the Adapter Configuration Wizard in Edit Mode Removes Property Aliases in an Empty BPEL Process
  • 8.2.14 Java Class BPELProcessRevisionInfo Has Moved to BPELProcessMetaData
• 8.3 Deployment and Run-Time Issues and Workarounds
  • 8.3.1 Missing ORMI Message
  • 8.3.2 Directory Reference for File Adapter Not Updating Correctly
  • 8.3.3 Reportees of the Topmost User in a Hierarchy Are Not Always Displayed
  • 8.3.4 TaskManager Is Not Listed Under Deployed Processes in Oracle BPEL Control
  • 8.3.5 Adapter-Based Application Deployment in OracleAS Integration InterConnect-Oracle BPEL Process Manager Environment Throws Exception
  • 8.3.6 BPEL Compiler Error When No Partner Link Exists
  • 8.3.7 Unit Test Does Not Support Iterative Partner Invocations
  • 8.3.8 OBANT.SH Does Not Handle JSSO Login If the HW_Services Application is JSSO Enabled
  • 8.3.9 ClassCastException Error Message with 10.1.2 Application Server Connections
  • 8.3.10 Unique IP Address Is Needed to Create an Application Server Connection
  • 8.3.11 Changing IP Requires Manual Deletion of tmp Directory
  • 8.3.12 Enterprise Manager Control Does Not Provide Some Oracle BPEL Process Manager Functions
  • 8.3.13 Starting Oracle BPEL Process Manager Through Oracle Enterprise Manager
• 8.4 Workflow and Worklist Issues and Workarounds
  • 8.4.1 Manually Configuring Oracle BPEL Process Manager on Oracle Application Server to Support Identity Management
  • 8.4.2 Deploying BPEL Projects with Workflow from Oracle JDeveloper
  • 8.4.3 Workflow Names Must Not Include Periods
  • 8.4.4 Compilation Warning Messages That Can Be Ignored
  • 8.4.5 Deleting an Entire User Task Activity
  • 8.4.6 Using the Category List in Oracle BPEL Worklist Application
  • 8.4.7 Getting Task Details with the getWorklistTaskDetails API
  • 8.4.8 Adding Delays to Task Operations
  • 8.4.9 Using the Custom Identity Service Provider Plug-in Sample on the Middle Tier
  • 8.4.10 Configuring the TaskActionHandler and TaskManager Services to Support SSL
  • 8.4.11 Full Path Name Needed for Task Attachment Stylesheet
  • 8.4.12 Recovery from Internal Server Error in Worklist Application
  • 8.4.13 Null Pointer Error During UpdateTaskOutcomeandRoute Call
  • 8.4.14 Task Definition Within a Human Task Activity Is Not Created Correctly
  • 8.4.15 Creation Dates Are Required for the Worklist Application Productivity Reports
  • 8.4.16 The Worklist Application Does Not Support SSO or JSSO Authentication
  • 8.4.17 High CPU Usage When Using a Human Task Activity
  • 8.4.18 Use the Workflow Folder Context Menu (Especially for Form Generation Actions)
  • 8.4.19 Human Task E-Mail Notification Does Not Support Multibyte Contents
  • 8.4.20 Multibyte Human Task Name Produces File Not Found Error
  • 8.4.21 Deployment Errors When the Application Server Connection OC4J Instance Name is Incorrect
  • 8.4.22 Creating a Human Task Activity Inside a Switch Activity
  • 8.4.23 Human Task Flex Field Mapping Restriction Related to BPEL Process Instances
  • 8.4.24 Identity Service Structural Requirements
  • 8.4.25 Searchable Attributes in LDAP Implementations
• 8.5 Notification Issues and Workarounds
  • 8.5.1 Some E-Mail Attachments Are Corrupted When Using ora:readFile
  • 8.5.2 SMS Notification Requires workPhone Attribute
  • 8.5.3 Notification Activity Contents Are Not Visible
  • 8.5.4 Role of NotificationServiceFault in 10.1.3
• 8.6 Transformation Issues and Workarounds
  • 8.6.1 Database Functions with JNDI Names Do Not Work Within a MapTest Window
• 8.7 XPath Expression Builder Issues and Workarounds
  • 8.7.1 Hyphens in XPath Expressions
  • 8.7.2 Some Listed XPath Expressions Are Not Appropriate for Human Task Workflow
  • 8.7.3 Null Pointer Error When Using a String Value in the XPath Expression Builder
• 8.8 Oracle BPEL Control and Oracle BPEL Server Issues and Workarounds
  • 8.8.1 Domain Names Must Be in Lower Case
  • 8.8.2 Safari Browser Is Not Supported
  • 8.8.3 Oracle BPEL Control Reports
  • 8.8.4 Unable to Delete a Domain or Recreate a Domain with the Same Name
  • 8.8.5 Error in Oracle BPEL Server Window When Reloading a BPEL Process Can Be Ignored
  • 8.8.6 Oracle BPEL Control Displays an Out-of-Memory Error and Oracle BPEL Server Restarts
  • 8.8.7 Logging In to Oracle BPEL Control Using Oracle Access Manager
  • 8.8.8 Creating BPEL Test Reports in Junit Format
  • 8.8.9 Error Messages Returned by Oracle Web Services Manager to Oracle BPEL Process Manager
• 8.9 Oracle BPEL Portlets Issues and Workarounds
  • 8.9.1 Oracle BPEL Control Report Portlets
  • 8.9.2 Oracle BPEL Worklist Application Portlets
• 8.10 Globalization/Multibyte Character Issues and Workarounds
  • 8.10.1 Ruler Scale Is Not Multibyte-Compliant in the Native Format Builder Wizard
  • 8.10.2 Encoding Issue for ora:readFile
  • 8.10.3 Installing Oracle BPEL Process Manager for Traditional Chinese
  • 8.10.4 Western European Number Format Issue in Transformations
• 8.11 Sample Demos and Tutorials Issues and Workarounds
  • 8.11.1 Missing Content in the readme.txt file for the XAInsert Sample
  • 8.11.2 Further Explanation About the BankTransferFlow and BankTransferFlowWith Compensation Demos
  • 8.11.3 No Audit Trail for the BankTransferFlow and BankTransferFlowWith Compensation Demos
• 8.12 Javadoc Errata
  • 8.12.1 ASSIGNMENT_FILTER_ALL Is Not Supported
  • 8.12.2 Correct Argument for oracle.bpel.services.workflow.query.ITaskQueryService.queryViewTasks
  • 8.12.3 Classes Not Included in the Javadoc
• 8.13 Documentation Errata
  • 8.13.1 Deploying BPEL Processes in a Cluster
  • 8.13.2 Setting up BPEL in a High Availability Configuration
  • 8.13.3 Creating Users and Groups to Access New and Existing BPEL Domains
  • 8.13.4 Password Entry Required in User Credentials File
  • 8.13.5 Explicitly Setting optSoapShortcut in the domain.xml File
  • 8.13.6 Updated syncMaxWaitTime Property Definition
  • 8.13.7 Incorrect Names in Developer's Guide for ROUND_ROBIN, MOST_PRODUCTIVE, and LEAST_BUSY Dynamic Assignment Functions
  • 8.13.8 Online Help for Property Tab of Partner Link Window is Incorrect
  • 8.13.9 Invalid Namespace Prefix for getFaultAsString Function

9 Oracle Web Services Manager

• 9.1 General Issues and Workarounds
  • 9.1.1 Basic Standalone Installation Cannot be Migrated
  • 9.1.2 Starting the Oracle WSM Server
  • 9.1.3 Error on Import Services Page
  • 9.1.4 Step Instance Creates One or More Long-Lived Connection to the Directory
  • 9.1.5 Deploying Oracle Web Services Manager Monitor
  • 9.1.6 Accessing a Virtualized Web Service
  • 9.1.7 Valid User Names and Passwords
  • 9.1.8 Multibyte User Names and Passwords
  • 9.1.9 Date and Time Format
  • 9.1.10 Using Non-Unicode Character Sets in the Database
  • 9.1.11 BouncyCastle is the Supported Security Provider for PKCS #12 Certificates
  • 9.1.12 Securing Oracle WSM Components over SSL
• 9.2 Configuration Issues and Workarounds
  • 9.2.1 NFS-Mounted Installations
  • 9.2.2 XE DB Settings
  • 9.2.3 Out of Memory Exception
  • 9.2.4 Web Browser Times Out
  • 9.2.5 Oracle Access Manager SDK Path
  • 9.2.6 Invoking Service from a Proxy Server
• 9.3 Documentation Errata
  • 9.3.1 One Oracle WSM Gateway Per Oracle WSM Instance
  • 9.3.2 Jar Files Required for Tibco JMS
  • 9.3.3 WSMADMIN Commands on UNIX Systems
  • 9.3.4 Correction to Command Syntax
  • 9.3.5 Correction to Proxy Server Settings Syntax
  • 9.3.6 Correction to Extract Credentials Policy Step
  • 9.3.7 AXIS Client Support
  • 9.3.8 Changing Database Passwords
    • 9.3.8.1 Updating the Database Configuration Properties
  • 9.3.9 Authentication Using Active Directory

10 Oracle Business Activity Monitoring

• 10.1 General Issues and Workarounds
  • 10.1.1 Some Product Features Previews Only
  • 10.1.2 Some Product Features Not Supported
  • 10.1.3 DateAdd Function in Filters Can Produce Incorrect Active Data
  • 10.1.4 Logging In Using "Run as" Not Supported
  • 10.1.5 Install Complete IIS When MS Cluster Service Installed
  • 10.1.6 The Oracle BAM Active Data Cache Service May Fail to Start
  • 10.1.7 Testing a BAM Server Connection in JDeveloper
  • 10.1.8 ICommand: Exporting Reports with Background Images
  • 10.1.9 ICommand: Special Character in Parameter Value Causes Export Failure
  • 10.1.10 Restricting BAM Web Services to BAM Users
  • 10.1.11 Web Service Calls May Not Be Logged
  • 10.1.12 Globalization and Localization Support Limitations
  • 10.1.13 Accessibility Compliance Limitation
  • 10.1.14 Performance Improvement for Microsoft Internet Explorer 6 Users
• 10.2 General Active Studio Issues and Workarounds
  • 10.2.1 Possible Active Studio Issues When Using Non-Default Windows DPI Settings
  • 10.2.2 Save As Dialog Box May Appear Inappropriately
  • 10.2.3 Save Prompt Not Displayed When Closing Report After Deleting a View
  • 10.2.4 ADC Exception on Adding Timestamp to a Non-Empty Data Object
  • 10.2.5 BLANK Selection Not Supported in Oracle Database
  • 10.2.6 Drill-through Fields Grayed Out After Editing Drill-through
  • 10.2.7 Rank Column Not Available in Some Views
  • 10.2.8 Use Global Change Data Object to Fix Reports Using Deleted Data Objects
  • 10.2.9 Pause/Resume Active Data Does Not Work After Viewset Expires
  • 10.2.10 Changing Data Types in Data Object Can Break Reports
  • 10.2.11 Using Default Report Name Can Generate an Error
  • 10.2.12 Active Data May Fail On Simultaneous Report Loading
  • 10.2.13 Use Field IDs Instead of Field Names in Shortcut Report URL
  • 10.2.14 Active Lookups Do Not Work With Deletes
  • 10.2.15 Multi-level Calculations in Combination with Other Data Manipulation
  • 10.2.16 Errors When Fields Hidden or Revealed After View Design
  • 10.2.17 Error When Group-by Data Crosses Year Boundary
  • 10.2.18 String Parameters Not Supported in Calculator
  • 10.2.19 Error When Changing View Type
  • 10.2.20 Save Offline Limitations
• 10.3 List View Issues and Workarounds
  • 10.3.1 Streaming List Range Buttons May Not Appear at Times
  • 10.3.2 Updating Ordered List: Cancel Button Not Functional with Top N
  • 10.3.3 Heading Text Cannot Be Removed
  • 10.3.4 Special Characters Affect Sort Order in Updating Ordered Lists
• 10.4 Chart View Issues and Workarounds
  • 10.4.1 Timestamp on Axis Label Causes ADC Error
  • 10.4.2 Data Labels Cut Off with Active Data
  • 10.4.3 Null Values Incorrect When Grouping in Charts
  • 10.4.4 Labels May Overlap in Charts
  • 10.4.5 Charts Using Top N May Fail with Active Data
  • 10.4.6 Grouping Can Cause Error
  • 10.4.7 Time Groups in Charts Must Use Default Date Format
  • 10.4.8 X-Axis May Not Clear Appropriately in Continuous Time Series
  • 10.4.9 Stacked Bar Chart Legend May Be Obscured by Negative Values
  • 10.4.10 Target Lines Work Only in Bar Chart
  • 10.4.11 Funnel Chart Limitations
  • 10.4.12 SPC Chart Limitations
• 10.5 Miscellaneous View Issues and Workarounds
  • 10.5.1 Active Now May Show Wrong Results with KPI View in Report
  • 10.5.2 Faulty View Report Hyperlink in Action Form View
  • 10.5.3 Surface Prompts View Does Not Render for Email
  • 10.5.4 Resizing Column Group Moves Entire Group View
  • 10.5.5 Crosstab, Summary Crosstab, and Matrix View Limitations
  • 10.5.6 Excel View Limitations
  • 10.5.7 Columnar Report and View Limitations
• 10.6 Filter Issues and Workarounds
  • 10.6.1 BLANK Value in Prompt Causes Error
  • 10.6.2 "Is Like" Filter on Datetime Fields Does Not Work
  • 10.6.3 Incorrect Daylight Savings Time May Be Displayed
  • 10.6.4 Cannot Create Filter When Field Changed to Lookup Field in Data Object
• 10.7 Calculated Field Issues and Workarounds
  • 10.7.1 In Some Cases Calculated Field Cannot Be Deleted
  • 10.7.2 Prompts and Parameters Wizard Does Not Include Calculated Fields
  • 10.7.3 Multi-level Calculation with Max or Min and Boolean Do Not Work
  • 10.7.4 ADC Error on Division with Two Calculated Fields
• 10.8 Alert Issues and Workarounds
  • 10.8.1 Time Change Requires BAM Services Restart
  • 10.8.2 Special Characters Can Cause Error When Editing Alerts
  • 10.8.3 Changing Event Type in Parameterized Alert Causes Exception in Event Engine
  • 10.8.4 Calculated Fields Do Not Appear in Alert Filters
  • 10.8.5 Filter Items May Appear Misaligned
  • 10.8.6 Alerts Not Deleted with Parent Reports
  • 10.8.7 Cancel Does Not Work on Clear Alert History
  • 10.8.8 Invalid Windows File Name Characters in Report Name
  • 10.8.9 Alerts Still Launch After Report Is Deleted
  • 10.8.10 Orphaned Alert Not Marked
  • 10.8.11 Unique Naming Not Enforced on Alert Parameters
  • 10.8.12 Row-level Security Not Supported for Alerts on Data Change
  • 10.8.13 Non-applicable Aggregates Included in Select Data Field Dialog
  • 10.8.14 Duplicate Fields May Appear in Field Lists
  • 10.8.15 Alerts on Aggregates May Misfire
  • 10.8.16 Calling .NET Web Service Directly Using External Action
  • 10.8.17 Alert Actions Ignored if Previous Action Fails
• 10.9 Administrator and Architect Issues and Workarounds
  • 10.9.1 Plan Setting Check May Take a Long Time
  • 10.9.2 Plan Does Not Restart When Plan Monitor Service Loses ADC Connection
  • 10.9.3 Cannot Edit Data Objects with Some Alerts
  • 10.9.4 Permission Changes May Not Propagate to Lookup Objects
  • 10.9.5 Invalid Lookups Prevent Deletes From Being Sent to the View
  • 10.9.6 Non-administrators Cannot Clear Data Objects with Joins
  • 10.9.7 Lookups That Return Multiple Rows Not Supported
  • 10.9.8 Decimal with Scale 10 Allows Seven Digits Left of Decimal Point
  • 10.9.9 Error May Occur When Deleting Row from Lookup Table
• 10.10 Enterprise Link Issues and Workarounds
  • 10.10.1 Nonexistent Alert Does Not Cause Plan to Fail
  • 10.10.2 GET Method Not Working in Enterprise Link Web Service
  • 10.10.3 .NET Framework 2.0 Causes Error When Running Enterprise Link Plans
• 10.11 BPEL-BAM Integration Issues and Workarounds
  • 10.11.1 10.1.3.1.0 BPEL and JDeveloper BPEL Plugin Must be Used
  • 10.11.2 Changing BAM Server From BPEL Console Takes No Effect at Runtime
  • 10.11.3 Batched Messages Lost On Restart
  • 10.11.4 Data Object Read Permission Required for Updates/Upserts or Deletes
  • 10.11.5 Duplicate Messages on IIS Restart
  • 10.11.6 Sensor Actions Order is Not Guaranteed When Using Batch Mode
  • 10.11.7 Western European Number Format Issue in Transforms

11 Oracle Sensor Edge Server

• 11.1 Installation and Configuration Issues
  • 11.1.1 OC4J 10.1.2 Must be Stopped if Installing Against It
  • 11.1.2 Default Database Tablespaces
  • 11.1.3 DBMS Lock Problem
  • 11.1.4 Unable to Create a JMX Connection
  • 11.1.5 Restart Server for Changes to Take Effect
  • 11.1.6 Oracle Sensor Edge Server Installation Fails
  • 11.1.7 Resolving the Reboot Issue for XML Configuration
• 11.2 General Issues
  • 11.2.1 Using UTL_EDG.REMOVE_RULE Displays an Error
  • 11.2.2 Adding a Rule Displays an Error
  • 11.2.3 Localization -- Navigation Tree in the SES Console Renders as the Server Locale-Defined Character Set
  • 11.2.4 Reassignment of Audio Event Type (207)
• 11.3 Documentation Issues
  • 11.3.1 Documentation for Oracle Sensor Edge Server Extensions
  • 11.3.2 Manually Deploying Sensor Data Streams Against an Existing Sensor Data Repository

12 Oracle HTTP Server

• 12.1 Issues and Workarounds
  • 12.1.1 Configuring Weighted Routing for AJP13 Destinations
  • 12.1.2 Changing the Location of the PID File Requires a Change in apachectl
  • 12.1.3 Routing Requests to Different Middle Tiers Based on the URL of the Request
• 12.2 Documentation Errata
  • 12.2.1 Oracle HTTP Server Apache Version Number
  • 12.2.2 Log Level Choices for Configuring IIS Listener for Single Sign-On are Incorrect
  • 12.2.3 Correction to SSLCARevocationFile Directive Description
  • 12.2.4 Correction to SSLCARevocationPath Directive Description
  • 12.2.5 Incorrect Tags Listed for 40-Bit and 56-Bit Export Ciphers
  • 12.2.6 Incorrect Web Address for mod_php Extensions Information
  • 12.2.7 Clarification for the Name of the Oracle Application Server Proxy Plug-In Definition File

13 Oracle Containers for J2EE

• 13.1 Configuration, Deployment, and Administration Issues and Workarounds
  • 13.1.1 Remove the Tomcat Examples
  • 13.1.2 Deprecated Environment Variables KeepWrapperCode, WrapperCodeDir, and DoNotReGenerateWrapperCode
  • 13.1.3 Deprecated System Property ejb.batch.compile
  • 13.1.4 Desupported orion-ejb-jar.xml Attributes
  • 13.1.5 System Property for File Information Cache Size
  • 13.1.6 Use of '/' for Context Root
  • 13.1.7 Allowed Format for Version Numbers in MANIFEST.MF File
  • 13.1.8 Having the AJP Listener Use the Loopback Interface Only
  • 13.1.9 Determining JVM, OC4J Instance, or Application Server Instance
  • 13.1.10 Use of the http.file.allowAlias Property
  • 13.1.11 Starting OC4J Using JDK 1.4.2 for a Headless Console
  • 13.1.12 Invocation by Servlet Name without Mapping Is Disabled by Default
  • 13.1.13 Warning Regarding Maximum Concurrent Timers
  • 13.1.14 New Wait Option for Sequential Redeployment to a Cluster
  • 13.1.15 Job Scheduler Redeployment
  • 13.1.16 Incompatible ONS Versions
  • 13.1.17 How to Specify Ports for State Replication in OPMN
  • 13.1.18 Incorporating Ant Tasks Using Ant 1.6.5 Outside OC4J with the OC4J Administrative Client
  • 13.1.19 Specifying the Mapping Attribute
  • 13.1.20 Using opmn Settings for OC4J home Instance As Template for New Instance
  • 13.1.21 OC4J Instances in a Group Must Have Same Version
  • 13.1.22 Same Destination for Trace Output from Two OC4J Instances Not Supported
• 13.2 Servlet Issues and Workarounds
  • 13.2.1 Servlet Invocation by Classname Disabled by Default
  • 13.2.2 Enabling Access Logging for Web Applications
  • 13.2.3 OC4J 10.1.3.1.0 Honors Session id Value Differently
  • 13.2.4 Exception and Stack Trace No Longer Displayed in HTML Error Page
  • 13.2.5 Disabling Servlet Reloading
• 13.3 JavaServer Pages (JSP) Issues and Workarounds
  • 13.3.1 Workaround to View JSP Demo Files
  • 13.3.2 Deprecated JSP Configuration Parameters
  • 13.3.3 ojsp Tag Libraries Deprecated
  • 13.3.4 Specifying justrun for Production Environment Efficiency
  • 13.3.5 Using a Tag Library with the ojspc Utility
• 13.4 EJB Issues and Workarounds
  • 13.4.1 EJB 3.0 Support
  • 13.4.2 EJB 3.0 Interceptors Supported in JDK 1.5 Only
  • 13.4.3 Remote EJB 3.0 Stateful Session Bean Does Not Failover When Using Extended Persistence
  • 13.4.4 Orion CMP Is Deprecated
  • 13.4.5 ejb-module Attribute remote Deprecated
  • 13.4.6 Support for persistence.xml in WEB-INF
  • 13.4.7 Default IP Address Stack
  • 13.4.8 Static EJB Method and JNDI Lookup Best Practices
  • 13.4.9 Support for BLOB-BLOB and CLOB-CLOB Mappings
  • 13.4.10 Migrating an Orion CMP Application With an Unmapped Entity Bean
  • 13.4.11 Set Managed Datasource Attribute manage-local-transactions To False When Using Oracle JMS Connector
  • 13.4.12 Excessive Bean Loading in Bi-directional, One-to-Many, and Many-to-Many Relationships with Orion CMP
• 13.5 Web Services Issues and Workarounds
  • 13.5.1 Configuration Issues
    • 13.5.1.1 Installation Fails in Web Services Inspection Language (WSIL) Configuration
  • 13.5.2 WebServicesAssembler Issues
    • 13.5.2.1 Multiple Service Elements in Top Down Web Service Assembly
    • 13.5.2.2 Relative Path Names Are Not Supported in WSDL or XSD Imports
    • 13.5.2.3 WebServicesAssembler Requires Schema Imports in the WSDL to Be Qualified by the schemaLocation Attribute
    • 13.5.2.4 The assemble Ant Task Raises an Exception when Java Files Contain J2SE 5.0 Annotations
  • 13.5.3 WSDL-Related Issues
    • 13.5.3.1 Support for Globalization Support (NLS) Characters in the WSDL
    • 13.5.3.2 Services that use Multiple Message Formats Cannot be Deployed in a Single Web Application
    • 13.5.3.3 genWsdl Command Does not Preserve Order of Variables
  • 13.5.4 Schema Features Limitations
    • 13.5.4.1 RPC Encoded Does Not Support Complex Types With Attributes
    • 13.5.4.2 XML Types xsd:choice and xsd:group Are Not Supported for Proxy or Top Down Web Service Assembly
    • 13.5.4.3 XML Type anyURI Is Not Supported for WSIF
  • 13.5.5 Test Page Issues
    • 13.5.5.1 Recursive Schema Definitions Are Not Supported in the Web Services Test Page
    • 13.5.5.2 Formatted XML Content Returned from a Service Invocation on the Web Services Test Page May Be Shown Incorrectly
    • 13.5.5.3 Test Page May Not Show Errors Originating from an Invalid Web Service WSDL
    • 13.5.5.4 Invalid Values in a Web Services Test Page Form Field May Result in an "Unable to get header stream in saveChanges" Error
    • 13.5.5.5 Web Services Test Page Does Not Support Globalization Support (NLS) Characters in User Name or Password
    • 13.5.5.6 Web Services Test Page Does Not Support the Schema Features: group, choice, union, or Derived Simple Types as Attributes
    • 13.5.5.7 Test Page Stress Test Report May Be Displayed Incorrectly Under Firefox or Mozilla
  • 13.5.6 Deployment Issues
    • 13.5.6.1 EJB 2.1 Web Services Deployed with an Invalid oracle-webservices.xml File
  • 13.5.7 Other Issues
    • 13.5.7.1 Get NodeLists by Using getFirstChild and getNextSibling Instead of getChildNode
    • 13.5.7.2 Using the 'class' Attribute in Ant Build Scripts to Specify JAX-RPC Web Service Handlers
    • 13.5.7.3 BEA Clients are Unable to Deserialize Responses from OC4J Web Services
    • 13.5.7.4 Mapping Issue with Simple Types (with Restrictions) on the .NET Platform
    • 13.5.7.5 genValueType Command Does Not Validate Restrictions
    • 13.5.7.6 XML Serialization Does Not Accept the Array Java Data Type for Document-Literal-Bare Message Format
• 13.6 OC4J Services Issues and Workarounds
  • 13.6.1 JNDI
    • 13.6.1.1 Spaces in Application Names
    • 13.6.1.2 Wrong Provider URL in the jndi.properties File
    • 13.6.1.3 New Package Names for RMI and Application Client Initial Context Factories
    • 13.6.1.4 Deprecated JNDI Environment Variables
    • 13.6.1.5 Local Host Not Supported
  • 13.6.2 Oracle Enterprise Messaging Service (OEMS)
    • 13.6.2.1 Error Starting OC4J after OracleASjms is Undeployed
    • 13.6.2.2 OC4J May Fail to Restart after Abnormal OC4J Shutdown
    • 13.6.2.3 XA-styled JMS Connections Not Supported Between OC4J Versions
    • 13.6.2.4 JMS Auto-Enlisting in Global Transactions is Desupported
    • 13.6.2.5 Changes in JMS Client Properties Require Restart
    • 13.6.2.6 Poor Performance When Persisting Messages to a Database
  • 13.6.3 Data Sources
    • 13.6.3.1 The oracleFatalError method is no Longer Available
    • 13.6.3.2 OracleConnectionCacheImpl Deprecated
    • 13.6.3.3 Orion CMP Fails Due to JDBC Driver Clash
    • 13.6.3.4 Upgrading the Oracle THIN JDBC Driver
  • 13.6.4 OC4J Transaction Support
    • 13.6.4.1 The In-DB Coordinator Is Deprecated
  • 13.6.5 RMI
    • 13.6.5.1 RMI Recommendations
    • 13.6.5.2 Incorrect "Provider URL..." Error Message
  • 13.6.6 XQS
    • 13.6.6.1 Updated XQS Client API
    • 13.6.6.2 SQL Usage has Changed
    • 13.6.6.3 Incorrect XQS Type-Checking Example
    • 13.6.6.4 XQS Schema Import Support
  • 13.6.7 Application Client Container
    • 13.6.7.1 Custom Security Callback Handler Fails
• 13.7 J2EE Connector Architecture (J2CA) Issues and Workarounds
  • 13.7.1 New Class Loader Architecture for Standalone Resource Adapters
  • 13.7.2 Deployment Dependencies between Standalone Resource Adapters
  • 13.7.3 Class Not Found Exceptions
  • 13.7.4 Restart of Default Application Required After Redeploying or Undeploying Internal Resource Adapters
• 13.8 Release Notes for OracleAS JAAS Provider and Security
  • 13.8.1 Correct JAZNMigrationTool Syntax
  • 13.8.2 Use of JAAS Permissions and JAZNMigrationTool with External LDAP Provider
  • 13.8.3 Proper Specification of osso.conf File Name for SSO Configuration
  • 13.8.4 User and Role APIs Replace OracleAS JAAS Provider Realm API Functions
  • 13.8.5 Migration Tool Issue: Prepending Oracle Internet Directory Realm Name to Custom Principals
  • 13.8.6 Controlling Caching of JNDI Contexts for LDAP Connections
  • 13.8.7 AJP13 Protocol Vulnerable to Bypass User Authentication
  • 13.8.8 JAZN Tool No Longer Includes -clustersupport
• 13.9 General OC4J Issues and Workarounds
  • 13.9.1 OutOfMemoryError on Multiple Restarts of Standalone OC4J through Application Server Control
• 13.10 Documentation Errata
  • 13.10.1 Web Services Guide
    • 13.10.1.1 Incorrect Link Provided for wsclient_extended.zip File
    • 13.10.1.2 Typos in XML Type Names in Advanced Web Services Developer's Guide
    • 13.10.1.3 ServerConstants Properties Cannot be used to Access the HTTP Layer from the Client
    • 13.10.1.4 Additions to List of Supported Platforms
  • 13.10.2 Oracle Application Server Advanced Web Services Developer's Guide
    • 13.10.2.1 Incorrect XML in Examples in the "Using Web Service Providers" Chapter
  • 13.10.3 Oracle Containers for J2EE Deployment Guide
    • 13.10.3.1 Incorrect Attribute Name in Example of Ant Task
    • 13.10.3.2 Incorrect Subswitch Names for admin_client.jar Commands
    • 13.10.3.3 Information Missing from Description of admin_client.jar -redeploy Command Subswitches
    • 13.10.3.4 File Name oracle-ant.jar Should Be ant-oracle.jar
    • 13.10.3.5 The version Property of the removeSharedLibrary Ant Task Should Be libraryVersion
    • 13.10.3.6 Checking for Updates by Comparing Directory and EAR or WAR Timestamps
    • 13.10.3.7 deploymentPlan Property Not Valid in Ant Task for WAR Deployment
    • 13.10.3.8 Incremental Redeployment of EJB Modules Not Supported by Application Server Control
  • 13.10.4 Oracle Containers for J2EE Configuration and Administration Guide
    • 13.10.4.1 Incorrect Subswitch Names for admin_client.jar Commands
    • 13.10.4.2 Information Missing from Description of admin_client.jar -redeploy Command Subswitches
    • 13.10.4.3 Incorrect Example for Disabling Text File Logging
    • 13.10.4.4 Format for Variables That Configure Text Logging for Web Sites
    • 13.10.4.5 Incorrect Description of Queue Attribute for Thread Pools
    • 13.10.4.6 Configuration of OPMN Gateway Element Shows Incorrect Order
    • 13.10.4.7 Starting Order Incorrect for Static Peer-to-Peer Replication
  • 13.10.5 Oracle Containers for J2EE Services Guide
    • 13.10.5.1 Wrong Data Source Element Name
    • 13.10.5.2 Wrong Defaults Listed for Connection Pool Attributes
    • 13.10.5.3 Invalid Attribute
    • 13.10.5.4 Revised Description for max-connections Attribute
  • 13.10.6 OracleAS JAAS Provider and Security Documentation Errata
    • 13.10.6.1 Incorrect Notes on 'Mixed Usage' between Identity Store and Policy Store
    • 13.10.6.2 Incorrect Note on Automatic Creation of Indirect User Accounts
    • 13.10.6.3 Obsolete <data-source> Element Cited
    • 13.10.6.4 Form Authentication Method Supported with Custom Login Modules
    • 13.10.6.5 Invalid Reference to x509cert.mapping.attribute Property
  • 13.10.7 Oracle Containers for J2EE Developer's Guide
    • 13.10.7.1 Missing Character in Service URL Strings
    • 13.10.7.2 Incorrect Setting for Client Module in orion-application.xml
  • 13.10.8 Oracle Containers for J2EE Servlet Developers Guide
    • 13.10.8.1 Do Not Specify a Host for the <host-access> domain Attribute
  • 13.10.9 Oracle Containers for J2EE Enterprise JavaBeans Developer's Guide
    • 13.10.9.1 Do Not Edit the boot.xml File As Documented

14 Oracle TopLink

• 14.1 General Issues and Workarounds
  • 14.1.1 Object-Relational Issues
    • 14.1.1.1 Incorrect outer join SQL on SQLServer2005
    • 14.1.1.2 UnitOfWork.release() not Supported with External Transaction Control
    • 14.1.1.3 ReportQuery Results for Aggregate Functions may be Truncated
    • 14.1.1.4 Attribute Joining of One-to-One Mappings not Supported with Inheritance
    • 14.1.1.5 Using Oracle Database Advanced Data Types may Fail with Some Data Sources
    • 14.1.1.6 Returning Policy with Optimistic Locking
    • 14.1.1.7 Using Timestamp
    • 14.1.1.8 Configuring Sequencing in sessions.xml
  • 14.1.2 Object-XML (JAXB) Issues
    • 14.1.2.1 Using Non-ASCII Characters with a JAXB 1.0 TopLink Project
    • 14.1.2.2 XML Document Preservation
    • 14.1.2.3 Multiple Composite Object Mappings Using Self "." XPath not Supported
    • 14.1.2.4 Marshalling a Non-root Object with Document Preservation
  • 14.1.3 Miscellaneous Issues
    • 14.1.3.1 Shared Installation
    • 14.1.3.2 Welcome Page
• 14.2 Documentation Errata
  • 14.2.1 Creating project.xml Programatically

15 High Availability

• 15.1 General Issues and Workarounds
  • 15.1.1 Compatible ASG Releases for OracleAS Instances from Different Oracle Application Server Releases
  • 15.1.2 Compatible ASG Releases in an OracleAS Disaster Recovery Topology
  • 15.1.3 Adding an Instance from a Remote Client Adds an Instance on the Local Instance and Not on the Remote Instance
  • 15.1.4 Switchover Operation in an Asymmetric Topology Requires All Components to be Shutdown on Instances on the Primary Site that Do Not Have a Standby Peer
  • 15.1.5 HTTP Server Configuration When Using a Server Load Balancer
  • 15.1.6 Problem Performing a Clone Instance or Clone Topology Operation
  • 15.1.7 OracleAS Guard Release 10.1.2.1.1 Cannot Be Used with Oracle RAC Databases
  • 15.1.8 OracleAS Guard Returned an Inappropriate Message When It Could Not Find the User Specified Database Identifier
  • 15.1.9 Database Instance on Standby Site Must Be Shutdown Before Issuing an asgctl create standby database Command
  • 15.1.10 Problem in an Oracle RAC-non Oracle RAC Environment with Naming Conventions
  • 15.1.11 In an Oracle RAC-non Oracle RAC Environment, an asgctl create standby database Operation Returns an Inappropriate Error When the Database Is Already in a Physical Standby State
  • 15.1.12 GNU Tar is Required for ASG Clone Topology or Clone Instance Operations
  • 15.1.13 ASG Operations Fail if Multiple DB ORACLE_HOMEs Exist on the Same System
  • 15.1.14 Placing the Oracle BPEL Process Manager Dehydration Store in a Database Managed by OracleAS Guard
  • 15.1.15 Application Server Components Tested and Certified with OracleAS Guard
  • 15.1.16 ASG to Catch Array Overflow Exceptions in Queries to Primary
  • 15.1.17 The create standby Command Fails if the Redo Log Files Directories do not Exist at the Standby
  • 15.1.18 Corrupt Index Blocks in Metadata Repository Databases
  • 15.1.19 Database SIDs Must be the Same for Database Peers at Primary and Standby Sites
  • 15.1.20 Use All Uppercase Characters for Database Initialization Parameters to Avoid Instantiate and Sync Problems
  • 15.1.21 Workaround for ASG_DUF-3800 "Failed trying to connect to the OPMN Manager" Error
  • 15.1.22 Use the Same Port for ASG on the Production and Standby Sites to Avoid clone instance Operation Problems
  • 15.1.23 Use Fully Qualified Path Names with the add instance Command
  • 15.1.24 ASG Cloning is Not Supported when the Number of Oracle Homes is Different at the Primary and Standby Hosts
  • 15.1.25 Start ESB Repository before Starting ESB Runtime Instances
  • 15.1.26 Use Static Routing for ESB Servers
• 15.2 Configuration Issues and Workarounds
  • 15.2.1 The asgctl shutdown topology Command Does Not Shut Down an MRCA Database That is Detected To Be of a repCa Type Database
  • 15.2.2 Only One Oracle RAC Node with an Instance on the New Primary Site Is Started Up Following an asgctl switchover Operation
  • 15.2.3 An asgctl add instance Operation from a Remote Client Adds an Instance on the Local System Rather than on the Intended Remote System
  • 15.2.4 Connecting to an OracleAS Guard Server May Return an Authentication Error
  • 15.2.5 All emagents Must Be Shut Down Before Performing OracleAS Guard Operations
  • 15.2.6 Procedure to Patch a 10.1.2.0.0 Disaster Recovery Setup with a 10.1.2.1.0 Patchset
  • 15.2.7 Running Instantiate Topology Across Nodes After Executing a Failover Operation Results in an ORA-01665 Error
  • 15.2.8 OracleAS Guard Is Unable to Shutdown the Database Because More Than One Instance of Oracle RAC is Running
  • 15.2.9 Add Instance Adds an Instance to Topology with Empty Instancename
  • 15.2.10 Create Standby Fails with if Initiated on a Different ASGCTL Shell
  • 15.2.11 Heartbeat Failure After Failover in Alert Logs
  • 15.2.12 Create Standby Database Fails If Database Uses OMF Storage or ASM storage
  • 15.2.13 Database Already Exists Errors During Create Standby
  • 15.2.14 Steps to Add a Database with OMF or ASM to ASG Topology
• 15.3 Documentation Errata
  • 15.3.1 Availability of a Previously Undocumented asgctl Command: create standby database
  • 15.3.2 "Oracle BPEL Process Manager Clustering" Chapter Can Be Found in the Oracle BPEL Process Manager Installation Guide
  • 15.3.3 Additional Site Switchover Information for RAC Deployments
  • 15.3.4 Configuring Jgroups and OC4J Groups in BPEL Active-Active Topology

16 Oracle Application Server Portal

• 16.1 Portlet and Provider Issues and Workarounds
  • 16.1.1 Error Configuring OC4J Standalone for OmniPortlet Deployment
• 16.2 Documentation Errors
  • 16.2.1 Edit Defaults Mode

17 Oracle Business Rules

• 17.1 Standalone OC4J Rule Author Installation
• 17.2 Multiple Inheritance Exception When Using XML Facts
• 17.3 Deploying Rule Author on Non-Oracle Containers
• 17.4 RL serviceDateValidation Error: Fact Class Should Be Declared Earlier