ora_setup, sp_tconf or other Shareplex process fails with ORA-01019 (4282500)

ora_setup, sp_tconf or other Shareplex process fails with "can't log into Oracle as SYSTEM, Error while trying to retrieve text for error ORA-01019" or "Oracle Error: connect failed... ORA-01019: unable to allocate memory in the user side". The problem is observed in some of the processes like ora_setup (after reinstallation of Shareplex during Oracle upgrade, for example), activation, etc.

The following type of error messages appear:

04/23/02 14:55 Process launched: sp_tconf (for o.SID queue *) [pid =4905]
04/23/02 14:55 Bad config file: file - unknown; Oracle Error: connect
failed for database o.SID - Error while trying to retrieve text for error
ORA-01019.
04/23/02 14:55 Process exited sp_tconf (for o.SID queue *) [pid =4905] - exit(1)

or

01/27/04 17:54 Bad config file: file - s1; Oracle Error: connect failed for database o.SID - ORA-01019: unable to allocate memory in the user side.
01/27/04 17:54 Process exited sp_tconf (for o.SID) [pid = 9735] - exit(1)
event_log (17/17)

etc.

The cause of the problem could be one of the following:

1. Wrong entry in oratab file for ORACLE_HOME or ORACLE_SID (names, case, etc). Need to correct the entry
2. Two oratab files on the server, for example, in /var/opt as well as in /etc. Remove the one that is not applicable.
3. ORACLE_SID and ORACLE_HOME were not set when sp_cop was started. Shutdown sp_cop and set these variables before starting sp_cop.
4. Wrong libraries are used to connect to Oracle. Install the correct libraries one more time after shutting down Shareplex. One example may be using 64 bit libraries though Shareplex is 32 bit application, and this may require relinking to 32 bit lib. This can be checked using the ldd command.