Help - I'm getting errors ORA-06502:and ORA-01002: at runtime

Question

Help
I am getting the following errors at runtime and need some isdeas on what to check:
ORA-06502: PL/SQL: numeric or value error: character string buffer too small
ORA-06512: at "OWB_RUNTIME.WB_RT_MAPAUDIT", line 1736
ORA-06512: at "OWB_RUNTIME.WB_RT_MAPAUDIT", line 2625
ORA-06512: at "OWB_TARGET.MAP_BSL_PLACEMENT_FACT2B", line 1148
ORA-01002: fetch out of sequence
ORA-02063: preceding line from BASIL@LOC_TARGET_NEW_LOC_BASIL_SOURC
ORA-06512: at "OWB_TARGET.MAP_BSL_PLACEMENT_FACT2B", line 1457
ORA-06512: at "OWB_TARGET.MAP_BSL_PLACEMENT_FACT2B", line 3458
ORA-06512: at line 1
My Mapping is a fact recording enrolments in courses (located in my main target database - oracle 9i)
joining with an equi-join to a table that contains an audit of all changes to the enrolment (in my source database - Sybase 12.5)
then updating two fields in a tabke that is a second definition of the first fact
The equi join uses the key to the enrolment table, plus a transaction type to identify only the creation of the record
Between the join and the update of the table one field is going thru a trim (converting char to varchar2) then an expression that sets the value to "not_supplied" for cases where the value was null.
The other field is a date (from sybase datetime to oracle Date)
(they are the user that created the enrolment and the date the enrolment was actioned)
I created this mapping by copying another mapping that does pretty much the same thing, deleting the join and table it was joining to and adding the audit table and new join.
Both mapping deploy fine with no warnings, the original executes fine the variation gives the errors above.
I have tried removing one then the other of the columns I am updating. (the same errors occur)
I am about to re-write the mapping from scratch, but can anyone guess what is wrong with it ? (I'm using OWB 9.2.0.2.8)

Answer 1

Thanks for the suggestion
There are no "char(32767)"s in the package - altho there are "varchar2(32767)"s
I have tried a variotion on the script, outputting the result to a new table instead of updating the enrolment - which ran fine so the error is in the update.
I tried adding a step using the result in the temp table to update the enrolment table - and got my errors again. So there is something funny in my data. Nothing obvious shows.
The full temp table contains 745292 records - when it failed 150 records had been written.
I note that although I had expected only to find one record per enrolment, there are some where there are two (@#$%!! source system writing two "insert" audit records) - could my problem be that I am updating a record previously updated - where do I set the script to commit as it goes?
Sandra