Conclusion

Summary

So that's the story on server management in DB2 9. This tutorial introduced you to the basic knowledge and skills of managing DB2 servers. Every server has one or more DB2 instances. An instance provides a logical environment in which DB2 commands and functions can execute. You learned how to create, drop, start, stop, list, migrate, and update instances. The DB2 environment plays an important role in influencing how DB2 behaves. It is made up of the operating system environment settings, DB2 profile registries, database manager, and database configuration parameters. They can be easily configured with commands as illustrated in the tutorial.

You learned three methods of configuring DB2 client and server connectivity. You can search the network with DB2 discovery, use DB2 access profiles, or specify communication information manually. The Configuration Assistant is available to use any of the methods to set up the node and database catalog directories. With proper connectivity configuration, you can attach to an instance to perform remote administration tasks and connect to a database for data access.

Managing a DB2 server also includes managing its access. DB2 security is composed of authentication and authorization. Authentication is performed externally by a security facility. There are different authentication types that allow you to control where authentication should take place. Once a user is authenticated, DB2 will check to make sure the user is allowed to perform the requested operations. Different levels of authorities and privileges are available to support granular security control.

You were also introduced to task creation and automation. Use the Task Center to create tasks that are coded in DB2 commands, OS commands, or MVS shell commands. The tool has options to enter instructions for notification purposes, and to specify other tasks to perform upon completion.

The DB2 administration notification log records errors and warnings raised by DB2, the Health Monitor, and user applications. Each event log entry contains information such as timestamp, database name, application ID, DB2 function and component that raise the message. This is definitely a good place to start in troubleshooting errors encountered in DB2.

Part 2, which discusses the creation of DB2 databases, as well as the various methods used for placing and storing objects within a database, provides an understanding of system calls, teaches you how to make your own modules, and, finally, shows you how to create, apply, and submit patches.

To keep an eye on this series, bookmark the series page DB2 9 DBA certification (Exam 731) preparation tutorials.

8 of 10 | Previous | Next

Comments

Back to top

Table of contents

• Before you start
• DB2 instances
• DB2 client/server connectivity
• DB2 security
• Scheduling jobs
• Using notification logs
• Installing and configuring DB2
• Conclusion
• Resources
• About the author

---

8 of 10 | Previous | Next

Next steps from IBM

• Try: DB2 Enterprise
• Demo: Create an electronic form solution with DB2 pureXML and Lotus Forms
• Community: DB2
• Buy: DB2 Enterprise

Dig deeper into Information Management on developerWorks

Try IBM PureSystems. No charge.

Experience today!

---

Get started with the cloud-based trial and pattern development kit.