Unexpected error registering BTS 2.00 datablade
Registering the BTS 2.00 DataBlade on IDS 11.50.FC3 (Linux) failed with "SYSBldTstSBSpace ... mi_named_get failed, no such name" and a generic registration failure. The cause: BTS 2.00 (unlike 1.xx, which only used external spaces) can store indexes in a smart blob space and requires a default logged sbspace, i.e. ONCONFIG SBSPACENAME pointing at an existing smart blob space. Creating/configuring an sbspace let registration succeed. IBM staff confirmed this requirement was simply missing from the docs and release notes, not a code bug.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
Has anyone else encountered this error when trying to register the BTS datablade? We're trying this in IDS version 11.50.FC3 on Linux. We've recently migrated from version 11.50.FC2 and we first unregistered the BTS database before migrating. # blademgr local_on>register bts.2.00 stores Register module bts.2.00 into database stores? [Y/n] Registering DataBlade module... (may take a while). blademgr: ERROR: DataBlade bts.2.00 could not be registered in database stores. Use 'show last log' for details of failures in module's scripts. local_on>show last log blade: bts.2.00 err expct: unexpected SQL stmt: execute function SYSBldTstSBSpace(""); SQL state: XU0001:-937 : mi_named_get failed, no such name. blade: bts.2.00 err expct: unexpected SQL stmt: EXCEPTION SQL state: Registration failed for DataBlade module "bts.2.00". local_on>
Ron MacNeil wrote: > Has anyone else encountered this error when trying to register the BTS > datablade? We're trying this in IDS version 11.50.FC3 on Linux. > We've recently migrated from version 11.50.FC2 and we first > unregistered the BTS database before migrating. > > # blademgr > local_on>register bts.2.00 stores > Register module bts.2.00 into database stores? [Y/n] > Registering DataBlade module... (may take a while). > blademgr: ERROR: DataBlade bts.2.00 could not be registered in database > stores. > Use 'show last log' for details of failures in module's scripts. > local_on>show last log > > blade: bts.2.00 > err expct: unexpected > SQL stmt: execute function SYSBldTstSBSpace(""); > SQL state: XU0001:-937 : mi_named_get failed, no such name. > > blade: bts.2.00 > err expct: unexpected > SQL stmt: EXCEPTION > SQL state: Registration failed for DataBlade module "bts.2.00". > > local_on> Sounds like you haven't configured an SBSpace for the engine to use. -- Cheers, Obnoxio The Clown http://obotheclown.blogspot.com
On Sat, Dec 6, 2008 at 4:12 AM, Obnoxio The Clown <obnoxio@serendipita.com> wrote: > Ron MacNeil wrote: >> Has anyone else encountered this error when trying to register the BTS >> datablade? We're trying this in IDS version 11.50.FC3 on Linux. >> We've recently migrated from version 11.50.FC2 and we first >> unregistered the BTS database before migrating. >> >> # blademgr >> local_on>register bts.2.00 stores >> Register module bts.2.00 into database stores? [Y/n] >> Registering DataBlade module... (may take a while). >> blademgr: ERROR: DataBlade bts.2.00 could not be registered in database >> stores. >> Use 'show last log' for details of failures in module's scripts. >> local_on>show last log >> >> blade: bts.2.00 >> err expct: unexpected >> SQL stmt: execute function SYSBldTstSBSpace(""); >> SQL state: XU0001:-937 : mi_named_get failed, no such name. >> >> blade: bts.2.00 >> err expct: unexpected >> SQL stmt: EXCEPTION >> SQL state: Registration failed for DataBlade module "bts.2.00". >> >> local_on> > > Sounds like you haven't configured an SBSpace for the engine to use. > > -- > Cheers, > Obnoxio The Clown > > http://obotheclown.blogspot.com > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > Yes I had figured that out too; adding an sbspace gets past the issue. Looks like this may be a bug in the new version of the BTS datablade at the very least an omission in the documentation. I've got a case opened with IBM to clarify the situation. Thanks.
Ron, You are correct, I just did some testing and it is a bug to me also. I will be submitting this on your behalf to R & D for an official answer. Thanks Carl Carl Williams Jr SWG Client Support - Software Technical Support Engineer Phone: 1-913-599-7100 x5260 Internal: 337-5260 carljr@us.ibm.com "Ron MacNeil" <macneil.ron@gmail.com> Sent by: ids-bounces@iiug.org 12/08/2008 08:48 AM Please respond to ids@iiug.org To ids@iiug.org cc Subject Re: Unexpected error registering BTS 2.00 data.... [14246] On Sat, Dec 6, 2008 at 4:12 AM, Obnoxio The Clown <obnoxio@serendipita.com> wrote: > Ron MacNeil wrote: >> Has anyone else encountered this error when trying to register the BTS >> datablade? We're trying this in IDS version 11.50.FC3 on Linux. >> We've recently migrated from version 11.50.FC2 and we first >> unregistered the BTS database before migrating. >> >> # blademgr >> local_on>register bts.2.00 stores >> Register module bts.2.00 into database stores? [Y/n] >> Registering DataBlade module... (may take a while). >> blademgr: ERROR: DataBlade bts.2.00 could not be registered in database >> stores. >> Use 'show last log' for details of failures in module's scripts. >> local_on>show last log >> >> blade: bts.2.00 >> err expct: unexpected >> SQL stmt: execute function SYSBldTstSBSpace(""); >> SQL state: XU0001:-937 : mi_named_get failed, no such name. >> >> blade: bts.2.00 >> err expct: unexpected >> SQL stmt: EXCEPTION >> SQL state: Registration failed for DataBlade module "bts.2.00". >> >> local_on> > > Sounds like you haven't configured an SBSpace for the engine to use. > > -- > Cheers, > Obnoxio The Clown > > http://obotheclown.blogspot.com > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > Yes I had figured that out too; adding an sbspace gets past the issue. Looks like this may be a bug in the new version of the BTS datablade at the very least an omission in the documentation. I've got a case opened with IBM to clarify the situation. Thanks. ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.
Carl: I just checked and BTS 2.0 does require a default Smart Blob space. This missed the release notes, but is a requirement. The reason for this is that BTS 2.0 default location for index is the default smart blob space. John F. Miller III STSM, Support Architect miller3@us.ibm.com 503-578-5645 IBM Informix Dynamic Server (IDS) ids-bounces@iiug.org wrote on 12/08/2008 08:45:52 AM: > Ron, > > You are correct, I just did some testing and it is a bug to me also. I > will be submitting this on your behalf to R & D for an official answer. > > Thanks Carl > > Carl Williams Jr > SWG Client Support - Software > Technical Support Engineer > Phone: 1-913-599-7100 x5260 Internal: 337-5260 > carljr@us.ibm.com > > "Ron MacNeil" <macneil.ron@gmail.com> > Sent by: ids-bounces@iiug.org > 12/08/2008 08:48 AM > Please respond to > ids@iiug.org > > To > ids@iiug.org > cc > > Subject > Re: Unexpected error registering BTS 2.00 data.... [14246] > > On Sat, Dec 6, 2008 at 4:12 AM, Obnoxio The Clown > <obnoxio@serendipita.com> wrote: > > Ron MacNeil wrote: > >> Has anyone else encountered this error when trying to register the BTS > >> datablade? We're trying this in IDS version 11.50.FC3 on Linux. > >> We've recently migrated from version 11.50.FC2 and we first > >> unregistered the BTS database before migrating. > >> > >> # blademgr > >> local_on>register bts.2.00 stores > >> Register module bts.2.00 into database stores? [Y/n] > >> Registering DataBlade module... (may take a while). > >> blademgr: ERROR: DataBlade bts.2.00 could not be registered in database > > >> stores. > >> Use 'show last log' for details of failures in module's scripts. > >> local_on>show last log > >> > >> blade: bts.2.00 > >> err expct: unexpected > >> SQL stmt: execute function SYSBldTstSBSpace(""); > >> SQL state: XU0001:-937 : mi_named_get failed, no such name. > >> > >> blade: bts.2.00 > >> err expct: unexpected > >> SQL stmt: EXCEPTION > >> SQL state: Registration failed for DataBlade module "bts.2.00". > >> > >> local_on> > > > > Sounds like you haven't configured an SBSpace for the engine to use. > > > > -- > > Cheers, > > Obnoxio The Clown > > > > http://obotheclown.blogspot.com > > > > > > > > ******************************************************************************* > > > Forum Note: Use "Reply" to post a response in the discussion forum. > > > > > Yes I had figured that out too; adding an sbspace gets past the issue. > Looks like this may be a bug in the new version of the BTS datablade > at the very least an omission in the documentation. I've got a case > opened with IBM to clarify the situation. > > Thanks. > > > ******************************************************************************* > > Forum Note: Use "Reply" to post a response in the discussion forum. > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. >
In BTS v1.xx, BTS only supported indexes built in an external space (ie in a directory on the file system outside the database). This was an issue for customers that wanted to use the index in an HDR environement (among other things). In IDS 11.50xC3, we included a significant feature to allow BTS indexes to be built in a SmartBlob space as well as maintaining backward compatibility with the extspace option. And bumped the version number to v2.00. BTS 2.00 can now be used in a HDR and Mach11 environment and supports updatable secondaries. With this change, to register BTS 2.00, the server needs the onconfig variable: SBSPACENAME set to an existing SmartBlob space to be configured with a logged default SmartBlob space. This addtional configuration requirment was an omission in the documentation and release notes that R&D is aware of and going to resolve moving forward. Note: BTS 2.00 also included the ability to index XML attribute values. Fair winds, Mark