Loading Tree Node/Leaf causing numerous errors

Question

I am loading a tree with UNSPSC codes using an application engine program with code borrowed from a delivered app engine program. The code loads most of the codes, however I receive numerous errors as follows:
Node not Found (92,3209) - I get this a lot but the data still loads in both PSTREENODE and PSTREELEAF
Return: 805 - ORA-00001: unique constraint (FS.PS_PSTREELEAF) violated
Failed SQL stmt:UPDATE PSTREELEAF SET TREE_NODE_NUM = :1, OLD_TREE_NODE_NUM = 'N' WHERE SETID = :2 AND SETCNTRLVALUE = :3 AND TREE_NAME = :4 AND EFFDT = TO_DATE(:5,'YYYY-MM-DD') AND OLD_TREE_NODE_NUM = 'Y' AND TREE_NODE_NUM = :6
Tree Save error (92,3061)
-- This error will rollback my changes to my last commit point, which, because of this error, I am committing after every value (saving tree, closing tree, and reopening the tree).
Node index error (0,0)
Node insert error (0,0)
-- These errors still allow me to enter the data.
A node without a parent was detected: %1 (25,22)
-- This error causes an abend.
The code used to update the tree is very simple (this code was copied verbatim from PV_CP_LOAD along with additional functions):
REM ****************************************************************************************;
Function AddToTree(&CAT_ID, &CAT_ID_PAR, &CAT_NAME, &ACCOUNT, &SIBLING)
REM ****************************************************************************************;
rem Add child to parent;
If &CAT_ID <> &FIRST_NODE Then
&MYNODE = &MS_TREE.FindNode(&CAT_ID, "");
If None(&MYNODE) Then
&MYNODE = &MS_TREE.FindNode(&CAT_ID_PAR, "");
If All(&MYNODE) Then
&NEWNODE = &MYNODE.InsertChildNode(&CAT_ID);
If All(&NEWNODE) Then
&NEWLEAF = &NEWNODE.INSERTDYNCHILDLEAF();
&NodeCount = &NodeCount + 1;
End-If;
End-If;
Else
rem in case tree node is already there, but category isn't;
rem addcategories(&CAT_ID, &CAT_NAME, &ACCOUNT, &CATEGORY_REC);
End-If;
End-If;
End-Function;
I am getting roughly 50% failure rate.
Is there a database issue? Configuration of my Tree?

Answer 1

What I discovered is that Node API method INSERTDYNCHILDLEAF tries to re-number all the leafs inserted each time it is called. However, it doesn't check to see if the TREE_NODE_NUM already exists. Since the TREE_NODE_NUM column is a key, it causes a unique constraint error.
I pointed this out to Oracle, however, since I was using this function in a custom app engine program, they would not look at the problem. My app engine trace clearly showed the problem.
I ended up re-writing the program to insert directly into the PSTREENODE and PSTREELEAF tables, controlling the TREE_NODE_NUM and PARENT_NODE_NUM columns myself. The result was a tree with 20499 rows with 0 audit errors.