DB Imported by External Source

The database can be put in place by an external source and the ImportDB page can be made unavailable to the users, see section Menu. 

If this method is used then it is the customer responsibility to ensure that the replacement of the schema/data is completed successfully and completely and nothing is left out.

If this is the case the following steps need to be followed

• Shutdown ServiceOptimizer and ServiceManager in the SWAT environment.
  
  
• ‘Drop and recreate’ the ServiceScheduling schema.  
       This may involve either complete dropping the user (See 'Drop ServiceOptimizer database user' below) and then recreating or by simple replacing the objects or data (by using such tools as datapump – refer 'Using a method where the user is not dropped' below).
  
  
• Using the ‘drop/create’ import mechanism:
       
       Ensure the ImportType option in the properties file is set to ‘import’ (see section Database)
  
       Drop ServiceOptimizer database user (not production user, the SWAT copy). 

                    Note: If there are open connections to the database then these should be dropped first.

               Recreate the ServiceOptimizer database user ensuring that the user has all required permission as stated in the ServiceOptimizer installation guide.

               Import the production ServiceOptimizer database into the SWAT environment.

              Jump to Run installation

• Using a method where the user is not dropped

               Ensure the ImportType option in the properties file is set to ‘datapump’ (see section Database)

               Replace ServiceScheduling objects/data using desired

• Run <installation directory>\webapps\ServiceSWAT\database\SWAT_SP_Configure_DB.pl