Registration | Login

Upcoming Projects

Firefly Online
To be announced


Peter Panzerfaust Motion Comic
To be announced

Upcoming Events

Wizard World Comic Con Chicago
August 24-27, 2017

San Francisco Comic Con
September 1-3, 2017

Wizard World Comic Con Nashville
September 8-10, 2017

Wizard World Comic Con Austin
November 17-19, 2017

Wizard World Comic Con New Orleans
January 5-7, 2017

The official funny thread
By chrisdvanne

Serenity Blu-ray Extra
By chrisdvanne

The OFFICIAL Summer Glau Appreciation Page!
By chrisdvanne

Summer Glau at Ottawa Comiccon 2014
By chrisdvanne

Interesting about the franchise and other TSCC things
By KevinInEngland

Submit a News or Article
By chrisdvanne

The Fanart Thread
By chrisdvanne

Juke Joint!
By Admirator

Misc. News on Movies and other Tidbits
By robbo

Photos of celebrities from the Glau-verse & beyond
By robbo




New comments

KevinInEngland on: Fan made TSCC season 3 trailer


Joseph Flowers on: Guess whose birthday it is today!


Joseph Flowers on: Guess whose birthday it is today!


Roboter on: Guess whose birthday it is today!


robbo on: Guess whose birthday it is today!


The1Russter on: Guess whose birthday it is today!


Charley_Dixon on: Guess whose birthday it is today!


Fermi on: Guess whose birthday it is today!


Admirator on: Guess whose birthday it is today!


Joseph Flowers on: Lovely shot of Summer and Val's wedding by Joan Allen


New videos

00:44:18

00:03:44

00:04:51


latest images

ORA-00942 when calling dbms_mview.refresh in schema cloned by exp/imp

POSTED BY Charley_Dixon ON Jul 20, 2011 / 1 COMMENTS


If you ever tried to refresh materialized view and got an error like this:
Code
BEGIN dbms_mview.refresh('MYMVIEW'); END;

*
ERROR at line 1:
ORA-00942: table or view does not exist
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2256
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2462
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2431
ORA-06512: at line 1

then it's probably because your schema was created by exporting and importing data from schema with another name. If you examine the content of a schema dump file like this:
Code
$ exp myschema@$ORACLE_SID file=myschema rows=n statistics=none
$ strings myschema.dmp|less

then you may see undocumented arguments in commands that create materialized views:
Code
CREATE SNAPSHOT "MYMVIEW" USING ("MYMVIEW", (8, 'DB.GLOBAL.NAME', 1, 0, 0, "MYSCHEMA", ...

The string "DB.GLOBAL.NAME" is obviously a global database name where you exported schema from. It is followed by a few digits and a name of the exported schema. There is also a lot of other stuff I have no idea about, but that probably does not matter.

The point is that if you import a dump file into schema with different name the "MYSCHEMA" argument will not be changed. So when you later try to refresh that materialized view Oracle will search for tables in schema "MYSCHEMA" instead of the current schema. And this is how we can get "ORA-00942: table or view does not exist" error.

So to fix that we should find where that "MYSCHEMA" is stored in the database and change it to the name of the schema the data was imported into. It turns out that it is stored in two tables: "SYS.SNAP$" and "SYS.SNAP_REFTIME$". Basically you need to connect to your database as SYSDBA and execute the following queries:
Code
update SYS.SNAP$ set MOWNER=SOWNER where MOWNER<>SOWNER;
update SYS.SNAP_REFTIME$ set MOWNER=SOWNER where MOWNER<>SOWNER;
commit;

Of course you should examine contents of those tables before executing these queries in case there is a legitimate reason for some materialized views to have differences in those values.

Disclaimer: I have no responsibility for this advice. If you crashed a production database executing code you found on a fan site you have no one to blame but yourself.



Like our Facebook fan page below to stay connected to the latest Summer Glau news!

Total comments: 1

  Message #1 | Leaidan | 2011 Nov 24, 00:03 GMT



Wow, that's a really clever way of tnhiikng about it!



 
Name *:
Email:
Code *: