|
|
|
|
|
|
|
|
|
|
|
|
|
|
Re: how to import dump of one databse to another database [message #636367 is a reply to message #636360] |
Wed, 22 April 2015 06:17 ![Go to previous message Go to previous message](/forum/theme/orafaq/images/up.png) ![Go to next message Go to next message](/forum/theme/orafaq/images/down.png) |
Lalit Kumar B
Messages: 3174 Registered: May 2013 Location: World Wide on the Web
|
Senior Member |
|
|
Michel Cadot wrote on Wed, 22 April 2015 16:27assuming production and development accounts are distinct.
Yes, I was talking only about lower environments or test environments. I thought it was evident that I am not talking about production. Of course, access is restricted on production. Perhaps, I should be more explicit while saying that export/import is not ONLY DBA task. Developers do use it as and when required depending on the requirement and the environment they are working on.
Mostly the testing teams or sustenance teams, who do not work on production systems, frequently does the import and export of the customers DB to debug and work on the fix. Hope it makes sense now.
Probably, this might be a practical scenario, the DBA at customer's side does the export, while developers at the sustenance team does the import.
Anyway, I think we should not get deeper into this
[Updated on: Wed, 22 April 2015 06:21] Report message to a moderator
|
|
|
Re: how to import dump of one databse to another database [message #636372 is a reply to message #636367] |
Wed, 22 April 2015 06:41 ![Go to previous message Go to previous message](/forum/theme/orafaq/images/up.png) ![Go to next message Go to next message](/forum/theme/orafaq/images/down.png) |
![](/forum/images/custom_avatars/102589.gif) |
Michel Cadot
Messages: 68733 Registered: March 2007 Location: Saint-Maur, France, https...
|
Senior Member Account Moderator |
|
|
Even in case of dev only environment, when now you use Data Pump, you write on the server and have to transfer files between servers.
For the first point, DBA is responsible of all database servers, even dev ones, and so you can't allow a developer to fill some FS with his dumps.
For the second point, you can't allow developer to have access to database servers, it just a security point (without speaking about the same issue than the previous one).
And, even with the old imp and exp, assuming you don't allow access to developers on the db server and so they export and import across the network, you can't let them overload this later which is often shared with other environment like office (mail, Internet... even if protected through firewalls) and sometimes even with production environment (not all enterprises can afford to have and manage multiple networks).
As I said, in about all the customers I worked, developers can't export and import.
|
|
|
|
Re: how to import dump of one databse to another database [message #636375 is a reply to message #636373] |
Wed, 22 April 2015 07:27 ![Go to previous message Go to previous message](/forum/theme/orafaq/images/up.png) ![Go to next message Go to next message](/forum/theme/orafaq/images/down.png) |
Lalit Kumar B
Messages: 3174 Registered: May 2013 Location: World Wide on the Web
|
Senior Member |
|
|
I completely understand.
Presently where I work, the machines are isolated and dedicated only for bug reproduction. Thus, developers import the customer's dump themselves and then work on the bug. Yes, the infrastructure is quite good, almost each developer/tester is provided a dedicated DB server.
|
|
|
|
|
|
|