DougR
Member
We have and instance of JDE v812 and we are running a 24/7 Europe wide operation and have a number of tables that have more than 45 million rows (>30Gb).
I am an Oracle DBA and am trying to establish a best practice policy.
Is it good practice to regenerate an entire table when adding a new index, particularly when the table contains over 45 million rows and is 25Gb in size from JDE? And then restore the data from a backup?
When creating a new index on the live database using JDE using the OMW, we encounter an error most likely due to locking by running processes.
Is it acceptable to apply new indexes to existing tables (after they have been set up and promoted to live) using raw SQL by the DBA, as this allows us to use the database’s extended commands to circumvent locking and accelerate the speed of applying the index?
All comments would be appreciated
I am an Oracle DBA and am trying to establish a best practice policy.
Is it good practice to regenerate an entire table when adding a new index, particularly when the table contains over 45 million rows and is 25Gb in size from JDE? And then restore the data from a backup?
When creating a new index on the live database using JDE using the OMW, we encounter an error most likely due to locking by running processes.
Is it acceptable to apply new indexes to existing tables (after they have been set up and promoted to live) using raw SQL by the DBA, as this allows us to use the database’s extended commands to circumvent locking and accelerate the speed of applying the index?
All comments would be appreciated