IT09779: STORAGE PROBES ARE AFFECTED BY AN SQL -811 EXCEPTION, HENCE NOT PERSISTING NEW INFORMATION INTO THE DATABASE.

APAR status

• Closed as program error.

Error description

• Probes to Storage device fail to persist new data due to DB2 SQL
  Error: SQLCODE=-811, SQLSTATE=21000
  
  dmvSvcTrace.log
  
  2015-06-17 11:59:39.466-0300 HWN099992W SQL Exception while
  persisting properties: {member_id=x, physicalvolumeid=xxxx,
  device_id=x, rpm=, mdisk_id=xx, ref_napi_id=xxx,
  uid=xxxxxxxxxxxxxx, is_solid_state=1, vendor_id=xxxx,
  ref_serviceurl=, node_name=, consolidated_status=0,
  tech_type=sas_ssd, operational_status=4, mdisk_name=mdisk21,
  firmware_rev=GB6Y, name=5, discovered_time=2015-06-17
  11:59:39.462, node_id=, enclosure_id=xx,
  fru_identity=xxxxxxxxxxxxxxxxxxxxxxx,
  product_id=xxxxxxxxxxxxxxxxxxxxxxxx, port_1_status=online,
  disk_type=4, flags=0, ref_namespace=, fpga_level=,
  update_timestamp=2015-06-17 11:59:39.464, port_2_status=online,
  firmware_level=GB6Y, device_type=DSRA_SVC,
  capacity=xxxxxxxxxxxxx, status=1,
  serial_number=xxxxxxxxxxxxxxxxxxxxxxxxxxx, ref_classname=ldisk,
  detectable=1, fru_part_number=85Y6189, id=5, block_size=512,
  physical_volume_id=9641719, display_name=5,
  job_logger=com.ibm.tpc.disk.common.log.LogTraceHelper@2938fdd1,
  storageextentid=xxxxxxxxxxxxxx, model_id=xxxx,
  subsystem_id=xxxx, tag=20, quorum_id=, section name=ldisk,
  use=member, svc_key_metadata=1, start_time=Wed Jun 17 11:59:07
  BRT 2015, slot_id=19, ref_system_names_id=1004,
  error_sequence_number=}@(-9223372036837974743;[-9223372036836765
  612,0,4];-9223372036836765353;Process Processor
  (Thread-416051))   com.ibm.tpc.disk.collection.DiskCIMProcessor
  persist
  2015-06-17 11:59:39.467-0300 HWN099993E DB2 SQL Error:
  SQLCODE=-811, SQLSTATE=21000, SQLERRMC=null, DRIVER=3.62.56
  @(-9223372036837974743;[-9223372036836765612,0,4];-9223372036836
  765353;Process Processor (Thread-416051))
  com.ibm.db2.jcc.am.SqlException: DB2 SQL Error: SQLCODE=-811,
  SQLSTATE=21000, SQLERRMC=null, DRIVER=3.62.56
  at com.ibm.db2.jcc.am.fd.a(fd.java:679)
  at com.ibm.db2.jcc.am.fd.a(fd.java:60)
  at com.ibm.db2.jcc.am.fd.a(fd.java:127)
  at com.ibm.db2.jcc.am.jn.b(jn.java:2299)
  at com.ibm.db2.jcc.am.jn.c(jn.java:2282)
  at com.ibm.db2.jcc.t4.cb.k(cb.java:370)
  at com.ibm.db2.jcc.t4.cb.a(cb.java:62)
  at com.ibm.db2.jcc.t4.q.a(q.java:50)
  at com.ibm.db2.jcc.t4.sb.b(sb.java:220)
  at com.ibm.db2.jcc.am.kn.lc(kn.java:3077)
  at com.ibm.db2.jcc.am.kn.b(kn.java:4034)
  at com.ibm.db2.jcc.am.kn.dc(kn.java:746)
  at com.ibm.db2.jcc.am.kn.executeUpdate(kn.java:729)
   at
  com.ibm.tpc.infrastructure.database.DBPreparedStatement.executeU
  pdate(DBPreparedStatement.java:261)
  at
  com.ibm.tpc.infrastructure.mapping.CLISVC6_LDiskToPhysicalVolume
  DBMapper.persistDiskGroupIDForLDisk(CLISVC6_LDiskToPhysicalVolum
  eDBMapper.java:330)
  at
  com.ibm.tpc.infrastructure.mapping.CLISVC6_LDiskToPhysicalVolume
  DBMapper.persist(CLISVC6_LDiskToPhysicalVolumeDBMapper.java:272)
  at
  com.ibm.tpc.disk.collection.DiskCIMProcessor.persist(DiskCIMProc
  essor.java:1868)
  at
  com.ibm.tpc.discovery.parser.NAPI_DS_SVC_Parser.persistEntity(NA
  PI_DS_SVC_Parser.java:295)
  at
  com.ibm.tpc.discovery.parser.NAPI_DS_SVC_Parser.processOutputFil
  e(NAPI_DS_SVC_Parser.java:223)
  at
  com.ibm.tpc.disk.discovery.SVC_CLI_PostProcess.parse(SVC_CLI_Pos
  tProcess.java:87)
  at
  com.ibm.tpc.disk.discovery.NAPIProbePostProcess.process(NAPIProb
  ePostProcess.java:384)
  at com.ibm.tpc.Router.perform(Router.java:1077)
  at com.ibm.tpc.Router.perform(Router.java:599)
  at
  com.ibm.tpc.discovery.ProcessProcessor.process(ProcessProcessor.
  java:69)
  at
  com.ibm.tpc.infrastructure.threads.TPCThread.run(TPCThread.java:
  258)com.ibm.tpc.disk.collection.DiskCIMProcessor persist
  
  RECREATE STEPS:
  Probe Device and view reports after name changes to device data.
  
  Problem as described by customer:
  Renamed v7k vdisks do not display correct name in TPC WEB GUI
  
  Initial customer impact: Med
  

Local fix

• Contact Support
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * TPC 5.2.x running storage probes                             *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See ERROR DESCRIPTION for DB2 SQL error.                     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fix maintenance when available.                        *
  ****************************************************************
  

Problem conclusion

• The fix for this APAR is targeted for the following maintenance
  package:
  
  | refresh pack | 5.2-TIV-TPC-RP0007 - target August 2015
  
  http://www-01.ibm.com/support/docview.wss?&uid=swg21320822
  
  The target dates for future refresh packs do not represent a
  formal commitment by IBM. The dates are subject to change
  without notice.
  

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:

Modules/Macros

• PROBE
  

Fix information

• Fixed component name

  TPC

• Fixed component ID

  5608TPC00

Applicable component levels

• R520 PSY

     UP

• R526 PSY

     UP