SAP on Solaris Filesyste sizing

Dear all,
I have to install Solaris 10 for Solution Manager 4.0 SR3. Can anyone guide me that what filesystem and their correct size should i create to avoid any problem during SAP installation?
Thanks
Imran Hasware

FYI - I didn't perform the install but we SM installed on Solaris using Oracle 10.2.0.2.
Here is the output from df -h:
df -h
Filesystem             size   used avail capacity Mounted on
/dev/md/dsk/d0         9.6G   5.8G   3.7G    62%    /
/devices                 0K     0K     0K     0%    /devices
ctfs                     0K     0K     0K     0%    /system/contract
proc                     0K     0K     0K     0%    /proc
mnttab                   0K     0K     0K     0%    /etc/mnttab
swap                    24G   1.3M    24G     1%    /etc/svc/volatile
objfs                    0K     0K     0K     0%    /system/object
fd                       0K     0K     0K     0%    /dev/fd
/dev/md/dsk/d3         4.3G   434M   3.9G    10%    /var
swap                    24G   176K    24G     1%    /tmp
swap                    24G    48K    24G     1%    /var/run
/dev/md/dsk/d49         34G    22G    12G    65%    /CDs
/dev/md/dsk/d61         25G   7.4G    17G    31%    /oracle
/dev/md/dsk/d4         1.0G    96M   916M    10%    /opt
/dev/md/dsk/d52        4.3G   3.1G   1.2G    72%    /oracle/stage
/dev/md/dsk/d58        1.4G   1.1G   259M    82%    /sapmnt/MAN
/dev/md/dsk/d53        471M    98M   326M    24%    /oracle/MAN/sapreorg
/dev/md/dsk/d54         39G    21G    18G    53%    /oracle/MAN/sapdata1
/dev/md/dsk/d55         20G    16G   3.8G    81%    /oracle/MAN/sapdata2
/dev/md/dsk/d57         20G    18G   1.9G    91%    /oracle/MAN/sapdata4
/dev/md/dsk/d56         20G    18G   1.9G    91%    /oracle/MAN/sapdata3
/dev/md/dsk/d59        6.9G   4.8G   1.9G    72%    /usr/sap/MAN
/dev/md/dsk/d62         20G   188M    19G     1%    /oracle/MAN/oraarch
/dev/md/dsk/d63        934M   113M   764M    13%    /oracle/MAN/origlogA
/dev/md/dsk/d65        934M   101M   776M    12%    /oracle/MAN/mirrlogB
/dev/md/dsk/d64        934M   113M   764M    13%    /oracle/MAN/origlogB
/dev/md/dsk/d66        934M   101M   776M    12%    /oracle/MAN/mirrlogA
SAPD05:/usr/sap/trans
                        25G   7.1G    17G    30%    /usr/sap/trans
/export/home/manadm    9.6G   5.8G   3.7G    62%    /home/manadm
If you need more info, let me know. I don't believe the database has grown much but I don't know what the installed size was.
Good luck,
Rick Morris

Similar Messages

SAP on SOLARIS on VMWare -- DELL ?

Friends, I noticed that Dell does not have hardware certified to run SAP on Solaris -> http://www.saponsolaris.com/hwlist.html
However I have a quest that requires SAP -> on Solaris -> on DELL
One of the solutions was virtualized Solaris and install SAP on Solaris: SAP -> on Solaris -> on VMWare -> on DELL
In the topic below there is a mention that SAP does not support this type of installation, but without any reference to any SAP Note:
ERP6 EHP4 SOLARIS 10 Sparc,Oracle 10g in a virtual envirn swap size requir
Do you know any case that could help me?
thank you

If I understand the license policy of Oracle Solaris properly, the only valid way of running Solaris entitled is on hardware you bought by Sun/Oracle.
There is no note because it is not supported. There are no Solaris specific VMWare tools available, there will be no integration in the monitoring becaues of that and hance it's not supported officially.
We had likewise problems and we will switch all Solaris boxes to Linux subsequently.
Markus

SAP on solaris x86 or sparc

Hi,
Can you please let me know the advantages of running SAP on Solaris X86 or SPARC machines. Which is recommended?
Thanks
Joyce

> If the compnay has very few end users to work on SAP i.e. less than 50 users, then x86 is suited.
> FOr large ended systems that is for large number of users to work on SAP, SPARC is better choice.
> SPARC is recommended.
I'm sorry but this is simply not true.
x86_64 is VERY suited for big systems, we run x86_64 systems with 1000+ users, on Solaris and on Linux.
Solaris on x86_64 is a very good choice, a mature OS with lots of features (zones, ZFS...) running on affordable hardware.
SPARC is a RISC architecture, there are even drawbacks in performance if you use e. g. T-series systems (UltraSparc) for ABAP systems and databases (see Oracle Metalink ID 781763.1 - "Migration from fast single threaded CPU machine to CMT UltraSPARC T1 and T2 results in increased CPU reporting and diminished performance").
So it's a matter of taste and choice - and money.
Markus

Install SAP on Solaris

Hi all,
I can install SAP on Windows and Linux, but now i want to install SAP on solaris,
Can anyone know how to install or provide me the SAP Note #
I have no idea about solaris.
regards
Imran Khan

import_monitor.java.log
"java version "1.4.2_19"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_19-b04)
Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_16-b05, mixed mode)
Import Monitor jobs: running 1, waiting 25, completed 2, failed 0, total 28.
Loading of 'SAPSSEXC' import package: ERROR
Import Monitor jobs: running 0, waiting 25, completed 2, failed 1, total 28.
Import Monitor jobs: running 1, waiting 24, completed 2, failed 1, total 28."
import_monitor.log
INFO: 2009-06-08 19:35:53
Import Monitor is started.
CONFIG: 2009-06-08 19:35:53
Application options:
dbCodepage=4102
dbType=ORA
ddlMap=ddl_mapping.txt
extFiles=yes
importDirs=/oracle/dump/d51033500_1/EXP1:/oracle/dump/d51033500_1/EXP2:/oracle/dump/d51033500_1/EXP3:/oracle/dump/d51033500_1/EXP4:/oracle/dump/d51033500_1/EXP5:/oracle/dump/d51033500_1/EXP6:/oracle/dump/d51033500_2/EXP7:/oracle/dump/d51033500_2/EXP8:/oracle/dump/d51033500_2/EXP9:/oracle/dump/d51033500_2/EXP10:/oracle/dump/d51033500_2/EXP11
installDir=/tmp/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS
jobNum=1
loadArgs=-stop_on_error
monitorTimeout=30
orderBy=
r3loadExe=/usr/sap/DEV/SYS/exe/run/R3load
sapinst=
trace=all
tskFiles=yes
CONFIG: 2009-06-08 19:35:53
List of packages with table structure: 'SAP0000'.
CONFIG: 2009-06-08 19:35:53
List of packages with views: 'SAPVIEW'.
TRACE: 2009-06-08 19:35:53 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of '/tmp/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/DDLORA.TPL' template file is started.
INFO: 2009-06-08 19:35:53 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of '/tmp/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/DDLORA.TPL' template file is successfully completed.
Primary key creation: after load.
Index creation: after load.
TRACE: 2009-06-08 19:35:53 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of '/tmp/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/DDLORA_LRG.TPL' template file is started.
INFO: 2009-06-08 19:35:53 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of '/tmp/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/DDLORA_LRG.TPL' template file is successfully completed.
Primary key creation: after load.
Index creation: after load.
TRACE: 2009-06-08 19:35:53 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of '/tmp/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/DDLORA.TPL' template file is started.
INFO: 2009-06-08 19:35:53 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of '/tmp/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/DDLORA.TPL' template file is successfully completed.
Primary key creation: after load.
Index creation: after load.
INFO: 2009-06-08 19:35:54
Data codepage 1100 is determined using TOC file '/oracle/dump/d51033500_1/EXP1/DATA/SAPSSEXC.TOC' for package 'SAPSSEXC'.
INFO: 2009-06-08 19:35:58
Version table 'SVERS' is found in STR file '/oracle/dump/d51033500_2/EXP10/DATA/SAPNTAB.STR' from package 'SAPNTAB'.
INFO: 2009-06-08 19:35:58
Data conversion tables 'DDNTF,DDNTF_CONV_UC,DDNTT,DDNTT_CONV_UC' are found in STR file '/oracle/dump/d51033500_2/EXP10/DATA/SAPNTAB.STR' from package 'SAPNTAB'.
TRACE: 2009-06-08 19:35:58 com.sap.inst.migmon.LoadTask run
Loading of 'SAPNTAB' import package is started.
TRACE: 2009-06-08 19:35:58 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPNTAB' import package:
/usr/sap/DEV/SYS/exe/run/R3load -ctf I /oracle/dump/d51033500_2/EXP10/DATA/SAPNTAB.STR /tmp/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/DDLORA.TPL SAPNTAB.TSK ORA -l SAPNTAB.log
TRACE: 2009-06-08 19:35:59 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPNTAB' import package into database:
/usr/sap/DEV/SYS/exe/run/R3load -i SAPNTAB.cmd -dbcodepage 4102 -l SAPNTAB.log -stop_on_error
INFO: 2009-06-08 19:55:40 com.sap.inst.migmon.LoadTask run
Loading of 'SAPNTAB' import package is successfully completed.
TRACE: 2009-06-08 19:55:54 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is started.
TRACE: 2009-06-08 19:55:54 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSSEXC' import package:
/usr/sap/DEV/SYS/exe/run/R3load -ctf I /oracle/dump/d51033500_1/EXP1/DATA/SAPSSEXC.STR /tmp/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/DDLORA.TPL SAPSSEXC.TSK ORA -l SAPSSEXC.log
TRACE: 2009-06-08 19:55:54 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSSEXC' import package into database:
/usr/sap/DEV/SYS/exe/run/R3load -i SAPSSEXC.cmd -dbcodepage 4102 -l SAPSSEXC.log -stop_on_error
ERROR: 2009-06-08 21:43:54 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is interrupted with R3load error.
Process '/usr/sap/DEV/SYS/exe/run/R3load -i SAPSSEXC.cmd -dbcodepage 4102 -l SAPSSEXC.log -stop_on_error' exited with return code 1.
For mode details see 'SAPSSEXC.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
INFO: 2009-06-09 11:11:09
Import Monitor is started.
CONFIG: 2009-06-09 11:11:09
Application options:
dbCodepage=4102
dbType=ORA
ddlMap=ddl_mapping.txt
extFiles=yes
importDirs=/oracle/dump/d51033500_1/EXP1:/oracle/dump/d51033500_1/EXP2:/oracle/dump/d51033500_1/EXP3:/oracle/dump/d51033500_1/EXP4:/oracle/dump/d51033500_1/EXP5:/oracle/dump/d51033500_1/EXP6:/oracle/dump/d51033500_2/EXP7:/oracle/dump/d51033500_2/EXP8:/oracle/dump/d51033500_2/EXP9:/oracle/dump/d51033500_2/EXP10:/oracle/dump/d51033500_2/EXP11
installDir=/tmp/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS
jobNum=1
loadArgs=-stop_on_error
monitorTimeout=30
orderBy=
r3loadExe=/usr/sap/DEV/SYS/exe/run/R3load
sapinst=
trace=all
tskFiles=yes
CONFIG: 2009-06-09 11:11:09
List of packages with table structure: 'SAP0000'.
CONFIG: 2009-06-09 11:11:09
List of packages with views: 'SAPVIEW'.
TRACE: 2009-06-09 11:11:09 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of '/tmp/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/DDLORA.TPL' template file is started.
INFO: 2009-06-09 11:11:09 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of '/tmp/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/DDLORA.TPL' template file is successfully completed.
Primary key creation: after load.
Index creation: after load.
TRACE: 2009-06-09 11:11:09 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of '/tmp/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/DDLORA_LRG.TPL' template file is started.
INFO: 2009-06-09 11:11:09 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of '/tmp/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/DDLORA_LRG.TPL' template file is successfully completed.
Primary key creation: after load.
Index creation: after load.
TRACE: 2009-06-09 11:11:09 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of '/tmp/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/DDLORA.TPL' template file is started.
INFO: 2009-06-09 11:11:09 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of '/tmp/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/DDLORA.TPL' template file is successfully completed.
Primary key creation: after load.
Index creation: after load.
INFO: 2009-06-09 11:11:10
Data codepage 1100 is determined using TOC file '/oracle/dump/d51033500_1/EXP1/DATA/SAPSSEXC.TOC' for package 'SAPSSEXC'.
INFO: 2009-06-09 11:11:15
Version table 'SVERS' is found in STR file '/oracle/dump/d51033500_2/EXP10/DATA/SAPNTAB.STR' from package 'SAPNTAB'.
INFO: 2009-06-09 11:11:15
Data conversion tables 'DDNTF,DDNTF_CONV_UC,DDNTT,DDNTT_CONV_UC' are found in STR file '/oracle/dump/d51033500_2/EXP10/DATA/SAPNTAB.STR' from package 'SAPNTAB'.
TRACE: 2009-06-09 11:11:15 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is started.
TRACE: 2009-06-09 11:11:15 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSSEXC' import package into database:
/usr/sap/DEV/SYS/exe/run/R3load -i SAPSSEXC.cmd -dbcodepage 4102 -l SAPSSEXC.log -stop_on_error
ERROR: 2009-06-09 11:11:17 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is interrupted with R3load error.
Process '/usr/sap/DEV/SYS/exe/run/R3load -i SAPSSEXC.cmd -dbcodepage 4102 -l SAPSSEXC.log -stop_on_error' exited with return code 2.
For mode details see 'SAPSSEXC.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
TRACE: 2009-06-09 11:11:39 com.sap.inst.migmon.LoadTask run
Loading of 'DOKCLU' import package is started.
TRACE: 2009-06-09 11:11:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'DOKCLU' import package:
/usr/sap/DEV/SYS/exe/run/R3load -ctf I /oracle/dump/d51033500_2/EXP11/DATA/DOKCLU.STR /tmp/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/DDLORA_LRG.TPL DOKCLU.TSK ORA -l DOKCLU.log
TRACE: 2009-06-09 11:11:40 com.sap.inst.migmon.LoadTask processPackage
Loading of 'DOKCLU' import package into database:
/usr/sap/DEV/SYS/exe/run/R3load -i DOKCLU.cmd -dbcodepage 4102 -l DOKCLU.log -stop_on_error
INFO: 2009-06-09 11:42:52 com.sap.inst.migmon.LoadTask run
Loading of 'DOKCLU' import package is successfully completed.
TRACE: 2009-06-09 11:43:10 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL2' import package is started.
TRACE: 2009-06-09 11:43:10 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPAPPL2' import package:
/usr/sap/DEV/SYS/exe/run/R3load -ctf I /oracle/dump/d51033500_2/EXP8/DATA/SAPAPPL2.STR /tmp/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/DDLORA.TPL SAPAPPL2.TSK ORA -l SAPAPPL2.log
TRACE: 2009-06-09 11:43:16 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL2' import package into database:
/usr/sap/DEV/SYS/exe/run/R3load -i SAPAPPL2.cmd -dbcodepage 4102 -l SAPAPPL2.log -stop_on_error
ERROR: 2009-06-09 11:49:45 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL2' import package is interrupted with R3load error.
Process '/usr/sap/DEV/SYS/exe/run/R3load -i SAPAPPL2.cmd -dbcodepage 4102 -l SAPAPPL2.log -stop_on_error' exited with return code 1.
For mode details see 'SAPAPPL2.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
INFO: 2009-06-09 11:58:24
Import Monitor is started.
CONFIG: 2009-06-09 11:58:24
Application options:
dbCodepage=4102
dbType=ORA
ddlMap=ddl_mapping.txt
extFiles=yes
importDirs=/oracle/dump/d51033500_1/EXP1:/oracle/dump/d51033500_1/EXP2:/oracle/dump/d51033500_1/EXP3:/oracle/dump/d51033500_1/EXP4:/oracle/dump/d51033500_1/EXP5:/oracle/dump/d51033500_1/EXP6:/oracle/dump/d51033500_2/EXP7:/oracle/dump/d51033500_2/EXP8:/oracle/dump/d51033500_2/EXP9:/oracle/dump/d51033500_2/EXP10:/oracle/dump/d51033500_2/EXP11
installDir=/tmp/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS
jobNum=1
loadArgs=-stop_on_error
monitorTimeout=30
orderBy=
r3loadExe=/usr/sap/DEV/SYS/exe/run/R3load
sapinst=
trace=all
tskFiles=yes
CONFIG: 2009-06-09 11:58:24
List of packages with table structure: 'SAP0000'.
CONFIG: 2009-06-09 11:58:24
List of packages with views: 'SAPVIEW'.
TRACE: 2009-06-09 11:58:24 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of '/tmp/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/DDLORA.TPL' template file is started.
INFO: 2009-06-09 11:58:24 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of '/tmp/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/DDLORA.TPL' template file is successfully completed.
Primary key creation: after load.
Index creation: after load.
TRACE: 2009-06-09 11:58:24 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of '/tmp/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/DDLORA_LRG.TPL' template file is started.
INFO: 2009-06-09 11:58:24 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of '/tmp/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/DDLORA_LRG.TPL' template file is successfully completed.
Primary key creation: after load.
Index creation: after load.
TRACE: 2009-06-09 11:58:24 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of '/tmp/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/DDLORA.TPL' template file is started.
INFO: 2009-06-09 11:58:24 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of '/tmp/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/DDLORA.TPL' template file is successfully completed.
Primary key creation: after load.
Index creation: after load.
INFO: 2009-06-09 11:58:24
Data codepage 1100 is determined using TOC file '/oracle/dump/d51033500_1/EXP1/DATA/SAPSSEXC.TOC' for package 'SAPSSEXC'.
INFO: 2009-06-09 11:58:30
Version table 'SVERS' is found in STR file '/oracle/dump/d51033500_2/EXP10/DATA/SAPNTAB.STR' from package 'SAPNTAB'.
INFO: 2009-06-09 11:58:30
Data conversion tables 'DDNTF,DDNTF_CONV_UC,DDNTT,DDNTT_CONV_UC' are found in STR file '/oracle/dump/d51033500_2/EXP10/DATA/SAPNTAB.STR' from package 'SAPNTAB'.
TRACE: 2009-06-09 11:58:30 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is started.
TRACE: 2009-06-09 11:58:30 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSSEXC' import package into database:
/usr/sap/DEV/SYS/exe/run/R3load -i SAPSSEXC.cmd -dbcodepage 4102 -l SAPSSEXC.log -stop_on_error
ERROR: 2009-06-09 11:58:32 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is interrupted with R3load error.
Process '/usr/sap/DEV/SYS/exe/run/R3load -i SAPSSEXC.cmd -dbcodepage 4102 -l SAPSSEXC.log -stop_on_error' exited with return code 2.
For mode details see 'SAPSSEXC.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
TRACE: 2009-06-09 11:58:54 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL2' import package is started.
TRACE: 2009-06-09 11:58:54 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL2' import package into database:
/usr/sap/DEV/SYS/exe/run/R3load -i SAPAPPL2.cmd -dbcodepage 4102 -l SAPAPPL2.log -stop_on_error

Does SAP support Solaris 10 ZFS filesystem when using DB2 V9.5 FP4?

Hi,
I'm installing NW7 (BI usage). SAPINST has failed in the step "ABAP LOAD due to the DB2 error message
"Unsupported file system type zfs for Direct I/O". It appears my Unix Admin must have decided to set these filesystems as ZFS on this new server.
I have several questions requiring your expertise.
1) Does SAP support ZFS filesystems on Solaris 10 (SPARC hardware)? I can not find any reference in SDN or Service Market Place? Any reference will be much appreciated.
2) How can I confirm my sapdata fielsystems are ZFS?
3) What actions do you recommend for me to resolve the SAPINST errors? Do I follow the note "Note 995050 - DB6: NO FILE SYSTEM CACHING for Tablespaces" to disable "Direct I/O" for all DB2 tablespaces? I have seen Markus Doehr's forum Link:[ thread|Re: DB2 on Solaris x64 - ZFS as filesystem possible?; but it does not state exactly how he overcame the error.
regards
Benny

Hi Frank,
Thanks for your input.
I have also found the command "zfs list" that would display any ZFS filesystems.
We have also gone back to UFS as the ZFS deployment schedule does not meet this particular SAP BW implementation timeline.
Has any one come across any SAP statement that states NW7 can be deployed with ZFS for DB2 database on Solaris SPARC platform. If not, I'll open an OSS message.
regards
Benny

SAP XI 3.0 Sizing

Bonjour a tous et a toutes,
Q1) When we say: We will execute a message that has a weight of 650KB 200 time a day. Since this is raw data and in SAP XI, (msg) are being represented in XML, Is there anyone who know if the SAP quick sizer tool is XML-lizing the weight of the document ? a 650KB msg worth much more (size wise) in XML.
Q2) Is there a sizing tool for SAP XI 7.0 ?
Merci !

Michel,
Check this sizing guide and it is same for XI3.0 and PI7.0 also:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/72e2bb90-0301-0010-e883-c390ad8a975a
For your example you have to put the size of this message as 650 * 200 * 2. Because your 650KB message when flows in XI we are counting as double the size with xml tags. It is only the approximate count not the exact count. You put this result in your sizing guide.
---Satish

Installing sap in solaris

hi kindly provide me documentation for installing sap 4.6c and 4.7c in sun solaris

Hi Shabnam!
I am looking for ECC 5.0/ERP2004 installation guides on Solaris 10 and Oracle 10. Do you know where to find them.. please provide complete path, as the places I have been looking does not contain an updated version.
https://websmp203.sap-ag.de/nw04installation, /erp-inst and /instguides all gave me the same old version from 28.feb 2005..
Please help.
Regards,
Thomas

SAP EIS Architecture and sizing

I have done lot of search for SAP documentation on sizing of different components involve in solutioning SAP EIS. But unfortunately I could not found any. Can you guys help me out here?
If you did already implemented EIS, then can you guys give me a rough estimate about your transaction volume, user base and your hardware sizing? That will at least help us for initial estimation. thanks in advance.
Regards,
Krishna

Krishna,
we hesitate to give you estimates on database and hardware sizing because, as Gabi states, sizing for EIS will vary from customer to customer based on the characteristics of the supply chain being modeled. Inputs for the sizing are the number of stocking points, number of supply paths, Bill of Material details (if applicable), the number of future periods to model, the number of historical periods of forecast and sales provided, lead times across the supply chain model and the number of models you will keep.
To make some very GENERAL comments, the more material sharing that occurs in your network the more memory needed to optimize (solve for Safety Stock) the model. Two customers can have the same number of stocking points and supply paths but if one has a distribution-only supply chain while the other has a model with a very detailed Bill of Material the distribution-only model will require much less memory to optimize.
Any further sizing information should go through Consulting as Gabi has indicated. Sizing an EIS implementation is somewhat unique and therefore general, cookie-cutter recommendations are not useful.
Hopefully that is helpful to you.
Chris

Uninstall SAP on Solaris

Hello,
I have an old machine with a sap system that is not used anymore.
I would like to uninstall sap.
/usr/sap/trans is not nfs shared.
I was thinking of removing the init/rc scripts, /usr/sap, /sapmnt and /oracle, /home/<SID>adm.
Are there files/directories that I have forgoten?
Thanks in advance for your answer.

Benoit,
If you are deleting all the files and directories, then entries will related to SAP in OS file systems will remain, like users,services etc..
Might be database instance will remain there which will give you error when you will install another instance of SAP in system.
As suggested by Deepak you should uninstall it using installation master CD or format the system bro. just kidding.
Just remove services entry and users, rest delete all SAP file system.If you will face any issues then it can be resolved, so go with it if you dont have installation master CD
Regards,
Amit Barnawal

SAP Install on Solaris 10 Sparse Root Zone ../usr/sap

Hi All,
I was wondering if anyone is running SAP on Solaris 10, SAP EHP4 ECC 6.0 Oracle DB version 10. App and Db in a sparse root zone.
When we initially created our SAP install the Directories containing <SID> and trans_<SID> was give to us as "/usr/sap"
Since this is a sparse root zone, the /usr directory is read only. To accommodate SAP, a directory was created in the global zone for each of the containers ( we have ECC, PI, BW etc..) and then mounted as a filesystem in each container.   /usr/sap exists in every container, and it was supposed to be nothing more than a mount point for the <SID> and trans_<SID> NFS mounts. This /usr/sap directory exists on the global zone of our M5000 and the additional files and folders are eating up OS space.
This creates me with two problems.
1. WHen I take a snapshot, I can't recover the zone in a automatic fashion because the local zone can not see the global /usr directory, so I have to recover that folder/file manually.
2. I don't know exactly, but files are being created in the usr/sap directory that is causing internal drives to grow quickly.
To resolve our issues it was determined that the best course of action is to remove the connection to the global zone by creating a /sap directory in each container and linking it as /usr/sap. The /sap directory will be an NFS/FC mount point and that will fix the issue of disk space usage and backup recovery.
Does anyone have another way to solve this problem or any suggestions that we should do something different. ?

I use sparse zones on Solaris with ZFS.
I delegate filesystems to the zone.
root@global ~# zonecfg -z zone_name info
zonename: zone_name
zonepath: /zfs_zones/zone_name
brand: native
autoboot: true
bootargs:
pool:
limitpriv:
scheduling-class:
ip-type: shared
hostid:
inherit-pkg-dir:
        dir: /lib
inherit-pkg-dir:
        dir: /platform
inherit-pkg-dir:
        dir: /sbin
inherit-pkg-dir:
        dir: /usr
net:
        address: w.x.y.z/nn
        physical: nxge0
        defrouter: w.x.y.z
dataset:
        name: zfs_zones/zone_name/oracle
dataset:
        name: zfs_zones/zone_name/sapmnt
dataset:
        name: zfs_zones/zone_name/usr_sap
root@zone_name ~# zfs list -o name,mountpoint
NAME                                     MOUNTPOINT
zfs_zones/zone_name/oracle               /oracle
zfs_zones/zone_name/oracle/SID_mirrlogA /oracle/SID/mirrlogA
zfs_zones/zone_name/oracle/SID_mirrlogB /oracle/SID/mirrlogB
zfs_zones/zone_name/oracle/SID_oraarch   /oracle/SID/oraarch
zfs_zones/zone_name/oracle/SID_origlogA /oracle/SID/origlogA
zfs_zones/zone_name/oracle/SID_origlogB /oracle/SID/origlogB
zfs_zones/zone_name/oracle/SID_sapdata1 /oracle/SID/sapdata1
zfs_zones/zone_name/oracle/SID_sapdata2 /oracle/SID/sapdata2
zfs_zones/zone_name/oracle/SID_sapdata3 /oracle/SID/sapdata3
zfs_zones/zone_name/oracle/SID_sapdata4 /oracle/SID/sapdata4
zfs_zones/zone_name/sapmnt               /sapmnt
zfs_zones/zone_name/usr_sap              /usr/sap
Edited by: RUSS HANSEN on Dec 14, 2011 8:52 PM

SAP filesystem layout on Solaris 10 Assistance

Hi Guys,
I'd like to ask who has experience running SAP over Solaris a few questions regarding filesystem. I have strong backgound on AIX server but little over Solaris, so im transitioning from AIX to Solaris to understand this
My goal is to identify/Analyse how a SAP instance was installed on a Solaris Server and if so, following Best Practices.
First of all is to determine if the /usr/sap/PRD and Oracle filesystems where mounted all on the root directory or if were mounted
on separate filesystems which is the recommended setup
As example i have this output for df -g
/oracle/PRD        (/dev/dsk/c4t0d2s5 ):
/sapmnt/PRD        (/dev/dsk/c4t0d6s5 )
/home/prdadm       (/dev/dsk/c4t0d7s3 ):
/usr/sap/PRD       (/dev/dsk/c4t0d5s3 ):
/oracle/PRD/oraarch(/dev/dsk/c4t0d9s0)
/oracle/PRD/sapdata14(/dev/dsk/c4t0d8s0 )
/oracle/PRD/sapdata15(/dev/dsk/c4t0d4s0 )
/oracle/PRD/origlogA(/dev/dsk/c4t0d7s0 ):
/dev/dsk/xxxxxxxxx does mean they are all on the "root" directory instead being splitted into multiple filesystems?
Which commands would be helpful to analyze the Disk layout of this Server so I can understand how SAP was mounted:
devices ( HDD )
Volume Groups
Logical Volumenes
and file systems
(On AIX lsvg, lslv would be the choices)
Any help would be highly appreciated
Regards!

$ cat /etc/vfstab
#device                             device          mount                     FS      fsck    mount   mount
#to mount                           to fsck         point                     type    pass    at boot options
fd                                         -            /dev/fd                     fd      -       no      -
/proc                                      -            /proc                       proc    -       no      -
/dev/md/dsk/d3                          -                 -                      swap    -       no      -
/dev/md/dsk/d0           /dev/md/rdsk/d0 /                                     ufs     1       no      logging
/devices                                 -            /devices                      devfs   -       no      -
ctfs                                       -            /system/contract            ctfs    -       no      -
objfs                                      -            /system/object           objfs   -       no      -
swap                                       -             /tmp                        tmpfs   -       yes     -
/dev/md/dsk/d6           /dev/md/rdsk/d6           /export/home              ufs     2       yes     logging
/dev/md/dsk/d12           /dev/md/rdsk/d12        /var/crash                ufs     2       yes     logging
/dev/dsk/c4t0d0s6       /dev/rdsk/c4t0d0s6      /opt/JES                ufs     2       yes     -
/dev/dsk/c4t0d2s5       /dev/rdsk/c4t0d2s5      /oracle/PRD             ufs     2       yes     -
/dev/dsk/c4t0d2s0       /dev/rdsk/c4t0d2s0      /oracle/PRD/sapdata9    ufs     2       yes     -
/dev/dsk/c4t0d2s1       /dev/rdsk/c4t0d2s1      /oracle/PRD/sapdata11   ufs     2       yes     -
/dev/dsk/c4t0d2s4       /dev/rdsk/c4t0d2s4      /oracle/PRD/sapdata12   ufs     2       yes     -
/dev/dsk/c4t0d0s1       /dev/rdsk/c4t0d0s1      /oracle/PRD/sapdata1    ufs     2       yes     -
/dev/dsk/c4t0d0s5       /dev/rdsk/c4t0d0s5      /oracle/PRD/sapreorg    ufs     2       yes     -
/dev/dsk/c4t0d0s3       /dev/rdsk/c4t0d0s3      /oracle/PRD/sapdata2    ufs     2       yes     -
/dev/dsk/c4t0d4s1       /dev/rdsk/c4t0d4s1      /oracle/PRD/sapdata7    ufs     2       yes     -
/dev/dsk/c4t0d2s3       /dev/rdsk/c4t0d2s3      /oracle/PRD/sapdata8    ufs     2       yes     -
/dev/dsk/c4t0d1s1       /dev/rdsk/c4t0d1s1      /oracle/PRD/sapdata4    ufs     2       yes     -
/dev/dsk/c4t0d0s0       /dev/rdsk/c4t0d0s0      /oracle/PRD/sapdata10   ufs     2       yes     -
/dev/dsk/c4t0d1s5       /dev/rdsk/c4t0d1s5      /oracle/PRD/102_64      ufs     2       yes     -
/dev/dsk/c4t0d1s3       /dev/rdsk/c4t0d1s3      /oracle/PRD/sapdata5    ufs     2       yes     -
/dev/dsk/c4t0d0s4       /dev/rdsk/c4t0d0s4      /oracle/PRD/920_64      ufs     2       yes     -
/dev/dsk/c4t0d1s6       /dev/rdsk/c4t0d1s6      /oracle/PRD/saparch     ufs     2       yes     -
/dev/dsk/c4t0d1s0       /dev/rdsk/c4t0d1s0      /oracle/PRD/sapdata3    ufs     2       yes     -
/dev/dsk/c4t0d1s4       /dev/rdsk/c4t0d1s4      /oracle/PRD/sapdata6    ufs     2       yes     -
/dev/dsk/c4t0d6s1       /dev/rdsk/c4t0d6s1      /oracle/PRD/mirrlogA    ufs     2       yes     -
/dev/dsk/c4t0d6s3       /dev/rdsk/c4t0d6s3      /oracle/PRD/mirrlogB    ufs     2       yes     -
/dev/dsk/c4t0d5s0       /dev/rdsk/c4t0d5s0      /usr/sap/put            ufs     2       yes     -
#/dev/dsk/c4t0d6s0      /dev/rdsk/c4t0d6s0      /usr/sap/PRD    ufs     2       yes     -
/dev/dsk/c4t0d5s3       /dev/rdsk/c4t0d5s3      /usr/sap/PRD    ufs     2       yes     -
/dev/dsk/c4t0d6s5       /dev/rdsk/c4t0d6s5      /sapmnt/PRD     ufs     2       yes     -
/dev/dsk/c4t0d7s0       /dev/rdsk/c4t0d7s0      /oracle/PRD/origlogA    ufs     2       yes     -
/dev/dsk/c4t0d7s1       /dev/rdsk/c4t0d7s1      /oracle/PRD/origlogB    ufs     2       yes     -
/dev/dsk/c4t0d7s3       /dev/rdsk/c4t0d7s3      /home/prdadm    ufs     2       yes     -
/dev/dsk/c4t0d7s4       /dev/rdsk/c4t0d7s4      /instalar               ufs     2       yes     -
/dev/dsk/c4t0d7s5       /dev/rdsk/c4t0d7s5      /oracle/stage           ufs     2       yes     -
/dev/dsk/c4t0d3s3       /dev/rdsk/c4t0d3s3      /oracle/PRD/sapdata13   ufs     2       yes     -
/dev/dsk/c4t0d8s0       /dev/rdsk/c4t0d8s0      /oracle/PRD/sapdata14   ufs     2       yes     -
/dev/dsk/c4t0d4s0       /dev/rdsk/c4t0d4s0      /oracle/PRD/sapdata15   ufs     2       yes     -
/dev/dsk/c4t0d9s0       /dev/rdsk/c4t0d9s0      /oracle/PRD/oraarch     ufs     2       yes     -
/dev/dsk/c4t0d3s0       /dev/rdsk/c4t0d3s0      /moniora                ufs     2       yes     -
sandboxifrs:/usr/sap/trans      -       /usr/sap/trans nfs     -       yes     soft,bg
##10.18.251.34:/vol/ELOPESAPVOL      -       /REDOTEMPORAL nfs     -       yes     soft,bg
10.18.251.37:/V490      -       /RESPALDO nfs     -       yes     soft,bg,vers=3

Solaris Cluter 3.2 for SAP

Hello All,
My SAP production environment needs to be running under Solaris Cluster 3.2. I am thinking of T5440 servers - 2 in number and StorageTek 6140. The agents available for SAP on Solaris Cluster 3.2 are:
Sun Cluster HA for SAP (failover or scalable).
Sun Cluster HA for SAP LiveCache (failover).
Sun Cluster HA for SAP Web Application Server (failover or scalable).
Sun Cluster HA for SAP DB (failover)
The ERP 6.0, EP 7.0, BI7.0 and Oracle HA DB needs to failover from one node to another.
My question is: What agents do I need to purchase for failing over the above the applications beside Sun Cluster HA for Oracle.
SAP vendor is asking me to provide three logical host names. The idea of Solaris 10 zones came into my mind.
Zones can be implemented with Sun Cluster 3.2 software in the global zone. That is, Sun Cluster 3.2 with zones enabled will be treated like physical nodes to be part of Sun Cluster Resource Groups. I feel it is best for those applications which are supported with containers and have a Sun Cluster agent but don't have the requirement of the zone itself failing over in case of a failure.
Any suggestions will be helpful.
Best Regards,
Bruce

You might be interested to read the following Solaris Cluster for SAP Configuration Guide:
[http://www.sun.com/third-party/global/sap/collateral/SAP-Cluster-Config-final.pdf|http://www.sun.com/third-party/global/sap/collateral/SAP-Cluster-Config-final.pdf]
Regards
Thorsten

Initial Sizing for SAP MDM

Need help on the initial sizing for hardware - app and db servers for SAP MDM 7.1 running on AIX and DB2.

Hi,
You can find all MDM guides at - https://websmp102.sap-ag.de/installmdm71
Sizing Guide -
https://websmp102.sap-ag.de/~sapidb/011000358700001921872008E
Thanks,
Shambhu.

SAP sizing on UCS

We are in the process of putting documentation together for sizing an SAP environment running on UCS. Our initial documentation looks to equate the SAP benchmark (SAPS) with blade/chassis sizing for UCS. When working with other hardware vendors, we usually provide them with the SAP Quicksizer output (SAPS) and they provide us with initial CPU/memory/server model information.
Has anyone worked with Cisco on an SAP sizing exercise or can anyone point me to documentation provided by Cisco on how to size SAP on UCS?
Thanks.
Matthew

Hello Matthew,
1) Cisco do not do sizing. Cisco create architecture, when a SAP partner, SAP consultant or SAP provide the requirements in terms of SAPS (the "horsepower" of a server).
2) Reach out to a Cisco person supporting SAP opportunities in your country.
3) You can locate CISCO partner for your country at following link
http://tools.cisco.com/WWChannels/LOCATR/openBasicSearch.do
I hope this will help
Regards,
Shahzad
-----Please remember to rate useful posts, by clicking on the stars below------

SAP CE SIZING

Dear All,
We are planing to Implement the SAP BPM in our land scape.
How ever we are about start the Sizing for the Hardware.
I tried searching the Quick sizer in the service market place but i did not find any clue.
Could any one help us for the sizing SAP CE
Awaiting for your reply.

Hi,
Try the Quick Sizer tool in the following way:
- Customer no. = 188213
- Project Name = A
- Click 'Display Projects'
- In the search box use 'CE'
- Check the 'Match whole word' box below the search box
That should give you some results. You'll see a SAP Netweaver Composition Environment sizing option. That should get you started although it looks like it CE 7.1 related.
Best Regards, Trevor

SAP on Solaris Filesyste sizing

Similar Messages

Maybe you are looking for