Ron - You should consider refreshing the instance by cloning your production
database. This way you get an exact replica in all respects, and you can
test your backup as a bonus. If you are interested in this method, tell us
how you backup your production database.
Dennis Williams
DBA
Lifetouch,
Ron - As far as losing the new functions, this is one reason we've moved to
a 3-instance layout. Production, staging, and test. This takes off a lot of
the pressure for overwriting test as you describe. Other than that, it
becomes a matter of negotiation. Describe what your options are, and let
Ron,
Of course, your milage may vary, but this is what I do:
1.) exp [EMAIL PROTECTED] file=prod_data_exp.dmp
owner=list,of,comma,separated,schemas direct=y
2.) connect to test_db.
3.) Disable all constraints. When you script this, make sure you order it so that
referential constraints
Like I said. There are new packages, procedures, functions, etc... in
TEST that we do not want to lose.
Ron
-Original Message-
Sent: Tuesday, December 16, 2003 9:04 AM
To: Multiple recipients of list ORACLE-L
Ron - You should consider refreshing the instance by cloning your
production
For this kind of situation I do normally like this
Store all table names in single file.
Exp constraints=n triggers=n indexes=n tables=`cat tables.lst`
file=table_data.dmp grants=n
Import the full file or by fromuser, touser option.
-Original Message-
Sent: Tuesday, December 16,
You can always disable triggers and constraints in existing schema
before running import (and then, enable them after import is done).
Also, specify CONSTRAINTS=N and TRIGGERS=N when exporting.
Igor Neyman, OCP DBA
[EMAIL PROTECTED]
-Original Message-
Smith, Ron L.
Sent: Tuesday,
Seems like last time I tried to disable constraints Oracle complained
and wouldn't let me due to dependant objects or something.
Ron
-Original Message-
Sent: Tuesday, December 16, 2003 9:15 AM
To: Multiple recipients of list ORACLE-L
You can always disable triggers and constraints in
What are all the problems with triggers and constraints? If you're talking
about unique/primary/foreign keys, disable constraints and those pesky things
that protect the integrity of your data will no longer be in your way. Of course,
you will not know whether your data is inconsistent or not, but
Hi Ron,
For just testdata you might take a look at http://www.databee.com/main.htm,
this can help you.
Dennis' method will work, but doesn't answer your question, because a
production copy will overwrite all new functionality as well. However, his
suggestion isn't as bad as it might seem on a
Ron,
here's an ugly way to do this:
Empty your TEST database of data. Drop constraints Indexes.
Perform and export of the TEST database with ROWS=N - this will export all
Functions, packages and procedures.
Import data from production.
Import the stuff from step 2 above. This should overlay
Here is a sample of the script I run to disable FK constraints:
declare lTables DBMS_SQL.VARCHAR2_TABLE;
lConstraints DBMS_SQL.VARCHAR2_TABLE;
nJ BINARY_INTEGER;
BEGIN
SELECT table_name, constraint_name
BULK COLLECT INTO lTables, lConstraints
FROM user_constraints
WHERE owner = 'IPN_DBA'
Hi Ron,
For just testdata you might take a look at http://www.databee.com/main.htm,
this can help you.
Dennis' method will work, but doesn't answer your question, because a
production copy will overwrite all new functionality as well. However, his
suggestion isn't as bad as it might seem on a
Thanks! I'll try it.
Ron
-Original Message-
Sent: Tuesday, December 16, 2003 9:44 AM
To: Multiple recipients of list ORACLE-L
Here is a sample of the script I run to disable FK constraints:
declare lTables DBMS_SQL.VARCHAR2_TABLE;
lConstraints DBMS_SQL.VARCHAR2_TABLE;
nJ
I do that every night, but I drop the user to be refresh in the test db,
is not a big DB.
Ramon E. Estevez
[EMAIL PROTECTED]
809-535-8994
-Original Message-
Sent: Tuesday, December 16, 2003 11:59 AM
To: Multiple recipients of list ORACLE-L
Hi Ron,
For just testdata you might take a
If the developers have code in dev they should have DDLs that generate the
triggers and changes. I hate it whenDevelopers think they can get away with
telling some else to own thier code...Database CODE in my mind always
includes the scripts to generate the object in addition to the funtioning
The methodology we developed for one client goes like this:
There are three databases - dev, test, and prod.
dev starts as a clone of prod, and fixes, changes and enhancements are developed and
unit tested there. One of the REQUIRED products of development is a script that will
upgrade prod to
Hi DBA's,=0D
I have the following problem,=0D
on a node I have some tables an a MV_master (done
with FAST refresh) build =
over these tables.=0D
I have to bribg this MV_master on the DB servers
but =0D
It's not possible to do this using snapshot log on
MV_master and building t=
he MV_slave's
17 matches
Mail list logo
