Problem 1 in my person form: hitting ora-1401 (view with check option).

Question

In an earlier stage I had a table PERSON and a table ENSEMBLE.
At some stage I decided it was not handy I was storing performing musicians in two different tables.
So I set up a supertype, CONTRIBUTOR. PERSON is now a view on CONTRIBUTOR.
The attribute IS_NATURAL_PERSON makes the record listed in person.
The view definition is
CREATE OR REPLACE FORCE VIEW "PARTITUREN"."PERSON" ("ID", "FIRST_NAME",
  "MIDDLE_INIT", "LAST_NAME", "GIVEN_NAME", "SORT_KEY", "DISPLAY_VALUE",
  "GENDER", "DATE_OF_BIRTH", "DATE_OF_BIRTH_APPROX", "LOCATION_OF_BIRTH",
  "DECEASED", "DATE_OF_DEATH", "DATE_OF_DEATH_APPROX", "LOCATION_OF_DEATH",
  "NATIONALITY", "ANV_ID", "NUMBERING_SYSTEM", "OPUSNUMBERS", "PORTRAIT",
  "MIME_TYPE", "FILE_NAME", "IS_NATURAL_PERSON", "LWTIMEST", "CREATED_BY",
  "CREATED_TS", "UPDATED_BY", "UPDATED_TS")
AS
  SELECT
    id,
    first_name,
    middle_init,
    last_name,
    given_name,
    sort_key,
    display_value,
    gender,
    date_of_birth,
    date_of_birth_approx,
    location_of_birth,
    deceased,
    date_of_death,
    date_of_death_approx,
    location_of_death,
    nationality,
    anv_id,
    numbering_system,
    opusnumbers,
    portrait,
    mime_type,
    file_name,
    is_natural_person,
    created_ts lwtimest,
    created_by,
    created_ts,
    updated_by,
    updated_ts
  FROM
    contributor
  WHERE
    is_natural_person='Y'
WITH CHECK OPTION;When I enter a record in Apex, I have the is_natural_person attribute default to Y.
However I always hit ora-1401.
It works in sql*developer and sql*plus.
I now always have to resort to non-Gui tools to enter someone. This is nasty.
Oracle 11.2.0.1, Apex 4.0.0.0.46
Sybrand Bakker
Senior Oracle DBA

Answer 1

Hello .
Some NLS charsets (such as UTF8) require more than one byte to store accented characters like "Ȩ", "ȿ", "�", "�", "ȵ", "ȭ" in the database.
For example, when a 10 character string is inserted into a varchar2(10) column, the above messages may be signaled if your string contains accentuated characters such as "Ȩ", "ȿ", "�", �", "ȵ", "ȭ". used in languages like German
One solution
If the UTF8 NLS charset is being used with French, German ... characters in an Oracle database, then the size of the target column length should be set accordingly.
Set the NLS_LANGUAGE and NLS_CHARACTERSET database parameters.
One approach is to change the Database settings as follows:
ALTER DATABASE CHARACTER SET WE8ISO8859P1;
SHUTDOWN IMMEDIATE
Onother
According to the Oracle documentation, column length semantics determine whether the length of a column is specified in bytes or in characters. You use BYTE to specify that the length is in bytes, and you use CHAR to specify that the length is in characters. CHAR length semantics is also known as codepoint length semantics.
Because some character sets require more than one byte for each character, a specification of 10 BYTE for a column might actually store less than 10 characters for certain character sets, but a 10 CHAR specification ensures that the column can store 10 characters, regardless of the character set.
You set the length semantics for an Oracle database using the NLS_LENGTH_SEMANTICS initialization parameter, and all VARCHAR2 and CHAR columns use the setting specified for this initialization parameter as the default. If this initialization parameter is not set, then the default setting is BYTE.
Edited by: Mortus on Jun 28, 2011 2:57 PM