Summary
Symptom
Topics Date changed
====== ============
1 General Information Apr/2013
2 Pre-Installation Aug/2012
3 Installation May/2011
4 Post-Installation Apr/2012
+===================================================================+
1: General Information
+===================================================================+
Hardware requirements
The hardware requirements described in section '3.6 Setup of Database Layout' of the installation guide apply.
Provide enough free space for the database file systems:
SAP NetWeaver 7.3/7.31/7.4:
ABAP
sapdata 40 GB
saplog 10 GB
Java
sapdata 10 GB
saplog 2 GB
SAP ERP 6.0 incl. EhP 5/EhP 6 on SAP NetWeaver 7.3 and higher:
Java
sapdata 10 GB
saplog 2 GB
SAP SRM 7.0 incl. EhP 1/EhP 2 on SAP NetWeaver 7.3 and higher:
Java
sapdata 10 GB
saplog 2 GB
SAP CRM 7.0 incl. EhP 1/EHP 2 on SAP NetWeaver 7.3 and higher:
Java
sapdata 10 GB
saplog 2 GB
-----------------------<D055517, Jun 17, 12>-------------------------
Prerequisite on AIX
APAR IV10828 is a prerequisite to be able to install and run SAP Business Suite on Sybase ASE on AIX.
Check if it is applied by running "emgr -lv3". See SAP Note 1458918.
The APAR is also contained in AIX 7.1 SP6: "oslevel -s" shows at least 7100-00-06-xxxx.
-----------------------<D055517, AUG 02, 2012>-------------------------
Heterogeneous system copy with target SAP Sybase ASE
Implement SAP Note 1612437 before you start the homogeneous system copy procedure on Unix or Windows.
For further information about heterogeneous system copy with target database Sybase ASE, refer to SAP Note 1672367 or 1697542, respectively.
+===================================================================+
2: Pre-Installation
+===================================================================+
-----------------------<D003144, Apr 9, 2013>-----------------------
Installation media
Copy all installation media locally to the host where the SAP system will be installed.
For more information, refer to SAP Note 1806816: Media list for installations based on NW 7.3 incl. EHPs.
-----------------------<D055517, MAY 19, 2011>-----------------------
Choose number of r3load processes to avoid running out of logspace
To avoid the following error during the ABAP import phase, adjust the number of r3load processes according to the size of your system.
[ASE Error SQL1105]Can't allocate space for object 'syslogs' in database '<SID>' because 'logsegment' segment is full/has no free extents.
+===================================================================+
3: Installation
+===================================================================+
-----------------------<D055517, MAY 19, 11>-------------------------
Installation phase 'ABAP Import' fails after running out of log space
Analysis:
An import logfile created by r3load, for example DD03.log, contains the following error message:
[ASE Error SQL1105]Can't allocate space for object 'syslogs' in database '<SID>' because 'logsegment' segment is full/has no free extents.
Solution:
Press 'Retry' in SAPinst to restart the failed package. In case the error reappears, increase the log space. Log on to the OS with user syb<sid>, call isql and login as user sapsa:
sp_helpdevice
go
<get the device path for the current log device>
go
use master
go
disk init name = log<SID>_2, physname='<device path>\log<SID>_2.dat', size = '2048M'
go
alter database <SID> log on log<SID>_2 = 2048
go
checkpoint <SID>
go
-----------------------<D055517, AUG 29, 2011>-------------------------
Installation phase 'Start Java engine' fails
Problem:
The Java central instance does not start.
Instance <SID>/JC<nn> reached state STOPPING after having state STARTING.
Giving up.
This problem might also appear during a Support Package import using JSPM.
Analysis:
std_bootstrap_ID<nnnnnnn>.out contains an entry
[Thr 08] *** ERROR => JsfGetShmVmci: check failed: sRefs.statAccess >
SFI_SMA_NOTINIT [jsfxxsproc.c 439]
Solution:
Edit the Java central instance profile and comment out the line
jstartup/max_caches=500.
Note:
This is only a workaround. If any other SAP Note requests to adjust this profile parameter in a certain way, do follow that SAP Note and adjust the parameter value according to your needs.
-----------------------<D055517, MAR 16, 11>-------------------------
(Only: Additional Dialog Installation) Installation phase 'Start Instance' fails
Problem:
You install an additional dialog instance. It fails after a timeout when it tries to bring the installed dialog instance online.
Analysis:
dev_disp contains an entry:
***LOG Q1K=> MsIAttachEx: StoC check failed, Kernel not compatible with system (rc=29) [msxxi.c 820]
*** ERROR => not allowed to connect to message server via port 3900 [dpxxdisp.c 12214]
*** ERROR => Please check your configuration (profile parameter rdisp/msserv_internal) [dpxxdisp.c 12215]
DpHalt: shutdown server >lsi406_TRX_01 < (normal)
DpHalt: stop work processes
Solution:
Change one line in DEFAULT.PFL from:
rdisp/msserv = sapms<SID>
to:
rdisp/msserv = 0
Press 'Retry' in SAPinst or start the dialog instance manually.
+===================================================================+
4: Post-Installation
+===================================================================+
-----------------------<D055517, APR 03, 2012>-----------------------
Update SAP Sybase ASE database and SAP kernel version
Apply the latest version for the SAP Sybase ASE database (SAP Note 1554717) and the SAP kernel available at http://service.sap.com/swdc.
The Sybase ASE database patches are available under:
--> Support Packages and Patches
--> Browse our Download Catalog
--> Sybase Products
--> Sybase ASE FOR BUSINESS SUITE
--> Sybase ASE 15.7 FOR BUS. SUITE
--> <your platform>
Do not download any SAP Sybase ASE database patches directly from Sybase.com
-----------------------<D055517, JUL 26, 2012>-----------------------
Error in step 53 of functional unit configuration tool for System Landscape Directory or when running RZ70 (only SAP_BASIS 7.31 SP0)
Problem: Execution of function BAPI_SLD_SUPPLIER_CONFIG_SET ends with an error (message ID: null, message number: connection closed without message (CM_NO_DATA_RECEIVED):null, message text: {3}).
Solution: Skip the step and continue.
Despite the error message, the system was successfully registered in the SLD.
-----------------------<D055517, AUG 03, 2012>-----------------------
Implement mandatory SAP notes
Make sure you implement the following SAP notes in order for the SAP
System and DBA Cockpit to operate correctly.
Solution:
Call transaction SNOTE.
Download and implement SAP Note 1558958 for SAP NW 7.30.
Download and implement SAP Note 1619967 for SAP NW 7.31.
Download and implement SAP Note 1617621.
-----------------------<D053089, NOV 22, 2011>-----------------------
Error message during java deployment "Attempt to insert duplicate key"
Problem: AS Java displays the following error message:
1. Attempt to insert duplicate key row in object 'BC_XMLA_ASETS' with unique index 'BC_XMLA_AS_19895790952' OpenSQLExceptionCategories: [NON_TRANSIENT, INTEGRITY_CONSTRAINT_VIOLATION] Create an OSS message.
Solution: Import the necessary Java patch, refer to SAP Note 1627468.
Installation SAP NetWeaver 7.3 / 7.3 incl. Enhancement Package 1 / 7.4 using software provisioning manager 1.0 for the installation.
- SAP NetWeaver 7.3
- SAP NetWeaver 7.3 incl. Enhancement Package 1
- SAP NetWeaver 7.4
- SAP Business Suite 7i2010 (SAP ERP 6.0 EHP5, SAP CRM 7.0 EHP1, SAP SRM 7.0 EHP1, SAP SCM 7.0 EHP1) on SAP NetWeaver 7.3 Java Hubs
- SAP Business Suite 7i2011 (SAP ERP 6.0 EHP6, SAP CRM 7.0 EHP2, SAP SRM 7.0 EHP2, SAP SCM 7.0 EHP2) on SAP NetWeaver 7.3 Java Hubs
- SAP Business Suite 7i2013 (SAP ERP 6.0 EHP7, SAP CRM 7.0 EHP3, SAP SRM 7.0 EHP3, SAP SCM 7.0 EHP3) on SAP NetWeaver 7.4
SAP Sybase ASE, installation, SAP systems based on SAP NetWeaver 7.3, SAP systems based on SAP NetWeaver 7.31, software provisioning manager
Reason and Prerequisites
You want to install an SAP system based on SAP NetWeaver 7.3 and higher using the installation tool software provisioning manager. This SAP Note is about problems discovered after the publication of the installation guide.
SolutionTopics Date changed
====== ============
1 General Information Apr/2013
2 Pre-Installation Aug/2012
3 Installation May/2011
4 Post-Installation Apr/2012
+===================================================================+
1: General Information
+===================================================================+
Hardware requirements
The hardware requirements described in section '3.6 Setup of Database Layout' of the installation guide apply.
Provide enough free space for the database file systems:
SAP NetWeaver 7.3/7.31/7.4:
ABAP
sapdata 40 GB
saplog 10 GB
Java
sapdata 10 GB
saplog 2 GB
SAP ERP 6.0 incl. EhP 5/EhP 6 on SAP NetWeaver 7.3 and higher:
Java
sapdata 10 GB
saplog 2 GB
SAP SRM 7.0 incl. EhP 1/EhP 2 on SAP NetWeaver 7.3 and higher:
Java
sapdata 10 GB
saplog 2 GB
SAP CRM 7.0 incl. EhP 1/EHP 2 on SAP NetWeaver 7.3 and higher:
Java
sapdata 10 GB
saplog 2 GB
-----------------------<D055517, Jun 17, 12>-------------------------
Prerequisite on AIX
APAR IV10828 is a prerequisite to be able to install and run SAP Business Suite on Sybase ASE on AIX.
Check if it is applied by running "emgr -lv3". See SAP Note 1458918.
The APAR is also contained in AIX 7.1 SP6: "oslevel -s" shows at least 7100-00-06-xxxx.
-----------------------<D055517, AUG 02, 2012>-------------------------
Heterogeneous system copy with target SAP Sybase ASE
Implement SAP Note 1612437 before you start the homogeneous system copy procedure on Unix or Windows.
For further information about heterogeneous system copy with target database Sybase ASE, refer to SAP Note 1672367 or 1697542, respectively.
+===================================================================+
2: Pre-Installation
+===================================================================+
-----------------------<D003144, Apr 9, 2013>-----------------------
Installation media
Copy all installation media locally to the host where the SAP system will be installed.
For more information, refer to SAP Note 1806816: Media list for installations based on NW 7.3 incl. EHPs.
-----------------------<D055517, MAY 19, 2011>-----------------------
Choose number of r3load processes to avoid running out of logspace
To avoid the following error during the ABAP import phase, adjust the number of r3load processes according to the size of your system.
[ASE Error SQL1105]Can't allocate space for object 'syslogs' in database '<SID>' because 'logsegment' segment is full/has no free extents.
+===================================================================+
3: Installation
+===================================================================+
-----------------------<D055517, MAY 19, 11>-------------------------
Installation phase 'ABAP Import' fails after running out of log space
Analysis:
An import logfile created by r3load, for example DD03.log, contains the following error message:
[ASE Error SQL1105]Can't allocate space for object 'syslogs' in database '<SID>' because 'logsegment' segment is full/has no free extents.
Solution:
Press 'Retry' in SAPinst to restart the failed package. In case the error reappears, increase the log space. Log on to the OS with user syb<sid>, call isql and login as user sapsa:
sp_helpdevice
go
<get the device path for the current log device>
go
use master
go
disk init name = log<SID>_2, physname='<device path>\log<SID>_2.dat', size = '2048M'
go
alter database <SID> log on log<SID>_2 = 2048
go
checkpoint <SID>
go
-----------------------<D055517, AUG 29, 2011>-------------------------
Installation phase 'Start Java engine' fails
Problem:
The Java central instance does not start.
Instance <SID>/JC<nn> reached state STOPPING after having state STARTING.
Giving up.
This problem might also appear during a Support Package import using JSPM.
Analysis:
std_bootstrap_ID<nnnnnnn>.out contains an entry
[Thr 08] *** ERROR => JsfGetShmVmci: check failed: sRefs.statAccess >
SFI_SMA_NOTINIT [jsfxxsproc.c 439]
Solution:
Edit the Java central instance profile and comment out the line
jstartup/max_caches=500.
Note:
This is only a workaround. If any other SAP Note requests to adjust this profile parameter in a certain way, do follow that SAP Note and adjust the parameter value according to your needs.
-----------------------<D055517, MAR 16, 11>-------------------------
(Only: Additional Dialog Installation) Installation phase 'Start Instance' fails
Problem:
You install an additional dialog instance. It fails after a timeout when it tries to bring the installed dialog instance online.
Analysis:
dev_disp contains an entry:
***LOG Q1K=> MsIAttachEx: StoC check failed, Kernel not compatible with system (rc=29) [msxxi.c 820]
*** ERROR => not allowed to connect to message server via port 3900 [dpxxdisp.c 12214]
*** ERROR => Please check your configuration (profile parameter rdisp/msserv_internal) [dpxxdisp.c 12215]
DpHalt: shutdown server >lsi406_TRX_01 < (normal)
DpHalt: stop work processes
Solution:
Change one line in DEFAULT.PFL from:
rdisp/msserv = sapms<SID>
to:
rdisp/msserv = 0
Press 'Retry' in SAPinst or start the dialog instance manually.
+===================================================================+
4: Post-Installation
+===================================================================+
-----------------------<D055517, APR 03, 2012>-----------------------
Update SAP Sybase ASE database and SAP kernel version
Apply the latest version for the SAP Sybase ASE database (SAP Note 1554717) and the SAP kernel available at http://service.sap.com/swdc.
The Sybase ASE database patches are available under:
--> Support Packages and Patches
--> Browse our Download Catalog
--> Sybase Products
--> Sybase ASE FOR BUSINESS SUITE
--> Sybase ASE 15.7 FOR BUS. SUITE
--> <your platform>
Do not download any SAP Sybase ASE database patches directly from Sybase.com
-----------------------<D055517, JUL 26, 2012>-----------------------
Error in step 53 of functional unit configuration tool for System Landscape Directory or when running RZ70 (only SAP_BASIS 7.31 SP0)
Problem: Execution of function BAPI_SLD_SUPPLIER_CONFIG_SET ends with an error (message ID: null, message number: connection closed without message (CM_NO_DATA_RECEIVED):null, message text: {3}).
Solution: Skip the step and continue.
Despite the error message, the system was successfully registered in the SLD.
-----------------------<D055517, AUG 03, 2012>-----------------------
Implement mandatory SAP notes
Make sure you implement the following SAP notes in order for the SAP
System and DBA Cockpit to operate correctly.
Solution:
Call transaction SNOTE.
Download and implement SAP Note 1558958 for SAP NW 7.30.
Download and implement SAP Note 1619967 for SAP NW 7.31.
Download and implement SAP Note 1617621.
-----------------------<D053089, NOV 22, 2011>-----------------------
Error message during java deployment "Attempt to insert duplicate key"
Problem: AS Java displays the following error message:
1. Attempt to insert duplicate key row in object 'BC_XMLA_ASETS' with unique index 'BC_XMLA_AS_19895790952' OpenSQLExceptionCategories: [NON_TRANSIENT, INTEGRITY_CONSTRAINT_VIOLATION] Create an OSS message.
Solution: Import the necessary Java patch, refer to SAP Note 1627468.
Header Data
| Release Status: | Released for Customer |
| Released on: | 05.09.2013 09:59:29 |
| Master Language: | English |
| Priority: | Correction with high priority |
| Category: | Installation information |
| Primary Component: | BC-DB-SYB Sybase ASE Database Platform |
Affected Releases
|
Related Notes
No comments:
Post a Comment