HI,
Can anyone help me with skipping the analyze statement from being executed on the standby database ? I am running 9.2.0.5
Kind Regards
Vishaal
Printable View
HI,
Can anyone help me with skipping the analyze statement from being executed on the standby database ? I am running 9.2.0.5
Kind Regards
Vishaal
HUH?Quote:
Originally posted by Vishaalc
HI,
Can anyone help me with skipping the analyze statement from being executed on the standby database ? I am running 9.2.0.5
Kind Regards
Vishaal
What do you mean? Through dbms_jobs?
Oh...Quote:
Originally posted by Vishaalc
HI,
Can anyone help me with skipping the analyze statement from being executed on the standby database ? I am running 9.2.0.5
Kind Regards
Vishaal
standby database recovery knows abt SCNs, archivelogs and recovery. Nothing more than that. It has no idea abour table structures or the statistics abt them. So, no way you controlling the data contained in disctionary when your standby database is being recovered.
If I understand the original poster correctly, the real question is:
When ANALYZE is isued on the primary database, this will eventualy propagate to the standby and hence the ANALYZE on the same tables/schema/database will be "executed" (of course in reality it will not be executed - only the coresponding block changes to the system TS will be applied) on the standby too. The original poster wants to avoid analyze to be "executed" on the standby side.
AFAIK, there is no option to prevent this on the standby if it was executed on the primary.
Vishaalc, WHY do you want to do this?
Vishaal,
It depends on which standby option you are using Physical or Logical....
Controlling DML/DDL is possible in Logical Standby database.
Rgds,
Milind
How so?Quote:
Originally posted by skmilind
Vishaal,
It depends on which standby option you are using Physical or Logical....
Controlling DML/DDL is possible in Logical Standby database.
Rgds,
Milind