Hi We have just upgraded (in-place) from R11.3 SP2 to R12 on our test system. Here are some issues we have found First make sure you backup all your servers in-case you need to do a restore. Glad we did since it took a couple of tries to upgrade We probably did over kill but we exported all our artifacts, ran a sql backup, backed up all 3 of our servers, and then did a snap/clone of them (much quicker to recover from snap/clones) Since this was our test system and it is almost impossible for us to force complete our active applications in production (like CA recommends), we found a quiet time and put all active applications on HOLD, and let the active jobs finish. The inplace upgrade is quite simple and quick, then you need to apply a patch again quite simple and easy. Then we tried to bring up DE R12.....and it won’t come up In our case (and this might be site specific to us) we had issues with our table ESP_STATUS_MESSAGE, we also hadn’t run maintenance on this table so it had over 5,000,000 rows and CA recommends no more than 200,000 rows. Anyways with CA’s help we truncated this table and we came up Next we released our on HOLD applications and these all appeared to work and continue running (Don’t know if I’d use this method for the production upgrade yet. CA doesn’t recommend this) Next we encountered a problem with resources. We have thousands of resources and we control them through JavaScript both in-stream in the application and with JavaScript in our repository. In R11.3 if a resource didn’t exist the JavaScript would continue running. In R12 it abends and the JavaScript doesn’t continue running (CA is looking at this). Status JavaScript could not be executed. The reason is: java.util.concurrent.ExecutionException: org.mozilla.javascript.WrappedException: Wrapped cybermation.library.script.CybScriptException: Missing resource name for the resetResourceProperty function. (#1) Type of command issued (but with over 100 threshold resources being set in one script) resetResourceProperty('MFSCHEDULER_AD80','Availability','1'); resetResourceProperty('MFSCHEDULER_AP91','Availability','1'); resetResourceProperty('MFSCHEDULER_AS88','Availability','1'); resetResourceProperty('APPP60WAS','Availability','1'); I got around this problem by running a CLI define resource command for all the resources in our biggest JavaScripts (still don’t know if there is more missing resources). The good news is that if the resources exist it will be ignored The problem with this is there’s no way to test these JavaScript without running them. I can see some of the problems were ‘fat fingers’ and I probably just created a few resources that shouldn’t of been created and that the JavaScript should of been fixed. Anyways hope this helps you Frank