The issue you're encountering seems to be related to a known 11.1.x Oracle JDBC Thin Driver issue, please review Note 1083794.1 - WebLogic Server: Intermittent Stuck Threads Caused Due to the 11.1.x Oracle JDBC Thin Driver to download and apply the latest JDBC driver for your version.
1. Login to server dev-xxxxx
2. Take backup of ojdbc6.jar files
3. Copy ojdbc6.jar with new one provided by vendor in weblogic /server/lib location.
4. Restart ms01 and ms02 one leg at a time.
There were reports of timeouts noticed on different interfacing systems and there were Stuck threads in the SOA service.
Note:
that in WLS 10.3.6 and 12.1.1 the drivers are under the $WL_HOME/server/lib directory, but in WLS 12.1.2 and 12.1.3 the drivers are under the $ORACLE_HOME/oracle_common/modules directory
2 Issue:"Invalid or corrupt jarfile ojdbc6.jar"
After downloading ojdbc6.jar per instructions in Document: 1094166.1 How to Upgrade ojdbc6.jar and orai18n.jar Bundled With Weblogic 10.3, the following error is obtained:
"Invalid or corrupt jarfile ojdbc6.jar"
Steps to reproduce the issue:
1. Download ojdbc6.jar from JDBC/UCP Download Page
2. Execute java -jar ojdbc6.jar -version
3. This command shows the error "Invalid or corrupt jarfile ojdbc6.jar"
Application Issue: [Expedited] PROD - Apply Bug fix patch 26442748 in Shared Service
1. Download the patch 26442748 from Oracle Support.
2. Stop Services on Shared service PRD application server on prd-xx & prd-xx.
3. Apply patch on prd-xx & prd-xxx.
4. Start Services on Shared service xx PRD application server on prd-xx & prd-xx
5. Sanity test from Infrastructure persepctive.
We have received a request from business to provide a fix for heritage admin url issue in PROD.
After applying latest Security patch set (26519417) in Shared Services environment,one of the heritage admin url stops working.
Vendor has identified as bug and provied a patch 26442748 as fix.
Shared Service consist of multiple applications like xxxxx
No comments:
Post a Comment