VERITAS Database Edition 1.0.2 for DB2 on AIX Release Notes

VERITAS Database Edition™ 1.0.2 for DB2

Release Notes

AIX

April 200330-000956-011

Disclaimer

The information contained in this publication is subject to change without notice. VERITAS Software Corporation makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. VERITAS Software Corporation shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this manual.

VERITAS Copyright

Copyright © 2002-2003 VERITAS Software Corporation. All rights reserved. VERITAS, the VERITAS logo, and all other VERITAS product names and slogans are trademarks or registered trademarks of VERITAS Software Corporation. VERITAS and the VERITAS Logo Reg. U.S. Pat & Tm. Off. Other product names and/or slogans mentioned herein may be trademarks or registered trademarks of their respective companies.

VERITAS Software Corporation350 Ellis St.Mountain View, CA 94043 Phone 650–527–8000 Fax 650–527–2908 www.veritas.com

Data Encryption Standard (DES) Copyright

Copyright © 1990 Dennis Ferguson. All rights reserved.

Commercial use is permitted only if products that are derived from or include this software are made available for purchase and/or use in Canada. Otherwise, redistribution and use in source and binary forms are permitted.

Copyright 1985, 1986, 1987, 1988, 1990 by the Massachusetts Institute of Technology. All rights reserved.

Export of this software from the United States of America may require a specific license from the United States Government. It is the responsibility of any person or organization contemplating export to obtain such a license before exporting.

WITHIN THAT CONSTRAINT, permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of M.I.T. not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. M.I.T. makes no representations about the suitability of this software for any purpose. It is provided “as is” without express or implied warranty.

http://www.veritas.com

Contents
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

The VRTSexplorer Diagnostic Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Downloading VRTSexplorer from the Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Installing VRTSexplorer from the CD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Obtaining a License Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Software Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Obtaining IBM FixPaks for the DB2 UDB Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Component Product Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Installation Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Packaging Changes and Setup Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Upgrade Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Software and Documentation Fixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Known Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Documentation Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Documentation Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Online Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

VERITAS Online Manual Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

VERITAS Database Edition/High Availability Information . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Supported Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

iii

iv Release Notes

Important Release Information

IntroductionThis document provides release information for VERITAS Database Edition for DB2. Read this entire document before you install VERITAS Database Edition.

This Edition has been qualified using DB2 Universal Database (UDB) 7.2 (Enterprise Edition) with FixPak 6 or higher and DB2 UDB 8.1 (Enterprise Server Edition) without the Database Partitioning Feature Support on AIX 5.1 with fileset bos.rte 5.1.0.25 (maintenance level 2) and appropriate APARs, AIX 5.1 with fileset bos.rte 5.1.0.35 (maintenance level 3) and appropriate APARs, and AIX 5.2 with fileset bos.rte 5.2.0.0 and appropriate APARs installed.

Getting HelpFor assistance with any of the VERITAS products, contact VERITAS Technical Support:

◆ U.S. and Canadian Customers: 1-800-342-0652

◆ International: +1-650-527-8555

◆ Email: [email protected]

For license information:

◆ Phone: 1-925-931-2464


◆ Fax: 1-925-931-2487

For software updates:


For additional technical support information, such as TechNotes, product alerts, and hardware compatibility lists, visit the VERITAS Technical Support Web site at:

http://support.veritas.com

1


The VRTSexplorer Diagnostic Program

For additional information about VERITAS and VERITAS products:

◆ Phone: 1-800-258-UNIX (1-800-258-8649) or 1-650-527-8000


◆ Visit the Web site at:


The VRTSexplorer Diagnostic ProgramThe VRTSexplorer program is available to assist VERITAS Customer Support engineers in diagnosing technical problems associated with VERITAS products. You can download this program from the VERITAS FTP site or install it from the VERITAS CD. For more information about the VRTSexplorer program, consult the README file located in the support directory.

Downloading VRTSexplorer from the Web

1. Use a web browser or the ftp program to download the VRTSexplorer program from the following URL:

ftp://ftp.veritas.com/pub/support/vxexplore.tar.Z

Save the file to a temporary directory, such as /tmp, as shown in the example below.

2. Log in as root on the system that is experiencing the problem. Extract the contents of the downloaded file to the directory /tmp/VRTSexplorer:

# cd /tmp# zcat vxexplore.tar.Z | tar xvf -

3. Run the VRTSexplorer program located in the VRTSexplorer directory:

# /tmp/VRTSexplorer/VRTSexplorer

4. When VRTSexplorer prompts for a destination directory for the information that it collects, press Return to accept the default directory /tmp, or enter an alternative path name of your own choice. VRTSexplorer writes the results of its analysis to a compressed tar file named VRTSexplorer_casenumber_hostname.tar.Z in the specified directory.

5. Use the file upload facility of your web browser or the ftp program, to transfer the VRTSexplorer output file to the VERITAS Customer Support anonymous FTP site:

ftp://ftp.veritas.com/incoming

2 VERITAS Database Edition for DB2 Release Notes


ftp://ftp.veritas.com/pub/support/vxexplore.tar.Z


The VRTSexplorer Diagnostic Program

6. Telephone VERITAS Technical Support at the number listed under “Getting Help” on page 1. Tell them that you have run VRTSexplorer and provide the name of the file that you transferred to the FTP site.

Alternatively, if you have already been assigned a call ID number by Customer Support, send email to [email protected] and include your case ID number in the subject line.

Installing VRTSexplorer from the CD

The file VRTSspt.bff is included on the VERITAS CD under the /support directory. To load the software from the CD-ROM:

1. Log in as superuser.

2. Place the VERITAS software CD into a CD-ROM drive connected to your system.

3. After inserting the CD, create a directory:

# mkdir -p /cdrom

4. Mount the directory:

# mount -V cdrfs -o ro /dev/cd0 /cdrom

5. Move to the support directory and install the VRTSspt package:

# cd /cdrom/support# installp -acX -d VRTSspt.bff VRTSspt

6. The program is installed in the /opt/VRTSspt directory. To run the program, enter:

# /opt/VRTSspt/VRTSexplorer/VRTSexplorer

7. Use the file upload facility of your web browser, or the ftp program, to transfer the VRTSexplorer output file to the VERITAS Technical Support anonymous FTP site:


8. Telephone VERITAS Technical Support at the number listed under “Getting Help” on page 1. Tell them that you have run VRTSexplorer and provide the name of the file that you transferred to the FTP site.

Alternatively, if you have already been assigned a call ID number by VERITAS Technical Support, send email to [email protected] and include your case ID number in the subject line.

VERITAS Database Edition for DB2 Release Notes 3


Obtaining a License Key

Obtaining a License KeyIn addition to the traditional License Key Request Form, you can now obtain your license key through the VERITAS vLicense Web site. To use the Web site, you need your customer number, order number, and serial number.

▼ To obtain a license key using the Web site

1. Use a web browser to access the VERITAS vLicense Web site.

http://vlicense.veritas.com

2. Create a new login using your customer number, order number, and serial number.

If you already have an account, you can simply log in.

3. Follow the instructions on the Web site.

You should receive your license key shortly. After receiving your license key, you can install the product.

To obtain your license key using the License Key Request Form, see the VERITAS Database Edition for DB2 Installation Guide.

FeaturesFeatures specific to VERITAS Database Edition for DB2 include new versions of the following component products:

◆ VERITAS File System™ (VxFS) Release 3.4 (fileset level 3.4.4.0)

◆ Quick I/O™ for Databases

◆ VERITAS Volume Manager™ (VxVM®), Release 3.2 (fileset level 3.2.2.0)

◆ Support for the FAStT500, FAStT700 array series. The new version of VERITAS Volume Manager included in this release supports the FAStT500, FAStT700 array series. The RDAC driver (on AIX) will control multipathing to these arrays. VERITAS Volume Manager will therefore see only one path to devices in these arrays even if there are multiple physical paths. The RDAC driver is part of the devices.fcp.disk.array.rte fileset.

◆ VERITAS Enterprise Administrator™ (VEA), Release 3.0.272.0

For details on VERITAS Database Edition features, as well as an overview of the features provided through the component products, see the VERITAS Database Edition for DB2 Database Administrator’s Guide.


http://vlicense.veritas.com

Software Requirements

Software RequirementsVERITAS Database Edition for DB2 can only be installed on a system running AIX 5.1 with fileset bos.rte 5.1.0.25 (maintenance level 2) and appropriate APARs, AIX 5.1 with fileset bos.rte 5.1.0.35 (maintenance level 3) and appropriate APARs, or AIX 5.2 with bos.rte 5.2.0.0 with appropriate APARs. (See “Operating System” on page 7 for more information.) The following table identifies the supported DB2 and AIX combinations for VERITAS Database Edition:

Note For the most up-to-date support matrix, go to http://support.veritas.com and see TechNote 256186 (Support matrix for DBED 1.0.2 for DB2 on AIX).

Software LimitationsThe following are known software limitations in this release of VERITAS Database Edition for DB2.

◆ Converting VxFS files to or from Quick I/O is not currently supported for DB2 7.2 or DB2 8.1 if the DB2 parameters DB2_MMAP_READ and DB2_MMAP_WRITE are set to ON, which is the default setting. Do not attempt to convert VxFS files to or from Quick I/O in this release using the qio_convertdbfiles command.

If the DB2 parameters DB2_MMAP_READ and DB2_MMAP_WRITE are set to ON, DB2 managers will attempt to use the AIX memory map (mmap) function for DMS containers that are type FILE. The DB2 container type is set during creation and cannot be changed at a later time. If users convert a VxFS file to a Quick I/O file, DB2 still reads the container type as FILE. DB2 managers will map the container with the memory map function; however, the memory map function does not work with Quick I/O files, which behave like character devices.

DB2 UDBRelease

AIX fileset bos.rte 5.1.0.25 (maintenance

level 2)

AIX fileset bos.rte 5.1.0.35 (maintenance

level 3)

AIX fileset bos.rte 5.2.0.0

7.2 Enterprise Edition (32- or 64-bit) with FixPak 6 or higher

Yes (32- and 64-bit) Yes (32- and 64-bit) Yes (32- and 64-bit)

8.1 Enterprise Server Edition (32- or 64-bit)

Yes (32- and 64-bit) Yes (32- and 64-bit) Yes (32- and 64-bit)



Obtaining IBM FixPaks for the DB2 UDB Product

◆ APAR IY36125 is currently unavailable. Without this APAR, the system hangs when trying to deinstall the VRTSvxfs package. To work around this problem, log in as root and kill the syncd process as follows:

# ps -ef|grep syncroot 9068 1 0 Jan 28 - 162:04 /usr/sbin/syncd 60# kill -9 9068# nohup /usr/sbin/syncd 60 &

You can now proceed with deinstalling the VRTSvxfs package.

◆ An AIX dynamic reconfiguration (DR) may take longer than expected when VxFS is running under heavy loads. The amount of physical memory and the level of fragmentation are other factors that can delay completion of a DR. Some VxFS operations, such as a file system reorganization (fsadm_vxfs), can take a long time, so it is advisable to complete lengthy VxFS operations before starting a dynamic reconfiguration.

◆ If you create a DB2 database in a Japanese AIX environment and the locale is set to en_US, the VERITAS Database Edition commands will not execute properly. For the commands work properly, you must modify the /opt/VRTSdb2ed/lib/vxdba_db2lib.sh file.

In the /opt/VRTSdb2ed/lib/vxdba_db2lib.sh file, remove the following line:

DEF_JP_DB2CODEPAGE=943

Then, add the following line:

DEF_JP_DB2CODEPAGE=819

Obtaining IBM FixPaks for the DB2 UDB ProductIt is important to have the correct version of DB2 UDB to work with VERITAS Database Edition for DB2. VERITAS Database Edition for DB2 requires DB2 UDB V7.2 with FixPak 6 or higher or DB2 UDB V8.1. IBM maintains DB2 UDB FixPaks for download at the following location:

http://www.ibm.com/cgi-bin/db2www/data/db2/udb/winos2unix/support/download.d2w/report


http://www.ibm.com/cgi-bin/db2www/data/db2/udb/winos2unix/support/download.d2w/report#V7

Component Product Release Notes

Component Product Release NotesIn addition to reading these Release Notes before you install VERITAS Database Edition, it is also important that you read all the component product Release Notes. The component product Release Notes are on the VERITAS Database Edition for DB2 distribution CD in a top-level directory called release_notes.

Because product Release Notes are not installed by any packages, VERITAS recommends that you copy them to the /opt/VRTS/doc directory so that they are available for future reference.

Installation Notes

Operating System

If you are installing VERITAS Database Edition for DB2 on AIX 5.1, the operating system must be AIX 5.1 bos.rte fileset 5.1.0.25 (with maintenance level 2 and appropriate APARs) or bos.rte 5.1.0.35 (maintenance level 3 and appropriate APARs) before installing VERITAS Database Edition. Installing this Edition on previous AIX releases will fail. If necessary, upgrade your AIX operating system before you install the VERITAS products.

If you are installing on AIX 5.2, the operating system must be at AIX 5.2 bos.rte fileset 5.2.0.0 with the appropriate APARs before installing VERITAS Database Edition. If necessary, upgrade your AIX operating system before you install the VERITAS products.

▼ To verify that the AIX 5.1 operating system is at fileset bos.rte 5.1.0.25 or 5.1.0.35

Log in and enter:

# lslpp -l bos.rte

The maintenance level and state of the bos.rte fileset is displayed.

You should see output similar to the following:

Fileset Level State Description ----------------------------------------------------------Path: /usr/lib/objreposbos.rte.install 5.1.0.25 COMMITTED LPP Install Commands

or

Fileset Level State Description ----------------------------------------------------------Path: /usr/lib/objreposbos.rte.install 5.1.0.35 COMMITTED LPP Install Commands


Installation Notes

▼ To verify that the AIX 5.1 operating system is at maintenance level 2 or maintenance level 3

Log in and enter:

# oslevel -r

Your output should show either maintenance level 2 or maintenance level 3:

5100-02

or

5100-03

If the operating system is at base level AIX 5.1 or maintenance level 1, you must upgrade your system to maintenance level 2 with the appropriate APARs or maintenance level 3 with the appropriate APARs.

The maintenance level 2 APARs to install are listed below. The following two must be installed in the order specified:

IY29813

IY29731

Note In order for asynchronous I/O to work properly, you must minimally upgrade the bos.rte.aio fileset to maintenance level 2 (that is, bos.rte.aio fileset version 5.1.0.25). To check the maintenance level, use:

# lslpp -l bos.rte.aiobos.rte.aio 5.1.0.25 COMMITTED Asynchronous I/O Extension

The maintenance level 3 APARs to install are listed below. The following two must be installed in the order specified:

IY30749

IY33705


Installation Notes

▼ To have LVM and VxVM co-exist

On AIX 5.1 bos.rte 5.1.0.25, verify the bos.rte.lvm release level using the following command:

# lslpp -l bos.rte.lvm

You should see:

bos.rte.lvm 5.1.0.25 COMMITTED Logical Volume Manager

Note If the release level of LVM is not correct, upgrade the bos.rte.lvm by applying APAR IY28392 on AIX 5.1 fileset bos.rte version 5.1.0.15.

Note You do not need to verify the bos.rte.lvm level if you are using AIX 5.2.

▼ To verify that the AIX 5.2 operating system is at fileset bos.rte 5.2.0.0

Log in and enter:

# lslpp -l bos.rte

The maintenance level and state of the bos.rte fileset is displayed.

The following output indicates that the bos.rte fileset is at 5.2.0.0:

Fileset Level State Description ----------------------------------------------------------Path: /etc/objreposbos.rte 5.2.0.0 COMMITTED Base Operating System

Runtime

The APARs that must be installed before installing VERITAS Database Edition are below. The following two must be installed in the order specified:

IY36125 (currently unavailable, see “Software Limitations” on page 5 or “Known Issues” on page 15 for more details)

IY37116

▼ To verify that the appropriate AIX 5.1 or 5.2 APARs have been installed

Use the instfix command as follows:

# instfix -ik apar_number


Installation Notes

Verifying Fileset Levels for AIX 5.1

Make sure the following filesets are at the minimum level shown below. The filesets available on your system depend on which OS level is installed in the /unix file. If /unix is symbolically linked to unix_64, the minimum level is:

bos.64bit 5.1.0.25 Base Operating System 64 bit Runtimebos.mp64 5.1.0.30 Base Operating System 64-bit Multiproc Runtime

If /unix is symbolically linked to unix_mp, the minimum level is:

bos.mp 5.1.0.30 Base Operating System Multiprocessor Runtime

If /unix is symbolically linked to unix_up, the minimum level is:

bos.up 5.1.0.30 Base Operating System Uniprocessor Runtime

After upgrading, make sure that each of the following filesets is also at the minimum level shown:

bos.rte.archive 5.1.0.26 Archive Commandsbos.rte.commands 5.1.0.26 Commandsbos.rte.filesystem 5.1.0.25 Filesystem Administration bos.rte.libc 5.1.0.25 libc Library

Verifying Fileset Levels for AIX 5.2

Make sure the following filesets are at the minimum level shown below. The filesets available on your system depend on which OS level is installed in the /unix file. If /unix is symbolically linked to unix_64, the minimum level is:

bos.64bit 5.2.0.0 Base Operating System 64 bit Runtimebos.mp64 5.2.0.0 Base Operating System 64-bit Multiproc Runtime

If /unix is symbolically linked to unix_mp, the minimum level is:

bos.mp 5.2.0.0 Base Operating System Multiprocessor Runtime

If /unix is symbolically linked to unix_up, the minimum level is:

bos.up 5.2.0.0 Base Operating System Uniprocessor Runtime

Make sure that each of the following filesets is also at the minimum level shown:

bos.rte.archive 5.2.0.0 Archive Commandsbos.rte.commands 5.2.0.0 Commandsbos.rte.filesystem 5.2.0.0 Filesystem Administration bos.rte.libc 5.2.0.0 libc Library


Upgrade Notes

Packaging Changes and Setup Requirements

▼ VERITAS Database Edition

◆ VERITAS Database Edition 1.0.2 for DB2 has been internationalized. All of the error and echo messages are located in the message catalog. The current message catalog is English only. In order to retrieve messages properly from the message catalog, two environment variables must be defined prior to running any VERITAS Database Edition for DB2 commands:

◆ LANG=en_US

◆ NLSPATH=/usr/lib/nls/msg/%L/%N:/usr/lib/nls/msg/%L/%N.cat

Upgrade Notes

▼ To upgrade from VERITAS Database Edition 1.0 for DB2 to VERITAS Database Edition 1.0.2

1. Shutdown the DB2 instance(s).

2. Check if any VERITAS File Systems or Storage Checkpoints are mounted:

# mount | grep vxfs

3. Unmount any Storage Checkpoints:

# umount /checkpoint_name

4. Unmount any mounted file systems.

# umount /mount_point

5. Remove all references to volumes by application programs, including shells, that are running on the system. The upgrade process will terminate if any VxVM volumes are in use.

6. If a volume is mounted as a file system, unmount it using the umount command.

# umount /dev/vx/dsk/diskgroup/volume_name

7. If a volume is listed in the /etc/filesystems file, comment it out or remove its entry by editing this file. Refer to your operating system documentation for more information about the format of this file and how you can modify it.


Upgrade Notes

8. Stop all volume activity using the vxvol command.

# vxvol stop volume_name

9. The VERITAS Enterprise Administrator server cannot be active during an upgrade. Before running the installation script, stop the VEA server:

# /opt/VRTSob/bin/vxsvc -k

10. Insert the VERITAS Database Edition software disc into a CD-ROM drive connected to your system.

11. Mount the CD-ROM by entering:

# mkdir /mnt# mount -V cdrfs -o ro /dev/cd0 /mnt

where cd0 is the default address for the CD-ROM drive.

12. Run the installation script to upgrade VERITAS Database Edition:

# /mnt/installDBED

The system prints out a series of status messages as the upgrade progresses and prompts you for any required information, such as the license key. Answer any questions asked of you during the upgrade.

13. Upgrade the operating system from AIX 5.1 to AIX 5.2, if necessary. VxVM identifies the correct version of the AIX operating system and loads the corresponding kernel extension during the upgrade. (During the upgrade, the system will be rebooted.)

Note If VERITAS File System was installed on AIX 5.1, you must run the following command to upgrade VxFS to the AIX 5.2 level after upgrading the operating system: # /etc/methods/vxkextadm upgrade

If VxFS is not upgraded, the VxFS kernel extension cannot be loaded on AIX 5.2 and VxFS file systems fail to mount at system startup. The following error message is displayed during every boot of AIX 5.2 until VxFS is upgraded: Failed to load vxfs kernel extension Run /etc/methods/vxkextadm upgrade

This upgrade is not required if the initial VxFS installation was on an AIX 5.2 system.


Upgrade Notes

14. (Optional) If you used the /etc/methods/vxkextadm upgrade command to upgrade VxFS to the AIX 5.2 level, you can verify that the kernel was loaded using the vxkextadm command as follows:

# /etc/methods/vxkextadm vxfs statusKernel extension /usr/lib/drivers/vxfs.ext_52 is loaded

15. If the install-db file exists, remove the file using the rm command.

# rm -f /etc/vx/reconfig.d/state.d/install-db

16. Reboot the system.

or

Manually restart VxVM.

a. Start the VxVM I/O daemons using the vxiod command.

# vxiod set 10

b. Start the VxVM configuration daemon, vxconfigd, in disabled mode using the vxconfigd command.

# vxconfigd -m disable

c. Initialize vxconfigd using the vxdctl command.

# vxdctl init

d. Initialize the VxVM dynamic multipathing (DMP) subsystem using the vxdctl command.

# vxdctl initdmp

e. Enable vxconfigd using the vxdctl command.

# vxdctl enable

17. Mount any volumes and file systems that were not automounted at reboot. If you previously commented out or removed volumes listed in the /etc/filesystems file, uncomment them or add them back in the file and then mount them.

18. Restart the DB2 instance(s).


Software and Documentation Fixes

Software and Documentation FixesThe following identifies the VERITAS Database Edition for DB2 fixes included in this release:

Incident Description

99695 Previously, the fsadm command failed when a file system was full. This has been fixed.

101685 Previously, if an error occurred while displaying configuration files from the VxDBA Utility, the complete error message did not display and the utility returned you to the “Display Database/VxDBA Information” submenu instead of the “Display VxDBA/Database Configuration Files” submenu.

The error message now displays properly and you are returned to the correct submenu.

102431 Previously, you received an error message after shutting down and then restarting the database using VxDBA if you did not first exit the utility. This has been fixed.

102890 When running the VxDBA Utility as root, the exit option was not behaving properly from the "Start/Stop Monitoring Agent" submenu. This has been fixed.

103348 Previously, when starting a Monitoring Agent from the VxDBA Utility, the generated message indicated the wrong file name:

See log file /var/log/db2ed_mon/dbed_mon.logfile.instance_name for results.

This problem has been fixed. The message now indicates the correct file name:

See log file /var/log/db2ed_mon/db2ed_mon.logfile.instance_name for results.

104152 After saving the configuration information from the VxDBA submenu "Save Volume/File System/Database Configuration", the contents of the database_instance_containers file and the database_instance_container_detail file were identical in the previous release. This has been fixed and the database_instance_containers file now contains brief descriptions and the database_instance_container_detail file contains detailed descriptions.

104247 Previously, if there was an error when using the VxDBA submenu "Save Volume/File System/Database Configuration" to collect configuration information, the user was not notified at the time of collection. The error only showed up in the generated reports. This has been fixed.

104880 You can now use vxinstall, installDBED, or vxlicinst to install a license key.


Known Issues

Known IssuesThe following are known issues in this release:

116220 Previously, when using BASH or CSH as your login shell for DB2, db2ed_mon failed and displayed the following error messages in /var/log/db2ed_mon/db2ed_mon.logfile.instance:

2002/12/27_12:51:24 db2ed_mon smos01 : DBED4429: ERROR: Could not open DB2 monitoring spool file /tmp/.db2spool.smos01.868.

2002/12/27_12:51:24 db2ed_mon smos01 : DBED4430: ERROR: Exit code was Not owner.

2002/12/27_12:51:24 db2ed_mon smos01 : DBED4431: ERROR: Log file for failed operation is located at /tmp/db2spacelog.smos01.868.

This has been fixed in this release.

118164 Previously, when an invalid path was set in the LOGPATH variable using the VxDBA “Configure Monitoring Agent Options” submenu, the monitoring agent exited silently without error. This has been fixed.


103740 Converting VxFS files to or from Quick I/O is not currently supported for DB2 7.2. Do not attempt to convert VxFS files to or from Quick I/O in this release.

103742 Converting VxFS files to or from Quick I/O is not currently supported for DB2 8.1. Do not attempt to convert VxFS files to or from Quick I/O in this release.

105220 Reorganizing a database table fails if tablespaces have been converted to Quick I/O files.

105224 If you convert a tablespace from a Quick I/O file to a regular file after backing up the database, you will not be able to restore the tablespace from that backup unless you re-create the necessary Quick I/O files.

For example, if you take a backup of a database that has a DMS tablespace with Quick I/O files as containers, and later convert the Quick I/O files to regular files, restoring the database from that backup will fail. For the backup to be successful, the DBA has to re-create all necessary Quick I/O files before restarting the backup.


Known Issues

120963 If you use SMIT or installp to upgrade the VRTSvxfs and VRTSvxvm packages (instead of installDBED), you will then need to force the installation of the VRTSvlic package to avoid licensing problems. To force the installation of the VRTSvlic package, do the following:

# mkdir /mnt

# mount -V cdrfs -o ro /dev/cd0 /mnt

# cd /mnt/pkgs/database_edition_for_db2

# installp -acFX -d . VRTSvlic

After forcing the installation of the VRTSvlic package, you may see the following error message if you have updated the VRTSobgui package:

Verifying selections...doneVerifying requisites...installp: Internal error. Unable to resolve conflicts

between base level filesets which are already installed and/or which are on the installation media. Use local problem reporting procedures. (NOTE: This error has not affected the current installation if the two filesets listed here do not appear in subsequent failure messages AND if there are no references to "disabled" filesets in subsequent failure messages.)fileset1: VRTSobgui 3.0.272.0fileset2: VRTSobgui 3.0.255.2

This should not affect the installation of the VRTSvlic package or VRTSobgui package.

Similarly, if you have upgraded the VRTSob package, you may see the following error message:

installp: APPLYING software for:VRTSob 3.0.272.0

Usage: VEAReg.config [-a|-r]

This should not affect the installation of the VRTSob package.

none You must reboot after installing VRTSvxfs 3.4.4.0, if VRTSvxfs 3.4.2.1 or VRTSvxfs 3.4.3.0 is already installed on your system.

none Do not disable Quick I/O on VxFS file systems containing Quick I/O containers of type DEVICE. Doing so causes the tablespace containing them to go offline.

none If you are running VERITAS Database Edition for DB2 in a High Availability (HA) environment and have the VxDBA monitoring agent configured, you will need to restart the agent from VxDBA if a VCS-detected failover occurs.



Documentation Notes

Documentation Notes

Documentation Issues

VERITAS Database Edition for DB2 Installation Guide

◆ Before deinstalling VERITAS Database Edition, you must stop the VERITAS Enterprise Administrator server. The server cannot be active during an upgrade. Before proceeding to Step 4 on page 27 of the VERITAS Database Edition for DB2 Installation Guide (“Deinstalling the VERITAS Database Edition Software”), stop the VERITAS Enterprise Administrator server by issuing the following command:


◆ On page 27 of the VERITAS Database Edition for DB2 Installation Guide, step 4 in the “Deinstalling the VERITAS Database Edition Software” section should read:

Use the installp command to remove the installed VERITAS Database Edition for DB2 software packages. Remove the packages in the order shown:

# installp -u VRTSdb2doc VRTSvmman VRTSfsdoc VRTSvmdoc \VRTSfspro VRTSvmpro VRTSobgui VRTSvxfs VRTSvxvm \VRTSvlic VRTSdb2ed# installp -u VRTSob

none Before deinstalling VERITAS Database Edition, you must stop the VERITAS Enterprise Administrator server. The server cannot be active during an upgrade. To stop the VERITAS Enterprise Administrator server, issue the following command:


none APAR IY36125 is currently unavailable. Without this APAR, the system hangs when trying to deinstall the VRTSvxfs package. To work around this problem, log in as root and kill the syncd process as follows:

# ps -ef|grep sync

root 9068 1 0 Jan 28 - 162:04 /usr/sbin/syncd 60

# kill -9 9068

# nohup /usr/sbin/syncd 60 &

You can now proceed with deinstalling the VRTSvxfs package.



Documentation Notes

Note Most packages in the VERITAS Database Edition product have kernel components. In order to ensure complete removal, a system reboot is recommended after all packages have been removed.

◆ If the system hangs when deinstalling the VRTSvxfs package, go to “Software Limitations” on page 5 and read the information pertaining to APAR 36125, which is currently not available.

◆ On page 33 of the VERITAS Database Edition for DB2 Installation Guide, step 2 in the “Starting VERITAS Enterprise Administrator Server” section should read:

Start the VEA server:

# /opt/VRTSob/bin/vxsvc

No output will appear after you enter the command. Please disregard the output that is shown in the guide.

Online Documentation

The following VERITAS Database Edition for DB2 documents are provided on the VERITAS Database Edition CD in Adobe Portable Document Format (PDF) format:

◆ VERITAS Database Edition for DB2 Installation Guide

◆ VERITAS Database Edition for DB2 Database Administrator’s Guide

These documents are installed under the /opt/VRTSdb2doc directory. See the VERITAS Database Edition for DB2 Installation Guide for specific package installation information.

VERITAS Volume Manager and VERITAS File System documentation is also supplied on the VERITAS Database Edition CD. See “Component Product Release Notes” on page 7 for more details.

VERITAS Online Manual Pages

The VERITAS online manual page source files were created in troff/nroff format. The source files are not readable using the man command unless the bos.txt.tfs fileset is installed. VERITAS product packages also install ASCII versions of the manual pages in the /opt/VRTS/man/catman* directories that are readable without the bos.txt.tfs fileset.

Please note that there is no vxdba(1M) online manual page included with this release. This manual page will be added in a future release. Also note that the db2ed(7) online manual page is listed in section 7 of the UNIX system manual even though it is not a “miscellaneous command.”


VERITAS Database Edition/High Availability Information

VERITAS Database Edition/High Availability InformationVERITAS Database Edition/HA (VCS) for DB2 is a separately licensed product available for database administrators with high availability needs. In addition to the VERITAS products included in the base VERITAS Database Edition for DB2, VERITAS Database Edition/HA (VCS) for DB2 incorporates the following product:

◆ VERITAS Cluster ServerTM (VCS) 3.5 (fileset level 3.5.0.0 or higher)

◆ VERITAS Cluster ServerTM (VCS) Enterprise Agent for DB2 UDB

Note It is recommended that you always install the latest product patches, if applicable.

Supported Software

◆ AIX 5.1 with fileset bos.rte 5.1.0.25 or 5.1.0.35

◆ AIX 5.2 with fileset bos.rte 5.2.0.0

◆ VERITAS Volume Manager™ (VxVM®) 3.2 (fileset level 3.2.2.0 or later)

◆ VERITAS File System™ (VxFS™) 3.4 (fileset level 3.4.4.0 or later)


VERITAS Database Edition/High Availability Information


Date post:	07-May-2015
Category:	Documents
Upload:	tess98
View:	571 times
Download:	6 times

VERITAS Database Edition 1.0.2 for DB2 on AIX Release Notes

Documents