ORA-01801 problem

Hi,
lately a client of ours encountered a rather strange problem with the ORA-01801 error.
The error only occurs at the clients system. On our development environment everything works as expected.
Here is a snippet from the stored procedure in which the error is occuring:
select DECODE(termin_datum,
NULL, t_startdate,
TO_TIMESTAMP(to_char(termin_datum, 'YYYY-MM-DD') || ' ' ||
termin_bis, 'YYYY-MM-DD HH24:MI')
into t_startdate from bewerbung where bew_id = n_bew_id;
t_startdate is TIMESTAMP set to some date
termin_datum is DATE (might be NULL)
termin_bis is VARCHAR2 (might be NULL, should contain a time of day (e.g. "14:30"))
I tried various malformed input values but i could not get oracle to produce a 01801 error (I only got 01858, 01850, 01851).
What could cause the 01801 error?
Thanks.
Ulrich

I just got word from our customer that this error only occurs intermittently.Don't you just hate it when that happens?
Your only hope is that it is not randomly intermittment but only when some particular combination of things happens. But without a lot of tracing through business processes I don't see how you'd nail that. Of course it could be a bug (most incidents of ORA-1801 seem to be) but again a lot of work to pin it down.
Good luck, APC

Similar Messages

Oracle 10g expdp fatal error (ORA-39125 & ORA-01801)

Key phrases: ORA-39125 ... DBMS_METADATA.FETCH_XML_CLOB [TABLE_STATISTICS] ... date format is too long
Hello,
While performing a routine export (expdp) of schemas in an Oracle 10.2 instance on Linux, a fatal error (ORA-39125) was genereted. A screen capture, including the error messages follows.
Export: Release 10.2.0.1.0 - 64bit Production on Wednesday, 20 May, 2009 15:34:44
Copyright (c) 2003, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
Processing object type SCHEMA_EXPORT/TABLE/TRIGGER
Processing object type SCHEMA_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
ORA-39125: Worker unexpected fatal error in KUPW$WORKER.UNLOAD_METADATA while calling DBMS_METADATA.FETCH_XML_CLOB [TABLE_STATISTICS]
ORA-01801: date format is too long for internal buffer
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 105
ORA-06512: at "SYS.KUPW$WORKER", line 6241
----- PL/SQL Call Stack -----
object line object
handle number name
0x807d2378 14916 package body SYS.KUPW$WORKER
0x807d2378 6300 package body SYS.KUPW$WORKER
0x807d2378 2340 package body SYS.KUPW$WORKER
0x807d2378 6861 package body SYS.KUPW$WORKER
0x807d2378 1262 package body SYS.KUPW$WORKER
0x801d2490 2 anonymous block
Job "SYSTEM"."SYS_EXPORT_SCHEMA_13" stopped due to fatal error at 15:34:54
Has anyone run into this problem?
Is it related to an Oracle bug?
Are there fixes/workarounds?
Thanks in advance,
Alan

Hi,
There have been fixes to this area. I don't know if this exact error has been fixed, but getting the latest patchset would be a good place to start.
Thanks
Dean

ORA-01801 Error

Hi,
We are using Oracle Ver 9.2.0.5 and the application connects to the database using JDBC. When are facing ORA-01801 date format error while executing some queries. When the same query is executed in SQL*Plus it gives the expected result.
Does anyone have faced the same problem and what is the solution to fix this.
Thanks in advance.

In our database we've both the date and timestamp columns. The occurs occasionally when we use date or timestamp column in the query.
I appreciate if you can direct me to the details to fix the problem or if you can let me know on how to solve this.
This very urgent please advise.

Java.sql.SQLException:ORA-01801:date format is too long for internal buffer

Hi,
I am getting the following exception when i trying to insert data in to a table through a stored procedure.
oracle.apps.fnd.framework.OAException: java.sql.SQLException: ORA-01801: date format is too long for internal buffer
when execute this stored procedure from ana anonymous block , it gets executed successfully, but i use a OracleCallableStatement to execute the procedure i am getting this error.
Please let me know how to resolve this error.
Is this error something to do with the Database Configuration ?
Thanks & Regards
Meenal

I don't know if this will help, but we were getting this error in several of the standard OA framework pages and after much pain and aggravation it was determined that visiting the Sourcing Home Page was changing the timezone. For most pages this just changed the timezone that dates were displayed in, but some had this ORA-01801 error and some others had an ORA-01830 error (date format picture ends before converting entire input string). Unfortunately, if you are not using Sourcing at your site, this probably won't help, but if you are, have a look at patch # 4519817.
Note that to get the same error, try the following query (I got this error in 9.2.0.5 and 10.1.0.3):
select to_date('10-Mar-2006', 'DD-Mon-YYYY________________________________________________HH24:MI:SS') from dual;
It appears that you can't have a date format that is longer than 68 characters.

Ora-00600 problem with the kodpunp1 and kope2upic954 arguments

hi everybody,
i have a problem with ora-00600 error on a oracle 8.1.7.0.0 database on winxp.
i've read about many ora-00600 problems but only few were with kodpunp1 and kope2upic954 arguments.
In my trc files i found something like this:
*** SESSION ID:(29.2808) 2006-02-08 11:05:33.177
*** 2006-02-08 11:05:33.177
ksedmp: internal or fatal error
ORA-00600: internal error code, arguments: [kope2upic954], [], [], [], [], [], [], []
Current SQL statement for this session:
call p$insert_rules_details(:1 , :2 , :3, :4)
*** 2006-02-08 11:06:48.400
ksedmp: internal or fatal error
ORA-00600: internal error code, arguments: [kodpunp1], [], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [kope2upic954], [], [], [], [], [], [], []
Current SQL statement for this session:
call p$insert_rules_details(:1 , :2 , :3, :4)
" so this is happenning when calling this procedure (p$insert_rules_details ...this is my procedure, not some procedure owned by sys).
if anyone can help me, pls reply. i've heard replies like: call oracle support, put a tar on metalink ..... i don't have metalink support so i appreciate real help ;)
what to do for avoiding/fixing this error?
tx

in addtion, this procedure p$insert_rules_details does some inserts into 3 tables from my schema. The problem might be from the usage of an num_array in this procedure declared as table of number. When number of elements from this num_array excels 4096, then the procedure generates errors.....i believe, not very sure about that. Can that be true?
by

Ora-01000 problem not resolve with other posts

I've the ora-01000 problem which has been argued in other posts but it persist on me.
I'm using JDK 1.3 and Oracle 8i with classes12_01.zip file.
I've been looking at v$open_cursor to see how many cursors where open and even if I put
rs.close(); rs=null;
stmt.close(); stmt=null;
it still doesn't work.
Any ideas?
Thanks.

Sorry. It do work. It was my fault.
null

ORA-01801 does not exist in Oracle Errors Documentation

Hi,
 
RMAN issed to me the following error: 
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 06/18/2007 09:55:57
RMAN-03999: Oracle error occurred while while converting a date: ORA-01801: date
format is too long for internal buffer 
Regardless of the error reason, when I looked up the ORA-01801 error in the following reference, I did not see the error number there: 
Oracle Database Error Messages 10g Release 2 (10.2) A14219-01
 
 
However, I saw it in Oracle 9i error documentation.
 
 
Are there any obsolete errors? Why I don't see the error in 10g doc?
Thanks in advance.

You should report such thing into Documentation
Nicolas.

Sqlldr encounters ORA-01801 when NLS_LANG=.UTF8

Hi,
When I set NLS_LANG=.UTF8 and then run SQL Loader, I get the following error:
ORA-01801: date format is too long for internal buffer
My CTL file characterset is UTF8 and the content in the DAT file is also in UTF8 format. In addition, the table specified in the CTL file does not have any DATE column, only VARCHAR2 columns.
I have checked that all rows are loaded correctly and no data is corrupted.
When I changed NLS_LANG back to a non-UTF8 charset, the error did not appear.
Can someone provide some insight into why this is happening?
Thanks,
Eric

Thanks for the reply.
I had previously gone through the G11N guide that you mentioned.
I am encountering this error on AIX51 only when I ran the SQL Loader under NLS_LANG=TRADITIONAL CHINESE_TAIWAN.UTF8.
AIX51 (or Unix in general) supports UTF8 natively, so it puzzles me why I am hitting this error.
What I can guess is that the date format send from the oracle client is in the longer Taiwanese format, which the database cannot proceed. The date buffer at the database side could be in another locale format.
I am adding additional NLS parameters to my database initialization file to see how it turns out.
-Eric

Ora-01843 problem

My code is giving me ora-01843 problem. When i put startdate as 01-jan-05 and
enddate as 31-jan-05, it gives me error. Please help me guys.
--declare
--ntwk_var varchar2(100);
SELECT PHY.PHYNAM,
decode (NETWORKPROTOCOL.LCC, 'Y', '<Lombardi Cancer Center>', '') ||
decode (NETWORKPROTOCOL.UMH, 'Y', ' <Union Memorial Hospital>', '') ||
decode (NETWORKPROTOCOL.GSH, 'Y', '<Good Somaritan Hospital>', '') ||
decode (NETWORKPROTOCOL.FSH, 'Y', '<Franklin Square Hospital>', '') ||
decode (NETWORKPROTOCOL.WHC, 'Y', '<Washington Hospital Center>', '') ||
decode (NETWORKPROTOCOL.HH, 'Y', '<Harbor Hospital>', '') as NETWORKID,
PRTCRC.FULLNAME,
CRCMTG.CRMTGDT, CRCMTG.CRCSTAT, PRTCRC.SUBMITTEDTOIRB,
PRTCRC.RECEIVEDIRBRESULTDATE,
PRTCRC.PRT, prtcrc.crcid,
PRTCRC.REVIEWSTATUS,
CRCMTG.CRCOUTCOME,
PRTCRC.REVIEWTYPE,
PRTCRC.MODIFICATIONDATE, PRTCRC.FINALIRBAPPROVALDATE,
PRTCRC.ACTIVATIONDATE, RECENTREAPPROVALDATE.RECENTREAPPROVAL,
recentamendmentdate.amenddate,
PRTCRC.CLOSURETOPATIENTACCRUAL, PRTCRC.TERMINATIONDATE,
prttype.descrip
FROM CRCMTG, PRTCRC, NETWORKPROTOCOL, RECENTREAPPROVALDATE, PHY, prttype, recentamendmentdate
WHERE
((CRCMTG.PRTCRCID(+)=PRTCRC.ID) AND
(NETWORKPROTOCOL.PRTCRCID(+)=PRTCRC.ID) AND
(PRTCRC.PRINCIPALINVESTIGATOR=PHY.PHY(+))
AND (PRTCRC.ID=RECENTREAPPROVALDATE.PRTCRCID(+))
AND (PRTCRC.ID=recentamendmentdate.PRTCRCID(+))
) and
TO_DATE('01'||SUBSTR(LTRIM( NVL(PRTCRC.CRCID, TO_CHAR(sysdate, 'MMYYYY'))) , 1, 6), 'DDMMYYYY') >= :startdate
and
TO_DATE('01'||SUBSTR(LTRIM( NVL(PRTCRC.CRCID, TO_CHAR(sysdate, 'MMYYYY'))) , 1, 6), 'DDMMYYYY') <= :enddate
) and
prtcrc.type=prttype.id(+) and
fullname is not null
order by &SORT

as Andrew had mentioned you are trying to convert a numeric into date that might not be in date format. for example you had a value of 482334
SQL> select substr(ltrim('482334'),1,6)
2 from dual;
SUBSTR
482334then you tried to convert it into date format
SQL> select to_date(substr(ltrim('482334'),1,6),'ddmmyyyy')
2 from dual;
select to_date(substr(ltrim('482334'),1,6),'ddmmyyyy')
ERROR at line 1:
ORA-01847: day of month must be between 1 and last day of month
SQL> it will give you an error. what is the datatype for your column PRTCRC.CRCID?

VERY weird ora-12705 problem

I have on a database running on Unix True64 a database link to another database. Also a True64 machine. The Oracle version is 8.1.7.0.0.
What happens is that I get a ora-12705 problem. Yes I know this has to do with NLS environment setting. But I doubt this is the case with this one. Look at the example:
unix> sqlplus /
SQL> select count(*) from zfindau;
select count(*) from zfindau
ERROR at line 1:
ORA-12705: invalid or unknown NLS parameter value specified
ORA-02063: preceding line from HUBD
SQL> connect system/<password>
SQL> connect /
SQL> select count(*) from zfindau;
COUNT(*)
74991
So under Unix I connect to an ops$ account. The zfindau is a synonym to the remote database table. First I do the select statement and get the ORA-12705 error. After I connect to a different user (system, or any other user available), do nothing and directly connect to the ops$account the same sql statement does work.
Does anyone of you know what's going on here.
Andre Seesink

anyone??

ORA-01552 problem, plz help it's urgent

Actually, before one week I made (run Norton QuikScan) & this ended by the ORA-01033 problem, I realized that the file (E:\ORACLE\PRODUCT\10.2.\ORADATA\ORCL\UNDOTBS01.DBF)
was corrupted, so I dropped it from the (Dos command Prompt), then the system generated it again and then everything was excellent.
After that I couldn't create any new tables.
NB. I've more than 30 large table.
then i got the ORA-01552 problem,
cannot use system rollback segment for non-system tablespace...
i did this:(
& i got this error:
SQL> alter system set undo_management=manual scope=spfile;
System altered.
SQL> shutdown immediate;
ORA-00376:file 2 cannot be read at this time
ORA-01110:data file 2:
'E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\UNDOTBS01.DBF'
SQL> select name, status, BLOCK_SIZE from v$datafile;
NAME
STATUS BLOCK_SIZE
E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\SYSTEM01.DBF
SYSTEM 8192
E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\UNDOTBS01.DBF
RECOVER 8192
E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\SYSAUX01.DBF
ONLINE 8192
NAME
STATUS BLOCK_SIZE
E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\USERS01.DBF
ONLINE 8192
E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\EXAMPLE01.DBF
ONLINE 8192
E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\UNDO01.DBF
ONLINE 8192
i need to solve it...:(
is it correct to uninstall the ORACLE & install it again.
thanks in advance.

ORA-01033 ORACLE initialization or shutdown in progress
Cause: An attempt was made to log on while Oracle is being started or shut down.
Action: Wait a few minutes. Then retry the operation.
Does not mean your datafile was corrupted!! You meed to recover the undo dbf. It does not have anything to do with reinstalling Oracle. You can restore from hot backup and recover the db, or drop and recreate the undo ts at mount.

Character set Conversion (US7ASCII to AL32UTF8) -- ORA-31011 problem

Hello,
We've run into some problems as part of our character set conversion from US7ASCII to AL32UTF8. The latest problem is that we have a query that works in US7ASCII, but after converting to AL32UTF8 it no longer works and generates an ORA-31011 error. This is very concerning to us as this error indicates an XML parsing problem and we are doing no XML whatsoever in our DB. We do not have XML columns (nor even CLOBs or BLOBs) nor XML tables and it's not XMLDB.
For reference, we're running 11.2.0.2.0 over Solaris.
Has anyone seen this kind of problem before?
If need be, I'll find a way to post table definitions. However, it's safe to assume that we are only using DATE, VARCHAR2 and NUMBER column types in these tables. All of the tables are local to the DB.
Thanks

We converted using the database using scripts I developed. I'm not quite sure how we converted is relevant, other than saying that we did not use the Oracle conversion utility (not csscan, but the GUI Java tool).
A summary:
1) We replaced the lossy characters by parsing a csscan output file
2) After re-scanning with csscan and coming up clean, our DBA converted the database to AL32UTF8 (changed the parameter file, changing the character set, switched the semantics to char, etc).
3) Final step was changing existing tables to use char semantics by changing the table schema for VARCHAR2 columns
Any specific steps I cannot easily answer, I worked with a DBA at our company to do this work. I handled the character replacement / DDL changes and the DBA ran csscan & performed the database config changes.
Our actual error message:
ORA-31011: XML parsing failed
ORA-19202: Error occurred in XML processing
LPX-00210: expected '<' instead of '�Error at line 1
31011. 00000 - "XML parsing failed"
*Cause: XML parser returned an error while trying to parse the document.
*Action: Check if the document to be parsed is valid.
Error at Line: 24 Column: 15
This seems to match the the document ID referenced below. I will ask our DBA to pull it up and review it.
Please advise if more information is needed from my end.

ORA-29855 problem with creation of a index

Hi to all,
I'm trying to create an index but I have this problem:
SQL>CREATE INDEX ITALIA_NODE_IDX ON ITALIA_NODE$(GEOMETRY) INDEXTYPE IS MDSYS.SPATIAL_INDEX;
CREATE INDEX ITALIA_NODE_IDX ON ITALIA_NODE$(GEOMETRY) INDEXTYPE IS MDSYS.SPATIAL_INDEX
ERROR at line 1:
ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
ORA-13249: internal error in Spatial index: [mdidxrbd]
ORA-13249: Error in Spatial index: index build failed
ORA-13249: Error in spatial index: [mdrcrtxfergm]
ORA-13249: Error in spatial index: [mdpridxtxfergm]
ORA-29400: data cartridge error
ORA-01653: unable to extend table M2_10A70$$.1024 by SPATIAL in tablespace USERS
ORA-06512: a "MDSYS.SDO_INDEX_METHOD_10I", line 10
What do you think about this problem?
thank you in advance.
Crystal
Edited by: crystal13 on 18-giu-2010 2.03

Hi,
it looks like your tablespace USERS is to small. You have no space left. So extend the size of the tablespace by enlarging the file underneath or putting a second one to it, or put the tablespace in AUTOEXTEND mode. See the administrators guide: http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/tspaces.htm#i1010516

ORA-00313 problem, thank you very much!!

Hi, there,
when I use OEM standalone to login the database, I found there is an error:
ORA-00313:open failed for members of log group1 of thred 1
ORA-00312:online log 1 thread 1 "c:\oracle-database-server\oradata\redo01.log"
then I can't open the database and only can mount it.
and then I found all the other databases on my local machine have the exact same problem. at the same time, I found the service of OracleOracle9iDB_serveManagementServer can't startup. whenever I want to start it, it warn me "start and stop, becuase there is no work connect to it". so I doublt it seems there is something wrong with my operation system, but not the database's problem. my os is WIN XP PRO.
does there anyone who knows the reason and how can I solve it? besides, can I backup the database in mount status and how?
thank you very much for any hint!
I do need you help, thank you so much!!

Does c:\oracle-database-server\oradata\redo01.log exist? Once I met a guy, who, as he said, deleted unnecessary log files :-)

ORA-00312 problem, thank you very much!

Hi, there,
when I use OEM standalone to login the database, I found there is an error:
ORA-00313:open failed for members of log group1 of thred 1
ORA-00312:online log 1 thread 1 "c:\oracle-database-server\oradata\redo01.log"
then I can't open the database and only can mount it.
and then I found all the other databases on my local machine have the exact same problem. at the same time, I found the service of OracleOracle9iDB_serveManagementServer can't startup. whenever I want to start it, it warn me "start and stop, becuase there is no work connect to it". so I doublt it seems there is something wrong with my operation system, but not the database's problem. my os is WIN XP PRO.
does there anyone who knows the reason and how can I solve it? besides, can I backup the database in mount status and how?
thank you very much for any hint!
I do need you help, thank you so much!!

Please repost this in one of the database forums, unfortunately most of us on the JDev team are better at Java than database issues.
Here's the URL to the general RDBMS forum here on OTN:
General Database Discussions
Hope this helps,
Rob

ORA-01801 problem

Similar Messages

Maybe you are looking for