Re: Illegal SPL Routine Entry you could try oncheck
or foreach spl you have genereate an update stats for it
eq:
unload to genupstats.sql delimiter ";"
select
"update statistics for routine " || trim (procname)
from sysprocedures;
run genupstats.sql and fingers crossed that it bombs on the problem one
or:
set sqlidebug
Windowze:
set SQLIDEBUG=2:c:\tmp\somefile
run
dbschema -d database -f all
use sqliprint to dump the contens from c:\tmp\somefile
fingers crossed you may find the problem one.
sqliprint comes with clientsdk.
Superboer.
Bill64bits schreef:
> This concerns IDS 9.4 TC2 on Windows 2000.
>
> I have one database that recently stopped exporting views from dbexport and
> there are no error messages. It imports fine, but no views.
>
> Also, I notice that when I do dbschema -d database -f all
> Then dbschema aborts after the last stored proc with:
> **
> Illegal SPL Routine Entry
>
> I don't know if these two things are related, but how would one find out
> what is hosed in the database? |