Category: SQL scripts

Notes on v$transaction The information here contains the view description from the Oracle9i documentation Earlier versions of Oracle may not include all columns. The v$transaction view lists the active transactions in the system. Column Datatype Description ————- ————– ————————————– ADDR RAW(4) Address of transaction state object XIDUSN NUMBER Undo segment number XIDSLOT NUMBER Slot number…

Read More “V$transaction notes for finding XID composition.” »

Declare v_filehandle UTL_FILE.FILE_TYPE; file_dir VARCHAR2(50) :=’/db3/oracle/utlfiles’; begin t_file_name :=’Vatti_test.dat’; v_filehandle := UTL_FILE.FOPEN(file_dir, t_file_name, ‘w’); UTL_FILE.PUT_LINE(v_filehandle, ‘Hello TEST’); UTL_FILE.FCLOSE(v_filehandle); exception when others then dbms_output.put_line(sqlcode || ‘ ‘ || sqlerrm); end; /

TYPE VARCHAR2(17) Identifies the type of record section: DATABASE, CKPT PROGRESS, REDO THREAD, REDO LOG, DATAFILE, FILENAME, TABLESPACE, LOG HISTORY, OFFLINE RANGE, ARCHIVED LOG, BACKUP SET, BACKUP PIECE, BACKUP DATAFILE, BACKUP REDOLOG, DATAFILE COPY, BACKUP CORRUPTION, COPY CORRUPTION, DELETED OBJECT, or PROXY COPY RECORD_SIZE NUMBER Record size in bytes RECORDS_TOTAL NUMBER Number of records allocated…

Read More “V$CONTROLFILE_RECORD_SECTION reference notes.” »

V$ View Definitions Library Doc ID: Note:220021.1

(1) When you attempt to set the ‘Processes’ parameter to high value (for example> 14000), the instance startup fails with ORA-00064: object is too large to allocate on this O/S ORA-00064: object is too large to allocate on this O / S. Solution: Change PROCESSES parameter. or The workaround to bypass this limit is to…

Read More “ORA-00064: object is too large to allocate on this O/S during startup” »

ALL DB = Primary + DR databases. -> Implement checkfile concept so script will not page for planned maitenance. (1) Connect and update all Primary db for hang check. (2) Check for pmon for all db. (3) Check Alert log for ORA error for Primary database. (4) Purge Alert log of Primary and keep backup…

Read More “standard Monitoring – 1” »

FROM TUNINGDB21 (Target) =============== tuningdb21*-/db1/home/oracle/paresh ==>ping 10.180.1.144 10.180.1.144 is alive tuningdb21*-/db1/home/oracle/paresh ==>ping oem2k.1800flowers.int ping: unknown host oem2k.1800flowers.int tuningdb21*-/db1/home/oracle/paresh ==>nslookup 10.180.1.144 *** Can’t find server name for address 127.0.0.1: Unspecified error *** Default servers are not available tuningdb21*-/db1/home/oracle/paresh ==>nslookup oem2k.1800flowers.int *** Can’t find server name for address 127.0.0.1: Unspecified error *** Default servers are not available…

Read More “OEM-troubleshooting on 20-MAY-08” »

exp userid=vivek file=ats_florist_zips_20MAY08.dmp log=ats_florist_zips_20MAY08.log grants=N indexes=N tables=ats.ats_florist_zips triggers=N statistics=None feedback=5000 imp userid=vivek file=ats_florist_zips_20MAY08.dmp log=imp_ats_florist_zips_20MAY08.log buffer=20971520 grants=N indexes=N fromuser=ats touser=5049 commit=Y constraints=N feedback=5000 statistics=None alter table “5049”.ATS_FLORIST_ZIPS rename to ats_florist_zips_05_20_2008;

D:oracle_homesagent10gBIN> emctl status agent D:oracle_homesagent10gBIN> emctl start agent D:oracle_homesagent10gBIN> emctl stop agent yantradevdb-YANTRAD> emctl getemhome yantradevdb-YANTRAD> emctl upload

Problem Description: ==================== You receive the following error: ORA-01562: “failed to extend rollback segment number %s” Cause: Failure occurred when trying to extend rollback segment Action: This is normally followed by another error message that caused the failure. You may take the rollback segment offline to perform maintainence. Use the alter rollback segment offline command…

Read More “V$ROLLSTAT status is Full” »