[Spacewalk-list] Taskomatic Bug in 2.2?

[Matthew Madey]

I currently use an Oracle database with Spacewalk 2.2. We have a primary
and standby database server. However, Taskomatic seems to try and connect
to the standby which is read only. This happens every couple of days.. and
causes the taskomatic to stop working. Restarting the service brings it
back ok, but the issue continues to happen. Below is the error I see in the
logs:

INFO   | jvm 1    | 2014/12/03 02:32:22 | Caused by: java.sql.SQLException:
ORA-00604: error occurred at recursive SQL level 1
INFO   | jvm 1    | 2014/12/03 02:32:22 | ORA-16000: database open for
read-only access

I'm going to check with my DBA's and play around with the settings in
tnsnames.ora to see if I can resolve the issue. Has anyone else running
Oracle seen this problem? It only affects Taskomatic, all other services
connect to the active, primary database just fine.


SPWDB=
 (DESCRIPTION_LIST=
  (LOAD_BALANCE=off)
  (FAILOVER=on)
  (DESCRIPTION=
     (CONNECT_TIMEOUT=5)(TRANSPORT_CONNECT_TIMEOUT=3)(RETRY_COUNT=3)
         (ADDRESS_LIST= (LOAD_BALANCE=on)
        (ADDRESS=(PROTOCOL=TCP)(HOST=spwdb.company.com)(PORT=1521)))
         (CONNECT_DATA=(SID=SPWDB)))
  (DESCRIPTION=
     (CONNECT_TIMEOUT=5)(TRANSPORT_CONNECT_TIMEOUT=3)(RETRY_COUNT=3)
     (ADDRESS_LIST= (LOAD_BALANCE=on)
            (ADDRESS=(PROTOCOL=TCP)(HOST=spwdb2.company.com)(PORT=1521)))
     (CONNECT_DATA=(SID=SPWDB))))
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20141203/45c8a5f3/attachment.htm>