End of Support date for Oracle WebLogic Server

 

WebLogic Server 12.1.x Releases

VersionRelease DateAnnouncementEnd of Grace Period
WLS 12.1.1.0.0Dec-11n/aJUL 2015 (b)
FMW 12.1.2.0.0Jul-13Note 1567707.1JUN 2016 (b)
FMW 12.1.3.0.0Jun-14Note 1567707.1(a)(b)(c)

 

(a) End of Error Correction is determined by a subsequent Patch Set release to set the beginning of the grace period. Without a subsequent Patch Set release, this version has error correction support as per the Lifetime Support Policy document’s Premier and Extended Support dates. Look for “12.1.x”.

(b) For 12c Release 1 (12.1), the grace period date is set based on the third digit or minor version, (e.g., 12.1.1, 12.1.2, 12.1.3) with a two year grace period for these 12.1.x releases. No Patch Sets were released for WebLogic Server 12.1.x. For WLS 12.1.x, the grace period date is set based on the third digit or minor version, e.g., 12.1.1, 12.1.2, 12.1.3. See Error Correction Policy Note 209768.1 and look for Oracle Fusion Middleware Appendix A.2.

(c) Update Nov 24, 2016 – Version 12.1.3 is the terminal release for 12.1.x  with no planned Patch Sets. Refer to (a). The direction is to upgrade to the next major release, see the following 12.2 table and Note 2067900.1, Oracle Fusion Middleware 12c Release 2 (12.2) Announcements.

WebLogic Server 12.2.x Releases


VersionRelease DateAnnouncementEnd of Grace Period
FMW 12.2.1.0.0Oct-15Note 2067900.1Jun-17
FMW 12.2.1.1.0Jun-16Note 2067900.1Oct-17
FMW 12.2.1.2.0Oct-16Note 2067900.1Aug-18
FMW 12.2.1.3.0Aug-17Note 2067900.1DEC 2021 (b)
FMW 12.2.1.4.0Sep-19Note 2067900.1(a)

 

(a) Version 12.2.1.4 is the final release to continue with Long Term Support (LTS) through the Premier and Extended Support dates provided in the Lifetime Support Policy. Look for “12.2.x” within the tables to find WLS and other FMW products you may have installed.

(b) Update April 23, 2020: Version 12.2.1.3 has been extended from SEP 2020 to DEC 2021. During this timeframe, content will be limited to P1 requests, functional issues, and security updates (CPU program)

WebLogic Server 14.1.1 Releases

VersionRelease DateAnnouncementEnd of Grace Period
WLS 14.1.1.0.0Mar-20Note 2646853.1(a)

 

(a) WLS 14.1.1 is not planned to be an LTS or terminal 14.1.x release. Oracle currently plans to deliver a subsequent 14.1.x WLS version, which when released, will initiate the end of error correction on WLS 14.1.1 after a Grace Period per the Oracle Error Correction Policy. Customers wishing to deploy only on LTS or terminal releases should wait until a WLS 14.1.x LTS or terminal release is identified before deploying to WLS 14.1.x. WLS 12.2.1.4 is an LTS or terminal patch set release for such purposes.

Comments

Post a Comment

Popular posts from this blog

How to fix Oracle SQL Developer connection issue "Got minus one from a read call"

Image
 During connection from SQL Developer to EBS database got below error message: Status : Failure - Test failed: IO Error: Got minus one from a read call Following solution can be done : 1. Go to directory $ORACLE_HOME / network / admin 2. Modify sqlnet.ora file with following parameter : tcp.validnode_checking = no 3. If you don 't want to disable this, you can put the machine names as follows: tcp.invited_nodes=(machine1, machine2) 3. Bounce the listener. Due to security enhancements it is not good to put tcp.validnode_checking = no or comment out will through error when we start listener like below: Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=shsebs7idb1.appsolworld.com)(PORT=1522))) TNS-00584: Valid node checking configuration error TNS-12560: TNS:protocol adapter error Better plan is to add localhost or IP address of client (Local Computer) in the sqlnet.ora file That will solve the problem NAMES.DIRECTORY_PATH=(TNSNAMES, ONAMES, HOSTNAME) SQLNET.EXPI
Read more

How to troubleshoot Long Running Concurrent Request in EBS 12.2

 The following points need to answer before jumping into troubleshooting: Are there any recent code changes done in the concurrent program?           Check long_running_sid and verify the recent code change of last_ddl_timestamp after a             discussion with the developer. Was this running long in the last few run as well, or was this time only?            ==> Check the program history. How much time does it take to complete?           Once again program history can give us some idea. Are these jobs fetching higher data compared to the last run           ===> Confirm on data change . Query Plan change will indicate this issue. Does this job runs at any specific time or it can be run anytime           ===> The nature of the job can help to understand the job's nature. Does this job fetch data using DB Link          ====> Check whether the DB link is involved or not. The below-given approach would help to conclude the gray areas. Check the load of the server using t
Read more

Few Important steps of Oracle Database Clone

 Make Sure oraInst.loc location is correct and accessble. [demantra@dsiddem ~]$ cat /etc/oraInst.loc inventory_loc=/orastage/oraInventory inst_group=dba [demantra@dsiddem ~]$ cd /orastage/oraInventory [demantra@dsiddem oraInventory]$ ls -ltr total 16 drwxrwx---. 5 demantra dba 4096 Jul 22 19:37 backup drwxrwx---. 2 demantra dba 4096 Jul 22 19:37 ContentsXML drwxrwx---. 2 demantra dba 4096 Jul 22 19:37 locks drwxrwx---. 3 demantra dba 4096 Jul 23 10:08 logs Remove Oracle Home from Inventory [demantra@dsiddem oraInventory]$ cd $ORACLE_HOME/oui/bin [demantra@dsiddem bin]$ ./runInstaller -detachHome ORACLE_HOME=$ORACLE_HOME Starting Oracle Universal Installer... Checking swap space: must be greater than 500 MB.   Actual 3039 MB    Passed The inventory pointer is located at /etc/oraInst.loc Run Clone.pl [demantra@dsiddem bin]$ echo $ORACLE_HOME /dnbsid/demantra/oracle/19.0.0 [demantra@dsiddem bin]$ echo $ORACLE_BASE /dnbsid/demantra [demantra@dsiddem bin]$ E01=ORACLE_HOME=$ORACLE_HOME [dema
Read more