dbimport schema has changed

This question concerns IBM Informix Dynamic Server Version 12.10.TC1IE running on Windows Server 2008R2 . The dbexport utility has started writing about 1500 of lines that were not there before. These are near the top of the schema file. What could have caused this? How do I get the old behavior back? create opaque type "informix".sysbldsqltext ( internallength=variable, maxlen=24000, alignment=1 ); grant usage on type "informix".sysbldsqltext to 'public' as "informix"; create row type "informix".bts_fsestoragerow ( sto_name lvarchar, num_buckets integer, bucket_num integer, bucket blob ); grant usage on type "informix".bts_fsestoragerow to 'public' as "informix"; create implicit cast (lvarchar as sysbldsqltext with "informix".sysbldsqltextin); create explicit cast (sysbldsqltext as lvarchar with "informix".sysbldsqltextout); create explicit cast (sysbldsqltext as sendrecv with "informix".sysbldsqltextsend); create implicit cast (sendrecv as sysbldsqltext with "informix".sysbldsqltextrecv); create implicit cast (impexp as sysbldsqltext with "informix".sysbldsqltextimpt); create explicit cast (sysbldsqltext as impexp with "informix".sysbldsqltextexpt); create implicit cast (impexpbin as sysbldsqltext with "informix".sysbldsqltextimpb); create explicit cast (sysbldsqltext as impexpbin with "informix".sysbldsqltextexpb); create function "informix".sysbldsqltextin (lvarchar) returns SYSBldSQLText external name '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldSQLTextIn)' language c; -- etc, etc... -- ====== at the end it has this... insert into informix.systracemsgs values ('BTSF9', 338, 'en_us.8859-1', NULL,'bts error - there is no snowball stemmer language specified after the period'); insert into informix.systracemsgs values ('BTSG0', 339, 'en_us.8859-1', NULL,'bts error - there is no snowball stemmer language support for the $DB_LOCALE setting: %PARAM1%'); insert into informix.systracemsgs values ('BTSG1', 340, 'en_us.8859-1', NULL,'bts error - there is no snowball stemmer language support for the specified language: %PARAM1%'); insert into informix.systracemsgs values ('BTSG2', 341, 'en_us.8859-1', NULL,'bts error - internal index length %PARAM1% is too long. The maximum is %PARAM2%'); insert into informix.systracemsgs values ('BTSG3', 342, 'en_us.8859-1', NULL,'bts error - bts_lock_setup: cannot get virtual processor lock pointer'); insert into informix.systracemsgs values ('BTSG4', 343, 'en_us.8859-1', NULL,'bts error - bts_lock_setup: virtual processor is not locked'); insert into informix.systracemsgs values ('BTSG5', 344, 'en_us.8859-1', NULL,'bts error - bts_lock_setup: virtual processor is not locked by the current transaction'); insert into informix.systracemsgs values ('BTSG6', 345, 'en_us.8859-1', NULL,'bts error - not (-) operator cannot be specified in thesaurus'); insert into informix.systracemsgs values ('BTSG7', 346, 'en_us.8859-1', NULL,'bts error - and (+) operator cannot be specified in thesaurus'); insert into informix.systracemsgs values ('BTSG8', 347, 'en_us.8859-1', NULL,'bts error - cannot determine index owner of thesaurus index %PARAM1%'); insert into informix.systracemsgs values ('BTSG9', 348, 'en_us.8859-1', NULL,'bts error - cannot lock thesaurus index %PARAM1%'); insert into informix.systracemsgs values ('BTSH0', 349, 'en_us.8859-1', NULL,'bts error - cannot read thesaurus index parameters for %PARAM1%'); insert into informix.systracemsgs values ('BTSH1', 350, 'en_us.8859-1', NULL,'bts error - the index %PARAM1% does not have the thesaurus parameter set'); insert into informix.systracemsgs values ('BTSH2', 351, 'en_us.8859-1', NULL,'bts error - thesaurus index cannot be fragmented'); insert into informix.systracemsgs values ('BTSH3', 352, 'en_us.8859-1', NULL,'bts error - invalid term found in thesaurus. Only word terms can be specified'); insert into informix.systracemsgs values ('BTSH4', 353, 'en_us.8859-1', NULL,'bts error - the %PARAM1% attribute must be specified'); insert into informix.systracemsgs values ('BTSH5', 354, 'en_us.8859-1', NULL,'bts error - the text or file attribute must be specified'); insert into informix.systracemsgs values ('BTSH6', 355, 'en_us.8859-1', NULL,'bts error - the copy_temp attribute can only be specified on an index in an sbspace'); insert into informix.systracemsgs values ('BTSH7', 356, 'en_us.8859-1', NULL,'bts error - the field is not in the document'); insert into informix.systracemsgs values ('BTSH8', 357, 'en_us.8859-1', NULL,'bts error - the directory cannot contain a bts index'); insert into informix.systracemsgs values ('BTSH9', 358, 'en_us.8859-1', NULL,'bts error - the ID is out of bounds'); insert into informix.systracemsgs values ('BTSI0', 359, 'en_us.8859-1', NULL,'bts error - must be a DBSA to use parameter %PARAM1%'); insert into informix.systraceclasses values ('blademgr', 1); insert into informix.systraceclasses values ('bts', 2);

These are related to using any Basic Text Search (BTS) features in this database. Using any BTS function or creating a BTS based index will create several tables and many stored routines that are part of the BTS Datablade. This is what dbexport/dbschema is including in the export. You can use the --no-blade-procs option to myschema to eliminate the stored procedures belonging to that database, but the tables and data types created by its installation are too hard for myschema to identify. Myschema will generate a script compatible with dbimport if you also add the -l option. Art Art S. Kagel, President and Principal Consultant ASK Database Management www.askdbmgt.com Blog: http://informix-myview.blogspot.com/ Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on the IIUG, nor any other organization with which I am associated either explicitly, implicitly, or by inference. Neither do those opinions reflect those of other individuals affiliated with any entity with which I am affiliated nor those of the entities themselves. On Sun, May 17, 2015 at 1:18 PM, BillHatVerizon <garage_dba@verizon.net> wrote: > This question concerns IBM Informix Dynamic Server Version 12.10.TC1IE > running > on Windows Server 2008R2 . > > The dbexport utility has started writing about 1500 of lines that were not > there before. > These are near the top of the schema file. > What could have caused this? How do I get the old behavior back? > > create opaque type "informix".sysbldsqltext > > ( > > internallength=variable, > > maxlen=24000, > > alignment=1 > > ); > > grant usage on type "informix".sysbldsqltext to 'public' as "informix";> > create row type "informix".bts_fsestoragerow > > ( > > sto_name lvarchar, > > num_buckets integer, > > bucket_num integer, > > bucket blob > > ); > grant usage on type "informix".bts_fsestoragerow to 'public' as "informix";> > create implicit cast (lvarchar as sysbldsqltext with > "informix".sysbldsqltextin); > > create explicit cast (sysbldsqltext as lvarchar with > "informix".sysbldsqltextout); > > create explicit cast (sysbldsqltext as sendrecv with > "informix".sysbldsqltextsend); > > create implicit cast (sendrecv as sysbldsqltext with > "informix".sysbldsqltextrecv); > > create implicit cast (impexp as sysbldsqltext with > "informix".sysbldsqltextimpt); > > create explicit cast (sysbldsqltext as impexp with > "informix".sysbldsqltextexpt); > > create implicit cast (impexpbin as sysbldsqltext with > "informix".sysbldsqltextimpb); > > create explicit cast (sysbldsqltext as impexpbin with > "informix".sysbldsqltextexpb); > > create function "informix".sysbldsqltextin (lvarchar) > returns SYSBldSQLText > external name '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldSQLTextIn)' > language c; > > -- etc, etc... > -- ====== at the end it has this... > insert into informix.systracemsgs values ('BTSF9', 338, 'en_us.8859-1', > NULL,> 'bts error - there is no snowball stemmer language specified after the > period'); > insert into informix.systracemsgs values ('BTSG0', 339, 'en_us.8859-1', > NULL,> 'bts error - there is no snowball stemmer language support for the > $DB_LOCALE > setting: %PARAM1%'); > insert into informix.systracemsgs values ('BTSG1', 340, 'en_us.8859-1', > NULL,> 'bts error - there is no snowball stemmer language support for the > specified > language: %PARAM1%'); > insert into informix.systracemsgs values ('BTSG2', 341, 'en_us.8859-1', > NULL,> 'bts error - internal index length %PARAM1% is too long. The maximum is > %PARAM2%'); > insert into informix.systracemsgs values ('BTSG3', 342, 'en_us.8859-1', > NULL,> 'bts error - bts_lock_setup: cannot get virtual processor lock pointer'); > insert into informix.systracemsgs values ('BTSG4', 343, 'en_us.8859-1', > NULL,> 'bts error - bts_lock_setup: virtual processor is not locked'); > insert into informix.systracemsgs values ('BTSG5', 344, 'en_us.8859-1', > NULL,> 'bts error - bts_lock_setup: virtual processor is not locked by the current > transaction'); > insert into informix.systracemsgs values ('BTSG6', 345, 'en_us.8859-1', > NULL,> 'bts error - not (-) operator cannot be specified in thesaurus'); > insert into informix.systracemsgs values ('BTSG7', 346, 'en_us.8859-1', > NULL,> 'bts error - and (+) operator cannot be specified in thesaurus'); > insert into informix.systracemsgs values ('BTSG8', 347, 'en_us.8859-1', > NULL,> 'bts error - cannot determine index owner of thesaurus index %PARAM1%'); > insert into informix.systracemsgs values ('BTSG9', 348, 'en_us.8859-1', > NULL,> 'bts error - cannot lock thesaurus index %PARAM1%'); > insert into informix.systracemsgs values ('BTSH0', 349, 'en_us.8859-1', > NULL,> 'bts error - cannot read thesaurus index parameters for %PARAM1%'); > insert into informix.systracemsgs values ('BTSH1', 350, 'en_us.8859-1', > NULL,> 'bts error - the index %PARAM1% does not have the thesaurus parameter > set'); > insert into informix.systracemsgs values ('BTSH2', 351, 'en_us.8859-1', > NULL,> 'bts error - thesaurus index cannot be fragmented'); > insert into informix.systracemsgs values ('BTSH3', 352, 'en_us.8859-1', > NULL,> 'bts error - invalid term found in thesaurus. Only word terms can be > specified'); > insert into informix.systracemsgs values ('BTSH4', 353, 'en_us.8859-1', > NULL,> 'bts error - the %PARAM1% attribute must be specified'); > insert into informix.systracemsgs values ('BTSH5', 354, 'en_us.8859-1', > NULL,> 'bts error - the text or file attribute must be specified'); > insert into informix.systracemsgs values ('BTSH6', 355, 'en_us.8859-1', > NULL,> 'bts error - the copy_temp attribute can only be specified on an index in > an > sbspace'); > insert into informix.systracemsgs values ('BTSH7', 356, 'en_us.8859-1', > NULL,> 'bts error - the field is not in the document'); > insert into informix.systracemsgs values ('BTSH8', 357, 'en_us.8859-1', > NULL,> 'bts error - the directory cannot contain a bts index'); > insert into informix.systracemsgs values ('BTSH9', 358, 'en_us.8859-1', > NULL,> 'bts error - the ID is out of bounds'); > insert into informix.systracemsgs values ('BTSI0', 359, 'en_us.8859-1', > NULL,> 'bts error - must be a DBSA to use parameter %PARAM1%'); > insert into informix.systraceclasses values ('blademgr', 1); > insert into informix.systraceclasses values ('bts', 2);> > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --047d7bd76aea6bd40e05164a7094

We have never intentionally used any BTS feature or created such an index. Maybe there was a typo someplace last week. How could I find out where the datablade is that caused this ? -----Original Message----- From: Art Kagel Sent: Sunday, May 17, 2015 12:30 PM To: ids@iiug.org Subject: Re: dbimport schema has changed [35110] These are related to using any Basic Text Search (BTS) features in this database. Using any BTS function or creating a BTS based index will create several tables and many stored routines that are part of the BTS Datablade. This is what dbexport/dbschema is including in the export. You can use the --no-blade-procs option to myschema to eliminate the stored procedures belonging to that database, but the tables and data types created by its installation are too hard for myschema to identify. Myschema will generate a script compatible with dbimport if you also add the -l option. Art Art S. Kagel, President and Principal Consultant ASK Database Management www.askdbmgt.com Blog: http://informix-myview.blogspot.com/ Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on the IIUG, nor any other organization with which I am associated either explicitly, implicitly, or by inference. Neither do those opinions reflect those of other individuals affiliated with any entity with which I am affiliated nor those of the entities themselves. On Sun, May 17, 2015 at 1:18 PM, BillHatVerizon <garage_dba@verizon.net> wrote: > This question concerns IBM Informix Dynamic Server Version 12.10.TC1IE > running > on Windows Server 2008R2 . > > The dbexport utility has started writing about 1500 of lines that were not > there before. > These are near the top of the schema file. > What could have caused this? How do I get the old behavior back? > > create opaque type "informix".sysbldsqltext > > ( > > internallength=variable, > > maxlen=24000, > > alignment=1 > > ); > > grant usage on type "informix".sysbldsqltext to 'public' as "informix";> > create row type "informix".bts_fsestoragerow > > ( > > sto_name lvarchar, > > num_buckets integer, > > bucket_num integer, > > bucket blob > > ); > grant usage on type "informix".bts_fsestoragerow to 'public' as> "informix"; > > create implicit cast (lvarchar as sysbldsqltext with > "informix".sysbldsqltextin); > > create explicit cast (sysbldsqltext as lvarchar with > "informix".sysbldsqltextout); > > create explicit cast (sysbldsqltext as sendrecv with > "informix".sysbldsqltextsend); > > create implicit cast (sendrecv as sysbldsqltext with > "informix".sysbldsqltextrecv); > > create implicit cast (impexp as sysbldsqltext with > "informix".sysbldsqltextimpt); > > create explicit cast (sysbldsqltext as impexp with > "informix".sysbldsqltextexpt); > > create implicit cast (impexpbin as sysbldsqltext with > "informix".sysbldsqltextimpb); > > create explicit cast (sysbldsqltext as impexpbin with > "informix".sysbldsqltextexpb); > > create function "informix".sysbldsqltextin (lvarchar) > returns SYSBldSQLText > external name '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldSQLTextIn)' > language c; > > -- etc, etc... > -- ====== at the end it has this... > insert into informix.systracemsgs values ('BTSF9', 338, 'en_us.8859-1', > NULL,> 'bts error - there is no snowball stemmer language specified after the > period'); > insert into informix.systracemsgs values ('BTSG0', 339, 'en_us.8859-1', > NULL,> 'bts error - there is no snowball stemmer language support for the > $DB_LOCALE > setting: %PARAM1%'); > insert into informix.systracemsgs values ('BTSG1', 340, 'en_us.8859-1', > NULL,> 'bts error - there is no snowball stemmer language support for the > specified > language: %PARAM1%'); > insert into informix.systracemsgs values ('BTSG2', 341, 'en_us.8859-1', > NULL,> 'bts error - internal index length %PARAM1% is too long. The maximum is > %PARAM2%'); > insert into informix.systracemsgs values ('BTSG3', 342, 'en_us.8859-1', > NULL,> 'bts error - bts_lock_setup: cannot get virtual processor lock pointer'); > insert into informix.systracemsgs values ('BTSG4', 343, 'en_us.8859-1', > NULL,> 'bts error - bts_lock_setup: virtual processor is not locked'); > insert into informix.systracemsgs values ('BTSG5', 344, 'en_us.8859-1', > NULL,> 'bts error - bts_lock_setup: virtual processor is not locked by the > current > transaction'); > insert into informix.systracemsgs values ('BTSG6', 345, 'en_us.8859-1', > NULL,> 'bts error - not (-) operator cannot be specified in thesaurus'); > insert into informix.systracemsgs values ('BTSG7', 346, 'en_us.8859-1', > NULL,> 'bts error - and (+) operator cannot be specified in thesaurus'); > insert into informix.systracemsgs values ('BTSG8', 347, 'en_us.8859-1', > NULL,> 'bts error - cannot determine index owner of thesaurus index %PARAM1%'); > insert into informix.systracemsgs values ('BTSG9', 348, 'en_us.8859-1', > NULL,> 'bts error - cannot lock thesaurus index %PARAM1%'); > insert into informix.systracemsgs values ('BTSH0', 349, 'en_us.8859-1', > NULL,> 'bts error - cannot read thesaurus index parameters for %PARAM1%'); > insert into informix.systracemsgs values ('BTSH1', 350, 'en_us.8859-1', > NULL,> 'bts error - the index %PARAM1% does not have the thesaurus parameter > set'); > insert into informix.systracemsgs values ('BTSH2', 351, 'en_us.8859-1', > NULL,> 'bts error - thesaurus index cannot be fragmented'); > insert into informix.systracemsgs values ('BTSH3', 352, 'en_us.8859-1', > NULL,> 'bts error - invalid term found in thesaurus. Only word terms can be > specified'); > insert into informix.systracemsgs values ('BTSH4', 353, 'en_us.8859-1', > NULL,> 'bts error - the %PARAM1% attribute must be specified'); > insert into informix.systracemsgs values ('BTSH5', 354, 'en_us.8859-1', > NULL,> 'bts error - the text or file attribute must be specified'); > insert into informix.systracemsgs values ('BTSH6', 355, 'en_us.8859-1', > NULL,> 'bts error - the copy_temp attribute can only be specified on an index in > an > sbspace'); > insert into informix.systracemsgs values ('BTSH7', 356, 'en_us.8859-1', > NULL,> 'bts error - the field is not in the document'); > insert into informix.systracemsgs values ('BTSH8', 357, 'en_us.8859-1', > NULL,> 'bts error - the directory cannot contain a bts index'); > insert into informix.systracemsgs values ('BTSH9', 358, 'en_us.8859-1', > NULL,> 'bts error - the ID is out of bounds'); > insert into informix.systracemsgs values ('BTSI0', 359, 'en_us.8859-1', > NULL,> 'bts error - must be a DBSA to use parameter %PARAM1%'); > insert into informix.systraceclasses values ('blademgr', 1); > insert into informix.systraceclasses values ('bts', 2);> > > > ***************************************************************

Before running the dbschema try unregistering the blade ??? Cheers Paul Paul Watson Oninit www.oninit.com +1 913 387 7529 Oninit® is a Registered Trademark of Oninit LLC > On May 17, 2015, at 16:13, BillHatVerizon <garage_dba@verizon.net> wrote: > > We have never intentionally used any BTS feature or created such an index. > Maybe there was a typo someplace last week. > How could I find out where the datablade is that caused this ? > > -----Original Message----- > From: Art Kagel > Sent: Sunday, May 17, 2015 12:30 PM > To: ids@iiug.org > Subject: Re: dbimport schema has changed [35110] > > These are related to using any Basic Text Search (BTS) features in this > database. Using any BTS function or creating a BTS based index will create > several tables and many stored routines that are part of the BTS > Datablade. This is what dbexport/dbschema is including in the export. > > You can use the --no-blade-procs option to myschema to eliminate the stored > procedures belonging to that database, but the tables and data types > created by its installation are too hard for myschema to identify. Myschema > will generate a script compatible with dbimport if you also add the -l > option. > > Art > > Art S. Kagel, President and Principal Consultant > ASK Database Management > www.askdbmgt.com > > Blog: http://informix-myview.blogspot.com/ > > Disclaimer: Please keep in mind that my own opinions are my own opinions > and do not reflect on the IIUG, nor any other organization with which I am > associated either explicitly, implicitly, or by inference. Neither do > those opinions reflect those of other individuals affiliated with any > entity with which I am affiliated nor those of the entities themselves. > > On Sun, May 17, 2015 at 1:18 PM, BillHatVerizon <garage_dba@verizon.net> > wrote: > >> This question concerns IBM Informix Dynamic Server Version 12.10.TC1IE >> running >> on Windows Server 2008R2 . >> >> The dbexport utility has started writing about 1500 of lines that were not >> there before. >> These are near the top of the schema file. >> What could have caused this? How do I get the old behavior back? >> >> create opaque type "informix".sysbldsqltext >> >> ( >> >> internallength=variable, >> >> maxlen=24000, >> >> alignment=1 >> >> ); >> >> grant usage on type "informix".sysbldsqltext to 'public' as "informix";>> >> create row type "informix".bts_fsestoragerow >> >> ( >> >> sto_name lvarchar, >> >> num_buckets integer, >> >> bucket_num integer, >> >> bucket blob >> >> ); >> grant usage on type "informix".bts_fsestoragerow to 'public' as>> "informix"; >> >> create implicit cast (lvarchar as sysbldsqltext with >> "informix".sysbldsqltextin); >> >> create explicit cast (sysbldsqltext as lvarchar with >> "informix".sysbldsqltextout); >> >> create explicit cast (sysbldsqltext as sendrecv with >> "informix".sysbldsqltextsend); >> >> create implicit cast (sendrecv as sysbldsqltext with >> "informix".sysbldsqltextrecv); >> >> create implicit cast (impexp as sysbldsqltext with >> "informix".sysbldsqltextimpt); >> >> create explicit cast (sysbldsqltext as impexp with >> "informix".sysbldsqltextexpt); >> >> create implicit cast (impexpbin as sysbldsqltext with >> "informix".sysbldsqltextimpb); >> >> create explicit cast (sysbldsqltext as impexpbin with >> "informix".sysbldsqltextexpb); >> >> create function "informix".sysbldsqltextin (lvarchar) >> returns SYSBldSQLText >> external name '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldSQLTextIn)' >> language c; >> >> -- etc, etc... >> -- ====== at the end it has this... >> insert into informix.systracemsgs values ('BTSF9', 338, 'en_us.8859-1', >> NULL,>> 'bts error - there is no snowball stemmer language specified after the >> period'); >> insert into informix.systracemsgs values ('BTSG0', 339, 'en_us.8859-1', >> NULL,>> 'bts error - there is no snowball stemmer language support for the >> $DB_LOCALE >> setting: %PARAM1%'); >> insert into informix.systracemsgs values ('BTSG1', 340, 'en_us.8859-1', >> NULL,>> 'bts error - there is no snowball stemmer language support for the >> specified >> language: %PARAM1%'); >> insert into informix.systracemsgs values ('BTSG2', 341, 'en_us.8859-1', >> NULL,>> 'bts error - internal index length %PARAM1% is too long. The maximum is >> %PARAM2%'); >> insert into informix.systracemsgs values ('BTSG3', 342, 'en_us.8859-1', >> NULL,>> 'bts error - bts_lock_setup: cannot get virtual processor lock pointer'); >> insert into informix.systracemsgs values ('BTSG4', 343, 'en_us.8859-1', >> NULL,>> 'bts error - bts_lock_setup: virtual processor is not locked'); >> insert into informix.systracemsgs values ('BTSG5', 344, 'en_us.8859-1', >> NULL,>> 'bts error - bts_lock_setup: virtual processor is not locked by the >> current >> transaction'); >> insert into informix.systracemsgs values ('BTSG6', 345, 'en_us.8859-1', >> NULL,>> 'bts error - not (-) operator cannot be specified in thesaurus'); >> insert into informix.systracemsgs values ('BTSG7', 346, 'en_us.8859-1', >> NULL,>> 'bts error - and (+) operator cannot be specified in thesaurus'); >> insert into informix.systracemsgs values ('BTSG8', 347, 'en_us.8859-1', >> NULL,>> 'bts error - cannot determine index owner of thesaurus index %PARAM1%'); >> insert into informix.systracemsgs values ('BTSG9', 348, 'en_us.8859-1', >> NULL,>> 'bts error - cannot lock thesaurus index %PARAM1%'); >> insert into informix.systracemsgs values ('BTSH0', 349, 'en_us.8859-1', >> NULL,>> 'bts error - cannot read thesaurus index parameters for %PARAM1%'); >> insert into informix.systracemsgs values ('BTSH1', 350, 'en_us.8859-1', >> NULL,>> 'bts error - the index %PARAM1% does not have the thesaurus parameter >> set'); >> insert into informix.systracemsgs values ('BTSH2', 351, 'en_us.8859-1', >> NULL,>> 'bts error - thesaurus index cannot be fragmented'); >> insert into informix.systracemsgs values ('BTSH3', 352, 'en_us.8859-1', >> NULL,>> 'bts error - invalid term found in thesaurus. Only word terms can be >> specified'); >> insert into informix.systracemsgs values ('BTSH4', 353, 'en_us.8859-1', >> NULL,>> 'bts error - the %PARAM1% attribute must be specified'); >> insert into informix.systracemsgs values ('BTSH5', 354, 'en_us.8859-1', >> NULL,>> 'bts error - the text or file attribute must be specified'); >> insert into informix.systracemsgs values ('BTSH6', 355, 'en_us.8859-1', >> NULL,>> 'bts error - the copy_temp attribute can only be specified on an index in >> an >> sbspace'); >> insert into informix.systracemsgs values ('BTSH7', 356, 'en_us.8859-1', >> NULL,>> 'bts error - the field is not in the document'); >> insert into informix.systracemsgs values ('BTSH8', 357, 'en_us.8859-1', >> NULL,>> 'bts error - the directory cannot contain a bts index

Run "blademgr" then, at the prompt, enter the command: my_servername> list <database name> That will print out a list of datablades registered to that database. Then you can use the "unregister <module name> <database name> You can see the blademgr command list by entering a question mark (?) at the command prompt. Art Art S. Kagel, President and Principal Consultant ASK Database Management www.askdbmgt.com Blog: http://informix-myview.blogspot.com/ Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on the IIUG, nor any other organization with which I am associated either explicitly, implicitly, or by inference. Neither do those opinions reflect those of other individuals affiliated with any entity with which I am affiliated nor those of the entities themselves. On Sun, May 17, 2015 at 5:13 PM, BillHatVerizon <garage_dba@verizon.net> wrote: > We have never intentionally used any BTS feature or created such an index. > Maybe there was a typo someplace last week. > How could I find out where the datablade is that caused this ? > > -----Original Message----- > From: Art Kagel > Sent: Sunday, May 17, 2015 12:30 PM > To: ids@iiug.org > Subject: Re: dbimport schema has changed [35110] > > These are related to using any Basic Text Search (BTS) features in this > database. Using any BTS function or creating a BTS based index will create > several tables and many stored routines that are part of the BTS > Datablade. This is what dbexport/dbschema is including in the export. > > You can use the --no-blade-procs option to myschema to eliminate the stored > procedures belonging to that database, but the tables and data types > created by its installation are too hard for myschema to identify. Myschema > will generate a script compatible with dbimport if you also add the -l > option. > > Art > > Art S. Kagel, President and Principal Consultant > ASK Database Management > www.askdbmgt.com > > Blog: http://informix-myview.blogspot.com/ > > Disclaimer: Please keep in mind that my own opinions are my own opinions > and do not reflect on the IIUG, nor any other organization with which I am > associated either explicitly, implicitly, or by inference. Neither do > those opinions reflect those of other individuals affiliated with any > entity with which I am affiliated nor those of the entities themselves. > > On Sun, May 17, 2015 at 1:18 PM, BillHatVerizon <garage_dba@verizon.net> > wrote: > > > This question concerns IBM Informix Dynamic Server Version 12.10.TC1IE > > running > > on Windows Server 2008R2 . > > > > The dbexport utility has started writing about 1500 of lines that were > not > > there before. > > These are near the top of the schema file. > > What could have caused this? How do I get the old behavior back? > > > > create opaque type "informix".sysbldsqltext > > > > ( > > > > internallength=variable, > > > > maxlen=24000, > > > > alignment=1 > > > > ); > > > > grant usage on type "informix".sysbldsqltext to 'public' as "informix";> > > > create row type "informix".bts_fsestoragerow > > > > ( > > > > sto_name lvarchar, > > > > num_buckets integer, > > > > bucket_num integer, > > > > bucket blob > > > > ); > > grant usage on type "informix".bts_fsestoragerow to 'public' as> > "informix"; > > > > create implicit cast (lvarchar as sysbldsqltext with > > "informix".sysbldsqltextin); > > > > create explicit cast (sysbldsqltext as lvarchar with > > "informix".sysbldsqltextout); > > > > create explicit cast (sysbldsqltext as sendrecv with > > "informix".sysbldsqltextsend); > > > > create implicit cast (sendrecv as sysbldsqltext with > > "informix".sysbldsqltextrecv); > > > > create implicit cast (impexp as sysbldsqltext with > > "informix".sysbldsqltextimpt); > > > > create explicit cast (sysbldsqltext as impexp with > > "informix".sysbldsqltextexpt); > > > > create implicit cast (impexpbin as sysbldsqltext with > > "informix".sysbldsqltextimpb); > > > > create explicit cast (sysbldsqltext as impexpbin with > > "informix".sysbldsqltextexpb); > > > > create function "informix".sysbldsqltextin (lvarchar) > > returns SYSBldSQLText > > external name '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldSQLTextIn)' > > language c; > > > > -- etc, etc... > > -- ====== at the end it has this... > > insert into informix.systracemsgs values ('BTSF9', 338, 'en_us.8859-1', > > NULL,> > 'bts error - there is no snowball stemmer language specified after the > > period'); > > insert into informix.systracemsgs values ('BTSG0', 339, 'en_us.8859-1', > > NULL,> > 'bts error - there is no snowball stemmer language support for the > > $DB_LOCALE > > setting: %PARAM1%'); > > insert into informix.systracemsgs values ('BTSG1', 340, 'en_us.8859-1', > > NULL,> > 'bts error - there is no snowball stemmer language support for the > > specified > > language: %PARAM1%'); > > insert into informix.systracemsgs values ('BTSG2', 341, 'en_us.8859-1', > > NULL,> > 'bts error - internal index length %PARAM1% is too long. The maximum is > > %PARAM2%'); > > insert into informix.systracemsgs values ('BTSG3', 342, 'en_us.8859-1', > > NULL,> > 'bts error - bts_lock_setup: cannot get virtual processor lock pointer'); > > insert into informix.systracemsgs values ('BTSG4', 343, 'en_us.8859-1', > > NULL,> > 'bts error - bts_lock_setup: virtual processor is not locked'); > > insert into informix.systracemsgs values ('BTSG5', 344, 'en_us.8859-1', > > NULL,> > 'bts error - bts_lock_setup: virtual processor is not locked by the > > current > > transaction'); > > insert into informix.systracemsgs values ('BTSG6', 345, 'en_us.8859-1', > > NULL,> > 'bts error - not (-) operator cannot be specified in thesaurus'); > > insert into informix.systracemsgs values ('BTSG7', 346, 'en_us.8859-1', > > NULL,> > 'bts error - and (+) operator cannot be specified in thesaurus'); > > insert into informix.systracemsgs values ('BTSG8', 347, 'en_us.8859-1', > > NULL,> > 'bts error - cannot determine index owner of thesaurus index %PARAM1%'); > > insert into informix.systracemsgs values ('BTSG9', 348, 'en_us.8859-1', > > NULL,> > 'bts error - cannot lock thesaurus index %PARAM1%'); > > insert into informix.systracemsgs values ('BTSH0', 349, 'en_us.8859-1', > > NULL,> > 'bts error - cannot read thesaurus index parameters for %PARAM1%'); > > insert into informix.systracemsgs values ('BTSH1', 350, 'en_us.8859-1', > > NULL,> > 'bts error - the index %PARAM1% does not have the thesaurus parameter > > set'); > > insert into informix.systracemsgs values ('BTSH2', 351, 'en_us.8859-1', > > NULL,> > 'bts error - thesaurus index cannot be fragmented'); > > insert into informix.systracemsgs values ('BTSH3', 352, 'en_us.8859-1', > > NULL,> > 'bts error - invalid term found in thesaurus. Only word t

What happens if you take the v11.70 onconfig .. and use that on the v12 without setting anything else .. I've had a similar issue between 11.70 and 12.10.fc3 ... haven't yet figured it out .. but I get the same execution times when running my old onconfig on the new version ... This might help to rule out that you have set something in the new onconfig that is creating the problem .... Peter Logan Database Administrator SpartanNash INC. Office: 616/878-8309 Mobile: 616/304-9672 E-Mail: peter.logan@spartannash.com From: "Art Kagel" <art.kagel@gmail.com> To: ids@iiug.org Date: 05/17/2015 01:31 PM Subject: Re: dbimport schema has changed [35110] Sent by: ids-bounces@iiug.org These are related to using any Basic Text Search (BTS) features in this database. Using any BTS function or creating a BTS based index will create several tables and many stored routines that are part of the BTS Datablade. This is what dbexport/dbschema is including in the export. You can use the --no-blade-procs option to myschema to eliminate the stored procedures belonging to that database, but the tables and data types created by its installation are too hard for myschema to identify. Myschema will generate a script compatible with dbimport if you also add the -l option. Art Art S. Kagel, President and Principal Consultant ASK Database Management www.askdbmgt.com Blog: http://informix-myview.blogspot.com/ Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on the IIUG, nor any other organization with which I am associated either explicitly, implicitly, or by inference. Neither do those opinions reflect those of other individuals affiliated with any entity with which I am affiliated nor those of the entities themselves. On Sun, May 17, 2015 at 1:18 PM, BillHatVerizon <garage_dba@verizon.net> wrote: > This question concerns IBM Informix Dynamic Server Version 12.10.TC1IE > running > on Windows Server 2008R2 . > > The dbexport utility has started writing about 1500 of lines that were not > there before. > These are near the top of the schema file. > What could have caused this? How do I get the old behavior back? > > create opaque type "informix".sysbldsqltext > > ( > > internallength=variable, > > maxlen=24000, > > alignment=1 > > ); > > grant usage on type "informix".sysbldsqltext to 'public' as "informix";> > create row type "informix".bts_fsestoragerow > > ( > > sto_name lvarchar, > > num_buckets integer, > > bucket_num integer, > > bucket blob > > ); > grant usage on type "informix".bts_fsestoragerow to 'public' as"informix"; > > create implicit cast (lvarchar as sysbldsqltext with > "informix".sysbldsqltextin); > > create explicit cast (sysbldsqltext as lvarchar with > "informix".sysbldsqltextout); > > create explicit cast (sysbldsqltext as sendrecv with > "informix".sysbldsqltextsend); > > create implicit cast (sendrecv as sysbldsqltext with > "informix".sysbldsqltextrecv); > > create implicit cast (impexp as sysbldsqltext with > "informix".sysbldsqltextimpt); > > create explicit cast (sysbldsqltext as impexp with > "informix".sysbldsqltextexpt); > > create implicit cast (impexpbin as sysbldsqltext with > "informix".sysbldsqltextimpb); > > create explicit cast (sysbldsqltext as impexpbin with > "informix".sysbldsqltextexpb); > > create function "informix".sysbldsqltextin (lvarchar) > returns SYSBldSQLText > external name '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldSQLTextIn)' > language c; > > -- etc, etc... > -- ====== at the end it has this... > insert into informix.systracemsgs values ('BTSF9', 338, 'en_us.8859-1', > NULL,> 'bts error - there is no snowball stemmer language specified after the > period'); > insert into informix.systracemsgs values ('BTSG0', 339, 'en_us.8859-1', > NULL,> 'bts error - there is no snowball stemmer language support for the > $DB_LOCALE > setting: %PARAM1%'); > insert into informix.systracemsgs values ('BTSG1', 340, 'en_us.8859-1', > NULL,> 'bts error - there is no snowball stemmer language support for the > specified > language: %PARAM1%'); > insert into informix.systracemsgs values ('BTSG2', 341, 'en_us.8859-1', > NULL,> 'bts error - internal index length %PARAM1% is too long. The maximum is > %PARAM2%'); > insert into informix.systracemsgs values ('BTSG3', 342, 'en_us.8859-1', > NULL,> 'bts error - bts_lock_setup: cannot get virtual processor lock pointer'); > insert into informix.systracemsgs values ('BTSG4', 343, 'en_us.8859-1', > NULL,> 'bts error - bts_lock_setup: virtual processor is not locked'); > insert into informix.systracemsgs values ('BTSG5', 344, 'en_us.8859-1', > NULL,> 'bts error - bts_lock_setup: virtual processor is not locked by the current > transaction'); > insert into informix.systracemsgs values ('BTSG6', 345, 'en_us.8859-1', > NULL,> 'bts error - not (-) operator cannot be specified in thesaurus'); > insert into informix.systracemsgs values ('BTSG7', 346, 'en_us.8859-1', > NULL,> 'bts error - and (+) operator cannot be specified in thesaurus'); > insert into informix.systracemsgs values ('BTSG8', 347, 'en_us.8859-1', > NULL,> 'bts error - cannot determine index owner of thesaurus index %PARAM1%'); > insert into informix.systracemsgs values ('BTSG9', 348, 'en_us.8859-1', > NULL,> 'bts error - cannot lock thesaurus index %PARAM1%'); > insert into informix.systracemsgs values ('BTSH0', 349, 'en_us.8859-1', > NULL,> 'bts error - cannot read thesaurus index parameters for %PARAM1%'); > insert into informix.systracemsgs values ('BTSH1', 350, 'en_us.8859-1', > NULL,> 'bts error - the index %PARAM1% does not have the thesaurus parameter > set'); > insert into informix.systracemsgs values ('BTSH2', 351, 'en_us.8859-1', > NULL,> 'bts error - thesaurus index cannot be fragmented'); > insert into informix.systracemsgs values ('BTSH3', 352, 'en_us.8859-1', > NULL,> 'bts error - invalid term found in thesaurus. Only word terms can be > specified'); > insert into informix.systracemsgs values ('BTSH4', 353, 'en_us.8859-1', > NULL,> 'bts error - the %PARAM1% attribute must be specified'); > insert into informix.systracemsgs values ('BTSH5', 354, 'en_us.8859-1', > NULL,> 'bts error - the text or file attribute must be specified'); > insert into informix.systracemsgs values ('BTSH6', 355, 'en_us.8859-1', > NULL,> 'bts error - the copy_temp attribute can only be specified on an index in > an > sbspace'); > insert into informix.systracemsgs values ('BTSH7', 356, 'en_us.8859-1', > NULL,> 'bts error - the field is not in the document'); > insert into informix.systracemsgs values ('BTSH8', 357, 'en_us.8859-1', > NULL,> 'bts error - the directory cannot contain a bts index'); > insert into informix.systracemsgs valu

Thanks, Art. There was one blade registered - namely bts.3.00 . I don't know how it got registered. I did not do it. Nobody else has access. I unregistered it. That reduced the number of lines of junk in the export from 1500 down to 234. How do I get rid of these? create opaque type "informix".sysbldsqltext ( internallength=variable, maxlen=24000, alignment=1 ); grant usage on type "informix".sysbldsqltext to 'public' as "informix"; create implicit cast (lvarchar as sysbldsqltext with "informix".sysbldsqltextin); create explicit cast (sysbldsqltext as lvarchar with "informix".sysbldsqltextout); create explicit cast (sysbldsqltext as sendrecv with "informix".sysbldsqltextsend); create implicit cast (sendrecv as sysbldsqltext with "informix".sysbldsqltextrecv); create implicit cast (impexp as sysbldsqltext with "informix".sysbldsqltextimpt); create explicit cast (sysbldsqltext as impexp with "informix".sysbldsqltextexpt); create implicit cast (impexpbin as sysbldsqltext with "informix".sysbldsqltextimpb); create explicit cast (sysbldsqltext as impexpbin with "informix".sysbldsqltextexpb); create function "informix".sysbldsqltextin (lvarchar) returns SYSBldSQLText external name '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldSQLTextIn)' language c; create function "informix".sysbldsqltextout (SYSBldSQLText) returns lvarchar external name '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldSQLTextIn)' language c; create function "informix".sysbldsqltextsend (SYSBldSQLText) returns sendrecv external name '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldSQLTextOut)' language c; create function "informix".sysbldsqltextrecv (sendrecv) returns SYSBldSQLText external name '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldSQLTextIn)' language c; create function "informix".sysbldsqltextimpt (impexp) returns SYSBldSQLText external name '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldSQLTextIn)' language c; create function "informix".sysbldsqltextexpt (SYSBldSQLText) returns impexp external name '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldSQLTextOut)' language c; create function "informix".sysbldsqltextimpb (impexpbin) returns SYSBldSQLText external name '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldSQLTextIn)' language c; create function "informix".sysbldsqltextexpb (SYSBldSQLText) returns impexpbin external name '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldSQLTextOut)' language c; create function "informix".equal (SYSBldSQLText,SYSBldSQLText) returns boolean external name '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldSQLTextEqual)' language c; create function "informix".sysbldlike (SYSBldSQLText,SYSBldSQLText) returns boolean external name '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldSQLTextLike)' language c; create function "informix".sysbldprepare() returns integer external name '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldPrepare2)' language C variant; create function "informix".sysbldregister(CHAR(64), CHAR(18)) returns integer external name '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldRegister)' language C variant; create function "informix".sysbldregister(CHAR(64)) returns integer external name '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldRegister2)' language C variant; create function "informix".sysbldunregister(CHAR(64), CHAR(18)) returns integer external name '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldUnregister)' language C variant; create function "informix".sysbldunregister(CHAR(64)) returns integer external name '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldUnregister2)' language C variant; create function "informix".sysbldtrace(CHAR(64), integer) returns integer external name '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldSetTraceFile)' language C variant; create function "informix".sysbldtrace(integer) returns integer external name '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldSetTraceFile2)' language C variant; create function "informix".sysbldcleanuptables() returns integer external name '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldCleanupTables)' language C variant; create function "informix".sysbldrelease() returns lvarchar external name '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(MackRelease)' language C not variant; create function "informix".sysbldgetsrvrfile(lvarchar, lvarchar) returns integer external name '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(FetchSrvrFile)' language C variant; create function "informix".sysbldlstbldtoprep() returns lvarchar external name '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(LstBldToPrep)' language C variant; create function "informix".sysbldprepblade(lvarchar) returns integer external name '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(PrepBlade)' language C variant; create function "informix".sysbldtstsbspace (lvarchar) returns integer external name '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldTstSBSpace)' language c variant; create function "informix".sysbldtstvp (lvarchar) returns integer external name '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldTstVP)' language c variant; create function "informix".sysbldunprepare() returns integer external name '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldUnPrepare)' language C variant; create function "informix".sysbldaddblddir(lvarchar, lvarchar) returns integer external name '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldAddBldDir)' language C variant; create function "informix".sysbldputsrvrfile(lvarchar, lvarchar) returns integer external name '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldPutSrvrFile)' language C variant; create function "informix".sysbldgetanysrvrfile(lvarchar, lvarchar) returns integer external name '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldGetAnySrvrFile)' language C variant; create function "informix".sysbldhtmltableize(lvarchar,lvarchar) returns integer external name '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldHTMLTableize)' language c; create function "informix".sysbldhtmlobjdependents(lvarchar,lvarchar) returns integer external name "$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldHTMLObjDependents)" language c; create function "informix".sysbldhtmlobjdependencies(lvarchar,lvarchar) returns integer external name "$INFORMIXDIR/exte

It could have been auto registered ?? Try removing/renaming the files in $INFORMIXDIR/extend ? These,AFAIK, are all to do with the blademgr, so in theory you can run remove them from the SQL. Cheers Paul > Thanks, Art. > There was one blade registered - namely bts.3.00 . > I don't know how it got registered. I did not do it. Nobody else has > access. > I unregistered it. That reduced the number of lines of junk in the export > from 1500 down to 234. > How do I get rid of these? > create opaque type "informix".sysbldsqltext > > ( > > internallength=variable, > > maxlen=24000, > > alignment=1 > > ); > > grant usage on type "informix".sysbldsqltext to 'public' as "informix";> > create implicit cast (lvarchar as sysbldsqltext with > "informix".sysbldsqltextin); > > create explicit cast (sysbldsqltext as lvarchar with > "informix".sysbldsqltextout); > > create explicit cast (sysbldsqltext as sendrecv with > "informix".sysbldsqltextsend); > > create implicit cast (sendrecv as sysbldsqltext with > "informix".sysbldsqltextrecv); > > create implicit cast (impexp as sysbldsqltext with > "informix".sysbldsqltextimpt); > > create explicit cast (sysbldsqltext as impexp with > "informix".sysbldsqltextexpt); > > create implicit cast (impexpbin as sysbldsqltext with > "informix".sysbldsqltextimpb); > > create explicit cast (sysbldsqltext as impexpbin with > "informix".sysbldsqltextexpb); > > create function "informix".sysbldsqltextin (lvarchar) > returns SYSBldSQLText > external name '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldSQLTextIn)' > language c; > > create function "informix".sysbldsqltextout (SYSBldSQLText) > returns lvarchar > external name '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldSQLTextIn)' > language c; > > create function "informix".sysbldsqltextsend (SYSBldSQLText) > returns sendrecv > external name '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldSQLTextOut)' > language c; > > create function "informix".sysbldsqltextrecv (sendrecv) > returns SYSBldSQLText > external name '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldSQLTextIn)' > language c; > > create function "informix".sysbldsqltextimpt (impexp) > returns SYSBldSQLText > external name '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldSQLTextIn)' > language c; > > create function "informix".sysbldsqltextexpt (SYSBldSQLText) > returns impexp > external name '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldSQLTextOut)' > language c; > > create function "informix".sysbldsqltextimpb (impexpbin) > returns SYSBldSQLText > external name '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldSQLTextIn)' > language c; > > create function "informix".sysbldsqltextexpb (SYSBldSQLText) > returns impexpbin > external name '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldSQLTextOut)' > language c; > > create function "informix".equal (SYSBldSQLText,SYSBldSQLText) > returns boolean > external name > '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldSQLTextEqual)' > language c; > > create function "informix".sysbldlike (SYSBldSQLText,SYSBldSQLText) > returns boolean > external name '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldSQLTextLike)' > language c; > > create function "informix".sysbldprepare() returns integer > > external name > '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldPrepare2)' > > language C variant; > > create function "informix".sysbldregister(CHAR(64), CHAR(18)) returns > integer > > external name > '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldRegister)' > > language C variant; > > create function "informix".sysbldregister(CHAR(64)) returns integer > > external name > '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldRegister2)' > > language C variant; > > create function "informix".sysbldunregister(CHAR(64), CHAR(18)) returns > integer > > external name > '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldUnregister)' > > language C variant; > > create function "informix".sysbldunregister(CHAR(64)) returns integer > > external name > '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldUnregister2)' > > language C variant; > > create function "informix".sysbldtrace(CHAR(64), integer) returns integer > > external name > '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldSetTraceFile)' > > language C variant; > > create function "informix".sysbldtrace(integer) returns integer > > external name > '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldSetTraceFile2)' > > language C variant; > > create function "informix".sysbldcleanuptables() returns integer > > external name > '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldCleanupTables)' > > language C variant; > > create function "informix".sysbldrelease() returns lvarchar > > external name > '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(MackRelease)' > > language C not variant; > > create function "informix".sysbldgetsrvrfile(lvarchar, lvarchar) returns > integer > > external name > '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(FetchSrvrFile)' > > language C variant; > > create function "informix".sysbldlstbldtoprep() returns lvarchar > > external name > '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(LstBldToPrep)' > > language C variant; > > create function "informix".sysbldprepblade(lvarchar) returns integer > > external name > '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(PrepBlade)' > > language C variant; > > create function "informix".sysbldtstsbspace (lvarchar) returns integer > > external name > '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldTstSBSpace)' > > language c variant; > > create function "informix".sysbldtstvp (lvarchar) returns integer > > external name > '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldTstVP)' > > language c variant; > > create function "informix".sysbldunprepare() returns integer > > external name > '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldUnPrepare)' > > language C variant; > > create function "informix".sysbldaddblddir(lvarchar, lvarchar) returns > integer > > external name > '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldAddBldDir)' > > language C variant; > > create function "informix".sysbldputsrvrfile(lvarchar, lvarchar) returns > integer > > external name > '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldPutSrvrFile)' > > language C variant; > > create function "informix".sysbldgetanysrvrfile(lvarchar, lvarchar) > returns > integer > > external name > '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldGetAnySrvrFile)'@@NL

It can auto register itself if someone with sufficient privileges called a BTS function. You will have to drop the objects that the BTS blade created. That would include the CASTs, PROCEDURES, types (row type bts_fsestoragerow and opaque type sysbldsqltext), and the tables systraceclasses and systracemsgs. No easy way around it. The unregister doesn't clean these up in case they are being used by other blades. Art Art S. Kagel, President and Principal Consultant ASK Database Management www.askdbmgt.com Blog: http://informix-myview.blogspot.com/ Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on the IIUG, nor any other organization with which I am associated either explicitly, implicitly, or by inference. Neither do those opinions reflect those of other individuals affiliated with any entity with which I am affiliated nor those of the entities themselves. On Mon, May 18, 2015 at 11:53 AM, BillHatVerizon <garage_dba@verizon.net> wrote: > Thanks, Art. > There was one blade registered - namely bts.3.00 . > I don't know how it got registered. I did not do it. Nobody else has > access. > I unregistered it. That reduced the number of lines of junk in the export > from 1500 down to 234. > How do I get rid of these? > create opaque type "informix".sysbldsqltext > > ( > > internallength=variable, > > maxlen=24000, > > alignment=1 > > ); > > grant usage on type "informix".sysbldsqltext to 'public' as "informix";> > create implicit cast (lvarchar as sysbldsqltext with > "informix".sysbldsqltextin); > > create explicit cast (sysbldsqltext as lvarchar with > "informix".sysbldsqltextout); > > create explicit cast (sysbldsqltext as sendrecv with > "informix".sysbldsqltextsend); > > create implicit cast (sendrecv as sysbldsqltext with > "informix".sysbldsqltextrecv); > > create implicit cast (impexp as sysbldsqltext with > "informix".sysbldsqltextimpt); > > create explicit cast (sysbldsqltext as impexp with > "informix".sysbldsqltextexpt); > > create implicit cast (impexpbin as sysbldsqltext with > "informix".sysbldsqltextimpb); > > create explicit cast (sysbldsqltext as impexpbin with > "informix".sysbldsqltextexpb); > > create function "informix".sysbldsqltextin (lvarchar) > returns SYSBldSQLText > external name '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldSQLTextIn)' > language c; > > create function "informix".sysbldsqltextout (SYSBldSQLText) > returns lvarchar > external name '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldSQLTextIn)' > language c; > > create function "informix".sysbldsqltextsend (SYSBldSQLText) > returns sendrecv > external name '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldSQLTextOut)' > language c; > > create function "informix".sysbldsqltextrecv (sendrecv) > returns SYSBldSQLText > external name '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldSQLTextIn)' > language c; > > create function "informix".sysbldsqltextimpt (impexp) > returns SYSBldSQLText > external name '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldSQLTextIn)' > language c; > > create function "informix".sysbldsqltextexpt (SYSBldSQLText) > returns impexp > external name '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldSQLTextOut)' > language c; > > create function "informix".sysbldsqltextimpb (impexpbin) > returns SYSBldSQLText > external name '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldSQLTextIn)' > language c; > > create function "informix".sysbldsqltextexpb (SYSBldSQLText) > returns impexpbin > external name '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldSQLTextOut)' > language c; > > create function "informix".equal (SYSBldSQLText,SYSBldSQLText) > returns boolean > external name '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldSQLTextEqual)' > language c; > > create function "informix".sysbldlike (SYSBldSQLText,SYSBldSQLText) > returns boolean > external name '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldSQLTextLike)' > language c; > > create function "informix".sysbldprepare() returns integer > > external name > '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldPrepare2)' > > language C variant; > > create function "informix".sysbldregister(CHAR(64), CHAR(18)) returns > integer > > external name > '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldRegister)' > > language C variant; > > create function "informix".sysbldregister(CHAR(64)) returns integer > > external name > '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldRegister2)' > > language C variant; > > create function "informix".sysbldunregister(CHAR(64), CHAR(18)) returns > integer > > external name > '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldUnregister)' > > language C variant; > > create function "informix".sysbldunregister(CHAR(64)) returns integer > > external name > '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldUnregister2)' > > language C variant; > > create function "informix".sysbldtrace(CHAR(64), integer) returns integer > > external name > '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldSetTraceFile)' > > language C variant; > > create function "informix".sysbldtrace(integer) returns integer > > external name > '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldSetTraceFile2)' > > language C variant; > > create function "informix".sysbldcleanuptables() returns integer > > external name > '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldCleanupTables)' > > language C variant; > > create function "informix".sysbldrelease() returns lvarchar > > external name > '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(MackRelease)' > > language C not variant; > > create function "informix".sysbldgetsrvrfile(lvarchar, lvarchar) returns > integer > > external name > '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(FetchSrvrFile)' > > language C variant; > > create function "informix".sysbldlstbldtoprep() returns lvarchar > > external name > '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(LstBldToPrep)' > > language C variant; > > create function "informix".sysbldprepblade(lvarchar) returns integer > > external name > '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(PrepBlade)' > > language C variant; > > create function "informix".sysbldtstsbspace (lvarchar) returns integer > > external name > '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldTstSBSpace)' > > language c variant; > > create function "informix".sysbldtstvp (lvarchar) returns integer > > external name > '$INFORMIXDIR/extend/ifxmngr/ifxmngr.bld(SYSBldTstVP)' > > language c variant; > > create function "informix".sy