If all of the objects in user1 are in tablespace1, and user1 is self-contained (ie, does not have dependencies on any other users in the database), then you can transport that tablespace from one database to another.
This can be done with Enterprise Manager or with your own scripts, the basic process being:
- backup that particular tablespace
- copy the database
Some introductory info here
http://docs.oracle.com/cd/E11882_01/server.112/e25494/tspaces.htm#ADMIN11394 The basics are:
- make the tablespace readonly on source
- datapump extract the tablespace metadata
- make the tablespace readwrite on source
- copy the files and the dumpfile to the new database
- datapump import the tablespace metadata to attach the tablespace to a new database
If you need to do it without making the tablespace readonly, you can use RMAN to do it (which is a little more complicated);
http://docs.oracle.com/cd/E11882_01/backup.112/e10642/rcmttbsb.htm But in a nutshell:
- RMAN starts an auxiliary instance.
- RMAN restores a backup of the source database control file to serve as the auxiliary instance control file and mounts this control file.
- RMAN restores auxiliary set and transportable set data files from the backups of the source database.
- RMAN stores the auxiliary data files in the selected auxiliary destination. The auxiliary destination is a disk location where RMAN can store auxiliary set files such as the parameter file, data files (other than those in the transportable set), control files, and online logs of the auxiliary instance during the transport. If the transport succeeds, then RMAN deletes these files.
- RMAN stores the transportable set files in the tablespace destination. The tablespace destination is a disk location that by default contains the data file copies and other output files when the tablespace transport command completes.
- RMAN performs database point-in-time recovery (DBPITR) at the auxiliary instance.
- RMAN opens the auxiliary database with the RESETLOGS options.
- RMAN places the transportable set tablespaces of the auxiliary instance into read-only mode. RMAN also invokes Data Pump Export in transportable tablespace mode to create the export dump file for the transportable set.
- RMAN also generates the sample Data Pump import script for use when plugging in the transported tablespaces at a target database. The contents of this script are written to a file named impscript.sql in the tablespace destination. The commands for the script are also included in the RMAN command output.
- If the preceding steps are successful, then RMAN shuts down the auxiliary instance and deletes all files created during the TRANSPORT TABLESPACE operation except for the transportable set files, the Data Pump Export file, and the sample import script.