Database Out of DiskspaceDatabase Out of Diskspace

What

If the cron jobs seem to have stopped generating job log entries this indicates that you probably ran out of diskspace on your database.

Why

It does not happen often, but you might have run out of diskspace. 
An indication of this could be that you can't upload files or you job log entries are missing:

• Check the job log. there will be logs registered but no data beside the notion of a start and duration time
• Check that you see the same pattern on some of the other cron jobs.

How

• To verify that this issue is because you are out of diskspace there are two methods:
  • Fetch console.log and look for errors stating:

Unable to save audit log entry 

unable to extend table 

ORA-01653: unable to extend table PUREDATA.JOB_LOG_LOG_ENTRY by 8192 in tablespace 

ORA-01653: unable to extend table PURE_OWNER.JOB_LOG_LOG_ENTRY by 8192 in tablespace 

• If it's not possible to fetch the console.log. Check free space left in the database.
  • It can be verified by querying the data dictionary for free temp space with this:

select TABLESPACE_NAME, BYTES_USED, BYTES_FREE
        from V$TEMP_SPACE_HEADER 

• To solve the issue, you'll need to extend the tablespace that Pure is using, and maybe add more diskspace if that is also needed.
• If this problem only occurs on a Staging instance, you can instead consider to delete the database entirely and then make a new copy from Production, if Production takes up less space.
• It is also recommend to run the job named Prune Job Log Entries that will cleanup old job logs. 

More information

KB-263 Job Log Clean Up 
Note: Some of this information is for internal use only and might not be accessible.