FRM-41839 ERROR WHEN TRYING TO VIEW THE LAST RECORD [ID 969646.1]
Information in this document applies to any platform.
***Comment Implemented on 27-DEC-2010***
Comments
--------
=== Question ===
User was trying to go down to the last record from a screen and he got and FRM-41839 error. Checked the TMPDIR (/tmp) has a lot of space and the file size setting is unlimited, but he still got that error.
Please advise
Comments
--------
=== Answer ===
From Bug.6652844 EXPORT AND VIEW LAST RECORD FAIL WITH, FRM-41839 DISK I/O ERROR ON TEMPORARY RE
Development have confirmed that they will not supply a fix for the issue as the root cause of the problem is a physical limitation of the export functionality and the way the developer code works. I think that any fix would involve a major re-write of the either the export or developer code.
The problem is that export was not designed for extracting large amounts of data because it consumes so much system resource to do it (imagine 100 users creating a 2Gb file each and the amount of network and server resource that would take)
However if this much data is required, and you have a valid requirement, then we must offer you some alternate functionality (i.e. report or concurrent job) however the solution will not be a change to the export functionality.
Applies to:
Oracle Project Costing - Version: 11.5.10.2 to 11.5.10.2 - Release: 11.5.10 to 11.5.10Information in this document applies to any platform.
***Comment Implemented on 27-DEC-2010***
Goal
Comments
--------
=== Question ===
User was trying to go down to the last record from a screen and he got and FRM-41839 error. Checked the TMPDIR (/tmp) has a lot of space and the file size setting is unlimited, but he still got that error.
Please advise
Solution
Comments
--------
=== Answer ===
From Bug.6652844 EXPORT AND VIEW LAST RECORD FAIL WITH, FRM-41839 DISK I/O ERROR ON TEMPORARY RE
Development have confirmed that they will not supply a fix for the issue as the root cause of the problem is a physical limitation of the export functionality and the way the developer code works. I think that any fix would involve a major re-write of the either the export or developer code.
The problem is that export was not designed for extracting large amounts of data because it consumes so much system resource to do it (imagine 100 users creating a 2Gb file each and the amount of network and server resource that would take)
However if this much data is required, and you have a valid requirement, then we must offer you some alternate functionality (i.e. report or concurrent job) however the solution will not be a change to the export functionality.
No comments:
Post a Comment