Well you know the obvious answer is have one metadata server 😉
But as you have said you cant change this.
If you have SAS Connect licensed you should be able to remote submit the SAS code from one workspace to the other, that would allow the Workspace server on the Oracle side pass a query to the workspace server on the Teradata side, using the SAS/Access to Teradata engine.
The issue is if you try and swap metadata servers mid processing then the SAS work file that have written to the Oracle/Workspace server will no longer be available amd vice versa.
If you wrote temporary SAS Datasets to a physical shared file path (accesable via EG) rather than a metadata based path that might work.
Or have two eg project's one doing the Oracle call and the other doing the teradata call and then call one within the other (somehow).
Or you could maybe do a manual metalib statement to define a libname on the Teradata Metadata server from the Oracle one.
Lots of maybe's but you would need to test each one to see if any work.
Interesting problem though...
... View more