Error while uploading attachments – "Unable to communicate with the server. Saving is not possible at the moment"
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
Users are unable to upload attachments to Confluence pages and get the error – "Unable to communicate with the server. Saving is not possible at the moment"
Environment
Confluence Server or Data Center
Oracle Database
Diagnosis
The issue is seen for all types of attachment files.
The issue is also seen irrespective of the file size.
The following error is observed in the Confluence application logs (under the
<Confluence-Home>/logs/atlassian-confluence.log)1 2 3 4ERROR [http-nio-8090-exec-1] [rest.api.model.ExceptionConverter] convertServiceException No status code found for exception, converting to internal server error : -- referer: http://example.com:8090/pages/resumedraft.action?draftId=44793881&draftShareId=ab2080bf-487f-4b94-8042-784f7538f86a& | url: /rest/api/content/44793880 | traceId: 7478e55292d6f17b | userName: externo2258 org.springframework.orm.hibernate5.HibernateJdbcException: JDBC exception on Hibernate data access: SQLException for SQL [n/a]; SQL state [64000]; error code [1157]; could not execute statement; nested exception is org.hibernate.exception.GenericJDBCException: could not execute statement ... ... Caused by: java.sql.SQLException: ORA-01157: cannot identify/lock data file 201 - see DBWR trace file ORA-01110: data file 201: '+CONFDB_DATA/CONFDB/temp01.dbf' ... Caused by: Error : 1157, Position : 0, Sql = update BODYCONTENT set BODY=:1 , CONTENTID=:2 , BODYTYPEID=:3 where BODYCONTENTID=:4 , OriginalSql = update BODYCONTENT set BODY=?, CONTENTID=?, BODYTYPEID=? where BODYCONTENTID=?, Error Msg = ORA-01157: cannot identify/lock data file 201 - see DBWR trace file ORA-01110: data file 201: '+CONFDB_DATA/CONFDB/temp01.dbf'
Cause
Quoting the Oracle docs about the error code ORA-01157: cannot identify/lock data file 201 - see DBWR trace file:
Cause: The background process was either unable to find one of the data files or failed to lock it because the file was already in use.
The database will prohibit access to this file but other files will be unaffected. However the first instance to open the database will need to access all online data files. Accompanying error from the operating system describes why the file could not be identified.
Action: Have operating system make file available to database. Then either open the database or do ALTER SYSTEM CHECK DATAFILES.
Solution
The '+CONFDB_DATA/CONFDB/temp01.dbf' datafile (as seen in the error above) is locked. Please consult your Oracle DBA to make sure '+CONFDB_DATA/CONFDB/temp01.dbf' is unlocked and accessible.
Was this helpful?