EPMExportAll export clone utility fails to export FDMEE & Reporting analysis artifacts
Errors encountered on the FDMEE server.
1)EPMLCM-34040:EPMLCM-12000:Improper format for migration definition file.
PS E:\Oracle\Middleware\user_projects\epmsystem2\bin> .\epm_cloneexport.bat .\input.properties
EPMLCM-34040:EPMLCM-12000:Improper format for migration definition file.
2)This utility is similar as LCM utility.sh.bat
Documentation on epm_cloneexport utility http://docs.oracle.com/cd/E57185_01/EPMLU/ch07s06s02.html
LCM export is caused by a corruption in the FR report 'pointers' for those problem reports and may be corrected with the following workaround:
1. Export the problem report(s) from the problem Workspace EXPLORE folder location and save to a location you can access so that later you may re-import the *.des file created.
2. After export then delete the original Workspace report from it's problem location.
3. Using Workspace FILE>IMPORT you can then import the exported *.des FR Report file back to the deleted location.
4. Now the LCM should not get that error any more on these deleted/re-imported problem reports
This is an bug ,see below the bug details
Errors encountered on the FDMEE server.
1)EPMLCM-34040:EPMLCM-12000:Improper format for migration definition file.
PS E:\Oracle\Middleware\user_projects\epmsystem2\bin> .\epm_cloneexport.bat .\input.properties
EPMLCM-34040:EPMLCM-12000:Improper format for migration definition file.
2)This utility is similar as LCM utility.sh.bat
Documentation on epm_cloneexport utility http://docs.oracle.com/cd/E57185_01/EPMLU/ch07s06s02.html
LCM export is caused by a corruption in the FR report 'pointers' for those problem reports and may be corrected with the following workaround:
1. Export the problem report(s) from the problem Workspace EXPLORE folder location and save to a location you can access so that later you may re-import the *.des file created.
2. After export then delete the original Workspace report from it's problem location.
3. Using Workspace FILE>IMPORT you can then import the exported *.des FR Report file back to the deleted location.
4. Now the LCM should not get that error any more on these deleted/re-imported problem reports
This is an bug ,see below the bug details
- BugDB:23332828
- BugDB:25519254
No comments:
Post a Comment