Showing posts with label update. Show all posts
Showing posts with label update. Show all posts

Friday, March 30, 2012

Link two tables in UPDATE - ERR:single-row subquery returns more than one row

1 UPDATE PM_ASSIGNMENTS
2 SET PM_ASSIGNMENTS.JOB_TYPE_CODE = (SELECT PM_TASK_DETAILS.JOB_TYPE_CODE
3 FROM PM_ASSIGNMENTS, PM_TASK_DETAILS
4 WHERE ((PM_ASSIGNMENTS.TASK_NUMBER) = (PM_TASK_DETAILS.TASK_NUMBER))
5* AND (PM_ASSIGNMENTS.TASK_NUMBER = '1000'))
SQL> /
SET PM_ASSIGNMENTS.JOB_TYPE_CODE = (SELECT PM_TASK_DETAILS.JOB_TYPE_CODE
*
ERROR at line 2:
ORA-01427: single-row subquery returns more than one rowthe sub-query is returning more than one row for the given condition.

either group-by them, or give all user-key conditions.

regards,
Raghu.sql

Monday, March 26, 2012

Link server problrm connecting to Oracle

I get the following error after trying to do update to an Oracle 9i table
from SQL Server 2000. :
The operation could not be performed because the OLE DB provider 'MSDAORA'
was unable to begin a distributed transaction.
Any ideas to solve this?
Check the following article:
INF: Troubleshooting Linked Server Error 7391
http://support.microsoft.com/?id=306212
-Sue
On Wed, 23 Mar 2005 12:44:06 GMT, "Mori"
<obibiman.nospam@.yahoo.com> wrote:

>I get the following error after trying to do update to an Oracle 9i table
>from SQL Server 2000. :
>The operation could not be performed because the OLE DB provider 'MSDAORA'
>was unable to begin a distributed transaction.
>Any ideas to solve this?
>

Link server problrm connecting to Oracle

I get the following error after trying to do update to an Oracle 9i table
from SQL Server 2000. :
The operation could not be performed because the OLE DB provider 'MSDAORA'
was unable to begin a distributed transaction.
Any ideas to solve this?Check the following article:
INF: Troubleshooting Linked Server Error 7391
http://support.microsoft.com/?id=306212
-Sue
On Wed, 23 Mar 2005 12:44:06 GMT, "Mori"
<obibiman.nospam@.yahoo.com> wrote:

>I get the following error after trying to do update to an Oracle 9i table
>from SQL Server 2000. :
>The operation could not be performed because the OLE DB provider 'MSDAORA'
>was unable to begin a distributed transaction.
>Any ideas to solve this?
>sql

Friday, March 9, 2012

limiting database listings

Update: When I use Query Analyzer to connect, it seems to
work properly, so I believe this could be fixed from a
client standpoint.
Does anybody know of any options in Enterprise Manager
that would limit your database listings to only ones that
you own?
Or another option would even be, if anyone knows of any
Enterprise Manager replacements. Software/websites made
by other people which might not have this problem. Any
input would be much appreciated. thanks!
-ariel
I feel your pain. However I spend most of my time in QA, not EM. The problem is due to the SQL-DMO library that EM is based on, because it loads all information for all databases, not just the names - thus usnig up your bandwidth. This will be "fixed" in
SQL Server 2005 ("Yukon"), in that the database access API will only load the database names, and not all other information, which will speeds things up many times.
Your best bet is to use QA. You can't filter your list. You might also want to consider using the new WebAdmin tool from Microsoft - this might speed things up for you (http://tinyurl.com/3cuzt).
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
|||Is there any way to remove my email address from the old posts? spam + virii like crazy

limiting database listings

Update: When I use Query Analyzer to connect, it seems to
work properly, so I believe this could be fixed from a
client standpoint.
Does anybody know of any options in Enterprise Manager
that would limit your database listings to only ones that
you own?
Or another option would even be, if anyone knows of any
Enterprise Manager replacements. Software/websites made
by other people which might not have this problem. Any
input would be much appreciated. thanks!
-arielI feel your pain. However I spend most of my time in QA, not EM. The problem
is due to the SQL-DMO library that EM is based on, because it loads all inf
ormation for all databases, not just the names - thus usnig up your bandwidt
h. This will be "fixed" in
SQL Server 2005 ("Yukon"), in that the database access API will only load th
e database names, and not all other information, which will speeds things up
many times.
Your best bet is to use QA. You can't filter your list. You might also want to consider
using the new WebAdmin tool from Microsoft - this might speed things up for you (http://tinyurl.com/3cuzt" target="_blank">
http://tinyurl.com/3cuzt).
Mark Allison, SQL Server MVP
http://www.markallison.co.uk|||Is there any way to remove my email address from the old posts? spam + viri
i like crazy