What else is needed when sending a database dump to support for restoring it? (4311870)

Description:

There are times when a Mart database or another database dump needs to be sent to support for diagnosis purposes.  Is any thing else also needed at the receiving end for restoring it?

Solution:

Yes, there are a few things that are needed for restoring it. Please use the following guidelines when sending a database dump to support.  It will be much quicker to restore the database if we have all this information available.

For Oracle Database:

1. Oracle database version.
2. Execute Select * from V$NLS_PARAMETERS; in Oracle query tool and send us that result. It is very important for us to know the values for the parameters NLS_CHARACTERSET and NLS_NCHAR_CHARACTERSET so we can create our database with the same character set.  Executing the above statement will also give us other (possibly important) environmental information so we can match our test instance to the one we are reveiving and allow the import to succeed. 
3. Send us the Mart Schema owner export, not the full export. This will reduce the size of the file and reduce the transmission time.
4. Use the Oracle EXPORT utility when exporting the dbms.  It will ensure that the export file can be restored on a Windows platform.  The TAR command is only good to restore on UNIX OS.
5. Mart Schema Owner name.
6. At least one user name with 'Mart Administrator' Privilege.
7. Names of the Data and Index Tablespaces.
8. Total and used size of the Data Tablespace.
9. Total and used size of the Index Tablespace.
10. Compress the file if it is large and include compression utility name.
11. Preferred backup method: Transfer compressed file to choice of backup hardware if electronic transfer is not available.
12. Preferred Hardware for backup file device: 4mm DAT, DLT or standard CD-ROM.

For SQL Server Database:

1. Database sort order and character set used (run sp_helpsort in the query tool to get this information).
2. Name of database.
3. Data device size.
4. Log device size.
5. Or total database size.
6. At least one user name with 'Mart Administrator' privilege.
7. Compress the file(s) if it is large and include compression utility name.

 For Sybase Database:

1. Database Version.
2. Database sort order and character set used (run sp_helpsort in isql to get this information.)
3. Name of database.
4. Data device size.
5. Log device size.
6. Or total database size.
7. At least one user name with 'ModelMart Administrator' privilege.
8. Compress the file(s) if it is large and include compression utility name.
9. If sending a bcp files then use character mode bcp option with unique set of column and row terminators. Also include the 'bcp out' script file so we can use it to do 'bcp in'.
10. Preferred backup method: Create bcp files set and transfer it to choice of backup hardware if electronic transfer is not available.
11. Preferred Hardware for backup file device: 4mm DAT, DLT or standard CD-ROM.