WCS: Carousel Integration Does Not Work In A RAC Environment
(Doc ID 2049729.1)
Last updated on MARCH 08, 2017
Applies to:Oracle Warehouse Management - Version 12.1.3 and later
Information in this document applies to any platform.
You find that using Oracle Warehouse Control Systems (WCS) the carousel integration does not work on a RAC instance if multiple nodes are used. This is due to the implementation using dbms_pipe.
Warehouse Control System (WCS) which is a subsystem of WMS that functions as a bridge between WMS and automated material handling devices does not work on Real Application Clusters (RAC) instances due to use of RDBMS pipes to handle device communications. DBMS_PIPE does not work on RAC when messages have to be sent across nodes in the cluster.
When E-Business Suite/WMS is installed on RAC, database sessions that send messages (from WMS mobile/desktop transactions) may be connected to a different node in the cluster than the node to which the WCS CarBri server is connected (listening for messages). Therefore WCS does not work when installed on RAC unless both the sending session and the receiving session (CarBri) are configured to connect to the same node in the cluster. Connecting both sessions to the same node has its drawbacks (no failover, workload imbalance, etc.), and in some cases this is not a workable option.
Warehouse Control System (WCS) works on RAC instances with the latest changes. Changes have been done to use DBMS_AQ instance of RDBMS pipes to handle device communications. (Note that DBMS_PIPE is still the recommended communication method when not using RAC). To setup WCS for RAC after applying the patch:
- 1. Set the new site-level profile WMS: Enable RAC deployment for WCS to Yes.
- 2. For each WMS enabled organization, run the new concurrent program Manage AQ message queues for WCS (short name WMSWCSAQ).
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|