Author: RahulG31
Subject: Reply to: how to specifiy partition endings when 1st col is nullable?
Posted: Thu Oct 27, 2016 1:20 am (GMT 5.5)
I think, you have wrongly mentioned the sqlcode as -635. It should have been -636:
http://www.ibm.com/support/knowledgecenter/SSEPEK_10.0.0/codes/src/tpc/n636.html
And, this is where you are going wrong (assuming ascending order Since you are using MAXVALUE at both places i.e. as start value and end value for date column):
I am not good at this but probably you can make your hard-coded dates in descending order till MINVALUE to see if that helps.
Or make use of MINVALUE in Parent_id column? Play with some MINVALUE/MAXVALUE in both columns and try to do ascending/descending to see if anything changes.
.
Subject: Reply to: how to specifiy partition endings when 1st col is nullable?
Posted: Thu Oct 27, 2016 1:20 am (GMT 5.5)
I think, you have wrongly mentioned the sqlcode as -635. It should have been -636:
http://www.ibm.com/support/knowledgecenter/SSEPEK_10.0.0/codes/src/tpc/n636.html
And, this is where you are going wrong (assuming ascending order Since you are using MAXVALUE at both places i.e. as start value and end value for date column):
| Quote: |
| Once MAXVALUE is specified, all subsequent columns must be MAXVALUE. |
I am not good at this but probably you can make your hard-coded dates in descending order till MINVALUE to see if that helps.
Or make use of MINVALUE in Parent_id column? Play with some MINVALUE/MAXVALUE in both columns and try to do ascending/descending to see if anything changes.
.