Home » RDBMS Server » Server Administration » OIP-04109
OIP-04109 [message #369403] Thu, 14 September 2000 03:30 Go to next message
Alex
Messages: 190
Registered: August 1999
Senior Member
Does anyone know how OIP assigns the file names of the temporary files. They seem to stop at oipsr999. Do they then recycle starting from oipsr1 or will you get an OIP-04109 error after oipsr999. (I have not seen a number higher than 999).
Thanks.
Re: OIP-04109 [message #369575 is a reply to message #369403] Fri, 27 October 2000 03:59 Go to previous messageGo to next message
sim, kyubok
Messages: 1
Registered: October 2000
Junior Member
This is an "OLE Automation Errors" and I found it on "Oracle Object for OLE Help : ver 4.10.1998"

//Followings are quoted;
The programmatic interface of the Oracle Object Server is the OO4O In-Process Automation server. Errors that occur during execution of methods are frequently reported simply as an OLE Automation Error (ERR = 440, ERROR$ ="OLE Automation Error").

When these error occur, check the LastServerErr property of the OraSession and OraDatabase objects to determine whether an Oracle database error has occurred. If LastServerErr is non-zero, then an error has been raised by the Oracle Object Server.

To find the Oracle Object Server Error, scan the string returned by the ERROR$ function for the string "OIP-NNNN" where NNNN is an error number included in the following table.

... ommitted

Constant :OERROR_TEMPFILE
Value :4109
Description:
An error occurred while trying to create a temporary file for data caching.

// unquoted

I also met OIP error 4099 but cannot found suitable help before when i lookup above mentioned help file. Why they inform me the error message with keyword "OIP". It made me more confused to solve this problem.
Anyway I feel again that "the solution is always near my back."

-bye-
Re: OIP-04109 [message #369576 is a reply to message #369575] Fri, 27 October 2000 04:12 Go to previous message
Alex
Messages: 190
Registered: August 1999
Senior Member
Hi Sim
Thanks for that. Your 4099 is probably caused by referencing a field in the result set that does not exist - possibly a typo.
Regards.
Previous Topic: slow insert statement
Next Topic: DBMS_SQL package - HELP
Goto Forum:
  


Current Time: Sat Apr 27 05:10:27 CDT 2024