Anyone ever got this error ?
Error 169. Severity 15. A column has been specified more
than once in the order by list. Columns in the order by
list must be unique.
I am trying to rebuild a clustered index on a table and it
generates this error. I copied the table to another server and rebuild the index without any problems, I then made a copy of the table with a different name on the same server and rebuilt the index without any hassles. The error doesn't make sense given the context. I figured it must be a data corruption issue but I cannot find the problem. Any ideas ?
YorkieQ1 Any ideas ?
A1 What results do you get running:
dbcc Checktable (ProblemTableName) WITH ALL_ERRORMSGS
-- in single user Mode
dbcc Checktable (ProblemTableName, REPAIR_ALLOW_DATA_LOSS ) WITH ALL_ERRORMSGS
-- And if that turns up nothing:
dbcc CheckDB (ProblemTableName) WITH ALL_ERRORMSGS
-- in single user Mode
dbcc CheckDB (ProblemTableName, REPAIR_ALLOW_DATA_LOSS ) WITH ALL_ERRORMSGS|||I have tried some of your suggestions, I cannot at this stage run the single user mode queries but so far nothing has turned up.|||RE: So far nothing has turned up.
You might want to try scheduling the rebuild of the clustered index for a time when no-one would be accessing it (or check to see if any locks related to user activity that involves the table may be causing the behavior).|||The current table that my live application is using is fine, it doesn't have the error however in the process of finding the error I renamed the dud table and made a copy that is now the live table. The system is working but I need to try and find the cause of the problem.
We have some maintenance applications that do cleanup on the table to keep the system running smooth and they were the ones that started to crash, somehow I though of rebuilding the index on the table and that is how I found the problem. If I copied the table and created identical indexes on the new table then I had no problems but if I tried to rebuild the indexes on the dud table I got the errors, I still do.
Problem is that you cannot rebuild the indexes on the table without having the error, in future I know what to look for if the same errors start occuring but rebuilding indexes daily can be a costly exercise on busy tables?|||RE: Problem is that you cannot rebuild the indexes on the table without having the error, in future I know what to look for if the same errors start occuring but rebuilding indexes daily can be a costly exercise on busy tables?
True enough, I'd be concerned about the cause, locus, timing and frequency as well. DBCC INDEXDEFRAG is fairly gentle and may be of help. (It might fail on the bad page and provide some additional clues as well. From there maybe use dbcc page to investigate further?)
Does this happen often?|||To my knowledge this was the first time we caught it, we have had strange hassles before but because of the obscurity of the error I hadn't looked there before. The database is a big one, 20GB, well it's big in my experience and we move about 250 000 records through this table everyday, so it can be very busy. I have the feeling that this is the first time this problem has occured because in the past the other issues have resolved themselves but this one could not be fixed by just rebuilding an index.
I will run the index defrag on the dud table and see what turns up. One more thing which is strange is that even when I ran a insert (into another table) and delete on this 'dud' table is came up with the error 169. Go figure?
Is it worth putting sp3 on windows2000 with SQL2000 sp2?|||Also, I forgot to mention, use dbcc showcontig with dbcc indexdefrag (to provide a measure that lets one get to know when defragging is probably going to be useful).
How fragmented is the EvilClusteredIndex if you run showcontig? For example
Use Pubs
Go
DBCC SHOWCONTIG (Authors, UPKCL_auidind) WITH TABLERESULTS, ALL_LEVELS
DBCC SHOWCONTIG WITH TABLERESULTS, ALL_INDEXES, ALL_LEVELS|||To my knowledge this was the first time we caught it, we have had strange hassles before but because of the obscurity of the error I hadn't looked there before. The database is a big one, 20GB, well it's big in my experience and we move about 250 000 records through this table everyday, so it can be very busy. I have the feeling that this is the first time this problem has occured because in the past the other issues have resolved themselves but this one could not be fixed by just rebuilding an index.
I will run the index defrag on the dud table and see what turns up. Good.
One more thing which is strange is that even when I ran a insert (into another table) and delete on this 'dud' table is came up with the error 169. Go figure? An interesting clue.
Is it worth putting sp3 on windows2000 with SQL2000 sp2?
The servers I run are there (some are also running the hotfix) but I don't think that will address your issue.|||Not defragmented at all, It might have been before I originally tried to recreate the index but I will never know now. When I run the query it scans 2054 pages and moves no pages. This is seriously one of those ghost in the machine stories, the one when you start a job as some who does not have a superstitious bone in your body and everyday you think evermore that the SQL box is after you. Superstitious Queerie Language. Still running tests.|||Not defragmented at all, It might have been before I originally tried to recreate the index but I will never know now.
I guess you droped i.e.(Drop EvilIndex or Alter Table drop index) and tried a fresh Create already?|||Had to. It was the last option I had. I still have the table with the evil index and it still produces the error when I try and rebuild the index so I can keep playing with it but fortunately I have another identical table without the error running live. Using DTS I copied the table and using query analyser I scripted the indexes on the old onto the new table, works like a dream, same data, no problem with index. Might be a bad spot on a disk? Wouldn't know where though because the filegroup is spread accross a few drives.|||I still have the table with the evil index and it still produces the error when I try and rebuild the index so I can keep playing with it but fortunately I have another identical table without the error running live.
Clearly corruption of some form, (though apparently undetectable by dbcc etc.), very unusual indeed; if you find out more please let us know.sql
Showing posts with label specified. Show all posts
Showing posts with label specified. Show all posts
Monday, March 26, 2012
Wednesday, March 21, 2012
Error 14266 - Is 11:59:59 PM not a valid time?
Hi,
I created a DTS package and wanted to schedule it to run at 11:59:59 PM. I
could not save the schedule.
An error "Error 14266: The specified '@.active_end_time' is invalid (valid
values are: before or after @.active_start_time). The job was not saved."
I tried 11:59:58 PM and 12:00:00 AM, both schedules can be saved. Why
11:59:59 PM not ?
Please help,
It sounds like this is from what you are selecting in the
daily frequency section when you schedule the job.
Without the details of this, I'd guess you are selecting
something like "occurs every 24 hours" with "starting at
11:59:59 PM" and "ending at 11:59:59 PM". That will give the
error you have.
If you want the job to run daily at 11:59:59 PM, select the
"occurs once at " option (the first one in the daily
frequency section). It will run once a day (or at whatever
interval you have set or want set in the Occurs section) at
11:59:59 PM.
-Sue
On Thu, 20 Jan 2005 09:03:09 -0800, "Julia"
<Julia@.discussions.microsoft.com> wrote:
>Hi,
>I created a DTS package and wanted to schedule it to run at 11:59:59 PM. I
>could not save the schedule.
>An error "Error 14266: The specified '@.active_end_time' is invalid (valid
>values are: before or after @.active_start_time). The job was not saved."
>I tried 11:59:58 PM and 12:00:00 AM, both schedules can be saved. Why
>11:59:59 PM not ?
>Please help,
|||Selecting "Occurrs Once At:" with a time of 11:59:59 PM will not work.
The scheduling wizard assumes that the end time is 11:59:59 PM. This is
why you get the error 14266. Enter any other time and it will work.
You can easily verify this by entering a different time and saving it.
Then right click on the associated job. Select "All Tasks > Generate
SQL Script...
A dialog box will appear "Generate SQL Script - SERVER NAME/JOB NAME"
Click on the preview button. Click on the copy button and paste into a
text editor. Search for "@.active_end_time"
you will see that it is set to 235959.
Sue Hoegemeier Wrote:[vbcol=seagreen]
> It sounds like this is from what you are selecting in the
> daily frequency section when you schedule the job.
> Without the details of this, I'd guess you are selecting
> something like "occurs every 24 hours" with "starting at
> 11:59:59 PM" and "ending at 11:59:59 PM". That will give the
> error you have.
> If you want the job to run daily at 11:59:59 PM, select the
> "occurs once at " option (the first one in the daily
> frequency section). It will run once a day (or at whatever
> interval you have set or want set in the Occurs section) at
> 11:59:59 PM.
> -Sue
> On Thu, 20 Jan 2005 09:03:09 -0800, "Julia"
> <Julia@.discussions.microsoft.com> wrote:
> PM. I
> (valid
> saved."
bdatch
bdatch's Profile: http://www.msusenet.com/member.php?userid=675
View this thread: http://www.msusenet.com/t-3298150
I created a DTS package and wanted to schedule it to run at 11:59:59 PM. I
could not save the schedule.
An error "Error 14266: The specified '@.active_end_time' is invalid (valid
values are: before or after @.active_start_time). The job was not saved."
I tried 11:59:58 PM and 12:00:00 AM, both schedules can be saved. Why
11:59:59 PM not ?
Please help,
It sounds like this is from what you are selecting in the
daily frequency section when you schedule the job.
Without the details of this, I'd guess you are selecting
something like "occurs every 24 hours" with "starting at
11:59:59 PM" and "ending at 11:59:59 PM". That will give the
error you have.
If you want the job to run daily at 11:59:59 PM, select the
"occurs once at " option (the first one in the daily
frequency section). It will run once a day (or at whatever
interval you have set or want set in the Occurs section) at
11:59:59 PM.
-Sue
On Thu, 20 Jan 2005 09:03:09 -0800, "Julia"
<Julia@.discussions.microsoft.com> wrote:
>Hi,
>I created a DTS package and wanted to schedule it to run at 11:59:59 PM. I
>could not save the schedule.
>An error "Error 14266: The specified '@.active_end_time' is invalid (valid
>values are: before or after @.active_start_time). The job was not saved."
>I tried 11:59:58 PM and 12:00:00 AM, both schedules can be saved. Why
>11:59:59 PM not ?
>Please help,
|||Selecting "Occurrs Once At:" with a time of 11:59:59 PM will not work.
The scheduling wizard assumes that the end time is 11:59:59 PM. This is
why you get the error 14266. Enter any other time and it will work.
You can easily verify this by entering a different time and saving it.
Then right click on the associated job. Select "All Tasks > Generate
SQL Script...
A dialog box will appear "Generate SQL Script - SERVER NAME/JOB NAME"
Click on the preview button. Click on the copy button and paste into a
text editor. Search for "@.active_end_time"
you will see that it is set to 235959.
Sue Hoegemeier Wrote:[vbcol=seagreen]
> It sounds like this is from what you are selecting in the
> daily frequency section when you schedule the job.
> Without the details of this, I'd guess you are selecting
> something like "occurs every 24 hours" with "starting at
> 11:59:59 PM" and "ending at 11:59:59 PM". That will give the
> error you have.
> If you want the job to run daily at 11:59:59 PM, select the
> "occurs once at " option (the first one in the daily
> frequency section). It will run once a day (or at whatever
> interval you have set or want set in the Occurs section) at
> 11:59:59 PM.
> -Sue
> On Thu, 20 Jan 2005 09:03:09 -0800, "Julia"
> <Julia@.discussions.microsoft.com> wrote:
> PM. I
> (valid
> saved."
bdatch
bdatch's Profile: http://www.msusenet.com/member.php?userid=675
View this thread: http://www.msusenet.com/t-3298150
Error 14266 - Is 11:59:59 PM not a valid time?
Hi,
I created a DTS package and wanted to schedule it to run at 11:59:59 PM. I
could not save the schedule.
An error "Error 14266: The specified '@.active_end_time' is invalid (valid
values are: before or after @.active_start_time). The job was not saved."
I tried 11:59:58 PM and 12:00:00 AM, both schedules can be saved. Why
11:59:59 PM not ?
Please help,It sounds like this is from what you are selecting in the
daily frequency section when you schedule the job.
Without the details of this, I'd guess you are selecting
something like "occurs every 24 hours" with "starting at
11:59:59 PM" and "ending at 11:59:59 PM". That will give the
error you have.
If you want the job to run daily at 11:59:59 PM, select the
"occurs once at " option (the first one in the daily
frequency section). It will run once a day (or at whatever
interval you have set or want set in the Occurs section) at
11:59:59 PM.
-Sue
On Thu, 20 Jan 2005 09:03:09 -0800, "Julia"
<Julia@.discussions.microsoft.com> wrote:
>Hi,
>I created a DTS package and wanted to schedule it to run at 11:59:59 PM. I
>could not save the schedule.
>An error "Error 14266: The specified '@.active_end_time' is invalid (valid
>values are: before or after @.active_start_time). The job was not saved."
>I tried 11:59:58 PM and 12:00:00 AM, both schedules can be saved. Why
>11:59:59 PM not ?
>Please help,|||Selecting "Occurrs Once At:" with a time of 11:59:59 PM will not work.
The scheduling wizard assumes that the end time is 11:59:59 PM. This is
why you get the error 14266. Enter any other time and it will work.
You can easily verify this by entering a different time and saving it.
Then right click on the associated job. Select "All Tasks > Generate
SQL Script...
A dialog box will appear "Generate SQL Script - SERVER NAME/JOB NAME"
Click on the preview button. Click on the copy button and paste into a
text editor. Search for "@.active_end_time"
you will see that it is set to 235959.
Sue Hoegemeier Wrote:[vbcol=seagreen]
> It sounds like this is from what you are selecting in the
> daily frequency section when you schedule the job.
> Without the details of this, I'd guess you are selecting
> something like "occurs every 24 hours" with "starting at
> 11:59:59 PM" and "ending at 11:59:59 PM". That will give the
> error you have.
> If you want the job to run daily at 11:59:59 PM, select the
> "occurs once at " option (the first one in the daily
> frequency section). It will run once a day (or at whatever
> interval you have set or want set in the Occurs section) at
> 11:59:59 PM.
> -Sue
> On Thu, 20 Jan 2005 09:03:09 -0800, "Julia"
> <Julia@.discussions.microsoft.com> wrote:
>
> PM. I
> (valid
> saved."
bdatch
---
bdatch's Profile: http://www.msmcse.ms/member.php?userid=675
View this thread: http://www.msmcse.ms/t-3298150
I created a DTS package and wanted to schedule it to run at 11:59:59 PM. I
could not save the schedule.
An error "Error 14266: The specified '@.active_end_time' is invalid (valid
values are: before or after @.active_start_time). The job was not saved."
I tried 11:59:58 PM and 12:00:00 AM, both schedules can be saved. Why
11:59:59 PM not ?
Please help,It sounds like this is from what you are selecting in the
daily frequency section when you schedule the job.
Without the details of this, I'd guess you are selecting
something like "occurs every 24 hours" with "starting at
11:59:59 PM" and "ending at 11:59:59 PM". That will give the
error you have.
If you want the job to run daily at 11:59:59 PM, select the
"occurs once at " option (the first one in the daily
frequency section). It will run once a day (or at whatever
interval you have set or want set in the Occurs section) at
11:59:59 PM.
-Sue
On Thu, 20 Jan 2005 09:03:09 -0800, "Julia"
<Julia@.discussions.microsoft.com> wrote:
>Hi,
>I created a DTS package and wanted to schedule it to run at 11:59:59 PM. I
>could not save the schedule.
>An error "Error 14266: The specified '@.active_end_time' is invalid (valid
>values are: before or after @.active_start_time). The job was not saved."
>I tried 11:59:58 PM and 12:00:00 AM, both schedules can be saved. Why
>11:59:59 PM not ?
>Please help,|||Selecting "Occurrs Once At:" with a time of 11:59:59 PM will not work.
The scheduling wizard assumes that the end time is 11:59:59 PM. This is
why you get the error 14266. Enter any other time and it will work.
You can easily verify this by entering a different time and saving it.
Then right click on the associated job. Select "All Tasks > Generate
SQL Script...
A dialog box will appear "Generate SQL Script - SERVER NAME/JOB NAME"
Click on the preview button. Click on the copy button and paste into a
text editor. Search for "@.active_end_time"
you will see that it is set to 235959.
Sue Hoegemeier Wrote:[vbcol=seagreen]
> It sounds like this is from what you are selecting in the
> daily frequency section when you schedule the job.
> Without the details of this, I'd guess you are selecting
> something like "occurs every 24 hours" with "starting at
> 11:59:59 PM" and "ending at 11:59:59 PM". That will give the
> error you have.
> If you want the job to run daily at 11:59:59 PM, select the
> "occurs once at " option (the first one in the daily
> frequency section). It will run once a day (or at whatever
> interval you have set or want set in the Occurs section) at
> 11:59:59 PM.
> -Sue
> On Thu, 20 Jan 2005 09:03:09 -0800, "Julia"
> <Julia@.discussions.microsoft.com> wrote:
>
> PM. I
> (valid
> saved."
bdatch
---
bdatch's Profile: http://www.msmcse.ms/member.php?userid=675
View this thread: http://www.msmcse.ms/t-3298150
Error 14266 - Is 11:59:59 PM not a valid time?
Hi,
I created a DTS package and wanted to schedule it to run at 11:59:59 PM. I
could not save the schedule.
An error "Error 14266: The specified '@.active_end_time' is invalid (valid
values are: before or after @.active_start_time). The job was not saved."
I tried 11:59:58 PM and 12:00:00 AM, both schedules can be saved. Why
11:59:59 PM not ?
Please help,It sounds like this is from what you are selecting in the
daily frequency section when you schedule the job.
Without the details of this, I'd guess you are selecting
something like "occurs every 24 hours" with "starting at
11:59:59 PM" and "ending at 11:59:59 PM". That will give the
error you have.
If you want the job to run daily at 11:59:59 PM, select the
"occurs once at " option (the first one in the daily
frequency section). It will run once a day (or at whatever
interval you have set or want set in the Occurs section) at
11:59:59 PM.
-Sue
On Thu, 20 Jan 2005 09:03:09 -0800, "Julia"
<Julia@.discussions.microsoft.com> wrote:
>Hi,
>I created a DTS package and wanted to schedule it to run at 11:59:59 PM. I
>could not save the schedule.
>An error "Error 14266: The specified '@.active_end_time' is invalid (valid
>values are: before or after @.active_start_time). The job was not saved."
>I tried 11:59:58 PM and 12:00:00 AM, both schedules can be saved. Why
>11:59:59 PM not ?
>Please help,|||Selecting "Occurrs Once At:" with a time of 11:59:59 PM will not work
The scheduling wizard assumes that the end time is 11:59:59 PM. This i
why you get the error 14266. Enter any other time and it will work.
You can easily verify this by entering a different time and saving it
Then right click on the associated job. Select "All Tasks > Generat
SQL Script...
A dialog box will appear "Generate SQL Script - SERVER NAME/JOB NAME"
Click on the preview button. Click on the copy button and paste into
text editor. Search for "@.active_end_time"
you will see that it is set to 235959.
Sue Hoegemeier Wrote:
> It sounds like this is from what you are selecting in the
> daily frequency section when you schedule the job.
> Without the details of this, I'd guess you are selecting
> something like "occurs every 24 hours" with "starting at
> 11:59:59 PM" and "ending at 11:59:59 PM". That will give the
> error you have.
> If you want the job to run daily at 11:59:59 PM, select the
> "occurs once at " option (the first one in the daily
> frequency section). It will run once a day (or at whatever
> interval you have set or want set in the Occurs section) at
> 11:59:59 PM.
> -Sue
> On Thu, 20 Jan 2005 09:03:09 -0800, "Julia"
> <Julia@.discussions.microsoft.com> wrote:
> >Hi,
> >
> >I created a DTS package and wanted to schedule it to run at 11:59:5
> PM. I
> >could not save the schedule.
> >
> >An error "Error 14266: The specified '@.active_end_time' is invali
> (valid
> >values are: before or after @.active_start_time). The job was no
> saved."
> >
> >I tried 11:59:58 PM and 12:00:00 AM, both schedules can be saved. Why
> >11:59:59 PM not ?
> >
> >Please help
--
bdatc
----
bdatch's Profile: http://www.msusenet.com/member.php?userid=67
View this thread: http://www.msusenet.com/t-329815sql
I created a DTS package and wanted to schedule it to run at 11:59:59 PM. I
could not save the schedule.
An error "Error 14266: The specified '@.active_end_time' is invalid (valid
values are: before or after @.active_start_time). The job was not saved."
I tried 11:59:58 PM and 12:00:00 AM, both schedules can be saved. Why
11:59:59 PM not ?
Please help,It sounds like this is from what you are selecting in the
daily frequency section when you schedule the job.
Without the details of this, I'd guess you are selecting
something like "occurs every 24 hours" with "starting at
11:59:59 PM" and "ending at 11:59:59 PM". That will give the
error you have.
If you want the job to run daily at 11:59:59 PM, select the
"occurs once at " option (the first one in the daily
frequency section). It will run once a day (or at whatever
interval you have set or want set in the Occurs section) at
11:59:59 PM.
-Sue
On Thu, 20 Jan 2005 09:03:09 -0800, "Julia"
<Julia@.discussions.microsoft.com> wrote:
>Hi,
>I created a DTS package and wanted to schedule it to run at 11:59:59 PM. I
>could not save the schedule.
>An error "Error 14266: The specified '@.active_end_time' is invalid (valid
>values are: before or after @.active_start_time). The job was not saved."
>I tried 11:59:58 PM and 12:00:00 AM, both schedules can be saved. Why
>11:59:59 PM not ?
>Please help,|||Selecting "Occurrs Once At:" with a time of 11:59:59 PM will not work
The scheduling wizard assumes that the end time is 11:59:59 PM. This i
why you get the error 14266. Enter any other time and it will work.
You can easily verify this by entering a different time and saving it
Then right click on the associated job. Select "All Tasks > Generat
SQL Script...
A dialog box will appear "Generate SQL Script - SERVER NAME/JOB NAME"
Click on the preview button. Click on the copy button and paste into
text editor. Search for "@.active_end_time"
you will see that it is set to 235959.
Sue Hoegemeier Wrote:
> It sounds like this is from what you are selecting in the
> daily frequency section when you schedule the job.
> Without the details of this, I'd guess you are selecting
> something like "occurs every 24 hours" with "starting at
> 11:59:59 PM" and "ending at 11:59:59 PM". That will give the
> error you have.
> If you want the job to run daily at 11:59:59 PM, select the
> "occurs once at " option (the first one in the daily
> frequency section). It will run once a day (or at whatever
> interval you have set or want set in the Occurs section) at
> 11:59:59 PM.
> -Sue
> On Thu, 20 Jan 2005 09:03:09 -0800, "Julia"
> <Julia@.discussions.microsoft.com> wrote:
> >Hi,
> >
> >I created a DTS package and wanted to schedule it to run at 11:59:5
> PM. I
> >could not save the schedule.
> >
> >An error "Error 14266: The specified '@.active_end_time' is invali
> (valid
> >values are: before or after @.active_start_time). The job was no
> saved."
> >
> >I tried 11:59:58 PM and 12:00:00 AM, both schedules can be saved. Why
> >11:59:59 PM not ?
> >
> >Please help
--
bdatc
----
bdatch's Profile: http://www.msusenet.com/member.php?userid=67
View this thread: http://www.msusenet.com/t-329815sql
Error 14262: specified @job_id... does not exist
Got a client who is getting this error when trying "Start synchronizing" on
a subscription in Enterprise Manager. When the subscription is run using the
Administrator account which originally created it, it runs OK. But when a
different account is being used, this error is thrown. Do subscriptions have
to be synchronized by the account which created them?
--
Mark
Is this a push or pull subscription? How is the subscription run?
The account should be in the PAL and the job owner should be the sa account.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Mark Rendle" <markdotrendleatcomputersoftwaredotcom> wrote in message
news:OKJGoHeFGHA.516@.TK2MSFTNGP15.phx.gbl...
> Got a client who is getting this error when trying "Start synchronizing"
> on a subscription in Enterprise Manager. When the subscription is run
> using the Administrator account which originally created it, it runs OK.
> But when a different account is being used, this error is thrown. Do
> subscriptions have to be synchronized by the account which created them?
> --
> --
> Mark
>
|||It's a pull subscription to a merge replication.
--
Mark
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:ukMaDdeFGHA.3056@.TK2MSFTNGP09.phx.gbl...
> Is this a push or pull subscription? How is the subscription run?
> The account should be in the PAL and the job owner should be the sa
> account.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Mark Rendle" <markdotrendleatcomputersoftwaredotcom> wrote in message
> news:OKJGoHeFGHA.516@.TK2MSFTNGP15.phx.gbl...
>
|||I've seen this error when the subscription has been running, was deleted,
and then recreated. EM has cached the old job's information. Can you try a
refresh before trying to run the job again?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Mark Rendle" <markdotrendleatcomputersoftwaredotcom> wrote in message
news:%23mzaXIpFGHA.2012@.TK2MSFTNGP14.phx.gbl...
> It's a pull subscription to a merge replication.
> --
> --
> Mark
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:ukMaDdeFGHA.3056@.TK2MSFTNGP09.phx.gbl...
>
a subscription in Enterprise Manager. When the subscription is run using the
Administrator account which originally created it, it runs OK. But when a
different account is being used, this error is thrown. Do subscriptions have
to be synchronized by the account which created them?
--
Mark
Is this a push or pull subscription? How is the subscription run?
The account should be in the PAL and the job owner should be the sa account.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Mark Rendle" <markdotrendleatcomputersoftwaredotcom> wrote in message
news:OKJGoHeFGHA.516@.TK2MSFTNGP15.phx.gbl...
> Got a client who is getting this error when trying "Start synchronizing"
> on a subscription in Enterprise Manager. When the subscription is run
> using the Administrator account which originally created it, it runs OK.
> But when a different account is being used, this error is thrown. Do
> subscriptions have to be synchronized by the account which created them?
> --
> --
> Mark
>
|||It's a pull subscription to a merge replication.
--
Mark
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:ukMaDdeFGHA.3056@.TK2MSFTNGP09.phx.gbl...
> Is this a push or pull subscription? How is the subscription run?
> The account should be in the PAL and the job owner should be the sa
> account.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Mark Rendle" <markdotrendleatcomputersoftwaredotcom> wrote in message
> news:OKJGoHeFGHA.516@.TK2MSFTNGP15.phx.gbl...
>
|||I've seen this error when the subscription has been running, was deleted,
and then recreated. EM has cached the old job's information. Can you try a
refresh before trying to run the job again?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Mark Rendle" <markdotrendleatcomputersoftwaredotcom> wrote in message
news:%23mzaXIpFGHA.2012@.TK2MSFTNGP14.phx.gbl...
> It's a pull subscription to a merge replication.
> --
> --
> Mark
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:ukMaDdeFGHA.3056@.TK2MSFTNGP09.phx.gbl...
>
Wednesday, March 7, 2012
Error 0x80070002 while preparing to load the package. The system cannot find the file specified
Hi,
I have a package which calls another package. It had been working fine for a while. Recently I changed the connection managers' names. Everything in the parent package works fine. Database has been updated correctly. But when it comes to calling the child package it generates :
OnError,CRPRCHMSQCZ,,Execute AMSClientAgentMaintenance,,,3/8/2007 5:49:38 PM,3/8/2007 5:49:38 PM,-1073602332,0x,Error 0x80070002 while preparing to load the package. The system cannot find the file specified.
. (there is a period here instead of a file name)
I tested the child package on the server. It works fine. I connected the child package to the Execute Package Task by selecting from the packages on the server. So it is there for sure. Connection manager's name is read from the .dtsConfig. Child package is executed from my development machine but not on the server. I made a small test package just to call this child package, it generates the same error...
Any help is appreciated
Gulden
Renaming the connection managers must have corrupted the package.
I restored from the backup and left the connection manager's names as they are.
Error 0x80070002 while preparing to load the package. The system cannot find the file specified
Hi,
I have a package which calls another package. It had been working fine for a while. Recently I changed the connection managers' names. Everything in the parent package works fine. Database has been updated correctly. But when it comes to calling the child package it generates :
OnError,CRPRCHMSQCZ,,Execute AMSClientAgentMaintenance,,,3/8/2007 5:49:38 PM,3/8/2007 5:49:38 PM,-1073602332,0x,Error 0x80070002 while preparing to load the package. The system cannot find the file specified.
. (there is a period here instead of a file name)
I tested the child package on the server. It works fine. I connected the child package to the Execute Package Task by selecting from the packages on the server. So it is there for sure. Connection manager's name is read from the .dtsConfig. Child package is executed from my development machine but not on the server. I made a small test package just to call this child package, it generates the same error...
Any help is appreciated
Gulden
Renaming the connection managers must have corrupted the package.
I restored from the backup and left the connection manager's names as they are.
Sunday, February 26, 2012
ERROR : FOR UPDATE cannot be specified on a READ ONLY ...
Hi All,
I am using SQL Server 2000 + JDeveloper 10g with ADF.
When i try to make changes to data and do COMMIT, I receive ERROR, I
have tried both JDBC Driver from Microsoft and jTDS, both FAILS.
Here is the error :
With Microsoft JDBC Driver :
(oracle.jbo.DMLException) JBO-26080: Error while selecting entity for
Departments
-- LEVEL 1: DETAIL 0 --
(java.sql.SQLException) [Microsoft][SQLServer 2000 Driver for
JDBC][SQLServer] FOR UPDATE cannot be specified on a READ ONLY cursor.
With jTDS JDBC Driver :
(oracle.jbo.DMLException) JBO-26080: Error while selecting entity for
Departments
-- LEVEL 1: DETAIL 0 --
(java.sql.SQLException) Line 1: FOR UPDATE clause allowed only for
DECLARE CURSOR.
Pls any body help...
Thank you,
Krist
Quite simple, really. SQL Server does not support FOR UPDATE; at least
not in the way that Oracle does. It's not standard SQL.
Alin,
The jTDS Project.
|||Hi ,
Thank you for your reply, it works now if I use JDBC driver from
Microsoft.
But if I use jTDS JDBC Driver, I get this error :
(oracle.jbo.DMLException) JBO-26041: Failed to post data to database
during "Update": SQL Statement
"UPDATE dbo.DEPARTMENTS SET DEPARTMENT_NAME=? WHERE DEPARTMENT_ID=?".
-- LEVEL 1: DETAIL 0 --
(java.sql.SQLException) Invalid parameter index 1.
Is there any options /setting on jDTS diver that I miss ?
Thank you for your help,
Krist
|||xtanto@.hotmail.com wrote:
> Hi ,
> Thank you for your reply, it works now if I use JDBC driver from
> Microsoft.
> But if I use jTDS JDBC Driver, I get this error :
> (oracle.jbo.DMLException) JBO-26041: Failed to post data to database
> during "Update": SQL Statement
> "UPDATE dbo.DEPARTMENTS SET DEPARTMENT_NAME=? WHERE DEPARTMENT_ID=?".
> -- LEVEL 1: DETAIL 0 --
> (java.sql.SQLException) Invalid parameter index 1.
> Is there any options /setting on jDTS diver that I miss ?
What does this have to do with FOR UPDATE?
Alin.
|||Hi Alin,
I am sorry, yes FOR UPDATE problem already solved after I upgrade to
JDev 10.1.2 and Oracle fix the problem by generating the correct sql
syntax for sqlserver.
However I still have problem with jTDS (described above).
I also post this in jTDS forum.
Thank you,
Krist
|||Could you enable DriverManager logging just before executing the code
that generates the exception and post the resulting log dump?
Alin.
I am using SQL Server 2000 + JDeveloper 10g with ADF.
When i try to make changes to data and do COMMIT, I receive ERROR, I
have tried both JDBC Driver from Microsoft and jTDS, both FAILS.
Here is the error :
With Microsoft JDBC Driver :
(oracle.jbo.DMLException) JBO-26080: Error while selecting entity for
Departments
-- LEVEL 1: DETAIL 0 --
(java.sql.SQLException) [Microsoft][SQLServer 2000 Driver for
JDBC][SQLServer] FOR UPDATE cannot be specified on a READ ONLY cursor.
With jTDS JDBC Driver :
(oracle.jbo.DMLException) JBO-26080: Error while selecting entity for
Departments
-- LEVEL 1: DETAIL 0 --
(java.sql.SQLException) Line 1: FOR UPDATE clause allowed only for
DECLARE CURSOR.
Pls any body help...
Thank you,
Krist
Quite simple, really. SQL Server does not support FOR UPDATE; at least
not in the way that Oracle does. It's not standard SQL.
Alin,
The jTDS Project.
|||Hi ,
Thank you for your reply, it works now if I use JDBC driver from
Microsoft.
But if I use jTDS JDBC Driver, I get this error :
(oracle.jbo.DMLException) JBO-26041: Failed to post data to database
during "Update": SQL Statement
"UPDATE dbo.DEPARTMENTS SET DEPARTMENT_NAME=? WHERE DEPARTMENT_ID=?".
-- LEVEL 1: DETAIL 0 --
(java.sql.SQLException) Invalid parameter index 1.
Is there any options /setting on jDTS diver that I miss ?
Thank you for your help,
Krist
|||xtanto@.hotmail.com wrote:
> Hi ,
> Thank you for your reply, it works now if I use JDBC driver from
> Microsoft.
> But if I use jTDS JDBC Driver, I get this error :
> (oracle.jbo.DMLException) JBO-26041: Failed to post data to database
> during "Update": SQL Statement
> "UPDATE dbo.DEPARTMENTS SET DEPARTMENT_NAME=? WHERE DEPARTMENT_ID=?".
> -- LEVEL 1: DETAIL 0 --
> (java.sql.SQLException) Invalid parameter index 1.
> Is there any options /setting on jDTS diver that I miss ?
What does this have to do with FOR UPDATE?
Alin.
|||Hi Alin,
I am sorry, yes FOR UPDATE problem already solved after I upgrade to
JDev 10.1.2 and Oracle fix the problem by generating the correct sql
syntax for sqlserver.
However I still have problem with jTDS (described above).
I also post this in jTDS forum.
Thank you,
Krist
|||Could you enable DriverManager logging just before executing the code
that generates the exception and post the resulting log dump?
Alin.
Subscribe to:
Posts (Atom)