Function call in an ASSIGN statement causes SYSTEM ERROR 17630 in the DB log

Jul 22, 2022
Knowledge

Title

URL Name

function-call-in-an-assign-statement-causes-system-error-17630-in-the-db-log

Article Number

000219811

Environment

Product: OpenEdge Version: 11.x, 12.x OS: All supported platforms

Question/Problem Description

Function call in an ASSIGN statement causes SYSTEM ERROR 17630 in the DB log
If a function call is used in an ASSIGN statement this can trigger index error 17630 in the database log.

The code that causes the problem is as follows:

FUNCTION get-name RETURNS CHARACTER ():
    RETURN 'aaa'.
END.

CREATE customer.
ASSIGN
    customer.custnum = 1
    customer.name    = get-name()

This code run against the Sports2000 database raises errors 132, 13917, 17630 and 19489. It also raises the error 17630 in the database log suggesting the database has indexing problems when in fact there are no indexing errors.

[2022/07/22@11:07:55.698+0100] P-4396 T-17116 I ABL : (17630) SYSTEM ERROR: Index CustNum in Customer for recid 756 partition 0 could not be deleted.
[2022/07/22@11:09:03.358+0100] P-4396 T-17116 I ABL : (19489) Please see Knowledge Base Article: (000010396) How to identify the root cause of indexing errors 1422, 17630, 2699, 12002, and 12112.

Steps to Reproduce

Clarifying Information

Error Message

** Customer already exists with Cust Num 1. (132) Cannot execute user-defined function, method or property accessor 'get-name' in an ASSIGN statement after an indexing error. (13917) SYSTEM ERROR: Index CustNum in Customer for recid 756 partition 0 cold not be deleted. (17630) Please see Knowledge Base Article: (000010396) How to identify the root cause of indexing errors 1422, 17630, 2699, 12002, and 12112. (19489)

Defect Number

OCTA-47853

Enhancement Number

Cause

The cause of the issue is the function call in the assign statement, see Crash when attempting to return error from UDF in ASSIGN
But it's not clear why the error 17630 is raised in the database log, suggesting there are indexing errors, when there actually aren't any. Defect OCTA-47853 has been logged to investigate this.

Resolution

None at this time.

Workaround

To avoid the problem move the function call before the ASSIGN statement, or in the ASSIGN move it before the key fields are assigned. For example:

FUNCTION get-name RETURNS CHARACTER ():
    RETURN 'aaa'.
END.

CREATE customer.
ASSIGN
    customer.name    = get-name()
    customer.custnum = 1.

With this code the index violation error 132 will still happen, but the error 17630 will not be displayed on the client or in the database log.

Notes

Progress Article(s):

How to identify the root cause of indexing errors 1422, 17630, 2699, 12002 and 12112
Crash when attempting to return error from UDF in ASSIGN

Keyword Phrase

Last Modified Date

7/22/2022 10:31 AM

Function call in an ASSIGN statement causes SYSTEM ERROR 17630 in the DB log

Files(0)

Was this article helpful?

Was this article helpful?

Function call in an ASSIGN statement causes SYSTEM ERROR 17630 in the DB log

Information

Related Articles