Home » SQL & PL/SQL » SQL & PL/SQL » ORA-14028
ORA-14028 [message #661470] Sun, 19 March 2017 11:28 Go to next message
angro123
Messages: 2
Registered: March 2017
Junior Member
Hi, I have partitioned table xxx which have one day partitions and one partition PMAX with MAXVALUE argument.
I would like to split PMAX partition (now it has data form few days) into daily partitions , but after SPLIT command I got ORA-14028 error (no AT or VALUES keyword).
But there it is VALUES keyword. Any suggestion?

ALTER TABLE xxx SPLIT PARTITION PMAX INTO
(PARTITION P20170101 VALUES LESS THAN (TO_DATE('2017-01-02','yyyy-mm-dd')),
PARTITION PMAX)

Regards
Re: ORA-14028 [message #661471 is a reply to message #661470] Sun, 19 March 2017 12:49 Go to previous messageGo to next message
Solomon Yakobson
Messages: 2614
Registered: January 2010
Location: Connecticut, USA
Senior Member
And you are incapable to open documentation and check ALTER TABLE SPLIT PARTITION syntax FOR YOUR VERSION? Syntax you are using is available starting 12C.

SY.
Re: ORA-14028 [message #661472 is a reply to message #661471] Sun, 19 March 2017 12:57 Go to previous messageGo to next message
angro123
Messages: 2
Registered: March 2017
Junior Member
Thanks, I did it in UAT where I have v12, on prod there is still v.11.
Re: ORA-14028 [message #661473 is a reply to message #661472] Sun, 19 March 2017 13:00 Go to previous messageGo to next message
BlackSwan
Messages: 25478
Registered: January 2009
Location: SoCal
Senior Member
angro123 wrote on Sun, 19 March 2017 10:57
Thanks, I did it in UAT where I have v12, on prod there is still v.11.
You need to either upgrade Prod to V12 or down grade UAT to V11
Let us know after the requisite change has been completed
Re: ORA-14028 [message #661482 is a reply to message #661472] Mon, 20 March 2017 08:08 Go to previous messageGo to next message
joy_division
Messages: 4755
Registered: February 2005
Location: East Coast USA
Senior Member
angro123 wrote on Sun, 19 March 2017 13:57
Thanks, I did it in UAT where I have v12, on prod there is still v.11.
I cannot stress how dangerous this is. With all of the new features in 12c, you write code, fully test it in QA and then promote it to Production, and then bang, it blows up because your production database does not support code that has been previously written and tested.
Re: ORA-14028 [message #661483 is a reply to message #661482] Mon, 20 March 2017 09:08 Go to previous message
cookiemonster
Messages: 12771
Registered: September 2008
Location: Rainy Manchester
Senior Member
Indeed, UAT should always be exactly the same version as prod, down to having the same patches applied if necessary. It's not just new features you have to worry about - there's also bugs and optimiser changes that'll impact performance.
Dev can be a higher version if you want, just so long as you remember not to implement new features from the higher version.
Previous Topic: ORDER BY Clause error in cursor
Next Topic: Append Hint in oracle
Goto Forum:
  


Current Time: Tue Jun 27 22:52:59 CDT 2017

Total time taken to generate the page: 0.20401 seconds