note 79919 modified in ref.oci8 by sixd
| From: | sixd@php.net | Date: | Thu, 10 Apr 2008 22:37:58 +0000 |
| Subject: | note 79919 modified in ref.oci8 by sixd | ||
| References: | 1 | Groups: | php.notes |
| Request: | Send a blank email to php-notes+get-138169@lists.php.net to get a copy of this message | ||
Do not underestimate the importance of NLS_LANG in your environment.
The Oracle error "ORA-03106: fatal two-task communication protocol error" is indicative of
not having NLS_LANG set.
In my case, I had a successfully processing INSERT statement followed by a failing SELECT statement
that was resulting in that ORA-03106 error. The successful INSERT implied that all Oracle
environment settings were fine. Ultimately we found that the NLS_LANG was not set, and I have to
assume that only the SELECT of data back from the database actually _needed_ it, and therefore it
was the SELECT statement that triggered the failure. Though, that is all speculation.
--was--
Do not underestimate the importance of NLS_LANG in your environment.
The Oracle error "ORA-03106: fatal two-task communication protocol error" is indicative of
not having NLS_LANG set.
In my case, I had a successfully processing INSERT statement followed by a failing SELECT statement
that was resulting in that ORA-03106 error. The successful INSERT implied that all Oracle
environment settings were fine. Ultimately we found that the NLS_LANG was not set, and I have to
assume that only the SELECT of data back from the database actually _needed_ it, and therefore it
was the SELECT statement that triggered the failure. Though, that is all speculation.
http://php.net/manual/en/ref.oci8.php