If you are running Production out of this home then yes you need to halt production. >>> "Schauss, Peter (ESS)" <peter.schauss@xxxxxxx> 4/22/13 2:01 PM >>> I have a windows server (32 bit) which I am attempting to upgrade from 11.1.0.7 to 11.2.0.3. For this particular application we are running test and production instances on the same server (not my choice), so I have to proceed with a bit of caution. I installed 11.2.0.3 in a separate ORACLE_HOME. Now I am trying to apply Patch Bundle 18 before I upgrade the test instance. At this point I have not migrated any of the databases to the new version and we are still using the 11.1.0.7 listener. When I run opatch I get: Following files are active : d:\oracle\product\11.2.0\dbhome_1\bin\oracommon11.dll d:\oracle\product\11.2.0\dbhome_1\bin\oraclient11.dll d:\oracle\product\11.2.0\dbhome_1\bin\orageneric11.dll d:\oracle\product\11.2.0\dbhome_1\bin\orapls11.dll d:\oracle\product\11.2.0\dbhome_1\bin\oran11.dll d:\oracle\product\11.2.0\dbhome_1\bin\oraxml11.dll d:\oracle\product\11.2.0\dbhome_1\bin\oci.dll d:\oracle\product\11.2.0\dbhome_1\bin\orannzsbb11.dll d:\oracle\product\11.2.0\dbhome_1\bin\oraasmclnt11.dll How can I tell what process is using these DLLs or is opatch confusing the 11.2.0 versions of these libraries with the 11.1.0 versions? Tasklist /m will only accept the file name, not the full path name. Does this mean that I have to shut down the production instances before I can apply a patch to the new ORACLE_HOME? Thanks, Peter Schauss -- //www.freelists.org/webpage/oracle-l -- //www.freelists.org/webpage/oracle-l