Results 1 to 6 of 6

Thread: UBE sequence and data dictionary size limit

  1. #1
    Senior Member johndanter's Avatar
    Join Date
    Sep 2003
    Location
    Cork, Ireland
    Posts
    1,346

    UBE sequence and data dictionary size limit

    Hi List,

    Does anyone know the maximum size limit E1 has on sequencing data dictionary columns?

    I have a text field which is a HASH summary of an E1 Order. It's a concatenation of ITM, QTY, RLOT, LOTN, LOCN # next line and so on. (all in all about 80 bytes per line, there maybe several lines on the order)

    Example for 2 lines no LOTN LOCN
    4809835,333,,,#5446909,333,,,#

    I then need to sequence and group by this value in order to find similar orders for batching.

    Initially my field was 9000 and I could not sequence on it as the UBe would crash. So I dropped it 2000 and it now works.

    So there must be a size limit?

    Thanks

    John
    John Danter
    You don't go out looking for a job dressed like that do you, on a weekday?

    E900 TR 9.1.5.3 Unix

  2. #2
    Hi john,

    Just a guess here, but could it be because JDE actually creates a BLOB field in the database when a String Data Item has a length over 2000.
    it probably doesn't like doing sequencing on a blob field. is it your case?

  3. #3
    Senior Member johndanter's Avatar
    Join Date
    Sep 2003
    Location
    Cork, Ireland
    Posts
    1,346
    Hi

    Yeah I think I did see a message in a log somewhere about a blob field, but I can't remember
    John Danter
    You don't go out looking for a job dressed like that do you, on a weekday?

    E900 TR 9.1.5.3 Unix

  4. #4
    Senior Member johndanter's Avatar
    Join Date
    Sep 2003
    Location
    Cork, Ireland
    Posts
    1,346
    CNC have realised that when I build the table it's build as an NVARCHAR2 yet when they build it it turns in an NCLOB....but only on one of their FAT clients, not them all.

    So I've fixed this now. But I'd still like to know the limit

    I have sequenced the UBE like this ITM, QTY, RLOT, LOTN, LOCN. So the HASH field follows suit anyway
    John Danter
    You don't go out looking for a job dressed like that do you, on a weekday?

    E900 TR 9.1.5.3 Unix

  5. #5
    Senior Member Larry_Jones's Avatar
    Join Date
    Nov 2000
    Location
    Spokane, WA, USA
    Posts
    3,209
    John,

    it should be based on whichever DBMS has the most restrictive limit.
    For example SQL Server max row size is ~ 8K (excluding BLOBS, CLOBS, etc) but both Oracle and AS/400 exceed that substantially.
    Oracle and SQL Server NCHAR data type max is 4,000 characters. I think AS/400 is 32K.

    Net, net JDE is "supposed" to restrict you to the minimum allowed out of the databases it supports.
    Larry Jones
    E1 9.2 - TR 9.2.2.6 on Win 2016 R2. SQL Server 2016
    Wintel, BI Publisher

  6. #6
    Senior Member johndanter's Avatar
    Join Date
    Sep 2003
    Location
    Cork, Ireland
    Posts
    1,346
    Cheers Larry

    That explains why dropping it form 9000 to 2000 worked.
    John Danter
    You don't go out looking for a job dressed like that do you, on a weekday?

    E900 TR 9.1.5.3 Unix

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
The legal restrictions and terms of use applicable to this site are available here.
Use of this site signifies your agreement to the terms of use.
JDELIST is NOT affiliated with JD Edwards® & Company, Oracle or Peoplesoft. Contents of this site are neither endorsed nor approved by JD Edwards® & Company and, or Oracle.