> Expert > Backup and Restore Agents > Archive Agents > Database Archive > Oracle Database Archiving

Troubleshooting - Oracle Archiving

Updated

ORARCH00001: Pruning Database Option Can Cause Oracle Warnings

Issue

When the production database deletes the data after the archive completes (see Specifying Archive Criteria for an Oracle Subclient), the following warnings may occur:

  • ORA-14066: illegal option for a non-partitioned index-organized table

  • ORA-10631: SHRINK clause should not be specified for this object

The reason for these warnings is the pruning option uses the SHRINK command, which is not available for Oracle index organized tables.

Solution:

When the Oracle database contains an Index Organized Table (IOT) table, the Oracle commands that allow new data to reclaim space from the deleted data fail. The shrink command failure cause an error that prevents the deletion script from proceeding

Ignore the warnings, or on the archive database set the sShrinkTableAfterPrune Additional Setting to N to prevent the Commvault software from reclaiming space.

  1. From the CommCell Browser, expand Client Computers.

  2. Right-click the Client, and click Properties.

  3. On the Client Properties dialog box, click Advanced.

  4. On the Additional Settings tab of the Client Properties dialog box and click Add.

  5. In the Add Additional Settings dialog box, enter the details for the additional setting.

    1. in the Name box, type sShrinkTableAfterPrune.

    2. In the Category box, type OracleAgent.

    3. In the Type box, select String.

    4. In the Value box, type N.

    5. Click OK to close the Add Additional Setting dialog box.

  6. Click OK to close the Client Properties dialog box.

ORARCH00002: Could Not Fetch Subclient Password

Issue

If you create an archiving instance and subclient that both use the default connect string, archiving jobs may fail if you change the instance connect string.

The error is that the software cannot not decrypt the password.

The Job Pending Reason (JPR) is that the subclient user password cannot be fetched.

Solution:

Re-enter the archive subclient connect string details.

  1. From the CommCell Browser, expand Client Computers | Client >Oracle > instance.

  2. Right-click the archive_subclient, and click Properties.

    The Archive Subclient Properties dialog box is displayed.

  3. On the Archive Options tab, enter the Connect Details for the archive database.

    For information on the connect string details, see Specifying Archive Criteria for an Oracle Subclient for more information.

  4. Click OK to close the Archive Subclient Properties dialog box.

ORARCH00003: Import Fails with an Incompatible Character Set Error

If the staging/destination database character set is different from the archive database character set, the following error is generated.

ORA-39123: Data Pump transportable tablespace job aborted 
 ORA-29345: cannot plug a tablespace into a database using an incompatible character set 
 Job "DEMODB_ARCHIVE"."SYS_IMPORT_TRANSPORTABLE_01" stopped due to fatal error at 17:23:14 
 ]