to find out whether it's senseful to reorganize the tables in new tablespaces : what harddrive-system are you using ?
raid ? harddrive access could be already heuristically optimized and no manual reorg would make sense...
to 1. : No.
to 2. : No.
to 3. : No.
nothing of what u asked for is possible in a proper customized system (with proper authorisation-conception)
the real security problems are found one level below, in database access, server communication etc.
hi
correction and transport system...
there is not another order then the one you give to the system.
you releaase a transport order, and then it will be queued in the destinations system import queue.
or do you mean what comes first if tables and source are transported in one transport order ...
Hi
Problem solved automatic after patching.
Seems to have been a "special feature".
Access-pathes have been equally for 34,35 or 36 elements, but only 35 were performing bad. Every element was a 6 byte literal. nothing in the patches description referred to be solving a problem like...
Hi
It uses exactly the same access-path ! (34,35 or 36 objects)
can there be a kind of internal splitting of the statement or a chunk-value like in oracle ?
Hi
I have experienced a strange behaviour of my DB2 DB when executing a IN-Clause Select on a very well indexed table.
With 35 objects in the IN-Clause it takes almost one minute to show results, with 34 or 36 objects it finishes after millisecs.
What can be the reason for that strange effect ...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.