Database dbexport and dbschema failed due to DELIMIDENT
Answered: amber (hollow confidence) — Set DELIMIDENT=Y so dbexport can handle quoted mixed-case or space-containing identifiers. It does not explain why the failure began on 11 June, and the asker did not reply.
Advisory only.
Posted in 2023
Topics: Migration, Import/Export & Data Conversion
HI
I have a client running IBM IDS 12.10.FC6WE on RedHat 7.5
The last successful dbexport backup was on 10 June 2023.
The dbexport failed started 11 June onwards till today.
The dbexport stop with following message
{ WARNING: Parts of this schema require DELIMIDENT set in the environment. }
There is no DELIMIDENT parameter been set in environment file as well as in configuration file.
Appreciate an expert advise to resolve the issue. There is no changed on the database schema since 10 June.
Regards
------------------------------
ABeMie
------------------------------
A database object or identified has been created with mixed case or spaces within quotations, and likely with DELIMIDENT set to Y. This is an environment variable and I have seen it set before within client application environments.
You will need to set DELIMIDENT to Y in your environment (e.g. export DELIMIDENT=Y) to perform your dbexport and dbschema. Once you have confirmed that this is successful, then start looking at what objects and identified have been created with quotations that may have mixed case, spaces, etc.
------------------------------
Mike Walker
xDB Systems, Inc
www.xdbsystems.com
------------------------------