IIRC: This was discussed several years ago. All stringy partition limits are now stored in
LIMITKEY with string delimiters. Existing values were not changed.
James Campbell
On 21 Oct 2022 at 19:40, Parvathavardhini Kannan via International wrote:
> Esteemed Listers,
> Is there any change to the way DB2 stores the timestamp value with V12 ?
> When we perform partition rotation for a table partitioned on timestamp column, the new limitkey values showup with single quote around them.
> But the existing LIMITKEY values with timestamp column does not show single quote around them.
> For example :
> PARTITION 115
> ENDING (2022-12-31-23.59.59.999999) === > before partition rotation
> INCLUSIVE
> PARTITION 116
> ENDING ('2023-01-07-23.59.59.999999') ===> After partition rotation.
>
> Any idea why it is occurring like this ?
>
> ------------------------------
> Thanks and regards,
> Parvathavardhini Kannan Kyndryl
> ------------------------------
>
Original Message:
Sent: 10/21/2022 3:41:00 PM
From: Parvathavardhini Kannan
Subject: DB2 zos V12 TIMESTAMP
Esteemed Listers,
Is there any change to the way DB2 stores the timestamp value with V12 ?
When we perform partition rotation for a table partitioned on timestamp column, the new limitkey values showup with single quote around them.
But the existing LIMITKEY values with timestamp column does not show single quote around them.
For example :
PARTITION 115
ENDING (2022-12-31-23.59.59.999999) === > before partition rotation
INCLUSIVE
PARTITION 116
ENDING ('2023-01-07-23.59.59.999999') ===> After partition rotation.
Any idea why it is occurring like this ?
------------------------------
Thanks and regards,
Parvathavardhini Kannan Kyndryl
------------------------------