Issue: ASM cannot connect to the SQL server on an application server
Certain requirements must be met before ASM can connect to a SQL application.
Workaround:
•
Ensure that a supported version of SQL Server is installed. ASM does not support any developer editions
of SQL Server. ASM supports SQL Server 2000 (SP4 or greater), SQL Server 2005 (SP2 or greater), and
SQL Server 2008.
•
Ensure that SQL-DMO is installed. SQL-DMO is installed by default with most editions of SQL Server 2000
and SQL Server 2005. SQL-DMO is not installed by default on SQL Server 2008. See issue 1000856963
in this document for more details.
•
Ensure that you have appropriate credentials configured on your SQL Server. The SQL user must have the
ability to log in locally to the application server and have 'dbadmin' privileges on the SQL Server you are
connecting to. Log into your SQL Server with this user account if you continue to have issues. See the ASM
Help topic
Configure Application Credentials
for more information on connecting to a SQL Server through
ASM.
Issue: Application credential error appears while running the Host a SQL Server Database Wizard
When attempting to host a SQL Server 2008 database using the Host a SQL Server Database Wizard, an
application credential error message may appear. This error might appear because SQL Distributed
Management Objects (SQL-DMO) is not installed with SQL Server 2008 by default.
Workaround: Before attempting the following workaround, check to make sure that you have properly entered
your SQL Server 2008 credentials. If your credentials are correct and the error message still appears, install
SQL-DMO.
To install SQL-DMO, run the SQL Server 2005 Backwards Compatibility installer:
1.
On the SQL Server 2008 Installation Media, navigate to the \x64\Setup\x64\ folder on 64–bit applic-
ation servers and \x86\Setup\x86\ on 32–bit application servers.
2.
Double-click
SQLServer2005_BC.msi
.
3.
Follow the on-screen instructions.
After installing SQL-DMO, run the Host a SQL Server Database Wizard again. The wizard will complete
without error.
Issue: ASM attempts to create non-existent storage during discovery
If you use a non-ASM tool (such as the Array Configuration Utility, for example) to modify storage settings,
you must allow ASM time to recognize those new settings during the discovery process. If you attempt to
perform storage operations before the discovery process is complete, ASM will erroneously attempt to perform
storage operations such as growing non-existent logical disks.
Workaround: When modifying storage settings outside of ASM, allow enough time for the ASM discovery
process to recognize those new storage settings before performing any other ASM operations.
Issue: When attempting to provision storage on ASM, an error message appears
When attempting to provision storage, an error message indicating that “no storage could be found or created
to satisfy the request” may be issued. This error can appear when attempting to provision storage across
multiple disk types.
Workaround: Virtual arrays that span multiple disk types cannot be created. When provisioning storage, the
maximum amount of space you can allocate is limited by the largest amount of space available for a single
disk type. You cannot completely utilize the space on all of the disks if the disks are of different types.
HP StorageWorks Automated Storage Manager
7
Содержание X1600 - StorageWorks Network Storage System 5.4TB SAS Model NAS Server
Страница 2: ......
