Mr.Nick,
Thanks for your reply.
I changed the
appserver.protocol value back to "t3://".
Also,the
domainName in the value
dbserver=hydhtc60432d.domainName isn't actual value.I changed it bcs I am not sure if I can post the domainName in a forum.But it is the correct value as per the domain we are working.
I checked both the glog.properties and the only major diff I see is : the unix prop file has
glog.webserver.xsl.debug=true which windows prop file doesn't have.
I am posting both the files in case you wish to verify.Pls note the two OTM Instances are accessing two different DB instances on two different DB servers.I thought both OTM instances are accessing the same DB instances until I saw the properties file of the OTM instance running on the UNIX.Sorry for posting wrong info.
glog.txt glog(Unix).txt
Regarding the same CU patch you mentioned before,I think the DB instance for the windows is already upgraded to CU4.
Pls let me know what could be going wrong.
Thanks for your time,
Durga
Quote:
Originally Posted by nick.polites  Durga,
Don't change the t3:// to http:// otherwise you won't get the application to work at all. The t3 needs to be there.
You have verified that the database parameters in your glog.properties are correct?
dbserver=hydhtc60432d.domainName is the correct URL?
If they match exactly what you have on your working instance then the only thing I can think of is you don't have the same CU patch applied otherwise you would be seeing the same issue on your other instance.
Post your glog.properties from your other working instance so I can compare the parameters.
Nick |