Hi there --

We have an archive server where the administrator, via a web interface, can import text files into a mysql database. The files are typically local to the machine. The operating system of the server is CentOS 5.4, and that of the mysql database is 5.0.77.

The database was originally on another server which was replaced by the one that is currently in use. The migration of the database from the older server involved creating a dump file, copying the file to the new machine, and importing it into the database. The version of the mysql database on the previous server was 5.0.45.

The problem that has started to occur is the following: When the administrator goes through the motions of importing a text file to the database, the text does not get imported even though there are no error messages appearing on-screen or in the mysqld.log file. The administrator can see what is already in the database, but he cannot add to it.

The web interface to the database utilizes perl modules and cgi files. I ran the cgi files from the command line to see if there were any error messages. There were none. The perl modules that were on the previous server were copied to the new server with the permissions kept intact. I also verified the user and database permissions on the new server match those on the older server.

I am at a loss as to why this is occurring, and I would appreciate any help I can get on this. I have enclosed the files that are involved with the importation of the text file into the database as a single text file attachment. The files are all cgi files with the exception of the last file being the perl module. The names of the files in the order of their appearance within the text file are the following:

If there is need of further information, please let me know. Thanks in advance.

Attached Files

combined files.txt (41.8 KB, 12 views)

Can you import the database dumps using phpmyadmin ? Or are the formats wrong ?

Main reason being to eliminate the new database's structure or state from the problem.

Hi there --

Thanks for your reply. I haven't had a chance to install phpmyadmin, but I did try the mysqlimport command. Unfortunately I am getting a syntax error when I run the command.

The command syntax that I am using is the following:

Where archivedicom is the name of the database, and full pathname to text file in question immediately follows. I also tried this command using just the filename of the text file instead of including the entire path to the file.

Whenever the command is run, the following error message appears:

I checked the mysql homepage, and it appears my syntax is correct. What am I missing? thanks.

After looking at those cgi scripts I see nothing that imports data from a db dump into a dbase using a standard import format. So the question is, how were these dump files created ? Were they dumps of tables or the entire dbase ?

Also, the syntax for mysqlimport requires the option --local and mysqlimport expects there to be a table named RODICOM_04may10-1. Does such a table exist ? You do not need a semi colon if this command is run from the shell, but you do need to specify the user and password for the database you are importing to.

If it was an entire dbase dump then use mysql -u user -p<password> dbasename < dbase-dumpfile to import it.

Hi there --

I tried running the mysqlimport utility again using the following command syntax:

I made sure to change the name of the file from RODICOM_04may10-1.txt to backupdicom.txt. The latter name reflects the name of the table within the archivedicom database. The command was run with just the filename as well as the full pathname: /home/ahk/backupdicom.txt.

I logged into the database as root and another user that has full access to the database. The command was run while either connected to the particular database, archivedicom, or when just logged into the database. The mysqlimport utility would not run unless I put the semi-colon at the end of the line.

The command failed in all instances with the 1064 error appearing on-screen.

Regarding the cgi scripts: They don't import data from a dump file into the database. Rather, they import data from a text file, and add it to the database. Listed below is an excerpt from one of the text files:

Sorry about the confusion.

You shouldn't need to be logged into to the database to run mysqlimport. mysqlimport is a shell command not a mysql shell command. That's why you specify user and password on the command line.

Without knowledge of the contents of the dump files, the purpose of the dbase or the original dump command, we have no way of knowing what type of dump was done.
Groping in the dark so to speak.

What happened to the person who originally set this up ? They are in a much better position to sort this out than I am.

Hi there --

Thanks for your reply. The author of the database is currently unavailable, but hopefully will be back in a week.

As far as the contents of the dump file is concerned, I can provide the file in question, or is/are there specific parts in it from which you need further information?

I would wait for the original author if I were you. If they were never coming back then it would be different but a week is not a long time to wait.

Fair enough...although this issue is going to be an 'itch' that is going to drive me crazy until it is resolved.