Migrating to 11g without having dev's change connection strings
We are looking for the best way to migrate our current 10g system to 11g. One scenario is to setup the 11g Environment on another machine, copy all data in 10g and at cut-over, point the current listener on the 10g to the new 11g machine. This way the upgrade will be transparent and the developers will not have to change code to point to the new DB. Thoughts and Recommendations welcome.
Your approch or the traditional upgrade approch works well in your case. I am not expecting 24x7 operations on this database otherwise you might miss data between export / import - actual cut off. Think about that as well.
Try hard to get what you like OR you will be forced to like what you get.
If your database is only 4GB you have a lot of options. Especially if it is only used during business hours. For larger databases it makes sense to set up the new server as a standby, and ship the log files until you are ready to cut over. you can then shutdown your primary after doing a few log switches, make sure that all of the logs are applied and run dbua to upgrade the database.
however, if this database was created with dictionary managed table spaces, i.e. pre 10g you may want to consider export and import into a new 11g database. This will clean up any strange extent issues that you might have.
You may want to practice the bringing the new database up a few times, and do testing with it before you do the final cut over. That way you can work the kinks out.