TYPO3 Core

So, did you use the latest SVN version?

Where can I get the SVN version?

I think, the error occurs, if I visit a page the first time. So can it be because of the cache-functionality?

Now I also get this error when I insert a new content element:
Warning: ociexecute() [function.ociexecute]: ORA-01704: string literal too long in ...\typo3\sysext\adodb\adodb\drivers\adodb-oci8.inc.php on line 1017

Another error now when I try to index external documents like PDF:
Warning: ociexecute() [function.ociexecute]: ORA-00001: unique constraint (INTRANET.SYS_C0090792) violated in ...\typo3\sysext\adodb\adodb\drivers\adodb-oci8.inc.php on line 1017

In the dbal-Log I see this (example):
sqlError ORA-00001: unique constraint (INTRANET.SYS_C0090792) violated

INSERT INTO "index_words" ( "wid", "baseword", "metaphone" ) VALUES ( '88728859', 'schalter', '212743736' )

I tried the SVN-version. I also dropped tt_content and recreated it with the install-tool. Now all VARCHAR2 columns became CLOB, nice done. But if I try to add new content I get this error:
Versuch einen Datensatz auf Seite 'ORA-00932: inconsistent datatypes: expected CLOB got CHAR' (tt_content:NEW475e89a46f341) ohne die nötigen Berechtigungen einzufügen. (Oder die Seite existiert nicht!) (msg#1.1.12)

I have seen this when using the 'Western European' Oracle Express 10g on a UTF-8 dataset.

Patrick Broens tipped me that character set conversions may be in the way here.

After re-installing the whole system using a 'Universal' Oracle Express 10g database with the same dataset, my problems went away.

Maybe send a reminder to Moreno. If he can still reproduce and gives some 'steps to reproduce', I will help to debug. Otherwise, close the bug.

This bug can be closed. At the end (and with some debugging work) all worked fine.

Thank you for your support!