8-way SMP with Solaris 8 x86

We're pondering the purchase of two 8CPU Intel boxes to run Oracle Parallel server. Since Oracle Parallel Server has not been ported to Linux, we'll need to run Solaris x86.
Now, my question: Does Solaris 8 x86 support 8 CPUs? I called Sun and was told no and e-mailed them and was told yes. So, I got two different answers. Can anyone point me to a definative answer?
Thanks,
Mike

Mike, Oracle Parallel server is not supported on Intel Solaris. ;-) check with Oracle (this should be true for 8.1.6 and maybe also 8.1.5). I do not believe you want to turn to Oracle7 in these modern days...

Similar Messages

Please suggest the fastest way to install Solaris x86 PC 30 boxes

I've already tested one and it's successfully installed.
I have to install 30 boxes , all are same spec.
Please advise the fastest procedure to install.
Note : There is no sparc machine.

Only problem with imaging a Solaris x86 box is that your machines will end up with the same hostid (which is pseudo-randomly generated at Solaris installation time for x86). This may, or may not, be a problem, depending on what commercial software you use...
To avoid this, you have to use jumpstart, or do some serious hacking.

Solaris x86 with Oracle RAC 10g Enterprise Edition Release 10.2.0.3.0

Hello,
Maybe you can help me (new on RMAN backup) in doing this.
I have configured a single Oracle 10g database to have backup with RMAN with following steps:
1. $ mkdir $ORACLE_BASE/rman_scripts
2. $ mkdir $ORACLE_BASE/logs
3. $ mkdir $ORACLE_BASE/tracking
4. $ mkdir $ORACLE_BASE/c_backup
5. $ sqlplus sys/<password> as sysdba
6. SQL> alter system set db_recovery_file_dest_size = 50G scope=both;
7. SQL> alter system set db_recovery_file_dest='${ ORACLE_BASE}/flash_recovery_ area' scope=both;
8. SQL> alter system set log_archive_dest_10='location= use_db_recovery_file_dest';
9. SQL> shutdown immediate
10. SQL> startup nomount
11. SQL> alter database archivelog;
12. SQL> alter database open;
13. SQL> alter database enable block change tracking using file '${ORACLE_BASE}/tracking/rman_ change_track.f';
14. $ rman target /
15. RMAN> CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK
TO '/var/opt/oracle/flash_ recovery_area/ORCL/c_backup/% F';
16. RMAN> CONFIGURE CONTROLFILE AUTOBACKUP ON;
17. RMAN> CONFIGURE BACKUP OPTIMIZATION ON;
18. RMAN> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
19. RMAN> exit
I need to configure incremental backup with RMAN on a two node Solaris x86 with Oracle RAC 10g Enterprise Edition Release 10.2.0.3.0 installation.
We also use ASM to store database files, and have Oracle software installed on separate file systems (two Oracle roots for Node1 and Node2).
I have following questions:
1) where to put Flash Recovery Area (FRA)?
I saw recommendations to put FRA on the ASM, is this the best way to do it?
2) Can I put FRA on another file system (not on the ASM) which is available only from Node1? This way I can save space on the ASM.
3) Is it possible/recommended to run RMAN from Node1 only?
Below is the script used to run RMAN on the normal Oracle database (without RAC) which I need to change :
=============================================================================================
2.0 Oracle backup script: /opt/app/oracle/rman_scripts/backup.sh
Use this for daily backups, possiblly as a cron job.
Once a week run this: /opt/app/oracle/rman_scripts/backup.sh FULL
All other days of the week: /opt/app/oracle/rman_scripts/backup.sh INCREMENTAL
Note: You may have to change ORACLE_SID, ORACLE_BASE below to match your database.
=============================================================================================
#!/usr/bin/ksh
ORACLE_SID=orcl
ORACLE_BASE=/opt/app/oracle
ORACLE_HOME=${ORACLE_BASE}/product/10.2.0/db_1
PATH=${ORACLE_HOME}/bin:/usr/bin
LOGDIR=${ORACLE_BASE}/logs
LOGFILE=${LOGDIR}/rman.log
if [[ $# < 1 ]]
then
echo "usage: backup.sh FULL|INCREMENTAL"
exit;
fi
BACKUPTYPE=${1}
full='FULL'
incremental='INCREMENTAL'
if [[ $BACKUPTYPE == $full ]]
then
$ORACLE_HOME/bin/rman target / nocatalog log ${LOGFILE} append << eof
run {
backup database;
SQL 'alter system archive log current';
backup archivelog all;
delete noprompt obsolete;
exit;
eof
echo ''
fi
if [[ $BACKUPTYPE == $incremental ]]
then
$ORACLE_HOME/bin/rman target / nocatalog log ${LOGFILE} append << eof
run {
backup database;
backup incremental level 1 database;
SQL 'alter system archive log current';
backup archivelog all;
delete noprompt obsolete;
exit;
eof
echo ''
fi

Hi [email protected],
Q1) where to put Flash Recovery Area (FRA)?
A1) With RAC: on the shared storage
I saw recommendations to put FRA on the ASM, is this the best way to do it?
If you want your backups to be available for both nodes you have to use shared storage or tape using an mml library.
So if you want to use the FRA for rman backups and the database is on ASM just make ASM the standard for the FRA as well.
Q2) Can I put FRA on another file system (not on the ASM) which is available only from Node1? This way I can save space on the ASM.
A2) Than you cannot recover in case Node1 is down. Best would be to send your storage admin to a training course so he can manage the clustered raw devices needed for ASM.
Q3) Is it possible/recommended to run RMAN from Node1 only?
A3) No see A2.
Regards,
Tycho

Intel network interface with Solaris 10 x86

Hi,
I have been Googling all evening to try and find a solution to this, but here is the problem:
I have a PC built around an Asus P4C800-E system board, and I have Solaris 10 x86 01/2006 installed. I would like to get the Ethernet interface (Intel adaptor, running on a CSA bus) up and running - but for some reason I can't seem to get the driver to bind to the proper address (pci8086,1019 - from what I have been able to find out): It instead insists on binding to pci1043,80f7. Even though pci8086,1019 is listed in /etc/device_aliases, it won't play nice.
I know the NIC is working, and have tried it under other OSes (including Linux).
Although Solaris x86 "sees" something there, and the interface is plumbed (it can even tell when the network link is up or down), I can't get the interface to work - pings do not work, etc.
Is there a way I can convince the driver to bind to pci8086,1019 instead of pci1043,80f7?
Any assistance would be greatly appreciated.
Joovilhar.

<table border="0" align="center" width="90%" cellpadding="3" cellspacing="1"><tr><td class="SmallText"><b>Joovilhar wrote on Wed, 08 March 2006 02:14</b></td></tr><tr><td class="quote">
I can't seem to get the driver to bind to the proper address (pci8086,1019 - from what I have been able to find out): It instead insists on binding to pci1043,80f7. Even though pci8086,1019 is listed in /etc/device_aliases, it won't play nice.
</td></tr></table>
Is 1043,80f7 the device's pci subsystem vendor and subsystem device id?
And 8086,1019 is the normal vendor/device id?
In this case everything would work as expected.
What is listed by "/usr/X11/bin/scanpci -v" for the ethernet controller?
<table border="0" align="center" width="90%" cellpadding="3" cellspacing="1"><tr><td class="SmallText"><b>Quote:</b></td></tr><tr><td class="quote">
I know the NIC is working, and have tried it under other OSes (including Linux).
Although Solaris x86 "sees" something there, and the interface is plumbed (it can even tell when the network link is up or down), I can't get the interface to work - pings do not work, etc.
</td></tr></table>
Try to boot the kernel with various settings of the "acpi-user-options" variable,
to disable / enable ACPI. In previous Solaris x86 releases, when
something went wrong configuring an interrupt vector for a nic device,
the typical end result is a nic that is unable to receive incomming
packets. Maybe your Asus P4C800-E is still problematic with ACPI, with
S10 x86 1/2006, and needs the acpi-user-options workaround.
http://blogs.sun.com/roller/page/danasblog?anchor=configurin g_solaris_acpi_at_boot
To change the "acpi-user-options" variable, edit the grub boot command
line and edit the "multiboot" line, e.g. append "-Bacpi-user-options=0x2".

Networking with solaris 7 on x86

Hi all
i installed Solaris 7 on 2 intel pcs. At the time of installing solaris 7, i was only asked to provide the host name, it didn't ask for the IP address. So after installation I saw a line in /etc/hosts file which is different from Sparc machines. Here is how it looked:
127.0.0.1 localhost loghost neptune
where neptune the local machine name, where i installed the os. Now i edited the /etc/hosts file following way
127.0.0.1 localhost
175.145.135.10 neptune loghost
after saving it, i tried to ping it:
ping neptune or ping 175.145.135.10
i get error message saying "ICMP error, host/gateway unreachable"
Does anyone have idea how to do networking in x86 running on Solaris 7???
thanks
Pranoz

Hi Allen
thanks for your help. I did that, but still it did not ask me for ip address or any network info. Then i tried to manually update /etc/hosts file with following lines it:
127.0.0.1 localhost
175.165.155.10 neptune loghost
After that i rebooted the machine and tried to
1. ping 127.0.0.1
2. ping neptune
3. ping 175.165.155.10
#1 returns "127.0.0.1' is alive. But #2 and #3 return following message:
ICMP Net unreachable from gateway localhost (127.0.0.1) for ICMP from localhost(127.0.0.1) to neptune(175.165.55.10)"
Does anyone has any experience/idea about how to configure network with solaris 7 on Intel platform??
Your help is grealty appreciated
thanks
Pran

Several mysterious problems with Solaris 11 x86 install

Hi folks,
I've recently installed Solaris 11 x86 as a replacement for Solaris 9 SPARC on an Ultra 2 machine. I like the operating system, but I've promptly acquired some mysterious problems. The computer is a Fujitsu Siemens Esprimo E2500 with a Pentium 4 HT 3.06 GHz processor, 2 GB RAM, an 80 GB SATA disk and a 147 GB SCSI disk.
I have had a few occasions on which the screen goes totally blank, the monitor claims that there is no signal, and I have to restart the machine. However, with the blank screen, the hard drive activity light is sometimes still flashing. This happens predictably when I try to log off (as opposed to shutting down) and when I use Totem media player and click on anything inside the Totem window. The motherboard has built-in graphics and brief specifications can be found here:
http://uk.ts.fujitsu.com/rl/servicesupport/techsupport/professionalpc/ESPRIMO/Datasheets/ds_esprimo_edition_e2500.pdf
Yesterday my PS/2 keyboard started causing the motherboard to beep crazily when I use it. It beeps rapidly 4 times, then prints the expected character. However, the problem doesn't occur at the initial log in screen. The mouse cursor has also gone beserk on one occasion, flying all over the screen (I had this problem with a previous PC, but a different OS, and thought it was a hardware fault, which I why I got this new computer). With the keyboard problem, the machine is basically unusable. However, it is configured as a dual boot machine, and the keyboard problem isn't present with Windows XP.
There are also a few smaller, odd problems. Occasionally all the icons vanish from my Gnome desktop. The command prompt also mysteriously changed from $chris@pluto to $bash-4.1 just before the keyboard problem appeared, although that might have had something to do with me copying my home directory to a different disk and editing the /etc/auto_home file (moving the home directory worked fine). Also, unlike with Solaris 9 SPARC, I find that I have to have external SCSI devices switched on at boot time, should I want to use them later. That's a pain. With Solaris 9, I could run "boot -r" when I first attached the device, then switch on the SCSI devices and mount them whenever I wanted.
After the useful advice I received here about "more" and "less", I thought I'd post these problems and see if anyone can help. I'd really appreciate some advice. Can anyone identify likely causes for these problems? Which problems can I expect to solve and which do I have to live with?
Many thanks,
Chris Tidy
Edited by: Chris Tidy on 23-Mar-2012 03:36

Hi folks,
I've recently installed Solaris 11 x86 as a replacement for Solaris 9 SPARC on an Ultra 2 machine. I like the operating system, but I've promptly acquired some mysterious problems. The computer is a Fujitsu Siemens Esprimo E2500 with a Pentium 4 HT 3.06 GHz processor, 2 GB RAM, an 80 GB SATA disk and a 147 GB SCSI disk.
I have had a few occasions on which the screen goes totally blank, the monitor claims that there is no signal, and I have to restart the machine. However, with the blank screen, the hard drive activity light is sometimes still flashing. This happens predictably when I try to log off (as opposed to shutting down) and when I use Totem media player and click on anything inside the Totem window. The motherboard has built-in graphics and brief specifications can be found here:
http://uk.ts.fujitsu.com/rl/servicesupport/techsupport/professionalpc/ESPRIMO/Datasheets/ds_esprimo_edition_e2500.pdf
Yesterday my PS/2 keyboard started causing the motherboard to beep crazily when I use it. It beeps rapidly 4 times, then prints the expected character. However, the problem doesn't occur at the initial log in screen. The mouse cursor has also gone beserk on one occasion, flying all over the screen (I had this problem with a previous PC, but a different OS, and thought it was a hardware fault, which I why I got this new computer). With the keyboard problem, the machine is basically unusable. However, it is configured as a dual boot machine, and the keyboard problem isn't present with Windows XP.
There are also a few smaller, odd problems. Occasionally all the icons vanish from my Gnome desktop. The command prompt also mysteriously changed from $chris@pluto to $bash-4.1 just before the keyboard problem appeared, although that might have had something to do with me copying my home directory to a different disk and editing the /etc/auto_home file (moving the home directory worked fine). Also, unlike with Solaris 9 SPARC, I find that I have to have external SCSI devices switched on at boot time, should I want to use them later. That's a pain. With Solaris 9, I could run "boot -r" when I first attached the device, then switch on the SCSI devices and mount them whenever I wanted.
After the useful advice I received here about "more" and "less", I thought I'd post these problems and see if anyone can help. I'd really appreciate some advice. Can anyone identify likely causes for these problems? Which problems can I expect to solve and which do I have to live with?
Many thanks,
Chris Tidy
Edited by: Chris Tidy on 23-Mar-2012 03:36

Solaris x86 with card on-board

Hi all,
I got a problem when installing Solaris9 x86 on ibm NetVista Machine.
I have installed 2 other machines with separated network card sucessfully. I can configure to connecto to my LAN network.
But when install on 2 ibm NetVista machines (which include onboard network card ), It is fail to be configured to connect to the network in both following cases:
Case 1: I choose proper driver as Sun suggest for Intel VE Pro(R) 10/100 : iprb. And the Solaris detect successfully. I checked by "ifconfig -a" and saw the network card active on "iprb0".
Next, I following correct instructions to configure the network card to connect to the LAN. But when i ping IP (9.187.186.18) to other computer in our same subnet LAN,
The system display eg: "No anwer from 9.187.186.18"
I run the "snoop" command to view broadcasr ARP in an other terminal. The snoop terminal displays ARP signal boradcasting from the Solaris. However, it can nerver get ARPs from other computer in LAN.
Case 2: I add 3COM network driver to the solaris ( onboard card is no loger used ). The system can auto-detected this card and i can configure to connect to the network. The problem remain unchange.
Is there any special in IBM Netvista machine need to be configure under Solaris x86 or any particular configuarion for on-board network card. ???
Can any boy help me to solve this problem ??
Best regards,
Thang,
Vietsoftware Developer

However, it can nerver get ARPs from other computer in LAN.Are you perhaps running "snoop" on a box different from the one that you're trying to ping, and are you using
a switched ethernet? In that case it would be OK if you only see the ARP broadcast, because the ping target
box will send the ARP reply directly to the MAC of the requesting station (i.e. there's no ARP broadcast reply),
and an ethernet switch will send the ARP reply directly to the port where the station with the given destination
MAC is connected - no other port should see the reply.
If you're trying to ping 9.187.186.18 from the new Solaris x86 box, try to run snoop on the 9.187.186.18
system. 9.187.186.18 should see the ARP broadcast from the LAN, and the 9.187.186.18 box should list the
ARP response it sends back to the LAN.
Is there any special in IBM Netvista machine need to be configure under Solaris x86 or any particular
configuarion for on-board network card. ???I guess the interrupt handler for the NIC is not working, so the Solaris x86 sees no incomming packets.
See the "troubleshooting" section on the following page:
http://solaris-x86.org/documents/tutorials/rtls.mhtml

Bind DMA handle fails with Solaris 10 x86

Our device driver and device uses no scatter gather and
we have always set the sgllen filed of the DMA_ATTR to 1.
Even so, ddi_dma_buf_bind_handle() would often result in
more than one dma cookie for a transfer on most x86 systems.
We handle this in the device driver, starting a new transfer from
the device for each cookie.
Along comes Solaris 10 and ddi_dma_buf_bind_handle() fails with a
DDI_DMA_TOOBIG error for all DMA transfer over 1200 bytes or so.
We are not sure what changed in Solaris 10 to cause our method to
no longer work.
Is the correct thing to simply set the sgllen field to -1?

Following up on my previous post ....
Setting the dma_attr_sgllen field of the DMA_ATTR to -1
does seem to solve the problem for Solaris 10. It works
on sparc v9, intel32 and amd64 platforms.
However, it does not work with Solaris 9 on x86 platforms.
In this case, ddi_dma_buf_bind_handle() fails with a
DDI_DMA_BADATTR error.
On sparc platforms it does not seem to matter. A value of
either 1 or -1 works for both Solaris 9 and 10.
In order to maintain backwards compatibility, we will need to
make use of autoconf variables, having our conifgure script
substitute an appropriate value for the dma_attr_sgllen
based on the host operating system version.

Help with evaluation for Solaris x86

Hello,
I would like to evaluate Oracle Identity Manager and Access Manager products at the latest version possible -- the host system(s) are Solaris x86 (SunOS .5.10) Unfortunately, I am having a bit of trouble compiling the list of packages/versions to achieve this for this platform. For instance, on the downloads page it appears that OIM is not available for Solaris x86, not even in older versions(?)
Thank you in advance,
Scott

Hi Scott,
I'm pretty sure that x86 Solaris is not yet certified to run the Identity Management suite. I've been involved in an evaluation process and we ran it all on RedHat Enterprise Server Release 4 Update 5, without too many problems.
cheers,
James

Help with oracle 10g install on solaris x86

hi, i downloaded solaris 10 from oracle site (sol-10-u8-ga-x86-dvd.iso) and i have installed it on vmware. i was going through the installation guide for oracle 10 for solaris x86 and while on the pre-installation steps, i issued this command
# /bin/isainfo -kv
and it gave me
# 64-bit amd64 kernel modules
instead of
# 32-bit i386 kernel modules
as the guide expected.
please what can i do, cos the guide says if i dont see the later, the installation cannot complete.
thnx

First check you Operating System Bit information whether it is 64 or 32 bit , for this first check any of the command path
Example ls command
$ which ls
/usr/sbin/ls
$ file /usr/sbin/ls
It will show you whether your OS is 64 bit or 32 bit and accordingly download the software from below link ,if it is showing 64 bit os then you have to download 64 bit database software .
http://www.oracle.com/technetwork/database/database10g/downloads/index.html

Dell Hardware on Linux or Solaris x86

Hi,
My company is considering moving to dell hardware in a move to drive TCO down. We currently run Sun sparc (240, 490,890) servers and they are nearing end of life. Doing the research, even visited some vendors and from what we've seen, running either RH 5 or even Solaris (x86) on Dell could prove to be a good move. We're running mostly 10.2 databases with a couple of 9.2 that we hope to have upgraded by year end.
Has anyone made a similar move and what is your experience? I worked on Dell about 4 years ago and back then we felt there were reliability issues. They crashed a little too often for my liking. I realize some of it was do to OS panics and not just hardware but that is part of the package.
Any feedbackup would be greatly appreciated.

If you're going to go Dell, you might aswell go the whole way and run RedHat.
Aside from the support issues mentioned (I'm not familiar with that aspect) Solaris has a history of being much more expensive to run (largely due to the cost of the employees that know it) with the major advantage being: better integration with Sun hardware.
As for Dell reliability, there's a reason we're an HP shop..

Mounting a Solaris x86 CD/DVD from a remote Windows CD/DVD-ROM drive

Greetings, all.
Is it possible to mount a remote Windows CD/DVD-ROM drive? I have the Solaris 10x86 Companion Software DVD sitting in a CD/DVD-ROM drive that's installed on a Windows server on my network. It is shared-out (F:) and the two servers can ping each other. I've also confirmed the NFS services/daemons are running on the Solaris x86 machine. I've tried the following variations but, all have failed to produce successful results:
# mount -F nfs x.x.x.x:/f /mnt
nfs mount: x.x.x.x: : RPC: Program not registered
nfs mount: retrying: /mnt
# mount -F hsfs x.x.x.x:/f /mnt
mount: No such device
mount: cannot mount x.x.x.x:/f
# mount -F hsfs x.x.x.x:/F /mnt
mount: No such device
mount: cannot mount x.x.x.x:/F
[FYI: S10_106_SOFTWARE is the DVD's label as reported by Windows Explorer.]
# mount -F hsfs x.x.x.x:/S10_106_SOFTWARE /mnt
mount: No such device
mount: cannot mount x.x.x.x:/S10_106_SOFTWARE
# mount -F hsfs x.x.x.x:/s10_106_software /mnt
mount: No such device
mount: cannot mount x.x.x.x:/s10_106_software
# mount -F nfs x.x.x.x:/S10_106_SOFTWARE /mnt
nfs mount: x.x.x.x: : RPC: Program not registered
nfs mount: retrying: /mnt
# mount -F nfs x.x.x.x:/s10_106_software /mnt
nfs mount: x.x.x.x: : RPC: Program not registered
nfs mount: retrying: /mnt
# mount -F hsfs x.x.x.x:/f/s10_106_software /mnt
mount: No such device
mount: cannot mount x.x.x.x:/f/s10_106_software
# mount -F hsfs x.x.x.x:/F/s10_106_software /mnt
mount: No such device
mount: cannot mount x.x.x.x:/F/s10_106_software
# mount -F hsfs x.x.x.x:/f/S10_106_SOFTWARE /mnt
mount: No such device
mount: cannot mount x.x.x.x:/f/S10_106_SOFTWARE
# mount -F hsfs x.x.x.x:/F/S10_106_SOFTWARE /mnt
mount: No such device
mount: cannot mount x.x.x.x:/F/S10_106_SOFTWARE
I've also tried mounting it at bootup by adding the appropriate entry in the /etc/vfstab file but, this does not work as well. I've tried Google'ing for an answer to my issue but, I haven't been able to find anything that applies directly to what I'm reporting. It's usually chatter about mounting from one UNIX server to another. Any advice from the community would be greatly appreciated.

After three weeks, you deserve a reply. Windoze does
not natively support NFS.Also deserves a decent answer...
There are two ways to do this:
Install Microsoft's free "Windows Services for UNIX," which includes a Windows NFS server; or
Install the 'sharity' package (google for it); it provides Solaris systems the ability to mount Windows shares

1) How to Boot from SAN for T4-1 Server with Solaris 11.1 OS on the disk? 2) How to SMI Label/Format a disk while OS Installation in Solaris 11.1?

FYI....boot from SAN is required for physical server (T4-1) (not OVM).
1) How to Boot from SAN for T4-1 Server with Solaris 11.1 OS on the disk?
The SAN disks allocated are visible in ok prompt. below is the output.
(0) ok show—disks
a) /pci@400/pci@2/pci@0/pci@f/pci@0/usb@0, 2/hub@2/hub@3/storage@2/disk
b) /pci@400/pci@2/pci@0/pci€a/SUNW, ezalxs@0, l/fp@0, 0/disk
e) /pci@400/pci@2/pci@0/pci@a/SUNW, ealxs@0/fp@0, 0/disk
d) /pci@400/pci@2/pci@0/pci@8/SUNW, emlxs@0, l/fp@0, 0/disk
e) /pci@400/pci@2/pci@0/pci@8/SUNW,enlxs@0/fp@0,0/disk
f) /pci@400/pci@2/pci@0/pci@4/scsi@0/disk
g) /pci@400/pci@1/pci@0/pci@4/scsi@0/disk
h) /iscsi—hba/disk
q) NO SELECTION
valid choice: a. . .h, q to quit c
/pci@400/pci@2/pci@0/pci@a/SUNW, ealxs@0/fp@0, 0/disk has been selected.
Type “Y ( Control—Y ) to insert it in the command line.
e.g. ok nvalias mydev “Y
for creating devalias mydev for /pci@400/pci@2/pci@0/pci@a/SUNW,emlxs@0/fp@0,0/disk
(0) ok set—sfs—boot
set—sfs—boot ?
We tried selecting a disk and applying sfs-boot at ok prompt.
Can you please help me providing detailed pre-requesites/steps/procedure to implement this and to start boot from SAN.
2) How to SMI Label/Format a disk while OS Installation in Solaris 11.1?
As we know that ZFS is the default filesystem in Solaris 11.
We have seen in the Oracle documentation that for rpool below are recommended:
- A disk that is intended for a ZFS root pool must be created with an SMI label, not an EFI label.
- Create root pools with slices by using the s* identifier.
- ZFS applies an EFI label when you create a storage pool with whole disks.
- In general, you should create a disk slice with the bulk of disk space in slice 0.
I have seen the solution that using format -e, we change the labelling but all the data will be lost, whats the way to apply a SMI Label/Format on a rpool disks while OS Installation itself.
Please provide me the steps to SMI Label a disk while installaing Solaris 11.1 OS.

Oracle recommends below things on rpool: (thats reason wanted to apply SMI Label)
I have seen in the Oracle documentation that for rpool below are recommended:
- A disk that is intended for a ZFS root pool must be created with an SMI label, not an EFI label.
- Create root pools with slices by using the s* identifier.
- ZFS applies an EFI label when you create a storage pool with whole disks.
- In general, you should create a disk slice with the bulk of disk space in slice 0.

Oracle 8.1.5 Client/WLS/Solaris x86

has anyone been able to get Oracle's client 8.1.5 running on Solaris x86 in conjunction with WLS to talk to back-end Oracle? Any help would be greatly appreciated.thanks.

This will not work. We have not built the native libraries to work with
Solaris on Intel..
I suggest trying the platform independent type 4 JDBC driver available for
free from Oracle. It is supported (as is any JDBC driver) with WebLogic
Server. To download it:
Go to http://www.oracle.com and select the "Download" option.
From the resulting page, use the "Select Utility or Driver" dropdown to
select Oracle JDBC drivers
From the resulting page, scroll down a little (since SQLJ stuff appears at
the top).
Or, to go directly there:
http://technet.oracle.com/software/tech/java/sqlj_jdbc/software_index.htm
Thanks,
Michael
Michael Girdley
BEA Systems Inc
"Dean Davis" <[email protected]> wrote in message
news:3a267487$[email protected]..
has anyone been able to get Oracle's client 8.1.5 running on Solaris x86in conjunction with WLS to talk to back-end Oracle? Any help would be
greatly appreciated.thanks.

How to integrate a Solaris x86 server on Sun Management Center ?

Hello people,
I want to integrate a Solaris x86 server on Sun Management Center platform.
If I'm not wrong, SunMC doesn't run for Solaris x86, server and client only as console with Java.
In speat of it, I try to install Sun Management Center 3.0 Agent for Solaris x86.
It seems to be ok, install packages, but when execute es-setup script, intents to create the following directory:
/opt/SUNWsymon/base/bin/sparc-sun-solaris2.8
I supose that in this directory, SunMC will install sparc binary files
At this point, I can't follow the installation and abort it.
Can anybody give me ideas to install and integrate my solaris x86 server on SunMC ?
Thanks

Hi Hisham,
hishooooo wrote:
Dear Gents,
I have one X86 Solaris Server configured and installed to be Sun Management Center Server.
successfully i could monitor the Sun Solaris Servers after i have installed the SMC agent on them.
my problem is that i could not install the SMC agent on Red Hat Linux. as i could not find an easy document or steps to do so.
could you guide please?If you still have a copy of your SunMC media around, the same ["es-inst"|http://docs.sun.com/app/docs/doc/820-2215/command-line-1?l=en&a=view] program you use to install Solaris Agents should work on Linux as well. It autodetects OS type and will install Solaris packages or RPMs as appropriate.
Regards,
[email protected]
http://www.HalcyonInc.com

8-way SMP with Solaris 8 x86

Similar Messages

Maybe you are looking for