FMw 11gR1 Patch 6 Released (11.1.1.7)

For anyone that didn't notice the Annoucement above, FMw 11gR1 Patch 6 (11.1.1.7) has been released. Details in the announcement:
https://forums.oracle.com/forums/ann.jspa?annID=2062

Welcome to the forums !
user4916474 wrote:
Is 11.1.0.6 to 11.1.0.7 a major upgrade or just some bug fixes? someone told me that with 11.1.0.6 is not a Oracle 11g database but 10g database. Is this true? Also is 11.1.0.7 works with Win2003 server?11.1.0.6 to 11.1.0.7 is mostly bug fixes. 11.1.0.6 is not 10g, it is 11gR1. 11.1.0.7 is supported/certified on Win 2003
http://download.oracle.com/docs/cd/B28359_01/install.111/b32006/reqs.htm#CHDHGGFE
MOS Doc 601739.1 - 11.1.0.7 Patch Set - List of Bug Fixes by Problem Type
MOS Doc 756494.1 - Changes introduced in 11.1.0.7 Patchset
HTH
Srini

Similar Messages

New Patch Release 3.0.9.8.1 for Oracle9iAS Portal 3.0.9.8.0

The patch can be found on metalink. The patch number is: 1841088.
Oracle9iAS Portal 3.0.9 Patch Release Notes
July 2001
Contents
For the latest release note updates, visit the Oracle Technology Network
and click the Documentation tab.
Installation and Setup Patch Contents
Installation (Windows) Bugs fixed by this patch
Installation (UNIX)
Post-installation steps
Installation (Windows)
You can only apply this patch to Release 3.0.9 of Oracle Portal
(Oracle9iAS v1.0.2.2). To apply this patch, do the following:
From the command line prompt, execute the patch command according to
the following syntax:
patch.cmd [-m patch_mode] [-s schema_name]
[-p schema_password] [-u sys_password]
-c connect_string [-l log_file_name]
-m patch_mode is the patch mode. Valid values are
loginserver or portalschema. Default value is
portalschema.
-s schema_name is the name of the Portal schema that you
want to patch. Default value is PORTAL30.
-p schema_password is the password of the schema you want
to patch. Default value is PORTAL30.
-u sys_password is the SYS Password. Default value is
CHANGE_ON_INSTALL.
-c connect_string is the TNS connect string information.
-l log_file_name is the name of the log file. Default value
is patch.log.
Examples:
To patch Login Server Only:
patch -m loginserver -s portal30_sso -p portal30_sso -u
change_after_install -c mydatabase -l mypatch.log
To patch Portal Schema Only
patch -m portalschema -s portal30 -p portal30 -u
change_after_install -c mydatabase -l mypatch.log
To patch both Portal Schema and Login Server
patch -m loginserver -s portal30_sso -p portal30_sso -u
change_after_install -c mydatabase -l mypatch.log
patch -m portalschema -s portal30 -p portal30 -u
change_after_install -c mydatabase -l mypatch.log
To complete the application of the patch, follow the instructions in
Post-installation steps.
Installation (UNIX)
You can only apply this patch to Release 3.0.9 of Oracle Portal
(Oracle9iAS v1.0.2.2). To apply this patch, do the following:
From the command line prompt, execute the patch command according to
the following syntax:
patch.csh [-m <patch_mode>] [<-l log_file_name>]
-m <patch_mode> is is the patch mode. Valid values are
loginserver, portalschema, or both. Default value is both.
-l log_file_name is the name of the log file. Default value
is patch.log.
Examples:
To patch Login Server only
patch.csh -m loginserver -l mypatch.log
To patch Portal Schema only
patch.csh -m portalschema -l mypatch.log
To patch both Portal Schema and Login Server
patch.csh -m both -l mypatch.log
patch.csh -l mypatch.log
To patch both Portal Schema and Login Server with default
log file
patch.csh -m both
patch.csh
To complete the application of the patch, follow the instructions in
Post-installation steps.
Post-installation steps
The bug fixes for bug numbers 1817550, 1830898, 1832632, 1840420, 1664594,
1810741, 1807325, and 1819442 are not installed via the patch script
because you must shut down your Web server prior to applying them. The
sections that follow describe how to apply these fixes.
JPDK.ZIP
On the Web server where the provider is running:
Unzip the contents of jpdk.zip into a directory (e.g., JPDK_30901).
Shut down your Web server.
Change your zone.properties file to include <extract
dir>/jpdk/lib/provider.jar in the wrapper.classpath.
If you are using Java Portal Development Kit (JPDK) samples from a
previous release of the JPDK, update your samples using those
included in the zip file. Refer to <extract dir>/installing.jpdk.html
for more details.
Restart your Web server.
Note: Refer to <extract dir>/release.notes.html for a list of changes made
in this release.
wwpage.jar
On the middle tier where the Portal listener is running:
Shut down your Web server.
Create a backup of your current wwpage.jar file.
Replace /$IAS_HOME/Apac he/Jserv/servlets/wwpage.jar with the new
wwpage.jar provided in this patch.
Restart your Web server.
New Parameters
The Parallel Page Engine now accepts two new parameters in the
zone.properties file:
minStall is the minimum stall value allowed for a contentfetcher
before it assumes there is a problem and times out. This value
defaults to 120 seconds. It was added to help upgrades from
308, which had a normal stall value of 40 seconds. The meaning
of stall has changed slightly, raising the need for a minimum
value.
minTimeout is the minimum timeout that may be sent by a
portlet. At times portlets send very small values, like 1
second. This almost always fails, and pages are rendered
incomplete. The minTimeout defaults to 5 seconds, but may be
set otherwise if this is not large enough. The minTimeout is
different from the requestTime. The requestTime is used when no
timeout value is sent for a portlet.
opca.jar
Back up your current opca.jar file, which is found in the
<IAS_HOME>/assistants/opca/ directory.
Copy the opca.jar file provided with this patch to the
<IAS_HOME>/assistants/opca/ directory.
To install the Portal repository, run the launch.bat (on NT) or
launch.sh (on Solaris) to invoke the Portal Configuration Assistant.
Follow the steps in the configuration assistant.
Oracle Portal Cache
Go to Oracle MetaLink and retrieve the patch for bug number 1817550.
Stop your Oracle HTTP Server.
Apply the patch you downloaded from Oracle MetaLink as per the
instructions in the README.txt file.
Login to your system as root and delete all cache files and
subdirectories under the directory
<IAS_HOME>/Apache/modplsql/cache/plsql. Make sure the directory
<IAS_HOME>/Apache/modplsql/cache/plsql is empty.
Start your Oracle HTTP Server.
Bugs fixed by this patch
This patch fixes the following known bugs:
Bug Number Bug Subject and Description
1817550 ON SOLARIS, WHEN RUNNING ON PORT 80, ORACLE PORTAL CACHE
GETS DISABLED
Due to a bug in the Oracle HTTP Server powered by Apache,
the Oracle Portal cache gets disabled when it is running
on port 80.
1819194 EXCEPTION THROWN IF A USER'S PASSWORD HAS AN AMPERSAND.
Special characters such as an ampersand (&) in passwords
or any text node that is sent to the Web providers were
causing errors.
1664594 XML TAGS IN THE JAVA STACK - CAUSING PARSER TO CRASH.
(Duplicate Bug: 1788506) Control characters were not
being properly escaped appropriately and causing errors
in the database SOAP parser.
1823166 PORTLET SECURITY IS RAISING AN ERROR FOR NON-ADMIN USERS
W/ ANY_PORTLET MANAGE.
1782458 NOT ABLE TO CREATE MASTER DETAIL REPORT.
1802055 308-309 UPGR: CLICKING ON "REFRESH ERROR" IN PORTLET
REPOSITORY GIVES ERROR.
1815257 UPGRADE: 306-309:308-309:SEARCH PEOPLE PORTLET: SHOWS
ERROR.
1744458 REPORTS FROM SQL: VALID SQL:GIVES AMBIGUOUS COLUMN ERROR
FOR JOINED TABLES.
1783257 REPORT COMPONENT AS PORTAL IN PAGE CAN'T BE ASSOCIATED
WITH TAB.
1801961 UPGRADE:307-309:ADD PORTLETS REGION IS SHOWING UP VERY
SLOW.
1807325 FETCHERS TIMEOUTS, AND PORTLET PRODUCED AN ERROR.
This bug pertains to a synchronization issue in the 3.0.9
fetching of portlet content. The Document could not be
contacted error is randomly raised. However, it may be
that other problems are causing this error. This bug only
refers to the synchronization issue in which the Parallel
Page Engine causes the problem.
1810741 PROVIDER USER DOES NOT DETECT PUBLIC USER CORRECTLY.
Previously, the JPDK did not correctly detect if the
current user was logged in or accessing the portal using
a public session. This bug also affected providers
registered with a login frequency of PUBLIC. Failure to
detect the logged in state of the user correctly caused
ProviderUser.isPublicUser() to return an incorrect value
when a provider written using JPDK release 3.0.9 was used
with earlier releases of Oracle9iAS Portal.
The most common symptom of thi s error is the Customize
link being shown to public users when the provider
definition specified that it should be hidden. A new
username parameter has been added so the JPDK can
correctly detect the logged in state of users while
maintaining backwards compatibility with older versions
of Oracle9iAS Portal.
1811275 GROUP NAME IS REPEATED IN LIST OF GROUPS IN SPANISH,
FRENCH ETC.
1812018 PERSPECTIVES ARE REMOVED FROM ITEMS IF THEY ARE EDITED.
1815037 OPCA HANGS AT 90%
Oracle Portal Configuration Assistant hangs at 90% during
the Oracle9iAS 1.0.2.2 installation.
1819442 PROVIDE MINTIMEOUT FOR PPE TO OVERRIDE SMALLEST
TIMEOUT(S).
Previously, there were no minimum values for timeouts.
The fix for this bug adds some minimum values for
timeouts and changes the defaults such that the Parallel
Page Engine works better without any configuration by the
user. These changes help to prevent getting the Portlet
could not be contacted error message.
1830898 SSOUNLCK.SQL DOESN'T UNLOCK SSO USER ACCOUNT.
1832632 BITMAP INDEXES IN EXPORT-IMPORT FAIL TO INSTALL ON ORACLE
8I STANDARD.
1833509 SITE MANAGER BUGS FOR CATEGORY, ITEMTYPE, FOLDERTYPE, AND
PERSPECTIVE.
This bug covers the following:
Showing the category popup correctly when you hide
categories.
Same Banner appears more than once while rendering.
All Item Types show up when you create Custom Item
Types.
All Folder Types show up when you create Custom
Folder Types.
No data found error occurs in perspective list of
content area manager.
All item types get hidden when you hide different
item types in different content areas.
Categories are not displayed appropriately when you
go into content areas of default languages other
than "us."
Minor issues with Bulk action.
1840420 CUSTOM WRITTEN EXTERNAL AUTH MODULE NEED TO BE UPDATED
AFTER 3.0.9 UPGRADE SSOXOID.PKB DOESN'T LOAD.
External authentication modules that were written before
3.0.9 need to be updated after upgrading to 3.0.9.
ssoauthx.pks is updated in 3.0.9 and contains additional
routines that need to be implemented.
null

Richard,
I have just applied patch to upgrade from Portal 3.0.9 to 3.0.9.8.1 (Patch applied to loginserver and portal schema) and the External Applications that were previously set up have gone from the portlet.
Does this relate to your note at the bottom:
"Minor issues with Bulk action. 1840420 CUSTOM WRITTEN EXTERNAL AUTH MODULE NEED TO BE UPDATED AFTER 3.0.9 UPGRADE SSOXOID.PKB DOESN'T LOAD.
External authentication modules that were written before 3.0.9 need to be updated after upgrading to 3.0.9. ssoauthx.pks is updated in 3.0.9 and contains additional routines that need to be implemented." ??
If I go to the "Login Server Administration" portlet and select the link "Administer External Applications" I get a list of 5 External Applications that have previously been set up.
If I go back to the Home Page and select "customize" on the "External Applications" portlet I get the message "Your Login Server administrator has not registered any external applications".
Does that mean I should just run 'ssoauthx.pks' & 'ssoxoid.pkb' or do I need to do something else ??
Thanks
Simo

Patch Release: Berkeley DB Java Edition 4.0.117

Berkeley DB Java Edition 4.0.117
http://www.oracle.com/us/products/database/berkeley-db/index.html
http://www.oracle.com/technetwork/database/berkeleydb/overview/index.html
http://www.oracle.com/technetwork/database/berkeleydb/overview/persistence-160890.html
http://www.oracle.com/technetwork/database/berkeleydb/overview/index-093405.html
Berkeley DB Java Edition 4.0.117 is a patch release consisting of many important fixes. We strongly recommend that users of the 4.0.x upgrade to this release. Those using 4.1.x need not be concerned with this patch release.
The critical patch fixes:
[#19422] - Fixes a bug that prevents recovery if CacheMode.EVICT_BIN is used.
The complete list of changes is in the change log page.
http://download.oracle.com/otndocs/products/berkeleydb/html/je/je-40117-changelog.html
Product documentation can be found at:
http://download.oracle.com/docs/cd/E17277_02/html/index.html
Download the source code including the pre-compiled JAR, complete documentation, and the entire test suite as a single package.
http://download.oracle.com/berkeley-db/je-4.0.117.zip
http://download.oracle.com/berkeley-db/je-4.0.117.tar.gz
Common questions are addressed in our FAQ that you can find here:
http://www.oracle.com/technetwork/database/berkeleydb/je-faq-096044.html
Then join OTN and participate in the Berkeley DB JE Support Forum discussions. Our engineering and support staff are highly active on these forums, if you have questions please ask them there first.
Berkeley DB Java Edition
For further information, or questions about licensing and sales of JE, please contact us at:
mailto:[email protected]
Thank you for your support of Berkeley DB Java Edition.

Hi Kristoffer,
We have never updated Maven central -- I think someone else, perhaps who is reading the forum, did that for 5.0.73. We should update it, but we don't quite have our act together on that. Hopefully we'll have more info on that soon, but for now you'll need to just copy the jar file or use the Oracle maven repo.
You should definitely read the release notes and the change log, and decide whether to upgrade.
BDB has both a commercial and an OSS license. Due to Oracle policy BDB does not have some of the things you might expect from an OSS project:
- bug system is not exposed
- roadmap is not published
- code contributions are fairly rare, mostly due to the nature of the code -- it's a database engine, and is fairly difficult to change casually.
What other questions about the process do you have? I wasn't sure exactly what you wanted to know.
--mark

Upcoming Patch Release

Hi Everyone,
We thank everyone for bringing to our notice some issues that has happened with the recent player and our sdk update. We have identified a server side issue for this and we are in process of fixing it. This will fix issues such as
a) Starting screen share second time after stopping not working
b) no publisherID text in the sample.
and some more.
Since it's a server side problem, giving out client side swc won't help. We will have a patch release around 10th December with these fixes and some more. We thank you for your patience and continued support to the community.
Thanks
Regards
LCCS Team

Didn't mean to mark this post as a question so....marking it as answered.

Announcement : New SPS Patch Release (v 6.0.3) Now Available

A newer release of Service Provisioning System (version 6.0.3) is now available for download on sunsolve
The Release Notes for this release are available here and is a good place to start.
{color:#0000ff}*You are strongly encouraged to go through the Release Notes AND the README instructions of all the patches thoroughly before starting your patch installations.*{color}
The following are the key changes that were incorporated in this release.
1) A fix in the SPS transport layer code was implemented to provide performance optimization of deployment jobs over a raw, SSH or SSL connection. Specifically, customers using an SSL connection between MS and the RA/LD nodes can observe noticeable performance improvements while deploying large payloads.
2) A fix was also added to correct the default database encoding for customers who want to use extended ASCII character sets. This would not only facilitate clean database migration between 5.2 to 6.0 of any UTF-8 characters, but also ensure data integrity on fresh 6.0 installation. It's strongly recommended that customers take necessary steps to apply this fix on their SPS 6.0 installations.
3) Certain GUI related bugs were fixed and some missing functionality was added back.
4) It is to be noted that this is a cumulative patch on top of the earlier patch release version 6.0.2. Hence all the bug fixes that were delivered with the 6.0.2 patch are also accumulated into the 6.0.3 patch
5) Response time of GUI login validation has been improved.

another option would be to make either the n1sps export not writing explicit end tags
<element />
instead of
<element></element>
or
making the import / schema a bit less sensitive about whitespace within elements. The current bug, that you cannot export the xml, reformat in netBeans and then re-import is extremely annoying.

Refer to Doc ID 825030 which talks about applying of patch for correction of date format in web adi. Is this patch can be applied on R12.1.3 instance as this patch released date is very old. Please suggest if there is another patch which be applied to cor

Refer to Doc ID 825030 which talks about applying of patch for correction of date format in web adi. Is this patch can be applied on R12.1.3 instance as this patch released date is very old. Please suggest if there is another patch which be applied to correct the date format in web adi. currently the date is coming in number format.

Hello,
This document is for 11i Date Format Changes When Loaded Into Webadi (Doc ID 825030.1)
use this document instead for R12 : Incorrect Date Format in Excel Sheet Generated Via WebADI (Doc ID 828253.1)
<Moderator Edit - deleted MOS Doc content - pl do NOT post such content>
Best Regards,
Eric.

Plans for Soa Suite 10.1.3 patch releases

Hi Experts
We have customer who has 10.1.3 license and they are on 10.1.3.5.0 patchset. We are helping them with some implementation .
On the OTN I see the last release of 10.1.3 soa suite patch set was 10gR3 PS3 (10.1.3.5.0). Can you please answer following queries
1. How long oracle plans to support 10.1.3 release
2. When can we expect the next patch release for 10.1.3 soa suite
3. Does oracle helps to support a customer with the critical bug fix
4. Does Oracle help to Processor Perpetual license by providing a bugfix or patch fixes
Regards
Vipin R.S
Edited by: 975550 on Dec 24, 2012 2:54 AM

Hi , I am facing the same issue.
were you able to resolve it.
please let me know if you were.
Many Thanks.

Announcement Oracle9iAS Portal Patch Release 3.0.9.8.3 For Solaris is now available

Oracle9iAS Portal Patch Release 3.0.9.8.3 For Solaris is now available for download from metalink. Bugnumber for the patch release is 2131815.
You must install this patch release over an Oracle9iAS 1.0.2.2 installation of Oracle9iAS Portal. You can install it over either a production installation (3.0.9.8.0) or a patched installation (3.0.9.8.1, 3.0.9.8.2). This patch release is cumulative and it incorporates the changes from the earlier patches (3.0.9.8.1, 3.0.9.8.2). The installation instructions are in README.TXT and RELNOTES.HTM contained in the patch release.
The patch will be available for other platforms by the end of May.

I saw this warning in the content area API home page.
Warning - The Content Area APIs available in 3.0.8.x and 3.0.9.x will not work with Oracle9iAS Portal 9.0.2. They are not available with this release
Will there be other API's?
Are you removing the concept of loading an item through APIs?
Thanks in advance
Harish

New patch releases: JE 5.0.48 and 4.1.20

All,
Please note that new patch releases for JE 5.0 and 4.1 are now available.
The JE 5.0.48 update contains a number of critical bug fixes that can cause corruption (data loss) under certain circumstances. We strongly recommend that anyone using JE 5 upgrade immediately to 5.0.48. This update also contains fixes for issues that prevent upgrading to JE 5 from an earlier release, or cause problems after upgrading.
Note that running the pre-upgrade utility is mandatory before upgrading to JE 5 from an earlier release, and the pre-upgrade utility must be run using JE 4.0.20. The JE 4.0.20 update contains fixes to the pre-upgrade utility as well as one critical bug fix. See the first section in the JE 5.0.48 change log for detailed information on upgrading and running the pre-upgrade utility.
We'd like to thank all the users who reported problems and especially those who worked with us over email, in some cases for long periods of time, to diagnose problems and test fixes. Some, but not all, of those who helped are mentioned in the change log. Thank you for contributing to the reliability of the product!
Complete information can be found in the JE documentation. The release is available via the download site or Maven.
--mark

Hi,
the biggest problem is that we are using bought application not made in our company. I have tried out this java application with JRE 1.4 and 1.5 and it just doesn't work. So the only solution is using JRE 1.3 on all intranet computers. This application uses digital certificate so why doesn't Sun allow digital signet java programs to run on older versions of JRE?
There could also be one more solution. I exactly know md5sum (or sha1sum) of 3 JAR files used by applet needing JRE 1.3. So if this sum would be enabled manualy (or I could send batch file to make this in registry or any other storage this would be good).
http://en.wikipedia.org/wiki/Md5sum
http://en.wikipedia.org/wiki/Sha1sum
Thanks,
Grofaty

Patch releases in R/3 and how to test and know d extractors???????????????

Some patches are going to happen in R3 development system .This effects the BW plug-ins meaning some data extractors will need testing.
Here I want to know how to Identify which extractors are effected based on the patch release notes .
Can anybody please give detailed information regarding this.
Could anyone provide me the patch release notes numbers.
Thanks
Padma.

Hi ,
visit this site:
https://websmp210.sap-ag.de/notes
you can serch all the notes.
Regards
Rahul

CRM On Demand Rel 17 Patch Release Notes 1142.0.02 is Available

CRM On Demand Rel 17 Patch Release Notes 1142.0.02 is Available. Go to MOS and search for ID 1104184.1

Hi Bobb,
I logged in and under Release Info Tab under What's New searched for Release 18 - Patch Release Notes link, but i didnt find the link.
Thanks,
Raghu

Oracle CRM On Demand Release 16 Patch Release Notes 1080.0.0

Oracle CRM On Demand Release 16 Patch Release Notes 1080.0.0 is now available on MetaLink. The document ID is 860682.1

hi bobb,
would it be possible to send me the document as well. my email : [email protected]
regards,
Stephan

CRM On Demand Rel 18 Patch Release Notes 1220.0.02 is Available

1. Click the Training and Support link from within CRM On Demand.
2. Click the Release Info tab.
3. Under What's New, click the Release 18 - Patch Release Notes link.

Hi Bobb,
I logged in and under Release Info Tab under What's New searched for Release 18 - Patch Release Notes link, but i didnt find the link.
Thanks,
Raghu

What are the patches released for new browsers

Hi Gurus,
It's a general question.
Is oracle released any patches for new browser versions?
Our client is experiencing the different issue with the latest browsers.
This is one of the error message which they had received: iRecuitment - oracle error 1403:java.sqlSQLException:ORA-01403: from Chrome user - need latest Patch.
Regards,
Joshna.

You need to use a certified browser -- Please see the docs referenced above for the list of supported browsers and client OS.
If you still get the same error, please see these docs.
Critical Patch Released For Release 12.1.1 and Higher Customers Using Projects Web ADI Functionality [ID 1315848.1]
Accessing Application Get Error: Fnd_session_management.Updatessioncontext Sql Exception [ID 1316294.1]
Thanks,
Hussein

Enterprise Portals versions and patches release dates

Could some one let me know, where can I find the release dates of the enterprise portal versions and patches, as I am interesetd to know about them.
I am new to EP and I dont have access to SAP service market place.
Thank you

Hi Raj Reddy,
You should have SAP market place id to get the EP versions and patch release dates. These are all available in the form pdf documents. In some documents we have to convert the weeks to corresponding years and months to guessestimate the dates.
Product overview
Version     Description     Release Type     Delivery Date     Status     Date     Mainstream / Extended Maintenance until     Printable Version
SAP WORKPLACE 2.11
SAP WORKPLACE 2.11      GA Release      General Availability      Available      Since 30.11.2000      30.09.2005 / -      Print...
Product overview
Version     Description     Release Type     Delivery Date     Status     Date     Mainstream / Extended Maintenance until     Printable Version
SAP ENTERPRISE PORTAL 5.0
SAP Enterprise Portal 5.0      GA Release      General Availability      Available      Since 28.12.2001      30.09.2005 / -      Print...
SAP EP 6.0 ON WEB AS 6.20
SAP Enterprise Portal 6.0 on SAP Web AS 6.20      Standard      Release to Customer      Available      Since 17.03.2003      31.12.2006 / -      Print...
Product overview
Version     Description     Release Type     Delivery Date     Status     Date     Mainstream / Extended Maintenance until     Printable Version
SAP NETWEAVER 04
SAP NETWEAVER 04      Standard      Release to Customer      Available      Since 31.03.2004      31.03.2010 / 31.03.2013      Print...
SAP NETWEAVER 2004S
SAP NETWEAVER 2004 S      Standard      Release to Customer      Planned      from 31.10.2005      31.03.2011 / 31.03.2014      Print...
The dates are available from EP5.0 General availability. to Netweaver 04 2005-06-03.
Hope this helps.
Regards,
Rajesh Khanna Venkatesan.

FMw 11gR1 Patch 6 Released (11.1.1.7)

Similar Messages

Maybe you are looking for