We have recently created a new database instance for an upgraded application. When we try to connect to the DB using ODBC from Excel it returns a "ORA-01017: invalid username/password; logon denied" error.
I am able to successfully logon to the database with SQL+ from the command line using the same username and password.
If I switch back to the previous database I can connect successfully using Excel.
Does anyone know what if anything needs setup on the new DB to allow it to accept the ODBC connection.
Something springs to mind years back when we first set this up about either username/passwords being converted to uppercase when trying to connect so both the USERNAME and PASSWORD are set to uppercase. I'm not sure whether anything else is needed server side or not.
Any help would be greatly appreciated.
ORA-01017: invalid username/password is always because of wrong username password combination.
Quite likely that the password is not in the right case in your Excel.
For the case sensitivity, check the SEC_CASE_SENSITIVE_LOGON parameter in the DB.
If parameter is set to true, passwords are case sensitive.
The issue isn't to do anything with the database, it is the connection string I'm using to connect to the database. It's using the old instance instead of the new one!!! I need to look at why that is using the old one when tnsnames is setup to point to the new one.
Related
I have a script from BluePrism to reset my "admin" password. It is the Learning edition 6.9.0.
What I can't figure out is how to actually apply that script to the BluePrism database.
I have MySql installed on my PC and I was hoping I could that to run the scripts, but I can't find an option to connect MySql to the blueprism database.
I can find the BluePrism database no problem, but MySql won't recognise it as a database file.
I have also tried setting up a new connection inside BluePrism itself but to no avail.
Thanks in advance for any assistance.
Here is a Solution that works for me.
This isn't the official script distributed by Blue Prism (as #Jerry
pointed out the existence of), but one I've used against several
installations to force a reset of the password.
Blue Prism v6 This finds the user with the username admin and resets
their password back to the original admin string. It will force a
password change for admin on their next login.
USE blueprism
UPDATE BPAPassword SET salt = '', hash = '208512264222772174181102151942010236531331277169151', type = 0
WHERE userid = (SELECT userid FROM BPAUser WHERE username = 'admin')
Also here is a video with another process that changes it to another password, maybe you could try it, if the first solution does not work or if you like a more visual resource.
I have create a node-pro with node+mongoose+mlab on backend,and vuejs on frontend, it worked on local, however, server can not connected to mlab or mongo.
My server system is Ubuntu, with Nginx server
and server did not worked
I have created a new user named 'Orton', and update it on my app.js, it also works.
I don't know if I need to set anything else?
It's only the case of entering proper credentials and it will work. You must be entering wrong credentials. Beware! It's different than your mongolab username and password. See what is your username for that particular database.....To fix it,
Go to mongo lab proper database, and then click on Users tab and enter the username shown here as username in the mongolab url and then enter the password. The password which you entered while creating that particular database is your password here for mongolab url.
If User's tab does not contain any database user, then you can add the user from the right side tab in corner.
Here's an image for your help.
I solved this problem:
My server's security group rules' port should be opened, it was why logged network error.
We've discovered that our secondary is not authenticating properly after having the primary fail over to it. We have 2 MongoDB servers (v3.4) both properly setup in a replicaset:
mongo1:27017
mongo2:27017
And our connection string (for Node.js's MongoDB driver v2.2.19), is like this:
mongodb://username:password#mongo1,mongo2/db?replicaSet=rs0
Now, our primary failed and the secondary, mongo2 was elected primary. However, DB calls failed with 'not authorized' errors. So I took another look at the MongoDB docs:
mongodb://[username:password#]host1[:port1][,host2[:port2],...[,hostN[:portN]]][/[database][?options]]
It looks ambiguous, could the username:password be needed for each host? But that's weird because they are all replicated so the users should be the same, right?
I even tried it, using this connection string in the application:
mongodb://username:password#mongo1,username:password#mongo2/db?replicaSet=rs0
But that fails with: Error: Username with password containing an unescaped colon
The username and passwords are alphanumeric, so there seems to be a parsing problem with that style URI. But with the original, it's not authenticated properly. So these problems seem at odds with each other. I have verified in standalone mode that the user exists on both servers, and has the proper permissions. So I'm not sure where the problem lies. I found another very similar question with a different driver, but no answers :(
Well, I could never figure this out but updating the Node.js driver (v2.2.19 -> v2.2.33) seems to have fixed it. I didn't see anything relevant in the changelog and I'm not interested enough to compare diffs. C'est la vie de programming.
To connect to MongoDB, you need to use http://mongodb.github.io/node-mongodb-native/2.0/api/MongoClient.html#.connect.
My question is about specifying the database in the connection string. It says:
Optional. The name of the database to authenticate if the connection string includes authentication credentials in the form of username:password#. If /database is not specified and the connection string includes credentials, the driver will authenticate to the admin database.
It seems to me that it's only useful to have the database if you also have the username:password#. But I've seen examples where the database is specified without the username:password#. The Node Driver example itself uses the string mongodb://localhost:27017/myproject.
Why would you ever want to have the database without the username:password#?
All the operation you will do will be done in the database you are choosing.
If you avoid the /database component you need to force it in the code (try to avoid hard coded elements) or you will work in the default database (not a great idea)
I'd like to use the MongoClient.Connect(Url) option for connecting from Node and in fact it does work for authenticated connections to the admin database. However, if I try to specify a different database I get an "auth Fails" with code 18.
I think this means that the credentials are only setup on the admin database and, unfortunately, I can't change this arrangement (for now, anyway).
It seems this Url syntax is the direction the driver is heading, so I'd like to use it if possible. Is there a way to use this syntax, authenticate and connect to the admin database, and then get a connection to one of the other databases on the server?
I just found out how to do this: You use the instance you get ("admin") to open another database you have access to:
db2 = db.db("name of other name");
See it hidden inside the documentation