If the service pack installer contains a database update, you can run the scripts manually. After you update the database, you should then run the installer to update the web server and the library.

If you are running the scripts on an Oracle Database server, it should be run by the schema owner account created at the installation of the Developer. If you are running the script on a Microsoft SQL Server, it should be run by an SQL administrator with either sysadmin or a combination of securityadmin and dbcreator privileges. The database objects creation does not necessarily require these privileges and could be performed by the user with db_owner privileges of the database. This would require modifications to the SQL scripts.

The installer files for the Service Pack are compiled into a self-extracting executable file. To run the scripts manually, you must extract the installer files.

To extract the installer files:

1. Create an empty folder for the files.
    
   Tip: It is easier if the folder is in the same location as the self-extracting executable.
    
2. From the Windows Start menu, open a Command Prompt window.
    
3. To extract the files into the newly created directory, enter the following at the command prompt: /extract_all:<extraction location>. Be sure to include the path to the folder in the command.
    
   Example: C:\ESPInstaller\UPK_11.1.0.2.exe/extract_all:C:\ESPInstaller\ExtractedFiles.

To update the Knowledge Center database manually on an Oracle server:

1. From the Windows Start menu, open a Command Prompt window.
    
2. Update the schema using the AlterSchemaObjects.sql script. The script contains variables that are replaced with the text supplied for the values.
    
   Warning! The values must be in this order for the script to be run successfully.
    
   Standard sqlplus syntax:
   sqlplus -s <SCHEMA_OWNER>/<SCHEMA_OWNER_PASSWORD>@<SERVER_INSTANCE> @"<SCRIPT_LOCATION>\<SCRIPT_NAME>" variable_value1 variable_value2 ... variable_valueN
    
   Note: The -s parameter runs SQL*Plus without SQL*Plus messaging.
    
   Run the following:
   sqlplus -s <SCHEMA_OWNER>/<SCHEMA_OWNER_PASSWORD>@<SERVER_INSTANCE> @"AlterSchemaObjects.sql"  <SCHEMA_OWNER>
    
   The variables that need to be replaced are:
   <SCHEMA_OWNER> - user created that is the schema owner
   <SCHEMA_OWNER_PASSWORD> - password for the schema owner
   <SERVER_INSTANCE> - name of the Oracle server instance where the schema is to be updated
    
   Example with default install parameters:
   sqlplus -s KUser/password@xe @"E:\ESPInstaller\patchfiles\Content\Database\KnowledgeCenter\ORACLE\AlterSchemaObjects.sql" KUser
    
3. Confirm the parameters and run the script.
    
4. Enter exit and press ENTER to return to the command prompt.
    
5. Enter exit and press ENTER to exit the Command Prompt window.

To update the Developer database manually on a Microsoft SQL Server:

1. From the Windows Start menu, open a Command Prompt window.
    
2. Update the database using the AlterDBObjects.sql script. The script contains variables that are replaced with the text supplied for the values.
    
   Warning! The values must be in this order for the script to be run successfully.
    
   Standard sqlcmd syntax:
   sqlcmd -E -S <SERVERNAME> -i <SCRIPTFILE> –v VARIABLE1="<VALUE1>" -v VARIABLE2="<VALUE2>"
    
   Note: The -E parameter means use an entrusted connection to the SQL Server.  To use a login and password, use -U <LOGINID> and -P <PASSWORD> parameters.
    
   Run the following:
   sqlcmd -E -S <SERVER_NAME> -i AlterDBObjects.sql -v DBOwner="<DATABASE_OWNER>" -v DBName="<DATABASE_NAME>"
    
   The variables that need to be replaced are:
   <SERVER_NAME> - the server instance to connect to
   <DATABASE_OWNER> - the primary owner of the database when the database was created
   <DATABASE_NAME> - the name of the database to be updated
      
   Example with default install parameters:
   sqlcmd -E -S Server -i "E:\ESPInstaller\patchfiles\Content\Database\KnowledgeCenter\MSSQL\AlterDBObjects.sql" -v DBOwner="KUser" -v DBName="KMaster"
    
3. Confirm the parameters and run the script.
    
4. Enter exit and press ENTER to exit the Command Prompt window.

Table of Contents  Back