Changes in Report 10gR2 (10.1.2.)

We’ve seen a lot of issues since we upgraded Oracle Report from10gR1 (9.0.4) to10gR2(10.1.2). As it turns out this is caused by big change in Report 10gR2's structure. The Oracle White paper "A GUIDE TO CHANGED FUNCTIONALITY BETWEEN ORACLE REPORTS 6i AND 10g" said that the 10gR2 stops using Reports Server clustering. The new version of Oracle Report also is no longer running (stand-alone) Reports Server as a Windows service. We need to start/stop Reports Servers through OPMN or OEM. If you have only one Report Server in a machine and this is "in-process reports server", everything should be OK. However in our test/development environment, there are multiple stand-alone Report Servers. We spent a few hours to create multiple stand-alone Report Servers in 10gR2 but cannot start up them. Sometime the first one is up but not the second and the third etc. We finally found a document in Metalink (Note:401271.1) that show how to fix it. However, while we were able to start up all Report Servers, users cannot connect to those Report Servers to generate reports. The error showed in the end-users' browser was "REP-51002: bind to reports server failed" . After googling I found a document (Note:413478.1) saying that I must change default broadcast mechanism from multicast to namingservice???. I guested that is because we had to re-installed Oracle S/W in the same machine several time, the default broadcast mechanism did not work any more. After changing to namingservice, everything was back to normal.