- Installation Guide
- Upgrading to Oracle LSH Release 3.4
- Migrate Secure File
- Post Secure File Migration Task for CDR_OUTPUT_CLOBS
Post Secure File Migration Task for CDR_OUTPUT_CLOBS
To perform the next set of tasks, wait for at least 12 hours after the
secure file migration completes. A complete application downtime is required.
- Stop all application tier services and job queue.
Note:
DO NOT stop the database.- Stop the listener and database services.
- Disable all the enabled DBMS SCHEDULER JOBS.
- Make sure that no scheduler job is in the RUNNING state.
- Disable the Logon Trigger.
- Make sure that no application-related sessions are there in gv$session.
- If there is any cronjob related to Oracle LSH or Oracle DMW, suspend them. Disable any custom scheduler or DBMS jobs related to Oracle LSH or Oracle DMW.
- Note the count of the invalid objects of APPS, APPLSYS, and CDR schema by
executing the following command:
select owner, status, count(1) from dba_objects where status <> 'VALID' and owner in ('APPS','APPLSYS','CDR') AND object_name <> 'CDR_SECUREFILE_MIGRATION' AND object_name NOT LIKE 'CDR%SECFILE%' AND object_name NOT LIKE 'CDR%SFM%' group by owner, status;
Or, create a backup table with the list of all INVALID OBJECTS by executing the following command:CREATE TABLE <TABLE_NAME> AS SELECT * FROM DBA_OBJECTS WHERE STATUS <>'VALID';
- Once all the application tier services are stopped, execute the cutover script
by performing the following steps:
- Log in to the application tier.
- Source the environment file.
- Navigate to the
$CDR_TOP/patch/115/sql
directory. - Log in to SQL*Plus as the APPS user.
- Execute the script
cdrsecfileclobcutoff.sql
.A prompt to press enter to start the process appears. - Press Enter.A prompt to enter the logfile pathname appears.
- Press Enter to select the default logfile pathname or enter a name of your choice.
- After the script execution is complete, check for any errors. In case of an error, contact Life Sciences Support.
It will take some time for the script to execute. - After the script
cdrsecfileclobcutoff.sql
executes, make sure no DBMS SCHEDULER JOBS are running related to secure file migration. - Make sure the new CDR_OUTPUT_CLOBS table's LOB column FILE_CLOB is of type
SECUREFILE.To do so, execute the following SQL command. The output of the SECUREFILE column should be YES corresponding to the CDR_OUTPUT_CLOBS table.
select OWNER, TABLE_NAME, COLUMN_NAME, SEGMENT_NAME, TABLESPACE_NAME, SECUREFILE from dba_lobs where table_name like 'CDR_OUTPUT_CLOBS%' and column_name ='FILE_CLOB' and OWNER='CDR';
- If there are new INVALID objects in the APPS, APPLSYS, or CDR schema, compile
those invalid objects.
select owner, status, count(1) from dba_objects where status <> 'VALID' and owner in ('APPS','APPLSYS','CDR') AND object_name <> 'CDR_SECUREFILE_MIGRATION' AND object_name NOT LIKE 'CDR%SECFILE%' AND object_name NOT LIKE 'CDR%SFM%' group by owner, status;
- Start the UTLRP and wait for its completion.
- Enable the Logon Trigger.
- Start the listener/database services.
- Enable all the DBMS SCHEDULER JOBS which were disabled at step 1.b.
- After all validations are successful, start all the application tier services and job queue.
Parent topic: Migrate Secure File