Informix - Problem description
Problem IT12614 | Status: Closed |
USING CONNECTION MANAGER FOR AUTOMATIC PROMOTION FROM RSS TO PRIMARY CAN MARK TEMP SMARTBLOB SPACES OFFLINE | |
product: | |
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10 | |
Problem description: | |
When a RSS server gets promoted to a primary during CM controlled failover, an assertion warning can sometimes happen when trying to recreate temporary smart blobspaces which then marks those spaces down/offline. MSGPATH output: 11:00:03 Assert Warning: recreate of temporary sbspsace failed sbsnum:3, err=12120 11:00:03 IBM Informix Dynamic Server Version 12.10.FC6 11:00:03 Who: Session(1, informix@server, 0, 0x44c48028) Thread(7, main_loop(), 44c01028, 8) File: rstbs.c Line: 4878 11:00:03 Results: Downing sbspace. 11:00:03 Action: Please notify IBM Informix Techical Support. 11:00:03 stack trace for pid 15235 written to /tmp/af.3efc692 Stack: 11:00:03 Assert Warning: recreate of temporary sbspsace failed sbsnum:3, err=12120 11:00:03 Who: Session(1, informix@server, 0, 0x44c48028) Thread(7, main_loop(), 44c01028, 8) File: rstbs.c Line: 4878 11:00:03 Results: Downing sbspace. afstack afhandler afwarn_interface recreate_tmpsbspace recreate_all_tmpsbspaces main_loop th_init_initgls startup | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * MACH11 cluster with temporary smartblob spaces during * * failover to standard or primary server. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Update to IBM Informix Server 12.10.xC7 * **************************************************************** | |
Local Fix: | |
Solution | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 04.12.2015 29.06.2016 29.06.2016 |
Problem solved at the following versions (IBM BugInfos) | |
12.10.xC7 | |
Problem solved according to the fixlist(s) of the following version(s) |