I have a cluster with 2 OSB servers. There is a datasource targeted on both servers, and two persistent stores associated with the servers.
At server startup the following error message appears only on the first server. The table and the store existed previously, and they worked fine.
<Error> <Store> <BEA-280061> <The persistent store "JDBCStore" could not be deployed: weblogic.store.io.jdbc.JDBCStoreException: [Store:280065]open failed (server="OSBServer1" store="JDBCStore" table="jms3_WLStore"):(Linked Cause, "java.sql.SQLSyntaxErrorException: ORA-01950: no privileges on tablespace 'OSB_JMS'
")
You might need to check the permissions on the DB side
ORA-01950: no privileges on tablespace 'OSB_JMS'
Cause: User does not have privileges to allocate an extent in the specified tablespace.
Action: Grant the user the appropriate system privileges or grant the user space resource on the tablespace.
Thus it indicate that there is an issue on the DB w.r.t permissions on the table space. You might also need to check if you are using the correct user in the datasource configuration for the persistent store if it was working for you before and nothing has changed on the WLS server.
Cheers!!
Related
I am using SQL Server 2012 and just logged in using SQL Server authentication. When I try to create a database in the SQL Server authentication mode, I get this error:
I tried to fix it by allowing privileges to it but all gone in waste. It also doesn't allow me alter privileges of User in the form of granting the access of dbcreator but also went in waste. Please help me anyone here.
Thanks in advance.
cannot access the specified path or file on the server, verify that
you have the necessary security privileges and that the path or file
exists
This issue related to a service account of the data engine. It has nothing to do with your SQL login and related permissions, like dbcreator.
Such a situation can be caused by changing the default data folder to a directory where the SQL Server service account does not enough permissions
So, make sure that the service account has FULL permissions on a folder where the database files to be created.
The service account can be checked/changed using SQL Server Configuration Manager:
go to SQL server configuration --> right click on MSSQLSERVER --> Properties --> built-in --> system
and then restart the instance.
this has worked for me.
I am having issues enabling the repository service on the Informatica Admin console. Steps I took so far,
create a new repository service with option to create contents, keeps spinning and after a while it times out. I log back in and I see the repository service created in the Admins console with option to disable but unavailable. Also not able to see the repository tables created in the metadata schema. And not able to connect using the powercenter repository manager as well.
create a new repository service without create contents. A disabled repository service is created. To add/restore contents I try to enable the service then it keeps spinning and nothing happens. After a while it times out and when I log back in I see the option to disable but the service is unavailable. Therefore I am unable to add contents.
I am looking for some helpful insight to resolve this crisis.
Thanks!
While creating repository did you provide database user name and password? And that user has necessary privileges to be a user of informatica repository?
User of that database must have necessary privileges. Even if you have error in the credentials provided during the creation, repository will be created as it can be created at any time in informatica. Kindly delete the repository and create the new one by providing accurate credentials.
Execute these queries to improve the visibility of the user to informatica,
increase the cursor size,
ALTER SYSTEM SET OPEN_CURSOR = 1000 SCOPE = BOTH;
GRANT CONNECT, RESOURCE, CREATE VIEW, SELECT ANY DICTIONARY TO USER_NAME;
Make sure you are executing these queries in sys user.
In case you need to clear the issue without deleting the created repository, go to,
Actions -> Repository contents -> Create
I have created some databases in Hive .After that I configured Hiveserver2 with jdbc client.
but through jdbc client i cant see hive databases, I can see only those databases which i created through jdbc client in hiveserver.
need your help
You can check below points :
Check1:Check the metastore and database ,you have provided in hive-site.xml
Check2:Check by providing the correct privileges to you metastore db. like below:
CREATE USER 'root'#'localhost' IDENTIFIED BY '';
GRANT ALL PRIVILEGES ON *.* TO 'root'#'%'
CREATE USER 'hive'#'%' IDENTIFIED BY 'hive';
GRANT all on *.* to 'hive'#localhost identified by 'hive';
flush privileges;
Let me know if it solves your problem..
I am unable to grant access to a newly restored database using sp_grantdbaccess. I am trying to do this via dynamic sql like below.
DECLARE #grant_access nvarchar(500)
SET #grant_access = 'EXEC ' + #new_db_name + '.dbo.sp_grantdbaccess ''IIS APPPOOL\myApp'''
EXEC sp_executesql #grant_access
I get the below error back trying to run this from a sproc. Any ideas on how I can grant permission for the app to call sp_grantdbaccess etc? I guess I am needing permission to give permission...
Error restore_backup restore_new_configDBThe server principal "IIS
APPPOOL\myApp" is not able to access the database "new_db_name" under
the current security context
Based on the error message it looks like you are trying to grant access to IIS APPPOOL\myApp using the security context IIS APPPOOL\myApp, but IIS APPPOOL\myApp doesn't have the access rights to the db to grant access rights to itself. I think this is akin to me trying to grant myself access to my neighbors house, but I don't have any authority to do so.
Depending on what type of security policies you are working under, I would either run the app pool under an account that has the greater privileges through integrated auth (but this might negate your need to grant privileges), or execute these SQL statements using a local SQL account with the necessary privileges to the database. In these cases, it would be like asking my neighbor (elevated access) to let me (IIS APPPOOL\myApp) in.
If you think it should work because IIS APPPOOL\myApp had access to the DB prior to being backed up, could this be a problem with IIS APPPOOL\myApp being an orphaned user? See http://msdn.microsoft.com/en-us/library/ms175475.aspx But with this case, you still might run into the above scenario trying to fix the orphaned user.
I am trying to query a database table in postgresql, but every time I run the below query it gives me the INSUFFICIENT PRIVILEGE error. What possibly could be the reason for such permission denied error. Also, I am using pgadmin tool in windows to connect the database which is in Linux environment. Below is the query I am running
> > SELECT appid,hash
> FROM app
> WHERE appid=1;
While running the same query I am getting the below Error
ERROR: permission denied for relation app
********** Error **********
ERROR: permission denied for relation app
SQL state: 42501
The user running the query will need permissions to that table. You can grant them to that user with the GRANT statement. The below is an example that grants to PUBLIC
GRANT SELECT ON tablename TO PUBLIC;
Also I have seen SELinux cause isses and places such as here mention it. I am not exactly sure of the command to turn SELinux off but you can see if it is running by using
selinuxenabled && echo enabled || echo disabled
It simply means that you have no permission to access app table. Request your root or database administrator to grant you the permission to access app table. if your are the root or have granting privilege you can use grant command to grant your self permission to use all sql statements on table or database
For Example:
grant all privileges on database money to cashier;
before that you have to login as root or user that have granting privileges
for more details on this command refer to
http://www.postgresql.org/docs/8.1/static/sql-grant.html
If it's DB2 then go to command console of DB2, select your respective Database and select Authorities option by right click on the Database then add your respective DB2 user and grant required access.
You need to make sure that the user with which you are connecting with also has the "USAGE" access on the schema you are trying to access with the user. I have recently faced an error where I got the dump restored into a database and then had some users to whom I was only supposed to provide the read-only access. I have followed the following steps -
CREATE ROLE myapp_readonly;
GRANT CONNECT ON DATABASE {database} TO myapp_readonly;
GRANT USAGE ON SCHEMA {schema} TO myapp_readonly;
GRANT SELECT ON TABLE {schema}.{table_name} TO myapp_readonly;
GRANT myapp_readonly TO {usre};
After performing these steps when I tried to access the table, had received the following error -
SQL Error [42501]: ERROR: permission denied for schema {schema}
In my case, my users were available already and the schemas and the database were restored recently. After I have provided the "USAGE" access to the schema to the user the error was resolved.