Synchronous Writethrough Cache Group in 11.2.1.6.1

Question

Hello,
I have created the following SWT cachegroup -
Cache Group CACHEADM.ENT_GRP_SWT_CG:
  Cache Group Type: Synchronous Writethrough
  Autorefresh: No
  Aging: No aging defined
  Root Table: TRAQDBA.ENT_GRP
  Table Type: Propagatebased on this DDL
create synchronous writethrough cache group CACHEADM.ENT_GRP_SWT_CG
from
    TRAQDBA.ENT_GRP (
            GRP_REPRESENTATIVE     NUMBER(12) NOT NULL DEFAULT 0,
            GRP_PARENT_KEY         NUMBER(12) NOT NULL,
            GRP_MEMBER_KEY         NUMBER(12) NOT NULL,
            EVIDENCE_KEY           NUMBER,
            NAME_SCORE             NUMBER(3) NOT NULL,
            ADDRESS_SCORE          NUMBER(3),
            DATE_TIME              TIMESTAMP(6),
            ALERT_ID               NUMBER,
            OLD_GRP_REPRESENTATIVE NUMBER(12),
        primary key (GRP_MEMBER_KEY));When I attempt to insert a row into the cachegroup via ttisql I get the following error -
Command> insert into ent_grp values (1,1,1,null,100,null,sysdate,null,null);
5213: Bad Oracle login error in OCISessionBegin(): ORA-01017: invalid username/password; logon denied rc = -1
5131: Cannot connect to backend database: OracleNetServiceName = "TRAQQA.world", uid = "TRAQDBA", pwd is hidden, TNS_ADMIN = "/app1/oracle/network", ORACLE_HOME= "/opt/oracle-local/home/oracle"
The command failed.When connecting to ttisql I supplied the timesten table owner userid and password. I know that if I supply the oracle password at connect time that the insert will work.
I have AWT cachegroups defined, for example -
Cache Group CACHEADM.EXCLUDED_GRP_ENTITY_AWT_CG:
  Cache Group Type: Asynchronous Writethrough
  Autorefresh: No
  Aging: No aging defined
  Root Table: TRAQDBA.EXCLUDED_GRP_ENTITY
  Table Type: Propagateand I can insert into these cachegroups without the need to supply the oracle password. For example -
Command> autocommit 0
Command> insert into EXCLUDED_GRP_ENTITY values (1,'1',1,1,1,sysdate,1);
1 row inserted.If this behaviour correct? Do I need to supply the oracle password for SWT cachegroups and not AWT cachegroups?
Thanks in advance.
Mark

Answer 1

Hi Chris,
Thanks very much for the information. One other thing we have noticed with the SWT cachegroups that you may be able to comment on - we are using stored procedures in the cache as API's on each of our tables. The stored procedures are owned by the same schema that owns the tables underneath the cache groups. We have an application user that has execute permission on the stored procedures and our java application connects to the application user to execute the stored procedures. We have found when, for example, we insert into the SWT cachegroup via the stored procedures a connection is made to the Oracle server using the userid that owns the stored procedure, not the userid that we have connected to TimesTen with. In our case the connection fails as we are supplying the application users oracle password in OraclePWD and not the schema owners password. Is this the expected behaviour when using stored procedures?
Regards
Mark
Edited by: user557876 on Apr 7, 2011 10:21 PM