Content View Hits : 8506

Giriş Formu






Forgot your password?
Forgot your username?
No Account Yet? Create an account

redo blocks read, 55450 data blocks need recovery PDF Print E-mail
Written by Administrator   

oracle alert log

22344 redo blocks read, 55450 data blocks need recovery

there is no response in server 

 

you should :

startup mount;

recover database;

alter database open;

 

 

Last Updated ( Wednesday, 27 January 2010 12:17 )
 
Dashboard answers tekrar alanların gruplanmaması PDF Print E-mail
Written by Nilay Burcu Geyik   
Dashboard içine eklenen answers raporundaki satıların tekrarlanması halinde otomatik gruplanmasının kaldırılması işlemi için aşağıdaki gibi seçeneklerin kullanması gerekmektedir.
Last Updated ( Friday, 15 January 2010 10:01 )
 
excel 2007 vlookup multiple PDF Print E-mail
Written by Administrator   
=IF(ISNA(VLOOKUP(J7;$M$7:$M$1682;1;FALSE));"0";"1")
 
ORA-04062: timestamp of package "x" has been changed PDF Print E-mail
Written by Administrator   

When a local piece of PL/SQL references a remote package, function, or procedure, the local PL/SQL engine needs to know if the reference(package, function, or procedure) is still valid, or, if the remote procedure has changed.

The locally compiled PL/SQL code is dependent on the remote code. This dependency is tracked by two models either TIMESTAMPS OR SIGNATURES in oracle.  

Check it :

SELECT name, value
FROM gv$parameter
WHERE name = 'remote_dependencies_mode';

 

REMOTE_DEPENDENCIES_MODE = Timestamp
The local PL/SQL block can only execute the remote PL/SQL block if the timestamp on the remote procedure matches the timestamp stored in the locally compiled PL/SQL block. If the timestamps do not match, the local PL/SQL must be recompiled.

REMOTE_DEPENCIES_MODE = Signature
The local PL/SQL block can still execute the remote PL/SQL block if its "signature" is the same, even if the timestamp has changed.

The term "signature" basically means the interface (procedure name, parameter types or modes) is the same, even if the underlying implementation has changed.

 
* You can alter the mode dynamically by using the DDL statements. For example, this example alters the dependency model for the current session:

Solution : ALTER SESSION SET REMOTE_DEPENDENCIES_MODE = {SIGNATURE | TIMESTAMP}

Thise example alters the dependency model systemwide after startup:
Solution : ALTER SYSTEM SET REMOTE_DEPENDENCIES_MODE = {SIGNATURE | TIMESTAMP}

 

Last Updated ( Thursday, 01 October 2009 16:20 )
 
calling shell script from pl/sql PDF Print E-mail
Written by Administrator   

-- create job

BEGIN
DBMS_SCHEDULER.create_program(
program_name => 'akn_prog1',
program_type => 'EXECUTABLE',
program_action => '/oracle/koccrmett/tani/tani_tekil_id_degisen.sh',
number_of_arguments => 0,
enabled => TRUE,
comments => 'Test Program sh tekil'
);
END;

--create job

BEGIN
DBMS_SCHEDULER.create_job(job_name => 'akn_job1',
program_name => 'akn_prog1',
start_date => NULL,
repeat_interval => NULL,
end_date => NULL,
enabled => TRUE,
auto_drop => FALSE,
comments => 'Export data Job');
END;

-- enable program and job

BEGIN
DBMS_SCHEDULER.enable(NAME => 'akn_job1');
DBMS_SCHEDULER.enable(NAME => 'akn_prog1');
END;
/

-- run job

BEGIN
DBMS_SCHEDULER.RUN_JOB(job_name => 'akn_job1',use_current_session => TRUE);
END;

 
More Articles...
« StartPrev1234567NextEnd »

Page 1 of 7