Skip to Main Content
Forums

Database Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

port overview not showing exadata 12em. Only through put is showing

User_PHC09Aug 7 2018 — edited Aug 13 2018

port overview not showing exadata 12em. Only through put is showing for IB switch. kinldy let me know how to troubleshoot it

Comments

LiisaU-Oracle

A couple of things to note:

  • ROOT deployment is for Sites Capture.  Failure of this application war to deploy is independent of Satellite Server (SS)
  • WCS 12.2.1.2 is no longer eligible for error corrections and is in limited support.  WebCenter Sites 12.2.1.2.0 - Terminal Patch Set Release (Doc ID 2550602.1).  Further information on Error Correction Support Dates and Policy,  please see the KM Document "Error Correction Support Dates for Oracle Fusion Middleware 12c - FMW/WLS" (Doc ID 1933372.1).

I see you have a remote satellite server (RSS) setup and the deployment is failed, but are you seeing pages being rendered by the Satellite Server?

  • For example, when you preview a page through the contributor UI, is the page rendering? The URL would look like this for a one of the sample site pages in Avisports:  http://{hostname:port} /sites/Satellite?c=AVIArticle&childpagename=avisports%2FAVIArticle%2FArticleLayout&rendermode=preview&pagename=avisports%2FevaluateVisitorStatus&cid=1330880428005
  • I'm hoping to understand if your Sites instance is really using the Remote SS instances, which is hard to do with a failed RSS deployment. If SS is working at all and you have this failed RSS deployment, then your Sites application may be using the Co-Resident SS.

Because there are a lot of sensitive information that Support uses to help troubleshoot issues like these, I highly recommend opening a Service Request.

User_CO104

Hi Liisa,

Thank you so much for your help. It is not remote, it is co-resident I think.

My team haven't installed it, so just guessing how was it configured.

We had multiple issues, but the major of them is that when a user edit an Asset, some users can see the new file and some other can not.We need to take down the whole domain, delete managed servers cache and the cache generated in the configure path on cs-cache.xml, cas-cache.xml, linked-cache.xml and ss-cache.xml

After cache cleaning it works for a while and the it starts with this bad behavior.

1 - 2
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Sep 10 2018
Added on Aug 7 2018
#exadata, #performance-availability
8 comments
216 views