While trying to connect to db2 , I am getting the following error
Connection failed: db2 sql error: sqlcode=-1060,sqlstate=08004
I tried to do a lookup on
http://publib.boulder.ibm.com/infocenter/dzichelp/v2r2/index.jsp?topic=/com.ibm.db2z9.doc.codes/src/tpc/n514.htm
but don't see any meaning of the error message pertaining to this sqlcode. Please suggest on how to resolve this issue.
This is the correct error:
SQL1060N User "" does not have the CONNECT
privilege.
Explanation:
The specified authorization ID does not have the CONNECT privilege to
access the database. The CONNECT privilege must be granted before the
user can connect to a database. This error is also returned when a
switch user request is made with a user ID allowed on the trusted
connection but that user ID does not hold CONNECT privilege on the
database. The connection is put in an unconnected state.
Federated system users: This situation can also be detected by the
data source
The command cannot be processed.
User response:
Contact the system administrator or database administrator for the
database and request a GRANT CONNECT for the authorization ID.
Resubmit the command.
If this error is returned as a result of a switch user request, then
until a switch user request with a valid user ID is made (the user ID
that established the trusted connection or a user ID allowed on the
trusted connection), if any SQL statement is issued, an error is
returned (SQLSTATE 08003). The connection remains trusted when it is
taken out of the unconnected state.
Federated system users: if necessary isolate the problem to the data
source that rejected the request (see the Troubleshooting Guide for
procedures to follow to identify the data source that failed) and
ensure that correct privileges have been granted for that data source.
Some data sources might use a different name than the CONNECT
privilege for the privilege required to connect to a database.
sqlcode: -1060
sqlstate: 08004
Related
I have a user with role rds_iam so IAM DB Auth is required for the user to connect to my Aurora PostgreSQL server (server A). Which works as expected. I have added a role to Server B that has permissions to rds-db:connect to server A. Now I need to update FDW to connect to server A using the IAM-enabled user.
I don't understand what is suppose to be used for password for the following command:
CREATE USER MAPPING IF NOT EXISTS FOR <current user> SERVER <server name>
OPTIONS (USER <username>, PASSWORD <password>);"
Currently, I am getting the following error:
[08001] ERROR: could not connect to server "XXXXXX" Detail: FATAL: PAM authentication failed for user "user-xxxxx"
I suspect because passsword was actually a token that I generated when setting up the user. But tokens expire afte 15 minutes. So how do setup an IAM-user with FDW?
Unless Amazon hacks postgres_fdw to add this capability, I think you would need to write some code that does ALTER USER MAPPING every 15 minutes, or give up on using IAM for this.
I have created a new sql account and assigned it dbmanager and loginmanager roles. It can be used to create new databases but I am not able to access the database afterwards with that user. When right clicking the new database to run a query, the login prompt apears and says that the security principal %user% can access the database under the current security context.
I am not able to alter or grant user any access to the DB now that I can't even run any queries.
The purpose here is that I have a powershell script that creates the databases and handles the automation under a spesific SQL user. What am I missing?
The login might lacks the necessary permissions to connect to the specified database. Logins that can connect to this instance of SQL Server but do not have particular database rights inherit the guest user's permissions. This is a security feature that prevents users from connecting to databases where they do not have permissions. When the guest user does not have CONNECT permission to the identified database and the trustworthy attribute is not set, this error message appears. When the guest user does not have CONNECT authorization to the listed database, this error message appears.
You can connect to the database in one of the following ways:
Grant the specific login access to the named database.
Grant the CONNECT permission to the database named in the error message for the guest user.
Enable the TRUSTWORTHY property on the database that has authenticated the user.
Please refer to the Microsoft Document for this error: MSSQLSERVER_916
Below command used for connecting database through Firebird SQL.
CONNECT "C:\Users\vkaja\Desktop\testing_mysql\newdb.db"
In newdb.db file Schema, data are dumped from SQLite.
Here newdb.db has read-write permission. But error projected here is not a valid username and password.
Statement failed, SQLCODE = -902
Firebird doesn't care about the extension of the database file. fdb is 'standard', and gdb is historical, but it could be anything. However the database you are connecting to must be a Firebird database. You can't just open a database file from a different database system (eg SQLite).
Your problem is one of authentication: you are trying to authenticate without a username + password combination, and if you haven't set the appropriate environment variables, it means Firebird tries to authenticate with an empty user and password, which doesn't exist for your Firebird install. In general you also get this error if you use a username and password that is not known to Firebird.
But even if you fix the authentication problem, you would immediately get a different error: invalid database (or similar), because the file is not a Firebird database.
On this site SQLDude talks about Application roles for MSSQL Server.
A more secure approach you could use for this is called "Application Roles". When connecting from an application you assume a particular role and only that role is granted privileges required in the database. So all apps connect via this mechanism and don’t give out SQL or NT logins for any unauthorised use. You will have to call sp_setapprole in your application with a password, once the connection is established. Once this call succeeds then the connection gets the privileges of the application role and loses privileges of the actual user, which is what we want. So if someone tried to connect to the database from SSMS or SQLCMD, they will access the DB using their credentials, which won’t have the required permissions on the tables, since only the application role has the rights on the tables. This is more secure & reliable approach, but one that requires application code change and as a DBA you will have to create the application role in SQL Server.
However i can't find the equivalent for PostgreSQL?
Is there something like this available in PostgreSQL?
I am using Oracle 11g client 32bit on all my servers and i have proceeded with all the dump imports the very same way I am doing here.
Firstly I create the user with default tablespace
Secondly I alter the user quota unlimited on tablespace
Thirdly I grant connect resource dba to the user.
Then I exit from Oracle and this is my import command
C:\Users\romit.poladiya>imp fajbdummy/fa#dmate file='E:\dump\fajblatest.dmp' full=Y;
I have always been doing this and I do not know why I have not been able to import this time. Please assist. Let me know if you require any more information
Thanking the team in advance,
Romit
ORA-01017: invalid username/password; logon denied
Cause: An invalid username or password was entered in an attempt to log on to Oracle. The username and password must be the same as was specified in a GRANT CONNECT statement. If the username and password are entered together, the format is: username/password.
Cure: Use the correct username & password. Check the system to make sure that the username exists, and set the password if necessary.
The following issue can be closed as I was able to do the tnsping but unfortunately my oracle went into an Idle Instance while I was connecting. Earlier it was not an issue and I have no idea whatever happened and the the oracle just went into Shutdown