When troubleshooting MAS issues, it is recommended to check windows event log and MAS log . The MAS log files are typically located in "C:\Windows\System32\LogFiles\MAS\" and will correspond to logging level set in the "MAS Configuration" tool.

This article explains the below error generated in MAS log:
---------------------------------------------------------------------------------------
Error in node '0020 Write Spreadsheet to Database':

Oracle bulk load completed with a warning return code. This means that some rows were discarded or rejected, or the load was discontinued. See log for details: D:\Profiles\Users\abc\AppData\Local\Temp\d357ac01-db2d-4660-b717-0342636e201e.log]
------------------------------------------------------------------------------------------

Cause :When a writeback node (included in a scheduled workspace) trying to write a table back to the Oracle database , and if the table violates the column restriction of the database setup, it will result in Oracle errors returned in this referred location (e.g.D:\Profiles\Users\<Username>\AppData\Local\Temp).

For instance, a column in the destination database is set to allow a max value at 100.  Whenever a value larger than 100 is being written back to the database via a WriteBack to Database node, Oracle generates a relevant error log in the Temp folder.
 

Resolution:
1. Go to the folder referred in the MAS error, such as D:\Profiles\Users\abc\AppData\Local\Temp.
2. Open and check the errors indicated in the log file.
3. Correct Oracle related errors.
4.  It is also recommend to regular check and correct the Oracle database issues logged in the Temp folder and clear up those log files timely. Otherwise, log files could pile up Temp folder, which might lead to other unexpected errors/behavior of MAS service.
 

This article walks through an example of troubleshooting Monitoring and Alerting Server (MAS) log error with Writeback to database node involved.