Compare client errors out with ORA-01114 (4302607)

Compare client errors out with ORA-01114

The following errors are observed in target event log when compare/repair is run on a table:

Notice   2017-04-03 04:29:58.523911 32375112 1 Compare client: Opened DataEquator client session log file /shareplex/vardir/log/declt_636-1_server_name_nnn.nnn.nn.nn_p32375112.log  [sp_declt] [module deq]

Error    2017-04-03 04:34:43.134833 32375112 1 Compare client: Oracle Error 12801: ORA-12801: error signaled in parallel query server P001.ORA-01114: IO error writing block to file 201 (block # 2525696).ORA-27063: number of bytes read/written is incorrect.IBM AIX RISC System/6000 Error: 28: No space left on device.Additional information: -1.Additional information: 253952.ORA-01114: IO error writing block to file 201 (block # 2525789).ORA-27063: number of bytes read/written is incorrect.IBM AIX RISC System/6000 Error: 28: No space left on device.Additional information: -1.Additional infor  [sp_declt] [module deq]

Error    2017-04-03 04:34:44.242359 9568264 1 Compare client: Error 1 in de_batch_setup see declt_636-1_server_name_nnn.nnn.nn.nn _p9568264  [sp_declt] [module deq]

Info     2017-04-03 04:34:44.476871 44695654 1 Compare client exited normally, pid = 9568264  [sp_declt]

Disk space is full

The ORA-01114 typically shows up when the disk is full. To resolve the issue, add more space to the device housing the variable directory or clean up some unwanted files (typically log files) from it.

Once the space has been reclaimed, run another compare/repair.

Please refer to our Knowledgebase article #s 39886 and 1700 for details on dealing with disk full issues by moving the variable directory to a different device or adding more space to it. 

Though the above error message are shown for an AIX environment, it can also occur for other Unix flavors. Here is the description of the error: ORA-01114: IO error writing block to file string (block # string) Cause: The device on which the file resides is probably offline. If the file is a temporary file, then it is also possible that the device has run out of space. This could happen because disk space of temporary files is not necessarily allocated at file creation time. Action: Restore access to the device or remove unnecessary files to free up space.