ORA-12899,database error

Hi,
iam getting error "ORA-12899,database error"while running workflow in informatica. Actually am getting this error at the time of data loading. I know the solution that is incresing datatype size but i dont have permissions to change the length for target database, my source is flatfil(fixed width), and i tried by putting substring for particular field but that one is not working..
actually the data is "sicav a échéance / vervallen sicav = QUE DES V/ENKEL V" in error am getting actual size:58 maximum:55,i calculatd the length of the data taht one 54 only,my field length is 55....am not understanding wat is the problem......can anybody please help me

You could chop you data in two, load both records, then see what the total length is in the DB? I can't see why you are getting 4 extra characters

Similar Messages

ORA-12899 mapping error

Hello!
I have only just started to work with OWB and I'm trying to build the staging area for our data warehouse. I've done mappings for all the necessary tables and each time I try to run the mapping I encounter the following error.
Warning
ORA-12899: liian suuri arvo sarakkeelle (nykyinen arvo: , enimmäisarvo: )
Warning
ORA-06502: PL/SQL: numeerinen virhe tai arvovirhe : Bulk Bind: Truncated Bind
Warning
CursorFetchMapTerminationRTV20007
Don't mind the finnish language, the error codes should speak for themselves. Note however that the warning doesn't even mention which field is in question. On some tables it DOES give me the field name in the error message and says that the "current length" is for example 33 and the max length is 30. The field length is copied exactly from the source table in the mapping. I've checked and double checked it. This problem can be circumvented by enlarging the target table field length and then the mapping runs fine. But when I afterwards look for any values that have a length of 33, I can't find them. All values where under 30 as they should be.
Then on some tables I get the error I've pasted to the top. It doesn't even mention the field in question so I'm having a hard time fixing this. In any case I don't want to have to enlarge the targe table field lengths just to get the data in.
Is this a bug or have I done something wrong perhaps? Any help would be most appreciated.
Versions:
OWB Client: 10.2.0.2.8
Repository: 10.2.0.2.0 (problem? DBA said there was a problem patching this)
Source DB: Oracle 9i
Target DB: Oracle 10g
Regards,
Erik

Hey!
No I am not using a view or a procedure in the mapping, if I understood you correctly. It's an extremely simple mapping where I move the source data straight from the operative system to the target table. I believe this happens via database links. Or at least I think so judging by the PL/SQL generated by the OWB.
The error is limited to VARCHAR2-fields. I'm guessing it might have something to do with scandic letters and/or umlauts and such.
Thanks anyways for your answer.

SQL Error: ORA-12899: value too large for column

Hi,
I'm trying to understand the above error. It occurs when we are migrating data from one oracle database to another:
Error report:
SQL Error: ORA-12899: value too large for column "USER_XYZ"."TAB_XYZ"."COL_XYZ" (actual: 10, maximum: 8)
12899. 00000 - "value too large for column %s (actual: %s, maximum: %s)"
*Cause:    An attempt was made to insert or update a column with a value
which is too wide for the width of the destination column.
The name of the column is given, along with the actual width
of the value, and the maximum allowed width of the column.
Note that widths are reported in characters if character length
semantics are in effect for the column, otherwise widths are
reported in bytes.
*Action:   Examine the SQL statement for correctness. Check source
and destination column data types.
Either make the destination column wider, or use a subset
of the source column (i.e. use substring).
The source database runs - Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
The target database runs - Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
The source and target table are identical and the column definitions are exactly the same. The column we get the error on is of CHAR(8). To migrate the data we use either a dblink or oracle datapump, both result in the same error. The data in the column is a fixed length string of 8 characters.
To resolve the error the column "COL_XYZ" gets widened by:
alter table TAB_XYZ modify (COL_XYZ varchar2(10));
-alter table TAB_XYZ succeeded.
We now move the data from the source into the target table without problem and then run:
select max(length(COL_XYZ)) from TAB_XYZ;
-8
So the maximal string length for this column is 8 characters. To reduce the column width back to its original 8, we then run:
alter table TAB_XYZ modify (COL_XYZ varchar2(8));
-Error report:
SQL Error: ORA-01441: cannot decrease column length because some value is too big
01441. 00000 - "cannot decrease column length because some value is too big"
*Cause:
*Action:
So we leave the column width at 10, but the curious thing is - once we have the data in the target table, we can then truncate the same table at source (ie. get rid of all the data) and move the data back in the original table (with COL_XYZ set at CHAR(8)) - without any issue.
My guess the error has something to do with the storage on the target database, but I would like to understand why. If anybody has an idea or suggestion what to look for - much appreciated.
Cheers.

843217 wrote:
Note that widths are reported in characters if character length
semantics are in effect for the column, otherwise widths are
reported in bytes.You are looking at character lengths vs byte lengths.
The data in the column is a fixed length string of 8 characters.
select max(length(COL_XYZ)) from TAB_XYZ;
-8
So the maximal string length for this column is 8 characters. To reduce the column width back to its original 8, we then run:
alter table TAB_XYZ modify (COL_XYZ varchar2(8));varchar2(8 byte) or varchar2(8 char)?
Use SQL Reference for datatype specification, length function, etc.
For more info, reference {forum:id=50} forum on the topic. And of course, the Globalization support guide.

I am getting error "ORA-12899: value too large for column".

I am getting error "ORA-12899: value too large for column" after upgrading to 10.2.0.4.0
Field is updating only through trigger with hard coded value.
This happens randomly not everytime.
select * from v$version
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
PL/SQL Release 10.2.0.4.0 - Production
CORE     10.2.0.4.0     Production
TNS for Linux: Version 10.2.0.4.0 - Production
NLSRTL Version 10.2.0.4.0 - Production
Table Structure
desc customer
Name Null? Type
CTRY_CODE NOT NULL CHAR(3 Byte)
CO_CODE NOT NULL CHAR(3 Byte)
CUST_NBR NOT NULL NUMBER(10)
CUST_NAME CHAR(40 Byte)
RECORD_STATUS CHAR(1 Byte)
Trigger on the table
CREATE OR REPLACE TRIGGER CUST_INSUPD
BEFORE INSERT OR UPDATE
ON CUSTOMER FOR EACH ROW
BEGIN
IF INSERTING THEN
:NEW.RECORD_STATUS := 'I';
ELSIF UPDATING THEN
:NEW.RECORD_STATUS := 'U';
END IF;
END;
ERROR at line 1:
ORA-01001: invalid cursor
ORA-06512: at "UPDATE_CUSTOMER", line 1320
ORA-12899: value too large for column "CUSTOMER"."RECORD_STATUS" (actual: 3,
maximum: 1)
ORA-06512: at line 1
Edited by: user4211491 on Nov 25, 2009 9:30 PM
Edited by: user4211491 on Nov 25, 2009 9:32 PM

SQL> create table customer(
2 CTRY_CODE CHAR(3 Byte) not null,
3 CO_CODE CHAR(3 Byte) not null,
4 CUST_NBR NUMBER(10) not null,
5 CUST_NAME CHAR(40 Byte) ,
6 RECORD_STATUS CHAR(1 Byte)
7 );
Table created.
SQL> CREATE OR REPLACE TRIGGER CUST_INSUPD
2 BEFORE INSERT OR UPDATE
3 ON CUSTOMER FOR EACH ROW
4 BEGIN
5 IF INSERTING THEN
6 :NEW.RECORD_STATUS := 'I';
7 ELSIF UPDATING THEN
8 :NEW.RECORD_STATUS := 'U';
9 END IF;
10 END;
11 /
Trigger created.
SQL> insert into customer(CTRY_CODE,CO_CODE,CUST_NBR,CUST_NAME,RECORD_STATUS)
2                values('12','13','1','Mahesh Kaila','UPD');
              values('12','13','1','Mahesh Kaila','UPD')
ERROR at line 2:
ORA-12899: value too large for column "HPVPPM"."CUSTOMER"."RECORD_STATUS"
(actual: 3, maximum: 1)
SQL> insert into customer(CTRY_CODE,CO_CODE,CUST_NBR,CUST_NAME)
2                values('12','13','1','Mahesh Kaila');
1 row created.
SQL> set linesize 200
SQL> select * from customer;
CTR CO_   CUST_NBR CUST_NAME                                R
12 13           1 Mahesh Kaila                             I
SQL> update customer set cust_name='tst';
1 row updated.
SQL> select * from customer;
CTR CO_   CUST_NBR CUST_NAME                                R
12 13           1 tst                                      Urecheck your code once again..somewhere you are using record_status column for insertion or updation.
Ravi Kumar

Replicat error: ORA-12899: value too large for column ...

Hi,
In our system Source and Target are on the same physical server and in the same Oracle instance. Just different schemes.
Tables on the target were created as 'create table ... as select * from ... source_table', so they have a similar structure. Table names are also similar.
I started replicat, it worked fine for several hours, but when I inserted Chinese symbols into the source table I got an error:
WARNING OGG-00869 Oracle GoldenGate Delivery for Oracle, OGGEX1.prm: OCI Error ORA-12899: value too large for column "MY_TARGET_SCHEMA"."TABLE1"."*FIRSTNAME*" (actual: 93, maximum: 40) (status = 12899), SQL <INSERT INTO "MY_TARGET_SCHEMA"."TABLE1" ("USERID","USERNAME","FIRSTNAME","LASTNAME",....>.
FIRSTNAME is Varchar2(40 char) field.
I suppose the problem probably is our database is running with NLS_LENGTH_SEMANTICS='CHAR'
I've double checked tables structure on the target - it's identical with the source.
I also tried to manually insert this record into the target table using 'insert into ... select * from ... ' statement - it works. The problem seems to be in the replicat.
How to fix this error?
Thanks in advance!
Oracle GoldenGate version: 11.1.1.1
Oracle Database version: 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
NLS_LANG: AMERICAN_AMERICA.AL32UTF8
NLS_LENGTH_SEMANTICS='CHAR'
Edited by: DeniK on Jun 20, 2012 11:49 PM
Edited by: DeniK on Jun 23, 2012 12:05 PM
Edited by: DeniK on Jun 25, 2012 1:55 PM

I've created the definition files and compared them. They are absolutely identical, apart from source and target schema names:
Source definition file:
Definition for table MY_SOURCE_SCHEMA.TABLE1
Record length: 1632
Syskey: 0
Columns: 30
USERID 134 11 0 0 0 1 0 8 8 8 0 0 0 0 1 0 1 3
USERNAME 64 80 12 0 0 1 0 80 80 0 0 0 0 0 1 0 0 0
FIRSTNAME 64 160 98 0 0 1 0 160 160 0 0 0 0 0 1 0 0 0
LASTNAME 64 160 264 0 0 1 0 160 160 0 0 0 0 0 1 0 0 0
PASSWORD 64 160 430 0 0 1 0 160 160 0 0 0 0 0 1 0 0 0
TITLE 64 160 596 0 0 1 0 160 160 0 0 0 0 0 1 0 0 0
Target definition file:
Definition for table MY_TAEGET_SCHEMA.TABLE1
Record length: 1632
Syskey: 0
Columns: 30
USERID 134 11 0 0 0 1 0 8 8 8 0 0 0 0 1 0 1 3
USERNAME 64 80 12 0 0 1 0 80 80 0 0 0 0 0 1 0 0 0
FIRSTNAME 64 160 98 0 0 1 0 160 160 0 0 0 0 0 1 0 0 0
LASTNAME 64 160 264 0 0 1 0 160 160 0 0 0 0 0 1 0 0 0
PASSWORD 64 160 430 0 0 1 0 160 160 0 0 0 0 0 1 0 0 0
TITLE 64 160 596 0 0 1 0 160 160 0 0 0 0 0 1 0 0 0
Edited by: DeniK on Jun 25, 2012 1:56 PM
Edited by: DeniK on Jun 25, 2012 1:57 PM

Sql*loader 11g - Error ORA-12899

Hi All,
I'm using Sqlload for inserti into a 11g db some csv file from db2.
My server is a Linux o.s. with Oracle 11.2.0.1.0 - 64bit.
I receive this error ORA-12899: Value too large for column on all file I try to load.
NLS for my db is:
SQL> select parameter, value from nls_database_parameters where parameter like '%CHARACTERSET%';
PARAMETER VALUE
NLS_CHARACTERSET AL32UTF8
NLS_NCHAR_CHARACTERSET UTF8
Have you any idea?
Thanks very much for help
Regards
Giovanni

In internet I found this short message:
“AL32UTF8 is a multi-byte characterset,that means some characters are stored in more than 1 character, that's true for these special characters.
If you have same table definitions in both databases you likely face error ORA-12899.
This metalink note discusses this problem, it's also applicable to sqlloader:
Import reports "ORA-12899: Value too large for column" when using BYTE semantic
Doc ID: Note:563893.1”
By metalink, I can see the Note linked to a one Oracle Internal Bug for Oracle 11g.....
I'm waiting you suggestion... thanks very much in advance.
Regards.
Giovanni

Error impdp ORA-12899 DATE Datatype

Importing the next table and show me the following error: ORA-12899: value too large for column....
-- describe source table
SQL> desc acs.BAZ_HECHOS_LAM
Name Null? Type
DFECARRIBO NOT NULL DATE
-- describe target table
SQL> desc acs.BAZ_HECHOS_LAM
Name Null? Type
DFECARRIBO NOT NULL DATE
-- impdp output
Processing object type TABLE_EXPORT/TABLE/TABLE_DATA
ORA-31693: Table data object "ACS"."BAZ_HECHOS_LAM" failed to load/unload and is being skipped due to error:
ORA-12899: value too large for column "ACS"."BAZ_HECHOS_LAM"."DFECARRIBO" (actual: 39, maximum: 7)
-- source table
SQL>select dfecarribo from ACS.BAZ_HECHOS_LAM where rownum < 5;
DFECARRIB
02-DEC-09
02-DEC-09
02-DEC-09
02-DEC-09
Elapsed: 00:00:00.03
What is the cause of error?
regards

Pl post the first 10 lines of the exp and imp logs, along with the database and OS versions on the source and target.
HTH
Srini

ORA-01401 and ORA-12899 : "too large for column" error messages

I posted this already in the Database - General forum.
Sorry for the double post.
For the past 8hours, I have been googling about
the related ORA-01401 and ORA-12899 error
messages.
I noticed that ORA-01401 had been removed from the list
of error messages in Oracle 10g documentation.
http://download-west.oracle.com/docs/cd/B14117_01/server.101/b10744/e900.htm#sthref30
And, ORA-12899 has been added.
http://download-west.oracle.com/docs/cd/B14117_01/server.101/b10744/e12700.htm
1. Is there an official Oracle document (e.g. release notes) stating such facts? If so, please provide the link.
2. Why did Oracle change the error code and not just update ORA-01401?
3. Someone posted in http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:7143933880166
Even if installed Oracle is 10g, when he tried to "insert a 100 into a number(2).",
he supposedly got ORA-01401. So, is ORA-01401 still part of 10g or not?
I have yet to confirm this myself.
Sorry for being meticulous. Our customer just wants to know the
information for the 2nd question. It's hard to convince them without
showing official documents.
Thanks!

1)
Well, go to Metalink and check out Note 119119.1 (B.4) and Note:287754.1
2)
Such details are seldom published. One guess is what they changed altered the reason behind the message so using the same code would be a bad idea.
3)
If you are referring to the occurrence of ora-1401 from a select on a XE db, that may be a bug.

ORA-600 [17069] error while running catrelod.sql to downgrade 11g database

Hi,
We are downgrading our 11.2.0.2 database to 10.2.0.4. We have successfullly run catdwgrd.sql without any errors in 11g env. While running catrelod.sql in 10g env we are facing the following error:
SQL> @?/rdbms/admin/catrelod.sql
TIMESTAMP
COMP_TIMESTAMP RELOD__BGN 2013-04-24 20:15:39 2456407 72939
DOC>#######################################################################
DOC>#######################################################################
DOC> The following statement will cause an "ORA-01722: invalid number"
DOC> error if the database server version is not 10.0.0.
DOC> Shutdown ABORT and use a different script or a different server.
DOC>#######################################################################
DOC>#######################################################################
DOC>#
no rows selected
DOC>#######################################################################
DOC>#######################################################################
DOC> The following statement will cause an "ORA-01722: invalid number"
DOC> error if the database has not been opened for MIGRATE.
DOC>
DOC> Perform a "SHUTDOWN ABORT" and
DOC> restart using MIGRATE.
DOC>#######################################################################
DOC>#######################################################################
DOC>#
no rows selected
Session altered.
Session altered.
no rows selected
DECLARE
ERROR at line 1:
ORA-00600: internal error code, arguments: [17069], [0x170FB8CA8], [], [], [],
[], [], []I have checked the trace file in udump but it dint give any readable information.
Please find below environment details.
OS : RHEL 5 64 bit
11g Database : 11.2.0.2
10g Database : 10.2.0.4
Kindly assist.

KR10822864 wrote:
Whenever an ORA-600 error is raised a trace file is generated and an entry written to the alert.log with details of the trace file location. Starting with Oracle Database 11g Release 1, the diagnosability infrastructure was introduced which places the trace and core files into a location controlled by the DIAGNOSTIC_DEST initialization parameter when an incident, such as an ORA-600 is created. For earlier versions, the trace file will be written to either USER_DUMP_DEST (if the error was caught in a user process) or BACKGROUND_DUMP_DEST (if the error was caught in a background process like PMON or SMON). The trace file contains vital information about what led to the error condition
please post 40 lines of alert log info .
MOS Note:ORA-600 [17069] "Failed to pin a library cache object after 50 attempts" [ID 39616.1]
"Look in the trace file for the text 'LIBRARY OBJECT HANDLE: handle=170fb8ca8'"
if not found any massages like above please raise [email protected].
Hi KR,
Thanks for your help. As suggested I have checked the trace file to search and found the below info. I suppose it is some kind of lock but not sure about it. Please let me know if the following makes sense:
    SO: 0x21158a6e0, type: 3, owner: 0x211006f28, flag: INIT/-/-/0x00
    (call) sess: cur 211572570, rec 211572570, usr 211572570; depth: 0
      SO: 0x21158a9b8, type: 3, owner: 0x21158a6e0, flag: INIT/-/-/0x00
      (call) sess: cur 211572570, rec 0, usr 211572570; depth: 1
        SO: 0x1727a2618, type: 54, owner: 0x21158a9b8, flag: INIT/-/-/0x00
        LIBRARY OBJECT PIN: pin=1727a2618 handle=170fb8ca8 mode=S lock=171243e98
        user=211572570 session=211572570 count=1 mask=001d savepoint=0x43 flags=[00]
        SO: 0x171243e98, type: 53, owner: 0x21158a9b8, flag: INIT/-/-/0x00
        LIBRARY OBJECT LOCK: lock=171243e98 handle=170fb8ca8 mode=S
        call pin=0x1727a2618 session pin=(nil) hpc=0000 hlc=0000
        htl=0x171243f18[0x17278a310,0x17278a310] htb=0x17278a310 ssga=0x172789928
        user=211572570 session=211572570 count=1 flags=PNC/[0400] savepoint=0x43
        LIBRARY OBJECT HANDLE: handle=170fb8ca8 mtx=0x170fb8dd8(0) cdp=0
        name=SYS.STANDARD
        hash=51570e225ed8a9a803b7318f191e0a8d timestamp=04-18-2006 00:00:00
        namespace=TABL flags=KGHP/TIM/SML/[02000000]
        kkkk-dddd-llll=0000-001d-001d lock=S pin=S latch#=3 hpc=0004 hlc=0004
        lwt=0x170fb8d50[0x170fb8d50,0x170fb8d50] ltm=0x170fb8d60[0x170fb8d60,0x170fb8d60]
        pwt=0x170fb8d18[0x170fb8d18,0x170fb8d18] ptm=0x170fb8d28[0x170fb8d28,0x170fb8d28]
        ref=0x170fb8d80[0x170fb8d80,0x170fb8d80] lnd=0x170fb8d98[0x170f05b50,0x170fa6858]
          LIBRARY OBJECT: object=170e82de8
          type=PCKG flags=EXS/LOC[0005] pflags=NST/IVR[0201] status=VALD load=0
          DATA BLOCKS:
          data#     heap pointer    status pins change whr
              0 170e831f8 170e82fc0 I/P/A/-/-    0 NONE   00
      SO: 0x21158e470, type: 5, owner: 0x21158a6e0, flag: INIT/-/-/0x00
      (enqueue) CU-70E88BC0-00000001    DID: 0001-001F-00000004
      lv: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 res_flag: 0x2
      res: 0x17677adc8, mode: X, lock_flag: 0x0
      own: 0x211572570, sess: 0x211572570, proc: 0x211006f28, prv: 0x17677add8
      SO: 0x177f82c28, type: 59, owner: 0x21158a6e0, flag: INIT/-/-/0x00
      cursor enqueue
      child: 170e89348, flag: 53, number: 0
      parent: 170e89738

ORA-12899 error from function invoked from SQL*Loader

I am getting the above error when I call a function from my SQL*Loader script, and I am not seeing what the problem is. As far as I can see, there should be no problem with the field lengths, unless the length of the automatic variable within my function is somehow being set at 30? Here are the details (in the SQL*Loader script, the field of interest is the last one):
====
Error:
====
Record 1: Rejected - Error on table TESTM8.LET_DRIVE_IN_FCLTY, column DIF_CSA_ID.
ORA-12899: value too large for column "TESTM8"."LET_DRIVE_IN_FCLTY"."DIF_CSA_ID" (actual: 30, maximum: 16)
=======
Function:
=======
CREATE OR REPLACE FUNCTION find_MCO_id (di_oid_in DECIMAL)
RETURN CHAR IS mco_id CHAR;
BEGIN
SELECT AOL_MCO_LOC_CD INTO mco_id
FROM CONV_DI_FLCTY
WHERE DIF_INST_ELMNT_OID = di_oid_in;
RETURN TRIM(mco_id);
END;
==============
SQL*Loader Script:
==============
LOAD DATA
INFILE 'LET_DRIVE_IN_FCLTY.TXT'
BADFILE 'LOGS\LET_DRIVE_IN_FCLTY_BADDATA.TXT'
DISCARDFILE 'LOGS\LET_DRIVE_IN_FCLTY_DISCARDDATA.TXT'
REPLACE
INTO TABLE TESTM8.LET_DRIVE_IN_FCLTY
FIELDS TERMINATED BY '~' OPTIONALLY ENCLOSED BY '"'
DIF_DRIVE_IN_OID DECIMAL EXTERNAL,
DIF_FCLTY_TYPE_OID DECIMAL EXTERNAL NULLIF DIF_FCLTY_TYPE_OID = 'NULL',
DIF_INST_ELMNT_OID DECIMAL EXTERNAL,
DIF_PRI_PERSON_OID DECIMAL EXTERNAL NULLIF DIF_PRI_PERSON_OID = 'NULL',
DIF_SEC_PERSON_OID DECIMAL EXTERNAL NULLIF DIF_SEC_PERSON_OID = 'NULL',
DIF_CREATE_TS TIMESTAMP "yyyy-mm-dd-hh24.mi.ss.ff6",
DIF_LAST_UPDATE_TS TIMESTAMP "yyyy-mm-dd-hh24.mi.ss.ff6",
DIF_ADP_ID CHAR NULLIF DIF_ADP_ID = 'NULL',
DIF_CAT_CLAIMS_IND CHAR,
DIF_CAT_DIF_IND CHAR,
DIF_DAYLT_SAVE_IND CHAR,
DIF_OPEN_PT_TM_IND CHAR,
DIF_CSA_ID CONSTANT "find_MCO_id(:DIF_DRIVE_IN_OID)"
============
Table Definitions:
============
SQL> describe CONV_DI_FLCTY;
Name Null? Type
DIF_INST_ELMNT_OID NOT NULL NUMBER(18)
AOL_MCO_LOC_CD NOT NULL VARCHAR2(3)
SQL> describe LET_DRIVE_IN_FCLTY;
Name Null? Type
DIF_DRIVE_IN_OID NOT NULL NUMBER(18)
DIF_INST_ELMNT_OID NOT NULL NUMBER(18)
DIF_FCLTY_TYPE_OID NUMBER(18)
DIF_ADP_ID VARCHAR2(10)
DIF_CAT_DIF_IND NOT NULL VARCHAR2(1)
DIF_CAT_CLAIMS_IND NOT NULL VARCHAR2(1)
DIF_CSA_ID VARCHAR2(16)
DIF_DAYLT_SAVE_IND NOT NULL VARCHAR2(1)
DIF_ORG_ENTY_ID VARCHAR2(16)
DIF_OPEN_PT_TM_IND NOT NULL VARCHAR2(1)
DIF_CREATE_TS NOT NULL DATE
DIF_LAST_UPDATE_TS NOT NULL DATE
DIF_ITM_FCL_MKT_ID NUMBER(18)
DIF_PRI_PERSON_OID NUMBER(18)
DIF_SEC_PERSON_OID NUMBER(18)
=========================
Thanks for any help with this one!

I changed one line of the function to:
RETURN CHAR IS mco_id VARCHAR2(16);
But I still get the same error:
ORA-12899: value too large for column "TESTM8"."LET_DRIVE_IN_FCLTY"."DIF_CSA_ID" (actual: 30, maximum: 16)
I just am not seeing what is being defined as 30 characters. Any ideas much appreciated!

Unable to open database : error , ora-03113 end of file communication

Hi Guys ,
I am facing a serious issue with my database
machine Oracle Linux Tikanga 5
database : 10.2.0.1
Error : ora-03113
I was trying to drop a logfile , while inserting the data ....
I restored and tried recovering it but it recovers with message , media recover complete but doesnot allows to open the database
gives the same error : Error : ora-03113 end of file communication
alert_log shows
alter database recover if needed
start
Media Recovery Start
ORA-264 signalled during: alter database recover if needed
start
Wed Jan 9 16:20:18 2013
db_recovery_file_dest_size of 2048 MB is 40.79% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Wed Jan 9 16:22:02 2013
alter database recover datafile list clear
Wed Jan 9 16:22:02 2013
Completed: alter database recover datafile list clear
Wed Jan 9 16:22:02 2013
alter database recover datafile list
1 , 2 , 3 , 4 , 5
Completed: alter database recover datafile list
1 , 2 , 3 , 4 , 5
Wed Jan 9 16:22:02 2013
alter database recover if needed
start
Media Recovery Start
ORA-264 signalled during: alter database recover if needed
start
Wed Jan 9 16:22:07 2013
alter database open
Wed Jan 9 16:22:07 2013
LGWR: STARTING ARCH PROCESSES
ARC0 started with pid=16, OS id=2049
Wed Jan 9 16:22:07 2013
ARC0: Archival started
ARC1: Archival started
LGWR: STARTING ARCH PROCESSES COMPLETE
ARC1 started with pid=17, OS id=2051
Wed Jan 9 16:22:07 2013
Repairing half complete open of thread 1
Wed Jan 9 16:22:07 2013
Errors in file /d1/app/oracle/oradata/orcl/bdump/orcl_lgwr_1966.trc:
ORA-00600: internal error code, arguments: [3712], [1], [1], [0], [445262], [0], [445261], []
Wed Jan 9 16:22:08 2013
Errors in file /d1/app/oracle/oradata/orcl/bdump/orcl_lgwr_1966.trc:
ORA-00600: internal error code, arguments: [3712], [1], [1], [0], [445262], [0], [445261], []
LGWR: terminating instance due to error 470
Instance terminated by LGWR, pid = 1966
can you please suggest on the same ..
Thanks

Due to the nature of the error and to prevent any trial-and-error, I would highly recommand you to open a service request with Oracle asap.
Oracle too recommands the same.
Thanks...

Ora-00600: internal error on 11g database in windows 2007 environment

Hello , i have these problems please help me to solve it.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>emctl status dbconsole
Environment variable ORACLE_SID not defined. Please define it.
C:\Windows\system32>set ORACLE_SID=testsid
C:\Windows\system32>emctl status dbconsole
Oracle Enterprise Manager 11g Database Control Release 11.1.0.6.0
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
https://local:1158/em/console/aboutApplication
Oracle Enterprise Manager 11g is not running.
Logs are generated in directory C:\app\23333941\product\11.1.0\db_3/local_testsid/sysman/log
C:\Windows\system32>sqlplus sys/@**** as sysdba
SQL*Plus: Release 11.1.0.6.0 - Production on Fri Jul 5 09:27:37 2013
Copyright (c) 1982, 2007, Oracle. All rights reserved.
SQL*Plus: Release 11.1.0.6.0 - Production
Copyright (c) 1982, 2007, Oracle. All rights reserved.
Use SQL*Plus to execute SQL, PL/SQL and SQL*Plus statements.
Usage 1: sqlplus -H | -V
    -H             Displays the SQL*Plus version and the
                   usage help.
    -V             Displays the SQL*Plus version.
Usage 2: sqlplus [ [<option>] [<logon>] [<start>] ]
<option> is: [-C <version>] [-L] [-M "<options>"] [-R <level>] [-S]
    -C <version>   Sets the compatibility of affected commands to the
                   version specified by <version>. The version has
                   the form "x.y[.z]". For example, -C 10.2.0
    -F             Enables the failover mode for a RAC environment.
    -L             Attempts to log on just once, instead of
                   reprompting on error.
    -M "<options>" Sets automatic HTML markup of output. The options
                   have the form:
                   HTML [ON|OFF] [HEAD text] [BODY text] [TABLE text]
                   [ENTMAP {ON|OFF}] [SPOOL {ON|OFF}] [PRE[FORMAT] {ON|OFF}]
    -R <level>     Sets restricted mode to disable SQL*Plus commands
                   that interact with the file system. The level can
                   be 1, 2 or 3. The most restrictive is -R 3 which
                   disables all user commands interacting with the
                   file system.
    -S             Sets silent mode which suppresses the display of
                   the SQL*Plus banner, prompts, and echoing of
                   commands.
<logon> is: (<username>[/<password>][@<connect_identifier>] | /)
              [AS SYSDBA | AS SYSOPER | AS SYSASM] | /NOLOG | [EDITION=value]
    Specifies the database account username, password and connect
    identifier for the database connection. Without a connect
    identifier, SQL*Plus connects to the default database.
    The AS SYSDBA, AS SYSOPER and AS SYSASM options are database
    administration privileges.
    <connect_identifier> can be in the form of Net Service Name
    or Easy Connect.
      @[<net_service_name> | [//]Host[:Port]/<service_name>]
        <net_service_name> is a simple name for a service that resolves
        to a connect descriptor.
        Example: Connect to database using Net Service Name and the
                 database net service name is ORCL.
           sqlplus myusername/mypassword@ORCL
        Host specifies the host name or IP address of the database
        server computer.
        Port specifies the listening port on the database server.
        <service_name> specifies the service name of the database you
        want to access.
        Example: Connect to database using Easy Connect and the
                 Service name is ORCL.
           sqlplus myusername/mypassword@Host/ORCL
    The /NOLOG option starts SQL*Plus without connecting to a
    database.
    The EDITION specifies the value for Application
    Edition
<start> is: @<URL>|<filename>[.<ext>] [<parameter> ...]
    Runs the specified SQL*Plus script from a web server (URL) or the
    local file system (filename.ext) with specified parameters that
    will be assigned to substitution variables in the script.
When SQL*Plus starts, and after CONNECT commands, the site profile
(e.g. $ORACLE_HOME/sqlplus/admin/glogin.sql) and the user profile
(e.g. login.sql in the working directory) are run. The files may
contain SQL*Plus commands.
Refer to the SQL*Plus User's Guide and Reference for more information.
C:\Windows\system32>sqlplus sys/1118@testsid as sysdba
SQL*Plus: Release 11.1.0.6.0 - Production on Fri Jul 5 09:29:03 2013
Copyright (c) 1982, 2007, Oracle. All rights reserved.
ERROR:
ORA-12154: TNS:could not resolve the connect identifier specified
Enter user-name: sysdba
Enter password:
ERROR:
ORA-01033: ORACLE initialization or shutdown in progress
Process ID: 0
Session ID: 0 Serial number: 0
Enter user-name: sys
Enter password:
ERROR:
ORA-01033: ORACLE initialization or shutdown in progress
Process ID: 0
Session ID: 0 Serial number: 0
SP2-0157: unable to CONNECT to ORACLE after 3 attempts, exiting SQL*Plus
C:\Windows\system32>sqlplus/nolog
SQL*Plus: Release 11.1.0.6.0 - Production on Fri Jul 5 09:32:59 2013
Copyright (c) 1982, 2007, Oracle. All rights reserved.
SQL> connect/as sysdba
Connected.
SQL> create table test(id number, id1 number);
create table test(id number, id1 number)
ERROR at line 1:
ORA-01109: database not open
SQL> select status from v$instance;
STATUS
MOUNTED
SQL> alter database open;
ERROR at line 1:
ORA-00600: internal error code, arguments: [kcrfr_update_nab_2], [0x51434A54],
[2], [], [], [], [], []
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
C:\Windows\system32>startup mount
'startup' is not recognized as an internal or external command,
operable program or batch file.
C:\Windows\system32>sqlplus/nolog
SQL*Plus: Release 11.1.0.6.0 - Production on Fri Jul 5 10:05:42 2013
Copyright (c) 1982, 2007, Oracle. All rights reserved.
SQL> connect/as sysdba
Connected.
SQL> startup mount;
ORA-01081: cannot start already-running ORACLE - shut it down first
SQL> recover database;
Media recovery complete.
SQL> select GROUP#,SEQUENCE#,ARCHIVED,STATUS from v$log order by SEQUENCE#;
    GROUP# SEQUENCE# ARC STATUS
         2        539 NO INACTIVE
         3        540 NO ACTIVE
         1        541 NO CURRENT
SQL> recover database;
ORA-00283: recovery session canceled due to errors
ORA-00264: no recovery required
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
C:\Windows\system32>sqlplus/nolog
SQL*Plus: Release 11.1.0.6.0 - Production on Fri Jul 5 10:17:10 2013
Copyright (c) 1982, 2007, Oracle. All rights reserved.
SQL> connect / as sysdba
Connected.
SQL> startup mount
ORA-01081: cannot start already-running ORACLE - shut it down first
SQL> shutdown immediate;
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
SQL> startup;
ORACLE instance started.
Total System Global Area 313860096 bytes
Fixed Size                  1332892 bytes
Variable Size             276826468 bytes
Database Buffers           29360128 bytes
Redo Buffers                6340608 bytes
Database mounted.
Database opened.
SQL> recover database;
ORA-00283: recovery session canceled due to errors
ORA-01124: cannot recover data file 1 - file is in use or recovery
ORA-01110: data file 1:
'C:\APP\23333941\ORADATA\TEST\DATAFILE\O1_MF_SYSTEM_8XB8TY3S_.DBF'
SQL> select GROUP#,SEQUENCE#,ARCHIVED,STATUS from v$log order by SEQUENCE#;
    GROUP# SEQUENCE# ARC STATUS
         3        540 NO INACTIVE
         1        541 NO INACTIVE
         2        542 NO CURRENT
SQL> restore database;
SP2-0734: unknown command beginning "restore da..." - rest of line ignored.
SQL> recover database;
ORA-00283: recovery session canceled due to errors
ORA-01124: cannot recover data file 1 - file is in use or recovery
ORA-01110: data file 1:
'C:\APP\23333941\ORADATA\TEST\DATAFILE\O1_MF_SYSTEM_8XB8TY3S_.DBF'
SQL>
Thanks with regards Ganaa;

What happened prior that resulted in the disaster scenario that you posted/
When was the last time the DB opened with out error?
What changed since then?

Database error"ORA-00060: deadlock detected while waiting for resource"

Hi All,
I got dump as
Database error text........: "ORA-00060: deadlock detected while waiting for
resource"
Internal call code.........: "[RSQL/RDUP/NRIV ]"
Please check the entries in the system log (Transaction SM21).
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught
in
procedure "READ_NRIV" "(FORM)", nor was it propagated by a RAISING clause.
Can u ppl tell me how to get correct this?
Edited by: Bala Chandar on Jul 20, 2009 11:01 AM

Hi Bala,
Same type of dump we got when we trigger the DTP which in process chain to load data from DSO to Info cube. And the load had processed with 225 data package and at 164th data package we got this error and except 164th data package all data package processed successfully
And the request was red. So we had done processed manually by clicking the icon. So all its been green and successfully loaded.
So when you do process manual the particular data package which got failed will be process successfully

The database error text is: ORA-01843: not a valid month

I am trying to use a date field as a query filter and I keep getting the
following error:
A database error occurred. The database error text is: ORA-01843: not a
valid month. (WIS 10901).
When I remove the query filter and run the query it works as
expected. I want to be able to allow the users to use the date field in order
to select a date range. Can someone provide me with some information on how to
resolve this issue.

SQL> SELECT (to_char(tO_date('09/29/2006', 'mm/dd/yyyy'))||':'||TO_CHAR(systimestamp,'hh24:mi:ss:ff6'))
2 FROM dual;
(TO_CHAR(TO_DATE('09/29/2006
29-SEP-06:01:33:09:023000
But you want mm/dd/yyyy hh24:mi:ss:ff6 format then use TO_CHAR function for format specifier
SQL> SELECT to_char(to_timestamp((to_char(tO_date('09/29/2006', 'mm/dd/yyyy'))||':'||TO_CHAR(systimestamp,'hh24:mi:ss:ff6')), 'dd/mm/yyyy hh24:mi:ss:ff6'),'mm/dd/yyyy hh24:mi:ss:ff6')
2 FROM DUAL
3 /
TO_CHAR(TO_TIMESTAMP((TO_CHAR
09/29/0006 01:40:27:113000
SQL> Khurram

A database error occured. The database error text is: ORA-29275: partial multibyte character . (WIS 10901)

Hi,
My Webi report is geeting failed with the error
"A database error occured. The database error text is: ORA-29275: partial multibyte character . (WIS 10901)"
may i know the root cause of the above error and how to resolve it. I am using BO 3.1.
Its very important to provide the report. Please help urgently.
Thanks in advance.
Abid

Hi Abid,
Please see SAP Note 1556127.
Symptom
A database error occurs after refreshing a web intelligence report in java report panel or web intelligence in interactive mode
The database error text is: ORA 29275 with partial multibyte character (WIS 10901)
Environment
windows 2003 Server
Cause
Environment variables are not set with value UTF-8:LC_ALL,LANG, and NLS_LANG
Resolution
Set following system environment variables: LC_ALL,LANG, and NLS_LANG with value UTF-8. For example, LC_ALL=EN_US.UTF-8

ORA-12899,database error

Similar Messages

Maybe you are looking for