Just a small wish that 4D compiler would detect and warn on possible losses of precision.
Right now 4D just truncates the decimal value without a peep.
Begin SQL UPDATE Table SET FieldInteger =CAST(1.4 as INT) WHERE id=29168 End SQL
// assume loadable record LOAD RECORD([Table]) [Table]FieldInteger:=1.4 SAVE RECORD([Table])
Link to official 4D feature request (login required).
Posted in 4D, Wish List | Tagged possible loss of precision, real to integer | 1 Comment »
I’m currently using Oracle Data Integrator (ODI) 10.1.3 and I went to clean out the logs generated by the completed executions. I know there is a purge logs trash can icon, but I couldn’t do this because the ‘UNDO’ tablespace was full.
Since I was getting this error I had to remove the reports manually. Aside from removing the reports from the “Session List” tab I also went to remove them from the “Scenarios” tab. Thinking I would save time by removing the entire scenario’s worth of reports I deleted the root node (see image).
What I didn’t know is removing the generated scenario from the ODI Operator view would also remove it from the Designer view. All I had to do was go back and regenerate the scenario from Designer view, but if your installation had different scenarios for fall back purposes this could lead to trouble.
Posted in Oracle Data Integrator | Tagged ODI, Oracle Data Integrator, Scenario | Leave a Comment »
Oracle Data Integrator 10.1.3 is a great tool and can even run fully functional against Oracle Express which is the only free Oracle database product available.
This limited database has it’s draw backs for production use. If Data Integrator is executing scenarios real time, or if the logs are never cleared it could quickly exceed the 5GB storage limit and this nasty error could show up.
Error When Purging Log
java.sql.SQLException: ORA-30036: unable to extend segment by 8 in undo tablespace 'UNDO'
Use Oracle APEX to find the maxed undo tablespace:
The problem is Oracle Express can’t extend the tablespace. Ultimately once the undo tablespace is full all reports need to be removed manually before a purge logs can be executed.
Sometimes purging the logs from the command line will work but not from the Operator view:
startcmd.bat OdiPurgeLog "-PURGE_REPORTS=1"
Otherwise manually remove all reports and then purge using the command line or trash icon. Hint selecting multiple and right clicking ‘delete’ reduces the selection to one item. Instead select multiple and press delete key.
If this doesn’t work delete the contents of the reports tables. I’d start with the SNP_EXP_TXT table because this could have 50million+ records.
Posted in Oracle Data Integrator | Tagged Data Integrator, log purge error, ODI, oracle express, ORA_30036 | Leave a Comment »
Cowboy Coder 