Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 years ago.
Improve this question
I'm trying to upgrade my version of PostgreSQL to 9.2 on a Windows Server OS and I keep getting the following error:
An error has occurred:
Error connecting to the server: FATAL: password authentication failed for user "postgres"
How do I make it not do this and actually connect like it is supposed to? I'm using the exact same password from my older installation.
Running the installer via EnterpriseDB prompts you for a password during the initial setup - This password is the postgres users password:
If you do not remember the password, or if you typed it incorrectly during the install(twice!) try these steps:
edit pg_hba.conf to allow trust authorization temporarily
Reload the config file (pg_ctl reload)
Connect and issue ALTER ROLE / PASSWORD to set the new password
edit pg_hba.conf again and restore the previous settings
Reload the config file again
The files will be located in C:\Program Files\PostgreSQL\9.2\data if you installed to the default path.
You can reload the configuration via PhAdmin III by right clicking on the server name and choosing reload configuration or use pg_ctl reload. Barring that restart the service or reboot.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
I have just instally successfully db2 on my linux machine, but I am not able to create a database.
When I make CREATE DATABASE ABC; I get the error that I haven't the authorization to create it...how can I get this authorization?
When you install DB2, you most probably use the root user of the Linux server.
Then in installing phase, you provide a user which will have the SYSADM and DBADM rights. That means DB2 creates a user which has all rights on the database(database admin).
So, after installation, you have to switch to that user to have rights to create a new database.
Depending on the version you installed, that username might be changed. But DB2 uses db2inst1 by default as administrator user.
Check your /home directory. You will see a new user(most probably db2inst1). Then switch to that user with:
su - db2inst1
then issue:
db2 CREATE DATABASE ABC
Let me know if you have a problem, also please provide your /home directory and the error message you get.
You can check details of create db command and related authorization required here on DB2 Info Center:
http://www-01.ibm.com/support/knowledgecenter/SSEPGG_10.5.0/com.ibm.db2.luw.admin.cmd.doc/doc/r0001941.html?cp=SSEPGG_10.5.0%2F3-5-2-4-21&lang=en
As said above, this should work if you login as instance user. Most of times you do not need root access with DB2.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
I'm using emacs on a console (emacs -nw). I use sql-mode, and when connecting to postgresql, it asks me to enter a password on a buffer, where password is visible.
If I customize-group and set the password option in sql-postgre-login-params list, it asks for password on the minibuffer, but also asks for password on a buffer.
How can customize sql-mode to get asked for password only on the minibuffer?
Thanks in advance.
Edit: the Emacs version: GNU Emacs 24.3.1 (x86_64-unknown-linux-gnu, GTK+ Version 2.24.10)
What emacs version are you using? This happened to me when I used emacs23, if that's the case, you have several options.
Update to emacs 24. It hides passwords automatically.
If this happens once or twice, you could use M-x send-invisible (RET) password (RET)
If this happens a lot, try:
(add-hook 'comint-output-filter-functions 'comint-watch-for-password-prompt)
Found a temporary solution to this problem.
According to psql man page:
-W, --password
Force psql to prompt for a password before connecting to a database.
This option is never essential, since psql will automatically prompt for a
password if the server demands password authentication. However, psql will
waste a connection attempt finding out that the server wants a password.
In some cases it is worth typing -W to avoid the extra connection attempt.
So, connecting to postgres database through psql when a connection needs a password will ever prompt for a password in a buffer.
A temporary solution might be set the -w option on psql call to not ask for a password. Then, it gets the password from the ~/.pgpass file. This file has 0600 permissions so it is insecure. But works for me right now.
In the .emacs file:
(custom-set-variables
'(sql-postgres-options (quote ("-P" "pager=off" "-w"))))
A better solution might be using ssl certificates, which I will explore.
Thank you all for your help.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Closed 8 years ago.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Improve this question
When I installed the PostgreSQL database server on my Mac, I created the "postgres" account so that it wouldn't have a password:
sudo dscl . -create /Users/postgres Password \*
I thought this would be a good security precaution to take. However, it also prevents me from logging in via the su command so that I can use psql to administer the database:
su - postgres # <- prompts me for password
I've tried to change the postgres password using the "passwd" and "dscl . -passwd /Users/postgres" commands but they always prompt me for the old password. How do I set the password in this situation?
Thanks.
Use sudo su - postgres instead. Enter the sudo password, and you'll be postgres.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
I'm attempting to install Bugzilla on a server with a MySQL database on it already. The database is on E: (for space) and Bugzilla is on C:. Currently Bugzilla does not have a database associated with it, and the perl checksetup script looks for a drive local database.
How can I attempt to get bugzilla to target the database on my other drive? Is there a line I can change in the initial scripts to do this?
You tell Bugzilla how to connect to the database server in the localconfig file.
$db_driver = mysql
# The DNS name of the host that the database server runs on.
$db_host = localhost
I believe with MySQL you can also directly connect via a local socket. Be sure to follow the Bugzilla installation instructions for setting up a database, a database user and password for the connection to use. The tables will be set up automatically by Bugzilla's setup scripts.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
I am trying to connect Oracle 10g database server from my client PC using toad 10 Commercial. I have Oracle 10g installed in my PC. When I try to connect, it gives error Can't initialize OCI.Error -1 .
So far I am able to perform tnsping to the oracle server. I have all the settings working in my tnsnames.ora.
Any suggestions are highly appreciated.
Thanks.
Found the solution myself. The problem was with windows 7 permission issue.
I opened Toad with run as administrator , privilege and the problem get solved.
Taken from https://support.quest.com/SolutionDetail.aspx?id=SOL61710
RESOLUTION 1:
Right-click the Toad for Oracle shortcut and select "Run as Administrator" to avoid the error.
RESOLUTION 2:
Right-click the Toad for Oracle shortcut | Properties | Compatibility Tab | check mark "Run this program in compatibility mode for" | choose "Windows XP Service Pack 3" from the drop-down list.
RESOLUTION 3:
Right-click My Computer | Properties | Advanced tab | Environment Variables | under ‘System Variables’ (lower part) | check if you have an entry for ORACLE_HOME. If yes, rename it to ORACLE_HOME_OLD, and then re-test the issue.
RESOLUTION 4:
Upgrade your Oracle client to a version that is 10.2.0.4 or later.
I have another resolution. I had this issue ater setting NLS_LANG environment variable to LATIN AMERICAN SPANISH.
When rebooting windows7, TOAD would not start showing error Can't initialize OCI. Error -1
I had to delete NLS_LANG / NLS_LANGUAGE environment variable.
Now i have to set NLS_LANGUAGE executing ALTER SESSION while logged in TOAD.
No OCI error anymore.
Hope it halps.
Kindly follow up the below steps to solve the (Can't initialize OCI. Error -1)title issue.
go to enviroment variable
remove all variable path in user variable.
Also check the permission.
Thanks
Anandaraj