Cloning from solaris 10 sparc to solaris 10 x86

Hi,
We would like to know if it is possible to clone from production instance solaris 10 sparc to test instance solaris 10 x86 (intel) in 11.5.10CU2.
And if yes or no is it possible in R12.1.2.
Thanks
Brice Guillard

Hi,
Is it possible to have the first node on solaris 10 x86 with the database and the other on solaris 10 sparc ?Not possible as this OS is not certified.
What happen with rapid clone if we clone the production instance full sparc to a test instance with solaris 10 x86 on the database and the application server on x86.Rapid Clone will not work on this target OS because it is not supported.
Regards,
Hussein

Similar Messages

Cloning from solaris 10 to solaris 10 RC-50013: Fatal failed to intantiate

while cloning from solaris 10 to solaris 10 RC-50013: Fatal failed to intantiate Driver /applprod/oracle/prddb/9.2.0/appsutil/driver/instconfig.drv

Application is 11.5.10.2
after running perl adcfgclone.pl dbTier getting error
bash-3.00$ tail -100 ApplyDBTier_02040759.log
backup : /applprod/oracle/prddb/9.2.0/.patch_storage/3682068/comps.xml.b4appl
y to /applprod/oracle/prddb/9.2.0/appsutil/out/PRD_flex-sprod/comps.xml5.b4apply
setting ownership: applprod:dba
instantiate file:
source : /applprod/oracle/prddb/9.2.0/appsutil/template/.patch_storage/368206
8/comps.xml.afterapply
dest : /applprod/oracle/prddb/9.2.0/.patch_storage/3682068/comps.xml.aftera
pply
backup : /applprod/oracle/prddb/9.2.0/.patch_storage/3682068/comps.xml.aftera
pply to /applprod/oracle/prddb/9.2.0/appsutil/out/PRD_flex-sprod/comps.xml5.afte
rapply
setting ownership: applprod:dba
instantiate file:
source : /applprod/oracle/prddb/9.2.0/appsutil/template/.patch_storage/369167
2/comps.xml.b4apply
dest : /applprod/oracle/prddb/9.2.0/.patch_storage/3691672/comps.xml.b4appl
y
backup : /applprod/oracle/prddb/9.2.0/.patch_storage/3691672/comps.xml.b4appl
y to /applprod/oracle/prddb/9.2.0/appsutil/out/PRD_flex-sprod/comps.xml6.b4apply
setting ownership: applprod:dba
instantiate file:
source : /applprod/oracle/prddb/9.2.0/appsutil/template/.patch_storage/369167
2/comps.xml.afterapply
dest : /applprod/oracle/prddb/9.2.0/.patch_storage/3691672/comps.xml.aftera
pply
backup : /applprod/oracle/prddb/9.2.0/.patch_storage/3691672/comps.xml.aftera
pply to /applprod/oracle/prddb/9.2.0/appsutil/out/PRD_flex-sprod/comps.xml6.afte
rapply
setting ownership: applprod:dba
instantiate file:
source : /applprod/oracle/prddb/9.2.0/appsutil/template/.patch_storage/416740
3/comps.xml.b4apply
dest : /applprod/oracle/prddb/9.2.0/.patch_storage/4167403/comps.xml.b4appl
y
backup : /applprod/oracle/prddb/9.2.0/.patch_storage/4167403/comps.xml.b4appl
y to /applprod/oracle/prddb/9.2.0/appsutil/out/PRD_flex-sprod/comps.xml7.b4apply
setting ownership: applprod:dba
instantiate file:
source : /applprod/oracle/prddb/9.2.0/appsutil/template/.patch_storage/416740
3/comps.xml.afterapply
dest : /applprod/oracle/prddb/9.2.0/.patch_storage/4167403/comps.xml.aftera
pply
backup : /applprod/oracle/prddb/9.2.0/.patch_storage/4167403/comps.xml.aftera
pply to /applprod/oracle/prddb/9.2.0/appsutil/out/PRD_flex-sprod/comps.xml7.afte
rapply
setting ownership: applprod:dba
instantiate file:
source : /applprod/oracle/prddb/9.2.0/appsutil/template/.patch_storage/425293
8/comps.xml.b4apply
dest : /applprod/oracle/prddb/9.2.0/.patch_storage/4252938/comps.xml.b4appl
y
backup : /applprod/oracle/prddb/9.2.0/.patch_storage/4252938/comps.xml.b4appl
y to /applprod/oracle/prddb/9.2.0/appsutil/out/PRD_flex-sprod/comps.xml8.b4apply
setting ownership: applprod:dba
instantiate file:
source : /applprod/oracle/prddb/9.2.0/appsutil/template/.patch_storage/425293
8/comps.xml.afterapply
dest : /applprod/oracle/prddb/9.2.0/.patch_storage/4252938/comps.xml.aftera
pply
backup : /applprod/oracle/prddb/9.2.0/.patch_storage/4252938/comps.xml.aftera
pply to /applprod/oracle/prddb/9.2.0/appsutil/out/PRD_flex-sprod/comps.xml8.afte
rapply
setting ownership: applprod:dba
instantiate file:
source : /applprod/oracle/prddb/9.2.0/appsutil/template/.patch_storage/438580
3/comps.xml.b4apply
dest : /applprod/oracle/prddb/9.2.0/.patch_storage/4385803/comps.xml.b4appl
y
backup : /applprod/oracle/prddb/9.2.0/.patch_storage/4385803/comps.xml.b4appl
y to /applprod/oracle/prddb/9.2.0/appsutil/out/PRD_flex-sprod/comps.xml9.b4apply
setting ownership: applprod:dba
instantiate file:
source : /applprod/oracle/prddb/9.2.0/appsutil/template/.patch_storage/438580
3/comps.xml.afterapply
dest : /applprod/oracle/prddb/9.2.0/.patch_storage/4385803/comps.xml.aftera
pply
backup : /applprod/oracle/prddb/9.2.0/.patch_storage/4385803/comps.xml.aftera
pply to /applprod/oracle/prddb/9.2.0/appsutil/out/PRD_flex-sprod/comps.xml9.afte
rapply
setting ownership: applprod:dba
instantiate file:
source : /applprod/oracle/prddb/9.2.0/appsutil/template/.patch_storage/270137
2/comps.xml.b4apply
dest : /applprod/oracle/prddb/9.2.0/.patch_storage/2701372/comps.xml.b4appl
y
backup : /applprod/oracle/prddb/9.2.0/.patch_storage/2701372/comps.xml.b4appl
y to /applprod/oracle/prddb/9.2.0/appsutil/out/PRD_flex-sprod/comps.xml10.b4appl
y
setting ownership: applprod:dba
instantiate file:
source : /applprod/oracle/prddb/9.2.0/appsutil/template/.patch_storage/270137
2/comps.xml.afterapply
dest : /applprod/oracle/prddb/9.2.0/.patch_storage/2701372/comps.xml.aftera
pply
backup : /applprod/oracle/prddb/9.2.0/.patch_storage/2701372/comps.xml.aftera
pply to /applprod/oracle/prddb/9.2.0/appsutil/out/PRD_flex-sprod/comps.xml10.aft
erapply
setting ownership: applprod:dba
instantiate file:
source : /applprod/oracle/prddb/9.2.0/appsutil/template/root.sh.old
dest : /applprod/oracle/prddb/9.2.0/root.sh.old
backup : /applprod/oracle/prddb/9.2.0/root.sh.old to /applprod/oracle/prddb/9
.2.0/appsutil//out/PRD_flex-sprod/root.sh.old
setting ownership: applprod:dba
instantiate file:
source : /applprod/oracle/prddb/9.2.0/appsutil/template/root.sh.old.1
dest : /applprod/oracle/prddb/9.2.0/root.sh.old.1
backup : /applprod/oracle/prddb/9.2.0/root.sh.old.1 to /applprod/oracle/prddb
/9.2.0/appsutil//out/PRD_flex-sprod/root.sh.old.1
setting ownership: applprod:dba
[AutoConfig Error Report]
The following report lists errors AutoConfig encountered during each
phase of its execution. Errors are grouped by directory and phase.
The report format is:
<filename> <phase> <return code where appropriate>
[INSTANTIATE PHASE]
AutoConfig could not successfully instantiate the following files:
Directory: /applprod/oracle/prddb/9.2.0/lib
clntsh.map INSTE8
Directory: /applprod/oracle/prddb/9.2.0/lib32
clntsh.map INSTE8
AutoConfig is exiting with status 2
RC-50013: Fatal: Failed to instantiate driver /applprod/oracle/prddb/9.2.0/appsu
til/driver/instconf.drv
Raised by oracle.apps.ad.clone.ApplyDBTechStack
StackTrace:
java.lang.Exception: RC-50013: Fatal: Failed to instantiate driver /applprod/ora
cle/prddb/9.2.0/appsutil/driver/instconf.drv
at oracle.apps.ad.clone.ApplyDBTechStack.checkInstallDrvErr(ApplyDBTechS
tack.java:717)
at oracle.apps.ad.clone.ApplyDBTechStack.runInstallConfigDriver(ApplyDBT
echStack.java:622)
at oracle.apps.ad.clone.ApplyDBTechStack.<init>(ApplyDBTechStack.java:38
9)
at oracle.apps.ad.clone.ApplyDBTier.<init>(ApplyDBTier.java:149)
at java.lang.reflect.Constructor.newInstance(Native Method)
at oracle.apps.ad.clone.util.CloneProcessor.run(CloneProcessor.java:68)
at java.lang.Thread.run(Thread.java:484)

ODBC to DB2 from Solaris 10 X86 64

I am trying to make a ODBC connection to a DB2 database on a AS400 via a datadirect ODBC driver. This is working.
Now i am trying to use the hsdodbc driver to make a connection from the Oracle 10.2.0.4 64bit database on the Solaris 10 x86 64 bit.
I modified the listener.ora.
lsnrctl reload
LSNRCTL for Solaris: Version 10.2.0.4.0 - Production on 21-APR-2009 15:24:14
Copyright (c) 1991, 2007, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=srv020.emons.nl)(PORT=1521)))
TNS-01201: Listener cannot find executable /oracle/oracle10/10.2.0/db_1/bin/hsodbc for SID HSAS400
the driver does not exist; only the file /oracle/oracle10/10.2.0/db_1/bin/hsodbcO
Apparantly hsodbc is not supported on this platform. What are the alternatives?
Thanks in advance,
Toon

use DG4ODBC V11.
DG4ODBC is a real gateway and thus can be installed independantly from the Oracle database; even on a separate machine.
Using DG4ODBC will allow you to use an Oracle database 9.2.0.8, 10.1.0.5, 10.2.0.3 (pay attention, these Oracle database requires a compatibility patch) or an Oracle db 10.2.0.4 and 11 (patch already included) to connect to a foreign database using ODBC.
The connection is then initated by the Oracle db which connects to the gateway listener on a second machine. The gateway listener spawns the gateway executable which loads the ODBC driver and connects to the foreign database.

Problem jumpstarting a Solaris 9 SPARC from Solaris 10 x86

Hi all,
I'm going to install a couple of servers using Jumpstart, but I've run
into a problem so I'm kinda in panic.
This is the net boot:
Executing last command: boot net - install
Boot device: /pci@1f,0/pci@1,1/network@c,1 File and args: - install
Timeout waiting for ARP/RARP packet
29200 panic - boot: Could not mount filesystem.
Program terminated
ok
I've setup the jumpstart server on my x86 PC, which is Solaris 10 final
with JET 3.7.3. Since I'm jumpstarting Solaris 9 onto a SPARC machine, I
had to do copy_solaris_media over NFS, since I can't mount the SPARC
ISO-CD1 on my x86. The install server seems to be OK, at least it didn't
complain during setup.
The log entry from sniffing the JS server:
3266 1:15:25.48103 aaa -> xxx WHO C port=33345
3267 1:15:25.48427 aaa -> xxx WHO C port=33345
3268 1:15:25.48636 aaa -> xxx WHO C port=33345
3269 1:15:25.48748 aaa -> xxx SYSLOG C port=32775 BAD.FMT:
3270 1:15:25.49044 aaa -> xxx SYSLOG C port=32775 BAD.FMT:
3271 1:15:25.49283 aaa -> xxx SYSLOG C port=32775 BAD.FMT:
3272 1:15:25.49394 aaa -> xxx PORTMAP R GETPORT port=32775
3273 1:15:25.49541 aaa -> xxx PORTMAP R GETPORT port=32775
3274 1:15:25.49673 aaa -> xxx PORTMAP R GETPORT port=32775
3275 1:15:25.49867 aaa -> xxx PORTMAP R GETPORT port=32775
/etc/bootparams:
xxx root=aaa:/opt/install/media/Solaris_9/Solaris_9/Tools/Boot
install=192.168.4.5:/opt/install/media/Solaris_9 boottype=:in
sysid_config=192.168.4.5:/opt/jet/Clients/xxx
install_config=192.168.4.5:/opt/jet rootopts=:rsize
32768
term=:vt100
Any idea what could be wrong? It stops at 29200, wheres Solaris 10 runs
further up to 38000 something.
Jumpstarting the Solaris 10 onto the same SPARC works perfectly, using
the exact same configuration files.
Thanks

Hi all,
I managed to solve the problem.
This is very weird! can someone explain why this happens?
Output for working Solaris 10 boot:
Executing last command: boot net -v
Boot device: /pci@1f,0/pci@1,1/network@c,1 File and args: -v
38600 Using RARP/BOOTPARAMS...
Internet address is: 192.168.4.6
hostname: xxx
Requesting Ethernet address for: 192.168.4.5
Found 192.168.4.5 @ 0:0:86:1f:f7:92
root server: aaa (192.168.4.5)
root directory: /opt/install/media/Solaris_10/Solaris_10/Tools/Boot
Size: 0x704c8+0x1b8d2+0x2e1ba Bytes
Output for non-working Solaris 9 boot:
Executing last command: boot net -v
Boot device: /pci@1f,0/pci@1,1/network@c,1 File and args: -v
Timeout waiting for ARP/RARP packet
29200 Using RARP/BOOTPARAMS...
Internet address is: 192.168.4.6
hostname: xxx
Found 192.168.4.5 @ 0:0:86:1f:f7:92
root server: aaa (192.168.4.5)
root directory: /opt/install/media/Solaris_9/Solaris_9/Tools/Boot
panic - boot: Could not mount filesystem.
Program terminated
ok
I then replaced /tftpboot/inetboot.SUN4U.Solaris_9-1 with /tftpboot/inetboot.SUN4U.Solaris_10-1 from the Solaris 10 tree, renamed /tftpboot/inetboot.SUN4U.Solaris_10-1 to /tftpboot/inetboot.SUN4U.Solaris_9-1
Voila!
Now works.
inetboot.SUN4U.Solaris_9-1 was not corrupt (must be some internal bootimage bug related to Netra-T1?).
Old bootimage: "inetboot.SUN4U.Solaris_9-1", 152376 bytes, "sum" 3662 and 298.
New bootimage: "inetboot.SUN4U.Solaris_9-1" (Sol 10 image), 214880 bytes, "sum" 53512 and 420.
By the way I was using latest Solaris 9/04, u7

Issues w/ LiveUpgrade from Solaris 10 x86 06/06 to 08/07 w/ SVMmetadevices

Hello all...
I am trying to upgrade a system from Sol 10 x86 6/06 to 8/07. For this example, we'll assume the following:
* The system has only 2 disks mirrored with SVM
* There are 0 free slices/partitions
* /, /usr, /var are separate slices/filesystems/mirrors
* There are 6 metadbs on 50MB slices, three on each disk
I run the following lucreate command (after having made sure that the appropriate packages and patches exist on the system):
lucreate -c s10u2 -n s10u4 -m /:/dev/md/dsk/d110:ufs,mirror -m /:/dev/dsk/c0d1s0:detach,attach,preserve \
-m /usr:/dev/md/dsk/d120:ufs,mirror -m /usr:/dev/dsk/c0d1s3:detach,attach,preserve \
-m /var:/dev/md/dsk/d130:ufs,mirror -m /var:/dev/dsk/c0d1s4:detach,attach,preserveI can then run luupgrade and every indication leads me to believe that it worked. So, I activate the new BE and init 6 and attempt to boot to the new BE. The boot ends up failing citing that it cannot mount /usr. So, I can either reboot and lumount the filesystems or boot into failsafe mode and take a look at the vfstab. The /etc/vfstab looks fine with the new metadevices identified as the /, /usr, and /var filesystems. However, those metadevices are never initialized. When I look at /etc/lvm/md.cf on the source BE, those metadevices are initialized there. However, they are not initialized in the secondary BE.
Am I missing something somewhere? Wondering why SVM does not appear to be updated on the secondary BE to add/initialize the new metadevices in the secondary BE.
TIA,
Rick

Ok...update...
I have found that there are bugs with LU where it relates to SVM mirrored /'s and what not. So, I modified my approach to the upgrade and "deconfigured" the /, /usr, and /var mirrors. I then executed the the procedure as described in the docs to create a new boot environment on the secondary disk. It worked!
Great! With that done, I can then remove the old boot environment and remirror the /, /usr, and /var filesystems as it was prior to the LU procedure. Wrong answer! There were two problems, the first was fairly simple to overcome....
Problem 1) When attempting to delete the old BE, I would get the following error:
The boot environment <s10u2> contains the GRUB menu.
Attempting to relocate the GRUB menu.
/usr/sbin/ludelete: lulib_relocate_grub_slice: not found
ERROR: Cannot relocate the GRUB menu in the boot environment <s10u2>.
ERROR: Cannot delete the boot environment <s10u2>.
Unable to delete boot environment.Through some Googling, I found that apparently, the Solaris 10 LiveUpgrade is attempting to use a function in /usr/lib/lu/lulib that only exists in OpenSolaris (whatever happened to backporting functionality?). Ok...easy enough. Backup the library and copy it over from an OpenSolaris box. Done...and it worked, but only led to problem #2...
Problem 2) Now when I run ludelete on the old BE, I get the following error:
The boot environment <s10u2> contains the GTRUB menu.
Attempting to relocte the GRUB menu.
ERROR: No suitable candidate slice for GRUB menu on boot disk: </dev/rdsk/c0d0p0>
INFORMATION: You will need to create a new Live Upgrade boot environment on the boot disk to find a new candidate for the grub menu.
ERROR: Cannot relocate the GRUB menu in boot environment <s10u2>.
Unable to delete boot environment.I have attempted to manually move/install GRUB on the secondary disk and make it the active boot disk, all to no avail. ludelete returns the same error every time.
Thoughts? Ideas?
TIA,
Rick

Network install from solaris 10 x86 server to x86 client

My setup is:
install server OS: Solaris 10, i86pc .
The install server is also boot server using tftpboot.
The dhpc server is configured according to the instructions which are
given when adding an install client in Solaris 10.
The client can communicate with the install and boot server but fails
to load the boot image. The snoop output is
Using device /dev/iprb0 (promiscuous mode)
cdm3 -> cdm2 ICMP Echo request (ID: 48130 Sequence number: 0)
cdm2 -> cdm3 TFTP Read "nbp.cdm2" (octet)
cdm3 -> cdm2 UDP D=2070 S=39122 LEN=22
cdm2 -> cdm3 TFTP Error: not defined
cdm2 -> cdm3 TFTP Read "nbp.cdm2" (octet)
cdm3 -> cdm2 UDP D=2071 S=39123 LEN=23
cdm2 -> cdm3 TFTP Ack block 0
cdm3 -> cdm2 TFTP Data block 1 (1456 bytes)
cdm2 -> cdm3 TFTP Ack block 1
cdm3 -> cdm2 TFTP Data block 2 (1456 bytes)
cdm2 -> cdm3 TFTP Ack block 2
cdm3 -> cdm2 TFTP Data block 3 (1456 bytes)
cdm2 -> cdm3 TFTP Ack block 3
cdm3 -> cdm2 TFTP Data block 4 (1456 bytes)
cdm2 -> cdm3 TFTP Ack block 4
cdm3 -> cdm2 TFTP Data block 5 (1456 bytes)
cdm2 -> cdm3 TFTP Ack block 5
cdm3 -> cdm2 TFTP Data block 6 (1456 bytes)
cdm2 -> cdm3 TFTP Ack block 6
cdm3 -> cdm2 TFTP Data block 7 (1456 bytes)
cdm2 -> cdm3 TFTP Ack block 7
cdm3 -> cdm2 TFTP Data block 8 (1456 bytes)
cdm2 -> cdm3 TFTP Ack block 8
cdm3 -> cdm2 TFTP Data block 9 (1456 bytes)
cdm2 -> cdm3 TFTP Ack block 9
cdm3 -> cdm2 TFTP Data block 10 (1456 bytes)
cdm2 -> cdm3 TFTP Ack block 10
cdm3 -> cdm2 TFTP Data block 11 (1456 bytes)
cdm2 -> cdm3 TFTP Ack block 11
cdm3 -> cdm2 TFTP Data block 12 (172 bytes) (last block)
cdm2 -> cdm3 TFTP Ack block 12
cdm2 -> BROADCAST DHCP/BOOTP DHCPDISCOVER
cdm2 -> BROADCAST DHCP/BOOTP DHCPDISCOVER
cdm3 -> cdm2 ICMP Echo request (ID: 48130 Sequence number: 0)
cdm3 -> cdm2 DHCP/BOOTP DHCPOFFER
cdm2 -> BROADCAST DHCP/BOOTP DHCPDISCOVER
cdm3 -> cdm2 ICMP Echo request (ID: 48130 Sequence number: 0)
cdm3 -> cdm2 DHCP/BOOTP DHCPOFFER
cdm2 -> BROADCAST DHCP/BOOTP DHCPDISCOVER
cdm3 -> cdm2 ICMP Echo request (ID: 48130 Sequence number: 0)
cdm3 -> cdm2 DHCP/BOOTP DHCPOFFER
And then fails: i.e. it seems not to find the boot image.
Any suggestions???
Lydia

I can't tell exactly what's wrong, since you attached only
snoop log.
But since you're using DHCP, I guess you are trying to
do PXE boot to install. When you use PXE boot, you need
to configure some vendor options (like SrootIP4, SrootNM
etc) and also create macros with dhcpmgr.
there is documentation at
http:docs.sun.com
so check the documentation to see what is missing.
If you've already done these, check NFS configuration
if all directory are correctly shared.

Tt_open() Fail, no Error code too.. from solaris 10 x86 to solaris 8 spac

when i try remote tt_open() alway fail. in solaris10 x86
between solaris10 x86 and solaris8 spac. it is version problem?
but strange one is solaris8-spac can be open to solaris10-x86.
this is my test list.
1. solaris 8(spac) can be tt_open() to solaris10(x86).. : Sucess (solaris8->solaris10)
2. solaris10(x86) can be tt_open() to solaris10(x86).. : Sucess(solaris10->solaris10)
3. solaris8(spac) can be tt_open() to solaris8(spac) : Sucess(solaris8->solaris8)
4. solaris10(x86) can not tt_open() to solaris8(spac) : Fail (solaris10->solaris8)
plese some body tell me how can do that.. it is each version problem? or not..
getting session is sucess but can not be tt_open..
here is source code and log file. this code almost same to tooltalk reference document.
and before the system (solaris 8-spac) we are normally use like this.
somebody any solution?
/////////////////////////////////// code ////////////////////////////////////////
tt_status status;
char* sessid;
    sessid = findRemoteSession(remHostId);
    cout << "RemHostId: " << remHostId << endl;
    cout << "sessid: " << sessid << endl;
    if( !sessid )
        throw PDPBException("Requested Host Not Responsive");
    status = tt_default_session_set(sessid);
    cout << "status: " << status << endl;
    if( status != TT_OK )
       throw PDTTException(status);
title = tt_open();
cout << "Try tt_Open() => title : " << title << endl; // << this return is Null when i try remote tt_open() to (solaris10->solaris8)
if(TT_OK != (status = tt_ptr_error(title)))
   cout << "tt_ptr_error" << endl;       ///// ERROR alwasy..................
   throw PDTTException(status);
zip = tt_fd();
if(TT_OK != (status = tt_int_error(zip)))
   throw PDTTException(status);
/////////////////////////////////// Code end ///////////////////////////////////////////////////////////////////////////// log ////////////////////////////////////////
master is alive
looking for master:0:
located master:0 (P 01 862 1289637086 1 1 102 10.10.104.165 5 master)
RemHostId: master
sessid: P 01 862 1289637086 1 1 102 10.10.104.165 5 master
status: 0
Try tt_Open() => title : N.18KZFF 01 862 1289637086 1 1 102 10.10.104.165 5 master
init Func()
init Func() End
End init masterHostId: master
sourceName: RECEIVER_REMOTE
Start init masterHostId: client1
RemHostId: client1
client1is alive
looking for client1:0:
located cc60:0 (P 01 585 1289637086 1 1 102 10.10.104.164 5 client1)
RemHostId: client1
sessid: P 01 585 1289637086 1 1 102 10.10.104.164 5 client1
status: 0
Try tt_Open() => title :
tt_ptr_error
///////////////////////////////////// log End ////////////////////////////////////////

No. Packet capturing is not working in non-global zones.
You can not manipulate network interfaces in a non global zones at all. You can add some types of devices to the non global zones, but no network adapters.
All ip filtering, packet capturing business can only be done in the global zone.
regards,
Imre

Networking changes between Solaris 10 x86 10/08 (u6) and previous versions?

Solaris Community:
We have a J2SE CORBA-based application (that uses the default Sun ORB) that has run without problems on Solaris 8, 9, and 10 on both SPARC and, more recently, X86 platforms. Upgrading our client side machine (X4100 M2 Opteron platform) from Solaris 10 x86 5/08 (u5) to Solaris 10 x86 10/08 (u6) has resulted in threading or socket contention issues that we have not experienced previously. Using Live Upgrade, we can quickly go back to the u5 install on the client machine .... and the problems go away .... going back to u6, however, and the problems begin to show almost immediately. Our Java code base is identical as is the version of the JDK (1.5.0_16), so it would appear that there must be an underlying change to socket, networking, or threading behavior between these two versions of Solaris.
Thus far, I've not been unable to find details of changes either in the networking support or the threading model that might explain this .... or course, I don't have great expertise in these areas.
I've tried to use 'ndd /dev/tcp SOME_PARAMETER' for all of the /dev/tcp parameters returned by 'ndd /dev/tcp \?' to try to see if there are underlying changes in the /dev/tcp parameters .... but have not found any differences between Solaris 10 u5 and u6.
Can anyone point me to resources that would discuss changes between Solaris 10 u5 or u6 that might explain the problems that we've encountered? Or, alternatively, other system parameters that I could check that might explain changes in either TCP socket or threading behavior?
Thanks for your input,
John

I have a vague memory of someone reporting something similar which turned out to be due to a solaris feature called tcp_fusion.
To check whether thats your problem or not try the following.
Add following line in the /etc/system file.
set ip:do_tcp_fusion = 0
Once the /etc/system file is updated, it will be necessary to restart the system before the workaround will take effect.

Upgrade from Solaris 8 SPARC with Sun cluster 3.1u3 to Solaris 10 SPARC

Dear All,
We are planning an upgrade of the OS from Solaris 8 SPARC to Solaris 10 SPARC on a two-node active-standby clustered system.
The current major software we have on the Solaris 8 system are:
1: Sun Cluster 3.1u3
2: Oracle 9i 9.2.0.8
3: Veritas File System Vxfs v4.0
4: Sun Solaris 8 2/04 SPARC
Any pointers as to what sequence and how the upgrade should be done?
Thanks in advance.
Regards,
Ray

yes I know it can be quite complicated and complex, but Sun provided us with a detailed documentation, at least in our case Solaris 9 to 10 it was very helpful.
You might get better help in the cluster forum http://forums.sun.com/forum.jspa?forumID=842
-- Nick

Oracle migration from Solaris 64 sparc to Solaris x86-64

Now that Solaris x86-64 is supported in Netweaver 2004s SR1, I was wondering about the migration path.
Would this be a heterogeneous migration or a homogeneous migration.
or to put it another way Export/import to migrate
or backup/restore????
No documents exist yet regarding this migration.

Hello Guys
Just wanted to ask you whether Migration of SAP system from Solaris SPARC to Solaris x86_64 is possible using the
backup/restore method.
I would be grateful if you could share your experience
Regards
Sarin

Migration from Solaris Sparc server to Solaris x86

Hi ,
I would like to know.
Migration from SAP ECC6 , Oracle , Solaris Sparc to Ecc6, Oracle, Solaris x86 , Is this consider Heterogeneous or Homogeneous system copy?
Thanks.
Best Regards,
ck chai

Solaris on SPARC is a BIgEndian platform, Solaris on X86 is LittleEndian - so it's heterogeneous --> you need to use R3load to performa a migration - and you need to have a certified migration consultant on-site to do that migration (http://service.sap.com/osdbmigration --> FAQ).
Markus

Re: migrate our ERP database from Solaris Sparc 64 to Linux x86_

hi ,
We want to migrate our ERP database from Solaris Sparc 64 to Linux x86_64 .
Please suggest some docs .
Regards.

I assume you are on R12 since you want to migrate the application tier node to Linux 64-bit (which is certified for the application tier node on R12 but not 11i), so please refer to the docs in this thread -- Re: Has anyone migrate/upgrade from R12.0.6 on Solaris to R12.1.3 on Linux?
Thanks,
Hussein

Migrating drivers from Solaris 9 to Solaris 10 (sparc)

I'm tasked to move some drivers from Solaris 9 to Solaris 10. Clearly, some elements of the interface have changed in this dot revision, as just installing the 2.9 drivers causes 2.10 to panic. I tried looking around the site for a guide to what changed in the driver interface. Can someone point me at a relevant document somewhere?

I'm tasked to move some drivers from Solaris 9 to
Solaris 10. Clearly, some elements of the interface
have changed in this dot revision, as just installing
the 2.9 drivers causes 2.10 to panic. I tried
looking around the site for a guide to what changed
in the driver interface. Can someone point me at a
relevant document somewhere?Nothing should have changed in the driver / kernel interfaces.
If the Solaris 9 driver uses only official / documented kernel
interfaces the same driver binary should run without problem on
Solaris 10.
All bets are off if the Solaris 9 driver is using internal kernel
data structures that are not part of the kernel / driver api.
Such a driver could fail by just installing OS patches to the system.

RMAN Restore from Sun Solaris 9 Sparc to Sun Solaris 10 X86

Hello,
I will need to perform a restore from a 10.2.0.4 DB on Sun Sparc to a Sun X86 10.2.0.4 DB. Since its the same platform will I have any issues?

Those are different endian formats and therefore will require the use of Cross-Platform Transportable Tablespaces or expdp/impdp.
Check Cross-Platform Tranportable Tablespace: CONVERT DATAFILE or TABLESPACE for details on the process.

How to configure CUPS in Solaris 10 X86 and SPARC

Dears,
I need help in configuring CUPS for Solaris 10 X86 as well as on SPARC.
What i did?
Downloaded the CUPS 1.5.0
read the readme.txt
read the INSTALL.txt
Pre-req installation requires :-
CFLAGS= -i /some/directory \
CPPFLAGS = -i /some/directory \
CXXFLAGS = -I /some/directory \
DSOFLAGS = -L /some/directgry \
LDFLAGS = -L /some/directory \
./configure --
It errors out with
checking for gawk ... no
checking for mawk... no
checking for nawk ...nawk
chekcing for gcc ... no
checking for cc ... no
checking for cl.exe no
Configure error: no acceptable C compiler found in $PATH
see 'config.log' for more details
I installed all the missing dependencies from www.sunfreeware.com and I have the same problem.
I also tried to install the software packages from the operating system dvd... like for
ls -lrt gcc
gcc "SUNWgcc", "SUNWgccS", "SUNWgccruntime"
ls -lrt cc
cc "SUNWgccruntime", "SUNWlccom", "SUNWcctpx", "SUNWccisgn" , "SUNWccinv", "SUNWccfwctrl", " SUNWccfw", "SUNWccccrr", "SUNWccccr", "SUNWccccfg", "SUNWislcc",
"SUNWaccu", "SUNWaccr", "IPLTccons", " SUWgccs", "SUNWgcc", "SUNWmccom", "SUNWmcc", "SUNWusbccids", "SUNWusbccid"
ls -lrt gawk
no results
ls -lrt mawk
no results
ls -lrt cl.exe
no results
Is there any way should i follow apart from the above?
Rgds,
Mky

Check pkginfo -l for each package.
export the PATH variable where the packages are installed, like /usr/local/bin and etc.

Cloning from solaris 10 sparc to solaris 10 x86

Similar Messages

Maybe you are looking for