[DM_STARTUP_W_DOCBASE_OWNER_NOT_FOUND] *** warning *** : The database user, XXXXXXXXX as specified by your server.ini is not a valid user as determined using the system password check api. This will likely severly impair the operation of your docbase.

Symptoms When starting your docbase, the full error you may see is: [DM_STARTUP_W_DOCBASE_OWNER_NOT_FOUND] *** warning *** : The database user,  <username> as specified by your server.ini is not a valid user as determined using the system  password check api. This will likely severly impair the operation of your docbase.  Cause In previous versions, database users were required to have a corresponding, valid OS account. This is no longer required, but it is still checked.  Resolution You can safely ignore this message.  We have logged this as Feature Request 156430.   To work around this problem, you can do either of the following: - Create the OS account for this user. - There is a program that is called when the docbase starts.  It is located at $DM_HOME/bin/dmsvaliduser.   It is responsible for doing the preliminary checks on user validity.  It will write the messages to the docbase  log if/when it fails one of these checks.  It is possible to just move this program to the side (rename it to something  like dmisvaliduser.s ave) and create an executable shell script that just returns a successful status.   I believe we expect a '0' status returned by the script for the system to consider it a successful status.   Keep in mind that this is not a supported solution, and has not been tested here.