http://www.americansupercamp.com/forum/welcome/193-watch-24-live-another-day-season-9-episode-7-free
↧
Thank you for helping me
↧
Mirroring failover
Hi,
My Mirroring failed over suddenly, to look at the possible reasons for this, I checkd the error logs and found the following
2014-06-10 12:16:57.28 spid38s SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'SQL Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2014-06-10 12:16:57.28 spid36s SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'Bound Trees' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2014-06-10 12:16:57.30 Logon Error: 18456, Severity: 14, State: 16.
2014-06-10 12:16:57.30 Logon Login failed for user 'XXXX'. [CLIENT: xxx.xxx.xx.xx}
2014-06-10 12:16:57.30 Logon Error: 18456, Severity: 14, State: 16.
2014-06-10 12:16:57.30 Logon Login failed for user 'Domain\xxxx'. [CLIENT: <local machine>]
2014-06-10 12:16:57.30 Logon Error: 18456, Severity: 14, State: 16.
2014-06-10 12:16:57.30 Logon Login failed for user 'User1'. [CLIENT: xxx.xx.xx.xxx}
2014-06-10 12:16:57.30 spid38s Starting up database 'DB1'
2014-06-10 12:16:57.30 spid35s Starting up database 'DB2'.
2014-06-10 12:16:57.31 spid23s The mirrored database "DB1" is changing roles from "PRINCIPAL" to "MIRROR" due to Role Syncronization.
I don't know what to conclude from this.
Can some one please help me here
Apart from the error log, how can I get more info on the failover., The Mirroring Monitor does not give me much information either
↧
↧
Mirror error 1418 (in principal server sql error log - :DNS lookup failed with error: '11004
Task- Mirroring between DC and DR. DC servers are in failover clustering having Virtual IP
xxx.xxx.xx.34. DR server is running on standalone server with IP xx.xxx.xx.73.DC&DR servers are in trusted domain having different subnet.
- SQL Servers are installed with same service account (domain account abc\admin) on DC &DR Site.
- Mirrored DB is restored with no recovery having latest full &transaction backup.
- port is used 3399. Opened this port on both side on firewall.
- Telnet is successfully executed from DC to DR and vice versa. On DC IP xxx.xxx.xx.34 (Virtual cluster IP).
- Endpoints are created on both side.
- But when configuring mirroring .error 1418 is occurred.
- Seen in sql log error in principal server :- ERROR :DNS lookup failed with error: '11004(The requested name is valid<c/> but no data of the requested type was found.)
- Checked DNS ,itz working ok.
- There is no error generating in SQL log of Mirror server.
- done for grant permission for endpoint
--GRANT CONNECT on ENDPOINT::Mirroring TO public; on both principal and mirror server.
@Please help.
Regards Naveen
↧
Automatic failover doesn't failback to the first server if the second server is lost.
Hi Everybody,
We use the database mirroring a lot in our product solutions and we have recently experienced a strange behaviour in our failover tests with SQL2008R2.
We have 2 servers running Windows 2008 R2 standard and SQL 2008 R2 standard SP2. (let's call them DB1 and DB2)
We also have a Witness workstation running SQL 2008 Express on a Windows 7
A database from DB1 is mirrored to DB2 in "safety full" mode, with witness. At this stage, the database is principal on DB1 and mirror on DB2
To test the automatic failover, we first restart the DB1 server which has the database in principal mode
After a few seconds, the database on DB2 becomes principal, which is normal , that's exactly what we want.
After a few minutes, DB1 comes back online and its database takes the mirror role (still OK). At this stage then, the database is principal on DB2 and mirror on DB1
when the monitoring application shows that the mirror is synchronized and that both servers are connected to the witness, we restart DB2 to trigger an automatic failover to DB1.
What we see is that DB1 never takes the principal role and the database stays in mirror.
In the DB1 Errorlog, I only see these 2 lines when DB2 disappears, no other message related to the mirroring session.
2014-01-22 08:57:26.91 spid43s Starting up database 'Test123'.
2014-01-22 08:57:26.95 spid43s Bypassing recovery for database 'Test123' because it is marked as a mirror database, which cannot be recovered. This is an informational message only. No user action is required.
When DB2 comes back online, the database on DB2 keeps its principal status and the database on DB1 stays mirror.
And what is really really strange is that, if I restart DB2 once again, directly after that, DB1 failover normally and the database on DB1 takes the principal role after a few seconds. without any configuration changes between the 2 restarts.
DB1 errorlog shows then :
2014-01-22 09:00:37.53 spid29s Error: 1474, Severity: 16, State: 1.2014-01-22 09:00:37.53 spid29s Database mirroring connection error 4 'An error occurred while receiving data: '64(The specified network name is no longer available.)'.' for 'TCP://DB2:5022'.
2014-01-22 09:00:37.53 spid18s Database mirroring is inactive for database 'Test123'. This is an informational message only. No user action is required.
2014-01-22 09:00:42.37 spid32s The mirrored database "Test123" is changing roles from "MIRROR" to "PRINCIPAL" due to Auto Failover.
2014-01-22 09:00:42.39 spid32s Recovery is writing a checkpoint in database 'Test123' (7). This is an informational message only. No user action is required.
2014-01-22 09:00:42.39 spid32s Recovery completed for database Test123 (database ID 7) in 78 second(s) (analysis 0 ms, redo 0 ms, undo 7 ms.) This is an informational message only. No user action is required.
So, if I summarize,
- a first failover from DB1 to DB2 always work
- then, a restart of DB2 never failover to DB1
- a second restart of DB2 always failover to DB1
This is pretty much systematic on one our server couple.
Any explanation for this or any idea where I can search to find the reason of this strange behavior ?
Thanks a lot for your help
Seb
↧
Hoe could this possibly be
http://m.gamevilusa.com/forums/group.php?discussionid=84319
http://scriptogr.am/tiff43tech
↧
↧
Database Mirroring failover
Hi,
I have configured mirroring, server A and server B, suppose if server A down, what are the action we need to tak bring up principal server.
Thanks in advance
Shashikala
↧
using WMI alert for mirroring in Sql server 2012
We are using mirroring in Sql Server 2012 and we are using WMI alerts for some of events such as Connection lost,Manual failover,...
In alert definition we have set the followings:
Type: WMI event alert
NameSpace: \\.\root\Microsoft\SqlServer\ServerEvents\MSSQLSERVER
Query: select * from DATABASE_MIRRORING_STATE_CHANGE where State = 6
The alert is bing triggered correctly,but on email description instead of having meaningful explaination like 'Connection lost',We have the same query:
Query: select * from DATABASE_MIRRORING_STATE_CHANGE where State = 6
We have used the same implementation in our Sql Server 2008 servers and it is working fine.This mashine (Sql Server 2012) is a new mashine.
I would appreciate if someone help me on this.AlsoI checked and 'Include body of e-mail in notification message' was already set.
Thanks
Aspet
A.G
↧
Witness provision Failure (Error Code 1456) for across Data center Mirroring Session
Hello Support,
We are provisioning Mirroring Session between two SQL Servers in VM hosted in different data centers. as per steps described in TechNet
- Principle (East US)
- Mirror (West US)
We are able to establish mirroring session successfully. This works fine for manual fail over.
While establishing automatic fail over and trying to set witness server we are facing following issue on "Alter Database Set Witness ..." statement,
Msg 1456, Level 16, State 3, Line 1 The ALTER DATABASE command could not be sent to the remote server instance 'TCP://witness_address:witness_port'. The database mirroring configuration was not changed. Verify that the server is connected, and try again.
Witness Server we had provisioned first in Europe Data center and then in East US also but it fails with above error each time.
Please not we are able to TelNet the witness server and also able to connect using SQL Server Management Studio from Principal server.
Please provide us more guide line or suggestions what could be the possibilities and how to rectify the same.
Regards,
Ved Yadav
↧
Is distrubution database system database?
Is distrubution database consider as system database?
Thanks
Shashikala
↧
↧
create mirror on active active cluster
have you tried this before?
on active active cluster, one instance ins1, another instance ins2, they are on same cluster. On ins1, create a database called pridb. Can I create one mirror on another instance ins2? what will happened if failover happened in ins1? Any other issue/concerns?
Thanks,
SkyRiver
↧
CALS USAGE
We have 2 Tier system
We have IIS, and IIS setup is connected to the MSSQL database
From IIS we have only one connection to the MSSQL database , But our IIS system will access by many users ,
Can't we use the CAL based license for that , Please advice
Riki
↧
DB Mirroring Listener port different
HI All
Today I setup first time DB mirroring for vCenter application, during failover my application vCenter not able to connect. During investigation I found my listener port is different on both nodes (Principal 5022) and (Mirror 5023). Please suggest if differe port can fail my failover test.
Getting below error -sql server error:- 2146893022 SQL Server native client 10.0 sql server network vcenter.
Please help me and give your valuable suggestion, its bit urgent.
↧
sql server 2008 backup and restore
Hello,
If I restore a backup file to another server, then does it also copy across the table Types, permissions, etc?
Thanks
If I restore a backup file to another server, then does it also copy across the table Types, permissions, etc?
Thanks
↧
↧
SQL 2008 R2 - Mirror sys.master_files data file size not updating
Hi,
I have an odd issue where the primary server is SQL 2008 R2 SP1 and the secondary is SQL 2008 R2 SP2. I have databases mirroring between these servers. We recently moved the log file on the secondary to a different drive. The file sizes match and are updating exactly the same between both servers. The mirror monitor shows the mirroring successful and everything is up to date. When we check the sys.master_files tables on the mirror, the size of the data file has not updated since moving the log file. Tried restarting SQL but not joy.
Anyone have any ideas?
Thanks
Rob
↧
mirroring
hello,
we have mirroring in place.
it takes table data from sql server server1 to server2.
It does not seem to copy the things such as stored procs, functions, views, etc.
1- Is it possible to set this mirroring so that it also copies what I mentioned above?
2- Is mirroring the same as replication?
3- is it possible to restore the latest backup of the production server and restore it into the mirroring server? this is so that the mirroring server will have all the production stored procs, views, etc.? this then avoids running the production changed stored
proc or view in the mirroring server one by one.
Thanks
↧
Recompile error in SQL Server mirror
Hi,
I have a problem with SQL Server mirror (from SQL1 to SQL2) … I did some changes in a stored procedure on the principal server (SQL1), with ALTER statement, and after several hours I performed a failover to the mirrored server (SQL2).
When I tried to run the SP on the second server (SQL2, now the principal) I got the following error:
System.Data.SqlClient.
The stored procedure in SQL2 was updated with the changes form SQL1, but only after I ransp_recompile, the problem was solved.
Did anyone encounter this problem before?
Any help would be appreciated…
Thanks
Chen
↧
Mirror and Witness Connection in a Disconnected state immediately after adding Witness Server to Mirror session.
After adding the Witness Server to the Mirror session, the Witness Connection state between the Mirror and Witness Connection is Disconnected and the state between Principal and Witness Connection is Connected.
The procedures defined in Books Online was used to setup Database Mirroring...when the Witness server was added to the Mirror session, only the alter database T-SQL statement was executed on the Principal server.
ALTER DATABASE <db_name> SET WITNESS = 'TCP://<servername>:<port>'
After executing the above statement, a few seconds later the state between Principal and Witness Connection changed to Connected and the state between Mirror and Witness Connection remains Disconnected.
The Mirror session is not using Certificates, every server is on the same domain, using the same domain login account, and all servers have SP2 installed running Enterprise Edition.
Any idea's why the state between Mirror and Witness Connection remains Disconnected?
Thanks,
↧
↧
SQL Server Agent fails to connect to DB after enabling mirror on failover cluster
Hello:
We have multiple databases running in a Failover Cluster instance: SQL 2012SP1 on Server 2008 R2 failover cluster (NOT AlwaysOn). We are trying to add a high-performance mirror in a standalone instance for DR. My understanding is that should be a perfectly normal, supported configuration.
The mirroring is working properly; however, the clustered SQL Server agent is unable to run jobs that run in the mirrored databases.
We get the following in the job log: Unable to connect to SQL Server 'VIRTUALSERVERNAME\INSTANCE'. The step failed.
There is a partner message in the agent log: [165] ODBC Error: 0, Connecting to a mirrored SQL Server instance using the MultiSubnetFailover connection option is not supported. [SQLSTATE IMH01]
The cluster is not a mulitsubnet cluster. All hosts are connected to the same subnets and there is no storage replication. I can not find any place where I can adjust the connect string options for SQL Agent.
Any guidance or suggestions on how to resolve this would be appreciated.
~joe
↧
Problem in Mirroring
Hi,
I have a problem with database mirroring. there are two servers one PrimaryServer1, and FailoverSever1. I am able to configure the mirroring scuccessfully.
there is one table(UsersInfo) with some data. while application is running this table being updated. I am able to see the updations in that table, suddenly I observed the updated data is vanisished, after some time I found that the Failoverserver1 system date time is more than 12 hours, compare to PrimaryServer1.
here I have two questions
1. Because of date issue, that data is vanished?
2. After removeing the Mirroring also, I am able to see the same behaviour in PrimaryServer1.
Still I am unable to identify the issue, can anybody the help me out to resolve this issue.
Environment - Windows Server 2008 and Sql Server 2008 R2.
Thanks
Sai
I have a problem with database mirroring. there are two servers one PrimaryServer1, and FailoverSever1. I am able to configure the mirroring scuccessfully.
there is one table(UsersInfo) with some data. while application is running this table being updated. I am able to see the updations in that table, suddenly I observed the updated data is vanisished, after some time I found that the Failoverserver1 system date time is more than 12 hours, compare to PrimaryServer1.
here I have two questions
1. Because of date issue, that data is vanished?
2. After removeing the Mirroring also, I am able to see the same behaviour in PrimaryServer1.
Still I am unable to identify the issue, can anybody the help me out to resolve this issue.
Environment - Windows Server 2008 and Sql Server 2008 R2.
Thanks
Sai
Sai
↧
unable to start mirroring due to 1418 Errror!
Hi all,
while starting mirroring getting error " TCp/ip does not exist "
The server network address "TCP://C0046739.itcs.hp.com:5022" can not be reached or does not exist. Check the network address name and that the ports for the local and remote endpoints are operational
1.TELNET ServerName 5022
2.firewall is turned off.
3. en poinst are started
4. endpoints dropped and recrted
eventhogh getting same error . pls help me...
Thanks in advance..
↧