Manually deployed again, still failed at the same point. Attached are the logs from Adobe CM and WebSphere App.

Yes, I did manual deployment for both LiveCycleES2.ear and LivCycleES2Native.ear. Any options other than EJB deployment needing to be checked?

I used the same archive for dev - installed one single-server and one cluster without any problems. Re-deploying right now on this second cluster for prod.

Thanks for the answer. the machine has 128GB RAM which should not be an issue; I'll check the installer. Is there a way to fix this without going through re-deployment of the entire components?

What's the function of adobe-guides.lca? it failed twice when I deployed LiveCycleES2 with errors attached below.The OS is SUN 64-bit SPARC and the DB is Oracle 10g, both clustered. All other componenents were deployed and validated fine. Will this affect any of the functions from Output, Forms and ...

Thanks.

I'm getting this error when the app server starts up. the installation itself finished without any problem or errors. The OS is SUN Solaris and DB is Oracle 10g. Any idea?[4/28/10 18:13:51:352 EDT] 00000019 DBModelPersis E com.adobe.datamodel.repository.DBModelPersistence getModels Naming exception ...

Thanks

Thanks Jayan for your quick reply.this leads to another question: wouldn't the deployment fail because adobe scripts are looking at the node level (and possibly the same names for IDP_DS or EDC_DS) ?

Is there a way to have multiple LC servers in the same cell with their own respective oracle DB  (url plug-ins willbe a separate concern) ?