> CommCell Console > Backup and Restore Agents > Databases > Documentum

Troubleshooting

DCM0001: Documentum discover instance fails

Documentum discover instance fails with the following error message:

Authentication process failed to start with given inputs. Please validate the inputs and try again.

Symptom

The error message appears and the discover instance fails if the Java path is not present in the Documentum shared location.

Resolution

Follow these steps to resolve this issue.

  1. From the CommCell Browser, navigate to Client Computers.

  2. Right-click the <Client> to be configured and then click Properties.

  3. Click Advanced.

  4. Click the Additional Settings tab and then click Add.

  5. In the Name field, type sDOCUMENTUM_JAVA_HOME.

  6. In the Value field, type the Documentum Java Home path. For example, /oradata/documentum/shared/java/XX.xx

  7. Click OK to save the key.

  8. Click OK.

Now you can create the instance again.

DCM0002: Documentum Backup Operation Goes to a Pending State during Storage Area Backup Phase

Documentum backup operation goes to a pending state with the following error in the log files:

RemoteHost:10.38.20.13 RemoteClient:dbmulti3 RemoteProcess:cvd.exe RemoteProcessId:22248 RemoteThreadId:8636 RemoteService: RemotePort:Type=Socket. IPv4 port=8400, IPv6 port=8400} + {CCvNetwork::CheckDataWaiting(5653)} + {CSessionConnectionSocket::CheckDataWaiting(734)/ErrNo.110.(Connection timed out)-Failed to peek data on socket. Receive returned error.}' (data received)

Symptom

The backup operation goes to a pending state while updating metadata indexing on the MediaAgent. If there are millions of objects for which metadata information has to be updated, the error appears in the log file.

Resolution

To the Documentum Application client and the MediaAgent, add the nINDEXINGBUSYTIMEOUT additional setting and set its value as the number of timeout seconds as shown in the following table. Then, restart the application client and the MediaAgent services.

For instructions on how to add additional settings from the CommCell Console, see Adding or Modifying Additional Settings from the CommCell Console.

Property

Value

Name

nINDEXINGBUSYTIMEOUT

Category

Cvd

Type

Integer

Value

Timeout in seconds

Changes to full-text index path in instance properties is not reflected in the subclient

When updating the details of a Full-Text Index in Instance Properties, the change will not be propagated properly to the Subclient. For Full-text Index modifications, the change needs to made in both the Instance and Subclient Properties.

For example:

  1. While configuring a Documentum instance, you click on the Storage Area and FTI tab and change the path from /documentum/dba/full to documentum/dba/fulltext.

  2. Open the Subclient Properties and in the Full Text Index tab, observe that the path for the Full-text Index still remains as documentum/dba/full. Running a backup job for this subclient will fail because of the invalid Full-text Index path.

  3. Correct the path in the in the Full Text Index tab of the subclient to documentum/dba/fulltext.

  4. Run a backup job on the subclient again, and it will now succeed since the paths match at both the Instance and Subclient levels.

Completed with one or more errors

Backup jobs from Documentum iDataAgent will be displayed as "Completed w/ one or more errors" in the Job History in the following cases:

  • When one of the files cannot be accessed during SA backup or FTI backup phase.

  • When one of the SA hosts goes offline during the backup phase, the corresponding DB backup completes with errors.

  • After successfully backing up the Database, job is killed before archive index.

×

Loading...