Can an Oracle test database import be done without adversely affecting the production Oracle instances?

Question

On a production database, 11gR2, I have exported everything via Sql Developer, file.sql. I just took all the defaults.

I have a test server with 11gR2 I am going to copy the .sql dump file over to.

Is there anything contained in a export, the one with everything in it, all the objects, data, and so on, that would cause problems for the production environment when I import the data into the test environment?

In other words, I don't want to break my production. I don't have tnsnames.ora set up on my test. I only want the schema, data, all the rest mentioned.

EDIT:

SELECT * FROM DBA_SCHEDULER_WINDOWS;

Showed nothing active.

DBA_JOBS

shows APEX jobs about the mail, stock jobs I think. One about, EMD_MAINTENANCE.EXECUTE_EM_DBMS_JOB_PROCS();

SELECT * FROM DBA_DB_LINKS;

There is a link. But, I know what it is from and it is no longer being used.

Thanks for the info you gave. I feel better now.

Answer 1

The standard things I would think of are:

• use another system (not the same VM/server as production)
• disable all DBA_SCHEDULER_JOBS and don't enable them back until you review their code
• disable all DBA_JOBS and don't enable them back until you review their code
• point DBA_DB_LINKS (both public and private database links) from the production databases to corresponding test databases or delete them; these sometimes use tnsnames.ora, but sometimes bypass it.