Errors in the high-level relational engine

I'm getting an error when processing a partition - Errors in the high-level relational engine. The table_name table that is required for a join cannot be reached based on the relationships in the data source view.

This table is actually joined to another dimension table, which is then joined to the fact table.

How can I resolve this error?

I did notice that there are no keys in the dimension table that relate to the fact table for this particular table. Is this a data issue?|||Well, that might be the reason... To be honest I can't imagine a business case where you have a dimension table without any link to a fact table... Perhaps you can help me to understand you issue...|||

Usually I find that missing dimension key issue when there is corruption in the data. My underlying view was actually pointed to the wrong database - I corrected that but surprisingly it still didn't fix the problem.

Interestingly enough, the previous AS 2000 database used the 'name' column as a key for some of the dimensions. In AS 2000 this was acceptable as long as they were unique. AS 2005 doesn't like that so much. So I went through each dimension & changed it's key column to the proper key.

I am still troubleshooting for some other dimensions. I think it has something to do with the datatype being bigint instead of double in a dimension key. I am finding this to be a very tedious and time-consuming process.

If there's any way of visuallizing the two queries side-by-side to compare dimension/fact table keys that may help me.

Also, are there any resources on how to best hook up a dimension that has a related dimension but no fact table key. (eg Dimension Group links to Dimension links to Fact)?

|||

Andrew,

you can define a snowflake schema (Dimension Group links to Dimension links to Fact). You simply define more than one table in your dimension...

I think SSAS 2005 is more restrictive when it comes to keys. And yes, I think it's good. It takes some time to get used to it but a good design helps you much in this case... And having a name as a key is everything but best practice...

Having a double as a key is also not best practice... It's much better to have int/bigint at this point...

You can also switch on the build-in "unknown member" support... It's much better to do that on your own in the ETL process but i.e. if you set your cube directly on top of a productive system it might be helpful...

|||

Good tips. thanks! I am just trying to get it processing successfully, so the double/bigint switch will be something to try afterwards. The dimension/fact table key data should line up and there is a big problem when every record has unknown dimension members.

Let's hope that processing 21m rows in the dimension today is faster than yesterday.

Errors in High Level Relational and OLAP Storage Engine

Hi Edward,

I have tried to go to the Partition tab of BI Development Studio. When i click the partition tab of the Development Studio, it discards an error that " An error prevented the view from loading".

Could you please outline me the steps of how to go about this.

I am really stack.

Ronald

Please, could someone bail me out on this.

Ronald

|||

Looks to me something gone wrong with your project. It is also possbile BI Dev Studio installation got corrupted.

I would suggest:

First, try re-create your cube. See if you can create more partitions for you cube and BI Dev Studio allows you to add new partitions.

Second. If you still getting an error trying to navigate to the partitions tab, try re-installing SQL Server on your machine.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||I also found this error last week. My data source is ORACLE database. This raised when I used "OracleClient Data Provider" for provider in Data Source. When I changed the provider to "Native OLEDB\Oracle Provider for OLE DB", this problem was solved.

Hopefully, this post can help you.

Ashari Imamuddin

Errors in High Level Relational and OLAP Storage Engine

Hi Edward,

I have tried to go to the Partition tab of BI Development Studio. When i click the partition tab of the Development Studio, it discards an error that " An error prevented the view from loading".

Could you please outline me the steps of how to go about this.

I am really stack.

Ronald

Please, could someone bail me out on this.

Ronald

|||

Looks to me something gone wrong with your project. It is also possbile BI Dev Studio installation got corrupted.

I would suggest:

First, try re-create your cube. See if you can create more partitions for you cube and BI Dev Studio allows you to add new partitions.

Second. If you still getting an error trying to navigate to the partitions tab, try re-installing SQL Server on your machine.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||I also found this error last week. My data source is ORACLE database. This raised when I used "OracleClient Data Provider" for provider in Data Source. When I changed the provider to "Native OLEDB\Oracle Provider for OLE DB", this problem was solved.

Hopefully, this post can help you.

Ashari Imamuddin

Errors in DB Integrity Check

I set up a test database to try and understand table partitioning. Since deleting the partition schemas, functions and all relevant info on the database properties page, I am getting the following errors during the weekly database integrity check:

Msg 8914, Level 16, State 1, Line 1
Incorrect PFS free space information for page (1:223) in object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 71776119065149440 (type LOB data). Expected value 0_PCT_FULL, actual value 100_PCT_FULL.

Can anyone suggest why this might be happening?

Thanks

Looks like database file corruption.

Try DBCC CHECKDB ( ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/tsqlref9/html/2c506167-0b69-49f7-9282-241e411910df.htm )

|||

Thanks

I ran this with the

REPAIR_ALLOW_DATA_LOSS option and it sorted the problems. Not something I would like to do on a live database though.

Thanks for your help

Susan

|||

I have the same error, already for the second times now, on a new installed SQL2005 sever running on a Win2003 X64 system.

2 times on a different Db. The Db was only created for a few days and already problems with the CheckDB.

I was lucky that the Db wasn't in use yet so I could solve it with the REPAIR_ALLOW_DATA_LOSS option.

I find this very disturbing because we are running SQL 7.0 and SQL 2000 now for more than 5 years and I never had to use this option on a DB and now it's already the second time that I see it on a fresh created, not used yet, database.

Did anyone has the same experience or is this a unique case?

Greetings,

Ludo

|||

I'm getting the following message

Microsoft(R) Server Maintenance Utility (Unicode) Version 9.0.1399
Report was generated on "VUELOSDATA".
Maintenance Plan: MaintenancePlan
Duration: 00:02:02
Status: Warning: One or more tasks failed..
Details:
Check Database Integrity (VUELOSDATA)
Check Database integrity on Target server connection
Databases: All user databases
Include indexes
Task start: 3/26/2007 3:00 AM.
Task end: 3/26/2007 3:02 AM.
Failed-1073548784) Executing the query "DBCC CHECKDB WITH NO_INFOMSGS
" failed with the following error: "Incorrect PFS free space information for page (1:70) in object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 71776119065149440 (type LOB data). Expected value 0_PCT_FULL, actual value 100_PCT_FULL.
Incorrect PFS free space information for page (1:71) in object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 71776119065149440 (type LOB data). Expected value 0_PCT_FULL, actual value 100_PCT_FULL.
Incorrect PFS free space information for page (1:7394) in object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 71776119065149440 (type LOB data). Expected value 0_PCT_FULL, actual value 100_PCT_FULL.
CHECKDB found 0 allocation errors and 3 consistency errors in table 'sys.sysobjvalues' (object ID 60).
CHECKDB found 0 allocation errors and 3 consistency errors in database 'CFGlobal'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (CFGlobal).". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

How serious is this error?, and how do I repair the database?

www.freebiesms.co.uk

Errors in DB Integrity Check

I set up a test database to try and understand table partitioning. Since deleting the partition schemas, functions and all relevant info on the database properties page, I am getting the following errors during the weekly database integrity check:

Msg 8914, Level 16, State 1, Line 1
Incorrect PFS free space information for page (1:223) in object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 71776119065149440 (type LOB data). Expected value 0_PCT_FULL, actual value 100_PCT_FULL.

Can anyone suggest why this might be happening?

Thanks

Looks like database file corruption.

Try DBCC CHECKDB ( ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/tsqlref9/html/2c506167-0b69-49f7-9282-241e411910df.htm )

|||

Thanks

I ran this with the

REPAIR_ALLOW_DATA_LOSS option and it sorted the problems. Not something I would like to do on a live database though.

Thanks for your help

Susan

|||

I have the same error, already for the second times now, on a new installed SQL2005 sever running on a Win2003 X64 system.

2 times on a different Db. The Db was only created for a few days and already problems with the CheckDB.

I was lucky that the Db wasn't in use yet so I could solve it with the REPAIR_ALLOW_DATA_LOSS option.

I find this very disturbing because we are running SQL 7.0 and SQL 2000 now for more than 5 years and I never had to use this option on a DB and now it's already the second time that I see it on a fresh created, not used yet, database.

Did anyone has the same experience or is this a unique case?

Greetings,

Ludo

|||

I'm getting the following message

Microsoft(R) Server Maintenance Utility (Unicode) Version 9.0.1399
Report was generated on "VUELOSDATA".
Maintenance Plan: MaintenancePlan
Duration: 00:02:02
Status: Warning: One or more tasks failed..
Details:
Check Database Integrity (VUELOSDATA)
Check Database integrity on Target server connection
Databases: All user databases
Include indexes
Task start: 3/26/2007 3:00 AM.
Task end: 3/26/2007 3:02 AM.
Failed-1073548784) Executing the query "DBCC CHECKDB WITH NO_INFOMSGS
" failed with the following error: "Incorrect PFS free space information for page (1:70) in object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 71776119065149440 (type LOB data). Expected value 0_PCT_FULL, actual value 100_PCT_FULL.
Incorrect PFS free space information for page (1:71) in object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 71776119065149440 (type LOB data). Expected value 0_PCT_FULL, actual value 100_PCT_FULL.
Incorrect PFS free space information for page (1:7394) in object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 71776119065149440 (type LOB data). Expected value 0_PCT_FULL, actual value 100_PCT_FULL.
CHECKDB found 0 allocation errors and 3 consistency errors in table 'sys.sysobjvalues' (object ID 60).
CHECKDB found 0 allocation errors and 3 consistency errors in database 'CFGlobal'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (CFGlobal).". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

How serious is this error?, and how do I repair the database?

www.freebiesms.co.uk

Errors in DB Integrity Check

I set up a test database to try and understand table partitioning. Since deleting the partition schemas, functions and all relevant info on the database properties page, I am getting the following errors during the weekly database integrity check:

Msg 8914, Level 16, State 1, Line 1
Incorrect PFS free space information for page (1:223) in object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 71776119065149440 (type LOB data). Expected value 0_PCT_FULL, actual value 100_PCT_FULL.

Can anyone suggest why this might be happening?

Thanks

Looks like database file corruption.

Try DBCC CHECKDB ( ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/tsqlref9/html/2c506167-0b69-49f7-9282-241e411910df.htm )

|||

Thanks

I ran this with the

REPAIR_ALLOW_DATA_LOSS option and it sorted the problems. Not something I would like to do on a live database though.

Thanks for your help

Susan

|||

I have the same error, already for the second times now, on a new installed SQL2005 sever running on a Win2003 X64 system.

2 times on a different Db. The Db was only created for a few days and already problems with the CheckDB.

I was lucky that the Db wasn't in use yet so I could solve it with the REPAIR_ALLOW_DATA_LOSS option.

I find this very disturbing because we are running SQL 7.0 and SQL 2000 now for more than 5 years and I never had to use this option on a DB and now it's already the second time that I see it on a fresh created, not used yet, database.

Did anyone has the same experience or is this a unique case?

Greetings,

Ludo

|||

I'm getting the following message

Microsoft(R) Server Maintenance Utility (Unicode) Version 9.0.1399
Report was generated on "VUELOSDATA".
Maintenance Plan: MaintenancePlan
Duration: 00:02:02
Status: Warning: One or more tasks failed..
Details:
Check Database Integrity (VUELOSDATA)
Check Database integrity on Target server connection
Databases: All user databases
Include indexes
Task start: 3/26/2007 3:00 AM.
Task end: 3/26/2007 3:02 AM.
Failed-1073548784) Executing the query "DBCC CHECKDB WITH NO_INFOMSGS
" failed with the following error: "Incorrect PFS free space information for page (1:70) in object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 71776119065149440 (type LOB data). Expected value 0_PCT_FULL, actual value 100_PCT_FULL.
Incorrect PFS free space information for page (1:71) in object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 71776119065149440 (type LOB data). Expected value 0_PCT_FULL, actual value 100_PCT_FULL.
Incorrect PFS free space information for page (1:7394) in object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 71776119065149440 (type LOB data). Expected value 0_PCT_FULL, actual value 100_PCT_FULL.
CHECKDB found 0 allocation errors and 3 consistency errors in table 'sys.sysobjvalues' (object ID 60).
CHECKDB found 0 allocation errors and 3 consistency errors in database 'CFGlobal'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (CFGlobal).". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

How serious is this error?, and how do I repair the database?

www.freebiesms.co.uk