This content has been marked as final. Show 7 replies
Thanks for your response.
We will be using the exact same hardware specs for 126.96.36.199. However, we can't choose the "Apply Maintenance Release" since Oracle verified that there is no roll back in doing this. Our operations policy requires a rollback procedure so the said option is not applicable.
The plan is have both 188.8.131.52 and 184.108.40.206 instances run in parallel for a month then we decide whether to use 220.127.116.11 and decommission 18.104.22.168, or rollback to 22.214.171.124.
Pablo wrote:Are you meaning on the same hardware, if so it is all the products that get upgraded and middleware components so there is no easy rollback.
I haven't tried that but I would also backup the user_projects folders so if you decide to rollback to 126.96.36.199 you can restore those folders as well as the DB
Thanks John and Pablo for the responses.
Just an update regarding my findings:
I tried to make this work for a couple of days now. Still no avail. The problem is that during the diagnostic phase (Configuration went fine), most of the components failed. I installed and configure the following: Foundation, CalcManager, Essbase Server, EAS, APS, Planning, HFM, FDM, and RA.
I'm getting the message "Make sure the application is started" when I run the diagnostic. That is, even all the services are started.
One consistent issue I found in the Essbase_ODL log file is "User native://DN=cn=911,ou=People,dc=css,dc=hyperion,dc=com?USER does not exist". I'm thinking that this is due to the fact that by default, Essbase is configured to use Internal authentication (ADMIN username), but the Shared Services database we used in the configuration has the Admin user in Essbase tagged as "External". That is the current authentication setting of our Essbase (188.8.131.52).
Another error I'm getting, this time from FoundationServices0.log is "weblogic.application.ModuleException: [HTTP:101216]Servlet: "WorkflowEngine" failed to preload on startup in Web application: "interop".
javax.servlet.ServletException: DSF initalization error [FMWGEN][SQLServer JDBC Driver][SQLServer]Invalid column name 'processname'."
I'm not sure if the tables in 184.108.40.206 and 220.127.116.11 are structured differently, but the error message tells us that one column being queried does not exists in the database/table.
If anyone has experienced configuring 18.104.22.168 using the databases in 22.214.171.124, and could give me an idea how to do it (or if it is even possible), that would be great.
Edited by: 26FEB1986 on Sep 21, 2012 2:37 AM