Excalibur datablade
Posted in 2013
User had ETX datablade registered in sysbldregistered but couldn't create indexes using it—error "Access method (etx) does not exist". Sysams table showed the access method existed. Re-registering the blade multiple times didn't help. Issue resolved by refreshing the instance from production backup.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
Topics: General Discussion
Informix 10.00.FC11 Solaris 5.10 I have a database that states that a datablade is registered ( ETX.1.31.FC1 ) but when I try to use it it states that the access_method etx does not exist. If I look in the sysams table there is an entry. if I try to create the access method it tells me it already exists. Anyone had problems with this datablade? Thanks Andy Grantham.
Hi Andy,
Thanks for asking the question.
To verify if a blade is registered or not, you can run:
select * from sysbldregistered;This will show you 3 blades ETX, TXT, LLD if ETX is registered.
When you said, no access method ETX, could you show me the sql statement you
ran and what output error came out?
Hope this will give us understanding what situation you ran into.
Thanks
--weiming
Hello weiming,
contents of sysbldregistered.
bld_id
LLD.1.20.FC2
TXT.1.10.FC6
ifxbuiltins.1.1
web.4.13.FC3
ifxrltree.2.00
ETX.1.31.FC1
Contents of sysams
am_name etx
am_owner informix
am_id 100
am_type S
am_sptype S
am_defopclass 0
am_keyscan 0
am_unique 0
am_cluster 0
am_rowids 0
am_readwrite 0
am_parallel 0
am_costfactor 0.00
am_create 344
am_drop 346
am_open 0
am_close 343
am_insert 349
am_delete 345
am_update 352
am_stats 0
am_scancost 351
am_check 342
am_beginscan 341
am_endscan 347
am_rescan 350
am_getnext 348
am_getbyid 0
am_build 0
am_init 0
SQL trying to run.
create index "ifx_web".i_lang_attr_value on "ifx_web".cw_lang_attr_val_local
(value etx_char_ops) using etx (word_support='PATTERN', phrase_support=
'MAXIMUM', char_set='OVERLAP_ISO') in sbspace;
ochut-ifx301:/usr/informix/var/PRF/newone/migration_attkw/attributes >
dbaccess oamicfi andy.sql
Database selected.
9845: Access method (etx) does not exist in database.
Error in line 3Near character position 47
Database closed.
Regards
Andy Grantham
> To: ids@iiug.org
> From: weiming@us.ibm.com
> Subject: Re: Excalibur datablade [31145]
> Date: Mon, 12 Aug 2013 17:58:09 -0400
>
> Hi Andy,
>
> Thanks for asking the question.
>
> To verify if a blade is registered or not, you can run:
>
> select * from sysbldregistered;> This will show you 3 blades ETX, TXT, LLD if ETX is registered.
>
> When you said, no access method ETX, could you show me the sql statement you
> ran and what output error came out?
>
> Hope this will give us understanding what situation you ran into.
>
> Thanks
> --weiming
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
Hi Andrew, Could you re-register the blade again and see if still give you this error? blademgr > register ETX.1.31.FC1 mydb Since this is a basic operation for years with all existing users, this error could be particularly related to this database. Thanks --weiming
Hello Weiming, Yes I tried that as well. 4 times to be exact. It made no difference. In the end I have refreshed the instance from production as the users required it for testing as they could not wait any longer. Thanks for your help. Regards Andy Grantham. > To: ids@iiug.org > From: weiming@us.ibm.com > Subject: Re: RE: Excalibur datablade [31176] > Date: Tue, 13 Aug 2013 14:28:13 -0400 > > Hi Andrew, > > Could you re-register the blade again and see if still give you this error? > > blademgr > > register ETX.1.31.FC1 mydb > > Since this is a basic operation for years with all existing users, this error > could be particularly related to this database. > > Thanks > --weiming > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. >
So I guessed the refresh of instance making the database back to normal. Btw, may consider to upgrade IDS 11.70 or 12.10, since IDS v10 is out of support. Thanks --weiming