ca.portal.admin

Connect and Disconnect System Index

Discussion created by ca.portal.admin on Jun 7, 2007
Hi,

Currently, we have a record that is having a system index. It is abit
slow to update a field which is the index field as the amount of data
need to be updated is huge. We would want to temporary disconnect the
system index and connnect back the index when the update is done. What
should be the correct procedure to do this.

Thks

Rgds


WARNING: This communication is meant only for the addressee(s) named
above and may contain information which is confidential and/or legally
privileged. If you are not the named addressee(s), or the agent
responsible for receiving and delivering this communication to the named
addressee(s), this communication has been sent to you in error. If so,
kindly notify the sender and delete the information immediately.
Unauthorised dissemination, distribution, copying or reliance on this
communication is prohibited and may attract criminal penalties.
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: Connect and Disconnect System Index
">if you rebuild from MEMBERS, it would not pick up new-ly added
records (at that time, they are not members)
perhaps from ALLROWS (using the clone schema/subschema) might make better sense




This is Chris Hoelscher and I approved this email
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: Connect and Disconnect System Index
"I think the following procedure could be used:

1) Backup the database areas that contain the member records and the
system-owned index

2) Clone a temporary schema (using a different schema name) changing
the system-owned index from Mandatory Automatic
to Optional Manual

3) Clone a new subschema using the new schema that includes the OM
system-owned index set and its member records

4) Re-compile the update/load program using the new subschema name. The
index prefix pointer already allocated to
existing members will remain unchanged.

5) Run your long running update / load program to add new member
records. Since the system-owned index is OM, no attempt
is made to connect the new members to the index set. Existing members
remain connected to the index set. But that
would not impede your update program performance

6) When completed, run Maintain Index to rebuild index from members. You
will use the old subschema (where the
system-owned index is defined as MA) for this job. NEWSUB will be the
same old subschema with the MA index set.

MAINTAIN INDEX
IN SEGMENT segment-name
USING subschema-name NEWSUB subschema-name
REBUILD index-name FROM MEMBERS


Regards,
Paul Mak
EDS | Australia ADU | Data Engineering Capability - DBA |
Level 1, 36-46 George Street, Burwood, NSW 2134 |
Office: +61 2 9012 5434 | Mobile: +61 419 398 116 |
Fax: +61 2 9012 6707 | Email: paul.mak@eds.com |

Outcomes