Unicenter Fast Unload for Oracle Version 4.2.0
2.0 Operating System Support
2.1 Agent Platforms Supported
2.2 Client Platforms Supported
2.3 Oracle Versions Supported
2.4 Supported Oracle Objects
2.5 Platform-Specific Information
3.0 System Requirements
4.0 Installation Considerations
5.0 General Considerations
5.1 Fixed Issues
5.2 Known Issues
5.3 Uninstall Issues
5.4 Known Oracle Bugs
6.0 Unicenter Database Management Common Services 2.5.0
6.1 System Requirements
6.2 Installation Considerations for Sybase and Oracle Agents
6.3 Limitations Affecting Unicenter Database Management Repository Configuration
6.4 Platform Patch Requirements
6.5 Unicenter Database Management Console - Known Technical Problems
6.6 Job Administration Service (JAS)
6.7 Uninstalling Repository Tables on NT
6.8 Disabling Unicenter Enterprise DBA File Transfer Service
6.9 Unicenter WorldView Support
7.0 Contacting Technical Support
Before you start using this version of Unicenter Fast Unload, review these notes for important additional information to help you with your implementation of Fast Unload.
Solaris 2.6, 2.7, 2.8, 2.9
AIX 4.3.3, 5L (5.1) (32 & 64 bit)
HP 9000/800, 700:
HP/UX 11.0 & 11i (11.11) (32 & 64 bit)
Tru64 4.0e, 4.0f, 4.0g, 5.0, 5.1
Intel (or compatible) Windows NT 4.0 SP6a
Windows 2000 SP3
Windows XP Professional SP1
Note: Install all required patches listed in the Oracle documentation for your operating system on the hosts where you install the Unicenter Fast Unload agent.
Microsoft Windows NT 4.0 SP6a
Microsoft Windows 2000 SP3
Microsoft Windows 98 SE
Microsoft Windows XP Professional SP1
The following Oracle objects are supported in Unicenter Fast Unload 4.2.0: Heap, clustered, and index-organized tables Partitioned and sub-partitioned tables Tables with up to 1000 columns Object tables Built-in column data types: BFILE, BLOB, CHAR, CLOB, DATE, INTERVAL, LONG, LONG RAW, NCHAR, NCLOB, NUMBER, NVARCHAR2, RAW, REF, ROWID, TIMESTAMP, and VARCHAR2 LOB and VARRAY data types in partitioned index-organized tables Tables containing Media, Spatial, URITYPE, and XMLTYPE data types User-defined column data types: object columns, nested table columns Subtypes and NOT FINAL object types Materialized views or snapshots
Fast Unload uses ORACLE_SID to connect to the instance. Starting with Oracle8i, the ORACLE_SID environment variable may not be set automatically during installation. To ensure the value of ORACLE_SID, you must either: Define the ORACLE_SID environment variable, or
Set the Fast Unload ORACLE_SID control file parameters.
Note: Do not set the ORACLE_HOME environment variable.
Fast Unload 4.1 required that the kernel extensions for Oracle 8i or 9i be installed on the system. Fast Unload 4.2 does NOT have that requirement.
Fast Unload 4.2 cannot perform character set conversations when unloading from Oracle 8.0.
Fast Unload requirements are: RAM: 64MB Disk space: 45MB (plus space required by Unicenter Database Management components)
Users running Fast Unload must have read privilege for all Oracle data files associated with all tables being unloaded.
The Fast Unload non-DBA package must be installed to allow non-DBA users to unload tables. See the "Unicenter Fast Unload for Oracle Administrator Guide" for details on installing this package.
Additionally, non-DBA users must have the Oracle EXP_FULL_DATABASE role enabled in order to unload using the DIRECT_EXPORT output format.
When upgrading from ManageIT Fast Unload for Oracle 2.4 to Unicenter Fast Unload for Oracle 4.2, Computer Associates recommends that you uninstall Version 2.4 before or after upgrading. By default, Version 4.2 installs in a different directory than Version 2.4.
Note: Uninstalling Version 2.4 is not required, but it may not run correctly once you have installed Version 4.2.
Call format = <StarTrak Number/Problem Number>:<Short Description>
Fixed Unicenter Fast Unload Issues
ST 12030054: ERROR MESSAGE DISPLAYED BY FUT
Fast Unload emits an error message when the national character set is JA16SJISFIXED.
ST 12030102: -w OPTION
Fast Unload emits an error when the -w command line flag is used without any other parameters.
ST 12030104: DELIMITER CAN'T USE CORRECTLY
Fast Unload incorrectly trims trailing spaces from the DELIMITER parameter when the parameter is enclosed in quotation marks.
ST 12030108: ENCLOSURE INCORRECT OPERATION
Fast Unload should not allow the ENCLOSURE value to contain the letters A-F or numbers 0-9 when BINARY OFF is specified.
ST 12030110: CHARACTER TRANSFORMED IN LOGS
Fast Unload is outputting multi-byte user name and table name as hexadecimal characters.
ST 12030135: JA16SJISFIXED
Fast Unload emits an error message when the national character set is JA16SJISFIXED.
ST 12030143: FASTUNLOAD CORE DUMPED
Fast Unload core dumps when the -f option is greater than 129 bytes.
ST 12030145: FASTUNLOAD CORE DUMPED
Fast Unload core dumps when the log file name is greater than 129 bytes.
ST 12030149: FASTUNLOAD CORE DUMPED
Fast Unload core dumps when a query is given and a literal string (enclosed in single quotation marks) is given instead of a column name in the column list.
ST 12030150: FASTUNLOAD CANNOT UNLOAD
Fast Unload fails to unload rows matching a WHERE clause when DBCS characters are in a LIKE operation.
ST 12030152: CANNOT USE -L OPTION
Fast Unload fails without error message when the -L option is greater than 128 bytes.
ST 12030155: CANNOT USE -Q OPTION
Fast Unload fails without error message when the -Q option is greater than 128 bytes.
ST 12030157: CANNOT USE -z OPTION
Fast Unload fails without error message when the -z option is greater than 128 bytes.
ST 12270823: COL.NAME IN SJIS: 5C IN HEX
Fast Unload strips bytes with hex value 5C (backslash in US7ASCII) from column names in SQL*Loader control file. However, 5C is a valid trailing byte in some SJIS characters.
ST 12716963: PROBLEMS ON MULTIPLE ORACLE
Fast Unload fails with error 2428 (error calling OCIHandleAlloc) if you attempt to unload data from a Windows machine with multiple Oracle versions installed.
ST 12770341: QUERY PROBLEM
When you unload a table with materialized views (or snapshots) that have the same name as the table but different owners, the Fast Unload 4.2 Beta returns the error "ORA-01422: exact fetch returns more than requested number of rows."
ST 12790324: MISSING DATA WITH PART IOT
Fast Unload 4.2 Beta unloads the first column incorrectly as NULL on a little-endian machine if the National Character Set is AL16UTF16 and the last column of the table is NCHAR or NVARCHAR.
PR#153: LOGIN WITH USER "IDENTIFIED EXTERNALLY"
In previous versions of FUO, it was possible to supply a blank user ID and password (for example, "-u /") to take advantage of Oracle's "IDENTIFIED EXTERNALLY" functionality (part of the "CREATE USER" command). In version 4.x however, the product verifies that the user has entered a non-blank user ID and password, which effectively disables access to Oracle's external user verification.
PR#155: BAD VARRAY DATE CONVERSION
In certain situations, the HOUR portion of VARRAY DATE/TIME columns may be corrupted on output.
PR#158: ORA-904 IN NON-DBA PARTITION QUERY
A missing column in the non-DBA view "fuo_apps_partition_objs" causes ORA-00904: "Invalid column name" error during selection of this view by the unloader.
PR#160: PARTITION UNLOAD WITHOUT LOCK
When Fast Unload for Oracle attempts to acquire a lock on a partition, a bug in the lock retry code causes FUO to assume that the lock has been acquired when in fact it has not. As a result, FUO processes the partition as if a lock had been acquired, omitting any uncommitted changes from the output file.
PR#161: NLS DECIMAL POINT NOT USED
Fast Unload for Oracle outputs a "." as the decimal point character, regardless of the NLS setting for this value.
PR#164: ORA-00942 (ORACLE 9I O7_DICTIONARY_ACCESSIBILITY)
While performing an unload against an Oracle9i instance with a user who has been granted the DBA role, but who does not have access to the SYS views (O7_DICTIONARY_ACCESSIBILITY initialization parameter), Fast
Unload for Oracle generates error "2428: oexfet - ORA-00942: table or view does not exist".
PR#165: ATTEMPT TO DELETE SPECIAL FILES
If an empty output file is created (for example, due to unloading a table containing zero rows), FUO deletes the empty file without checking first to make sure the file is a "regular" file (that is, not a pipe or other type of special file).
PR#166: INVALID CHARACTERS IN NUMBER OUTPUT
In certain situations, Oracle may zero one or more of the internal bytes of a number column causing Fast Unload for Oracle to place the characters ":1" into the output stream.
PR#168: CORE DUMP OVERWRITING END OF BUFFER
A buffer overrun in a message output function causes FUO to core dump with signal 11.
PR#169: ORA-235 SELECTING V_$DATAFILE
During periods of high Oracle server activity, FUO may receive ORA-235 errors when it attempts to select data file names from sys.v_$datafile, even though a timed retry loop is in place to trap for this error and to retry the select statement. The time limit for this loop has been increased from 60 to 180 seconds.
PR#170: INVALID CLIENT CHARACTER SET (US7ASCII)
Fast Unload for Oracle reports "Error (3875): Invalid client character set." when "US7ASCII" has been selected for the NLS NCHAR character set, and this setting differs from the selected client character set. Since "US7ASCII" is a subset of all other character sets, this error should not be emitted.
PR#171: EXPANDING FIXED FORMAT OUTPUT
When Fast Unload for Oracle creates FIXED format output, it must take into account possible output field expansion due to conversion between character sets. For example, a varchar(10) containing data encoded in a single-byte character set would need to be converted to a varchar(30) if the client character set is UTF8. However, FUO does not always handle such expansions correctly, sometimes expanding columns when such expansion is not necessary.
PR#172: INVALID CLIENT CHARACTER SET (JA16SJISFIXED)
Fast Unload for Oracle reports "Error (3875): Invalid client character set." when "JA16SJISFIXED" has been selected for the NLS NCHAR character set, and the client character set is "JA16SJIS". Since "JA16SJISFIXED" is a subset of "JA16SJIS", this error should not be emitted.
PR#173: LOGIN WITH USER "IDENTIFIED EXTERNALLY" - PART 2
Further modifications were performed in support of problem #153 (described above).
PR#174: "SELECT LIKE" DOESN'T WORK WITH MULTI-BYTE CHARACTER SETS
When the SELECT statement is used with the LIKE keyword against a multi-byte character set, Fast Unload may not retrieve any rows even though rows exist which meet the selection criteria.
PR#175: POSSIBLE SQL*LOADER ERROR ORA-01461
When Fast Unload for Oracle outputs LONG RAW columns in SQL*Loader CONVENTIONAL mode, "sqlldr" may generate error ORA-01461: "can bind a LONG value only for insert into a LONG column" during a load of the
output data whenever any of these LONG RAW columns exceed 2000 bytes in length (1000 bytes for Oracle versions less than 8.0). This behavior is due to limitations within SQL*Loader, and this modification identifies the potential problem with a warning message.
PR#176: BACKSLASHES REMOVED FROM COLUMN NAMES
Fast Unload for Oracle removes backslash characters from column names written to the SQL*Loader control file, causing SQL*Loader to generate error ORA-00904: "Invalid column name" during the load.
PR#177: SELECT AGAINST MULTI-BYTE DATA RETURNS NO ROWS
When a 'SELECT' query is performed against multi-byte character data, Fast Unload for Oracle may not return any rows even though rows that meet the selection criteria actually do exist in the table.
PR#178: PACKED NUMBER OUTPUT INCORRECT
FUO may output additional, invalid data bytes while processing NUMBER type columns with a precision of one (1) in PACKED format.
PR#180: ERROR 2428 WITH DATE FILTER QUERY
When a DATE column is used in an FUO SQL query, FUO will terminate with error 2428, "oexfet - ORA-01405: fetched column value is NULL", "select to_date('','<date_format>') from dual."
PR#181: DIRECT_EXPORT CORE DUMPS ON >2GB OUTPUT FILES
When Fast Unload for Oracle is run in DIRECT_EXPORT format and any output file exceeds 2GB in size, signal 11 with a core dump is generated if FUO attempts to re-open and determine the size of the output file prior to adding the export file trailer.
PR#183: LARGE STRINGS IN FUO CONTROL FILE CAUSE ERRORS
When a large (> 2K) string is encountered within the FUO control file (for example, a PACKED or DIRECTORIES statement with multiple continuation lines), an internal buffer is overflowed causing various errors, possibly including a core dump.
PR#184: ERROR 3475 WITH CERTAIN MULTI-BYTE TABLE NAMES
If any of the bytes of a multi-byte table name represent any of the lowercase characters of the US7ASCII character set (for example, a table named "x83x62" or a single Japanese SJIS character with a second byte that looks like the letter "b" in US7ASCII), FUO generates error 3475 when it attempts to verify that the table name does not contain any lowercase characters.
For the latest information on known problems, go to the Support website at https://Support.ca.com.
In Windows, Unicenter Fast Unload adds the install path and other entries to your user PATH variable. The Unicenter Fast Unload uninstall script does not remove any of these entries.
We recommend that you remove these entries manually when you uninstall Unicenter Fast Unload. If you do not remove the entries, your PATH variable can reach its maximum character limit and may truncate.
Oracle has identified the following bugs that may affect reloading data into your database. Check with Oracle on the availability of a patch.
Bug# 1730290 : If you select SJIS as the database character set on Oracle 8i or 9i on Windows 2000, Fast Unload for Oracle or SQL*Loader may fail due to character mapping problems in the Microsoft Windows code pages. Fast Unload for Oracle error 3317 or SQL*Loader error ORA-00904 will occur if certain characters are present in the data being unloaded, or in an object name (for example, a table name). The following Oracle patches address the problem:
Oracle 8.1.6: PSR 18.104.22.168.8 or above.
Oracle 8.1.7: Oracle 22.214.171.124 and PSR 126.96.36.199.10.
Oracle 9i: Latest available Oracle 9i patch.
See http://www.microsoft.com/JAPAN/support/kb/articles/JP286/7/76.asp for further information.
Bug# 1900166: When SQL*Loader encounters a row containing a NULL REF value that matches the NULLIF clause, SQL*Loader will sometimes core dump.
Bug# 1900970: SQL*Loader fails to load the parent table data when it contains a nested table inside column object. It yields the "ORA-00932: inconsistent datatypes" error.
Bug# 2217233: SQL*Loader fails with "ORA-03113 end of communication channel" if two adjacent rows have NULL XML data. The workaround is to use DIRECT=TRUE on the SQL*Loader command line.
Bug# 2690646: When importing a table with a column of INTERVAL YEAR(0) TO MONTH, Oracle import fails with the following errors: IMP-00003: ORACLE error 30088 encountered and ORA-30088: datetime/interval precision is out of range.
Bug# 2712114: SQL*Loader may not load VARRAY data in Oracle 9.2 if the VARRAY is within an object column.
Bug# 2716317: SQL*Loader aborts with an internal error (SQL*Loader-702: Internal error - ulpvdcnv:ulpvdidtx) if the table has a VARRAY of TIMESTAMPs.
Oracle does not provide any indication that a replacement character was used if converting from a database character set (other than US7ASCII) to the US7ASCII client character set. Therefore, Unicenter Fast Unload cannot emit a replacement character warning message in this situation.
The Unicenter Database Management Common Services components disk space requirements are:
|Component ||Windows ||Solaris ||AIX ||HPUX ||DEC OSF |
|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 |
If you install the Agent on the same Windows NT or Windows 2000 machine as the Unicenter Database Management Repository, you must configure the Unicenter Database Management Repository to start automatically on reboot.
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. The following options on the Configuration Wizard, Repository Access - Choose a Database Type dialog are not enabled for this release: DB2 UDB for z/OS and OS/390 via EDBC (UNIX only) Ingres
These requirements are in addition to requirements stated elsewhere in this document.
On Win32 platforms, the standard Microsoft ODBC administration, Driver Manager, Cursor Library and standard ODBC Trace library must also be installed, Version 3.510.3002.23 (as seen in the About dialog for the ODBC Data Source Administrator) or higher. Note that these Microsoft ODBC products are part of standard Windows installations.
The original edition of Windows 98 does not install the ODBC Driver Manager. The Windows 98 Second Edition installs the correct ODBC components. If you are running Window 98, the Second Edition is required.
Note: NT 4.0 CDs install version 3.02 of Microsoft ODBC software, which will not work with these drivers. As of 03/20/2001, the ODBC Install checks for the Microsoft ODBC Driver Manager support level, and will issue a warning dialog with an opportunity to abort if that support is not at least 3.51.
Microsoft has bundled their ODBC administration, ODBC Driver Manager and related software into their "Microsoft Data Access Components" (MDAC) package. As of 03/21/2001, the current MDAC GA version for all Win32 platforms is "MDAC 188.8.131.5202.3 (GA)". This can be found at:
Look at Microsoft Universal Data Access - Free Downloads in the "MDAC 2.1 SP2" section. Click on the "Read the MDAC 2.1 release details" in that section, and then click Download MDAC 184.108.40.20602.3 (GA) to download the "MDAC 220.127.116.1102.3 (GA)" install.
AIX 4.x Requirements
Unicenter Database Management products require a minimum AIX full maintenance level of 18.104.22.168. Use the "oslevel" command to verify your current operating system version.
If you are connecting to Oracle 8.1.7 servers you need to have a minimum full maintenance level of 4.3.3.09.
The C++ run time library level on your system must be 22.214.171.124 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
/bin/lslpp -l | grep xlC.rte
which displays something similar to
xlC.rte 126.96.36.199 COMMITTED C Set ++ Runtime
The software state in Column 3 can be APPLIED as well as COMMITTED. Anything other state will cause a problem.
If the version number in Column 2 is less than 188.8.131.52, you must apply an IBM patch. AIX Patch ID U463496 installs the 184.108.40.206 version.
The CAI/PT ODBC Unix install scripts enforce that the C++ run time library level is 220.127.116.11 or greater. If not, CAI/PT ODBC will not install.
Compaq Tru64 UNIX Requirements
The message "undefined symbol __cxx_call_static_dtors" in the middle of the ODBC part of the install, occurs if the version of libcxx on your machine is outdated. Unicenter Database Management uses the latest Compaq C++ compilers. However, in version 6.2 of Compaq's 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 Compaq's 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."
Install the latest libcxx patch/update available from Compaq at:
You will need version 6.2 of libcxx or newer. According to Compaq's documentation, version 4.0F ships with this library by default, but older versions of Tru64 UNIX do not.
Oracle 8 on HPUX Requirements
If you are running an Oracle 8.0.x client on HPUX and connecting to Oracle 8i (8.1.x) servers you will need to have a minimum patch level of 18.104.22.168.0.
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 command UPDATE DBM CFG USING CATALOG_NOAUTH YES at the client or the gateway to correct the problem.
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, use the IBM DB2 Control Center to set communications options by doing the following:
From the Start Menu, select IBM DB2, Control Center. From the Control Center window, expand the icons in the explorer tree to show the instance you want to discover. Right-click the instance and select Setup communications from the popup menu. With the TCP/IP option selected, click on the associated Properties button. From the Configure TCP/IP - DB2 dialog, click Default to populate the Service name and Port number fields. Click OK to exit the dialogs. 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.
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 11 client libraries.
PROBLEM: Unable to access objects containing single quotes as part of the owner or object name.
SOLUTION: None. Currently this is not supported within the scope of the Unicenter Database Management Console.
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).
Unicenter Database Management Common Services do 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.
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 CA Unicenter Database Management Common Services:
WARNING! The command should only be run if you are uninstalling all Unicenter Database Management components from any system using this repository.
When installing on a machine that has a prior installation of Unicenter Enterprise DBA 5.2.0, the following message may 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:
Open the Windows Services window. Look for "Unicenter Enterprise DBA File Transfer" service. If it exists, stop the service. Change the startup type for that service to "Disabled".
The Unicenter Database Management database tools provide integration to the Unicenter WorldView for launching the Unicenter Database Management Database Console. The Unicenter Database Management tools are supported for use with:
Unicenter TNG 2.4
Unicenter TNG Framework 2.4.1
Unicenter Common Services 3.0 (bundled with Unicenter NSM 3.0 and other products)
For further technical assistance with this product, contact Technical Support at https://support.ca.com for a complete list of locations and phone numbers. Technical Support is available 24 hours a day, 7 days a week.