When creating a new SQL Server PI repository database, a message similar to the following appears (the X represents the size of the model database in the SQL Server instance)
Failed to enable SQL PI monitoring extension.
Suggestions:
Please retry If the issue still occurs, please contact Quest Software technical support.
Failed to enable SQL PI monitoring extension for SQL Agent AGENTNAME.
Failed to create SPI repository database. Error: The CREATE DATABASE statement failed. The primary file must be at least X MB to accommodate a copy of the model database.
Cannot create a new PI database which is the same size as the model database.
In the system environment, the size of the model database used as the template is 1024 MB. When creating the new PI database, the sizing the installer uses is smaller than 1024. As a result, the database cannot be created.
The size currently hard coded in the SQL to create the PI database is 8192 KB.
WORKAROUND
For SQL Server agents
1. Create a database for the SQL Server PI repository
2. Run the attached script install_schema_mssql.sql in the new database to create the schema
3. Run the following SQL to create a filegroup for 1m data
USE [master]
GO
ALTER DATABASE [Database Name] ADD FILEGROUP [REPO_1M_FG]
GO
ALTER DATABASE [Database Name] ADD FILE ( NAME = N'1mData', FILENAME = N'[Driver 1]:\[1 minute Filegroup directory]\1mData.mdf' , SIZE = 8192KB , FILEGROWTH = 65536KB ) TO FILEGROUP [REPO_1M_FG]
GO
4. Run the attached script pass_wait_event_dim.sql in the new database to initialize the wait event categories
5. Run the following SQL statement in the new database to initialize the PI configuration record
insert into pa_repository values(current_timestamp, '20181203-1904', '4.7.0-5-1', '1.10', 0)
For Oracle agents
1. Create a database for the SQL Server PI repository
2. Run the attached script build_oracle_schema_mssql.sql in the new database to create the schema
3. Run the following SQL to create a filegroup for 1m data
USE [master]
GO
ALTER DATABASE [Database Name] ADD FILEGROUP [REPO_1M_FG]
GO
ALTER DATABASE [Database Name] ADD FILE ( NAME = N'1mData', FILENAME = N'[Driver 1]:\[1 minute Filegroup directory]\1mData.mdf' , SIZE = 8192KB , FILEGROWTH = 65536KB ) TO FILEGROUP [REPO_1M_FG]
GO
4. Run the following SQL statement in the new database to initialize the PI configuration record
insert into pa_repository values(current_timestamp, '20181203-1904', '4.7.0-5-1', '1.10', 0)
For SSAS agents
1. Create a database for the SQL Server PI repository
2. Run the attached script build_ssas_schema_mssql.sql in the new database to create the schema
3. Run the following SQL to create a filegroup for 1m data
USE [master]
GO
ALTER DATABASE [Database Name] ADD FILEGROUP [REPO_1M_FG]
GO
ALTER DATABASE [Database Name] ADD FILE ( NAME = N'1mData', FILENAME = N'[Driver 1]:\[1 minute Filegroup directory]\1mData.mdf' , SIZE = 8192KB , FILEGROWTH = 65536KB ) TO FILEGROUP [REPO_1M_FG]
GO
4. Run the attached script pass_wait_event_dim.sql in the new database to initialize the wait event categories
5. Run the following SQL statement in the new database to initialize the PI configuration record
insert into pa_repository values(current_timestamp, '20181203-1904', '4.7.0-5-1', '1.10', 0)
STATUS
This issue has been logged as FOM-231 and have been fixed in the 5.9.7.10 and higher versions of the SQL Server and Oracle database cartridges.
© ALL RIGHTS RESERVED. Feedback 利用規約 プライバシー Cookie Preference Center