I don't think that this is the cause of the problem, at least, I have found nothing that documents this
However, I think that it is time to get more resources involved, and I suggest that you open a case with the response center
Make cure that you include that the 'dbkconf' came back with RETVAL*0
