Also check your client settings. Often problems go away when the client and
database parameter settings simply match. This may also have NOTHING to do
with your problem, but it is worth a look.
mwf
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]
On Behalf Of Reen, Elizabeth (Redacted sender "elizabeth.reen" for DMARC)
Sent: Wednesday, May 10, 2017 11:03 AM
To: 'MAdams@xxxxxxxxxx'; oracle-l@xxxxxxxxxxxxx
Subject: RE: fun with character sets
You could have a non printing character in there. I had a
problem 10 years ago with non printing characters and the move from one
instance to another. I don't remember the details, but I remember going
crazy with it.
Liz
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]
On Behalf Of Matt Adams
Sent: Wednesday, May 10, 2017 9:37 AM
To: oracle-l@xxxxxxxxxxxxx
Subject: RE: fun with character sets
Thanks for the quick reply.
Oracle Support (Long Live Metalink!) was my first stop. I agree that the
first doc you listed has no real useful information and the RMAN one was not
releveant. I've been searching he formsweb.cfg and default.env config
files on our forms server, trying to see where anything releated to
character sets might be located. No luck so far, but I'm not the expert
with that technology. I'm hoping the other DBA will be able to point me in
the right direction when she gets in this morning.
To me, the real question is..why does the app seem to be converting between
char and nchar character sets (at least that's what the error message says
it is doing) when there are no NCHAR columns in the application tables.
Matt
From: Powell, Mark [mailto:mark.powell2@xxxxxxx] ;
Sent: Wednesday, May 10, 2017 9:24 AM
To: oracle-l@xxxxxxxxxxxxx; Matt Adams
Subject: Re: fun with character sets
If you have access to Oracle support I found a couple of notes on the
subject. The first is very generic but the second even though it was
related to rman was actually a script parameter passing error, rather than
rman itself, so depending on what your login screen does may apply. The
third note is a Report problem but the cause being a setting in Reports.sh
made me question if Forms has a similar config file.
- -
OERR: ORA-12713 "Character data loss in NCHAR/CHAR conversion" Reference
Note (Doc ID 172617.1)
ORA-12713 Character data loss in NCHAR/CHAR conversion during RMAN Backup
(Doc ID 2207886.1)
ORA-12713 Running a Report on Unix Environment (Doc ID 1627746.1)
- -
Mark Powell
Database Administration
(313) 592-5148
_____
From: oracle-l-bounce@xxxxxxxxxxxxx <oracle-l-bounce@xxxxxxxxxxxxx> on
behalf of Matt Adams <MAdams@xxxxxxxxxx>
Sent: Wednesday, May 10, 2017 9:05:40 AM
To: oracle-l@xxxxxxxxxxxxx
Subject: fun with character sets
I've created a new dev environment for one of our systems.
The old system used we8iso8859p1 / al16utf16 for the character set and
NCHAR character set.
The new system uses AL32UTF8 / al16utf16 for the character set and NCHAR
character set
Both DBs are version 11.2.0.4 on Solaris 10
The application is written in Forms and the same app tier (web logic, forms
server, etc) is used to access both databases.
On the new system, the login screen is returning ORA-12713
oerr ora 12713
12713, 00000, "Character data loss in NCHAR/CHAR conversion"
// *Cause: When character set conversion happens between CHAR and NCHAR
// either implicitly or explicitly, some characters are lost
// due to no mapping characters in the destination character set.
// *Action: Make sure all the characters can be mapped to destination
//
I've checked the application tables and NONE of them have any columns of
type NCHAR or NVARCHAR or NCLOB.
The NLS_NCHAR_CONV_EXP parameter is set to FALSE on both systems.
I can't figure out why this error is being thrown. I can't even figure out
why the app is appearing to try to convert from the normal character set to
the nchar character set (or vice versa) when none of the application tables
use those data types.
Anyone have any helpful thoughts?
**** This communication may contain privileged and/or confidential
information. If you are not the intended recipient, you are hereby notified
that disclosing, copying, or distributing of the contents is strictly
prohibited. If you have received this message in error, please contact the
sender immediately and destroy any copies of this document. ****
**** This communication may contain privileged and/or confidential
information. If you are not the intended recipient, you are hereby notified
that disclosing, copying, or distributing of the contents is strictly
prohibited. If you have received this message in error, please contact the
sender immediately and destroy any copies of this document. ****
