tag:blogger.com,1999:blog-4516533711330247058.post2307480702072951561..comments2024-03-29T05:35:42.451-07:00Comments on Robert's Db2 blog: Db2 for z/OS Partitioned Table Spaces: How the Number of Partitions can Impact PerformanceRoberthttp://www.blogger.com/profile/02058625981006623480noreply@blogger.comBlogger5125tag:blogger.com,1999:blog-4516533711330247058.post-53282986095102564692023-11-12T18:10:53.346-08:002023-11-12T18:10:53.346-08:00I don't know what you mean by "other envi...I don't know what you mean by "other environment." If you are talking about two different Db2 for z/OS systems, and if the same tool or same query is used in both cases to return table partition information, you should get consistent results. I do not know why you appear to be getting inconsistent results, if the circumstances are in fact equivalent.<br /><br />RobertRoberthttps://www.blogger.com/profile/02058625981006623480noreply@blogger.comtag:blogger.com,1999:blog-4516533711330247058.post-87255150538453041702023-11-12T04:49:29.922-08:002023-11-12T04:49:29.922-08:00I faced the same situation like above user in my s...I faced the same situation like above user in my shop.The "PL" option showed below before rotate partition:<br />------------------------<br />DEV1:<br />----------<br />part limitkey logicalpart<br />1 31-05-2023 1<br />2 30-06-2023 2<br />3 31-07-2023 3<br />4 31-08-2023 4<br />5 30-09-2023 5<br />On Executing:<br />Alter table tablename rotate partition first to last ending at ('xxx') reset;<br />It looked like below :<br />part limitkey logicalpart<br />1 31-10-2023 5-->new limitkey replaced old key & moved to top<br />2 30-06-2023 1<br />3 31-07-2023 2<br />4 31-08-2023 3<br />5 30-09-2023 4<br />But same rotate partition command issued in other environment on same table looks like below .how is that possible? Table defintion/structure is all same across environment.<br />part limitkey logicalpart<br />1 30-06-2023 1<br />2 31-07-2023 2<br />3 31-08-2023 3<br />4 30-09-2023 4<br />5 31-10-2023 5----------->stays at bottom with new limitkey,but oldest limitkey is removed.<br />Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-4516533711330247058.post-33203650366024437452023-09-27T05:59:15.685-07:002023-09-27T05:59:15.685-07:00Pretty simple: the CA tool is listing partitions i...Pretty simple: the CA tool is listing partitions in physical order (left-hand side), with the corresponding logical partition to the right. The "IBM site" display is in logical partition order (right-hand side), with the corresponding physical partition to the left. It's just two different ways of looking at the same information.<br /><br />RobertRoberthttps://www.blogger.com/profile/02058625981006623480noreply@blogger.comtag:blogger.com,1999:blog-4516533711330247058.post-74473861911321513632023-09-27T03:15:19.693-07:002023-09-27T03:15:19.693-07:00Rob,below is the screenshot from CA tool vs IBM si...Rob,below is the screenshot from CA tool vs IBM site<br />ca tool:<br />PART LIMITKEYVAL LOGPART<br />1 '2023-11-3> 19<br />2 '2022-05-3> 1<br />3 '2022-06-3> 2<br />4 '2022-07-3> 3<br />5 '2022-08-3> 4<br />6 '2022-09-3> 5<br />7 '2022-10-3> 6<br />8 '2022-11-3> 7<br />9 '2022-12-3> 8<br />10 '2023-01-3> 9<br />11 '2023-02-2> 10<br />12 '2023-03-3> 11<br />13 '2023-04-3> 12<br />14 '2023-05-3> 13<br />15 '2023-06-3> 14<br />16 '2023-07-3> 15<br />17 '2023-08-3> 16<br />18 '2023-09-3> 17<br />19 '2023-10-3> 18<br /> ibm site:<br />PART LIMITKEYVAL LOGPART<br />2 '2022-05-3> 1<br />3 '2022-06-3> 2<br />4 '2022-07-3> 3<br />5 '2022-08-3> 4<br />6 '2022-09-3> 5<br />7 '2022-10-3> 6<br />8 '2022-11-3> 7<br />9 '2022-12-3> 8<br />10 '2023-01-3> 9<br />11 '2023-02-2> 10<br />12 '2023-03-3> 11<br />13 '2023-04-3> 12<br />14 '2023-05-3> 13<br />15 '2023-06-3> 14<br />16 '2023-07-3> 15<br />17 '2023-08-3> 16<br />18 '2023-09-3> 17<br />19 '2023-10-3> 18<br />1 '2023-11-3> 19<br /> My question is:why ca tool shows a different order(first line & last line ) vs what we see from ibm site.which is right? I'm wondering ,may be any other ddl/any statements would have the order displayed in this way in ca tool?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-4516533711330247058.post-28290083861929339262023-09-26T08:48:11.324-07:002023-09-26T08:48:11.324-07:00Hi Rob,
I have pbr table-with part 1 to 19.The log...Hi Rob,<br />I have pbr table-with part 1 to 19.The logical part & physical part was in same sequence(1...19)when I issued below alter<br />ALTER TABLE xxxxxx <br /> ROTATE PARTITION FIRST TO LAST <br /> ENDING AT ('xxxx-11-30') RESET ; <br />COMMIT; <br /><br />the logical part looked like this:<br /> LOGPART <br /> 19 <br /> 1 <br /> 2 <br /> 3 <br /> 4 <br /> 5 <br /> 6 <br /> 7 <br /> 8 <br /> 9 <br /> 10 <br />But in IBM site,-https://www.ibm.com/docs/en/db2-for-zos/13?topic=partitions-rotating<br />it shows as new limitkey value with old part would get listed in bottom.<br /><br />P010 12/31/2005 catname.DSNDBx.dbname.psname.I0001.A010<br />P011 12/31/2006 catname.DSNDBx.dbname.psname.I0001.A011<br />P001 12/31/2007 catname.DSNDBx.dbname.psname.I0001.A001<br /><br />Can you clarify on this? Anonymousnoreply@blogger.com