sql login permissions: sql-dmo

Showing posts with label sql-dmo. Show all posts

Friday, March 23, 2012

logshipping error

Hi Guys,
i am using log shipping in sql server 2000(sp3) but in loading in the
destination it is giving following error
Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC SQL
Server Driver][SQL Server]Could not redo log record (8078:18995:3), for
transaction ID (0:90997930), on page (1:783096),
in the source database there are no problems now but there wsa one index
corruption and loss of data.
pLS AdviceThis is a multi-part message in MIME format.
--040104080107040407070908
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Sounds like the corruption on the primary DB has put the tlog syncs out
of whack (that's the technical term for it). I would resync from a
recent full DB backup (and subsequent log backups) that was done AFTER
the corruption was fixed. (This might mean a complete resync of the log
shipping pair for you using the DB maint wizard.)
--
*mike hodgson* |/ database administrator/ | mallesons stephen jaques
*T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
*E* mailto:mike.hodgson@.mallesons.nospam.com |* W* http://www.mallesons.com
bijupg@.hotmail.com wrote:
>Hi Guys,
>i am using log shipping in sql server 2000(sp3) but in loading in the
>destination it is giving following error
>Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC SQL
>Server Driver][SQL Server]Could not redo log record (8078:18995:3), for
>transaction ID (0:90997930), on page (1:783096),
>in the source database there are no problems now but there wsa one index
>corruption and loss of data.
>pLS Advice
>
--040104080107040407070908
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>Sounds like the corruption on the primary DB has put the tlog syncs
out of whack (that's the technical term for it).Â I would resync from a
recent full DB backup (and subsequent log backups) that was done AFTER
the corruption was fixed.Â (This might mean a complete resync of the
log shipping pair for you using the DB maint wizard.)</tt> 
<div class="moz-signature">
<title></title>
<meta http-equiv="Content-Type" content="text/html; ">
-- 
 mike
hodgson | database administrator
| mallesons stephen jaques 
T +61 (2) 9296 3668 | F +61
(2) 9296 3885 | M +61
(408) 675 907 
E
<a href="http://links.10026.com/?link=mailto:mike.hodgson@.mallesons.nospam.com">
mailto:mike.hodgson@.mallesons.nospam.com</a> | W <a href="http://links.10026.com/?link=/">http://www.mallesons.com">
http://www.mallesons.com</a> 
</div>
 
 
<a class="moz-txt-link-abbreviated" href="http://links.10026.com/?link=mailto:bijupg@.hotmail.com">bijupg@.hotmail.com</a> wrote:
<blockquote cite="midD73EA24F-DBEA-4E4F-9F4F-797DC31E31FF@.microsoft.com"
type="cite">
<pre wrap="">Hi Guys,
i am using log shipping in sql server 2000(sp3) but in loading in the
destination it is giving following error
Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC SQL
Server Driver][SQL Server]Could not redo log record (8078:18995:3), for
transaction ID (0:90997930), on page (1:783096),
in the source database there are no problems now but there wsa one index
corruption and loss of data.
pLS Advice
</pre>
</blockquote>
</body>
</html>
--040104080107040407070908--|||This is a multi-part message in MIME format.
--=_NextPart_000_000D_01C56A79.C4EDC0F0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: quoted-printable
yes.
Sounds like you need to Re-Synch the DBs
Greg Jackson
PDX, Oregon
--=_NextPart_000_000D_01C56A79.C4EDC0F0
Content-Type: text/html;
charset="Utf-8"
Content-Transfer-Encoding: quoted-printable
=EF=BB=BF<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&

yes.
Sounds like you need to Re-Synch the DBs
Greg Jackson
PDX, Oregon

--=_NextPart_000_000D_01C56A79.C4EDC0F0--

Logshipping error

Hi,
I get the following error after I setup logshipping and
try to restore the copied trn file.
Any ideas'
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 4326:
[Microsoft][ODBC SQL Server Driver][SQL Server]The log in
this backup set terminates at LSN 37123000007023700001,
which is too early to apply to the database. A more
recent log backup that includes LS
N 37731000001578500001 can be
restored.
[Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE
LOG is terminating
abnormally.| I get the following error after I setup logshipping and
| try to restore the copied trn file.
| Any ideas'
|
| [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 4326:
| [Microsoft][ODBC SQL Server Driver][SQL Server]The log in
| this backup set terminates at LSN 37123000007023700001,
| which is too early to apply to the database. A more
| recent log backup that includes LS
| N 37731000001578500001 can be
| restored.
|
| [Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE
| LOG is terminating
| abnormally.
--
It looks like your transaction log backups are out-of-synch. Can you review
your scheduled jobs and make sure that only the log shipping process and no
other independent jobs are creating transaction log backups.
Hope this helps,
--
Eric Cárdenas
SQL Server support

logshipping error

Wednesday, March 7, 2012

Login to MSDE on Win 98

Hi all,

I have the the problem with logging to MSDE using SQL-DMO interface. On the
W2K with LoginSecure=TRUE everything is OK (connect is made without any
parameters)

But when LoginSecure=FALSE (on Win 98)

connect( 'instance_name', 'sa', 'sa_password' )

then it returns error message :

I install MSDE on Win 98 with parameters :

INSTANCENAME='instance_name'
SECURITYMODE=SQL
SAPWD='sa_password'

Server runs with given instance name.

Who knows why I can not login to MSDE ?

TIA,

Marek Powichrowski"Marek Powichrowski" <marekp@.telbank.pl> wrote in message
news:bv81ss$hnp$1@.korweta.task.gda.pl...
> Hi all,
> I have the the problem with logging to MSDE using SQL-DMO interface. On
the
> W2K with LoginSecure=TRUE everything is OK (connect is made without any
> parameters)
> But when LoginSecure=FALSE (on Win 98)
> connect( 'instance_name', 'sa', 'sa_password' )
> then it returns error message :
> Login failed for user 'sa'. Reason : Not associated with a trusted SQL
> I install MSDE on Win 98 with parameters :
> INSTANCENAME='instance_name'
> SECURITYMODE=SQL
> SAPWD='sa_password'
> Server runs with given instance name.
> Who knows why I can not login to MSDE ?
> TIA,
> Marek Powichrowski

The error is slightly strange, since it suggests MSDE is running in Windows
authentication mode, however that isn't supported on Windows 98. Can you
connect to the MSDE instance locally using osql, for example?

osql -S instance_name -U sa -P sa_password

If you can connect like this, then the issue is probably somewhere in your
SQLDMO code, and perhaps you could post the part which makes the connection.
If this doesn't work, then could you post the error message? And did you
install the latest MSDE version, ie. SP3a?

Simon|||>
> The error is slightly strange, since it suggests MSDE is running in
Windows
> authentication mode, however that isn't supported on Windows 98. Can you
> connect to the MSDE instance locally using osql, for example?
> osql -S instance_name -U sa -P sa_password
> If you can connect like this, then the issue is probably somewhere in your
> SQLDMO code, and perhaps you could post the part which makes the
connection.
> If this doesn't work, then could you post the error message? And did you
> install the latest MSDE version, ie. SP3a?

Cause of error was setting LoginSecure to TRUE for the connection made on
the Win 98. When I change LoginSecure to FALSE then connection ends
succesfully (for proper server name user name and password) . So I can
create database using script generated by Enterprise Manager from my
computer and can atatch existing database to MSDE without Enterprise Manager
in the easy way (few lines of code).

Thanks for your support.

Marek Powichrowski

Login to MSDE

Hi all,
I have the the problem with logging to MSDE using SQL-DMO interface. On the
W2K with LoginSecure=TRUE everything is OK (connect is made without any
parameters)
But when LoginSecure=FALSE
connect( 'instance_name', 'sa', 'sa_password' )
it returns error message :
Login failed for user 'sa'. Reason : Not associated with a trusted SQL
I install MSDE Win 98 with parameters :
INSTANCENAME='instance_name'
SECURITYMODE=SQL
SAPWD='sa_password'
Server runs with given instance name.
Who knows why I can not login to MSDE ?
TIA,
Marek PowichrowskiCheck out article 319930, especially the section entitled:
Enable Mixed Mode Authentication After Installation
to verify that MSDE is in fact running in mixed mode.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Uytkownik "Rand Boyd [MSFT]" <rboyd@.onlinemicrosoft.com> napisa w
wiadomoci news:KWta2ad5DHA.824@.cpmsftngxa07.phx.gbl...

quote:

> Check out article 319930, especially the section entitled:
> Enable Mixed Mode Authentication After Installation
> to verify that MSDE is in fact running in mixed mode.
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
>

Thanks for your support.
Marek Powichrowski

Friday, March 23, 2012

logshipping error

Logshipping error

logshipping error

logshipping error

Wednesday, March 7, 2012

Login to MSDE on Win 98

Login to MSDE

sql login permissions

Blog Archive

About Me