IDS Forum

Re: dbimport schema has changed

Posted By: Art Kagel
Date: Sunday, 17 May 2015, at 1:30 p.m.

In Response To: dbimport schema has changed (BillHatVerizon)

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

Messages In This Thread

• dbimport schema has changed
  BillHatVerizon -- Sunday, 17 May 2015, at 1:18 p.m.
  • Re: dbimport schema has changed
    Art Kagel -- Sunday, 17 May 2015, at 1:30 p.m.
    • Re: dbimport schema has changed
      BillHatVerizon -- Sunday, 17 May 2015, at 5:13 p.m.
      • Re: dbimport schema has changed
        Paul Watson -- Sunday, 17 May 2015, at 5:21 p.m.
      • Re: dbimport schema has changed
        Art Kagel -- Sunday, 17 May 2015, at 6:51 p.m.
        • Re: dbimport schema has changed
          BillHatVerizon -- Monday, 18 May 2015, at 11:53 a.m.
          • Re: dbimport schema has changed
            Paul Watson -- Monday, 18 May 2015, at 12:24 p.m.
          • Re: dbimport schema has changed
            Art Kagel -- Monday, 18 May 2015, at 12:45 p.m.
    • Re: dbimport schema has changed
      Peter.Logan@spartannash.com -- Monday, 18 May 2015, at 8:38 a.m.

IDS Forum is maintained by Administrator with WebBBS 5.12.