| Full Import to new database [message #220404] |
Tue, 20 February 2007 10:01  |
Seismo
Messages: 5
Registered: February 2007
|
Junior Member |
|
|
Hey guys.
I've been a DBA for a particular product that my company develops for a few years now.
Whenever I we need to create a test database, I usually just build a new blank database, create the two schemas that we use and import those two schemas (fromuser=,touser=) from the production export file.
I'm moving to a new product now and there are many users that I need to import so a user-based import is not practical.
I've never done a full import, though.
I assume that I create an empty database without running any of the dictionary scripts (catalog.sql, catproc.sql, catexp.sql, pupbld.sql) and then just "imp user/pw file=file.dmp full=y"
Does this sound correct?
|
|
|
|
|
|
| Re: Full Import to new database [message #220409 is a reply to message #220404] |
Tue, 20 February 2007 10:28  |
 |
Mahesh Rajendran
Messages: 10708
Registered: March 2002
Location: oracleDocoVille
|
Senior Member
Account Moderator |
|
|
>>I assume that I create an empty database without running any of the dictionary scripts (catalog.sql, catproc.sql, catexp.sql, pupbld.sql)
Your definition of "empty" database is just wrong.
The scripts you have mentioned form the Oracle data dictionary, without which an Oracle database cannot exist.
An empty database is something that does not have any user generated data.
So just create a database.
Pre-create the tablespaces (as found in the original database) that are used by the custom schema.
And then do a full import.
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
