Run the Script for RFID 27629203

If you use Oracle DMW 2.5 with Oracle TMS and your study was created in a release prior to Oracle DMW 2.4.8.1, you must run a script to update the p-package of TMS-enabled tables to resolve bug number 27629203. Before you run the script:

• Plan a maintenance window and run the script for a select group of TMS-enabled studies, rather than all studies
• Check in work areas and data models for studies impacted by this script
• Plan to run the script on a computer with an Oracle client that can connect to the DMW database server using SQLPlus

Note:

If you previously installed Oracle DMW 2.4.8.1 patch or later before upgrading to Oracle DMW 2.5, you do not need to run this script. Skip this procedure.

1. Log in to SQLPlus (not SQLDeveloper) as the APPS database user.
2. To invoke the script, enter:

   <directory where the script is located>\sql>sqlplus <APPS database user name>/<APPS database user pwd>@<database name>

3. Enter the following:

   DEFINE Username = <username1>

   For <username1>, specify a valid DMW user who has permissions to install work areas and data models in all lifecycles.
4. To execute the script, enter:

   SQL> @dmeupdtmsppkg.sql

5. Specify the studies that you want to execute the script against, using one of the following options.
   • To run the script for a select group of TMS-enabled studies, enter the study names in a comma-separated list:

     DEFINE Study_Names = <Study_Name1>, <Study_Name2>

   • To run the script for all studies:

     DEFINE Study_Names = ALL

   • To run the script for all but a select group of studies, enter the study names to exclude in a comma-separated list:

     DEFINE Exclude_Study = <Study_Name1>, <Study_Name2>

   Note:

   Oracle recommends that you run the script for specific studies.
6. Specify the lifecycles to run the script against, using one of the following options.
   • To run the script for a single lifecycle:

     DEFINE Lifecycle = $LIFECYCLE$<lifecycle name>

   • To run the script for all lifecycles:

     
     
         DEFINE Lifecycle = $LIFECYCLE$DEV, $LIFECYCLE$QC, $LIFECYCLE$PROD
     

7. Optionally, for more information about the script’s success or failure, see the log file DMEUpdTMSPpkg_datetime.csv, and the Install log. If the script completed successfully, it commits the transaction and closes.

   Note:

   • If you see the error message string beginning <stringtext> is too long. maximum size is 240 characters, remove some of the parameters and execute the command again. For example, if you are defining a list of study names to run the script against, run the script against a small group, and then re-run it for the remaining studies.
   • If the script’s status in the DMEUpdTMSPpkg_datetime.csv log file is Failure, the work area installation failed, and the data model is not installed.
   • If the script’s status in the DMEUpdTMSPpkg_datetime.csv log file is Partial, the work area installation was successful, but the data model installation failed. This could occur if:
     • The data model is checked out during the time when you ran the script. Check in the data model and try again.
     • Runtime or validation errors occurred. For more information on those errors, review the Install log.