Table Partitioning: date format error when create Partition Policy Details - Forum - OpenEdge RDBMS - Progress Community

Table Partitioning: date format error when create Partition Policy Details

 Forum

Table Partitioning: date format error when create Partition Policy Details

This question is answered

Hello,

When I try to create partition policy detail through Database Administration Console I get next message:

1. Select Date (no error):

2. Click Commit (error occurs):

In %DLC%/startup.pf 

-E
-d dmy
-lng "English"
-cpcase Basic
-cpcoll Basic
-cpinternal iso8859-1
-cpstream iso8859-1

I tried to change -d to "ymd" - the same error.

What else there are settings for the dates in OEM?

Verified Answer
  • I can see the same problem when for example doing load partition ..... with -d dmy in DLC\startup.pf.

All Replies
  • Just a guess - what are the regional settings on the machine where the browser is ?

  • Hi Libor,

  •  
    I believe the date format for TP is restricted to mm/dd/yyyy regardless of regional settings.
     
     
    From: Valeriy Bashkatov [mailto:bounce-Arelav2@community.progress.com]
    Sent: Tuesday, September 30, 2014 7:43 AM
    To: TU.OE.RDBMS@community.progress.com
    Subject: RE: [Technical Users - OE RDBMS] Table Partitioning: date format error when create Partition Policy Details
     

    Flag this post as spam/abuse.

  • This error does not depend on the regional settings.

    Pic from the server

  • It is depend on -d startup parameter in %DLC%/startup.pf

    When I changed it to "mdy" and then restart the AdminServer -  the error not occurs.

    When I returned to the old value "dmy" - the error occurs again.

    Also, now I see this error when I open a page Edit Partition Policy Details, where previously I created some partition details:

    And this is a bad and strange - I think that it is a BUG.

  • I can see the same problem when for example doing load partition ..... with -d dmy in DLC\startup.pf.

  • This does appear to be a bug.

    I recommend reporting it to Tech Support so it can be investigated.

  • Ø  I recommend reporting it to Tech Support so it can be investigated.

    That would be me.