Oracle 10.2.0.3 Databases  - Restore to New Server

We will soon be replacing an old server with a new server and I need to restore all Oracle 10.2.0.3 databases to the new server
and ensure Oracle functionality/connectivity with all databases.
I am in the process of testing and need advice and hopefully a 'Step by Step' process I can follow.
I am a systems admin - not an Oracle db admin - so please explain details of any commands I may have to run.
I have already tested once:
ran command prompt: sqplus / as sysdba
SQL>shutdown immediate;
Stopped all Oracle services:
Oracle Database
Oracle Listener
Oracle DBConsole
Installed Oracle 10.2.0.3 on new server
Ensured that the SID and all other Oracle services information matched the old server during installation on the new server.
Stopped all Oracle services on the new server (used the steps above).
Backed-up and test restored to new server.
Enterprise Manager shows: Listener Up Database Instance Down Agent Down
Any help would be appreciated

It would be good to know your operation system. I hope both new and old match or similar.
You can use RMAN to dumplicate you DB so you can follow [Creating a Duplicate Database on a New Host. Doc ID: 388431.1|https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=388431.1]
but a simple file system copy based manual duplication is also possible if new and old OS system is similar...

Similar Messages

  • Moving oracle database to a new server with an upgraded oracle software

    Hi Guys,
    Here is the scenario, we have an existing Oracle 9.2 demo database on a Solaris 5.9 server. I was asked to transfer this to another server with same OS but with an Oracle 10g software installed. The original plan was to mount the exisiting Oracle home from the original server to the new server and from there copy all the database files and bring up the database.
    Here are the steps:
    - Issue an "alter database backup controlfile to trace", get the script from the trace file
    - Copy all database files to the new server
    - Edit parameter files
    - Do a startup mount recreate the control files, do a recover database, and startup the database on the new server.
    I suggested that we to a transport tablespace but due to limited resources and that the 9.2 database does not have this feature we can't perform this process. I also can't do a exp/imp of the database since we really have limited resources on a disk. I was wondering if the steps I enumerated above are correct? Or would result in an error?

    Hi,
    why you want to recreate the controlfile, does the mount point locations are changing from old server to new server?
    if you recreating controlfile new incarnation starts, keep in mind.
    you have the downtime to upgrade.. :)
    shutdown
    take cold backup and move to new server.
    create the directory structure as exist in PFILE including CRD files.
    install software
    startup upgrade
    upgrade database(need to add sysaux TBS)
    shut immediate
    startup
    *@?/rdbms/admin/utlrp.sql*
    change hostname in listner.ora/tnsnames.ora files.
    Thanks

  • How can I move the distribution database to a new server?

    I need to migrate an old distribution database to a new VM. My understanding is that you can detach/attach the distribution DB to make this easier. What are the 'gotchas' in this process? Do I need the detach/attach the system databases as well? The distributor
    is facilitating data from Oracle to SQL Server.
    Another question.. what are some good benchmarks for figuring out how much horsepower I should have set up in my VM that running distribution?
    Thanks,
    phil

    Hi philliptackett77,
    As your description, you want to migrate the distribution database to a new server. Based on my research, you need to remove the replication,  create the distribution on the new server, and recreate publication and subscription according to Satish's post.
    So you don’t need to detach or attach the distribution database or system databases.
    To make this process simple, you could use SQL Server Management Studio (SSMS) to generate scripts and run the scripts to recreate publications and subscriptions or drop publications and subscriptions as the screenshot below. Checking ‘To create or enable the
    components’ generates the script for creating the publications and subscriptions, and Checking ‘To drop or disable the components’ generates the script for dropping the publications and subscriptions.
    Firstly, please use SSMS to generate the script which is used to create publications and subscriptions.
    1.Connect to Publisher, or Subscriber in SSMS, and then expand the server node.
    2.Right-click the Replication folder, and then click Generate Scripts.
    3.In the Generate SQL Script dialog box, check ‘To create or enable the components’.
    4.Click Script to File.
    5.Enter a file name in the Script File Location dialog box, and then click Save. A status message is displayed.
    6.Click OK, and then click Close. For more information about the process, please refer to the article:
    http://msdn.microsoft.com/en-us/library/ms152483.aspx
    Secondly, follow the steps above, check ‘To drop or disable the components’ to generate the script used to drop publications and subscriptions. Then run the sript to drop publications and subscriptions.
    Thirdly, please disable distribution using Transact-SQL or SSMS following the steps in the article:
    http://technet.microsoft.com/en-us/library/ms152757(v=sql.105).aspx.
    Fourthly, please create the distribution at the new server using Transact-SQL or SSMS following the steps in the article:
    http://msdn.microsoft.com/en-us/library/ms151192.aspx#TsqlProcedure.
    Last, please run the script generated in the first step to recreate publications and subscriptions.
    Regards,
    Michelle Li

  • Move database to the new server

    Hello,
    I have 10.2.0.1 Standard Edition database (7GB, not in archivelog mode) on Windows2003 server, and need to move it to the new server (same environment). I thought to use OEM Clone option, but it appears cloning to the other host is working only in Grid - and I have DB Control.
    I know about manual cloning/recreation, but now looking into export and import option. So I think to install Oracle database on the new server, then import some relevant tablespaces exported from the old database. I will use datapump utility in OEM, under system username.
    Is that a good approach ? What rules should be applied to avoid problems in that case ? Sorry if it's very basic question, never moved database before.
    Marina

    Options for porting the database from one server to another after installing Oracle on the new server incldue
    Export/Import using expdp/impdp
    Rman duplicate to compatiable hardware
    Rman file conversion to non-compatiable hardware
    On advantage of expdp/impdp is this option supports reconfiguring the database tablespace/file/object storage layout as part of the migration. Also the adoption of new features like ASSM.
    A disadvantage is that using expdp/impdp will probably be slower and involve more DBA work than using file copies via rman. There are approaches to reduce the clock time necessary to support export/import and the work is often beneficial for long-term database management efforts.
    There have been threads on this topic before and failry recently. You might want to hunt one or two of them down.
    HTH -- Mark D Powell --

  • RMAN Hot backup Restore in new Server

    Hi,
    Our Current Environment:
    Source: Current Production
    Database: 11.1.0.7
    OS: Windows server 2003 R2
    Target Environemnt:
    Database 11.2.0.1
    OS:windows server 2008 R2
    Here my scenario is  need to take RMAN Hot backup in Prod Instance and need to restore in New Server with smae SID which is going to use as Prod instance.
    Please suggest the detailed steps in order to achive the goal.
    Waiting for your thoughts.
    Thanks
    Shaik

    RMAN can make it easy to restore a database to a new host.
    Notice that: Using RMAN RESTORE and RECOVER commands to move a database permanently to another host, will keep the original database identifier (DBID) and will therefore cause a conflict in the RMAN repository, because the restored database with the same DBID will be considered the current target database.
    Below you may find the steps:
    Preparing the New Host
    Record the DBID of the source database.
    Copy the initialization parameter file from the source database to the new host.
    Make sure that all source database backups are available to the new host. Do not connect to the recovery catalog.
    Restoring and Recovering on the New Host
    Configure environment variables on the new host.
    Connect to the new target database with NOCATALOG.
    Set the DBID.
    Start the instance with NOMOUNT.
    Restore the SPFILE from backup.
    Shut down the new instance.
    Edit the PFILE.
    Start the instance with NOMOUNT (again).
    Create an RMAN RUN block to restore the control file.
    Create an RMAN RUN block to restore and recover the database.
    Open the database with RESETLOGS.
    Regards,

  • Restore database Error when restoring database to a new server

    Hi folks,
    I am oracle 10g on an AIX server (5.3).
    I created an rman backup of a database. I then copied it over to a new server where I am trying to restore it (I just created the backup today). However, I am getting the error below.
    Essentially, I used an initdb.ora file to create an instance of the database, and mounted it, on the new server. And then I ran a simple "restore database" command, the end of which is displayed below, with a "Restore complete. ..."
    I have looked up this error (ora-01152) online and I cannot find a scenario which best provides me with a fix to my problem, about the file not being restored from a sufficiently old backup. Could any one help please?
    piece handle=/ora_backup/prev_0/qconfig/dbf/QCONFIG_18_1_721669501_2010_06_14_15:44_Mon_full tag=2010_06_14_15:44_MON_FULL
    channel ORA_DISK_4: restore complete, elapsed time: 00:03:30
    channel ORA_DISK_2: restored backup piece 1
    piece handle=/ora_backup/prev_0/qconfig/dbf/QCONFIG_15_1_721669501_2010_06_14_15:44_Mon_full tag=2010_06_14_15:44_MON_FULL
    channel ORA_DISK_2: restore complete, elapsed time: 00:05:00
    Finished restore at 14-JUN-10
    RMAN> alter database open resetlogs;
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of alter db command at 06/14/2010 17:48:12
    ORA-01152: file 1 was not restored from a sufficiently old backup
    ORA-01110: data file 1: '+DGROUP1/testdb/datafile/system.751.721679898'Edited by: efachim2 on Jun 15, 2010 2:19 AM

    I ran only as below because I copied over the backup right after it finished, when there were no archivelogs.
    RMAN> restore database;
    Starting restore at 14-JUN-10
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=651 devtype=DISK
    allocated channel: ORA_DISK_2
    channel ORA_DISK_2: sid=650 devtype=DISK
    allocated channel: ORA_DISK_3
    channel ORA_DISK_3: sid=649 devtype=DISK
    allocated channel: ORA_DISK_4
    channel ORA_DISK_4: sid=648 devtype=DISK
    channel ORA_DISK_1: starting datafile backupset restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    restoring datafile 00002 to +DGROUP1/testdb/datafile/undots1.667.721227421
    channel ORA_DISK_1: reading from backup piece /ora_backup/prev_0/testdb/db/testdb_16_1_721669501_2010_06_14_15:44_Mon_full
    channel ORA_DISK_2: starting datafile backupset restore
    channel ORA_DISK_2: specifying datafile(s) to restore from backup set
    restoring datafile 00007 to +DGROUP1/testdb/datafile/a1_x.641.721227553
    restoring datafile 00009 to +DGROUP1/testdb/datafile/ent_sm01_x.659.721227557
    restoring datafile 00013 to +DGROUP1/testdb/datafile/in01_x.657.721227569
    restoring datafile 00015 to +DGROUP1/testdb/datafile/cs01_x.656.721227571
    restoring datafile 00016 to +DGROUP1/testdb/datafile/cs01_d.650.721227559
    restoring datafile 00021 to +DGROUP1/testdb/datafile/h01_x.644.721227575
    restoring datafile 00023 to +DGROUP1/testdb/datafile/doc01_x.647.721227575
    restoring datafile 00025 to +DGROUP1/testdb/datafile/og01_x.645.721227577
    channel ORA_DISK_2: reading from backup piece /ora_backup/prev_0/testdb/db/testdb_19_1_721669509_2010_06_14_15:44_Mon_full
    channel ORA_DISK_3: starting datafile backupset restore
    channel ORA_DISK_3: specifying datafile(s) to restore from backup set
    restoring datafile 00003 to +DGROUP1/testdb/datafile/sysaux.662.721227423
    restoring datafile 00006 to +DGROUP1/testdb/datafile/a01_d.639.721227549
    restoring datafile 00010 to +DGROUP1/testdb/datafile/ent_lg01_d.666.721227423
    restoring datafile 00012 to +DGROUP1/testdb/datafile/in01_d.658.721227511
    restoring datafile 00014 to +DGROUP1/testdb/datafile/cs01_d.661.721227521
    restoring datafile 00019 to +DGROUP1/testdb/datafile/ndata_x.654.721227423
    restoring datafile 00022 to +DGROUP1/testdb/datafile/doc_01_d.660.721227531
    restoring datafile 00029 to +DGROUP1/testdb/datafile/in01_x.642.721227471
    channel ORA_DISK_3: reading from backup piece /ora_backup/prev_0/testdb/db/testdb_17_1_721669501_2010_06_14_15:44_Mon_full
    channel ORA_DISK_4: starting datafile backupset restore
    channel ORA_DISK_4: specifying datafile(s) to restore from backup set
    restoring datafile 00001 to +DGROUP1/testdb/datafile/system.655.721227423
    restoring datafile 00004 to +DGROUP1/testdb/datafile/users.653.721227453
    restoring datafile 00005 to +DGROUP1/testdb/datafile/tools.663.721227423
    restoring datafile 00008 to +DGROUP1/testdb/datafile/en_sm01_d.665.721227473
    restoring datafile 00018 to +DGROUP1/testdb/datafile/n_data_d.664.721227423
    restoring datafile 00020 to +DGROUP1/testdb/datafile/hfig01_d.652.721227527
    restoring datafile 00024 to +DGROUP1/testdb/datafile/og01_d.651.721227535
    restoring datafile 00028 to +DGROUP1/testdb/datafile/in1_d.646.721227469
    channel ORA_DISK_4: reading from backup piece /ora_backup/prev_0/testdb/db/testdb_18_1_721669501_2010_06_14_15:44_Mon_full
    channel ORA_DISK_2: restored backup piece 1
    piece handle=/ora_backup/prev_0/testdb/db/testdb_19_1_721669509_2010_06_14_15:44_Mon_full tag=2010_06_14_15:44_MON_FULL
    channel ORA_DISK_2: restore complete, elapsed time: 00:00:27
    channel ORA_DISK_2: starting datafile backupset restore
    channel ORA_DISK_2: specifying datafile(s) to restore from backup set
    restoring datafile 00017 to +DGROUP1/testdb/datafile/cs_lg01_x.640.721227579
    restoring datafile 00026 to +DGROUP1/testdb/datafile/am1_d.643.721227581
    restoring datafile 00027 to +DGROUP1/testdb/datafile/am1_x.671.721227581
    channel ORA_DISK_2: reading from backup piece /ora_backup/prev_0/testdb/db/testdb_20_1_721669624_2010_06_14_15:44_Mon_full
    channel ORA_DISK_2: restored backup piece 1
    piece handle=/ora_backup/prev_0/testdb/db/testdb_20_1_721669624_2010_06_14_15:44_Mon_full tag=2010_06_14_15:44_MON_FULL
    channel ORA_DISK_2: restore complete, elapsed time: 00:00:07
    channel ORA_DISK_2: starting datafile backupset restore
    channel ORA_DISK_2: specifying datafile(s) to restore from backup set
    restoring datafile 00011 to +DGROUP1/testdb/datafile/ent_lg01_x.648.721227421
    channel ORA_DISK_2: reading from backup piece /ora_backup/prev_0/testdb/db/testdb_15_1_721669501_2010_06_14_15:44_Mon_full
    channel ORA_DISK_1: restored backup piece 1
    piece handle=/ora_backup/prev_0/testdb/db/testdb_16_1_721669501_2010_06_14_15:44_Mon_full tag=2010_06_14_15:44_MON_FULL
    channel ORA_DISK_1: restore complete, elapsed time: 00:02:30
    channel ORA_DISK_3: restored backup piece 1
    piece handle=/ora_backup/prev_0/testdb/db/testdb_17_1_721669501_2010_06_14_15:44_Mon_full tag=2010_06_14_15:44_MON_FULL
    channel ORA_DISK_3: restore complete, elapsed time: 00:03:15
    channel ORA_DISK_4: restored backup piece 1
    piece handle=/ora_backup/prev_0/testdb/db/testdb_18_1_721669501_2010_06_14_15:44_Mon_full tag=2010_06_14_15:44_MON_FULL
    channel ORA_DISK_4: restore complete, elapsed time: 00:03:30
    channel ORA_DISK_2: restored backup piece 1
    piece handle=/ora_backup/prev_0/testdb/db/testdb_15_1_721669501_2010_06_14_15:44_Mon_full tag=2010_06_14_15:44_MON_FULL
    channel ORA_DISK_2: restore complete, elapsed time: 00:05:00
    Finished restore at 14-JUN-10
    RMAN>  alter database open resetlogs;

  • RMAN backup restoring to new server help!

    I'm using Oracle 8.1.7. The production database was copied (datafiles, controlfile etc) to a NEW server that I'm trying to set up as a development DB. I take full database backups using RMAN from the production server, and I want to restore them on the development server. I think I somehow have to specify the filename/location of the backup file but I can't seem to figure out how to do it.
    I am not using a recovery catalog.
    Any help is appreciated.

    If you restore the controlfile backup to the development server RMAN
    will "read" the expected location of the backupsets from there.
    In 8i you cannot use the CATALOG command so you have to copy all
    the backupsets to the same path on the development server as on the
    production server.
    Once you have your init.ora and controlfiles in place (and created the
    expected target directory structure for the database and redolog files),
    you can use STARTUP MOUNT and thene RESTORE from RMAN.
    I believe that you should be able to rename files in 8i RMAN as well.
    If not, you'll have to stick to restoring to the same location.
    The key thing is that the controlfile records the "location" of the RMAN backupsets
    and the "location" where datafiles are to be restored to.

  • Error when recovering a database in a new server

    Hi folks,
    I took a full RMAN backup from a Windows Server 2003 32bit and tried to restore it in a new server (Windows Server 2003 64bit). The restore was apparently ok, but when recovering, I got this error:
    archived log for thread 1 with sequence 0 is already on disk as file /u01/app/oracle/oradata/GIEVOTE2/redo01.log
    Oracle Error:
    ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
    ORA-01194: file 1 needs more recovery to be consistent
    ORA-01110: data file 1: '/u01/app/oracle/oradata/GIEVOTE2/system01.dbf'
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 06/15/2010 14:04:59
    RMAN-06053: unable to perform media recovery because of missing log
    RMAN-06025: no backup of archived log for thread 1 with sequence 1041 and starting SCN of 1745356128 found to restore
    I tried to recover using backup controlfile until cancel but same error. I don't need to apply any archivelog as it is a testing env.
    Info:
    Oracle Server: 10g R1 (10.1.0.4)
    DB Type: Single Instance
    Thanks in advance,

    You do not show your rman script, but if you are restoring to another server, you will need to do an incomplete recovery
    This will require a 'set until' parameter.
    eg:
    run {
    set until sequence xxx thread 1;
    allocate channel dev1 type disk;
    recover database;
    sql 'alter database open resetlogs';
    or
    run {
    set until time "to_date( '22-03-2010 10:00:00', 'DD-MM-RRRR HH24:MI:SS')";
    allocate channel dev1 type disk;
    recover database;
    sql 'alter database open resetlogs';
    If you do not use this it will keep requesting logs until it finds the end of thread marker (EOT) in a log, which occurs when the database is shutdown, and this will be a complete recovery

  • BACKUP FROM OLD SERVER & RESTORE TO NEW SERVER

    Hi ,
    i have install SAP on New Server (ADM X86) , it has good hardware. that why i want to shiftout from old deveopment Server to new Server . From old server i want to take backup through DB13 and restore through Brtools on new server. backup will be on disk.
    please guide me which type of backup should be taken ?
    and what is difft b/t whole backup and full backup ?
    NEW SERVER with 2 Quard core processor, 24 GB RAM
    OS= SOLARIS 10
    DB= Oracle 10.2.0.4 with 39 Interim opatch
    SAP= Ecc 6.0
    Hostname=sapdev
    System No.=00
    OLD Server(SPARK) WITH 1 Dual Core Processor , 6 GB RAM
    OS= SOLARIS 10
    DB= Oracle 10.2.0.4 with 39 Interim opatch
    SAP= Ecc 6.0
    Hostname=devsap
    System No.=00
    Best Regard
    Imran Khan

    Hi Imran,
    In you have a full backup, using this existing backup further you can take incremental backups. The incremental backup is based on the previous full backup. The full and incremental backups is controlled by RMAN (Recovery manager).
    You can take a full backup and restore the same in your new server and later take an incremental backup from your old server and restore it to the new server for all the delta changes made. By this you can make sure that your production data is made consistent in the new server.
    If you have sufficient dowtime then, you can take a whole DB backup with redo log files and restore them in your new server.
    There is no difference between whole backup and full backup, with respect to the database data.
    784118 - System Copy Java Tools
    check the OraBrcopy tool in this note. It might help you.
    regards,
    chandru.

  • Restore on new server with new DB_NAME/SID?

    My goal is to restore database with the RMAN backup on a server that has no connectivity to the production database (I don’t want to use duplicate command).
    I restore a database from RMAN using a same DB_NAME/SID and everything was ok.
    -     restore spfile
    -     restore controlfile
    -     restore database
    -     recover database
    -     open with reset logs
    Now I want to restore database but with different DB_NAME/SID (My production database is PROD and I want to restore this PROD RMAN backup on new server and this new database I want to be called DEV).
    How to restore database with new DB_NAME/SID?
    Oracle 10g, Windows Server 2003
    Thanks in advance!

    user9106065 wrote:
    My goal is to restore database with the RMAN backup on a server that has no connectivity to the production database (I don’t want to use duplicate command).
    I restore a database from RMAN using a same DB_NAME/SID and everything was ok.
    -     restore spfile
    -     restore controlfile
    -     restore database
    -     recover database
    -     open with reset logs
    Now I want to restore database but with different DB_NAME/SID (My production database is PROD and I want to restore this PROD RMAN backup on new server and this new database I want to be called DEV).
    How to restore database with new DB_NAME/SID?
    Oracle 10g, Windows Server 2003
    Thanks in advance!You can use NID command
    Run NID and you can see the options to run
    or see How to Change the DBID, DBNAME Using NID Utility in version 10GgR2 onwards [ID 863800.1]
    Cheers

  • Rman restore in new server?

    My linux machine hardisk has crashed, i am rebuilt entire thing from begining, we have the rman backup & controlfiles & init.ora, pwd file in the tape.
    How to rebuild the database from the new catalog. appreciate any body provide a rman step to restore & rebuild...
    Adv thanks

    >>
    Whether i need to create catalog first?. Steps pls
    >>
    Tell us onething, were was the catalog kept? Was it in the same database? or any other database? or you were using controlfile instead catalog to backup your database?
    Lets, catalog is maintained in another database or nocatalog (controlfile) is used to backup.
    set oracle_sid
    startup nomount
    rman target /
    run {
    allocate channel t1 type 'sbt_tape';
    restore controlfile to '<destination>';
    sql "alter database mount";
    restore database;
    recover database;
    sql "alter database open resetlogs";
    }Jaffar

  • RMAN backup restore on new server with CATALOG START WITH

    Hello Experts,
    CATALOG START WITH
    is this required RMAN in catalog mode ?
    reference of post
    Disastor Recovery with RMAN : Restore backup on new separate Server
    Edited by: 873142 on Jul 18, 2011 9:27 PM

    If you use a recovery catalog and want to duplicate database in a fresh server.
    1. connect with the target database.
    2. connect with the recovery catalog.
    3. connect with the auxiliary database.
    4. Run the duplicate command.
    Before running the duplicate command copy the backup piece to your fresh server from the target server. Both mount point should be same.
    Regards
    Asif Kabir
    -- mark your helpful post as correct/helpful.

  • Change the hostname after Database move to new server in Windows

    We are moving database from one server to new server on Windows running 9.2.0.6. Temporarily the new server is named as XYZ after the database is moved. We want to change the servername to ABC , what changes is required ??
    I think only tnsnames and listener.ora is required to be changed. Is anything else need to be changed for Intellligent Agent to work properly ??? Nothing in Registry I believe ???
    Thanks
    Atul

    nothing to change in registry.Just stop the database and services and restart after renaming and rebooting.
    change the client tnsnames too if host name is specified.

  • Database Restore on another Server

    Could someone please explain to me (or point me in the right direction) the procedure (How-To) on how to restore a database to another server?
    please understand I'm just learning oracle and this is all new to me.
    e.g., I have good backups of a database. I restore those database files (control files, dbf, redo logs) to another server. What are the steps in bringing that database up online on a different server?
    ...thanks

    Read thread
    how to clone a database
    Always serach forum.oracle.com, beofre open new thread.
    Cheer,
    Virag Sharma

  • Database Restore in SQL Server

    Hello,
    I have a Server in SQL Server 2012 which have two Databases called DB1 and DB2 . I have taken full backup of DB1 and want to restore in DB2 without Modifying its name,logical name and physical name. how can i do it ?
    Prem Shah

    Then apparently you are not using the Restore command correctly.  We cannot read your mind nor see your desktop, so telling us that something doesn't work without specifying exactly what you are doing is not much help.  And while I'm at it, the
    term "server" is not particularly meaningful since it might refer to your physical machine or it might refer to an instance of sql server (and there can be multiple instances running on a physical machine).  The best way to get answers and useful responses
    is to post the query you are using.  And the best way to learn sql server is to write your tsql commands rather than use the SSMS GUI.
    And I'll point out that your original "requirements" are impossible to meet - 2 (or more) databases cannot share the same physical file names. 

Maybe you are looking for