ORACLE CONNECTOR AND HIGH USE OF METADATA ORACLE ALL_SYNONYM
Moderators: chulett, rschirm, roy
ORACLE CONNECTOR AND HIGH USE OF METADATA ORACLE ALL_SYNONYM
Hi all,
I have a question.
Our jobs read/write data through an Oracle Connector from DB.
Due to security reasons, the access to table happens using synonyms and views.
Our DBA noticed many access to metadata table ALL_SYNONYMS, ALL_VIEWS, ALL_TABLES, done by user datastage.
About your opinion, is there some reason?
Is there some behavior related to Oracle Connectore DS?
Thanks in advance,
Sandro
I have a question.
Our jobs read/write data through an Oracle Connector from DB.
Due to security reasons, the access to table happens using synonyms and views.
Our DBA noticed many access to metadata table ALL_SYNONYMS, ALL_VIEWS, ALL_TABLES, done by user datastage.
About your opinion, is there some reason?
Is there some behavior related to Oracle Connectore DS?
Thanks in advance,
Sandro
I'm not sure what "excessive use" might mean... it's not like the tables will wear out or something. Or are you being billed for your access, hence the concern?
As noted it is normal, customary and I assume essential behavior and I'm not aware of any way to mitigate it. However, if you really need to pursue this, open up a support case and see if there is anything that can be done.
As noted it is normal, customary and I assume essential behavior and I'm not aware of any way to mitigate it. However, if you really need to pursue this, open up a support case and see if there is anything that can be done.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Every time you run a job, or use View Data, DataStage checks for metadata mismatch. It has to go to system tables in order to be able to do this.
Any database worth its salt should be able to handle large numbers of small select queries that don't require exclusive locks. Your DBA needs to be made aware of DataStage's behaviour and the reason for it. And of the fact that it cannot be disabled.
It's a DBA's role to provision a system that can do what its users require.
Any database worth its salt should be able to handle large numbers of small select queries that don't require exclusive locks. Your DBA needs to be made aware of DataStage's behaviour and the reason for it. And of the fact that it cannot be disabled.
It's a DBA's role to provision a system that can do what its users require.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact: