Strange error when start cube viewer

Question

Dear all,
i have been installed the BIBdemo succesfully, and run the cube viewer, after that i create a cube on my schema and (by creating a collection from owb9.2 and executing it directly in the db from birdge,after that the cube viewer didn't work correctly for BIBdemo ,and error message is there is errors in the dimensions of my cube ,i didn't understatnd what the relation between the two schemas,my schema and bibdemo schema ,after that i dropped my cube from enterprise manager , and the error remains the same when iam tring to run the cube viewer for bibdeom cubes), please i need a cwm statments to clear any metadata for my cubes and dimensions.
any help is so appreciated

Answer 1

Just for the benefit of anybody running into similar surprising difficulties: it is, in my case, a sniffer-problem.
For determining the client browser's java-vendor from the applet, I used an old trick that used to work pretty well. The relevant part is where the vendor is SUN, but a distinction must be made between SUN java on SUN machines and SUN-java in MSIE. This is done as follows:
     String s = System.getProperty("java.vendor");
     if (s.indexOf("Microsoft") != -1) setJavaVendor(MICROSOFT);
     else if (s.indexOf("Netscape") != -1) setJavaVendor(NETSCAPE);
     else if (s.indexOf("Sun") != -1) {
          try {
// ***> ay, there's the rub:
               getWindow().eval("window.statusbar.visible");
               setJavaVendor(SUN);
          } catch (Exception e) {
               setJavaVendor(SUNINIE);
     } else setJavaVendor(UNKNOWN);
The point is that the java-error is correctly caught (so the end result is as desired), but not the Javascript error that is generated external to the applet by the eval-command. So that is what triggers that error-popup in MSIE6, which does not have any consequences apart from being a nuisance.
Why older MSIE-versions don't seem to mind and ignore the error escapes me, and is not a very intersting question anyway. The thing is just to replace the "statusbar" test by something not involving Javascript.
One more reason to avoid using javascript for such purposes anyway is that Apple cannot make heads or tails of livewire (applets tapping into javascript).
Rik