05-31-2019
Not sure why the system was complaining about the INDEX file, However, when I re-ran the make_config for all the different images, it started working. Thanks for the link.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I want to deal with several data, i.e., data.*.txt with following structure
MSG|20010102|123 125 4562 409|SEND
MSG|20010102|120 230|SEND
MSG|20010102|120 204 5071|SEND
MSG|20010103|2 11 1098 9810|SEND
......
index file index.txt is
11
201
298
100
......
What I want to do is:
1)... (0 Replies)
Discussion started by: zhynxn
0 Replies
2. Filesystems, Disks and Memory
why do inode indices starts from 1 unlike array indexes which starts from 0
its a question from "the design of unix operating system" of maurice j bach
id be glad if i get to know the answer quickly
:) (0 Replies)
Discussion started by: sairamdevotee
0 Replies
3. UNIX for Dummies Questions & Answers
brothers why inode index starts from 1 unlike array inex which starts from 0
its a question from the design of unix operating system of maurice j.bach
i need to know the answer urgently...someone help please (1 Reply)
Discussion started by: sairamdevotee
1 Replies
4. Solaris
Hi All,
We have the JMS Queue startup script S52imq and some other scripts in our solaris server 5.8 version. now unknowingly something happend to those scripts and its lost. How can I recreate those scripts again to start the JMQ queue again?
We have Solaris 5.10 version which is having... (3 Replies)
Discussion started by: nsurendiran
3 Replies
5. UNIX for Dummies Questions & Answers
Dear Friends,
I have messed up with my .bashrc file (something I have deleted) and now i can't login back to system..
any Idea..
I can do login with other login and password.. but I dont have root password because of security reason...
If I ask root then It will take about 4 -5 days to go... (4 Replies)
Discussion started by: umeshjaviya
4 Replies
6. Shell Programming and Scripting
Hi All,
I have a file (FileNames.txt) which contains the following data in it.
$ cat FileNames.txt
MYFILE17XXX208Sep191307.csv
MYFILE19XXX208Sep192124.csv
MYFILE20XXX208Sep192418.csv
MYFILE22XXX208Sep193234.csv
MYFILE21XXX208Sep193018.csv
MYFILE24XXX208Sep194053.csv... (5 Replies)
Discussion started by: krish_indus
5 Replies
7. Shell Programming and Scripting
Hello,
I recently just switched my phphandler to suPHP on my server in order to increase security a bit. I am working with 2 scripts, one of which is vbulletin forums and the other is custom. The vbulletin forum avatars are all symbolic links to pictures in the other custom script. When I... (2 Replies)
Discussion started by: ambition13
2 Replies
8. UNIX for Dummies Questions & Answers
Hi,
I am working off of a MacBook Pro OSx 10.5.8.
I have a tab deliminted text file on my desktop that I created in excel. It has 4 columns and 20,000 rows. When I scroll down it in excel, everything lines up perfectly, and is where it is supposed to be. After copying it into my terminal... (6 Replies)
Discussion started by: lrae
6 Replies
9. Shell Programming and Scripting
Hi all,
i have a small script to remove locks for the prevous day and create new lock for processing in the path on my server
i have made something like this
#!/bin/sh
#lock_remover
#script to remove regular lockfiles and hang
curr_month=`date "+%b"`
2day=`date "+%_d"`
cd... (4 Replies)
Discussion started by: godie_b_w
4 Replies
10. UNIX for Dummies Questions & Answers
I have a BIG problem...
I host a public (Debian) repository on Cydia (for jailbroken iphones). I use my home Mac running Ubuntu in VMWare Fusion. For the repository, I have to have 5 items in a folder to make it 'live:'
1. deb_files folder (to hold my Debian packages)
2. Packages file
3.... (0 Replies)
Discussion started by: thazsar
0 Replies
LEARN ABOUT REDHAT
reindex
REINDEX(7) SQL Commands REINDEX(7)
NAME
REINDEX - rebuild corrupted indexes
SYNOPSIS
REINDEX { TABLE | DATABASE | INDEX } name [ FORCE ]
INPUTS
TABLE Recreate all indexes of a specified table.
DATABASE
Recreate all system indexes of a specified database. (User-table indexes are not included.)
INDEX Recreate a specified index.
name The name of the specific table/database/index to be reindexed. Table and index names may be schema-qualified.
FORCE Force rebuild of system indexes. Without this keyword REINDEX skips system indexes that are not marked invalid. FORCE is irrelevant
for REINDEX INDEX, or when reindexing user indexes.
OUTPUTS
REINDEX
Message returned if the table is successfully reindexed.
DESCRIPTION
REINDEX is used to rebuild corrupted indexes. Although in theory this should never be necessary, in practice indexes may become corrupted
due to software bugs or hardware failures. REINDEX provides a recovery method.
REINDEX also removes certain dead index pages that can't be reclaimed any other way. See the "Routine Reindexing" section in the manual for
more information.
If you suspect corruption of an index on a user table, you can simply rebuild that index, or all indexes on the table, using REINDEX INDEX
or REINDEX TABLE.
Note: Another approach to dealing with a corrupted user-table index is just to drop and recreate it. This may in fact be preferable
if you would like to maintain some semblance of normal operation on the table meanwhile. REINDEX acquires exclusive lock on the ta-
ble, while CREATE INDEX only locks out writes not reads of the table.
Things are more difficult if you need to recover from corruption of an index on a system table. In this case it's important for the backend
doing the recovery to not have used any of the suspect indexes itself. (Indeed, in this sort of scenario you may find that backends are
crashing immediately at start-up, due to reliance on the corrupted indexes.) To recover safely, the postmaster must be shut down and a
stand-alone PostgreSQL backend must be started instead, giving it the command-line options -O and -P (these options allow system table mod-
ifications and prevent use of system indexes, respectively). Then issue REINDEX INDEX, REINDEX TABLE, or REINDEX DATABASE depending on how
much you want to reconstruct. If in doubt, use REINDEX DATABASE FORCE to force reconstruction of all system indexes in the database. Then
quit the standalone backend and restart the postmaster.
Since this is likely the only situation when most people will ever use a standalone backend, some usage notes might be in order:
o Start the backend with a command like
postgres -D $PGDATA -O -P my_database
Provide the correct path to the database area with -D, or make sure that the environment variable PGDATA is set. Also specify the name
of the particular database you want to work in.
o You can issue any SQL command, not only REINDEX.
o Be aware that the standalone backend treats newline as the command entry terminator; there is no intelligence about semicolons, as there
is in psql. To continue a command across multiple lines, you must type backslash just before each newline except the last one. Also, you
won't have any of the conveniences of command-line editing (no command history, for example).
o To quit the backend, type EOF (Control+D, usually).
See the postgres(1) reference page for more information.
USAGE
Recreate the indexes on the table mytable:
REINDEX TABLE mytable;
Rebuild a single index:
REINDEX INDEX my_index;
Rebuild all system indexes (this will only work in a standalone backend):
REINDEX DATABASE my_database FORCE;
COMPATIBILITY
SQL92
There is no REINDEX in SQL92.
SQL - Language Statements 2002-11-22 REINDEX(7)