Results 1 to 8 of 8

Thread: Multiserver Job

  1. #1
    Join Date
    Sep 2002
    Posts
    17

    Unanswered: Multiserver Job

    hello
    when we are trying to execute a multiserver job the following error is coming.can u please suggest the exact solution for this


    Blocking error preventing further downloads: The specified @database_name ('ibbflorida') does not exist. [SQLSTATE 42000] (Error 14262) Unable to create the local version of MSX job '0x6160950EA825544CA777E978E09ECC59'. [SQLSTATE 42000] (Error 50000)



    thank you.

  2. #2
    Join Date
    Feb 2002
    Location
    Houston, TX
    Posts
    809
    my guess is that your job is referencing a database called 'IBBFLORIDA' and on one of your servers this database does not exist.
    Paul Young
    (Knowledge is power! Get some!)

  3. #3
    Join Date
    Sep 2002
    Posts
    17
    Thanks for responding MR.Paul.

    The database Ibbflorida is existing in one of my server but still it is giving error i could not understand what is the problem

  4. #4
    Join Date
    Feb 2002
    Location
    Houston, TX
    Posts
    809
    you didn't explain what your job does or attaach any code around this db reference so I am guessing here...

    If ther should only be one copy of IBBFlorida tha I suspect that when your job runs on the linked server, the linked server incorrectly assums the IBBFlorida db is local. What happens if you add a server reference. If IBBFlorida is on ServerA and the job is running on ServerB then change all references to IBBFlorida to ServerA.IBBFlorida.
    Paul Young
    (Knowledge is power! Get some!)

  5. #5
    Join Date
    Sep 2002
    Posts
    17
    hi paul
    iam sending u the code for your convenience plz check it here i used db1, db2 in place of original databases names is there any problem with procedure.

    thank you once again

    CREATE procedure dbo.SP_IU_BALANCES
    as
    DECLARE
    @LV1 VARCHAR(255),
    @LV2 VARCHAR(255),
    @LV3 varchar(9)

    declare TABLECURSOR CURSOR
    FOR
    select F3,F4,F1 from SERVER1.DB1.dbo.TABLE1
    OPEN TABLECURSOR
    FETCH NEXT FROM TABLECURSOR INTO @LV1,@LV2,@LV3
    WHILE @@FETCH_STATUS=0
    BEGIN
    update SERVER2.DB2.dbo.TABLE2
    set TABLE2F1 = @LV1,
    TABLE2F2 = @LV2
    where TABLE2F3=@LV3
    FETCH NEXT FROM TABLECURSOR INTO @LV1,@LV2,@LV3
    END;

    CLOSE TABLECURSOR;
    DEALLOCATE TABLECURSOR;

    insert into SERVER1.DB1.dbo.TABLE1(F1, F2, F3, F4, F5)
    (select F1, getdate() +1 , F3, 0, F3
    from SERVER1.DB1.dbo.TABLE1 where F2 = getdate())

  6. #6
    Join Date
    Feb 2002
    Location
    Houston, TX
    Posts
    809
    when you execute this are you still seeing the error from your original post?
    Paul Young
    (Knowledge is power! Get some!)

  7. #7
    Join Date
    Sep 2002
    Posts
    17
    procedure is working fine when we executed manually. but when the same procedure is called in the job then it is giving the error which i mentioned before

  8. #8
    Join Date
    Feb 2002
    Location
    Houston, TX
    Posts
    809
    I am drwaing a blank on this one, I will continue to research the problem.

    Anyone else have an idea?
    Paul Young
    (Knowledge is power! Get some!)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •