How-To Sun JES 5 on Solaris 10 -Zones

Hi Experts,
I am in a process of installing JES 5 on Soalris 10 ( T2000 server with Global and non-global Zones).I ahve installed the below components in various zones :
Shared components -- Gloabl zone
Directory Server --Zone 1
Access Manager over web server-- Zone 2
Now, where should i install portal server provided that i want a Applicaiton server also.
Please put some light on this .
thanks
Lokesh

Hi ,
Many thanks for the reply.
Basically I want to go with the choice of having PS over Application Sever in a New Zone.
I tried Installing Application server and Portal server in a new Zone,while installing I provided the values for the already Installed Directory Server and Access Manager (which are on diff zones).
The Installation of Portal server was successfull but config failed.I looked into the /var/opt/SUNWportal/logs/config/portal.fabric.0.0.log and found the below error
[#|2007-10-31T14:17:49.638+0000|SEVERE|SJS Portal Server|debug.com.sun.portal.fabric.config|ThreadID=10; ClassName=com.sun.portal.fabric.config.ValidatePortalInputData; MethodName=validateAMSDK; |PSFB_CSPFC0056:Error while validating the SSO Token.
com.iplanet.sso.SSOException: Error occurred while creating SSOToken.
at com.sun.portal.util.SSOUtil.createSSOToken(Unknown Source)
at com.sun.portal.fabric.config.ValidatePortalInputData.validateAMSDK(Unknown Source)
at com.sun.portal.fabric.config.ValidatePortalInputData.<init>(Unknown Source)
at com.sun.portal.fabric.config.ConfigurePortal.main(Unknown Source)
Since the Access Manager and Portal server are on different web containers ( Webserver and Portal Server respectively) , I suppose the above errors are related to those.
Please let me know -
1) Is the deploymen architecture Correct?
2) What can be done to solve the above problem.
Thanks for your time on this post.
Rgds
Lokesh

Similar Messages

Problem installing Sun JES 5u1 on OpenSolaris (snv_b77 x86)

We have a new X4600 server dedicated to tests of the latest Sun-related software stack we could get our hands on to build a demo-installation of "the newest" for a customer, so we installed it with OpenSolaris (snv_b77 was the most recent back then).
After doing the needed tests, we decided to see how the Sun JES behaves with a recent Solaris. We have many Sun JES projects (dating back from Portal 6.0 and JES 2003Q4, JES 4 and 5/5u1); and since Solaris 10u2 (6/06) we host them in zones of a "minimalistically" configured server (approx 270 packages).
When I tried to repeat a similar approach with OpenSolaris (snv_b77) and Sun JES 5u1, the Orion(?) installer behaved differently than on Solaris 10u3 or 10u4. In particular, there are less choice options in Directory Server (i.e. no Directory Proxy Server at all), and a dozen lines in High Availability services (HA for this and HA for that, albeit "Unsupported in zones").
The bigger problem is that the installer doesn't succeed in installing some packages (Cacao, mfwk, jdmk) and configuring the products. I could manually register some of the CACAO components and get a working pair of Directory Server and DPS, now I'm fighting with the Application Server.
What's sad, I don't have to do these tricks with any recent Solaris 10 server we've had set up.
The root of the problem seems to be that the system identifies as "SunOS 5.11" and the installer doesn't seem to support that (installation goes on with a stacktrace that classes for 5_11 could not be found). Example:
PSPERR:++++++++++++++++++++++++++ {Missing Resource Exception in the loading of the PkgRelativePaths{Can't find bundle for base name com.sun.entsys.installer.common.resources.PkgRelativePaths5_11, locale en}}
I made a wrapper script for /sbin/uname which replaces "5.11" with "5.10" and linked "Solaris_11" to "Solaris_10" directories in the unpacked distribution, but these steps did not help.
Does anybody know of tricks required to fool the installer to work in "Solaris_10" mode regardless of the system? Changing programs to wrappers, or replacing /etc/release and similar files are okay - the setup is in a zone dedicated to one task.
Or is there a newer Sun JES beta release which does not need such fooling? :)

I had the same problem this evening on b81, and have had the problem in the past but didn't care long enough to look at it. I do care tonight because I need to use B81 with Crossbow, so as I have VNIC support.
I've spent some time figuring it out (thanks to truss + find) and I've found a way that sorts the issue. You need not rename directories (in fact, this will break it in my experience).
NOTE: Seeing as you've mucked around with directories and so on, unzip a fresh copy of JES.
NOTE: Sun probably don't want you to do this and it is unsupported, do so at your own peril.
Run the installer (I've used text mode):
Unable to access a usable display on the remote system. Continue in command-line mode?(Y/N)
Y
Once you say "Y", I've found it goes off creates a directory called /tmp/.entsys_CaChE
Inside this directory you will find the following seemingly relevant files:
./Solaris_x86/.install/config/PPXMLS/Clusters/EntsysCluster_SUNOS_SPARC_5_10.xml
./Solaris_x86/.install/config/PPXMLS/Clusters/EntsysCluster_SUNOS_X86_5_10.xml
./Solaris_x86/.install/config/PPXMLS/Clusters/OrionCluster_SUNOS_SPARC_5_10.xml
./Solaris_x86/.install/config/PPXMLS/Clusters/OrionCluster_SUNOS_X86_5_10.xml
./Solaris_x86/.install/config/com/sun/entsys/installer/common/resources/PkgRelativePaths5_10.properties
In another terminal window, copy the relevant files for your platform to the same file but with 5_11 instead of 5_10
cd /tmp/.entsys_CaChE
cp ./Solaris_x86/.install/config/PPXMLS/Clusters/EntsysCluster_SUNOS_X86_5_10.xml ./Solaris_x86/.install/config/PPXMLS/Clusters/EntsysCluster_SUNOS_X86_5_11.xml
cp ./Solaris_x86/.install/config/PPXMLS/Clusters/OrionCluster_SUNOS_X86_5_10.xml ./Solaris_x86/.install/config/PPXMLS/Clusters/OrionCluster_SUNOS_X86_5_11.xml
cp ./Solaris_x86/.install/config/com/sun/entsys/installer/common/resources/PkgRelativePaths5_10.properties ./Solaris_x86/.install/config/com/sun/entsys/installer/common/resources/PkgRelativePaths5_11.properties
Then continue the installer as normal.
Then you should get to here:
1. Install
2. Start Over
3. Exit Installation
What would you like to do [1] {"<" goes back, "!" exits}?
And if you continue now things are happy:
Java Enterprise System 5
|-1%--------------25%-----------------50%-----------------75%--------------100%|
Installation Complete
Software installation has completed successfully. You can view the installation
summary and log by using the choices below. Summary and log files are available
in /var/sadm/install/logs/.
All good!
Regards,
Geoff Ongley
http://unixsysadmin.net/ (shameless plug)

Is it sun only release solaris 10 for x86-64 ? then how about 32 bit ?

http://www.sun.com/software/solaris/get.jsp

No, the Solaris 10 GA release bits for x64/x86 support:
- 32-bit "x86" cpus (amd & intel)
- 64-bit "x64" cpus (amd opteron, amd athlon 64 with amd64
extension, intel cpus with em64t extension)

Oracle licensing in Solaris zones

Hi all,
I've read a few documents about Oracle licensing :
http://www.sun.com/third-party/global/oracle/consolidation/Containers_Oracle_041305.pdf
http://www.oracle.com/corporate/pricing/partitioning.pdf
However, there's one thing not clear to me. In Solaris zones, you dedicate threads (usually referred to as 'CPU' on Solaris) to zones. Oracle licensing is always about the number of cores used by the partition, not the number of threads. How do you convert from threads to cores?
I'll give an example:
A T2 system with 2 processors, 8 cores each, 8 threads each (128 threads in total). You create a resource pool with 2 CPUs (threads): 1 thread from one core, and 1 thread from another one (or they are assigned like that for you) and associate a zone that runs Oracle.
I can think of two ways of calculating the number of cores used:
1) divide the number of dedicated threads by the number of threads per core: 2 / 8 = 0.25 (optionally round it up to 1) -- This is how IBM does its licensing.
2) count the number of physical cores that are being used by the zone. In this case this is 2, as the threads are not running on the same core.
Can anyone help me figuring this out?
Thanks!
Regards,
Mathieu

Hi Dezutterm,
I'm not a sales guy, but from how I understand things... you've already figured it out yourself:
dezutterm wrote:
I'll give an example:
A T2 system with 2 processors, 8 cores each, 8 threads each (128 threads in total). You create a resource pool with 2 CPUs (threads): 1 thread from one core, and 1 thread from another one (or they are assigned like that for you) and associate a zone that runs Oracle.
I can think of two ways of calculating the number of cores used:
1) divide the number of dedicated threads by the number of threads per core: 2 / 8 = 0.25 (optionally round it up to 1) -- This is how IBM does its licensing.
2) count the number of physical cores that are being used by the zone. In this case this is 2, as the threads are not running on the same core.
Can anyone help me figuring this out?Like you've seen, Oracle cares about how many cores are running Oracle software, not threads (from "Processor" definition here: http://www.oracle.com/corporate/pricing/technology-price-list.pdf). If you have 2 cores running Oracle software, you take "2" and multiple by the Core Processor Licensing Factor for that model of CPU (http://www.oracle.com/corporate/contracts/library/processor-core-factor-table.pdf) which for a T2 is 0.25... meaning you need 2 x 0.25 = 0.5 processor licenses. If you would have used both threads from the same core, you would need 0.25.
If this isn't correct, somebody please let us know, thanks!
[email protected]

Zfs core dumps in Solaris Zones after patchcluster installation

Hi
I've installed the recommended patch cluster for Solaris 10 (SPARC) on my T2000 Server.
Now after the reboot all the Solaris Zones (got about 10 of them) instantly do zfs core dumps when their booted.
Some Output:
Dec 15 15:34:43 XXXXX genunix: NOTICE: core_log: zfs[1711] core dumped: /var/core/core_XXXXXX_zfs_0_0_1292423682_1711
bash-3.00# svcs
STATE STIME FMRI
online 13:58:50 svc:/system/svc/restarter:default
online 13:58:51 svc:/system/filesystem/root:default
online 13:58:51 svc:/network/loopback:default
online 13:58:53 svc:/network/pfil:default
online 13:58:54 svc:/system/installupdates:default
online 13:58:55 svc:/system/boot-archive:default
online 13:58:56 svc:/network/physical:default
online 13:58:57 svc:/system/filesystem/usr:default
online 13:58:57 svc:/system/identity:node
online 13:58:58 svc:/system/device/local:default
online 13:58:58 svc:/system/keymap:default
online 13:58:58 svc:/milestone/devices:default
online 13:58:58 svc:/system/filesystem/minimal:default
online 13:58:58 svc:/system/rmtmpfiles:default
online 13:58:58 svc:/system/cryptosvc:default
online 13:58:59 svc:/system/identity:domain
online 13:58:59 svc:/system/name-service-cache:default
online 13:58:59 svc:/system/coreadm:default
online 13:58:59 svc:/network/ipsec/ipsecalgs:default
online 13:58:59 svc:/application/print/ppd-cache-update:default
online 13:58:59 svc:/network/ipsec/policy:default
online 13:59:00 svc:/milestone/network:default
online 13:59:00 svc:/network/initial:default
online 13:59:00 svc:/system/manifest-import:default
online 13:59:00 svc:/network/service:default
online 13:59:00 svc:/milestone/single-user:default
online 13:59:00 svc:/network/dns/client:default
online 13:59:00 svc:/network/routing-setup:default
online 13:59:00 svc:/milestone/name-services:default
online 13:59:03 svc:/milestone/sysconfig:default
online 13:59:03 svc:/system/utmp:default
online 13:59:03 svc:/system/console-login:default
offline 13:58:51 svc:/system/sysidtool:net
offline 13:58:51 svc:/network/rpc/bind:default
offline 13:58:51 svc:/system/sysidtool:system
offline 13:58:52 svc:/network/nfs/status:default
offline 13:58:52 svc:/network/nfs/nlockmgr:default
offline 13:58:52 svc:/network/nfs/cbd:default
offline 13:58:52 svc:/network/nfs/mapid:default
offline 13:58:52 svc:/network/inetd:default
offline 13:58:52 svc:/network/nfs/client:default
offline 13:58:52 svc:/system/filesystem/autofs:default
offline 13:58:53 svc:/system/system-log:default
offline 13:58:53 svc:/network/smtp:sendmail
offline 13:58:53 svc:/system/cron:default
offline 13:58:53 svc:/milestone/multi-user:default
offline 13:58:54 svc:/application/management/snmpdx:default
offline 13:58:54 svc:/application/management/dmi:default
offline 13:58:54 svc:/application/management/seaport:default
offline 13:58:54 svc:/network/ssh:default
offline 13:58:54 svc:/milestone/multi-user-server:default
offline 13:58:54 svc:/application/font/fc-cache:default
offline 13:58:55 svc:/application/management/sma:default
offline 13:58:58 svc:/system/sac:default
offline 13:59:00 svc:/network/shares/group:default
offline 13:59:00 svc:/system/boot-archive-update:default
maintenance 15:34:43 svc:/system/filesystem/local:default
uninitialized 13:58:52 svc:/network/rpc/gss:default
uninitialized 13:58:54 svc:/application/font/stfsloader:default
uninitialized 13:58:55 svc:/network/rpc/rstat:default
uninitialized 13:58:55 svc:/application/print/rfc1179:default
uninitialized 13:58:55 svc:/application/x11/xfs:default
uninitialized 13:58:55 svc:/network/finger:default
uninitialized 13:58:55 svc:/network/ftp:default
uninitialized 13:58:56 svc:/network/login:rlogin
uninitialized 13:58:56 svc:/network/nfs/rquota:default
uninitialized 13:58:56 svc:/network/rpc/rusers:default
uninitialized 13:58:56 svc:/network/rpc/smserver:default
uninitialized 13:58:57 svc:/network/security/ktkt_warn:default
uninitialized 13:58:57 svc:/network/shell:default
uninitialized 13:58:57 svc:/network/telnet:default
uninitialized 13:58:58 svc:/network/rpc-100235_1/rpc_ticotsord:default
uninitialized 13:58:58 svc:/network/rpc/cde-calendar-manager:default
uninitialized 13:58:59 svc:/network/rpc/cde-ttdbserver:tcp
bash-3.00# svcs -x
svc:/system/filesystem/local:default (local file system mounts)
State: maintenance since Wed Dec 15 15:34:43 2010
Reason: Start method exited with $SMF_EXIT_ERR_FATAL.
See: http://sun.com/msg/SMF-8000-KS
See: /var/svc/log/system-filesystem-local:default.log
Impact: 24 dependent services are not running. (Use -v for list.)
svc:/network/rpc/gss:default (Generic Security Service)
State: uninitialized since Wed Dec 15 13:58:52 2010
Reason: Restarter svc:/network/inetd:default is not running.
See: http://sun.com/msg/SMF-8000-5H
See: gssd(1M)
Impact: 11 dependent services are not running. (Use -v for list.)
svc:/network/rpc/rstat:default (kernel statistics server)
State: uninitialized since Wed Dec 15 13:58:55 2010
Reason: Restarter svc:/network/inetd:default is not running.
See: http://sun.com/msg/SMF-8000-5H
See: rpc.rstatd(1M)
See: rstatd(1M)
Impact: 1 dependent service is not running. (Use -v for list.)
bash-3.00# cat /var/svc/log/system-filesystem-local:default.log
[ Jul 10 03:41:35 Enabled. ]
[ Jul 10 03:43:45 Rereading configuration. ]
[ Jul 10 03:44:17 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Jul 10 03:44:18 Method "start" exited with status 0 ]
[ Jul 10 12:44:36 Enabled. ]
[ Jul 10 12:44:45 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Jul 10 12:44:45 Method "start" exited with status 0 ]
[ Jul 10 12:45:03 Enabled. ]
[ Jul 10 12:45:09 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Jul 10 12:45:09 Method "start" exited with status 0 ]
[ Jul 10 13:54:39 Enabled. ]
[ Jul 10 13:54:46 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Jul 10 13:54:46 Method "start" exited with status 0 ]
[ Jul 18 12:34:19 Enabled. ]
[ Jul 18 12:34:27 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Jul 18 12:34:27 Method "start" exited with status 0 ]
[ Jul 18 17:29:08 Enabled. ]
[ Jul 18 17:29:15 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Jul 18 17:29:15 Method "start" exited with status 0 ]
[ Jul 19 11:13:34 Enabled. ]
[ Jul 19 11:13:42 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Jul 19 11:13:42 Method "start" exited with status 0 ]
[ Jul 19 11:32:23 Enabled. ]
[ Jul 19 11:32:30 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Jul 19 11:32:31 Method "start" exited with status 0 ]
[ Jul 19 11:57:06 Enabled. ]
[ Jul 19 11:57:13 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Jul 19 11:57:13 Method "start" exited with status 0 ]
[ Jul 19 12:40:05 Enabled. ]
[ Jul 19 12:40:12 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Jul 19 12:40:12 Method "start" exited with status 0 ]
[ Jul 20 15:51:46 Enabled. ]
[ Jul 20 15:51:54 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Jul 20 15:51:54 Method "start" exited with status 0 ]
[ Jul 24 11:42:17 Enabled. ]
[ Jul 24 11:42:25 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Jul 24 11:42:25 Method "start" exited with status 0 ]
[ Jul 27 12:05:06 Stopping because service disabled. ]
[ Jul 27 12:05:07 Executing stop method (null) ]
[ Jul 27 12:13:10 Enabled. ]
[ Jul 27 12:13:17 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Jul 27 12:13:17 Method "start" exited with status 0 ]
[ Jul 27 13:10:26 Stopping because service disabled. ]
[ Jul 27 13:10:26 Executing stop method (null) ]
[ Jul 27 13:18:19 Enabled. ]
[ Jul 27 13:18:26 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Jul 27 13:18:26 Method "start" exited with status 0 ]
[ Jul 31 10:12:31 Enabled. ]
[ Jul 31 10:12:38 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Jul 31 10:12:39 Method "start" exited with status 0 ]
[ Aug 7 10:08:52 Stopping because service disabled. ]
[ Aug 7 10:08:52 Executing stop method (null) ]
[ Aug 7 10:34:50 Enabled. ]
[ Aug 7 10:34:57 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Aug 7 10:34:58 Method "start" exited with status 0 ]
[ Aug 9 09:14:50 Stopping because service disabled. ]
[ Aug 9 09:14:50 Executing stop method (null) ]
[ Aug 9 09:55:03 Enabled. ]
[ Aug 9 09:55:10 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Aug 9 09:55:11 Method "start" exited with status 0 ]
[ Aug 16 10:46:43 Enabled. ]
[ Aug 16 10:46:50 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Aug 16 10:46:50 Method "start" exited with status 0 ]
[ Aug 16 12:06:56 Enabled. ]
[ Aug 16 12:07:02 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Aug 16 12:07:02 Method "start" exited with status 0 ]
[ Aug 16 13:45:10 Enabled. ]
[ Aug 16 13:45:16 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Aug 16 13:45:16 Method "start" exited with status 0 ]
[ Aug 16 14:36:59 Enabled. ]
[ Aug 16 14:37:07 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Aug 16 14:37:07 Method "start" exited with status 0 ]
[ Aug 16 15:00:40 Enabled. ]
[ Aug 16 15:00:47 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Aug 16 15:00:47 Method "start" exited with status 0 ]
[ Aug 22 16:00:13 Enabled. ]
[ Aug 22 16:00:21 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Aug 22 16:00:21 Method "start" exited with status 0 ]
[ Aug 23 09:49:04 Enabled. ]
[ Aug 23 09:49:10 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Aug 23 09:49:11 Method "start" exited with status 0 ]
[ Aug 23 09:49:23 Stopping because service disabled. ]
[ Aug 23 09:49:23 Executing stop method (null) ]
[ Aug 23 10:04:13 Enabled. ]
[ Aug 23 10:04:20 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Aug 23 10:04:20 Method "start" exited with status 0 ]
[ Aug 23 10:06:57 Enabled. ]
[ Aug 23 10:07:04 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Aug 23 10:07:05 Method "start" exited with status 0 ]
[ Oct 23 08:43:05 Enabled. ]
[ Oct 23 08:43:14 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Oct 23 08:43:14 Method "start" exited with status 0 ]
[ Nov 21 14:51:50 Enabled. ]
[ Nov 21 14:51:58 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Nov 21 14:51:59 Method "start" exited with status 0 ]
[ Nov 29 15:33:19 Enabled. ]
[ Nov 29 15:33:26 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Nov 29 15:33:27 Method "start" exited with status 0 ]
[ Dec 18 13:37:35 Enabled. ]
[ Dec 18 13:37:42 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Dec 18 13:37:42 Method "start" exited with status 0 ]
[ Dec 19 08:48:07 Enabled. ]
[ Dec 19 08:48:14 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Dec 19 08:48:14 Method "start" exited with status 0 ]
[ Dec 19 08:56:07 Enabled. ]
[ Dec 19 08:56:14 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Dec 19 08:56:14 Method "start" exited with status 0 ]
[ Dec 19 08:57:41 Enabled. ]
[ Dec 19 08:57:48 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Dec 19 08:57:48 Method "start" exited with status 0 ]
[ Feb 1 10:39:48 Enabled. ]
[ Feb 1 10:39:55 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Feb 1 10:39:56 Method "start" exited with status 0 ]
[ Feb 8 11:12:50 Enabled. ]
[ Feb 8 11:12:57 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Feb 8 11:12:57 Method "start" exited with status 0 ]
[ Jun 6 10:08:34 Enabled. ]
[ Jun 6 10:08:44 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Jun 6 10:08:46 Method "start" exited with status 0 ]
[ Aug 8 09:45:48 Enabled. ]
[ Aug 8 09:46:35 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Aug 8 09:46:36 Method "start" exited with status 0 ]
[ Aug 14 17:53:59 Enabled. ]
[ Aug 14 17:54:06 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Aug 14 17:54:06 Method "start" exited with status 0 ]
[ Aug 14 17:55:20 Enabled. ]
[ Aug 14 17:55:27 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Aug 14 17:55:27 Method "start" exited with status 0 ]
[ Aug 18 15:19:17 Enabled. ]
[ Aug 18 15:19:24 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Aug 18 15:19:24 Method "start" exited with status 0 ]
[ Aug 29 12:56:48 Enabled. ]
[ Aug 29 12:56:55 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Aug 29 12:56:55 Method "start" exited with status 0 ]
[ Oct 13 11:59:43 Enabled. ]
[ Oct 13 11:59:50 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Oct 13 11:59:51 Method "start" exited with status 0 ]
[ Feb 26 16:47:00 Enabled. ]
[ Feb 26 16:47:07 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Feb 26 16:47:07 Method "start" exited with status 0 ]
[ Apr 14 15:54:17 Enabled. ]
[ Apr 14 15:54:24 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Apr 14 15:54:25 Method "start" exited with status 0 ]
[ Aug 28 08:49:58 Stopping because service disabled. ]
[ Aug 28 08:49:58 Executing stop method (null) ]
[ Aug 28 08:52:54 Enabled. ]
[ Aug 28 08:53:01 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Aug 28 08:53:01 Method "start" exited with status 0 ]
[ Aug 28 09:08:20 Stopping because service disabled. ]
[ Aug 28 09:08:20 Executing stop method (null) ]
[ Sep 1 16:05:36 Enabled. ]
[ Sep 1 16:06:05 Executing start method ("/lib/svc/method/fs-local") ]
[ Sep 1 16:06:05 Method "start" exited with status 0 ]
[ Sep 1 19:29:19 Enabled. ]
[ Sep 1 19:29:27 Executing start method ("/lib/svc/method/fs-local") ]
[ Sep 1 19:29:27 Method "start" exited with status 0 ]
[ Sep 1 23:04:00 Enabled. ]
[ Sep 1 23:04:08 Executing start method ("/lib/svc/method/fs-local") ]
[ Sep 1 23:04:08 Method "start" exited with status 0 ]
[ Sep 2 00:23:41 Stopping because service disabled. ]
[ Sep 2 00:23:42 Executing stop method (null) ]
[ Sep 2 00:46:46 Enabled. ]
[ Sep 2 00:46:53 Executing start method ("/lib/svc/method/fs-local") ]
[ Sep 2 00:46:54 Method "start" exited with status 0 ]
[ Sep 26 12:04:34 Enabled. ]
[ Sep 26 12:04:41 Executing start method ("/lib/svc/method/fs-local") ]
[ Sep 26 12:04:42 Method "start" exited with status 0 ]
[ Oct 20 13:05:09 Stopping because service disabled. ]
[ Oct 20 13:05:10 Executing stop method (null) ]
[ Oct 20 13:24:01 Enabled. ]
[ Oct 20 13:24:08 Executing start method ("/lib/svc/method/fs-local") ]
[ Oct 20 13:24:09 Method "start" exited with status 0 ]
[ Oct 21 16:30:59 Enabled. ]
[ Oct 21 16:31:09 Executing start method ("/lib/svc/method/fs-local") ]
[ Oct 21 16:31:09 Method "start" exited with status 0 ]
[ Oct 21 16:32:42 Stopping because service disabled. ]
[ Oct 21 16:32:42 Executing stop method (null) ]
[ Oct 21 16:42:05 Enabled. ]
[ Oct 21 16:42:15 Executing start method ("/lib/svc/method/fs-local") ]
[ Oct 21 16:42:15 Method "start" exited with status 0 ]
[ Oct 21 17:27:37 Enabled. ]
[ Oct 21 17:27:47 Executing start method ("/lib/svc/method/fs-local") ]
[ Oct 21 17:27:47 Method "start" exited with status 0 ]
[ Oct 22 11:08:34 Enabled. ]
[ Oct 22 11:08:43 Executing start method ("/lib/svc/method/fs-local") ]
[ Oct 22 11:08:43 Method "start" exited with status 0 ]
[ Dec 9 09:17:33 Stopping because service disabled. ]
[ Dec 9 09:17:33 Executing stop method (null) ]
[ Dec 10 11:47:14 Enabled. ]
[ Dec 10 11:47:24 Executing start method ("/lib/svc/method/fs-local") ]
[ Dec 10 11:47:25 Method "start" exited with status 0 ]
[ Dec 15 10:52:25 Stopping because service disabled. ]
[ Dec 15 10:52:25 Executing stop method (null) ]
[ Dec 15 12:42:16 Enabled. ]
[ Dec 15 12:42:26 Executing start method ("/lib/svc/method/fs-local") ]
Abort - core dumped
WARNING: /usr/sbin/zfs mount -a failed: exit status 134
[ Dec 15 12:42:28 Method "start" exited with status 95 ]
[ Dec 15 13:13:19 Enabled. ]
[ Dec 15 13:13:28 Executing start method ("/lib/svc/method/fs-local") ]
Abort - core dumped
WARNING: /usr/sbin/zfs mount -a failed: exit status 134
[ Dec 15 13:13:30 Method "start" exited with status 95 ]
[ Dec 15 13:58:51 Enabled. ]
[ Dec 15 13:59:00 Executing start method ("/lib/svc/method/fs-local") ]
Abort - core dumped
WARNING: /usr/sbin/zfs mount -a failed: exit status 134
[ Dec 15 13:59:03 Method "start" exited with status 95 ]
[ Dec 15 15:34:41 Leaving maintenance because clear requested. ]
[ Dec 15 15:34:41 Enabled. ]
[ Dec 15 15:34:41 Executing start method ("/lib/svc/method/fs-local") ]
Abort - core dumped
WARNING: /usr/sbin/zfs mount -a failed: exit status 134
[ Dec 15 15:34:43 Method "start" exited with status 95 ]
bash-3.00# /usr/sbin/zfs mount -a
internal error: Unknown error
Abort (core dumped)
Before that I've installed the patch cluster with halted solaris zones which produced following output:
Application of patches finished : 2010.12.15 12:08:43
Following patches were applied :
119254-77 119812-10 125719-31 140159-03 142911-01
141588-04 119900-11 125731-05 142292-01 142933-02
142251-02 119906-16 126206-05 141444-09 142909-17
118666-28 120460-17 126363-08 141500-07 143140-04
118667-28 121012-03 126365-16 141502-02 143502-01
118777-16 121308-20 126868-04 141506-09 143506-01
140860-02 122212-40 127724-02 141514-02 143615-02
119059-56 122261-03 136998-09 141518-12 143731-01
119213-23 122675-05 137000-07 141552-03 143733-01
124628-10 123003-04 137080-05 141558-01 143977-01
119252-29 123590-12 137147-06 141586-01 144053-04
119280-23 123893-22 138195-04 141590-02 144106-01
124188-03 124393-11 138822-07 141874-09 144254-01
120199-15 124457-02 138826-07 141876-07 144488-04
119534-19 124630-42 138880-02 142084-04 144492-01
120272-28 125215-03 139099-04 142397-01 145124-01
119757-18 125388-03 139620-01 142529-01 145796-01
119783-15 125555-07
Following patches were skipped :
Patches already applied
120900-04 119063-01 119810-05 123005-07 137093-01
121133-02 119081-25 119986-03 124444-01 138866-03
119317-01 119130-33 120061-02 124939-03 137137-09
121296-01 123611-04 120201-05 124943-01 137871-02
138215-01 140899-01 120292-02 124997-01 138181-01
127884-01 122640-05 120329-02 125279-05 138361-01
118712-23 126897-02 121975-01 125539-06 138373-02
118918-24 127755-01 120719-02 125891-01 138647-01
138217-01 125503-02 120830-06 126440-01 141016-01
119578-30 125547-02 121095-02 126540-02 139555-08
121453-02 140796-01 121606-04 127127-11 139967-01
121453-02 120011-14 124171-07 136882-02 140455-01
121118-16 139520-02 123630-03 137032-01 140563-01
118833-36 119764-06
Patches obsoleted by one or more patches already applied
118731-01 124204-04 122660-10
Patches not applicable to packages on the system
121181-03 120410-33 121211-02 125533-15 143317-03
119115-35 120412-11 122259-03 125541-06 143510-01
119117-52 120414-27 122470-03 125952-20 143725-01
119315-19 120543-21 122911-24 137004-08 143727-01
119548-14 120739-06 122958-06 138387-01 143739-01
119903-02 120811-09 123938-02 138824-07 144325-01
120094-30 120849-04 125136-24 138876-01 145006-02
120185-21 121104-11 125137-24 139986-01 145080-01
119368-04 121136-02 125332-14 142244-02 145200-01
120286-03
Installation of patch set complete. PLEASE REBOOT THE SYSTEM.
when i tried to reboot the system by init 6 the service iscsi hanged and produced syslog errors about a unkown iocall -> killed the process. System rebooted w/o errors.
Does anyone have got an idea how to find out which patch or whatever do produce these errors?

Hi,
I'm having the same issue of diskmon core dumps after upgrading grid and database from 11.2.0.1 to 11.2.0.2 on Solaris 10 x86-64. Following this thread, I'm trying to deinstall the Oracle 11.2.0.1 grid home.
I answered the following questions asked by the grid deinstall tool:
1. ASM configuration was not detected in this Oracle home. Was ASM configured in this Oracle home (y|n): y
2. Specify the ASM Diagnostic Destination: /db01/app/oracle/diag/asm/+ASM
3. Specify the diskgroups that are managed by this ASM instance: DATA FRA
4. De-configuring ASM will drop all the diskgroups at cleanup time. Do you want deconfig tool to drop the diskgroups:
If I answer no to question 1, the tool exits with error.
How do I answer question #4? (confused about this question of dropping diskgroups, it's already been upgraded)
Deinstall of Oracle db Home 11.2.0.1 was successful.
The +ASM instance has been upgraded and is running fine under 11.2.0.2 except for the excessive diskmon core dumps.
Thanks,
Lisa
Edited by: user12018917 on Apr 19, 2011 10:21 AM

EM 12c and Solaris Zone Monitoring

Hi all,
I am using Oracle EM 12c to monitor Oracle database server which run on Solaris zone, which is capped to run using only 4 cores.
BUT the Host management home page is still showing "Total Cores" of 8 (I am using Sun T4-1).
Is there some configuration which required to be done to reflect the number of capped CPU.
Also is there a way to isolate the CPU, Memory, Filesystem and Network utilization to only look at the local zone?
I suspect what I see now represent the resource utilization of the physical machine.
Thank you.
-Joel

Loc,
I've opened quite a few SRs, some handled well, some not. My biggest issue perhaps is that SRs are needed at all. We are a small shop that relied on OEM 10.2 for a long time, skipped over 11G and went right to 12R2. It was a culture shock, and I'm not sure if skipping the version added to our woes.
There are 3 DBAs here, with Oracle experience between 13 and 18 years, we are not newbies. I took the em12c class from Oracle.
But still, acceptance of its use has not been high, mostly because it's no longer the quick, targeted place we 'go to'. It's a huge product now, with much built-in. We are finding we need a mind adjustment to use it and the transition period related to how much time we can spend on that. Our intent, though, was to make things easier, not harder.
Case in point is our implementation of DataGuard. This project was new to us and I made EM12C upgrade as a predecessor project because I needed its help. I ultimately abandoned it, we hired a consultant, we learned manual steps, and that's what we use today. Everything is homegrown.
I feel as through the purpose for EM moved from a DBA monitoring tool. Remember OEM 10.2 and its initial summary page that showed the overall health of everything on one shot? I can't do that in em12c, or at least haven't found that.
Here are some SRs:
SR 3-6392247151
Sr 3-7159111371
SR 3-6645421051
* SR 3-6608820051
SR 3-6667182071
* Covers "invalid objects" missing, something we previously relied on.
Back to the original question of this post - I understand now that if we use EM to switch our databases, the role reversal will show. We would have loved to rely on EM for everything. Now that we must do everything manually, I have to then manually drop the target being monitored and re-add it. Again, something that should make our jobs easier is now harder.
Thanks for listening. Am I really the only DBA that says EM12C is harder to use for basic functionality?
Sherrie

SUN JES 6.2 MTA with Symantec_Brightmail_AntiSpam_6.0.5

Hi,
We are trying to configure SUN JES 6.2 MTA with Brightmail antispam_6.0.5, How ever are facing the following erro:
OS is Solaris 10
Brightmail Version 6.0.5
Here below is the imsimta test out:
14:33:24.81: Final result "l|[email protected]|tcp_intranet|@mymx.stj.com:[email protected]"
14:33:24.81: - passed.
14:33:24.81: - orig_mail_access mapping check: ||MAIL|l|[email protected]|l|[email protected]
14:33:24.81: Mapping 7 applied to ||MAIL|l|[email protected]|l|[email protected]
14:33:24.81: Final result "||MAIL|l|[email protected]|l|[email protected]"
14:33:24.81: - passed.
14:33:24.81: Loading spam filter #0, library /opt/symantec/sbas/Scanner/lib/libbmiclient.so.1
14:33:24.81: os_find_image_symbol_v : dlopen failed - ld.so.1: rewrite_test: fatal: libbmishareddata.so: open failed: No such file or directory
14:33:24.81: os_find_image_symbol("/opt/symantec/sbas/Scanner/lib/libbmiclient.so.1", "bmiEndHeaders") returned 2
14:33:24.81: - Spam filter initialization failure: Cannot load spam filter bmiEndHeaders
14:33:24.81: - adding address [email protected] to headers.
14:33:24.81: Copy estimate after address addition is 1
Expanded address:
[email protected]
Submitted address list:
Address list error -- 4.7.1 Cannot load spam filter bmiEndHeaders: [email protected]
Submitted notifications list:
Here below is the /opt/SUNWmsgsr/config/option.dat
Brightmail_Library=/opt/symantec/sbas/Scanner/lib/libbmiclient.so.1
Brightmail_config_file=/opt/symantec/sbas/Scanner/etc/bmiconfig.xml
! Debug Info
OS_DEBUG=1
MM_DEBUG=5
LOG_MESSAGE_ID=1
SEPARATE_LOG_CONNECTION=1------------------------------------------------------
Here are the permissions:
-rwxr-xr-x 1 mailwall bmi 562857 Mar 24 2007 libbmiclient.so.1
-rwxr-xr-x 1 mailwall bmi 14826 Mar 24 2007 libbmishareddata.so---------------------------------------------------------------------------------------------------------------

I haven't used BrightMail before, so guessing from general administrivia: the server can't find the additional libraries (the config lines you showed don't include it explicitly with a full path).
Wild guess: try adding the birghtmail library directory path (/opt/symantec/sbas/Scanner/lib) to LD_LIBRARY_PATH by changing the start scripts for the messaging service, or (not so prone to overwrite by upgrades) by using Solaris crle utility:
crle -u -s /opt/symantec/sbas/Scanner/libIf there are also 64-bit versions of the libraries, also issue this command:
crle -64 -u -s /opt/symantec/sbas/Scanner/lib/amd64for x86_64, or
crle -64 -u -s /opt/symantec/sbas/Scanner/lib/sparcv9for SPARC.

SAP Java and Solaris Zones SolMan 4.0

May require Solaris Zones experience to continue.
I have three SAP database instances/central instances running in three sparse Solaris zones with no problem.
I have created a new sparse zone for a new SAP installation (Solution Manager 4.0) and started the installation. SAP requires a 1.4.2 SDK even though Java 1.5 comes with Solaris 10. The 1.4.2 SDK is in /usr/j2se. The installation in the sparse zone errors out because it can't get "write" rights to /usr/j2se/jre/lib/security/local_policy.jar as it is trying to install some security encryption JCE component.
I have thought about creating a /usr/j2se_zonename file system, copying the contents of /usr/j2se into it and then mounting /usr/j2se_zonename in the zone as a lofs with the name /usr/j2se. However when I do the copy of /usr/j2se I get some recursion errors.
Any thoughts about how to add a writable /usr/j2se into the sparse zone with the least amount of effort ? Otherwise plan B would be to create a "large" zone with a writable /usr directory.
Received a great answer, that while it may not be architecturally "pure" it may get the job done.
You might just download the relevant JDK tarball and unpack that
somewhere in your zone (anywhere you like), and point SAP at it...
http://java.sun.com/j2se/1.4.2/download.html
Get the one called "self extracting file"-- you can unpack that anywhere
you want.
Message was edited by: Atis Purins

Hi Russ,
no you only have to generate two RFCs to your R/3 and assign them in SMSY to for system monitoring
Then you need a Solution, assign your R/3 to the Solution, setup the system monitoring.
Regards,
uDo

Resource Management and Solaris Zones Developer Guide

Solaris Information Products ("Pubs") is creating a
developer guide for resource management and Solaris Zones.
The department is seeking input on content from application
developers and ISVs.
We plan to discuss the different categories of applications
that can take advantage of Solaris resource management
features, and provide implementation examples that discuss
the particular RM features that can be used.
Although running in a zone poses no differences to most
applications, we will describe any possible limitations and
offer appropriate workarounds. We will also provide
information needed by the ISV, such as determining
the appropriate system calls to use in a non-global zone.
We plan to use case studies to document the zones material.
We would like to know the sorts of topics that you would
like to see covered. We want to be sure that we address
your specific development concerns with regard to these
features.
Thank you for your comments and suggestions.

Hi there, i'm using solaris resource management in a
server with more thant 2thousand acounts.
Created profiles for users, defaul, staff, root and
services.Seeing the contents of your /etc/project file could be helpful.
But while using rctladm to enable syslog'ing, I set up
global flags of "deny" and "no-local-action" in almos
everything.The flags on the right hand side of the rctladm(1M) output are read-only:
they are telling you the characteristics of the resource control in question (what
operations the system will allow the resource control to take).
Now, many aplications don't work because they are
denied enough process.max-stack-size and
process.max-file-descriptor for them to work.
Applications such has prstat.If prstat(1) is failing due to the process.max-file-descriptor control value, that's
probably a bug. prstat(1) is more likely bumping into the limit to assess how many file
descriptors are available, and then carrying on--you're just seeing a log message since
prstat(1) tested the file descriptor limit, and you've enabled syslog for that control. Please
post the prstat(1) output, and we'll figure out if something's breaking.
I don't find a way to disable the global flags. You can't. I would disable the syslog action on the process.max-stack-size control first;
there is an outstanding bug on this control, in that it will report a false triggering event--
no actual effect to the process. (If you send me some mail, I will add you as a call record
on the bug.)
Can anyone tell me:
how to disable global flags?
how to disable and enable solaris resource management
all together?You could raise all of the control values, but the resource control facility (like the resource
limit facility it superseded) is always active. Let's figure out if you're hitting the bug I mentioned,
and then figure out how to proceed.
- Stephen
Stephen Hahn, PhD Solaris Kernel Development, Sun Microsystems
[email protected]

SUN JES 8.1 Q2UR2: Intermittently application server jvm crashed.

Application server jvm intermittently crashed but due to the feature in SUN JES 8.1 ur2 the application server will auto restarts the service. Most of the JVM crashes were due to memory corruption.
The following are SUN findings:
1) Multithreading issue that causes 2 threads writing on the same memory block
2) Based on dtrace, it indicated that there was a race condition happens but the jvm doesn�t crash during the occurrence.
Questions:
1) Is it possible that I can use dtrace to monitor the memory block or to find out the root cause?
System information:
Oracle:
DriverVersion: [10.2.0.1.0]
DriverMajorVersion: [10]
DriverMinorVersion: [2]
DriverName: [Oracle JDBC driver]
URL: [jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST= (ADDRESS=(PROTOCOL = TCP) (HOST = XXXXXX) (PORT = 1524)) (ADDRESS=(PROTOCOL = TCP) (HOST = XXXXXX) (PORT = 1524))) (CONNECT_DATA = (SID = CP_P)) (source_route=yes))]
UserName: [CP_P1]
Database Product Name: [Oracle]
Database Product Version: [Oracle9i Enterprise Edition Release 9.2.0.6.0 - 64bit Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.6.0 - Production]
Database Product Major: [9]
Database Product Minor: [2]
Drivers: Type 4
JDK
JDBC Major: [10]
JDBC Minor: [2]
The JDK version is 1.5.0_02
SUN JES Application Server
Sun Java System Application Server Enterprise Edition 8.1_02 running under solaris 10

Most of the
JVM crashes were due to memory corruption.
And how do you know that?
csgan97: Based on sun support input where its due to either trying to read or write to a memory (pblock) that causes the crash.
could identify as a pblock issue
----------------- lwp# 102 / thread# 102 -------------------- fef40f90 lwpkill (6, 0, fef24a98, ffffffff, fef68284, 6) + 8
feebff98 abort (4a600, 1, febbeaac, a83f0, fef6b298, 0) + 110
febb9a9c __1cCosFabort6Fi_v_ (1, 4e10, 10c5b4, 1cb, fecc6000, 4c00) + 58 fec325a0 ???????? (0, fece3ee0, 4000, febbd19c, fec37eee, febbd19c) + 78b5c
fe9ff2d8 JVM_handle_solaris_signal (b, 5931fa70, 5931f7b8, 5000, 4,
184c128) +
9e8
fef3fec8 __sighndlr (b, 5931fa70, 5931f7b8, fe9fe8d0, 0, 1) + c
fef34ff4 call_user_handler (b, ffbffeff, c, 0, 5bb37c00, 5931f7b8) + 3b8 5f2b08fc pblock_kpinsert (4efa78, 1246c28, 1246520, 2c00, 7398ae8,
2e64) + 17c
5f2b0b28 pblock_kvinsert (4efa78, 1246900, 12, 1246520, ff00, 80808080)
+ 108
5f2d5938 INTservact_objset_uri2path (1237c80, 1237cf8, e436b0, 30f4, 680ac6a8,
5f3e5f54) + e4
5f2d77a8 INTservact_handle_processed (1237c80, 1237cf8, 1237c80, 1237cf8, 680ea948, 10ddda0) + 4c 5f31a0ec __1cLHttpRequestUUnacceleratedRespond6Mpc_v_ (1237be0, 5f3ed614, 3114, 50, 1237cf8, 1237c80) + 3c8 5f3197dc __1cLHttpRequestNHandleRequest6MpnGnetbuf__i_ (1237be0, 12442d8, 1246430, 1246410, 1000, 1244338) + 62c
5f317bc4 __1cNDaemonSessionDrun6M_v_ (1234430, 1000, 5f3f3254, 0, 0,
5f3f320c)
+ 17c
627e6dbc ThreadMain (1234430, 1240848, 3, 0, 1, 0) + 24
680d0028 ptroot (1240848, 59320000, 0, 0, 40000, 680e8d70) + d0 fef3fd9c lwpstart (0, 0, 0, 0, 0, 0)
# An unexpected error has been detected by HotSpot Virtual Machine:
# SIGSEGV (0xb) at pc=0x5f2b08fc, pid=16489, tid=102 # # Java VM: Java HotSpot(TM) Client VM (1.5.0_02-b09 mixed mode) # Problematic frame:
# C [libns-httpd40.so+0x308fc] pblock_kpinsert+0x17c #
The following are SUN findings:Meaning Sun (the company) and not you or someone else determined this?
csgan97: From Sun support engineer
1) Multithreading issue that causes 2 threads writing
on the same memory blockSo? That might indicate a bug in your code. By itself it doesn't mean that it caused the crash.
csgan97: If there is a bug, we would like to identify it. All findings are hypothesis and we still dont have evident to really prove that is multithreading issue. Is it possible to use dtrace to track?
2) Based on dtrace, it indicated that there was a
race condition happens but the jvm doesn�t crash
during the occurrence.Again so? I wouldn't expect that to cause a crash.
csgan97: Why? During the jvm crashed, the dtrace monitoring doesnt indicate any race condition. It only indicated twice but during that time the jvm doesnt crash.
DriverName: [Oracle JDBC driver]
URL: [jdbc:oracle:thinIf it is memory corruption then it would be a JVM bug not this driver because it is java only.
If you have any JNI or 3rd party libraries that use JNI then those are the most likely source.
csgan97: A far as we know there isnt any JNI or 3rd party libraries that use JNI.

Best Practices for patching Sun Clusters with HA-Zones using LiveUpgrade?

We've been running Sun Cluster for about 7 years now, and I for
one love it. About a year ago, we starting consolidating our
standalone web servers into a 3 node cluster using multiple
HA-Zones. For the most part, everything about this configuration
works great! One problem we've having is with patching. So far,
the only documentation I've been able to find that talks about
patch Clusters with HA-Zones is the following:
http://docs.sun.com/app/docs/doc/819-2971/6n57mi2g0
Sun Cluster System Administration Guide for Solaris OS
How to Apply Patches in Single-User Mode with Failover Zones
This documentation works, but has two major drawbacks:
1) The nodes/zones have to be patched in Single-User Mode, which
translates to major downtime to do patching.
2) If there are any problems during the patching process, or
after the cluster is up, there is no simple back out process.
We've been using a small test cluster to test out using
LiveUpgrade with HA-Zones. We've worked out most of bugs, but we
are still in a position of patching our HA-Zoned clusters based
on home grow steps, and not anything blessed by Oracle/Sun.
How are others patching Sun Cluster nodes with HA-Zones? Has any
one found/been given Oracle/Sun documentation that lists the
steps to patch Sun Clusters with HA-Zones using LiveUpgrade??
Thanks!

Hi Thomas,
there is a blueprint that deals with this problem in much more detail. Actually it is based on configurations that are solely based on ZFS, i.e. for root and the zone roots. But it should be applicable also to other environments. "!Maintaining Solaris with Live Upgrade and Update On Attach" (http://wikis.sun.com/display/BluePrints/Maintaining+Solaris+with+Live+Upgrade+and+Update+On+Attach)
Unfortunately, due to some redirection work in the joint Sun and Oracle network, access to the blueprint is currently not available. If you send me an email with your contact data I can send you a copy via email. (You'll find my address on the web)
Regards
Hartmut

Clusterware to control solaris zones/containers

Hi,
Does anyone uses crs to control solaris zones/containers?
Is it supported, what are the implementations you have? Do you have the zones installed on a acfs filesystem, ufs or zfs?
How does the crs control them? Scripts?
Regards

Hi,
what exactly do you mean by crs? I only know this term in conjunction with the Oracle Clusterware, which comes with the Grid Infrastructure.
In general there is no build in function from Oracle Clusterware/Grid Infrastructure to control Solaris Zones/Containers, especially if you install the Oracle Grid Infrastructure in the local zone, then you do not have any control for the zone itself. Even if you install GI in the global zone, there are no build in control functions. You would have to write something yourself, but in this case I would use Solaris Clusterware.
So if you need a clusterware to control the zones, I would take Oracle Solaris Clusterware. (Note the difference, this is not the Grid Infrastructure, but the original SUN clusterware).
This also answers your other questions. Solaris Zones cannot be build on ACFS, since ACFS comes with the GI.
So normally zones will be build on ZFS. Solaris Cluster also has build in functionaly to control the zones.
Regards
Sebastian

Are Solaris Zones PCI compliant

We are going through a PCI compliance audit. The auditors are saying that solaris zones are not pci compliant and that we cannot use them. Period. I was wondering if Sun had any insight into this, and possibly how to go around it. I am not happy with the company doing the audit and am not taking their word as the final say. Any help would be greatly appreciated.
thanks

These forums are, generally speaking, a simple user-to-user conversation site.
Theyr're not Sun's techsupport.
(There may be some exceptions on the more esoteric programming topic forums.)
I'd like to suggest you contact your Sun account representative directly.
If there isn't such a person, contact your closest Sun Support Center.
http://www.sun.com/contact/
My understanding of the definition of PCI has always been that it described
an architecture of a particular hardware data bus.
http://en.wikipedia.org/wiki/Peripheral_Component_Interconnect
... the bus and not the data that passes through it.
My rudimentary understanding of the concept of zones
is that they are a 100% software construct.
Since it's possible such a construct could be created
on a number of different hardware architectures,
that audit company is "talking through their @$$" and doesn't have a clue.
Call Sun and get some direct guidance from the company that gave you zones.

SUN JES 8.1 Q2UR2: Long time taken in getting database connection.

Application server registered intermittent slowness in getting database connection from javax.sql.DataSource. Based on the following JMX value, the application servers still haven�t reached the threshold. Its identified the slowness was due to application server performing validation (select count(*) from dual).
Sample code:
ds.getConnection(username, password); // where DS is the javax.sql.DataSource
Network
It is observed that the bi-directional ping stats showed that the response time < 1.19 ms. Network Switch port utilisation was <30% and there were no errors and collision detected.
Database
Based on oracle database statspack, it showed that the database is healthy. On top of that, the following query was scheduled to be executed every second to monitor Select count(*) from dual elapsed time.
select sess.sid, sess.serial#, sess.client_info, sess.program, sql.sql_text, sql.elapsed_time from V$SESSION sess, V$SQL sql where sess.sql_hash_value=sql.hash_value and upper(sql.sql_text) like 'SELECT COUNT(*) FROM DUAL' order by sess.sid
Basically this query will capture the cumulative elapsed time per session id. This query is able to caption �Select count(*) from dual� that ran more than 2 seconds.
Example 1 � how the cumulative elapsed time registered in the log:
2006_11_02_16_53_55,Connection 1, SID 1 perform a select count(*) from dual. Oracle registered elapsed time 10 ms.
2006_11_02_16_53_55,Connection 2, SID 2 perform a select count(*) from dual. Oracle registered elapsed time 10 ms.
2006_11_02_16_54_57,Connection 1, SID 1 perform a select count(*) from dual. Oracle registered elapsed time 20 ms.
2006_11_02_16_54_58,Connection 1, SID 1 perform a select count(*) from dual. Oracle registered elapsed time 30 ms.
2006_11_02_16_54_58,Connection 2, SID 2 perform a select count(*) from dual. Oracle registered elapsed time 20 ms.
Example 2 � If query ran more than 2 sec:
2006_11_02_16_53_55,Connection 1, SID 1 perform a select count(*) from dual. Oracle registered elapsed time 10 ms.
2006_11_02_16_53_57,Connection 1, SID 1 perform a select count(*) from dual. Oracle registered elapsed time 20 ms.
2006_11_02_16_54_57,Connection 1, SID 1 perform a select count(*) from dual. Oracle registered elapsed time 2030 ms. << if query that ran more than 2 secs, there will be a sudden jump of 2 secs in the subsequent cumulative elapsed time.
Previously based on jmx log, it do registered 10k connections was acquired in 1 second and only 6 active connections was used. If same connection was used and on the same second, the cumulative elapsed time will registered in the log. The longest elapsed time that registered in 2 Nov 2006 01:00 pm to 05:00 pm logs was 800 ms but long get database connection still registered 5 to 7 seconds.
Questions:
1) Is it possible that I can use dtrace to capture the bottleneck?
System information:
Oracle:
DriverVersion: [10.2.0.1.0]
DriverMajorVersion: [10]
DriverMinorVersion: [2]
DriverName: [Oracle JDBC driver]
URL: [jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST= (ADDRESS=(PROTOCOL = TCP) (HOST = XXXXXX) (PORT = 1524)) (ADDRESS=(PROTOCOL = TCP) (HOST = XXXXXX) (PORT = 1524))) (CONNECT_DATA = (SID = CP_P)) (source_route=yes))]
UserName: [CP_P1]
Database Product Name: [Oracle]
Database Product Version: [Oracle9i Enterprise Edition Release 9.2.0.6.0 - 64bit Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.6.0 - Production]
Database Product Major: [9]
Database Product Minor: [2]
Drivers: Type 4
JDK
JDBC Major: [10]
JDBC Minor: [2]
The JDK version is 1.5.0_02
SUN JES Application Server
Sun Java System Application Server Enterprise Edition 8.1_02 running under solaris 10

Massive Crossposting:
http://forum.java.sun.com/thread.jspa?threadID=790473&messageID=4491822#4491822
http://forum.java.sun.com/thread.jspa?threadID=790472&messageID=4491819#4491819
http://forum.java.sun.com/thread.jspa?threadID=790471&messageID=4491817#4491817
http://forum.java.sun.com/thread.jspa?threadID=790470&messageID=4491816#4491816
http://forum.java.sun.com/thread.jspa?threadID=790469&messageID=4491815#4491815
http://forum.java.sun.com/thread.jspa?threadID=790468&messageID=4491814#4491814
http://forum.java.sun.com/thread.jspa?threadID=790466&messageID=4491812#4491812

How to auto login in Solaris 10

Hi all
I'm trying to establish auto login in Solaris 10, as a regular user or root. This is a personal testing machine, so security is not an issue.
I want to automatically login preferably in the shell mode, ( no GUI if it's possible ), otherwise I can login with GUI, no biggie.
From what I've found, it does not seem an easy job, given that my Solaris experience is somewhat limited, ( been working more on Linux ).
If I can get that going, I'd prefer to run a few scripts upon login, which I think I can do it.
So what steps must I go through to have auto login upon boot ? How hard is it ?
Appreciate any comments. Thanks
P.S. Just noticed I might have posted in the wrong forum. Sorry !
Which forum should I post again ?
Edited by: mysol on Jul 20, 2009 10:44 AM

ZFS has not yet been integrated into Solaris 10...
At this time you need either the "Software Express for Solaris 2/06"
( http://www.sun.com/software/solaris/solaris-express/ ) or the
"Solaris Express: Community Release"
( http://www.opensolaris.org/os/downloads/on/ ) to play with ZFS.
.

How-To Sun JES 5 on Solaris 10 -Zones

Similar Messages

Maybe you are looking for