SimonLockington
Member
In the document it says 'all users must be logged off the system', would this include stopping the scheduler from running as well?
tnelipov
Active Member
Melissa -
We have rebuilt existing indexes (that are built from the vanilla JDE) and
have created additional indexes for performance (that JDE does not know
about) without difficulties. All this was done through the db (Oracle).
JDE will submit its sql statement to the db which then chooses the best
execution path (most likely cost-based optimizer for Oracle). That
execution path will take into account pertinent indexes, statistics, etc.
JDE SQL is generic - I have not seen any hint usage or the like.
Creating tables and views is a different story, though. JDE needs to know
about those so they can be used by UBEs, APPLs, etc.
Tony
We have rebuilt existing indexes (that are built from the vanilla JDE) and
have created additional indexes for performance (that JDE does not know
about) without difficulties. All this was done through the db (Oracle).
JDE will submit its sql statement to the db which then chooses the best
execution path (most likely cost-based optimizer for Oracle). That
execution path will take into account pertinent indexes, statistics, etc.
JDE SQL is generic - I have not seen any hint usage or the like.
Creating tables and views is a different story, though. JDE needs to know
about those so they can be used by UBEs, APPLs, etc.
Tony
Alex_Pastuhov
Legendary Poster
Melissa,
It's fine. Oracle does a better job.
Regards,
Alex.
It's fine. Oracle does a better job.
Regards,
Alex.
MelissaS
Active Member
Thanks for the reassurance!
JEMILLER
VIP Member
I would say that the scheduler is in essence an active user. If it is launching reports during the index rebuild you may have either performance problems or (perhaps) integrity issues.
Most of the database engines used with OneWorld allow for indexes to be dropped and created while users are active and accessing the associated database tables. However, if the Primary Key on OneWorld tables is dropped and recreated by this UBE I could imagine there being a potential for duplicate records while the PK is being recreated. Perhaps this is why JDE instructs us to do this with uses off the system.
Regards,
Most of the database engines used with OneWorld allow for indexes to be dropped and created while users are active and accessing the associated database tables. However, if the Primary Key on OneWorld tables is dropped and recreated by this UBE I could imagine there being a potential for duplicate records while the PK is being recreated. Perhaps this is why JDE instructs us to do this with uses off the system.
Regards,
