Freshly install the Essbase 188.8.131.52 on Window server 2008 r-2 with the recommended hardware specification. After Installation configure 184.108.40.206 with the DB/Schema
Take the all data back up of the essbase applications using script export or directly exporting from the cube.
Use the EAS Migration wizard to migrate the essbase applications
After the Migrating the applications successfully,reLoad all the data into cube.
For the 4th Point
IBH error generally caused when there is a mismatch in the index file and the PAG file while e executing the calculation script .Possible solutions are available
The recommended procedure is:
a)Disable all logins.
alter application sample disable connects;
b)Forcibly log off all users.
alter system logout session on database sample.basic;
c)Run the MaxL statement to get invalid block header information.
alter database sample.basic validate data to local logfile 'invalid_blocks';
d)Repair invalid block headers
alter database sample.basic repair invalid_block_headers;
I would bet this is not the official and recommended way for essbase data migration.
It may possibly work, however you cannot request any support from Oracle.
I would choose the supported path.
1. Migration via EAS from 9.3.x to 11.2.x (as you have done)
2. data export in 9.x (e.g. in column format)
3. copy these export files to the 11.2.x machine (...app/db directory)
4. data import in 11.2.x
I would suggest you to take a supported approach what has been suggested by andreml
The essbase object files internally stores the path information and moving from system 9x to 11x whole lot of things have changed even the ARBORPATH.
The way you are doing is not recommended and Oracle will not support.