Convert Solaris 10 Zones into a Logical Domain

I am in the process of building a Solaris 10 server on a T3-2 server. I am installing the 8/11 update of Solaris 10 and will be installing OVM for SPARC v2.2 on the server to migrate our older physical servers to Logical Domains. Currently we are running a number of Solaris Zones on Solaris 10 servers. Instead of creating a Logical Domain for each of the physical servers with zones on them, I want to convert each of the zones into a logical domain. The zones are running on SunFire V890s and SunFire V440 servers. They are running the 10/09 update of Solaris 10 that has been patched to the latest kernel level, 147440-15. Can anyone guide me in an appropriate procedure to build the logical domains? Thanks.

may be better to move zone into s10 zone inside s11 ldom

Similar Messages

Convert Solaris 10 zones to Logical Domain

I am in the process of building a Solaris 10 server on a T3-2 server. I am installing the 8/11 update of Solaris 10 and will be installing OVM for SPARC v2.2 on the server. Currently we are running a number of Solaris Zones on Solaris 10 servers. Instead of creating a Logical Domain for each of the physical servers with zones on them, I want to convert each of the zones in a logical domain. The zones are running on SunFire V890s and SunFire V440 servers. They are running the 10/09 update of Solaris 10 that has been patched to the latest kernel level, 147440-15. Can anyone guide me in an appropriate procedure to build the logical domains? Thanks.

may be better to move zone into s10 zone inside s11 ldom

Solaris 8, 9, and 10 zones in logical domains

We are planning to migrate our current environment to T5-2.
Current application environment is running with Solaris 8, 9 and 10 OS versions in V8* series and M5000.
Our plan is to install multiple logical domains in T5-2 with Solaris 10 or 11 and migrate the current running Solaris 8, 9 and 10 servers as zones. Plan is to create the flash using flar and restore in the target T5-2.
Will there be any issue with the said OS versions on migration?
Please suggest.

Lars,
Use ldmp2v to convert existing physical server to VM and
Convert Solaris 8 and 9 physical servers to container in Solaris 10 VM?
Is that what you are saying?
Major constraint I have is, applications running in the current physical servers have no vendor support, vendor doesn't exist any more. Application has been locked to run only on the same OS version. What I am worried is, while running ldmp2v should not prevent the application coming up in the new virtualized environment. Keeping that in mind, I gave a thought like
1. Install and configure the CDOM (control domain)
2. configure and Install LDOMs with Solaris 10 OS
3. Run flar on the existing Solaris 10 physical server
4. Transfer the flar created to Solaris 10 LDOM and configure it as a zone
5. For Solaris 8 and 9, create LDOMs with Solaris 10 OS
6. Install additional patches and packages needed for supporting Solaris 8 and 9 zones
6. create flar images on the existing Solaris 8 and 9 physical servers
7. transfer the images to newly created LDOM and configure the zone.
8. Current servers sun4u which has to be converted to sun4v.

Zones or Logical Domains

Hello,
If I have an Enterprise T5120 server, would I be better off employing solaris zones or logical domains? I took a long break from this area of expertise and find myself in the wonderful world of virtualization!
Also, if you have any recommendations on books, whitepapers, other documentation, etc., that I can read on both subjects, I would be very appreciative.
Thank you for you assistance.

Well, you could use both :)
did you see this article? I find it rather good:
http://blogs.oracle.com/bobn/entry/zones_vs_ldoms
.7/M.

Convert system time into User local time.

Hi,
How to convert System time into User Local time.
Are there any FMs available.
Regards,
Kiran

hi,
There is just one simple funda behind the Date and time logic in SAP.
-> It is absolutely useless to store Date and time directly in DB. Why ?
Because 00:00 a.m in London could mean 05:30 in India !! So If I (in India) store a Date 1st Feb 2008 , 10:00 a.m .. This time for a person in London could be invalid.. because he is behind your time zone..
So the solution is to store the date/times in Timestamps format. Taking the above example.. 1st Feb 2008, 10:00 a.m (in India) will be stored as 20080201043000.
This time if seen in German Time zone will look as : 1st Feb 2008, 05:30 a.m.
Simple right
-> In India we store date as DD.MM.YYYY while in other countries they store it as MM.DD.YYYY.
The separator could be . or - or / .
The date format is user dependent. I might prefer to store it as DD.MM.YYYY and you might want to store it as MM-DD-YYYY.
System does not bother what your format is. It always stores in YYYYMMDD (8 Char)
On screens if you want to display Date then it must always be shown in that users format who is seeing it. How to get this done ?
DATA : lv_date(10) type c.
write sy-datum into lv_date.
So in LV_DATE variable the date will be stores in the users format.
Simple right
There are function modules that do the same. But normally we should avoid use of FM to make code simpler, short and easy... no complications at all ..
You can use system variables sy-datlo (Local Date for Current User) and sy-timlo ( Local Time of Current User ).
You can also use GET TIME statement.
reward if useful,
preet

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

How to create Logical domain in Sun Fire T2000 server

Hi,
I am new to this Logical domain, Can some one provide me doc to install a guest OS in logical domain.I have sun T 2000 server with solaris 10 OS
Regards
Alex

Hi Alex,
this is a good place to start reading (even though it refers to LDOMs 1.0):
http://www.sun.com/blueprints/0207/820-0832.pdf
followed by here for the docs set for whichever version you're using - have fun!
http://docs.sun.com/app/docs/prod/ldoms

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

Convert Solar Hejra(Hijri) date to Anno Domini date

Hi everyone:
I am developeing an application cfm format. The company has
some paper forms that the dates are in Solar Hejra(Hijri) date
format and I need them to be converted into Anno Domini date. Do
you know any solution/tutorial or ready_to_use code in cfm format?
Or if it is not avaiable what do you seggest? I use some javascript
code? Do you know one that does it for me?
Thanks
Benign

Benign wrote:
> Hi:
> Thanks for the fast reply.
> I will work on and try to make a neat convertor but do
you know any
> ready_to_use convertor? The one that only converts
Persian Date into Gregorian
> Date it is all I need.
that *is* a ready to use convertor. to convert the islamic
calendar dates to
gregorian (well to cf datetime objects) you use the
i18nDateParse function. you
can ignore the rest of the methods in that CFC (though if you
deal w/this sort
of thing once, you'll likely deal with it again). the only
tricky bit is knowing
if the original islamic dates are based on civil or religious
calendars.

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]

How do you convert a quotation into a purchase requisition?

How do you convert a quotation into a purcahse requisition?

Hi Ganesh
But from ME51N in shows selection varaint it show RFQ for creation of Requisition but when you drop the RFQ to header for creation , it is not working..
Chek again.
Kishor
Hi Christopher
See Purchase requisition creation can happen without vendor and price details as well.
so once you have finalised your vendor and price ,you can put the vendor and price details in PR and then PR can go further for approval...there will be some manual work ,,but I do not think any more option available.
hope its logical,.
Kishor

Cluster Patch on Solaris Zones

Hi all,
Lately, there is a requirement for us to perform a cluster patch on some of
our Solaris Zone VMs. Under such circumstances, is there a need to patch
the global zone also ? What are the precautionary measures to take in case
things break and system goes into panic mode ?
Pls provide all necessary steps and procedures. Thanks a lot.
Regards,
LP

There are many available patch clusters, however you would normally use the 'Recommended Patch Cluster" or the latest dated cluster, for example "10/08 Patch Bundle". Note that the latest bundles have been split into multiple parts due to the size increase from older bundles.
Please refer to the [download instructions|http://sunsolve.sun.com/html/cluster_bundle.html] and the readme for the relevant cluster that you download. Note that a password is required to apply that patch clusters and that the password can be found in the readme.
If you run into any problems with the clusters, please contact [email protected] .

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.

LDOMs, Solaris zones and Live Migration

Hi all,
If you are planning to use Solaris zones inside a LDOM and using an external zpool as Solaris zone disk, wouldn't this break one of the requirements for being able to do a Live Migration ? If so, do you have any ideas on how to use Solaris zones inside an LDOM and at the same time be able to do a Live Migration or is it impossible ? I know this may sound as a bad idea but I would very much like to know if it is doable.

Thanks,
By external pool I am thinking of the way you probably are doing it, separate LUNs mirrored in a zpool for the zones coming from two separate IO/Service domains. So even if this zpool exist inside the LDOM as zone storage this will not prevent LM ? That's good news. The requirement "no zpool if Live Migration" must then only be valid for the LDOM storage itself and not for storage attached to the running LDOM. I am also worried about a possible performance penalty introducing an extra layer of virtualisation. Have you done any tests regarding this ?

Convert Solaris 10 Zones into a Logical Domain

Similar Messages

Maybe you are looking for