IT29272: TEMP DBSPACE CHUNKS NOT RE-CREATED AT RESTART ON SECONDARIES

APAR status

• Closed as program error.

Error description

• On a primary or standard server, temporary dbspaces would get
  re-initialized during restart, potentially even re-created if in
  some bad state, e.g. down or zero size files.
  
  On a secondary this wouldn't occur, so a temp dbspace could be
  unavailable there even though its chunks physically exist and
  meet all requirements.
  
  Where this can particularly bite you is when newly initializing
  a secondary, through physical restore and 'onmode -d
  secondary|RSS', and this initial primary-server connection isn't
  successful in such a way that the secondary will go down (e.g.
  certain onconfig mismatch). Despite unsuccessful connection, the
  secondary now is a secondary.
  The physical restore will not have done anything about temporary
  dbspaces (with T flag), so if a chunk under such dbspace would
  have been a zero size file, or a file with some old non-fitting
  content, it will be unchanged, yet upon restart this dbspace and
  its chunks will now be expected to be 'sane', fail chunk sanity
  check and be down forever.
  

Local fix

• Such dbspace had to be dropped and recreated on the primary in
  order to make it available again on the secondary.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Users of Informix Server prior to 12.10.xC15 and 14.10.xC6.  *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See Error Description                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Upgrade to Informix Server 12.10.xC15 (when available) or    *
  * 14.10.xC6 (when available).                                  *
  ****************************************************************
  

Problem conclusion

• Fixed in Informix Server 12.10.xC15 and 14.10.xC6.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  INFORMIX SERVER

• Fixed component ID

  5725A3900

Applicable component levels