This works for me on Oracle 19c using a linked server on SQL 2019:

SELECT * FROM OPENQUERY(LINKEDSERVERNAME, 'SELECT CAST(DBMS_LOB.SUBSTR(FIELD_NAME, 4000,1) as VARCHAR2(4000)) as DATA_CLOB,
CAST(DBMS_LOB.SUBSTR(FIELD_NAME, 4000,4001) as VARCHAR2(4000))...

• This reply was modified 3 years, 3 months ago by  Rooster.

Right click on the solution and select properties.  Under Configuration Properties -> Debugging change "Run64BitRuntime" to False and try again.  The drivers you have installed are most likely 32bit not...

If you have a remote distributor setup it must also be set as a publisher.  Not having this set will produce error 20036.

The Workaround:
To get around...

.

I've managed to resolve this by creating a factless fact table and defining many to many dimension relationships. To add the season into the product dimension would mean I...

That's fixed it! Many thanks

I found a way around this - I had a window of downtime where nothing was happening on any of the servers.

First I setup the new server as a publisher...

Is the operating system 64bit? If so try selecting "Use 32 bit runtime" from the Execution options tab in the SQL Server Agent job. This is found by...

Did you find out what was causing this? I have a client that is experiencing the same issue....

Looks like someone had added an expensive update to the summary table which used a cursor and sent values into a function. I simplified this with a single statement...

The execution plans are using the correct indexes as far as I can see

SP4 is installed - I'm just trying a disk defrag at the moment before doing an index...