Cannot drop database in IDS 11.50.FC4 (again)

The thread of my original posting with a legitimate question was subsequently fouled by profanity-laden replies and removed from the newsgroup. So I am again posting my first and the only relevant, useful reply (thank you, Richard) in an attempt to find a solution to this problem (which may be related to Automated Update Statistics running in the background): red_valsen@yahoo.com schrieb: > We recently upgraded to IDS 11.50.FC4 from 9.40 on HPUX 11.23 and are > experiencing sharp teething pains. We have scripts which run during > off hours to reload test and development databases by shutting down > appservers to drop all connections, then drop the target DB. Then > dbimport/myimport is used to load. Now after all connections have > been dropped we get 425/107 errors when the script attempts to execute > 'drop database'. Examining the database when this occurs we find no > connections reported by onstat, and queries vs. system catalog tables > show only empty lock-related tables. Call to IBM tech support > indicates this problem was reported and solved with XC4, with > workaround to shutdown scheduler (execute function admin("scheduler > shutdown")) immediately prior to drop and re-start immediately > afterwards. This works but we'd like to avoid editing our scripts, > and besides, this bug was reported fixed in this version (maybe > platform-specific idiosyncracy?). > > We've not been able to reproduce the state that induces the error -- a > database can easily be created immediately and dropped in the > afflicted instance. What else can we check? Anyone understand what's > causing this behavior? Hi, if 'scheduler' is the new dbScheduler, then I have this in the output of onstat -m 03:22:19 On-Line Mode 03:22:20 SCHAPI: "INFORMIXDIR/etc/sysadmin/stop" file is present. Bypassing dbScheduler and dbWorker threads startup. As I did not understand what the sysadmin database is good for, the first thing for me to do was to deactivate it until I test what happens when I gonna drop it altogether. Some searching brought how to avoid having dbScheduler and dbWorker active: create a file with the name 'stop' touch $INFORMIXDIR/etc/sysadmin/stop Then bounce the server onmode -ky && oninit -v Maybe worth a try... dic_k P.S.: remarks: Yes, I did read SQL syntax V11 docs, pg 6-5 ff. and no, I am not on MS Windows or Vista, and if so I'd have cygwin running including X Windows (to use onperf) and to have cron and at. -- Richard Kofler SOLID STATE EDV Dienstleistungen GmbH Vienna/Austria/Europe