Description

After running the fsefile command with any of the following options: --history, --recall,

 

--migrate, --trigger-migration, the command fails and reports:

 

6004 Caught Corba exception.

Explanation

See Workaround.

Workaround

First, try to identify the problem as follows:

 

1. Find out the status of the FSE partition with the command:

 

fsepartition --status PartitionName

 

2. Check if the fse-hsmprocess is running on the corresponding FSE client.

 

Linux specific

 

Use the command ps -ef grep fse-hsm.

 

Windows specific

 

Use Windows Task Manager for this purpose.

 

If the partition status is set to any other value than mounted, and the fse-hsmprocess is

 

running on the client, the problem may be caused by an improper configuration of the

 

omniORB.cfg files. For information on which omniORB.cfg settings are correct and how to

 

configure omniORB.cfg appropriately, see ”Reconfiguring FSE interprocess communication”

 

on page 83.

Description

In a distributed or mixed FSE implementation, after the consolidated FSE system or FSE server is

 

restarted, the fsepartition -l -D command reports FSE partitions on external FSE clients as not

 

mounted.

Explanation

The consolidated FSE system or FSE server lost connection with all external FSE clients after it

 

was restarted.

Workaround

On each external FSE client, restart the FSE processes using the fse --restartcommand.

 

This needs to be done with the above FSE implementations each time after the FSE server or the

 

integrated FSE system is restarted.

HP StorageWorks File System Extender Software user guide 247