February 8, 2011 at 6:30 am
Hi all,
We have a job that is being run for the past 4 years and it never failed due to this reason.The job fetches the data from OLEDB Linked Server .and on every tuesday morning at 2:00am we are getting this:
Executed as user: CHN\sqlserver. The OLE DB provider "OraOLEDB.Oracle" for linked server "ODS"
reported an error. The provider did not give any information about the error. [SQLSTATE 42000] (Error 7399)
Cannot fetch a row from OLE DB provider "OraOLEDB.Oracle" for linked server "ODS". [SQLSTATE 42000]
(Error 7330). The step failed.
This has been the issue from the past 2 weeks we don't know why yet?as soon an this error comes if we start the job again it is running perfectly.
Can anyone help me with this.
February 8, 2011 at 6:55 am
Is that possibly some sort of maintenance window or something like that on the Oracle server? That's what it sounds like to me.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
February 8, 2011 at 7:34 am
srilu_bannu (2/8/2011)
Hi all,We have a job that is being run for the past 4 years and it never failed due to this reason.The job fetches the data from OLEDB Linked Server .and on every tuesday morning at 2:00am we are getting this:
Executed as user: CHN\sqlserver. The OLE DB provider "OraOLEDB.Oracle" for linked server "ODS"
reported an error. The provider did not give any information about the error. [SQLSTATE 42000] (Error 7399)
Cannot fetch a row from OLE DB provider "OraOLEDB.Oracle" for linked server "ODS". [SQLSTATE 42000]
(Error 7330). The step failed.
This has been the issue from the past 2 weeks we don't know why yet?as soon an this error comes if we start the job again it is running perfectly.
Can anyone help me with this.
Ask your Oracle DBA to check alert log and listener log at and immediately before time of failure.
_____________________________________
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at Amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.February 18, 2011 at 5:17 am
We have had similar errors like yours in our house and the cause was either that for a short time the user for connecting to the target server could not be acknowledged by the Active Directory Domain Controler or the linked server name could not resolved by any DNS server. Either the network was down shortly or the AD- or DNS-server was in heavy load. But the admin guys never admit that 😉
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply