IT28688: UPGRADE TO 10.1.3 OFFLOAD CAN FAIL WITH ERROR "SQLITE3. OPERATIONALERROR: ATTEMPT TO WRITE A READONLY DATABASE"

APAR status

• Closed as program error.

Error description

• After an upgrade to IBM Spectrum Protect Plus 10.1.3 the
  following error can be seen for a cloud offload job in
    the job log:
  
      sqlite3.OperationalError: attempt to write a readonly
      database
  
  IBM Spectrum Protect Plus Versions Affected:
    10.1.3
  Customer/L2 Diagnostics (If Applicable)
    N/A
  
  Initial Impact:
    Low
  Additional Keywords:
    TS002017348 SPP ISPP OFFLOAD COS
  

Local fix

•   The readonly permissions can be fixed locally by simply
    restarting these services on the vSnap server:
  
      sudo systemctl restart vsnap
      sudo systemctl restart vsnap-maint
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * IBM Spectrum Protect Plus level 10.1.3 and 10.1.4.           *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See Error Description                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fixing level when available. This problem is currently *
  * projected to be fixed in IBM Spectrum Protect Plus level     *
  * 10.1.5. Note that this is subject to change at the           *
  * discretion of IBM.                                           *
  ****************************************************************
  

Problem conclusion

• During vSnap startup, multiple services independently start and
  attempt to initialize or upgrade the internal configuration
  database. Depending on the timing and order of service startup,
  the configuration database may be initialized by a more
  privileged service with restricted permissions and thus become
  read-only from the point of a view of a less privileged service.
  The issue has been resolved by improving the timing and ordering
  of startup of vSnap services to ensure that the configuration is
  initialized with the appropriate privileges that make it
  accessible to all vSnap services.
  

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

  SP PLUS

• Fixed component ID

  5737SPLUS

Applicable component levels