| Oracle® Clinical Installation Guide Release 4.6 Part Number A83779-08 |
|
|
View PDF |
| Oracle® Clinical Installation Guide Release 4.6 Part Number A83779-08 |
|
|
View PDF |
This chapter describes the recommended approach to upgrading an Oracle Clinical Release 4.5.1, 4.5.2, or 4.5.3 installation to Release 4.6. If you are upgrading an Oracle Clinical Release 4.5 or earlier installation, see the Oracle Clinical Release 4.5 Installation Guide to upgrade to Release 4.5.1 before continuing.
Notes:
Back up your existing Oracle Clinical installation before you begin.
Oracle Clinical 4.6 does not support replication. Future releases will support replication. Oracle recommends that if you use replication, wait for the future release.
Most of the effort in upgrading from Release 4.5.1, 4.5.2, or 4.5.3 involves the database tier. However, you also have to install new Forms Servers, Reports Servers, and clients. Where the upgrades are the same as new installations, this guide refers you to the instructions for the new installations instead of repeating them here.
This chapter includes the following topics:
This section describes upgrading from Oracle Clinical Release 4.5.1, 4.5.2, or 4.5.3 database tier, which runs against Oracle Database 9i, to Release 4.6 database tier, which run against Oracle Database 11g. The upgrade process requires that you upgrade the technology stack in the order presented in this section.
Tasks for Database Tier Installation
The following list outlines the general sequence of the tasks you perform to upgrade the databases in your environment to Oracle Clinical 4.6. This section combines the instructions for the Database Server upgrade and the database upgrade because you have to implement them and their environments in this order:
This section covers tasks to prepare your environment for a new Oracle Database 11g home. There is a list of general tasks followed by more detailed tasks.
Review the topics in this section, which might impact your upgrade strategy.
If you chose not to partition your databases in earlier implementations, take this opportunity to reconsider.
Oracle Clinical partitioning requires the Partitioning Option to Oracle Database 11g. If you plan to implement Oracle Clinical partitioning, install this option just after you upgrade Oracle Database 11g.
Legacy Installation Dependencies
Oracle Clinical 4.6 is not dependent on previous installations. Once you have completed updating all users and migrated all databases to Oracle Clinical 4.6, you can archive earlier Oracle Clinical releases and delete them.
Before you install Oracle Database 11g perform these preliminary tasks:
Check My Oracle Support for up-to-the-minute changes to the upgrade process.
Review the bug fix descriptions of bugs fixed in Oracle Clinical 4.6. Check for this information on My Oracle Support.
Ensure that you have a recent backup of your system, including operating system files and databases.
Ensure that your operating system and environment meet the requirements described in Section 1.3, "Planning an Oracle Clinical Database Tier Installation."
Stop all Oracle Clinical activity on the database tier, including databases, listeners, PSUB jobs, or Reports Server jobs.
When you have completed these preliminary tasks, continue with the instructions in the following sections.
Your Oracle Clinical installation may not use any form of replication, just conventional replication, or both conventional and symmetric replication. Before upgrading Oracle Clinical databases, assess which types of replication you use and take the steps described in this section to stop all replication before continuing the upgrade.
Note:
Oracle Clinical 4.6 does not support replication. If you use replication, wait for an upcoming release that will support replication.The term replication includes these three areas:
Conventional Oracle Clinical replication activities. Oracle Clinical provides PSUB activities for replicating the Global Library, lab ranges, study design, study definition, and study data. These are collectively referred to as "conventional Oracle Clinical replication."
Automatic replication of study design via symmetric replication (as described in the Oracle Clinical Administrator's Guide). This area uses Oracle's symmetric, or advanced, replication to automatically propagate study design information among databases.
In addition, Thesaurus Management System or a particular application in your company might be performing conventional or symmetric replication with Oracle Clinical databases.
Tip:
You must upgrade all databases in your Oracle Clinical installation to Oracle Clinical 4.6 before setting up, or resuming, replication in any of them.When upgrading a database you must either ensure that all incremental replications are up-to-date or perform full definition replications for each study and Global Library after you complete the upgrade. New Mandatory columns do not have values in the journal tables the system uses for both incremental replication and auditing. It would violate the audit trail to back-populate the journal tables with values for the new Mandatory fields, which are left null. An incremental replication that draws upon journal records created prior to the upgrade fails with the Mandatory column is null error. Use caution when applying the percent symbol (%) wild card to specify which studies to bring across when doing FULL study replication. This wild card pulls all studies over that have the Available for Replication flag checked, from all owning locations. If your company has many studies at multiple locations, consider specifying studies uniquely.
To stop conventional replication activities in your installation:
Cease the initiation of any new conventional replication activities.
Ensure that no replication commands are issued, and no replication batch jobs are executed, until all database upgrades are complete.
Replicated Environments:
If you have a replicated environment, follow these extra instructions:Perform either an incremental or a full replication so that all sites are consistent.
Suspend replication.
Upgrade all databases in a replicated set according to the instructions in this section. Do not restart replication until you finish upgrading all databases in a replicated set.
If you follow the instructions above, you need only perform incremental replication after the upgrade. If you do not make all sites consistent before the upgrade, you must perform full replication after the upgrade.
Because symmetric replication operates independently of Oracle Clinical, you must take action to stop the database activities that are controlling the symmetric replication activities. Take the following steps in each database in the installation.
Log in as user REPSYS.
Check the replication queue and push all pending jobs.
select * from DEFTRAN;
To push these pending transactions:
dbms_defer_sys.execute(destination=>'other sites.WORLD', execute-as-user=>TRUE);
Disable the replication queues until the upgrade is complete.
List the jobs in the queue:
select * from USER_JOBS;
Locate all the job ID numbers for all push transactions (dbms_defer_sys.execute transactions)
Stop each of these jobs by running:
dbms_jobs.broken(job_id,TRUE);
Note:
This command halts all symmetric replication operations in and out of the affected database, including non-Oracle Clinical replication.Stop all modifications to the database.
As much as possible, avoid making changes to programs, projects, organization units, regions, planned studies, factors, strata, active substances, drugs, or treatment regimens.
Quiesce the databases by executing the following against the master database:
execute dbms_repcat.suspend_master_activity ('RXA_DES');
Drop the replication group from both databases:
execute dbms_repcat.drop_master_repgroup ('RXA_DES');
This step applies only if you are upgrading a database that has previously been at Oracle Clinical 4.0.
Starting with Oracle9i Database Release 2, a temporary tablespace is not allowed to be the default tablespace. The study access accounts in Oracle Clinical 4.0 were created with temporary tablespace as their default tablespace. If your database has been upgraded from Oracle Clinical 4.0 to Oracle Clinical 4.5.1, you should have run the alter_dx_tablespace.sql script as part of the upgrade process. This script changes the Data Extract Study Access Accounts default tablespace to the USERS tablespace.
If you are upgrading a database that has previously been at Oracle Clinical 4.0, check that you ran this script. If not, run the alter_dx_tablespace.sql script, located in the install directory at \oc\Misc.
Create a new Oracle home by following these operating system-specific tasks.
To install Oracle Database 11g in a new UNIX Oracle home, follow the instructions in these sections:
To create a new Oracle Database 11g Oracle home on Windows, follow the instructions in these sections:
Because the Installer checks for ORACLE_HOME directory, and if it has write access, you must change the access settings for this directory before installing the Oracle Clinical component. You must grant write access to the Oracle Database 11g ORACLE_HOME directory. See Section 2.2, "Granting Write Access to Oracle-Owned Directories" for instructions.
To upgrade the database from the old Oracle Home to the new Oracle Home, you can use either the export/import options or the Oracle Database Upgrade Assistant (DBUA).
For performing an in-place upgrade using the Oracle DBUA, see the following documents on My Oracle Support:
Complete Checklist for Upgrades to 11gR1 using DBUAArticle ID: 556477.1
Oracle Database Upgrade Guide 11g Release 1 (11.1)Chapter 3, "Upgrading to the New Release" Part Number: B28300-03
Install the Oracle Clinical Database Server component against the new Oracle Home, choosing a new OPA Home directory for this installation so that you do not overwrite your existing environment.
To install the Database Server component, you log in to the server, run the Installer from the appropriate download location, and select the OC Server product. Here are platform-specific instructions:
For UNIX Database Servers, run the Oracle Installer to install Oracle Clinical 4.6 and modify the default environment variable settings.
Perform the UNIX-specific installation instructions in Chapter 2, Section 2.6, "Installing the Oracle Clinical 4.6 Database Server."
Then perform the installation instructions in Chapter 2, Section 2.6, "Installing the Oracle Clinical 4.6 Database Server". When you finish, continue with the following task.
Installing Oracle Clinical 4.6 creates the OPA_HOME/bin/opa_settings file. This file contains global environment setting defaults that you can now, if necessary, modify for this computer. See Section 2.7.3, "Review the opa_settings File" for instructions.
Note:
The default settings for all databases or the specific settings for a particular database, such as NLS_LANG, must be correct in the opa_settings file.If you modified any Oracle Clinical files, you must reapply the changes to the Oracle Clinical 4.6 files. This section lists possible modified files.
Reapply Form, Menu, Report, or PLL Customizations
If you modified any of the following components, recompile them using Forms Builder 10g and redeploy the customized versions:
rxcuser.fmb
rxcuser.mmb
rxclbcli.pll
rxcdrptl.rdf
rxcdrptp.rdf
If you have customized any of the scripts in the following list in Oracle Clinical 4.5.1, 4.5.2, or 4.5.3, you may need to reapply your customizations.
rxcptdxvb.sql: No changes in Oracle Clinical 4.6. If you customized this file in Release 4.5.1, 4.5.2, or 4.5.3, you can copy the file from that release.
rdcpb_client.sql: Changed in Oracle Clinical 4.5.3. If you customized before Release 4.5.3, you must reapply your customizations.
rdcps_client.sql: Changed in Oracle Clinical 4.5.3. If you customized before Release 4.5.3, you must reapply your customizations.
ocl_client_pb.sql: No changes in Oracle Clinical 4.6. If you customized this file in Release 4.5.1, 4.5.2, or 4.5.3, you can copy the file from that release.
Preserve the Replication Setup Script
To preserve edits to the replication setup script rxasravw.sql, copy it to the Oracle Clinical 4.6 RXC_INSTALL directory.
Note that the rxasravw.sql script is not automatically executed when upgrading. You must manually run the script after the upgrade.
Note:
Oracle Clinical 4.6 does not support replication.To install Oracle Clinical 4.6 on Windows Database Servers:
Perform the installation instructions in Section 3.3, "Installing the Oracle Clinical 4.6 Database Server."
Grant write access to the ORACLE_HOME directory and its contents.
Continue with the tasks in Section 9.1.5, "Repair Data."
Ensure that you applied the following data diagnostic and repair patches (or their successors) on your Oracle Clinical data.
Follow the patch instructions to apply the patches to each Oracle Clinical 4.5.1 database in your entire Oracle Clinical installation.
Patch OC_4.5.1.58: Finds the data affected by bugs 5186346 and 5766849.
Patch OC_4.5.1.67: Includes repairs in discrepancy management, soft-deleting documents in a study with enabled CRF page-tracking, replication problems, and modifications to the DCF report.
Patch OC_4.5.1.68: Finds and fixes the data affected by bug 7515931.
Follow the patch instructions to apply the patches to each Oracle Clinical 4.5.3 database in your entire Oracle Clinical installation.
Patch OC_4.5.3.16 (or its successor). Run the find_inadv_approve.sql and the list_inadv_approve.sql scripts.
Patch OC_4.5.3.11 and Patch OC_4.5.3.12 (or their successors). Caution: skip this task if you already applied these patches.
Oracle Clinical 4.6 includes enhancements for tracking changes to audit data and verifications that were introduced in Oracle Clinical Patch OC_4.5.3.11 and Patch OC_4.5.3.12. Patch OC_4.5.3.11 repaired data and Patch OC_4.5.3.12 migrated existing data to work with the enhancements. Oracle Clinical 4.6 runs the repairs from Patch 4.5.3, however, you must manually migrate your data from that repair. For more information, see Appendix A, "Migrating Data for Approvals and Verifications Enhancements."
Oracle recommends that you create all tablespaces with the Autoextend On option on to avoid running out of storage space.
However, depending on your upgrade path, the upgrade process can be shortened, and the application's performance may be improved by modifying and manually running the ocl452indexchg.sql script. This operation can improve running queries from RDC.
Review the default values in the ocl452indexchg.sqlis script, which is located in the RXC_INSTALL folder. Adjust the values to fit your installation's data.
Note:
During the database upgrade operation, the Installer creates default tablespace sizes contained in these upgrade scripts. Modify the scripts before you run the Installer.In addition, review the following document on My Oracle Support for the latest information about tablespace sizes:
Configuring Oracle Clinical Remote Data Capture Onsite 4.6 for Performance and ScalabilityArticle ID: 873743.1
Tablespace Sizes When Upgrading from Oracle Clinical 4.5.1
If upgrading from Oracle Clinical 4.5.1, the indexes are recreated automatically. This process could take a long time, depending on the amount of data in the application. Consider modifying ocl452indexchg.sql in resizing (redefining) the storage clause for the indexes being created there.
Tablespace Sizes When Upgrading from Oracle Clinical 4.5.2 or 4.5.3
If upgrading from Oracle Clinical 4.5.2 or 4.5.3 — and the indexes were not created during the upgrade to 4.5.3 — again, consider modifying ocl452indexchg.sql in resizing (redefining) the storage clause for the indexes and executing this script standalone.
Running the ocl452indexchg.sql Script
You can manually run the ocl452indexchg.sql script by following these instructions. The ocl452indexchg.sql script is located in the RXC_INSTALL folder.
Running ocl452indexchg.sql on UNIX From the command line, enter:
opa_setup database 46 cd $RXC_INSTALL sqlplus /nolog @ocl452indexchg.sql
Running ocl452indexchg.sql on Windows From the command line, enter:
set p1=database set p2=46 opa_setup cd %RXC_INSTALL% sqlplus /nolog @ocl452indexchg.sql
You must stop the PSUB process pointing at each database you upgrade.
Navigate to the Services control panel.
Highlight the PSUB service.
Click Stop.
Log in to the operating system of the local computer in the RXCPROD account.
Set the environment variables for the database and code environment.
Enter the following command:
rxcpstop.sh rxc/password
After the upgrade completes, set the init.ora parameters according to the instructions in Section 4.2.8, "Set Initialization Parameters."
Review the Performance Tuning White Paper
In addition, review the following document on My Oracle Support for the latest information about setting the init.ora parameters:
Configuring Oracle Clinical Remote Data Capture Onsite 4.6 for Performance and ScalabilityArticle ID: 873743.1
Stop, and then start the database to activate the changed init.ora parameters.
This section describes running the Installer from the appropriate Oracle Clinical 4.6 Server for your Database Server platform to apply the product OC Database Upgrade to the database you are currently upgrading.
The study was hard deleted.
Jobs were submitted from the Special menu of data management screens.
PL/SQL jobs were submitted with or without using the PSUB screen.
Read this entire section before you start the Installer. It describes the information you should have available before you begin. This section contains the following sections, in the order listed:
Detailed preliminary steps for UNIX systems
Detailed preliminary steps for Windows systems
Platform-independent steps for using the Installer screens.
Follow these instructions to set the correct installation environment and start the Installer. Where the platforms have different instructions, there are separate sections.
The Installer acts in two phases. In the first phase, the Installer collects information about your system. During this phase, you can move back and forward through the screens, revising your entries. During the second phase, the Installer runs the scripts to set up the Oracle Clinical software according to the information you provided in the first phase.
The media is Disk V17174-01 from the Oracle Clinical 4.6 and Oracle Thesaurus Management System 4.6.1 Media Pack. The media is already extracted on the computer from the server code installation. To install an Oracle Clinical database on a UNIX Database Server:
Set the installation environment:
Log in to the server computer as the opapps user.
Change the primary group of the opapps account to the oinstall group by entering this command, where oinstall is the name for your Inventory Owner group. Enter:
newgrp oinstall
Set the X Window display output to your local computer's IP address, represented in the example by 123.45.67.89. Note the addition of ":0" to the end of the IP address:
setenv DISPLAY 123.45.67.89:0
Navigate to this location in the folder where you extracted the database server code:
server_code_platform\Disk1\install
Enter:
./runInstaller
The Universal Installer opens. Continue at Section 9.1.9.3, "Attend to the Upgrade Installer Screens."
To begin the installation.
Log in using an account with Windows system administrator privileges.
Insert Disk V17174-01 of the Oracle Clinical 4.6 and Oracle Thesaurus Management System 4.6.1 Media Pack.
Locate and execute file:
oc\middle_tier\install\setup.exe
The Installer opens to the Welcome screen.
Follow the instructions for each screen in the following section.
This section describes each of the successive Installer screens.
Click Next to continue the installation. Click Installed Products to see a list of installed Oracle products.
Select OC Database Upgrade 4.6.0.0.XX (where XX is the build number). ClickNext.
Select Installation Type OC Database Upgrade 4.6.0.0.XX (Note: XX is the build number.)
Select Upgrade and Configure (0 KB), and then click Next.
Specify Home Details Destination
Enter or select a name for the installation and the full path where you want to install the product.
Enter the path to the directory that you established during the installation of the Oracle Clinical 4.6 Database Server code.
Choose Database Connect string for database to be upgraded
Enter the Oracle SID of the database — for example, prod.
Choose Directory For new tablespaces
Specify the directory for these tablespaces:
BC4J_INTERNAL_TSPA: (Internal use only)
DX_TABLE_DATA: (Locally-managed tablespace for DX table data)
DX_INDEX_DATA: (Locally-managed tablespace for DX indexes)
Enter Database Configuration Parameters
Accept the default values for DB Hostname and DB Port Number.
In successive screens, the Installer prompts you to enter passwords for the following DBA or subsystem schemas:
| SYS | SYSTEM | RXC | RXA_DES |
| RXA_LR | OPA | RXC_REP | RXC_PD |
| RXC_DISC_REP | RXC_MAA | TMS | RXC_SERVLETST |
For a description of each password, see Section 4.3.4, "Attend to the Oracle Clinical Database Installation Screens."
Yes/No Ignore tablespace creation errors?
Tablespace creation can fail for various reasons. Here are two situations that can arise for Oracle Clinical:
There is not enough space. If so, you should accept the default and leave the response to this dialog to No.
The tablespace is already in existence, for instance, if you are reinstalling into an existing Oracle Clinical database. In this case, you should change the response to this dialog to Yes.
Select either the Yes or No.
This screen confirms your parameters.
This concludes the information-gathering portion of the installation process. When you are satisfied that the entries to the previous screens are satisfactory, click Install.
The Installer starts an SQL*Plus session in the background that updates the database. To monitor the progress review the log file from the upgrade install/oclupg_database.log
This screen displays whether the installation succeeded. Click Exit.
See the Oracle Clinical Administrator's Guide for information about enrolling users.
After running the installer, check the log files to confirm that the upgrade succeeded. Upgrading the Oracle Clinical database produces the following log files:
compile_all_invalid_database.log
html_blob_seeddata_database_timestamp.log
html_dialg_templ_database_timestamp.log
load_olsardcstatemachine_jar_database.log
oclconfig_database.log
oclupg_database.log
opaconnectcheck_system_database.log
upgrade_database_timestamp.log
xmlp_clob_seeddata_database_timestamp.log
xml_clob_seeddata_database_timestamp.log
The rest of this section describes finding errors in the log files (as logfile), and descriptions of known errors.
See the Oracle Clinical 4.6 Release Notes (Article ID 859753.1) for Known Installation Issues for a description of any error messages.
If the installation fails to reencrypt any password, it does not list them as errors. Instead, it lists them in the log files in a section titled, "Passwords for the following schema accounts were not converted." Check if this section exists and if it lists any accounts. If there are any accounts, you must reencrypt them by using set_pwd command.
To simplify reviewing upgrade results, run these commands for each of the four database upgrade log files:
Oracle Enterprise Linux. From the command line, enter:
opa_setup database 45cd $RXC_INSTALL
/bin/grep -n -E '^ORA-|^PLS-|^SP2-' logfile | more
Oracle Solaris. From the command line, enter:
opa_setup database 45
cd $RXC_INSTALL
/usr/xpg4/bin/grep -E '^ORA-|^PLS-|^SP2-' logfile | more
HP-UX Itanium. From the command line, enter:
opa_setup database 45
cd $RXC_INSTALL
/usr/bin/grep -n -E '^ORA-|^PLS-|^SP2-' logfile | more
Windows. From the command line, enter:
set p1=database
set p2=45
opa_setup
cd %RXC_INSTALL%find /i "error" logfile | find /v "No error"
This section describes known error messages and possible actions you can take to resolve them.
See Chapter 6 of the Oracle Clinical Administrator's Guide for instructions on implementing partitioning for the responses table in Oracle Clinical 4.6.
See "Upgrading Indexes" in the Oracle Clinical Administrator's Guide for instructions on upgrading your indexes.
The Oracle Clinical 4.6 database upgrade process runs the compile_all_invalid.sql script. To reduce the time required to run, this script does not recompile objects in RXC_PD beginning with RXCPD, or schemas that have a dollar symbol ($) in the name. Instead, you use the compile_schema_invalid script to selectively recompile invalid objects that match a pattern.
If there are any remaining invalid objects, run compile_schema_invalid.sql as sys. The compile_schema_invalid.sql is located in the $RXC_INSTALL directory. This section describes how to use this script.
Note:
If you have any PL/SQL code referenced from your generated procedures, ensure that these objects are valid before running this script. For example, if you created a schema namedX, which contains all of the PL/SQL code referenced from your generated procedures, you would first run:
compile_schema_invalid.sql X
Before running:
compile_schema_invalid.sql rxc_pd
To compile any invalid objects in OPS$ accounts, enter this command:
start compile_schema_invalid OPS$%
Recompiling Study-level Data Extract View Accounts
To compile any invalid objects for the Data Extract views owned by a study, enter this command:
start compile_schema_invalid studyname$%
To compile any invalid objects in accounts that have the $ symbol in the account name, enter this command:
start compile_schema_invalid %$%
Recompiling all Invalid Objects
To compile all invalid objects in all schemas, enter this command:
start compile_schema_invalid %
To improve performance, some of Oracle Clinical's packages are pin-able packages; Pinning allocates a stable memory location so that a package cannot be subjected to being swapped out of memory. Oracle Clinical provides the rxcdbinit.sql script to pin the database packages.
Note:
You must reexecute this script each time you restart the database. Consider creating an entry in the database startup script that runsrxcdbinit.sql.Oracle Clinical provides scripts that analyze the storage characteristics of tables and indexes of computed statistics. Run these scripts now, and as you accumulate data in this database. See the Oracle Clinical Administrator's Guide, Appendix E, "Collecting Statistics for Optimization."
Run anarxctab.sql.
Run anadestab.sql as rxa_des.
Run analrtab.sql as rxa_lr.
Run anaopatab.sql as opa.
If you set up the event parameter in the init.ora file to trace unique key constraints before upgrading, you should set the event parameter back to its required value. See Section 4.2.8, "Set Initialization Parameters" for details.
The instructions for starting the PSUB process are platform-specific.
Log in as rxcprod, or as any other account that has OPA_HOME/bin in its path.
Enter:
start_psub database 45
where database is the connect string for the database instance to which the PSUB process connects.
If you are not logged on as rxcprod, you are prompted to provide the password for the rxcprod account. If the PSUB process is already running, the system displays an error message.
Changing the Startup of the PSUB Service on Windows
Navigate to the Control Panel, Services window, and select the PSUB service.
In the Services dialog box, select the PSUB Service and enter values for the Startup parameters (one string):
database-connect-string code-environment [verbose | noverbose] value-of-RXC_ROOT
For example:
prod 46 verbose c:\\opapps\\oc\\46
Click Start.
Troubleshooting PSUB on a Windows Database
If you have difficulty starting PSUB on a Windows database after upgrading to or installing Oracle Clinical 4.6:
Open the sqlnet.ora file.
Locate the following line:
sqlnet.authentication_service=(NTS)
Insert the pound symbol (#) at the beginning of the line to comment the line.
Attempt to start PSUB.
If PSUB fails to start:
Open the sqlnet.ora file.
Remove the pound symbol (#) from the following line:
#sqlnet.authentication_service=(NTS)
Open the init.ora file. Ensure that the following lines are not commented out:
remote_os_authen=true os_authent_prefix="OPS$"
Shut down any databases on the 2000 machine.
Bring the databases back up.
Open the sqlnet.ora file. Insert the pound symbol to comment out the following line:
sqlnet.authentication_service=(NTS)
You should change the default passwords of all schemas and roles and, if appropriate, use the set_pwd utility located at $RXC_BIN/set_pwd to encrypt the passwords in the database. See Appendix C of the Oracle Clinical Administrator's Guide for a list of users. (For instructions about how to change encrypted passwords and schema passwords, see the Oracle Clinical Administrator's Guide.)
The technology stack is different for Oracle Clinical 4.6 Forms Servers, so you must create new Forms Servers.
Note:
If you changed the default values of the DE_GRIDWIDTH and DE_GRIDHEIGHT parameters, record their values before you upgrade your Forms Servers. You must reset them to the same values after you upgrade in order for your Data Entry windows to appear correctly.The general tasks for each installation are as follows:
Install a new Oracle Clinical 4.6 Forms Server. See Chapter 5.
Recompile customized forms. (See Section 9.2.1, "Upgrade Forms Server Customizations.")
If they are relevant to your installation, perform the procedures in this section after you complete installing at least one of each of the essential Oracle Clinical 4.6 components. See Interfacing from Oracle Clinical for more information about these customizations.
Oracle Clinical no longer includes the rxclbgen.pll file.
The rxcuser.pll file is located on the Forms Server in the OPA_HOME\oc\admin directory. If you customized rxcuser, upgrade the following files located in the Forms Server's Admin directory:
Recompile rxcuser.fmb with Forms Builder 10g.
Recompile rxcuser.mmb with Forms Builder 10g.
Detach rxclbgen.pll from rxcuser.fmb, and attach rxcuser.pll.
Replace your recompiled rxcuser.fmb and rxcuser.mmb files on each Forms Server in your network.
If you have customized rxclbcli.pll, recompile it with Forms Builder 10g. See Chapter 3 of Interfacing from Oracle Clinical for more information.
Replace your recompiled rxclbcli.pll file on each Forms Server in your network.
The technology stack is different for Oracle Clinical 4.6 Reports Servers, so you must create new Reports Servers. For instructions on how to install a new Oracle Clinical 4.6 Reports Server, see Chapter 6. The following two sections are other Reports Server upgrade tasks.
Oracle Clinical's Data Clarification Form (DCF) report system is a utility for generating paper forms from an Oracle report. The report includes a placeholder graphic named rxcdcf.bmp.
You can replace rxcdcf.bmp with your own graphic, or redraw it with a graphics drawing application.
rxcdcf.bmp is located on Oracle Clinical Reports Server installations in the OPA_HOME\oc directory (for example, c:\ opapps\oc\). You can edit it locally and then copy it to your server.
If you customized DCF Reports files rxcdrptl.rdf and rxcdrptp.rdf, recompile them with Oracle 10g DS Reports Developer Release 2. The source files are located on the Forms Server in the OPA_HOME\oc\admin directory.
Configure your application tier browsers and your users' browsers according to the instructions in Chapter 7, "Setting Up Clients."
|
 Copyright © 1996, 2010, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|