sqlnet.ora paramters
-Default order of NAMES. DIRECTORY_PATH is TNSNAMES, OID, HOSTNAME in sqlnet.ora. -EZCONNECT is available after 10g onwards. -Make sure Names.default_domain is set property to avoid any kind of client connectivity issues.
Category: Oracle
TNSNAMES entries details
Option: Try each address, in order, until one succeeds ( Failover only). By default failover=true if you have more than one entry in address list. ============================================================================= MEHTA = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = NYBOX)(PORT = 1555)) (ADDRESS = (PROTOCOL = TCP)(HOST = FLBOX)(PORT = 1600)) ) (CONNECT_DATA = (SERVICE_NAME =…
Oracle 11g Training on 29JAN1010
-SERVICE_NAMES = INSTANCE_NAME + DB_DOMAIN -GLOBAL DATABASE NAME should be same as SERVICE_NAMES -If system ts is LMT then temporary tablespace is required. -if system ts is lmt then no dmt can be created in db. -When system ts is LMT then undo tbs is also must. -1 tbs can have max 1022 dbfs. -1…
Very clear article about oracle dataguard
http://www.dbazine.com/oracle/or-articles/liu4
oracle fast start failover best practice
http://www.oracle.com/technology/deploy/availability/pdf/MAA_WP_10gR2_FastStartFailoverBestPractices.pdf
Difference between SYNC and AFFIRM
LGWR SYNC AFFIRM in Oracle Data Guard is used for zero data loss. How does one ensure zero data loss? Well, the redo block generated at the primary has to reach the standby across the network (that’s where the SYNC part comes in – i.e. it is a synchronous network call), and then the block…
useful dg links
http://www.oracle.com/technology/obe/11gr2_db_prod/ha/dataguard/dg_broker/dg_broker.htm http://www.oracle.com/technology/obe/11gr2_db_prod/ha/dataguard/activedg/activedg.htm http://www.oracle.com/technology/obe/11gr2_db_prod/ha/dataguard/physstby/physstdby.htm
Does DBMS_JOB recompute the NEXT_DATE interval after or before
goal: Does DBMS_JOB recompute the NEXT_DATE interval after or before executing the procedure or job? fact: PL/SQL fix: The NEXT_DATE is computed AFTER the job gets executed successfully. The INTERVAL date function is evaluated immediately before a job is executed. If the job completes successfully, the date calculated from INTERVAL becomes the new NEXT_DATE. If…
Read More “Does DBMS_JOB recompute the NEXT_DATE interval after or before” »
Committing distributed transaction using commit force
Committing Using Only the Transaction ID The following SQL statement commits an in-doubt transaction: COMMIT FORCE ‘transaction_id’; The variable transaction_id is the identifier of the transaction as specified in either the LOCAL_TRAN_ID or GLOBAL_TRAN_ID columns of the DBA_2PC_PENDING data dictionary view. For example, assume that you query DBA_2PC_PENDING and determine that LOCAL_TRAN_ID for a distributed…
Read More “Committing distributed transaction using commit force” »
Rollback force for distributed transactions
FORCE Clause Specify FORCE to manually roll back an in-doubt distributed transaction. The transaction is identified by the text containing its local or global transaction ID. To find the IDs of such transactions, query the data dictionary view DBA_2PC_PENDING. A ROLLBACK statement with a FORCE clause rolls back only the specified transaction. Such a statement…