Error "Poster: 15002 - Ora_setup has not been run for database "SID_name" " when configuring Shar (4299388)

Post complained about ora_setup not run for the database and consequently no entry for login found in paramdb though the ora_setup was indeed run earlier and it ran successfully:

Info     2009-03-23 16:25:22.759436 2649 1 Command server launched, pid = 2649 (connecting from server_name.xyz.com)
Info     2009-03-23 16:21:00.710279 27679 1 Poster exited with code=1, pid = 29783  (posting from name1, queue queue_name, to SID_name)
Error    2009-03-23 16:21:00.696157 29783 1 Poster stopped: Internal error encountered; cannot continue  (posting from name1, queue queue_name, to SID_name)
Error    2009-03-23 16:21:00.686686 29783 1 Poster: 15002 - Ora_setup has not been run for database "SID_name"..  (posting from name1, queue queue_name, to SID_name) [module opo]
Warning  2009-03-23 16:21:00.678566 29783 1 Poster: Failed to get Oracle username/password from paramdb  (posting from name1, queue queue_name, to SID_name) [module pdb]
Notice   2009-03-23 16:21:00.674297 29783 1 Poster: Parameter SP_ORD_LOGIN_O.SID_NAME not found  (posting from name1, queue queue_name, to SID_name) [module pdb]

Incorrect SID name in the environment when running ora_setup in a RAC environment.

When running ora_setup in a RAC environment, the users need to have the environment variable ORACLE_SID pointing to the alias created in tnsnames.ora for the Oracle and not use the local SID in the environment. Pointing ORACLE_SID to locate SID entry when running ora_setup will create an entry in paramdb for local SID but the entry for the alias will still be missing from it. This is despite the fact that the sql*net was used in ora_setup and the password was appended with @<tns_alias>  as <password>@<tns_alias>  instead of just <password>.  So, to correct the problem:

1. Shutdown Shareplex.
2. Make sure that the environment is modified so that ORACLE_SID now points to the tns_alias and not the local SID.
3. Re-run ora_setup while making sure that the sql*net is used and the alias is used for connect string.

Starting with SharePlex 8.6.2, it is no longer required to append the password with the connect string in SQL*net environment. During running of ora_setup, SharePlex is able to gather info on connect string and is able to append the value of connect string to the password field specified by the user. Please refer to the knowledgebase article 184662 for details.

See Solution # SOL22923 for general guidelines when setting up Shareplex for running on a RAC environment.