Monthly Archives: December 2008

'Oracle Database Server invalid' after 10.2.0.4-upgrade

Manually upgraded a 9.2.0.6 – database to 10.2.0.4. The output of ‘catupgrd.sql’ shows me the result in the end:

Oracle Database Server INVALID 10.2.0.4.0 00:15:57   ,   while the rest is VALID…

zv7qrnb
By |December 31st, 2008|Categories: Database||0 Comments

Refresh materialized view slower in 10g

Yep,  took over existing procedure of a database with several hundreds of dbms_snapshot.refresh in it, and all on Oracle 9i.  Installed a test-database next to it with 10.2.0.4, and a complete refresh appeared to be 6 times slower, while producing a lot of archive_logs.

Changing to dbms_mview.refresh didn’t help, while the parameter  atomic_refresh is default ‘false’, and as a result of that, records are deleted instead of truncating the table.  Solution: atomic_refresh=>FALSE.

All on 2 Metalink-notes: 365157 en 553464.1

Did some tests  (the  timing is approximately, while there’s some caching):

on the old  9.2 database:

1. Original snapshot-refresh

SQL> exec dbms_snapshot.refresh( list => ‘<mview_name>’, method => ‘C’);

Elapsed: 00:00:01.02

2. De old way on the  10g-database:

SQL>  exec dbms_snapshot.refresh( list => ‘<mview_name>’, method => ‘C’);

Elapsed: 00:00:03.08

3. Using mview_refresh, no change:

SQL> exec dbms_mview.refresh(‘<mview_name>’,’C’,atomic_refresh=>TRUE);

Elapsed: 00:00:03.58

4. Changed to  atomic_refresh=false:

SQL> exec dbms_mview.refresh(‘<mview_name>’,’C’,atomic_refresh=>FALSE);

Elapsed: 00:00:00.90

By |December 11th, 2008|Categories: Database|Tags: |1 Comment

ORA-04062 bij package. Timestamp has been changed..

Foutmelding in job. Package gaf de volgende melding:

Onverwachte fout; proces volledig afgebroken:
ORA-20001: Fout in <package> bij nr. 18212  ORA-00604: error occurred
at recursive SQL level 1
ORA-06502: PL/SQL: numeric or value error
ORA-06512: at line 11
ORA-04062: timestamp of package "INET.INET_ALGEMEEN_PCK" has been
changed
By |December 8th, 2008|Categories: Database||0 Comments

RMAN-06053 tijdens Point in Time Recovery

Zo’n 6 keer uitgevoerd op een ontwikkel-database: restoren via rman naar een bepaalde tijd. 7e keer gaat het restore-gedeelte goed, recovery niet: RMAN-06053, missing log – terwijl die er toch echt is naar mijn bescheiden mening. Database versie 10.2.0.3 op Suse 9.

By |December 6th, 2008|Categories: RMAN||0 Comments