Importing full database to different name

Hi i have one douhgt ,i want to import a full database dump to a new database with different name and new location.Can i do that i will explain the steps what i am plan to do
1) create an blank database with new name eg dev and same talbepsaces
2) take and full db export from source name prod using system
3) import with full db with system
4)Source is 9i and dest is 10grel2
Whether it will throw any error ?
rgds
jon

fine.
But i think exp/imp binary don't support 9i to 10g import.
so you using 10g export binary to take the 9i database full backup and import into 10g database use the 10g export binary.
Regards
Rajabaskar

Similar Messages

Import full database to different version (from 11.2 to 10.2)

I have source database which is
SQL>select * from v$version;
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - 64bi
PL/SQL Release 10.2.0.5.0 - Production
CORE    10.2.0.5.0      Production
TNS for HPUX: Version 10.2.0.5.0 - Production
NLSRTL Version 10.2.0.5.0 - ProductionI have target database which is
SQL>select * from v$version;
BANNER
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
PL/SQL Release 11.2.0.2.0 - Production
CORE    11.2.0.2.0      Production
TNS for IBM/AIX RISC System/6000: Version 11.2.0.2.0 - Production
NLSRTL Version 11.2.0.2.0 - ProductionI took export of the source database using below command
expdp "'/ as sysdba'" full=Y dumpfile=DATA_PUMP1:full%U.dmp, DATA_PUMP2:full%U.dmp logfile=DATA_PUMP1:full.log FILESIZE=10G PARALLEL=4I am expecting my import command to be
impdp "'/ as sysdba'" full=Y dumpfile=DATA_PUMP1:full%U.dmp, DATA_PUMP2:full%U.dmp logfile=DATA_PUMP1:impdp_full.log FILESIZE=10GMy question is
1.     What change do I need to make while importing since database version in source and target are different?
2.     Do I need to change any thing in my import command?

1. What change do I need to make while importing since database version in source and target are different?You don't have to do anything. You are exporting metadata that will be recreated in your new database and new version. Just run the import command.
2. Do I need to change any thing in my import command?I don't think you need to change anything. You an add parallel if you want, but the import parallel does not have to match the export parallel, so keeping it as you have it will be fine.
Dean

Unable to copy database with different name in the same instance

I had a huge database and wanted to try some change optimization changes.
So wanted to make a copy of the database along with data in the same instance.
I have tried copy database wizard several times but always see the error as in attachment.
Can someone let me know how to troubleshoot further?
If this is not the correct way please suggest how do i copy a database with different name in the same instance along with data.

Hi Nandu,
From the screenshot, the error 1813 happens when corrupt database log is attempted to attach to the SQL Server. To work around this issue, please preform the following steps, for more details, please review this
blog.
1. Create a new database with same name which you want to recover. Make sure that the MDF file and LDF file have same name with previous database data and log file.
2. Stop SQL Server. Move original MDF file from old location to new location by replacing just created MDF file. Delete the LDF file of new location just created.
3. Start SQL Server. At this point, the database is in suspect status.
4. Make sure that system tables of Master database allows to update the values. Please note that you will be performing this in query window.
Use Master
go
sp_configure 'allow updates',1
reconfigure with override
go
5. Change database mode to emergency mode.
SELECT *
FROM sysdatabases
WHERE name = 'DatabaseName'
BEGIN
UPDATE sysdatabases
SET status = 32768
WHERE name = ' DatabaseName '
COMMIT TRAN
6. Restart SQL Server. Then execute the following DBCC command in query window to create new log file.
DBCC TRACEON (3604)
DBCC REBUILD_LOG(databasename,'c:\yourdatabasename_log.ldf')
GO
7. Reset the database status using following command.
sp_RESETSTATUS yourdatabasename
GO
8. Turn off the update to system tables of Master database running following script.
USE MASTER
GO
sp_CONFIGURE 'allow updates',0
RECONFIGURE WITH OVERRIDE
GO
9. Reset the database status to previous status.
BEGIN
UPDATE sysdatabases
SET status = (value retrieved in first query of step 5)
WHERE name = 'DatabaseName‘
COMMIT TRAN
GO
Make sure that you have done all the steps in order and restarted SQL Server where it is mentioned. Also run SQL Server Management Studio as administrator.(Right click-> Run as Administrator)
Thanks,
Lydia Zhang

Importing Full database wid Crrent production dumpfile on test Database

hi,
I have production database 9.2.0.4 on widows server.
I have Current Dumpfile of Production database.
I Have test Database on another server which is too 9.2.0.4 on windows server.
I need to Import full database on test Database with Current Production Dump file.
COuld u reply the complete procedure
I have tested on test Server But i am not getting all tables some tables are missing.
Thankx
Edited by: oradb on Nov 29, 2010 1:54 AM

which method are you using to take the dump ?
if you are using the imp/exp method ,
then simple create a parameter file with the following parameters :
indexes=y
rows=y
grants=y
buffer=500000
ignore=y
statistics=none
full=y
log=logfile.log
and then run the following command :
imp system/**** <parfilename>
Always refer to the logfile to see for successfull completion of the import.
hope this helps
- KKukreja-
that should help
Edited by: rattlesnake on Nov 29, 2010 3:15 AM

Importing full database in 8i

I have a full database export of a database.
I will have to import that into an oracle 8i database.
May I know what are the considerations to be made/ precautions to be taken care of in precise?
Shd I create all the tablespaces and users forehand? Or the full=y statement during import creates it all ?

imp will attempt to run CREATE TABLESPACE statement with the DATAFILE names and sizes being the same as in the source database.
If your filesystem structure / filesystem sizes are different at the target you should manually precreate each Tablespace.
Also, manually precreating Tablespaces gives you the option to change DEFAULT STORAGE parameters.
Hemant K Chitale

Importing full database and SYSTEM password

Hi,
I have a export dump of a database (full database dump). Want to import on my existing database.
I have create a database, with tablespaces matching names with source database (i.e. got a list of tablespaces from the dba of source database and created them). Now, I am ready to import with imp command (with FULL=Y option).
Will the full database import change my SYSTEM's password to the system's password on the source database ?
Reason for this question is, If you try to read the export of full database (using wordpad !!), you will find all commands creating tablespaces, users, roles etc etc etc. Also, you will see commands which alter the users SYS and SYSTEM to change the password !!!
Any past experiences ??
Thanks in advance.

Hi,
>>Will the full database import change my SYSTEM's password to the system's password on the source database ?
Yes, take a look at demonstration below:
C:\>exp system/pass file=test.dmp full=y statistics=none
Export: Release 10.2.0.1.0 - Production on Mon Apr 21 13:59:51 2008
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Express Edition Release 10.2.0.1.0 - Production
Export done in WE8MSWIN1252 character set and AL16UTF16 NCHAR character set
About to export the entire database ...
. exporting tablespace definitions
. exporting profiles
. exporting user definitions
. exporting roles
. exporting resource costs
. exporting rollback segment definitions
. exporting database links
. exporting sequence numbers
. exporting directory aliases^C
C:\>findstr /C:"ALTER USER SYS" TESTE.DMP
ALTER USER SYS IDENTIFIED BY VALUES '5638228DAF52805F' TEMPORARY TABLESPACE "TEMP"
ALTER USER SYSTEM IDENTIFIED BY VALUES 'D4DF7931AB130E37' TEMPORARY TABLESPACE "TEMP"
Cheers
Legatti

Export/Import full database dump fails to recreate the workspaces

Hi,
We are studying the possibility of using Oracle Workspace to maintain multiple versions of our business data. I recently did some tests with the import/export of a dump that contains multiple workspaces. I'm not able to import the dump successfully because it doesn't recreate the workspaces on the target database instance, which is an empty Oracle database freshly created. Before to launch the import with the Oracle Data Pump utility, I have the "LIVE" workspace that exists in the WMSYS.WM$WORKSPACES_TABLE table. After the import is done, there is nothing in that table...
The versions of the Oracle database and Oracle Workspace Manager are the same on source and target database:
Database version (from the V$VERSION view):
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
PL/SQL Release 10.2.0.4.0 - Production
CORE 10.2.0.4.0 Production
TNS for 64-bit Windows: Version 10.2.0.4.0 - Production
NLSRTL Version 10.2.0.4.0 - Production
Workspace Manager version (from the WM_INSTALLATION view):
OWM_VERSION: 10.2.0.4.3
In order to recreate the tablespaces successfully during the full import of the dump, the directory structure for the tablespaces is the same on the target database's computer. I used the instructions given in this document, section "1.6 Import and Export Considerations" at page 1-19:
http://www.wyswert.com/documentation/oracle/database/11.2/appdev.112/e11826.pdf
Considering that the release of Oracle database used is version 10.2.0.4, I use the following command to import the dump since it doesn't contain the WMSYS schema:
impdp system/<password>@<database> DIRECTORY=data_pump_dir DUMPFILE=expfull.dmp FULL=y TABLE_EXISTS_ACTION=append LOGFILE=impfull.log
The only hints I have in the import log file are the following block of lines:
1st one:
==============================
Traitement du type d'objet DATABASE_EXPORT/SYSTEM_PROCOBJACT/PRE_SYSTEM_ACTIONS/PROCACT_SYSTEM
ORA-39083: Echec de la création du type d'objet PROCACT_SYSTEM avec erreur :
ORA-01843: ce n'est pas un mois valide
SQL en échec :
BEGIN
if (system.wm$_check_install) then
return ;
end if ;
begin execute immediate 'insert into wmsys.wm$workspaces_table
values(''LIVE'',
''194'',
''-1'',
2nd one at the end of the import process:
==============================
Traitement du type d'objet DATABASE_EXPORT/SCHEMA/POST_SCHEMA/PROCACT_SCHEMA
ORA-39083: Echec de la création du type d'objet PROCACT_SCHEMA avec erreur :
ORA-20000: Workspace Manager Not Properly Installed
SQL en échec :
BEGIN
declare
compile_exception EXCEPTION;
PRAGMA EXCEPTION_INIT(compile_exception, -24344);
begin
if (system.wm$_check_install) then
return ;
end if ;
execute immediate 'alter package wmsys.ltadm compile';
execute immediate 'alter packag
The target operating system is in french... here is a raw translation:
1st one:
==============================
Treatment of object type DATABASE_EXPORT/SYSTEM_PROCOBJACT/PRE_SYSTEM_ACTIONS/PROCACT_SYSTEM
ORA-39083: Object type creation failed PROCACT_SYSTEM with error :
ORA-01843: invalid month
failed SQL :
BEGIN
if (system.wm$_check_install) then
return ;
end if ;
begin execute immediate 'insert into wmsys.wm$workspaces_table
values(''LIVE'',
''194'',
''-1'',
2nd one at the end of the import process:
==============================
Treatment of object type DATABASE_EXPORT/SCHEMA/POST_SCHEMA/PROCACT_SCHEMA
ORA-39083: Object type creation failed PROCACT_SCHEMA with error :
ORA-20000: Workspace Manager Not Properly Installed
failed SQL :
BEGIN
declare
compile_exception EXCEPTION;
PRAGMA EXCEPTION_INIT(compile_exception, -24344);
begin
if (system.wm$_check_install) then
return ;
end if ;
execute immediate 'alter package wmsys.ltadm compile';
execute immediate 'alter packag
By the way, the computer of the source database is Vista 64 in english and the destination computer is Vista 64 in french, do you think this has anything to do with these error messages? The parameters of the NLS_SESSION_PARAMETERS view are the same in the source and target database...
Thanks in advance for your help!
Joel Autotte
Lead Developer
Edited by: 871007 on Jul 13, 2011 7:31 AM

I tried to import the full database dump with the "imp" command and I had the same error message with more detail:
. Import d'objets SYSTEM dans SYSTEM
IMP-00017: Echec de l'instruction suivante avec erreur ORACLE 1843 :
"BEGIN "
"if (system.wm$_check_install) then"
" return ;"
" end if ;"
" begin execute immediate 'insert into wmsys.wm$workspaces_ta"
"ble"
" values(''LIVE'',"
" ''194'',"
" ''-1'',"
" ''SYS'',"
" *to_date(''09-DEC-2009 00:00:00'', ''DD-MON-YYYY HH"*
*"24:MI:SS''),"*
" ''0'',"
" ''UNLOCKED'',"
" ''0'',"
" ''0'',"
" ''37'',"
" ''CRS_ALLNONCR'',"
" to_date(''06-APR-2011 14:24:57'', ''DD-MON-YYYY HH"
"24:MI:SS''),"
" ''0'',"
" '''')'; end;"
"COMMIT; END;"
IMP-00003: Erreur ORACLE 1843 rencontrée
ORA-01843: ce n'est pas un mois valide
ORA-06512: à ligne 5
The call to the TO_DATE function with the string of the date format is incompatible with the format and language set in the NLS parameters of my database. Since I know that the "imp" and "exp" commands work client side (unlike "impdp" and "expdp"), I did a full export of the source database from the computer on which I try to import the dump to have the same language exported in the dump and I was able to import the dump successfully.
But, I would like to use the Data Pump tool instead of the old import and export tools. How would it be possible to set the NLS parameters that "impdp" must use before to launch the import of the dump?
The NLS parameters are set to the "AMERICAN" settings in both source and destination database when I validate that with the "NLS_DATABASE_PARAMETERS" view. The dump I did with "expdp" on the source database exported the data with the "AMERICAN" settings as well...
On the destination database, the computer language is in french and I guess it is considered by the Data Pump import tool since it outputs the log in the language of the computer and it tries to do a TO_DATE with the wrong date format because it works with the "CANADIAN FRENCH" settings...
Any suggestions? I'll continue to read on my side and re-post if I find the solution.
Thanks!
Edited by: 871007 on Jul 19, 2011 8:42 AM
Edited by: 871007 on Jul 19, 2011 8:43 AM
Edited by: 871007 on Jul 19, 2011 8:43 AM

Importing full database

Hello,
I am transferring a full database from a unixware711 based server running oracle 8.0.4 to a windows xp with sp2 based machine using export / import.
I have exported the db on the unix server , since there is an issue on unix servers that dont allow export dmp files to exceed 2gb limit the export file has been generated as three split files each under 2 gb. The total export file size comes to around 5gb.
now how do I import from these split files on the windows machine since these export split files are unix based will windows be able to concatenate these files if yes please advise how
if not then please suggest how this can be accomplished.
thanks.

This isn't really the appropriate forum for this. You should try the Database - General forum.
You can transfer the files to windows using FTP binary mode and then concatenate them using copy, (assuming the files were created using split)
copy part1+part2+part3 wholefile.dmp

Importing full database xport

Hello all,
I have made a full database export.
When I now do an import can I: 1) use the DBA user of the database in which i do the import?
2) is there an automatical creation of the tabespaces and user from the import file
3) If not what do I have to do to get the exact the same database
Thanks in advance!
Hans Puts

Hi
It creates the tablespaces and users.Check your export dump file in wordpad.U will find details whatall it creates.
Jitesh

Import full database

please tell me complete steps of importing database in full mode.
the steps which I followed are:
1.I created a database with system and undo tablespace
2. I performed import using the following command
imp userid=system/manager file=c:\abc.dmp full=y
But there are so many errors
and nothing could be imported
somebody told me to create all the tablespaces and then to perform import
then I created 'USERS' tablespace and again performed import,
then even data of this tablespace could not be imported!! please help

1.I created a database with system and undo tablespace
2. I performed import using the following commandimp userid=system/manager file=c:\abc.dmp full=y
First, what is your oracle version?
Second,Was it a Full Database export?
what was the export parameters used?

Error while restoring database with different name on subscriber

Hi all,
I am using merge replication in sql server 2008R2. Yesterday I wanted to create a test environment, so
I did:
1. on publisher I restored from backup production db with another name ( lets call it TEST and new files
.mdf, .ldf and no switch KEEP_REPLICATION). After this step original replication between production
dbs worked fine.
2. on subscriber I did the same: restore as new db TEST with new
files .mdf, .ldf and no switch KEEP_REPLICATION.
Unfortunately I noticed, that after second step replication stopped. SQL agent replication job on Subscriber
is gone.
Why restoring db with new name did affect original replication?
Finally the most important: replication was set up by external company and I have to bring it to live now
but I don't know this subject so good. How can I do it?
Assuming, that there is no data change on subscriber in replicated tables is it enough when I select ‘reinitialize’
on Publisher and Subscriber?
Thanks in advance
Artur

Hello,
Sorry for late response, but I was out of the office during last week.
Regarding problem 1: restoring replication. I contacted guy who made originally our replication and he recreated subscription agent. So this is solved.
problem 2: why did it happen?
Lydia, in link which you provided I found only info about restoring db in replication, but I didn't want to restore replication.
I checked SQL Server and Server Agent logs and there were no entries on that time. The only entries are regarding db restoring. Below:
09/11/2014 12:45:59,Backup,Unknown,Database was restored: Database: Logik_ATData_TEST<c/> creation date(time): 2012/04/27(13:55:41)<c/> first LSN: 21392:66:267<c/> last LSN: 21392:227:1<c/> number of dump devices: 1<c/> device information: (FILE=1<c/> TYPE=DISK: {'D:\MSSQLBackup\Dzienny\Logik_ATData_PROD\Logik_ATData_PROD_backup_2014_09_10_231001_6391536.bak'}). Informational message. No user action required.
09/11/2014 12:45:59,Backup,Unknown,Restore is complete on database 'Logik_ATData_TEST'. The database is now available.
09/11/2014 12:45:59,spid72,Unknown,CHECKDB for database 'Logik_ATData_TEST' finished without errors on 2012-04-26 22:50:05.490 (local time). This is an informational message only; no user action is required.
09/11/2014 12:44:53,spid72,Unknown,Recovery is writing a checkpoint in database 'Logik_ATData_TEST' (13). This is an informational message only. No user action is required.
09/11/2014 12:44:53,spid72,Unknown,Starting up database 'Logik_ATData_TEST'.
09/11/2014 12:44:51,spid72,Unknown,The database 'Logik_ATData_TEST' is marked RESTORING and is in a state that does not allow recovery to be run.
09/11/2014 12:44:51,spid72,Unknown,Starting up database 'Logik_ATData_TEST'.
In Windows application log there were also no other entries, besides these above.
I also could not check job history, because the job was gone in SSMS jobs list, while the subscription was present in SSMS Replication with info, that last successful synchronization was at 12:42 (there is a 5 min. sync period).
I also don't understand how the job was deleted, because according this manual (http://www.mssqltips.com/sqlservertip/1803/auto-alert-for-sql-agent-jobs-when-they-are-enabled-or-disabled/) I have 2 triggers in sysjobs table and every time, when
job is deleted/disabled I got @ notification. In this case I got no @.
My SQL Server version:
Product_Version Product_Level Edition
10.50.2550.0 SP1 Standard Edition (64-bit)
Any idea what happened?
Thanks,
Artur

Imported photos have a different name.

When I export an album of photos to desktop and work on them in photoshop, change the names (using save as command) and import them back to iPhoto- iPhoto renames each photo with the original album name.
The reason I want to import them back to iPhoto is that I want to use them for iWeb on the Album page.
It would save a lot of time matching and renaming the photos in iPhoto if that didn't occur.

Using Photoshop (or Photoshop Elements) as Your Editor of Choice in iPhoto.
1 - select Photoshop as your editor of choice in iPhoto's General Preference Section's under the "Edit photo:" menu.
2 - double click on the thumbnail in iPhoto to open it in Photoshop. When you're finished editing click on the Save button. If you immediately get the JPEG Options window make your selection (Baseline standard seems to be the most compatible jpeg format) and click on the OK button. Your done.
3 - however, if you get the navigation window that indicates that PS wants to save it as a PS formatted file. You'll need to either select JPEG from the menu and save (top image) or click on the desktop in the Navigation window (bottom image) and save it to the desktop for importing as a new photo.
This method will let iPhoto know that the photo has been editied and will update the thumbnail file to reflect the edit..
If you want to use both iPhoto's editing mode and PS without having to go back and forth to the Preference pane, once you've selected PS as your editor of choice, reset the Preferences back to "Open in main window". That will let you either edit in iPhoto (double click on the thumbnail) or in PS (Control-click on the thumbnail and seledt "Edit in external editor" in the Contextual menu). This way you get the best of both worlds
TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto (iPhoto.Library for iPhoto 5 and earlier) database file and keep it current. If problems crop up where iPhoto suddenly can't see any photos or thinks there are no photos in the library, replacing the working Library6.iPhoto file with the backup will often get the library back. By keeping it current I mean backup after each import and/or any serious editing or work on books, slideshows, calendars, cards, etc. That insures that if a problem pops up and you do need to replace the database file, you'll retain all those efforts. It doesn't take long to make the backup and it's good insurance.
I've created an Automator workflow application (requires Tiger), iPhoto dB File Backup, that will copy the selected Library6.iPhoto file from your iPhoto Library folder to the Pictures folder, replacing any previous version of it. It's compatible with iPhoto 6 and 7 libraries and Tiger and Leopard. iPhoto does not have to be closed to run the application, just idle. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.

Import full database question

We running oracle rdbms 11.2.0.3 on aix 6.2 and I am going to create a copy of a production database by using expdp and impdp. My quesition is that the target database for the impdp already has all of the data from the last time we refreshed from prod.
Can I do a fulll database import over the top of what is already there or do I have to start with a blank general purpose database first?
Thanks.

>
Can I do a fulll database import over the top of what is already there or do I have to start with a blank general purpose database first?You can use APPEND which would just append the data.
Also, you can clear the objects on the target database and do a fresh import.

Export schema and import with different name

Hi ,
I need your assistance guys,
I need to export a schema from a database and then import it with different name to another database. How can I do that?
I export it with the following command:
exp userid=system/PW file=May_02_Export.dmp log=May_02_Export.log owner=schema_name statistics="none"
Now I want to import it but with different name (schma_name).
Regards

Did you try FROMUSER and TOUSER option ?
E:\oracle\product\10.2.0\db_1\install>sqlplus / as sysdba
SQL*Plus: Release 10.2.0.1.0 - Production on Sat May 2 20:01:09 2009
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to an idle instance.
SQL> startup
ORACLE instance started.
Total System Global Area 167772160 bytes
Fixed Size                  1247900 bytes
Variable Size              71304548 bytes
Database Buffers           92274688 bytes
Redo Buffers                2945024 bytes
Database mounted.
Database opened.
SQL> create user fromuser identified by fromuser;
User created.
SQL> grant resource, create table, create session to fromuser;
Grant succeeded.
SQL> create user touser identified by touser;
User created.
SQL> grant resource, create table, create session to touser;
Grant succeeded.
SQL> conn fromuser/fromuser
Connected.
SQL> create table export_table(a char);
Table created.
SQL> exit
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
E:\oracle\product\10.2.0\db_1\install>exp fromuser/fromuser file=e:\a.dmp
Export: Release 10.2.0.1.0 - Production on Sat May 2 20:03:06 2009
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
Export done in WE8MSWIN1252 character set and AL16UTF16 NCHAR character set
. exporting pre-schema procedural objects and actions
. exporting foreign function library names for user FROMUSER
. exporting PUBLIC type synonyms
. exporting private type synonyms
. exporting object type definitions for user FROMUSER
About to export FROMUSER's objects ...
. exporting database links
. exporting sequence numbers
. exporting cluster definitions
. about to export FROMUSER's tables via Conventional Path ...
. . exporting table                   EXPORT_TABLE          0 rows exported
. exporting synonyms
. exporting views
. exporting stored procedures
. exporting operators
. exporting referential integrity constraints
. exporting triggers
. exporting indextypes
. exporting bitmap, functional and extensible indexes
. exporting posttables actions
. exporting materialized views
. exporting snapshot logs
. exporting job queues
. exporting refresh groups and children
. exporting dimensions
. exporting post-schema procedural objects and actions
. exporting statistics
Export terminated successfully without warnings.
E:\oracle\product\10.2.0\db_1\install>imp help=y
Import: Release 10.2.0.1.0 - Production on Sat May 2 20:03:47 2009
Copyright (c) 1982, 2005, Oracle. All rights reserved.
You can let Import prompt you for parameters by entering the IMP
command followed by your username/password:
     Example: IMP SCOTT/TIGER
Or, you can control how Import runs by entering the IMP command followed
by various arguments. To specify parameters, you use keywords:
     Format: IMP KEYWORD=value or KEYWORD=(value1,value2,...,valueN)
     Example: IMP SCOTT/TIGER IGNORE=Y TABLES=(EMP,DEPT) FULL=N
               or TABLES=(T1:P1,T1:P2), if T1 is partitioned table
USERID must be the first parameter on the command line.
Keyword Description (Default)       Keyword      Description (Default)
USERID   username/password           FULL         import entire file (N)
BUFFER   size of data buffer         FROMUSER     list of owner usernames
FILE     input files (EXPDAT.DMP)    TOUSER       list of usernames
SHOW     just list file contents (N) TABLES       list of table names
IGNORE   ignore create errors (N)    RECORDLENGTH length of IO record
GRANTS   import grants (Y)           INCTYPE      incremental import type
INDEXES import indexes (Y)          COMMIT       commit array insert (N)
ROWS     import data rows (Y)        PARFILE      parameter filename
LOG      log file of screen output   CONSTRAINTS import constraints (Y)
DESTROY                overwrite tablespace data file (N)
INDEXFILE              write table/index info to specified file
SKIP_UNUSABLE_INDEXES skip maintenance of unusable indexes (N)
FEEDBACK               display progress every x rows(0)
TOID_NOVALIDATE        skip validation of specified type ids
FILESIZE               maximum size of each dump file
STATISTICS             import precomputed statistics (always)
RESUMABLE              suspend when a space related error is encountered(N)
RESUMABLE_NAME         text string used to identify resumable statement
RESUMABLE_TIMEOUT      wait time for RESUMABLE
COMPILE                compile procedures, packages, and functions (Y)
STREAMS_CONFIGURATION import streams general metadata (Y)
STREAMS_INSTANTIATION import streams instantiation metadata (N)
The following keywords only apply to transportable tablespaces
TRANSPORT_TABLESPACE import transportable tablespace metadata (N)
TABLESPACES tablespaces to be transported into database
DATAFILES datafiles to be transported into database
TTS_OWNERS users that own data in the transportable tablespace set
Import terminated successfully without warnings.
E:\oracle\product\10.2.0\db_1\install>imp system/oracle fromuser=fromuser touser=touser file=e:\a.d
Import: Release 10.2.0.1.0 - Production on Sat May 2 20:04:20 2009
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
Export file created by EXPORT:V10.02.01 via conventional path
Warning: the objects were exported by FROMUSER, not by you
import done in WE8MSWIN1252 character set and AL16UTF16 NCHAR character set
. importing FROMUSER's objects into TOUSER
. . importing table                 "EXPORT_TABLE"          0 rows imported
Import terminated successfully without warnings.
E:\oracle\product\10.2.0\db_1\install>sqlplus touser/touser
SQL*Plus: Release 10.2.0.1.0 - Production on Sat May 2 20:04:36 2009
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
SQL> desc export_table
Name                                      Null?    Type
A                                                  CHAR(1)
SQL>HTH
Aman....

How to keep same database with two different names in SharePoint 2013 for two different applications

Hi All,
I have very strange situation.
I had SP2010 production database(wss_content_contoso) migrated to SP13 few months back to migrate one site collection only while I have 15 site collections stored in this database and created a site contoso.com
Now, I want to migrate same(wss_content_contoso) SP2010 database to SP13 and want to create contoso2.com.
I changed database name from wss_content_contoso to wss_content_contoso2 and assigned newID during mount process.
After this exercise, I don't see any site for contoso2.com and issue seems to be the same database.
My question is!!!!
How I can keep both databases(actually same database with different names) and run both application simultaneously?
Any help appreciated!!
Thank you,
AM
AM Senior SharePoint Consultant

You need to run Backup-SPSite/Restore-SPSite on each Site Collection you want to 'duplicate'. You cannot restore the same Content Database to the same farm as the Site Collections have the same GUID, which is stored globally for the farm.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Importing full database to different name

Similar Messages

Maybe you are looking for