Error dumping sequence values - Forum - OpenEdge RDBMS - Progress Community

Error dumping sequence values

 Forum

Error dumping sequence values

  • Anyone ever seen this before when dumping sequence values in OE10.2B08? 

    ** Unable to understand after -- "asat-link-number CURRENT-VALUE". (247)
    ** Item must be expression, SPACE phrase, or SKIP phrase. (406)
    ** c:\tmp\p06738.adm Could not understand line 1. (198)
    ** Unable to understand after -- "rb-next-report CURRENT-VALUE". (247)
    ** Item must be expression, SPACE phrase, or SKIP phrase. (406)
    ** c:\tmp\p06738.adm Could not understand line 2. (198)
    ** Unable to understand after -- "s-contact CURRENT-VALUE". (247)
    ** Item must be expression, SPACE phrase, or SKIP phrase. (406)
    ** c:\tmp\p06738.adm Could not understand line 3. (198)
    ** Unable to understand after -- "s-id-number CURRENT-VALUE". (247)
    ** Item must be expression, SPACE phrase, or SKIP phrase. (406)
    ** c:\tmp\p06738.adm Could not understand line 4. (198)
    ** Unable to understand after -- "s-report-sequence CURRENT-VALUE". (247)
    ** Item must be expression, SPACE phrase, or SKIP phrase. (406)
    ** c:\tmp\p06738.adm Could not understand line 5. (198)
    ** Unable to understand after -- "user-menu-item-id CURRENT-VALUE". (247)
    ** Item must be expression, SPACE phrase, or SKIP phrase. (406)
    ** c:\tmp\p06738.adm Could not understand line 6. (198)

  • I've sorted it, but it's an odd one. I had my logical DB names set as '1' and '2' as I'm migrating settings from 1 to 2 as part of a D&L process. If I change the logical names to pctrl1 and pctrl2 it works fine. So something to do with this evidently?

  • Documentation says about Logical Database Name (-ld): "The first character must be an uppercase or lowercase letter". Hence  '1' and '2' are not valid names. But Progress allows to use only digits with the -ld parameter while the compiler (when it's used to compile on fly as with the sequences) does not like such names:

    pro sports -ld 1

    **Unable to realise FRAME f_Buffers. (4025)

  • Thanks George. Surprising I've never come across that before.