Now, I have attemtpted to duplicate this on a seperate server.

I emptied the database and did an import (except for system). Only dropped all the user and application data. Did an import from the first of the month. Copied over the archive logs. Opened the database and issued the recover command. Got the message that the database did not need recovery.

Now, is this because the export produced an in-sync setup? I am still reading through the backup and recovery books, but I am thinking that it should have worked. If I undersand correctly, the SCN's in the control file, to show where we "are" in the process, would not match the header information in the datafiles, thus prompting a roll forward of the archive logs. But, I did not copy over the datafiles, I just emptied them and refilled them. So, will hte header information be the same.

I seem to be remember being told in my backup and recovery class that you could not create a new database on a new machine, copy over archive logs from old machine, and roll forward. He said the SCN's are machine dependent.

If I restore the database from a previous cold backup, then there is no need for the import. Once I issue the open command, the database will recover automatically. Might take it a little while to roll through the logs, but it will open.

I am reviewing the restore procedures from hot backups.

If i also drop the SYSTEM tablespaces and reimport them from the export, will that cause the archive logs to roll forward on the new box? What is "telling" the database that it has to roll forward. Is it a check of the current log number and SCN?

BTW, thanks for the patience and the answers. It's what I love about posting to this forum. Very helpful. Thanks !!