July 14, 2011 at 5:52 am
Dear All,
I have Live DB "PRSP_Live_010909" at live server. I have configured Full Backup Routine with three backups daily. I restored one of the backups with PRSP_Live_010909_13072011 db on our Dev Server. But When I issue the select Statement select * from dbo.CR_CO_LOANEE_LEDGER on PRSP_Live_010909_13072011 db. It give me the Error given below .
Msg 4104, Level 16, State 1, Procedure _dta_mv_123, Line 1
The multi-part identifier "PRSP_Live_010909.dbo.CR_CO_LOANEE_LEDGER.RECPA" could not be bound.
Msg 4104, Level 16, State 1, Procedure _dta_mv_123, Line 1
The multi-part identifier "PRSP_Live_010909.dbo.CR_CO_LOANEE_LEDGER.RECPA" could not be bound.
Msg 4104, Level 16, State 1, Procedure _dta_mv_123, Line 1
The multi-part identifier "PRSP_Live_010909.dbo.CR_CO_LOANEE_LEDGER.RECSC" could not be bound.
Msg 4104, Level 16, State 1, Procedure _dta_mv_123, Line 1
The multi-part identifier "PRSP_Live_010909.dbo.CR_CO_LOANEE_LEDGER.RECSC" could not be bound.
Msg 4104, Level 16, State 1, Procedure _dta_mv_123, Line 1
The multi-part identifier "PRSP_Live_010909.dbo.CR_CO_LOANEE_LEDGER.REBATE" could not be bound.
Msg 4104, Level 16, State 1, Procedure _dta_mv_123, Line 1
The multi-part identifier "PRSP_Live_010909.dbo.CR_CO_LOANEE_LEDGER.REBATE" could not be bound.
Msg 4413, Level 16, State 1, Line 1
Could not use view or function '_dta_mv_123' because of binding errors.
Astonishingly, The table was binding with the name of my Live DB PRSP_Live_010909.dbo.CR_CO_LOANEE_LEDGER.RECPA instead of PRSP_Live_010909_13072011.dbo.CR_CO_LOANEE_LEDGER.RECPA , Because I run query in PRSP_Live_010909_13072011.
By viewing the Error, I restored the backup at dev server with same name as of Live DB and problem was solved. This is happening from last one day, before this we adopt same procedure to restore backup with different name as of live DB and there was no problem.
There is also no problem when we use top (1000) with query but when we give some criteria in where clause then same error occur.
We have created some new indexes on some tables and dropped some unused indexes before problem occur, No other Change has been made on DB so for. I dropped all indexes which I created during this period but Problem is there. At the same time Query is running successfully at Live DB and no problem at the Live DB.
CR_CO_LOANEE_LEDGER is the largest table in our DB with 6516749 records.
Any help would be appreciated, Thanks in advance.
Azhar Iqbal
July 14, 2011 at 6:24 am
what is the definition of Procedure _dta_mv_123?
i suspect that someone has created the procedure with a 4 part qualifier instead of a 3 part qualifier so it is always looking for the database
So DB1.schema1.table1.column1 instead of schema1.table1.column1
July 14, 2011 at 6:53 am
Thanks Dear for Help,
You pointed out problem in a right way,
There many Views that are created in our DB automatically, We have just have replication in our DB and backup routines nothing more. When ever I right click on a view like _dta_mv_123 Then I face the same error.
The Error and views are given in a attached image file. This will explain situation well.
Why these views are being created automatically?
Further help is needed.
Thanks
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply