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

Similar Messages

R18 Patch Release Notes 018.020.004FP (1220.0.04) is Now Available.

You can get this document by clicking on the link shown below:
http://www.box.net/shared/7htopivauh

Thank you...
Just to confirm, as this is a major issue for us - Am I correct in stating that currently the "Update Opportunity Totals" button is not calculating correctly, and will not be until Patch 018.020.005FP is applied to our environment?
According to our "Service Information" section, that will not occur until 5/7/11...
Can you please confirm that I am understanding you correctly?
If that is, the case, can you please provide an additional documentation with specifics on this miscalculation?
Edited by: mckinnmd on Mar 24, 2011 6:48 PM

R18 Patch Release Notes 018.020.005FP (1220.0.05) is Now Available

Click on the following link to get this document:
http://www.box.net/shared/ure9eulaba

Thank you...
Just to confirm, as this is a major issue for us - Am I correct in stating that currently the "Update Opportunity Totals" button is not calculating correctly, and will not be until Patch 018.020.005FP is applied to our environment?
According to our "Service Information" section, that will not occur until 5/7/11...
Can you please confirm that I am understanding you correctly?
If that is, the case, can you please provide an additional documentation with specifics on this miscalculation?
Edited by: mckinnmd on Mar 24, 2011 6:48 PM

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

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.

Oracle Database 10g Release 1(10.1.0.3) for Solaris x86

I've downloaded this version of oracle to be installed on solaris x86 for version 5.10 but unfortunatly the following error has occurred:
$ ./runInstaller
Starting Oracle Universal Installer...
Checking installer requirements...
Checking operating system version: must be 5.6, 5.7, 5.8 or 5.9. Actual 5.10
Failed <<<<
Exiting Oracle Universal Installer, log for this session can be found at /tmp/OraInstall2006-02-15_11-16-32AM/installActions2006-02-15_11-16-32AM.log
so it is failed to install ...
please advise,,
thx alot...

from metalink:
General Notes For Oracle Database - Enterprise Edition On
Solaris Operating System x86:
Sun Solaris OS 10 Information:
o Oracle will announce certification of the following database products on the Sun Solaris 10 operating system shortly after it is announced as being generally available by Sun. This is planned for March 2005.
+ Oracle Database 9iR2 (with 9.2.0.4 Patchset) for Sun Solaris SPARC32
+ Oracle Database 9iR2 (with 9.2.0.5 Patchset) for Sun Solaris SPARC64
+ Oracle Database 10gR1 (with 10.1.0.3 Patchset) for Sun Solaris SPARC64
+ Oracle Database 10gR1 (includes 10.1.0.3 Patchset) for Sun Solaris x86
o When Oracle Database 10gR2 releases on Sun platforms later in 2005, the following releases will be certified on the Sun Solaris 10 operating system:
+ 10gR2 Database for Sun Solaris SPARC64
+ 10gR2 Database for Sun Solaris AMD64
+ 10gR2 Database for Sun Solaris x86
pasquale rago

Java RTS 2.1 Beta free evaluation release for Solaris and Linux available

Hi:
I would like to notify this forum that a free evaluation release of
Java Real-Time System (Java RTS) 2.1 Beta is now available for downloading
at our public web site.
Supported platforms are Solaris/SPARC, Solaris/x86, and Linux/x86 with
real-time POSIX APIs. The specific Linux distributions which this release
has been tested on are: SUSE Linux Enterprise Real Time 10 (released)
and Red Hat Enterprise MRG 1.0 (beta). As for the Solaris versions,
both Solaris 10 Update 3 and Update 4 are supported.
The URL for the web page where to start in order to be able to get to
the download link is:
http://java.sun.com/javase/technologies/realtime/rts/
The download link will be presented to you after you fill out a quick
survey and agree with a click-through, 90-days e-license.
The latest version of the Java RTS Beta technical documentation
bundle included with the product is being separately maintained at
our public website and can be accessed starting from here:
http://java.sun.com/javase/technologies/realtime/reference/rts_productdoc.html
Thanks,
-Carlos
Carlos B. Lucasius
Java SE Embedded and Real-Time Engineering
Sun Microsystems, Inc.
http://java.sun.com/javase/technologies/embedded/index.jsp
http://java.sun.com/javase/technologies/realtime.jsp
http://java.sun.com/javase/technologies/realtime/faq.jsp
http://developers.sun.com/learning/javaoneonline/j1sessn.jsp?sessn=TS-1331&yr=2007&track=5
http://developers.sun.com/learning/javaoneonline/j1sessn.jsp?sessn=TS-2901&yr=2007&track=5
http://developers.sun.com/learning/javaoneonline/j1lab.jsp?lab=LAB-7250&yr=2007&track=4
http://www.sun.com/training/catalog/courses/DTJ-4103.xml
http://www.youtube.com/v/xH1yUXd9krU
http://blogs.sun.com/jtc/
http://blogs.sun.com/delsart
http://blogs.sun.com/bollellaRT

Hello,
Just a quick question: can we have an official position from Sun regarding support of earlier releases of Solaris with Java RTS 2.1? Our customer is currently running Solaris 10 Update 3 with current Recommended patches, and the 2.1 beta cyclic driver supported this version of Solaris. However with the official release version of 2.1, support for U3 disappeared (only U4 and U5 are now supported). Aside from "rubber stamping" the Solaris build via /etc/release, is there a technical reason why U3 is no longer supported? As long as our kernel is up to date, can we safely use 2.1? Or is it just a case of being unable to officially support and test so many releases of Solaris?
Is this a general rule-of-thumb we can expect in future: only supporting the last 2 updates of Solaris 10?
Your advice is appreciated.
Thanks,
Dave.

Discoverer Patch Release 2 (9.0.2.53) for Windows

I can't get the response file to work correctly. If I set SHOW_RELEASE_NOTES to false it still shows up. I need to accomplish this install silently. All of the other boolean operators work fine, the release notes is the only window I get. I have tried changing it to SHOW_RELEASE_NOTES_PAGE with no luck. Any ideas?

It seems that it is only possible to start download of two files at a time. If you try to start more, the system hangs up. If you are trying to download the version that is split in ten files, you have to do this one file at a time. If you are trying to download a single file, make sure that this is the ONLY download session that is running on your computer.
Yours sincerely
Niels Terp

OWB 10.1.0.3 patch released

OWB 10g patch 10.1.0.3 for Windows is now available. This patch is to be applied on top of OWB 10g (10.1.0.2). 73 bugs are fixed in this patch. The details are in the README included with the patch.
MetaLink Download Instructions:
1. Go to MetaLink website: http://metalink.oracle.com/ and login
2. Select Patches from left hand menu.
3. New MetaLink Patch Search
4. Enter patch number 4074429
Nikolai Rochnik

AIX                     10.1.0.3
HP Tru64 UNIX          10.1.0.3
HP-UX Itanium          10.1.0.3
HP-UX PA-RISC(64-bit)      10.1.0.3
Linux Itanium          10.1.0.3
Linux x86               10.1.0.3
MS Windows 32bit          10.1.0.2 ???? But the description says Warehouse Builder: Patchset                    ORACLE 10G WAREHOUSE BUILDER PATCH 10.1.0.3 FOR WINDOWS
MS Windows 64bit     10.1.0.3
Solaris SPARC 64 bit     10.1.0.3
We are running XP clients with AIX database. Previously we were unable to apply the Windows patch because it would have put our back end out of sync with the front end, so to speak.
Now that 10.1.0.3 is available for XP and AIX is it worth applying this and has anyone tried to apply the Windows and UNIX versions together?
If so how did it go?
Thanks
Steven

Sun VDI 3.0 Patch 3 is now available at SunSolve

Hi folks,
we just released a third patch revision for Sun VDI 3.0. The patch binaries are available at SunSolve:
[Patch ID 141481-03 (Solaris 10 sparc) |http://sunsolve.sun.com/search/document.do?assetkey=1-21-141481-03-1]
[Patch ID 141482-03 (Solaris 10 x86) |http://sunsolve.sun.com/search/document.do?assetkey=1-21-141482-03-1]
Please notice that due to CR 6880209 ("The VirtualBox 2.0.x web service doesn't require clients to authenticate") both patch binaries are flagged as security relevant. This affects customers using VirtualBox as virtualization platform. A corresponding Sun Alert (268328) will be published soon.
This patch is accompanied with a minor update release of VirtualBox (*VirtualBox 2.0.12*). This updated VirtualBox version must be installed after applying the Sun VDI 3.0 patch 3 (see instructions below). The updated VirtualBox installer for Solaris 10 is available from the [Sun VDI 3.0 download page|http://www.sun.com/software/vdi/get.jsp]. VirtualBox binaries for other operating systems, for example, for creating desktop templates on your preferred platform, are available here.
- Klaus
The following steps are recommended for updating VirtualBox installations:
1. Login to the Sun VDI administration UI (http://yourserver:1800)
2. Select the affected VirtualBox desktop provider
3. Switch to the "Hosts" tab
4. Select the desired VirtualBox host and click on "Disable"
This ensures that no new desktops/virtual machines will be balanced/started on this host. Please notice, that this will not stop any already running desktops on this host. Thus you either need to ask users to shutdown their desktops or you explicitly trigger the shutdown/power off yourself using the administration UI. After the shutdown, users can immediately request their desktops again - new desktops will automatically be started on the remaining (enabled) VirtualBox hosts (assuming that more than one VirtualBox host is configured in your setup).
5. Download the updated VirtualBox installer from the [Sun VDI 3.0 download page|http://www.sun.com/software/vdi/get.jsp] and extract the archive in a temporary location.
6. Un-install the previous VirtualBox version by triggering
# vbox_2.0/vbox-install -u7. Install the new VirtualBox version by executing
# vbox_2.0/vbox-install8. If the installation fails due to an issue with the VirtualBox kernel module, reboot the machine and repeat step 7 again.
The installation of the new VirtualBox version will change the SSL certificate of the web service. Thus you need to re-import the certificate in Sun VDI 3.0 to establish the communication again.
1. In the Sun VDI administration UI select the affected VirtualBox desktop provider.
2. Switch to the "Hosts" tab
3. Select the desired VirtualBox host and click on "Edit"
4. In the host wizard confirm the changed certificate and click on "Finish"
The last step is to enable the VirtualBox host again:
5. On the "Hosts" tab select the disabled VirtualBox host and click on "Enable"
At this point the Sun VDI 3.0 system will again balance desktops to the updated VirtualBox host. You can now update the next VirtualBox host in your setup.

Hi folks,
we just released a third patch revision for Sun VDI 3.0. The patch binaries are available at SunSolve:
[Patch ID 141481-03 (Solaris 10 sparc) |http://sunsolve.sun.com/search/document.do?assetkey=1-21-141481-03-1]
[Patch ID 141482-03 (Solaris 10 x86) |http://sunsolve.sun.com/search/document.do?assetkey=1-21-141482-03-1]
Please notice that due to CR 6880209 ("The VirtualBox 2.0.x web service doesn't require clients to authenticate") both patch binaries are flagged as security relevant. This affects customers using VirtualBox as virtualization platform. A corresponding Sun Alert (268328) will be published soon.
This patch is accompanied with a minor update release of VirtualBox (*VirtualBox 2.0.12*). This updated VirtualBox version must be installed after applying the Sun VDI 3.0 patch 3 (see instructions below). The updated VirtualBox installer for Solaris 10 is available from the [Sun VDI 3.0 download page|http://www.sun.com/software/vdi/get.jsp]. VirtualBox binaries for other operating systems, for example, for creating desktop templates on your preferred platform, are available here.
- Klaus
The following steps are recommended for updating VirtualBox installations:
1. Login to the Sun VDI administration UI (http://yourserver:1800)
2. Select the affected VirtualBox desktop provider
3. Switch to the "Hosts" tab
4. Select the desired VirtualBox host and click on "Disable"
This ensures that no new desktops/virtual machines will be balanced/started on this host. Please notice, that this will not stop any already running desktops on this host. Thus you either need to ask users to shutdown their desktops or you explicitly trigger the shutdown/power off yourself using the administration UI. After the shutdown, users can immediately request their desktops again - new desktops will automatically be started on the remaining (enabled) VirtualBox hosts (assuming that more than one VirtualBox host is configured in your setup).
5. Download the updated VirtualBox installer from the [Sun VDI 3.0 download page|http://www.sun.com/software/vdi/get.jsp] and extract the archive in a temporary location.
6. Un-install the previous VirtualBox version by triggering
# vbox_2.0/vbox-install -u7. Install the new VirtualBox version by executing
# vbox_2.0/vbox-install8. If the installation fails due to an issue with the VirtualBox kernel module, reboot the machine and repeat step 7 again.
The installation of the new VirtualBox version will change the SSL certificate of the web service. Thus you need to re-import the certificate in Sun VDI 3.0 to establish the communication again.
1. In the Sun VDI administration UI select the affected VirtualBox desktop provider.
2. Switch to the "Hosts" tab
3. Select the desired VirtualBox host and click on "Edit"
4. In the host wizard confirm the changed certificate and click on "Finish"
The last step is to enable the VirtualBox host again:
5. On the "Hosts" tab select the disabled VirtualBox host and click on "Enable"
At this point the Sun VDI 3.0 system will again balance desktops to the updated VirtualBox host. You can now update the next VirtualBox host in your setup.

Get the patch 5 for Solaris

can you tell me where can download 6i patch 5 for Sun Solaris? thanks
null

1) Go to http://Metalink.oracle.com
2) Then click on the link at the top with text:
==> Click here for Patches released after February 19, 2001 and for all Application Patches. "
3) Then Choose
Product family = oracle developer
Platform = Solaris or anything you wish
Limit Search to = Latest Product Patchsets or Minipacks
You should be able to see the patchset you are asking for. If you are looking for a one-off patch then select the default "all product patches" for the option "Limit search to".
null

Sun VDI 3 Patch 2 is now available at SunSolve

Hi folks,
in case you have not noticed it already, we have just released a second patch for Sun VDI 3.0. The patch binaries are available via SunSolve:
[Patch ID 141481-02 (Solaris 10 sparc)|http://sunsolve.sun.com/search/document.do?assetkey=1-21-141481-02-1]
[Patch ID 141482-02 (Solaris 10 x86)|http://sunsolve.sun.com/search/document.do?assetkey=1-21-141482-02-1]
Please notice that due to CR 6856923 ("ESC - Secure authentication disregards the user DN and is actually working as anonymous binding") both patch binaries are flagged as security relevant. This affects customers that use or plan to use secure LDAP authentication for retrieving information from a user directory. A corresponding [Sun Alert (265488)|http://sunsolve.sun.com/search/document.do?assetkey=1-66-265488-1] has been published.
This patch is accompanied with a minor update release of VirtualBox (*VirtualBox 2.0.10*). The updated VirtualBox installer for Solaris 10 is available from the [Sun VDI 3.0 download page|http://www.sun.com/software/vdi/get.jsp]. VirtualBox binaries for other operating systems, for example, for creating desktop templates on your preferred platform, are available here.
This updated VirtualBox version specifically addresses the issue around desktop recycling for non-Windows guest OS, filed as CR 6856906 ("Ubuntu/Opensol desktops does not get recycled on logging out the session"). Customers that want to use desktop recycling for Ubuntu/OpenSolaris desktops must also install the corresponding VirtualBox 2.0.10 guest additions.
Regards, Klaus

The following steps are recommended for updating VirtualBox installations:
1. Login to the Sun VDI administration UI (http://yourserver:1800)
2. Select the affected VirtualBox desktop provider
3. Switch to the "Hosts" tab
4. Select the desired VirtualBox host and click on "Disable"
This ensures that no new desktops/virtual machines will be balanced/started on this host. Please notice, that this will not stop any already running desktops on this host. Thus you either need to ask users to shutdown their desktops or you explicitly trigger the shutdown/power off yourself using the administration UI. After the shutdown, users can immediately request their desktops again - new desktops will automatically be started on the remaining (enabled) VirtualBox hosts (assuming that more than one VirtualBox host is configured in your setup).
5. Download the updated VirtualBox installer from the [Sun VDI 3.0 download page|http://www.sun.com/software/vdi/get.jsp] and extract the archive in a temporary location.
6. Un-install the previous VirtualBox version by triggering # vbox_2.0/vbox-install -u7. Install the new VirtualBox 2.0.10 version by executing # vbox_2.0/vbox-install8. If the installation fails due to an issue with the VirtualBox kernel module, reboot the machine and repeat step 7 again.
The installation of the new VirtualBox version will change the SSL certificate of the web service. Thus you need to re-import the certificate in Sun VDI 3.0 to establish the communication again.
1. In the Sun VDI administration UI select the affected VirtualBox desktop provider.
2. Switch to the "Hosts" tab
3. Select the desired VirtualBox host and click on "Edit"
4. In the host wizard confirm the changed certificate and click on "Finish"
The last step is to enable the VirtualBox host again:
5. On the "Hosts" tab select the disabled VirtualBox host and click on "Enable"
At this point the Sun VDI 3.0 system will again balance desktops to the updated VirtualBox host. You can now update the next VirtualBox host in your setup.

OEM Grid Control Release (not just agent) for Solaris x86?

I see management agents that can be downloaded off of OTN, but is there an official release of Grid Control for Solaris on x86?
"Oracle Enterprise Manager 10g Grid Control *Release 5* (10.2.0.5) for Solaris Operating System *(SPARC)*"
"Oracle Enterprise Manager 10g Grid Control *Management Agent Release 1* (10.1.0.3) for Solaris *x86*"

Please throw me some more meat on that bone. I'm still waiting for my Metalink access. (i.e., can you cut and paste the note text onto this forum message.)Sharing(Cut&Paste) Metalink Notes is not legal.
Oracle has no plans for 10.2.0.4 and for 10.2.0.5 it's expected by Q3 on x86(32&64)

Oracle Enterprise Manager 10g Grid Control Release 1 (10.1.0.2) for Windows

Any new guestimates when product "Oracle Enterprise Manager 10g Grid Control Release 1 (10.1.0.2) for WINDOWS" will finally become available.
Thanks.

Below is what's available for download thru OTN. To ensure my question is clear, approximately when will the MICROSOFT WINDOWS version finally be released:
Enterprise Manager 10g Grid Control Release 1 (10.1.0.2)
Oracle Enterprise Manager 10g Grid Control Release 1 (10.1.0.2) for Linux x86
Oracle Enterprise Manager 10g Grid Control Release 1 (10.1.0.2) for Solaris Operating System (SPARC) (32-bit)
Oracle Enterprise Manager 10g Grid Control Release 1 (10.1.0.2) for HP-UX
Oracle Enterprise Manager 10g Grid Control Release 1 (10.1.0.2) for AIX5L Based Systems
Oracle Enterprise Manager 10g Grid Control Release 1 (10.1.0.2) for HP Tru64 UNIX

Missing download: EM10g Grid Control Release 2 (10.2.0.1) for HP-UX Itanium

According to http://www.oracle.com/technology/software/new_downloads.html there should be a new download EM10g Grid Control Release 2 (10.2.0.1) for HP-UX Itanium. Unfortunately I cannot find the software on the download page. Can anyone help?
Kind regards..........Lorenz

Below is what's available for download thru OTN. To ensure my question is clear, approximately when will the MICROSOFT WINDOWS version finally be released:
Enterprise Manager 10g Grid Control Release 1 (10.1.0.2)
Oracle Enterprise Manager 10g Grid Control Release 1 (10.1.0.2) for Linux x86
Oracle Enterprise Manager 10g Grid Control Release 1 (10.1.0.2) for Solaris Operating System (SPARC) (32-bit)
Oracle Enterprise Manager 10g Grid Control Release 1 (10.1.0.2) for HP-UX
Oracle Enterprise Manager 10g Grid Control Release 1 (10.1.0.2) for AIX5L Based Systems
Oracle Enterprise Manager 10g Grid Control Release 1 (10.1.0.2) for HP Tru64 UNIX

Announcement Oracle9iAS Portal Patch Release 3.0.9.8.3 For Solaris is now available

Similar Messages

Maybe you are looking for