PI92936: BIG SQL TOPOLOGY CHANGES MAY FAIL WITH RANGER PLUGIN ENABLED

APAR status

• Closed as fixed if next.

Error description

• Starting in Big SQL version 5.0.2, any attempt to call
  syshadoop.big_sql_service_mode will fail if the Big SQL plugin
  for Ranger is enabled.  This may affect topology changes such
  as ADD WORKER and DROP WORKER as well as autoconfigure and
  other maintenance operations.
  To identify this error, search for error SQL0727N in the
  /tmp/bigsql/logs log files that correspond to the operation
  being performed. When performing an operation such as ADD
  WORKER or DROP WORKER, check log files on both the worker host
  and the Big SQL head host. The error will look similar to this:
  SQL0727N  An error occurred during implicit system action type
  "5".
  Information returned for the error includes SQLCODE "-707",
  SQLSTATE "42939"
  and message tokens "SYSPSM_SYSHADOOP_P63188929_3".
  SQLSTATE=56098
  2018-01-17.07:37:58.270 @ Line(01169) @ Fun
  switchToServiceMode: ..Failed to switch service mode with rc=[4]
  Specifically, an SQL0727N with nested sqlcode -707.
  Contact IBM support to gain access to the latest service stream
  patch for your version of Big SQL. Once the patch has been
  applied, run
  db2 "CALL SYSPROC.SYSINSTALLOBJECTS('BIGSQL', 'C', CAST (NULL
  AS VARCHAR(128)), CAST (NULL AS VARCHAR(128)))"
  to rebuild the syshadoop.big_sql_service_mode procedure.
  

Local fix

• Until a fix is available, to work around this problem you
  should disable the Big SQL plugin for Ranger, perform the
  topology change, then enable the Ranger plugin again. You
  should export your Ranger policies before disabling the plugin,
  so that you can import them again after enabling.
  

Problem summary

• Please see problem decription.
  

Problem conclusion

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

Applicable component levels