Invalid parameter binding(s

[DALE STOCKMAN]

Ok - here's an odd one:

• Two custom portlets, based on custom queries
• Security clauses are disabled on both
• Portlets both display perfectly well on my machine, and on others
• Have one user where the two portlets do no display - only "Error" is shown (below)
• Error message in log:  Invalid parameter binding(s)
• NSQL preview generates no errors.
• Have restored dashboard, portlets, removed portlets, put them back on, published, cleared caches, tried in different browsers (Chrome, IE, Edge)
• Oh, and when IT logs in as the user from a different machine, everything works fine for the user

Ideas?



------------------------------
Dale Stockman
Tech Specialist-Project Systems
ZF
------------------------------

[David Morton]

Colons?

In that, the unhelpful "invalid parameter bindings" message is one I only ever see when I have inadvertently left a colon in the NSQL (eg using a SQL parameter format rather than a NSQL parameter format). Not sure that your description of the symptoms is the same scenario though, but it might be a flavour of the same underlying problem, that some errant colon has made its way into the parsed SQL at execution time - perhaps in some data being passed it as a parameter or even in the data retrieved by the query?

The mysteries of exactly how and when NSQL gets parsed into SQL is something beyond my comprehension but this might give you a clue?

[DALE STOCKMAN]

Thanks David – some ideas to kick around.

 

The odd part is that the two portlets use queries that are quite different, have default filter parameters set (so that when users first bring them up, they all see the same thing). 

 

• Works every time for me
• Never works for the guy sitting 30 feet away from me
• And, it works when we login as him from a different machine

 

Maybe I'll change the options to present results until filtering – see if the portlet comes up, see what appears in his filter fields before hitting filter?

 

 

 

[David Morton]

• Oh, and when IT logs in as the user from a different machine, everything works fine for the user

- some local PC settings then perhaps? ; can you try logging in as (eg) your user on the odd-machine - if that gets the error then I'd start looking at the browser settings on that PC (locale, languages) - (can you try a different browser as the odd-user?) and the operating system settings (languages and so on).

Your symptoms are all very odd though. :(

[DALE STOCKMAN]

We've tried different browsers (Chrome, Edge) on the user's machine with the same result.  Haven't tried logging in as myself on his machine.  Will try this.  Also, will try the "F12" thing while he's logged in – maybe there will be something posted there that will be helpful.

 

It is a new machine.  He sits 30 feet away – same operating system, English.  Will check other settings.

 

I've changed the portlets to not display anything until filtering is initiated by the user.  Now, I need to go see if the portlets display initially, and then generate the error only after filtering is initiated.  That will at least confirm if filter parameters are the right area to be looking at.  And, I should be able to see the default values picked, before initiating the filters.

 

Glad you agree that this one is very odd.  These are the ones I like to bring to the community!  More fun!

 

[Suman Pramanik]

Hi Dale

Have seen this some time and we had to work with DBA to flush the plan which bad query was generating and then it fixed. Also saw a problem with data direct drivers and in clarity we use data direct drivers too. https://knowledgebase.progress.com/articles/Article/3000

It will be best to get some advance trace at database level and engage oracle to see if they can help.


------------------------------
Thanks & Regards
Suman Pramanik
Principal Support Engineer | Customer Success & Support, Enterprise Software Division
Broadcom
------------------------------

[DALE STOCKMAN]

Ok, with 'Don't display results until filtering' set, the two problematic portlets displayed correctly, without data, as one would expect.  Upon filtering, a new error message was generated:

 

 

Before, we were getting just "ERROR Contact System Administrator."  Looking into logs, now, to see if the message in the log is any different, more informative.

 

Prior to filtering, did not see anything in the selected parameters different from my login, or the login of others, where this is working.  Also, we had a DB restart at noon, related to a unrelated issue – and we had no luck as the restart did not help us with this issue (but it did fix the issue which called for the restart).

 

I then logged into Clarity on the user's machine, same browser, using my login – and, everything worked fine, no errors. 

 

Will get the error log, next.  Also, expect we will run an SQL trace with the user logged in on his own machine, once he is free (Friday?).  For now, that's what we know.