We did a proof of concept on a RHEL4 linux server and it worked fine. We then went to deploy a production version on our new RHEL5 linux server. The install goes fine. pretty much plain vanilla, MySQL, Tomcat, the defaults. All looks fine. We can even use the import wizard to grab templates from other BO servers. However whenever we schedule an instance it goes into a running state and stays that way permanently. Sometimes refresh can show the state alternately as pending or running. We've evn tried test reports that don't have a data source to rule that out. the only error we occassionly get is: "[Fri Jun 6 22:17:44 2008] 492 1123658640 assert failure: (ScheduleObject.cpp:220). (0 :
no message)." But often times we get no error at all. just perpetual running. Does CRS not work in RHEL5? Any clues would be appreciated.