Oracle 10g - ICE 30
Does any1 know how to resolve ICE 30.
I am packaging Oracle Discoverer Desktop v 9.0.4 (10g) which installs the files with the same name in different directories (under Inventory).
On validation ICE 30 occurs as different components are installing files with the same name.
Any way around the above?
I am packaging Oracle Discoverer Desktop v 9.0.4 (10g) which installs the files with the same name in different directories (under Inventory).
On validation ICE 30 occurs as different components are installing files with the same name.
Any way around the above?
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
MSIPackager
18 years ago
It's just an MSI limitation with the 8.3 formatting system for long file names. It will generate a short file name reference for any files names over 8 characters but because the Oracle install has loads of files with the same name into different folders it causes errors in the MSI. It's not Oracle's fault particularly - other than the way their apps work!
Take the CompID.properties file for example - the 1st reference in the MSI file table will be COMPID~1.PRO
The second will be COMPID~2.PRO and so on until it gets to COMPID~Z.PRO
After that every SFN reference to the file will be COMPID~Z.PRO - which is where the ICE30s start appearing.
I appreciate having all these errors in a package doesn't look good but as far as I'm aware there is no way around it - how can there be? As long as you aren't installing the package on a SFN system then you will be fine.
That's how I understand it anyway [8|] If anyone knows a way to fix ICE30s without creating ICE03s then I'd be interested - and impressed!
Take the CompID.properties file for example - the 1st reference in the MSI file table will be COMPID~1.PRO
The second will be COMPID~2.PRO and so on until it gets to COMPID~Z.PRO
After that every SFN reference to the file will be COMPID~Z.PRO - which is where the ICE30s start appearing.
I appreciate having all these errors in a package doesn't look good but as far as I'm aware there is no way around it - how can there be? As long as you aren't installing the package on a SFN system then you will be fine.
That's how I understand it anyway [8|] If anyone knows a way to fix ICE30s without creating ICE03s then I'd be interested - and impressed!
Posted by:
MSIPackager
18 years ago
As far as I know this error should only present a problem if you are planning on deploying your package to a SFN system.
If you aren't you can either leave the ICE30 errors - or fix them (by removing the SFN file reference) which will create ICE03 errors instead.
I think the package will install and work fine either way... I had the same problem repackaging the Oracle 9i client!
Hope this helps,
Rob.
If you aren't you can either leave the ICE30 errors - or fix them (by removing the SFN file reference) which will create ICE03 errors instead.
I think the package will install and work fine either way... I had the same problem repackaging the Oracle 9i client!
Hope this helps,
Rob.
Posted by:
oofemioo
18 years ago
Wozik:
It complains about both LFN and SFN. Oracle Discoverer installs almost 40 files with the same names to different folders.
MSIPackager:
I've tested this client and it works as far as I know. However the nos. of ICE 30 errors reported by Orca is close to 300! This really concerns me as I've always endeavored to remove all ICE errors I come across in my professional career.
Is this a problem with Oracle not following Microsoft guidelines?
It complains about both LFN and SFN. Oracle Discoverer installs almost 40 files with the same names to different folders.
MSIPackager:
I've tested this client and it works as far as I know. However the nos. of ICE 30 errors reported by Orca is close to 300! This really concerns me as I've always endeavored to remove all ICE errors I come across in my professional career.
Is this a problem with Oracle not following Microsoft guidelines?
Posted by:
rpfenninger
18 years ago
I just got the same problem (ICE30) after repackaging Oracle OLE-DB 9.2.0.7.0.
I know that we used to rename all those Short File Names manually so that they were unique afterwards and we didn't get any ICE30 errors anymore.
However, if this is only a cosmetic thing, I don't think that it is worth spending so much time on it.
Roland
I know that we used to rename all those Short File Names manually so that they were unique afterwards and we didn't get any ICE30 errors anymore.
However, if this is only a cosmetic thing, I don't think that it is worth spending so much time on it.
Roland
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.