After Restoring Siebel Attachments From Backup And Run The SFSpartition Utility For The Second Time The Files From Source File System Partition Are Not Deleted As Stated In The Output And The SAF Files Are Deleted From The Target Partitions (Doc ID 3005870.1)

Last updated on JUNE 14, 2024

Applies to:

Symptoms

After restoring SAF files (Siebel Attachments) from backup and executing sfspartition utility for the second time, the SAF files from source partition are not deleted as stated in the output. However the files are deleted from the target partitions.

The issue can be reproduced at will with the following steps:

1. Create new Siebel File System folders like "C:\Siebel\fs1\att,C:\Siebel\fs2\att,C:\Siebel\fs3\att,C:\Siebel\fs4\att,C:\Siebel\fs5\att"

2. Login to Siebel Application Object Manager and upload couple of attachments. Query for the saf files on existing Siebel File System drive:

C:\Siebel\fs\att\S_ACCNT_ATT_1-2S0C_1-335.SAF
. . .
C:\Siebel\fs\att\S_ACCNT_ATT_1-2S0L_1-33E.SAF

In this example, the "C:\Siebel\fs\att" folder includes 10 SAF files.

3. Make a backup of "C:\Siebel\fs\att" folder.

4. Execute sfspartition utility:

If a SAF file stored in source partition has been already distributed, then sfspartition should not consider that file for moving or should not delete it from the target partition.

Changes

Perform Siebel File System partitioning.

Cause

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