DSA fails to start reporting DSA_I3420
search cancel

DSA fails to start reporting DSA_I3420

book

Article ID: 97174

calendar_today

Updated On:

Products

CA Directory

Issue/Introduction



We had made a configuration change and now the DSA is failing to start. Looking at the ALARM log (or running 'dxserver -d start {dsaname}' command from system prompt) reports:

C:\Windows\system32>dxserver -d start {dsaname} 
** ALARM **: DSA_I1880 Loading XML model version 32 (encrypted) 
DSA_I1880 Loading XML model version 32 (encrypted) 
** ALARM **: DSA_I3420 The DXgrid .db file failed to load as it contains the object identifier '(1.3.6.1.4.1.37146.1.2.7)' which is not defined in the directory schema. If using a copy of the .db file, please ensure the schema used by the DSA matches where the .db file was sourced. 
DSA_I3420 The DXgrid .db file failed to load as it contains the object identifier '(1.3.6.1.4.1.37146.1.2.7)' which is not defined in the directory schema. If using a copy of the .db file, please ensure the schema used by the DSA matches where the .db file was sourced. 
** ALARM **: DSA_E1280 Error in initialization files 
DSA_E1280 Error in initialization files 
** ALARM **: DSA_I1240 DSA shutting down 
DSA_I1240 DSA shutting down 
Failed to start

Environment

Release:
Component: ETRDIR

Resolution

As the error indicates, you have data present in the DSA (within dsaname.db file under DATA location) that contains attributes and values while the actual attributes (SCHEMA .dxc file) are not present in the definition. Most commonly you are missing to 'source' in the correct SCHEMA .dxc file for this DSA. If not sure, please review DXHOME/config/servers/dsaname.dxi file and see what is being 'sourced' under SCHEMA section and make sure you are sourcing all correct (various) schema .dxc files that are tied to the data already present in your DSA.

During the startup phase, DSA (behind the scene) performs a one-one check on existing data with known attribute(s) definition. If anything is missing, it reports the error mentioned above.