Orphaned partitions can appear in the Essbase Administration Services (EAS) Console after doing the following:
- After creating, editing or validating a partition, the partition appears under the Orphaned Partitions Node in EAS.
- After deleting a partition, the partition appears under the Orphaned Partitions Node in EAS.
1. Confirm that the Essbase Server name in the partition matches the Essbase Server name used in the EAS Console under Essbase Servers. For example, if you have added the Essbase Server in the EAS Console using the IP Address, then you must also use the IP Address when creating the partition. If there is a mismatch the partition will become orphaned.
2. An Essbase Server name containing more than 32 characters can also cause the partition to become orphaned. A possible workaround is to use the NODENAME setting in the Essbase.cfg file with the IP Address. For example: NODENAME 127.0.0.1
After making changes to the Essbase.cfg file you must restart the Essbase Server for the settings to take effect.
3. Starting with Essbase v18.104.22.168, enable IPv6.
4. a) Remove “NODENAME” from cfg file if set.
b) Update hosts file with IP, full and short Servernames.
c) Add Essbase server using “EssbaseCluster-1” in EAS without the port number.