11gR2 Post-Upgrade Questions Regarding tnsnames, listener, pwd, and init

Question

Hello.
Am planning on upgrading a significant # of RHEL5 10gR2 RAC and non-RAC DBs to 11gR2 (11.2.0.3.1, specifically). The servers are still not available to me, but I have been poring on the install and upgrade documents as well as referencing several blogs of users who have done them. I have almost literally read the guides verbatim. I will be using the DBUS - not doing a manual upgrade. Since I cannot test of the upgrade yet, I have a few questions related to POST_UPGRADE actions in terms of the listener, tnsnames, password, and init files.
1.) The upgrade document indicates on p 3-24, "DBUA then proceeds to create new configuration files (parameter and listener files) in the new Oracle home." Will the init file (assuming spfile will be copied as we are using one everywhere now) have deprecated parameters REMOVED after it is copied over to the NEW/TARGET home?
2.) While the install/upgrade guides do not call for it, several blogs indicate that the tnsnames and password files should be copied over from the old/source DB network/admin location ($TNSNAMES/admin) to the new/target DB /network/admin location. Do I need to do this or with the DBUA also copy them over? If all 4 files (tnsnames/listener/spfile/password) are copied over, I am not sure why the document doesn't indicate this.
3.) Other than the spfile being copied over and modified, I don't see any difference between the old/source and new/destination copies of the listener, tnsnames, and password file. Do you agree?
I am just trying to figure out what really need to be copied over and what doesn't in lieu of the DBUA doing it for me.
Thank you all for your help. If I had HW to test this out, I would do it. In the meantime, I am writing the procedures to do the actual upgrade.
Matt

Answer 1

page 3-24 corresponds to following
http://docs.oracle.com/cd/E11882_01/server.112/e23633/upgrade.htm#CHDDCBHG
which states
You must run the Oracle Net Configuration Assistant before running DBUA. See "Configuring the Listener When Upgrading from Oracle9i".
If you are upgrading an existing Oracle Enterprise Manager Database Control or if you are configuring a new Oracle Enterprise Manager Database Control for the new Oracle Database 11g release, then the listener must be running before upgrading Oracle Enterprise Manager. If DBUA detects that an Oracle Enterprise Manager upgrade or configuration is requested, and DBUA does not see a listener running, then it prompts you and starts the default listener in either of these cases.
running netca from new home results in creating a new listener.ora file, this could complain that listener is already used if the old listener is running with the same name or port (default 1521) taken.
I think the "+DBUA reloads the listener.ora file in both the old and new Oracle Database environments.+" which point c in that list has to be taken in context with the two previous points a, b, where the usecase is shown how services , entries are removed from one listener.ora file and added to another. So to make sure those services are started from the "now" correct home those listener.ora are reloaded.
If you look in the 11.1 upgrade guide this text is written as "DBUA removes the entry of the upgraded database from the old listener.ora file and reloads the listener of the old database." http://docs.oracle.com/cd/B28359_01/server.111/b28300/upgrade.htm#i1011982
If after the upgrade old oracle home is not used anymore (no database is running out of that) you can ignore the listener.ora on the old home.