Wow, now this was a perplexing situation.
Calling a procedure which executes 2 merge statements, almost identical, yet only the second one was returning the error message. I really have to thank Oracle for their descriptive error messages on this one, took a little bit of searching but managed to get it sorted.
Seems merge statements only like 1:1 or 1:0 matches and doesn't handle 1:many so updating a master record with multiple children (monthly payments) is a no go. Luckily slapping it in a loop that issues a merge for every month does the job and makes me go home happy.
God bless fast fingers and good resources.
No comments:
Post a Comment