Welcome to the Oracle Analytics Community: Please complete your User Profile and upload your Profile Picture
Comments
-
What user is the crontab under? So if you run /data/app/oracle/product/Middleware/Oracle_Home/BackUps/CRONCodiubBackupsRPDeCAT.sh -d f it works just fine? What about putting a >> /tmp/foo.log 2>&1 on the end of the crontab statement to see output? Do you know for sure that the crontab is even executing in the first place?…
-
Usually the mistake made with crontab (and I always make it) is that it runs with no environment set, whereas when you test the script you'd usually do it from the user's login shell which will have various paths etc already set. So the crontab may be running, but failing. You can test running it with su without the -…
-
Hardcode the connection details, import your metadata, and then switch the connection back to variable-based.
-
That's fine, but my point stands. In general (anecdotal data excepted), this approach is a bad one. Use the version of the Admin Tool that matches that of your OBIEE server.
-
That'a a pretty bad idea, IMO. You're going to invariably end up with either (a) extra work and/or (b) versions of the RPD that are not compatible and/or (c) issues created by downgrading the RPD.
-
Have you verified that 9514 is the port on which the BI Server (nqsserver) is listening? Use status.sh/.cmd with the -v flag to do this.
-
Why? Why do something that's going to leave you with a non-standard deployment? Leaving scheduler running makes no difference if you're not using it. If you disable it, neatly or not, you're almost certainly always going to have a "component down" big red cross in EM - so each time you mentally need to check is that an…
-
Assuming you're talking about getting an email alerting you if OBIEE has gone down, here's some reading for you: Automated Monitoring of OBIEE in the Enterprise - an overview An introduction to monitoring OBIEE with Nagios Advanced monitoring of OBIEE with Nagios
-
Did you try restarting them ... ?
-
Check if the EM deployment is running in Admin Server
-
What kind of workload are you expecting? Pre-canned reports, ad-hoc, or both? Is your 10TB raw data, or does that include aggregates?
-
Why would you expect an answer to this, after such bad netiquette on your previous post??? Pro tip: generic pen testing sucks. Any fool can tick a bunch of boxes, yet miss serious flaws.
-
The manuals are here: https://docs.oracle.com/middleware/1221/biee/docs.htm
-
What happens if you run the import with just default values? i.e. importServiceInstance('/app/oracle/biee/user_projects/domains/bi','ssi','/app/oracle/migration/importDir/ssi.bar') If you unzip the .bar file, do you see content in the resulting datamodel folder?
-
Looks like the DB you're trying to use for your RCU schema is having problems, and/or you've mis-specified its connection details.
-
Jeremy - it's best to start a new thread for problems, and you can reference back to any others you've found for info. That way you can start with a good description of your problem and environment (http://catb.org/~esr/faqs/smart-questions.html#beprecise) In terms of logs, check the sawlog and saw-diagnostic log, as well…
-
All that log tells you is that bip.py exited with an error code, thus causing the install to fail. Have a dig around and see if you can find the output/error in the execution of that particular step.
-
whether to implement cache or not.? Yes. No. Maybe. It Depends * Yes: In a well-implemented OBIEE solution, I would tend to implement caching as "the icing on the cake". Everything else working nicely, caching can give you that final burst of speed. * No: if you've already got performance problems, if you implement caching…
-
BI Server caching will do what you're wanting. It's worth pointing out that if your query takes 30+ minutes to run you've got serious problems in your stack, in the design and/or implementation of it. Caching will "paper over the cracks" but you should be trying to fix the performance problems at root, not sweep them under…
-
I'd raise an SR then, to clarify if this is expected.