This content has been marked as final. Show 11 replies
It is probably caused by your importexport.properties file being incorrect in some fashion.
Did you update this file when you moved to production? Double check that all fields are correct. I have seen where you forget to move it over period and it will therefore get the default file and almost guarantee to fail. Another scenario is you put the importexport.properties file in the wrong place.
Thanks EW for responding. Please see the property file below and i am trying to export the provisioning info only for one planning application and my export of provisiionning is failing. And my importexport file is at the right location which is in exact place like in Dev environment. Please let me know if i am missing anything.
# EXPORT OPERATIONS orig
# EXPORT OPERATIONS
# export.provisioning.apps=(Hyperion System 9 BI+=Hyperion System 9 BI+:bdowsphypfrs.bdo.com:6800::1)
# export.provisioning.apps=(Analytic Servers:BDOWSDHYPES:1=ASOsamp)
#export.provisioning.apps=(Analytic Servers:BDOWSDHYPES:1=Analytic Servers:BDOWSDHYPES:1)
# export.provisioning.apps=(APS 9.3.1 Servers=APS_9.3.1_BDOWSDHYPWB1_33162)
export.provisioning.apps=(Hyperion System 9 Planning=BDO_DMND)
Thanks for your reply. I was also thinking the same but i dont know how and where exactly i can fix this issue. Used Ldap Browser to Browse through Shared Services and found all the applications have different CSS iD associated to them. Can you all please help me out in order to fix thiis issue.
never want to argue with John.
9 times out of 10 those errors are related to something being incorrect with the .properties file. but John Highlight a good point. We are exporting information from Shared Services not Essbase, so Essbase isn't mentioned in the properties file.
So could be that John is holding back on his idea, but my next thought would be to check to see if Essbase is properly configured to Shared Services. Easy check is to go into SS and if you can provision someone to Essbase.
Again, could be John has the solution and just waiting to see if someone else tells you something before weighing in.
I believe you should have received an export file anyways. Please confirm. It says it only failed for one provisioning.
Did you recently delete an application or did you get a corrupted application? The next lines say that it wasn't able to export for a 'specific' application. So you should have a file with everything (native users, groups, LDAP user, and some provisioning). The file should give you a clue with application failed.
Again just thoughts to help you figure this out.
That is right i agree with you, John answered all my previous weird issues like this before and i am hoping he will help me out another weird one again :). EW, as you said i tried each and everything but didnt find any luck. As you said Provisioning a test account using Shared Services to Essbase was working Good without causing any issue but exporting provisioning info is failing.
Again Thank you all for responding to my issue and helping me out in order to resolve this.
Unfortunately I don't have a solution, it is not an error I have come across, I am sure somebody else might have encountered it.
Can you export provisioning information for a different planning application or does this error happen when you export anything.
Yes you are right except Provisioning info i am able to export all other things like user info ,Group info etc. except Provisioning info ... It is failing when it comes to export provisioning step either it is for planning or essbase application only. If i try to export provisioning info only for BI+ it is exporting info without any problems but this is happening when i attempt to export planning and essbase projects only. Please let me know if you need any further details from me.
Thanks John and EW in trying to help me in order to fix this issue. John, i opened a ticket with Oracle
and waiting for their response from last 5 days and havent heard from them anything regarding this thought to try and see in the forum if anybody faced this problem before.
Again thanks to both of you.