We have different Hudson jobs that interact with the database because they write all the databases and delete the data , We can not run 2 jobs at the same time scared of the possibility of running conditions.
So we have decided that we will create separate users for each job (in which case the result of a different schema). I created a new user, logged into the oracle, yet I was able to see the tables and the data that another user put in. I understand that when a new user is created, you will get a clean slate.
Is my Hudson jobs still the problem of running a race or would it be the solution to create a new user for every job?
Any help would be appreciated.
To clarify the words.
A database is a group of users, each of which can be objects (eg tables).
A user can refer to other user-owned items.
For example, the FRED table may be blue. User Barney can write a SELECT * FRED.BLUE statement. The statement will only work if Bernie freed. Selection privilege has been granted on BLE, or there is no selection privilege.
If a user (i.e., Wilm) is red with one selection *, then the red solution becomes as if the first one object failed as their default schema, or as a public option. A user's default schema is usually theirs but it can be replaced with an alternate session SET CURRENT_SCHEMA
, so if your Hudson job enters one database in the same database If they are, they can use a public SYNONYM to refer to objects in a specific schema, or to refer to objects in a specific schema, or they are There are only one ALTER session for the schema.
Comments
Post a Comment