UUT flow control in manufactiring

Hello colleagues,
I would like to implement a system to control the UUT flow in the manufacturing.
I think some companies call it CIM or PCS.
For know, what I need is to certify that no untested units will be shipped. In addition, I would like to certify that all units of part number "A" will be tested in the test stattions "A1", "A2", "A3", in this sequence.
My test programs are creating a local file with the UUT test result. I need upload it in a database and to control the product flow.
My company is small size, so we don't have a CIM team to implement this control system (database, UI for tracking queries etc).
Please tell me if you know some software that implement this functions. Is there some open source software what implements it?
Regards
Marcio

I'm not aware of any open source software but I've never really looked for any. It sounds like TestStand might suit your needs.
Using LabVIEW 2010SP1 and TestStand 4.5

Similar Messages

Console flow control

With no flow control on the console port, it's common to overrun the port when sending large config files from a terminal emulator. Is there any way to avoid this, other than manually breaking up the file and sending a chunk at a time, maybe by adjusting the console buffer size, if possible?

Michael
Most terminal emulator programs (like Hyperterm, or TeraTerm, or SecurCRT, etc) have a setting where you can specify character delay and or line delay. If you use these parameters to specify some delay you can send the config file (even very large configs) without over-running the console.
HTH
Rick

Want to know what exactly is flow control in odi

Hi Experts
I want to know what exactly is flow control in odi.can anybody explain with an example.i have created a simple interface ie using contol append km .in this both the tables are in one data server ie in different schemas.in this interface i have set the flow control as false.in what circumstances we will use this flow control.
Regards
sree

Hi Sree,
Couple of points u need to aware.
There are two ways of Constraint checking in ODI (PK, FK, Condition, NOT NULL etc) using CKM.
FLOW_CONTROL: If u enable this in ur IKM all the constraints checking will be done at I$ table (before target table loading).
STATIC_CONTROL: If u enable this in ur IKM all the constraints checking will be done at TARGET table (after target table loading). In this case u need to DISABLE the constraint first and once STATIC_CONTROL is done then u need to ENABLE it.
So all the violated/errored record will be moved to E$ table in both approach.
Makes sense?
Thanks,
Guru

Problems with parity and flow control using visa serial

I am trying to create a basic user interface with the options that my
company uses most often for a force indicator. You can configure
the indicator over serial, as well as read the values off the
indicator. I am trying to create the user interface so that using
producer/consumer loops with events, once you change a value, it will
write that new value to the serial port, ie the device.
The problem I am having is transfering the parity and flow control
values for the serial config to the Basic read write VI. The
problem is that once the consumer loop executes, it will write the
values correctly to the VI, but then the outer loop executes 200 ms
later and clears the values. I know that this is normal behavior
and that in order to keep the values stored, normally you would use a
shift register. I tried to use this and had some issues with
correct data types/array mis-mtaches, ets, so I created an indicator
and had a local vaible read the indicator, which seems to be working
for the stop bits, read bits, baud rate, etc, but not the parity anf
flow control. I always get "blank" outputs for theses values (if
you enable the digital display you can see that they are outputing the
value 0 which correspondes to None in both cases, which is
correct). Even though it appears that it is outputting the
correct value, I get an error that says the VISA property is
invalid. I initally did a search and found that my stop bit
control was wrong (outputting double instead of integer), but I could
not find anything on the parity/flow control issue. I even tried
to copy the serial config controls from the basic serial read/write to
my dialog box and that did not work either.
I would be grateful for any suggestions.
Thanks
Kenny
Kenny
Attachments:
BGI_main pandc.zip ‏232 KB

I should add that I am using LV 8.0 and that the serial config
indicator in the consumer loop will be off the frontpanel in the final
VI so that it is not visible to the user.
Kenny

How to implement autotuning pid in labview in flow control process????

I tried the same way as Example available in LabVIEW..... that is general auto PID simulator... But that didn't worked out for me.....

The 'General Auto PID Simulator.vi' example uses the technique "PID Relay" feedback where it tries to calculate the PID values based on the relay feedback, but using the PID also in the loop:
(http://zone.ni.com/reference/en-XX/help/370401H-01/lvpidmain/pidrelay_alg/)
This technique works, but it requires initial PID parameters that will make the relay setpoint stable and it is able to obtain the results you are expecting.
Now, for flow control, you can try the most classic techniques. Please use other shipping examples that start with "autotuning" and in special this:
C:\Program Files (x86)\National Instruments\LabVIEW 2013\examples\control\PID\Autotuning PID Online.vi
In this VI, you can choose other techniques like open-loop step response, closed-loop step response and the original 'relay feedback' where it doesn't have a PID inside the estimation loop.
Anyway, here you have more information about those techniques http://zone.ni.com/reference/en-XX/help/370401H-01/TOC4.htm.
One more thing: keep in mind that depending on the plant parameters, a PID could not be suited for your application and a more complex controller need to be developed.
Hope this can help you...
Barp - Control and Simulation Group - LabVIEW R&D - National Instruments

ORA-25307: Enqueue rate too high, flow control enabled

I am stuck. I have my stream setup and they were previously working on two of my dev environments well. Now when I get the streams setup the CAPTURE process has a state of "CAPTURING CHANGES" for like 10 seconds and then changes to state "PAUSED FOR FLOW CONTROL". I believe this is happening because the PROPAGATION process is showing an error of "ORA-25307: Enqueue rate too high, flow control enabled".
I don't know what to tweak to get rid of this error message. The two environments are dev databases and there is minimal activity on them so i don't think it's a case of the APPLY process is lagging behind the PROPAGATION process. Has anyone run into this issue?? I've verified my db link works, my stream admin user has dba access. Any help or advise would be greatly appreciated.
thanks, dave

As rule of thumb, you don't need to set GLOBAL_NAME=TRUE as long as your are 100% GLOBAL_NAME compliant.
So, setting GLOBAL_NAME=TRUE will not have any effect if your dblink is not global_name compliant
and if your installation is global_name compliant, you don't need to set GLOBAL_NAME=TRUE.
The first thing when you diagnose is to get the exact facts.
Please run this queries both on source and target so that to see what are in the queues and where.
Run it multiple time to see if figures evolves.
- If they are fixed, then your Streams is stuck in its last stage. As a cheap and good starting point, just stop/start the capture, propagation and target apply process. Check also the alert.log on both site. when you have a propagation problem, they do contains information's. If you have re-bounced everything and no improvement then the real diagnose work must start here but then we know that the message is wrong and the problems is elsewhere.
- if they are not fixed then your apply really lag behind for what ever good reason, but this is usually easy to find.
set termout off
col version new_value version noprint
col queue_table format A26 head 'Queue Table'
col queue_name format A32 head 'Queue Name'
select substr(version,1,instr(version,'.',1)-1) version from v$instance;
col mysql new_value mysql noprint
col primary_instance format 9999 head 'Prim|inst'
col secondary_instance format 9999 head 'Sec|inst'
col owner_instance format 99 head 'Own|inst'
COLUMN MEM_MSG HEADING 'Messages|in Memory' FORMAT 99999999
COLUMN SPILL_MSGS HEADING 'Messages|Spilled' FORMAT 99999999
COLUMN NUM_MSGS HEADING 'Total Messages|in Buffered Queue' FORMAT 99999999
set linesize 150
select case
when &version=9 then ' distinct a.QID, a.owner||''.''||a.name nam, a.queue_table,
              decode(a.queue_type,''NORMAL_QUEUE'',''NORMAL'', ''EXCEPTION_QUEUE'',''EXCEPTION'',a.queue_type) qt,
              trim(a.enqueue_enabled) enq, trim(a.dequeue_enabled) deq, x.bufqm_nmsg msg, b.recipients
              from dba_queues a , sys.v_$bufqm x, dba_queue_tables b
        where
               a.qid = x.bufqm_qid (+) and a.owner not like ''SYS%''
           and a.queue_table = b.queue_table (+)
           and a.name not like ''%_E'' '
   when &version=10 then ' a.owner||''.''|| a.name nam, a.queue_table,
              decode(a.queue_type,''NORMAL_QUEUE'',''NORMAL'', ''EXCEPTION_QUEUE'',''EXCEPTION'',a.queue_type) qt,
              trim(a.enqueue_enabled) enq, trim(a.dequeue_enabled) deq, (NUM_MSGS - SPILL_MSGS) MEM_MSG, spill_msgs, x.num_msgs msg,
              x.INST_ID owner_instance
              from dba_queues a , sys.gv_$buffered_queues x
        where
               a.qid = x.queue_id (+) and a.owner not in ( ''SYS'',''SYSTEM'',''WMSYS'') order by a.owner ,qt desc'
   end mysql
from dual
set termout on
select &mysql
/B. Polarski

Standard flow control

JSTL support for standard flow control.
what that means ?
I am aware of that JSTL can help in SQL processing , XML processing through Tag libraries.
But however, how the JSTL supports standard flow control ? is it the JSTL iterator we are talking about ?

Although you can apparently access a database on the JSP page using JSTL tags, it doesn't mean its a good idea. I suggest you use the MVC design. You separate the layers and not put database functionality in the presentation layer (JSP).
Hers is one MVC approach in which a single servlet acts as the control. There are other ways of doing it via Spring, Structs, etc. However, I suggest you master this approach before moving onto those.
presentation layer:
JSP, CSS, Javascript, and JSTL.
The JSP page and its supporting languages is responsible for displaying data and submitting user input back the controller. The Javascript is typically responsible for basic client side validation of user input. JSP gets its data that it is to display from request scope (and perhaps some from session scope). JSTL assists JSP in displaying data by doing such tasks as looping though a Java collection from the request scope and displaying it. The JSP page should not contain any logic from the other layers (below). The page will get complicated enough over time just displaying data without making it even more difficult to read by inserting business logic into it.
control layer:
A single servlet. This servlet takes in all url request and page submits coming from JSP pages. Avoid JSP to JSP page naviigation (there are exceptions to this rule). Go through the control layer. This servlet calls business logic to get data that the page requests. It puts it in request and/or session scope, and dispatches to the appropriate JSP page. Because all url request go through this servlet, the servlet can do centralized authentication (log in) and authorization (user assigned to a role). Dont generate presentation data (html) from this layer.
business layer:
Java classes that carry out requests from the control layer. It calls the database layer for raw data from the database and performs business logic on the data (if any) before sending it to the control layer.
database layer:
Takes in requests from the business layer. Queries the database via SQL. Is the only layer that has sql in it. Reads the resultSet from the database and puts the data in some kind of Java collection before returning it to the business layer. Never return the resultSet (a database concept) to the business layer.

Introduction of flow control and synchronization steps in Test Description

Hi ALL,
          I am working on developing of Test Scripts in ATML standards. Can any one inform me how to introduce flow control (if, else, end, for, while, break etc)  and synchronization (wait etc) steps into the Test scripts. Thanks in advance.
With Best Regards,
Kalyan

I had a similar issue in a project I am working on. I'm not sure if I did this the "Best Practices" way or not, but it works perfectly.
In the head area of my JSP I include the following:
<f:view>
    <h:outputText id="refresher1" rendered="#{queryHandler.queryRunning}">
        <f:verbatim escape="false">
            <meta http-equiv="refresh"
                  content="5,<%=response.encodeURL(request.getContextPath()+
                          "/queryStatus.jsf")%>">
        </f:verbatim>
    </h:outputText>
    <h:outputText id="refresher1" rendered="#{queryHandler.queryFinishedRunning}">
        <f:verbatim escape="false">
            <meta http-equiv="refresh"
                  content="5,<%=response.encodeURL(request.getContextPath()+
                          "/queryResults.jsf")%>">
        </f:verbatim>
    </h:outputText>This puts a 5 second refresh meta in the header to direct the browser to the correct page based on the status of the query thread.
There are many ways to accomplish the effect you want. I suggest putting all the controls into the JSP and making use of the rendered attributes instead of the JSTL conditionals to show the controls you want for the state of the application.
-jeffhoward

Paused for Flow Control but no flow occurring

10.2.0.2
Our destination database had problems this AM and it was bounced. The capture process on the source went into "Paused for Flow Control" status and never recovered. Here's the process I went through.
1. There was nothing being propagated according to v$propagation_sender.
2. The apply process was running but was not receiving any messages according to v$streams_apply_reader, v$streams_apply_server
3. I stopped and restarted the apply process - no change.
4. I stopped and restarted the capture process and after the dictionary initilization it went back into the paused state.
5. alter logs showed nothing for either database.
6. dbms_propagation_adm.stop_propagation resulted in an ORA-24082
I finally had to run dbms_propagation_adm.stop_propagation with force=>true and restart it for data to start flowing again, albeit slowly.
So the question is - why? Why did I have to forcefully stop the propagation process and restart it when this is all supposed to be seamless? Is this expected behavior that others have run into and the proces you need to perform whenever your destination becomes unavailable for a time period?
Just curious.
Thanks - Brian

I've tried setting up a Streams for schema replication and have run into the "Paused for Flow Control issue". I'm not getting any streams errors so i don't know what's wrong with it.
I'm not that familiar with Streams so i'm not sure where to start to diagnose the problem. I used the Enterprise Manager to set up the streams and tried stopping and restarting the capture process but i'm still getting the "Paused for Flow Control issue". Where is the best place to start to look for a solution?
Thanks!

Message Flow Control

Hello,
          as I read, WLS provides the possibility to slow down message producers when certain paging thresholds are exceeded. I'm not quite sure, if the slow down of a producer is tied to it's session lifecycle, i.e. if the producer is slowed down only within its current session - or are producers, which are created from a new session, also slowed down right from the start.
          It would be great if someone could answer that. Unfortunately I have found nothing about that in the documentation.
          Regards,
          Dirk

Hello Tom.
          First of all, thank you for your quick response. This forum is really working!
          I searched for this topic in the documentation, but didn't find anything appropriate explaining the in-depth details of the JMS flow control mechanism. Therefore, I wrote a simple test case (implementation and server configuration is attached at the end of this message) to check the flow control handling for certain conditions. Since there is no API to access the flow control properties of a message producer, I measured the JMS throughput within the test case and tried to derive some conclusions.
          Regarding the server configuration:
          - I configured one JMS Server (Test_JMSServer) with one Queue (TestQueue). I enabled the message paging at server level, starting at 1000 messages (i.e. message threshold high). The lower message threshold was set to 100 messages. As a paging store a file store (TestPagingStore) was used.
          - Message thresholds at destination level was disabled.
          - I further configured a connection factory (TestConnectionFactory) for which I enabled the flow control with a max. throughput of 50 msg/sec and a min. throughput of 1 msg/sec. The flow interval was set to 60 seconds, the number of steps was set to 6.
          Regarding the test case:
          There are 3 scenarios within the test case. Within each scenario
          - first all messages are consumed from the queue,
          - then 1000 messages are send to the queue in a row, thereby measuring the throughput,
          - finally again 1000 messages are send to the queue in a row, thereby measuring the throughput.
          The scenarios differ in how the bulk-send operation is performed.
          - The first scenario (test_noReuse) creates a new connection for each message to be send.
          - The second scenario (test_sessionReuse) creates a new session at the start and reuses that session for sending the messages. A new sender is created of each message.
          - The third scenario (test_senderReuse) creates a new sender at the start and reuses that sender for sending the messages.
          Here are the results of the test:
          ==[test_noReuse]=======================
          Cleaned up <2000> messages.
          Throughput (messages/second): 51 [startMillis=1161249409788;endMillis=1161249429210;messagesSend=1000]
          Throughput (messages/second): 62 [startMillis=1161249429210;endMillis=1161249445304;messagesSend=1000]
          ==[test_sessionReuse]=======================
          Cleaned up <2000> messages.
          Throughput (messages/second): 231 [startMillis=1161249452773;endMillis=1161249457101;messagesSend=1000]
          Throughput (messages/second): 245 [startMillis=1161249457101;endMillis=1161249461179;messagesSend=1000]
          ==[test_senderReuse]=======================
          Cleaned up <2000> messages.
          Throughput (messages/second): 790 [startMillis=1161249467351;endMillis=1161249468616;messagesSend=1000]
          Throughput (messages/second): 1 [startMillis=1161249468616;endMillis=1161249999226;messagesSend=1000]
          To me it seems, that reusing a session has no effect on the message flow control if a new sender is created for sending a message. The only scenario where a throttling occurs (at least it seems to be that way) is the last scenario, where the sender is reused for all messages.
          So my conclusion is, that message control flow is superfluous to configure, as long as
          - you don't have a small amount of (batch) message producers, each of which reusing a single sender for each message,
          - or you have some cache of senders (or a single sender) in your application and reuse the cached senders for sending messages.
          The latter is, of course, strongly discouraged, since neither JMS sessions, nor senders are thread-safe. So you need to implement some thread-safe cache and also have to deal with re-creating stalled JMS resources within that cache -- a really non-trivial implementation. Further, if many different threads produce messages, the flow control has no (or at least few) effect on the message load in the server.
          I just ask myself, what the flow control was designed for, since the cases where it really applies are rather rare, IMHO. Or have I made some error in the test or in the server configuration?
          Best regards,
          Dirk
          The test class:
          <pre>
          import java.util.Hashtable;
          import javax.jms.BytesMessage;
          import javax.jms.JMSException;
          import javax.jms.Message;
          import javax.jms.Queue;
          import javax.jms.QueueConnection;
          import javax.jms.QueueConnectionFactory;
          import javax.jms.QueueReceiver;
          import javax.jms.QueueSender;
          import javax.jms.QueueSession;
          import javax.jms.Session;
          import javax.naming.InitialContext;
          import junit.framework.TestCase;
          public class JMSFlowControlTest extends TestCase {
          private int messagesThresholdHigh = 1000;
          private QueueConnectionFactory conFactory;
          private Queue queue = null;
          protected void setUp() throws Exception {
          super.setUp();
          InitialContext ctx = null;
          Hashtable ctxEnv = null;
          ctxEnv = new Hashtable();
          ctxEnv.put(
          InitialContext.INITIAL_CONTEXT_FACTORY,
          "weblogic.jndi.WLInitialContextFactory");
          ctxEnv.put(
          InitialContext.PROVIDER_URL,
          "t3://localhost:7001");
          ctx = new InitialContext(ctxEnv);
          this.queue = (Queue) ctx.lookup("jms/queue/TestQueue");
          this.conFactory = (QueueConnectionFactory)
          ctx.lookup("jms/factory/TestConnectionFactory");
          public void test_noReuse() throws Exception {
          System.out.println();
          System.out.println("==[" + this.getName() + "]=======================");
          this.cleanupQueue();
          System.out.println(
          this.bulkSendMessage(
          this.messagesThresholdHigh,
          1024));
          System.out.println(
          this.bulkSendMessage(
          this.messagesThresholdHigh,
          1024));
          public void test_sessionReuse() throws Exception {
          QueueConnection con = null;
          QueueSession session = null;
          System.out.println();
          System.out.println("==[" + this.getName() + "]=======================");
          try {
          con = this.conFactory.createQueueConnection();
          session =
          con.createQueueSession(false, QueueSession.AUTO_ACKNOWLEDGE);
          this.cleanupQueue();
          System.out.println(
          this.bulkSendMessage(
          session,
          this.messagesThresholdHigh,
          1024));
          System.out.println(
          this.bulkSendMessage(
          session,
          this.messagesThresholdHigh,
          1024));
          } finally {
          if (con != null) {
          try {
          con.close();
          } catch (JMSException e) {}
          public void test_senderReuse() throws Exception {
          QueueConnection con = null;
          QueueSession session = null;
          QueueSender sender = null;
          System.out.println();
          System.out.println("==[" + this.getName() + "]=======================");
          try {
          con = this.conFactory.createQueueConnection();
          session =
          con.createQueueSession(false, QueueSession.AUTO_ACKNOWLEDGE);
          sender = session.createSender(this.queue);
          this.cleanupQueue();
          System.out.println(
          this.bulkSendMessage(
          session,
          sender,
          this.messagesThresholdHigh,
          1024));
          System.out.println(
          this.bulkSendMessage(
          session,
          sender,
          this.messagesThresholdHigh,
          1024));
          } finally {
          if (con != null) {
          try {
          con.close();
          } catch (JMSException e) {}
          private Throughput
          bulkSendMessage(
          int messagesToSend,
          int messageSizeBytes)
          throws Exception {
          int messagesSend = 0;
          long startMillis = 0L;
          long endMillis = 0L;
          QueueConnection con = null;
          QueueSession session = null;
          QueueSender sender = null;
          startMillis = System.currentTimeMillis();
          for (int i = 0; i < messagesToSend; i++) {
          try {
          con = this.conFactory.createQueueConnection();
          session =
          con.createQueueSession(false, QueueSession.AUTO_ACKNOWLEDGE);
          sender = session.createSender(this.queue);
          sender.send(this.createMessage(session, messageSizeBytes));
          messagesSend++;
          } finally {
          if (con != null) {
          try {
          con.close();
          } catch (JMSException e) {}
          endMillis = System.currentTimeMillis();
          return new Throughput(startMillis, endMillis, messagesSend);
          private Throughput
          bulkSendMessage(
          QueueSession session,
          int messagesToSend,
          int messageSizeBytes)
          throws Exception {
          int messagesSend = 0;
          long startMillis = 0L;
          long endMillis = 0L;
          QueueSender sender = null;
          startMillis = System.currentTimeMillis();
          for (int i = 0; i < messagesToSend; i++) {
          sender = session.createSender(this.queue);
          sender.send(this.createMessage(session, messageSizeBytes));
          messagesSend++;
          endMillis = System.currentTimeMillis();
          return new Throughput(startMillis, endMillis, messagesSend);
          private Throughput
          bulkSendMessage(
          QueueSession session,
          QueueSender sender,
          int messagesToSend,
          int messageSizeBytes)
          throws Exception {
          int messagesSend = 0;
          long startMillis = 0L;
          long endMillis = 0L;
          startMillis = System.currentTimeMillis();
          for (int i = 0; i < messagesToSend; i++) {
          sender.send(this.createMessage(session, messageSizeBytes));
          messagesSend++;
          endMillis = System.currentTimeMillis();
          return new Throughput(startMillis, endMillis, messagesSend);
          private Message
          createMessage(
          Session session,
          int messageSizeBytes)
          throws Exception {
          BytesMessage message = null;
          message = session.createBytesMessage();
          message.writeBytes(new byte[messageSizeBytes]);
          return message;
          private void cleanupQueue() throws Exception {
          QueueConnection con = null;
          QueueSession session = null;
          QueueReceiver receiver = null;
          Message message = null;
          int messageCount = 0;
          try {
          con = this.conFactory.createQueueConnection();
          session =
          con.createQueueSession(false, QueueSession.AUTO_ACKNOWLEDGE);
          receiver = session.createReceiver(this.queue);
          con.start();
          do {
          message = null;
          message = receiver.receiveNoWait();
          if (message != null) {
          messageCount++;
          } while (message != null);
          } finally {
          if (con != null) {
          try {
          con.close();
          } catch (JMSException e) {}
          System.out.println("Cleaned up <" + messageCount + "> messages.");
          private static final class Throughput {
          private final long startMillis;
          private final long endMillis;
          private final int messagesSend;
          public Throughput(long startMillis, long endMillis, int messagesSend) {
          this.startMillis = startMillis;
          this.endMillis = endMillis;
          this.messagesSend = messagesSend;
          public int value() {
          long timeElapsedMillis = 0L;
          int timeElapsedSeconds = 0;
          int value = 0;
          timeElapsedMillis = this.endMillis - this.startMillis;
          if (timeElapsedMillis == 0) {
          timeElapsedMillis = 1;
          value = (int) ((this.messagesSend * 1000L) / timeElapsedMillis);
          return value;
          public String toString() {
          StringBuffer buffer = new StringBuffer();
          buffer
          .append("Throughput (messages/second): ").append(this.value())
          .append(" [startMillis=").append(this.startMillis)
          .append(";endMillis=").append(this.endMillis)
          .append(";messagesSend=").append(this.messagesSend)
          .append("]");
          return buffer.toString();
          </pre>
          The (partial) server configuration:
          <pre>
          <JMSConnectionFactory
          DefaultDeliveryMode="Non-Persistent"
          FlowMaximum="50"
          FlowMinimum="1"
          FlowSteps="6"
          JNDIName="jms/factory/TestConnectionFactory"
          Name="TestConnection Factory"
          Targets="SchufaDev"
          XAConnectionFactoryEnabled="true"/>
          <JMSFileStore Directory="filestore/paging" Name="TestPagingStore"/>
          <JMSServer
          MessagesPagingEnabled="true"
          MessagesThresholdHigh="1000"
          MessagesThresholdLow="100"
          Name="Test_JMSServer"
          PagingStore="TestPagingStore"
          Targets="SchufaDev">
          <JMSQueue
          CreationTime="1151395702234"
          JNDIName="jms/queue/TestQueue"
          JNDINameReplicated="false"
          Name="TestQueue"
          RedeliveryDelayOverride="5000"
          RedeliveryLimit="5"
          StoreEnabled="false"/>
          </JMSServer>
          </pre>

Odi error : Flow control not possible if no key is declared in your target

Hi ...
I have a requirement where I am trying to populate a view(the view some has some pl/sql package running behind the scenes to populate the appropriate tables) on database (oracle11g) using the odi interface.
We are expcetd to populate the view only.
I am encountering this error when i try to run the interface (Flow control not possible if no key is declared in your target datasource).
The view doesnt have any key & I cannot change the key structure of the view.
Is their any workaround for this in the ODI.

If you don't have any keys on your table, Flow Control will not be possible as the step of flag rows for update. You must have a key defined in your table to use both resources of ODI.
I recommend you to disable the FLOW_CONTROL option in your IKM and if you need to update your table, you'll have a problem. If you don't have, just disable the Update option also and go ahead with the execution.
TIP: Do not forget of set keys on your temporary tables when uses the IKM of Incremental Update.
Best regards.
Luiz Araujo (A.K.A. Buchu)

Increase of priority flow control counters in a FCoE environment

Hi,
I need some input about what is normal in a FCoE environment in regards to priority flow contol counters.
I see Increase of RxPPP and TxPPP counters on a FCoE end to end enviroment. however we don't see high traffic rates to/from storage array(<1Gbps). Customer have not reported low transfer from storage.
Setup:
CNA hosts - FEX2232 - N5K - EMC-VNX
FCoE end-to-end, No native FibreChannel.
CNA adapters = Emulex.
Is a problem I should look further into or is it normal?
I have read the troubleshooting guide.
http://www.cisco.com/en/US/partner/docs/switches/datacenter/nexus5000/sw/troubleshooting/guide/n5K_ts_fcoe.html
some output:
N5K-2# sh inter priority-flow-control
============================================================
Port               Mode Oper(VL bmap) RxPPP      TxPPP
============================================================
FEX101-2232 1-8
Ethernet1/1        Auto Off           0          211994
Ethernet1/2        Auto Off           0          0
Ethernet1/3        Auto Off           2891830    0
Ethernet1/4        Auto Off           6269410    0
Ethernet1/5        Auto Off           12109662   0
Ethernet1/6        Auto Off           79534      0
Ethernet1/7        Auto Off           0          0
Ethernet1/8        Auto Off           0          0
FEX102-2232 9-16
Ethernet1/9        Auto Off           0          9994780
Ethernet1/10       Auto Off           0          0
Ethernet1/11       Auto Off           24678      0
Ethernet1/12       Auto Off           0          0
Ethernet1/13       Auto Off           4316       0
Ethernet1/14       Auto Off           136        0
Ethernet1/15       Auto Off           0          0
Ethernet1/16       Auto Off           0          0
!VNX-FCOE-ATTACHED SP_A
Ethernet1/19       Auto On (8)       1888566    10100200
!VNX-FCOE-ATTACHED SP_A
Ethernet1/20       Auto On (8)       10414603   1367098
Ethernet1/23       Auto Off           0          0
Ethernet1/24       Auto Off           0          0
Ethernet1/25       Auto Off           0          0
Ethernet1/26       Auto Off           0          0
Ethernet1/27       Auto Off           0          0
Ethernet1/28       Auto Off           0          0
Ethernet1/30       Auto Off           0          0
Ethernet1/32       Auto On (8)       0          0
Ethernet1/38       Auto Off           0          0
Ethernet1/39       Auto Off           0          0
Ethernet1/40       Auto Off           0          0
Ethernet1/41       Auto On (8)       0          0
Ethernet1/42       Auto On (8)       0          0
Ethernet1/43       Auto On (8)       0          0
Ethernet1/44       Auto On (8)       0          0
!CNA atttached hosts.
Ethernet101/1/1    Auto On (8)       37109      33155
Ethernet101/1/2    Auto On (8)       120        32336
Ethernet101/1/3    Auto On (8)       274        34404
Ethernet101/1/4    Auto On (8)       1924       64754
Ethernet101/1/5    Auto On (8)       144        14684
Ethernet101/1/24   Auto On (8)       4296788    4466
Ethernet101/1/25   Auto On (8)       104520     22
Ethernet101/1/26   Auto On (8)       838        30824
Ethernet101/1/27   Auto On (8)       796        7770
Ethernet101/1/28   Auto On (8)       13749152   1684
Ethernet101/1/29   Auto On (8)       5912918    1276
Ethernet101/1/30   Auto On (8)       3296026    2292
Ethernet101/1/31   Auto On (8)       0          80
Ethernet101/1/32   Auto On (8)       0          0
Ethernet102/1/1    Auto On (8)       75656      323512
Ethernet102/1/2    Auto On (8)       0          5632
Ethernet102/1/3    Auto On (8)       4278       173828
Ethernet102/1/4    Auto On (8)       0          0
Ethernet102/1/28   Auto On (8)       2872       300046
Ethernet102/1/29   Auto On (8)       28216      11808124
Ethernet102/1/30   Auto On (8)       4792       441340
Ethernet102/1/31   Auto On (8)       0          0
Ethernet102/1/32   Auto On (8)       1040       201214
Ethernet1/19       Auto On (8)       1888566    10100200
Ethernet1/20       Auto On (8)       10414603   1367098
Just a one of the servers
GDC-CORE-SW04# sh inter e101/1/29 priority-flow-control
============================================================
Port               Mode Oper(VL bmap) RxPPP      TxPPP
============================================================
Ethernet101/1/29   Auto On (8)       5912932    1276
GDC-CORE-SW04# sh inter e101/1/29 | in pause
    0 Rx pause
    0 Tx pause
GDC-CORE-SW04# sh inter e101/1/29 priority-flow-control
============================================================
Port               Mode Oper(VL bmap) RxPPP      TxPPP
============================================================
Ethernet101/1/29   Auto On (8)       5913378    1276
GDC-CORE-SW04#
GDC-CORE-SW04# sh inter e101/1/29 | in pause
    0 Rx pause
    0 Tx pause
VNX
GDC-CORE-SW04# sh inter priority-flow-control | in Ethernet1/19 ne 1
Ethernet1/19       Auto On (8)       1889064    10100536
Ethernet1/20       Auto On (8)       10414603   1367164
GDC-CORE-SW04# sh inter e1/19 | in "input rate"
30 seconds input rate 133346744 bits/sec, 16668343 bytes/sec, 10762 packets/sec
    input rate 96.22 Mbps, 8.31 Kpps; output rate 118.68 Mbps, 8.83 Kpps
GDC-CORE-SW04# sh inter e1/20 | in "input rate"
30 seconds input rate 36024752 bits/sec, 4503094 bytes/sec, 2342 packets/sec
    input rate 33.96 Mbps, 2.09 Kpps; output rate 24.95 Mbps, 1.50 Kpps

Hi, thank your for your answer.
I actually already enabled the system qos manually since we run 5.0(2)N2 release.
We will implement FCoE over 5500. What I'm worried about is the warning message I posted above on Nexus 7009s connected to my 5500s after I enabled the system qos.
Could it be originated by the DCBX feature? May I have some problem if 'Priority-flow-control' setting between N5k and N7k don't match?

" Flow control: Entry SAPMV45B, PSTC, P1, * , * , * is missing in T185"

Hi all,
I have an order with 5 line items, and all are from same plant. When i try to change some thing for line item 5 system is saying that " No status object is missing for SDI xxxxx/50, where as xxxxx is a sales order number and 50 is line item.
Then again i click on object status on item level status tab, it is giving a message that " Flow control: Entry SAPMV45B, PSTC, P1, * , * , * is missing in T185".
What i have missed here?
item category for all the items is same, and are of same material types. But this message i am getting only for 5 line item.
Any help is appreciated.
Venkat Cheedlla

Hi,
SAP suggested to run the program SDSTATU2 program.
But i did not got a chance to check it.
Venkat

Debugging - Process flow control

Hi All,
I am doing initial load for one condition object(R3AS), and when I check SMW01 I am getting BDoc validation Error.
I want to debug the BDoc flow context i.e MI0(validation function module) where Bdoc posting is failing.
I followed OSS note- 432661- Debugging and process support of flow control: Enhancement
Here is the Note:
Symptom
Error analysis requires debugging flow control services.
Other terms
SMW01, Flow Control, BDOC, BDoc, BDoc Message, Flow Service, Update task, qRFC step, asynchronous step
Reason and Prerequisites
Error analysis requires debugging flow control services.
Solution
This feature is available with CRM 3.0 starting SP04 and higher releases.
Usage:
     The flow header structure SMW3_FHD is extended to hold a flag indicating debug mode. To debug, set this flag before calling CL_SMW_MFLOW=> PROCESS_OUTBOUND (Parameter IN_HEADER, Field DBGMODE), PROCESS_NOTIFICATION (Parameter HEADER, Field DBGMODE) or PROCESS_NOTIFICATION_MULT (Parameter HEADER, Field DBGMODE). If update task and/or asynchronous tRFC/qRFC step is done, the message is not written into a qRFC queue or tRFC. Instead the message get's a new state 'D01': To be processed (Debug).
The message processing can then be continued from transaction SMW01.
     Select messages in state D01 possibly with bdoc type, send date, creation time, and user.
     In the list display check the message check box that you want to debug.
     Choose function Retry to process.
The message will be processed by flow service function modules in the order shown in transaction SMO8FD. Processing occurs directly. Therefore all active breakpoints can be used to stop processing for further analysis.
I set HEADER-DBGMODE = X, and passed this structure to CL_SMW_MFLOW=> PROCESS_OUTBOUND
But none of the message is set to D01. Anyone have idea where I am missing?
I basically want to debug this validation function module while Bdoc comes in CRM, Any other way other than this OSS note..?
Thanks,
Vijay Raheja

what the description of the error?
Give details. Just by saying bdoc validation error does not nelp.
Click on the error details icon and see wat it says.
let us know then only can we help
Julius

Reg: UTA ports FCoE, 10GbE flow control settings

Could someone shed some light on the flow control settings for UTA ports, below is the scenario.I am working on the configutation of 4 node 3220 custer. We are using this 4 node cluster for FC and NFS traffic. each UTA port on the node used to serve both FcoE and NFS traffic( UTA port logically acting as FC and 10GbE ports) . However, the flow control is set to FULL on the 10GbE logical port to serve the NFS traffic. I think this flow control settings at 10GbE logical port level doesn't effect the FC traffic flow of the UTA port. the flow control settings would be effective on 10GE logical ports only.. Please confirm this... NetApp recommend to set the flow control to NONE and upper layer protocalls can take care of flow control( as per Best practise). If I want to change the flow control setting of 10GbE logical port, does it effect the data flow of logical FC0E port aswell?Now the actual issues is we are using the controllers mostly to serve FC trafic and we are experienceing Performance issues on all the nodes. current ONTAP version on the controller is 8.2p5we are hitting the latency of 50-80ms, I am trying to track the IO on the controllers, IO is not really high when we had the performace issues, But some times disk utilizations and cpu utlization hitting 80%. Performace manager doesn't have the granularity at aggregate level to track what LUN/volumes are casuing the high utlization at aggregate level..I am using the coomands sysstat -M, sysstat -x, netstat , statit commands mainly. However, I am not sure on any other internal porcesses are causing the high disk uitlizations...Please share your ideas on this..Oh.. another point this.. These controllers are flexpod config.....

Hi,We haven't worked on flow control settings.. you mean you are able to Disable the flow control on CNA cards?We have upgraded these filers to 8.2.3P3. at the moment filers are working fine, no performance issues.. However I wanted to disable the flow control on these ports, if possble. But NetApp docs tell that we cann't disable the flow control on the CNA cards. https://library.netapp.com/ecmdocs/ECMP1368834/html/GUID-31241255-4914-46FF-BDB5-A02DCCEABCCA.html Regards,Chandra

UUT flow control in manufactir​ing

Similar Messages

Maybe you are looking for

UUT flow control in manufactiring