SCO Plug-in fails the cg-commit within the actual commit timeout
Applies to
- SnapCenter Server 6.x using ZAPI
- SnapCenter Plug-in for Oracle (SCO) 6.x
- ONTAP 9.16.1
Issue
Oracle backups occasionally run into a cg-commit timeout error during regularly scheduled backups, visible form the SMCore job log:
2026-08-25T23:30:20.4543629+02:00 DEBUG SMCore_15095 PID=[10944] TID=[1030] Command: Invoke-NcSystemApi. Storage System: [IP_ADDR]. Version: NetApp Release 9.16.1P11: Thu Jan 15 11:21:38 UTC 2026. Connection Mode: ZAPI. Username: [USERNAME]2026-08-25T23:30:20.4718673+02:00 DEBUG SMCore_15095 PID=[10944] TID=[1030] ex.Message : The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: Connection timed outThis response came within 17.5 ms of the request !
Note also that this example is showing the time showing in CEST timezone +2:00h)
--
From ONTAP in the mlog\audit.log, we see at the same time (this is showing UTC timezone +0:00h):
Tue Aug 25 2026 21:30:20 +00:00 [kern_audit:info:4154] [traceid:e2aec2b14d175e3a92370f5507f50fe8] 8503e80000581ab6 :: [NODE]:ontapi :: [SNAPCENTER-IP]:[SRC-PORT] :: [SVM-NAME]:[USERNAME] :: <netapp version='1.7' xmlns='http://www.netapp.com/filer/admin' vfiler='[SVM-NAME]'><cg-commit> <cg-id>[CG-PREP-ID]</cg-id> </cg-commit></netapp> :: Pending:Tue Aug 25 2026 21:30:20 +00:00 [kern_audit:info:4154] [traceid:e2aec2b14d175e3a92370f5507f50fe8] 8503e80000581ab6 :: [NODE]:ontapi :: [SNAPCENTER-IP]:[SRC-PORT] :: [SVM-NAME]:[USERNAME] :: cg-commit :: Error: Connection timed outTiming is not as accurate as the SMCore log's timing, but even here the response is sent in the same second as the request arrived.
