Install db using sapinst on sql cluster

I'm having an issue installing the ep6 db using sapinst on a sql cluster. sapinst wants to install to the localhost/default, but I need to specify the "virtual" sql cluster name.
Is there a workaround using sapinst, or is there some special way one needs to backup/restore onto the cluster from another machine..
any ideas?
jm

<snip>
Marty McCormick
Posts: 17
Registered: 2/25/04
Hi Gabor-
Although it's not supported, you can get EP6 SP2 to work with clustered SQL server 2000 on a virtual MSCS cluster. (We have it working here on Win2003)
The instructions were posted somewhere on this discussion board before, but here they are again:
1) Install SQL as a default local instance with the DB files on a clustered drive. Make sure to choose custom install and select Binary 850 collation.
2) Select a clustered drive for the SQL data files.
3) Install SQL SP3
4) Install SQL hotfix xxxx
5) Run instcoll.exe on the local instance to upgrade to 850 BIN2
6) Run SAPinst, choose ?Database? and allow the setup to create the databases PCD and WCM
7) Detach the databases (Right click on the DB in SQL Enterprise Manger and Detach)
8) Upgrade the local SQL instance to a clustered instance (Note: when running sql setup again, make sure there is no other default instance running on the other node or you will not have the upgrade option). You will have to give the SQL install an instance name at this point.
9) Re-install SQL SP3
10) Re-install hotfix xxx
11) Re-run instcoll.exe (Note: You will have to do this while SQL services are running. Instcoll will prompt you to stop them using the SQL Services Manager, follow the instructions Instcoll displays).
12) Attach the PCD and WCM databases.
13) Run SAPInst on your portal servers and point the install at the clustered SQL virtual server name / instance.
General comments:
There are 3 main considerations when installing EP6 with a clustered SQL backend:
1) You can only run SAPinst ? Database (creates PCD and WCM databases, SAPPCD and SAPWCM users) against a local non-named instance of SQL (SAPinst used the local SQL pipe to connect)
2) Instcoll.exe will NOT run against a SQL installation that has the two EP6 databases (PCD/WCM) attached, hence the need to detach them before running setup / instcoll.
3) Be very careful with collations. After the upgrade to cluster operation the collation will not be the same. If you attach the PCD and WCM databases to a SQL server running the wrong collation YOU WILL CORRUP THE DATABASES!
</snip>

Similar Messages

Not using MSDTC in SQL Cluster when using SSIS

I have an SSIS package that reads data from Oracle and inserts it into SQL Server.
The SQL Server is clustered (node1, node2) but it doesn't have MSDTC. The package runs fine without problems.
I have read that if you are using SSIS package then MSDTC is a must when configuring SQL Server cluster. But I am not using it and still package is working fine so I wanted to ask what's the use of MSDTC? How is my package working without it?

Please refer below link and determine if you need it. If you are using distributed transaction in SSIS package you will require it.
Do i need to configure MSDTC
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers
My TechNet Wiki Articles

SCOM 2012 Reporting Components with a shared SQL cluster

Hi, we are planning to install SCOM 2012 but i am a bit confused around the reporting components.
We have a shared SQL Enterprise cluster with multiple instances which we would like to use for our OperationsMananger and OperationsManagerDW databases. However after trying a test SCOM deployment, installing the SCOM reporting components on a VM requires
a local running copy of SQL reporting services.
Is this true? It seems ludicrous to have to purchase an additional license of SQL just to run the reporting components of SCOM. We have spent a lot of money on our SQL cluster and we would like to use it. We dont want to install the SCOM reporting components
on the shared SQL cluster.
If this is true, can you tell me which license of SQL we require? Just to run SQL reporting services on a VM should just require a standard SQL license, right?
Also if we have to purchase a SQL license for this standalone VM, would you recommend having the OperationsManagerDW database on the shared SQL cluster or on the VM where the standalone instance of SQL reporting services resides.
Surely this is something that other people have an issue with? I would have thought most people would want to use a shared SQL cluster. Any help is much appreciated.

Just to add that SQL Reporting Services isn't cluster aware so the best you could do is to install stand-alone onto a node of the cluster.
To reinforce what Scott is saying, see this screenshot of the install of SCOM reporting:
http://www.systemcentersolutions.co.uk/images/easyblog_images/42/scom/CTP2/Install/SQRS9.png
Technically you can install SCOM reporting on a shared SQL Server Reporting Services instance but as Scott (and the screenshot) state - it will overwrite any existing security settings on existing reports.
Scott is also correct that SQL Server Standard Edition is included as part of the licensing cost of System Center 2012 as long as the SQL instance only runs components of System Center.
cheers
Graham
Regards Graham New System Center 2012 Blog! -
http://www.systemcentersolutions.co.uk
View OpsMgr tips and tricks at
http://systemcentersolutions.wordpress.com/
I have one SQL 2012 Server with a few instances. 1 for Scom, 1 for SCCM and 1 for Service Manager. The instance shows up as blank for reporting services on the SCOM. Do I have to install SQL on the SCOM box also? Why Can't
it see the instance on my 2012 SQL box? It is in a different instance than SCCM.

Can a SQL Cluster have many Master Secret \ SSO systems?

We are trying to build a BizTalk environment that will offer multiple BizTalk instances off one SQL cluster.
Our SQL cluster consists of 2 servers configured in an ACTIV\ACTIVE configuration and reads data from a SAN.
We have to set up 6 BizTalk instances to create 6 environments for UAT, Support, DR, etc. These BizTalk groups will contain 2 BizTalk servers each. Each instance will have a group of service accounts assigned to it ino order to separate the environments
but will still use the same SQL cluster.
We have named cluster resources for each UAT, Support, etc for the SAN so that the databses are written and read from mounted disks.
My question and confusion surrounds SSO and the clustering of the Master Secret for multiple instances.
I want to cluster the Master Secret on the existing SQL cluster as the documentation states, but I am not sure if this is correct when there are multiple BizTalk instances running off the the same SQL cluster. The nodes of the SQL cluster will have
the SSO service installed and so too will the BizTalk servers in each instance group - UAT, Support, etc. So, would this mean there is only one master secret being used for all BizTalk instances, which I feel is wrong?
Or should the master secret just exist on a bizTalk server without HA?
I want HA but not sure where the SSO and master secret should go and ensure there are no dependencies from the other BizTalk instances should the SSO service need restarting on the SQL cluster.
I have not implemented multiple instances on the same SQL cluster before so this is new and confusing. The microsoft documentation isn't too great either.
Any help and guidance would be greatly appreciated.

post Windows Server 2008 you can have multiple MS DTC instances on one cluster. So unlike previous versions (w2k3) where the recommendation was to add MSDTC to the base cluster group, you can now have one instance of MSDTC cluster resource per resource group.
In short yes if you feel that MSDTC is becoming a bottleneck in your processing. Also it would be preferred that for each of your BizTalk Environments you create at least ONE MSDTC resource per environment.
Regards.

Install SharePoint 2013 database on SQL server 2012 SP1 cluster

Good Day all,
We are trying to install SharePoint 2013 database on a SQL server 2012 Enterprise with SP1 cluster (configured for mixed mode) but the connection is not working (times out). We can telent the SQL cluster network name on port 1433 and we made
a UDL connection file, test the connection via windows authentication and it is working, but if we use the sql authentication it is not working.
Also we have two SharePoint 2013 servers connected via NLB.
Any idea about this issue guys?

event if 3355 means 3 things:
The SQL Server might be offline.
The SharePoint Foundation database access account might not have the necessary permissions to communicate with the SQL Server.
A firewall that runs on either the local server or on SQL Server might be blocking network communications.
Big question, how you trying to connect SQL windows or sql authentication? is it throwing error on Config wizard or somewhere else?
Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

Install SQL Cluster

Hi all,
Kindly what is the step by step procedue to install sql server 2012 sp1 cluster to host sharepoint 2013 databases? Knowing that the sharepoint 2013 servers (two servers) and the sql servers (two) in different zones (there is a firewall between them)
Regards,

i assume you want to Install SQL Cluster for High Availability group, please follow the link below, walk through the all steps from failover cluster to SQL Installation to configure the high Availability group.
Configure SQL Server 2012 AlwaysOn Availability Groups for SharePoint 2013
One thing make sure, you punch the hole in firewall for all the ports you used on the SQL server so that sharepoint can communicate to sql server.
Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

Siebel 8.1.1 Install error using MS SQL Server 08

Hi,
I am trying to set up a Siebel Proto environment on WinXP system. The database that I am using is MS SQL Server 2008 with SP1 installed.
After installing Siebel at the Database Install step, I encountered a failure on step 'Import Repository Data' The error log generated is as follows:
2010-04-03 18:47:45     C:\sba81\siebsrvr\bin\repimexp.exe /a I /G ENU /u SADMIN /p ***** /c SBA_81_DSN /d dbo /r "Siebel Repository" /f C:\sba81\dbsrvr\common\mstrep.dat /l C:\sba81\siebsrvr\log\install\output/imprep_prim.log
2010-04-03 18:47:45
2010-04-03 18:47:45     Connecting to the database...
2010-04-03 18:47:46     Connected.
2010-04-03 18:47:46     Starting common api.
2010-04-03 18:47:46     SQLstyle is 'Microsoft SQL Server'
2010-04-03 18:47:46     SARM is OFF -change param SARMLevel to enable
2010-04-03 18:47:46     SARM Client is OFF -change param SARMClientLevel to enable
2010-04-03 18:47:46     SARM is OFF -change param SARMLevel to enable
2010-04-03 18:47:46     SARM Client is OFF -change param SARMClientLevel to enable
2010-04-03 18:47:46     SARM is OFF -change param SARMLevel to enable
2010-04-03 18:47:46     SARM Client is OFF -change param SARMClientLevel to enable
2010-04-03 18:47:47     Unable to verify login name SADMIN.
2010-04-03 18:47:47     Unable to start common api.
2010-04-03 18:47:47     Unable to start common api.
2010-04-03 18:47:47     Error in initiate function..
2010-04-03 18:47:47     Elapsed time: 2 sec.
2010-04-03 18:47:47     (logapi.cpp (184) err=1 sys=0) SBL-GEN-00001: (logapi.cpp: 184) error code = 1, system error = 0, msg1 = (null), msg2 = (null), msg3 = (null), msg4 = (null)
I am using SADMIN user for Database account and SIEBEL user for Table owner. I have also tried using SIEBEL user in both places.
Basically what is SARM? And how can I enable it?
I have tried connecting to the DB from the Server system and am successful in that.
Thanks for the help in advance.
With Regards,
Tanmay Jain

Hi EvtLoglvl,
I am able to connect to the SQL Server using the ODBC connections and also SADMIN id has requisite SSE_ROLE granted to it and the default DB for it is SIEBEL_DB on which I am attempting installation. I was able to successfully run the grantuser.sql file that Siebel provides by default to create the roles and logins for SIEBEL, SADMIN and LDAPUSR.
The problem I am encountering is when I try to perform the Database Server configuration. The system creates the required tables and indexes successfully on the DB. The problem is coming when it tries to Import the base repository that Siebel Server Installation comes with. The error log was for the same.
I feel that the Siebel Installer is missing some APIs to connect to SQL Server 08.
The SQL Server is hosted on a system with x64 architecture and the Siebel Server is on a x86 architecture system. I also have Service Pack 1 installed on both the DB Server and Siebel Server. Using third party tools I am able to manipulate the database without any hitches from the Siebel Server system.
Latest, I have tried reinstalling the virtual environment completely, i.e. started from scratch and had the same issue when I tried the Siebel Database Server installation step. I sure hope I dont have to install SQL 05 and install Siebel Database on it and then do an upgrade of the database.
Thanks for the info about SARM. It still shows up in the Log file and after it the install fails though.
Thanks and Regards,
Tanmay Jain

Can DB look up option set up using SQL cluster

Could you please confirm, if the DB look up feature in ICM can be set up using SQL cluster.
If, yes, could you please confirm, if this right configuration.
Registry : \\CORPVCLUCSQL899\MSSQLP899\ETN_ICMContactLookup=(ETNICMLookup,l000kOnly)
ICM configuration\Database look up explorer :
\\MSSQLP899\DEBN_3701
SQL Cluster server name : CORPVCLUCSQL899
Instance name : MSSQLP899
Table name :
DEBN_3701

I tried various combination of updating the path. But still getting same error. Please find below log of DB worker. Yes, we are aware that it supports only minimal feture.
17:15:55:093 ra-dbw Add of ScriptTable complete. externaldb (5000).
17:15:55:093 ra-dbw Trace: Invalid pathname for externaldb: \\CORPVCLUCSQL899\MSSQLP899\DEBN_3701
17:15:55:094 ra-dbw Trace: Handling delete for ScriptTable 5000 (ScriptTableInfo::QueueUpdate (BadPath))
17:15:55:094 ra-dbw Trace: Action=4 type=0 count=0
17:15:55:094 ra-dbw Trace: Action=1 type=127 count=1
17:15:55:094 ra-dbw Trace: Action=5 type=0 count=0
17:15:55:094 ra-dbw Trace: Transaction complete.
17:15:55:094 ra-dbw Add of ScriptTableColumn complete. ID 5000.
17:15:55:094 ra-dbw Trace: Invalid pathname for externaldb: \\CORPVCLUCSQL899\MSSQLP899\DEBN_3701
17:15:55:094 ra-dbw Trace: ScriptTable externaldb (ID 5000) disconnected.
17:18:24:502 ra-dbw Trace: Action=4 type=0 count=0
17:18:24:504 ra-dbw Trace: Action=3 type=126 count=1
17:18:24:505 ra-dbw Trace: Action=5 type=0 count=0
17:18:24:506 ra-dbw Trace: Transaction complete.
17:18:24:506 ra-dbw Update of ScriptTable complete. externaldb (5000).
17:18:24:506 ra-dbw Trace: Invalid pathname for externaldb: \\MSSQLP899\DEBN_3701
17:18:24:506 ra-dbw Trace: Handling delete for ScriptTable 5000 (ScriptTableInfo::QueueUpdate (BadPath))
17:18:24:506 ra-dbw Trace: ScriptTable externaldb (ID 5000) disconnected.
17:34:21:436 ra-dbw Trace: Action=4 type=0 count=0
17:34:21:437 ra-dbw Trace: Action=3 type=126 count=1
17:34:21:437 ra-dbw Trace: Action=5 type=0 count=0
17:34:21:437 ra-dbw Trace: Transaction complete.
17:34:21:437 ra-dbw Update of ScriptTable complete. externaldb (5000).
17:34:21:438 ra-dbw Trace: Invalid pathname for externaldb: \\151.110.200.190\MSSQLP899\DEBN_3701
17:34:21:438 ra-dbw Trace: Handling delete for ScriptTable 5000 (ScriptTableInfo::QueueUpdate (BadPath))
17:34:21:438 ra-dbw Trace: ScriptTable externaldb (ID 5000) disconnected.
17:36:40:954 ra-dbw Unable to parse SQL login info string.
17:38:18:725 ra-dbw Unable to parse SQL login info string.
17:45:54:366 ra-dbw SQL login info updated.
17:46:55:926 ra-dbw Trace: Action=4 type=0 count=0
17:46:55:926 ra-dbw Trace: Action=3 type=126 count=1
17:46:55:927 ra-dbw Trace: Action=5 type=0 count=0
17:46:55:927 ra-dbw Trace: Transaction complete.
17:46:55:927 ra-dbw Update of ScriptTable complete. externaldb (5000).
17:46:55:928 ra-dbw Trace: Invalid pathname for externaldb: \\151.110.200.190\ETN_ICMContactLookup
17:46:55:928 ra-dbw Trace: Handling delete for ScriptTable 5000 (ScriptTableInfo::QueueUpdate (BadPath))
17:46:55:928 ra-dbw Trace: ScriptTable externaldb (ID 5000) disconnected.
18:02:54:302 ra-dbw SQL login info updated.
18:51:57:417 ra-dbw Trace: Action=4 type=0 count=0
18:51:57:417 ra-dbw Trace: Action=3 type=126 count=1
18:51:57:418 ra-dbw Trace: Action=5 type=0 count=0
18:51:57:418 ra-dbw Trace: Transaction complete.
18:51:57:419 ra-dbw Update of ScriptTable complete. externaldb (5000).
18:51:57:419 ra-dbw Trace: Invalid pathname for externaldb: \\ETN_ICMContactLookup\DEBN_3701
18:51:57:419 ra-dbw Trace: Handling delete for ScriptTable 5000 (ScriptTableInfo::QueueUpdate (BadPath))
18:51:57:420 ra-dbw Trace: ScriptTable externaldb (ID 5000) disconnected.
18:59:46:937 ra-dbw Trace: Action=4 type=0 count=0
18:59:46:937 ra-dbw Trace: Action=3 type=126 count=1
18:59:46:937 ra-dbw Trace: Action=5 type=0 count=0
18:59:46:938 ra-dbw Trace: Transaction complete.
18:59:46:938 ra-dbw Update of ScriptTable complete. externaldb (5000).
18:59:46:939 ra-dbw Trace: Invalid pathname for externaldb: \\ICMLOOKUP\ETN_ICMContactLookup\DEBN_3701
18:59:46:939 ra-dbw Trace: Handling delete for ScriptTable 5000 (ScriptTableInfo::QueueUpdate (BadPath))
18:59:46:939 ra-dbw Trace: ScriptTable externaldb (ID 5000) disconnected.
19:00:28:945 ra-dbw Trace: Action=4 type=0 count=0
19:00:28:945 ra-dbw Trace: Action=3 type=126 count=1
19:00:28:945 ra-dbw Trace: Action=5 type=0 count=0
19:00:28:946 ra-dbw Trace: Transaction complete.
19:00:28:946 ra-dbw Update of ScriptTable complete. externaldb (5000).
19:00:28:946 ra-dbw Trace: Invalid pathname for externaldb: \\ICMLOOKUP\ETN_ICMContactLookup
19:00:28:946 ra-dbw Trace: Handling delete for ScriptTable 5000 (ScriptTableInfo::QueueUpdate (BadPath))
19:00:28:947 ra-dbw Trace: ScriptTable externaldb (ID 5000) disconnected.

SQL cluster 2008 R2 migration to new Hardware in VM

Hi,
We have a task to migrate existing Physical SQL Cluster DB to new Hardware but in VM. (cannot argue with the client)
hence our plan is to install new Cluster in VM with same Windows and SQL version i.e Win 2K8 R2 ENT w/SP and SQL 2K8
R2 STD w/SP and use SQL mirroring option for the DB to migrate on the new Server (keeping the downtime to as low as possible and advantage of bringing the old server online in case of any issues..)
Below points are for a single instance, couple of DB to migrate:
Keep the physical production server running
In-Parallel build New SQL Cluster in VM (keep same version windows/sql)
Keep Same drive letter for Quorum, MSDTC, DATA, LOG & Backup
Keep the same Instance Name, SQL Network Name can be different (will be changed to old network name once the PROD is shutdown)
Check all logins windows and SQL to be same on both the clusters
Copy all the jobs, SSIS packages etc.. .create the location folder as per current server on the VM SQL Cluster
Perform full backup of old cluster company-db databases or use the existing latest backup (full, differential, transaction)
Restore databases in the new cluster with no recovery so additional log file or differential backup can be restored
Create SQL Mirroring for the Database and select the principal server (old cluster) and the mirror server (new VM cluster)
Choose mirroring without witness ( no auto failover as we don’t need the old server later)
Start the mirroring – (hopefully everything synchronized and working)
During the downtime –
Stop the application/ client connection – if possible
Failover the DB through Mirroring option
Once the mirrored server becomes Principal and data is accessible – stop the mirroring
Now the new VM SQL Cluster DB is online
Shutdown the old cluster company-db (Node1 & Node2)
Come back to VM SQL Cluster and change the Network name to the old server network name (so that client connections are not affected)
Check if the DNS entries are updated with correct name and IP address
Delete DNS entries for old company-db on DNS Servers if not deleted, delete the old server SQL network name in computer object
Stop SQL Resources on the new VM SQL Cluster (take it offline all the resources)
Bring online the SQL Resource and make sure the SQL resources are online and new network name is reachable
Wait till you see machine name company-db in active directly (AD) and DNS server will have entry for company-db
Verify connectivity for company-db from outside.
If things are not going as per the plan then shut down the new VM cluster
Revert back the DNS settings
Power up the Old SQL Server
The DB will show “restoring mode” – use command to make it online “RESTORE DATABASE (dbname) WITH RECOVERY”
Check the DB
Start using the OLD server again
Troubleshoot the failed scenario ;)
Need to know if the above steps are okay, and any consideration once the new VM SQL Cluster is online.
Kindly let me know if there anything else to transfer apart from the logins, jobs, folder location etc.. !!
Many Thanks

Hello,
Well if you don’t change the instance name (name = ABC) then its OK.
Try the following resources about transferring SQL Server logins:
http://support.microsoft.com/kb/918992/en-us
http://www.mssqltips.com/sqlservertip/2081/transfer-sql-server-jobs-task-and-transfer-sql-server-logins-task-in-ssis/
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Sharepoint 2010 farm Sql cluster

hello,
i have sharepoint farm with 3 server ( Web front , Sql , search server )
can i make sql cluster to sql with 3 sql server or it be must before begin install sharepoint farm
thanks
Nour

Your question isn't very clear but i think i understand.
You have an existing farm with a single SQL server.
You want to upgrade your single SQL server to a clustered SQL installation.
Doing so is not easy, you can't upgrade a single server SQL install to a clustered install as far as I know. You'd need to re-build the SQL server as a single node cluster and add the new servers to make the full cluster before moving the SharePoint databases
over.
In addition you'd need to use SQL Aliases to point to the new clustered SQL address. If you've already used them then that's great, if not you'd need to use the old, single server, address as the Alias address and point it to the cluster.
In short: You can do it later but it's quite tricky and best done before you install SharePoint.

SQL Cluster - Unable to obtain IP Address from System Center IP Pool

Hi everyone,
we are trying to deploy a SQL cluster into a windows azure pack tenant cloud.
Our azure pack environment contains:
- 4X Hyper-V server in a failover cluster
- 1X SCVMM server
- multiple WAP server
Steps we have done:
-   Windows failover cluster is installed and configured successfully
-   Quorum disk was configured successfully
-   SQL server 2014 installation (via static IP) is successfully. But routing between the VMs is not possible.
-   SQL server 2014 installation (via DHCP) fails at the end of the installation with following error:
       -> We used DHCP to obtain an IP from the scvmm IP pool.
(01) 2015-04-22 15:29:11 Slp: Running Action: cluster_ip_address_cluster_config_Cpu64
(01) 2015-04-22 15:29:11 Slp: Action Data:
(01) 2015-04-22 15:29:11 Slp:   Feature = SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64
(01) 2015-04-22 15:29:11 Slp:   Scenario = install
(01) 2015-04-22 15:29:11 Slp:   Timing = ConfigNonRC
(01) 2015-04-22 15:29:11 Slp:   ConfigObjectType = Microsoft.SqlServer.Configuration.ClusterConfiguration.ClusterIPAddressPrivateConfigObject
(01) 2015-04-22 15:29:11 Slp:   FeatureName = SQL_Engine_Core_Inst
(01) 2015-04-22 15:29:11 Slp:   FeatureCpuType = Cpu64
(01) 2015-04-22 15:29:11 Slp:   FeaturePackageId = sql_engine_core_inst
(01) 2015-04-22 15:29:11 Slp:   FeatureClusterState = CompleteFailoverCluster
(01) 2015-04-22 15:29:11 Slp: Creating IPv4 address 'SQL IP Address 1 (SQLADFS)'.
(01) 2015-04-22 15:29:11 Slp: Creating cluster resource 'SQL IP Address 1 (SQLADFS)' of type 'IP Address' in group 'SQL Server (ADFS)'
(01) 2015-04-22 15:29:11 Slp: Bringing IP address resource 'Type='IP Address' NetworkName='Cluster Network 1' Group='SQL Server (ADFS)' Resource='SQL IP Address 1 (SQLADFS)'' online
(01) 2015-04-22 15:29:11 Slp: Bringing cluster resource 'SQL IP Address 1 (SQLADFS)' online
(01) 2015-04-22 15:29:12 Slp: Prompting user if they want to retry this action due to the following failure:
(01) 2015-04-22 15:29:12 Slp: ----------------------------------------
(01) 2015-04-22 15:29:12 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
(01) 2015-04-22 15:29:12 Slp: Inner exceptions are being indented
(01) 2015-04-22 15:29:12 Slp:
(01) 2015-04-22 15:29:12 Slp: Exception type: Microsoft.SqlServer.Configuration.Cluster.ResourceOnlineException
(01) 2015-04-22 15:29:12 Slp:     Message:
(01) 2015-04-22 15:29:12 Slp:         The cluster resource 'SQL IP Address 1 (SQLADFS)' could not be brought online. Error: There was a failure to call cluster code from a provider. Exception message: Generic failure
. Status code: 5023. Description: The group or resource is not in the correct state to perform the requested operation.
(01) 2015-04-22 15:29:12 Slp:         .
(01) 2015-04-22 15:29:12 Slp:     HResult : 0x86d8003a
(01) 2015-04-22 15:29:12 Slp:         FacilityCode : 1752 (6d8)
(01) 2015-04-22 15:29:12 Slp:         ErrorCode : 58 (003a)
(01) 2015-04-22 15:29:12 Slp:     Data:
(01) 2015-04-22 15:29:12 Slp:       resourceName = SQL IP Address 1 (SQLADFS)
(01) 2015-04-22 15:29:12 Slp:       errorMessage = There was a failure to call cluster code from a provider. Exception message: Generic failure . Status code: 5023. Description: The group or resource is not in the correct state
to perform the requested operation.
(01) 2015-04-22 15:29:12 Slp:       WatsonData = Microsoft.SqlServer.Configuration.Cluster.ResourceOnlineException@58
(01) 2015-04-22 15:29:12 Slp:       DisableRetry = true
(01) 2015-04-22 15:29:12 Slp:     Inner exception type: Microsoft.SqlServer.Configuration.Cluster.ClusterProviderDetailedException
(01) 2015-04-22 15:29:12 Slp:         Message:
(01) 2015-04-22 15:29:12 Slp:                 There was a failure to call cluster code from a provider. Exception message: Generic failure . Status code: 5023. Description: The
group or resource is not in the correct state to perform the requested operation.
(01) 2015-04-22 15:29:12 Slp:                 .
(01) 2015-04-22 15:29:12 Slp:         HResult : 0x86d70002
(01) 2015-04-22 15:29:12 Slp:                 FacilityCode : 1751 (6d7)
(01) 2015-04-22 15:29:12 Slp:                 ErrorCode : 2 (0002)
(01) 2015-04-22 15:29:12 Slp:         Data:
(01) 2015-04-22 15:29:12 Slp:           ExceptionMessage = Generic failure
(01) 2015-04-22 15:29:12 Slp:           StatusCode = 5023
(01) 2015-04-22 15:29:12 Slp:           Description = The group or resource is not in the correct state to perform the requested operation.
(01) 2015-04-22 15:29:12 Slp:           WatsonData = Microsoft.SqlServer.Configuration.Cluster.ClusterProviderDetailedException@2
(01) 2015-04-22 15:29:12 Slp:         Stack:
(01) 2015-04-22 15:29:12 Slp:                 at Microsoft.SqlServer.Configuration.Cluster.WmiClusterResource.Online(Int32 timeout)
(01) 2015-04-22 15:29:12 Slp:                 at Microsoft.SqlServer.Configuration.Cluster.ClusterResource.Online(Int32 timeout)
(01) 2015-04-22 15:29:12 Slp:         Inner exception type: System.Management.ManagementException
(01) 2015-04-22 15:29:12 Slp:             Message:
(01) 2015-04-22 15:29:12 Slp:                         Generic failure
(01) 2015-04-22 15:29:12 Slp:             HResult : 0x80131501
(01) 2015-04-22 15:29:12 Slp:             Data:
(01) 2015-04-22 15:29:12 Slp:               WmiErrorCode = Failed
(01) 2015-04-22 15:29:12 Slp:               WatsonData = Failed@5023
(01) 2015-04-22 15:29:12 Slp:               Description = The group or resource is not in the correct state to perform the requested operation.
(01) 2015-04-22 15:29:12 Slp:               ErrorType = 1
(01) 2015-04-22 15:29:12 Slp:               Operation = ExecMethod
(01) 2015-04-22 15:29:12 Slp:               ParameterInfo = MSCluster_Resource.Name="SQL IP Address 1 (SQLADFS)"
(01) 2015-04-22 15:29:12 Slp:               ProviderName = WinMgmt
(01) 2015-04-22 15:29:12 Slp:               StatusCode = 5023
(01) 2015-04-22 15:29:12 Slp:             Stack:
(01) 2015-04-22 15:29:12 Slp:                         at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
(01) 2015-04-22 15:29:12 Slp:                         at System.Management.ManagementObject.InvokeMethod(String methodName, ManagementBaseObject
inParameters, InvokeMethodOptions options)
(01) 2015-04-22 15:29:12 Slp:                         at Microsoft.SqlServer.Configuration.WMIInterop.Resource.BringOnline(UInt32 TimeOut)
(01) 2015-04-22 15:29:12 Slp:                         at Microsoft.SqlServer.Configuration.Cluster.WmiClusterResource.Online(Int32 timeout)
(01) 2015-04-22 15:29:12 Slp: ----------------------------------------
We have tried to reinstall the servers multiple times, without result.
Can anyone assist us in this case?
Thanks
Kind Regards
Julian

Hi Darryl,
thanks for your supply.
We don't have an DHCP in the Cloud. System Center DHCP is used for assigning IP addresses and routing inforamtion to the vms.
This works fine for assigning IP addresses to the vms.
At my current point of understanding network virtualisation with system Center, we do not have an alternative to this way of assigning IP addresses.
Kind Regards
Julian

SQL cluster name on a Windows Failover Cluster

Hello,
I am installing a SQL cluster (first timer) using Windows server and SQL (both 2008 R2)
Windows failover cluster is setup and functioning. I am now installing the SQL failover cluster part.
Question: What should be the "SQL server network name", should it be the same as my Windows cluster name or different name ?
Thanks for your help,
Luca

It should be different, this is known as the virtual SQL Server name in earlier versions of SQL Server failover clusters.
SQL Server Network Name —
Specify a network name for the new SQL Server failover cluster. This is the name that is used to identify your failover cluster on the network.
https://msdn.microsoft.com/en-us/library/ms179530.aspx?f=255&MSPPError=-2147217396
This will be the name used to identify your cluster on the network. This is the name that will be available on the
network for the clients to connect SQL instance.
http://www.mssqltips.com/sqlservertip/1709/install-sql-server-2008-on-a-windows-server-2008-cluster-part-3/

Disk and tempdb configuration for multiple Instances in one SQL cluster

Hi Everyone ,
I am in planing to build SQL Cluster on Blade server . Two blades are allocated for SQL. and planning to cluster those two blades. It will be windows 2012R2 and SQL 2012/2014. Initially it was plan to put most of database on one SQL instance. but
due to other requirements I will be Installing more SQL Instance on same cluster.
for now Everything will be on RAID 10 but do not have more details about storage yet that how it will get configured
256 GB Ram on Each blade server.
1) what are the Disc configuration recommendation for data and log files when each instance get added?
2) what are the Disc configuration recommendation for tempdb files when each instance get added?
3) Each Instance Tempdb file on Same drive is good practice?
Any other Best practices should follow for this setup?
Thank you ....
Please Mark As Answer if it is helpful. \\Aim To Inspire Rather to Teach A.Shah

1) what are the Disc configuration recommendation for data and log files when each instance get added?
Keep both the sql instances in diffèrent drives.read the below link for RAID levels and according to your usage you can cofigure it..
http://technet.microsoft.com/en-us/library/ms190764%28v=sql.105%29.aspx
Storage best practice.
http://technet.microsoft.com/en-us/library/cc966534.aspx
2) what are the Disc configuration recommendation for tempdb files when each instance get added?
Its good to have sepreate drive for tempdb and each instance too with correct allocation or configuration..RAID5
for data if you must, but have to keep a spare drive around for that.
Best is 10 everywhere. If that's too expensive, then 1 or 10 for log and 5 for data (and 10 for TempDB)
RAID 5 is terrible for logs because it has a high write overhead. Tran logs are write-heavy, not read-heavy.
3) Each Instance Tempdb file on Same drive is good practice?
Tempdb configuration is depends, its completelty based on your server and tempdb usage..Make sure to have equal size for all the files in tempdb, As a general rule, if the number of logical processors is less than 8, use the same number of data files
as logical processors. If the number of logical processors is greater than 8, use 8 data files and then if contention continues, increase the number of data files by multiples of 4 (up to the number of logical processors) until the contention is reduced to
acceptable levels or make changes to the workload/code.
http://www.confio.com/logicalread/sql-server-tempdb-best-practices-initial-sizing-w01/#.U7SStvFBr2k
http://msdn.microsoft.com/en-us/library/ms175527(v=sql.105).aspx
http://www.sqlskills.com/BLOGS/PAUL/post/A-SQL-Server-DBA-myth-a-day-(1230)-tempdb-should-always-have-one-data-file-per-processor-core.aspx
Raju Rasagounder Sr MSSQL DBA

Installing Application Server JAVA on SQL 2005

We are looking to install a NW 7.0 system with Application Server Java only. We would like to install the SCS and the Central Instance on one host on a Windows 2008 64-bit server and the Database Instance on a seperate host. The DB host is a Windows 2008 32-bit server and has MSSQL 2005 installed on it.
We are new to MSSQL with SAP and have a couple questions:
1) Is the scenario I described above possible? Looking at the PAM it looks like we need to have Windows 2008 on a 64-bit platform in order for SQL 2005 to work.
2) For installing the database instance, do you have to use sapinst on the DB host and install the database instance? If so, how do you connect the SCS to the DB? Or can you use the sapinst where the SCS was installed and link to the DB host?
Thanks and any help would be great.
Dale Dingmann

Hi Dale
If you're installing this to work as a Clustered system, I think you want to have the 2 servers (DB & CI) the same.
Ken

How to migrate SQL Cluster into Virtual SQL server or Virtual SQL Cluster

Hello All,
Currently we will be attempting to migrate a SQL cluster of (2 systems) into are virtual enviroment. We have been tracking the system requirements with Vmware Consolidation Tool and IO Meter to make sure our hosts have enough resources to accomidate this. All the metrics coming back looks like it will run just fine virtulized as the cluster was just for failover purposes anyhow and not for performance purproses. With that said a few questions have come up.
1.) What is the best way to virtulize this or to convert it (P2V)
- Should we just create a new Virtual Machine and install the same version of SQL and do a manual migration to the new SQL server and leave it as 1 SQL server with HA
- Or is there a way to P2V this kind of a setup ? if so what are the steps involved?
2.) If a P2V is possible I was under the impression that you will have to use a RAW mapping for the hard disks otherwise the cluster will not work ? Can anyone speak to this? as I'm pretty sure I have clustered windows server 2008 without RAW mapping before but not with SQL

Another quick question. The Vmware SQL Clustering KB article says:
vSphere MSCS Setup Limitations
Before you set up MSCS, review the list of functionality that is not supported for this release, and any
requirements and recommendations that apply to your configuration.
The following environments and functionality are not supported for MSCS setups with this release of vSphere:
n Clustering on iSCSI, FCoE, and NFS disks.
n Mixed environments, such as configurations where one cluster node is running a different version of ESX/
ESXi than another cluster node.
n Use of MSCS in conjunction with VMware Fault Tolerance.
n Migration with VMotion of clustered virtual machines.
n N-Port ID Virtualization (NPIV)
n With native multipathing (NMP), clustering is not supported when the path policy is set to round robin.
n You must use hardware version 7 with ESX/ESXi 4.0.
Can you not do clustering if your shared storage is iSCSI ? or can you not do RAW mapping with it to create the cluster ?

Install db using sapinst on sql cluster

Similar Messages

Maybe you are looking for