Sponsored Content
Top Forums UNIX for Beginners Questions & Answers Deleting unused kdb+ analytic files in RedHat Post 303043296 by Neo on Thursday 23rd of January 2020 10:05:48 AM
Old 01-23-2020
Quote:
Originally Posted by Michael37
I don't want to truncate or reduce any tables. I want to delete analytic files that do not create any tables..
I could be wrong, but I don't think "analytic files" (your words) "create tables" (your words).

Normally tables are created when the DB is created or modified by the admin, and "analytics files" add rows to those tables.

Is this not how your DB works?

Sorry, I don't have hands on experience with kdb+ but it looks interesting Smilie
 

8 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Deleting old files

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

Analytic functions in Pro*c

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

Need help comparing two files and deleting some things in those files!

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

AIX system.... deleting files in remote directory after retrieving files

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

Deleting files

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

Kdb - vscsi disk mapping from AIX 5.3 CLIENT side

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

How to get the stack trace using kdb?

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

Bash script deleting my files, and editing files in subdirectories question

#!/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
Jifty::Script::Schema(3pm)				User Contributed Perl Documentation				Jifty::Script::Schema(3pm)

NAME
Jifty::Script::Schema - Create SQL to update or create your Jifty application's tables SYNOPSIS
jifty schema --setup Creates or updates your application's database tables Options: --print Print SQL, rather than executing commands --setup Upgrade or install the database, creating it if need be --create-database Only creates the database --drop-database Drops the database --ignore-reserved-words Ignore any SQL reserved words in schema definition --no-bootstrap don't run bootstrap --help brief help message --man full documentation DESCRIPTION
Manages your database. options --print Rather than actually running the database create/update/drop commands, Prints the commands to standard output --create-database Send a CREATE DATABASE command. Note that --setup, below, will automatically send a CREATE DATABASE if it needs one. This option is useful if you wish to create the database without creating any tables in it. --drop-database Send a DROP DATABASE command. Use this in conjunction with --setup to wipe and re-install the database. --setup Actually set up your app's tables. This creates the database if need be, and runs any commands needed to bring the tables up to date; these may include CREATE TABLE or ALTER TABLE commands. This option is assumed if the database does not exist, or the database version is not the same as the application's version. --ignore-reserved-words Ignore any SQL reserved words used in table or column definitions, if this option is not used and a reserved word is found it will cause an error. --no-bootstrap don't run Bootstrap, mostly to get rid of creating initial data --help Print a brief help message and exits. --man Prints the manual page and exits. DESCRIPTION
Looks for all model classes of your Jifty application and generates SQL statements to create or update database tables for all of the models. It either prints the SQL to standard output (--print) or actually issues the "CREATE TABLE" or "ALTER TABLE" statements on Jifty's database. (Note that even if you are just displaying the SQL, you need to have correctly configured your Jifty database in ProjectRoot"/etc/config.yml", because the SQL generated may depend on the database type.) By default checks for SQL reserved words in your table names and column definitions, throwing an error if any are found. If you want to permanently turn this behaviour off you can set CheckSchema to 0 in the database section of your applications config file. BUGS
Due to limitations of DBIx::DBSchema, this probably only works with PostgreSQL, MySQL and SQLite. It is possible that some of this functionality should be rolled into Jifty::DBI::SchemaGenerator METHODS
run Prints a help message if the users want it. If not, goes about its business. Sets up the environment, checks current database state, creates or deletes a database as necessary and then creates or updates your models' schema. run_upgrades Take the actions we need in order to bring an existing database up to current. setup_environment Sets up a minimal Jifty environment. schema Returns a Jifty::Schema object. probe_database_existence Probes our database to see if it exists and is up to date. create_all_tables Create all tables for this application's models. Generally, this happens on installation. create_tables_for_models TABLEs Given a list of items that are the scalar names of subclasses of Jifty::Record, either prints SQL or creates all those models in your database. upgrade_jifty_tables Upgrade Jifty's internal tables. upgrade_application_tables Upgrade the application's tables. upgrade_plugin_tables Upgrade the tables for each plugin. upgrade_tables BASECLASS, FROM, TO, [UPGRADECLASS] Given a "BASECLASS" to upgrade, and two version objects, "FROM" and "TO", performs the needed transforms to the database. "UPGRADECLASS", if not specified, defaults to "BASECLASS"::Upgrade manage_database_existence If the user wants the database created, creates the database. If the user wants the old database deleted, does that too. Exits with a return value of 1 if the database drop or create fails. perl v5.14.2 2011-02-10 Jifty::Script::Schema(3pm)
All times are GMT -4. The time now is 02:27 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy