Hello!
Does'nt than seem to be a problem with the script, I smell it. It could be a physical resource problem or the scripts are getting killed. So just trying to help you in identifying where "could be" the problem area, you can do the following, unless GT helps you or someone else:
1- Use "Top" command after you login via SSH or telnet (You need to have your own rights for that). Then press M for the listing with memory. Change the refresh to everyone sec by pressing s and then 1. See if the RAM and MEM is OK or free enough.
Here what happens is that the entire table is loadad into the memory, first in the RAM. Thereafter it is loadad into the SWAP partition, assuming that you use UNIX, I explain this. So keep an eye on the Swap, if there is a bottleneck developed.
2- Try to find out where exactly the scripts stops and figure out its behaviour by printing the lines as displays, like the following:
Exactly after the code in the line I have described above, exactly as below,
#############################
import_print "\n--------------------------------------\n";
import_print "\n Line 277 $Links_counter = Links_counter\n";
import_print "\n Line 278 $Category_counter = Category_counter\n";
import_print "\n Line 279 $new_id = new_id \n";
import_print "\n Line 280 $old_id = old_id\n";
##################################
3 - You will see that the script will start displaying all the inserts on the monitor.
4- You can chose the data-intigrity option as this will not duplicate the data.
Also you need to keep mild warnings and errors turned on.
Assuming that your NEW database is "EMPTY", which is the fundamental presumtion of the designer. Mind you, if you have the categories ALREADY inside the new database, things will work different and you need to tell us here, before you begin.
Editing this note, I saw what paul writes. Yes, it could be also true. It may just be importing and importing. This you can also view from the top command. You can also use Explorer 6.x and it will not get over until the cgi is working, which is a sign that it is still working.
Does'nt than seem to be a problem with the script, I smell it. It could be a physical resource problem or the scripts are getting killed. So just trying to help you in identifying where "could be" the problem area, you can do the following, unless GT helps you or someone else:
1- Use "Top" command after you login via SSH or telnet (You need to have your own rights for that). Then press M for the listing with memory. Change the refresh to everyone sec by pressing s and then 1. See if the RAM and MEM is OK or free enough.
Here what happens is that the entire table is loadad into the memory, first in the RAM. Thereafter it is loadad into the SWAP partition, assuming that you use UNIX, I explain this. So keep an eye on the Swap, if there is a bottleneck developed.
2- Try to find out where exactly the scripts stops and figure out its behaviour by printing the lines as displays, like the following:
Exactly after the code in the line I have described above, exactly as below,
#############################
import_print "\n--------------------------------------\n";
import_print "\n Line 277 $Links_counter = Links_counter\n";
import_print "\n Line 278 $Category_counter = Category_counter\n";
import_print "\n Line 279 $new_id = new_id \n";
import_print "\n Line 280 $old_id = old_id\n";
##################################
3 - You will see that the script will start displaying all the inserts on the monitor.
4- You can chose the data-intigrity option as this will not duplicate the data.
Also you need to keep mild warnings and errors turned on.
Assuming that your NEW database is "EMPTY", which is the fundamental presumtion of the designer. Mind you, if you have the categories ALREADY inside the new database, things will work different and you need to tell us here, before you begin.
Editing this note, I saw what paul writes. Yes, it could be also true. It may just be importing and importing. This you can also view from the top command. You can also use Explorer 6.x and it will not get over until the cgi is working, which is a sign that it is still working.
