Unicenter Fast Unload r11 for DB2 UDB for Linux Unix Windows - CA Technologies
{{search ? 'Close':'Search'}}

Unicenter Fast Unload r11
for DB2 UDB for Linux, Unix, Windows

1.0 Welcome

2.0 Operating System Support
2.1 Agent Platforms Supported
2.2 Client Platforms Supported
2.3 DB2 UDB Versions Supported

3.0 Portal Requirements

4.0 System Requirements
4.1 RAM
4.2 Disk Space

5.0 Known Issues
5.1 Server Discovery
5.2 Uninstall

6.0 Unicenter Database Management Common Services
6.1 System Requirements
6.2 Installation Considerations
6.3 Post-Installation Server Setup
6.4 Limitations Affecting Unicenter Database Management Repository Configuration
6.5 Platform Requirements
6.6 Known Issues
6.7 Using Oracle 10g as a Database Management Repository (DMR)
6.8 Job Administration Service (JAS)
6.9 Setting Administrator Privileges for Job Administration Service (JAS)
6.10 ODBC Configuration on AIX
6.11 Uninstalling Repository Tables in a Windows Environment
6.12 Disabling File Transfer Service
6.13 Unicenter WorldView Support

7.0 Documentation

8.0 International Support

9.0 Contacting Technical Support


1.0 Welcome

Welcome to Unicenter Fast Unload for DB2 UDB for Linux, UNIX, Windows (Unicenter Fast Unload). Before you start using this release of Unicenter Fast Unload, you should review these notes for important additional information to help you with your implementation of Unicenter Fast Unload.


2.0 Operating System Support


2.1 Agent Platforms Supported

Sun SPARC

Solaris 2.7, 2.8, 2.9 (32- & 64-bit)

IBM RS/6000

5L (5.1, 5.2) (32- and 64-bit)

HP 9000/800, 700

HP-UX 11.0 & 11i (11.11) (32- and 64-bit)

Intel x86 or compatible

RedHat Linux AS 2.1 (kernel version 2.4.21) & 3.0

Windows 2000 Service Pack 4

Windows XP Professional Service Pack 2

Windows 2003 Server

z/Series

SuSE Linux SLES8


2.2 Client Platforms Supported

Microsoft Internet Explorer 6.0


2.3 DB2 UDB Versions Supported

IBM DB2 Universal Database 8.1.6 and 8.2.0


3.0 Portal Requirements

Microsoft

Windows 2000 Service Pack 4

Windows XP Professional Service Pack 2

Windows 2003

Sun SPARC

Solaris 2.7, 2.8, 2.9 (32- and 64-bit)


4.0 System Requirements

The following RAM and disk space requirements must be met or exceeded for Unicenter Fast Unload to install and run correctly.


4.1 RAM

On Windows:

128 MB for agent (server) machines, 512 MB+ recommended

    1 GB for the UDM Portal machine

On UNIX/Linux:

256 MB for agent (server) machines, 1 GB+ recommended

    1 GB for the UDM Portal machine


4.2 Disk Space

Agent Install:

AIX Sun HP-UX Linux Windows
175 MB 100 MB 175 MB 100 MB 180 MB

Portal Install (Web Server):

1.5GB

The values specified for disk space are the minimum values required to install the product.

Note: The system requirements for Unicenter Fast Unload include the system requirements for Unicenter Database Management Common Services components. For specific information about these components, see the System Requirements section under Unicenter Database Management Common Services.


5.0 Known Issues

To download the latest patch, or to view the latest information on known problems, go to the Technical Support web site at http://ca.com/about/support.htm.

5.1 Server Discovery

When using the Server Discovery feature from the portal's Configuration Tools some fields (specifically SID), for Oracle servers 9.0 and above, may not be populated. Manually edit the servers and enter the missing information.


5.2 Uninstall

During Uninstall of the application, the following entries are not removed from your PATH:

  • C:Program FilesCACleverPath Portaljakarta-tomcat-3.3awebappsdbmWEB-INFbin
  • C:Program FilesCASharedComponentspecbin
  • C:Program FilesCASharedComponentsUnicenterDatabaseManagementbin
  • C:Program FilesCAUnicenterFastUnloadUDBbin

To remove these entries manually:

  1. Right-click My Computer and select Properties.
    The System Properties dialog window opens.
  2. Click the Advanced tab.
  3. Click the Environment Variables button.
    This will open the Environment Variables dialog.
  4. Modify the Path entry in the System variables section. To do this:
  5. Scroll to and select the Path entry within the table
  6. Click the Edit... button.
  7. The Edit System Variable dialog opens where you can
    remove the leftover entries.
  8. Click Ok on the Edit System Variable dialog.
  9. Click Ok on the Environment Variables dialog.
  10. Click Ok on the System Properties dialog.

6.0 Unicenter Database Management Common Services

The following sections contain system requirements, installation considerations and known issues for Unicenter Database Management Common Services.


6.1 System Requirements

The Unicenter Database Management Common Services components disk space requirements are:

Component Windows Solaris AIX HPUX Tru64 UNIX
Common Services 52 MB 15 MB 51 MB 21 MB 45 MB
PEC 6 MB 14 MB 51 MB 14 MB 13 MB
ODBC 5 MB 52 MB 49 MB 62 MB 19 MB


6.2 Installation Considerations

If you install the Agent on the same Windows machine as the Unicenter Database Management Repository, you must configure the Unicenter Database Management Repository to start automatically on reboot. See the "Agent Platforms Supported" section for supported Windows platforms.


6.3 Post-Installation Server Setup

After installing a new release of the Unicenter Database Management Console, you must run Server Setup on all servers you want to access.

After performing a database discovery (see the Getting Started), select a server icon in the DBMS Explorer portion of the Unicenter Database Management Console. Select Server, Server Setup from the main menu or right-click the server icon and select Server Setup from the popup menu. Follow the prompts in the DB Setup Wizard to add stored procedures and other required objects to the selected server.

Note: Server Setup is not required on DB2 UDB for z/OS and DB2 UDB for UNIX/Windows.


6.4 Limitations Affecting Unicenter Database Management Repository Configuration

  • The Oracle 9.2 client is not certified to connect to Oracle 7.3 databases (see Oracle Document ID 172179.1). Therefore, we recommend that you do not create the Unicenter Database Management Repository on Oracle 7.3. To avoid compatibility issues, create your repository on the latest available Oracle version.
  • If the tablespace containing the Unicenter Database Management Repository is created on an Oracle 9.0 server ensure the tablespace is created with SEGMENT SPACE MANAGEMENT set to MANUAL. Tables in the repository contain LOB columns, and Oracle 9.0 does not support tables with
    LOB columns in a tablespace with automatic segment space management.
  • The following options are not enabled for this release on the Configuration Wizard, Repository Access - Choose a Database Type dialog.
    • Ingres

    6.5 Platform Requirements

    These requirements are in addition to requirements stated elsewhere in this document.


    Solaris Requirements

    Unicenter Database Management products require the libCstd.so library that may not be included in all Solaris installs. To obtain the libCstd.so library, download the Solaris patch released in June 2003 or later.


    The Ingres user must be in both the /etc/passwd and /etc/shadow files, or it must not be in either file.


    AIX Requirements

    Unicenter Database Management products require a minimum AIX full maintenance level of 4.3.3.0. Use the oslevel command to verify your current operating system version.


    If you are connecting to Oracle 8.1.7 servers, you must have a minimum full maintenance level of 4.3.3.09.


    The C++ run time library level on your system must be 4.0.2.0 or greater. If the C++ run time library level is less than that, the ODBC driver libraries cannot be dynamically loaded. An ldd run on any one of them will show a Symbol <symbol> is not defined error message, where<symbol> will contain the characters Exception. For example:

      ldd ./ptor813s.so   exec(): 0509-036 Cannot load program ./ptor813s.so because of the   following errors:   0509-023 Symbol __setUncaughtExceptionFlag__3stdFb in   /opt/ca/caiptodbc/lib/libptbas13.a is not defined.

    You can determine the C++ run time library level with the following:

     /bin/lslpp -l | grep xlC.rte

    This displays in columns similar to the following:

     xlC.rte 4.0.2.0 COMMITTED C Set ++ Runtime

    The software state in Column 3 can be APPLIED as well as COMMITTED. Any other state will cause a problem.

    If the version number in Column 2 is less than 4.0.2.0, you must apply an IBM patch. AIX Patch ID U463496 installs the 4.0.2.0 version.

    The CAI/PT ODBC UNIX install scripts enforce that the C++ run time library level is 4.0.2.0 or greater. If not, CAI/PT ODBC will not install.


    Hewlett Packard Tru64 UNIX Requirements

    The following message occurs in the middle of the ODBC part of the install if the version of libcxx on your machine is outdated:

     undefined symbol __cxx_call_static_dtors

    Unicenter Database Management uses the latest C++ compilers. However, in version 6.2 of the native C++ compiler, a bug fix regarding destruction of objects on unloading DLL from an application required an update to libc. To quote from the C++ compiler release notes:

    "The compilation system and run-time library now call destructors that are defined in shared images which have been closed correctly using dlclose(), with the linker option -depth_ring_search. This feature requires that a new libcxx be installed on your system with Version 6.2. Otherwise, the compiler reports the undefined symbol __cxx_call_static_dtors."

    If your version of libcxx is lower than 6.2, install the latest libcxx patch/update available at:

    ftp://ftp.compaq.com/pub/products/C-CXX/tru64/cxx

    According to HP's documentation, version 4.0F ships with this library by default, but older versions of Tru64 UNIX do not.


    6.6 Known Issues

    This section describes known issues, workarounds, and/or solutions for Unicenter Database Management Common Services.

    Problem: When you click on an Oracle instance within the Unicenter Database Management Console, the name of the Connected As user may not display properly in a Japanese windows environment.

    Solution: Select a supported Japanese font for the Unicenter Database Management Console. From the console toolbar select Options, Preferences, Application Preferences, change Font. From the Font drop-down list select the font that supports Japanese. Click Apply and Ok. From the DBMS Explorer, click on the instance from the tree browser to update the view.

    Problem: Products that are certified for Japanese language may not display locale characters properly during the server setup process. This has no effect on the server setup or configuration.

    Solution: After the Server Setup process is completed, verify that all objects are created properly. A message will display indicating that the status is successful or has failed.

    Problem: The Oracle8 ODBC drivers cannot connect to Oracle7 from an Oracle10g client.

    Solution: Look for the following:

    C:Program FilesCASharedComponentsUnicenterDatabaseManagementcfgmanageit.cfg

    Change ORACLE CAI/PT ORACLE 8 to ORACLE CAI/PT ORACLE 7.

    Problem: If you change the host name manually, the Database Management Console might modify the SQL.INI file for your Sybase database. Registry settings might also be changed for Microsoft SQL-Server or Informix, if you modify server configuration information outside of the Unicenter Database Management Console application.

    Solution: Always use the Console Server options to add or configure servers you will manage using Unicenter Database Management Common Services.

    Problem: On DB2 UDB, the connect operation fails to retrieve port information required for alias cataloging if you are not logged in as db2admin.

    Solution: If you are using LDAP support, ensure that you or the DB2 Connect gateway can perform the CATALOG DATABASE, NODE, and DCS DATABASE commands.

    Invoke the following command at the client or gateway to correct the problem:

     UPDATE DBM CFG USING CATALOG_NOAUTH YES

    Problem: When connecting to a local instance of DB2 UDB, the DB2INSTANCE environment variable must be set to the name of the local instance. Otherwise, you will not be able to connect and in some cases the Database Management Console may unexpectedly terminate.

    Solution: Set DB2INSTANCE to the name of the local instance.

    Problem: The Database Management Console fails to discover DB2 UDB instances due to a problem with the TCP/IP protocol.

    Solution: Before running Auto Discovery, perform the following steps using the IBM DB2 Control Center to set communications options:

    1. From the Start Menu, select IBM DB2, Control Center.
    2. From the Control Center window, expand the icons in the explorer tree to show the instance you want to discover.
    3. Right-click the instance and select Setup communications from the popup menu.
    4. With the TCP/IP option selected, click on the associated Properties button.
    5. From the Configure TCP/IP - DB2 dialog, click Default to populate the Service name and Port number fields.
    6. Click OK to exit the dialogs.
    7. Restart the instance.

    Problem: The application fails to start with no errors.

    Solution: Try adding the following to the DBADESK.INI file in your windows directory.

       [Desktop DBA]    AllowOneEXE=0

    Problem: When connecting to a Sybase server using Version 10 of the client libraries, users will experience a fault when disconnecting from the server after using the Query Wizard component.

    Solution: Install and configure the Version 11client libraries.

    Problem: If Unicenter Database Console is connected to an Oracle 8i instance that has o7_dictionary_accessibility=false, then the user will have difficulties installing the necessary database objects required by the Database Console.

    Solution: Run the following GRANT statements replacing user_name with the owner of the objects installed by the Unicenter Database Console. Additionally, this SQL should be run for each user attempting to use the Unicenter Database Console.

      ======================================================================   GRANT SELECT ON "SYS"."OBJ$"                       TO user_name;   ---------------------------------------------- -----------------------   GRANT SELECT ON "SYS"."TAB$"                       TO user_name;   ---------------------------------------------- -----------------------   GRANT SELECT ON "SYS"."USER$"                      TO user_name;   ---------------------------------------------- -----------------------   GRANT SELECT ON "SYS"."COL$"                       TO user_name;   ---------------------------------------------- -----------------------   GRANT SELECT ON "SYS"."ATTRCOL$"                   TO user_name;   ---------------------------------------------- -----------------------   GRANT SELECT ON "SYS"."COLTYPE$"                   TO user_name;   ---------------------------------------------- -----------------------   GRANT SELECT ON "SYS"."HIST_HEAD$"                 TO user_name;   ---------------------------------------------- -----------------------   GRANT SELECT ON "SYS"."COM$"                       TO user_name;   ---------------------------------------------- -----------------------   GRANT SELECT ON "SYS"."CDEF$"                      TO user_name;   ---------------------------------------------- -----------------------   GRANT SELECT ON "SYS"."CON$"                       TO user_name;   ---------------------------------------------- -----------------------   GRANT SELECT ON "SYS"."COM$"                       TO user_name;   ---------------------------------------------- -----------------------   GRANT SELECT ON "SYS"."MLOG$"                      TO user_name;   ---------------------------------------------- -----------------------   GRANT SELECT ON "SYS"."SLOG$"                      TO user_name;   ---------------------------------------------- -----------------------   GRANT ALL ON "SYS"."DBA_ALL_TABLES";               TO user_name;   ======================================================================

    Problem: Due to an Oracle error, Unicenter Database Management applications can receive the following error on Oracle 8.1.7 on Windows 2000:

    TNS-12640 Authentication adapter initialization failed.

    Solution: This can be remedied by one of the following steps:

    • Apply Oracle patch 1522966 to your server. Contact Oracle support to obtain this patch.
    • Go to Control Panel, Administrative Tools, Services. Change the "Unicenter Database Management Job Administration Service" to log on as a domain authenticated user (rather than the local system account).
    • Edit SQLNet.ora and change
      sqlnet.authentication_services = (NTS) to
      sqlnet.authentication_services = (NONE).

    Problem: Text does not display beneath the Toolbar icons.

    Solution: Ensure that you select the Add text to buttons option in the Configure Toolbar Dialog. If you select this option and the text does not display beneath the toolbar icons, close and reopen the application.

    Problem: Attempting to access objects containing single quotes as part of the owner or object name causes SQL errors.

    Solution: Objects of this type are currently not supported within the scope of the Unicenter Database Management Console.

    Problem: When you right click the mouse, a menu with the Find or Change option displays in the SQL Scripts window. This may cause the Find or Change Dialog to display outside of the view area.

    Solution: After selecting the Find or Change option, press and hold the Alt key, then press the space bar. The system menu for the dialog should appear with the move and close options. Select move and move the dialog into view.

    Problem: The DBMS Explorer is not always refreshed when creating or dropping objects.

    Solution: Click the Refresh button on the main toolbar after creating or dropping objects.

    Problem: When opening multiple DBMS Explorer windows to navigate and perform Unicenter DBA functions, the object presented in a selected dialog may not be the last object selected. Therefore the action performed may be on an undesired object.

    Solution: When multiple DBMS Explorer windows are present, verify that the database, schema and object displayed in any dialog are as expected.


    6.7 Using Oracle 10g as a Database Management Repository (DMR)

    If you want to use Oracle10g as the DMR and your machine has a combination of older and newer Unicenter Database Management products installed, you must upgrade all the older Unicenter Database Management products to the most recent release.

    When using the Configuration Wizard to reconfigure the DMR, and all Unicenter Database Management products currently installed are Oracle 10g enabled, you will be asked if you are planning to use Oracle 10g as a repository with any of the Unicenter Database Management products installed on the machine.

    Select one of the following:

    Yes--Use Oracle10g as the DMR.

    No--Use earlier versions of Oracle as the DMR.

    Note: To upgrade to an Oracle10g DMR in the future, you must rerun the Configuration Wizard.


    6.8 Job Administration Service (JAS)

    Unicenter Database Management Common Services does not support LANG=C. There may be other character sets that are not yet supported. If the specified character set is not supported by Unicenter Database Management Common Services or not installed on the UNIX Server, the JAS agent (mitjasag) process terminates with "MITJAS_AGENT-0027" and "ODBC-Error = 2012" error message in the $MANAGEIT_HOME/log/mitjasag.log file.

    The character set is set by exporting LANG=<character_set>. If you encounter the referenced JAS agent failure, please try setting LANG to the default character set on your UNIX system, first. If the specified character set does not work, try setting LANG=en_US. You can find the list of character sets that are installed on your UNIX server by executing the "locale -a" command. Please set LANG before the udminit.sh or manageitinit.sh line in the .profile.


    6.9 Setting Administrator Privileges for Job Administration Service (JAS)

    The JAS agent is used to run database level commands. On a DB2 UDB database, commands fail because JAS is using the local SYSTEM account. The SYSTEM account does not have proper permissions to access the local DB2 catalog.

    From the Windows Control Panel select Administrative Tools, Services, and right-click on the Unicenter Database Management Job Administration Service entry. From the menu choose properties and select the Log On Tab. Change JAS to use a local or domain user with administrator privileges.


    6.10 ODBC Configuration on AIX

    If ODBC is installed while the $SYBASE environment variable is set to a Sybase 12.0 instance, ODBC creates links to Sybase 12.0 libraries. If Sybase is upgraded to Sybase 12.5 or multiple versions of Sybase exist on the same machine, a library incompatibility is created when trying to load different versions of Sybase libraries.

    Run CONFIG.SH to redefine the proper $SYBASE directory followed by sourcing the new resulting obdcemv.sh or odbcemv.csh with the override option (-a). For example, specify the following to use the proper Sybase driver with a Sybase 12.5 client installation:

    • odbcemv.sh -a

    6.11 Uninstalling Repository Tables in a Windows Environment

    If you have a Windows only environment, the standard Unicenter Database Management uninstall does not remove the Unicenter Database Management Repository tables.

    To remove them, run the following command before you uninstall the Unicenter Database Management Common Services:

     %MANAGEIT_HOME%binMitDeleteRepo.exe

    WARNING! The command should only be run if you are uninstalling all Unicenter Database Management components from any system using this repository.


    6.12 Disabling File Transfer Service

    When installing on a machine that already has the products installed, the following message can display:

    The Enterprise Communicator components appear to be in use...

    If this message displays, you will be prompted to abort installation and perform the following steps before installing or upgrading any of the Unicenter Database Management products:

    1. Open the Windows Services window.
    2. Look for File Transfer service. If it exists, stop the service.
    3. Change the startup type for that service to Disabled.

    6.13 Unicenter WorldView Support

    The Unicenter Database Management database tools provide integration to Unicenter WorldView for launching the Unicenter Database Management Console. The Unicenter Database Management tools are supported for use with Unicenter Common Services 3.0 (bundled with Unicenter NSM 3.0.1 and 3.1.0).

    WARNING! DB2 UDB databases that are discovered using the DB Console will not synchronize to the Unicenter NSM 3.0 Business Process View.


    7.0 Documentation

    Each PDF guide in a documentation set has a unique Document ID (DID) that appears on the title page of the guide. The DID uses the first six characters to identify the guide, a hyphen, then two characters at the end to identify the edition and language in which it is written. For example, J00218-1E identifies the first edition of the English version of the Unicenter Fast Unload for DB2 UDB for Linux, UNIX, Windows Administrator Guide. When the second edition of this guide is published, the DID is incremented to J00218-2E. The DID is used without the hyphen for the .PDF file on the product media and on SupportOnline as shown in File Name column of the following table.

    The DIDs and file names for this product's guides are:

    Guide Name DID File Name
    Unicenter Fast Unload for DB2
    UDB for Linux, UNIX, Windows
    Administrator Guide
    J00218-1E J002181E.PDF
    Unicenter Fast Unload for DB2
    UDB for Linux, UNIX, Windows
    Getting Started
    J00219-1E J002191E.PDF
    Unicenter Fast Unload for DB2
    UDB for Linux, UNIX, Windows
    Release Summary
    J00220-1E J002201E.PDF
    Unicenter Database Management
    Common Services Administrator
    Guide
    J00264-1E J002641E.PDF

    The DID for this readme file appears under the readme title; the same DID without the hyphen is used for the readme file name on SupportOnline.


    8.0 International Support

    An internationalized product is an English product that runs correctly on local language versions of the required operating system and required third-party products, and supports local language data for input and output. Internationalized products also support the ability to specify local language conventions for date, time, currency and number formats.

    A translated product (sometimes referred to as a localized product) is an internationalized product that includes local language support for the product's user interface, online help and other documentation, as well as local language default settings for date, time, currency, and number formats.

    In addition to the English release of this product, Computer Associates supports only those languages listed in the following table.

    Language Internationalized Translated
    Brazilian Portuguese Yes No
    Chinese (Simplified) Yes No
    Chinese (Traditional) Yes No
    French Yes No
    German Yes No
    Italian Yes No
    Japanese Yes No
    Korean Yes No
    Spanish Yes No

    Note: If you run the product in a language environment not listed in the table, you may experience problems.

    Localized characters in product install paths are not supported.

    Localized characters in object or schema names are only supported when the character set of the database matches the character set of the operating system.


    9.0 Contacting Technical Support

    For online assistance and a complete list of locations and phone numbers, contact Customer Support at http://ca.com. Customer support is available 24 hours a day, 7 days a week.

    For telephone assistance, call:

    U.S. and Canada 1-800-645-3042

    International (1) 631-342-4683

    Chat with CA

    Just give us some brief information and we'll connect you to the right CA Expert.

    Our hours of availability are 8AM - 5PM CST.

    All Fields Required

    connecting

    We're matching your request.

    Unfortunately, we can't connect you to an agent. If you are not automatically redirected please click here.

    • {{message.agentProfile.name}} will be helping you today.

      View Profile


    • Transfered to {{message.agentProfile.name}}

      {{message.agentProfile.name}} joined the conversation

      {{message.agentProfile.name}} left the conversation

    • Your chat with {{$storage.chatSession.messages[$index - 1].agentProfile.name}} has ended.
      Thank you for your interest in CA.


      How Did We Do?
      Let us know how we did so that we can maintain a quality experience.

      Take Our Survey >

      Rate Your Chat Experience.

      {{chat.statusMsg}}

    agent is typing