CODEWITHSUNDEEP
oracle-sqldeveloper
Harry Hoffhines
Harry Hoffhines

Reputation: 153

SQL Developer returns query results on one computer but not on another

I can run a query on views in SQL Developer 3.1.07 and it returns the results I expect. My co-worker, who is in Mexico using the same user, can connect to the same database, sees the same views, runs the same query and gets no results, even from a simple "select * from VIEWNAME" query. The column headers display, but no data. If he selects a view from the connections window and selects the DATA tab no data displays. This user does not have access to any tables on this specific database.

I'm not certain he is running the same version of Developer, but it's not far off. I have checked as many settings in SQL Developer that I think could be the issue, but see no significant difference in his settings from mine.

Connecting to another database allows him to access data in both tables and views

Any thoughts on what we're missing?

Upvotes: 1

Views: 4319

Answers (4)

Adwait Mathkari
Adwait Mathkari

Reputation: 140

I was facing the same issue, turned out that the update to the database from my sqldevelolper was not commited to the main database, that's why, I was getting results on my sqldeveloper for that query, but from aws it was returning empty results. When I chatted with DBA, he could find stale data. After I committed the data from my sqldeveloper, the db was actually updated.

Upvotes: 0

bluehilltech
bluehilltech

Reputation: 31

Faced the same which got resolved when I checked the 'skip NLS settings' box. My query was returning zero results earlier but when I ran the same query again, I could see the table rows.

Since your co-worker is in a different country, most probably the NLS settings (related to the language) are the culprit here.

Upvotes: 2

snapple
snapple

Reputation: 21

I know I'm a few years late, but check if the underlying view doesn't filter on something that is based on localisation! I just had the issue and it turned out to be a statment like this that was causing issues:

SELECT * 
FROM sometable
WHERE language = userenv('LANG')

Upvotes: 2

Neelima
Neelima

Reputation: 1

Copy the JDBC folder from your oracle home and copy it over to your c-workers machine. we had the same issue and replacing the JDBC folder worked.

Upvotes: 0

Related Questions