I sent and SQL statement to my Oracle DBA, this SQL already had been used to build a materialized view. Now the DBA is getting an error.
*** 2005-08-04 12:48:24.862
*** SESSION ID
44.506) 2005-08-04 12:48:24.844
A deadlock among DDL and parse locks is detected.
This deadlock is usually due to user errors in
the design of an application or from issuing a set
of concurrent statements which can cause a deadlock.
This should not be reported to Oracle Support.
The following information may aid in finding
the errors which cause the deadlock:
ORA-04020: deadlock detected while trying to lock object CLARITY.CLARITY_SER
Question. I don't see how the Select Statement is causing this error. Is that possible? It seems more likely to me the error is due to the DBA trying to build 2 MV's at the same time using the same tables. Any ideas? Doesn't the error need to be on the build side DDL, not on the Select statement DML?
*** 2005-08-04 12:48:24.862
*** SESSION ID
44.506) 2005-08-04 12:48:24.844A deadlock among DDL and parse locks is detected.
This deadlock is usually due to user errors in
the design of an application or from issuing a set
of concurrent statements which can cause a deadlock.
This should not be reported to Oracle Support.
The following information may aid in finding
the errors which cause the deadlock:
ORA-04020: deadlock detected while trying to lock object CLARITY.CLARITY_SER
Question. I don't see how the Select Statement is causing this error. Is that possible? It seems more likely to me the error is due to the DBA trying to build 2 MV's at the same time using the same tables. Any ideas? Doesn't the error need to be on the build side DDL, not on the Select statement DML?
