Hey @Ashwani_Pratap ,
I’m not very sure, but from the logs you provided it’s clear it has something to do with the connection URL.
Could you check the URL if it’s correct?
What I think is after the port number, we should be having database name in the URL separated with a
/ like this:
Now talking about the logs, if you are trying to connect to Oracle database I’m curious about how MongoDB logs/exception logs are coming in picture
Could you please check on this point once?
Talking about the exception message :
The connection string contains invalid user information. If the username or password contains a colon (:) or an at-sign (@) then it must be urlencoded
This exception is thrown when we try connecting to MongoDB database and the connection string or the username or the password contains
@. In such a case, it’s a good practice to encode these values and then use them.
This could be the last thing to try out once.
I hope something out from the above mentioned points works out.