My Oracle Support Banner

When Using Oracle TMS To Import A DSI The Job Returns Failure ORA-06512 and ORA-29283: invalid file operation (Doc ID 790739.1)

Last updated on SEPTEMBER 05, 2017

Applies to:

Oracle Thesaurus Management System - Version 4.6.0 and later
Information in this document applies to any platform.

Symptoms

 

TMS
TMS_DSI_IMPORT.lProcessDir
ORA-29283: invalid file operation
ORA-06512: at "SYS.UTL_FILE", line 449
ORA-29283: invalid file operation

 

 

User has set-up and configured per the TMS 4.6 Install Guide below:

Before you can export or import data you must initialize your site as either a sponsor
or source site. To run the job:

1. Select Definition, then Jobs, then Initialize Disconnected System Integrations.

The Initialize Disconnected System Integrations job pop-up window appears.

2. For the job-specific parameter DSI Instance Type, select either Source or Sponsor.

3. If necessary, enter the name of your report server;

4. Submit the job.

At the sponsor site only, register the database used by each source site for DSI by
running the job:

From the Definition menu, select Jobs, then choose Register Remote DSI Databases.
You must register remote databases one at a time.

The job takes the following parameters:
■ Instance. Enter the source site database name.
■ External System. From the list, choose the external source data system (such as Oracle Clinical)
whose data will be sent to the remote system via DSI.

Note:

If you used the DSI feature before installing TMS Release 4.6,
you must now declare your TMS instance to be either a sponsor or a
source site by running the DSI initialization job. If you need to act as a
sponsor for some studies and a source for other studies, you must set
up a different database for each role.

The initialization job will fail if:
■ you try to initialize as a sponsor but any of your DSI definitions
includes your own database as the Instance name.

■ you try to initialize as a source but any of your DSI definitions
includes a database other than your own as the Instance name.

If you have this situation, first delete the X Areas associated with the
incorrect instance and then delete the DSI definition that includes the
incorrect instance.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.