3300 MXE III MIVoice Business

[sadic]

How to format the hard drive without upgrading.

Any ideas..

[ralph]

If you don't want to upgrade you'd just re-install the same software level.
Why would you want to re-format?

Ralph

[sadic]

thanks for the reply ralph, i want to re-format the system due to an error on dbms. If I run the dbms check full the error info says
DBMS
INTERNAL
1 view errors
DB (DBTable)error: First key for table 0 not supported DBMS(DBSynch)warning:Database Read access denied to ... PID=($0006,$0609)dtrnkmon Access is blocked by... PID=($0007,$004C)dbrefa "Major alarm" shows

[ralph]

Before I reformatted, I'd try just restoring the database to see if that cleared the error.

Ralph

[sarond]

Also if you want to just clear programming you could try "DBMS FLAG OFF" maintenance command to wipe the system.

[sadic]

Thank you guys

[acejavelin]

How to format the hard drive without upgrading.

Any ideas..

The blunt answer here is yes... reinstall the same software load manually (FTP method), and there is a flag to re-partition the drive, this will cause a format action to occur and reinstall the same software load.

Typically though, if there is a database issue like you state, the first method of correcting the issue is to perform a backup and restore from the the administrative web portal. During the restoration process, any invalid or corrupt data is ignored and you can watch the output of the serial port or telnet 2002 session to see what is failing, note that the database isn't REALLY restored until the next reboot, so you have to monitor it through the entire process.

[lundah]

How to format the hard drive without upgrading.

Any ideas..

The blunt answer here is yes... reinstall the same software load manually (FTP method), and there is a flag to re-partition the drive, this will cause a format action to occur and reinstall the same software load.

Typically though, if there is a database issue like you state, the first method of correcting the issue is to perform a backup and restore from the the administrative web portal. During the restoration process, any invalid or corrupt data is ignored and you can watch the output of the serial port or telnet 2002 session to see what is failing, note that the database isn't REALLY restored until the next reboot, so you have to monitor it through the entire process.

In addition to monitoring the restore via the serial port or TCP 2002, the system writes the restore log to *.dr.logfile_1 which can then be viewed post-restore by going to Maintenance Commands and entering "type *.dr.logfile_1". From there you can copy/paste the report into Notepad or your preferred text editor.