|
Problem IC63989
|
Status: Geschlossen |
ACTION SCRIPT DOES NOT WORK PROPERLY IF USING TERM CHAR ;(SEMI-COLON). |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problembeschreibung: |
Specified action script with term char ; will fail.
If you execute journal, you can see the sqlcode
"-22220" error.
For example)
The health monitor failed, with sqlcode "-22220", to initiate
an alert action, running "script" "C:\tmp\test.sql" on
system "YOUR_COMPUTER_NAME",
when the Health Indicator "Log Filesyetem Utilization"
("db.log_fs_util")
went into the "Alerm" alert state on "database" "sample". |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* you will see the sqlcode "-22220" error. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See the APAR description. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 UDB version 9.7 fixpack 1. *
**************************************************************** |
| Local-Fix: |
db2set db2options= "-t" |
| verfügbare FixPacks: |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Lösung |
Problem was first fixed in DB2 UDB Version 9.7 FixPack 1. |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 22.10.2009
22.02.2010
22.02.2010 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
9.7.FP1
|
| Problem behoben lt. FixList in der Version |
| 9.7.0.1
|
 |
