numcheckpointstats does not work - Forum - OpenEdge RDBMS - Progress Community

numcheckpointstats does not work

 Forum

numcheckpointstats does not work

This question is answered

Every time I try something new Progress bites me back.

This time I tried a new parameter -numcheckpointstats

Since it is not in 11.6 documentation and it is in 11.7 documentation, I assume it is a brand new one.

When starting sports database with -numcheckpointstats 64 I am getting the following error and sports database does not start.

$ proserve -pf sports.pf

OpenEdge Release 11.7.1 as of Wed Jun 14 19:00:30 EDT 2017
08:39:55 SERVER : ** Could not recognize argument: -umcheckpointstats. (301)

It does not work without -pf file, on a command line also

$ proserve -pf sports.pf -numcheckpointstats 64

OpenEdge Release 11.7.1 as of Wed Jun 14 19:00:30 EDT 2017
08:51:25 SERVER : ** Could not recognize argument: -umcheckpointstats. (301)

Use Number of checkpoint statistics (-numcheckpointstats) to specify the number of rows maintained in

the_Checkpoint VST. 

Multi-user default is 32

OpenEdge 11.7.1 on IBM AIX 7.1

Dmitri Levin

Alphabroder

Verified Answer
  •  
     
    Please try it this way:
     
     
        -numCheckpointStats
     
     
     
     

    Ken Meehan

    meehan@progress.com

  • Dmitri, this is a doc bug.  Try "-numCheckpointStats".  

All Replies
  •  
     
    Please try it this way:
     
     
        -numCheckpointStats
     
     
     
     

    Ken Meehan

    meehan@progress.com

  • Dmitri, this is a doc bug.  Try "-numCheckpointStats".  

  • Is just me or is there something wrong with the error as well, -umcheckpointstats. (301)  (NO N at the beginning).  perhaps try starting with what the error is using -umcheckpointstats

  • Thank you. -numCheckpointStats works fine. Doc need to be fixed.

    Dmitri Levin

    Alphabroder

  • > Is just me or is there something wrong with the error as well, -umcheckpointstats. (301)  (NO N at the beginning).

    The problem is not particular to this parameter.  It's a limitation in the parameter-parsing logic that it often gives error messages that don't make sense when dealing with misspelled parameters.

  • Examples:

    proserve sports -prefetchfactor

    You have not supplied a parameter for argument -p. (1403)

    proserve sports -prefetchfactor 100

    You have not supplied a parameter for argument -e. (1403)

  •  
     
    I opened new doc issue for this:
     
    Issue:PSC00365117
     
     
     

    Ken Meehan

    meehan@progress.com

  • Thank you Ken

    Dmitri Levin

    Alphabroder