MCB2300 compilation warnings

Hello, my ARMS 1.0 eval with LV 8.5.1 and uVision v3.80. I use the MCB2300 eval Board and I tested the Board and tools with examples of uVision. I can't throw Blinky of LabVIEW however. I get the following warning:

which connects...
.\Obj\LabVIEW.SCT(15): WARNING: L6314W: no section corresponds to LPC23_EMAC.o (ZI) pattern.
.\Obj\LabVIEW.SCT(15): WARNING: L6314W: no section will match pattern LPC23_EMAC.o (RW).
Program size: Code = 47600 RO-data = RW-data = 1000 ZI-data = 24056 9304
«.\Obj\LabVIEW.axf' - 0 error (s), 2 warning (s).

Then the build fails. When I try to find the problem in uVision I'm pointing to line 15 of this file:

; *************************************************************
; Description file generated by uVision XY-loading point clouds *.
; *************************************************************

LR_IROM1 0x00000000 0 x 00080000 {; load region size_region
ER_IROM1 0x00000000 0 x 00080000 {; load address = address of delivery}
*.o (RESET, + Prime)
*(InRoot$$sections)
. NO (+ RO)
}
0X40000000 RW_IRAM1 0 X 00008000 {;} The RW data
. NO (+ RW ZI)
}
RW_RAM1 0X7FE00000 {0 X 00004000}
LPC23_EMAC.o (+ ZI + RW)
}
RW_IRAM2 0X7FD00000 {0 X 00002000}
. NO (+ RW ZI)
}
}

Any thoughts?

Richard


Tags: NI Products

Similar Questions

  • Compilation warnings TestStand ActiveX controls in WPF 2012

    Hi all

    I use the TestStand (ApplicationMgr, SequenceMgr, ExcutionMgr) ActiveX controls in my project written in WPF 2012.

    After that I put the controls on the form, there are a few referrences automatically included in my project. But when I compile, I had the following warnings in the output window:

    CSC: warning CS1762: a reference has been made to the embedded PIA 'c:\Windows\assembly\GAC_MSIL\NationalInstruments.TestStand.Interop.UI\5.1.0.226__ad9244eb3b825cd8\NationalInstruments.TestStand.Interop.UI.dll' because of an indirect reference to that assembly established by the Assembly "c:\Program Files (x 86) \National Instruments\TestStand 2013\API\DotNet\Assemblies\CurrentVersion\NationalInstruments.TestStand.Interop.UI.AxControls.dll". You want to change the property "Include the Interop Types" or another Assembly.
    CSC: warning CS1762: a reference has been made to the embedded PIA 'c:\Windows\assembly\GAC_MSIL\NationalInstruments.TestStand.Interop.UI.Support\5.1.0.226__ad9244eb3b825cd8\NationalInstruments.TestStand.Interop.UI.Support.dll' because of an indirect reference to that assembly established by the Assembly "c:\Program Files (x 86) \National Instruments\TestStand 2013\API\DotNet\Assemblies\CurrentVersion\NationalInstruments.TestStand.Interop.UI.AxControls.dll". You want to change the property "Include the Interop Types" or another Assembly.
    CSC: warning CS1762: a reference has been made to the embedded PIA 'c:\Windows\assembly\GAC_MSIL\NationalInstruments.TestStand.Interop.API\5.1.0.226__ad9244eb3b825cd8\NationalInstruments.TestStand.Interop.API.dll' because of an indirect reference to that assembly established by the Assembly "c:\Program Files (x 86) \National Instruments\TestStand 2013\API\DotNet\Assemblies\CurrentVersion\NationalInstruments.TestStand.Interop.UI.AxControls.dll". You want to change the property "Include the Interop Types" or another Assembly.
    CSC: warning CS1762: a reference has been made to the embedded PIA 'c:\Windows\assembly\GAC\stdole\7.0.3300.0__b03f5f7f11d50a3a\stdole.dll' because of an indirect reference to that assembly established by the Assembly "c:\Program Files (x 86) \National Instruments\TestStand 2013\API\DotNet\Assemblies\CurrentVersion\NationalInstruments.TestStand.Interop.UI.AxControls.dll". You want to change the property "Include the Interop Types" or another Assembly.

    When I change the property "Include the Interop Types", I rather the errors. Can anyone give some advice? What does the warning message? How do I get rid of the warnings or do I just ignore them?

    Thank you very much!

    Kind regards

    According to the text in the warnings, it looks like you had always incorporate true on some of the meetings.

    Try changing all those in warnings to not stir, and then the warnings will probably disappear.

    -Doug

  • How unserializing soft types without compilation warnings

    I'm trying to serialize a Hashset < Type > and Arraylist < type >. Can I use data streams. WriteObject to serialize the OK.

    And water courses. ReadObject reads the object OK. But I get a warning that complie-time
    setmoveList = (ArrayList<Move>) (is.readObject());
    has a casting uncontrolled.

    If I replace the code with
    Object o= is.readObject();
    if (o instanceof ArrayList<Move>) {
      SetMoveList=  (ArrayList<Move>) o
    }
    I get a compilation error "type of generic instanceof non-compliant".

    Of course, I cannot live with the warnings, but is there a way to produce clean code that checks the type correctly?

    Published by: ptoye on May 7, 2013 02:51

    Your quest to write clean code is commendable, but it is quite subject to personal taste. For example: I find code that has delete annotations of warning this topic clean enough, others will ridicule me for her. What do you think?

    is there a way to produce clean code that checks the type correctly?

    The reason about this for a moment: can you check the correct type at compile time? readObject() is totally a matter of execution.

  • Can not get rid of compilation warnings, after that that they have been resolved. Ahhh

    I started to migrate to Flex 4 and have solved all my problems of compilation, but the compiler shows still 10 warnings, still

    Description


    "DropShadowVisible' style is only supported by the type"mx.controls.List"with the themes"spark. " line 487

    I did a complete search of the code and it is there no reference to dropShadowVisible anywhere.

    Does anyone have an idea how I can get rid of these? I tried

    The clean-up project

    recording in the form of archive and reconstruction.

    Looks like this: http://bugs.adobe.com/jira/browse/SDK-25720

    You use a mx:List and Halo theme by chance?

    Peter

  • duplicate the compiler warnings?

    I have a small question in Flex Builder 3 using Eclipse. Whenever I save my project, it is not up-to-date warnings from the compiler generated, leaving old and sometimes double job with warnings in the tab "Problems." Even when the problem is resolved. In some cases that there the same warning applied 4 or 5 times and I can't delete it.

    Any ideas?

    Use "Clean... the project" more frequently

  • Developer SQL not display warnings from the compiler

    I just test the new compiler in 11g warning message related to the exception handler so that "others" when there is a subsequent increase or raise_application_error.

    in SQL Plus, it works fine:

    SQL> alter session set plsql_warnings='enable:all';
    
    Session altered.
    
    SQL>
    SQL> create or replace function do_stuff
      2  return number
      3  as
      4     v_return number;
      5  begin
      6
      7     v_return := 3;
      8     return v_return;
      9
     10  exception
     11  when others then
     12     return null;
     13  end;
     14  /
    
    SP2-0806: Function created with compilation warnings
    
    SQL> show errors;
    Errors for FUNCTION DO_STUFF:
    
    LINE/COL ERROR
    -------- -----------------------------------------------------------------
    1/1      PLW-05018: unit DO_STUFF omitted optional AUTHID clause; default
             value DEFINER used
    
    11/6     PLW-06009: procedure "DO_STUFF" OTHERS handler does not end in
             RAISE or RAISE_APPLICATION_ERROR
    but Developer SQL, the output is:
    BANNER                                                                           
    -------------------------------------------------------------------------------- 
    Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production     
    PL/SQL Release 11.2.0.3.0 - Production                                           
    CORE     11.2.0.3.0     Production                                                         
    TNS for Linux: Version 11.2.0.3.0 - Production                                   
    NLSRTL Version 11.2.0.3.0 - Production                                           
    
    session SET altered.
    FUNCTION do_stuff compiled
    No Errors.
    Someone at - there experience this problem? is there a setting that makes Developer SQL behave differently?

    There is a bug.

    The solution is to make sure that the name of the object in CREATE or REPLACE is uppercase

    So in your example make DO_STUFF

    Run as a Script

    Then check the compiler Log/Logging Panel, you will see your mistakes.

    It has been marked to be fixed in our next release.

  • Warnings of compilation of a stored procedure in NDS (immediate execution);

    CREATE OR REPLACE PROCEDURE P_PRO1 AS
    P_VAR VARCHAR2 (1000): =' CREATE OR REPLACE PROCEDURE PROC1 AS
    X CONSTANT BOOLEAN: = TRUE;
    BEGIN
    IF X THEN
    DBMS_OUTPUT. PUT_LINE('||)
    Q'! 'REAL'!'
    *||'); *
    ON THE OTHER
    DBMS_OUTPUT. PUT_LINE('||)
    Q'! 'FALSE'!'
    *||'); *
    END IF;
    END;';
    BEGIN
    RUN IMMEDIATELY P_VAR;
    END;

    ALTER SESSION SET PLSQL_WARNINGS = ' ENABLE: ALL ';

    Set serveroutput on
    EXECUTE P_PRO1; -(No warning messages)




    I don't have any compilation warnings by running the above query. In fact, the procedure PROC1, which is compiled by "Execute Immediate" should produce the bcz of warning messages all types of warnings are ENABLED through Alter session, but there are no warnings when running the main proceedings and no log of warnings in the table of user_errors also. Whence the PROC1 warning went?

    NDS would only know to run the query given at runtime,
    then the PROC1 procedure is compiled at runtime in the main proceedings P_PRO1 will produce warning or not?
    If so, den how to check that the warning message?


    Thanks for the reply,
    Shafir.

    You create dynimically then you are the person who needs to print the WARNING.

    You can do this by querying the table ALL_ERRORS

    select *
      from all_errors
     where name = 'PROC1'
       and type = 'PROCEDURE'
    
  • compiler options

    Hello

    is it possible to customize the compiler options? Knowledge, I would disable all compiler warnings. I can't find a way to do it.

    Thanks for help.

    You can use "-w" option for qcc

    See

    https://developer.BlackBerry.com/native/reference/com.QNX.doc.neutrino.Utilities/topic/q/Qcc.html

    If it is a project of cascades c ++, you directly change the "warn_on" to be "warn_off" for the CONFIG in the QT project file.

    for example

    change

    CONFIG += qt warn_on debug_and_release waterfalls

    to be

    CONFIG += qt warn_off debug_and_release waterfalls

  • Conditional compilation: "If the $$id cannot be set to a value, then the PLW-6003 warning message is reported.

    Hello

    So according to the documentation:

    Conditional Directives of Compilation using survey

    The directive of inquiry is used to check the compilation environment. The directive of inquiry is of the form:

    inquiry_directive ::= $$id

    A directive of inquiry can be preset as described in 'predefined help investigation with Conditional Compilation Directives' or be defined by the user. The following describes the order of the processing flow during conditional compilation is trying to solve a directive of inquiry:

    1. The id is used as a guideline for investigation in the form $$ id for the search key.
    2. Re-encoding algorithm is as follows: the string in the PLSQL_CCFLAGS initialization parameter is scanned from right to left, the search with id for a matching name (case sensitive); if it's recognized. The predefined survey guidelines are sought after; Done if found.
    3. Si le $$ id cannot be resolved to a value, then the PLW-6003 warning message is sent if the original text is not wrapped. The literal NULL is substituted as the value for undefined investigation guidelines. Note that if the PL/SQL code is wrapped, then the warning message is disabled so that the directive of inquiry not defined is not revealed.

    I take this means, if you $IF $$xxx.00 = $5 THEN... $END but have not set a $$xxx.00 with "alter session set plsql_ccflags" then you should expect an error.

    But I am unable to make this trigger, a warning, or an error, either by

    ALTER session set plsql_warnings = ' error: 06003. "

    or

    ALTER session set plsql_warnings = ' enable: all ';

    test configuration:

    SCOTT@ORCL> alter session set plsql_ccflags = '';
    Session altered.
    SCOTT@ORCL> alter session set plsql_warnings = 'enable:all', 'error:06003';
    Session altered.
    BEGIN
        $IF $$DEBUGON $THEN
            dbms_output.put_line('debug is on');
        $ELSIF NOT $$DEBUGON $THEN
            dbms_output.put_line('debug is NOT on');
        $ELSE
            dbms_output.put_line('debug is neither on nor off - DEBUGON IS NOT SET!');
        $END
       
    END;
    /
    show errors
    
    debug is neither on nor off - DEBUGON IS NOT SET!
    
    
    PL/SQL procedure successfully completed.
    
    
    No errors.
    SCOTT@ORCL>
    
    

    Miss me something; It is late after all; Thank you

    Jason

    The compiler warnings do not seem to work for anonymous blocks, only for named objects:

    dev1 > alter session set plsql_ccflags = ";

    Modified session.

    dev1 > alter session set plsql_warnings = ' enable: all ';

    dev1 > create or replace procedure p as
    2 start
    $3 $IF $DEBUGON $THEN
    4 dbms_output.put_line ('debug is on ');
    5 $ELSIF $ $DEBUGON $THEN NO
    6 dbms_output.put_line ("' debugging is NOT on");
    7 $END
    8 dbms_output.put_line (' ' in the procedure ');
    9 end;
    10.

    SP2-0804: Procedure created with compilation warnings

    dev1 > view the error
    P: PROCEDURAL errors

    LINE/COL ERROR
    -------- -----------------------------------------------------------------
    3/8 PLW-06003: directive of unknown inquiry ' $$DEBUGON '
    5/15 PLW-06003: directive of unknown inquiry ' $$DEBUGON '

    John

  • IMP db every success with warnings

    Looking for options to fix those or I can ignore them? What would be the side effect if I drop/cascade users and rerun imp once growing tablespace TS_PUBLIC size or I shouldn't do? and just difficulty warnings little or even just ignore them?

    Most of the tables (I'd say 95%) & there data imported successfully after full imp, db size is around 80GB, import completed successfully with warnings, which is less...



    IMP-00017: statement failed with error ORACLE 1659:
    "CREATE TABLE"CA_QUERY_1"
    «ABLESPACE «TS_PUBLIC»»

    IMP-00041: WARNING: object created with compilation warnings
    ' CREATE THE FORCE 'ADMIN' VIEW. ". CHECK_EXTENTS_V ".

    IMP-00041: WARNING: object created with compilation warnings
    "CREATE TRIGGER MT1758. MEDDRA_MT1758_THE_SYN_UPD ".

    DBA2011 wrote:
    Thank you, advice to confirm that all the imp and all data has correctly applied in the new db, before giving it to the customer?

    Review the LOG file.

  • [HELP] Call library function node...

    I have a DLL that has a function as follows:

    int GetMessageNameNumber (char * messageName [], const int MessageNumber);

     

    The function is used thus:

    char * MessageName = NULL;
    int MessageNumber = 0;
    ...

    error = HL1553API_GetMessageNumberName (& MessageName, MessageNumber);

    MessageName will contain the name of the message as a string.

    I saw the Devils own job trying to wrap this in a Labview module.  I have a knot of library function to call the above function, but I'm not sure what to set the parameter "MessageName" also!  I tried array of integers 8 signed bits, adapted to the Type of pointer to data in the table and then passed in an array of strings.  Whatever I do translates into LabView crash.  I know HL1553API_GetMessageNumberName works, because if I call it directly in TestStand it works fine.  I need LabView well!

    Any ideas?

    C a pointer to a string or an array of strings are completely ambiguous.

    char * something = char * something [].

    You can't tell the two apart from the syntax, but only from the documentation or an example of how the function is called. A C compiler treats the equal in terms of access (but a C++ compiler will do a syntactic differentiation when code syntax checking, with the possible result compile warnings when you are prompted to use a sufficiently high level of warning).

    The example shows that it is not a string array gets allocated by the caller and passed to the function, but a string pointer that is passed by reference. So the function will allocate a pointer and return it (a very atypical C practice at least for strings). This automatically raises the question when and how this pointer will be released? The documentation for this function should document the call from Manager memory allows to allocate this pointer and also point to the function to call to release. Ideally the library (DLL) provides an exported function for this purpose.

    Assume that everything I spoke so far is clear and available you need to cheat a bit LabVIEW. You need to configer a pointer size whole that is passed by reference. Now this whole in the diagram IS actually your channel. If you only need to pass this pointer to other library functions call that you're already doing. Otherwise if you need access to the contents of this string from the diagram LabVIEW, you will need to copy the information from this string to a real string of LabVIEW pointer.

    One way to do that is to use the export of the MoveBlock() C function that LabVIEW exports itself. I have explained this several times here on this forum and the MoveBlock research will no doubt find out these positions.

    Another slightly better way is to use the LStrPrintf() function which also exports of LabVIEW. To do this, you configure a library function call as follows:

    Library name: LabVIEW

    Function name: LStrPrintf

    Calling Convention: C

    Thread: both are possible, but the function is thread safe, so just use environment

    return parameter: int32 (there is a possible LabVIEW Manager error code)

    1st parameter: handle string of LabVIEW, passed by value

    parameter 2: C string pointer

    3rd parameter: integer pointer size, passed by valu

    Wire an empty string in the first parameter constant.

    Wire a constant containing the text '%s' without the quotes on the 2nd.

    The pointer to your thread on the 3rd string

    The function will return 0 as a return value and the content of the string on the side of the exit of the 1st parameter or a zero value indicating that a mistake to return back.

  • Problematic JDeveloper facilities (rt.jar)

    Hello

    I have problems with JDeveloper facilities on my new laptop Windows 7. My previous laptop was also Windows 7, and he has not had these problems with the same versions of JDeveloper.

    I installed 11.1.1.6 and 11.1.1.9 JDeveloper and both versions have the following symptoms:

    • Sometimes I can't start JDeveloper from the Start Menu, I have to go into the installation with Explorer directory and launch it by clicking on jdeveloper.exe.
    • Compilation warnings:
    Warning: Error occurred during initialization of VM
    Warning: java/lang/ClassNotFoundException: error in opening JAR file  C:\Oracle\Middleware_11.1.1.9\jdk160_29\jre\lib\rt.jar
    
    • Running an integrated Weblogic application works well at first but after a while, I get an error internal server with the following types of errors:
    weblogic.servlet.jsp.CompilationException: Failed to compile JSP /view1.jspx
    view1.jspx:7:4: The type java.lang.Object cannot be resolved. It is indirectly referenced from required .class files
      <f:view>
    

    By following the instructions on this forum and elsewhere, I have tried using a different JDK (I used JDK provided for 11.1.1.6 and tried to use then the one that came with 11.1.1.9), checked that I can open rt.jar after changing the type of file in .zip etc. I also changed the directory privileges so that my user account has full control of all files in JDeveloper.

    Any suggestions what I should try next?

    Thank you!

    Jdev 11.1.1.9 is provided with the jdk 1.6?

    I thought that it uses jdk 1.7.

    Try to download the latest jdk 1.7 and install it on your pc. Then install jdev 11.1.1.9 and download the generic installation program. Install jdev using the generic installation program (run as admin) and use the jdk 1.7, you have installed before.

    Timo

  • EXCEPTION (ERROR) HANDLING - Concepts

    Hello everyone;

    Now, I'm learning "PL/SQL " EXCEPTIONS MANAGEMENT (ERRORS)

    I have official document of interim oracle. If I want to record some doubts here. 

    (I have googled but is not clear, so I expect answers from experts)

    REF_LINK: http://docs.oracle.com/cd/E11882_01/timesten.112/e21639/exceptions.htm#BABHCGHA


    Whenever occurs an error in the program - PL/SQL throws an exception


    Question 1: What is exactly predefined Exceptions?


    Consider that I have 5 PL/SQL blocks, if 1st slice with the error and the fact of block t contains an exception handler.


    Question 2: If so, does pl/sql runs remaining all the blocks?  or leave suddenly 1st block?


    Question 3: If any block does not contain an exception handler, what will happen? (review, error occurred in a whole block)


    Thanks in advance !

    TimesTen?  -I don't know what timesten

    Then why did you post a link to the ' PL/SQL oracle TimesTen In - Memory Database® Developer's guide'

    See the Guide of Dev of PL/SQL Oracle DB

    http://docs.Oracle.com/CD/E11882_01/AppDev.112/e25519/errors.htm#CHDFGBJI

    This chapter explains how to handle warnings compiling PL/SQL and PL/SQL runtime errors. These are called exceptions.

    Note:

    The language of the warning and error messages depends on to the NLS_LANGUAGE parameter. For more information about this setting, see the Oracle database globalization support Guide.

    Topics

    Visit this section for 'predefined Exceptions "? It lists these exceptions and tells you what they are.

    The "Overview of the management of exceptions" section will explain how exceptions are handled.

    If an exception is thrown in a block that has no exception for her handler, the exception propagates. That said, the exception reproduces itself in successive inclusive blocks until a block contains a handler for it or there is no enclosing block (for more information, see "Propagation of the Exception"). If there is no handler for the exception, PL/SQL returns an unhandled environmental exception error caller or host, that determines the outcome (for more information, see "unhandled Exceptions").

    So if your five blocks are NOT nested each of them can have an exception handler. So if an exception occurs in a block and you handle this exception the next block will BE executed.

    If your five nested blocks then the exception in an inner block will spread it is enveloping block if you do not manage it.

  • Upgrade of the ODM EA4.0 errors

    Hello

    I have improved my 11.2.0.3 DB which has patterns of ODM, workflows, etc.

    The said upgrade window «Task completed Successfullt»

    But when I check the log file I following should I be worried by these?  are they actual errors during the upgrade? or everything is OK?

    Compiled PACKAGE BODY ODMR_ENGINE_SEC

    Fixed: WARNING: ODMR_ENGINE_SEC BODY of PACKAGE created with compilation warnings or errors.

    Errors: Newspaper the compiler check

    Compiled PACKAGE BODY ODMR_INTERNAL_UTIL

    Fixed: WARNING: ODMR_INTERNAL_UTIL BODY of PACKAGE created with compilation warnings or errors.

    Errors: Newspaper the compiler check

    Compiled PACKAGE BODY ODMR_PROJECT_SEC

    Fixed: WARNING: ODMR_PROJECT_SEC BODY of PACKAGE created with compilation warnings or errors.

    Errors: Newspaper the compiler check

    Compiled PACKAGE BODY ODMR_ENGINE_TRANSFORMS_SEC

    Fixed: WARNING: ODMR_ENGINE_TRANSFORMS_SEC BODY of PACKAGE created with compilation warnings or errors.

    Errors: Newspaper the compiler check

    Compiled PACKAGE BODY ODMR_INTERNAL_UTIL_SEC

    Fixed: WARNING: ODMR_INTERNAL_UTIL_SEC BODY of PACKAGE created with compilation warnings or errors.

    Errors: Newspaper the compiler check

    Compiled PACKAGE BODY ODMR_ENGINE_TEXT_SEC

    Fixed: WARNING: ODMR_ENGINE_TEXT_SEC BODY of PACKAGE created with compilation warnings or errors.

    Errors: Newspaper the compiler check

    Compiled PACKAGE BODY ODMR_ENGINE_OUTPUT_SEC

    Fixed: WARNING: ODMR_ENGINE_OUTPUT_SEC BODY of PACKAGE created with compilation warnings or errors.

    Errors: Newspaper the compiler check

    Compiled PACKAGE BODY ODMR_ENGINE_MINING_SEC

    Fixed: WARNING: ODMR_ENGINE_MINING_SEC BODY of PACKAGE created with compilation warnings or errors.

    Errors: Newspaper the compiler check

    Compiled PACKAGE BODY ODMR_ENGINE_DATA_SEC

    Fixed: WARNING: ODMR_ENGINE_DATA_SEC BODY of PACKAGE created with compilation warnings or errors.

    Errors: Newspaper the compiler check

    Compiled PACKAGE BODY ODMR_WORKFLOW_SEC

    Fixed: WARNING: ODMR_WORKFLOW_SEC BODY of PACKAGE created with compilation warnings or errors.

    Errors: Newspaper the compiler check

    Compiled PACKAGE BODY ODMR_ENGINE

    Fixed: WARNING: ODMR_ENGINE BODY of PACKAGE created with compilation warnings or errors.

    Errors: Newspaper the compiler check

    Compiled PACKAGE BODY ODMR_PROJECT

    Fixed: WARNING: ODMR_PROJECT BODY of PACKAGE created with compilation warnings or errors.

    Errors: Newspaper the compiler check

    Compiled PACKAGE BODY ODMR_ENGINE_TRANSFORMS

    Fixed: WARNING: ODMR_ENGINE_TRANSFORMS BODY of PACKAGE created with compilation warnings or errors.

    Errors: Newspaper the compiler check

    Compiled PACKAGE BODY ODMR_ENGINE_DYNAMIC_NODE

    Fixed: WARNING: ODMR_ENGINE_DYNAMIC_NODE BODY of PACKAGE created with compilation warnings or errors.

    Errors: Newspaper the compiler check

    Compiled PACKAGE BODY ODMR_UTIL

    Fixed: WARNING: ODMR_UTIL BODY of PACKAGE created with compilation warnings or errors.

    Errors: Newspaper the compiler check

    Compiled PACKAGE BODY ODMR_ENGINE_TEXT

    Fixed: WARNING: ODMR_ENGINE_TEXT BODY of PACKAGE created with compilation warnings or errors.

    Errors: Newspaper the compiler check

    Compiled PACKAGE BODY ODMR_ENGINE_OUTPUT

    Fixed: WARNING: ODMR_ENGINE_OUTPUT BODY of PACKAGE created with compilation warnings or errors.

    Errors: Newspaper the compiler check

    Compiled PACKAGE BODY ODMR_ENGINE_MINING

    Fixed: WARNING: ODMR_ENGINE_MINING BODY of PACKAGE created with compilation warnings or errors.

    Errors: Newspaper the compiler check

    Compiled PACKAGE BODY ODMR_ENGINE_DATA

    Fixed: WARNING: ODMR_ENGINE_DATA BODY of PACKAGE created with compilation warnings or errors.

    Errors: Newspaper the compiler check

    Compiled PACKAGE BODY ODMR_WORKFLOW

    Fixed: WARNING: ODMR_WORKFLOW BODY of PACKAGE created with compilation warnings or errors.

    Errors: Newspaper the compiler check

    anonymous block filled

    Start to undermine repository DB object Upgrade.18 - JUL-13 13:56:41.332000000 + 01:00

    HI Brendan,

    The sequencing of the installation process can lead to the original pl/sql compilation failing, but this is supported later in the process.

    You should see something like the following in the log (see below).

    Let us know if you encounter any problems using ODMr.

    Thank you, Mark

    Validate the ODMRSYS to ensure that all objects are valid. 16 JULY 13 02.56.19.981369000 PM - 04:00

    anonymous block filled

    Invalid ODMRSYS objects report

    Total number of invalid objects: 0

  • Messages do not queue--procedure not called plsqlcallback

    I'm having a problem with queued messages do not

    My code is quite complicated, so I tried this example: http://asktom.oracle.com/pls/asktom/f?p=100:11:0:P11_QUESTION_ID:8760267539329, except for:
    sys@ORA920> begin
      2     dbms_aqadm.grant_system_privilege
      3     ('ENQUEUE_ANY','AQ',FALSE);
      4     dbms_aqadm.grant_system_privilege
      5     ('DEQUEUE_ANY','AQ',FALSE);
      6  end;
      7  /
    My user DQIDW has execute privileges on dbms_aq and on the role of AQ_ADMINISTRATOR_ROLE and is the owner of the queue/data/code - no other databases or users are involved.

    I think it is sufficient according to the documentation (http://docs.oracle.com/cd/E11882_01/server.112/e11013/manage.htm)

    Once I ran example of Tom Kyte I have a session of line in OBJMSGS80_QTAB and nothing in message_table - nothing seems to change over the next hour.

    What do need me to do further investigation.

    Thank you very much

    Ben
    BANNER
    ________________________________________________________________________________
    Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
    PL/SQL Release 11.2.0.3.0 - Production
    CORE    11.2.0.3.0      Production
    TNS for 64-bit Windows: Version 11.2.0.3.0 - Production
    NLSRTL Version 11.2.0.3.0 - Production
    That's what I run:
    DWDQI> CREATE type dqidw.Message_typ as object
      2    ( subject VARCHAR2(30), text VARCHAR2(80));
      3  /
    
    Type created.
    
    DWDQI>
    DWDQI> begin
      2      DBMS_AQADM.CREATE_QUEUE_TABLE
      3      ( queue_table => 'dqidw.objmsgs80_qtab',
      4        queue_payload_type =>  'dqidw.Message_typ',
      5        multiple_consumers => TRUE );
      6
      7      DBMS_AQADM.CREATE_QUEUE
      8      ( queue_name => 'MSG_QUEUE',
      9        queue_table => 'dqidw.objmsgs80_qtab');
     10
     11      DBMS_AQADM.START_QUEUE
     12      (  queue_name => 'MSG_QUEUE');
     13  end;
     14  /
    
    PL/SQL procedure successfully completed.
    
    DWDQI>
    DWDQI> create procedure enqueue_msg( p_msg in varchar2 )
      2  as
      3   enqueue_options dbms_aq.enqueue_options_t;
      4   message_properties dbms_aq.message_properties_t;
      5   message_handle RAW(16);
      6   message dqidw.message_typ;
      7  BEGIN
      8     message := message_typ('NORMAL MESSAGE',  p_msg );
      9     dbms_aq.enqueue(queue_name => 'msg_queue',
     10                     enqueue_options => enqueue_options,
     11                     message_properties => message_properties,
     12                     payload => message,
     13                     msgid => message_handle);
     14  end;
     15  /
    
    Procedure created.
    
    DWDQI>
    DWDQI> create table message_table( msg varchar2(4000) );
    
    Table created.
    
    DWDQI>
    DWDQI> create or replace procedure notifyCB( context raw,
      2                                        reginfo sys.aq$_reg_info,
      3                                        descr sys.aq$_descriptor,
      4                                        payload raw,
      5                                        payloadl number)
      6  as
      7   dequeue_options dbms_aq.dequeue_options_t;
      8   message_properties dbms_aq.message_properties_t;
      9   message_handle RAW(16);
     10   message dqidw.message_typ;
     11  BEGIN
     12     dequeue_options.msgid := descr.msg_id;
     13     dequeue_options.consumer_name := descr.consumer_name;
     14     DBMS_AQ.DEQUEUE(queue_name => descr.queue_name,
     15                     dequeue_options => dequeue_options,
     16                     message_properties => message_properties,
     17                     payload => message,
     18                     msgid => message_handle);
     19     insert into message_table values
     20     ( 'Dequeued and processed "' || message.text || '"' );
     21     COMMIT;
     22  END;
     23  /
    
    SP2-0804: Procedure created with compilation warnings
    
    DWDQI> sho err
    Errors for PROCEDURE NOTIFYCB:
    
    LINE/COL ERROR
    ________ _________________________________________________________________
    1/21     PLW-06010: keyword "CONTEXT" used as a defined name
    DWDQI>
    DWDQI> begin
      2      dbms_aqadm.add_subscriber
      3      ( queue_name => 'dqidw.msg_queue',
      4        subscriber => sys.aq$_agent( 'recipient', null, null ) );
      5  end;
      6  /
    
    PL/SQL procedure successfully completed.
    
    DWDQI>
    DWDQI> BEGIN
      2      dbms_aq.register
      3      ( sys.aq$_reg_info_list(
      4          sys.aq$_reg_info('DQIDW.MSG_QUEUE:RECIPIENT',
      5                            DBMS_AQ.NAMESPACE_AQ,
      6                           'plsql://AQ.notifyCB',
      7                            HEXTORAW('FF')) ) ,
      8        1 );
      9  end;
     10  /
    
    PL/SQL procedure successfully completed.
    
    DWDQI>
    DWDQI>
    DWDQI>
    DWDQI> select * from message_table;
    
    no rows selected
    
    DWDQI>
    DWDQI> exec enqueue_msg( 'This is a test....' );
    
    PL/SQL procedure successfully completed.
    
    DWDQI>
    DWDQI> commit;
    
    Commit complete.
    
    DWDQI>
    DWDQI> select * from message_table;
    
    no rows selected
    and looking round related tables
      1* select * from objmsgs80_qtab
    
    Q_NAME                         MSGID
    ______________________________ ________________________________
    CORRID
    ________________________________________________________________________________________________________________________
      PRIORITY      STATE DELAY                                                                       EXPIRATION
    __________ __________ ___________________________________________________________________________ __________
    TIME_MANAGER_INFO                                                           LOCAL_ORDER_NO   CHAIN_NO       CSCN
    ___________________________________________________________________________ ______________ __________ __________
          DSCN ENQ_TIME                                                                    ENQ_UID
    __________ ___________________________________________________________________________ ______________________________
    ENQ_TID                        DEQ_TIME
    ______________________________ ___________________________________________________________________________
    DEQ_UID                        DEQ_TID                        RETRY_COUNT EXCEPTION_QSCHEMA
    ______________________________ ______________________________ ___________ ______________________________
    EXCEPTION_QUEUE                   STEP_NO RECIPIENT_KEY DEQUEUE_MSGID                    SENDER_NAME
    ______________________________ __________ _____________ ________________________________ ______________________________
    SENDER_ADDRESS       SENDER_PROTOCOL
    ____________________ _______________
    USER_DATA(SUBJECT, TEXT)
    ________________________________________________________________________________________________________________________
    USER_PROP()
    ________________________________________________________________________________________________________________________
    MSG_QUEUE                      1F9BB7888DD9462BB4F7E026C92D8E5F
    
             1          0
                                                                                             0          0          0
             0 28-FEB-13 18.41.07.677000                                                   DQIDW
    77.12.1223030
                                                                            0
                                            0             0
    
    MESSAGE_TYP('NORMAL MESSAGE', 'This is a test....')
    
    DWDQI> select count(*) from AQ$_OBJMSGS80_QTAB_F;
    
      COUNT(*)
    __________
             1
    
    DWDQI> select count(*) from AQ$_OBJMSGS80_QTAB_G;
    
      COUNT(*)
    __________
             0
    
    DWDQI> select count(*) from AQ$_OBJMSGS80_QTAB_H;
    
      COUNT(*)
    __________
             1
    
    DWDQI> select count(*) from AQ$_OBJMSGS80_QTAB_I;
    
      COUNT(*)
    __________
             1
    
    DWDQI> select count(*) from AQ$_OBJMSGS80_QTAB_L;
    
      COUNT(*)
    __________
             0
    
    DWDQI> select count(*) from AQ$_OBJMSGS80_QTAB_S;
    
      COUNT(*)
    __________
             3
    
    DWDQI> select count(*) from AQ$_OBJMSGS80_QTAB_T;
    
      COUNT(*)
    __________
             0

    Location_name: plsql://AQ.notifyCB

    Ben,

    You have created a notifyCB to DQIDW, but it is recorded as AQ.notifyCB. Please unsubscribe it and re-save it under DQIDW.notifyCB.

    BEGIN
      2      dbms_aq.UNregister
      3      ( sys.aq$_reg_info_list(
      4          sys.aq$_reg_info('DQIDW.MSG_QUEUE:RECIPIENT',
      5                            DBMS_AQ.NAMESPACE_AQ,
      6                           'plsql://AQ.notifyCB',
      7                            HEXTORAW('FF')) ) ,
      8        1 );
      9  end;
    /
    
    BEGIN
      2      dbms_aq.register
      3      ( sys.aq$_reg_info_list(
      4          sys.aq$_reg_info('DQIDW.MSG_QUEUE:RECIPIENT',
      5                            DBMS_AQ.NAMESPACE_AQ,
      6                           'plsql://DQIDW.notifyCB',
      7                            HEXTORAW('FF')) ) ,
      8        1 );
      9  end;
    /
    

    Hope that helps.

Maybe you are looking for