Re: note 79919 modified in oci8.setup by sixd
| From: | Thiago H. Pojda | Date: | Fri, 26 Jun 2009 19:09:29 +0000 |
| Subject: | Re: note 79919 modified in oci8.setup by sixd | ||
| References: | 1 2 | Groups: | php.notes |
| Request: | Send a blank email to php-notes+get-157613@lists.php.net to get a copy of this message | ||
What's up with these edits? I diff'ed them and got nothing.
Thiago Henrique Pojda
http://nerdnaweb.blogspot DOT com
On Fri, Jun 26, 2009 at 3:48 PM, <sixd@php.net> wrote:
> 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/oci8.setup.php
>
> --
> PHP Notes Mailing List (http://www.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>