AskTom

Hi,

today I want to try clone my db by Grid control but at the begining I’ve got an error:

Completes the Clone Database Configuration screens and setup, then on “Submit” get a failure:
Error:
Invalid clone bean object. Submit failed
TNS 04414: File error

Cause
The problem occured when the listener.ora is parsed and modified. I.e., such as syntax error due to someone’s modification of the network files in the network/admin directory.

Once network files were created by OEM, the clone succeeded without error although all previous
attempts, regardless of which databases failed with same error. This justifies cause.

Solution
To implement the solution, please execute the following steps:

1. Specify another network configuration location at Destination Options page instead of using the
default one (we discover the default one). The location could be an empty directory, and OEM will
create necessary network config files there.

551957.1 Clone Database via Grid Control Fails With - Invalid Clone Bean Object
395941.1 Invalid clone bean object TNS 04414: File error cloning database

Regards,

Tom

Monitoring Refreshes
=======================
The following queries can be used to monitor mview refreshes.
This is part of metelink note 258252.1 MATERIALIZED VIEW REFRESH: Locking, Performance, Monitoring

When an mview was last successfully refreshed
———————————————–
The following query will indicate when an mview was last successfully
refreshed and what type of refresh was done.

column last_refresh_type format a18
column owner format a7
column mview_name format a12
select owner, mview_name, last_refresh_type, last_refresh_date
from dba_mviews;

OWNER   MVIEW_NAME   LAST_REFRESH_TYPE  LAST_REFRESH_DATE
——- ———— —————— ——————
SCOTT   CREF_DEPT    COMPLETE           24-JAN-03 22:17:25
SCOTT   MYDEPT       FAST               23-JAN-03 15:44:24
SCOTT   MY_EMP       FAST               27-JAN-03 21:40:13
SCOTT   UPSNP_DEPT   COMPLETE           24-JAN-03 14:35:37

Status of a Refresh Group Using the Job Queue
———————————————
The following query shows all the jobs scheduled in the job queue to perform
refreshes.  It shows when the last refresh was run, the total amount of time
spent by the system running the job since the instance started, if the job is
broken or has failures, and when the next refresh will run.

column broken format a6
alter session set nls_date_format=’DD-MON-YY hh24:MI:SS’;

select job, last_date last_refresh,
next_date next_refresh, total_time,
broken, failures, what
from dba_jobs
where what like ‘%dbms_refresh%’;

JOB LAST_REFRESH       NEXT_REFRESH       TOTAL_TIME BROKEN   FAILURES
—– —————— —————— ———- —— ———-
WHAT
————————————————————————
1 05-FEB-03 16:37:57 05-FEB-03 16:47:57          2 N               0
dbms_refresh.refresh(’”SYS”.”REFRESHG1″‘);

Note: TOTAL_TIME - you can determine how long (in seconds) a refresh job takes
to run by querying total_time for the job before and after the job runs,
and calculating the difference.  This is helpful in determining what
interval to use to stager refreshes.

Refreshes Currently Running
——————————–
The following query shows all refresh jobs that are currently running, when
they started, and if any have failed.

select r.job, r.this_date, r.failures
from all_jobs_running r, all_jobs j
where j.job = r.job
and j.what like ‘%dbms_refresh%’;

JOB  THIS_DATE            FAILURES
———- —————— ———-
1 05-FEB-03 16:37:57          0

If an mview belongs to a refresh group, you can also use the ALL_REFRESH
and ALL_REFRESH_CHILDREN to obtain information about the mview refresh

select r.rowner, r.rname, r.job, c.name,
r.next_date next_refresh, r.broken
from all_refresh r, all_refresh_children c
where r.job = c.job;

ROWNER     RNAME             JOB NAME       NEXT_REFRESH       BROKEN
———- ————— —– ———- —————— ——
SYS        REFRESHG1           1 MYDEPT     05-FEB-03 16:47:57 N

Regards,

Tom

Hi,

today I found that my refresh job si broken.

SQL> select job, broken, what, next_date from dba_jobs;
Job B WHAT                                                 Next Date
——– - ————————————————–   ——————
384 Y dbms_refresh.refresh(’”TEST”.”REFRESH_MVS”‘);        Aug 27 2009 04:15:50

so I how can i solve this issue?
You remove the broken status from a job that has been marked as broken with  DBMS_JOB.BROKEN with the following syntax:
run EXEC DBMS_JOB.BROKEN(384,FALSE);

Oracle allows you to mark a job you own as broken using the Oracle DBMS_JOB.BROKEN statement.
The following is an example of the DBMS_JOB.BROKEN statement:

EXEC DBMS_JOB.BROKEN(384,TRUE);

The above DBMS_JOB.BROKEN statement will mark Job number 384 as broken.
If the job you are marking as broken with the DBMS_JOB.BROKEN statement is running at the time execution the job will continue to run until stopped. If you are unable to stop the job you may wish to kill your Oracle session.
If a job has been marked as broken with DBMS_JOB.BROKEN, or has been marked as broken by Oracle, Oracle will not attempt to execute the job until the broken status has been removed or the the job has been forced to execute.
To force a job marked as broken, using the  DBMS_JOB.BROKEN statement, the following command can be used:
EXEC DBMS_JOB.RUN(384);

Regards,

Tom