ansaurus

Question

Query SQL Server from Oracle - force metadata refresh

Answer 1

A:

Maybe you can do?:

alter view <<view_name>> compile;

I haven't tested this because I have no db link from Oracle to MSSQL.

tuinstoel 2009-05-16 18:37:45

I will try first thing on Monday.

Bill 2009-05-16 21:23:24

Answer 2

+1 A:

This sounds like an issue with TOAD, not oracle. What happens if you do it in SQL*Plus?

Matthew Watson 2009-05-17 01:38:25

Same thing happens in SQL*Plus. If I exit and get back in, it works just fine. Must be caching metadata on the connection object.Next test, I queried the view in TOAD, changed it, queried it again. It failed. Then I opened a second connection. Query ran just fine. Must be on the connection object.

Bill 2009-05-18 20:46:26

what happens if you do a commit/rollback in your session?

Matthew Watson 2009-05-19 00:58:09

Nope. Nothing short of killing the connection forces the metadata refresh. Must be something in the Oracle client configuration - which is controlled by our Operations staff. I will discuss with them.Thanks Matthew and tuinstoel for the help.

Bill 2009-05-19 18:45:24

Answer 3

A:

This seems to be an issue with the Oracle 10g client. The current solution is to disconnect and reconnect. Given that I haven't been able to find anyone else with this problem, i will assume that it is a problem with my client config.

Bill 2009-05-21 14:53:55

ansaurus

tags:

views:

answers:

Query SQL Server from Oracle - force metadata refresh

related questions