Support Article

Unable to start SPI process after changing Oracle password



As per the SOX compliance, the Oracle account's password is changed and the vantage.init is updated. After this change, the SPI process stops and does not restart. Therefore, the relevant CMD logs are not generated in the error log directory.

Error Messages

Not Applicable

Steps to Reproduce

Start the Task Group or schedule any CMD objects.

Root Cause

  • The new password set for the user account contained a '#' symbol, due to which all the characters followed by '#' were considered as comment.
  • Some recent environment changes were made due to which access permissions for CMD files and directories were also modified. This was one of the reasons that logs were not generated and CMD operations were failing.
  • The account did not have the required permissions to connect to the Oracle database through SQL PLUS. Hence, the user was not able to connect to the database through SQL PLUS (from user's command prompt).


  • Reset the password to one that does not contain '#'. Update the new password in the CMD scripts and Vantage.init file.
  • Change the CMD error directory path to the path location which has the correct access permissions. In this use case, it was an older directory path.

For the SQL PLUS launch issue:

  1. Contact local DBA to fix the SQL PLUS launch issue from the command prompt of the user.
  2. After successful launch of the SQL PLUS, connect to database with the new password. Unlock the account if necessary.
  3. Once the user successfully connects to the database, kill the lock and SPI processes and restart them.

Published April 17, 2017 - Updated May 29, 2017

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.