Hi Raj,
Thanks for your response.
For our application we are running the command with jdbc and use the full connection string listing all hosts. When using jdbc we are getting this error whenever we list all hosts. We need to do this because we have a requirement for high availability where an active node (including the primary) could be a failover node.
Otherwise we would have to run a query to figure out what the actual primary is and have a different connection url for export from our normal jdbc url.
Thanks,
Jason