Database Reference
In-Depth Information
• The database instance term remains unchanged.
• The Software Deployment Manager (SDM) component is no longer available in the
Java system. JSPM (Java Support Package Manager) performs all the activities of
SDM as well.
• You no longer need to download JDK from another vendor. SAP JVM is shipped
along with the install software in the master DVD, and is automatically installed by
SAPinst.
SAP System Install Build Specifications
Now that we have reviewed the definitions that will be used in this and subsequent chapters
related to SAP installations, let us look at a sample UNIX build specification. It is a best
practice to write a formal build specification with all the naming conventions and provide it
to the UNIX, storage, and database teams so that they can start allocating the needed storage
space and building the underlying operating system (OS) file system (see
Table 5-1
) that is
needed for the database and the SAP application installation. Please note that this is not a
comprehensive build specification. Additional information such as swap space require-
ments, UNIX kernel parameters, OS patches, and swap information is included in the build
specification as per the instructions and operating system-specific OSS Notes provided in
the install guide. User accounts <SAPSID>adm (e.g., devadm) and ora<SAPSID> (e.g.,
oradev) can be created before the start of the installation as per instructions in the install
manual and your organizations standards. Otherwise, the SAPinst program will create the
accounts in the system during the course of the install.
