Salesforce

Restricted IDXBUILD fails after 2748

« Go Back

Information

 
TitleRestricted IDXBUILD fails after 2748
URL NameIDXBUILD-fails-rerun-2748-14624-000069742
Article Number000185896
EnvironmentProduct: OpenEdge
Version: 11.4x, 11.5x, 11.6x
OS: All supported platforms
Other: IDXBUILD table, area
Question/Problem Description
When a restricted IDXBUILD commandline Option using "table" or "schema" is interrupted, a rerun fails with error 14624 and the .xb file is deleted
IDXBUILD table "[tablename] > CTRL+C > rerun idxbuild
IDXBUILD schema "[schemaname] > CTRL+C > rerun idxbuild

When a restricted command line indexbuild with "area" is interrupted, a rerun drops to the Menu Options and fails to rebuild the indexes and the .xb file is deleted
IDXBUILD area "[areaname]" > CTRL+C > rerun idxbuild
  
Steps to Reproduce
Clarifying Information
When the equivalent restricted IDXBUILD run through the Index Build Menu is interupted, a rerun succeeds
By Area           (r/R) - Choose indexes in selected areas
By Schema     (c/C) - Choose indexes by schema owners
By Table          (t/T) - Choose indexes in selected tables
Error MessagePrevious index rebuild was interrupted. This is a new try (2748)
Internal error in upPartitionIdLockAndGet, return -1215, inst 3. (14624)
Internal error in get_idxlistbyTable, return -1215, inst 1. (14624)
Defect NumberDefect PSC00348310 / OCTA-3388
Enhancement Number
Cause
The exact cause is not known at this time. This issue appears to have been introduced with the DatabaseTable Partitioning feature since OpenEdge 11.4 when IDXBUILD is run with restricted commandline options on non-partitioned tables
Resolution
Upgrade to the current OpenEdge 11.7.LTS Update. IDXBUILD with restricted commandline options (table, area, schema) no longer fail. While this defect was not explicitly fixed, it no longer fails in current 11.7 versions.
  1. Optionally, use the IDXBUILD Menu Options instead of command line restricted options (area, table, schema, activeindexes, inactiveindexes)
  2. Use the Workaround below to recover from failure to re-run a command line  interrupted restricted IDXBUILD
Workaround
After a failed re-run of a command line interrupted restricted IDXBUILD, before re-running IDXBUILD create a complete .xb file for the indexes that were previously involved.

Manually creating the dbname.xb file:
  • The file needs to have <dbname>.xb for the file name. Example: sports2000.xb 
  • This <dbname>.xb file must exist in the working directory where the IDXBUILD command is going to be issued. When the IDXBUILD utility is run, it looks in the current directory for the <dbname.xb> file. 
  • The contents of the <dbname>.xb file has the following format which needs to be repeated for all tables and indexes associated with the failed IDXBUILD. 
tableowner
tablename
indexname
  • The file also needs to have an "!" exclamation mark for the final entry and a new line. 
  • When the IDXBUILD utility is rerun, it will locate the <dbname>.xb file and display to the screen all tables and indexes which need to be rebuilt then prompt for approval prior to starting the IDXBUILD.  It will then ask for information regarding sort space and then proceed with the rebuild.
  • On successful completion of a subset index rebuild the <dbname>.xb file is deleted.

Example: sports2000.xb file:
PUB
customer
name
PUB
customer
custnum
PUB
order
custorder
PUB
order
orderdate
!
<CR here>
 

Further details on rebuilding the .xb file are provided in Article:
Notes
Keyword Phrase
Last Modified Date3/21/2021 4:08 PM

Powered by