Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

VS2015 / SSRS - ORA-01008 Not all variables bound

VS2015 / SSRS - ORA-01008 Not all variables bound

VS2015 / SSRS - ORA-01008 Not all variables bound

We are converting our VS2008 reports to VS2015 and have come across an issue where some (not all) reports that have parameters are throwing an error ORA-01008 Not all variables bound. I have banged my head against the wall trying to figure out what is causing this. I ended up creating a brand new very simple report to see if I could figure this out, but no luck. Any help or suggestions would be appreciated
Data Source:

Report Parameter:

Data Set Properties:

Query window:


I know the simple query works because if I hard code the value instead of passing a parameter it works:

RE: VS2015 / SSRS - ORA-01008 Not all variables bound

The error message appears to be an Oracle error dealing with parameters in a query. I do not know much about Oracle, so I am not much help. Also your screen shots are pretty small and hard to read, but I do not see the parameter name in the query preceded by an ampersand (i.e., @personnum).

RE: VS2015 / SSRS - ORA-01008 Not all variables bound

Yes it is an Oracle error. The parameter is preceded with an ':' as that is what Oracle wants as opposed to the '@' which is a SQL Server thing. Thanks!

RE: VS2015 / SSRS - ORA-01008 Not all variables bound

Okay, did not know that. Go figure.

RE: VS2015 / SSRS - ORA-01008 Not all variables bound

Hi klkuab,
We are migrating our SSRS reports from 2008 to 2017 using the same type of data source and I have EXACTLY the same issue with our parametric reports, turning slowly crazy...
I am wondering if you got any kind of fix / workaround for that in the meantime? Thanks!

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close