IBM DB2 9 SAP SID DR1, DR11DBM1, DR11IRLM, DR11DIST, Sapinst, Rrsd, Sapd, SGDR1CAT, SGDR1LOG

Page 40

XIII

Naming Conventions

1. The following elements should be part of an overall naming convention plan:

SAP SID

DR1

DB2 Started Task Names for MSTR, DBM1,DIST, IRLM DR11MSTR

 

DR11DBM1

 

DR11IRLM

 

DR11DIST

DB2 Member/Subsystem Name

DR11

DB2 SYSADM Userid

SAPINST

DB2 Group Attach Name

DR1

RRS Started Task Name

RRSD

TCP/IP Host Names

SAPD

TCP/IP DDF Port Numbers

 

ICF Catalog Name

CATALOG.SAPDB2.xxxxx

High Level Qualifier For Dataset Names

DR1U for SAP Data

 

DR1IC for DB2 Image Copies

 

DR1 for DB2 Catalog,

 

Directory,

 

DR11 for System Libraries

 

DR11 for DB2 Active Logs,

 

Archive Logs, BSDS

SAP SMS Storage Groups

SGDR1CAT

 

SGDR1LOG

 

SGDR1ARC

 

SGDR1SAP

 

SGDR1IC

DB2 Connect Instance Name

DR1INST1

DB2 Connect Userid

DR1DB2C

DDF Location Name

DR1DDF

USS superuser (to run saposcol,sapccmsr)

DR1SUSER

2.For multiple mySAP.com components consider a naming convention such as:

-First character identifies the type of system (e.g., development=D, production=P, quality assurance=Q, training=T, sandbox=S)

-Second character identifies the component (e.g., R/3=R, BW=B, APO=A, EBP=E, CRM=C)

-Third character is the system number or region:

Example: DR1 is the first development R/3 system

PR1 is the first production R/3 system

QR1 is the first quality assurance R/3 system

PB1 is the first production BW system

Copyright 2006 IBM Solutions Technical Sales (STS)

12/18/2007Page 40 of 51

12/18/2007

 

Image 40
Contents Albert D. Rodi Trademarks VII What is new with SAP Web Application Server 6.40 ? What is new with SAP Web Application Server 7.0 ?General Preparation Steps DB2 DBA 12/18/2007Page 6 12/18/2007Page 7 12/18/2007Page 8 12/18/2007Page 9 II z/OS Hardware Preparation 12/18/2007Page 11 III AIX Hardware Preparation Required for High Availability ENQ/SCS Solution IV z/OS Software PreparationRequired Highly Recommended12/18/2007Page 14 12/18/2007Page 15 Class Nameiggcas 12/18/2007Page 17 DB2 Preparation MLMT=4 MAXCSA=0 DEADLOK=5,1 12/18/2007Page 20 System Timeout Term Longlog Drain Delay Drainwait Retry RetrydelayMaxro Drain ALLSapcl FAQ VI DB2 Related OSS Notes12/18/2007Page 24 AIX Software Preparation Highly Recommended for AIX Application ServersViii Windows Hardware/Software Preparation SAP Installation Preparation MAXSHAREPAGES131072 Sample BPXPRMxx MemberForkcopycow Afinet Transport for TCP/IP Sample DB2 Dsnzparms DB2 = required/recommended value for SAPIRLMSWT=300, * LRDRTHLD=10 MAXKEEPD=8000, * MINSTOR=YES NPGTHRSH=10RECALL=YES RECALLD=120 RELCURHL=YES SYSOPR1=SYSOPRXLKUPDLT=TARGET DSN6ARVP ALCUNIT=TRK, CYL CATALOG=YESIDFORE=60 LBACKOUT=NO MON=YESAPPENSCH=EBCDIC MAXKEEPD=8000, * MINSTOR=YES MXDTCACH=128, * NPGTHRSH=10 PROTECT=NO PARTKEYU=YES RECALL=YES RECALLD=120SECQTY=100 LBACKOUT=NO, * LOGAPSTG=100 LOBVALA=1GB LOBVALS=50GB IDFORE=60 IDXBPOOL=BP3 IMPDSDEF=NO IMPTSCMP=YESMGEXTSZ=YES MON=YES TSQTY=720 TIMELEN=0 END XII TCP/IP ConnectivitySapinst SAP SID DR1DR11DBM1 DR11IRLMXIV Gateway XV Sample OSA-Express GB ConfigurationStart PORTGBF8 DB2 Backup/Recovery Notes OSS Note Recover TABLESPACE/RECOVER IndexspaceStop DB2 12/18/2007Page 45 12/18/2007Page 46 Xvii SAP Automation And High Availability Solution NFS 12/18/2007Page 49 XIX Sample SMS Storage Group Assignments SYS SortSoftw HFS

DB2 V8, DB2 9 specifications

IBM DB2 is a family of data management products that provide powerful capabilities for managing large amounts of data. Among its various versions, DB2 9 and DB2 V8 stand out due to their advanced features and technologies that cater to both enterprise needs and modern database requirements.

DB2 9, also known as "Viper," was a significant release that brought substantial enhancements to the database management system. One of its standout features is its support for XML data. This version introduced a native XML storage architecture, allowing users to store, retrieve, and manage XML data efficiently. The advanced query capabilities for XML data made it easier to integrate both structured and unstructured information into applications.

Another notable aspect of DB2 9 is its enhanced security features. It introduced features like label-based access control, ensuring that sensitive data could be properly managed according to the security policies of an organization. This version also included a transparent data encryption mechanism, protecting data at rest without impacting performance.

DB2 V8, released prior to DB2 9, presented several key features that had a lasting impact on database technology. One of its major advancements was the introduction of pureXML, which laid the groundwork for handling XML data. DB2 V8 also provided improved performance through enhancements such as table partitioning, which allowed for more efficient data organization and retrieval.

Additionally, DB2 V8 emphasized high availability and disaster recovery, incorporating features like DB2 HADR (High Availability Disaster Recovery). This allowed organizations to ensure data continuity even in the event of system failures, a critical aspect for enterprise environments that rely on uninterrupted access to their data.

Both versions of DB2 leveraged advanced technologies such as multi-version concurrency control (MVCC), which enhanced transaction integrity and performance. Their ability to support various platforms, including Linux, UNIX, and Windows, demonstrated IBM's commitment to providing flexible solutions tailored to different environments.

In summary, both IBM DB2 9 and DB2 V8 established a strong foundation in the database management ecosystem. With features focused on XML data management, enhanced security, performance improvements, and high availability, these versions have equipped organizations with the tools necessary to handle contemporary data challenges efficiently and effectively. Their legacy continues to influence database technology today, highlighting IBM's enduring impact on data management solutions.