You've got to have a dream. When you lose your dreams, you die.
2012-03-26
2012-03-21
ORA-25137 Data value out of range
Sometimes , there could be also a logical corruption inside an oracle table , which could lead to this error message .
In our case, the corruption was identified by applying length(affected_column) . The result was -1 for a row, which signifies a logical corruption .
In our case, the corruption was identified by applying length(affected_column) . The result was -1 for a row, which signifies a logical corruption .
esecul by tudor galos
"...unde începe eșecul? Eșecul începe în momentul în care îți miroase a bine; atunci trebuie să te pregătești, pentru că sub mirosul de flori s-ar putea să vină mirosul de putregai al vreunui detaliu pe care îl uiți în beția succesului. "
"In momentul în care lucrurile merg foarte bine, lumea uită de disciplină; nu mai este atentă la detalii, nu mai este atentă la informațiile care curg, se uită doar la cifre; care cifre arată bine"
"In momentul în care lucrurile merg foarte bine, lumea uită de disciplină; nu mai este atentă la detalii, nu mai este atentă la informațiile care curg, se uită doar la cifre; care cifre arată bine"
2012-03-20
[Oracle][Odbc]Numeric Value Out Of Range. (#0)
Sometimes it's easier to delete the entire statistics (dbms_stats.delete_table_stats) for the table affected :
2012-03-08
how to recover ocr when it is on ASM
How to restore ASM based OCR after complete loss of the CRS diskgroup on Linux/Unix systems [ID 1062983.1]
2012-03-07
why SGA + PGA must be maximum 60% of total memory available on a Linux Server
http://blog.ronnyegner-consulting.de/2011/10/13/info-task-blocked-for-more-than-120-seconds/
By default Linux uses up to 40% of the available memory for file system caching.
You can lower the mark for flushing the cache from 40% to 10% by setting “vm.dirty_ratio=10″ in /etc/sysctl.conf.
By default Linux uses up to 40% of the available memory for file system caching.
You can lower the mark for flushing the cache from 40% to 10% by setting “vm.dirty_ratio=10″ in /etc/sysctl.conf.
job_queue_processes
Starting with Oracle Database 11g Release 2 (11.2), setting
https://blogs.oracle.com/UPGRADE/entry/dbms_scheduler_jobs_stuck_after
JOB_QUEUE_PROCESSES
to 0
causes both DBMS_SCHEDULER
and DBMS_JOB
jobs to not run. Previously, setting JOB_QUEUE_PROCESSES
to 0
caused DBMS_JOB
jobs to not run, but DBMS_SCHEDULER
jobs were unaffected and would still run. https://blogs.oracle.com/UPGRADE/entry/dbms_scheduler_jobs_stuck_after
2012-03-06
CRS daemon depends on private interconnect
How to Modify Private Network Interface in 11.2 Grid Infrastructure [ID 1073502.1]