I'm getting an unexpected error while trying to run a script in the Command
Center: SQL2001N.
The message says that an interrupt occurred but no one did anything but
launch an unsaved script in the Script pane of the Command Center and wait
for it to finish. Every time the script is launched, SQL2001N happens after
a couple of seconds.
This message would be appropriate if the user was interrupting the script
somehow, maybe with a CTRL- C or something like that, but that isn't
happening here.
Does anyone know of any other reason for this error occur? Can anyone
suggest a resolution?
The environment is DB2 Personal Edition V 8.1.2 on Windows XP.
--
Rhino