Yes, are there problems with the database? Typically you see this if the database is experiencing a problem. You would have the same problem if you pasted the SQL into TOAD or SQL*PLUS. Ask your DBA if there is a problem.
This is the Oracle Action:
If this message occurs during a connection attempt, check the setup files for the appropriate SQLNet driver and confirm SQLNet software is correctly installed on the server. If the message occurs after a connection is well established and the error is not due to a physical failure, check if a trace file was generated on the server at failure time. Existence of a trace file may suggest an ORACLE internal error that requires the assistance of Worldwide Customer Support.
But before you worry too much just speak to a DBA.
what we have done is copy the SQL generated in to SQL plus and it runs fine in it. I am totally confused with this error, as only this error comes only while running this query from Business Objects.
I was hoping this wouldn’t happen to you. Yes I have seen this before. A colleague had the problem intermitently on a particular oracle database. We never traced the cause before it just stopped. She said that if she closed BO and opened it again this sometimes solved the problem - and sometimes it didn’t…
what kind of bomain.key did you generate? are you set up to disconnect after each transaction, or is it ‘waiting’ - maybe it timed out? This may be shown in the listener.log file, on the Oracle box.
I had a similar issue on a laptop, but that turned out to be that the docking station and the laptop both had nics, both were ‘active’ - SQL*Net got confused by that (test by running w/out the docking station).
i’d look at the server side listener log - may see messages there. also, look in the bdump / udump folders (again, the oracle box) - you may be generating an exception error there.
3113’s are tough to debug, get your dba involved - you may also have to work with your network folk - this can be generated by corrupted sql*net packets…
good luck (also, do some searching on oracle forums, this error is a common / frustrating one, lots of discussion out there).
I’ve seen this happen numerous times, with several causes. If the database goes down while you are running the query, you will get this message. I’ve also had it happen when the network got overloaded, and the flow of data just got cut off. Try running the query during offpeak hours. That may help.
In Oracle (I believe 8.1.6) there is a bug concerning a parameter Star Join = True. This may not be the exact definition, but this was causing me to have this error randomly. Check with your DBA and have this set to False. We experienced this problem with a report. In our test environment it worked fine (star join = False) in our production environment it failed randomly (star join = True).
got this error message last week, sent it to DBA, and he replied “that is is a known bug in Oracle” and would find a work around. He sent me some modified code in which he coverted my numeric values to char and then back to number. Not sure why this works, but this was the work-around until a patch or something can be implemented.
I am getting same kind of error. Database is Oracle 9i with BOXI R2. Its a migrated report from 6.5. What you think is it bug in Database or some thing wrong in BO.