01-23-2020
Also, I noticed (my guess) is that your application is related to predictive analytics and perhaps algorithmic trading.
In that case, these algorithms rely heavily on historical data and (often expensive) analytics.
I recommend you do not delete any of these "analytic files" unless you are sure you have backup copies.
May I ask why you are doing this (deleting analytical files which you believe to be unused)?
Are you having a disk space issue?
8 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,
I have a directory which contains files.This Directory keeps getting in new files from time to time.I want to maintain only 15 files in that directory at any time and the old files should be deleted.
Eg:
Directory 'c' @'a/b/c contains:
1_a
2_a
3_a...
I want to delete all the old... (2 Replies)
Discussion started by: shiroh_1982
2 Replies
2. Programming
Hi All,
when I use the following analytic function in sql prompt, i am getting the result
count(emp_no) over (partition by emp_no )
/* select count(emp_no) over (partition by emp_no ) from temp */
but when i use the same analytic function in Pro*c i get the following error
Error... (2 Replies)
Discussion started by: quintet
2 Replies
3. Shell Programming and Scripting
So I have two files:
File1
pictures.txt 1.1 1.3
dance.txt 1.2 1.4
treehouse.txt 1.3 1.5
File2
pictures.txt 1.5 ref2313 1.4 ref2345 1.3 ref5432 1.2 ref4244
dance.txt 1.6 ref2342 1.5 ref2352 1.4 ref0695 1.3 ref5738 1.2 ref4948 1.1
treehouse.txt 1.6 ref8573 1.5 ref3284 1.4 ref5838... (24 Replies)
Discussion started by: linuxkid
24 Replies
4. Shell Programming and Scripting
Hi Friends,
I am new to this , I am working on AIX system and my scenario is to retrive the files from remote system and remove the files from the remote system after retreving files. I can able to retrieve the files but Can't remove files in remote system. Please check my code and help me out... (3 Replies)
Discussion started by: vinayparakala
3 Replies
5. Shell Programming and Scripting
Hi all, I have developed a shell script to copy the files from source to destination and simultaneously to delete the copied files in source. I can copy the files but the files cannot be deleted in source side. (3 Replies)
Discussion started by: Venkatesan
3 Replies
6. AIX
If you're familiar with vscsi mappings thru a VIO Server, you are probably aware, on an AIX 6.1 Client LPAR, that:
print cvai | kdbcan provide useful information to you.... like VIO Server name & vhost #. But, "cvai" does not appear to be part of the Kernel Debugger in AIX 5.3.
My question is... (3 Replies)
Discussion started by: The Doctor
3 Replies
7. AIX
Hi All,
I am trying to debug my core file using kdb.
When I try to get the stack trace I am facing this error.
core mapped from @ 700000000000000 to @ 70000000306fc04
Preserving 1680415 bytes of symbol table
Dump does not start with valid magic number
WARNING: Possibly truncated or... (2 Replies)
Discussion started by: Sachin1987
2 Replies
8. Shell Programming and Scripting
#!/bin/bash
#
name=$1
type=$2
number=1
for file in ./**
do
if
then
filenumber=00$number
elif
then
filenumber=0$number
fi
tempname="$name""$filenumber"."$type"
if (4 Replies)
Discussion started by: TheGreatGizmo
4 Replies
DISKPART(8) System Manager's Manual DISKPART(8)
NAME
diskpart - calculate default disk partition sizes
SYNOPSIS
/usr/sbin/diskpart [ -p ] [ -d ] disk-type
DESCRIPTION
Diskpart is used to calculate the disk partition sizes based on the default rules used at Berkeley. If the -p option is supplied, tables
suitable for inclusion in a device driver are produced. If the -d option is supplied, an entry suitable for inclusion in the disk descrip-
tion file /etc/disktab is generated; c.f. disktab(5). On disks that use bad144-style bad-sector forwarding, space is left in the last
partition on the disk for a bad sector forwarding table. The space reserved is one track for the replicated copies of the table and suffi-
cient tracks to hold a pool of 126 sectors to which bad sectors are mapped. For more information, see bad144(8).
The disk partition sizes are based on the total amount of space on the disk as given in the table below (all values are supplied in units
of 512 byte sectors). The `c' partition is, by convention, used to access the entire physical disk. The device driver tables include the
space reserved for the bad sector forwarding table in the `c' partition; those used in the disktab and default formats exclude reserved
tracks. In normal operation, either the `g' partition is used, or the `d', `e', and `f' partitions are used. The `g' and `f' partitions
are variable-sized, occupying whatever space remains after allocation of the fixed sized partitions. If the disk is smaller than 20
Megabytes, then diskpart aborts with the message ``disk too small, calculate by hand''.
Partition 20-60 MB 61-205 MB 206-355 MB 356+ MB
a 15884 15884 15884 15884
b 10032 33440 33440 66880
d 15884 15884 15884 15884
e unused 55936 55936 307200
h unused unused 291346 291346
If an unknown disk type is specified, diskpart will prompt for the required disk geometry information.
SEE ALSO
disktab(5), bad144(8)
BUGS
Certain default partition sizes are based on historical artifacts (e.g. RP06), and may result in unsatisfactory layouts.
When using the -d flag, alternate disk names are not included in the output.
4th Berkeley Distribution November 17, 1996 DISKPART(8)