Category: SQL scripts

http://www.toadworld.com/KNOWLEDGE/KnowledgeXpertforOracle/tabid/648/TopicID/2471975d4f31c8aa/Default.aspx

-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.

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 =…

Read More “TNSNAMES entries details” »

-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…

Read More “Oracle 11g Training on 29JAN1010” »

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 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” »

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…

Read More “Rollback force for distributed transactions” »

Check user$ table for same.

SELECT SID, SERIAL#, CONTEXT, SOFAR, TOTALWORK, ROUND(SOFAR/TOTALWORK*100,2) “% COMPLETE” FROM V$SESSION_LONGOPS WHERE OPNAME LIKE ‘RMAN%’ AND OPNAME NOT LIKE ‘%aggregate%’ AND TOTALWORK != 0 AND SOFAR TOTALWORK /

set lines 120 pages 500 col owner format a30 col segment_name format a30 col tab_sum format 999999999999999 col indx_sum format 999999999999999 col MB format 999999999 accept pvm_owner prompt ‘Enter Owner Name -> ‘ accept pvm_table prompt ‘Enter Table Name -> ‘ select tab.owner, tab.segment_name, tab.tablespace_name, (tab_sum+indx_sum)/(1024*1024) MB from (select p.owner, p.segment_name, p.tablespace_name, sum(p.bytes) tab_sum from…

Read More “Find_table_size.sql” »