Skip to Main Content

SQL Developer

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!

Question about how SQL Developer Connects to DB

user8894222Sep 9 2013 — edited Sep 9 2013

I'm trying to test TAF and client connection failover, for a 3 node cluster db  by faking the first entry in my tnsnames.ora file and connecting with SQL Developer.

In theory SQL Developer should failover to the second node listed in my tnsnames.ora file.

The problem is that no matter what I put in my tnsnames.ora file, SQL Developer still connects to the first listed database, proddb1, EVEN when I 1) remove that entry from TNS and 2) when I misspell the entry so it doesn't resolve in DNS.

So how does SQL Developer connect to the DB? Is there a cache somewhere that I'm not seeing?

This post has been answered by thatJeffSmith-Oracle on Sep 9 2013
Jump to Answer

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 Oct 7 2013
Added on Sep 9 2013
4 comments
152 views