The following errors are observed when trying to activate a config file:
03/19/05 20:34 Logging user command: splexadm activate config config_name
03/19/05 20:34 Process launched: sp_tconf (for o.SOURCE_SID) [pid = 175]
03/19/05 20:34 Notice: Oracle env - SOURCE_SID:/opt/oracle/8.1.7 [sp_tconf(pdb)/175]
03/19/05 20:34 Error: Can't lock <path>/config_name - Permission denied [sp_tconf(act)/175]
03/19/05 20:34 Error: 14002 - sp_conf exit due to activation failure. [sp_tconf/175]
03/19/05 20:34 Bad config file: file - unknown; Error: Unable to activate config.
03/19/05 20:34 Process exited sp_tconf (for o.SOURCE_SID) [pid = 175] - exit(1)
Incorrect permissions on the config file may be causing the error.
The problem can happen due to Incorrect permissions on the config file. The following are the most common reasons:
1. The config file is edited outside of sp_ctrl using vi or other editors. This can result in incorrect ownerships/permissions on the config file. There are many other side effects that can be encountered when editing a config file outside of sp_ctrl. Please see Solution # SOL54895 for details.
2. When moving vardir around by copying it from one server to another, the ownerships/permissions on the config file can change.
The above are the most common reasons for activation to fail with "Error: Can't lock <path>/config_name - Permission denied". Once the ownership/permission issues are addressed, the config file can be successfully activated. If in doubt, one can compare the ownership/permission of the config file in question to one in an installation of Shareplex. There is a template config file named ORA_config located in $SP_SYS_VARDIR/config directory that has the defult ownership/permission and any deviation from it can be corrected. The activation can then be attempted again.