2016-09-27

live

http://www.thelancet.com/pdfs/journals/lancet/PIIS0140-6736(16)31467-2.pdf

2016-09-26

nunti

http://republica.ro/z-cat-merge-darul-un-olandez-la-o-nunta-ritual-de-initiere-in-cultura-romaneasca

knime assignments

http://mzym.susu.ru/courses/dm-en/Assignments.pdf

excel to knime

https://www.knime.org/blog/migrating-from-excel-to-knime-analytics-platform

http://www.joelonsoftware.com/articles/fog0000000043.html

8. Do programmers have quiet working conditions?
There are extensively documented productivity gains provided by giving knowledge workers space, quiet, and privacy. The classic software management bookPeopleware documents these productivity benefits extensively.
Here's the trouble. We all know that knowledge workers work best by getting into "flow", also known as being "in the zone", where they are fully concentrated on their work and fully tuned out of their environment. They lose track of time and produce great stuff through absolute concentration. This is when they get all of their productive work done. Writers, programmers, scientists, and even basketball players will tell you about being in the zone.
The trouble is, getting into "the zone" is not easy. When you try to measure it, it looks like it takes an average of 15 minutes to start working at maximum productivity. Sometimes, if you're tired or have already done a lot of creative work that day, you just can't get into the zone and you spend the rest of your work day fiddling around, reading the web, playing Tetris.
The other trouble is that it's so easy to get knocked outof the zone. Noise, phone calls, going out for lunch, having to drive 5 minutes to Starbucks for coffee, and interruptions by coworkers -- especially interruptions by coworkers -- all knock you out of the zone. If a coworker asks you a question, causing a 1 minute interruption, but this knocks you out of the zone badly enough that it takes you half an hour to get productive again, your overall productivity is in serious trouble. If you're in a noisy bullpen environment like the type that caffeinated dotcoms love to create, with marketing guys screaming on the phone next to programmers, your productivity will plunge as knowledge workers get interrupted time after time and never get into the zone.
With programmers, it's especially hard. Productivity depends on being able to juggle a lot of little details in short term memory all at once. Any kind of interruption can cause these details to come crashing down. When you resume work, you can't remember any of the details (like local variable names you were using, or where you were up to in implementing that search algorithm) and you have to keep looking these things up, which slows you down a lot until you get back up to speed.
Here's the simple algebra. Let's say (as the evidence seems to suggest) that if we interrupt a programmer, even for a minute, we're really blowing away 15 minutes of productivity. For this example, lets put two programmers, Jeff and Mutt, in open cubicles next to each other in a standard Dilbert veal-fattening farm. Mutt can't remember the name of the Unicode version of the strcpy function. He could look it up, which takes 30 seconds, or he could ask Jeff, which takes 15 seconds. Since he's sitting right next to Jeff, he asks Jeff. Jeff gets distracted and loses 15 minutes of productivity (to save Mutt 15 seconds).
Now let's move them into separate offices with walls and doors. Now when Mutt can't remember the name of that function, he could look it up, which still takes 30 seconds, or he could ask Jeff, which now takes 45 seconds and involves standing up (not an easy task given the average physical fitness of programmers!). So he looks it up. So now Mutt loses 30 seconds of productivity, but we save 15 minutes for Jeff. Ahhh!

2016-09-23

ORA-06512: at "SYS.XMLTYPE", line 169

ORA-06502: PL/SQL: numeric or value error: character string buffer too small
ORA-06512: at "SYS.XMLTYPE", line 169

Job Fails With ORA-21780 ORA-6512 After Upgrade from 11.2.0.1.0 To 11.2.0.3.0 (Doc ID 1537703.1) To BottomTo Bottom

In this Document
Symptoms
Cause
Solution
References

APPLIES TO:

Oracle Database - Enterprise Edition - Version 11.2.0.3 to 11.2.0.3 [Release 11.2]
Information in this document applies to any platform.
SYMPTOMS

Database was upgraded from 11.2.0.1 to 11.2.0.3.1.
Query using:

XMLTYPE
(
REGEXP_REPLACE
(
SYS_XMLGEN
(
XMLELEMENT

See test case for details.
gets for each row error:

ORA-21780: Maximum number of object durations exceeded.
ORA-06512: at "SYS.UTL_SMTP", line 186
ORA-06512: at "I2B2STAGINGHPCE.SP_SEND_EMAIL", line 22
ORA-06512: at "I2B2STAGINGHPCE.USP_LOAD_FACT_POPCASES", line 650
ORA-21780: Maximum number of object durations exceeded.
ORA-06512: at "SYS.XMLTYPE", line 310
ORA-06512: at "I2B2STAGINGHPCE.FN_PERIOP_ONTIME", line 1112
...

Notes:
This was working fine in 11.2.0.1 and it is throwing this error in 11.2.0.3.1
Customer's database characterset is WE8MSWIN1252


CAUSE

Code bug

Bug 16404196 - JOB FAILS WITH ORA-21780 ORA-6512
set as duplicate of Bug 13829838 - ORA-07445 [KKXUEXE] DUING PL/SQL PROCESS


SOLUTION

Download and apply patch 13829838

Log into https://support.oracle.com
Click on Patch ID or Number
Patch ID or Number is : 13829838
Click on Search
Click on Bug Number associated to your platform: Choose 11.2.0.3.0 for Linux, it can be applied to the 11.2.0.3.1 installation as well
Click on Download