Posts

Oracle: Track TEMP size

 SELECT sysdate,a.username, a.sid, a.serial#, a.osuser,  (b.blocks*d.block_size)/1048576 MB_used, c.sql_text FROM v$session a, v$tempseg_usage b, v$sqlarea c,      (select block_size from dba_tablespaces where tablespace_name='TEMP02') d     WHERE b.tablespace = 'TEMP02'     and a.saddr = b.session_addr     AND c.address= a.sql_address     AND c.hash_value = a.sql_hash_value     AND (b.blocks*d.block_size)/1048576 > 1024     ORDER BY b.tablespace, 6 desc;
Post a Comment
Read more

Oracle: To find COBOL version

 psoft-psfsps601.tmw.com:fsprod:/opt/lib/visualcobol/bin> cob -V version @(#)cob.c       6.0.0.84 PRN=KXCRH/AAD:Ao.U4.13.04 PTI=32/64 bit PTI=Micro Focus Visual COBOL Development Hub 6.0 - Patch Update 02 PTI=Patch Update 02 PTI=pkg_264847 PTI=MFInstaller I see no work (see `cob -?' for help)
Post a Comment
Read more

ORA: ORA-19809: limit exceeded for recovery files

 released channel: aux1 RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of Duplicate Db command at 01/24/2016 13:31:46 RMAN-05501: aborting duplication of target database RMAN-03015: error occurred in stored script Memory Script RMAN-06136: ORACLE error from auxiliary database: ORA-19809: limit exceeded for recovery files ORA-19804: cannot reclaim 512000000 bytes disk space from 2147483648 limit SQL> alter database open resetlogs; alter database open resetlogs * ERROR at line 1: ORA-00392: log 18 of thread 1 is being cleared, operation not allowed ORA-00312: online log 18 thread 1: '/usr/opt/app/oracle/admin/hrcnv1/flash01/HRCNV1/onlinelog/o1_mf_18_%u_.log' SQL> alter database clear unarchived logfile group 18; Database altered. SQL> alter database open resetlogs; alter database open ...
Post a Comment
Read more

Oracle: Fixing RMAN‑11003 with ORA‑00379 “no free buffers available”

Image
  Fixing RMAN‑11003 with ORA‑00379 “no free buffers available” This error means RMAN cannot allocate the required block buffers in the default buffer pool during the ALTER DATABASE RECOVER LOGFILE command, usually because the DB_16K_CACHE_SIZE (or other block buffer sizes) is set too low. databasewithsanga.blogspot.com Why it happens ORA‑00379 indicates the database has no free buffers in the default buffer pool for the requested block size (16K here) databasewithsanga.blogspot.com . RMAN needs these buffers to read and write recovery logfiles. If the parameter is zero or too small, the operation fails databasewithsanga.blogspot.com . This can occur after a restore/recovery in a new environment, or if parameters were reset. How to fix it You must allocate memory for the block buffers before retrying the recovery. Step‑by‑step (from Oracle docs and community guidance) databasewithsanga.blogspot.com Log in to the database as a privileged user (e.g., sys ). Check the current blo...
Post a Comment
Read more