Unable to start Cognos Configuration because the configuration data is locked by another instance
Using cogconfig.sh -s, occasionally get an error saying that the configuration has been locked.
Unable to start Cognos Configuration because the configuration data is locked by another instance of Cognos Configuration
Cognos Configuration is either already in use, or was last shutdown with errors.
UNIX (all platforms)
Resolving the problem
When Cognos Configuration is started, a cogstartup.lock file is created. If this file is present, the lock is enabled. Delete this file to release the lock.
From the Cognos Configuration User Guide:
"You may get an error message that the configuration data is locked by another instance of Cognos Configuration. When you start Cognos Configuration, it checks to see if the cogstartup.lock file exists in c10_location/configuration. The file may exist if a previous instance did not shut down properly or if another instance of Cognos Configuration is running. If another instance of Cognos Configuration is running, you should exit that instance. Otherwise, any changes you make to the local configuration may result in errors. If no other instance of Cognos Configuration is running, delete the cogstartup.lock file in c10_location/configuration. If the Cognos component service is stopped, click Start."
More support for:
Cognos Business Intelligence
Install and Config
Software version: 10.2, 10.2.1, 10.2.2
Operating system(s): AIX, HP-UX, Linux, Solaris, Windows
Reference #: 1340141
Modified date: 14 May 2011
Translate this page: