Check the NLS_LANG variables for the client and the server.
Use the following query to determine the
select nls_language || '_' || nls_territory || '.' || nls_characterset
nls_lang
from
(
select
nl.value nls_language
, nt.value nls_territory
, nc.value nls_characterset
from
nls_database_parameters nl
, nls_database_parameters nt
, nls_database_parameters nc
where nl.parameter = 'NLS_LANGUAGE'
and nt.parameter = 'NLS_TERRITORY'
and nc.parameter = 'NLS_CHARACTERSET'
);
This is likely what should be the correct NLS_LANG
setting for the client.
Or, you can just remove the NLS_LANG variable from the
client environment, and it will default to the database
setting.
The NLS issues can get very complex, but this may suffice.
HTH
Jared
On Mon, 2003-08-18 at 17:03, Ian Jones wrote:
> We've been getting the following error when calling an oracle stored
> procedure (including a bindparam in the call) using DBD-Oracle. The
> error doesn't occur every time. Has anyone seen this before? Is it
> really a character set error, or can it just not output the real error
> text.
>
> Thanks.
>
> DBD::Oracle::st execute failed: ORA-06550: line 39, column 21:
> PLS-00553: character set name is not recognized
> ORA-06550: line 0, column 0:
> PL/SQL: Compilation unit analysis terminated (DBD ERROR: OCIStmtExecute)
> at ascm_wo.cgi line 1370.
