Seeing errors in the log when doing a simple select object operation.

I've been seeing a lot of these errors in the log when doing a simple SDM select object operation. The operator appears to be configured correctly and the operation completes successfully but under the hood there is definitely something not happy here. Is there anything that can be done about this?

I believe these errors are occurring because of extra values that are filled in somewhere but not in use. The above is on the JDBC operator and on the wizard screens. Even if you select one database type, PAM still evaluates all the other values under each database type. Make sure to remove any extra info in the operator that is not in use and that should get rid of these errors.

I believe these errors are occurring because of extra values that are filled in somewhere but not in use. The above is on the JDBC operator and on the wizard screens. Even if you select one database type, PAM still evaluates all the other values under each database type. Make sure to remove any extra info in the operator that is not in use and that should get rid of these errors.

I'm a little confused here. I'm not using a direct query to the database as depicted in the KB article but rather one of the out of the box commands provided for PAM/SDM integration which leans itself on a SOAP call.

This has me thinking though... We have custom fields that we are using. I'm wondering if we are running into a similar sort of issue because we are requesting custom fields that the out of the box soap operator never accounted for?

So I disconnected my SDM select operator essentially accepting to throwing the baby out with the bathwater for getting at the information I need and attempted to use a more direct to the metal approach by selecting directly off the server and implemented that approach outlined in the KB article above. In the end this replaces the Soap related errors that I was seeing before with a whole new set of SQL errors in my logs:

Gotcha, At the heart of the matter is that we have this series of soap calls that we make to assemble some information about the request to make some decisions in how we approach our workflow in PAM. These Soap calls are all generated using the out of the box select object operator not direct SQL communication. These operators are generating the errors per my first comment. My colleague has mentioned that these errors might just be acceptable fall out coming off the operation but at this point I don't have anything to base that assumption off of. Either way at the end of the day I'd like to eliminate all the errors that this process generates prior to going live. Thanks for taking a stab at the matter Andrew. I do appreciate the attention on it.

I'm still guessing that there is something that the operator properties has filled in that isn't in use, but that PAM is reporting in the logs anyway. But if the above suggestions have not helped to pinpoint the error messages, it might be worth opening a support issue so we can help you dig into it a little deeper.