Trouver les objets invalides dans la base
https://blog.devart.com/find-invalid-objects-in-your-databases.html
En poursuivant votre navigation sur ce site, vous acceptez l'utilisation de cookies. Ces derniers assurent le bon fonctionnement de nos services. En savoir plus.
https://blog.devart.com/find-invalid-objects-in-your-databases.html
https://pgstef.github.io/2018/01/04/introduction_to_pgbackrest.html
https://fr.slideshare.net/slardiere/pgbackrest-pgdayfr
http://laetitia-avrot.blogspot.com/2017/02/faire-une-sauvegarde-avec-pgbackrest.html
http://laetitia-avrot.blogspot.com/2017/02/restaurer-avec-pgbackrest.html
calcul de l'are
https://droit-finances.commentcamarche.com/faq/3561-allocation-chomage-2019-calcul-de-l-indemnite-are-2019
calcul du salaire journalier de référence
https://droit-finances.commentcamarche.com/contents/1532-chomage-calcul-du-salaire-journalier-de-reference
-- ----------------------------------------------------------------------------------- -- File Name : https://oracle-base.com/dba/monitoring/identify_trace_file.sql -- Author : Tim Hall -- Description : Displays the name of the trace file associated with the current session. -- Requirements : Access to the V$ views. -- Call Syntax : @identify_trace_file -- Last Modified: 17-AUG-2005 -- ----------------------------------------------------------------------------------- SET LINESIZE 100 COLUMN trace_file FORMAT A60 SELECT s.sid, s.serial#, pa.value || '/' || LOWER(SYS_CONTEXT('userenv','instance_name')) || '_ora_' || p.spid || '.trc' AS trace_file FROM v$session s, v$process p, v$parameter pa WHERE pa.name = 'user_dump_dest' AND s.paddr = p.addr AND s.audsid = SYS_CONTEXT('USERENV', 'SESSIONID');
Avant la 10G :
Activer la trace :
SQL> EXEC DBMS_SYSTEM.set_sql_trace_in_session(sid=>123, serial#=>1234, sql_trace=>TRUE);
Désactiver la trace : SQL> EXEC DBMS_SYSTEM.set_sql_trace_in_session(sid=>123, serial#=>1234, sql_trace=>FALSE);
Après la 10G :
Activer la trace :
SQL> EXEC DBMS_MONITOR.session_trace_enable(session_id=>1234, serial_num=>1234); SQL> EXEC DBMS_MONITOR.session_trace_enable(session_id =>1234, serial_num=>1234, waits=>TRUE, binds=>FALSE);
Désactiver la trace :
SQL> EXEC DBMS_MONITOR.session_trace_disable(session_id=>1234, serial_num=>1234);
merci :
http://www.lami-dba.com/2018/03/desactiver-active-dataguard.html
RMAN> shutdown immediate
RMAN> startup mount
RMAN> run
2> {
3> set until restore point <nomdupointderestaure>;
4> restore database;
5> recover database;
6> }
RMAN> alter database open resetlogs;
database opened
RMAN>
le site inclus les prérequis que l'on oublie souvent:
Oracle Net connectivity is established between the physical standby database and the primary database.
You can do this by adding an entry corresponding to the primary database in the tnsnames.ora
file of the physical standby database.
The password files on the primary database and the physical standby database are the same.
The COMPATIBLE
parameter in the initialization parameter file of the primary database and physical standby database is set to 12.0.
...
4 . (For Active Data Guard only) Perform the following steps to recover redo data and open the physical standby database in read-only mode:
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE UNTIL CONSISTENT;
ALTER DATABASE OPEN READ ONLY;
...
Source : https://www.orafaq.com/forum/t/122395/
to start a standby database :
#!/bin/bash ORA_HOME="/opt/oracle/920" ORA_OWNER="oracle" SQLCMD="sqlplus '/as sysdba'" LOGFILE="strt.log" cat startup.sql | su - $ORA_OWNER -c "$SQLCMD" > $LOGFILE
to shutdown a standby database :
#!/bin/bash ORA_HOME="/opt/oracle/920" ORA_OWNER="oracle" SQLCMD="sqlplus '/as sysdba'" LOGFILE="sht.log" cat shutdown.sql | su - $ORA_OWNER -c "$SQLCMD" > $LOGFILE
startup.sql :
startup nomount; alter database mount standby database; alter database recover managed standby database disconnect from session;
shutdown.sql:
alter database recover managed standby database cancel; shutdown immediate; exit
Source : https://valehagayev.wordpress.com/2016/07/09/dataguard-commands-and-sql-scripts/
start redo apply in foreground
stop redo apply process on the Standby database (to stop MRP)
start real-time redo apply
start redo apply in background
check redo apply and Media recovery service status
gather Data Guard configuration information(standby)
calculate the Redo bytes per second
check status of Data Guard synchronization(standby)
verify there is no log file gap between the primary and the standby database
verify that the primary database can be switched to the standby role
convert the primary database into a physical standby
verify Managed Recovery is running on the standby
show information about the protection mode, the protection level, the role of the database, and switchover status
On the standby database, query the V$ARCHIVED_LOG view to identify existing files in the archived redo log
On the standby database, query the V$ARCHIVED_LOG view to verify the archived redo log files were applied.
To determine which log files were not received by the standby site.
http://www.aodba.com/steps-stop-start-oracle-standby-database/
https://support.oracle.com/knowledge/Oracle%20Database%20Products/1221163_1.html
MRP : Managed Recovery Process
et bien plus encore sur le DG Broker .