The Post queue was backlogged and not moving:
sp_ctrl (servername:2100)> qstatus
Queues Statistics for servername
Name: queue_name(o.SID1-o.SID2) (MTPost queue)
Number of messages: 249975 (Age 165 min; Size 877 mb)
Backlog (messages): 249975 (Age 165 min)
Though the status was showing it as running:
sp_ctrl (servername:2100)> show
Process Source Target State PID
---------- ------------------------ ------------ -------------------- ------
Import NAME NAME Running 23975
MTPost o.SID1-queue_name o.SID2 Running 23881
The "show post detail" showed that it was not moving at all:
sp_ctrl (servername:2100)> show post detail
Host : servername
Source : o.SID1 Queue : queue_name
Operations
Target Status Posted Since Total Backlog
---------- --------------- ---------- ------------------ ---------- ----------
o.SID2 Running 0 07-Jul-09 16:24:13 0 0
Last operation posted:
Redo log: 0 Log offset: 0
INTERNAL OPERATION
Post state : Waiting
Activation Id : 0
Last operation transaction id : 0
Number of open transactions : 0
Number of active transactions : 0
Number of messages read released : 6510
Number of threads : 0
Operations posted : 0
Transactions posted : 0
Insert operations : 0
Update operations : 0
Delete operations : 0
Other operations : 0
Key cache hit count
Ora_setup was run with incorrect input for ORACLE_SID.
On a RAC system shareplex MUST be setup to use tnsalias of the RAC (not the instance name or alias or each SID).
The workaround is:
1. Shutdown Shareplex.
2. Create a tnsalias for the instances of the RAC (in tnsnames.ora) and then run ora_setup using this tnsalias instead of using any of the individual SIDs. The main difference when running ora_setup to configure a tnsalias (as opposed to configuring for Bequeath) is to specify '<password>@<tnsalias>" instead of just specifying '<password>' whenever the ora_setup prompts you for a password.
3. Restart Shareplex and Post (the latter if it was earlier stopped).
NOTE: this tnsalias must also be in the oratab file.
See Solution # SOL22923 for guidelines for installing Shareplex in a RAC environment.
The solution applies to a specific scenario and there could be other reasons for receiving ORA-27140 error.
Here is the description of the Oracle error:
Oracle Error :: ORA-27140
attach to post/wait facility failed
Cause
The program attempted to initialize the post/wait facility, but the facility could not be attached.
Action
Check for additional errors and contact Oracle Support.
And a brief analysis of its cause as taken from a web resource:
"This error is due to missing permission, so make the user is under the 'dba' group"
© 2021 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy