Prithvi Information Solutions 425 N. Craig Street, Suite 202, Pittsburgh, PA

Transcription

1 IBM DB2 Universal Database Enterprise Edition, V7.2 for Windows Operating Environments Prithvi Information Solutions 425 N. Craig Street, Suite 202, Pittsburgh, PA Contributed by: Manish Pokarna DBA

2 Introduction IBM DB2 Universal Database is a leader in database scalability, reliability, multimedia extensibility, and Web enabling needed for most of the demanding e-business applications. DB2 products are available for a large number of platforms. DB2 Universal Database Version 7.2 is a fully Web-enabled relational database management system. It is scalable from single processors to symmetric multiprocessors to massively parallel clusters. DB2 Universal Database features multimedia capabilities with image, audio, video, text, spatial and other advanced object relational support. Each new version of DB2 Universal Database builds on the strong foundation of the previous release. With Version 7.2, DB2 Universal Database delivers even more powerful support for business intelligence, data management, and e-business solutions. Strong support is included for added compatibility across the DB2 family. DB2 Installation Prerequisites Before installing DB2, you must ensure that the system meets the hardware and software requirements for DB2. Note The DB2 GUI tools are a set of administration and configuration tools that include the Command Center, Control Center, and the Data Warehouse Center. Additional GUI tools are available on Windows 32-bit and OS/2 operating systems. These include the Client Configuration Assistant, Event Monitor and Event Analyzer. To run a DB2 Run-Time Client or a DB2 Application Development Client, you need a minimum of 16 MB of RAM, and to run a DB2 Administration Client, you require a minimum of 32 MB of RAM. Disk Requirements The fixed disk requirements of any installation depend on the file system and the components that you install. DB2 Servers A typical installation of DB2 Server requires a minimum of 245 MB of disk space. This includes the online product documentation, tools, and the Java Runtime Environment. DB2 Clients Approximate disk space on the client workstations depend on the type of installation and the client Operating Systems. Client Operating Systems Windows 95 or Windows 98 for Client or Personal installation Windows NT or Windows 2000 for Server, Client or Personal installation

3 DB2 offers several options: DB2 Enterprise Edition (DB2EE) DB2EE is a fully enabled RDBMS, scalable from single processors to symmetric multiprocessors and to parallel clusters. This also supports unstructured data such as image, video, text, spatial and audio DB2 Workgroup Edition (DB2WE) Designed for LAN environments, supports both local and remote clients. Also, it can be connected to a network and can participate in distributed environment. DB2WE includes Extenders and Net.data, which allows building Internet ready applications that use DB2 database. DB2 Enterprise-Extended Edition (DB2EEE) This enables DB2 to partition data across clusters and huge parallel computers, as a result it enhances the execution speed as all SQL statements are processed in parallel. The database appears to be on a single computer. DB2 Personal Edition (DB2PE) Enables a single user to create database on the workstation where DB2 is installed. Can be used as remote client to DB2 server. DB2 Satellite Edition (DB2SE) This supports systems that operate disconnected from the central system majority of the time and connect occasionally to the central database to exchange data. DB2 Everyplace (DB2EP) This is a minute database of 100K. Designed for low-cost, lowpower, small devices like Personal Digital Assistants, PDA s and Handheld Personal Computers, HPCs. DB2EP provides a local data store on mobile or embedded device for storing data from any other data source in the enterprise.

4 Installation on Windows 95 or Windows 98 The DB2 products that can be installed on Windows 95 and Windows 98 are: DB2 Universal Database (UDB) Personal Edition Requirements for installing DB2 UDB Personal Edition are: Memory: 128 MB recommended if you plan to use the administration tools Disk Space: approximately 300 MB for a typical install, including the JRE DB2 Connect Personal Edition Requirements for installing DB2 Connect Personal Edition are: Memory: 32 MB Disk Space: approximately 250 MB for a typical install, including the JRE DB2 Clients DB2 clients on Windows 95 or Windows 98 Run-Time Client Requirements for installing the Run-Time Client are: Memory: 16 MB Disk Space: approximately 40 MB Application Development Client Requirements for installing the Application Development Client are: Memory: 16 MB Disk Space: approximately 325 MB, including the JDK Administration Client Requirements for installing the Administration Client are: Memory: 32 MB Disk Space: approximately 250 MB Note: For all the installations given above, the Operating System should be Windows 95 or Windows 98. Tip The Windows 95 version required for the Administration Client installation should be or above.

5 Installation on Windows NT or Windows 2000 The products that you can install on Windows NT Workstation, Windows NT Server, Windows 2000 Professional, Windows 2000 Server or Windows 2000 Advanced Server are: DB2 UDB Personal Edition Requirements for installing DB2 UDB Personal Edition are: Memory: 128 MB recommended if you plan to use the administration tools Disk Space: approximately 300 MB for a typical install, including the JRE DB2 UDB Workgroup Edition Requirements for installing DB2 UDB Workgroup Edition are: Memory: 128 MB recommended if you plan to use the administration tools Disk Space: approximately 400 MB for a typical install, including the JRE DB2 UDB Enterprise Edition Requirements for installing DB2 UDB Enterprise Edition are: Memory: 128 MB recommended if you plan to use the administration tools Disk Space: approximately 420 MB for a typical install, including the JRE DB2 UDB Enterprise-Extended Edition Requirements for installing DB2 UDB Enterprise-Extended Edition are: Memory: 128 MB recommended if you plan to use the administration tools Disk Space: approximately 420 MB for a typical install, including the JRE Note: Supported Protocols:,, IPX/SPX, Named Pipes, Net BIOS, The Windows 9x base operating system provides Net BIOS, IPX/SPX,, and Named Pipes connectivity. IPX/SPX connectivity is only supported to Windows NT and Windows 2000 servers.

6 Installation from the CD-ROM From the DB2 CD-ROM, you may select from the groups: DB2 UDB Enterprise Edition Version 7.2 for Windows OE IBM DB2 Warehouse Manager Version 7.2

7 To start the install process for DB2 UDB v7.2 Enterprise Edition 1. Go to the DB2V72 folder in the root of the CD-ROM 2. Execute SETUP.EXE Figure 1.1 shows the screen invoked on executing SETUP.EXE Click Install to begin the installation of DB2 UDB Enterprise Edition. Figure 1.1, you can view the Installation Prerequisites and the Release Notes, you can take a quick Tour to explore the features, capabilities, and benefits of DB2, or you can proceed directly to the installation.

8 From the next screen, select the products to be installed as shown in Figure 1.2: DB2 Enterprise Edition DB2 Application Development Client DB2 Administration Client Figure 1.2 shows the products available for installation after you click Install. Once you have initiated the installation, proceed by following the setup program s prompts. To invoke the online help, click Help or press F1. You can click Cancel at any time to end the installation. Figure 1.2 shows the products that can be installed

9 From the next screen, select the type of Installation as shown in Figure 1.3: Typical Installation with default values Compact- Basic components and functionality Custom Should have advanced knowledge of DB2. Can select components that have to be installed. Figure 1.3 shows the available types of installation If you select Typical, the following components are installed DB2, Base Warehouse, OLAP Starter Kit. Compact Installation gives the basic database components and client components required to run the database.

10 Figure 1.4 Shows the path of Installation and space required of installation type selected If Custom Setup is selected, list of parent components that can be installed are displayed. To view the subcomponents that is the components within the components, click on subcomponents. The Parent Components are: Communication Protocols Stored Procedure Builder Application Development Interfaces Sample Applications System Bind Files DB2 Query Patroller Client DB2 Connect Server Support Documentation Thin Client Code Server Data Warehousing Tools Data Warehouse ISV Toolkit DB2 OLAP Starter Kit Base DB2 UDB Support Administration and Configuration Tools Getting Started

11 Select the components and sub-components that you need to be install. Figure 1.4 shows the parent components that can be installed during Custom setup You can view at the description of each component. Check the component to be installed and to view the subcomponents within the component click on subcomponents and these can be viewed as seen in Figure 1.5

12 Figure 1.5 Lists of Subcomponents within a component and its description The subcomponents with a gray checkbox cannot be deselected as they are the integral part of component. After the subcomponents are selected click on continue, you are back to Figure 1.4. Clicking on Next shows the Figure 1.6 asking for a confirmation whether a database instance is to be created or not

13 Figure 1.6 shows the creation of Database Instance After confirming the creation of Database Instance, you need to configure the DB2 services. Available Services on DB2 are DB2 Instance (DB2) Administration Server (DB2DAS00) Control Server (DB2CTLSV) The service names given above in parenthesis are configured in Protocols. The service name and the port number is configured when the Protocols button is clicked. These services have default port number as given. DB2 service, the port number is DB2DAS00, the port number service is 523 DB2CTLSV, the port number service is The Startup button configures each services startup attribute. By default, the startup type of all the services is set to automatic.

14 Configuring DB2 Services These are basic services which can be started from Windows NT/2000 services, if configured to manual. Figure 1.7 shows the different services available during creation of Instance The services in figure 1.7 depends on the type of Log on as in the Windows services.

15 Define a Local Warehouse Control Database To define a control database, or to migrate and initialize an existing control database, enter the instance name, the database name, the schema, the username and the password. Figure 1.8 Defining Instance DB2 administrator user name and password are initialized before the creation of database and the confirmation is asked as given in Figure 1.9 below. Figure 1.9 shows the confirmation screen for creation of user account for the database The db2admin user is authorized to start the various services of DB2

16 DB2 Administrator Account On the Primary Domain Controller, PDC, you need to use the User Manager for Domains under Administration tools to create a user account that DB2 will use. For example, db2admin in the Windows 2000 domain db2domain. Create the user account with the privileges required by DB2. If you plan to have more than one DB2 instance on the domain, it is recommended that you create a new group for DB2 users and assign the appropriate DB2 required privileges to the group. Once you create the DB2 group, you can assign each new DB2 instance user account the membership of the DB2 group. Creating a DB2 group will also help if you plan to migrate to DB2 EEE in future. The required Advanced User privileges are: Act as part of the operating system Create a token object Increase quotas Replace process-level token Log on as a service Log on locally Also, you need to assign the logon rights: Be a member of the Local Administrators Group Be known to the local machine

17 Figure 1.10 shows the different databases that can be created with default names These are on-line analytical processing, OLAP databases for both production and development. Figure 1.11 shows the Files that will be copied during installation This displays the type of installation and all the components that are selected for setup.

18 Click on next in Figure 1.11 takes you the Installation screen Figure 1.12 shows the start of Installation All the required files are being copied to the destination folder and the database will be created after setup After the copy procedure is complete, you will see the final screen of DB2 installation. Figure 1.13 shows the final screen of DB2 installation. Setup is complete

19 Installation of DB2 Client on Windows DB2 client provides a runtime environment that is required for DB2 applications to access the database resources. Most of the database administrator tasks can be performed from a DB2 client. You can install one of the three types of DB2 clients: DB2 Run - Time Client Provides a basic application execution environment. DB2 Administration Client provides all the features of DB2 Run Time Client and includes Administration GUI tools, documentation. DB2 Software Developer s Kit provides all the features of Administration Client and also includes libraries, header files and APIs with documentation. During the setup of DB2 Client, by default these components are installed: DB2 Run-Time Client Communication Protocol ODBC Support Java System Bind Files GUI Tools Query Patroller Client Documentation Note: The installation program creates a client instance called DB2.

20 Connecting to the Database Server Applications running on the same machine as the DB2 database or from the remote machines using distributed connection can access the DB2 database You can also use these distributed connections on a client to perform administrative tasks on the database server. Any application or DB2 client using the required protocol connects to the DB2 server as show below in Figure 2.1 Figure 2.1 shows the connection flow from remote client to the database Using different protocols like, IPX/SPX, clients can connect to DB2 servers. Remote clients use a communications product, remote access service, RAS to support the protocol the client uses when accessing a remote database server. You need to install and configure the protocol stack on the client before it can communicate with a server. The supported protocols are: TCI/IP, Net Bios, Named Pipes, IPX/SPX and. Table 2.2 gives all the possible connections between client and server and the different protocols that you can use.

21 Table 2.2 AIX DB2 Servers AIX HP-UX OS/2 SCO UnixWare 7 Solaris Windows NT SCO OpenServer SINIX HP-UX Macintosh OS/2 SCO OpenServer SCO UnixWare 7,(2),(2),(2) NetBIOS, NetBIOS Silicon Graphics IRIX SINIX Solaris Windows 3.x,(2),(2),(2) NetBIOS Local Named Pipes NetBIOS Windows 95 or Windows 98 Windows NT NetBIOS NetBIOS Named Pipes NetBIOS Named Pipes NetBIOS

22 Table Legend: 1 represents Direct Addressing 2 represents File Server Addressing Note: SCO OpenServer and SINIX referred to in Table 2.2 are compatible only with DB2 Version 2.

23 There are several methods to setup communications between a DB2 client and a DB2 server. Configure the communication-specific steps. For example, if you are using, update the services file on the server with the port number that the database server is listening on. Catalog the remote node. Catalog Database, is the database server to which you want to establish the connection. You can establish Connection using: DB2 Discovery This allows you to automate the configuration of clients connecting to the database(s). A discovery message is sent to the DB2 servers, and if the servers are configured to support the discovery process, the data is returned to the client. The returned data gives a list of instances, including name and description for each available database and protocols that DB2 discovery uses. Access Profiles An access profile contains the information that a client needs to catalog database to a DB2 server. Manual Configuration To do this, you need to know the details of the communications setup between the client and the server. There are two ways to manually configure the connection o Manual Option in the Client Configuration Assistant (CCA) A GUI tool that prompts you for all the values o CATALOG NODE/DB commands