You have two correct answers.  Read the MSDN article again.  http://msdn2.microsoft.com/en-us/library/ms172473.aspx

2 (B). The server likely was stopped by someone, which caused a broken connection and eventually a timeout.

You may be able to get them to attach if the compatibility level is set to 70 in database properties - options.  I have done this in the past without...

0x80004005 is access denied.  This is definitely a permissions problem.  Verify that the username and password are correct and that the user account is working properly on your Oracle server. ...

Register the DTSRuntimeWrap dll and it should work. 

Dialog and transport are communication protocols for the service broker.  Users authenticate through the use of a certificate.  This question is not concise.

Change connection string timeout from 30 to 120 and problem should go away.

It is either a corrupt file or the databse does not have a reference for the assembly.  Try restoring the databse again and/or re-register the assembly.

The Transact-SQL timestamp data type is not the same as the timestamp data type defined in the SQL-92 standard. The SQL-92 timestamp data type is equivalent to the Transact-SQL datetime...

Of course, it is an 8 byte value, so there is a limit and you can easily determinie granularity with just a little math...