I've taken an offline backup from one environment and copied the file
to two other enviroments. I restored the backup in the first
environment using this command.

restore db EDW taken at 20100923215956 without rolling forward

I was able to connect to the database immediately after the restore.
Everything is fine in this environment

I then used the same restore command in the second enviroment. The
restore completed. When I went to connect to the database I got this
message.

SQL1116N A connection to or activation of database "EDW" cannot be
made because of BACKUP PENDING. SQLSTATE=57019

I didn't think this was possbile, since it's the same backup being
restored in each environment. A coworker suggested I add a "replace
existing" to the restore command. That restore is still running, so I
don't know if it has fixed the problem, but regardless, I'm confused
in knowing when to use certain restore flags to avoid issues like this
in the first place. Thx.

This is for DB2 UDB 8.2

The "replace existing" made no difference, and after reading the
manual on that flag, it was
definitely not going to fix the problem.

Anyone have any insight into the original problem?

TIA

Just a guess:
There was already a database named EDW on both systems.
The first was in "recovery" mode, the second not.
So for the second restore the recovery mode (of the db) was changed to
"yes" and DB2 wants a backup then.
I don't know if the db parameter exists in 8.2 - but you can try what
DB2 says:

SQL1116N A connection to or activation for database "<name>"
cannot be made because of BACKUP PENDING.

Explanation:

The specified database requires a backup to be taken to provide a
starting point for roll-forward recovery.

No connection was made.

User Response:

Back up the database by calling the BACKUP routine or, if
roll-recovery is not required, set the database configuration
parameters LOGARCHMETH1 and LOGARCHMETH2 to OFF.