Update to the original post ------------------------------- I can also see the same behavior in tkprof output even running the query using table of same schema but using schema name with object name. For example: Select col1 from schema1.tab1 But I am not able to reproduce the issue when run the same query from sqlplus and this only happens when running the query from application. -----Original Message----- From: Harvinder Singh Sent: Thursday, October 12, 2006 6:14 PM To: oracle-l Subject: Multiple schema and Query performance issue Hi, In our application we have 1 main schema (schema1) and 3 other schema(schema2,schema3,schema4) in nologging mode for performance reasons. Now when I try to run the following query connected as schema1 that should take less than few ms: SELECT col1,col2 FROM Schema2.tmp_tab1 Optimizer run the following recursive query and that takes 3-4 sec: SELECT /*+ RULE */ COUNT(*) FROM ALL_SYNONYMS WHERE DB_LINK IS NOT NULL AND SYNONYM_NAME= 'TMP_tab1' AND OWNER='SCHEMA2' Is this a normal behavior when running the query that uses table of another schema as 3-4 sec looks very high time and explain plan showing lot of access to internal tables. What are the possible solutions to make sure that optimizer don't need to run the recursive query? Thanks --Harvinder -- //www.freelists.org/webpage/oracle-l