Remove the views that have Oracle spevcific syntax in them from the host.Create the remote and then add the views back in to the host. Since 7.5.x not sure exact version, all views are now sent to the remote, since the syntax recognized by SQL it ill error out.
I had discovered that any Oracle specific views (ones that would not be valid in SQLServer) were causing an issue for cutting. After removing these, I had success. It does not matter that they are not enabled.
SLX told me this was by design. It did not work this way in 7.2. Personally I think if a view is not enabled, then it should be ignored by the database cuts as before. We have several views for 3rd party apps and reporting that will now have to be re-worked to be compatible with SQLServer, or moved to another schema.
