Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 3 results
    • https://kb.netapp.com/data-mgmt/SnapCenter/SC_KBs/SnapCenter_Custom_Plug-Ins_backups_fail_with_could_not_read_result_file
      Using a sudoers account (a.k.a. <LINUX_USER> from the oracle_checksum.txt file) for deployment Perl based plug-ins from the Automation Store and the SC Server provided Storage 2.0 Plug-in (*) When per...Using a sudoers account (a.k.a. <LINUX_USER> from the oracle_checksum.txt file) for deployment Perl based plug-ins from the Automation Store and the SC Server provided Storage 2.0 Plug-in (*) When performing a SCC backup operation it fails with the error SCC-00161: Application unquiesce for the plug-in [plug-in name] failed with exit code [1] and error : Could not read result file /opt/NetApp/snapcenter/scc/plugins/wrapper/out/1+<PLUGIN>+<WRAPPER_ID>+quiesce (Permission denied)
    • https://kb.netapp.com/data-mgmt/SnapCenter/SC_KBs/Sybase_CT-LIBRARY_connection_error_with_SnapCenter_Creator_Plug-in
      Applies to SnapCenter 4.x SnapCenter Sybase Plug-in from the Automation Store Issue Running a backup with a Sybase resource group, fails the ISQL connection as seen in the SYBASE_<job>.log: SCC-00164:...Applies to SnapCenter 4.x SnapCenter Sybase Plug-in from the Automation Store Issue Running a backup with a Sybase resource group, fails the ISQL connection as seen in the SYBASE_<job>.log: SCC-00164: Application quiesce for plug-in [SYBASE] failed with exit code [255] and with error : Msg 4002, Level 14, State 1: Server '<SID>': Login failed. CT-LIBRARY error: ct_connect(): protocol specific layer: external error: The attempt to connect to the server failed.
    • https://kb.netapp.com/data-mgmt/SnapCenter/SC_KBs/SnapCenter_backup_for_Sybase_database_plugin_randomly_fails
      YYYY/MM/DD hh:mm:ss server Processes trying to issue an I/O operation on the quiesced database(s) will be suspended until the user executes a QUIESCE DATABASE command with the RELEASE option. YYYY/MM/...YYYY/MM/DD hh:mm:ss server Processes trying to issue an I/O operation on the quiesced database(s) will be suspended until the user executes a QUIESCE DATABASE command with the RELEASE option. YYYY/MM/DD hh:mm:ss server QUIESCE DATABASE: Waiting for at least one transaction (owner spid XXX) in the 'master' database to complete. YYYY/MM/DD hh:mm:ss server Process YYYY is aborted by 'QUIESCE DATABASE as transactions in the 'master' database did not finish within the prescribed time limit.