home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC84302 Status: Closed

UPDATING INSTANCE FOR USER USING CSH GIVES "AMBIGUOUS OUTPUT
REDIRECT" ERROR

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
When executing db2iupdt for a user instance that runs in csh, we 
get the following output: 
------ 
+ return 0 
+ /usr/bin/chmod ugo+w /db2/db2gbt/sqllib/ctrl/.cleandpf 
+ /opt/IBM/db2/V9.7_2/instance/db2iexec db2gbt 
/db2/db2gbt/sqllib/bin/rah ";/db2/db2gbt/sqllib/adm/db2iclean 
2>&1 
1>/dev/null " 2>&1 1>/dev/null 
Not a terminal 
Not a terminal 
Ambiguous output redirect. 
------ 
 
db2iupdt calls the db2iutil script. 
 
At line 2604 of db2iutil: 
---------------------------------------------------------------- 
${DB2DIR?}/instance/db2iexec ${INSTNAME?} 
"${INSTHOME?}/sqllib/bin/rah 
\";${INSTHOME?}/sqllib/adm/db2iclean 2>&1 1>/dev/null \" 2>&1 
1>/dev/null" 
---------------------------------------------------------------- 
 
At line 83 of db2iexec: 
PROFILE="source ${USERHOME?}/${SQLLIB?}cshrc >& /dev/null; $* " 
 
And at line 87 of db2iexec: 
/usr/bin/su - ${INSTNAME?} -c "${PROFILE?}" 
 
So the "2>&1" syntax is passed as is to a csh session where it 
cannot be parsed.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users using csh                                              * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V10.1 Fixpack 1                               * 
****************************************************************
Local Fix:
Modify "2>&1 1>/dev/null" to ">& /dev/null" at 2604 Line of 
db2iutil file as below. 
 
<Original command> 
${DB2DIR?}/instance/db2iexec ${INSTNAME?} 
"${INSTHOME?}/sqllib/bin/rah 
\";${INSTHOME?}/sqllib/adm/db2iclean 2>&1 1>/dev/null \" 2>&1 
1>/dev/null" 
 
<Modified command> 
${DB2DIR?}/instance/db2iexec ${INSTNAME?} 
"${INSTHOME?}/sqllib/bin/rah 
\";${INSTHOME?}/sqllib/adm/db2iclean 2>&1 1>/dev/null \" >& 
/dev/null"
available fix packs:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
First fixed in DB2 V10.1 Fixpack 1
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
13.06.2012
05.11.2012
05.11.2012
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.1 FixList
10.5.0.1 FixList