Can delete trace files in bdump

Hi all,
i have lot of trace file is user dump directory i deleted all trace file.but i have confusion that whether to delete background trace files which are being generated by backgroung process in bdump directory.please any one suggest me what should i do. i know these kind of files ar only daignostic file.thanks alot in advance.

Hi,
What I usually do is scheduling a process that deletes old files (let's say older than 1 week or so).
As you said, this is for diagnostic only, and we usually don't need old files.
Decide how much time you want to keep, and delete older files (make sure to delete only .trc files, you should keep .log files more).
Liron Amitzi
Senior DBA consultant
[www.dbsnaps.com]
[www.orbiumsoftware.com]

Similar Messages

  • Cant reclaim free space from deleted trace file in bdump

    Hi ,
    Os : IBM aix 5.3
    Oracle : oracle 10.2.0.3 enterprise edition
    My /oracle space is only 2gb remaining .
    i deleted more 2gb trace files from bdump folder but when i check on os for free space its still showing that only 2gb is remaining for /oracle
    plz help me guys................

    Hi,
    You need to kill the OS PID's accessing the dump directory FS to get space released ..Refer below, how it can be done
    [oracle9i@M6UAT-DB:/home/oracle9i>]pwd
    /oracle/product/admin/M6CORP/udump
    [oracle9i@M6UAT-DB:/home/oracle9i>]fuser -c /oracle/product/admin/M6CORP/udump
    /oracle/product/admin/M6CORP/udump:   102612c  213018c  278544  327850c  340170c  356426c  466986c  495782c  516276c  565368c  610416c  626822c  647266c  696352c  704692c  708632c  745654c  753666c  766036c  778448c  794750c  798966c  852002c  864438c  880678c  884826c  892980c  905248c  925944c  938066c  950490c  958478c  966900c  974924c  979180c  991400c 1007816c 1015990c 1028342c 1032316c 1040494c 1044584c 1048790c 1064962c 1069198c 1077448c 1114204c 1130594c 1143014c 1146978c 1175638c 1191982c 1196276c 1216524c 1241106c 1249470c 1253520c 1261794c 1278186c 1290380c 1302720c 1306640c 1343604c 1347682c 1351874c 1355950c 1359928c 1372280c 1380602c 1384452c 1405106c 1454216c 1458424c 1462418c 1474594c 1482906c 1511456c 1515552c 1523846c 1527914c 1544408c 1548308c 1552392c 1560670c 1564732c 1568938c 1581288c 1597468c 1601616c 1630268c 1634464c 1650836c 1654816c 1667186c 1679502c 1683656c 1687722c 1695962c 1700028c 1703952c 1712276c 1720546c 1728524c 1732832c 1736736c 1744946c 1749098c 1757358c 1761474c 1769496c 1777784c 1781850c 1785944c 1789966c 1798162c 1806568c 1822912c 1851628c 1855700c 1867794c 1871934c 1892562c 1900660c 1904794c 1908936c 1917174c 1921244 1929398c 1937446c 1945762c 1957936c 1962036c 1994984c 1998914c 2039896c 2044122c 2060456c 2064548c 2068632c 2072672c 2076892c 2084908c 2089162c 2101466c 2105384c 2109494c 2125952c 2130136c 2134050c
    [oracle9i@M6UAT-DB:/home/oracle9i>]kill -9 102612  213018  278544  327850  340170  356426  466986  495782  516276  565368  610416  626822  647266Thanks,
    Ajay More
    http://moreajays.blogspot.com

  • Can I delete trace files

    Hi All
    Some time back I enabled "ALTER SYSTEM SET trace_enabled = TRUE,ALTER SESSION SET sql_trace = TRUE". So now I am not able to connect to the database. It is giving no space left error. So I suspect it is because of huge number of log files. Can I delete all *.trm and *.trc files or some are impotent. I am new to the Database.
    Thanks,
    Venkat.

    yes you can delete old files .Do not delete the recent files.

  • Need help deleting trace files

    Hi,
    I am new to Oracle RAC and I need to get rid of trace files since they are growing too big. I have one that is 22Gigs and I only have 60 Gigs available right now on that drive. I want to know if I can delete the file manually using the rm command.
    My trace files are in: /u01/app/oracle/diag/rdbms/.../.../trace
    The file I am concerned is called: "linux1_pz99_13299.trc" and "linux1_pz99_13299.trm"
    I am using Oracle 11.1.0.6.0 on Oracle Unbreakable Linux.
    Thanks for any help that can be provided.

    Is that really going to work?
    It is my understanding (supported by some inconclusive observations and experiments) that once a trace file grows beyond about 8 kilobytes Oracle will hang onto it in a death grip. You may delete it but Oracle will still have the file handle open and be writing to it.
    If the database is running on a Windows platform then an equivalent script will not even give the illusion of deleting the file.
    It used to be the case that switching trace file output to a different directory would cause Oracle to release the active trace files but now the trace directory is part of the ADR heirarchy so switching is a more global and more intrusive operation and could interfere with other diagnostics.
    You may have to rely on ADRCI's "purge" command unless there is a PL/SQL equivalent.
    I shall be very interested to see what others have to say.

  • Hp unix delete trace file

    Hi
    How to delete trace files on Hp ux for the past 3 days .
    Thank You

    963554 wrote:
    Hi
    How to delete trace files on Hp ux for the past 3 days .
    Thank YouThis question is more from Unix rather than Oracle.
    If you are using 11g, then why cant you go for using ADRCI utility, it can manage and trim the trace files
    http://gavinsoorma.com/2010/09/purging-trace-and-dump-files-with-11g-adrci/
    From unix, check links from google, sample is below.
    http://stackoverflow.com/questions/6995807/file-delete-older-than-1-day-question-on-hp-ux

  • How do I find 'Other' when it comes to my hard drive so I can delete unwanted files?

    Can someone please help me with this problem?
    When pulling up my system profiler, the catagories under storage are:
    Audio
    Movies
    Photos
    Apps
    Backups
    Other
    How do I find where the files that are located in the 'Other' group. So I can delete unwanted files from there?
    It seems to be taking up a lot of space on my hard drive, so I would like to know whats in it?
    My computer is a 2010 MacBook Pro 15" 2.4GHz Core i5, 64GBSSD, OSX Lion, let me know if you need more information than this?
    Thank you so much to anyone that can help me please.
    Scott

    Download OmniDiskSweeper from the Internet (free) and open it.  It will produce a display i a sequential format showing what you have on your MBP and the space each item is taking.  This should assist you in identifying all of your disk space 'hogs'.
    Ciao.

  • Hi I would like to know if I can delete my file fpsaud (Library Cache) because my app Clean my mac cannot do it. Is this operation dangerous? Thanks

    Hi I would like to know if I can delete my file psaud (Library Cache) because my App Mac Cleanse cannot do it. Can I move this this manually into the trash? Is it dangerous? Thanks

    You should have stopped after the first paragraph, because that was the only helpful part. You managed to sarcastically tell the questioner that he or she is dumb, throw in a couple of tidbits to convince any reader how smart you must be, and discourage any further learning.
    I saw nowhere in the original question where marcozroberto was complaining about speed.
    Caches, to us lesser mortals, are one of the first culprits that come to mind when all the cookies (including smart cookies) and browser cache have been erased, yet the ads on Web pages still want to know if I'd like to find a date tonight in my specific area code. So, I turn to sites like the Apple discussion pages to find out what other pieces of memory I have to flush to feel less stalked.  According to you, I shouldn't bother my poor head learning about this machine I bought, I should just trust  manufacturers and programmers to manage everything.
    I doubt fpsaud is really the problem with my browsing (my next guess is the IP address), but I won't learn that here.

  • How I can delete remained files on phone mem after...

    How I can delete remained files on phone mem after removing apps?
    Because it uses a lot of space and I can't use many apps and it says:
    "Memory card full.remove some files first."

    You cannot delete the default apps. Only those that you have added.
    Default apps wiggle, but they don't delete.

  • Non root user can delete root files, bug?

    We're having an odd permissions based problem on Solaris 10 u5 x86_64, (new install, fully patched as of 2 days ago) It means that non root users can delete root owned files, which is something I've never seen before, and I've been doing this for almost 10 years.
    We're installing into an 80Gb container on VMware ESX server 3.0.1. The OS takes 20Gb (2 processors, 4Gb memory, 8Gb swap) most of the remaining 60Gb is being used as both file systems and raw devices under disksuite as soft partitions. It's one of the file systems, /apps (where we plan to install sybase) that is giving us "issues"
    Essentially:
    # more /etc/vfstab |grep apps
    /dev/md/dsk/d0 /dev/md/rdsk/d0 /apps ufs 2 yes -
    # newfs -v /dev/md/rdsk/d0
    /dev/md/rdsk/d0: Unable to find Media type. Proceeding with system determined parameters.
    newfs: /dev/md/rdsk/d0 last mounted as /apps
    newfs: construct a new file system /dev/md/rdsk/d0: (y/n)? y
    mkfs -F ufs /dev/md/rdsk/d0 20971520 -1 -1 8192 1024 264 1 546 8192 t 0 -1 8 7 n
    /dev/md/rdsk/d0: Unable to find Media type. Proceeding with system determined parameters.
    Warning: 4096 sector(s) in last cylinder unallocated
    /dev/md/rdsk/d0: 20971520 sectors in 3414 cylinders of 48 tracks, 128 sectors
    10240.0MB in 214 cyl groups (16 c/g, 48.00MB/g, 5824 i/g)
    super-block backups (for fsck -F ufs -o b=#) at:
    32, 98464, 196896, 295328, 393760, 492192, 590624, 689056, 787488, 885920,
    20055584, 20154016, 20252448, 20350880, 20449312, 20547744, 20646176,
    20744608, 20843040, 20941472
    # mount /apps
    # ls -al /apps
    total 20
    drwxr-xr-x 3 root root 512 Sep 10 12:31 .
    drwxr-xr-x 38 root root 1024 Sep 10 12:09 ..
    drwx------ 2 root root 8192 Sep 10 12:31 lost+found
    # su - sybase
    Sun Microsystems Inc. SunOS 5.10 Generic January 2005
    sol10% cd /apps
    sol10% rm *
    rm: lost+found is a directory
    sol10% rm -rf *
    rm: cannot read directory lost+found: Permission denied
    sol10% ls -al
    total 20
    drwxr-xr-x 3 root root 512 Sep 10 12:31 .
    drwxr-xr-x 38 root root 1024 Sep 10 12:09 ..
    drwx------ 2 root root 8192 Sep 10 12:31 lost+found
    sol10% exit
    sol10% logout
    # chgrp sybase /apps
    # chmod g+w /apps
    # ls -ald /apps
    drwxrwxr-x 3 root sybase 512 Sep 10 12:31 /apps
    # ls -al /apps
    total 20
    drwxrwxr-x 3 root sybase 512 Sep 10 12:31 .
    drwxr-xr-x 38 root root 1024 Sep 10 12:09 ..
    drwx------ 2 root root 8192 Sep 10 12:31 lost+found
    # su - sybase
    Sun Microsystems Inc. SunOS 5.10 Generic January 2005
    sol10% cd /apps
    sol10% rm -rf *
    sol10% ls -al
    total 4
    drwxrwxr-x 2 root sybase 512 Sep 10 12:34 .
    drwxr-xr-x 38 root root 1024 Sep 10 12:09 ..
    sol10% id
    uid=***(sybase) gid=***(sybase)
    sol10% exit
    sol10% logout
    # pwd
    # ls -ald /apps
    drwxrwxr-x 2 root sybase 512 Sep 10 12:34 /apps
    # ls -al /apps
    total 4
    drwxrwxr-x 2 root sybase 512 Sep 10 12:34 .
    drwxr-xr-x 38 root root 1024 Sep 10 12:09 ..
    It's a new "bare metal" (in as much as there is no metal) install. I created the sybase user from scratch by hand editing passwd, group and shadow, buy copying and pasting the data out of the NIS maps. All I've done besides the install & patch is setup networking manually, and created the metadb's and the soft partitions and the mount points & newfs'ed & mounted three of them . I then changed ownership of /apps to be sybase:sybase, and handed it to the database team for the sybase install. they came back and said "should we be able to do this?" as they habitually run rm rf * knowing they can't delete root owned files, only now they can... This is true even if I just chgrp the directory and give them group write permissions. They can still delete anything owned by root, even if it doesn't have group permissions just like the lost+found directory. No other "real" machine we have, x86 or SPARC does this, but we've never installed u5 before either.
    As you can imagine losing the lost+found directory is a bit of a problem, however what's really worrying me is if they can do that, what happens when they run sybase as the sybase user? If it borks can they trash the OS and write/overwrite random files?
    It's a VM, so in as much that's not a problem, but the reason it's a VM is somebody wants to send a VM to a client as a demo, and at present it's highly unstable IMO.
    Does anyone have any idea where to start? My thoughts are that it may be a VMware issue, (though the hardware and the guest OS is supported) it could be a bug, because I've never seen that weird newfs error before, and then I found this:
    http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6622243
    Or it could be me, and the fact that I'm hand configuring it, and u5 now requires I do it "properly" with useradd, etc. I'd like to test, but the guy wants it built, and wants it now, so I patched it up, and gave it back to the database team and told them to be careful.
    I'd be interested in you opinions regardless.
    The full spec of the "machine" is below, sol10 is not it's name for obvious reasons, and I've hashed out the ID & GIUD for similar reasons.
    # uname -a
    SunOS sol10 5.10 Generic_127128-11 i86pc i386 i86pc
    # prtdiag
    System Configuration: VMware, Inc. VMware Virtual Platform
    BIOS Configuration: Phoenix Technologies LTD 6.00 09/06/2007
    ==== Processor Sockets ====================================
    Version Location Tag
    Pentium(R) Pro CPU socket #0
    Pentium(R) Pro CPU socket #1
    ==== Memory Device Sockets ================================
    Type Status Set Device Locator Bank Locator
    DRAM in use 0 RAM slot #0 RAM slot #0
    DRAM in use 0 RAM slot #1 RAM slot #1
    DRAM in use 0 RAM slot #2 RAM slot #2
    DRAM in use 0 RAM slot #3 RAM slot #3
    ==== On-Board Devices =====================================
    VMware SVGA II
    ES1371
    ==== Upgradeable Slots ====================================
    ID Status Type Description
    0 unknown ISA ISA Slot J8
    0 unknown ISA ISA Slot J9
    0 unknown ISA ISA Slot J10
    1 in use PCI PCI Slot J11
    2 in use PCI PCI Slot J12
    3 in use PCI PCI Slot J13
    4 available PCI PCI Slot J14
    # dmesg
    Wednesday, 10 September 2008 15:33:35 BST
    Sep 10 10:17:44 sol10 busra: [ID 490441 kern.info] NOTICE: ndi_ra_free: bad free, dip ffffffff803807a8, resource type memory
    Sep 10 10:17:44 sol10 busra: [ID 883242 kern.info] NOTICE: ndi_ra_free: freeing base 0xe0000, len 0x4000 overlaps with existing resource base 0x0, len 0xf4000000
    Sep 10 10:17:44 sol10 rootnex: [ID 349649 kern.info] pci0 at root: space 0 offset 0
    Sep 10 10:17:44 sol10 genunix: [ID 936769 kern.info] pci0 is /pci@0,0
    Sep 10 10:17:44 sol10 scsi: [ID 365881 kern.info] /pci@0,0/pci1000,30@10 (mpt0):
    Sep 10 10:17:44 sol10 Rev. 1 LSI, Inc. 1030 found.
    Sep 10 10:17:44 sol10 pcplusmp: [ID 637496 kern.info] pcplusmp: pci1000,30 (mpt) instance 0 vector 0x11 ioapic 0x2 intin 0x11 is bound to cpu 0
    Sep 10 10:17:44 sol10 scsi: [ID 365881 kern.info] /pci@0,0/pci1000,30@10 (mpt0):
    Sep 10 10:17:44 sol10 mpt0 Firmware version v0.0.0.0 (?)
    Sep 10 10:17:44 sol10 scsi: [ID 365881 kern.info] /pci@0,0/pci1000,30@10 (mpt0):
    Sep 10 10:17:44 sol10 mpt0: IOC Operational.
    Sep 10 10:17:44 sol10 pci: [ID 370704 kern.info] PCI-device: pci1000,30@10, mpt0
    Sep 10 10:17:44 sol10 genunix: [ID 936769 kern.info] mpt0 is /pci@0,0/pci1000,30@10
    Sep 10 10:17:44 sol10 scsi: [ID 193665 kern.info] sd0 at mpt0: target 0 lun 0
    Sep 10 10:17:44 sol10 genunix: [ID 936769 kern.info] sd0 is /pci@0,0/pci1000,30@10/sd@0,0
    Sep 10 10:17:44 sol10 genunix: [ID 408114 kern.info] /pci@0,0/pci1000,30@10/sd@0,0 (sd0) online
    Sep 10 10:17:44 sol10 unix: [ID 190185 kern.info] SMBIOS v2.31 loaded (1695 bytes)
    Sep 10 10:17:44 sol10 genunix: [ID 408114 kern.info] /cpus (cpunex0) online
    Sep 10 10:17:44 sol10 pseudo: [ID 129642 kern.info] pseudo-device: dld0
    Sep 10 10:17:44 sol10 genunix: [ID 936769 kern.info] dld0 is /pseudo/dld@0
    Sep 10 10:17:44 sol10 pcplusmp: [ID 637496 kern.info] pcplusmp: i8042 (i8042) instance 0 vector 0x1 ioapic 0x2 intin 0x1 is bound to cpu 1
    Sep 10 10:17:44 sol10 pcplusmp: [ID 398438 kern.info] pcplusmp: i8042 (i8042) instance #0 vector 0xc ioapic 0x2 intin 0xc is bound to cpu 1
    Sep 10 10:17:44 sol10 i8042: [ID 526150 kern.info] 8042 device: keyboard@0, kb8042 # 0
    Sep 10 10:17:44 sol10 genunix: [ID 936769 kern.info] kb80420 is /isa/i8042@1,60/keyboard@0
    Sep 10 10:17:44 sol10 i8042: [ID 526150 kern.info] 8042 device: mouse@1, mouse8042 # 0
    Sep 10 10:17:44 sol10 genunix: [ID 936769 kern.info] mouse80420 is /isa/i8042@1,60/mouse@1
    Sep 10 10:17:44 sol10 unix: [ID 950921 kern.info] cpu0: x86 (GenuineIntel family 6 model 15 step 8 clock 2000 MHz)
    Sep 10 10:17:44 sol10 unix: [ID 950921 kern.info] cpu0: Intel(r) Xeon(r) CPU E5335 @ 2.00GHz
    Sep 10 10:17:47 sol10 unix: [ID 950921 kern.info] cpu1: x86 (GenuineIntel family 6 model 15 step 8 clock 2000 MHz)
    Sep 10 10:17:47 sol10 unix: [ID 950921 kern.info] cpu1: Intel(r) Xeon(r) CPU E5335 @ 2.00GHz
    Sep 10 10:17:47 sol10 unix: [ID 557827 kern.info] cpu1 initialization complete - online
    Sep 10 10:17:47 sol10 rootnex: [ID 349649 kern.info] iscsi0 at root
    Sep 10 10:17:47 sol10 genunix: [ID 936769 kern.info] iscsi0 is /iscsi
    Sep 10 10:17:52 sol10 genunix: [ID 454863 kern.info] dump on /dev/dsk/c1t0d0s1 size 8197 MB
    Sep 10 10:17:53 sol10 pci: [ID 370704 kern.info] PCI-device: pci8086,7191@1, pci_pci0
    Sep 10 10:17:53 sol10 genunix: [ID 936769 kern.info] pci_pci0 is /pci@0,0/pci8086,7191@1
    Sep 10 10:17:54 sol10 mac: [ID 469746 kern.info] NOTICE: e1000g0 registered
    Sep 10 10:17:54 sol10 pcplusmp: [ID 637496 kern.info] pcplusmp: pci8086,100f (e1000g) instance 0 vector 0x12 ioapic 0x2 intin 0x12 is bound to cpu 0
    Sep 10 10:17:54 sol10 e1000g: [ID 766679 kern.info] Intel(R) PRO/1000 Network Connection, Driver Ver. 5.1.11
    Sep 10 10:17:54 sol10 pseudo: [ID 129642 kern.info] pseudo-device: zfs0
    Sep 10 10:17:54 sol10 genunix: [ID 936769 kern.info] zfs0 is /pseudo/zfs@0
    Sep 10 10:17:55 sol10 pseudo: [ID 129642 kern.info] pseudo-device: pm0
    Sep 10 10:17:55 sol10 genunix: [ID 936769 kern.info] pm0 is /pseudo/pm@0
    Sep 10 10:17:55 sol10 pseudo: [ID 129642 kern.info] pseudo-device: power0
    Sep 10 10:17:55 sol10 genunix: [ID 936769 kern.info] power0 is /pseudo/power@0
    Sep 10 10:17:56 sol10 pseudo: [ID 129642 kern.info] pseudo-device: devinfo0
    Sep 10 10:17:56 sol10 genunix: [ID 936769 kern.info] devinfo0 is /pseudo/devinfo@0
    Sep 10 10:17:56 sol10 rootnex: [ID 349649 kern.info] xsvc0 at root
    Sep 10 10:17:56 sol10 genunix: [ID 936769 kern.info] xsvc0 is /xsvc
    Sep 10 10:17:56 sol10 pseudo: [ID 129642 kern.info] pseudo-device: pseudo1
    Sep 10 10:17:56 sol10 genunix: [ID 936769 kern.info] pseudo1 is /pseudo/zconsnex@1
    Sep 10 10:17:56 sol10 pcplusmp: [ID 637496 kern.info] pcplusmp: lp (ecpp) instance 0 vector 0x7 ioapic 0x2 intin 0x7 is bound to cpu 1
    Sep 10 10:17:56 sol10 isa: [ID 202937 kern.info] ISA-device: ecpp0
    Sep 10 10:17:56 sol10 genunix: [ID 936769 kern.info] ecpp0 is /isa/lp@1,378
    Sep 10 10:17:56 sol10 pcplusmp: [ID 637496 kern.info] pcplusmp: asy (asy) instance 0 vector 0x4 ioapic 0x2 intin 0x4 is bound to cpu 0
    Sep 10 10:17:56 sol10 isa: [ID 202937 kern.info] ISA-device: asy0
    Sep 10 10:17:56 sol10 genunix: [ID 936769 kern.info] asy0 is /isa/asy@1,3f8
    Sep 10 10:17:56 sol10 pcplusmp: [ID 398438 kern.info] pcplusmp: asy (asy) instance #1 vector 0x3 ioapic 0x2 intin 0x3 is bound to cpu 0
    Sep 10 10:17:56 sol10 isa: [ID 202937 kern.info] ISA-device: asy1
    Sep 10 10:17:56 sol10 genunix: [ID 936769 kern.info] asy1 is /isa/asy@1,2f8
    Sep 10 10:17:56 sol10 pcplusmp: [ID 637496 kern.info] pcplusmp: ide (ata) instance 0 vector 0xe ioapic 0x2 intin 0xe is bound to cpu 1
    Sep 10 10:17:56 sol10 pcplusmp: [ID 637496 kern.info] pcplusmp: ide (ata) instance 0 vector 0xe ioapic 0x2 intin 0xe is bound to cpu 0
    Sep 10 10:17:56 sol10 genunix: [ID 640982 kern.info] ATAPI device at targ 0, lun 0 lastlun 0x0
    Sep 10 10:17:56 sol10 genunix: [ID 846691 kern.info] model VMware Virtual IDE CDROM Drive
    Sep 10 10:17:56 sol10 genunix: [ID 479077 kern.info] ATA/ATAPI-4 supported, majver 0x1e minver 0x17
    Sep 10 10:17:56 sol10 pci: [ID 370704 kern.info] PCI-device: ide@0, ata0
    Sep 10 10:17:56 sol10 genunix: [ID 936769 kern.info] ata0 is /pci@0,0/pci-ide@7,1/ide@0
    Sep 10 10:17:56 sol10 genunix: [ID 935449 kern.info] ATA DMA off: disabled. Control with "atapi-cd-dma-enabled" property
    Sep 10 10:17:56 sol10 genunix: [ID 882269 kern.info] PIO mode 4 selected
    Sep 10 10:17:56 sol10 genunix: [ID 935449 kern.info] ATA DMA off: disabled. Control with "atapi-cd-dma-enabled" property
    Sep 10 10:17:56 sol10 genunix: [ID 882269 kern.info] PIO mode 4 selected
    Sep 10 10:17:56 sol10 genunix: [ID 935449 kern.info] ATA DMA off: disabled. Control with "atapi-cd-dma-enabled" property
    Sep 10 10:17:56 sol10 genunix: [ID 882269 kern.info] PIO mode 4 selected
    Sep 10 10:17:56 sol10 genunix: [ID 935449 kern.info] ATA DMA off: disabled. Control with "atapi-cd-dma-enabled" property
    Sep 10 10:17:56 sol10 genunix: [ID 882269 kern.info] PIO mode 4 selected
    Sep 10 10:17:56 sol10 scsi: [ID 193665 kern.info] sd1 at ata0: target 0 lun 0
    Sep 10 10:17:56 sol10 genunix: [ID 936769 kern.info] sd1 is /pci@0,0/pci-ide@7,1/ide@0/sd@0,0
    Sep 10 10:17:56 sol10 pcplusmp: [ID 637496 kern.info] pcplusmp: fdc (fdc) instance 0 vector 0x6 ioapic 0x2 intin 0x6 is bound to cpu 1
    Sep 10 10:17:56 sol10 isa: [ID 202937 kern.info] ISA-device: fdc0
    Sep 10 10:17:56 sol10 fdc: [ID 114370 kern.info] fd0 at fdc0
    Sep 10 10:17:56 sol10 genunix: [ID 936769 kern.info] fd0 is /isa/fdc@1,3f0/fd@0,0
    Sep 10 10:17:56 sol10 genunix: [ID 314293 kern.info] device pciclass,030000@f(display#0) keeps up device sd@0,0(sd#1), but the latter is not power managed
    Sep 10 10:17:56 sol10 pseudo: [ID 129642 kern.info] pseudo-device: nvidia255
    Sep 10 10:17:56 sol10 genunix: [ID 936769 kern.info] nvidia255 is /pseudo/nvidia@255
    Sep 10 10:17:56 sol10 pseudo: [ID 129642 kern.info] pseudo-device: ramdisk1024
    Sep 10 10:17:56 sol10 genunix: [ID 936769 kern.info] ramdisk1024 is /pseudo/ramdisk@1024
    Sep 10 10:17:56 sol10 pseudo: [ID 129642 kern.info] pseudo-device: lockstat0
    Sep 10 10:17:56 sol10 genunix: [ID 936769 kern.info] lockstat0 is /pseudo/lockstat@0
    Sep 10 10:17:56 sol10 pseudo: [ID 129642 kern.info] pseudo-device: llc10
    Sep 10 10:17:56 sol10 genunix: [ID 936769 kern.info] llc10 is /pseudo/llc1@0
    Sep 10 10:17:56 sol10 pseudo: [ID 129642 kern.info] pseudo-device: lofi0
    Sep 10 10:17:56 sol10 genunix: [ID 936769 kern.info] lofi0 is /pseudo/lofi@0
    Sep 10 10:17:56 sol10 pseudo: [ID 129642 kern.info] pseudo-device: dtrace0
    Sep 10 10:17:56 sol10 genunix: [ID 936769 kern.info] dtrace0 is /pseudo/dtrace@0
    Sep 10 10:17:57 sol10 pseudo: [ID 129642 kern.info] pseudo-device: profile0
    Sep 10 10:17:57 sol10 genunix: [ID 936769 kern.info] profile0 is /pseudo/profile@0
    Sep 10 10:17:57 sol10 pseudo: [ID 129642 kern.info] pseudo-device: systrace0
    Sep 10 10:17:57 sol10 genunix: [ID 936769 kern.info] systrace0 is /pseudo/systrace@0
    Sep 10 10:17:57 sol10 pseudo: [ID 129642 kern.info] pseudo-device: fbt0
    Sep 10 10:17:57 sol10 genunix: [ID 936769 kern.info] fbt0 is /pseudo/fbt@0
    Sep 10 10:17:57 sol10 pseudo: [ID 129642 kern.info] pseudo-device: sdt0
    Sep 10 10:17:57 sol10 genunix: [ID 936769 kern.info] sdt0 is /pseudo/sdt@0
    Sep 10 10:17:57 sol10 pseudo: [ID 129642 kern.info] pseudo-device: fasttrap0
    Sep 10 10:17:57 sol10 genunix: [ID 936769 kern.info] fasttrap0 is /pseudo/fasttrap@0
    Sep 10 10:17:57 sol10 pseudo: [ID 129642 kern.info] pseudo-device: fcp0
    Sep 10 10:17:57 sol10 genunix: [ID 936769 kern.info] fcp0 is /pseudo/fcp@0
    Sep 10 10:17:57 sol10 pseudo: [ID 129642 kern.info] pseudo-device: fcsm0
    Sep 10 10:17:57 sol10 genunix: [ID 936769 kern.info] fcsm0 is /pseudo/fcsm@0
    Sep 10 10:17:57 sol10 pseudo: [ID 129642 kern.info] pseudo-device: lx_systrace0
    Sep 10 10:17:57 sol10 genunix: [ID 936769 kern.info] lx_systrace0 is /pseudo/lx_systrace@0
    Sep 10 10:17:57 sol10 pseudo: [ID 129642 kern.info] pseudo-device: ucode0
    Sep 10 10:17:57 sol10 genunix: [ID 936769 kern.info] ucode0 is /pseudo/ucode@0
    Sep 10 10:17:57 sol10 pseudo: [ID 129642 kern.info] pseudo-device: fssnap0
    Sep 10 10:17:57 sol10 genunix: [ID 936769 kern.info] fssnap0 is /pseudo/fssnap@0
    Sep 10 10:17:57 sol10 pseudo: [ID 129642 kern.info] pseudo-device: winlock0
    Sep 10 10:17:57 sol10 genunix: [ID 936769 kern.info] winlock0 is /pseudo/winlock@0
    Sep 10 10:17:57 sol10 pseudo: [ID 129642 kern.info] pseudo-device: vol0
    Sep 10 10:17:57 sol10 genunix: [ID 936769 kern.info] vol0 is /pseudo/vol@0
    Sep 10 10:17:57 sol10 pseudo: [ID 129642 kern.info] pseudo-device: rsm0
    Sep 10 10:17:57 sol10 genunix: [ID 936769 kern.info] rsm0 is /pseudo/rsm@0
    Sep 10 10:17:57 sol10 pseudo: [ID 129642 kern.info] pseudo-device: pool0
    Sep 10 10:17:57 sol10 genunix: [ID 936769 kern.info] pool0 is /pseudo/pool@0
    Sep 10 10:17:57 sol10 ipf: [ID 774698 kern.info] IP Filter: v4.1.9, running.
    Sep 10 10:18:05 sol10 nfs4cbd[395]: [ID 867284 daemon.notice] nfsv4 cannot determine local hostname binding for transport tcp - delegations will not be available on this transport
    Sep 10 10:18:10 sol10 sendmail[598]: [ID 702911 mail.crit] My unqualified host name (localhost) unknown; sleeping for retry
    Sep 10 10:18:10 sol10 sendmail[600]: [ID 702911 mail.crit] My unqualified host name (localhost) unknown; sleeping for retry
    Sep 10 10:18:17 sol10 mac: [ID 736570 kern.info] NOTICE: e1000g0 unregistered
    Sep 10 10:19:10 sol10 sendmail[598]: [ID 702911 mail.alert] unable to qualify my own domain name (localhost) -- using short name
    Sep 10 10:19:10 sol10 sendmail[600]: [ID 702911 mail.alert] unable to qualify my own domain name (localhost) -- using short name
    Sep 10 10:20:10 sol10 pseudo: [ID 129642 kern.info] pseudo-device: devinfo0
    Sep 10 10:20:10 sol10 genunix: [ID 936769 kern.info] devinfo0 is /pseudo/devinfo@0
    Sep 10 10:24:54 sol10 mac: [ID 469746 kern.info] NOTICE: e1000g0 registered
    Sep 10 10:24:54 sol10 pcplusmp: [ID 637496 kern.info] pcplusmp: pci8086,100f (e1000g) instance 0 vector 0x12 ioapic 0x2 intin 0x12 is bound to cpu 0
    Sep 10 10:24:54 sol10 e1000g: [ID 766679 kern.info] Intel(R) PRO/1000 Network Connection, Driver Ver. 5.1.11
    Sep 10 10:24:59 sol10 e1000g: [ID 801725 kern.info] NOTICE: pci8086,100f - e1000g[0] : Adapter 1000Mbps full duplex copper link is up.
    Sep 10 10:28:21 sol10 in.routed[502]: [ID 798604 daemon.error] empty response from 129.0.1.124
    Sep 10 10:35:17 sol10 genunix: [ID 935449 kern.info] ATA DMA off: disabled. Control with "atapi-cd-dma-enabled" property
    Sep 10 10:35:17 sol10 genunix: [ID 882269 kern.info] PIO mode 4 selected
    Sep 10 10:35:17 sol10 genunix: [ID 935449 kern.info] ATA DMA off: disabled. Control with "atapi-cd-dma-enabled" property
    Sep 10 10:35:17 sol10 genunix: [ID 882269 kern.info] PIO mode 4 selected
    Sep 10 10:35:17 sol10 genunix: [ID 935449 kern.info] ATA DMA off: disabled. Control with "atapi-cd-dma-enabled" property
    Sep 10 10:35:17 sol10 genunix: [ID 882269 kern.info] PIO mode 4 selected
    Sep 10 10:35:17 sol10 genunix: [ID 935449 kern.info] ATA DMA off: disabled. Control with "atapi-cd-dma-enabled" property
    Sep 10 10:35:17 sol10 genunix: [ID 882269 kern.info] PIO mode 4 selected
    Sep 10 10:35:17 sol10 pcplusmp: [ID 637496 kern.info] pcplusmp: lp (ecpp) instance 0 vector 0x7 ioapic 0x2 intin 0x7 is bound to cpu 1
    Sep 10 10:35:17 sol10 isa: [ID 202937 kern.info] ISA-device: ecpp0
    Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] ecpp0 is /isa/lp@1,378
    Sep 10 10:35:17 sol10 pcplusmp: [ID 637496 kern.info] pcplusmp: asy (asy) instance 0 vector 0x4 ioapic 0x2 intin 0x4 is bound to cpu 0
    Sep 10 10:35:17 sol10 isa: [ID 202937 kern.info] ISA-device: asy0
    Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] asy0 is /isa/asy@1,3f8
    Sep 10 10:35:17 sol10 pcplusmp: [ID 398438 kern.info] pcplusmp: asy (asy) instance #1 vector 0x3 ioapic 0x2 intin 0x3 is bound to cpu 0
    Sep 10 10:35:17 sol10 isa: [ID 202937 kern.info] ISA-device: asy1
    Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] asy1 is /isa/asy@1,2f8
    Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: nvidia255
    Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] nvidia255 is /pseudo/nvidia@255
    Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: ramdisk1024
    Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] ramdisk1024 is /pseudo/ramdisk@1024
    Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: lockstat0
    Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] lockstat0 is /pseudo/lockstat@0
    Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: llc10
    Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] llc10 is /pseudo/llc1@0
    Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: lofi0
    Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] lofi0 is /pseudo/lofi@0
    Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: profile0
    Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] profile0 is /pseudo/profile@0
    Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: systrace0
    Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] systrace0 is /pseudo/systrace@0
    Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: fbt0
    Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] fbt0 is /pseudo/fbt@0
    Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: sdt0
    Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] sdt0 is /pseudo/sdt@0
    Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: fcp0
    Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] fcp0 is /pseudo/fcp@0
    Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: fcsm0
    Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] fcsm0 is /pseudo/fcsm@0
    Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: lx_systrace0
    Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] lx_systrace0 is /pseudo/lx_systrace@0
    Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: ucode0
    Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] ucode0 is /pseudo/ucode@0
    Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: fssnap0
    Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] fssnap0 is /pseudo/fssnap@0
    Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: winlock0
    Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] winlock0 is /pseudo/winlock@0
    Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: pm0
    Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] pm0 is /pseudo/pm@0
    Sep 10 10:35:17 sol10 pseudo: [ID 129642 kern.info] pseudo-device: rsm0
    Sep 10 10:35:17 sol10 genunix: [ID 936769 kern.info] rsm0 is /pseudo/rsm@0
    Sep 10 10:55:50 sol10 genunix: [ID 935449 kern.info] ATA DMA off: disabled. Control with "atapi-cd-dma-enabled" property
    Sep 10 10:55:50 sol10 genunix: [ID 882269 kern.info] PIO mode 4 selected
    Sep 10 10:55:50 sol10 genunix: [ID 935449 kern.info] ATA DMA off: disabled. Control with "atapi-cd-dma-enabled" property
    Sep 10 10:55:50 sol10 genunix: [ID 882269 kern.info] PIO mode 4 selected
    Sep 10 10:55:50 sol10 genunix: [ID 935449 kern.info] ATA DMA off: disabled. Control with "atapi-cd-dma-enabled" property
    Sep 10 10:55:50 sol10 genunix: [ID 882269 kern.info] PIO mode 4 selected
    Sep 10 10:55:50 sol10 genunix: [ID 935449 kern.info] ATA DMA off: disabled. Control with "atapi-cd-dma-enabled" property
    Sep 10 10:55:50 sol10 genunix: [ID 882269 kern.info] PIO mode 4 selected
    Sep 10 11:28:55 sol10 in.routed[502]: [ID 798604 daemon.error] empty response from 129.0.1.124
    Sep 10 12:28:56 sol10 in.routed[502]: [ID 798604 daemon.error] empty response from 129.0.1.124
    Sep 10 13:29:01 sol10 in.routed[502]: [ID 798604 daemon.error] empty response from 129.0.1.124
    Sep 10 14:29:10 sol10 in.routed[502]: [ID 798604 daemon.error] empty response from 129.0.1.124
    Sep 10 15:29:38 sol10 in.routed[502]: [ID 798604 daemon.error] empty response from 129.0.1.124
    # prtconf
    System Configuration: Sun Microsystems i86pc
    Memory size: 4132 Megabytes
    System Peripherals (Software Nodes):
    i86pc
    scsi_vhci, instance #0
    isa, instance #0
    i8042, instance #0
    keyboard, instance #0
    mouse, instance #0
    lp, instance #0
    asy, instance #0
    asy, instance #1
    fdc, instance #0
    fd, instance #0
    pci, instance #0
    pci15ad,1976 (driver not attached)
    pci8086,7191, instance #0
    pci15ad,1976 (driver not attached)
    pci-ide, instance #0
    ide, instance #0
    sd, instance #1
    ide (driver not attached)
    pci15ad,1976 (driver not attached)
    display, instance #0
    pci1000,30, instance #0
    sd, instance #0
    pci15ad,750, instance #0
    iscsi, instance #0
    pseudo, instance #0
    options, instance #0
    agpgart, instance #0
    xsvc, instance #0
    objmgr, instance #0
    acpi (driver not attached)
    used-resources (driver not attached)
    cpus, instance #0
    cpu (driver not attached)
    cpu (driver not attached)
    # format
    Searching for disks...done
    AVAILABLE DISK SELECTIONS:
    0. c1t0d0 <DEFAULT cyl 10440 alt 2 hd 255 sec 63>
    /pci@0,0/pci1000,30@10/sd@0,0
    Specify disk (enter its number): 0
    selecting c1t0d0
    [disk formatted]
    Warning: Current Disk has mounted partitions.
    /dev/dsk/c1t0d0s0 is currently mounted on /. Please see umount(1M).
    /dev/dsk/c1t0d0s1 is currently used by swap. Please see swap(1M).
    /dev/dsk/c1t0d0s3 is currently mounted on /usr. Please see umount(1M).
    /dev/dsk/c1t0d0s4 is currently mounted on /var. Please see umount(1M).
    /dev/dsk/c1t0d0s5 is currently mounted on /opt. Please see umount(1M).
    /dev/dsk/c1t0d0s6 is part of SVM volume sp:d8. Please see metaclear(1M).
    /dev/dsk/c1t0d0s7 contains an SVM mdb. Please see metadb(1M).
    FORMAT MENU:
    disk - select a disk
    type - select (define) a disk type
    partition - select (define) a partition table
    current - describe the current disk
    format - format and analyze the disk
    fdisk - run the fdisk program
    repair - repair a defective sector
    label - write label to the disk
    analyze - surface analysis
    defect - defect list management
    backup - search for backup labels
    verify - read and display labels
    save - save new disk/partition definitions
    inquiry - show vendor, product and revision
    volname - set 8-character volume name
    !<cmd> - execute <cmd>, then return
    quit
    format> p
    PARTITION MENU:
    0 - change `0' partition
    1 - change `1' partition
    2 - change `2' partition
    3 - change `3' partition
    4 - change `4' partition
    5 - change `5' partition
    6 - change `6' partition
    7 - change `7' partition
    select - select a predefined table
    modify - modify a predefined partition table
    name - name the current table
    print - display the current table
    label - write partition map and label to the disk
    !<cmd> - execute <cmd>, then return
    quit
    partition> p
    Current partition table (original):
    Total disk cylinders available: 10440 + 2 (reserved cylinders)
    Part Tag Flag Cylinders Size Blocks
    0 root wm 1 - 131 1.00GB (131/0/0) 2104515
    1 swap wu 132 - 1176 8.01GB (1045/0/0) 16787925
    2 backup wm 0 - 10439 79.97GB (10440/0/0) 167718600
    3 usr wm 1177 - 1829 5.00GB (653/0/0) 10490445
    4 var wm 1830 - 2091 2.01GB (262/0/0) 4209030
    5 unassigned wm 2092 - 2614 4.01GB (523/0/0) 8401995
    6 unassigned wm 2617 - 10439 59.93GB (7823/0/0) 125676495
    7 unassigned wm 2615 - 2616 15.69MB (2/0/0) 32130
    8 boot wu 0 - 0 7.84MB (1/0/0) 16065
    9 unassigned wm 0 0 (0/0/0) 0
    partition> quit
    FORMAT MENU:
    disk - select a disk
    type - select (define) a disk type
    partition - select (define) a partition table
    current - describe the current disk
    format - format and analyze the disk
    fdisk - run the fdisk program
    repair - repair a defective sector
    label - write label to the disk
    analyze - surface analysis
    defect - defect list management
    backup - search for backup labels
    verify - read and display labels
    save - save new disk/partition definitions
    inquiry - show vendor, product and revision
    volname - set 8-character volume name
    !<cmd> - execute <cmd>, then return
    quit
    format> q
    # metastat -p
    d8 -p c1t0d0s6 -o 109973513 -b 61440
    d7 -p c1t0d0s6 -o 109461512 -b 512000
    d6 -p c1t0d0s6 -o 109051911 -b 409600
    d5 -p c1t0d0s6 -o 88080390 -b 20971520
    d4 -p c1t0d0s6 -o 67108869 -b 20971520
    d3 -p c1t0d0s6 -o 46137348 -b 20971520
    d2 -p c1t0d0s6 -o 41943043 -b 4194304
    d1 -p c1t0d0s6 -o 20971522 -b 20971520
    d0 -p c1t0d0s6 -o 1 -b 20971520

    An easy way to think of it is this -- everything in Unix is a file. Including directories; they are just a file which contains a list of the files in that directory, and pointers to them.
    If the 'sybase' user has write permission on the directory, they have permission to edit that "list", and can add or remove files to the list. It doesn't matter who the files on the list belong to, because the files are not what is being modified. Only the list of files is being modified. (Of course, in Unix, if you erase the file's listing from all of the lists it's on, the file itself goes away for housekeeping purposes.)
    One thing that would have stopped the 'sybase' user from removing the lost+found directory is if that directory itself had files in it -- without write permission to the lost+found directory, that user could not have removed those files, and since one cannot remove a non-empty directory, that operation would have failed. Since lost+found was empty in this case, it could be removed simply by having permission to write to the /apps directory.
    This behavior does change if you set the sticky bit on the directory -- in that case, files may only be removed by the owner of the file or directory, or if the user has write permission to the file. This would have prevented the sybase user from removing the lost+found directory. (Note, this also applies to the 'rename' function call.) This would probably be the best way to handle your situation, since you apparently do want the sybase user to be able to add files to /apps, but do not want them to be able to remove lost+found.
    Edited by: MadBishop on Sep 12, 2008 7:46 AM

  • Trace file in bdump (SQL ID with large Version Count encountered.)

    Hi, all.
    I found tons of this trace file in one of my oracle servers. What does this mean? did anyone ever see this? How to solve it?
    Thanks.
    *** ACTION NAME:(Auto-Flush Slave Action) 2009-01-28 18:00:10.985
    *** MODULE NAME:(MMON_SLAVE) 2009-01-28 18:00:10.985
    *** SERVICE NAME:(SYS$BACKGROUND) 2009-01-28 18:00:10.985
    *** SESSION ID:(84.5246) 2009-01-28 18:00:10.985
    SQL ID with large Version Count encountered.
    SQL Id: b221muwskhm6
    Version Count: 299, Parse Calls: 12, Shareable Mem: 11907351
    Elapsed Time: 0, CPU Time: 0, Executions: 0
    Disk reads: 0, Buffer Gets: 0, I/O Wait Class: 0
    Application WC: 0, Concurrency WC: 0, Cluster WC: 0

    Refer Oracle Support note 4632024.8

  • Can anybody recommend a program that can delete ghost files in my Itunes library?

    I have a HUGE music library and really don't have that kinda time to delete these ghost files. I also don't know which are all ghost files since I have to keep clicking on each song to figure it out. Is there a program to delete these ghost files?
    Any help would be greatly appreciated.
    Thanks in advance,
    Chris

    You can use iTunes Folder Watch with its option to Check for dead tracks on startup as a way to clean out dead links. If your library contains both originals and duplicates of the same tracks only one of which is broken then you might find my script DeDuper useful.
    tt2

  • How to find out the Correct Controlfile script Trace .trc file in /bdump

    Hi Guys
    This is the most childish queries in this forum ..
    I wanna know how to Find out the correct trace file when we Issue alter database backup controlfile to trace at sqlprompt for Creating controlfile script.
    As i find it a bit confusing to go through the same Date & almost same time .trc files out of hundreds of trace file in /bdump directory to find the correct one.
    if we 've to find the Alert log file in /bdump directory $ ls -l al* & we get the alert log file .... if there is any similar way to find out the controlfile script Trace file ?
    Thanks & regards
    MZ

    MZ_AppsDBA wrote:
    Hi Guys
    This is the most childish queries in this forum ..
    I wanna know how to Find out the correct trace file when we Issue alter database backup controlfile to trace at sqlprompt for Creating controlfile script.
    As i find it a bit confusing to go through the same Date & almost same time .trc files out of hundreds of trace file in /bdump directory to find the correct one.
    if we 've to find the Alert log file in /bdump directory $ ls -l al* & we get the alert log file .... if there is any similar way to find out the controlfile script Trace file ?
    Thanks & regards
    MZcreation of the does not happen automatically. What script, and when does it run, do you have that creates the control file trace? Look for files in that time frame. Better, modify that script to specifically name the file .. BACKUP CONTROLFILE TO TRACE AS ....

  • I keep getting an error stating that my disk is full in syslog. The file is empty and I want to stop it from logging data. Can I just delete the file?

    Can I just delete the syslog file?

    Hello,
    Yes, you can delete the file. A new file in Syslog directory is started each time that LabVIEW and the Tag Engine is started. You can either manually delete old files or write a simple VI to automatically delete files that are older than a certain number of days.
    As an alternative, you can save these files into another folder, just to free up syslog directory space, and still have these history files for later use.
    Zvezdana S.
    National Instruments

  • Can I free up some disk space by deleting preview files?

    Help please anyone!!
    I'm new working with CS4, my hard disk ran out of space therefore I'm unable to transcode my project in Encore, and I'm also unable to burn a DVD in premiere because of no enough hard disk space. I read somewhere that I can delete preview files with deleting files in the actual project. is it truth?  Any suggestions?

    Yes, so long as you do not Render again. Do not delete your .CFA and .PEK files, as they will just be regenerated, when you load the Project.
    However, you are likely to not gain that much additional space. The best solution would be to add more HDD's. I'd try doing an Archive of any older Projects, and cleaning off (obviously Moving to an external) any unused media files.
    On my laptop, I also have had great experience editing to/from FW-800 externals. If you have, or can add, eSATA, that would be even better. Still, I'd pick up a handful of 1TB internals first.
    Good luck,
    Hunt

  • I have a Macbook Air and the start up disk is full so it won't boot up.  How can I get it to boot so I can delete files?

    I have a Macbook Air and the start up disk is full so it will not boot up.  How can I boot it up so I can delete some files?

    You will have to see about booting it from another drive or USB flash drive or another computer. When you are able to then see the following:
    Freeing Up Space on The Hard Drive
      1. See Lion's Storage Display.
      2. You can remove data from your Home folder except for the /Home/Library/ folder.
      3. Visit The XLab FAQs and read the FAQ on freeing up space on your hard drive.
      4. Also see Freeing space on your Mac OS X startup disk.
      5. See Where did my Disk Space go?.
      6. See The Storage Display.
    You must Empty the Trash in order to recover the space they occupied on the hard drive.
    You should consider replacing the drive with a larger one. Check out OWC for drives, tutorials, and toolkits.
    Try using OmniDiskSweeper 1.8 or GrandPerspective to search your drive for large files and where they are located.

Maybe you are looking for