01-16-2008
Could be a corrupted file?
Hello!
Do you know the meaning of...
"crw-rw---- 1 informix informix 64 0x020001 Jan 21 2004 rifxroot"
I don't know what the first "c" means. Furthermor, if I try to copy this file (rifxroot) it appears a message:
"cp: cannot open rifxroot: No such device or address"
I don't know why? Could be a corrupted file? Can you help me?
Thx in advance!
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi all,
I've got a corrupted tar file with some filename being like ?a=n is it possible to get them repaired? (1 Reply)
Discussion started by: klintsovi
1 Replies
2. Shell Programming and Scripting
Hello,
Newbie question:
How can I detect a corrupted file from a script (ksh)?
Thank you,
Martin (6 Replies)
Discussion started by: starless
6 Replies
3. HP-UX
Good Day
Our HP box was hacked and the passwd file has been altered,there are only 2 user accounts active,and these dont have any administrative rights.I need to edit the passwd file to correct the su and root entries.
Does any body have any suggestions as to how i can do this with out the root... (10 Replies)
Discussion started by: cantona7
10 Replies
4. UNIX for Dummies Questions & Answers
Hi,
I am new to UNIX, and have recently installed Suse 9.3. I have been experimenting with all of the commands and have somehow managed to modify the default shell of the root user to an invalid file. Consequently I cannot su to the root user as I receive the 'no such file or directory' error... (2 Replies)
Discussion started by: Tony Montana
2 Replies
5. UNIX for Dummies Questions & Answers
Preparing for a move to a new server, I needed to offload about somewhat over a gigabyte of newsfeeds that my website collects, and that I had been saving on the server. I tarred them and zipped them into about a dozen smaller files of about 150Mb each. All seemed well. I downloaded them onto my... (3 Replies)
Discussion started by: JohnTinker
3 Replies
6. UNIX for Advanced & Expert Users
Hello. I`m writing a bash script who archive log files and send them to backup server. I need some kind of checking mechanism for *.tar.gz files.
I found something like: gunzip -t file.tar.gz //Not output from it.
And for tar: tar tf file.tar.gz //Only lists archive
1.) I need make a... (3 Replies)
Discussion started by: jabalv
3 Replies
7. Solaris
Hi All
I work on solaris 8, 9 and 10 platforms and have encountered an error which is my wtmpx files appear to be corrupted as all entries contain the date 1970 (the birth of unix).
Now this is obviously not the case, so my query is:
1 - Can the existing wtmpx files be manipulated to... (6 Replies)
Discussion started by: drestarr96
6 Replies
8. Linux
hi,
yesterday I made something wrong and deleted daemon.log file. Then created a new file with the same name under the same path but now, it seems that file constructed has been corrupted .
In earlier times, it was including regex name. Now there is no regex name.
This is the current... (0 Replies)
Discussion started by: baris35
0 Replies
9. Red Hat
Hi,
Unexpectedly i entered wrong entries in .bash_profile for my user which has administrative permissions. So, i am getting errors for every command. I dont have backup file also, so any body can help me how to recover it.
Regards,
Mastan (7 Replies)
Discussion started by: mastansaheb
7 Replies
10. UNIX for Dummies Questions & Answers
Hi Folks,
While transferring file from FTP software like Filezilla the files gets corrupted.
Is there any way I can check if the recently transferred file is in ASCII and not corrupted. I have tried using file -i filename command which does tell if the file character set is ASCII or binary... (6 Replies)
Discussion started by: Khan28
6 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)