Problem in sending the data of graphic writing in words

I had this problem and it is said that the limit is 4000 rows or columns, someone knows how can I change the limit?

IM using report generation tools to draw the graph in Microsoft Words

I have more than 10000 of data that will be used to draw the graph.

Someone knows how to fix this?

And also that

Tags: NI Software

Similar Questions

  • should which product I buy to be able to save and send the data entered in a form?

    Hello, should what product I buy to be able to save and send the data entered in a form?

    Hi clarka14179614,

    If you are referring to record and send after filling out a form, you can either use an Adobe Reader or Acrobat application.

    Adobe Reader is a free service and you can install it here: Adobe - Adobe Acrobat Reader DC Distribution

    Let us know if you need additional assistance.

    Kind regards

    Meenakshi

  • How to solve "here has been a problem to read the data in the layer. read the composite data instead? »

    Hello

    I'm working on the UI for a 2 month Word Press theme, and it has a ton of layers with file size of 900 MB.

    When designing, I get a message that says:

    "here was a problem to read the data in the layer. read the composite data instead? »

    Please solve this problem because I am so tired of working on this that I don't want this effort in vain.

    and sorry if my English is bad.

    dffd.jpg

    Hi AymanAlrifai,

    Would you be able to share the file problem with me zipped upward? petgreen [at] adobe [dot] com

    I'll see if I have the same problem and check with the team to investigate the issue here and see if we can resolve it for you.

    Kind regards

    Pete

  • Sends the data backend Java

    What is the best way to send a flex object to a java backend and then do something about this on the server? I have a table that contains a custom class. When the user clicks on send, I want to send the picture to Java, then get the content of the table to handle the content and write it to a file.

    I have a remote Java object I want to send the data, in order to manipulate it. I don't think that I need a remote object to represent the purpose of flex, but because that would mean that whatever changes I do object in flex continually is sent to the back-end right? I want to just send it in one appointment once the user has finished editing on the front-end server.

    I found XML serializers that people did that recursively go through the object and create XML. It must then be deserialized on the coast of Java. I thought that there must be an easier way. Is there a library or something for this?

    Perhaps, I do not understand the reason for your implementation so don't take no not this personally.  But why would you send a Canvas object, which is part of the view on the server?  If you are only wanting to send the data contained in the text to the server for processing objects you want to do is create a ValueObject (TransferObject for some) and send it to the server, as well as perhaps instructions you want to send.

    On the other hand (and this is just a blind guess at what you're trying) If you are wanting to send the objects so that you can implement some sort of compilation side server, then you want to send the object to plain text for the Web as one of the settings contained in your ValueObject.  Alternatively, you can use Adobe AIR and zip all of the defined object and send the file to the server where it can be decompressed and compiled.

    Here is a blog post on data transfer between Java and Flex using RemoteClass.

    ATA-transfer-objects-from-Java-to-Flex/ http://pachamuthu.wordpress.com/2009/07/15/using-BlazeDS-to-Send-User-Defined-Data-types-d

    I hope this helps.  If this isn't the case, then perhaps a little more information on what you are trying to accomplish might help.

    -Joe

  • Sends the data sequentially to the FPGA to a file during playback

    Hi all

    I am a new user of the Labview FPGA module, and I need your help.

    I have a huge file in my computer and I want to treat my FPGA Module. I have a VI divided into small files first, but to my FPGA I do not know how. My idea is to create two blocks of memory in the FPGA in order to have a structure of Ping-pong, module while the second memory is written the first memory was read and the data is processed.

    The first problem is to forward these data to my blocks (as text and the FPGA does not accept it).

    The second problem is that I don't know if as it is made of wiring will work. Can you help me it wiring? I don't know if data should I wire in the host of the read method will go directly to the data items in the FPGA VI.

    Created memories are 64 MB each. I work with FlexRio.

    Thanks in advance.

    Greetings from King,
    Miguel.

    What you want to do, is create a DMA FIFO to send data down to the FPGA.  Make the data type of the DMA a U8.  Thus, on the side of the host, you just read your data from the file, use the array of strings of bytes and write to the DMA FIFO.  On the side of FPGA, you read DMA FIFO inside a loop TO make your table and then treat.  You may need to use a different DMA FIFO to send data to the host computer.

  • A result of sending the data to a while loop through another loop of TCP communication

    Hi all

    I have 2 screws

    1 matching model (using the method of Grab) which is put inside a while loop. This VI works correctly and returns a string in a specific format (position and the angle of the object).

    2 TCP server who always listens to a specific port, if it receives a correct command string, it sends the string above VI - 1 (position and angle).

    The two 2 screws works if they are in separate VI. But I want to combine them into 1 single VI and I get the problem: Pattern matching doesn't work anymore (the video has only first frame then stops).

    I tried to put the two while loop in parallel or put the TCP while loop inside while loop Pattern Matching. Nothing has worked.

    Pls see my attached VI and the TCP module.

    What is the solution for requirement?

    Thank you all!

    What I would do, is be your two screws at the same time.  Given that you do not send the last result, store the result in a global variable.  Your comparison models written VI the global variable of the results of each iteration of the loop and the TCP bed module global variable results when it receives the right to order and then send it.

  • Why convert? What is the advantage? Why convert it before you send the data over the network?

    Hello everyone.

    I have a question quite simple and intuitive. Yet Google does not seam to get the answer.

    Basically, I'm curious why should we catalogued something? It seems to me that it's just a little like a "band-aid" for editing data in conversion to a new data type, when it is not properly declared with an appropriate data type. What would be the advantage of this?

    Furthermore, I see a lot of data type casting to U8 programs before sending it over the network. Various reviews say it's for speed, but I can't understand how it improves speed. The same amount of data is still sent, just in a different type of data. This is overcoming a limitation of the network. The network somehow send smaller data types faster?

    I've been curious about this for a while and have yet to find an answer. Any help is appreciated.

    Thank you
    Taylor S. Amarel

    tsa256 wrote:

    Basically, I'm curious why should we catalogued something? It seems to me that it's just a little like a "band-aid" for editing data in conversion to a new data type, when it is not properly declared with an appropriate data type. What would be the advantage of this?

    It really depends on the specific situations.

    For example, some functions explicitly require certain types of data as inputs if they are not polymorphic.

    This means that if you do not convert the data yourself and you will see a red dot forced LabVIEW will do it for you.

    As to why the data was not the correct data type in the first place, it is sometimes inevitable.

    A few examples

    -What happens if you just read a text file as a long string.

    If there is digital data in this file, you need to analyze, and then convert it to a usable type (int, sgl, dbl, etc.)

    -you are given a 3rd part VI, dll, etc. that returns a numeric value as a double, but you need the value to I8.

    You cannot change the output of the function given to you, so what you can do to remedy this situation is cataloged data.

    tsa256 wrote:

    Furthermore, I see a lot of data type casting to U8 programs before sending it over the network. Various reviews say it's for speed, but I can't understand how it improves speed. The same amount of data is still sent, just in a different type of data. This is overcoming a limitation of the network. The network somehow send smaller data types faster?

    Somehow, this is my first response, but in a more general sense.

    Many functions down to the level of the OS run in binary.

    If your data are not already in binary, the sending computer must convert it to binary, and then send it, have the receiving computer convert in return.

    Two conversions on each side of the transmission add unnecessary delays.

  • Problem to adjust the data using the algorithm of lev - mar...

    Hello

    I'm a casual user of LV, and I need signal level using a non-linear custom model. The signal is basically a decay of exp (order 1) with a continuous component, so it's pretty simple.

    When I apply the routine of Lev - Mar's non-linear editing, I've always had the famous "an exception has occurred in externally called by a function of the call library node. This could have corrupted memory of LabView. Save any work., etc.. VIwas stopped to node "" a call to "NI_AALPro.lvlib: Real - Decomposition.vi of SWINE vesicular disease.

    The thing is I've already adapted successfully some basic (linear model) data using this form of Lev - Mar non-linear... but it won't work this time... and I don't see why.

    Could you watch my VI and model definition and tell me what I need to improve, and what might cause the problem? The main VI (TPV_Fit_ExpDec1_v1.0.vi) open a text file that contains my data (3 columns: time, a pulse (not useful for editing), the signal to fit). At the beginning, I isolate the part of the signal that matches t > = 0, because it is where begins the exponential decay. So I want just to get the part. I join the main VI, a txt file containing typical data, and made the VI that define the model to the lev-mark function.

    I would appreciate your help and suggestions!

    Thank you very much in advance.

    MY VERSION of LABVIEW is the 8.2

    JB

       
       
       

    Here's a quick rewrite. You should ALWAYS figure the curve for the initial parameter estimates see if they are in the ballpark. Rather than modify the data, you could just put the weight to zero for negatvie x. see if it works better.

  • Problem in sending the request to the server, MDS started after expired connection error

    Hello

    I have a problem when sending request to the server. I need to manage the time of connection error. When I send a request from my device to serve and connection time-out error, I need to send the request back to the server.  To test this error, before sending the request, the MDS quit and then I try sends the request to the server. After 2 minutes, the appliance up Connection Timed out Error.

    Now when I start the MDS and refer the request to the server, the request sent when the connection has expired also reached the server. (Totally 2 request are sent to the server).

    What is the behaviouir of MDS? If so how should I handle this.

    or have I missed something on my side?

    I use BlackBerry 4.2.1 JDE with SDM (4.5.0)

    Thanks in advance.

    (Note: see this link for the behavior of MDS.)

    Hi all,

    I finally found the solution.

    Everytime I go to start the net, I check that the connection is available or not by using below codes...

    HttpConnection conn=null;try    {    conn = (HttpConnection) getConnection(myURL);      if(conn == null)     {           Inform the user the process is in offline       }     catch(Exception e)      {      }      finally      {                try                {                    conn.close();                    conn = null;                }                catch (Exception e)                {                    conn = null;                }            }
    

    When this function is execute the connection is not closed properly.

    After that I got the connection error, start the MDS, meanwhile runs unclosed connection.

    Now, I removed the check above, its works very well.

    I made a mistake. Finally, I saw that and correct it.

    Once again thanks for all your opinions and answer.

    Sorry for my English.

  • Send the data stored in the variable clob as an attachment

    Hello

    Im trying to send an email with an attachment usinng UTL_SMTP. The following code queries data in the table and stores it in a variable of clob. But he throws ORA-06502: PL/SQL: digital error or value every time that I run it. The data is greater than 32 k. Can someone help me with this

    Create or replace procedure MAIL AS

    BEGIN

    DECLARE

    l_clob CLOB.

    BEGIN

    l_clob: = ' FIRST_NAME, LAST_NAME, ARRANGE_DATE, SLOT_FROM, SLOT_TO, Address1, WORKNUMERO, HOMENUMBER, LAPTOP, employe_id, COST_CENTER;

    FOR c1 IN (SELECT *)

    RESULTS)

    LOOP

    l_clob: =.

    l_clob

    || CHR (10)

    || C1. FIRST NAME

    || ','

    || C1. LAST_NAME

    ||','

    || C1. ARRANGE_DATE

    ||','

    || C1. SLOT_FROM

    ||','

    || C1. SLOT_TO

    ||','

    || C1. ADDRESS1

    ||’,’

    || C1. WORKNUMERO

    ||','

    || C1. HOMENUMBER

    ||','

    || C1. PORTABLE

    ||','

    || C1. EMPLOYEE_ID

    ||','

    || C1. COST_CENTER;

    END LOOP;

    SEND_TRANSPORT_MAIL (p_to = > ' [email protected]', )

                p_from        => ' [email protected] ',

    p_subject = > "Dump."

    p_text_msg = > ' Hi

    p_attach_name = > 'DUMP.csv. "

    p_attach_mime = > "text/plain",

    p_attach_clob = > l_clob,

    p_smtp_host = > 'a.b.c.d');

    END;

    END;

    /

    SQL>begin
      2    dbms_output.put_line( length( rpad( ' ', 32767 ) || 1234 ) );                        -- result in clob with length 32771
      3    dbms_output.put_line( length( rpad( to_clob( ' ' ), 32767 ) || 1234 ) );             -- result in clob with length 32771
      4    dbms_output.put_line( length( rpad( to_clob( ' ' ), 32768 ) || to_char( 1234 ) ) );  -- result in clob with length 32772
      5    dbms_output.put_line( length( rpad( to_clob( ' ' ), 32768 ) || 1234 ) );             -- ORA-06502: PL/SQL: numeric or value error
      6  end;
      7  /
    

    32771

    32771

    32772

    Start

    *

    ERROR on line 1:

    ORA-06502: PL/SQL: digital error or value

    ORA-06512: at line 5

    It looks like to the | default operator using varchar2.

    In line 3 the clob and number are implicit cast to a varchar2, and both are concatenated in a clob

    In line 4 the clob cannot be cast to a varchar2 because it is in the long run, so Oracle varchar2 (with the number) caste implied on the clob type too, that succeeds

    In line 5 the clob cannot be cast to a varchar2 because it's for a long time, so Oracle is trying to get the number to a clob to-online error

  • Is he closer to display the data in graphic format in the OPS?

    Hello Experts,

    I'm working on a feasibility OFA study and I have a question: is there in the OPS, any approach to represent data in graphic format, such as the schema of the Terminal?

    As far as I know, ADF supports this kind of representation and it can be incorporated into the OAF page as region. But it seems to separate server for the ADF, which is not supported in my project (assuming we have only EBS server). And the situation is similar for embedded Analytics OBIEE approach.

    Would like to share your experience or the reference of this kind of solution? Appreciate your help in advance!

    Thank you and best regards,

    Clark

    You can use graphics in the OPS.

    Visit this link: Java Based Technology Blog Sushant: 14. Graphic design in the OPS

    Sushant-

  • Strange problem casting between the DATE and time STAMP

    Hello world

    I'm faced with a problem of strange casting between the DATE and time STAMP. Strange, because this happens in SQL-Developer and the Testdatabase, but not when called from inside SQL-Plus, even if all Session settings are set to the top completely equal.

    I work on the Oracle 11 g Enterprise Edition Release 11.2.0.1.0 Windows database and run the following script, taken from SQL-Developer script output:

    < pre >
    create table ts_test)
    time/date stamp,
    stamp_copy timestamp)
    table TS_TEST standing.

    create or replace view vw_test as
    Select cast (date stamp) buffer,
    Cast (stamp_copy as date) stamp_copy
    of ts_test
    view VW_TEST standing.

    insert into ts_test
    Select systimestamp, the double null
    1 eingefugt Zeilen.

    Commit
    festgeschrieben.

    create or replace trigger trg_ts_test_iu
    instead of update on vw_test
    Start
    Update ts_test
    Set stamp_copy =: new.stamp_copy;
    end;
    RELAXATION trg_ts_test_iu kompiliert

    Update vw_test
    Set stamp_copy = stamp
    1 Zeilen written on.

    Select the stamp, stamp_copy, dump (stamp_copy)
    of ts_test
    STAMP STAMP_COPY DUMP (STAMP_COPY)
    -----------------------------------------------------------------------------------------------------------------
    30.05.2012 19:08:49, 218000000 30.05.3192 20:09:50, 000000000 Typ = 180 Len = 7: 131,192,5,30,21,10,51

    Select *.
    of nls_session_parameters
    VALUE OF THE PARAMETER
    ----------------------------------------------------------------------
    NLS_LANGUAGE GERMAN
    NLS_TERRITORY GERMANY
    NLS_CURRENCY €
    NLS_ISO_CURRENCY GERMANY
    NLS_NUMERIC_CHARACTERS.
    NLS_CALENDAR GREGORIAN
    NLS_DATE_FORMAT exact hh24:mi:ss
    NLS_DATE_LANGUAGE GERMAN
    NLS_SORT GERMAN
    NLS_TIME_FORMAT HH24:MI:SSXFF
    NLS_TIMESTAMP_FORMAT JJ. MM YYYY HH24:MI:SSXFF
    NLS_TIME_TZ_FORMAT HH24:MI:SSXFF TZR
    NLS_TIMESTAMP_TZ_FORMAT JJ. MM YYYY HH24:MI:SSXFF TZR
    NLS_DUAL_CURRENCY €
    BINARY NLS_COMP
    NLS_LENGTH_SEMANTICS TANK
    NLS_NCHAR_CONV_EXCP FAKE

    17 Zeilen offiziell

    Rollback
    Rollback abgeschlossen.
    < / pre >

    Look at the strange data that stamp_copy was after the update.

    When run from SQL over, everything is fine. But when I run this code in our application, the same phenomenon occurs. I've even seen a data dating back to the year 11907 (!), giving an exception by selecting from the table.

    Someone at - it an idea on how to work around this bug?

    Best regards

    Jürgen

    Did you check metalink for bugs?

    There are a few listed in this blog, that may be useful for you.

    http://hoopercharles.WordPress.com/2011/02/17/strange-timestamp-behavior/

  • Problem when sorting the data based on the date

    I am trying to sort the following data based on the column of date of receipt of Transaction, couldn't do it usi g the following syntax:

    <? sort: TRANSACTION_RECEIPT_DATE; ' ascending '; type_donnees = 'date '? >

    I have problem to convert the canonical date report date, there at - it another way to reach the exit without converting the date format.

    <? XML version = "1.0"? >
    <! - generated by the Oracle version 6.0.8.27.0 reports - >
    < RECDTREP >
    < LIST_G_ASW_REC_DATE >
    < G_ASW_REC_DATE >
    < SNO_CREATED_BY > 1433 < / SNO_CREATED_BY >
    < SNO_REQUEST_ID >-1 < / SNO_REQUEST_ID >
    < VENDOR_LOT_NUM > PO104 < / VENDOR_LOT_NUM >
    < SNO_CREATION_DATE > 7 April 09 < / SNO_CREATION_DATE >
    < SNO_ATTRIBUTE1 > < / SNO_ATTRIBUTE1 >
    < > 24636 OBJECT_ID < / OBJECT_ID >
    < INITIALIZATION_DATE > 7 April 09 < / INITIALIZATION_DATE >
    < ORGANIZATION_CODE > 10 < / ORGANIZATION_CODE >
    < ORGANISATION_NAME > NDC - PARTS < / ORGANISATION_NAME >
    < Serial_number > 6510863063 < / Serial_number >
    < ITEM_CODE > 3000.006 < / ITEM_CODE >
    < DESCRIPTION > ALLISON 3000 SERIES WE HWY TRANSMISSION E016392 < / DESCRIPTION >
    ALLISON < MANUFACTURER > < / MANUFACTURER >
    < APPLICATION > home < / APPLICATION >
    < ITEM_COST > 8879.02 < / ITEM_COST >
    < MATERIAL_COST > 631.09 < / MATERIAL_COST >
    AUD < CURRENCY_CODE > < / CURRENCY_CODE >
    < PO_UNIT_PRICE > < / PO_UNIT_PRICE >
    < TRANSACTION_RECEIPT_DATE > 7 April 09 < / TRANSACTION_RECEIPT_DATE >
    < PO_NUMBER > 982121 < / PO_NUMBER >
    < / G_ASW_REC_DATE >
    < G_ASW_REC_DATE >
    < SNO_CREATED_BY > 1433 < / SNO_CREATED_BY >
    < SNO_REQUEST_ID >-1 < / SNO_REQUEST_ID >
    < VENDOR_LOT_NUM > PO107 < / VENDOR_LOT_NUM >
    < SNO_CREATION_DATE > 7 April 09 < / SNO_CREATION_DATE >
    < SNO_ATTRIBUTE1 > < / SNO_ATTRIBUTE1 >
    < > 24641 OBJECT_ID < / OBJECT_ID >
    < INITIALIZATION_DATE > 7 April 09 < / INITIALIZATION_DATE >
    < ORGANIZATION_CODE > 10 < / ORGANIZATION_CODE >
    < ORGANISATION_NAME > NDC - PARTS < / ORGANISATION_NAME >
    < Serial_number > 6510863068 < / Serial_number >
    < ITEM_CODE > 3000.006 < / ITEM_CODE >
    < DESCRIPTION > ALLISON 3000 SERIES WE HWY TRANSMISSION E016392 < / DESCRIPTION >
    ALLISON < MANUFACTURER > < / MANUFACTURER >
    < APPLICATION > home < / APPLICATION >
    < ITEM_COST > 8879.02 < / ITEM_COST >
    < MATERIAL_COST > 631.09 < / MATERIAL_COST >
    AUD < CURRENCY_CODE > < / CURRENCY_CODE >
    < PO_UNIT_PRICE > < / PO_UNIT_PRICE >
    < TRANSACTION_RECEIPT_DATE > 7 April 09 < / TRANSACTION_RECEIPT_DATE >
    < PO_NUMBER > 982121 < / PO_NUMBER >
    < / G_ASW_REC_DATE >
    < G_ASW_REC_DATE >
    < SNO_CREATED_BY > 1433 < / SNO_CREATED_BY >
    < SNO_REQUEST_ID >-1 < / SNO_REQUEST_ID >
    PO123 < VENDOR_LOT_NUM > < / VENDOR_LOT_NUM >
    < SNO_CREATION_DATE > 7 April 09 < / SNO_CREATION_DATE >
    < SNO_ATTRIBUTE1 > 2008/06/11 00:00:00 < / SNO_ATTRIBUTE1 >
    < > 24658 OBJECT_ID < / OBJECT_ID >
    < INITIALIZATION_DATE > 7 April 09 < / INITIALIZATION_DATE >
    < ORGANIZATION_CODE > 10 < / ORGANIZATION_CODE >
    < ORGANISATION_NAME > NDC - PARTS < / ORGANISATION_NAME >
    < Serial_number > 6510863086 < / Serial_number >
    < ITEM_CODE > 3000.006 < / ITEM_CODE >
    < DESCRIPTION > ALLISON 3000 SERIES WE HWY TRANSMISSION E016392 < / DESCRIPTION >
    ALLISON < MANUFACTURER > < / MANUFACTURER >
    < APPLICATION > home < / APPLICATION >
    < ITEM_COST > 8879.02 < / ITEM_COST >
    < MATERIAL_COST > 631.09 < / MATERIAL_COST >
    AUD < CURRENCY_CODE > < / CURRENCY_CODE >
    < PO_UNIT_PRICE > < / PO_UNIT_PRICE >
    < TRANSACTION_RECEIPT_DATE > 7 April 09 < / TRANSACTION_RECEIPT_DATE >
    < PO_NUMBER > 982121 < / PO_NUMBER >
    < / G_ASW_REC_DATE >
    < G_ASW_REC_DATE >
    < SNO_CREATED_BY > 1433 < / SNO_CREATED_BY >
    < SNO_REQUEST_ID >-1 < / SNO_REQUEST_ID >
    PO75 < VENDOR_LOT_NUM > < / VENDOR_LOT_NUM >
    < SNO_CREATION_DATE > 31 March 09 < / SNO_CREATION_DATE >
    < SNO_ATTRIBUTE1 > < / SNO_ATTRIBUTE1 >
    < > 22190 OBJECT_ID < / OBJECT_ID >
    < INITIALIZATION_DATE > 14 April 09 < / INITIALIZATION_DATE >
    < ORGANIZATION_CODE > 10 < / ORGANIZATION_CODE >
    < ORGANISATION_NAME > NDC - PARTS < / ORGANISATION_NAME >
    < Serial_number > 6510860842 < / Serial_number >
    < ITEM_CODE > 3000.006 < / ITEM_CODE >
    < DESCRIPTION > ALLISON 3000 SERIES WE HWY TRANSMISSION E016392 < / DESCRIPTION >
    ALLISON < MANUFACTURER > < / MANUFACTURER >
    < APPLICATION > home < / APPLICATION >
    < ITEM_COST > 8879.02 < / ITEM_COST >
    < MATERIAL_COST > 631.09 < / MATERIAL_COST >
    AUD < CURRENCY_CODE > < / CURRENCY_CODE >
    < PO_UNIT_PRICE > < / PO_UNIT_PRICE >
    < TRANSACTION_RECEIPT_DATE > 31 March 09 < / TRANSACTION_RECEIPT_DATE >
    < PO_NUMBER > 971515 < / PO_NUMBER >
    < / G_ASW_REC_DATE >
    < G_ASW_REC_DATE >
    < SNO_CREATED_BY > 1433 < / SNO_CREATED_BY >
    < SNO_REQUEST_ID >-1 < / SNO_REQUEST_ID >
    < VENDOR_LOT_NUM > PO116 < / VENDOR_LOT_NUM >
    < SNO_CREATION_DATE > 25 June 09 < / SNO_CREATION_DATE >
    < SNO_ATTRIBUTE1 > 2008/06/11 00:00:00 < / SNO_ATTRIBUTE1 >
    < > 64271 OBJECT_ID < / OBJECT_ID >
    < INITIALIZATION_DATE > 30 June 09 < / INITIALIZATION_DATE >
    < ORGANIZATION_CODE > 10 < / ORGANIZATION_CODE >
    < ORGANISATION_NAME > NDC - PARTS < / ORGANISATION_NAME >
    < Serial_number > 6510863077 < / Serial_number >
    < ITEM_CODE > 3000.006 < / ITEM_CODE >
    < DESCRIPTION > ALLISON 3000 SERIES WE HWY TRANSMISSION E016392 < / DESCRIPTION >
    ALLISON < MANUFACTURER > < / MANUFACTURER >
    < APPLICATION > home < / APPLICATION >
    < ITEM_COST > 8879.02 < / ITEM_COST >
    < MATERIAL_COST > 631.09 < / MATERIAL_COST >
    AUD < CURRENCY_CODE > < / CURRENCY_CODE >
    < PO_UNIT_PRICE > < / PO_UNIT_PRICE >
    < TRANSACTION_RECEIPT_DATE > 25 June 09 < / TRANSACTION_RECEIPT_DATE >
    < PO_NUMBER > 982121 < / PO_NUMBER >
    < / G_ASW_REC_DATE >
    < G_ASW_REC_DATE >
    < SNO_CREATED_BY > 1433 < / SNO_CREATED_BY >
    < SNO_REQUEST_ID >-1 < / SNO_REQUEST_ID >
    < VENDOR_LOT_NUM > PO92 < / VENDOR_LOT_NUM >
    < SNO_CREATION_DATE > 31 March 09 < / SNO_CREATION_DATE >
    < SNO_ATTRIBUTE1 > 2008/06/11 00:00:00 < / SNO_ATTRIBUTE1 >
    < > 22253 OBJECT_ID < / OBJECT_ID >
    < INITIALIZATION_DATE > 14 April 09 < / INITIALIZATION_DATE >
    < ORGANIZATION_CODE > 10 < / ORGANIZATION_CODE >
    < ORGANISATION_NAME > NDC - PARTS < / ORGANISATION_NAME >
    < Serial_number > 6510860890 < / Serial_number >
    < ITEM_CODE > 3000.006 < / ITEM_CODE >
    < DESCRIPTION > ALLISON 3000 SERIES WE HWY TRANSMISSION E016392 < / DESCRIPTION >
    ALLISON < MANUFACTURER > < / MANUFACTURER >
    < APPLICATION > home < / APPLICATION >
    < ITEM_COST > 8879.02 < / ITEM_COST >
    < MATERIAL_COST > 631.09 < / MATERIAL_COST >
    AUD < CURRENCY_CODE > < / CURRENCY_CODE >
    < PO_UNIT_PRICE > < / PO_UNIT_PRICE >
    < TRANSACTION_RECEIPT_DATE > 31 March 09 < / TRANSACTION_RECEIPT_DATE >
    < PO_NUMBER > 971515 < / PO_NUMBER >
    < / G_ASW_REC_DATE >
    < G_ASW_REC_DATE >
    < SNO_CREATED_BY > 1433 < / SNO_CREATED_BY >
    < SNO_REQUEST_ID >-1 < / SNO_REQUEST_ID >
    < VENDOR_LOT_NUM > PO99 < / VENDOR_LOT_NUM >
    < SNO_CREATION_DATE > 31 March 09 < / SNO_CREATION_DATE >
    < SNO_ATTRIBUTE1 > < / SNO_ATTRIBUTE1 >
    < > 22263 OBJECT_ID < / OBJECT_ID >
    < INITIALIZATION_DATE > 14 April 09 < / INITIALIZATION_DATE >
    < ORGANIZATION_CODE > 10 < / ORGANIZATION_CODE >
    < ORGANISATION_NAME > NDC - PARTS < / ORGANISATION_NAME >
    < Serial_number > 6510860899 < / Serial_number >
    < ITEM_CODE > 3000.006 < / ITEM_CODE >
    < DESCRIPTION > ALLISON 3000 SERIES WE HWY TRANSMISSION E016392 < / DESCRIPTION >
    ALLISON < MANUFACTURER > < / MANUFACTURER >
    < APPLICATION > home < / APPLICATION >
    < ITEM_COST > 8879.02 < / ITEM_COST >
    < MATERIAL_COST > 631.09 < / MATERIAL_COST >
    AUD < CURRENCY_CODE > < / CURRENCY_CODE >
    < PO_UNIT_PRICE > < / PO_UNIT_PRICE >
    < TRANSACTION_RECEIPT_DATE > 31 March 09 < / TRANSACTION_RECEIPT_DATE >
    < PO_NUMBER > 971515 < / PO_NUMBER >
    < / G_ASW_REC_DATE >
    < G_ASW_REC_DATE >
    < SNO_CREATED_BY > 1433 < / SNO_CREATED_BY >
    < SNO_REQUEST_ID >-1 < / SNO_REQUEST_ID >
    < VENDOR_LOT_NUM > PO109 < / VENDOR_LOT_NUM >
    < SNO_CREATION_DATE > 25 June 09 < / SNO_CREATION_DATE >
    < SNO_ATTRIBUTE1 > < / SNO_ATTRIBUTE1 >
    < > 64204 OBJECT_ID < / OBJECT_ID >
    < INITIALIZATION_DATE > 30 June 09 < / INITIALIZATION_DATE >
    < ORGANIZATION_CODE > 10 < / ORGANIZATION_CODE >
    < ORGANISATION_NAME > NDC - PARTS < / ORGANISATION_NAME >
    < Serial_number > 6510863070 < / Serial_number >
    < ITEM_CODE > 3000.006 < / ITEM_CODE >
    < DESCRIPTION > ALLISON 3000 SERIES WE HWY TRANSMISSION E016392 < / DESCRIPTION >
    ALLISON < MANUFACTURER > < / MANUFACTURER >
    < APPLICATION > home < / APPLICATION >
    < ITEM_COST > 8879.02 < / ITEM_COST >
    < MATERIAL_COST > 631.09 < / MATERIAL_COST >
    AUD < CURRENCY_CODE > < / CURRENCY_CODE >
    < PO_UNIT_PRICE > < / PO_UNIT_PRICE >
    < TRANSACTION_RECEIPT_DATE > 25 June 09 < / TRANSACTION_RECEIPT_DATE >
    < PO_NUMBER > 982121 < / PO_NUMBER >
    < / G_ASW_REC_DATE >
    < G_ASW_REC_DATE >
    < SNO_CREATED_BY > 1433 < / SNO_CREATED_BY >
    < SNO_REQUEST_ID >-1 < / SNO_REQUEST_ID >
    < VENDOR_LOT_NUM > PO135 < / VENDOR_LOT_NUM >
    < SNO_CREATION_DATE > 25 June 09 < / SNO_CREATION_DATE >
    < SNO_ATTRIBUTE1 > 18/06/2008 00:00:00 < / SNO_ATTRIBUTE1 >
    < > 64296 OBJECT_ID < / OBJECT_ID >
    < INITIALIZATION_DATE > 30 June 09 < / INITIALIZATION_DATE >
    < ORGANIZATION_CODE > 10 < / ORGANIZATION_CODE >
    < ORGANISATION_NAME > NDC - PARTS < / ORGANISATION_NAME >
    < Serial_number > 6510875546 < / Serial_number >
    < ITEM_CODE > 3000.006 < / ITEM_CODE >
    < DESCRIPTION > ALLISON 3000 SERIES WE HWY TRANSMISSION E016392 < / DESCRIPTION >
    ALLISON < MANUFACTURER > < / MANUFACTURER >
    < APPLICATION > home < / APPLICATION >
    < ITEM_COST > 8879.02 < / ITEM_COST >
    < MATERIAL_COST > 631.09 < / MATERIAL_COST >
    AUD < CURRENCY_CODE > < / CURRENCY_CODE >
    < PO_UNIT_PRICE > < / PO_UNIT_PRICE >
    < TRANSACTION_RECEIPT_DATE > 25 June 09 < / TRANSACTION_RECEIPT_DATE >
    < PO_NUMBER > 982121 < / PO_NUMBER >
    < / G_ASW_REC_DATE >
    < G_ASW_REC_DATE >
    < SNO_CREATED_BY > 1433 < / SNO_CREATED_BY >
    < SNO_REQUEST_ID >-1 < / SNO_REQUEST_ID >
    < VENDOR_LOT_NUM > PO101 < / VENDOR_LOT_NUM >
    < SNO_CREATION_DATE > 7 April 09 < / SNO_CREATION_DATE >
    < SNO_ATTRIBUTE1 > < / SNO_ATTRIBUTE1 >
    < > 24618 OBJECT_ID < / OBJECT_ID >
    < INITIALIZATION_DATE > 7 April 09 < / INITIALIZATION_DATE >
    < ORGANIZATION_CODE > 10 < / ORGANIZATION_CODE >
    < ORGANISATION_NAME > NDC - PARTS < / ORGANISATION_NAME >
    < Serial_number > 6510863046 < / Serial_number >
    < ITEM_CODE > 3000.006 < / ITEM_CODE >
    < DESCRIPTION > ALLISON 3000 SERIES WE HWY TRANSMISSION E016392 < / DESCRIPTION >
    ALLISON < MANUFACTURER > < / MANUFACTURER >
    < APPLICATION > home < / APPLICATION >
    < ITEM_COST > 8879.02 < / ITEM_COST >
    < MATERIAL_COST > 631.09 < / MATERIAL_COST >
    AUD < CURRENCY_CODE > < / CURRENCY_CODE >
    < PO_UNIT_PRICE > < / PO_UNIT_PRICE >
    < TRANSACTION_RECEIPT_DATE > 7 April 09 < / TRANSACTION_RECEIPT_DATE >
    < PO_NUMBER > 982121 < / PO_NUMBER >
    < / G_ASW_REC_DATE >
    < G_ASW_REC_DATE >
    < SNO_CREATED_BY > 1433 < / SNO_CREATED_BY >
    < SNO_REQUEST_ID >-1 < / SNO_REQUEST_ID >
    < VENDOR_LOT_NUM > PO120 < / VENDOR_LOT_NUM >
    < SNO_CREATION_DATE > 7 April 09 < / SNO_CREATION_DATE >
    < SNO_ATTRIBUTE1 > 2008/06/11 00:00:00 < / SNO_ATTRIBUTE1 >
    < > 24653 OBJECT_ID < / OBJECT_ID >
    < INITIALIZATION_DATE > 7 April 09 < / INITIALIZATION_DATE >
    < ORGANIZATION_CODE > 10 < / ORGANIZATION_CODE >
    < ORGANISATION_NAME > NDC - PARTS < / ORGANISATION_NAME >
    < Serial_number > 6510863081 < / Serial_number >
    < ITEM_CODE > 3000.006 < / ITEM_CODE >
    < DESCRIPTION > ALLISON 3000 SERIES WE HWY TRANSMISSION E016392 < / DESCRIPTION >
    ALLISON < MANUFACTURER > < / MANUFACTURER >
    < APPLICATION > home < / APPLICATION >
    < ITEM_COST > 8879.02 < / ITEM_COST >
    < MATERIAL_COST > 631.09 < / MATERIAL_COST >
    AUD < CURRENCY_CODE > < / CURRENCY_CODE >
    < PO_UNIT_PRICE > < / PO_UNIT_PRICE >
    < TRANSACTION_RECEIPT_DATE > 7 April 09 < / TRANSACTION_RECEIPT_DATE >
    < PO_NUMBER > 982121 < / PO_NUMBER >
    < / G_ASW_REC_DATE >
    < G_ASW_REC_DATE >
    < SNO_CREATED_BY > 1433 < / SNO_CREATED_BY >
    < SNO_REQUEST_ID >-1 < / SNO_REQUEST_ID >
    < VENDOR_LOT_NUM > PO122 < / VENDOR_LOT_NUM >
    < SNO_CREATION_DATE > 7 April 09 < / SNO_CREATION_DATE >
    < SNO_ATTRIBUTE1 > 2008/06/11 00:00:00 < / SNO_ATTRIBUTE1 >
    < > 24657 OBJECT_ID < / OBJECT_ID >
    < INITIALIZATION_DATE > 7 April 09 < / INITIALIZATION_DATE >
    < ORGANIZATION_CODE > 10 < / ORGANIZATION_CODE >
    < ORGANISATION_NAME > NDC - PARTS < / ORGANISATION_NAME >
    < Serial_number > 6510863085 < / Serial_number >
    < ITEM_CODE > 3000.006 < / ITEM_CODE >
    < DESCRIPTION > ALLISON 3000 SERIES WE HWY TRANSMISSION E016392 < / DESCRIPTION >
    ALLISON < MANUFACTURER > < / MANUFACTURER >
    < APPLICATION > home < / APPLICATION >
    < ITEM_COST > 8879.02 < / ITEM_COST >
    < MATERIAL_COST > 631.09 < / MATERIAL_COST >
    AUD < CURRENCY_CODE > < / CURRENCY_CODE >
    < PO_UNIT_PRICE > < / PO_UNIT_PRICE >
    < TRANSACTION_RECEIPT_DATE > 7 April 09 < / TRANSACTION_RECEIPT_DATE >
    < PO_NUMBER > 982121 < / PO_NUMBER >
    < / G_ASW_REC_DATE >
    < G_ASW_REC_DATE >
    < SNO_CREATED_BY > 1433 < / SNO_CREATED_BY >
    < SNO_REQUEST_ID >-1 < / SNO_REQUEST_ID >
    < VENDOR_LOT_NUM > PO127 < / VENDOR_LOT_NUM >
    < SNO_CREATION_DATE > 7 April 09 < / SNO_CREATION_DATE >
    < SNO_ATTRIBUTE1 > 2008/06/11 00:00:00 < / SNO_ATTRIBUTE1 >
    < > 24662 OBJECT_ID < / OBJECT_ID >
    < INITIALIZATION_DATE > 7 April 09 < / INITIALIZATION_DATE >
    < ORGANIZATION_CODE > 10 < / ORGANIZATION_CODE >
    < ORGANISATION_NAME > NDC - PARTS < / ORGANISATION_NAME >
    < Serial_number > 6510863090 < / Serial_number >
    < ITEM_CODE > 3000.006 < / ITEM_CODE >
    < DESCRIPTION > ALLISON 3000 SERIES WE HWY TRANSMISSION E016392 < / DESCRIPTION >
    ALLISON < MANUFACTURER > < / MANUFACTURER >
    < APPLICATION > home < / APPLICATION >
    < ITEM_COST > 8879.02 < / ITEM_COST >
    < MATERIAL_COST > 631.09 < / MATERIAL_COST >
    AUD < CURRENCY_CODE > < / CURRENCY_CODE >
    < PO_UNIT_PRICE > < / PO_UNIT_PRICE >
    < TRANSACTION_RECEIPT_DATE > 7 April 09 < / TRANSACTION_RECEIPT_DATE >
    < PO_NUMBER > 982121 < / PO_NUMBER >
    < / G_ASW_REC_DATE >
    < G_ASW_REC_DATE >
    < SNO_CREATED_BY > 1433 < / SNO_CREATED_BY >
    < SNO_REQUEST_ID >-1 < / SNO_REQUEST_ID >
    PO100 < VENDOR_LOT_NUM > < / VENDOR_LOT_NUM >
    < SNO_CREATION_DATE > 7 April 09 < / SNO_CREATION_DATE >
    < SNO_ATTRIBUTE1 > < / SNO_ATTRIBUTE1 >
    < > 24585 OBJECT_ID < / OBJECT_ID >
    < INITIALIZATION_DATE > 7 April 09 < / INITIALIZATION_DATE >
    < ORGANIZATION_CODE > 10 < / ORGANIZATION_CODE >
    < ORGANISATION_NAME > NDC - PARTS < / ORGANISATION_NAME >
    < Serial_number > 6510863033 < / Serial_number >
    < ITEM_CODE > 3000.006 < / ITEM_CODE >
    < DESCRIPTION > ALLISON 3000 SERIES WE HWY TRANSMISSION E016392 < / DESCRIPTION >
    ALLISON < MANUFACTURER > < / MANUFACTURER >
    < APPLICATION > home < / APPLICATION >
    < ITEM_COST > 8879.02 < / ITEM_COST >
    < MATERIAL_COST > 631.09 < / MATERIAL_COST >
    AUD < CURRENCY_CODE > < / CURRENCY_CODE >
    < PO_UNIT_PRICE > < / PO_UNIT_PRICE >
    < TRANSACTION_RECEIPT_DATE > 7 April 09 < / TRANSACTION_RECEIPT_DATE >
    < PO_NUMBER > 982121 < / PO_NUMBER >
    < / G_ASW_REC_DATE >
    < G_ASW_REC_DATE >
    < SNO_CREATED_BY > 1433 < / SNO_CREATED_BY >
    < SNO_REQUEST_ID >-1 < / SNO_REQUEST_ID >
    < VENDOR_LOT_NUM > PO110 < / VENDOR_LOT_NUM >
    < SNO_CREATION_DATE > 25 June 09 < / SNO_CREATION_DATE >
    < SNO_ATTRIBUTE1 > 2008/06/11 00:00:00 < / SNO_ATTRIBUTE1 >
    < > 64265 OBJECT_ID < / OBJECT_ID >
    < INITIALIZATION_DATE > 30 June 09 < / INITIALIZATION_DATE >
    < ORGANIZATION_CODE > 10 < / ORGANIZATION_CODE >
    < ORGANISATION_NAME > NDC - PARTS < / ORGANISATION_NAME >
    < Serial_number > 6510863071 < / Serial_number >
    < ITEM_CODE > 3000.006 < / ITEM_CODE >
    < DESCRIPTION > ALLISON 3000 SERIES WE HWY TRANSMISSION E016392 < / DESCRIPTION >
    ALLISON < MANUFACTURER > < / MANUFACTURER >
    < APPLICATION > home < / APPLICATION >
    < ITEM_COST > 8879.02 < / ITEM_COST >
    < MATERIAL_COST > 631.09 < / MATERIAL_COST >
    AUD < CURRENCY_CODE > < / CURRENCY_CODE >
    < PO_UNIT_PRICE > < / PO_UNIT_PRICE >
    < TRANSACTION_RECEIPT_DATE > 25 June 09 < / TRANSACTION_RECEIPT_DATE >
    < PO_NUMBER > 982121 < / PO_NUMBER >
    < / G_ASW_REC_DATE >
    < G_ASW_REC_DATE >
    < SNO_CREATED_BY > 1433 < / SNO_CREATED_BY >
    < SNO_REQUEST_ID >-1 < / SNO_REQUEST_ID >
    < VENDOR_LOT_NUM > PO130 < / VENDOR_LOT_NUM >
    < SNO_CREATION_DATE > 25 June 09 < / SNO_CREATION_DATE >
    < SNO_ATTRIBUTE1 > 2008-06-13 00:00:00 < / SNO_ATTRIBUTE1 >
    < > 64275 OBJECT_ID < / OBJECT_ID >
    < INITIALIZATION_DATE > 30 June 09 < / INITIALIZATION_DATE >
    < ORGANIZATION_CODE > 10 < / ORGANIZATION_CODE >
    < ORGANISATION_NAME > NDC - PARTS < / ORGANISATION_NAME >
    < Serial_number > 6510875487 < / Serial_number >
    < ITEM_CODE > 3000.006 < / ITEM_CODE >
    < DESCRIPTION > ALLISON 3000 SERIES WE HWY TRANSMISSION E016392 < / DESCRIPTION >
    ALLISON < MANUFACTURER > < / MANUFACTURER >
    < APPLICATION > home < / APPLICATION >
    < ITEM_COST > 8879.02 < / ITEM_COST >
    < MATERIAL_COST > 631.09 < / MATERIAL_COST >
    AUD < CURRENCY_CODE > < / CURRENCY_CODE >
    < PO_UNIT_PRICE > < / PO_UNIT_PRICE >
    < TRANSACTION_RECEIPT_DATE > 25 June 09 < / TRANSACTION_RECEIPT_DATE >
    < PO_NUMBER > 982121 < / PO_NUMBER >
    < / G_ASW_REC_DATE >
    < / LIST_G_ASW_REC_DATE >
    < CF_SORT_BY > manufacturing, the Date of receipt, organization, Code section < / CF_SORT_BY >
    < CF_SERIAL_WHERE > < / CF_SERIAL_WHERE >
    < / RECDTREP >

    HELLO Manu,

    7 April 09
    It is not a date,
    If you need to change the query to get the format to the xsd format: YYYY-MM-ddTHH + hh: mm

    otherwise, you need to write a custom sort function to decode and order it.
    If you make custom order and use

    the data will be processed as a string and you will see that the line is sorted on the channel.

  • My computer has a problem so that the dates are wrong, but he created a large number of captures instant wrong date

    Because now when I create AWR report, the dates of these snapshots are all wrong.  How can I remove those?

    You can use snapshot of packages specified with the id of component snap-in:

    BEGIN
    DBMS_WORKLOAD_REPOSITORY. DROP_SNAPSHOT_RANGE (low_snap_id-online 12, high_snap_id-online 40);
    END;

    Which will remove the clichés with ID between 12 and 40.

    K

  • XTTS - problem by copying the data file in ASM

    I test the migration of database from AIX to Linux using the cross-platform transportable tablespaces.
    DB version: source: 10.2.0.4
    Destination: 10.2.0.5
    OS version: source: AIX6.1 - AIX - Based Systems (64-bit)
    Destination: RedHat Linux - Linux x 86 64-bit

    I have run the commands before copying the file data to destination below.
    EXECUTE DBMS_TTS.TRANSPORT_SET_CHECK('TBLSP1,TBLSP2', TRUE);
    
    SELECT * FROM TRANSPORT_SET_VIOLATIONS;
    
    no rows selected
    
    alter system archive log current;
    
    alter tablespace TBLSP1 read only;
    
    alter tablespace TBLSP2 read only;
    
    expdp DUMPFILE=xtts_exp.dmp DIRECTORY=DUMP_DIR logfile=xtts_exp.log TRANSPORT_TABLESPACES=TBLSP1,TBLSP2
    
    CONVERT TABLESPACE TBLSP1,TBLSP2 
    TO PLATFORM 'Linux x86 64-bit'
    FORMAT '/dataimport/%U';
    /DataImport is a shared file system mounted on Linux server and am able to see the file of data out there. But receive the error below to try to copy the data file on the linux server. Could someone let me know if I missed something / how to fix this error.
    $rman target /
    
    RMAN> copy datafile '/dataimport/data_D-DBMGRT_I-3320277811_TS-TBLSP1_FNO-26_05m8miia' to '+DATA';
    Starting backup at 05-APR-11
    using channel ORA_DISK_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of backup command at 04/05/2011 10:19:44
    RMAN-20201: datafile not found in the recovery catalog
    RMAN-06010: error while looking up datafile: /dataimport/data_D-DBMGRT_I-3320277811_TS-TBLSP1_FNO-26_05m8miia

    To be honest, I don't really see what you have done in the op, so I can't really comment on. I see you have an export of the TTS, but that's all.

    If you have followed all the list I mentioned (you did write the TTS reading?), then you can try to save the file with RMAN, but I suspect that it does not work. Do you get the error even if you move the shared location (/ donneesimporter) to a local directory on the target area? Maybe he doesn't like the fact that it's a NFS mount (or whatever the proportion is).

    Or maybe it's because you going to 10.2.0.4 10.2.0.5. I have always had the same group of patches and updated once I had plugged the tablespaces on the target database.

Maybe you are looking for