We have the following situation:
Due to a lack of Library slots the log filled up to its maximum of 13 Gb, we were unable to extend the log files and restart the TSM server.
The 108Gb TSM database was dumped to tape (ltoclass). We then ran loadformat to prepare the log and database devices. We then ran loaddb. It has been running for 43 hours, so far we have loaded 471000 000 database entries and still loading...
Hardware specs are Intel P4 Xeon 2.4 Ghz, with 2.5 Gb RAM on Windows 2003.
Any formula as to how long the load could take?
Any advice as to recovering the server would be appreciated.
Stuart
Due to a lack of Library slots the log filled up to its maximum of 13 Gb, we were unable to extend the log files and restart the TSM server.
The 108Gb TSM database was dumped to tape (ltoclass). We then ran loadformat to prepare the log and database devices. We then ran loaddb. It has been running for 43 hours, so far we have loaded 471000 000 database entries and still loading...
Hardware specs are Intel P4 Xeon 2.4 Ghz, with 2.5 Gb RAM on Windows 2003.
Any formula as to how long the load could take?
Any advice as to recovering the server would be appreciated.
Stuart